Database Users

Galaxy s4 i9500 freezes FOR HOURS!!

i9500
when i go sleeping, i keep my device on for alarm and stuff you know..
but in the morning, i turn on the device, and lock screen says "1;15" AM.. which means the time is stuck and not updated, and its stuck since this time until the morning.. it doesnt even reboot itself!
in addition, I can NOT do anything.. its stuck for no reason! alarm is disabled and i can NOT receive calls as well.
I have nothing to do.. i have to take out the battery and turn in on again.. and it happens A LOT!
even after updating my device using KIES, it still happens.
for some reason, it seems the system application always crashes
some information about my device:
I9500, android 4.2.2
STOCK ROM, NOT ROOTED-- XXUAHMDK
kernel version- 3.4.5 april 23
**I have not installed any applications/ never made any changes in the device..
I know an update has been released a few days ago, but according to my device, the latest software is already installed and no updates have been found yet

darixtorento said:
i9500
when i go sleeping, i keep my device on for alarm and stuff you know..
but in the morning, i turn on the device, and lock screen says "1;15" AM.. which means the time is stuck and not updated, and its stuck since this time until the morning.. it doesnt even reboot itself!
in addition, I can NOT do anything.. its stuck for no reason! alarm is disabled and i can NOT receive calls as well.
I have nothing to do.. i have to take out the battery and turn in on again.. and it happens A LOT!
even after updating my device using KIES, it still happens.
for some reason, it seems the system application always crashes
some information about my device:
I9500, android 4.2.2
STOCK ROM, NOT ROOTED-- XXUAHMDK
kernel version- 3.4.5 april 23
**I have not installed any applications/ never made any changes in the device..
I know an update has been released a few days ago, but according to my device, the latest software is already installed and no updates have been found yet
Click to expand...
Click to collapse
There could be some thing causing the issue like some app, bad files etc
Have u tried complete Reset from ur device and if possible also from a memory card u have that should solve the issue for u
Incase u havent recieved any update u can manually install the same using ODIN
and can download a New updated version from below link
http://samsung-updates.com/device/?id=GT-I9500
Let me know incase anything else u wanna know

guess need to send to gurannty
---------- Post added at 02:32 PM ---------- Previous post was at 02:32 PM ----------
also try factory reset!

Try a factory reset or reflash the stock firmware (as suggested by other members here already). If that does not work then it is time you took it back

my samsung galaxy s4 i9500 going restart again and again. sometime its going on for 5 min, i uninstall all the application but when its restart again same applications showing there. even cant recovery mode. i tried in download mode but odin shows fail.
please help me, that one rooted mobile.

[Q] a dying nook ?

Hi all
A while ago my trusty nook started to behave erractically and then wouldn't boot at all. I removed the battery, reattached it and still no boot. Before I threw it out I left it for a few days and for some reason it started to boot again BUT it had problems so I flushed all the memory locations, reset it back to CM7 factory defaults and reloaded. All seemed to be well for about a month THEN this week I got the phantom key strokes issue and some erratic behaviour. Today it really started to go wrong, here are the symtoms:
1 100% battery all well and function fine
2 85% battery ( about 15 minutes into a streaming vid) noise on the audio
3 81% play bar on stream started to flash on and off though fingers no where near it
4 80% screen flash then shut down.
5 boot only to seemingly frozen CM7 android logo no looping arrow.
6 can't boot to recovery
7 took out sg card freezes at CM7 logo.
So is this really the end of my old buddy? I have pretty much tried everything.
thanks

Charge for 3/4 hours while turned off completely with stock charger.
Create a clockworkmod recovery sd card. (not twrp since you have touchscreen issues)
Boot into cwm and wipe everything but system and boot. (Battery stats, cache, data, etc)
Reboot.
Charge for another hour.
Profit.
---------- Post added at 10:28 AM ---------- Previous post was at 10:25 AM ----------
If that doesn't work, look in leapinlar's tips thread, and use his format tools to format everything, then boot into cwm from the sd card, and install the latest cm7 stable, GAPPS, etc.

