Related
Hi Guys,
I am on ICS 4.0.4 and my S3 shows 779 MB, which is always busied by 680 or so!!!
I checked an S2 with ICS 4.0.4 and the memory is 830, and is busied by 450 on average. (S2 has larger memory than S3 on ICS4.0.4???)
So what is wrong with the S3 memory? i keep on killing apps all day and night to bring it to 450 or around, I dont have too many programs, and, i am not using except two widgets, checking on the background processes annd programs, most of the system's stuff is running on its own, even if i freeze some using Titanium pro.
Anyone has the same problem (if i can call it a problem?!) is that normal??!
Why would you consider it as a problem? Android is best at multitasking. You don't have to kill apps, its the nature of the beast so to speak to have a semblance of the apps running in the background for your convenience.
Sent from my GT-P3113 using XDA Premium HD app
Bigger screen and stuff like Smart stay and S voice eat up extra Ram.
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Okay, i got it, No more killing APPS , now the question is, how come the S2 has more overall ram than the super S3, on ICS4.0.4??? considering the 779MB to the 830? its just a noob question
gennoz said:
Q: Whats up with the ram?
Click to expand...
Click to collapse
Q: What's up with searching the forum?
Why are people asking the same questions over and over again?
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
goodie said:
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
Click to expand...
Click to collapse
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Click to expand...
Click to collapse
Bullied?
Try reading the rules before posting. Rule number 1 is search before asking a question. Now you're asking the difference between odexed and deodexed... Do you seriously think you're the only person who has asked this? It's discussed EVERYWHERE!
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
Click to expand...
Click to collapse
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
The search on the site is horrible. I use Google and type xda after anything I'm looking for
Sent from my LG-P999 using XDA App
Roastario said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
Wow, seriously thanks for your time
Query on RAM....
norpan111 said:
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Dude... My s3 ram in task manager is showing 883..... previously it was 779mb.... i donno wat would b the cause for this.... i have updated to jelly bean.... please ans my query....
Roastario said:
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
I suppose "standard ROMS" have no apps or anything in the "Dalvik cache" ? (as all apps have "stand-alone" APK's ?) ... correct ?
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
noobee1 said:
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
Click to expand...
Click to collapse
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
corleno said:
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
Click to expand...
Click to collapse
yes I am well aware of rooting/un-rooting and other basics, had done all that on my S2(i9100), also found it more fun and efficient than stock but time is the only factor that's stopping me from experimenting. and thanks for the omega tip. I am certainly going to flash a custom ROM, after trying out few official ones, When I do, I would definitely go for Omega, alot of people recommending that one.
Omega is good as is WanamLite, Foxhound and Hyperlight. Smoothest I've used were Foxhound and Omega although I'm running WanamLite at the moment. Smoothest version I've used.
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)*
If anyone is experiencing this problem, I hope the following steps may help.
I would like to express my appreciation to XDA members, who have commended and helped out with this. Credits go to @LordManhattan and @abuihsan . Many thanks for your help.
1/ Do a re-flash: I always thought my device was a c6802, after I flashed c6833, it helped.
2/ Do a factory reset/ Cache wipe/ Dalvik Wipe/ in recovery or in the phone settings.
3/ Install SD-Maid and clean the mess from the programs, also take a look at APPCONTROL to see which is running. You can freeze it here.
4/ Install Performance control to Underclock your CPU. Believe me, 1.7Ghz is far too enough for all the tasks you need.
5/ Use more pwerful tool, like Titanium Backup to stop all the backgound-running apps. You just need to leave the one which were in GREEN color.
6/ Use Wakelock Detector to see which apps get your phone out of deepsleep. Mostly they are Facebook and Messenger. My advice: Disable Facebook notice and if you don't use chat quite often, don't install facebook messenger.
Hope these help.
Personally I had tried a lot of methods, including checking the processes and re-insert the memory card but no such helps. Therefore, if you need any advice or any comments, feel free to send me an PM or reply here, I will gladly help you out, like what the community had helped me our of my situation.
Hi everyone,
Recently I just bought a ZU from a local vendor here. It runs 4.2.2 with no problem. However, I want to get rid of the *new system update* and I also want to use the xperia Themes, I decided to upgrade to 4.3.
My phone model is C6802, and I chose the file here : http://forum.xda-developers.com/showthread.php?t=2453921
The upgrade went through fast and smooth, as I had experienced in many Sony devices.
However, after getting to 4.3, I had noticed some problems as follow:
+ Heat: Device heats up very fast, even left alone. Just imagine you have the phone on 100% battery lying on your table, a moment later it heats up and the battery drops dramatically.
+ Battery drop: Just as mentioned above, the battery drops quickly. I do not expect extreme battery life on this device, but since 4.3, it is too low, I can barely make it to 6 hours without doing anything consuming battery.
+ Process: When checking the battery, I notice that most of the process that takes up battery is Android OS, which nearly 50-60%. I use the phone frequently to answer SMS and call, sometimes play games. I think that the most used applications should be the bad-ass screen?
I am running on the 14.2.A.0.290 with R4B.
Anyone had experienced this problem before, or know a solution to fix? Will clearing the Dalvik Cache help? I had re-flash several times but the problem is still there.
Many thanks in advance.
Click to expand...
Click to collapse
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
Sent from my iPad mini using Tapatalk HD
fjevel said:
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note:
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
First of all, thanks for your reply and suggestion.
I had tried to flash the roms multiple times, but the problem still exists. Furthermore, I even flash back to 4.2.2 and the problem is still there. The phone heats up slowly and battery runs out pretty fast.
I had installed the Wakelock Detector on my device and I will update the situation tomorrow, I will leave it there for a night and see the status tomorrow.
Did you wipe after updating? I had the same issue when i updated to 4.3.
Correct me if I'm wrong, but as long as he's been downgraded to 4.2.2 again, he'd have to wipe. At least that is how it was on my Xperia Z.
-KJ
this might not be related, but I've been noticing much worse battery life today than normal! i normally only drop about 50% in 24 hours, but today I've dropped 30% in just a few hours. Android OS seems to be doing it...
no real heat issue tho, maybe slightly warmer from whatever the OS is doing, but nothing too major. running stock rooted 4.3
had that on my Xperia Z on a 4.1 or 4.2 build (dunno which one). Sounds strange, but simply turning off the sync fixed the problem, give it a try :laugh:.
Hope it also helps on your XZU.
LordManhattan said:
Did you wipe after updating? I had the same issue when i updated to 4.3.
Click to expand...
Click to collapse
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
justsomebody said:
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
Click to expand...
Click to collapse
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app. I use GREENIFY and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
abuihsan said:
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app.and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
Click to expand...
Click to collapse
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
justsomebody said:
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
Click to expand...
Click to collapse
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
abuihsan said:
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
Click to expand...
Click to collapse
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
justsomebody said:
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
Click to expand...
Click to collapse
The thing is, you don't need a task killer/cleaner app. It was useful way back on Android 2.1/2.3, but you shouldn't use it at all on 4.0+. You're actually making things worse.
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
ij0rgei said:
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
LordManhattan said:
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
Click to expand...
Click to collapse
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
ij0rgei said:
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
Click to expand...
Click to collapse
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
LordManhattan said:
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
Click to expand...
Click to collapse
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
ij0rgei said:
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
LordManhattan said:
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
Click to expand...
Click to collapse
ok. so I haven't done anything at all to remedy the situation. I figured I'd ask about it before messing it up myself. I upgraded to .290 via pcc. it updated fine with no errors. once it was done updating, it was hot and battery was diminished. I had seen on another thread that most people had that happened so I didn't see it as an issue, just a side effect of the update process.
I have been checking back to see if anyone was having heating issues with 4.3 after the update and didn't hear about it until I had seen this thread. the OP stated he flashed .290 on his 6802 and is rooted. I am not, so I wasn't sure if the steps he was taking were the same given my 6833 being completely stock.
Sent from my C6833 using xda app-developers app
Hey guys,
Currently I am using CM11 M9 snapshot, boeffla kernel, no OC/UV. But the problem occured even back on CM 10.2 Jelly Bean.
The phone randomly freezes when there is a lot going on (updates for example), also it becomes laggy after a while and needs a few minutes of quiet time. Even after a full wipe and only ROM install (no apps, no custom kernel) I sometimes ran into it freezing for a few seconds like it's working hard and then coming back. It seems to register touch commands and executes them "when it's back".
By now I have over 120 apps installed that I use from time to time. I thought having a big amount of apps does not matter since they're not running at the same time and even then the android memory management does a good job?
I am really confused, maybe I have broken hardware? Is there any way to test my hardware stability/quality? Could the CPU have degraded? Or the internal storage? What else can I do to my phone to "clean it up"? I thought a factory reset or FULL WIPE, clean install and trimming the storage is all I can do? I uninstalled the facebook app which seemed to help a little bit but I am still confused.
Would this help at all I wonder, but it's only for jelly bean.
I know there are multiple threads out on this but they all recommend "factory reset & clean install" which is what I did...
I really hope I did not make thread x-thousand on this case but I did not find anything related to "phone slow after factory reset".
Thanks in advance guys.:highfive:
Cant do anything
Behemoth1702 said:
Hey guys,
Currently I am using CM11 M9 snapshot, boeffla kernel, no OC/UV.
The phone randomly freezes when there is a lot going on (updates for example), also it becomes laggy after a while and needs a few minutes of quiet time. Even after a full wipe and only ROM install (no apps, no custom kernel) I sometimes ran into it freezing for a few seconds like it's working hard and then coming back. It seems to register touch commands and executes them "when it's back".
By now I have over 120 apps installed that I use from time to time. I thought having a big amount of apps does not matter since they're not running at the same time and even then the android memory management does a good job?
I am really confused, maybe I have broken hardware? What else can I do to my phone to "clean it up"? I thought a factory reset or FULL WIPE, clean install and trimming the storage is all I can do? I uninstalled the facebook app which seemed to help a little bit but I am still confused.
Would this help at all I wonder, but it's only for jelly bean.
I know there are multiple threads out on this but they all recommend "factory reset & clean install" which is what I did...
I really hope I did not make thread x-thousand on this case but I did not find anything related to "phone slow after factory reset".
Thanks in advance guys.:highfive:
Click to expand...
Click to collapse
Propably thats M9 problem. Seems like every snapshot is getting worst and worst.
I added some information to the first post.
The problem occured even back on CM 10.2. It just started getting worse and worse over time. It was the reason I wiped and flashed CM11 M9. I do not feel a difference between the two.
But seriously, that freaking facebook app gone helps a lot.
Still, is there any way to test my hardware stability/quality? Could the CPU have degraded? Or the internal storage?
i dont really know
Behemoth1702 said:
I added some information to the first post.
The problem occured even back on CM 10.2. It just started getting worse and worse over time. It was the reason I wiped and flashed CM11 M9. I do not feel a difference between the two.
But seriously, that freaking facebook app gone helps a lot.
Still, is there any way to test my hardware stability/quality? Could the CPU have degraded? Or the internal storage?
Click to expand...
Click to collapse
I dont think your hardware is degrading, try to to do a comlete wipe even the internal storage...anyway i didnt notice a big difference too. My s3 was slowed down since M8 and now M9 with this problems. Just switched to those s5 roms
PearOfSteel said:
I dont think your hardware is degrading, try to to do a comlete wipe even the internal storage...anyway i didnt notice a big difference too. My s3 was slowed down since M8 and now M9 with this problems. Just switched to those s5 roms
Click to expand...
Click to collapse
Internal storage wipe -> format SD card?
Hmm, switching from CFQ from ROW scheduler really bumped up the performance.
I start to suspect that that dredded facebook app and the CFQ scheduler screwed my device. I will test some big apps/games now.
EDIT: Aaaand it's running pretty good. Mhh, I will continue monitoring.
Good
Sent from my SM-G900F using XDA Free mobile app
Hello guys.. I'm a flashaholic.
The reason i'm here, is because i've just realized, that i haven't had my quick fix for some time now..
Everything seems so stable, except the *mic* issue, but hey, i fixed it with a hands-free.. Otherwise, i'm very happy with my phone, it works, it doesn't use up that much battery, and it doesn't crash, you can even do normal stuff to it.
But to the point.. I really, REALLY miss AOSP, especially the theming.
I can live with the occasional bugs, though i wish it could be at least somewhat stable.. *You know, im not that picky*.
But the one thing that keeps me from using AOSP; is the camera app from Sony, because i like taking pictures of my son, and the environment..
Are there any Camera app out there comparable to the Sony equivalent?
Oh, the urge..
Shidapu said:
Hello guys.. I'm a flashaholic.
The reason i'm here, is because i've just realized, that i haven't had my quick fix for some time now..
Everything seems so stable, except the *mic* issue, but hey, i fixed it with a hands-free.. Otherwise, i'm very happy with my phone, it works, it doesn't use up that much battery, and it doesn't crash, you can even do normal stuff to it.
But to the point.. I really, REALLY miss AOSP, especially the theming.
I can live with the occasional bugs, though i wish it could be at least somewhat stable.. *You know, im not that picky*.
But the one thing that keeps me from using AOSP; is the camera app from Sony, because i like taking pictures of my son, and the environment..
Are there any Camera app out there comparable to the Sony equivalent?
Oh, the urge..
Click to expand...
Click to collapse
I have the same urge, I wanna get the full output from my Xperia Z2, feel all those four cores working in my hand. But that one Sony Camera app stops me because it's beautiful. It's matchless. That's the only reason I'm not changing my ROM and be bound to what Sony's put in my phone.
I am in the same boat here! I want to flash PA so bad especially with all their features but then the camera app, the noise cancelling features and x-reality etc is really stopping me from doing so
i use to be in the same boat before i noticed there is no point to flashing roms when im on a rom which does what i want
perhaps you should find a rom which has what you want
Same here.I literally used to flash a new ROM on my Nexus 5 everyday. As has been said though, the stock Z2 ROM does everything I want it to and rooted with some xposed mods its perfect.I just have to learn to live with my phone the way most other people do.
just a note
formatting then writing a rom to your system slows your device ALOT, it also cause alot of other issues but that comes after long wear n tear
Envious_Data said:
just a note
formatting then writing a rom to your system slows your device ALOT, it also cause alot of other issues but that comes after long wear n tear
Click to expand...
Click to collapse
Does this include doing a clean install? I mean doing clean install also slows the system? I've done clean install (re-install the stock Sony Z2 ROM) for 3 times till now. (Via Sony PC Companion)
V4LKyR said:
Does this include doing a clean install? I mean doing clean install also slows the system? I've done clean install (re-install the stock Sony Z2 ROM) for 3 times till now. (Via Sony PC Companion)
Click to expand...
Click to collapse
included:
repair via sony pc companion
firmware upgrade
flashing custom rom
flashing ftf via flashtool
flashing via emma
all of those wear bout the same, its a matter of which one you do the most
in this case, flashing custom roms is this one
Envious_Data said:
included:
repair via sony pc companion
firmware upgrade
flashing custom rom
flashing ftf via flashtool
flashing via emma
all of those wear bout the same, its a matter of which one you do the most
in this case, flashing custom roms is this one
Click to expand...
Click to collapse
But I've done clean install via Sony PC Companion for 3 times now... So does this mean my phone isn't as fast as the day I bought it? Even though I've installed a clean ROM?
V4LKyR said:
But I've done clean install via Sony PC Companion for 3 times now... So does this mean my phone isn't as fast as the day I bought it? Even though I've installed a clean ROM?
Click to expand...
Click to collapse
minor signs should show about 25th time to my experiance
Envious_Data said:
minor signs should show about 25th time to my experiance
Click to expand...
Click to collapse
I remember reading somewhere years ago that flashing new firmware over and over will eventually wear out the hardware and cause it to slow down/eventually fail. I can't seem to find anything for this when searching though! Would it be possible for you to shed some light on what I should be searching for or what causes this issue?
Thanks in advance!
Devzz said:
I remember reading somewhere years ago that flashing new firmware over and over will eventually wear out the hardware and cause it to slow down/eventually fail. I can't seem to find anything for this when searching though! Would it be possible for you to shed some light on what I should be searching for or what causes this issue?
Thanks in advance!
Click to expand...
Click to collapse
there is something called read/write cycle life
you can only write info so many times onto a disk before it wears out and stops working
formatting a partition takes a huge amount of cycles, installing roms does the same too because its alot of data that has to write
some info
http://en.wikipedia.org/wiki/Flash_memory
Envious_Data said:
there is something called read/write cycle life
you can only write info so many times onto a disk before it wears out and stops working
formatting a partition takes a huge amount of cycles, installing roms does the same too because its alot of data that has to write
some info
http://en.wikipedia.org/wiki/Flash_memory
Click to expand...
Click to collapse
Cheers for the reply! From what I read on the link, it says most flash memory have a P/E cycle of around 100,000 and from what I can remember, it varies depending on the type/quality of the flash memory used (Nexus 7 2012 had rubbish flash memory which a lot of people complained about). Just going off an assumption that the Z2 has a P/E cycle of 100,000, wouldn't it take quite a lot of ROM flashes before the memory deteriorates? Or is it more due to the size of the data being written/erased than the amount of times it is being done?
Sorry for the questions, I know this isn't the thread for it but it is interesting to me!
Devzz said:
Cheers for the reply! From what I read on the link, it says most flash memory have a P/E cycle of around 100,000 and from what I can remember, it varies depending on the type/quality of the flash memory used (Nexus 7 2012 had rubbish flash memory which a lot of people complained about). Just going off an assumption that the Z2 has a P/E cycle of 100,000, wouldn't it take quite a lot of ROM flashes before the memory deteriorates? Or is it more due to the size of the data being written/erased than the amount of times it is being done?
Sorry for the questions, I know this isn't the thread for it but it is interesting to me!
Click to expand...
Click to collapse
I used to flash a lot roms everyday on various devices. I didn't notice any side effects of it. As I know a little about hardware there is nothing to fear. You can imagine than one memory cell is one bit of data. If it withstands 100 000 writes it literally means that you can save data (eg. flash rom on it) 100 000 times. There is no way that you can cross this number even with everyday flashing. And it doesn't matter how much data we are writing because each memory cell deteriorates individually, so if we write on 1000 cells it means that every cell will deteriorate only by one write operation which means every cell will still be able to be written 99 999 times.
Another thing is that the storage memory in smartphones is usually one chip which means that all your data including /system partition (which you overwrite during rom flashing) and your photos and music on /data are on one physical device. The conclusion is that if you are afraid of rom flashing and wiping you should also be afraid of saving photos to internal memory. And since we are using our int. memory and change files placed on it a lot it means that we can flash roms as we please without consequences.
Ruku1994 said:
I used to flash a lot roms everyday on various devices. I didn't notice any side effects of it. As I know a little about hardware there is nothing to fear. You can imagine than one memory cell is one bit of data. If it withstands 100 000 writes it literally means that you can save data (eg. flash rom on it) 100 000 times. There is no way that you can cross this number even with everyday flashing. And it doesn't matter how much data we are writing because each memory cell deteriorates individually, so if we write on 1000 cells it means that every cell will deteriorate only by one write operation which means every cell will still be able to be written 99 999 times.
Another thing is that the storage memory in smartphones is usually one chip which means that all your data including /system partition (which you overwrite during rom flashing) and your photos and music on /data are on one physical device. The conclusion is that if you are afraid of rom flashing and wiping you should also be afraid of saving photos to internal memory. And since we are using our int. memory and change files placed on it a lot it means that we can flash roms as we please without consequences.
Click to expand...
Click to collapse
Thanks for the thorough explanation. I had my suspicions this would be the case and you've driven it home by explaining the whole music/data/pictures scenario. I used to flash PA and other roms on my N4 more often than I care to count but I never once saw a decrease in performance so it's good to know (personally and for others) the phone's read/write performance is not going to be realistically affected! :highfive:
Envious_Data said:
minor signs should show about 25th time to my experiance
Click to expand...
Click to collapse
I've flashed previous android devices ( HTC magic / Desire HD / SGS 3) 100+ times each with no obvious slow down, my albeit limited understanding was that NAND chips where rated for 100k+ P/E cycles?
ghostofcain said:
I've flashed previous android devices ( HTC magic / Desire HD / SGS 3) 100+ times each with no obvious slow down, my albeit limited understanding was that NAND chips where rated for 100k+ P/E cycles?
Click to expand...
Click to collapse
Correct from the wiki link provided a few posts ago:
"Most commercially available flash products are guaranteed to withstand around 100,000 P/E cycles before the wear begins to deteriorate the integrity of the storage.[21] Micron Technology and Sun Microsystems announced an SLC NAND flash memory chip rated for 1,000,000 P/E cycles on 17 December 2008"