Related
Hello everyone,
I know this question was asked and answered, but the answers didn't solve it for me.
I'm using Eagle's Blood ROM, and I have this problem with Synergy and Jugs. The white line from the last frame of the CRT off animation appears 1st when unlocking.
I wiped Cache and Dalvik and fixed permissions, and the problem went away, however when I rebooted, it came back. I did the wipe and permission fix twice and every time it comes back after a reboot.
I'm sorry for asking this here, but I'm new and not allowed to post in the relevant thread.
Great work on the ROMs and Kernels, you guys are what Android is all about
I think its the kernels man.... I had a lot of issues with the custom kernels on eagles blood :l so flash other roms if you want to use the kernels or jus flash the stock kernel again
Sent From my Galaxy S II T-Mobile
Thanks for the reply
I forgot to mention that I also tried the Juggernaut ROM... same problem there too. I will try other ROMs and see if the problem goes away.
to CWM wipe all caches and fix permissions. that will fix it
Pellel2 said:
to CWM wipe all caches and fix permissions. that will fix it
Click to expand...
Click to collapse
Tried that... won't stick. Try rebooting and tell me if it comes back.
benegessrit said:
Tried that... won't stick. Try rebooting and tell me if it comes back.
Click to expand...
Click to collapse
What kernel? I think it's that. Plus, I think it also may be because of slower graphical performance. I noticed it when the rest of my system was laggy and kinda choppy.
-We do what we must because we can. For the good of all us, except the ones who are dead.-
reflash the kernel
and do these steps
I_am_Error said:
What kernel? I think it's that. Plus, I think it also may be because of slower graphical performance. I noticed it when the rest of my system was laggy and kinda choppy.
Click to expand...
Click to collapse
Pellel2 said:
reflash the kernel
and do these steps
Click to expand...
Click to collapse
I had the same problem with both Synergy and Jugs. I don't think it is because of any slow-down or choppiness; I never had this problem with the stock kernel, even though it has its share of lag.
I think it may be the CRT off effect, it could be conflicting with the custom kernels.
I did flash Jugs twice, and every time the problem goes away after I do the wipe-caches-and-fix-permissions thingy. However, as soon as I reboot, it comes back.
I think I found a solution. Fixng permission clearing cache and dalvic cache didn't work. But a hard reboot worked. Hold power button till phone reboot tada!
lookitzjohnny said:
I think I found a solution. Fixng permission clearing cache and dalvic cache didn't work. But a hard reboot worked. Hold power button till phone reboot tada!
Click to expand...
Click to collapse
I just tried that... didn't work
worked for me... i tried other options.. maybe try pulling your battery out and push hold the power button for 5 seconds and then put battery back in and turn on the device,
lookitzjohnny said:
worked for me... i tried other options.. maybe try pulling your battery out and push hold the power button for 5 seconds and then put battery back in and turn on the device,
Click to expand...
Click to collapse
Just tried that, and it worked, then came back after a reboot.
lol, this is so annoying. Btw, I wanted to thank you for the Crysis and Beam Bat. charging mod., they are awesome
I have a question about them that I posted at the thread
Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
someone please please help me.....
I flashed nikez's rom a month back, and this week it started bootlooping on it's own. random reboots and constant bootlooping. but today, it went completely off the hinges, so i decided to reflash it after full wipe, but now it's even worse. now no other rom boots, it just bootloops. i have tried to flash vj's roms, pa and nikez today, but none of them make it past the boot animation.
PS, i'm not new to flashing, but this phone is very very very precious to me... someone please help me ...............
The Andy Girl said:
someone please please help me.....
I flashed nikez's rom a month back, and this week it started bootlooping on it's own. random reboots and constant bootlooping. but today, it went completely off the hinges, so i decided to reflash it after full wipe, but now it's even worse. now no other rom boots, it just bootloops. i have tried to flash vj's roms, pa and nikez today, but none of them make it past the boot animation.
PS, i'm not new to flashing, but this phone is very very very precious to me... someone please help me ...............
Click to expand...
Click to collapse
You are doing a full wipe before flashing right? Try some gingerbread roms as well, and see if they work.
If youre still having problems, it could be your sdcard. Try doing a full reformat of the card. If even after that its not working, it could be a hardware fault in the card...try a different sdcard. Did you do anything that caused this, or it just suddenly started?
Chromium_ said:
You are doing a full wipe before flashing right? Try some gingerbread roms as well, and see if they work.
If youre still having problems, it could be your sdcard. Try doing a full reformat of the card. If even after that its not working, it could be a hardware fault in the card...try a different sdcard. Did you do anything that caused this, or it just suddenly started?
Click to expand...
Click to collapse
it started a couple of weeks ago. just random reboots and stuff. yes, it corrupted my sd card too. now i have a newly formatted sdcard, with some songs that run ok on my other mobile, and all roms on it that i flashed. but this isn't just working. roms flashes ok, then i reboot device 9in cwm) but then after a few seconds, it bootloops. doesn't even start the rom, then stays stuck at htc logo.
First of all, you should be sleeping
Secondly, you were warned, weren't you? About the consequences?
Thirdly, try wiping your sdcard in cwm, then put on a rom. After flashing the rom, pull out your sdcard, then check if it boots. If that doesn't work, try wiping battery stats too, That's sure as hell gonna solve your problem.
alicarbovader said:
First of all, you should be sleeping
Secondly, you were warned, weren't you? About the consequences?
Thirdly, try wiping your sdcard in cwm, then put on a rom. After flashing the rom, pull out your sdcard, then check if it boots. If that doesn't work, try wiping battery stats too, That's sure as hell gonna solve your problem.
Click to expand...
Click to collapse
Yep, I posted and went to sleep.
I did the wiping in cwm and put cm7.2 on it. During flashing it stopped, and stuck there until I pulled out the battery and did the procedure again, albeit after a bit of time. This time it flashed okay, but the same bootlooping.
I pulled out the battery, and let it be for some time. then I put it in and the ROM started (viola!)
But this didn't remain for long since as I tried to meddle with settings a bit, like turning off mobile data, it did the bootlooping again.
I pulled out the battery again, and in morning repeated the procedure, but the same happens. after little use, it goes bootlooping again.
The Andy Girl said:
Yep, I posted and went to sleep.
I did the wiping in cwm and put cm7.2 on it. During flashing it stopped, and stuck there until I pulled out the battery and did the procedure again, albeit after a bit of time. This time it flashed okay, but the same bootlooping.
I pulled out the battery, and let it be for some time. then I put it in and the ROM started (viola!)
But this didn't remain for long since as I tried to meddle with settings a bit, like turning off mobile data, it did the bootlooping again.
I pulled out the battery again, and in morning repeated the procedure, but the same happens. after little use, it goes bootlooping again.
Click to expand...
Click to collapse
I think there is a problem with your motherboard heating up. Your motherboard is faulty.... It's okay when cool, but not so okay when warm, and that's when bootloops happen. Try freezing your phone, and if it works that way, then you have your solution in front of you. Carry around a minifridge with you.
alicarbovader said:
Try freezing your phone, and if it works that way, then you have your solution in front of you. Carry around a minifridge with you.
Click to expand...
Click to collapse
Hahaha best solution ever
alicarbovader said:
Carry around a minifridge with you.
Click to expand...
Click to collapse
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Chromium_ said:
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Click to expand...
Click to collapse
Hehe
Chromium_ said:
Stealing my technique?
http://forum.xda-developers.com/showthread.php?t=2428600
Sent using xda-developers app
Click to expand...
Click to collapse
seemed legit a while ago
Hello,
I installed today's nightly on my phone and once it would be done starting the OS, I would see the unlock page, then I assume it crashed and reboot over and over again.
I have tried installing older builds (a day old to a few days old) that used to work, still on sd card, but it crashes-reboots after the whole "optmizing apps" thing, and then gets stuck in bootloader loops.
I have wiped cache and dalvik, not yet done a factory reset as I'm hoping to find another solution if possible.
If not I'll just do that.. but hoping something else is feasible
Any idea?
Thanks!
edit: ooooh I just realized today's nightly was for 11.0, I guess no choice but a wipe then.
edit2: yup that was it, and it feels so much faster... or maybe it is because I have not bloated it yet...
/Thread
geearf said:
Hello,
I installed today's nightly on my phone and once it would be done starting the OS, I would see the unlock page, then I assume it crashed and reboot over and over again.
I have tried installing older builds (a day old to a few days old) that used to work, still on sd card, but it crashes-reboots after the whole "optmizing apps" thing, and then gets stuck in bootloader loops.
I have wiped cache and dalvik, not yet done a factory reset as I'm hoping to find another solution if possible.
If not I'll just do that.. but hoping something else is feasible
Any idea?
Thanks!
edit: ooooh I just realized today's nightly was for 11.0, I guess no choice but a wipe then.
edit2: yup that was it, and it feels so much faster... or maybe it is because I have not bloated it yet...
/Thread
Click to expand...
Click to collapse
Try a nandroid backup if you have any and then do a fresh install of the ROM?
UnknownTroll1 said:
Try a nandroid backup if you have any and then do a fresh install of the ROM?
Click to expand...
Click to collapse
Once I realized it was a 11.0 nightly, I wiped it out and it worked right away...
Thanks!
No problem
geearf said:
Once I realized it was a 11.0 nightly, I wiped it out and it worked right away...
Thanks!
Click to expand...
Click to collapse
Hit that little Thanks button eh buddy??
I was on CyanogenMod M5 lately and everthing worked fine. After M6 was released and I flashed it my device started to behave strangly.
Basicly every action has the cance to freeze the device, making it unusable for the next 20 seconds to 2 minutes. These are the symptoms:
1. Screens goes black. Notification bar and software buttoins remain visible but unusable
2. Power button still works
3. screen goes blank eventually
4. Does not come back when power button is pressed, while still frozen.
5. Afrter a while screen can be reactivated
6. Notifcation bar is pulled down; disappears
7. phone is usable again.
I've tried a factory reset to no avail. After this I tried factory reset + flashing Omni Rom. Lastly I tried flashing OmniRom without gapps. I have no idea what i going wrong right now.
If this a known symptom for failing hardware, please let me know.
Kind regards
Maybe its because of their theme engine bug.. Might be solved in next snapshot..
Sent from my Galaxy Nexus using XDA Free mobile app
Yup, the new CM theme engine bug. Either you go back to M5 or use another ROM that doesn't have the new CM theme engine.
I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.
servellia said:
I went back to M4 and It did not resolve.
I'll start to backup my media folders (pictures/music/videos) before something serious happens. After this I'm going to format the sd card and flash SlimKat as a last ditch effort - maybe with another kernel.
Click to expand...
Click to collapse
Did you do a clean install for the M4? People that updated to M6 and downgraded back to M5 without clean install still had the issues. You won't need wipe your SD card.
As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.
servellia said:
As clean as it can get: Factory reset. Format system. Install.
It gets worse everytime.... or my patience is dwindeling. I'm this short of grabbing my hardware-reprogramming-tool (read: hammer) and give it a few good hits.
Click to expand...
Click to collapse
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?
jkleo said:
The Hardware-Altering Magically Miraculous Efficient Rectifier (patent pending) [emoji6]?
In all seriousness, this maybe a dumb question but since I didn't see you mention about wiping cache and Dalvik, have you done that while wiping data and system before flashing a new ROM?
Click to expand...
Click to collapse
Yep, done all of that.
What a shame, I love my gnex. Time to move on.
servellia said:
Yep, done all of that.
What a shame, I love my gnex. Time to move on.
Click to expand...
Click to collapse
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.
jkleo said:
Hmmm.. So you have tried wiping everything and flashing SlimKat and it still didn't work? I had pretty much the same symptoms as you after flashing to M6 and M5 but after I did a clean install to another ROM without the buggy CM theme engine, my phone is working fine again. And since you said your problems began after flashing the M6 build then it should be a software issue, not hardware issue.
Click to expand...
Click to collapse
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SPIGEN case is payed for
servellia said:
Excactly this. Every partition, which is accessible via Recovery has been wiped at least once in the process.
I solved this problem eventually by ordering a Nexus 5 and put the Gnex on ebay. If I can get 20 bucks out of it, at least the SIGMA case is payed for
Click to expand...
Click to collapse
Wow.. Well like they say, if the old doesn't go, the new doesn't come. Enjoy your Nexus 5 [emoji106]!