Things to get sense 3.5 running smoother - HD2 Android Q&A, Help & Troubleshooting and Genera

Just trying my best to help out! These are the things i do to improve performance on my hd2 (tmous) running sense 3.5. Some of these are risky so read before applying
1. Swap.
There is much of debate about using swap on your android device,some say its useless and it wears down the sd card and others say it speeds up your device on a notable level. What i've noticed is that swap behaves according to what else is using the sd on android at the time, remember that android is also accessing the fat32 and your ext4 partitions. Right now im not using my ext4 partition on my sd and and i can notice the little boost from swap , and on the previous rom which ext4 was needed, using swap would more show up on benchmark than actually being experienced.
HOW TO GET SWAP WORKING. Its very easy on the sense 3.5 roms!!!! Just partition your sd using recovery in magldr, download script manager from the market and download swap-hard.sh from Dorimanx's high performance rom.
in script manager go to where u downloaded the script and run it (run as root and run at boot). Thats it!
2. VM heap size.
i set mine to 96m ,using blade buddy from the market. In advanced settings edit the value in dalvik.vm.heapsize press menu save and restart.(dont overdo it 96 already is.
3. Overclock. I just overclock to 1.382Ghz max 576 min with the performance governor. (please read about the dangers of overclocking your hd2 before choosing to do so.)
4. v6 supercharger. Search for it, read the thread!!! use and enjoy!
5. Reduce system traffic. As wonderful as the hd2 is we need to remember that it has its limits no matter the os u put on it (lack of speed, heating up, speedy discharges ect). this is all due to what im calling system traffic, the autosync every 10 minutes, the running 10 apps you dont need just because, things like that. These things unbalance the performance vs the productivity. Set the auto sync to an hour or take it off . close apps when u r done with them. Clean up the temp files regularly (caches ect).
6.Flash the newest radio Leo_RADIO_2.15.50.14
This is it for now if u got anything else to help then please reply as these things can help any rom , also u shall take full responsibility for any future damage to your phone or phones hardware (nothing to be scared about but im putting it up incase.) And it would be great to get a dev's opinion on this and to also correct or guide people to better settings.
i would love to post a video but i have a dell streak 7 and the vid recording is horrid!!! but the average quadrant is in the 1200s.

Related

multitouch

i rooted, and installed cyanogenmod 4.0.4 or whatever the stable release for 32b is.
i want multitouch, can i just flash something onto it withtout wiping?
Go experimental.
His latest ROM build has the multi-touch browser installed. TONS of additional features built into the browser. (Thanks to Loccy)
You can find that download at his website or download his application in the Android Marketplace called, "CyanogenMOD Updater." That will allow you to download his ROM over-the-air.
As for full-on MULTI-TOUCH, he is working on that as far as I know. Cyanogen is always eager and waiting (ready) for when Google drops more code.
btw, have you noticed any change in battery life with cyanogen vs tmobile rom? i havent had a chance to test it since ive been downloading my apps all day.
and how is apps/cache2sd do you notice any change in speed?
Not noticed, if at all.
kchau said:
btw, have you noticed any change in battery life with cyanogen vs tmobile rom? i havent had a chance to test it since ive been downloading my apps all day.
and how is apps/cache2sd do you notice any change in speed?
Click to expand...
Click to collapse
Take a look at my sig.
I'm running the latest build from Cyanogen...his ROM is naturally overclocked @ 528MHz (correct me if I'm wrong) so it's quite fast. That can take a toll on overall battery life, depending on your average daily use. I adjust the CPU usage with an application known as, "Overclock Widget." If you would like to utilize minimal battery life - then I suggest you adjust the MHz to a lesser value.
WARNING: Altering those settings incorrectly or at an inappropriate time can crash your phone immediately upon CPU changes!
As for the Cache2SD and Apps2SD, that's automatic within his builds...for the most part. I still utilize an application called, "Move Cache for Root Users." Which, for the record can be downloaded from the Marketplace, free of charge. That will simply create a cache folder on your SD card to spare room on your device's internal memory capacity. It's great!
Reignzone said:
Take a look at my sig.
I'm running the latest build from Cyanogen...his ROM is naturally overclocked @ 528MHz (correct me if I'm wrong) so it's quite fast. That can take a toll on overall battery life, depending on your average daily use. I adjust the CPU usage with an application known as, "Overclock Widget." If you would like to utilize minimal battery life - then I suggest you adjust the MHz to a lesser value.
WARNING: Altering those settings incorrectly or at an inappropriate time can crash your phone immediately upon CPU changes!
As for the Cache2SD and Apps2SD, that's automatic within his builds...for the most part. I still utilize an application called, "Move Cache for Root Users." Which, for the record can be downloaded from the Marketplace, free of charge. That will simply create a cache folder on your SD card to spare room on your device's internal memory capacity. It's great!
Click to expand...
Click to collapse
oh, is his rom not dynamically overclocking? its always at 528?
the wiki says that the htc magic is a 528mhz cpu.. could you elaborate?

