I've tryed many 4.1 rooms and I have problems with lagging with almost all of them. I have tryed almost all recent 4.1 official leaks but still: lagging in desktop even without live wallpaper.
Some time ago I had AOSP what was working really good in comparison with new leaks. Even if I reset phone lagging is not gone (a bit better).
Also I have tryed installing stock rom and kernel before last flash (to 2.3, than to 4.0 and now to 4.1) but its still laggy. Any ideas, solution? Is this normal behavior? Because most of the people doesn't say its lagging to them...
When you flash roms do you do a full wipe? Do you go into mounts/storage and format system,data,preload, etc?
I'm wondering if maybe there are too many old files on your phone that should be cleaned out.
I'm currently using Alliance JB, the latest leak, and there is next to no lag.
I also use BlackCNA, an older ASOP rom, and that has ZERO lag.
When you flash roms do you do a full wipe?
Click to expand...
Click to collapse
Many times. Wipe, cache, dalwik... all...
Do you go into mounts/storage and format system,data,preload, etc?
Click to expand...
Click to collapse
Thats actualy the only think I didn't do (format all storage). But I have deleated folders, programs many times, so there shouldn't be many files that aren't currently in use.
Than I should delete partition one day, until then: any more ideas what would be wrong?
M-XXXX said:
Many times. Wipe, cache, dalwik... all...
Thats actualy the only think I didn't do (format all storage). But I have deleated folders, programs many times, so there shouldn't be many files that aren't currently in use.
Than I should delete partition one day, until then: any more ideas what would be wrong?
Click to expand...
Click to collapse
Formatting system, data, preload is recommended..so, may b u can flash a rom after following all these steps & then see the difference..I hv installed 2-3 custom JB roms & haven't felt that its laggy apart frm some known bugs on the leaked firmwares..
Related
Is it 100% neccessary to wipe before updating a rom if its the same rom just a different version? Like I have cyans 3.6.8.1 and want to go to cyans 4.0.1
I'm just looking for some clarification on this matter. I know when you switch roms you want to but I haven't really seen anything concrete on upgrading roms. Any help would be appreciated
No, no, no.... you need to wipe when you use a bathroom, not when you flash software
People will hate me for this but... here it goes
We wipe to avoid problems with the new rom. We DO NOT know if we will have problems, good chance that we will NOT. I never wipe untill something goes wrong, and I was just fine for last 14-15 flashes.
Here's another way to think about it.... do OTA updates wipe your phone? Didn't think so.
Flash away. If you have problems then, and only then, nand back to your previous configuration, wipe, reflash. Don't wipe after flash... Cyan's roms don't like that AFAIK.
Good luck.
SlicedKuniva said:
Is it 100% neccessary to wipe before updating a rom if its the same rom just a different version? Like I have cyans 3.6.8.1 and want to go to cyans 4.0.1
I'm just looking for some clarification on this matter. I know when you switch roms you want to but I haven't really seen anything concrete on upgrading roms. Any help would be appreciated
Click to expand...
Click to collapse
I heard somewhere that it's best to wipe when going from HTC rom to Google rom and vice versa. I know that for cyan's roms that if you rarely have to wipe (I had to wipe when trying out 3.9.11.*), but for the most part you won't have to (went from 3.4.6 to each update until 4.0.1 without wipe)
xidominicanoix said:
I heard somewhere that it's best to wipe when going from HTC rom to Google rom and vice versa. I know that for cyan's roms that if you rarely have to wipe (I had to wipe when trying out 3.9.11.*), but for the most part you won't have to (went from 3.4.6 to each update until 4.0.1 without wipe)
Click to expand...
Click to collapse
At this point..the only HTC roms we have are Hero and that's a whole another story. Not only you have to wipe but also reformat your sd. Big mess... not worth it IMHO. Your mileage may vary.
Thanks for ppointing this out though...
Personally, I wipe, then repair ext filesystems before I flash a new ROM. The only time I don't is when I'm updating a ROM that I have, cm x.x.x to cm x.x.x, in hich case I'll just repair ext's then flash. But, when in doubt...
Original question(s) seem to be solved.
Closing thread
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Did you perform a full wipe before applying CM9/10?
Eiertschik said:
Did you perform a full wipe before applying CM9/10?
Click to expand...
Click to collapse
If by full wipe you mean the three wipe options in OpenRecovery (Dalvik, Data and Cache) then yes. I even deleted the /system folder and nothing!
UPDATE: I tried to install CM10, removed system, data and cache through ADB and dalvik cache, installed CM10 and gapps. When booting, the first screen asking for language rapidly appears, and reboots. I tried to boot again, then I rapidly touched the screen when the screen appeared, and it didn't reboot! Well, that's better, but CM10 is too lagged for daily use, that's why I want to install CM9!
I'm using CM10 from couple of days..
I get enough RAM to run apps that I daily use...check for unwanted apps that are not being used, disable it through hwa setting app. Just use it for a day .. IMO CM10 is better than CM9.
BTW I removed gtalk, maps, email, exchange service and other unwanted apps from OR...which I don't use at all..
Sent from my Milestone using xda app-developers app
Hell Angel 1910 said:
Hey guys, I'm having a problem
Sorry if I'm posting this in a wrong area
Well, I'm using CyanogenMod 7.2.0 stable by Kabaldan for Milestone A853. Then I tried to install CyanogenMod 9 Nightly (from Skrilax build bot), the latest version. Everything was going well, then when I tried to boot, a screen about "Android is updating applications" appeared, and then after updating, the phone hard rebooted, back to the M logo. Then I left it booting again, and it rebooted again, though this time the update screen didn't appeared. Sometimes I get the first screen to appear, but I can't even touch the phone because it reboots before I try to do so. I tried installing CyanogenMod 10 (Skrilax nightly build bot again) and the same error happened! What is happening to my phone? I've never found anyone with this problem
Please help me! Thanks.
Click to expand...
Click to collapse
If nothing solves your problem, you should reflash the SBFs and start all over again. I had to do this sometimes. Formatting the SDCard (after backing-up your personal data) also helps to prevent this from ocurring.
Well, never mind, I was robbed saturday. Thanks for the help folks
Sad! But it's a chance to get a better phone. Good luck!
Tiago Costa said:
Sad! But it's a chance to get a better phone. Good luck!
Click to expand...
Click to collapse
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
justforlove said:
Really sorry to know that you have said goodbye to your great milstone... Anyway, I'd like to share what I did when I was in your situation:
- Flash the stock ROM to come back to stock 2.1
- Erase and format SD card
- Partion the SD card angain
- Root the fone and flash to the latest CM10
And now, my stone works like a charm and I have not yet to have idea to change to a new phone now :victory:
Just for sharing!
Click to expand...
Click to collapse
and BPSW for 2.1.1 is needed? or optional?
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Erovia said:
It's optional.
You only have to wipe data,dalvik-cache and data (you will lose all your information, so backup everything) and to create an ext partition on your sdcard.
Click to expand...
Click to collapse
yeah I know, I read the dev thread but can't make replies there. I am now on CM10 from 09/24 (last 4.1.1) and considering about CM10 4.2 but I was little bit confused about BPSW. And will there be problem If I will uprgade from 2.2? Because I don't have nandroid backup of 2.1
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Erovia said:
(FYI, the current CM10 is based on Android 4.1.2.
4.2 will be the next version of Android and probably CM11 will be based on it.)
Anyway, i upgraded from 2.2 to 4.0.4 and then to 4.1.1 and now 4.1.2.
I believe you can upgrade from 2.2 to 4.1.2 without any problem.
(but always make a nandroid before upgrading)
Click to expand...
Click to collapse
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Tiago Costa said:
Yes, it's perfectly possible upgrade from 2.2 Stock ROM, although it's more difficult to root it.
I did it without any problems.
Is there any difference between upgrading from 2.1 or from 2.2?
Click to expand...
Click to collapse
I've read somewhere, that one must upgrade to 2.2 because upgrading from 2.1 will cause problem with some hardware module.
zemko said:
Yeah, sorry for that mistake, my fault. I upgraded from 2.2 to 4.0.4 and now I have 4.1.1. I tried to upgrade to 4.1.2 from 4.1.1 but it was laggy (10/16 and 10/17) so I restore it back to 4.1.1 which is pretty stable and I will wait to better time for this upgrade, because it is my main phone and my boss is upset when I am not available when he calls me
Click to expand...
Click to collapse
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Erovia said:
Kabaldan is working on it. It seems, if the CPU's clockspeed is under 600MHz, then something is wrong with the GPU performance. (So you should consider using Performance CPU governor.)
Click to expand...
Click to collapse
I know that someone wrote it in dev thread for CM9 or CM10, but my battery is pretty weak, I am glad that with Juice defender it lasts for 12 hours and Performance governor is pretty aggressive to battery drain. Anyway thanks for answering my nooby questions
It 's been a week since i flashed saurom rom to my phone and it was really slow so i decided to go back to jb.i ve just installed paranoidandroid romand my phone still lags like hell.Everything is slow even the rom installing takes more time...
i always do all the wipes before and after the installation.Anyone has any idea to help?
You could try another kernel or install greenify and hibernate some apps. If it doesnt chaNge anything, at least you discard those as culprits.
it feels like my internal sd card has gone slow is this possible?
How old is your i9000? ho many rom do you have flashed?
ElmirBuljubasic said:
How old is your i9000? ho many rom do you have flashed?
Click to expand...
Click to collapse
2,5 years old .I ve flashed about 20 roms or maybe more.
You have to start with a clean slate, I guess
1. Backup EVERYTHING you can, even contacts, sms and notes to paper notepad
Don't forget about Nandroid, efs and programs ofc
2. Disable all your tweaks
3. Install the latest stock ROM via Odin 1.82 or Heimdall
4. Root it!
5. Install CM7 then CM9 then CM10.2
6. And Paranoid Android
After this hardcore method your phone shoud work as a charm
DumF0rGaming said:
You have to start with a clean slate, I guess
3. Install the latest stock ROM via Odin 1.82 or Heimdall
After this hardcore method your phone shoud work as a charm
Click to expand...
Click to collapse
what stock rom you suggest?
also i have to do a repartition is it not needed?
ntragas said:
what stock rom you suggest?
also i have to do a repartition is it not needed?
Click to expand...
Click to collapse
Get the JVU stock rom , the repartition makes the .PIT file in odin...
Get a stock ROM , CM7 or CM9 ; cause these 3 are the fastest and best.
To say the truth , you can forget CM10,CM10.1 and CM10.2 ; cause the battery life or the smoothness are quite bad.
I see CM10 and above only as a little gimmick
ntragas said:
what stock rom you suggest?
also i have to do a repartition is it not needed?
Click to expand...
Click to collapse
Maybe JVU from Heimdall thread? The last one is JW9
I'm not sure, but I think you have to use PIT file too. That's why I'm saying about backups
ntragas said:
2,5 years old .I ve flashed about 20 roms or maybe more.
Click to expand...
Click to collapse
backup evrything and wipe the internal sd card..
heimdall link for jvu is broken...any other suggestion?
Any latest ROM you see in www. You'll need this only to get stability
I noticed on several occasions that within a week or two after a new ROM flash, the performance goes down until it gets really annoying (choppy, actions take a longer time). This has happened to me on both stock and custom ROMs. I read on the boards suggestions like cleaning the cache, having task killers, etc. But I wonder, isn't caching supposed to speed up things by principle? Furthermore, some apps cannot essentially be killed, since they start automatically again shortly after.
q-parser said:
I noticed on several occasions that within a week or two after a new ROM flash, the performance goes down until it gets really annoying (choppy, actions take a longer time). This has happened to me on both stock and custom ROMs. I read on the boards suggestions like cleaning the cache, having task killers, etc. But I wonder, isn't caching supposed to speed up things by principle? Furthermore, some apps cannot essentially be killed, since they start automatically again shortly after.
Click to expand...
Click to collapse
Please don't use third party task killer. They are just waste of battery and performance.
It helps to wipe dalvik cache from time to time.
kevinrus123 said:
Please don't use third party task killer. They are just waste of battery and performance.
It helps to wipe dalvik cache from time to time.
Click to expand...
Click to collapse
Task killers, really? I had no idea. I have always thought that it's the otherway round, improving performance, because sometimes it's insane how many apps are running on the background.
Anyway, thank you for the tip.
q-parser said:
Task killers, really? I had no idea. I have always thought that it's the otherway round, improving performance, because sometimes it's insane how many apps are running on the background.
Anyway, thank you for the tip.
Click to expand...
Click to collapse
When you like a taskkiller use the preinstalled one. Press the homebutton for few seconds and swipe from left to right.
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
you wipe cache and dalvik cache then you flash rom on top.
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
bober10113 said:
you wipe cache and dalvik cache then you flash rom on top.
Click to expand...
Click to collapse
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
youdoofus said:
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
Click to expand...
Click to collapse
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
bober10113 said:
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
Click to expand...
Click to collapse
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
youdoofus said:
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
Click to expand...
Click to collapse
If I were to go to advanced wipe when flashing a new build if I were to leave data option alone. Will that keep all of my data or not?
edit:
@R77
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
bober10113 said:
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
Click to expand...
Click to collapse
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
youdoofus said:
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
Click to expand...
Click to collapse
did i make it sound like i was replying to you?
guess i should have quoted him to make it obvious.
and again, if he's on rom A 1.0 and wants to upgrade to rom A 1.1 then no need to clean wipe or del android folder each and every time.
have you ever had an OTA ? samsung dosent wipe clean ure device just because u upgrade. so his question regarding a similar scenario would apply, dirty flash would work fine.
and again as stated before, if there is weird stuff happening then just clean wipe. no need to get nuclear each and every time.
btw various rom builds require clean flashes because they suppose people are coming from other roms. not saying that there aren't situations where continuously dirty flashing the same custom rom all along its progress wouldint eventually mandate ir benefit from a clean flash but i know of no one that clean flashes each time their rom dev updates/increments a build. they/we only do it incase of issues, this is of some sorts an unwritten law so to speak. devs even state it when users ask if they can do as such.