Related
The fruits of my deodexing project are now available for everyone to taste. What this ROM has is JH7 fully deodexed and zipaligned, and then tweaked. I have decided to remove the focus off the optimization, as others have made far more advances, and my choices may not be agreeable to someone else. I am not responsible for anything that happens to your phone, but I have tested this on my phone, and other than the issues noted below, I have not run across anything deal breaking. This is just a different way to optimize the files, so risk of any hardware damage is minimal. You'll only run into software that won't work.
How to install:
1. Download the zip file, and place it on the sd card.
2. Fire up ROM manager, and apply from SD card, also recommend doing a nandroid back up at the same time
3. ???
4. Profit
What yout get:
1. Stock JH7 deodexed, and zipaligned
2. AT&T and Samsung bloatware removed
2. Superuser and Busybox preinstalled
3. build.prop preedited to allow you to see all market apps
4. The kernel is untouched during the update, but the user data, and cache are wiped. You will need a Titanium Backup to restore.
Known Issues:
1. This is a stock style ROM, and you have to apply any optimizations or fixes manually, or using something like SRE. The JH7 files are all there (except the odex's of course), so the latest SRE should be compatible in theory, but I have always done all tweaks on the phone myself in the past so I am not 100% sure. I'll let some of you be the guinea pigs and report back.
2. Deodexing, and zipaligning is not some magic bullet for performance increase. I personally see no significant difference between the stock performance and this installation. But this is more flexible down the line to get us nearer to Vanilla Eclair due to having been deodexed.
How to Remove:
Use ROM manager, and restore previous backup.
The ROM can be downloaded Here:
Captivate-Deodexed-JH7_v_0.2-Stock
I hope for this to become a test bed of new ideas I can try out to make things better on our phone. So if you want to test it and guide me, I'd appreciate your input. If someone wants to take this and build upon it further, feel free to do so. I'll look into fixing the two apps force closing, with focus being on the camera, followed by the keyboard. Squashed.
Wow lets see what's to come off this + sre + new kernel + voodoo lag fix + froyo!
BRING ON THE THEMES!
WOw! How long did this take you???
TheTodFather said:
WOw! How long did this take you???
Click to expand...
Click to collapse
Not all that long. The deodexing itself is very automated. Making the ROM took a couple of more days to work out the updating script. I still need to work on the best way to integrate superuser and busybox.
i'll give it a shot!
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
skinien said:
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
Click to expand...
Click to collapse
I've wandered this as well
I would try it but I am too happy with how I've got it. The next time I flash it, it's gonna be to stock so I can get the 2.2 OTA. The work tho, I will say thank you for that.
Quick question..Why is sideloading disabled???
Flashing in just a sec, will update.
Sideloading is controlled by the settings.db file in dbdata. When you flash this ROM, that file gets wiped out and is rebuilt on first boot. I think the original is in the ramdisk packed with the kernel. So on first boot the old crippled file is recreated for you to hack into again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Camera FC all the time, besides that ROM is pretty fast and zippy good job OP.
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Will installing this ROM negatively affect my phone in any way besides voiding the warranty?
spook said:
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Click to expand...
Click to collapse
It will be very easy for me to release the vanilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force closure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rather have a stock deodexed ROM that they optimize themselves, I can release it a short time. I will also have to look at tweaking the deodexing process some to get rid of the force closes on the keyboard and camera apps.
+1 on a vanilla Rom..That would be great
rajendra82 said:
It will be very easy for me to release the vnilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force clodure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rathe have a stock deodexed ROM that they opimize, I can release it a short time. I will also have to look at tweaking the deodexing process to get rid of the force closes.
Click to expand...
Click to collapse
vanilla would be great my friend...much appreciated
OP updated with stock deodexed ROM linked.
Now I need your help. I know the Camera app that is force closing is Camera.apk, but what app is the Samsung keyboard? On the same lines, when an app force closes, is there a log file generated somewhere to explain what happened.
frenchtoasted said:
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
Click to expand...
Click to collapse
Camera issue acknowledged. Looking to fix that. The superuser app version I used had that issue anyway on stock ROM before deodexing, later versions seem to have solved it. I have now decided to keep this a stock ROM project to weed out extraneous issues such as these. WiFi worked fine for me at home and work, so I am not sure what's going on at your end.
E_man5112 said:
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Click to expand...
Click to collapse
Other than the kernel, everything that SRE does will be wiped out, as the whole system, data, and cache partitions will revert back to stock. You can always re flash SRE though.
I made this thread over in nexus s forums, but I wanted to post it here for anyone using Ice cream sandwich. It really makes a difference. Much smoother!!
Alright, so I have been reading about how to supercharge ICS for awhile, but the process looked daunting. However I figured it out, and it works great! This will work on ANY ROM, so try it out!
I have been using this for awhile, and it's just super smooth. I've been using it a lot lately, and it hasn't given me a bit of lag yet! It's just gone!
What is V6?
V6 supercharger is a script that manages the RAM memory. This makes multi-tasking much faster, and it knows when to kill off apps that are taking a lot of RAM. This makes your phone a lot faster and more efficient!
Here is the person who made the script: V6 Supercharger
Here is a dl link to the script: DOWNLOAD LINK
I'm in! So... How Do I Do this?
Well I made a video for you:
Here are instructions:
1. Download the supercharger script from the link above and put it on the root of your SD card.
2. Get an app called script manager from the market. It's free. Open it up and click on the supercharge script from the list of what's on your SD card. Click the SU button, then hit run.
3. Go through the setup. Set scrolling speed to 1. When they ask if you want to integrate it into the system, say yes. You will get to a list of about 30 options after a little bit.
4. Select number 7 for this phone, and hit enter. It will go through a whole bunch of stuff.
5. It will ask you to superclean and restart. SAY NO. You'll do that inn a minute. Just hit the home button.
6. Open the browser on your phone and go to : android.mimic.ca and hit the upload button. There will be a popup, select root explorer (Install it if you don't have it already). Go into system/framework/ and select the services.jar file. It will take you back to the website. Hit upload. The page will reload. Now select the CMW flashable zip option and download it. Go to root explorer and move that to the root of your SD card.
7. Reboot into recovery, wipe cache and dalvic, then flash the zip. Reboot. Done! Enjoy the speedieness!
Click to expand...
Click to collapse
Let me know what ya think!
P.S. Here is where I posted it originally: http://forum.xda-developers.com/showthread.php?t=1541806
A few things.
1, we've had Supercharger here for a long time.
2, Select 0 for scrolling speed, not one, and it scrolls faster and smooth
3, CMW Flashable?? You mean CWM?? As in recovery?? Uhh, why flash a new recovery? And if that IS what you're saying, CWM sucks on the EVO. Might be great on other phones, but definitely not on the EVO.
4, your steps are wrong, after you make your selection in script manager, you enter the choice for exit, and when it's done, back out to the root, then hit data, then hit the Supercharger.su in Data, select run at boot, when it;s done, back out. I don't know where you got going to some website, etc.
unless doing it for ICS is just a completely different process.
HipKat said:
A few things.
1, we've had Supercharger here for a long time.
2, Select 0 for scrolling speed, not one, and it scrolls faster and smooth
3, CMW Flashable?? You mean CWM?? As in recovery?? Uhh, why flash a new recovery? And if that IS what you're saying, CWM sucks on the EVO. Might be great on other phones, but definitely not on the EVO.
4, your steps are wrong, after you make your selection in script manager, you enter the choice for exit, and when it's done, back out to the root, then hit data, then hit the Supercharger.su in Data, select run at boot, when it;s done, back out. I don't know where you got going to some website, etc.
unless doing it for ICS is just a completely different process.
Click to expand...
Click to collapse
I had an EVO for a year, I know that this is how you supercharge gingerbread. However it is different on Ice Cream Sandwich. The services.jar file needs to be patched for the supercharger script to work. That's where the website comes in. The patched services.jar can be flashed via recovery. Or it can be replaced manually. Look at the supercharger thread, in the second post. It's all there.
CMW isn't great on the EVO. It may work on other recoveries, I'm not sure. Everyone that has a Nexus S uses CMW as it's great on that phone.
I'm looking into running the data/Supercharger.su at boot. I've never done that before. My supercharger setting have stuck after many reboots without doing that however.
I figured that there had to just be a stark difference for ICS.
CWM is probably the best Recovery on a majority of phones out there. Just not the Evo for some reason
I'm not sure about all ICS roms, but with AOKP. Supercharger works with and without patch. But I noticed it is even better with the patch. Also, script works fine without setting script manager for it a boot.
LinuxGuru007 said:
I'm not sure about all ICS roms, but with AOKP. Supercharger works with and without patch. But I noticed it is even better with the patch. Also, script works fine without setting script manager for it a boot.
Click to expand...
Click to collapse
The RAM manager in V6 works without the patch. However for it to be able to re-prioritize the apps (lock home in memory, bulletproof apps, etc..) you need the patched services.jar.
Yeah I updated Post 2 to better explain that ICS won't load the ADJ priorities from build.prop or local.prop and the services.jar mod is to get the priorities changed along with getting the launcher supercharged.
I got this script running on my evo 4g with gummy worm rom and its great.. Question can I run this with papa smurf tweaks... thanks
I ran through all the steps on my Gummys install on my Evo. I didn't notice that much of a change when compared to supercharging my GB install. Perhaps i'm doing something wrong?
thnxx for sharing.
neno2323 said:
I got this script running on my evo 4g with gummy worm rom and its great.. Question can I run this with papa smurf tweaks... thanks
Click to expand...
Click to collapse
Nope. These tweaks do it all.
I ran through all the steps on my Gummys install on my Evo. I didn't notice that much of a change when compared to supercharging my GB install. Perhaps i'm doing something wrong?
Click to expand...
Click to collapse
If you did it according to the video then it should be working. I haven't tried it on that ROM
Wanna thank Evol4G for the idea of starting a thread to focus on future development of MIUI ICS and how it can carry over to other ICS ROMS.
This is an add-on thread to talk about Specifically MIUI ICS and the different parts of the ROM that need specific attention.
This is NOT the place to ask about HWA, WIMAX, lagginess or anything that is probably attributed to user error or lack of reading/searching skills.
GUIDE TO RUNNING A BUG FREE MIUIv4
This guide goes over all the steps you'll need to get as close as we can for a bug free MIUI, A lot of bugs people get can be avoided if the steps are done propperly that is why this thread is so important..
THE GOAL HERE IS TO GET EVERYONES EVO RUNNING SMOOTH!
IF YOU FEEL THAT YOUR METHOD IS BETTER PLEASE POST IT! The whole point here is trial and error to see how we can get these ROMS to run as smooth as possible and to expose the less than obvious bugs to help the devs pin point the issues..
I have followed all of the ICS Threads on XDA pretty carefully and I have made a career out of determining the very best way to go about setting up a new ROM on a phone.
I know that ALL of the Devs working on ICS Roms are fantastic in what they do and should be commended for what they have accomplished, but in MY opinion, Swiper/Fergie's MIUI v2.4.6 is the closest to a complete ROM out of any of them, but it's not as easy as a quick wipe and a flash to get it up and running.
This is how I flashed this ROM, from step 1 to finish and probably why i have a fast, responsive, almost bug free ICS ROM that is easily my daily. I'll never go back to Gingerbread.
A lot of this is the same as what I have in my All Things Evo Guide
The first thing I do is prep the ROM itself. I remove all the ringtones, alarms and notifications from the Zip file. I keep those on my SD Card already, so I don't need them in there. I also have Astro File Manager on my Phone and I use that to back up all my apps, occasionally. I take the apps that I know I'll need right away from the backup folder for Astro and add them to the zip.
Specifically, Titanium backup, Maps, GPS Status, Connectbot, and now, the new VVM for ICS, which DOES work!
http://forum.xda-developers.com/show....php?t=1547780
Step 1. This is a MIUI ROM, which means GPS could be an issue, so the first thing I do is make a nandroid of my current Setup, then I restore my stock/rooted ROM.
Step 2. I update Profle and PRL, then I do the Sense GPS Fix.
You must be in a Sense ROM for this
Open Maps; get a lock on your position.
Open GPS Status & Tool Box, get a lock on your Sats and then hit Menu>Tools>Manage A-GPS State>Reset.
Open Dialer and dial ##GPSCLRX#
In the popup that asks for your password, enter your MSL, (You'll need MSL Reader from the market) then reboot.
When the phone is rebooted, Open Maps, get a lock; Open GPS Status, hit Menu>Tools>Manage A-GPS State>Download. Once you are locked onto your Sats, power down, then Reboot to Recovery.
Of course, I only use Amon Ra and in Recovery, I wipe everything, completely; Factory Reset., then each option underneat that, except SD Card:
Then I run Factory Reset again, then Cache and Dalvik Cache and Data again, jsut to make sure it's all clear.
Go to Flash, and Flash the Rom. Once it's done, go right back to flash and flash DT A2SD, the nI boot to System and once booted, I let it sit for a good 10 minutes, so everythign get's booted up and settled in.
At this point, I open LBE manager (Superuser) and set all my permissions to on and accept all.
I open Maps, get a lock, open GPS Status, and I already know I'll get a lock on my sats. Then I hit menu and update GPS Data.
Next is Connectbot, and I move my Dalvik Cache to my SD Card. Here's the commands
su
a2sd check
a2sd cachesd
The phone will reboot and again, I just let it sit for about 10 minutes.
Once I wake it up, I set my preferences, display, sounds, accounts, etc. MIUI ICS hasd a TON of new settings and one is the Status Bar Options. Hit Customize Statas Bar Notification and make sure Hide Notification is turned off. This will allow notifications to show up.
Once I'm done, I reboot to recovery, wipe Cache and Dalvik and Flash my Kernel.
The BEST kernel to use right now is Mason v0.14 SBC No FSO. I also Flash Vipermod.
That's it. If you use a different kernel and you have problems, this is the first place to look.
Upon reboot, I let the phone settle, then I open Titanium backup and restore my apps/Data. Now, I have had a lot of problems in the past with TB Freezing up when U try to restore all 117 apps I have in one session, so I do it in 3 now. I alphabetize the apps and then go A-H, I-P, Q-Z
Once finished, I open Rom Toolbox and go to Autostart Manager and make sure all the apps I DON'T need to be runnign at boot are toggled off. Then I set Car O Dope Tweaks. I'm one of the believers that Car O Dope is for AOSP, V6 is for Sense. I have yet to give Smurfs tweaks a run, but I plan to, soon.
I reboot and run Vipermod -50 in Connectbot, and then setup my desktop folders, etc. Then I g othrough any apps I need to set preferences for, Make sure VVM is working and that is basically it. Took some extra time, but I shake my head at the problems people are having that are almost alwasy attributed to shortcutting the process.
Almost all of the links and files anyone needs are on the guide in my signature
Bugs & Fixes.
• USB Connect - The two ways to fix this are with the app, USB Mass Storage in the market or the FTP Function is File Explorer.
• Camera only takes 3MP pics - D/L Camera ICS from the market and you'll get up to 8MP
• Theme Manager - There are very few themes for MIUI ICS. I understand that a new Theme Manager should be coming soon, according to the rumors.
• Music Player/Theme Sounds not seeing music folder - D/L Rescan Media form the market. Problem solved.
• Slow 3G/Data Speeds and Market Downloads. For me, after about a day, this fixed itself
Known Issues
No WIMAX
No HWA, yet
No Front Facing Camera
No Video Recorder
I know these are a lot of steps but if you can follow them I promise your phone will see massive improvement.. it's worth it, trust me
First of all, You'll see that my steps are close to hipkats that's because i learned a bit of this from him but I do a few things different, one of the main things is that I don't use the SENSE GPS fix, gpsfix from the play store works great for me and saves me the headache of the sense fix..
Secondly, I'm running swiperrat's MIUI 2.4.6, if you haven't tried it yet I suggest you do, it's the most stable yet IMO..
(*) asterick means that this step is highly recommended but not necessary
1) View thread to download Swiperrat's MIUI v4 HERE
* Download Dark Tremor's Apps2SD HERE
* Download viperMOD HERE
* Add 3rd party apks to the zip before flashing, this step isn't necessary but it does save you some time..(I added Titanium Backup,Terminal Emulator, GPSFIX, Srpint VVM for ICS)
2) Reboot into recovery (Amon Ra IS HIGHLY RECOMMENDED!!!!!!GET IT HERE!!!!!)
3) Wipe user data/factory reset, cache, dalvik cache, data, and boot (I do factory reset, cache, and dalvik 3x)
4) Flash ROM (DO NOT FLASH CUSTOM KERNEL YET!!!)
* Flash DTA2SD
5) Boot up phone and let it set for about 10 minutes
* I recommend waiting until the sd has fully completed its read before unlocking the phone
6) Run GPSFIX
* If you have DTA2SD I strongly recommend moving cache to sd as well, I garuntee you will absolutely love how much free space you'll have on your internal storage
TO MOVE CACHE TO SD open up terminal emulator and type in all lowercase
"su"
"a2sd check"
"a2sd cachesd"
7) Reboot into recovery, wipe cache and dalvik and flash custom kernel, I use MASON Kernel the one in my signature, and let sit for another ten (hipkats recommendation)
* Set up tweaks, I use Car-o-Dope which you can find HERE
8) Restore backup via TB or MIUI BACKUP
9) Use any kind of startup manager you have and disable all the apps you don't need to start up at boot.. (this helps reduce the time the phone takes to boot and stops stupid apps from running in the background behind your back) THANKS HIPKAT, idk why i was forgetting to do this, I used to all the time but the past 5 or 6 flashes I forgot lol
10) FIX PERMISSIONS (I hate ROM manager and don't even have it installed on my phone so this is how i do it)
- Open Terminal Emulator type in all lowercase "a2sd check" then "a2sd fixapk"
11) Reboot into recovery (only if you want vipermod, if not then just reboot)
* Flash Vipermod and reboot, then open terminal emulator again and type "vipermod" then set it to your liking (i set at -50mv)
12) Download MX player from the play store once installed go to settings and make sure s/w is checked and h/w is unchecked (THIS FIXES THE CHOPPY VIDEO!)
13) THE MOST IMPORTANT. IF YOU DON'T DO THIS YOU'VE WASTED SO MUCH TIME AND EFFORT!.. enjoy
Reserved
Thanks for sharing your knowledge. Just realized the recent version of dta2sd wasn't on my sd after reading your post.
Sent from my PC36100 using xda premium
thanosart said:
Thanks for sharing your knowledge. Just realized the recent version of dta2sd wasn't on my sd after reading your post.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I'm using an old version of dta2sd, it still works perfect but to be honest it's only because I've been to lazy to update... I guess I'll get on that tonight
sent from my kick ass evo using xda premium
I have the same version I've had for quite some time. Is there a newer version?
HipKat said:
I have the same version I've had for quite some time. Is there a newer version?
Click to expand...
Click to collapse
ya, hyperlink is in my post ;] tbh i'm reconsidering upgrading... I know the version i have works and have yet to have a problem with it so i don't really see the point in updating... anyways this thread needs some love... I would say move it to MIUIandroid but tbh this thread isn't supposed to be solely about MIUI in the long run it's supposed to help ALL ics roms but i don't think people understand that yet...
Native Messaging works for sending/receiving MMS in MIUI ICS by Swiper/Fergie so al lwe're waiting for is FFC, Video Recorder, HWA.. a few other things.
Since MIUI is based on CM, shouldn't this be able to be reversed to bring CM9 to the Evo?
what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!
zetsui said:
what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!
Click to expand...
Click to collapse
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work
josuearisty said:
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work
Click to expand...
Click to collapse
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.
Dr. Orange said:
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.
Click to expand...
Click to collapse
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10
zetsui said:
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10
Click to expand...
Click to collapse
Hmmm. The only issue I've had is trying to restore system apps/data between android 2.3.x and 4.0.x/4.1.x. Never had problems with restoring various other apps. That being said, you shouldn't have an issue restoring any apps from ics to jb.
Don't restore the google play store. That's a system app and I think that's why you've had problems. Just flash gapps when you flash roms. You can then do batch restore in titanium and it will restore your missing apps/data. I think that should fix the problems you've been having.
zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.
skeevy420 said:
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.
Click to expand...
Click to collapse
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?
zetsui said:
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?
Click to expand...
Click to collapse
Most devices have 4+ vsel slots. Moto phones are screwed by the bootloader\limited Moto Kernel features.
It should be. The thing with the bravo (when tweaking governors) is trying to find the magic values that use vsel2 more than vsel3 and still provide a smooth ui. The reason that a 700mhz vsel2 works good is that the Bravo comes with a stock vsel3 of 800mhz. CM7\9 work\use resources much better than our stock Froyo making that 700mhz perform like 800mhz on a stock rom.
Now that CM10.2 nightlies are available for Nook HD and HD+, I am opening this thread as a place to discuss common issues people may face when migrating to 10.2.
I am watching a lot of people posing the same questions time and again on the development thread, so this thread will provide people to share issues and find solutions to their common problems.
I updated to CM 10.2 after a dirty install on 10.1. I immediately regretted the decision.
1) The market would fail to download or update any apps giving [RPC:S-5:AEC-0] error. This issue arises, I believe, because the identity of the device has changed. People have suggested that clearing the cache (setting>storage>cache) and removing and adding your Google Account solves this problem. In my case, at least, it did not solve the problem but I will not stop anyone from trying it, as it is much quicker than the solution to this problem.
2) Clock and Google Music would crash.
So here is what I suggest
CLEAN INSTALL CM10.2 to avoid any problems.
3) I have been using this version of GAPPS
http://forum.xda-developers.com/showthread.php?t=2378992
[courtesy of johje] and have not had any problems with it (except two clock icons in apps which I can live with)
4) Superuser still does not work with 4.3. You have to download this version from
http://forum.xda-developers.com/showthread.php?t=1538053&page=350
[Thanks Sherip for suggesting this solution]
before you could use adaway or Titanium back
5) [Resolved] Lock Screen slider positions does not work. Even if you add or remove shortcuts, your preferences will not be saved.[Edit: After a couple of restarts, now I can see a save button on top, Before that it only showed the reset button.]
6) Finally, for the first few hours after the install, the tablet was excruciatingly slow. so slow that I wanted to go back to 4.2. I think it was because of all the background Google processes and after the first few hours, the tablet is much more responsive now.
I will add more issues here once I found them. Please feel free to share, discuss and find solutions to your common CM10.2 issues.
---
Deafcyclist said:
Sorry if this is a noobish question but what can I do to make a 'clean' install? Just wipe data/factory reset? what other thing I can wipe to 'clean' it up further? Is it possible to completely remove the previous CM for a clean slate install?
thanks.
Click to expand...
Click to collapse
That's what I did. I spent around six hours trying to fix a dirty install over CM10.1. The dirty install preserves your apps and settings (if it works). However, I would suggest that you update your backup (using Titanium Backup or any backup app you use) and then wipe data/factory reset before installing CM10.2. I installed CM10.2 img, gapps and Superuser zip together and restored most of my apps and settings within the first hour.
Deafcyclist said:
Sorry if this is a noobish question but what can I do to make a 'clean' install? Just wipe data/factory reset? what other thing I can wipe to 'clean' it up further? Is it possible to completely remove the previous CM for a clean slate install?
thanks.
Click to expand...
Click to collapse
Make sure you also clear dalvik cache, battery stats and format internal sd. And please don't restore apps from Titanium Backup
---------- Post added at 05:38 PM ---------- Previous post was at 05:32 PM ----------
I installed 10.2 dirty but everything seems to work fine.
Try Greenify donated version it allows you to hibernate system apps to free up RAM
---
kareinanikko said:
Make sure you also clear dalvik cache, battery stats and format internal sd. And please don't restore apps from Titanium Backup
---------- Post added at 05:38 PM ---------- Previous post was at 05:32 PM ----------
I installed 10.2 dirty but everything seems to work fine.
Try Greenify donated version it allows you to hibernate system apps to free up RAM
Click to expand...
Click to collapse
I personally do not think that restoring user apps from Titanium backup will do any harm to your system. I know that it also backups system apps and settings which should not be transferred to CM10.2 but user apps, e.g., Facebook can safely be restored from backup. Just make sure that you have updated the latest version of your apps or else you may have to update them immediately in Play store. Even then, you retain all your settings which is important for me.
Though I have not yet installed 10.2
I really appreciate you starting this thread so I know what I'm in for when I do.
Thanks for the info. Since the only issue I have is some lag that is likely more hardware than software related and one game "Vice City" not working, I will pass for now. Can not be bothered starting from scratch with over 200 apps and about 17GB in total size. Not seeing the value-add in relation to current performance. Comics, video, browsing, emulators, games and Flash all perform fine. A little UI and app start lag seems the lesser of the "evils". Especially since I doubt software can compensate for a 4470 with 760mb of free ram and a older gpu pushing a 1080p display. The lower res Nook has none of the lag and is quite zippy. Only real difference is less than half the pixles to push.
Seems likely I could go through the effort and still have the lag. Added: I am tired of that word "lag". I prefer the "L" word.
rushless said:
Thanks for the info. Since the only issue I have is some lag that is likely more hardware than software related and one game "Vice City" not working, I will pass for now. Can not be bothered starting from scratch with over 200 apps and about 17GB in total size. Not seeing the value-add in relation to current performance. Comics, video, browsing, emulators, games and Flash all perform fine. A little UI and app start lag seems the lesser of the "evils". Especially since I doubt software can compensate for a 4470 with 760mb of free ram and a older gpu pushing a 1080p display. The lower res Nook has none of the lag and is quite zippy. Only real difference is less than half the pixles to push.
Seems likely I could go through the effort and still have the lag. Added: I am tired of that word "lag". I prefer the "L" word.
Click to expand...
Click to collapse
I would say this upgrade is worth the hassle to go through a fresh install. My main motivation to upgrade to 10.2 was the presence of TRIM support which both increase the responsiveness and life of emmc. I have read [Leapliner] the trim app some people installed in 10.1 bricked their tablets so upgrading was the only option. If you make an update of your user apps, a fresh install will take less than an hour. Also make sure to take a nandroid backup. Even if something goes wrong, you can have your old setup back in a flash.
Dirty Install
excalibar001 said:
Now that CM10.2 nightlies are available for Nook HD and HD+, I am opening this thread as a place to discuss common issues people may face when migrating to 10.2.
I am watching a lot of people posing the same questions time and again on the development thread, so this thread will provide people to share issues and find solutions to their common problems.
I updated to CM 10.2 after a dirty install on 10.1. I immediately regretted the decision.
Click to expand...
Click to collapse
I did a dirty update, but my results were largely different from yours.
1) Superuser works for me.
2) You used the old gapps (20130726), and I used the new (20130813) so I had no issues with the play store.
3) It was really laggy until I discovered that it only seems to like ( on my tablet anyway ) the ondemand governor with the cfq scheduler.
I have lost a few apps/widgets, but nothing that I miss so far ( stuff like 'Temp + Cpu v2 ), but it screwed up gl to sd until I manually edited its .xml file.
I update to 10.2 20130814 from 10.1 20130813, and it seems to be working but I have a lot more live testing to do...
RageAgain said:
I did a dirty update, but my results were largely different from yours.
1) Superuser works for me.
2) You used the old gapps (20130726), and I used the new (20130813) so I had no issues with the play store.
3) It was really laggy until I discovered that it only seems to like ( on my tablet anyway ) the ondemand governor with the cfq scheduler.
I have lost a few apps/widgets, but nothing that I miss so far ( stuff like 'Temp + Cpu v2 ), but it screwed up gl to sd until I manually edited its .xml file.
I update to 10.2 20130814 from 10.1 20130813, and it seems to be working but I have a lot more live testing to do...
Click to expand...
Click to collapse
That's good info to have. I'll try ondemand with cfq scheduler, and see if that helps. The only thing I noticed was that it was "slightly" slower than the 10.1 version. But not horribly so. I'll give this a try and see if it helps.
My stable pre 10.2 nightly salutes all of you folks that jumped in!
I will remain peaking out of a bunker, twenty fathoms below sea level until a common trend of opinion is it is worth it- not seeing that yet.
Unless lag free, I see no reason to take the six hours (really) to download and set-up everything again. 272 apps at 17GB total. So far, some state it is
actually slower and some say faster- net result though at this point seems a net wash.
bpaulien said:
That's good info to have. I'll try ondemand with cfq scheduler, and see if that helps. The only thing I noticed was that it was "slightly" slower than the 10.1 version. But not horribly so. I'll give this a try and see if it helps.
Click to expand...
Click to collapse
That is how I feel too. It is slower but not enough to make me migrate back.
rushless said:
My stable pre 10.2 nightly salutes all of you folks that jumped in!
I will remain peaking out of a bunker, twenty fathoms below sea level until a common trend of opinion is it is worth it- not seeing that yet.
Unless lag free, I see no reason to take the six hours (really) to download and set-up everything again. 272 apps at 17GB total. So far, some state it is
actually slower and some say faster- net result though at this point seems a net wash.
Click to expand...
Click to collapse
stable? you have a stable build? my 10.1 reboots at the worst times
The nightly just before 10.2 version has had zero reboots for me and very low battery bleed in standby. Not seeing how 10.2 is worth it ATM since for every person raving, another is either having issues, or a slightly slower device. This does not include folks that installed over 10.1 rather than start from scratch.
Looking forward to 10.2 with feedback that is more favorable for performance to offset my apathy for starting from scratch.
rushless said:
Looking forward to 10.2 with feedback that is more favorable for performance to offset my apathy for starting from scratch.
Click to expand...
Click to collapse
Understandable. I am not having the same slowdowns and lag that occurred with the 20130814 now that I have updated to the 20130815 of the 10.2. Much smoother and more responsive, as now it never doesn't wake up right away when I push the power button, and the lock screen responds immediately. I have had no spontaneous reboots, and my screen hasn't gone black momentarily at all. Hopefully this positive trend will continue. My only current issue is the apps that no longer work, or no longer work correctly. Still a far larger percentage work without incident than not, and the ones that don't are mostly Android 4.3 problems and not Nook HD(+) problems so they will be fixed eventually.
All in all, I would say that 4.3 isn't as bad as it was initially made out to be...
RageAgain said:
Understandable. I am not having the same slowdowns and lag that occurred with the 20130814 now that I have updated to the 20130815 of the 10.2. Much smoother and more responsive, as now it never doesn't wake up right away when I push the power button, and the lock screen responds immediately. I have had no spontaneous reboots, and my screen hasn't gone black momentarily at all. Hopefully this positive trend will continue. My only current issue is the apps that no longer work, or no longer work correctly. Still a far larger percentage work without incident than not, and the ones that don't are mostly Android 4.3 problems and not Nook HD(+) problems so they will be fixed eventually.
All in all, I would say that 4.3 isn't as bad as it was initially made out to be...
Click to expand...
Click to collapse
I agree. I'm one who said it was slightly slower than 10.1 initially, but after updating to the 0815 nightly version, it doesn't seem to be the case anymore.
Although, I also changed the governor to OnDemand, and scheduler to cfq, like I heard from somebody who got better results with that configuration, on another post somewhere... So I don't know if it was one or the other, or a combination of both. But I have no complaints with the current setup.
RageAgain said:
I did a dirty update, but my results were largely different from yours.
1) Superuser works for me.
2) You used the old gapps (20130726), and I used the new (20130813) so I had no issues with the play store.
3) It was really laggy until I discovered that it only seems to like ( on my tablet anyway ) the ondemand governor with the cfq scheduler.
I have lost a few apps/widgets, but nothing that I miss so far ( stuff like 'Temp + Cpu v2 ), but it screwed up gl to sd until I manually edited its .xml file.
I update to 10.2 20130814 from 10.1 20130813, and it seems to be working but I have a lot more live testing to do...
Click to expand...
Click to collapse
Could you please let us know what you did for the dirty update, I am planning to upgrade from CM10.1 to CM10.2 without loosing the Apps and User profiles(?) For normal updates in CM10.1, I just run the ROM update choosing the Update file (No cache clearing etc, it automatically update without going to CMW recovery mode, at least i dont have to choose any options in this kind of update). If this is not correct method of Upgrading to 10.2, could you please provide all the steps that i need to do. Thanks in advance.
sudheersagar said:
Could you please what you did for the dirty update, I am planning to upgrade from CM10.1 to CM10.2 without loosing the Apps and User profiles(?) For normal updates in CM10.1, I just run the ROM update choosing the Update file (No cache clearing etc, it automatically update without going to CMW recovery mode, at least i dont have to choose any options in this kind of update). If this is not correct method of Upgrading to 10.2, could you please provide all the steps that i need to do. Thanks in advance.
Click to expand...
Click to collapse
First, I am using the TWRP recovery and not the CMW, as I just wanted the touch...
The steps that I took were just, in TWRP choose both the update file and the gapps file and let it install both. Then I cleared the cache and dalvik cache, and rebooted. I usually wait until it settles down after the initial boot and then reboot.
So, in CMW, I guess that would be ( they way I used to do it in CMW anyway ):
1) Reboot into CMW
1a) When in doubt, do a backup
2) Install System update
3) Install Gapps ( 4.3 version latest that I used was the 20130813 )
4) Clear/wipe cache and dalvik cache
5) Reboot into Android and wait til it stops fiddling with itself
6) Reboot again
It is the method I have used since my Acer A500 days...
SU Still Mishandling Environment
Even with the SuperSU package linked in the first post, I'm still having issues with SU misbehaving in terms of how environmental variables are handled. In 10.1 I can pass pretty much whatever I want into the su session, and it behaves quite similarly to su running on a linux desktop. In 10.2, I can't pass anything, even with the --preserve-environment flag (which shouldn't even be necessary, since I'm not using -l.) SuperSU doesn't seem to improve the situation much, except for making su usable in the shell again. Has anyone else noticed this, or am I in the minority of people that wants to pass things like PATH and ZDOTDIR into my su session? Is this a security feature of Android 4.3, or just a quirk with SU at this point?
I've tried some test cases to illustrate this behavior:
CM 10.1 20130813
Code:
[[email protected] /]% su -v
13 com.android.settings
[[email protected] /]% export TESTVAR=1234
[[email protected] /]% su
[[email protected] /]# echo $TESTVAR
1234
CM 10.2 20130815 w/ SuperSU linked in OP
Code:
[email protected]:/ $ su -v
1.51:SUPERSU
[email protected]:/ $ export TESTVAR=12345
[email protected]:/ $ su
[email protected]:/ # echo $TESTVAR
[email protected]:/ # exit
3|[email protected]:/ $ su --preserve-environment
[email protected]:/ # echo $TESTAR
CM 10.2 20130815 without SuperSU had the same result, but had really broken output.
CM 10.2 20130817 has the same behavior as the previous nightly.