Just want my 32B to be as fast as possible. What to do?

So, I'm running Cyanogenmod 4.2.15.1 but I always think it's a bit slow. Maybe it's all the widgets, installed apps or often having mp3's playing in the background but I can't help thinking that the original ROM was much faster.
What can I do to improve speed?
I'm running TasKiller but that alone doesn't really speed things up enough.
For music, I'm using Meridian player, but perhaps there's a faster player out there?
Is it worth installing any of the 2.1 ROMs or should I wait for the official release or is that even likely to be slower than Cyanogenmod?
A couple of things you can do. You can use an application called setCPU which is for root users. It allows you to modify how the phone is run e.g. it can run from 128MHz to 528MHz depending on your preference. 528 will give you the highest performance. There is a min and max for them, and I have 384 to 528 usually.
Instead of taskiller, I use advanced task manager. Kill some processes as well. I like it better at least.
My recommendation is use superD or FastTest. They are, in my opinion, the fastest ROMs out there. A lot of Eclair ROMs are stable as well, but not as fast as the donut ROMs.
Thanks.
I've always thought that setCPU didn't make a difference, cause it's Magic is already running at max CPU in most ROMs. If not, how come it's mentioned so rarely around here? Surely it should be one of the most popular apps?
I've never heard of Super D or FastTest til you mentioned them. Might be worth a shot, although I'll have to admit I'd prefer not changing ROM all the time. When I first got the phone I tried loads of Sense ROMs but they all seemed either unstable or slow, or both. I think I'll read up a bit more on SuperD before having a go.
dont really have any other info on your setup except its a 32B....why not give us some more info in your signature, like:
what size and class SD card you have
whether you have swap enabled
whether you have compcache enabled
whether your sdcard is partitioned, and how
IMHO u dont need setcpu, its already written in to CM for the cpu to be 528-384
you could try:
JIT http://forum.xda-developers.com/showthread.php?t=637419
the swap userinit.sh http://forum.xda-developers.com/showpost.php?p=5342507&postcount=577
and the lowmemory killer minfree approach (which i prefer instead of "task-killers" which are just another app running) http://forum.xda-developers.com/showthread.php?t=622666
and of course, the all important 10 MB RAM Hack http://www.absolutelyandroid.com/10mb-ram-hack-for-cyanogenmod-version-4-2-15/
CM should be nice and fast for you on a 32B, best one I've found so far
"what size and class SD card you have
whether you have swap enabled
whether you have compcache enabled
whether your sdcard is partitioned, and how"
SD card is class 4, 8 GB I think.
Yes, swap enabled. Can't remember the exact details regarding how the SD is partioned. Anyway to check that?
Don't think I've got compcache enabled. As a matter of fact, I've never heard that term before.
That 10 MB hack sounds interesting. I'll give that a shot.
I actually use setCPU profiles to save battery as well. When the screen is turned off, I have it set for almost minimum.
SuperD and FastTest have 10MB RAM hack versions so you don't need to install it on your own I don't thnk JIT hack is necessary for these ROMs anyways.
Armadillo123 said:
So, I'm running Cyanogenmod 4.2.15.1 but I always think it's a bit slow. Maybe it's all the widgets, installed apps or often having mp3's playing in the background but I can't help thinking that the original ROM was much faster.
What can I do to improve speed?
I'm running TasKiller but that alone doesn't really speed things up enough.
For music, I'm using Meridian player, but perhaps there's a faster player out there?
Is it worth installing any of the 2.1 ROMs or should I wait for the official release or is that even likely to be slower than Cyanogenmod?
Click to expand...
Click to collapse
I got this just do as I do on my magic
Cyanogen is good for tons of features & I respect Steve (the ROM developer) for the ROM but for full speed & stability on a 32B Magic I suggest going by my signature as a guide.
I'm using Meridian player also & find it the best but Mixzing or Tunewiki is faster Mixzing has a little more then Tunewiki though but Meridian player is the best overall for the features.
OK in regards to ROMS, flash a new one all this talk of setcpu & stuff merely provides a quick fix but doesn't help in the long run (at least in my experience on a 32B Magic).
In fact here...
Download Dwang 1.17.1 - http://forum.xda-developers.com/showthread.php?t=567023
Add style & download Pays Black Elegance Theme 1.1 http://forum.xda-developers.com/showthread.php?t=608412
Backup your apps & stuff & do a nandroid just to be safe.
Now proceed to enter recovery like your about to flash a ROM (as soon you will be ) wipe all that can be wiped (use Amon_RA Recovery for that) & flash Dwang like you did Cyanogen
Load it up (first start up is the longest), set up & when you hit the home screen power off your Magic & then switch it on into recovery like you are gonna flash a ROM (there it is again).
Flash Pays Black Elegance 1.1 Theme (NO WIPE!!) just flash over Dwang once that is done reboot & then try it for a week & report back here with your verdict
This is what I'm using & have been for over 2months now & I don't see me switching anytime soon as I can't find anything that is éclair that is like this ROM.
YES its 1.6 but it is super sweet for a 1.6 & personally for me it beats those 2.1 ROMs (which are good don't get me wrong but they ain't no Dwang)
ROM Stats
121 Apps installed
15-25sec wait on home screen load at times but not always & that is only cause I use like 12 widgets & filled 4 of the 5 screens with icons to applications.
10MB Hack is on this so 3D Games are a little laggy otherwise overall the best ROM i have used & only 1 random reboot but I kinda caused that running a whole heap of stuff like 30 processes at once haha.
Anyway let me know your verdict I hope my tip helps!
From my experience, super d 1.10.2 was, by far the fastest rom i've ever, used i havent messed with swap or compcache, but super d truly gave me that wow factor when it came to my phone, only downside is that it sorta ate my battery real quick, and i changed back to 1.9.3 wesgarner kernel, which is pretty quick too ...
Use Dwang 1.17.1, buy CacheMate from Market and clear your cache weekly.
This is the fastest I can get my 32B to run. I've tried Super D and CM, they are slower in my opinion. Dwang includes 32Mb compcache by default which seems to be the sweet spot. I've never played around with swap on SD card.
I use the default music player with Pure Music Widget. I used to use some other music player with "genius-like" functionality and all that rubbish but found it to be too slow for my liking.
Make sure you do the build.prop edits for HSPA as per this thread.

