Related
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
I admit there are some issues with the battery and heat and bugs, but i have not experienced any freezing with the stock browser or any program really, alarm clock extreme and it works for me, I don't use the Facebook app often but the few times i have, no real issues sometimes it lags trying to update. I will say thay the market SUCKS or play whatever they call it. Maybe you got a corrupt OTA file or something is wrong with your update installation. Maybe try doing a factory reset, i know that sucks to do but i do it before every OTA and im not really experiencing any of the software issues you are experiencing. If that doesn't help, root it and use the razr 1.7 utility to reinstall the system files.
Did you try to wipe the device (factory default)? It helped in my case.
Sent from my XT910
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
abw1987 said:
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
Click to expand...
Click to collapse
Data wipe, itll fix it. If you dont want to.do.that then root and wipe the cache and dalvik cache.
Sent from my DROID RAZR using Tapatalk 2
AndroidGreg said:
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
Click to expand...
Click to collapse
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
syrnett said:
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
+1
ICS is very different from GB, and Motonverizola tried really hard to get ICS to play well with existing GB cache data and GB settings. All of that stuff changed a LOT.
The problem isn't ICS: the problem is data conversion from GB to ICS.
Wipe the cache and dalvik. If that doesn't get it, then do a factory reset and set everything up again.
Mine runs for days with light use (1-3 hours a day), or a day+ with heavy use. It doesn't get hot, unless you mean that the other way. But that'd be kinda creepy.
Hi
This is my first post here at this forum and I'm not a Razr user but thinking about getting the Maxx because of it's hardware and big battery which fits my usage of a smartphone, I have a Galaxy S right now.
I have looked at some of the posts and screenshots of the battery usage on the new leaked/released ICS for the Razr and read about complains about the short lived battery and the devices that overheat, well, we had the same problem when GB has been released to the Galaxy S and that is all related to the Android OS app that is using the battery because it's got into a loop, this will not get fixed unless you make Motorola aware of the problem. I could be wrong but I think that is related to the dalvik-machine. Android OS should be using around a single-digit of the battery of all time (3%-7%), we don't have this issue anymore since Samsung fixed this bug in the later releases of GB firmwares.
A temporary fix of the Android OS is to reboot the phone when you can see that it's hijacking the battery, this is until Motorola fixes the issue.
I wish you all good luck and hope that you will get a better firmware soon.
Its always good practice to start fresh when accepting an update that big. Less variables = less problems.....
Id do a factory reset and start from scratch... that sux... i know, but so does a useless phone
Ics def wasnt all the hype.... but its also not that bad... just gotta start clean.
Good luck!
Complete disaster? How is it a disaster compared to my update? After the update I could no longer receive text messages, Consider the fact that I send a receive hundreds of text messages per day this is honestly the biggest cause of outrage I have with a flagship that can't perform even what a Nokia 6280 could, when I finally receive texts they come in 4 hours late and worse still, in DUPLICATES and I can't seem to find any solution to this as of yet. A factory reset fixes this for an hour at best but the problem suffices after that. Does anyone have a SOLUTION to this? Honestly driving me nuts
I agree with most others... do a factory reset. I always do after a major upgrade (and ICS is a major upgrade!)
Then check what apps you are putting on the machine; some cause issues. For instance, I put the new Starbucks 2.0 app upgrade on my phone yesterday - consumed battery like mad, phone ran hot (like cook-an-egg-on-it hot), runaway processes, etc. Turns out it was the new Starbucks app; after removing it the phone ran normal.
Otherwise I love ICS! So try the cache wipe; and if that doesn't help then do a factory reset and reinstall things. Takes time, but it saves in the long run.
Wow, this is crazy to hear. My update has been flawless but I did a factory reset after getting it. I bet if you did that it would fix 99% of your problems.
I also rooted after and now I'm running a cm9 rom. This is the best my phone has ever run.
Ultimately, even if you don't root you can fix most of these problems with a factory reset.
Sent from my Droid Razr using xda premium
Hold down the Home button to see what's running, download a task manager to see what's dominating the CPU. The phone won't get hot by itself, something is using up the CPU (like you said) if you don't want to factory reset you've got to figure out what it is. Rooting and setting the CPU governor to hotplug will save quite a bit in battery (shuts the 2nd core off when not needed).
I'm on a Canadian leak, the first day battery performance was terrible. By the 4th day, the battery lasted longer than GB
I concur with everyone here about the factory reset.
As other's have mentioned, going from GB to ICS is a major overhaul. I've read elsewhere what this really entails and it's not pretty. Suffice it to say, I backed up all my user apps and data (using Titanium Backup), saved off all other things that were on my internal SD card just to be safe and then applied the OTA update in stock recovery, wiped data and cache and rebooted. I then rooted, installed Safestrap and flashed Eclipse ICS v1.2 RC1 and restored my apps with TiBu.
I also tried stock ROM as well and restored my apps via TiBu.
In both cases, no performance issues nor forced closes. Runs like a champ.
I'm running the latest .214 leak and my battery life has improved over .211.
.214
Razr Maxx
I was having shorter battery life with the ICS .211 build and then updated to .214
My battery life is way better then it ever was with GB or ICS .211
I ran it the other day for 36hrs and 3 of it actually talking on the phone and had 20% battery life left.
It has currently been on for 4hrs 6 min and is at 90%. light email and phone use. I do have an IMAP email account that poles every 10 minutes with push for instant updates.
Mine is running fine after simple reboot
I am getting great battery life and my Razr Maxx is working almost flawlessly after the ICS OTA stock update. I just rebooted it shortly after the update when it was running hot and haven't had any problems since.
If .214 is even better, great.
Looking forward to Jelly Bean to get even more from my device.
Jeff
Was on the soak test and had the same battery problems. Only way to fix was via a factory reset. This did however fix all the problems.
Cant use motocast, it wont connect to my motocast on my mac. So i cant sync my media. How to solve this?
Sent from my XT910 using Tapatalk 2
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
abw1987 said:
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
Click to expand...
Click to collapse
Its under the advanced menu.
Sent from my DROID RAZR using Tapatalk 2
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
pneuma00 said:
Hello all.
As the title says, I've been having random reboot sessions on my phone lately. When these reboot sessions occur, the battery gets hot.
I'd like to give some more information about my situation:
I've been using CM7.2 on my Huawei u8160 for almost half a year now, without any kind of problems. Lately, the phone started rebooting randomly, especially during phone calls, making the phone almost useless. The reboots also occur when the phone is idle. These reboots drain the battery extremely fast.
I've been using CM7 with the V6 supercharger, as I said, for months without problem. When these reboots started happening, I reflashed the rom, doing a full wipe (clear cache, clear dalvik, format system, format data, factory reset etc.) , but that didn't solve the problem. I reflashed CM7 several times, with / without V6 supercharger, without deleting those system apps that are safe to remove (live wallpapers, update notify etc.). I also reflashed the stock froyo rom the device came with. None of these methods worked.
It is getting more and more frustrating, since they occur randomly, and I can't make a proper phone call, since it's almost guaranteed the phone will reboot during the conversation.
I tried formatting the SD card, using another SD card, resetting the battery stats, using a program on the market and the CMW Recovery - nothing helped.
Another thing I noticed (this may sound very stupid) is that the phone reboots more often when I'm outside (it's winter here now), or when I enter in a warmer place, or when the phone is in my pocket.
I asked an assistant from a nearby Vodafone store, she said that it is a software problem ( -.- ) and that the phone needs to be sent for service. I told her I've already reflashed the software, and she said I only did an update not a full soft flash (lol).
I would really appreciate if anyone could give some suggestions, or help me in any way.
I have also created an error report using the device specific setting menu included in the CM7 rom, which I am attaching here.
Help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Jimmy_Christ said:
Yeah, going to the store after flashing a custom ROM is rarely going to yield favorable results. Honestly, I'd try clearing app data and fixing permissions. What recovery are you using? When in doubt, wipe twice.
Click to expand...
Click to collapse
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
pneuma00 said:
Yeah, I know that rooting void varranty and everything but the naive me thought maybe they can say something clever...
I tried clearing everything, formatting system, data, cache, everything, fixing permissions etc.
I'm using ClockworkMod Recovery 5.0.x.
I am planning to buy a new battery because I observed it's getting really hot sometimes, and after the reboots occur, it's also really hot.
Click to expand...
Click to collapse
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
The more time you devote to this the more you'll realize that most of the folks at the stores dont know much. It wont hurt to buy a new battery. Wipe the battery stats. Do you use a custom kernel? Ovetclocked? Underclocked? Played with the voltage tables?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, you're right...
I did wipe the battery stats, let it drain completely and did a full recharge. For the kernel, I don't really know much about these stuff (yet). This is the ROM I use : http://forum.xda-developers.com/showthread.php?t=1259739. Im my phone info menu it says 2.6.32.9-perf [email protected] #23 (no idea what this means) so I don't know if it's a custom kernel or a stock one. For clock values I use min: 30MHz max: 600MHz (which is the stock value if I'm not wrong). I don't know what you mean by voltage tables, I'd appreciate if you could explain that.
Thanks so far.
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Jimmy_Christ said:
Well basically in a nutshell, voltage is the power sent to the CPU. Some custom kernels allow for what's called undervolting. Basically you're you're lowering the amount of power sent to the CPU, where in theory you'll achieve better battery life. However, this can be very dicey. I would not recommend playing with voltage tables until you're a bit more experienced. I asked because undervolting can lead to boot loops and seemingly random reboots. You're running a solid rom with cm7. If you didn't touch it, then that's the stock cm rom. Have you searched the forum thread?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yes, I haven't touched anything in the ROM I'm using currently.
I've been searching the forums for days before starting this thread, without success.
What I noticed about the reboots is that it occurs almost exclusively when making / receiving a phone call and when the phone is idle.
*edit: I forgot to mention that I'm using Segoe font, not sure if that makes a difference though. I have replaced almost every font in the /system/fonts folder (droid sans+bold+mono and even droid serif+bold+italic+bolditalic)*
Looking for advice here. I have no idea if this is hardware, software, something I'm doing wrong. I'd say the past year of having my note, it's painfully laggy. I've tried most of the more popular roms that are released. It's not always horribly slow.. but just about any time I switch to any new app, it becomes temporarily unresponsive. I've just come to terms with this thinking it is what it is.
I'm currently running the first cm 4.3 nightly, with the Uber kernel, running Jamie's settings. I've never been too into modding kernel stuff, so I don't know if I should look there first. but yeah.. any help would be appreciated. Just sick of the inconsistent speed
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Since you said this was with all roms you flashed, I'm going to guess something you're doing.
This is usually due to not properly formatting data and system areas before flashing, and also improperly restoring apps after flashing.
Install Black Star X or an ICS based ROM. If it's laggy, it's your phone. If it's not, it's because you've been trying jelly bean ROMs.
cgibsong002 said:
Looking for advice here. I have no idea if this is hardware, software, something I'm doing wrong. I'd say the past year of having my note, it's painfully laggy. I've tried most of the more popular roms that are released. It's not always horribly slow.. but just about any time I switch to any new app, it becomes temporarily unresponsive. I've just come to terms with this thinking it is what it is.
I'm currently running the first cm 4.3 nightly, with the Uber kernel, running Jamie's settings. I've never been too into modding kernel stuff, so I don't know if I should look there first. but yeah.. any help would be appreciated. Just sick of the inconsistent speed
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
What is your flashing procedure? do you do the proper wipes... wait a bit after install before touching or changing much, rebooting like 4 times at least to let it settle in?
What clock speed / governor are you running?
undervolted?
SD boosting cache write amount, if any?
sinasiadat said:
What is your flashing procedure? do you do the proper wipes... wait a bit after install before touching or changing much, rebooting like 4 times at least to let it settle in?
What clock speed / governor are you running?
undervolted?
SD boosting cache write amount, if any?
Click to expand...
Click to collapse
Ok.. I'll try to give my best answers.
Using TWRP, i'll go to wipe>system, then factory reset (data/cache).
Then flash the rom, then gapps if necessary.
Settle? Eh, I usually try to let it. I've also heard from the Devs there's no actual reason to do this, it's just to stop people from complaining the first 10 minutes of using the rom.
As for the other stuff... I've never really messed with it. After flashing the UBer kernel I tried to follow some settings I saw jamie recommend.. ondemand governer. That's really it.
Do I need to get more into tweaking frequency profiles, voltage, etc? different governors?
And btw.. yes, these are all JB roms. I refuse to use ICS.
cgibsong002 said:
Ok.. I'll try to give my best answers.
Using TWRP, i'll go to wipe>system, then factory reset (data/cache).
Then flash the rom, then gapps if necessary.
Settle? Eh, I usually try to let it. I've also heard from the Devs there's no actual reason to do this, it's just to stop people from complaining the first 10 minutes of using the rom.
As for the other stuff... I've never really messed with it. After flashing the UBer kernel I tried to follow some settings I saw jamie recommend.. ondemand governer. That's really it.
Do I need to get more into tweaking frequency profiles, voltage, etc? different governors?
And btw.. yes, these are all JB roms. I refuse to use ICS.
Click to expand...
Click to collapse
Storage saturation is far more important than any of the factors we've spoken about.
Just answer this one question. Have you ever moved an app to your SD Card?
Jamesyboy said:
Storage saturation is far more important than any of the factors we've spoken about.
Just answer this one question. Have you ever moved an app to your SD Card?
Click to expand...
Click to collapse
I went to apps>sd card in settings. It appears my user downloaded apps are all on my SD card. I'm guessing thats a problem. How would I change that? That's nothing I ever did, that's a default.
edit: nvm. I misinterpreted that screen. XDA app was the only one that was checked off for on sd card. They're all on my phone.
cgibsong002 said:
I went to apps>sd card in settings. It appears my user downloaded apps are all on my SD card. I'm guessing thats a problem. How would I change that? That's nothing I ever did, that's a default.
edit: nvm. I misinterpreted that screen. XDA app was the only one that was checked off for on sd card. They're all on my phone.
Click to expand...
Click to collapse
Sorry, I should have been more specific.
I meant moving your apps to your external SD Card when the internal storage (the 2gb /data partition) got full.
Moving as few as little as a single app to your external SD card can dramatically slow down android (for some reason). Nonetheless, a full partition elsewhere can still effect performance significantly.
Download "Storage Analyzer" from the Play Store, and see if any of your partitions are particularly full.
I try to keep 300mb or more free on all of them.
Additionally, you can wipe cache & dalvik.
Sent from my Transformer TF101 using XDA Premium HD app
cgibsong002 said:
And btw.. yes, these are all JB roms. I refuse to use ICS.
Click to expand...
Click to collapse
Then be content knowing you're trading speed and stability to satisfy your need to say you run jb
cgibsong002 said:
Ok.. I'll try to give my best answers.
Using TWRP, i'll go to wipe>system, then factory reset (data/cache).
Then flash the rom, then gapps if necessary.
Settle? Eh, I usually try to let it. I've also heard from the Devs there's no actual reason to do this, it's just to stop people from complaining the first 10 minutes of using the rom.
As for the other stuff... I've never really messed with it. After flashing the UBer kernel I tried to follow some settings I saw jamie recommend.. ondemand governer. That's really it.
Do I need to get more into tweaking frequency profiles, voltage, etc? different governors?
And btw.. yes, these are all JB roms. I refuse to use ICS.
Click to expand...
Click to collapse
1. if you have been around at all, then you would know many wipe as many as 3 times.
2. I don't know what dev's told you there is no reason.........there is and it not to stop people from complaining. that sounds pretty selfish to me and the folk who develop here are far from that. I am not sure of he actual terminology, but the data basically needs to work its way through the system. your phone needs to read all this new system it is supposed to run.
some developers will even flash rom, then flash rom again with gapps. let it boot and settle the 10. then boot it again. set it up and then boot yet again and wiping davlik and cache every flash.
3. many developers ill also suggest you give rom a day or so with stock kernel. if you make so many changes so fast how do you know what working or whats not?
but hey if that's all to much trouble for you, to have a phone run the way you are expecting it to....... congratulations. your phone is perfect.
I apologize if this sounds harsh, it just sounds like you expect your phone to run flawlessly, but you don't want to exhaust what minimal efforts are needed to get it that way.
good luck my friend
------------edit-------------
I just went back an double checked your post count. you are definitely not a newbie here. a lot of this should be common practice for you, even if you were coming from another device.
cgibsong002 said:
Ok.. I'll try to give my best answers.
Using TWRP, i'll go to wipe>system, then factory reset (data/cache).
Then flash the rom, then gapps if necessary.
Settle? Eh, I usually try to let it. I've also heard from the Devs there's no actual reason to do this, it's just to stop people from complaining the first 10 minutes of using the rom.
As for the other stuff... I've never really messed with it. After flashing the UBer kernel I tried to follow some settings I saw jamie recommend.. ondemand governer. That's really it.
Do I need to get more into tweaking frequency profiles, voltage, etc? different governors?
And btw.. yes, these are all JB roms. I refuse to use ICS.
Click to expand...
Click to collapse
Playing with JB roms you have to keep in mind that the radio you are on, and corresponding certs/ril/PRL .. etc, will most likely not be made for that rom and have your radio switching back n forth, left, right, n all around looking for a signal because it isnt configured right... that being said, your kernel is an integral part of the whole package and should also be flashed properly (wipe CACHE/DALVIK) at least once.. 3-4 times is proper. Go into settings, select remove method of -rm .. and repeat the wipes. Then flash kernel on top of an already settled rom ... or sometimes you flash the kernel before you even boot into the rom (my preference when possible). FIX PERMISSIONS . . always. Then sometimes do a Cache/Dalvik wipe AGaIN after the flash , especially if instructed. Same goes for flashing radios.
When flashing a ROM .. you gotta wipe everything except the external SD (Assuming you didnt move apps/data) there... remove android secure with a wipe, system wiped, boot, dalvik, cache, system, factory reset, internal SD, wipe wipe wipe wipe. If you have ever looked at the partitions after only one wipe you will know why all the fuss.
Assuming you flashed PERFECT, no dirty overlapping/conflicting stuff going on, and the rom has executed its post install scripts without being messed with, reboots done a few times to break it in.. the kernel you flash will have to be configured to the hardwares capabilities. Not all can be undervolted and or overclocked the same. . SD boost cache size is almost a must 1024 - 2048 or whatever are adequate .. might wanna do a benchmark in ROM Manager to see where your SD sees the best performance. Also, the IO scheduler type (sio, noop, cfq, vr, etc)
On demand is a good balanced governor but its only one in many variables... SD Swap.. dalvik vm heap sizes, JIT
pretty sure you know how to get into dev mode with those roms.. enable debugging .. if not, just go to phone info and hit the build a buncha times . .
memory and task management is another thing.. how many things you got loading at startup .. what is managing memory to close unwanted processes etc. .
Android Tune + ROM Manager should take care of that.. .
I've found the latest beanstalk rom with the latest uberkernel 4.3 and the Blaze modem isn't laggy but I have a new factory-refurbished phone. I have not moved any of the apps to the SDcard. But then again I don't have any games on the phone and I just came from an old Galaxy S 4g so I may not have any idea of what lag is. I noticed that some of the 4.3 roms, the Pac-Man nightlies, for instance, seemed slow enough so that I immediately flashed back to Beanstalk.
this may be another question, but I've noticed that the IO scores -- file system writes and database reads -- come out a bit slow on quadrant. On my previous phone, there was a script that sped that up, but I don't know what the equivalent would be for this phone and jelly bean.
this is getting a little ridiculous because the phone was working just fine and after i got back from marshmallow to kitkat it started acting differently than before. there was a lot of lag, and when i said a lot i mean that i had to restart my phone every few minutes to get it in some usable state.
then i thought maybe i should clean internal storage so i made a full wipe; the data, media, system, cache, dalvik... everything. and after that it was fine but not as it was before i flashed marshmallow rom.
now i'm a bit confused because i don't know what did i miss or it is the price of flashing custom roms?
Isn't it just a placebo effect?
can you elaborate your answer? what is exactly placebo effect here?
I mean, you kinda think its not running like it used to. I might be wrong tho
that's rly silly tbh been using 6.0.1 for more than a month now, feels same if not faster than 4.4.4 in some aspects.
Change your CPU governor, which rom did you use also? I've found Resurrection Remix to be much faster than stock.
Flash the rom twice with a data wipe in between. Remnants may exist.
Sent from my HTC One M9 using XDA-Developers mobile app
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
KobaltPanther said:
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
Click to expand...
Click to collapse
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
NinjaL said:
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
Click to expand...
Click to collapse
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
KobaltPanther said:
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
Click to expand...
Click to collapse
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
NinjaL said:
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
Click to expand...
Click to collapse
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
KobaltPanther said:
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
Click to expand...
Click to collapse
Yeah twrp is what I use too :good: