[Q] Is that ICS Bug or Kernal Bug? - Galaxy S I9000 General

well i tested some roms like slim ics, dark night, aokp and gamerz. But i seen one similar issue which i was facing and it irritates me alot . The problem is when i installing some apps the phone becomes slow. Even when i press the menu button it will open slowly and touch sensitvity becomes lag. Is everybody facing this issue please let me know

Have you tried to wipe cache, dalvik cache and data?
Do you restore your apps from Titanium Backup? That could be the problem if you made the backup when you were on Gingerbread.

MortenJ said:
Have you tried to wipe cache, dalvik cache and data?
Do you restore your apps from Titanium Backup? That could be the problem if you made the backup when you were on Gingerbread.
Click to expand...
Click to collapse
Every time i will do wipe/factory settings, wipe cache, dalvik cache and data. Rom runs extra ordinary at the first time after using some days, the phones becomes slow when i touch on menu button it will opens very slow and i checked the ram the phone is using only 200mb rest 140mb is free.
I didn't restore any apps from titanium. For every new rom i will install new apps from Google Play.

Related

Dalvik cache wipe. Now EVERYING FC

So I did this once before and had to nand restore. I just did it again on a new install of fresh 1.1 with apps2sd and it did the same thing. Instant FC on ALL apps at boot. I'm doing this from RA menu. why is this happening?!
*I noticed the typo in title but can't fix it*
not sure what the problem is I noticed that as well.
is there a reason you want to wipe the dev cache?
I just wanted to clean up the cache just incase there were any screwy entrees... It's not really a big problem, it just makes me a little nervous...
That always happened to me whenever I tried to do that. I'm not sure how you're "supposed" to do it, but I wipe the dalvik-cache before I load a new ROM.

Upgrading Roms MIUI 1.6.1 to 1.6.17

Hi i'm currently running MIUI 1.6.1 and i just finally got it completely setup exactly how i want it, took me like hours upon hours a day for a week getting all my apps and contacts and data set up along with themeing etc etc
I want to upgrade to the newer one that just came out today the 1.6.17 -- Do i have to do a FULL Factory reset/delvik cache and/ cache wipe?
or can i just wipe the delvik and cache and then flash overtop without losing everything?
Basically i dont want to have to go back in and re-fix my Sprint VVM and re-add Swype again as both those took me like 50 installs a piece to get working, along with like 50 apps i downloaded, and all my contacts, etc, etc do i have to do a full wipe and start from scratch again, or can i just flash and upgrade and keep all my stuff without doing a full factory reset and also without having a ton of errors and force closes?
pulazki said:
Hi i'm currently running MIUI 1.6.1 and i just finally got it completely setup exactly how i want it, took me like hours upon hours a day for a week getting all my apps and contacts and data set up along with themeing etc etc
I want to upgrade to the newer one that just came out today the 1.6.17 -- Do i have to do a FULL Factory reset/delvik cache and/ cache wipe?
or can i just wipe the delvik and cache and then flash overtop without losing everything?
Basically i dont want to have to go back in and re-fix my Sprint VVM and re-add Swype again as both those took me like 50 installs a piece to get working, along with like 50 apps i downloaded, and all my contacts, etc, etc do i have to do a full wipe and start from scratch again, or can i just flash and upgrade and keep all my stuff without doing a full factory reset and also without having a ton of errors and force closes?
Click to expand...
Click to collapse
Doesn't Titanium Backup or Mybackup Pro work with MIUI?
pulazki said:
Hi i'm currently running MIUI 1.6.1 and i just finally got it completely setup exactly how i want it, took me like hours upon hours a day for a week getting all my apps and contacts and data set up along with themeing etc etc
I want to upgrade to the newer one that just came out today the 1.6.17 -- Do i have to do a FULL Factory reset/delvik cache and/ cache wipe?
or can i just wipe the delvik and cache and then flash overtop without losing everything?
Basically i dont want to have to go back in and re-fix my Sprint VVM and re-add Swype again as both those took me like 50 installs a piece to get working, along with like 50 apps i downloaded, and all my contacts, etc, etc do i have to do a full wipe and start from scratch again, or can i just flash and upgrade and keep all my stuff without doing a full factory reset and also without having a ton of errors and force closes?
Click to expand...
Click to collapse
First backup using MIUI's built in backup. It had two parts: system and stuff, and apps. Back up all the apps. Then backup wifi and desktop at the very least. I don't backup contacts because then I get duplicates.
Reboot into recovery
Nand backup
Wipe just cache and dalvik cache.
Flash the update
Reboot.
Usually this is fine. But if you get fc's then you probably need to wipe clean everything and then restore via backup.
It's not.that bad. I've never had any problems re-installing swype and/or sprint voicemail. The only thing I usually have to redo is the theme.
Evo HW 003
MIUI 1.6.17
Cut Corners theme
I have been running MIUI for a couple of months now. Whenever I flash a new release (an update, in my situation) I just wipe cache & dalvik then flash. Once the rom has fully booted and settled, I'll reboot. I let it fully boot, then reboot into recovery (Amon 2.3) and "fix apk uid mismatches", then wipe cache and dalvik again, flash Tiamat since they started including the CM kernel instead, then reboot and I'm good to go. My theme sticks throughout and I haven't run into any problems doing it this way, other than broken themes from constant ui changes... which thankfully finally slowed down. Sometimes I'll skip on fixing permissions, it's more of a ritual than necessary.
Last week I decided it was probably time for a full wipe so I did. Between the MIUI Backup app & Titanium Backup Pro, setting back up took roughly 15-30 minutes (including flashing the rom and kernel). Just nandroid first to be safe, but I've always treated it as an update.
(from... Evo/MIUI/Tapatalk)