[A] [NAND] ROM Space and Battery Issues

I have picked up lots of bits of information about how to maximize space issues and maximize battery life for those of us who are in love with these amazing new NAND builds....especially those of us with European HD2 phones who only have 512MB to play with
I have compiled them below for ease of reference - I claim no originiality for these ideas...I am just bringing them together...so MAJOR THANKS TO ALL THOSE OUT THERE! You know who you are...
I have already posted this on the DFT thread as I love that particular build, but they should (might!) work for other builds and I post it here for further reference as it took me a long time to sift through the threads to find it all.
Space
1. Before flashing your phone, using DFT Stock Desire, for example, you can edit the flash.cfg file and change the following line:
cache ya 40M >>to>> cache ya 15M
This reduces the cache by 25M with no discernible impact on the speed of the build (imo).
This should give you in excess of 130MB free after a clean flash on that particular ROM. Expect that to drop to around 100MB once Market, Flash and a couple of other apps update themselves.
Some NAND ROMs will not even have this as an option, and others may look a little different. You can read about how the flash.cfg file is structured here.
2. Immediate install Z4 to root your device. You will need to get it from here. (Note: it may get stuck on 'Rebooting'. Wait a minute or so and then manually reboot - it will work fine and SuperUser will now work after the reboot)
Put it on your SD card and then install a file manager from the Market to browse to it and then install and run. Follow the details on the thread...
3. Install Move2SD. You can get it from the Market. Full details are here.
This allows you to move most (not quite all) apps to SD. It is the best option I have found to move most of those awkward apps.
I have now installed pretty much all of my apps that I used to run on non-NAND builds and have moved about 90%+ of them to the SD card. At time of writing I have loads of apps installed and still have over 70MB free
Battery
1. Install Battery Monitor Widget or Current Widget from the Market so that you have a way of tracking your current usage.
2. Install Set CPU - free for XDA members from here, but also available on the Market.
After setting your Main Screen to 'OnDemand' and 'Set on Boot', assign SetCPU a couple of profiles. I tend to use:
>> Screen Off: Max/Min 245000, Scaling 'OnDemand', Priority 50%
>> Battery <25% Max 384000/Min 245000, Scaling 'OnDemand', Priority 50%
You can play to your hearts content here, but these give me consistently 7ma in Standby.
Also, you can reduced the sampling rate to 20000 and 'Set on Boot' in Advanced if you like.
3. Avoid power hungry background stuff like animated wallpapers and turn off GPS, Wireless etc. There are LOADS of apps out there that can do this automatically for you free from the market, but I have found that making sure my GPS is off (I have a widget to show me) plus SetCPU is plenty. It may work for you though.
4. Some have reported that Darkstone's suggestion makes a major difference to their power consumption:
"To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds."
Anyway, there you go - a few consolidated thoughts - happy NANDing!
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
dungphp said:
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
Click to expand...
Click to collapse
Not sure I'm afraid...have you tried it? I tried it and Z4 got stuck on the 'Rebooting' screen, but when I manually reboot it had solved it...
dungphp said:
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
Click to expand...
Click to collapse
isn't that the v0.3 itself already been rooted at the first place?
I installed Root Explorer and gotten root access immediately...
But can't check permission some folder to change themem or something !
When you do this
"To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless
networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds."
Click to expand...
Click to collapse
You will loose weather on main screen. It will say "To see local weather tap here"
SetCPU doesnt work on Nand ROM..Is there any similiar program like SetCPU for Nand ROM ?
well guys i really dont understand why everybody you complaining about nand build
well my nand build is nexus one and i get 2-3ma battery drain in standby
olso the spuset in on 1190smartass
i dont want to be a smartass guy, but please ram and rom is different
ram = random access memory
rom = read only memory
when i look at the thread title of couse i think about ram, not rom... and too much thread title have that 2 things mixed in and im sure that will make alot of people (including me) confused
btw i thank you for the info
Clubeer said:
SetCPU doesnt work on Nand ROM..Is there any similiar program like SetCPU for Nand ROM ?
Click to expand...
Click to collapse
It does for me Are you rooted?
aboveluna said:
i dont want to be a smartass guy, but please ram and rom is different
ram = random access memory
rom = read only memory
when i look at the thread title of couse i think about ram, not rom... and too much thread title have that 2 things mixed in and im sure that will make alot of people (including me) confused
btw i thank you for the info
Click to expand...
Click to collapse
You're quite right - too much 'New Year cheer' the day before I started the OP
Have changed it as you correctly point out - thanks.

