Develop Bugs

HTC Hermes overclocking

Hi folks!
How can the HTC Hermes overclock. Did it with some tools tried, but rather less successful. Batteerystatus no, xcpuscalar, overclocked but not really at 472-500 MHz. And with the PHM I can overclock well, but then does my GPRS connection to the Internet no longer work.
Is there a way to change this?
Translated by Google

This has been gone over numerous times and no, you can't overclock the Hermes reliably....

f21270 said:
Hi folks!
How can the HTC Hermes overclock. Did it with some tools tried, but rather less successful. Batteerystatus no, xcpuscalar, overclocked but not really at 472-500 MHz. And with the PHM I can overclock well, but then does my GPRS connection to the Internet no longer work.
Is there a way to change this?
Translated by Google
Click to expand...
Click to collapse
i overclock before to 500mhz using XCPUScalar

ov2rey said:
i overclock before to 500mhz using XCPUScalar
Click to expand...
Click to collapse
Is it reliable?

f21270 said:
Hi folks!
How can the HTC Hermes overclock. Did it with some tools tried, but rather less successful. Batteerystatus no, xcpuscalar, overclocked but not really at 472-500 MHz. And with the PHM I can overclock well, but then does my GPRS connection to the Internet no longer work.
Is there a way to change this?
Translated by Google
Click to expand...
Click to collapse
Although it is possible to overclock Hermes it cannot be done relyabily or without damaging the CPU...
Some utilities may allow an active and practical overclock but I wouldn't advise it...
As you may know, if wou want your Hermes to be more responsive, performant, you can increase your ROM page pool size prior to flashing.
Cheers.

it might not be able to overclock.. but, should be able to keep the cpu locked at 400mhz and not throttle to lower speeds.. which would make it much more responsive.. I've been meaning to test this

Black6spdZ said:
it might not be able to overclock.. but, should be able to keep the cpu locked at 400mhz and not throttle to lower speeds.. which would make it much more responsive.. I've been meaning to test this
Click to expand...
Click to collapse
The CPU is always at 400mhz. Wtf are you talking about?

no its NOT always at 400Mhz.. it has auto speed scaling built in. something is not right with both tcpmp and gxmark benchmarks.. using the newest PHM I manually set the lowest possible speed of 251Mhz, and disabling built-in scaling thinking of past knowledge that it doesn't do anything to our devices. I should not see any difference right? well visually it is MUCH slower than setting it at 400Mhz with both programs showing the same score at both speeds.. this CANNOT be correct.. I can see it with my eyes a night and day difference.. 420 seemed stable but the scores were showing slower than factory clock.. whats going on here?

this has been gone over so many times in the forum its not even funny any more.
use the search facility...

yes I know, I've read the overclocking threads from two years past.. ever considered newer software might change things? It does identify the processor correctly as a S3C2442A. I still want to know the answer to why benchmarks aren't reporting correctly.. BTW this thread should be moved
here are some results.. with a fresh boot I loaded a 39306KB AVI movie in CorePlayer 1.2.4. I ran its benchmark and also timed it with a stopwatch. The benchmark reported 1.60Mbit/s @ 3 Minutes and 21 seconds, also correct on the stopwatch. 321994752 bits divided by 201 seconds comes out to 1.601 Mbit/sec just like their calcs. Now I opened pockethackmaster 4.33 and set the clock to 420Mhz and reran the coreplayer benchmark. Here's the wierd part, the test reported that it took 4 minutes and 2 seconds with a 1.33Mbit/s rate but in actuality it only took 2 minutes and 58 seconds according to my stopwatch. Do the match, thats 1.809 Mbits/sec real throughput. So overclocking DOES work.. pretty significantly if I might add, but it appears that the timers used in these benchmarks are skewed and not reporting accurate numbers. Someone else try some tests and back me up here.

silly post ;0
When i get a tilt I want to overclock my hermes 100 to 900MHZ and see how fast it will melt!! Just kidding

