Twice in the last like 4 days or so, my screen ended out freezing and the colors all of a sudden were really bright.
Anyone know what may be the cause?
I'm running Nebula ROM 1.0.6 and the Gingerbread theme 1.8.5.
It's not a really a big deal to me, but I'm just curious to see if anyone has had this problem.
I am on Nebula 1.0.7 and mine seems to freeze overnight while charging. I get blue led indicating charging complete, and the menu/back/home/search buttons are illuminated.
I used to get occasional freezes like that on stock dk28 as well.
I am running Nebula 1.0.7 and random things just started FCing making my phone impossible to use. I just did 3 more factory resets and cache wipes and it worked like a charm.
I'm on nebula rom 1.07 and don't have any problems. You could make your system unstable if you flash a theme or a mod
Sent from my SPH-D700 using XDA App
Related
Has anyone else experienced this on DK28? It's happening to me quite often.
Is it an unavoidable bug?
Sent from my SPH-D700 using XDA App
are you running stock?
Mhmm, no custom Rom as of yet. Is it a stock only issue?
Sent from my SPH-D700 using XDA App
What are you doing when the phone does that?
Sent from my Evo Killer!!!
Running Facebook, or running the Android market or tweetcaster or the XDA app, but it's stopped so far oddly enough.
EDIT: It still persists to happen. I still haven't figured out why. It's always when the keyboard is out typing. Swype, the Samsung Keypad, as well the GB keyboard.
Sent from my SPH-D700 using XDA App
I get that. Running ext 4 viper rom.
Vibrates twice then reboots.
Then when it turns on, I've went from 66 percent to 13 percent battery life for example.
Strange bug
/And that's my 0.2 florin... Another message exported from Epic4g via Tapatalk Pro
hayabusa1300cc said:
I get that. Running ext 4 viper rom.
Vibrates twice then reboots.
Then when it turns on, I've went from 66 percent to 13 percent battery life for example.
Strange bug
/And that's my 0.2 florin... Another message exported from Epic4g via Tapatalk Pro
Click to expand...
Click to collapse
Same as well. Either the app crashes or my phone will reboot. I reinstalled the leak again and it persists to be that way still. Hopefully the official comes out soon, but for now I'm fine with this.
Sent from my SPH-D700 using XDA App
Does it reboot or shut down?
It sort of sounds like a low battery shutdown. Maybe there is a problem with your battery. I'm just guessing here.
I have seen that happen from a couple of scenarios...
Not doing a wipe after going to DK28
Switching between roms and not wiping
Or flashing a rom or theme that you failed to verify the integrity of the zip before flashing.
I had this problem for a while and it seemed to get worse over time. I backed-up everything and wiped the cache and factory reset in CWM. Seems to have fixed the problem so far.
djbacon06 said:
I had this problem for a while and it seemed to get worse over time. I backed-up everything and wiped the cache and factory reset in CWM. Seems to have fixed the problem so far.
Click to expand...
Click to collapse
I'm going to take your approach to it and try that, hopefully it goes well for me, if not I'll just deal with it lol. Either way I have a functional phone. That vibrates and closes everything lol.
I will report that last night this happened on my walk home.
Phone kept rebooting over and over.
Phone was in my pocket and my hands were full so I could do nothing. Absolutely nothin would bring my device to life expect reinstall the rom. Even when I pushed my data backup I made while it boot looped on me, it would do the same.
So I had to start fresh. I have to say, previously I may have had a bad installation.
I went from 100 to 1 as to calibrate the battery once, no reboot yay. Also before, playing music while getting a text only muted the sound of incoming text for a plit second to where yu wouldn't know if not paying attention, sounds like a skip.
Now it decends volume while sounding the alert, and return music volume as normal.
/And that's my 0.2 florin... Another message exported from Epic4g via Tapatalk Pro
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
If you're using setcpu, raise the screen off clock speed.
Texted while driving
Thanks for the suggestion. I am using set CPU. I looked and can't find that setting. How do I get there?
I am getting the same thing on different ROMS. Specifically the latest Midnight and Syndicate ROMS, which are the only two ROMS I have ever ran. It just started this out of no where as well. I was running Midnight for over a week with no issues, and then yesterday it started shutting off multiple times. So, I wiped everything three times, and flashed Syndicate last night, and then this morning it started doing it again. I just Odin'd back to stock, and am going to see how it runs before rooting and flashing again. I would love to hear what could be causing this issue.
I've been having the same issue. I've had it with the latest Syndicate ROMs, Bonsai ROMs, and Midnight ROMs. It's been very frustrating as I've only been able to reproduce the issue after using the phone for a day our two. It only happens when on battery power and when the screen has been off for several minutes. I've always ensured Set CPU is set to minimum 200 mhz and I've also had the issue without set cpu installed, so I don't think that's it.
I've been doing lots of testing to determine what might be causing it and so far I've eliminated the kernel and ext4 as the culprit. I think it must be some relatively new tweak that all the custom ROMs are implementing. My latest theory is perhaps the NCIQ tweaks.
Thanks so much for the input. Hopefully someone can figure this thing out
Sent from my SPH-D700 using XDA Premium App
mpscmedic said:
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
Click to expand...
Click to collapse
I experienced the same issue, and reported it in the Bonsai 4.0.1 thread, as that's the ROM I'm using. I would defnitely like to know about the solution, as it is quite frustrating when this occurs and it does not allow using the phone without the battery power cycle.
Sent from my SPH-D700 using XDA App
Data corruption
I, have found it is best to fully wipe everything.
I installed srf and got freezes and random reboots.
Then i installed cm7, and re-flashed srf from that not a problem since.
This issue has been discussed before,and i suggested this remedy to fix the ailments.
It is tedious but it works just fine.
Not sure what the problem is, but you probably came from an EC05 stock rooted ROM.
I think that is the underlying cause of these problems.
fully wipe your phone 3 times wipe everything flash cm7 ,you dont need to flash the gapps then flash srf or bonsai and watch them run.
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
TheManCalledX said:
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
Click to expand...
Click to collapse
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
That's the min for gingertiny right? If so, then yes. But I've literally never run into this problem since going from CM back to Sense. Never once had it happen during all my different Sense ROM flashes. Could it be something to do with the way CM does it's storage tree vs sense? I'm at a loss right now and just want some ideas on what to look into.
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
TheManCalledX said:
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
Click to expand...
Click to collapse
Flash amon ra recovery from rommanager. Then go into the recovery and select other anf fix apk uid mismatches, and fix permissions. You can flash back to clockwork when your done. I would also raise your min freq to 245000, and try that for awile.
Okay, I flashed a Nandroid backup from the very first day I rooted my phone. Then a couple others from other sense ROMs I have run. Every once in a while I'm still dealing with a little lag loading something, and I'm trying to let things settle in for a couple days before I flash a new kernel.
But, a friend at work also has an Inc, and after going from Sense to CM back to Sense, he's experienced similar problems. So I have a vague idea of what the problem is, but literally no idea how to fix it.
cmlusco said:
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
Click to expand...
Click to collapse
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
EDIT: I thought i would also mention that this happens on all governers except performance, not just on sa or sa2.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
cmlusco said:
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
Click to expand...
Click to collapse
I never had the problem using 128 before I switched to CM and back to Sense.
TheManCalledX said:
I never had the problem using 128 before I switched to CM and back to Sense.
Click to expand...
Click to collapse
Well i have never used CM, i have always used sense roms.
Try smartass governor (not smartass v2) and see if it helps. I don't know about reboots but there is no wake lag or virtually none.
Sent from my ADR6300 using Tapatalk
Ok, I posted a test release in the kernel thread. Please test it if you're having lag issues.
to themancalledx
I had the exact same problem going from aosp to sense. For me it was a pretty simple fix. I hope it works for you. Go into recovery select advanced and then fix permissions. Good luck.
New kernel released. Try that one.
Sent from my ADR6300 using Tapatalk
I just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?
Using it the last few days w zero issues. Which one are you using and how did you flash?
Sent from my SPH-D710 using xda app-developers app
I just installed it myself yesterday, but all has been good. I haven't had any of those problems. You probably should download it again and flash it again.
kdubhotsauce said:
I just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?
Click to expand...
Click to collapse
Really stupid question, but did you use "Calkulin's_FORMAT_ALL_for_E4GT" zip file before flashing CM9? I only ask because I have had issues in the past with other roms by forgetting to wipe everything beforehand. Even the savvy tech could forget something sometimes :silly:
I'm running the exact same ROM. I underclocked mine down to 800Mhz to save battery and it was causing constant restarts. I moved it up to 1000Mhz and they stopped. If you tried messing with the clock speeds that might have caused it
OP, did you fix your problem or did it just go away? I recently flashed mine to cm9 alpha 6 and am having the exact same problem. Never has this phone had problems before.
Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!
sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?
I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).
I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.