[Q] Super Froyo by [email protected] on rooted G1

My apologies if my thread manners are off. Please feel free to move this post to the appropriate spot (and please reply telling me what the general rules are) if I'm posting this in the wrong place. I'm a relative noob when it comes to flashing ROMs, though I have tried about 12 in the past few weeks after I finally rooted my G1. Thus, I think XDA won't let me respond in the specific Rom forum because I haven't written enough posts (this is my first) or something.
Anyway, I have a few questions about this ROM and its settings after flashing it on my G1 last night. For clarity & redundancy, I am running "SUPERFROYO V8.4 Update 11/01/10." I downloaded and installed it last night (Sunday, April 10th, 2011- in the event there is a newer one available after I post this)
I have not installed the battery saver yet, though I plan on doing so once I figure out the answer to my more pressing question:
QUESTION SETUP:
I know the main issue that plagues the G1 is its ridiculously low internal memory, but according to the Phone storage settings page, I still seem to have roughly 8 megs of internal memory left for apps. I've moved a number of apps to the SD card, but the phone keeps telling me that my internal storage is low anyway. I never got these warnings unless I had roughly 1 meg or less left when I was running stock 1.6 Android (before and after rooting it in mid March).
ACTUAL QUESTION: Is there some setting I can tweak within the ROM, or app I can download to allot more internal memory for apps? Failing that, is there a way to change the warning threshold to more closely match stock 1.6 Android's threshold on the G1? I'm thinking that Froyo has a different idea of "low phone storage" than the stock ROM because newer phones all have assloads more memory available, and that I might be able to tweak that setting somewhere. Unfortunately, a lot of the pre-installed system management apps on this ROM are in Spanish, and it's been over a decade since I took Spanish. I could go through the menu options and attempt to translate, but I'm hesitant to delve into a new program that is ALSO in a foreign language.
Any help would be greatly appreciated. Also, I would like to thank the entire XDA community for all of their efforts and support for users. Finally, I would like to tip my hat to the unlockr community for their entry-level tutorials. Thanks again.
I think you forgot to mention this, and i dont see you have no signature with your specs, radio, boot etc...
But did you partitioned your SDcard with the correspondent EXT/SWAP/FAT32 paritions ??
Also the developer on that ROM (superatmel) doesnt give support to his ROM is if isnt within the forum where he orignaly releases his work.
Make sure you install the 15MB-boot from the DEV site. it will give you and additional 15MB.
Also, turn on Apps2SD option in the SupSetup. Then you can move apps to SD.
Depending on the size of your SD card, if you have 8GB SD, I would recommend the setting on my sig.
yeah that sounds about right.. you either didnt partition correctly or some how some way you forgot to do a wipe but still got the rom to flash, which would amaze me so i doubt it.. but i would recommend re partitioning your sd, my pref.. swap128mb ext1024mb(1g) and also do a reflash of the rom but be sure to wipe EVERYTHING and i mean everything.. it doesnt hurt to clean out the system completely every once in a while.. besides that flash the ram hack and do whatever else you normally do try keeping widgets to a minimum.. regardless wat rom it jus always helps to keep a nice clean home screen but dont be scared to make it look nice.. (contradicted myself a lil there lol) anyways good luck and happy flashing i hope this helped...
also try wiping your cache from the browser.. not sure if you surf the web alot but it builds up pretty fast try to stay on top of that lol hope it helps you out
BEST SETTINGS for Super Froyo
I did some research on compcache settings and vm heap settings so I can know what they're intended for. Upon doing so, I found it is best to disable compcache and increase vm heap to max then reboot as instructed by the rom being used. This made my super froyo run superfast compared to when the vm heap was at its default setting. Also, where Linux Swap is concerned, it is best to have a 50% swappiness and the 64mb swap partition on the sd(I actually have about 80 something mb swap, but thats just me). Maybe these settings wont work for you but they definitely worked for me. Give it a shot and see!
Current Devices
HTC Vision/G2-Virtuous Quattro beta8
Samsung Vibrant-ICS Passion v10.5
HTC Espresso/MyTouch 3G Slide-Cyanogenmod 7.1.0
Motorola Cliq/DEXT-Cyanogenmod 7.1.0
HTC Dream/G1-Super Froyo v8.4
Scratch what I said about...
...setting the vm heap to the max. Instead, set it to the lowest possible setting and that will make this rom much snappier. I've been playing around with the settings non-stop and found this to be the best. Also, what would really help this rom is to use Firerats MTD Hack and repartition the devices internal memory partitions in order to better suit the roms performance.
Current Devices
HTC Vision/G2-Virtuous Quattro beta8
Samsung Vibrant-ICS Passion v10.5
HTC Espresso/MyTouch 3G Slide-Cyanogenmod 7.1.0
Motorola Cliq/DEXT-Cyanogenmod 7.1.0
HTC Dream/G1-Super Froyo v8.4

