After reading the general forum a bit, I stumbled across a post from someone using the Seeder APK [Root required] to help mitigate some of the lag/stutter/UI weirdness some of us are seeing on the G3.
I had never heard of this app before, so I looked into it and found out more here.
I downloaded the APK and turned it all the way up. I enabled all it's options and let it work; and well it did. Specifically I saw a reduction in stutter when flipping to the recent apps screen, and generally improved performance with other UI animations like scrolling. Some are even reporting better performance with how third party keyboards animate and respond, a problem I had run into using Swiftkey.
I cannot explain why this is working and apparently neither can the developer, because the newer versions of Android do not handle the processes this is supposed to address in the same way. Give the thread a read and try it out, so far its made a difference for me and I'm happy with it. :laugh:
I've used seeder for a long time now over 3 different phones and it always seems to do the trick. I have been getting some laggy animations on the G3 (why can't these companies focus on making the experience smooth throughout :/ ) and seeder has seem to reduce the lag the most. I'm surprised how choppy the animations are on the G3 at times because my G2 ran like a dream most the time. I expected more from the G3 though it's still a great phone that imo is much better than the m8 and s5. I mostly assume it's down to the screen res and size and the fact that apps and android itself is becoming more and more resource hungry. I guarantee if you put ASOP 4.0-4.3 on this thing it would fly.
Do we download the latest apk from that forum you are providing?
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
I don't know which forum to get it from. when I click where it says "here" that jumps into to the middle of another forum there's another link on that forum also to another forum
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
sorry I believe I got it, in downloading seeder 2.0.0
It's been debunked by Google itself and there is no empirical evidence that it works at all.
edit: https://code.google.com/p/android/issues/detail?id=42265
and
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
scy1192 said:
It's been debunked by Google itself and there is no empirical evidence that it works at all.
edit: https://code.google.com/p/android/issues/detail?id=42265
and
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
Click to expand...
Click to collapse
I have read that, however despite that information I do perceive a difference and no its not a placebo. I understand that the professionals cannot substantiate a change. All that I can suggest is that anyone that has a complaint regarding the G3 and laggy behavior...give this a shot. If it doesn't work, chuck it....if it does great!
Understanding why is works? Hmm yeah Id love to know.
SJUnion said:
I have read that, however despite that information I do perceive a difference and no its not a placebo.
Understanding why is works? Hmm yeah Id love to know.
Click to expand...
Click to collapse
There's no way you would be able to tell if it was placebo effect or not without a double blind study or some evidence to backup your claim other than observation.
bobbarker2 said:
There's no way you would be able to tell if it was placebo effect or not without a double blind study or some evidence to backup your claim other than observation.
Click to expand...
Click to collapse
Ok. Does that mean your not gonna try it?
Well, I can confirm that it works well for me. I can see significant difference right away. Thanks for @SJUnion for shearing.
Sent from my VS985 4G using XDA Premium 4 mobile app
I don't know about anyone else but it did work for me. I can significantly noticed the difference
I have to agree, there is a significant improvement for me as well.
Sent from my VS985 4G using Tapatalk
Yes their is a very much of improvement of speed/no lag after installing, #mysimplepleasure
Sent from my VS985 4G using XDA Premium 4 mobile app
Hooray for seeder!
People always try to debunk the fact that seeder works but the reviews in the google play store and my eyes have always told me otherwise. When a phone is very clearly lagging and then you install seeder and notice the change right after I don't think we need any experts to tell us our own eyes and mind are deceiving us. Experts have made a living off being wrong about things.
What Seeder settings is everyone running?
Wot-75 said:
What Seeder settings is everyone running?
Click to expand...
Click to collapse
Aggressive, everything on. I don't think it does much to be honest.. but until they fix the launcher.. I wouldn't mind throwing whatever I can at it. For me, everything's good..but there's a definite loading lag when in the app drawer (the first time in it) or tapatalk (sometimes).. but the launcher home pages I'm all good..
SJUnion said:
I have read that, however despite that information I do perceive a difference and no its not a placebo. I understand that the professionals cannot substantiate a change. All that I can suggest is that anyone that has a complaint regarding the G3 and laggy behavior...give this a shot. If it doesn't work, chuck it....if it does great!
Understanding why is works? Hmm yeah Id love to know.
Click to expand...
Click to collapse
I've tried it on two phones and... I could find no difference that it made.
Disabling the Amazon apps fixed my lag issues.
Btw. Verizon puts that crap on their phones not LG so you can thank Verizon for the lag.
I have noticed while entering text in the text box in these forums that it does not update the typing.until I click back on the text box. Anyone else get that? Chrome BTW..
SJUnion said:
Ok. Does that mean your not gonna try it?
Click to expand...
Click to collapse
I've tried entropy generators in the past before I knew more about the subject and never saw a difference. This is programming, not magic. We know what Seeder does and we know how android works
The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random… well… less random
Click to expand...
Click to collapse
I tried the symlink method and could not detect any appreciable change in load averages under otherwise similar usage scenarios. I cannot find evidence of access to the /dev/random file. I cannot find similar wait paths in the kernel code that accesses the entropy pool that is shared by /dev/(random/random). That leaves other kernel locking or blocking mechanisms (spinlocks?) if there really is a responsiveness boost. I haven't seen conclusive evidence either way, I am just trying to understand what would possibly influence responsiveness should this hack prove founded in data.
Click to expand...
Click to collapse
I'm sorry why no one is mentioning this, but the 'fix' involves running a daemon that writes to /dev/random every second. This daemon should affect the CPU freq governor and make the CPU run at higher clocks than a device without the daemon. This alone would account for the performance increase users claim to be experiencing.
I've played with CPU frequency governors in the past. Perception of lag is affected greatly by this.
The claims about the depleted entropy pool leading to lower performance are not substantiated. I am thinking that there shouldn't be such a huge dependency on /dev/random in Android to cause an appreciable performance difference.
Click to expand...
Click to collapse
bobbarker2 said:
I've tried entropy generators in the past before I knew more about the subject and never saw a difference. This is programming, not magic. We know what Seeder does and we know how android works
Click to expand...
Click to collapse
No problem Bob, and I understand where your coming from. Thanks for inserting logical analysis into this discussion, and for sharing what is known and understood about this apk.
Does that mean I will stop using it? No, because it works for me. Do I encourage others to try it? Yes, for the same reason. Do I accept that there are many that wouldn't even glance at this because its not supposed to work?...Yes. No big, I'm not the developer.
Afterthoughts..
From what I can glean I think this is what we may be seeing here - "I've played with CPU frequency governors in the past. Perception of lag is affected greatly by this."
Can we do this currently? I mean change CPU frequencies without an unlocked boot-loader and a custom ROM?
I just wonder how all this is affecting your battery life. Has anyone done any research into how these effect wake time and battery performance? Seems to be the idea is if you keep the cpu a bit active you get better performance? It seems to me that if that is the case then a less aggressive cpu governor would have the same or better effect on reducing lag. At least that is was I perceive after reading about entropy regarding cpu and different platforms. Linux and windows generate random numbers differently.
Turn on developer options.
Look in the options settings.
Set all animation values to .5x
Related
OK, I have written an app to attempt and stop call wonkyness on CM7 builds. Specifically the phone locking up when making and receiving calls.
It's my observation that it's the mic that causes the phone to lock up and so this app opens and closes the mic every minute to keep it "fresh". It's a long shot, but I can't seem to duplicate wonkyness with it enabled so I'm posting it for other to try.
Now after a few positive comments to help boost my confidence in the app, I've made it's own thread to make it easy to track comments.
Just install and run (or just reboot as it auto-start on boot). To disable, uninstall it.
Please post your results!
Change Log:
Version 1.4
Made service more persistent by adding notification bar. Turns out, Android was killing off the service when memory was running low causing wonk to surface.
Version 1.3
Can only be installed on internal memory. Needed to make sure the service can started up on boot. (Thanks to mjukis for pointing this out)
Version 1.2
Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.
Removed debug logging
[Post edited because the wonkyness is still there and this .apk works fine to fix it]
Dude.... As best as I can tell in 20 minutes' time, this damn thing seems to actually work! Gotta tell ya how skeptical I was....but I'm pretty flippin' pleased right now!
Good looking out!!
Much appreciated for this app.
While it's still too early to say it's 100% working, so far so good.
I have had the wonk since build 3 to 23 (except for 16).
I will keep testing and report back often.
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Agree with the op. Can't say for sure its the miracle I've been waiting for... but 4 calls in (admittedly 2 from myself, ) no wonks. When I'd expect all to be wonky
If this 'wonklessisity' continues you will surely become supreme ruler of xda!
Will report back soon.
Sent from my Nexus One using XDA App
TheMasterBaron said:
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Click to expand...
Click to collapse
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Does this fix it?
http://review.cyanogenmod.com/#change,2642
shaggy-h said:
Does this fix it?
http://review.cyanogenmod.com/#change,2642
Click to expand...
Click to collapse
No, that's a different problem.
Sent from my Nexus One using Tapatalk
makelegs said:
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Click to expand...
Click to collapse
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
I also believe it have something to do with the mic, since all apps that use it have the same freeze, and it seems to work for me. Thanks
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Seems reasonable enough, to me.
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Maybe watchdog would be a better app for checking. Would give us a better idea of CPU use. Also juice plotter may help see prior and after install battery consumption
I've tested it,and havent got any wongkiness for today. I think its working...
Sent from my Nexus One using XDA App
Got source?
fitsnugly said:
Got source?
Click to expand...
Click to collapse
Added to the OP
TheMasterBaron said:
Added to the OP
Click to expand...
Click to collapse
gracias!
You deserve an E-Cookie for coming up with such an awesome name
Wonky just visited me when my wife called. Installed your dewonky app for testing.
Thanks.
This bug is the reason I got off CM7 nightlies, so damn annoying. Maybe this is a Gingerbread thing rather than a Nexus S problem cause the Nexus S is supposed to be rebooting itself while in calls as I'm sure everyone knows.
So I followed the instructions in the v6 SuperCharger script thread and the phone is wicked fast now, virtually no lag whatsoever. But I have what appears to be a battery drain issue. Spare Parts and SystemPanel let me zero in on a process called "zygote" which was consuming 30% of the CPU even when the screen was off. I may try disabling the script to see what happens but I'd hate to go back to the stock laggy experience.
Does anyone know what zygote does or is for and why it would keep running continuously? Are the new memory values causing the phone to keep shifting around apps/processes to maintain the minimum free memory and this is using up CPU and therefore battery?
Eric
Which areas on the phone were you noticing considerable lag?
Did you also figure out what the process was and why it was taking up so many cycles?
PnoT said:
Which areas on the phone were you noticing considerable lag?
Did you also figure out what the process was and why it was taking up so many cycles?
Click to expand...
Click to collapse
Are you asking me? The process is called "zygote" in SystemPanel. Under Spare Parts, Android System was shown as keeping the phone awake.
The original lag I was experiencing was within various apps and also ADW Launcher flipping between homescreens.
Eric
I was intrigued and googled it. The best answer I found without too much digging was here:
http://groups.google.com/group/android-discuss/browse_thread/thread/fa8a9e3f3b891b0d/44b3bb43d0aa783a
But by that explanation it doesnt seem like zygote should be using that much cpu. Perhaps this script changes its behavior?
Still surprised people do not have red flags for concern in regards to having to use this app in the first place. People are having to use an app designed for low memory devices (256mb) on a device with 512mb. gTablet has 512mb, Tegra 2, Froyo as well, but does NOT have these problems and performs much better (never thought I would say that, but the gtablet DOES perform MUCH better).
That said, if the mystery of the low ram issue, audio pops and random reboots are fixed in an update- the DX2 will be great (IMO). Had the DX2 for two weeks and wanted to keep it, but the issues mentioned were not worth messing with. Having the similar software and hardware on the gTablet gave me a source for comparing and realizing something is wrong with the DX2's firmware.
Not to hijack, but when you get to this part in the Tutorial, which setting should one choose for the x2?
"Touch the screen and tap the number 6, Balanced 3, the best choice for GT540, and hit ENTER .... The script will work .... after finished, touch the screen again and tap the number 16"
digital0verdose said:
Not to hijack, but when you get to this part in the Tutorial, which setting should one choose for the x2?
Click to expand...
Click to collapse
"9 MegaMemory Device"
assuming you're using update2
YMMV
theguru1974 said:
So I followed the instructions in the v6 SuperCharger script thread and the phone is wicked fast now, virtually no lag whatsoever. But I have what appears to be a battery drain issue. Spare Parts and SystemPanel let me zero in on a process called "zygote" which was consuming 30% of the CPU even when the screen was off. I may try disabling the script to see what happens but I'd hate to go back to the stock laggy experience.
Does anyone know what zygote does or is for and why it would keep running continuously? Are the new memory values causing the phone to keep shifting around apps/processes to maintain the minimum free memory and this is using up CPU and therefore battery?
Eric
Click to expand...
Click to collapse
Any resolution on this guru? I'm having the exact same issue.
rushless said:
Still surprised people do not have red flags for concern in regards to having to use this app in the first place. People are having to use an app designed for low memory devices (256mb) on a device with 512mb. gTablet has 512mb, Tegra 2, Froyo as well, but does NOT have these problems and performs much better (never thought I would say that, but the gtablet DOES perform MUCH better).
That said, if the mystery of the low ram issue, audio pops and random reboots are fixed in an update- the DX2 will be great (IMO). Had the DX2 for two weeks and wanted to keep it, but the issues mentioned were not worth messing with. Having the similar software and hardware on the gTablet gave me a source for comparing and realizing something is wrong with the DX2's firmware.
Click to expand...
Click to collapse
You're an idiot.
I've told you a few times already that the script fixes badly configured memory management no matter what the device.
The minfrees is a secondary to the primary function - fixing OOM groupings and priorities for optimal performance.
Is an app like AKMO or AMM only good for 256 mb devices?
No, they aren't. But all they do is change minfree values.
So don't be so stupid.
And for those that think it's causing battery drain, unsupercharge.
You will still have battery drain and the phone will be slower.
zeppelinrox said:
You're an idiot.
I've told you a few times already that the script fixes badly configured memory management no matter what the device.
The minfrees is a secondary to the primary function - fixing OOM groupings and priorities for optimal performance.
Is an app like AKMO or AMM only good for 256 mb devices?
No, they aren't. But all they do is change minfree values.
So don't be so stupid.
And for those that think it's causing battery drain, unsupercharge.
You will still have battery drain and the phone will be slower.
Click to expand...
Click to collapse
You appear to be a rude individual who disgraces Led Zep and showed be forced to change your icon to Vanilla Ice
The DX2 should NOT require to be managed for low ram. gTablet has none of these issues and besides some telephony tasks, has the same hardware and software setup as the DX2- none of the issues and no need to have to manage low operational ram. Seems the DX2 does not truly have 512mb of FUNCTIONAL ram, hence the need to run non standard scripts. For folks that do not root, they are SCREWED due to pi55 poor firmware by Motorola.
Start being nicer to people and you can keep your Led Zep icon with honor/honour.
zeppelinrox said:
You're an idiot.
I've told you a few times already that the script fixes badly configured memory management no matter what the device.
The minfrees is a secondary to the primary function - fixing OOM groupings and priorities for optimal performance.
Is an app like AKMO or AMM only good for 256 mb devices?
No, they aren't. But all they do is change minfree values.
So don't be so stupid.
And for those that think it's causing battery drain, unsupercharge.
You will still have battery drain and the phone will be slower.
Click to expand...
Click to collapse
I tend to agree with you on this. Having dealt with hardware for 25+ years, rarely does the hardware come optimized to a truly great point. Some are definitely worse than others, but there can still be improvements.
Expecting a perfectly optimized piece of hardware/software from any company seems bit foolish. Fortunately the community that uses the hardware are generally the best at getting it to it's best state, regardless of what those who like to drink the koolaid might say.
In any case, I ran this on my X2 and everything had been tip-top since. I have not seen this Zygote issue and I used option 9.
digital0verdose said:
I tend to agree with you on this. Having dealt with hardware for 25+ years, rarely does the hardware come optimized to a truly great point. Some are definitely worse than others, but there can still be improvements.
Expecting a perfectly optimized piece of hardware/software from any company seems bit foolish. Fortunately the community that uses the hardware are generally the best at getting it to it's best state, regardless of what those who like to drink the koolaid might say.
In any case, I ran this on my X2 and everything had been tip-top since. I have not seen this Zygote issue and I used option 9.
Click to expand...
Click to collapse
Not seeing/tasting the koolaid here. Very simple point that out of box, the DX2 has to be managed like a 256mb ram device. I have been around a tad too and have my undergrad in computer electronics (so far back, we still used Tandy's to program eeproms then) so have a teeny bit of subject matter appreciation.
The points were never about the script, but the device itself. Out of box, the device operates with low ram- just like the Droid 1 (which I also owned). Back then, no problem, since 2.1 and lower only really used 256mb ram and the Droid 1 was (IMO) ten times better than the G1 that I also bought at launch.
For as long as there have been computers, people have been tweaking them.
Tell me, does each windows computer sold have a different memory configuration depending on ram?
No, its managed the same across the board.
Same thing with android.
I've been tweaking them since I had a pentium 90..ya... 90mhz with windows95.
You got rid of it and still troll forums as your new hobby.
No, you didn't drink the koolaid.
You tried V6 with low ram values, ignored my suggested megamemory settings, returned the phone, and troll and whine every chance you get about it.
So stop being an ignorant suck and enjoy your new whatever...
Oh yeah... I can be rude... big deal.
Just like you can be ignorant.
I just have a low tolerance to intentional ignorance.
You still spew stuff about 256mb device settings despite the fact that the script has megamemory device settings while the main feature is fixing the notoriously bad memory configuration of gingerbread on ALL devices.
If you can't grasp that, you're stupid too.
Sent from my Milestone using Tapatalk
zeppelinrox said:
For as long as there have been computers, people have been tweaking them.
Tell me, does each windows computer sold have a different memory configuration depending on ram?
No, its managed the same across the board.
Same thing with android.
I've been tweaking them since I had a pentium 90..ya... 90mhz with windows95.
You got rid of it and still troll forums as your new hobby.
No, you didn't drink the koolaid.
You tried V6 with low ram values, ignored my suggested megamemory settings, returned the phone, and troll and whine every chance you get about it.
So stop being an ignorant suck and enjoy your new whatever...
Oh yeah... I can be rude... big deal.
Just like you can be ignorant.
I just have a low tolerance to intentional ignorance.
You still spew stuff about 256mb device settings despite the fact that the script has megamemory device settings while the main feature is fixing the notoriously bad memory configuration of gingerbread on ALL devices.
If you can't grasp that, you're stupid too.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
To think I spent years in the Marines defending the rights of free speech for smack talkers like yourself
Based on your retorts and recalcitrant position, it seems you have everything figured out.
Bonzo would NOT approve of your attitude, nor the DX2 firmware.
yep, telling it like it is is not always popular, just ask Howard Cosell.
Btw why do you think musical artists are gods or religious figures or something?
That's so misguided. heh.
Oh yeah, there's the zep bio called Hammer of the Gods... I've read it and they aren't really gods lol
But they swung a mean hammer so maybe I do the name justice after all
I found this today on reddit, thought I'd share it with everyone. All credit goes to Lambgx02
I'm running this on CM10 and I've noticed a difference.
Link to OP & Download
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
Click to expand...
Click to collapse
Thank you OP. ...
I'm going to get the playstore version for support purposes ...regardless of the xda report.
The developer worked hard on this. ...g
Tried it out, noticed an immediate, significant improvement!! If that was a placebo, the OP must have played it up to be a damn good one
I might be crazy (and I'm sure it's just a coincidence) but I seemed to notice an actual IMPROVEMENT in battery life after installing this.
Thanks for sharing!
I'm not sure if I've noticed any major improvement myself, but it has been a little zippier. I keep a very close eye on my battery, so I should be able to report any battery improvements. Hopefully I didn't waste a 1.50 on this app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
CPA Poke said:
Tried it out, noticed an immediate, significant improvement!! If that was a placebo, the OP must have played it up to be a damn good one
I might be crazy (and I'm sure it's just a coincidence) but I seemed to notice an actual IMPROVEMENT in battery life after installing this.
Click to expand...
Click to collapse
If you're using the apk method, it's literally impossible to have better battery life as mentioned by the guy who made it. It keeps your device awake a lot more often to refill the entropy. The difference may be small enough that it won't affect you but it can't actually increase your battery life.
I've been trying the apk method as well as the other ones without really seeing any concrete difference. Currently running the sysctl method since it's "free" and doesn't use any system resources.
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/ just a heads up
ChronoReverse said:
If you're using the apk method, it's literally impossible to have better battery life as mentioned by the guy who made it. It keeps your device awake a lot more often to refill the entropy. The difference may be small enough that it won't affect you but it can't actually increase your battery life.
I've been trying the apk method as well as the other ones without really seeing any concrete difference. Currently running the sysctl method since it's "free" and doesn't use any system resources.
Click to expand...
Click to collapse
Haha yeah, that's why I said it was probably a coincidence Said battery "improvement" has since gone away, but my device still seems to be much snappier.
Been on it since its release and it has improved my phone. I will say, don't subscribe to the main thread though, omg notification every 2 secs....its crazy....well it has slowed down slightly but wow
Well. ..
Based on the report by arcee, whom I trust as being a top tier development expert, Im going to shut down the application.
His report is accurate in disecting the hack.
The resources used to run the hack, obviously outweigh the benefits.
It's a near placebo effect modification with no tangible performance advantage beyond what the CPU can already produce with governors and clocking tweaks.
None the less, I do believe the developer to be honest in his attempt in bringing us a well executed application with sincere intentions.
That being said, a thank you is still in order, and a small price of $1.50 is certainly not to high a price considering the work and coding involved. ...g
NO. This does NOTHING. Stop it, people.
Its been a night and day difference on my phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
Another tweak is always great. Thanks for the contribution.
Sent from my SAMSUNG-SGH-I717
Tasty placebo... Seriously, people are still doing this? I thought all the threads were closed as nonsense.
Agreed ..please close this thread...
The mod does nothing...and has been confirmed by XDA ..g
Edit: reported ....people, don't waste your money.
As stated on XDA: http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
As is always the case, anything you use here on XDA is done at your own risk, and you assume all liability for your actions. That said, there are times we pass on inaccurate information, and this is one of those times. We do applaud all of our developers for working to find fixes for the things that nag at them. However, we jumped the gun on this, without letting adequate discussion and testing take place.
Click to expand...
Click to collapse
Title says all. If possible, to how much can you overclock it?
Honestly, I don't know why you would overclock for anything other than bragging rights. this thing is fast.
All it needs is for the software to be optimized.
Undervolt is always good too.
Sorry for not really answering your question, but i'm sure it's possible. I mean, if you can undervolt, I'm sure you can overvolt and mess with the multiplier and all that jazz.
http://forum.xda-developers.com/showthread.php?t=2012320
That is what I'm talking about. International only though.
From what I've gathered from reading various posts, it is generally frowned upon as a bad idea for a variety of reasons, ultimately coming down to it will end up damaging your phone one way or another. So, yeah, of course, I'm sure you could find a way to do it, but if it were me I wouldn't(and this is coming from someone who overclocked every modern phone he's had except this one).
Once I see the trusted devs talking about it and saying it's a good idea...that's when I'll try it. Just my 2 cents.
SunnyChrono6 said:
Title says all. If possible, to how much can you overclock it?
Click to expand...
Click to collapse
well - if it behaves like the hox
you should be able to get about +15%
but why you want to do that at all
normally you only underclock this battery eater
Sent from my HTC One X+ using xda app-developers app
Well I haven't found a way. Besides, I think the phone would heat up to much anyways.
sixcarnage said:
Well I haven't found a way. Besides, I think the phone would heat up to much anyways.
Click to expand...
Click to collapse
well - no kernel is supporting it
so it will be hard for you to find a way
Sent from my HTC One X+ using xda app-developers app
Have you ever actually run into a situation where the phone does not have enough cpu power? I know I haven't but there have been many situations where I wished I if more battery Mah, what you really want to overclock is the gpu which is stable running at about 600mhz. The main reason why the cpu might not perform well is due to the cpu getting stuck in single core mode or failing to scale properly, just head over to nik3r's or maxwen's kernel threads and flash the latest version.
ryanjsoo said:
Have you ever actually run into a situation where the phone does not have enough cpu power? I know I haven't but there have been many situations where I wished I if more battery Mah, what you really want to overclock is the gpu which is stable running at about 600mhz. The main reason why the cpu might not perform well is due to the cpu getting stuck in single core mode or failing to scale properly, just head over to nik3r's or maxwen's kernel threads and flash the latest version.
Click to expand...
Click to collapse
Overclocking and people with EOS (Extreme Overclocking syndrome) care little about if they need the extra power for a purpose. There sole mission is to push a CPU as far as they dare without frying it
This is fine with a PC, as PC's have all manner of 3rd party cooling solutions. But I totally agree with everyone that trying to overclock the HOX+ CPU is futile and borderline stupid. It struggles to keep itself cool at the best of times. Putting the CPU through extra thermal stress for no reason and to gain little in the way of performance is not something I would risk....
---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------
maxwen said:
well - no kernel is supporting it
so it will be hard for you to find a way
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Without being a ****.... He could just try and compile his own kernel. There are plenty of tuts on the subject and setting up the environment is not too difficult :silly:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
try flash custom kernel..the memory management is very good with custom kernel
Sent from my Nexus 9 using Tapatalk
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Choochter said:
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Click to expand...
Click to collapse
Firstly, you need to face the fact that 2GB was a bad decision by Google for this tablet. There is nothing that we can ever do about that. :crying:
If you want to stay on stock, Chrome is the main culprit in consuming Ram. Switching to Habit Browser makes things better as well as changing your DPI to 288. Do a search on XDA regarding this. Whilst it improved things, it was still not enough for me.
I snapped a week ago and have now rooted and flashed CM13 and stuck with Habit. I've been using a few days now, and for the first time, I can keep my 3 Fantasy Premier League Tabs open, (they are huge,) without constant refreshes, redraws and lag. :victory: Right now, I feel for the first time, I'm getting what I paid for and the Nexus Experience. The only bug so far, is that always listening doesn't work.
If you've just bought this tablet, I'd consider returning it if you are not prepared to root. The performance will never be acceptable on stock.
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
Clearing dalvik cache will do precisely ONE thing and ONLY one thing; make it take a long time to boot next time as it regenerates it.
Ignore the amount of available memory. People who are concerned about the amount of free memory are trying to apply bad mswindows knowledge to Android. Totally different and no comparison. UNUSED MEMORY IS WASTED MEMORY!!!
So here is how memory management works in Android; it *preloads* everything that it thinks you are most likely to actually use, so that when you DO use it, it is more likely already loaded and starts up very quickly. If you are switching to something that is NOT already loaded, then it just needs to dump lower priority programs out of memory, which basically only takes a few nanoseconds (billionths of a second). So that is NOT it.
If your device is acting slowly, then you need to figure out what the actual cause is. Trace the CPU utilization with something like the "top" command (the one with busybox is a lot nicer than the one that comes with Android) while you are experiencing slowdown. You can also look to see if there is excessive I/O happening (i.e. read/write to the internal storage), and of course, some software will require a network exchange before it will start up -- nothing you can do about network lags.
kacang87 said:
try flash custom kernel..the memory management is very good with custom kernel
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Thanks. I am still on the official rom, I probably should switch.
Choochter said:
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Click to expand...
Click to collapse
I have done it several times. As I said, I really have not so many apps and just the very common google apps are installed.
Masteryates said:
Firstly, you need to face the fact that 2GB was a bad decision by Google for this tablet. There is nothing that we can ever do about that. :crying:
If you want to stay on stock, Chrome is the main culprit in consuming Ram. Switching to Habit Browser makes things better as well as changing your DPI to 288. Do a search on XDA regarding this. Whilst it improved things, it was still not enough for me.
I snapped a week ago and have now rooted and flashed CM13 and stuck with Habit. I've been using a few days now, and for the first time, I can keep my 3 Fantasy Premier League Tabs open, (they are huge,) without constant refreshes, redraws and lag. :victory: Right now, I feel for the first time, I'm getting what I paid for and the Nexus Experience. The only bug so far, is that always listening doesn't work.
If you've just bought this tablet, I'd consider returning it if you are not prepared to root. The performance will never be acceptable on stock.
Click to expand...
Click to collapse
Thanks for your reply. Yeah, most of the times, the slow down happens while I am in chrome and browsing..it actually is not snappy at all in internet browsing...however, I remember it was back in the days that I had bought it.
No, I have this Nexus 9 since last May I think, but have not yet found the time to root it and flash a custom kernel and rom . Anywyas, I have done it previously for my other devices, so not that much rookie in it. Probably will give it a try,
doitright said:
Clearing dalvik cache will do precisely ONE thing and ONLY one thing; make it take a long time to boot next time as it regenerates it.
Ignore the amount of available memory. People who are concerned about the amount of free memory are trying to apply bad mswindows knowledge to Android. Totally different and no comparison. UNUSED MEMORY IS WASTED MEMORY!!!
So here is how memory management works in Android; it *preloads* everything that it thinks you are most likely to actually use, so that when you DO use it, it is more likely already loaded and starts up very quickly. If you are switching to something that is NOT already loaded, then it just needs to dump lower priority programs out of memory, which basically only takes a few nanoseconds (billionths of a second). So that is NOT it.
If your device is acting slowly, then you need to figure out what the actual cause is. Trace the CPU utilization with something like the "top" command (the one with busybox is a lot nicer than the one that comes with Android) while you are experiencing slowdown. You can also look to see if there is excessive I/O happening (i.e. read/write to the internal storage), and of course, some software will require a network exchange before it will start up -- nothing you can do about network lags.
Click to expand...
Click to collapse
Thanks for your kind reply and explanation.
I think that is exactly the problem as even sometimes switching between the apps that I have just opened is also so slow and the nexus lags badly....Yes, I am aware of the network lags, but the problem I was talking about does not have anything to do with it...I will try the command you said, but can I run it on stock rom? I have not yet rooted my nexus nor flashed a custom rom.
Thanks
arminvm said:
Thanks for your kind reply and explanation.
I think that is exactly the problem as even sometimes switching between the apps that I have just opened is also so slow and the nexus lags badly....Yes, I am aware of the network lags, but the problem I was talking about does not have anything to do with it...I will try the command you said, but can I run it on stock rom? I have not yet rooted my nexus nor flashed a custom rom.
You can do some investigation by watching the processes and seeing which are taking the CPU and memory on stock. The problem is, when you find out, there isn't much you can do about it.
Thanks
Click to expand...
Click to collapse
You can do some investigation by watching the processes and seeing which are taking the CPU and memory on stock. The problem is, when you find out, there isn't much you can do about it.
Its quicker and easier to just install a custom rom where this type of work has already been done for you. :victory:
Lately, I've discovered that loading Chrome immediately raises my CPU temp by 30+ degrees. Sometimes that's enough to make things run really slow
Yeah, I agree...I will try to fimd sometime amd go over flashing a custom rom. ??
Yes! I habe noticed that these slow downs mostly happen when I am browsing in Chrome...
Web browsers are DEFINITELY a source of slowdowns.
The problem, more often than not, is actually *javascript* that is written by MORONS. Even on a desktop machine, you can watch the web browser for CPU and RAM utilization, and it just grows and grows and grows until you finally kill the process and start a new one.
What this may come down to is actually quite simple; the CPU in the Nexus 9 is actually more suitable for use as a stovetop than an actual CPU. These things get way too hot way too fast. If you beat on them with a web browser, they'll get hot and throttle down to low/verylow frequency, which will make them generally unresponsive. So if that is what is happening to you, there really end up being a few options to deal with it;
1) disable javascript in the browser,
2) don't use the browser,
3) improve the ability to disperse heat from the CPU.
For #3, you may note that when it gets hot, it is pretty localized to the corner of the device up near the power button. An easy solution to distribute heat better might be something simple, like adding a layer of copper foil to the inside of the back cover. The thicker the copper foil the better. Copper is very good at conducting heat, so this would spread the heat around over the entire area covered by that foil. http://www.ebay.com/itm/Copper-Foil...nductive-Adhesive-Ship-from-USA-/162018486132
I also found chrome was slow starting up, switching tabs etc. Found that logging out of my Google account in chrome improved this. Seems that synching tabs etc triggers the pause. This might be an acceptable workaround for some but I appreciate it isn't a great fix if you want to use that feature. Actually I'm not bothered as I think Google know too much anyway. �� But the underlying problem is this tablet... I don't have this problem on my phone.
doitright said:
Web browsers are DEFINITELY a source of slowdowns.
The problem, more often than not, is actually *javascript* that is written by MORONS. Even on a desktop machine, you can watch the web browser for CPU and RAM utilization, and it just grows and grows and grows until you finally kill the process and start a new one.
What this may come down to is actually quite simple; the CPU in the Nexus 9 is actually more suitable for use as a stovetop than an actual CPU. These things get way too hot way too fast. If you beat on them with a web browser, they'll get hot and throttle down to low/verylow frequency, which will make them generally unresponsive. So if that is what is happening to you, there really end up being a few options to deal with it;
1) disable javascript in the browser,
2) don't use the browser,
3) improve the ability to disperse heat from the CPU.
For #3, you may note that when it gets hot, it is pretty localized to the corner of the device up near the power button. An easy solution to distribute heat better might be something simple, like adding a layer of copper foil to the inside of the back cover. The thicker the copper foil the better. Copper is very good at conducting heat, so this would spread the heat around over the entire area covered by that foil. http://www.ebay.com/itm/Copper-Foil...nductive-Adhesive-Ship-from-USA-/162018486132
Click to expand...
Click to collapse
Yeah, they do get hot...and the browser is the problem, I agree...however, I think they are not the main reason...there is something wrong with low memory or maybe some apps...
astralbee said:
I also found chrome was slow starting up, switching tabs etc. Found that logging out of my Google account in chrome improved this. Seems that synching tabs etc triggers the pause. This might be an acceptable workaround for some but I appreciate it isn't a great fix if you want to use that feature. Actually I'm not bothered as I think Google know too much anyway. �� But the underlying problem is this tablet... I don't have this problem on my phone.
Click to expand...
Click to collapse
Haha, I agree...google already knows a lot!..thanks
arminvm said:
Yeah, they do get hot...and the browser is the problem, I agree...however, I think they are not the main reason...there is something wrong with low memory or maybe some apps...
Click to expand...
Click to collapse
I don't agree with that.
We use our N9's *all of the time*, and there is never any perceptible slowdown. Possibly with the exception of straining them with web browsers, but web browsers are... poopy... on EVERY platform and device, so that doesn't really stand out. Typically just minimize the use of web browsers and all is well.
Web browsers were good in 1996 when they were simple things to display an html website. Since then, they've added all kinds of useless crap to them that bloat them out, hog up tons of memory, and just generally make them into a useless waste of space.
doitright said:
I don't agree with that.
We use our N9's *all of the time*, and there is never any perceptible slowdown. Possibly with the exception of straining them with web browsers, but web browsers are... poopy... on EVERY platform and device, so that doesn't really stand out. Typically just minimize the use of web browsers and all is well.
Web browsers were good in 1996 when they were simple things to display an html website. Since then, they've added all kinds of useless crap to them that bloat them out, hog up tons of memory, and just generally make them into a useless waste of space.
Click to expand...
Click to collapse
I know..but everyone knows that N9 should be faster!...
Sent from my HTC One_M8 using XDA-Developers mobile app
Update:
I think I have kind of find the problem of low speed of my Nexus 9...I uninstalled an app that was for weather prediction and from that time on my Nexus 9 is very fast and responsive...No problem so far. I also uninstalled some other apps alogaide that which I was never using them,so I am not sure if the weather app was exactly the reason of the slow downs...but the other apps where just some games or some simple apps....well, I hope this information helps! Let me know your idea. Thanks everyone
Sent from my HTC One_M8 using XDA-Developers mobile app