How does CPU of android phone cant handle processes like windows OS. It would be very energy saving and. Instead of adjusting to the load needed, Cpu goes straight to max freq which is set 1Ghz and with voltage on line equal to 1200Mv. Sure it is not worst couse by default DS CPU has 1000Mv on 245MHz(lowest freq) and 1.2V is not that much of jump compared to 1.0V. But if you underVOLT like me:
Mhz - CPU_____Mv -default _______Mv -lowest stable is:
24______________1000______________750
61______________1000______________750
122_____________1000_____________ 775
184_____________1000______________775
192_____________1000______________800
245_____________1000______________800
368_____________1050______________825
768_____________1100______________875
806_____________1100______________900
1024____________1200______________975
1200____________1200______________1050
1400____________1250______________1175
1490____________1250______________1175
You get 800mV at 245Mhz and 975mV at 1024Mhz so its stil 0,175V difference and its not that much but if Android Would handle CPU load by app and by how much it is needed it would make epic difference if you underclock like this.
So its my opinion on how they should fix CPU Battery drain problem on all devices.
Second battery drain problem is screen, which in my opinion should be led technology based so it doesnt drain so much battery.
If Google/Android/manufacturers fix these two problems current batterys should be more than enough for phones to last at least 3 days top medium usage.
So what you think guys? Should there be any changes in these two things and if so what should they be
BTW: Does all phone OS's handle it same way?
First depending on your governor it does scale related to load (even more, it as well does switch processors "off" at multi core architectures when they are not needed).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oled is more power efficient, but has a darker screen, it's user depending what is preferred.
Before you break your head about such stuff, wait what project roadrunner will bring, there are many people already working on it that have a much deeper insight at the whole thing
Sent from my GT-I9300 using Tapatalk 2
Tectas said:
First depending on your governor it does scale related to load (even more, it as well does switch processors "off" at multi core architectures when they are not needed).
View attachment 1393761
Oled is more power efficient, but has a darker screen, it's user depending what is preferred.
Before you break your head about such stuff, wait what project roadrunner will bring, there are many people already working on it that have a much deeper insight at the whole thing
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
All this pick proves is that it just gradually rises to max freq. every time and after some timeout it falls gradually. And i have never ever heared of Android phone handling CPU load anything even remotely similair to Windows OS(PC), and curent handling is just not energy saving, thats why all the governors have been created to adjust the imperfect scaling to make it better to live with.
And i am not breaking my head about it i am just generally disapointed in those two aspects of smartphones these days an di just want to hear what others think about it.
On touch it scales up to 800mhz (at my device, because i set it to act that way), that's one of the things introduced with project butter, but when you check the Times you see yourself it is most of the time at 200mhz, because today i read much at the device, the 20 minutes max frequency are, because i played a bit as well.
As well check yourself, download cpu spy, keep it running a bit and refresh it every now and then, depending on your governor it will be pretty much at 200mhz even while screen is on and a app running, because it needs no load, except you have some rouge app in the background.
Governors haven't been invented to fix something (or yes, but only to fix it for the inventor, because his needs where different), they have been invented to be able to modify the cpu scaling to your needs, raw power or battery or something in between, depending on your preferences.
Sent from my GT-I9300 using Tapatalk 2
Tectas said:
On touch it scales up to 800mhz (at my device, because i set it to act that way), that's one of the things introduced with project butter, but when you check the Times you see yourself it is most of the time at 200mhz, because today i read much at the device, the 20 minutes max frequency are, because i played a bit as well.
As well check yourself, download cpu spy, keep it running a bit and refresh it every now and then, depending on your governor it will be pretty much at 200mhz even while screen is on and a app running, because it needs no load, except you have some rouge app in the background.
Governors haven't been invented to fix something (or yes, but only to fix it for the inventor, because his needs where different), they have been invented to be able to modify the cpu scaling to your needs, raw power or battery or something in between, depending on your preferences.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
It is true only for late governors, they are for tweaking and early governors there for moking it better overall, and on touch it always scales on to max aswell even if it doesnt need it. Thats the problem. Didint know project butter can do that.
TeddyOFLove said:
It is true only for late governors, they are for tweaking and early governors there for moking it better overall, and on touch it always scales on to max aswell even if it doesnt need it. Thats the problem. Didint know project butter can do that.
Click to expand...
Click to collapse
Making it better is much user depending, the early governors you talk about differ as well, performance keeps the max frequency, powersave the lowest
The scaling to max on touch is only project butter, before only the governor handled the scaling based on load.
Sent from my GT-I9300 using Tapatalk 2
Tectas said:
Making it better is much user depending, the early governors you talk about differ as well, performance keeps the max frequency, powersave the lowest
The scaling to max on touch is only project butter, before only the governor handled the scaling based on load.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Still its is very unbalanced and battery unfriendly system which should be modified. And also Cpu modes i think only serve to ruin it all. Cpu usage transition sshould be smooth not jumping from strickt mode to other. It is also what gets in the way of ever getting battery friendly CPU usage.
TeddyOFLove said:
Still its is very unbalanced and battery unfriendly system which should be modified. And also Cpu modes i think only serve to ruin it all. Cpu usage transition sshould be smooth not jumping from strickt mode to other. It is also what gets in the way of ever getting battery friendly CPU usage.
Click to expand...
Click to collapse
Oh, thinking about writing a new governor are you? Well good luck with that :thumbup:
And by the way, as far as I know, no CPU can change frequencies "smoothly", even on the magnificent windows os...
Sent from my Desire S using xda app-developers app
TeddyOFLove said:
Still its is very unbalanced and battery unfriendly system which should be modified. And also Cpu modes i think only serve to ruin it all. Cpu usage transition sshould be smooth not jumping from strickt mode to other. It is also what gets in the way of ever getting battery friendly CPU usage.
Click to expand...
Click to collapse
Man really, it isn't that bad at all, yes it isn't perfect and there is still place to enhance, but they are already working on it (see project roadrunner) and are you aware of how hard it is to get the "perfect" balance (even without adding personal preferences). Really, get deeper into it, it does not jump from strict mode to another, with the right governor you get smooth scaling (at least as far as possible), it only jumps, at touch with project butter, the other times the governor scales.
If your not happy with it, flash ics or gb and stick with it, no project butter.
Or switch to Windows phone and stick with the closed platform.
Android needs reading, find the fitting setup for you, play with kernel parameters, system parameters and so on and get what you like to have our even better if you are not happy with what currently is available, invent a "better" governor yourself.
Sent from my GT-I9300 using Tapatalk 2
teadrinker said:
Oh, thinking about writing a new governor are you? Well good luck with that :thumbup:
And by the way, as far as I know, no CPU can change frequencies "smoothly", even on the magnificent windows os...
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Definition of Smoothly is hard to define in this case it is more like as smooth as it can get . What i am talking about if you atleast read anything in this thread is that governors (curent system) is full of flaws and very battery unfriendly, so it has to be changed by Android/Google (android software developers and cpu and phone makers)
TeddyOFLove said:
Definition of Smoothly is hard to define in this case it is more like as smooth as it can get . What i am talking about if you atleast read anything in this thread is that governors (curent system) is full of flaws and very battery unfriendly, so it has to be changed by Android/Google (android software developers and cpu and phone makers)
Click to expand...
Click to collapse
Use conservative, it hits every frequency step at scaling up and down, that's what you wanted ha?
And no they aren't, only you say it, because you have not much clue how you can get your setup right done (or it at least seems that way), they aren't perfect, but no current mobile os is perfect.
Sent from my GT-I9300 using Tapatalk 2
TeddyOFLove said:
Definition of Smoothly is hard to define in this case it is more like as smooth as it can get . What i am talking about if you atleast read anything in this thread is that governors (curent system) is full of flaws and very battery unfriendly, so it has to be changed by Android/Google (android software developers and cpu and phone makers)
Click to expand...
Click to collapse
I still don't get what differences you see between android and other systems in this respect.
Sent from my Desire S using xda app-developers app
Tectas said:
Man really, it isn't that bad at all, yes it isn't perfect and there is still place to enhance, but they are already working on it (see project roadrunner) and are you aware of how hard it is to get the "perfect" balance (even without adding personal preferences). Really, get deeper into it, it does not jump from strict mode to another, with the right governor you get smooth scaling (at least as far as possible), it only jumps, at touch with project butter, the other times the governor scales.
If your not happy with it, flash ics or gb and stick with it, no project butter.
Or switch to Windows phone and stick with the closed platform.
Android needs reading, find the fitting setup for you, play with kernel parameters, system parameters and so on and get what you like to have our even better if you are not happy with what currently is available, invent a "better" governor yourself.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yeah its full of flaws and perfection is not possible couse of hardware and human psibilitie. Thats what i am talkin about here is what i think of these things and i i only asked what others thiink about it. But sadly enough nnone have their own opinions anymore or they simply dont care.
You know thats what forums are about to disscuss things about common intrests (this case Smartphones and stuff directly related to them).
And as for your statement that it isnt that badi would disagree, becouse it is not normal to keep releasing phones with unsolved problems like this. If new phone is released it should atleast fix or tweak those problems or make for example beter battery's.
OFF-topic:
It is common knowledge that for example batterys with better potential and better capacity are already invented long time ago, it is simply that phone makers dont want to spend extra money for battery . Would you sell Your creation phone for 1500$ production cost is 500$ at most. And when you add battery which alone costs 200$ instead of simple old 20$ battery, you get 1500-500+20-200=820$ profit and not 1000$. If you sell 100,000 copies with better battery you would loose 180$*100,000=18,000,000$ it is funny how it works they only need our money. Companies that make give or take 1,000,000,000$ a year are ready to "risk" it all at expense of their consumers.
teadrinker said:
I still don't get what differences you see between android and other systems in this respect.
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
I dont, couse i havent used other OS phones. I talk about it in generall, and i asked what other members think about CPU handling of other Phones OS compared to Android.
Tectas said:
Use conservative, it hits every frequency step at scaling up and down, that's what you wanted ha?
And no they aren't, only you say it, because you have not much clue how you can get your setup right done (or it at least seems that way), they aren't perfect, but no current mobile os is perfect.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
You know yourself it is not what anyone wants + it is slow. It is only climbing stairs. Jumping from one to other (at preprogramed condition, probably timout like uaually), so it hits every freq but is is as i said just jumping around without concern for what is going on. Just getting preprogrammed condition realised.
UPDATE:
Ohh sry for triple post (should have multi queted) not spammin and will not happen again
Because it's a problem for you it doesn't mean it's a problem for anyone, i charge my phone anyway every evening and i can pass the day without problems.
The thing is you state it like everyone should be pissed, because it is as bad, but that's only your opinion, not only that it's your opinion without founding it one enough background.
And stating to have no own opinion, because I'm not sharing yours is just childish.
About your off topic, yes they want to make profit, that's what they live from.
The reason why current devices aren't equipped with better battery cells is simple, they could build it for sure, but they would need to sell it at a price level no one would pay for such a device.
Sent from my GT-I9300 using Tapatalk 2
OFF TOPIC: I'm beginning to think TeddyOfLove should go into politics
TeddyOFLove said:
You know yourself it is not what anyone wants + it is slow. It is only climbing stairs. Jumping from one to other (at preprogramed condition, probably timout like uaually), so it hits every freq but is is as i said just jumping around without concern for what is going on. Just getting preprogrammed condition realised.
UPDATE:
Ohh sry for triple post (should have multi queted) not spammin and will not happen again
Click to expand...
Click to collapse
You moaned about smooth scaling, that way you get it.
With the right governor it does not jump around without concern, it scales based on load, yes it's preprogrammed, but still doesn't scale completely up if it's not needed. Or do you want something like an a.i. for scaling? Good idea, take a second device just for scaling the first or get a damn slow device, because of the overhead with worse battery life than current devices.
Sent from my GT-I9300 using Tapatalk 2
Tectas said:
Because it's a problem for you it doesn't mean it's a problem for anyone, i charge my phone anyway every evening and i can pass the day without problems.
The thing is you state it like everyone should be pissed, because it is as bad, but that's only your opinion, not only that it's your opinion without founding it one enough background.
And stating to have no own opinion, because I'm not sharing yours is just childish.
About your off topic, yes they want to make profit, that's what they live from.
The reason why current devices aren't equipped with better battery cells is simple, they could build it for sure, but they would need to sell it at a price level no one would pay for such a device.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I neve said it problem for everyone everyday. It is problem for everyone, but as you say me too charge phone once ~24 hours, and i can use it at medium use(so no problem there). And dont call me childish couse i was reffering to all people that read this thread and dont post any opinion on this matter. You did post your opinion we disscused and it is normal (noone is childish or anything) just all (3 people atm ) having their own opinions.
teadrinker said:
OFF TOPIC: I'm beginning to think TeddyOfLove should go into politics
Click to expand...
Click to collapse
Heh you should be comedian
Tectas said:
You moaned about smooth scaling, that way you get it.
With the right governor it does not jump around without concern, it scales based on load, yes it's preprogrammed, but still doesn't scale completely up if it's not needed. Or do you want something like an a.i. for scaling? Good idea, take a second device just for scaling the first or get a damn slow device, because of the overhead with worse battery life than current devices.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Preprogrammed being mostly timeouts and time based scenarios. It is not time that you need is looking at state of devise and adjusting. A.I. would be nice.but its more from fantazy world .
P.S. And once again i just point out that i dont moan(or anything close to that.) I just simply state opinion give arguments- you and others agree disagree on some points and give arguments and its goes round and round. If you dont like to read, post , discuss, share, think - then you are robot man (like auto answer machine). And i doubt forums were created so Some Auto-aswer machines (spambots) would post. It was for real interaction and communication. So just stop flaming, and if you dont like something about this thread just as you before did post your opinion and leave(not an order just healthy advise, couse rage of some Forum is pathetic)
BTW how do you delete post if its fail(double post i mean) so you can make it as edit last.
Related
Hi,
having registered here some time ago i've been reading many threads about custom ROMs and the kernels used. Many of them seem to support overclocking your phones CPU. The thing i'm wondering about is that there's kernels which actually overclock your CPU to double the speed its CPU is supposed to be running on (!!), giving the CPU some more voltage i believe.
Actually i'm a bit sceptical about how setting the CPU to such sick frequencies has a bad effect on the CPU's lifetime. The way i understood the problem with clocking the CPU high is always the heat development, meaning without proper cooling the CPU will simply "melt away" (at least that's how it is on desktop computers). Of course, CPU's on smartphones are not cooled or anything. Now that there seem to be many people here, developpers or not, who got deeper into the hardware, probably already opened up a phone, or have some experience with the long term consequences of overclocking.
So my final question is: What is safe and what is not? I saw for the Galaxy 3 for example exist different kernels, some non-overlock kernels, as some kernels only doing limited overclocking up to 800 MHz (which seems to be the most healthy option to me), but also some kernels overclocking up to 1300 MHz, which as i said seems kinda sick to me. Well i bet there's someone out there with a bit more experience than me regarding this so i'd be thankful for any answer.
I believe its safe as long as you dont keep the phone at high overclocked spds all the time. Besides, this chips are designed to last 5 years at least so if you overclock and shorten its life, you would have already changed your phone. In short, dont worry, just dont leave your phone at above 1000mhz all the time
Sent from my GT-I9003 using xda premium
bscraze said:
Besides, this chips are designed to last 5 years at least so if you overclock and shorten its life, you would have already changed your phone.
Click to expand...
Click to collapse
You got a point there hehe. Technical progress is moving in light speed. Anyway, i want to make my phone last as long as possible of course. But it's true, with CPU stepping it won't run on the highest frequency the whole time, even if overclocked, so i guess that overheating won't be an issue.
The only time i overclock is when im playing 3d games. Other times mine is 700mhz at most
Sent from my GT-I9003 using xda premium
hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??
LooksLikeSmart said:
hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??
Click to expand...
Click to collapse
No.. 800mhz should be your main profile. When charging i put 1200mhz 300mhz on demand. You shouldnt always leave it at 1200mhz. Only when you need it
Sent from my GT-I9003 using xda premium
LooksLikeSmart said:
hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??
Click to expand...
Click to collapse
if you use a governor like OnDemand/Conservative, your phone wont always be on 1200 but usually on the lower values...It will go only to 1200 when needed
I used to always use 'on demand' on other phone. Does this have do with the unreleased tegra drivers? Do scaling profiles even make a difference with battery life impact?
Thank you for your time
samsizzle said:
I used to always use 'on demand' on other phone. Does this have do with the unreleased tegra drivers? Do scaling profiles even make a difference with battery life impact?
Thank you for your time
Click to expand...
Click to collapse
Tegra is unique in this aspect. The governor on our phones is in a sense 'hard coded' into the phone, its called DVFS Dual-core Voltage Frequency Scaling (im actually not sure if i made this name up or its the right one... )
either way, it can only be tweaked by a kernel dev, and we cannot use any other governors.
the way nvidia made the phone we are locked into this (and by default the settings they used) and also unfortunately for alot of us, it seems that nvidia preferred performance over battery life.
yes, on most phones governors can make a HUGE difference, in battery life, performance, and feel of the rom. but not for us
Klathmon said:
Tegra is unique in this aspect. The governor on our phones is in a sense 'hard coded' into the phone, its called DVFS Dual-core Voltage Frequency Scaling (im actually not sure if i made this name up or its the right one... )
either way, it can only be tweaked by a kernel dev, and we cannot use any other governors.
the way nvidia made the phone we are locked into this (and by default the settings they used) and also unfortunately for alot of us, it seems that nvidia preferred performance over battery life.
yes, on most phones governors can make a HUGE difference, in battery life, performance, and feel of the rom. but not for us
Click to expand...
Click to collapse
However you gotta give it to nvidia for making a very good chunk of code on that one cause it still works very well despite the nvidia nazi tendencies
Pin it to Win it.
Learn something new everyday! Thanks for clearing that up
I.R.Chevy said:
However you gotta give it to nvidia for making a very good chunk of code on that one cause it still works very well despite the nvidia nazi tendencies
Pin it to Win it.
Click to expand...
Click to collapse
well yeah, for all the **** this phone gets, its very good at what it's made for. (playing games)
However it's unfortunate that we can't change it's propensity for speed and power.
Sent from my LG-P999 using Tapatalk 2
Getting better battery life is a struggle most mobile device users will have for the foreseeable future. Even if advanced batteries are released that give users two days of heavy use, there will naturally be a script, an application, and a kernel tweak to improve this figure further. As batteries get better, so do battery applications. Now, a new tool has been released that’s looking to be the best.
The application is called One Power Guard. Made by XDA Forum Member fonter, it is designed for rooted and custom ROM users. It brings an all-in-one approach to battery life and phone tweaking. You can adjust pretty much anything, including the I/O scheduler, CPU governor, CPU over- or under-clocking, settings tweaks, and more. There are also six modes you can choose from that tweak your phone for you. They include:
AI Mode: It intelligently adjusts cpu frequency and optimizes kernel to greatly extend battery time according to system loading.
Powersave Mode: It runs devices under low frequency to extend standby time.
Game/Video Mode: It provides flow game and video experience while offering satisfactory power-saving strategy.
Call Mode: It powers up the core function of phone conservation. For business persons trapping by phone.
Standby Mode: It lowers system frequency and prolongs stand-by time to the extreme. For sleepers and dreamers.
Custom Mode: It indulges pros to customize cpu frequence, scheduling and io adjustment, and to choose parameters of their own.
It’s a really nice application for those who don’t want to re-tweak their phone after every ROM flash and those who don’t know how to tweak their phones manually. For additional information on how each mode works and download links, check out the original thread.
You can try One Power Guard, Download from onexuan.com
I lol'ed at the fact that they state it's for android, yet it has a picture of an iPhone. I'll have to try this. Thanks!
trying this out, we'll see how well it does compared to the others
OK app works much better than anyone I've tried for this matter, doesn't help too too much but it does make a little bit of difference, also this should be obvious but it does slow the system down a bit, and i also had some conflicts with it changing kernel values but I'd rate it a 3.5 out of 5 for what it does though when compared to other apps four the same thing out would be a 4.5-5 not a full 5 because there has to be done room for improvement
Sent from my SGH-I997 using xda premium
deathblade said:
OK app works much better than anyone I've tried for this matter, doesn't help too too much but it does make a little bit of difference, also this should be obvious but it does slow the system down a bit, and i also had some conflicts with it changing kernel values but I'd rate it a 3.5 out of 5 for what it does though when compared to other apps four the same thing out would be a 4.5-5 not a full 5 because there has to be done room for improvement
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the info, i'll give this a try your settings.
Settings i used on the app? I just chose ai mode
Sent from my SGH-I997 using xda premium
I'd have to give this probably a 3.5 as well, could be better with a widget for one thing. I used ai most of the time, but when I went to custom mode and changed the frequency for max to 1200, it didn't change it and left it at 200. It did provide a good bit of information though!
Sent from my SGH-I997 using xda app-developers app
Slowed my phone
I unistalled this. My phone became almost useless. It was so slow and nearly unresponsive.
gabdes said:
I unistalled this. My phone became almost useless. It was so slow and nearly unresponsive.
Click to expand...
Click to collapse
Same here
Sent from my SGH-I997 using xda premium
Seems to be working pretty good on mine. Definitely added about 12hrs to my extended battery.
Sent from my SGH-I997 using xda premium
From here: http://forum.xda-developers.com/showthread.php?t=1987032
I came to that thread via LifeHacker, in which they featured it. I'm going to try this now on my freshly-updated-to-Jelly-Bean Note 10.1.
If you want to share a feedback, please post it here. If you want to thank the developer, suggest something, or buy him a beer, please post it on his thread.
APK: Click here (original direct link from his thread)
lambgx02 said:
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. :good:
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! :highfive:
Click to expand...
Click to collapse
I don't know if it's a placebo effect, but it seems that enabling this entropy seeder makes the device faster for real ^^
Does this need root?
Sent from my Nexus 4 using xda app-developers app
tuffballa said:
Does this need root?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I forgot to add.
Redemption rom 4.1.2 is pretty quick and only lag was keyboard opening.
This mod keyboard instant opening now .
jje
Sent from my GT-N8010 using xda premium
Post one on the portal has more info .
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
jje
Without reading the portal piece I guess the reason you may perceive speed up as that the device will be spending longer on higher cpu cycles by this polling.
In other words it is not a good thing for battery.
You can try playing with the governor settings to increase responsiveness, but "lag" can be caused by quite a lot of things. Random seeding shouldn't be one of them.
Sent from my GT-N7000 using Tapatalk 2
A lot of developers are stating that this is a fluke on anything running ICS+. Any boost in performance is 99% a placebo effect.
Placebo effect or not, I can notice improvement in the note general operation.
Sent from my GT-N8000 using Tapatalk HD
Disprove it or walk away.
Any dev saying it's a placebo effect needs to hold up data to prove the assertion, otherwise, the dev is just speculating. Being an Android dev can mean a variety of things, so the title doesn't grant authority.
Any dev claiming random data seeding shouldn't have an effect, should contact the APK writer and ask to see the trace logs, i.e. duplicate the experiment and verify the results. Otherwise, see above.
Everyone else, download it. Enjoy a faster UI experience. I confirm it works, which is at least as good as any dev who hasn't tested it.
--#
7April said:
Any dev saying it's a placebo effect needs to hold up data to prove the assertion, otherwise, the dev is just speculating. Being an Android dev can mean a variety of things, so the title doesn't grant authority.
Any dev claiming random data seeding shouldn't have an effect, should contact the APK writer and ask to see the trace logs, i.e. duplicate the experiment and verify the results. Otherwise, see above.
Everyone else, download it. Enjoy a faster UI experience. I confirm it works, which is at least as good as any dev who hasn't tested it.
--#
Click to expand...
Click to collapse
Have *you* checked logs to see what's happening as you claim you can see a performance hike.
I tried it on 3 devices earlier, all did exactly what I suspected. Pushed the cpu time up quite a bit, but that's what this does. It's forcing an io which causes the cpu to ramp, so of course it feels more responsive, it's starting from a higher cpu clock and less time in the lower click rates.
One of my services it caused serious slow down, die to pegging the cpu as it didn't play nicely with the particular aml quadcore governor.
Sent from my GT-N7000 using Tapatalk 2
fards said:
Have *you* checked logs to see what's happening as you claim you can see a performance hike.
I tried it on 3 devices earlier, all did exactly what I suspected. Pushed the cpu time up quite a bit, but that's what this does. It's forcing an io which causes the cpu to ramp, so of course it feels more responsive, it's starting from a higher cpu clock and less time in the lower click rates.
One of my services it caused serious slow down, die to pegging the cpu as it didn't play nicely with the particular aml quadcore governor.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Couldn't agree more with your comments, I also tested this on a variety of devices and got exactly the same results, on one of my devices I was loosing 5% battery per hour!
seeder is working on all devices?
xda just had an apology article for featuring this lol
How do you tell if which type of cpu your phone has? I've looked and can't seem to find out how to check my phone to see which I have. My cpu always seems to run hot no matter what type of kernel I try, and I'm wondering if the cpu may be slow and not capable of tweaking.
Any help someone can give me would be great.
To find out which processor you have, use Terminal Emulator from the Play Store. Reboot then type this command:
su
dmesg | grep ACPU
Here's an explanation of what this means and also recommended voltage settings for each processor type courtesy of a very knowledgeable, helpful, and great kernel dev: Imoseyon. Any "thanks" goes to him and not me for providing all this info.
Post #1341, just read Imoseyon's response to me:
http://rootzwiki.com/topic/31329-ke...11012/page__st__1340__p__1034933#entry1034933
Imoseyon post #1418 for recommended voltage settings per cpu type:
http://rootzwiki.com/topic/31329-ke...-kernel-v16-11012/page__st__1410#entry1042976
This is the output I get from that command. How am I supposed to interpret this as fas, nominal, or slow?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using xda premium
Try it again after rebooting, mine works each time
Sent from my SCH-I535 using xda app-developers app
crjjr said:
How do you tell if which type of cpu your phone has? I've looked and can't seem to find out how to check my phone to see which I have. My cpu always seems to run hot no matter what type of kernel I try, and I'm wondering if the cpu may be slow and not capable of tweaking.
Any help someone can give me would be great.
Click to expand...
Click to collapse
Found it. For anyone else that may be looking, go to this site and follow the directions. You'll need terminal installed on your phone. It works on any GS3.
http://teamuscellular.com/Forum/top...eankernel-tw-jb-imoseyon-droidroidz-usc-v141/
Finally, it worked.
Is there a performance difference between a slow CPU, a nominal CPU, and a fast CPU?
BlueCross said:
Finally, it worked.
Is there a performance difference between a slow CPU, a nominal CPU, and a fast CPU?
Click to expand...
Click to collapse
Not that I know of, you can run pretty much any kernel stock as well as adjust governors and io scheduler. The primary difference is in how much you can UC/OC or even UV/OV and how well your CPU can hold those tweaks without fear of bootlooping or instability. But as far as just flashing kernels and leaving them there, you're fine. Like I said, I'm basing this all off of what Imoseyon has said so he is WAY more knowledgeable in this area if you need additional input. This slow, nominal, fast cpu exists based on the manufacturer process so its not something you can adjust. It's permanently set with the cpu.
SlimSnoopOS said:
Not that I know of, you can run pretty much any kernel stock as well as adjust governors and io scheduler. The primary difference is in how much you can UC/OC or even UV/OV and how well your CPU can hold those tweaks without fear of bootlooping or instability. But as far as just flashing kernels and leaving them there, you're fine. Like I said, I'm basing this all off of what Imoseyon has said so he is WAY more knowledgeable in this area if you need additional input. This slow, nominal, fast cpu exists based on the manufacturer process so its not something you can adjust. It's permanently set with the cpu.
Click to expand...
Click to collapse
The basis for the difference in CPUs is the same as car Manufacturing. Part's are divided by spec tolerances. The closer to spec is the difference. In car terms GM separates parts according to how close they are to spec. Fast would go in Cadillac, Nominal Buick and slow Chevrolet. They all use the same part just have closer spec tolerance. :laugh:
prdog1 said:
The basis for the difference in CPUs is the same as car Manufacturing. Part's are divided by spec tolerances. The closer to spec is the difference. In car terms GM separates parts according to how close they are to spec. Fast would go in Cadillac, Nominal Buick and slow Chevrolet. They all use the same part just have closer spec tolerance. :laugh:
Click to expand...
Click to collapse
I can always count on this guy to drop some thorough knowledge.
Sent from my SCH-I535 using xda app-developers app
I tried this and got an error message :
sh: grep: not found
write: Broken pipe
I'm on stock rooted, and I granted the su permission.
Sent from my SCH-I535 using Tapatalk
HeadlessPonch said:
I tried this and got an error message :
sh: grep: not found
write: Broken pipe
I'm on stock rooted, and I granted the su permission.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Have to do immediately after a reboot and some custom boot animations will keep it from working.
prdog1 said:
Have to do immediately after a reboot and some custom boot animations will keep it from working.
Click to expand...
Click to collapse
No custom animation. I got rid of my lock screen to get to my homescreen faster and added a shortcut to the terminal app. I started typing as soon as the app would let me and got the same error.
Your busybox install must be borked. Download busybox free from the playstore and do a "smart install"
prdog1 said:
The basis for the difference in CPUs is the same as car Manufacturing. Part's are divided by spec tolerances. The closer to spec is the difference. In car terms GM separates parts according to how close they are to spec. Fast would go in Cadillac, Nominal Buick and slow Chevrolet. They all use the same part just have closer spec tolerance. :laugh:
Click to expand...
Click to collapse
As a general rule, CPUs that come off the same fab are tested and then placed into different "bins", based on how they perform at different speeds and voltages. The better performing "top bin", chips get rated and sold at the highest clock speed. The slower chips get a lower clock speed assigned, and are sold at a lower price.
This method works well for AMD and Intel, who both sell a wide range of clock speeds for a particular generation CPU at different price points. It eliminates waste by enabling them to sell the lower performing chips instead of rejecting or destroying them, and allows them to offer different price points which is beneficial from a marketing perspective.
With phones, the CPUs are often clocked the same (e.g. [email protected] 1.5 GHz), but the CPUs still range in capability depending on their mfg tolerances, and in the case of our Snapdragon S2s, they are tagged accordingly. Whether you end up with a slow or fast chip in your phone is totally random, but frequently your chances of getting a faster chip increase over time as the fab process is fine tuned, and chip yields go up.
That doesn't mean you can't get a fast CPU right off the bat. For example, I pre-ordered mine on day 1 (June 6th?) and still got a fast CPU.
x714x said:
Your busybox install must be borked. Download busybox free from the playstore and do a "smart install"
Click to expand...
Click to collapse
That worked, thanks!
Now I know I'm nominal. The first line says "ACPU PVS: [1],FMAX[0]". It's different from the other 2 posted results in this thread (all 3 are actually different). What do those numbers mean?
I was lucky enough to have a fast CPU; which values on those charts do I want? I opened Kernel Turner and went to "Voltage" and it is a bunch of weird numbers--and I see something for "-1.5 across board," how many times should I hit that? I'm assuming that's how you undervolt.
Kelton Rivas said:
I was lucky enough to have a fast CPU; which values on those charts do I want? I opened Kernel Turner and went to "Voltage" and it is a bunch of weird numbers--and I see something for "-1.5 across board," how many times should I hit that? I'm assuming that's how you undervolt.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36743286
Would this apply for his aosp kernel as well? The 4.2 kernel?
Sent from my SCH-I535 using xda premium
Hi,
First post in this forum in a long time. Or maybe ever.
Not sure if this is the right place to ask this, I'm new to this ROM, and had a stable one in my Thunderbolt, so was away from flashing for almost a year. Just got a vz S3, rooted it as soon as I got home, and after doing some research, decided on Liquid Smooth. Downloaded Liquid-JB-v2.1-Beta3.1-d2vzw this morning, so whatever the latest version as of this morning (Jan 23) is what I flashed. Also got the correct gapps. All went well, and so far, I like what I've seen. (Thanks, developers, this has been the EASIEST flash to a new rom I've ever done.
One problem, and I hope someone can point me in the right direction, as I'm googled out on trying to find a solution.
When I go to settings, performance, current, or, maximum CPU frequency, the highest it goes it 1512. The youtube videos on this show choices up to 1900.
Can anyone point me in the right direction on this?
Thank you.
---------- Post added at 01:54 AM ---------- Previous post was at 01:46 AM ----------
Just installed Setcpu, and it would not allow (nor show) any setting higher than 1512.
Thanks again for any insight.
tprophit said:
Hi,
First post in this forum in a long time. Or maybe ever.
Not sure if this is the right place to ask this, I'm new to this ROM, and had a stable one in my Thunderbolt, so was away from flashing for almost a year. Just got a vz S3, rooted it as soon as I got home, and after doing some research, decided on Liquid Smooth. Downloaded Liquid-JB-v2.1-Beta3.1-d2vzw this morning, so whatever the latest version as of this morning (Jan 23) is what I flashed. Also got the correct gapps. All went well, and so far, I like what I've seen. (Thanks, developers, this has been the EASIEST flash to a new rom I've ever done.
One problem, and I hope someone can point me in the right direction, as I'm googled out on trying to find a solution.
When I go to settings, performance, current, or, maximum CPU frequency, the highest it goes it 1512. The youtube videos on this show choices up to 1900.
Can anyone point me in the right direction on this?
Thank you.
Click to expand...
Click to collapse
tprophit said:
Hi,
First post in this forum in a long time. Or maybe ever.
Not sure if this is the right place to ask this, I'm new to this ROM, and had a stable one in my Thunderbolt, so was away from flashing for almost a year. Just got a vz S3, rooted it as soon as I got home, and after doing some research, decided on Liquid Smooth. Downloaded Liquid-JB-v2.1-Beta3.1-d2vzw this morning, so whatever the latest version as of this morning (Jan 23) is what I flashed. Also got the correct gapps. All went well, and so far, I like what I've seen. (Thanks, developers, this has been the EASIEST flash to a new rom I've ever done.
One problem, and I hope someone can point me in the right direction, as I'm googled out on trying to find a solution.
When I go to settings, performance, current, or, maximum CPU frequency, the highest it goes it 1512. The youtube videos on this show choices up to 1900.
Can anyone point me in the right direction on this?
Thank you.
---------- Post added at 01:54 AM ---------- Previous post was at 01:46 AM ----------
Just installed Setcpu, and it would not allow (nor show) any setting higher than 1512.
Thanks again for any insight.
Click to expand...
Click to collapse
You need to run a custom kernel that is overclockable. The stock kernel on liquid isnt overclockable from what I remember.
---------- Post added at 11:24 AM ---------- Previous post was at 11:23 AM ----------
BlueCross said:
Would this apply for his aosp kernel as well? The 4.2 kernel?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ya, its hardware level so it doesnt make a difference what rom you are running.