joshkoss said:
When i get a tilt I want to overclock my hermes 100 to 900MHZ and see how fast it will melt!! Just kidding
Click to expand...
Click to collapse
I tried to overclock my oven but after that it keeps buning all my food
Is this process reverseable?
I need too cook a roasted chicken tonight and i will get nothing but a pile of coal...
Please help me!
I searched both the forum and the wiki but couldn't find any answer.
Cheers.

Kevlar-Source said:
I tried to overclock my oven but after that it keeps buning all my food
Is this process reverseable?
I need too cook a roasted chicken tonight and i will get nothing but a pile of coal...
Please help me!
I searched both the forum and the wiki but couldn't find any answer.
Cheers.
Click to expand...
Click to collapse
Just take it out really fast, lol.

6 months ago, i tried to overclock my hermes and then it was broken. i mean touch screen cant be touched=)) but i dont know is it about overclocking. just share my experiment

Kevlar-Source said:
As you may know, if wou want your Hermes to be more responsive, performant, you can increase your ROM page pool size prior to flashing.
Cheers.
Click to expand...
Click to collapse
But then you lose Ram, and when you only have 30 or so mb's of it to start its a crapshoot.

sure, it might make some of your videos or games faster but you'll most likely have problems with any data connection

PHM can brick your phone to an irreversable state, and xcpuscalar falsely shows an increase in processor speed. Battery status will not work for the hermes, and I don't think there is a program that will overclock a hermes CPU. As for the not constantly running at 400mhz, that is not a bad thing. Think of it as a P.C., when you are not running apps, there is a system idle process that occupies the majority of the processor, meaning that not all of the speed is utilized. If this is the case, that means that the processor is not running at full speed. Same goes for the Hermes, however there is no system idle process, just a slower clock speed. When you open an app it will reach, but not go over 400mhz.

pleas see attached zip file
this program give you the ability to overclock the hermes up to 420Mhz
i tested it - and at 420Mhz the device becomes slower and some minor flicks of the screen
i went back to 400Mhz and the device went back to usual operation
regards
edward

I too have tried various clock speeds but at the end of it all i left it default as the device was too unstable.

Also I have of course continue my attempts to overclock Hermes, but I am no satisfactory conclusion. At the moment I use xcpuscalar have all possibilities of tuning 500mhz switched on and it is stable. A benchmark I have not done, so I do not know exactly whether he has speed. But the belief puts mountains.
translated by Google

[Q] overclocking desire causes reboot and crash

Current phone rom and radio in sig.
Im using SetCPU and anything over 1036Mhz will eventually crash. Anything over 1113Mhz will cause instant crash and reboot-to-crash loop.
I've tried other CPU programs and the same thing happens.
Is there something I'm missing here? Can I not simple set the CPU and have it run at that speed, or is there another mod I should have completed before attempting to overclock?
I've tried search, nothing came back relevant. If there is a thread I've missed feel free to link.
Many thanks.

overclock a device that is much faster then anyother device to make it even faster?! bit greedy wouldnt you say? anyways.. it is very likely that you might have damaged your CPU.. use search button seen this problem before

I wouldn't say I'm greedy but overclocking is available and when there are a lot of CPU heavy apps, things can slow down. I wouldn't necessarily say I am running a lot, but I like the smoothness o/c brings. For the few seconds before it crashes.
If it was damaged then it wouldn't work at all. I don't think that is the answer I'm looking for. Thanks all the same.

JagSem said:
I wouldn't say I'm greedy but overclocking is available and when there are a lot of CPU heavy apps, things can slow down. I wouldn't necessarily say I am running a lot, but I like the smoothness o/c brings. For the few seconds before it crashes.
If it was damaged then it wouldn't work at all. I don't think that is the answer I'm looking for. Thanks all the same.
Click to expand...
Click to collapse
yeah I know.. that why we have cutom ROM, make the most of the phone we pay for
tried helping, with my limited knowledge about o/c'ing .. sorry !

if it's like PC overclocking, then it won't damage it unless you overvolt it - although some mods will allow this (custom kernels).

http://forum.xda-developers.com/showpost.php?p=8373423&postcount=7000

Anyone found a solution for the lag in apps drawer scroll