stuck on HTC white screen after clearing dalvik

Hey all,
I have an ext3 partition for my apps, and I noticed that it was using 400+ mb when I only have for about 200 mb MAX of apps. So I wondered if it was my dalvik cache (which i also store on that same partition) since it had been using 80 MB before.
So I cleared dalvik cache and cache (not data), and now my phone won't boot anymore.
I can still go to recovery. I tried backing up (ofcourse AFTER I had the problem) and then restoring, hoping somehow that would work, but nothing. I have waited an hour on the HTC logo, so I doubt that the dalvik re-initializing would take that long?
Anybody knows what I should do? Should I try to reflash my ROM (without clearing data first) to try if that works. Or if that does not work, is the last resort really using a previous nandroid backup?
Cheers!
nobody? :s
wolfway said:
Hey all,
I have an ext3 partition for my apps, and I noticed that it was using 400+ mb when I only have for about 200 mb MAX of apps. So I wondered if it was my dalvik cache (which i also store on that same partition) since it had been using 80 MB before.
So I cleared dalvik cache and cache (not data), and now my phone won't boot anymore.
I can still go to recovery. I tried backing up (ofcourse AFTER I had the problem) and then restoring, hoping somehow that would work, but nothing. I have waited an hour on the HTC logo, so I doubt that the dalvik re-initializing would take that long?
Anybody knows what I should do? Should I try to reflash my ROM (without clearing data first) to try if that works. Or if that does not work, is the last resort really using a previous nandroid backup?
Cheers!
Click to expand...
Click to collapse
Hi, strange one this!!! Dalvik cache normally regenerates itself on boot after a wipe,But you say you backed up after the problem!!! Why would you back up knowing you had the problem? So I guess that's why you can't boot up your rom. So yes I would definitely try a rom install like you said and failing that then its either a fresh install wiping everything except sdcard of course or an old nandroid. Goodluck.
" once its gone,its GONE."
I made the backup after the problem to see if restoring it somehow would fix the bug that I had (which as I suspected was not the case). But it was not the origin of the error.
Anyway I reflashed my ROM and it seems that everything is okay again, still have all my data etc.
Still my ext3 is using way to much space but that's another thing to look at

[q] bluetooth peculiar issue

I had installed AOKP ICS ROM, in which theres a bluetooth not working issue, then I did davlik and cache wipe and installed AURORA 4.1a Over it.. Evrything was smooth except Blutooth continued to be non functional. Now I again did the double wipe and installed ELORA over it, and the Blutooth is still an issue. Is there any way to correct this without a complete wipe?
Hello jy0thish,
i think you can not avoid a full wipe. Every rom is different and if you don not delete the data it will cause problems with other roms.Thats why u need to do a full wipe before installing a new rom, You can backup SMS and contacts with SuperBackup and apps with TitaniumBackup. If the full wipe wipe is not the solution, than flash the gingerbread update by Huawei again, so you have a clean phone and try it again .
good luck

[Q] JB CM10 sudden bootloop. How to recover?

Hi all, I changed the levels automatic brightness adjustments, then a call occurred and I aswered. When I closed the call, my defy+ rebooted immediately (no messages appeared) and then went in a bootloop: cyano glowing logo, then a single red LED flash, then it repeats.
Tried to clear dalvik cache, with no luck.
Is there a way to recover easily? Unfortunately I have no backups but want to keep contacts and application data. Not interested in keeping SMS's or photos.
Thank you
Contacts are usually stored with gmail account. I don't know about the app data though.
Sent from my MB526 using xda app-developers app
tried to wipe cache, dalvik cache, then install latest CM10 but ended up with the very same problem.
Should I only go RSD?
manualle said:
tried to wipe cache, dalvik cache, then install latest CM10 but ended up with the very same problem.
Should I only go RSD?
Click to expand...
Click to collapse
Make a backup of your /data in custom recovery, then wipe your /data partition (and cache/dalvik if you want), then reboot.
This will most likely get it to boot up again, then you can use Titanium Backup to restore your apps and app data. Do not restore your complete backup, because it most likely got corrupted, and do not restore System apps either.
You can restore SMS, by restoring Phone/Messaging Storage, and to restore Call Logs/Contacts, restore Contacts Storage. You might want to check the "Migrate System Data" checkbox in Preferences if it doesn't work at first.
Thank you, but I've already gone RSD. Good to know anyway. tnx
manualle said:
Thank you, but I've already gone RSD. Good to know anyway. tnx
Click to expand...
Click to collapse
Sorry we couldn't find a solution in time.
For me, it's not that important; I full wipe at every sign of a bootloop. With the Desire I used to wipe all, including /system!
As long as you have a google account, you can reinstall the ROM and add your Google account at the beginning. That restores your previous setup of applications and appdata. Contacts are automatically synced and added to People.
droid_<3er said:
Sorry we couldn't find a solution in time.
For me, it's not that important; I full wipe at every sign of a bootloop. With the Desire I used to wipe all, including /system!
As long as you have a google account, you can reinstall the ROM and add your Google account at the beginning. That restores your previous setup of applications and appdata. Contacts are automatically synced and added to People.
Click to expand...
Click to collapse
well, it's really not that bad.
Trying the latest CM with good results
thank you for the info! bye

Categories

Resources