Hey guys. I just upgraded to DU 4.3.1 from the previous version and I am wondering what amount of free ram I should be seeing when, after I turn the phone on, by holding down the home button. It usually shows about 50 or so megabytes. All I have installed is the gapps. I wiped cache and dalvic before installing. Just curious because I figured that it would have more.
eel_dahc said:
Hey guys. I just upgraded to DU 4.3.1 from the previous version and I am wondering what amount of free ram I should be seeing when, after I turn the phone on, by holding down the home button. It usually shows about 50 or so megabytes. All I have installed is the gapps. I wiped cache and dalvic before installing. Just curious because I figured that it would have more.
Click to expand...
Click to collapse
I remember this ROM not being particularly friendly with RAM... you might want to try the new KitKat DU build (it's on here somewhere)
skepticmconfirms 504536 said:
I remember this ROM not being particularly friendly with RAM... you might want to try the new KitKat DU build (it's on here somewhere)
Click to expand...
Click to collapse
Thanks for the confirmation, I think I will. I love these ROMs.
Related
I'm already running CM9 (awesome club release), which is great. I'm looking to update to the latest build 1.1.2.
Is it sufficient to wipe dalvik and then install the new zip? I could obviously wipe data as well but I'd rather not if I didn't have to.
killersiafu said:
I'm already running CM9 (awesome club release), which is great. I'm looking to update to the latest build 1.1.2.
Is it sufficient to wipe dalvik and then install the new zip? I could obviously wipe data as well but I'd rather not if I didn't have to.
Click to expand...
Click to collapse
This did not need a new thread.
killersiafu said:
I'm already running CM9 (awesome club release), which is great. I'm looking to update to the latest build 1.1.2.
Is it sufficient to wipe dalvik and then install the new zip? I could obviously wipe data as well but I'd rather not if I didn't have to.
Click to expand...
Click to collapse
Joker says you don't have to. It won't hurt though. After you reboot, I would power off, boot into recovery, and fix permissions. Doing that seems to correct the minor bugs that may arise.
Sent from my MB855 using xda premium
I have tried previous versions of cm9 2days ago I flashed the camera fix, and for some reason my battery is taking for ever to charge.. any ideas? I been plugged into wall charger for about 2 hrs now, only got a 20% increase of charge, haven't been running anything. Just texting here n there..
Sent from my MB855 using XDA App
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
I've been running 10.1.2, but this morning was notified of update. So I installed the update.
However, the update killed my Wi-Fi, in that I was getting signal, but no internet connection.
So I tried to roll back to 10.1.2, but now have the constant CyanogenMod loading animation and it's been like it for an hour. So I held down the power and volume button and it does exactly the same thing, reboots and get's stuck with the animation?
I can't turn if off or anything?
Can someone please help?
WannabeMKII said:
I've been running 10.1.2, but this morning was notified of update. So I installed the update.
However, the update killed my Wi-Fi, in that I was getting signal, but no internet connection.
So I tried to roll back to 10.1.2, but now have the constant CyanogenMod loading animaition and it's been like it for an hour. So I held down the power and volume button and it does exactly the same thing, reboots and get's stuck with the animation?
I can't turn if off or anything?
Can someone please help?
Click to expand...
Click to collapse
Have had similar problems would love a dev input here,think it has something to do with having to separately flashing a compatible kernel? Or a bug in cm recovery when whipe? Anyways flash meow kernel and ROM, then in twmp recovery wipe all under advanced, then reinstall cm, that should fix it for you.
cantenna said:
Have had similar problems would love a dev input here,think it has something to do with having to separately flashing a compatible kernel? Or a bug in cm recovery when whipe?
Click to expand...
Click to collapse
Frustrating, whatever it is...
cantenna said:
Anyways flash meow kernel and ROM, then in twmp recovery wipe all under advanced, then reinstall cm, that should fix it for you.
Click to expand...
Click to collapse
Sorry, but how do I do that?
Can anyone assist please, as I'm pretty stuck at the moment. Thanks.
WannabeMKII said:
Can anyone assist please, as I'm pretty stuck at the moment. Thanks.
Click to expand...
Click to collapse
Download cm-10.2-20131029-UNOFFICIAL-pollux_windy.zip from here
http://www.windowsxlive.net/xperia-ztablet-z-cyanogenmod-10-2-fidelity-edition-build-20131029/
wipe factory reset in cwm recovery and install rom
once booted into new rom reset into twmp recovery
wipe and advanced wipe all check boxes except last and iinstall cm rom
should boot now. let me know if it works for you. Did for me.
also see
http://forum.xda-developers.com/showthread.php?t=2383800
also side note, i upgraded to sony stock 4.2.2 befire goingbto custom
Perfect. I managed to get into CWM, cleared all the old data and re-installed 10.1 that was still on the SD card. I then installed Gapps and updated CM, but not to the latest this time!
Thanks for the help, I can relax now and the Mrs can now go on Facebook again
WannabeMKII said:
Perfect. I managed to get into CWM, cleared all the old data and re-installed 10.1 that was still on the SD card. I then installed Gapps and updated CM, but not to the latest this time!
Thanks for the help, I can relax now and the Mrs can now go on Facebook again
Click to expand...
Click to collapse
Anytime, happy wife, happy life!
cantenna said:
Anytime, happy wife, happy life!
Click to expand...
Click to collapse
Lol, so true! :laugh:
I am wondering if anyone can help. I installed a new rom and the data partition is showing 9.31GB /9.59GB used. I haven't loaded any additional apps since I started with this rom though, so I don't know what is using the data. Because of this, I can't install new apps.
When I loaded the rom, it shows 9GB free, but then after restarting for the first time, it uses up all 9GB. I've tried wiping and formatting the data in twrp, but it still has the issue.
I'm currently using PAC rom but I also had the same issue with Omni, Slimkat, and liquid smooth.
Any ideas?!!
You really don't need to start a second thread...
sent by baja kitkat S4
decaturbob said:
You really don't need to start a second thread...
sent by baja kitkat S4
Click to expand...
Click to collapse
Thanks for your help
Fitz1883 said:
I am wondering if anyone can help. I installed a new rom and the data partition is showing 9.31GB /9.59GB used. I haven't loaded any additional apps since I started with this rom though, so I don't know what is using the data. Because of this, I can't install new apps.
When I loaded the rom, it shows 9GB free, but then after restarting for the first time, it uses up all 9GB. I've tried wiping and formatting the data in twrp, but it still has the issue.
I'm currently using PAC rom but I also had the same issue with Omni, Slimkat, and liquid smooth.
Any ideas?!!
Click to expand...
Click to collapse
I'd say it's time to just wipe the phone using Odin and start over since you've had that issue across a few ROMs
Sent from my SCH-I545 using Tapatalk
Hello,
I am running Slim Bean 4.1.1 on my Galaxy S2 for almost one year now. I never had any bigger issues with this rom until yesterday. My battery died so I plugged the charging device in and re-started the phone but the booting animation won't go away. I am caught...I can still get into the recovery but that's it.
Any ideas how to solve this issue?
Thanks in advance
travisbotello said:
Hello,
I am running Slim Bean 4.1.1 on my Galaxy S2 for almost one year now. I never had any bigger issues with this rom until yesterday. My battery died so I plugged the charging device in and re-started the phone but the booting animation won't go away. I am caught...I can still get into the recovery but that's it.
Any ideas how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
Let the battery charge a bit until you boot it up, then see if you can boot into the rom. If you can't, boot into recovery and wipe regular cache and dalvik.
Best practice is to never let your battery die - these older devices (and some new ones as well) sometimes don't respond well to a complete discharge.
SteveMurphy said:
Let the battery charge a bit until you boot it up, then see if you can boot into the rom. If you can't, boot into recovery and wipe regular cache and dalvik.
Best practice is to never let your battery die - these older devices (and some new ones as well) sometimes don't respond well to a complete discharge.
Click to expand...
Click to collapse
Thanks!! I tried wipe cache and dalvik. Now I was stuck in the "android is upgrading starting apps" loop. So I just decided to do a full wipe and re-install everything...
travisbotello said:
Thanks!! I tried wipe cache and dalvik. Now I was stuck in the "android is upgrading starting apps" loop. So I just decided to do a full wipe and re-install everything...
Click to expand...
Click to collapse
If you're going to do a full wipe why not just upgrade to KK? The JB Slim isn't supported anymore, but @cyril279 has a few options for you, should you chose that route:
SlimSaber: http://forum.xda-developers.com/showthread.php?t=2772468
SlimKat: http://forum.xda-developers.com/showthread.php?t=2760074
SteveMurphy said:
If you're going to do a full wipe why not just upgrade to KK? The JB Slim isn't supported anymore, but @cyril279 has a few options for you, should you chose that route:
SlimSaber: http://forum.xda-developers.com/showthread.php?t=2772468
SlimKat: http://forum.xda-developers.com/showthread.php?t=2760074
Click to expand...
Click to collapse
That makes sense. I just upgrade to SlimSaber...and I love it. :victory: This morning I was soo p*ssed because of this whole thing but sometimes it just needs an event like this to try out new things
Thanks again!