Hey guys. Anyone found a fix to the lag issue when scrolling up and down in the apps drawer? To know more that I mean, pls click on the below 2 links:
http ://forum.xda-developers.com/showthread.php?t=679037&highlight=scroll+speed
and
http ://forum.xda-developers.com/showthread.php?t=657569&highlight=lag+program+menu+htc+desire

That's strange, I don't experience any lag at all... It's supersmooth and fast.

Ditto, smooth as anything here

Are you using a live wallpaper? one thing i've noticed is cpu intensive live wallpapers make scrolling the apps menu lag quite badly. At a guess i'd say live wallpapers remain running when the apps menu is displayed.
Switch to a static wallpaper or the relatively undemanding htc sense live wallpaper, see if it makes a difference.

Weird..no lag here.
Super smooth.

Yeah, I have a solution for you: buy an iPhone!
Okay, enough trolling. I experienced that as well, but it suddenly stopped and now it's very smooth. I don't know what I did, but I am certain that it stopped after the second 2.2 OTA.

I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!

nawoa said:
I have a few different ideas you can try. I do all of these on my own phone and it's snappy as anything, even though I've limited the clock speed to 650 maximum.
1) Copy everything back to your phone if you currently have most/all things on your SD card, leaving the things on your SD only if they're actually big. Say, everything below 2mb keep on your phone.
2) Install a different launcher, like ADW. Aside from possibly being a little faster, it allows you to customize your app drawer and remove things you don't need. For example I've removed everything I already have an icon on my home screen for, and now I only use the app drawer for odds and ends or things I'm still deciding if I need them or not - like, 15 things at most usually. I don't even NEED to scroll!
3) Install a better OS, like Cyanogenmod. It's faster in general.
4) Install an OS (or patch/script) which allows you to use an EXT partition on your SD card for apps. EXT2/3/4 are much faster and lower-latency than FAT32.
5) Use SetCPU or a similar app to increase your CPU's MINIMUM speed while the screen is on, from 245 to 384. This will eliminate the initial stutter your phone may have before it decides to clock up the CPU. Even though it's a 50% increase or whatever, in practice it will have virtually no effect on your battery life since it will only take effect while the screen's on - at which time your screen will be using lots more power than the CPU does at any speed.
If #5 solves it for you, just remember the stuttering you're experiencing is only for the sake of battery savings, it's got nothing to do with your phone's performance. In that sense, it highlights one of Android's features rather than a deficiency, even if it's doing this in an unattractive way!
Click to expand...
Click to collapse
I have my Desire set at 768 max and there really isn't a noticeable difference from the normal 998. Hell. I clocked it way down and it was still WAY faster then my HTC Magic ever was. It's funny that the Desire's processor is faster at 3xx mhz then the Magic's is at 710mhz. I found the Desire to be unstable for sustained periods of anything under 700mhz though. Is yours running stable at 650? Maybe it was just the 691mhz speed I was using.

{Script} CPU1 disabler while in sleep!!! The Battery Saver Mod!

Script Version!
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
CPU Sleeper
Honestly the Script can be made to work with any Dual Core / Quad Core! The Only Problem is you need to be Rooted!
~ Currently the issue with CM9, is that the boot becomes incomplete while in init.d folder without Modification to the sysinit..
~ however, with any rooted device you can download the script & continue to use it via a script manager app on every boot.
~ With the Script Manager App, this script virtually can run on any Multi-Processor CPU
Hope that clears things Up,
~~Eugene
Click to expand...
Click to collapse
What is it?
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
How does it work?
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
WARNING! READ THIS!
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
Instructions
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Version 1: Flashable
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
Version 2: Script only
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
Init.d supported kernel:
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Once done, reboot the system, and it will take effect when your system is finished rebooting.
Script Manager
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
What do I do if I can't boot after using this?
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
Downloads
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: Script Only - Recommend Install via Script Manager App
CPU Sleeper script only
Quad Core:
Download: Script Only - Recommend Install via Script Manager App
cpusleep
Thanks to pio_masaki for rewriting the OP

I gonne try this the next days. But first i have to get a battery-life reference for my phone/settings.
Sent from my GT-I9300 using xda premium

