• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Recently flashed Miui XJ, got a couple questions/problems

M

MolecularSpade

Member
Ok so first problem:
Last night when charging my phone it said 91% and the LED was green, i left it to charge till 97%. I unplugged the charger, plugged it back in and it changed to fully charged straight away?

Next, this morning i got a notification on my phone to say that there is a system update, do i go ahead and install it straight away? is it safe?

Finally, ive got go launcher installed however sometimes when i try to open a folder on one of my homescreens it lags really badly. Nothing else lags at all? A reboot seems to sort it for a while. Any ideas?
 
MolecularSpade said:
Ok so first problem:
Last night when charging my phone it said 91% and the LED was green, i left it to charge till 97%. I unplugged the charger, plugged it back in and it changed to fully charged straight away?

Next, this morning i got a notification on my phone to say that there is a system update, do i go ahead and install it straight away? is it safe?

Finally, ive got go launcher installed however sometimes when i try to open a folder on one of my homescreens it lags really badly. Nothing else lags at all? A reboot seems to sort it for a while. Any ideas?
Click to expand...


Try delete battery stat via recovery (cwm) or Battery Calibration or calibrator from the market.

The update is fine, I think it's every Friday you'll get one. Started to really annoy me.

Some people (I think Rastaman but not 100% sure) had issues with go, having it sometimes lag while other people's has been fine.
I believe an older version works fine, but I couldn't say which since I've never had problems.
 
The latest Go is laggy on homescreens for me (v2.8) so I went Back. Battery stats are wiped everytime you plug the charger in anyway. Nothing to do with what % the battery reports as being full / empty. Calibration is the only way. But the unplugging and showing as charged may well have been a calibration of sorts.
 
Yeah. All bat stats are, is how much % of battery was used by screen since last time unplugged. How much battery used by cell standby etc etc
 
SUroot said:
The latest Go is laggy on homescreens for me (v2.8) so I went Back. Battery stats are wiped everytime you plug the charger in anyway. Nothing to do with what % the battery reports as being full / empty. Calibration is the only way. But the unplugging and showing as charged may well have been a calibration of sorts.
Click to expand...

How do you go back to the last version of go?
 
Not from the market with your current ROM and partitions.

Most custom memory tables actually shrink the cache partition considerably, and many ROMs contain features to work around this, basically using space on sd-ext or a RAM disc for the /cache. But in many cases the system checks the size of the cache partition on boot and only uses these workarounds when a small cache is detected, so with the standard memory table these features may not be activated.

Of course that's a limit on the actual apk size - if an app had a smaller apk and then downloaded other resources when run that would cause no problem (it's just the market that uses /cache this way). I don't think I've got any apps that size anyway, though I'm not a serious gamer.
 
Ok got another problem, after installing some more apps:

A2SD storage:
Total 0.96GB Free 623MB

Internal Storage
Total 148MB Free 18.27MB

So i decide to try moving some large games to my SD card and my internal free shoots up to about 40MB? Then i move some more and it goes all the way up to 70MB free! I dont understand how this works?
 
Are you confused because you thought that an app that was "on the phone" would actually be on your ext partition, and hence moving it wouldn't actually change the internal space used? Actually that would have been correct with Froyo, but with Gingerbread the story changed.

The ROM's a2sd script moves the apks, and (optionally) the dalvik cache. But an app can contain other elements, and these will still be in internal storage. With Gingerbread "moving to sd" now moves some other elements of the app as well as the apk (certainly the library, if the app contains one). So an app with a large library will take up less space when moved to SD, even when you have a2sd+ working. And very often the very large apps are that size because they have such a large library, so moving a big app can indeed have this effect.

Note that Google's move to sd does not move the dalvik cache, so since you have only 148MB internal the partition is valuable to you for that, and also the a2sd+ script moves apps that won't allow themselves to be moved to SD. So it's still a good thing for you to have! But if you are short of space then as you've seen moving some of the larger apps to sd as well can be beneficial.
 
Hadron said:
Are you confused because you thought that an app that was "on the phone" would actually be on your ext partition, and hence moving it wouldn't actually change the internal space used? Actually that would have been correct with Froyo, but with Gingerbread the story changed.

The ROM's a2sd script moves the apks, and (optionally) the dalvik cache. But an app can contain other elements, and these will still be in internal storage. With Gingerbread "moving to sd" now moves some other elements of the app as well as the apk (certainly the library, if the app contains one). So an app with a large library will take up less space when moved to SD, even when you have a2sd+ working. And very often the very large apps are that size because they have such a large library, so moving a big app can indeed have this effect.

Note that Google's move to sd does not move the dalvik cache, so since you have only 148MB internal the partition is valuable to you for that, and also the a2sd+ script moves apps that won't allow themselves to be moved to SD. So it's still a good thing for you to have! But if you are short of space then as you've seen moving some of the larger apps to sd as well can be beneficial.
Click to expand...

ah thanks for clearing that up, it just seemed that every guide i read said that i should keep things on the internal storage for the a2sd to work.
 
Well as I say, with Froyo there was no advantage at all in moving an app to SD once you had an a2sd script. And it is a bit messy having bits of the app spread between 3 places (sd, internal and ext) - but if the alternative is running out of space, then a bit of messiness is probably tolerable ;)
 
Hadron said:
Well as I say, with Froyo there was no advantage at all in moving an app to SD once you had an a2sd script. And it is a bit messy having bits of the app spread between 3 places (sd, internal and ext) - but if the alternative is running out of space, then a bit of messiness is probably tolerable ;)
Click to expand...

haha im usually a tidy person, but in this case, i will have bits of everything all over the place :)
 
You must log in or register to reply here.
Back
Top Bottom