Mineturtle33 said:
Charge for 3/4 hours while turned off completely with stock charger.
Create a clockworkmod recovery sd card. (not twrp since you have touchscreen issues)
Boot into cwm and wipe everything but system and boot. (Battery stats, cache, data, etc)
Reboot.
Charge for another hour.
Profit.
---------- Post added at 10:28 AM ---------- Previous post was at 10:25 AM ----------
If that doesn't work, look in leapinlar's tips thread, and use his format tools to format everything, then boot into cwm from the sd card, and install the latest cm7 stable, GAPPS, etc.
Click to expand...
Click to collapse
thanks for you great advice BUT had already done all of the above before I posted. Rebuilt it from scratch ala leapinlar's tips ( really useful) no luck. Just read a book until the power dropped below 65% then erratic behaviour starts. Was reading using coolreader, first the pages start to turn without any touch. Then menus pop up and icons get pushed. I just shut it down and will power it back up to 100%. Cleaned the screen completely. So pretty sure this is a power issue as it happens at 65% and below. Above that it's perfect.

Replace the battery. That's all I can say. That or get a replacement if you can fake unbroken warranty.

Mineturtle33 said:
Replace the battery. That's all I can say. That or get a replacement if you can fake unbroken warranty.
Click to expand...
Click to collapse
thanks for trying but I'll just keep it for parts. Still would be interested in finding out why low battery makes the phantom key presses appear.

[N910F]Random reboots (links to logs included)

Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .

*bump*

I have the same problem. Help would be highly appreciated. : )

*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?

Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...

I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1

[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.

The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!

Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart

Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!

Galaxy S5 Freezes

I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.

Similar experience from another user....
Literally could have written your post word for word (S5, 14.1, same symptoms) and created an account to tell you so, but it won't let me. Still a n00b in many respects but I've backed my way out of enough soft bricks to not feel totally out of my depth when I say "This is weird, but probably not unique." So, thanks.
Additional info, in case it helps in any way:
- T-Mobile network
- was working fine until about 8:45pm when it died while I was making a call. Plugged it in, turned it on, freeze.
- Recently installed a new SD card because my old one was unreadable, discovered by "too little storage, delete some apps." 128GB Samsung brand (just because I was bitter about it). Promptly made a full backup Jan 20. Tried to restore it but it was giving me a LOT of **** about making the SD internal, and I got so frustrated that I gave in. Result: "Cannot restore modem -- mounted read only." Restoring everything but the modem now.

Moved to Galaxy s5 Q&A

same same
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.

novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
tron65 said:
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.
Click to expand...
Click to collapse
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.

martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
i am now again using nougat, the latest nightly fixed all problems, i suppose it was a bug in the specific version, then. now i am at 7.1.2
cheers

martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
I only found a solution doing a full install and going back to 6.0.1. The latest (last) CyanogenMod build didn't work for me, and now they're defunct anyhow.

S5 Prime half screen jumping up and down

Hi, I have an S5 prime SM-G906L that has been working great for the last 2 years. I installed blue light filter pro a few months back for reading in low light and it was working great. When I didn't need the filter e.g. during the day I would turn it off, then a week ago whilst off the right hand side of the screen started to jump up and down but only in apps with text not games. Anyway I have so far uninstalled the filter app and also cleared the cache and even did a hard reset and upgraded from 5.1 to 6.01 but the flickering is still there. It does go away when I use the blue light filter app on green at 20% or more which is a handy temporary fix for now.
My question is would a complete wipe and a fresh install of android fix it or does it sound like the hardware is on its way out?
Many thanks in advance

I don't think the hardware would work with some apps and not others if it was dying... If you have custom recovery get a ROM and wipe the phone 100%, I mean put your music n photos on your SD card and go to advanced and wipe data, system and internal storage. Do not wipe modem or anything else there or you hurt your device. If you are on stock... Flash twrp recovery using Odin and still do the above. You can reflash stock too but I suspect something in your system is buggy or altered and as the upgrade kept your files the issue still persists. That's why I want you to delete everything and start fresh.
---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------
Make sure the rom being installed is on the SD also