schurgatzi said:
I gonne try this the next days. But first i have to get a battery-life reference for my phone/settings.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks! It's been confirmed working perfect for all Dual / Quad Cores device with no ill effect..

I think that this script is placebo effect if someone thinks to see a difference in battery life. On the Galaxy Nexus this maybe is a battery saver, but on the Galaxy s3 Samsung has delivered us the pegasusq governor and controls every core for itself. So your script doesn't change anything in the functionality if I understand it correct what it does. Because without this script the phone shuts down the uneeded cores, so where's the difference?
L

@ the op, what are you getting in terms of time without charge?
I've seen these ideas come and go and I give you merit for trying.
What is your up time from max charge to depletion?
If it works it works and I'm sure people will use it , we just need to make sure it's not a placebo and that it is actually saving battery.
Is there any lag on wake? Does the script ever cause too deep a sleep, forcing a restart or battery pull? What's been your experience?
I am curious about this because I've found the battery life on this phone to be no better than my evo 3D.
Many thanks.
Sent from my GT-I9300 using xda premium

lmao... then don't use it... CPU 1/2/3 is always online! even if it's report offline...
If you don't like it, don't use it! simple fact is, even when asleep there online & being used...
dladz said:
@ the op, what are you getting in terms of time without charge?
I've seen these ideas come and go and I give you merit for trying.
What is your up time from max charge to depletion?
If it works it works and I'm sure people will use it , we just need to make sure it's not a placebo and that it is actually saving battery.
Is there any lag on wake? Does the script ever cause too deep a sleep, forcing a restart or battery pull? What's been your experience?
I am curious about this because I've found the battery life on this phone to be no better than my evo 3D.
Many thanks.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Don't Care.... People who have used it enjoy it... so??
yeah I don't care at this point!

I'll give it a go and let you guys know how I find the mod under different situations.
Thanks for sharing OP!
edit: Isn't this what a Tegra 3 does? It has 4 cores and a sleep core. This might be good for non Tegra 3 devices but I can't see this helping.

eugene373 said:
lmao... then don't use it... CPU 1/2/3 is always online! even if it's report offline...
If you don't like it, don't use it! simple fact is, even when asleep there online & being used...
No lag, battery is increased & there is no placebo!
This has been confirmed from Quad-core users before even posting it...... You only see Battery increase during sleep, if you are a heavy user then likely no you will not see any increase......
however, this works great due to android even when asleep still uses all the CPU..... I Don't f'k care if it's being report offline.....
when asleep, this scripts force all CPU offline until awake, as 1 cpu asleep can handle everything the phone is doing.
Click to expand...
Click to collapse
hmmm, I've watched how the cores behave for quite some time via adb. Actually everytime I send the phone to sleep mode aka push power button, core 1-3 is going offline. So I guess pegasusq does its work already

I downloaded the script in order to place in init.d but it was downloaded as a .txt file, what should the file extension be/how do I download it without altering the extension?
Regards
Jack

eugene373 said:
making sure no file extensions get added
Click to expand...
Click to collapse
JSale said:
I downloaded the script in order to place in init.d but it was downloaded as a .txt file, what should the file extension be/how do I download it without altering the extension?
Regards
Jack
Click to expand...
Click to collapse
So..
Delete the file extension and that's all.

When you say script manager, do you mean SManager from Google Play?

This is a nonsense implementation. I don't advise anybody to use it.
It's a while loop just trying to send the CPUs into offline mode every 2 seconds per CPU, or every 6 seconds per CPU if you're turning off 3 cores. It does absolutely nothing to prevent the cores from powering up in terms of hot-plug logic and it can even decrease the battery life if there is some kind of load that would trigger a CPU to get online; so CPUs might just go online and then get shut down.
Edit: Oh, you also absolutely fail to mention that this script will turn on all 4 CPUs while screen on, completely disregarding hotplugging.

