I am having SERIOUS issues with the new version of the ROM. It is super glitchy and very unresponsive... Is there anyone that is having similar issues? If so, did you get them fixed? How? I loved 1.5 but 1.6 is giving me serious fits...
If you did a full data wipe prior to installing you should be cool. Try re-downloading the ROM and make sure you check the md5 to see if they match the original posting's md5. Seems like a lot of problems occur due to the download/upload not pulling properly, so always check the md5 before flashing. Full data wipe is always the way to go if you're running into problems.
You can grab an md5 checksum program here if you're on Windows: http://www.pc-tools.net/win32/md5sums/
I did do a full wipe but I didn't check the md5 I will look into doing that! Thanks for the response...
Edit: Checked the MD5 and it matches :/ So should I try a full wipe again to see if that fixes it?
Try that same rom with a different kernel.
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
nhartse1 said:
I did do a full wipe but I didn't check the md5 I will look into doing that! Thanks for the response...
Edit: Checked the MD5 and it matches :/ So should I try a full wipe again to see if that fixes it?
Click to expand...
Click to collapse
I would recommend downloading again from another location to be safe. And check the md5 before and after you place it on your SD Card. Keep us posted.
Same issues here. I checked the md5 before flashing, and did a full wipe. No good...
Sent from my ADR6400L using XDA App
I did wiped twice and flashed the ROM again... Seems to be running better now. I got everything fixed in time for the 1.6.1
Sent from my ADR6400L using XDA App
This is the smoothest bamf yet for me, everything is working better than ever here. You must have done something wrong somewhere. If you installed it from ROM manager try doing it manually instead, sometimes ROM manager is screwey.
how is the BAMF Remix on battery compared to normal BAMF? Or BAMF remix compared to stock rom? I want to take the plunge and get my first TB Rom going, have some hesitation. I am happy with the kernel/rom combo I have going now but I wouldn't mind some eye candy either.
any comments appreciated
I can't get the 6 bar signal strength indicator to show up or the time stamp to go away on the status bar. When I reboot, the 6 bar indicator shows up intially when the phone doesn't have signal, but once it picks up signal it reverts back to the old 4 bar indicator. Used the BAMF toolkit to try and remove the status bar clock and no dice. Any ideas what I'm doing wrong?
sprodigy said:
how is the BAMF Remix on battery compared to normal BAMF? Or BAMF remix compared to stock rom? I want to take the plunge and get my first TB Rom going, have some hesitation. I am happy with the kernel/rom combo I have going now but I wouldn't mind some eye candy either.
any comments appreciated
Click to expand...
Click to collapse
I'm not sure about the difference between the regular and the remix. I have only used the remix. I think the battery life is pretty rocking, but I use the imoseyon lean kernel extreme or 1.92X. I get awesome battery life from the extreme kernel but not so much from 1.92X (because of the MASSIVE overclocking). The best thing to do it try it out there is no harm in doing so, in fact that is the best way to find the combo you like best!
Sent from my DAS BAMF 1.6.2 ThunderBolt!
I'm confused, I flashed DAS BAMF 1.6 and the animations, toolkit, and battery with the percentage are there. Although I'm not debloated, still have blockbuster and all the VZW apps. I don't have the 6 bar signal either. What did I do wrong, I flashed this using ROM manger and wiped data and cache and davlik cache. Has anyone else had this issue?
EDIT: Fixed the issue, evidently flashing with ROM Manager was the problem. Did it manually and all is good.
Random Reboots
I'm getting random reboots with this version. I also had this issue with the previous version. Has anyone else had this issue? MD5 is good, I have not overclocked just using standard clock speed, but I have not tried any different kernals. Ahy help would be appreciated.
toadzilla said:
I'm getting random reboots with this version. I also had this issue with the previous version. Has anyone else had this issue? MD5 is good, I have not overclocked just using standard clock speed, but I have not tried any different kernals. Ahy help would be appreciated.
Click to expand...
Click to collapse
Are you using the new leaked radio? If you are that is causing a lot of people random reboots. I was having trouble with reboots with that leaked radio, flashed back to stock and all is good.
Yes I am. Maybe that is the problem. Thanks for your help. I changed kernels this morning and I'm going to let that run for a while and see, but if that doesn't help then I'll flash the old radio back and try that. Thanks Again.
toadzilla said:
Yes I am. Maybe that is the problem. Thanks for your help. I changed kernels this morning and I'm going to let that run for a while and see, but if that doesn't help then I'll flash the old radio back and try that. Thanks Again.
Click to expand...
Click to collapse
Sounds like some random stuff. I installed Das Damf Remix 1.6 yesterday with whatever kernel it comes with. I also installed the new radio before installing the rom. I'm clocked at around 1.2 ghz max with the smartass scaler. I haven't had a single problem with reboots or anything. I wonder whats different? Did you wipe your data and cache first?
When I installed the 1.5 I did a complete wipe, installed radio and then the ROM. As a matter of fact I'm still a little old school and did the 3 wipes like we used to with the D1. I had the issue with 1.5, so I did another wipe re-checked the MD5 and reinstalled. Still had the same issues. It is random some days no reboots, and some days 4 or 5. So far wiht the new kernel installed I have not had a reboot, but the day is young. I'm gonna run this set up for a few days and see how it works. It already seems a little smoother than it was with kernel that comes with the ROM. We shall see!
I am having trouble with the new 1.6.2, when i was on 1.6.1 everything was perfect. now i am having battery issues... I went and saw a movie last night with 90 % battery and when i came out of the battery i had 20 % battery and i checked the battery usage and it said the phone hasnt slept since i unplugged it and that the main cause of battery drain was system or something was running. I had nothing running and again today the same thing. another issue is depending on who i call especially another verizon phone the people on the other end cant hear me. i have to restart my phone and then everything works fine. ANY IDEAS!!!
Das BAMF 1.6
I also had various issues with the 1.6 version. Altho, I did mess around with some of the BAMF toolkit stuff (it did warn me it could mess things up). I love the BAMF ROM's so far. My only customization is a transparent flip clock and transparent status/task bar (and wallpaper, of course). OH, and it always changes my wallpaper on reboot?
EDIT: Running on new radio as well. And getting the random reboots. Thought it might be the OC'ing, so removed it and running stock. Still get the random reboots. Will revert to old radio, as it didn't seem to help with GPS at ALL..
Mayhem8869 said:
I also had various issues with the 1.6 version. Altho, I did mess around with some of the BAMF toolkit stuff (it did warn me it could mess things up). I love the BAMF ROM's so far. My only customization is a transparent flip clock and transparent status/task bar (and wallpaper, of course). OH, and it always changes my wallpaper on reboot?
EDIT: Running on new radio as well. And getting the random reboots. Thought it might be the OC'ing, so removed it and running stock. Still get the random reboots. Will revert to old radio, as it didn't seem to help with GPS at ALL..
Click to expand...
Click to collapse
Definitely try out the stock one, you will have no more issues with random reboots. I actually didn't get as good of a signal on the leaked radio, odd I know.
Related
I recently went from the original leaked froyo rom to super clean 2.9. Ever since I flashed that rom I have had the sleep of death. When I say that my phone has the sleep of death that is Everytime my phone goes to sleep. I have tried many things...I have tried using odin and flashing back to the original and them putting 2.9 and even going to 2.9.1. I have also went as far as not even installing titanium period. I eventually gave up and tried installing DarkRevenge v3 and am having the same results. I guess my only option is to go back to stock non-froyo. I have read that it is a froyo issue, but can't understand why I never had a problem with the original froyo leak. I honestly believe that I had the same kernel every time. I believe that I first had the froyo leak with DL09 then upgraded to the EB01. Let me add that each upgrade I never used voodoo, nor have I ever used voodoo...to my knowledge. I also went into wifi settings and changed the sleep policy to the plugged in option in hopes of saving battery life and thought it might be what was causing the issue, but it is not after switching back and having the same results.
If anybody has any ideas it would greatly be appreciated. I have tried wiping everything and flashing all roms according to instructions to a "T". If my SOD problem with just once or twice a day it would be tolerable, but every time has got to be a pain, especially since I have to take the phone out of the case and do a battery pull. Of course my battery life sucks, but that is acceptable. I am hoping that someone can help me with this issue before I go back to stock. I really like SC 2.9 and DarkRevenge v3 these roms are sooooo awesome. There again I am scared when I go back to stock I will still get the SOD...I hope not.
Thanks,
Leroy \oo/
Having the EXACT same issue ... any success?
I had to go back to a non froyo rom. I went with dl05 super dark with voodoo5 kernel. It runs great with no sod and awsome battery life with no froyo though. I might do some experimenting this weekend and I will let you know if I find any solutions.
Sent from my SCH-I500 using Tapatalk
Whats up guys? First post here for a new guy. My Thunderbolt is rooted and I have been trying to find a good kernel that helped my battery life. Started with Das Bamf 1.6.3 remix but the Kernel that came with it was awful on battery life. Without using the phone at all the battery would die after 6 hours. I originally flashed this rom through Rom Manager. I then moved to Liquid Thundersense 1.5 and then flashed a kernel that was ok but not great. Did this through Rom Manager as well. Then I read thatit was best to flash through recovery in Clockwork mod. I did this and went back to Das Bamf. Same problems with the kernel that came with it. I then decided to try Imoseyons lean kernel. First tried the battery saver mode using the terminal emulator in the das bamf toolkit. That did not work at all. Then I tried option #1 for the normal mode. This kernel is INCREDIBLE! The battery barely moves at all and this seems to be the one I want to stay with. One problem.....every once in a while I turn the phone and and see that I used 10-15% of the battery while doing nothing. Every time this happens I see that my 3G icon at the top of my screen is showing data going in and out at all times and won't turn off. The only way to fix this problem is to reboot. Then the kernel is back to being amazing. Has anyone experienced these problems before? If so, is there a fix. With the way that I use the phone I should easily be able to go a full day and still have lots of battery left if I don't run into this problem. I would much rather not go with the fat extended battery. If this has been covered elsewhere I apologize. I tried reading through a bunch of threads but had no luck.
Nobody has anything???? I also noticed today that I had a random reboot. I was leaving a voicemail for my brother and I looked down to see that it was rebooting. The kernel is not extreme in the overclocking or the undervolting. I guess if no one has any ideas I will have to try some other kernels. Its a shame cause the battery life was incredible with this one.
I believe its a great kernel. Reboots could be caused by anything... Almost everyone is getting random Reboots with the tbolts. Your data issue is probably Rom related, I would personally reinstall after manually wipe on everything.
The vary life on this phone is not good, but my personal experience is that its my screen sucking down my batt! It's to much fun to play with.
Sent from my ADR6400L using XDA Premium App
The network could be the culprit, too. I have problems more often than I'd like in metro Atlanta. I've woken up twice since I've had the TB with the battery completely drained after 7 hours, so my alarm clock doesn't go off obviously. I've already dropped to 1X for a couple minutes this morning, so I'm sure the battery loves that.
That's probably Rom related as well. Something is sucking data when it shouldn't be.
My phone only uses around 1-2 % all night. But will drain quickly when I do some morning browsing.
Check your sync. It might be set wrong or you could have one of 1000 or issues.
Sent from my ADR6400L using XDA Premium App
Could be, but both times it happened actually before I rooted, which is interesting. I've only had this happen twice in over 2 months, so who knows.
At least I'm not getting random reboots.
ercDROID said:
Whats up guys? First post here for a new guy. My Thunderbolt is rooted and I have been trying to find a good kernel that helped my battery life. Started with Das Bamf 1.6.3 remix but the Kernel that came with it was awful on battery life. Without using the phone at all the battery would die after 6 hours. I originally flashed this rom through Rom Manager. I then moved to Liquid Thundersense 1.5 and then flashed a kernel that was ok but not great. Did this through Rom Manager as well. Then I read thatit was best to flash through recovery in Clockwork mod. I did this and went back to Das Bamf. Same problems with the kernel that came with it. I then decided to try Imoseyons lean kernel. First tried the battery saver mode using the terminal emulator in the das bamf toolkit. That did not work at all. Then I tried option #1 for the normal mode. This kernel is INCREDIBLE! The battery barely moves at all and this seems to be the one I want to stay with. One problem.....every once in a while I turn the phone and and see that I used 10-15% of the battery while doing nothing. Every time this happens I see that my 3G icon at the top of my screen is showing data going in and out at all times and won't turn off. The only way to fix this problem is to reboot. Then the kernel is back to being amazing. Has anyone experienced these problems before? If so, is there a fix. With the way that I use the phone I should easily be able to go a full day and still have lots of battery left if I don't run into this problem. I would much rather not go with the fat extended battery. If this has been covered elsewhere I apologize. I tried reading through a bunch of threads but had no luck.
Click to expand...
Click to collapse
If your worried about data using your battery when your not using the phone you should check out Juice Defender. Just set it up to turn off all data when your screen is off.
Heres your fix..
Ditch DBAMF 1.6.3 and go back to 1.6.1 with the lean kernel.. I get amazing battery life with 161 and 2.5.1 kernel.
I'll give that a try. I also didn't seem to have problems with Liquid Thundersense 1.5 so that may be another option.
Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)
I'm trying to test my battery life so I downloaded a 2.17 RUU.exe (Freeza's all in one crashes mid-install for me, it always has...maybe related to eng hboot? probably not but idk) so I could run a stock ROM for the tests (I had intermittent reboots on the ROM I was running previously). I got the ROM all set up, installed my apps, flashed and updated superuser, installed busybox, and updated superuser binary, then I installed a team d3rp skin and leedroid tweaks. I wiped cache, dalvik and rebooted after the leedroid tweaks and when my phone booted up, I saw that wifi just said "error" on it. I didn't think anything of it since all I'm doing is using this ROM to try to drain my battery and I'm going back to another ROM soon and I figured it was something wrong with the kernel (I did not flash a kernel btw), but then I tried to turn on 4g as well (just to drain battery faster) and the 4G wouldn't turn on either; I got the message "4G was unable to start"
Anyone else have this issue? The only thing I can think of is maybe it could be leedroid tweaks was the odexed version, which I had read was what stock ROMs normally "use" (that's probably not the correct terminology, sorry if it isn't.)
Why would you do all of that just to drain your batter?
You could of searched "Battery Drainer" on the play store.
But to answer your question.
It is probably leedroid tweaks. I had this problem once and had to do a full wipe and flash a new Rom,
iTzLOLtrain said:
Why would you do all of that just to drain your batter?
You could of searched "Battery Drainer" on the play store.
But to answer your question.
It is probably leedroid tweaks. I had this problem once and had to do a full wipe and flash a new Rom,
Click to expand...
Click to collapse
Well I have a Seidio 4000 mAh battery and I want to have the ROM somewhat customized since I'll be on it a couple days minimum since I want to record battery history from multiple charges using battery monitor widget. I'll try a reinstall, thanks.
Also, I didn't think to check the store for battery draining apps, I guess I didn't expect there to be apps specifically designed for draining batteries only...
Thank you for the info
I know if a kernel wasn't flashed right can cause borked 4G and WiFi. If your hboot 1.5 . What was the last thing you did new when it happened?
Sent from my PG86100 using xda premium
w0rdOo said:
Well I have a Seidio 4000 mAh battery and I want to have the ROM somewhat customized since I'll be on it a couple days minimum since I want to record battery history from multiple charges using battery monitor widget. I'll try a reinstall, thanks.
Also, I didn't think to check the store for battery draining apps, I guess I didn't expect there to be apps specifically designed for draining batteries only...
Click to expand...
Click to collapse
heres one i used before.
https://play.google.com/store/apps/details?id=com.batterydrainer&hl=en
Drained my 99 percent battery in one hour. (without the vibrate option in the app)
reaper24 said:
I know if a kernel wasn't flashed right can cause borked 4G and WiFi. If your hboot 1.5 . What was the last thing you did new when it happened?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
The last thing I did before it broke was install the skin apk, then I rebooted to recovery, wiped cache+dalvik, then flashed leedroid tweaks odexed
I didn't think a bad kernel flash would bork 4g too. I've never had s-on though. Also, after wifi/4g broke but before trying to do a fresh install, I decided to flash one of chad's stable anthrax kernels, no luck with 4g/wifi, and I tried ziggy's kernel that virus posted in his thread a few days ago, no luck with that either. I'm going to do a fresh install and I'm actually going to add one mod in at a time this time, so I know what breaks it (assuming something actually goes wrong this time around).
How do I check if a ROM is odexed/deodexed if it's already on my phone? I can't exactly pull apart the windows RUU.exe to check, so is there any way of checking thru adb or root explorer, maybe something else similar?
iTzLOLtrain said:
heres one i used before.
https://play.google.com/store/apps/details?id=com.batterydrainer&hl=en
Drained my 99 percent battery in one hour. (without the vibrate option in the app)
Click to expand...
Click to collapse
thanks for the link I'll download that. The guys over in the 3rd party battery database thread would probably like to see this too
Hmm, I still haven't done a fresh install yet but I just installed system tuner...Apparently, neither of the kernels I tried actually flashed, but I have flashed the same exact zips successfully on other ROMs. I'm thinking it may have been the RUU itself that I downloaded, I'm just going to try a 2.08 RUU, take the OTA, then root, recovery, etc as that's the only way I've successfully used an executable RUU in the past without any issues.
Please, nobody else post in this thread, just let it die. Thanks to those who posted to help me out though
I flash a lot. I also have noticed my CM10.1 running like total crap lately. I also went back to Sense about a week ago but came back to CM.
I have done this once before and had great success, and just did it again today and my phone is running super smooth.
1) Back up anything you care about (pics, music, docs, titanium backups, etc)
2) boot into recovery
3) FORMAT EVERYTHING.
4) Copy ROM to storage (might have to mount it)
5) Flash
I did not restore everything from TiBU, but installed most of my apps from the Play Store. I decided to install things as I needed them because I realized I don't use probably half of the apps I have backed up. I did about 20 apps from TiBU (no data).
Copy stuff back to your phone that you want to have on it...for me it was just pics and a few eBooks.
I know a factory reset and a flash would normally do the trick, but I think perhaps something got screwy when I went to the Sense ROM. Since did these steps this morning, my phone has not rebooted, crashed system ui, screen always wakes up, no proximity issues, and battery life is pretty good (stock CM kernel from Fly)
Edit: statement that proximity sensor issue did not occur has been revoked.
3)FORMAT EVERYTHING
mind to explain this step
Sent from my GT-I9100G using xda app-developers app
nainaabd said:
3)FORMAT EVERYTHING
mind to explain this step
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
I don't just wipe data and factory reset. I format the storage media and the system partition. If you have TwRP go to Wipe, advanced, check everything and wipe. Basically your phone is a clean slate.
I used to use AmonRa and I know you can do the same, but can't recall the actual steps.
Sent from my ADR6425LVW using Tapatalk 2
I've been having FC and reboot problems for almost 3 months, and I can not figure out whats going on. I thought this was going to be the solution, but I followed the steps you listed (even flashed a stock RUU and wiped again for good measure), and I'm still having problems. I have alot of problems when trying to wake the device. Any other ideas? I'm really getting sick of flashing every other day!
jcdrummr said:
I've been having FC and reboot problems for almost 3 months, and I can not figure out whats going on. I thought this was going to be the solution, but I followed the steps you listed (even flashed a stock RUU and wiped again for good measure), and I'm still having problems. I have alot of problems when trying to wake the device. Any other ideas? I'm really getting sick of flashing every other day!
Click to expand...
Click to collapse
First, backup all your files, including your SD Card.
@D8nkE posted these in the Infection thread
Boot into Amon Ra
Format data, system, cache Ext4 | Ext3 > Format all to ext3
Then Upgrade all to ext4
Hopefully this helps
gleggie said:
First, backup all your files, including your SD Card.
@D8nkE posted these in the Infection thread
Boot into Amon Ra
Format data, system, cache Ext4 | Ext3 > Format all to ext3
Then Upgrade all to ext4
Hopefully this helps
Click to expand...
Click to collapse
I had wiped everything, but changing the formatting made me nervous. I'll give it a shot today. Thanks!
jcdrummr said:
I had wiped everything, but changing the formatting made me nervous. I'll give it a shot today. Thanks!
Click to expand...
Click to collapse
I have noticed a lot depends on what you are flashing and what you are doing with it. I use FlyHalf's CM build and kept getting myself into trouble with custom kernels. I have been running incredibly stable for about a week now on stock kernel with no tweaks. I do have Autokiller Memory Optimizer installed now however. Not sure if it's helping, but it definitely is not hurting.
Sent from my ADR6425LVW using Tapatalk 2
So I've been on Infection 2.7 since Sunday. Formatted as instructed, installed very little apps, all from the play store. Didn't restore anything (including my Nova backup, which I did almost every time before this), and I kept the stock kernel (Funky 3.4) without making ANY changes to the settings.
I have noticed that it is much more stable, as I have only gotten 1 or 2 FCs since flashing...I used to get 2-3 per hour. I am still getting the "hot reboot" on manual wake though. The scenario is this: "Notification!", I press the power button, the soft keys light up but the screen stays black, a few seconds later I get the infamous spinning matrix android. To me, because it happens almost exclusively on wake, it has to be related to the kernel/governor and have something to do with it pulling out of deep sleep.
I am following the Infection, SenseXP and Funky AOSP threads, and will try each of the new ROMS/Kernel/Recovery combos this weekend and post some results as soon as I get something definitive.
As always, post if you have anything else I can try, but for anyone wondering if its worth formatting....it certainly appears to have made my phone alot more stable, so give it a shot.
I have another user that is getting very similar symptoms -sans the FC's on a different rom I dev for. Best me and him could come up with is that it is a signal issue, causing a crash at low end. Try a minimum clock @ 432mhz.
Snuzzo said:
@jcdrummr
S on or s off?
Get with me via pm. We will figure this out.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
jcdrummr said:
S-Off
HBOOT 2.27
Click to expand...
Click to collapse
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=2205469
Try that out. Are you able to get any recovery to flash at all?
@Luke1213
You tried Hiro out lately? My buddys work has been flawless as of late!!! Half tempted to ditch the current CPU table in my base and revert back to the old one.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
jcdrummr said:
I was able to flash CWM and AR fine with fastboot. Just flashed the zip, and it sits on the HTC logo, then reboots.
Should I try HIRO, with Amon Ra, or is TWRP worth the hassle?
PM Sent, in case you want to pull this off thread.
Click to expand...
Click to collapse
This may be another issue altogether.
Snuzzo said:
I have another user that is getting very similar symptoms -sans the FC's on a different rom I dev for. Best me and him could come up with is that it is a signal issue, causing a crash at low end. Try a minimum clock @ 432mhz.
Click to expand...
Click to collapse
Is there a way to prevent deep sleep? I know this would destroy battery life, but it might help determine if its related to waking from deep sleep. In the mean time, I'll bump the min to 432.
Snuzzo said:
This may be another issue altogether.
Click to expand...
Click to collapse
Yeah, I'm on RA, HIRO, and Infection 2.8.1 right now, so we'll see how it goes.
You don't want to disable deep sleep. At max you will only get 2hrs of battery also could even trigger thermal throttling. Try a sense ROM with my kernel version 3.4 and report back that's if 432 doesn't work out.
Also try switching to Br0kens vanilla aokp.
Sent from my Nexus 7 using Tapatalk HD
Snuzzo said:
You don't want to disable deep sleep. At max you will only get 2hrs of battery also could even trigger thermal throttling. Try a sense ROM with my kernel version 3.4 and report back that's if 432 doesn't work out.
Also try switching to Br0kens vanilla aokp.
Click to expand...
Click to collapse
UPDATE
Increasing to 432 did not solve the problem, but then I thought that my screen brightness app Lux may have something to do with it. After disabling the app, I didnt have a single quick reboot in 2 or 3 days. Just re-installed it this morning and rebooted on my first wake. I did not have any reboots on the stock live wallpaper or a replacement wallpaper, but I was on a non-live wallpaper when I got the reboot from the app.
If I have any more issues, I'll try the Sense or Br0ken roms and report back.
OP: Sorry for the thread jack, and thanks again for the tip to wipe. That plus what I mentioned above has given me the most stable experience I've had since March!
Things were getting wonky with more than usual reboots, no matter what rom I loaded. So I backed up pics, formatted everything in recovery (all partitions and storage, flashed (Beanstalk) and treated the phone as if it were new. No app or data restores, etc.
Phone is running super solid without any issues, not a single blip.
It's like formatting a hard drive and reinstalling the OS and rebuilding from scratch.
Sent from my ADR6425LVW using Tapatalk 4 Beta