Hi All,
Am I the only one that has to add the following files to the System/framework & system etc/permissions folders each time an update is applied?
com.google.android.maps.jar
com.google.android.maps.xml
************************************************** ************************************************** *************
Battery life & Performance
I have to say that all upates since 10/4 has seen a dramatic increase in battery usage when using the simplist app on the phone to the point that I can actually see the battery indicator dropping. There also is some serious lag as well overall as well. I've tried overclocking to 1200, setting to 1100. Governors set to Interactive at the moment but I've tried them all. I also tried a full system wipte, format the SD card as well but still see the same issue.
Anyone else having this, did have this & what was the fix (if any)?
I am not sure what MOD you meant, but when it comes to mods like CM9 or CM10, they are pretty demanding. What I always do to save my battery:
- keep number working widgets minimized as low as it's possible
- set the 2g instead of 3g
- I use a profile application to enter the flight mode during night
- set WIFI policy to never
I hope that helps somehow.
Related
i've figured out the best settings without the supercharger. supercharger may allow multitasking but it makes the system crawl, barely any apps go to cache, app launches are slow etc, AND IT EATS BATTERY LIKE A CANNIBAL on it-self on the ICS beta roms.
what i have done to get incredibly smooth operation is by that i have changed a few and added a few more lines to my build.prop
1) change/add the dalvik.vm.heapsize to 96m from 64m (for lesser multitaskig but smoother apps - i get two apps to multitask with this) or reduce to 48m for more multitasking (i am getting 3 apps multitasking with this 2do, officesuite N email).
2) add MAX_HIDDEN_APPS=1 and MAX_ACTIVITIES=6 (this seems to prevent multiple apps for trying to access the memory and the cpu power at the same time, giving you a better experience, i haven't had any problems with notifications for my facebook, email, pulse n whatsapp)
3) delete the 99supercharger* script from your system/etc/init.d folder
4) i am using the supercharger's bulletproof apps thing for my phone, aNag, phone dialer (option 17) get the ICS services.jar from http://forum.xda-developers.com/show....php?t=1533044 (apparantly its needed to make ICS understand OOM adjustments.
5) go to cwm to clear the dalvik cache or just do superclean-restart with the supercharger script (option 30)
btw, you have to use the DoomLoRD's advanced stock kernel with the stock wifi modules - the doomkernel v4 is superbuggy and unstable. the stock kernel itself doesnt have init.d support for the bulletproofing so you'll need the advanced stock kernel
UPDATE : 5.5) force GPU rendering under developer options in settings.
UPDATE : 6) also add 3 more things via rom toolbox's kernel tweaks for faster launches : vfs_cache_pressure=10 dirty_background_ratio=60 dirty_ratio=95 (i got this from kickasskernelizer) n make em load on reboot. also in kernel tweaks under advanced change up threshold to 75 (higher battery but slower initiations) or 30 (super fast scaling, but lower battery) sampling rate to 200000, powersave bias to 30 (make this 0 for supersmooth, or 60 for more battery life) and i/o scheduler to noop.
UPDATE 7) if you want better multitasking (albeit lesser smooth) apply the superharger OOM+bulletproof launcher settings N lower the screen updates (**** i forgot its name) thing from 200 to 120 (supercharger changes it to 200, which causes lags n a hyper accelerated scrolling)
(I had posted this under JJ's rom, but since its applicable to all ICS beta based roms (out of which i find jj's rom to be the leanest n the meanest) I am posting this here to see what others say about it. also, try his Fold Animations w/buttons (if you like buttons, albeit with a smaller screen area) or my favorite Twister animations.
p.s. devs, please suggest other pros n cons of doing the above.
please press thanks if you like this
I'll try this too.
Thanks
Thanks for the info this weekend I test these things if I can. Looks nice
ok, nothing seemed to be making the touchscreen responsive with the ICS beta n its derivatives.
except one thing just did.
i changed the sampling rate from 200000(2 lak) to 20000 (20 hazar), n of course i had to change the up-threshold so i changed that to 95 (i did all these in rom-toolbox's kernel tweaks settings)
now everything is super-responsive (app startups, physical buttons, onscreen buttons, switching, yo name it) N while you are just lets say reading stuff on the screen, the cpu is generally at its lowest
what that means is : both responsiveness and higher battery.
please comment.
UPDATE : check the 7th post on this forum for more tweaks for snappy app launching n switching here http://forum.xda-developers.com/showthread.php?t=1570374#post24186676
UPDATE : ADDITIONAL TWEAK (more battery life) : in rom-toolbox change powersave bias to 35 (in rom toolbox) : saves a lot more battery by preventing the cpu from rushing to full-frequency while you are doing simple tasks like flicking the screen.
UPDATE : 3/31/12 : an interesting observation about "force gpu" 's causing poor performance on my post here : http://forum.xda-developers.com/showthread.php?t=1570374&page=2#post24266342
UPDATE : 4/7/12 : want even more battery life n smoothness?
add these to your build.prop save , reboot into recovery, clean dalvik-cache and /cache partition then reboot into system. things should be faster. and oh, underclock it.
ro.kernel.android.checkjni=0
dalvik.vm.execution-mode=int:jit
ro.ril.disable.power.collapse=0
ro.mot.buttonlight.timeout=1
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
you can also do a semi-odex using titanium backup's integrate system dalvik into rom thing, but then you won't be able to change any file in the rom (like applying patches, mods etc until you've either done undo integration thing in titanium backup or just used adb shell to delete *.odex from /system/apps n rebooted)
UPDATE : 4/28/12 : if you are using a derivative of the .562 ICS then you can change the kernel tweaks/sysctl settings to dirty_ratio = 80 dirty_background_ratio = 20 and vfs_cache_pressure = 20 to get snappy app startups up_threshold and powersave_bias can both be set to 90 and select ignore_nice_load. if you use lots of apps then raise the dirty background ratio and dirty ratio both by 15 points and reduce vfs_cache_pressure by 15 for low cpu usage while the apps are running. i've noticed that many of the custom roms have started getting my tweaks or similars preincluded , plus the official ics is much better than icsbeta in memory management. and oh, use arcknight kernel. its super awesome for both features and battery life. i switch my governor to interactivex or smartassv2 when i am recording using the 14mbps camcorder mod, and then back.
the android backup & restore under person in settings should be turned off. it takes a lot of cpu, battery, data n memory. its aweful.
if this works for you, press the thanks button.
How can this be done?
Duvel999 said:
How can this be done?
Click to expand...
Click to collapse
i used rom toolbox pro, its free version is available here - https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
anything else that can edit sysctl.conf (e.g. https://play.google.com/store/apps/details?id=com.jrummy.sysctl.config and https://play.google.com/store/apps/details?id=scd.atools ) will also work.
Gonna try it
system seems to be a bit snappier
thx mate
thnx mate.
for snappy app switching i discovered another bunch of settings
in rom toolbox's kernel tweaks under performance, change min free kbytes to [CORRECTION]8192[not 8096] (or [UPDATE] 6144 - whichever one you like), dirty ratio to 95, dirty background ratio to 70 and vfs cache pressure to 5 (n of course check the apply on boot option)
let me know how you like this additional tweak
UPDATE: some observations ; high dirty ratio causes lower cpu usage n faster app-switching, low dirty background ratio causes faster app startups but uses too much cpu, vfs cache pressure above 5 or 10 causes high cpu usage n lags. (i use lots of apps)
UPDATE #2 FURTHER IMPROVEMENTS (fast all around with acceptable cpu usage, super app switching, n decently fast launcher without sacrificing cpu-speed n battery life)
Kernel Tweaks :
reduce dirty background ratio to 50
check the OOM kill allocating task (if your device crashes after this, uncheck this, it may kill the android system n android os processes as well in some cases)
Auto Memory Manager :
foreground 6
visible 8
secondary 32
hidden 40
content 48
empty 120
Thnks
[white10char]
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
perhaps kickass kernel script
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
check the 98kickasskernelizer (i'd find the respective values - especially min-free n change them in the script itself), there are two other not so popular scripts out there too that you may be using.
please share with us whatever was causing the overriding of rom toolbox's (or sysctl etc)'s settings.
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
hansip87 said:
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
Click to expand...
Click to collapse
the benchmarks dont tell you about usability. better responsiveness is due to faster cpu response to situations.
antutu's benchmark tests for continuous high performance (battery hogging w/lags) while running just one app.
my settings are for giving great experience (touch, app switching and app launching as well)
think of it as antutu being a mr. universe test, while mine are a gymnastics olympics tournament.
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
darth5zaft said:
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
Click to expand...
Click to collapse
thank you.
i just posted another slight tweak for higher battery life. its in the first post.
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
Could it be that these settings are conflicting with Supercharger?
Sent from my LT15i (Xperia arc) on KA ICSony
hootnath said:
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
Click to expand...
Click to collapse
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
estuardo4 said:
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
Click to expand...
Click to collapse
i found another interesting thing today.
the force GPU for 3d in the settings -> developer options actually uses a lot of the cpu and causes lags. i turned it off and have instead done the following
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
source : http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/ ;
now, i have changed the powersave bias in teh romtoolbox's kernel tweaks to 95 instead of {correcton}35{not]95. the cpu is spending more time @ 122mhz and deep sleep now without lags (which means more battery)
if this thing works for you, please press thanks.
I want to first thank Hashcode, Jonpry, and everyone else that has worked to get Kexec working on our phone (props for Kholk too). I decided to add some tweaks to the build prop to enhance my experience with a rom. Please note that there are no magical tweaks that would make your phone perform even better but my tweaks seem to have a positive effect on a thing here and here. My build prop is attached to the forum below. I have also included in this post what additional tweaks I've added, and what they do. If you have any good tweaks, I will add them to the list! At this moment this is CDMA only, you will have to add GSM tweaks to this build prop for those using GSM.
Code:
ro.telephony.call_ring.delay=1500
My Tweak: Originally set to 3000ms I halved to 1500.
Reason: This reduces the lag while dialing out.
Code:
wifi.supplicant_scan_interval = 180
My Tweak: The scan interval was originally set to 90. I upped it to 180.
Reason: This determines when our phones will scan for remembered access points. The higher the number, the longer the interval of scans. This is important if you often forget to turn off your wifi, like me.
Code:
ro.max.fling_velocity=11750
ro.min.fling_velocity=7500
My Tweak: Faster scrolling
Reason: Faster and Furiouser.
Code:
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
My Tweak: Disables Error checking and sending of usage data.
Reason: In the basics of computers there are 1's and 0's. 1 means on or yes and 0 means no or off, an interesting fact is that most power button symbols show a 1 inside a 0. I disabled all error checking because it would likely use a little less resources and add some stability for some apps. Some people have been reporting issues with Angry Birds and other games kicking them back to the desktop. If an app that worked before this tweak constantly does not work (after a reboot), remove the first two lines. ro.config.nocheckin just sends usage data.
Code:
persist.adb.notify=0
My Tweak: Disables notification for debugging
Reason: My phones is always set to USB debugging, I don't need to be reminded. This just disables the notification in the notification bar.
Code:
dalvik.vm.dexopt-flags=m=v,o=y
persist.sys.purgeable_assets=1
My Tweak: More aggressive but reasonable RAM management
Reason: Your phone will be less likely to think that something is still in use when it is actually not being used. This will free up more ram but it will force the phone to use a little bit more of the processer from time to time. Our phones actually have a decent processer but they lack ram. I've noticed some RAM heavy apps perform a little better after this tweak. persist.sys.purgeable_assets=1 is an option I found in CM9 roms seems to be used quite often (will remove if problems occur).
Tweaks that either do not work in ICS or do nothing at all.
Code:
Stagefright
Myth: Better media management and perfomance
Reason: While it is possible that this is true, Stagefright has been known to cause audio issues on Motorola phones. This may not be true on our ICS build but it's not needed due to the way ICS works. If you have a good reason to add it, I am willing to change my mind.
Code:
Heap sizes greater than 64
Myth: The bigger the heapsize the better, allowing apps to process faster and to improve multitasking.
Reason: Google's ICS default is 64 for devices that have 1024 ram or lower, anything higher will not do anything. Developers will never need more than 64 for their apps, unless they need to improve their coding.
Code:
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Myth: A fair amount of people believe this will make our pictures, videos, and sounds load faster, stronger, and better.
Reason: It's already there! It would be redudant
Code:
dalvik.vm.execution-mode
Myth: Enables the execution of JIT, which makes the phone faster
Reason: JIT execution is enabled by default on ICS and some people say this is useless anyways.
Code:
windowsmgr.max_events_per_sec=##
Myth: Allows for inputs such as screen touches to be read faster
Reason: Google's default setting is 90. Android maxes out at 60fps, setting max_events too high could slow down the UI making it process way to many things that it shouldn't.
Code:
Magikarp uses Splash!
Myth: Splash is a water based attack so it should be super effective against the right opponent types
Reason: It does 0 damage, and just wastes time. Teach Magikarp a TM and use it until Magikarp evolves.
-------------------------------------------------------------------TESTING----------------------------------------------------------------------------------
The following code has not fully been tested, or I know little of it's effectiveness. I am in the process of testing.
Code:
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
Supposedly this will force the system to use the GPU for 2D frames in applications and make things smoother. I'm almost positive that this is built into the rom.
-----------------------------------------------------------------Install--------------------------------------------------------------------------------
***There are three build.props. builds.prop is Stable. BuildT.prop is my test build. Try it out at your own risk! Be sure to back up your original build prop. I have added it to the post as BuildO.prop just in case you need it. XDA will not allow extension .prop so I changed it to .txt****
To install it:
I am not responsible for anything that happens to your phone, you do this at your own risk.
1. Open your root explorer
2. Navigate to the very root of your phone
3. Go to System, and copy your original build.prop somewhere else or change the extension to .bak
4. Naviate to the build.prop you downloaded and copy it
5. Navigate back to root -> system and paste
6. Rename it to build.prop
7. Reboot.
* If problems occur, you can delete it and rename or replace it with the original but a build.prop has to be in there for it to reboot!
waiting for the gsm BUILD.prop
I will be looking into a downloadable GSM build.prop. In the mean time whatever method used to get GSM working on the stock Kexec build can be used on this build prop.
Sent from my XT862 using xda premium
I made an 883 prop thread in the General section if you want.
Sent from my XT883 using xda app-developers app
After following the progress made here, I decided to make my own modded ROM.
The name was chosen because I'm a total newbie in modding and I don't expect it to be very good, but well enough at least for me.
I DON'T TAKE ANY RESPONSABILITY FOR ANY PROBLEM WITH YOUR DEVICE(S)!
ABOUT:
- Based on CoolrunnerII's CM7.2
- LauncherPro (Because Nemus started to lag)
- Increased Heap Memory size to stop Market and Wallpaper problem (now the Market can be updated)
- Replaced Music with Winamp (Beta, but stable version of Winamp to be as light as possible)
- I "borrowed" Kuskro's ideas (like quicksettings and RealCalc)
- I included Rotation Locker (to change from portrait to landscape)
- I included some lines in build.prop which improve 3G and changing to wi-fi and wi-fi connecting speed
- I gave up on CPUTuner because it caused too much lag for the small ammount of saved battery
- Bootanimation changed.. Thanks to SDogo for the X1 Bootanimation.zip
N00bDroid 1.1 Download
N00bDroid (first release) Download
HOW TO:
- Format in CWM Recovery partitions /system, /data, /cache
- Install ROM - Detailed instructions HERE
- Boot into ROM
- Once booted, make sure it won't go in standby until after next step
- Go in Settings>CyanogenMod settings>Display and deactivate everything except 0 degrees
- Go in Settings>CyanogenMod settings>Performance and check Use 16bit Transparency
- Go in Settings>CyanogenMod settings>Performance>CPU Settings>Max CPU Frequency and set any freq between 528 and 576 MHz
- Reboot in recovery
- Install the GAPPS
- Reboot
- Have fun
I will put here a list of tweaks when I will have more time
Thanks: Sp3dev, Zargloub, CoolRunnerII, Jerrytan93, Kuskro, Elibl and BrianXP7 for contributing at this project
Working:
Mainly:
-Mobile data (Voice/3G Edge/HSDPA) - Improved HSDPA to wi-fi change speed
-Wi-fi (currently it works only with WPA)
-Bluetooth (as CoolrunnerII says, if you deactivate bluetooth, the battery will drain very fast, so after using bluetooth, deactivate then reboot)
-GPS (I haven't test yet, but it should work)
-Camera - Without Auto-focus
Secondary
-Flash LED
-Coloured LEDs
-Battery life about 18 hours (with 30-40 minutes music - that took a bit - , 10-20 minutes wi-fi, 5-10 minutes voice call and some messages)
-Market can be updated
____________________________________________________________________________________________________________________
Not working/problems
- battery still drains too fast (in standby it's about 25 times more power consuming by coolrunnerII's measurements)
- Wi-fi WEP is not working
- Battery meter goes to <20% after reboot. However, it will not influence overall battery life
- Camera is not focusing
- FM Radio
- HQ videos
- Front camera
___________________________________________________________________________________________________________________
TWEAKS:
- You can use SetCPU (thread - here) to enable better control of CPU as it goes (also on project's google page):
Stability
Minimum (MHz): 19.2
Maximum (MHz): 528
Governor: ondemand
Performance
Minimum (MHz): 128
Maximum (MHz): 614.4
Governor: performance
If you have the possibilities, you can support the developer by buying the app on Google Play
- For a easier use of Rotation Locker go in Settings>CyanogenMod Settings>Input>Long-Press menu settings>Choose behaviour>Custom application then Select custom application>Application>Rotation Locker
- Also for a easier use of Advanced Task Manager go in Settings>CyanogenMod Settings>Input>Long-Press home settings Uncheck "Show Recent apps tile", check "Use custom application", Select custom application>Applications>Advanced task killer free
- You can change the lock screen into a less-laggy one by going in Settings>CyanogenMod Settings>Lockscreen>Lockscreen style>Rotary(it's my favourite)/Sliding tab/Lense
- Go in Auto Mount app and tick "Enable SD Card Auto-Mounting"
______________________________________________________________________________________________________________________
Changelog
28.11.2012 V1.1
- Changed Nemus Launcher to LauncherPro
- Changed QuickPic to Picturen Lite
- Change Maxthon Browser to Boat Browser
- Included Advanced task killer
- Included OI Flashlight
- Included AutoMount
- Edited build.prop to often search for wi-fi (CAUTION - It may drain your battery if you don't turn off wi-fi when not needed)
25.10.2012 V1
- Initial release
________________________________________________________________________________________________________________________
NOTE: I am open-minded to any improvement idea as long at it's still in my understanding limits.
Many thanks to be there with new projects.
Let me tell you that CPU Tuner works properly on ZeamDroid but on CM7.2 doesn't because of CM CPU controller. For CM7.2 the best option is not the CM CPU controller the best choice is SetCPU.
Best.
kuskro said:
Many thanks to be there with new projects.
Let me tell you that CPU Tuner only works properly on CM7.1 but on CM7.2 doesn't. For CM7.2 the best option is not the CM CPU controller the best choice is SetCPU.
Best.
Click to expand...
Click to collapse
True, but SetCPU is a paid app, so even though I can pay it, I'm not allowed to include it in my ROM
ady_95 said:
True, but SetCPU is a paid app, so even though I can pay it, I'm not allowed to include it in my ROM
Click to expand...
Click to collapse
Well, the version 2.24 is free for xda user: http://forum.xda-developers.com/showthread.php?t=505419
.
The reason why CPU tuner doesn't work is because of CM CPU controller. But CPU Tuner is the best frequency switcher for our Xperia X1.
Dear ady_95
Thanks a lot, for your nice work, could you please tell us, what is working and what is not ?!
and what about the battey life?
thnx dude !
V1.1 released (V2 will be released when we will have a major change in the build... Until that, only 1.x.y)
BrianXP7 said:
Just wanted to point out the link is broken and it's October, not September.
Here's the link ady_95 gave me via PM: http://www.fileden.com/files/2012/10/28/3361429/kovsky_signed_102812_191920.zip
Click to expand...
Click to collapse
I edited the name and about the google drive link, it's now fixed...(so please, if you can, remove the link from your post, because I don't know what's the downloads limit - or if there is one) also, the DL speed on Google Drive is bigger
Well, guys, it seems the base ROM and the kernels had not changed in the last weeks so until an update comes I retire and go back to WM because my camera is f**ked up and my X1 is the only replacement, I have to manage a high-school radio (from everywhere) and also I have semestrial tests in the next 2 weeks.
I will still follow the forum and when a major update will come, expect for me
See ya!
Hi, this ROM works great for me, very good performance, but after awhile it's not letting me make any calls. Whenever y try to call someone it just shows in red "Call Ended 0:00".
Wish I could go back to windows mobile as well, as I love using my X1, but I wouldnt use it if i did, as there's no Whatsapp or decent gtalk app on windows mobile.
Anyway, thanks for the ROM, great work.
I using QVOD to download movie and the speed consistent 400kb/s - 450kb/s, however, i multitasking to another application, the speed will drop to 100 - 200kb/s immediately. After I switch back to QVOD, download speed increase back to 400-500kb/s
Question: Is there any setting to restrict the performance when running background? Please assist to figure out.