AndreiLux said:
This is a nonsense implementation. I don't advise anybody to use it.
It's a while loop just trying to send the CPUs into offline mode every 2 seconds per CPU, or every 6 seconds per CPU if you're turning off 3 cores. It does absolutely nothing to prevent the cores from powering up in terms of hot-plug logic and it can even decrease the battery life if there is some kind of load that would trigger a CPU to get online; so CPUs might just go online and then get shut down.
Edit: Oh, you also absolutely fail to mention that this script will turn on all 4 CPUs while screen on, completely disregarding hotplugging.
Click to expand...
Click to collapse
Don't Care.... People who have used it enjoy it... so??
yeah I don't care at this point!

eugene373 said:
lmao... Correct.... This is why I can care less about this Forums even though It's be Proven to save battery... But, Clearly you know more than me... So Please for the love God & Don't use it..
Sorry, got to Ask though? Why have other CPU's if you can use during wake? Okay then... And since when does Hot=Plugging work Correctly?
~Eugene
Click to expand...
Click to collapse
Stop whining and address the issues at hand. Turn on DVFS debugging in /sys/devices/system/cpu/cpufreq/pegasusq/dvfs_debug and open a terminal to monitor /proc/kmsg either on your own device or through ADB to test the screen off nonsense; the core statistics with load of each core, if they're online or not, the runqueue lengths and the frequency for each sampling period of the governor.
Why have other CPU's if you can use during wake?
Click to expand...
Click to collapse
I don't know what you mean by this unintelligible piece of gibberish, but I assume you are asking why having multiple CPUs if they are not online. The CPUs are turned on based on load and turned off when idling when there is nothing to do to preserve power. Hotplugging has worked since ever and it works perfectly. I don't know what planet you lived on or what credentials you have to earn that recognized developer title but you have clearly no idea of what you are talking about and have some issues with dealing with criticism.
This script certainly decreases screen-on battery life and in a best case-scenario does nothing to idle time, and in a worst-case scenario decreases it and conflicts with other scaling logics of the processor.

AndreiLux said:
Stop whining and address the issues at hand. Turn on DVFS debugging in /sys/devices/system/cpu/cpufreq/pegasusq/dvfs_debug and open a terminal to monitor /proc/kmsg either on your own device or through ADB to test the screen off nonsense; the core statistics with load of each core, if they're online or not, the runqueue lengths and the frequency for each sampling period of the governor.
I don't know what you mean by this unintelligible piece of gibberish, but I assume you are asking why having multiple CPUs if they are not online. The CPUs are turned on based on load and turned off when idling when there is nothing to do to preserve power. Hotplugging has worked since ever and it works perfectly. I don't know what planet you lived on or what credentials you have to earn that recognized developer title but you have clearly no idea of what you are talking about and have some issues with dealing with criticism.
This script certainly decreases screen-on battery life and in a best case-scenario does nothing to idle time, and in a worst-case scenario decreases it and conflicts with other scaling logics of the processor.
Click to expand...
Click to collapse
Don't Care.... People who have used it enjoy it... so??
yeah I don't care at this point!

eugene373 said:
All I can do is Laugh at your ignorance...
Honestly, if you think it wont work, then don't use it.... However! It's been confirm across the board before you start shooting off with the mouth!
Samsung Hot-Plugging does not work Correct, well this being the case for msm8660, I don't claim to know it all, nor do I want to.. My Problem is people jump the gun without testing & start talking BS before even testing...
This has been confirmed... It does work.... It does Save battery, so why act like a jerk when helping out?
~Eugene
Click to expand...
Click to collapse
I tested it already and posted how to see the facts and statistics in my last post. You don't own the device, I do.
I see now that you're just very severely confused. This is the INTERNATIONAL (i9300) Galaxy S3 forum. The quadcore or any Exynos for that matter has proper and working hot-plugging. This is not running on Qualcomm processors. Re-read the last 2 phrases 10 times.
Now go back to my last post and read what I wrote before you starting releasing things for a) The wrong device b) Having no clue about the device you are releasing something for. I consider you are clueless since there is currently no quad-core CPU on the planet right now in mobile phones which does not support hot-plugging, so you couldn't have mixed that up.
Your confirmation is coming from some random people which know even less about the facts and installed that script just yesterday, making it worthless and meaningless.
Feel free to argue this with other users as I'm done here.
Edit: By the way, I see that you created a copy of this thread for every single ****ing variant of the S3 [1],[2],[3],[4] (Way to go with all US versions being in the same sub-forum category!). While I don't have access to any of those, I'm fairly sure they also have working hot-plugging.

