Database Develop

[Q] Hardware diagnostics for GT-i9000

Around 2am this morning the data connection stopped working on my Gt-i9000 (UK 2.3.4 I9000XJVQ, stock firmware, unrooted) The phone/SMS still work, USB still works, Wifi has never seen anything anyway, but it does the "checking" thing, spins the wheel, etc. It was working fine last night, now, nothing.
I've tried rebooting it, enabling and disabling the APN, nothing works.
Is there any app I can use or any built in code or diagnostics, to look for? I have OS monitor installed but that just shows the interfaces which are either zeroed or 127.x.x.x addresses. It also shows errors in messages but I'm not exactly sure what I'm looking at.
I appear to be getting power management errors and C errors:
[wm8994_samsung.c (wm8994_resume,3483)]------WM8994 Revision = [3]------
these are fairly regular, any ideas?
Are there things to look for to see if the hardware is actually coming up on reboot?
Will flashing to 2.3.5 help, (I have that at home)

Progress.
Well it's not dead, so that's good news
It woke up briefly, told me I had mail, then promptly shut down again. From the logs it appears to be something to do with power management, allied to something holding open a filesystem.
There was a log entry along the lines of, X has responded to power down after (a massive number, [02:00 - 15:00]) of seconds, at which point loads of things resumed, including wlan0, but then went to sleep again. Seems to be some kind of contention/locking issue.
So I'm just going to back it all up and blow it away with a firmware update, at least I know now that the hardware is good.

[Q] S3 Mini constantly powers itself off

Hi - I'm new to these forums and was hoping someone could offer me some advice.
Recenty the only way I can get my S3 mini to work correctly is if its connected to a power source. The device has started to power itself off whilst using it and then it tries to reboot many times unsuccessfully. It seems like it is caught in a restarting loop.
A number of people have recommended I get a full software reset installed, I've used the Samsung Kies to update/reinstall the software but the issue still exists. I was wondering if I went down the route of flashing my fone would this resolve the issue? Any ideas would be greatly appreciated.

[Q] Challenge: hack a phone with shattered screen and digitizer

Well, I've had this phone for a good 3 years, and a few weeks ago it fell out of my pocket and shattered the screen.
Yesterday I've managed to connect to it through adb, although most of the commands weren't working, just kept getting
Code:
/sbin/sh: su: not found
Today, however, I can't seem to connect to it, just keep getting "error:device offline"
So, I thought I'd update my SDK, turns out the one I was using was from 2012.
Updated, but the problem now is this:
Code:
error: device unauthorized. Please check the confirmation dialog on your device.
Of course, as it's a different adb instance, never been authorized. But, as I said, the screen and digitizer are both dead, so no chance of checking that confirmation dialog.
This new adb still works in recovery, so I've already pulled all my files through there.
Now, the challenge is to find a way to bypass this confirmation dialog without access to screen or adb. Then get screencast working. Or this thing:adbcontrol Maybe somehow fix the problem with the old adb and use that to enable the newer one. But better without it. Main reason of doing this is as a learning experience and fun, but also so I can go into an app and get some data out of there (a note app), but that's of secondary importance.
I'm pretty sure USB debugging is enabled, or was last night (maybe that's the reason it stopped working today? Somehow got disabled?)
Phone is rooted, running latest version of SlimKat.
I've been googling for a while now, no leads yet. Anyone got any ideas?

[Q] S5 mini 4.4.2 full stock random freeze/reboots

Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem

contrinsan said:
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
Click to expand...
Click to collapse
This seems to be a common error with the S5 mini. There is a whole thread in the German Android forum about this issue. Also the German Amazon product page for the S5 mini has about 40 users complaining about this problem.
Some users report that the reboots start after some weeks of usage. First it just reboots once per week, then it gets more frequent until it reboots once per day.
Factory resets or firmware updates do not help. Some users sent their phone in for repair but not with huge success.
But not every device is affected by this. So far I did not notice that behavior with my phone (G800F).
I guess it is a hardware issue as not every device is affected and the error gets worse after some time.
The only way to diagnose what's wrong with the device is to check the adb and kernel log (at least the last kernel log before reboot might be available at /proc/last_kmsg). But this would require rooting the device which in turn would void the warranty. It would also be interesting if those reboots also occur with CM 12 (installing this will also void your warranty).
So it seems that sending the device in (without a great chance of repair) is the only option that Samsung gives you without loosing warranty.
Alternatively you also might want to wait for the official Lollipop release and hope that this will fix the problem.
If someone with this problem already rooted his device it would be interesting to get the log files (adb + kernel) of the times of the crashes.

Thanks for your reply, so it might be a hardware problem after all

Device malfunctioned on Windows 10

Recently I've been having problems connecting my P9 to my Windows 10 PC to transfer files between the two. It keeps telling me the device malfunctioned and the device descriptor request failed. I've trawled around Google and followed various bits of advice to make all kinds of adjustments to my machine but to no avail and I've also factory reset my phone multiple times. At one point after the second factory reset my PC did connect to the phone then after about ten minutes it decided the device had malfunctioned again and I've not been able to get it to reset since. One other thing I noticed was that factory resets seem to happen very quickly (as in <30 secs) and when it finishes my phone still has the same wallpaper and also requires I sign in with "the google account that was previously synced to this device" which seems odd, it's like it's not actually reset it at all. I was wondering if anyone else has experienced something similar or might shed some light as to what's going on?