Samsung Mobile Phone

[cronk-flakes]

Hi there,

If anybody could help me out I would greatly appreciate it.

A mate of mine has a Samsung Z-140v mobile phone. But recently it has taken a turn for the worse. The phone has become unusable. Everytime he turns it on it comes up with a blue error screen. With a load of characters. The error screen can be seen in the picture below.

Any ideas wouldbe greatly appreciated.

Thanks alot.

J

EDIT: A link to the photo would help - Photo

Edited by cronk-flakes on Saturday 4th November 17:55

[plasticpig]

Buy a new phone. Not very helpful I know but that screen it indicates that something is very broken on the phone. What you could try (if it is possible) is to update the firmware on the phone.

[ThePassenger]

Major fault, probably hardware related.

The 'DigiWatchdog' / 'DigiWatchguard' is basically a error handler designed to trap errors and deal with them in a graceful manner (so it handles dropped calls, lost signals, corrupt pictures, etc). A google search for various things in that picture doesn't give any pointers other than the general assumption that something known to the phone as 'Mocha' has failed.

If it's under waranty get it changed, if it's not go buy another one as this unit is fecked.

[cronk-flakes]

Yeah, i thought about the firmware, but looking around, i dont think the z-140v was one of samsungs major handsets, so theres not much i can find by updates.

Thanks for your help, appreciate it. Does help me understand it a bit more.

Thanks again.

J

[plasticpig]

ThePassenger said:

Major fault, probably hardware related.

The 'DigiWatchdog' / 'DigiWatchguard' is basically a error handler designed to trap errors and deal with them in a graceful manner (so it handles dropped calls, lost signals, corrupt pictures, etc).
If it's under waranty get it changed, if it's not go buy another one as this unit is fecked.

Failing on an assert is hardly a graceful way of saying the phone is broke. Asserts are for developers to find out the code is broke they should not be used for error handling. The end user should get a nice pretty graphic and some text saying something like "I am sorry this phone is broken. Please go and see you nearest Samsung phone dealer to purchase your new phone. Have a nice day!"

[ThePassenger]

plasticpig said:

ThePassenger said:

Major fault, probably hardware related.

The 'DigiWatchdog' / 'DigiWatchguard' is basically a error handler designed to trap errors and deal with them in a graceful manner (so it handles dropped calls, lost signals, corrupt pictures, etc).
If it's under waranty get it changed, if it's not go buy another one as this unit is fecked.

Failing on an assert is hardly a graceful way of saying the phone is broke. Asserts are for developers to find out the code is broke they should not be used for error handling. The end user should get a nice pretty graphic and some text saying something like "I am sorry this phone is broken. Please go and see you nearest Samsung phone dealer to purchase your new phone. Have a nice day!"

Didn't know what an assert is as tbh I couldn't program my way out of a plastic bag; I do a nice line in shell scripty and C utilities to help me admin machines but that's about it.
Probably find that the thing is complaining it can't get to the "Your phone is broken. Go away." section of code, it is saying "NEVER GET HERE" in the text so I think it's proper fecked

[R1 GTR]

Just hoope it doesn't happen to mine!
It's been fine so far........

Edited by R1 GTR on Sunday 5th November 17:27

[cronk-flakes]

aha! Forgot to mention, if it does happen to anyone. Its simply fixed by a master-reset. Lose all your photos and stuff....but phone works.