[HowTo] Tweak your Archos

Hi,
recently i came upon a thread with someone asking :
how to optimize the archos to be quicker ?
As this is propably a question many people might ask (even I still do ) I thought about creating a thread about. This is not just to answer his question but also for all u nerds out there to corrent me - as I might be wrong in some points AND to gather new options to speed up the device. This is what i have learned yet...
Anyway all of the things I list here require root as far as I know. So get your device rooted or abandon the Thread
ALL THINGS IN THIS THREAD ARE WITHOUT WARRENTY - SO IF YOUR DEVICE STARTS MUTATING INTO A DOG HUNTING YOUR ASS FOR NEW FLESH - BE WARNED
Memory Management:
Introduction: HAVING FREE UNUSED MEMORY ON ANDROID HAS (nearly) NO ADVANTAGE (exception having 0 memory also fu**s up the device -> 1. )
All of those methods wont make your device faster in the meaning of really getting faster in speed... as android already has a quite good memory management.
BUT if u get more space in memory your device can keep more of the apps U LIKE in memory (being inactive according to app lifecycle). This will make them get called faster next time u use them and your device will "feel" faster and more responsive.
1. What should work on all roms are the "minfree" settings -> meaning when android really kills apps - depending on free memory (if u don't know what is mean by - search for the "App Lifecycle" of android)
You can try setting those to the values mentioned by sibere (scroll down) or try finding your own settings. There for u can use any app like "AutoKiller Memory Optimizer" just serach "memory optimizer" in the market.
KEEP IN MIND - you may play a bit with those settings - BUT still u should know what u are doing if u use it!
LOW: If u set the values to low the device will kill apps very late keeping much of them in memory this might make you device get slow. If there is too less Memor fo a "new" app or another process just need more memory while running it has to close down other processes before memory can be allocated.
HIGH: If u set em too high u kill most apps instantly - and your device will get problems and might get unstable as far as i understood.
2. Try gettign more "free" memory by disabeling services - as those got the highest priority they wont get killed that fast by the memory management. For checking u might get an app like "TaskManager" wich lists all running processes.
Just check out what takes your memory and disable those u dont need.U can disaable them by using "Titanium Backup" disable app / uninstall em / or just uncheck their autorun by using a programm like "Autorun Manager". Remember if u just disable the autorun they might (re)start later still.
3. Use a low sceen count in your launcher and keep the widget count low. This is related to 2.) as most widgets run a "background service" to update itself / pulling information (e.g. a waether widget getting latest conditions, a calendar widget keeping connection to your calendar app,...) - each widget took at least 8MB memory when i checked with TaskManager - "greater" widgets like "Fancy Widget (sense like clock and weather widget)" sometimes take up to 25MB
4. DONT USE A LIVE WALLPAPER (live wallpapers use MUCH memory most 20MB-40MB - either they get closed down all the time - or they just reside in memory taking the memory u wanted to use for keeping other apps active)
I also noticed that the App Drawer got "much/noticeable" slower in every Laucher I tested while a live wallpaper was active
5. DO NOT USE A TASK KILLER (remeber the introduction!!! - and think about it yourself - if at least 20 ppl ask why - i write this down here )
6. SWAP / COMPCACHE (can be activated through UD config) - this is a really hard question - those methods extend your memory but the memory u gain is MUCH slower then the internal memory. So again u have to decide and try out if it helps u or it doesn't (I used em long time but never realy felt a big advantage of. Compcache even made my device feel slower and i got more FC's most time - also I tried to figure out how the memory management uses this "memory". But i din't find a clear answer yet - as some ppl mentioned that "inactve apps" wont get swapped - need some clear source... Anway in general those 2 should increase Multitasking capability at cost of speed.
7. FUDGESWAP
- noting yet - its GINGERBREAD only - so we have to wait...
FINALY: u have to decide on your own what u really NEED to run "simultaniously" (I personaly rather have less widgets and run background services like growl, eventghost, tasker) but u can count it yourself by checking back with taskmanager and having in mind your archos (GEN8) just has 256MB of internal memory.
CPU Manaagement:
8. (UD) If u got Urukdroid u can try setting your CPU Governor to another value like:
"Interactive" is more reactive than "on demand" (-> SIBERE)
9. Try an OC (OverClocked) Kernel -> get it in the Urukdroid Dev Thread (I wont link any here as u should know what u do and wich u choose!)
BEWARE not all devices can use an OC Kernel (sadly mine can't) but try it out...
10. Try overclocking your device with the Milestone Overclock Utility. This overclock method is based on a module insert. Again this just works with root.
OVERCLOCKING:
Each CPU is different -> each device is different and can handle different maximum speeds - this is related to the former position of the CPU on its waver while production...
So u have to try out what your CPU can handle safely - so it might happen your device will refuse to boot after u flashed a kernel or set some permanen OC values. Keep a BACKUP or reflash old kernel...
In general u normaly can't brick your device by overclocking as the CPU overheats -> safety function of the CPU stops it -> the device resets itself before the CPU get "burned" (hope this also aplies to ARM processors )
Other:
11. The Launcher: I tested out much lauchers already: ADW, ADW EX, VTL, Laucher PRO, Zeam Laucher, GO Laucher - most of them seem to be eaqual in speed and more differ in features (event Laucher PRO is still the fastest on my Wildfire [but development stopped some time ago], GO seemed to be a bit slower imho) - take any of those but avoid taking some over exagerated 3D'ish laucher like Regina, SPB Shell, Claystone...
12. Apps like "AutoKiller Memory Optimizer" have additionaly features to "optimise" the speed,... u might test those out but I didnt notice a difference most time. Still keep in mind - u should know what u are doing
13. Ok - u may want to hit me for that:
It's more a cosmetic thing - but I recently used UOT Kitchen for theming my framework and used the fly-in animations - and they feel much faster then the default animations just try it out... keep a backup of your original framework for reverting.
All the following Tweaks are mentioned by sibere (credits go to him and propably some other people)
echo "1536,2048,4096,6144,8192,10240" > /sys/module/lowmemorykiller/parameters/minfree
(this is related to 1. ; 1MB = 256 => valueas above are 6MB, 8MB, 16MB, 24MB, 32MB, 40MB)
to enable cgroups cpuacct:
mkdir /acct
mount -t cgroups -o cpuacct none /acct
mkdir /acct/uid
to change ioscheduler:
cd /sys/block/mmcblk1/queue
echo "deadline" > scheduler
cd iosched
echo 1 > fifo_batch
These are lost on reboot so if you wanna keep them, add a script to /etc/init.d
Finaly I also have patched the sqlite library. If you want the file, let me know. It boost a lot SQL database writings. See this thread http://forum.xda-developers.com/showthread.php?t=903507
Click to expand...
Click to collapse
Will ask him to comment on "cgroups, ioscheduler, and sqlite" as im not sure if they work with all rom versions / neither how they work exactly.
THANKS Sibere
EDIT:
aditional threads with tweaks
- Supercharger
- http://forum.xda-developers.com/showthread.php?t=1227269
BEWARE I HAVEN'T HAD THE TIME TO CHECK THEM OUT YET AND DIDN'T TEST THEM
SOME OF THEM MIGHT NOT WORK AND PEOPLEARGUE ABOUT THEM (e.g. the "debug.sf.hw =1" is heavily discussed)
IF ANYONE KNOWS MORE ABOUT THOSE OR CAN HELP TESTING IM HAPPY TO LEARN MORE ABOUT
Hi.
For a full reference to cgroups, you may read the cgroups documentation from the kernel.
Basically, it provides process aggregations in the Linux kernel, mainly for resource tracking purposes.
deadline IO scheduler has been used a lot for SSDs and proven to be quite adapted to flash memory.
The minfree settings set here are pretty much optimised by me for the archos. It gives you a good balance between available cache and free ram . Android starts to complain when the free ram drops below 32Mb. with these settings, the OOM task killer will try to maintain a free ram level above 32Mb. You DON'T need a task killer. It will just use precious ram resources and will mess up with the android integrated task killer.
Those settings are reset on boot, so you may add them in a script added to /etc/init.d/ directory.
SQlite optimisation is of great help and I already posted a lot of information about it when I posted the tweaked file. Please refer to this post. (You'll have to look for it, it's somewhere in the dev thread )
Enjoy your optimised archos!
Thanks guys, learning new tips.
Nice! Good tips. Thanks.
Very usefull reading, thanks!
thanks for the tips ! cheers!
Hello, I am JustLoveJoy, I am an up and coming developer, although I work very hard on my phone right now, my gf has gotten an Archos 8 G2 4GB tablet and I have it rooted but it constantly gives me some issues. Finding this thread, I have to ask, can these or any tweaks be applied to her tablet? is there any source code on github or somewhere else? I mainly wish to get her to be able to do her Farmville on it. I'd like to get on to the development boards with a custom rom for it but I need someone with a little experience to point me in the right direction for that. Thanks So much for starting this thread!
hi i just want to try to root my arnova 7g2 bit i don't find a straight 3d on xda. you clan indicate the right street
Inviato dal mio GT-N7000 con Tapatalk 2
did you notice that crow (CM7) for Gen8 was released ?
still nothing for developing for the Archos 8 G2 4GB? If I can get adb shell I would be happy!
Thanks
thinks man
:good:
Thanks for the great post! I still have one of these!

Categories

Resources