Related
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Do you leave bluetooth, gps, anything on? Trip turning your mobile days off añd let.the phone go through the däy then check your usage.
Android 17 said:
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Not really I'm getting between 20-30% usually .
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
With WiFi on
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
When did it start doing that?
Android 17 said:
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
For the most part I only get really high android system usage if I'm on my phone a lot. For the most part its less than 20%. But it can approach 50 if I'm using my phone a ton.
Sent from my ADR6300 using XDA App
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
drmacinyasha said:
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
Click to expand...
Click to collapse
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Android 17 said:
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Click to expand...
Click to collapse
1) It will not format or wipe the SD card.
2) Nandroid backup is always done as a precautionary measure. You do not restore from it afterwards, in this case.
Yea i've been reading a lot of people with that ota has been having that problem
Android 17 said:
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Click to expand...
Click to collapse
I just got my EVO last week so I have 3.70 and have not rooted yet. My phone has been off the charger for 7 hours and Android System is currently at 94% with Cell Standby, WiFi and Phone idle all at 2%. I had a Hero before the EVO and the Screen was what always seemed to use the most battery and its not even on the list for my EVO which I thought was very strange. I guess I need to look into the manual Root method since the others are not HBoot 2.10 and 3.7 compatible at this time.
I'm running stock 3.70 unrooted and right now Android System battery use is at 59%.
All of you with issues:
1) Download the FORMAT_ALL.zip from above.
2) Backup with Titanium Backup and Nandroid.
3) Flash FORMAT_ALL.zip
4) Flash your ROM
5) Via Titanium Backup, restore only user apps and their data, no system apps, system app data, or system settings! Do not restore from Nandroid.
I'm having the same issue. I'm stock UNROOTED 3.70. Is there a way to fix this for us non-rooted folks? I have been having significant battery drain and I did a factory reset and wiped everything except the SD card before the update. I do plan on roofing soon but I have the new 2.10 HBoot an hardware version 0003 and i want to make sure there is a well tested method and instructions before I attempt it. I'm no noob i've read this site daily since I got my Evo in June and I'm also an electrical engineering aka NERD but i just want to be certain before I root as this only phone I use and can't be longer than a day without it due to work. Any input here as well as on a fix for the high system use would be greatly appreciated! Thanks in advance!
This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....
Hi guys,
I've done a fair share of searching but it seems nobody is having the same issues
Basically, I thought i'd try out these new tweaks I found, the V6 Supercharger and the 3G Turbocharger from zeppelinrox - The V6 installed fine and was running smoothly but when i installed the faster version of the 3G turbocharger sent my phone into a bootloop (it eventually came back on to my relief). My HTC Wildfire is now thrown into a bootloop every time i enable mobile data. WIFI works fine.
I have reflashed my ROM, wiped data and dalvik cache, but when i flash the G_apps, the phone goes into the boot loop - and thats after a full wipe and reboot (i have now restored a backup - but the issue is still apparant)
Another thing worth mentioning is my local.prop file is empty and i'm not sure if this should contain any script.
Any help appreciated. Phone Spec below.
Thanks
Phone Model: HTC Wildfire Buzz
Android Version : 2.3.7
Rom: Cyangoen Mod-7.1.0.1-Buzz
Kernal: 2.6.35.14-nFinity [email protected] #1
Radio: 3.35.15.31
Baseband: 13.45.55.24U_3.35.15.31
Hboot: 6.01.1002
S-OFF
V6 Supercharger - Unsupercharged
3G Turbo Charger - Uncharged
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Fix for bootloop after 3g turbocharger script install
FIX:
Ran an RUU for wildfire.
- Downloaded (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24_ 3.35.15.19_release_141106_signed) from android forums.
- Connected phone to PC and ran RUU
- This downgraded phone OS to eclair (android 2.1)
- Let it do the bizniss
- Had to re-root with unrevoked 3
- Re-Flashed CM7 and gApps
All ok
I'll say one thing, CM7 doesnt need a v6 or a 3G super/turbocharger. It works fine without them. The minfree values are set at an ok level and I always have HSDPA signal. Its not worth the effort.
Yeah after carefully tweaking this and that - all one change after the other and testing a lot before going on - I've been pretty much satisfied with my old buzz. Until I decided to give that 3G Supercharger a try (because of 3G didn't ever work really good - the only thing I was not completely satisfied with)...
It turned out that there hasn't been any improvement from my perspective so I just reverted the settings and went on.
It took me 2 weeks to find out where the bootloops suddenly came from (1 day to narrow down the prob had to do with switching on data and at least 10 days for the 2g/3g part).
Is there anybody who can explain more specific a) what causes this behaviour and b) what would be necessary to eliminate the cause (and probably avoid it in the future)
I won't get misunderstood but just "do an RUU update" sounds a bit like the standard no.1 suggestion "format and re-install" in all those amateur winsucks forums...
3xeno said:
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Click to expand...
Click to collapse
Thanks for the hint but even after reading all the related posts several times I don't feel enlighted somehow (besides the information that I don't need any super charge scripts with CM - which I'm half the way to be convinced of )
noone? I just want to find out what exactly is the problem (to avoid it in the future) and I'm really curious why a complete wipe doesn't help. The Supercharger scripts just tweak values in config files (correct me if I'm wrong) - so if the problem is caused by the script(s): why can't it be solved by simply revert those changes (or replace the files by the default ones)?
Fix for bootloop after 3g turbocharger script install
eventcom
Did you find anything more about this problem?
I have the boot loop after using 3g/4g optimizer from the market, but I can get partial network use if I enable only 2g and not 3g. Better than nothing while I see if it can be fixed without a RUU.
Just wondering if a RADIO flash may solve the problem.
Regards.
Phone Model: HTC Wildfire Buzz
Android Version : 2.2.1
Rom: Stock
Kernel: [email protected] #1
Radio: 3.35.20.10
Baseband: 13.55.55.24U_3.35.20.10
Hboot: 6.01.1002
S-OFF
st3v3droid said:
Did you find anything more about this problem?
Click to expand...
Click to collapse
nope unfortunately not, but it seems, that the problem still occurs - see in this thread or here in that one - I've given it another try to flash radio again - with no help. The information about changed values in build.prop isn't new to me (as I did expect something like that) - what I don't know is which values exactly and how to overwrite them (if too many) when flashing a new rom...
So I went a bit deeper into the build.prop and made a simple diff against the build.prop of October 2011 (has been an earlier nightly and that problem definitely didn't occur at that time).
The only differences were those:
This looks like a simple addition for identification
Code:
+++ ro.cm.device=buzz
Perhaps that's a better guess (looks like this had been added sort of randomly anyway? - qualifies):
Code:
+++ # For PDP overlap problem
+++ ro.ril.avoid.pdp.overlap=1
That shouldn't harm anything:
Code:
+++ # update the acoustic table for Buzz NEL lab testing
+++ ro.ril.update.acoustic.table=1
My own changes which didn't cause any trouble before:
Code:
--- dalvik.vm.heapsize=24m
+++ dalvik.vm.heapsize=32m
+++ ro.compcache.default=0
That shouldn't have to do with the problem, too:
Code:
+++ persist.sys.rotationanimation=false
+++ persist.sys.scrollingcache=2
but that one probably?:
Code:
+++ # Lock dirty_ratio to 20 when USB is mounted for improved transfer speed
+++ ro.vold.umsdirtyratio=20
So I simply commented out the stuff I guessed to be responsible (no. 2 and 6) and restarted - no success. Reboots again when turning on 3G
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Doddster said:
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Click to expand...
Click to collapse
that sounds exactly like LucidSomnia's report in the thread I've used to continue with my experiences. I can't tell if my solution (if it was any and not by accident) will help you but it shouldn't hurt to give it a try...
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
P.S The camera works occasionally, I get viewfinder but no way of taking picture and if I install the 3rd party app Line camera I can take pictures with no viewfinder.
Doddster said:
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
Click to expand...
Click to collapse
As you can see in my posts (in three threads) I've done a lot of stuff, too, what did the trick in the end (if it was not just by accident) was
Total/full/mega wipe (except SD card)
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (older one in my case)
Boot
after that just the same procedure
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (newest in my case)
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
If that's the case with you I'd give my method a try and if that doesn't work I'd do an RUU (the safe flash variant first of course).
eventcom said:
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
Click to expand...
Click to collapse
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Steps followed:
(In recovery)
Wipe Cache,
Factory Reset.
Flashed CM7
Flashed Radio (3.35.19.25) using CMrecovery 2.5.0.7
Thanks eventcom
**Dunno if I'm gonna have the balls to install CM9 again after all this
Doddster said:
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Click to expand...
Click to collapse
glad to hear that it helped
**Dunno if I'm gonna have the balls to install CM9 again after all this
Click to expand...
Click to collapse
I'm not really sure about what exactly caused the problem (at my side at least) - but even if CM9 on the Wildfire is highly experimental this particular problem doesn't look to me that it has to do with the ROM. I slightly remember a few people having this problem after flashing a different ROM but in most cases this could be solved by a simple restore. Did you also use some tweaks - like a different kernel, RAM scripts or something similar?
nope, nothing different from what was included on the CM7 and CM9 builds. :/
It's frustrating as ICS actually runs ok on the wildfire, it's only till it hits the radio or camera hurdles it lets itself down lol
I'm getting another phone soon so I will be using my Wildfire for development and I'll put all my effort into helping us wildfire'ers run ICS with no hassle.
Im gonna stick my neck out here, all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Could be coincidence or could be the reason!
Forum fishing.... Who's biting!
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Doddster said:
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Click to expand...
Click to collapse
Have you ever had the problem with the radio outside of cm9?
Ive never tried cm9 nor had issue with any of my radios but have had bootloops when i tried the v6 scripts back in my early days.
Forum fishing.... Who's biting!
slymobi said:
all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Click to expand...
Click to collapse
Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
]Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
Click to expand...
Click to collapse
I try to follow all threads here in wildfire as well as a handful outside and like i said the main 3 factors mentioned above are nearly always present or come to be eventually
I dont think it will ever be pinpointed or whittled down to just one reason due to there being so many possible causes/possible triggers. I can however say from my own experiences that ive not had a single bootlooping issue since the day i removed and never again used any v6/juuwes enhancing scripts. I keep my processor at 633 max,264 min ondemand/smartass, my readahead sd speed never over 1024(516 is my preference, to limit sd errors) set on any rom i use.
I always unzip the rom and study within to edit, mod, remove certain elements i desire/dont need or want prior to flashing it.
This way i have the setup i want and need for my own personal liking.
Regards slym.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
So today my beloved Galaxy Nexus completely self-destructed.
I've been trying out Franco's M2 kernel with AOKP M4, a good combo supposedly. I was in a coffee bar, logging onto a wifi network, when it suddenly froze and required a battery pull. Not that big a deal. Then it got locked into an endless boot.
I'm able to get into bootloader/recovery. So, I tried a few things.
1. Tried to restore from an older nandroid. It loads up into Android, but then immediate locks up before I can really do anything. Not the result I'm looking for.
I had heard of this happening before... for instance, somehow a kernel really messes up a phone, requiring a total wipe and restore. Sucks, but not the end of the world.
I did a nandroid of my existing data. Perhaps not such a good sign, the phone REBOOTED ITSELF during a couple of the backup attempts.
2. I did a total wipe and flashed the ROM I've been using, with no restoration of any data. Same problem! It loads up to the very beginning of the configuration screens, then freezes.
3. I had heard that doing a complete total wipe, including sdcard, sometimes was necessary! So, after using adb to transfer out the necessary files, I locked and unlocked my bootloader, which essentially wipes out everything.
4. I tried fastboot installing the system image for 4.0.2 (minus the bootloader and radio). It installed the recovery, but aborted for the actual data. Error is "too many links"
5. So now, I have essentially no actual ROM on the Nexus. As a last attempt, I adb push some ROM zips onto the sdcard. This is hit or miss, as sometimes the file ends up there, and sometimes even though adb reports it as successful, it's nowhere to be found.
I reinstall the ROM zip and now it freezes at the boot animation.
I'm beginning to think there's a major hardware breakdown somewhere.
The screen sometimes does a horizontal 'shake' (the image quickly flickers to the right or left). Usually on the boot animation. That's not a good sign either.
I consider myself well-versed in how these things work, so, I'm looking for any other suggestions before I throw this thing in for a warranty repair.
Idk... that "horizontal shake" of the boot animation that you described sounds like it is toast (hardware problem). Perhaps try restoring using Googles stock Images (including radio and boot loader) and use the flash-all.sh script instead of individually (fast boot flash blah blah blah). Other than that idk...
Thanks for the thoughts.
I left the battery out overnight, and amazingly, it actually booted first thing this AM! Great, I thought!
Um, no. It allowed me to do some MTP file transfers, so I put a nandroid backup onto the /sdcard. As soon as I tried doing anything required, like logging into the market, it crashed within seconds.
Same problem when I restored a good nandroid backup, crashing 5 seconds after loading Android. And the same flickering screens (in recovery too!) accompanied by reboots.
Negri RMA is going in today. They're quite prominent on this forum, with aiding in warranty repairs, so I will report back. I expect their word to be good.
The phone was always babied, never overclocked or overvolted, so a bit sad.
Are you overclocking the CPU? Maybe a heat issue?
No overclocking at all. Battery life is my main priority, so I never pushed the envelope for speed =)
Also, I would expect (though I don't know for certain) that all those settings would be remedied with ROM clearing and reflashing.
if the screen flickers and freezes in the bootloader, you have a bad motherboard. good to see you're already RMA'n it.
Turns out it's a bad processor apparently. Either way no software is going to fix that!
Having major problems with my Note 4. It is often really sluggish. Has horrible lag. Sometimes it just randomly resets. And, when it resets, sometimes it goes straight to download mode and says could not do normal boot at the top. For example, right now it has been on the Samsung galaxy note 4 boot screen for a few minutes. I had to pull the battery for it to boot. Sometimes, when I press and hold the power button, it doesn't respond.
I have tried a number of fixes.
-Factory reset.
-Full wipe
-Format data, then full wipe
-Odin back to stock firmware (KK, LP and MM)
-Restore backup from TWRP
I searched and saw another thread with similar symptoms, but it was pretty old with only one response. I am really at a loss as to what to do. I can only assume it is hardware related. I haven't really dropped it. No water damage. Always in a case.
Any help would be appreciated
I had the exact same issues you are describing. It ended up being the only reason i upgraded to note 7. Now of course note 7 is being recalled & i wish i could go back to a fully functional note 4.
Hope somebody has a solution for this!
The OP describes a bad flash or OTA update, corrupt partition or failing eMMC. I'd advise replacing battery as a first step of troubleshooting. Make sure it's charged fully at least once and have 75% or more capacity before starting.
I've never had to do anything risky with "PIT with repartition" or "nand erase all" but there are other advanced forums for that but I don't venture into recommending risky measures I haven't performed with experienced guidance. You could find these by googling or visiting Sammobile specific forums- I don't think it's acceptable to post external links.
But before I considered risking those methods there's some steps I'd eliminate first (warning: they may seem redundant but if having issues, I'd be thorough even if it appears redundant):
1. Backup and boot system, enable developer mode and enable USB debugging.
2. Disable reactivation lock in Settings/Security.
3. Open SuperSU app and fully un-root.
4. Wipe everything but extSdCard, factory reset and format data and power down and pull battery. Get serial number from underneath battery for Smart Switch.
5. Install Smart Switch on PC.
6. IMO, you should Odin stock tar before using Smart Switch if previously rooted.
7. Use Smart Switch to either install latest update or emergency restore phone. I didn't know Smart Switch worked in Note 4 so refer to Sammobile.
8. Once done, Check stock for stability for days before opting to do anything unless you've duplicated same results. If you have a true hardware issue, it may be evident while trying these steps.
9. Determine if you need to do anything further. I can't help with the riskier stuff; I've been fortunate enough not to experience anything warranting a risky procedure.
Sent from my SM-N910P using Tapatalk
i am now having this same issue on my note 4. i have gone through all of the steps outlined in this thread. The only thing i haven't tried yet is a full repartition. Any thoughts? OP have you had any success?
Thanks,
JD
I succeeded in a full brick lol. That's about it. Wont even charge/power on.
last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD
JudasD said:
last night i re-odined with a pit file. I had selected re-partition, nand erase and hone EFS clear. I did get a successful odin and the phone had to reactivate with sprint. IN the end i still have the very laggy performance, phone sometimes not responding and spontaneous reboots.
All of this started in an instant. Everything was running fine on a TW rom that i had been running for about a week. I went to use the camera, the app froze and the speaker made a slight static kind of sound and then all of this started. No matter what kind of rom i put on here they now all act the same. very strange.
JD
Click to expand...
Click to collapse
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk
samep said:
Doesn't sound like you're having all the issues posted by the OP if stock was fine for a week and you can Odin successfully and have no issue until installing a custom ROM.
You replaced your battery and stopped using older ones? That camera issue was either a bad battery or incompatible camera in a custom ROM, IMO.
The stock ROM that worked fine for a week and the custom ROM that spontaneously reboots, which were they? Most likely, you're limited to what mods you can apply. In that condition, were you using stock or custom kernel? Kernel tweaker or none? Am I wrong to conclude your issue is the custom ROM and possibly custom setups?
Could you describe the random reboots? I've personally experienced a scenario where a ROM may run fine until user factory resets and ItsOn tries to install its bootstrapper but cannot with custom kernel or missing resources. It's persistent though, got a prompt to reboot with no issue or reason given when all seems well except the prompt to reboot that may actually become unexpected reboot if notification it's disabled and ignored. Some have found its best to factory reset and wipe internal memory when this happens and then install custom ROM cleanly. @freeza even added a line in script to delete /carrier/ItsOn folder and contents when that was identified as the issue when not wiping internal memory when completing ItsOn bootstrapper prior to installing custom ROM. I believe that works in that scenario but it highlights a need for user to follow OP install to prevent that in ROMs that omit that line in scripts. This could be a disconnect where phone isn't tested but deemed compatible with Sprint and data patch.
But kernel tweaks can cause issues with random reboots. The kernel I use works well with interactive governor but the rest are not as stable or fluid. I can under volt but only 25 or 30 mV and I limit over clocking to 2 steps above stock, no further (goal is stability without hurting battery with reasonable gains). You should consider that each processor has already been profiled to run within a specific volt to frequency table based on its ability so there's little room to limit with no adverse effects. Major steps can have adverse effects. Over clocking should also be given the same respect. We're already maximizing performance near threshold of stability. Think small steps, rather than large. Using the developer recommended kernel tweaking app is paramount for success as well.
Swapping kernels repeatedly may also leave your phone in an incompatible state so that even restoring boot.img partition to stock isn't helping. The reason is the modules the kernel uses. Developers will modify the contents of /system/lib/modules. Hopefully that's done in a compatible way but each custom flash over pre-existing custom setup may not be ideal but works best flashed over stock modules. If developer has done thorough testing, maybe the adverse effects have minimized but you can see where not having the phone for testing may impact users. Restoring boot.img only leaves the modules in unintended modification, especially for stock boot.img
Just a few examples of why a custom ROM may not be as compatible as stock for some users or carrier subscribers. You should mention the ones not being so compatible when comparing to stock as well as knowing that custom kernel tweaks and applications may not work as well on all ROMs.
There is a possibility you've chosen an incompatible ROM; ported ROMs may be nearly fully functional but have issues like you described. There's many workarounds posted in this forum that admittedly aren't fully functional; much effort has been shared by a few that have given much effort to find most compatible ROM but I think we'll get more stable support out of the box for Sprint version on Sprint from @tx_dbs_tx soon enough if your phone holds up- the OP describes an all too common failure with eMMC failure on Note 4. Sprint compatibility is tougher due its network and porting ROMs is tedious and may not work fully on phones not on hand for test.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD
JudasD said:
I apologize i was not 100% clear in my previous post. I was running a custom rom when the camera issue happened. Since then any rom i install is very laggy and has spontaneous reboots. This includes stock odin roms with no mods at all. I have also tried multiple batteries.
JD
Click to expand...
Click to collapse
OK, my mistake too. Maybe you said that before and I didn't follow the flow of your comments.
You did the nand erase all but do you typically wipe internal memory and factory reset prior to flashing ROM or stock tar? I also prefer to power down and pull battery before going to download mode and flashing stock tar.
If you've done everything and get random reboots on stock or failed to normal boot or eMMC failure, that may be your eMMC failing or other internal failure. I would expect it only gets worse over time- time to repair our replace. I just did my local research with uBreakItIfixIt and the guy says I'd have to bring in my own part but labor is only $10 plus tax to replace main motherboard. Part lists on web for $80 or more. Amazon has a listing for it too.
https://www.amazon.com/gp/aw/d/B01M..._SY340_FMwebp_QL65&keywords=Motherboard+N910P
Sub $100 repair estimate isn't so unreasonable compared to increasing cost of upgrading to locked phone with no root possibilities. But HTC is an option if their offering is appealing. I'm thinking maybe 2017 HTC has an appealing upgrade that I may find worthy for the money. Sure wish an OEM would duplicate the Note 4 on a refresh with updated internal components.
If my phone were to break today, I'd give that a go. I trust business names like Amazon and uBreakItIfixIt. Ubreakitifixit usually has parts on hand for simple or common repairs like screens, internal batteries and USB ports. That outfit just did an economical repair in an iPhone 6 for my wife. Replaced screen and battery for just over $160.
Sent from my SM-N930P using Tapatalk