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.
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 just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". I can force close it, wait, or access the power menu. But, the screen is black, and I can't do anything. This is after a day full of reflashing and wiping because the damn device couldn't receive text messages.
xzillerationer said:
I just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". I can force close it, wait, or access the power menu. But, the screen is black, and I can't do anything. This is after a day full of reflashing and wiping because the damn device couldn't receive text messages.
Click to expand...
Click to collapse
If you have a backup try restoring
Sent from my DROID2
How? I'm trying to follow the guides, but whereever I go, the SBF zip is corrupted.
It appears to be working now. I think I'll hold off tinkering with it for a little while. I still would like to know why it did this, though. For now, I'll just restore my apps, but only the ones I use all the time,
xzillerationer said:
It appears to be working now. I think I'll hold off tinkering with it for a little while. I still would like to know why it did this, though. For now, I'll just restore my apps, but only the ones I use all the time,
Click to expand...
Click to collapse
Did you happen to delete any system apps when you were customizing? You might have deleted an app that settings was dependent on by accident, which could cause something like that.
ALWAYS do a nandroid backup before you start tinkering with the phone, it will save a lot of trouble.
Heres how to do it:
1. Boot into clockworkmod recovery using Koush's Bootstrap Recovery
2. Select Mounts and Storage, and mount /system and /data
3. Return to the main menu and select Backup and Restore
4. Select backup and let it work.
5. When its done, return to main menu, and choose to reboot.
Now you can tinker however you want. If you happen to mess something up, return to clockworkmod recovery (hint: if you can't get the phone to boot properly, boot the phone, and pull the battery when you see the M logo. Replace the battery and it should take you to clockworkmod)
1. Boot into recovery
2. Mount your /system and /data again
3. Go back and select Backup and Restore
4. Select restore, and select you restore file (should be the only one if you've only done 1 backup)
5. Let it work, then reboot the phone, and your phone will be in the exact same state as it was when you did the backup.
If you can't get into clockwork, you'll need to SBF.
SBF guide:
http://forum.xda-developers.com/showthread.php?t=770224
SBF Download (download in guide doesn't work):
hxxp://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html (replace xx with tt)
Hope this helps!
Thanks, that'll really come in useful. The reason I couldn't fix it before is because Moto sucks, and encrypted the bootloader, so I was having a problem getting back into Clockwork. Did I say thanks? Oh well. Thanks.
Sent from my DROID2 using XDA Premium App
Yeah moto does suck for that. They are giving options on future devices to lock and unlock the bootloader though (like the xoom) so at least they are making progress. Doesn't help us though...
xzillerationer said:
I just installed the latest version of Apex, did a few customizations, then rebooted because I changed the LCD Density. Now, whenever I boot, it says "Process System is not responding". [... ]
Click to expand...
Click to collapse
Are you using Droid 2 Overclock? I'm asking because it allows setting screen density. I found that the new startup scripts added to Apex 1.4.1 don't play well with OC settings that were fine on Apex 1.3. The scripts add sysctl and CPU tweaks.
I set my OC settings to more conservative settings, and it has been far more stable. This isn't a knock against either product. Both work fine together with a bit of work.
Fab did release a test release (1.4.2 seems to be the informal name) that doesn't launch his new startup scripts automatically, and that's what I'm currently running.
- Bob
bobstro said:
Are you using Droid 2 Overclock? I'm asking because it allows setting screen density. I found that the new startup scripts added to Apex 1.4.1 don't play well with OC settings that were fine on Apex 1.3. The scripts add sysctl and CPU tweaks.
I set my OC settings to more conservative settings, and it has been far more stable. This isn't a knock against either product. Both work fine together with a bit of work.
Fab did release a test release (1.4.2 seems to be the informal name) that doesn't launch his new startup scripts automatically, and that's what I'm currently running.
- Bob
Click to expand...
Click to collapse
Aye, I am. It seems fine most of the time for me. However, I've only been running for a few days, and have barely rebooted.
Sent from my DROID2 using XDA Premium App
I am had luck with 1.4.2 by setting my OC values to defaults before doing my pre-flash backup with Titanium Backup. After flashing, I was able to restore everything, including OC (default) values.
I also disabled the CPU tweaks Apex puts in /etc/init.d scripts, and and re-run QuickClock Advanced to recalculate my clock and voltage settings and imported those into Droid 2 Overclock.
So far (5 hours), it's been solid. If you don't want these issues, stick to Apex 1.4.0 for now. It was very stable.
- Bob
Since there's been some interest in comparing the 2.2 ROMs with the 2.1, here are some stock eclair nandroid images based on the Cincinnati Bell 2.1 ROM that can be used in OpenRecovery without flashing SBFs. You can use these to switch between 2.1 and other 2.2 ROMs without bothering with RSD Lite/sbf_flash.
Of course gallery key, camera and FM radio work well on these. Although, I've been having market problems (paid apps fail to download). Hopefully that will resolve itself if/when market decides to self-update... In the interim, I recommend using something like Titanium Backup to migrate your paid apps.
Eclair Strikes Back v2 (2011.06.23)
This is a tweaked version of CBW_eclair_STR_U2_04_1E_1.zip with some tricks we've been using in 2.2 (expanded apns-conf.xml, JIT from FrozenEclair, memhack to move dalvik-cache to /cache, egl.cfg hack to disable software rendering).
eclair-strikes-back-v2-beta.zip (the beta is now final )
Changes since v1:
ext-partition support compatible with the stock221-derived ROMs*
Automatic swap support for fjfalcon's fastboot kernel
Automatic support for link2sd (either FAT extra partition or stock221's /sd-ext/link2sd method)
Additional cpu governors (conservative, interactive)
Market upgraded to 2.2.7
*dalvik-cache on /sd-ext is not supported by default on this ROM.
Previous release: Eclair Strikes Back v1
eclair-strikes-back.zip
2011-06-16 Update to fix market on ESB v1 (upgrades market to 2.2.7)
Stock 2.1 (Cincinnati Bell)
This is a rooted version of Cincinnati Bell's STR_U2_04.1E.1 with OpenRecovery support pre-installed.
CBW_eclair_STR_U2_04_1E_1.zip
Hey Mioze do you have the app2ext script that is in the Bluesteel rom? Might try your eclair nands with it and see what i get.
I've finally successfully downloaded and installed a paid app from the market now on Eclair Strikes Back. Market is still old one though... not sure why it's taking so long to update to new one. When I did a factory reset on stock 2.1 soon after I bought the phone the market updated itself pretty quickly IIRC.
Still, this feels so smooth and fast....
EDIT:
And don't seem to be having downloading issues with any apps, be it paid or free anymore. Maybe you'll have to manually replace the market.apk with the new one though, since I'm not sure it's ever going to self-update.
syrenz said:
I've finally successfully downloaded and installed a paid app from the market now on Eclair Strikes Back. Market is still old one though... not sure why it's taking so long to update to new one. When I did a factory reset on stock 2.1 soon after I bought the phone the market updated itself pretty quickly IIRC.
Still, this feels so smooth and fast....
EDIT:
And don't seem to be having downloading issues with any apps, be it paid or free anymore. Maybe you'll have to manually replace the market.apk with the new one though, since I'm not sure it's ever going to self-update.
Click to expand...
Click to collapse
And what about moving applications to the sd? available or will be applied app2sd?. Open recovery will still work? I have some applications that are supported only from 2.2, they can no longer be installed .... of course there will have to sacrifice something.
I at the continuing problems of delay in opening and closing apps, malfunction of the camera, out of trouble and delay an application to load the launcher and would return to around 2.1, but I also like the space for application installation and open recovery.
PS: It's easy to return to 2.1?
download on process
kinda miss the haptic feedback hahaha..
thx a lot Mioze..
I'm pretty sure you can only move apps to SD for 2.2... since I never used it (I never have so many apps installed at once that it's neccesary) I don't mind losing that functionality.
There are a few apps from 2.2 that I like, most notably the new gmail and youtube apps, but those are minor sacrifices for me really.
Open recovery is installed in both those links. I find the camera works much better on 2.1, seems much faster in taking and processing pictures.
In any case, it is indeed very easy to return to 2.1 and then return back to a 2.2 ROM if you don't like it. You take one of those links (I'm using eclair strikes back) and flash it through nandroid just as you would any other ROM that we have here. And you can flash back the same way if you don't like it.
Be advised, there are currently some issues around the android market for some reason (just see the posts above)... I'm thinking we might have to replace the market apk.
Anyways, I personally am loving it.
EDIT:
Oh, you might have to setup the APN's as well.
Tavinsky said:
And what about moving applications to the sd? available or will be applied app2sd?. Open recovery will still work? I have some applications that are supported only from 2.2, they can no longer be installed .... of course there will have to sacrifice something.
I at the continuing problems of delay in opening and closing apps, malfunction of the camera, out of trouble and delay an application to load the launcher and would return to around 2.1, but I also like the space for application installation and open recovery.
PS: It's easy to return to 2.1?
Click to expand...
Click to collapse
I intend to make an updated eclair-strikes-back to add app2ext support and additional governors but I probably won't have time until later in the week. I view link2sd as the eclair equivalent of froyo's native app2sd, though. Link2sd may already work with fat as the second partition, but I haven't tested it yet because of the market problem. The market problem is #1 on my list when I get time.
And yes, these 2.1 ROMs will keep OpenRecovery intact and you can just flash between 2.1 and 2.2 ROMs the same way you would switch between 2.2 ROMs.
Thanks for the work Mioze7Ae! Let's try it, you know, always gives a bit of fear making a mistake, but gradually removes the fear. I do not know that flashing. It's like applying an Update? I apply a copy nandroid?
Tavinsky said:
Thanks for the work Mioze7Ae! Let's try it, you know, always gives a bit of fear making a mistake, but gradually removes the fear. I do not know that flashing. It's like applying an Update? I apply a copy nandroid?
Click to expand...
Click to collapse
I know how you feel. I always used to have fear/apprehension when flashing a ROM. I've done it enough times now that it's all gone by now though.
Anyways:
Download the ROM. Unzip it. Copy and paste the folder (should contain 4 things in it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've gone to a 2.2 ROM you should see that ROM in the same place where you're putting this). Anyways, launch open recovery and do recovery boot or hold volume up while pressing power on (if your phone is off). If you get an image and nothing happens, you may have to go into open recovery and select install recovery system before doing this - if you have a bunch of weird pictures in your gallery including Darth Maul then you don't have to worry about this. Then navigate - using the volume keys to move up and down and the camera button to select - to Nandroid, select restore, select Eclair strikes back, select restore all. Once that's done, make sure to wipe data/factory reset and then wipe/clear dalvik cache and cache. Then reboot and it should work. (First reboots are long).
You may have to setup your APN's also.
Excellent. Thanks, sounds simple ... downloading ..... then tell how it worked.
syrenz said:
it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've
Click to expand...
Click to collapse
They actually go in nandroid/openrecovery/, it's the updates.zip that go in OpenRecovery/updates/ so it's easy to remember that wrong. I'm always adb push'ing to them so I only noticed the mistake because I've got the muscle memory from typing them all the time. Gotta love the consistency
hey mioze7ae, using it right now btw, is it possible to change the read_ahead settings to 2048 instead of 128? i can manually replace the file but once reboot, it changes back.
thanks!
Manual market update
I replaced /system/app/Vending.apk with the 2.2.7 com.android.vending.apk found here:
http://forum.xda-developers.com/showthread.php?t=875067
After doing this and rebuilding dalvik-cache I have the new market and I am able to install paid apps! I'll make an update for it tomorrow, I have to crash.
Two things you can get from market before you flash. APN backup/ restore and SD speed Increase. You can backup your APNs and then once you get to the eclairs, restore them. SD Speed Increase will kick up your SD cache to 2048, instead of 128. Both are free.
Woodrube said:
Two things you can get from market before you flash. APN backup/ restore
Click to expand...
Click to collapse
Much appreciated... Didn't know there was such an app and it's a pain to re-enter all that stuff...
syrenz said:
I know how you feel. I always used to have fear/apprehension when flashing a ROM. I've done it enough times now that it's all gone by now though.
Anyways:
Download the ROM. Unzip it. Copy and paste the folder (should contain 4 things in it boot.img etc...) into your SD card under OpenRecovery/Nandroid/ (if you've gone to a 2.2 ROM you should see that ROM in the same place where you're putting this). Anyways, launch open recovery and do recovery boot or hold volume up while pressing power on (if your phone is off). If you get an image and nothing happens, you may have to go into open recovery and select install recovery system before doing this - if you have a bunch of weird pictures in your gallery including Darth Maul then you don't have to worry about this. Then navigate - using the volume keys to move up and down and the camera button to select - to Nandroid, select restore, select Eclair strikes back, select restore all. Once that's done, make sure to wipe data/factory reset and then wipe/clear dalvik cache and cache. Then reboot and it should work. (First reboots are long).
You may have to setup your APN's also.
Click to expand...
Click to collapse
I just want to check; is it completely safe to remove those wierd pics in the gallery?
androidlover123 said:
I just want to check; is it completely safe to remove those wierd pics in the gallery?
Click to expand...
Click to collapse
Yes. But if you have to use open recovery for whatever reason, you'll need them. You can either click install recovery as needed (which creates the pics) and delete them after, or the best thing to do is get an app that just hides the pics from gallery - so they are there when you need them, but don't interfere. I saw an app "Gallery Excluder" or something floating around in the XDA Android Apps section - that would work. Or a gallery like QuickPic let's you hide things as well.
EDIT:
Nevermind, Gallery Excluder hides folders only. There are other apps though, I believe.
Just an update on progress with ESB
I've done some testing and Link2SD already works with the released eclair-strikes-back but currently only when using FAT for the second partition.
To get ext support in, I'm trying to get the darktremor a2sd scripts to work. They look high quality and robust and should handle swap gracefully when booting the custom kernel as well (current status--some rare hung boots with a flaky SD card when using the latest beta scripts, will try the stable release next). There's also a GUI in the market for managing the SD card (currently only Froyo+, I'm inquiring whether the developer can add eclair support).
Mioze7Ae said:
Just an update on progress with ESB
I've done some testing and Link2SD already works with the released eclair-strikes-back but currently only when using FAT for the second partition.
To get ext support in, I'm trying to get the darktremor a2sd scripts to work. They look high quality and robust and should handle swap gracefully when booting the custom kernel as well (current status--some rare hung boots with a flaky SD card when using the latest beta scripts, will try the stable release next). There's also a GUI in the market for managing the SD card (currently only Froyo+, I'm inquiring whether the developer can add eclair support).
Click to expand...
Click to collapse
I am hoping that the ext will come through. If I am using the sd-ext/app folder on the Steelblue ROM, can I leave all my apps in there and flash your eclair with ext support (when ready) or will I have to use Titanium-migrate? I would think that it really wouldn't matter for most of the apps, except FroYo specific ones like Flash 10.3 but not sure.
p.s. Are you going to call your next version "Return of the Eclair"?
MD5 Check failed. Does this have something to do with the fact that I bought my phone in the middle east?
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.
I found something that has greatly improved my game performance that I thought I'd share with y'all. I have tried a lot of scripts over a lot of devices, and this one really make a difference, in both benchmarks and games and everyday uses. I did not make this and will not benefit from you using it, I just want to help people out who would like better performance. I have tried this on a couple of sense roms with the elemental x kernel. I have not tested on gpe or aosp. Make sure you have your rom set up and have booted into it at least once with your choice of kernel. Do not install a custom kernel after this or it will override some of the settings. It does break root, so you will need to flash superuser or super su from recovery after you have flashed this and booted your phone. Enough talk, go here and get comadose http://forum.xda-developers.com/showthread.php?t=2419255
[MOD][TWEAK-PACK][8-24-13][S4][i9500] ComaDose The Best, By The Best
Has anyone tried it?
UI performance, apps loading time and overall responsiveness are amazing, but games lag a lot
EDIT: Use only these 4 scripts (extract from zip, put into init.d, set permissions)
16_sqlite3 (you'll need sqlite binary from zip)
70B2R
KB_read_ahead_tweaks
S02_direct_inject
For entropy use Entropy Fixer free app (my settings: read 1024, write 2048)
That's funny, game lag went down with me significantly, everything else improved for me also. He used crossbreeder for entropy in his script, I'll give you suggestions a try also though.
I just flash the zip or what ? + use which one crossbreeder or normal one ?
Nightf0x_007 said:
I just flash the zip or what ? + use which one crossbreeder or normal one ?
Click to expand...
Click to collapse
Flash the latest zip, it's 3. Something I believe. Is the first one you come across, not the one that says crossbreeder. Wipe cache and dalvik, make sure you have the kernel you want installed, mount system and data, then flash comadose. Reboot, let it settle, go back into recovery, flash the latest super su zip, reboot, done.
Honestly... I dont play a lot on my HTC One, but Ive never experienced any laggs issues. I find this phone the most powerful device Ive ever had.
Play the new gangstar Vegas and rio games, turn graphics so the way up on GTA San Andreas, some drifting games, you'll see. I agree, it if the fastest I've owned but now there are faster and software is evolving to stay with the new hardware.