AndreiLux said:
I tested it already and posted how to see the facts and statistics in my last post. You don't own the device, I do.
I see now that you're just very severely confused. This is the INTERNATIONAL (i9300) Galaxy S3 forum. The quadcore or any Exynos for that matter has proper and working hot-plugging. This is not running on Qualcomm processors. Re-read the last 2 phrases 10 times.
Now go back to my last post and read what I wrote before you starting releasing things for a) The wrong device b) Having no clue about the device you are releasing something for. I consider you are clueless since there is currently no quad-core CPU on the planet right now in mobile phones which does not support hot-plugging, so you couldn't have mixed that up.
Your confirmation is coming from some random people which know even less about the facts and installed that script just yesterday, making it worthless and meaningless.
Feel free to argue this with other users as I'm done here.
Edit: By the way, I see that you created a copy of this thread for every single ****ing variant of the S3 [1],[2],[3],[4] (Way to go with all US versions being in the same sub-forum category!). While I don't have access to any of those, I'm fairly sure they also have working hot-plugging.
Click to expand...
Click to collapse
Don't Care.... People who have used it enjoy it... so??
yeah I don't care at this point!

Wow!!!! Lol.. I just learned a hell of a lot from both of you.!! Thanks!!

eugene373 said:
lmao... then don't use it... CPU 1/2/3 is always online! even if it's report offline...
If you don't like it, don't use it! simple fact is, even when asleep there online & being used...
Don't Care.... People who have used it enjoy it... so??
yeah I don't care at this point!
Click to expand...
Click to collapse
Lol, easy tiger, I was literally just asking, I wasn't doubting you in any way shape or form, just had a few questions thats all.
Ill try it and see how it goes.
Sent from my GT-I9300 using xda premium

There has been countless Number of People that has Confirmed this on the Atrix2 / SGS2 / Sensation / SGS3 and One X is currently being test as well..
However Correct, I do not own this device, other than what People have stated to me in IRC...
If it don't work, well then it don't work.... All I ask is People to test it out without jumping down my ****
I do however owe everyone an apology for last night.. I was Drinking & normally not that hot headed nor will it happen again.
I Highly Recommend Using the App Version.
Thanks,
~Eugene

[Q] Should This help for lag?

Was on the portal and noticed this:
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Caveats
There is a (theoretical) security risk, in that seeding /dev/random with /dev/urandom decreases the quality of the random data. In practice, the odds of this being cryptographically exploited are far lower than the odds of someone attacking the OS itself (a much simpler challenge).
This may adversely affect battery life, since it wakes every second. It does not hold a wakelock, so it shouldn't have a big impact, but let me know if you think it's causing problems. I can add a blocking read to the code so that it only executes while the screen is on. On the other hand, many of us attribute lag to lacking CPU power. Since this hack eliminates almost all lag, there is less of a need to overclock, potentially reducing battery consumption.
If you try it, let me know how it goes.
ROM builders - feel free to integrate this into your ROMs (either the .apk / application, or just the rngd binary called from init.d)!
If anyone's interested, I've launched a paid app on the Play store for non-xda users. As I add features I'll post the new versions here as a thanks to you guys (and xda community at large for being such a great resource). But if anyone's interested in the market's auto-update feature, just thought I'd mention it.
Cheers!
Click to expand...
Click to collapse
Should this help with the lag that we get on the Play?
If anyone else wants to try it heres the link to the thread:
http://forum.xda-developers.com/showthread.php?t=1987032

I tried it and it i got faster loading on some minor stuff (like contact picture loading) and apps installed on the internal memory seems to load faster, in terms of UI smoothness I don't notice any difference, because UI is smooth since the beginning

I think i may try it out although i don't see any instructions
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

BTW, somebody already posted this in the XPlay Android Dev section:
http://forum.xda-developers.com/showthread.php?t=2073382