Related
I usually don't flash a new version of cm7 until 8 to 10 nightlies pass. I'm on 51 now so ill prob wait til low 60's to flash again. How often do you flash or upgrade?
ITS ALL WONKY!!!
I usually look at the changelog to see if any big updates have been made and then look in the nightly thread to see if people are having problems. If not, I'll flash.
You're missing out. 56 is a rock!
I flash every 2 to 3 nightlys unless changelog shows they have change something dramatically. On 54 right now
Sent from my LG-P999 using XDA Premium App
Every.. single.. morning haha! keep a nandroid backup handy
Sent from my LG-P999 using XDA App
jonnyboyca said:
Every.. single.. morning haha! keep a nandroid backup handy
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
yup I do the same minus the nandroid backups... I live on the edge
( I do have them but they are like a week or two old)
I upgrade once a week..
everyday unless there wasn't really anything changed. remember all you have to do is flash an old version no need to do a nano since when you flash the old version it over writes what had changed. I also do a titanium backup before each flash since if i need to wipe that puts me back to where i was at anyway.
I just have my stock nandroid backup in case I ever want to go back
Sent from my LG-P999 using XDA App
I upgrade daily in the morning.
#55 and #56 have lots of new fixes.
Battery Driver, Dual-Radio bandwidth (doubles bandwidth), Builtin Notification Backlights, etc.
I don't see much difference between #55 and #56 but I'm sure there are some tweaks. So grab the latest and go. Anyone using CM7 should upgrade to #55 at least.
Nightly, and literally nightly.
Haven't run into crashes since well, i reboot every darn day.
While charging overnight it does freeze (known issue seen other have same issue).
That darn battery.
I took a break from CM7 just to try Evil's ROM. Also other reason I stopped was the brightness issue. 55+ the issue went away.
vmartinez39 said:
Nightly, and literally nightly.
Haven't run into crashes since well, i reboot every darn day.
While charging overnight it does freeze (known issue seen other have same issue).
That darn battery.
I took a break from CM7 just to try Evil's ROM. Also other reason I stopped was the brightness issue. 55+ the issue went away.
Click to expand...
Click to collapse
The brightness was fixed on earlier roms but came back, then went away, and came back. Brightness bug came back around #53 and fixed on #55.
Mine doesn't freeze, reboot, or lockup while charging over night... on any CM build.
I'll be honest I'm rooting for CM7 and will be my final ROM when it reaches stable/RC version. The crashes/reboots are gone and I don't keep the uptime past 20+ hours because I keep flashing to the latest ROM.
Battery freeze is disappointing, but I blame it on the hardware/LG. Its not perfect but its getting there. Gingerbread update will fix this. It better
I usually look at the channel log to see what has changed, but every 2-3 days. If I am having good luck with the current build I will stick with it, if it is giving me issues, I will update on the next build. I was on 54 for 2 days (with the same battery charge) and updated to 56 yesterday. After only using 20% of my battery after 12 hours of mild use and a lack of any cool/important updates, I will stick with this build for another day or 2.
You really should update. 54 fixed a LOT of problems: the battery meter now gives accurate readings and data speeds are doubled.
Any time there is fresh Gigglebread;-)
Swyped from HTC Pyramid, using XDA Premium App.
I was updating every morning before work but right now im on 56. Its been running pretty good for me so im probably going to stay on this one for a little bit.
Sent from my LG-P999 using Tapatalk
Every day since I started using CM7. 21:35:33 on #57 so far...
LordButtersI said:
You really should update. 54 fixed a LOT of problems: the battery meter now gives accurate readings and data speeds are doubled.
Click to expand...
Click to collapse
I know. I wanna be done with this backloght crap but I'm gonna wait until I need to reboot because I wannna see howblong of an uptime I can have. I'm just about at 105 hours ans no reboots so far.
ITS ALL WONKY!!!
I flash almost every day. I keep nandroid backups on my SD, my desktop and my dropbox. I guess I'm paranoid.
Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?
No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...
Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?
Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Mines running fine. Maybe try reflashing?
jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.
Hey guys,
The topic of this thread has change slightly since I started it. Please disregard the first few posts after this one.
The problem is that when I install a new ROM, it works perfectly for an hour or perhaps even the day, and then I start getting random shutdowns. These seem to start out of the blue and I cant work it out.
When installing a new ROM, I always check the MD5 and perform a superwipe before starting to use the ROM. Ill put back a few apps using titanium backup pro.
I don't use any hacked apps or task killers.
I have searched but cant find anything useful.
Currently using Insertcoin Sense 4 RC5. Firmware 3.32.
I have tried three different kernals (Bricked, Sebastian and RCMix), all with the same problem.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz with max screen off at ~500Mhz. Seems stable for now, been running 24hrs - no restarts.
This is interesting because I had a GB Rom running at 1.5Ghz with no problems, maybe its something to do with ICS.
Any ideas?
[SOLVED]
Sent the phone off to htc and they have replaced the motherboard. Its all fine and dandy now!
They dont know why it happened or how to avoid it in the future...useful, but if you're still in warranty then send it off, it took exactly a week to get back to me (Monday to Monday). Good luck!
Max
Well no need for factory reset. Superwipe? Yes.
What roms cause this?
What firmware is ur senny on? Ex: 1.17? 3.24?
Phone have physical damage?
Has it been wet?
Sent From Space Using My ICS Flavored Sensation
Thanks for your reply.
No, the phone is basically new, but as I said this has happened before.
Running this ROM on 3.24:
http://forum.xda-developers.com/showthread.php?t=1468683
But this does happen on other ROMS too, they work perfectly for a while and then slowly begin to develop problems. At this stage I usually install the latest version of the ROM but I'm actually happy with the ROM at the moment and dont want to have to keep changing it!
I've been running Darkforest ROM since early stages and have had no problems so far. Maybe try that one. It's on v 5.1.5 now and it's very fast and very stable, moreso than many other ROMs i've tried.
Could be a defective device possibly? Are u using the kernel that comes with the rom?
Sent From Space Using My ICS Flavored Sensation
I would download 1-click cleaner and clean the cache every week. Also you might want to boot into recovery and wipe cache and dalvik cache every two weeks.
Sent from my HTC Sensation 4G using XDA App
I dont think there is anything wrong with the device, I'll try wiping the cache's and see if that makes a difference. Thank you very much for all your answers so far.
Max
Could possibly be an app try removing all your apps and install 1 by 1 give it a couple of weeks see if it happens again, I got a problem from juice defender pro (payed for) worked alright for few days then my launcher started force closing all the time took me ages to figure it out but got there by removing all my apps and installing them 1 by 1 long and time staking but worth a try
Sent from my HTC Sensation Z710e using xda premium
Okay well ive tried clearing the cache and davlik cache with no luck, less restarts but they are still there. I am resistant to start removing apps as I use them on a daily basis. Before I try this, does anyone have any other ideas?
Thanks,
Max
I have the same problem :/ it happens in both GB and ICS but It never happened to me till about 2 or 3 months ago
Sent from my HTC Sensation Z710e using xda premium
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
darksupernova said:
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
Click to expand...
Click to collapse
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
ardom said:
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
What other information would you like?
I think it may be a kernel issue, I'm going to try a few...
Tried three different kernals now, all with the same problem which would indicate its not a kernal problem? Something else perhaps? (Tried bricked, sebastian and RCMix)
its not a problem, its with network connection
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Danyal93 said:
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Click to expand...
Click to collapse
Pretty sure its a power/bat problem for me.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz
Any ideas?
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Having EXACT ones you are having. Buy another battery if that doesn't work its a hardware problem. I still need to buy my battery but will post and let you know if it worked.
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
darksupernova said:
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Click to expand...
Click to collapse
I'm also starting to think its caused by not letting the battery fully die and recharging it a lot but that's just my guess?
I switched back to gingerbread yesterday and so far I've had no problems which would indicate its not a hardware issue...? Usually by now I've had a few shut downs..
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
sickorwuut said:
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
Click to expand...
Click to collapse
Yeah the problems started again for me on gingerbread. I've read its a motherboard problem I think I'm gonna have to send it off to HTC... Great... 3 weeks no phone...
I am on AOKP B31 without fast charge enabled but seem to have a problem with the phone charging when off. If I plug it into a USB or wall charger, both samsung, the initial battery screen will come on but after the screen turns off it will not turn back on. I left it there for 30 min turned it on and it showed 50% more battery. We all know with a samsung that is not possible. Just want to see if others are having this issue, or a fix.
Thanks in advance.
I am sporadically having this issue as well- Samsung charger, AOKP b31. I will play with it over the weekend and see if I can figure anything out. For the moment I am not seeing this behavior, but initially after flashing I did...
I have not had this issue on any other THS or AOKP build and I have used a lot of them. The last one I was on was milestone 4 and it was fine.
Sent from my AOKP ICS captivate using XDA
Hmm, still doing it. Setting the Min CPU to 200MHz has not helped, as I have seen posted elsewhere. Charging screen turned off at some point, and when I booted up it was at 64% (from 7%). I'm not super worried about it though, seeing as how I flash like crazy and will not be on Build 31 for any length of time. If I get this on other builds or other Roms I will update again.
Edit: Build 32 is out, so I am going to flash and see if that resolves the issue. I am wondering is this is a kernel issue, as the Glitch for Build 31 was the first time I had switched from Glitch version 14 beta 6. Maybe I'll try the Semaphore kernel if the issue remains.
I flashed 32 and it still is the same issue. Also tried the min CPU increase but nothing. Hopefully it will be fixed soon. My concern is that it will continue to charge after 100%.
Sent from my SGH-I897 using XDA
read the first post of AOKP. report bugs where it tells you to. they will not look here, or will they care if they do look here, if you do not follow their instructions for reporting bugs.
look to see if the bug exists, and if it is there, click the STAR to vote for the issue as that page says to do.
I have read the OP but I did not want to flood the bug tracker if it was a problem already found or known. I did not have the 10 posts needed to post in the development section, so I figured start this to see if anyone had an issue. I know how much everyone hates the development thread being diluted with dumb question after question. I did report it on the bug reporter site.
P.S. - Thanks for your essentials mod, makes everything much easier.
Just wonder - will disable fast charge help?
I have not enabled fast charge. I thought that only effects charging when on USB? I could be wrong though.
Sent from my SGH-I897 using XDA
I have been testing with both i897 and i9000 bootloaders. This may be a Glitch kernel issue, as I have flashed Semaphore ICS kernel 1.0.0 and have not seen this. Looks like there is already a bug reported in the AOKP page. Not a huge concern though, I think, because the phone seems to charge nevertheless.
Alright Guys i needs some help ive been trying for days to trigger where the heat issue is coming from. Now im not a Vet but im not no noob. ive searched countless threads from android Donut to Jelly bean. so far i havent found the full triggers yet but i have found that if your ram is running around 50mb left over and extensive downloading example long period download like a ROM the heat starts to spike any where from 78 to 111.2!!!
so my question is does anyone else experience this as well im currently runnign slim bean/hotcakez NO oc runnning 384-918 ive tried every rom/kernel and i still experience the same issue and depending on the heat my phone SMELLS LIKE BURNT Bacon lol help please
crashpsycho said:
Alright Guys i needs some help ive been trying for days to trigger where the heat issue is coming from. Now im not a Vet but im not no noob. ive searched countless threads from android Donut to Jelly bean. so far i havent found the full triggers yet but i have found that if your ram is running around 50mb left over and extensive downloading example long period download like a ROM the heat starts to spike any where from 78 to 111.2!!!
so my question is does anyone else experience this as well im currently runnign slim bean/hotcakez NO oc runnning 384-918 ive tried every rom/kernel and i still experience the same issue and depending on the heat my phone SMELLS LIKE BURNT Bacon lol help please
Click to expand...
Click to collapse
Have you tried going back to stock with Odin?
Not sure if your issue is the same as mine, but after I went back to stock it seems to have corrected the issue. It still seems to warm up a little when I'm using it a lot (playing a game, looking at the LOL Droid app, but not, oddly, playing a video) but the battery issue seems to have been solved.
I know that using the phone is going to make the processor run faster, and that faster processor speeds can definitely contribute to heat build up. Do you have a case? If so, take it off. If not, maybe give the phone a break every now and then? I don't know.
liquidzoo said:
Have you tried going back to stock with Odin?
Not sure if your issue is the same as mine, but after I went back to stock it seems to have corrected the issue. It still seems to warm up a little when I'm using it a lot (playing a game, looking at the LOL Droid app, but not, oddly, playing a video) but the battery issue seems to have been solved.
I know that using the phone is going to make the processor run faster, and that faster processor speeds can definitely contribute to heat build up. Do you have a case? If so, take it off. If not, maybe give the phone a break every now and then? I don't know.
Click to expand...
Click to collapse
Yes sir reverted several times to stock and back to another even happens on ICS personally I think its my phone but wanted to know if anyone had similar issues. Thanks for the feedback
Sent from my SAMSUNG-SGH-I727 using xda premium
I had a over heating issue a while back... Turned out to be a run away wake lock. Media scanner. I had to Odin back to stock and rebuild back to the custom rom to totally get rid of it.
Sent from my SAMSUNG-SGH-I727 using xda premium
crashpsycho said:
Yes sir reverted several times to stock and back to another even happens on ICS personally I think its my phone but wanted to know if anyone had similar issues. Thanks for the feedback
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You never know...it could be the weather around here
I would install Better Battery Stats (if you don't already have it installed) and monitor it for wakelocks to see if something is preventing the phone from deep sleeping.
liquidzoo said:
You never know...it could be the weather around here
I would install Better Battery Stats (if you don't already have it installed) and monitor it for wakelocks to see if something is preventing the phone from deep sleeping.
Click to expand...
Click to collapse
Agreed az is known for pure heat not humidity thank god lol but I will check my wake locks again again and try to find what's cause media scanner only runns once at boot otherwise doesn't need to run. But I think I might switch back to stock and see if it does it on rot stock
thanks guys
Sent from my SAMSUNG-SGH-I727 using xda premium