[Android Software/Hacking General [Developers Only]] mw86:
Changes are in the original post.

So far 1.2.6 apk starts on boot and this time i actually see super user rights granted message on this apk. The monitor for entropy is working good. It seemed to raise entropy while monitoring but after waiting a little it stopped rising so there is no problem there. The monitor works as well as the other monitor app for entropy in playstore.

Can someone explain this to me. No seeder installed i did some tests after some thoughts i had.

Default read_wakeup_threshold is 64, write_wakeup_threshold being double at 128. So i followed some of Zed or Zep user posts about the systctrl method. Basically to test the effectiveness of keeping the entropy pool full cant we set like 8 read_wakeup_threshold and write_wakeup_threshold 16. Randomize_va_space 0 and 2 i tried both. What i saw was it hovered low and actually got to around 32 on average and when i messed with Ui even jumped to 70s. Question is I was reading in some ways 3* read_wakeup_threshold should be max entropy seen and the write_wakeup_threshold is similar to a minimum entropy before building up entropy again or ie what it resets to if it reaches max.

Couldn't using such a minimum max show more lag since entropy would run out fast and easily making the kernel halt till it refilled? Helping find situations we could test to prove the benefit seen in keeping entropy from depleting?

Weird thing is the other end of the spectrum. I set 1376 read_wakeup_threshold and randomize_va_space one way or other didn't make a huge difference and write_wakeup_threshold to stock 128. Entropy started low and could raise as high as 4096 and around 3500 it slows down in how quick i can rack up entropy by messing with the UI like status bar or flipping screens.

With 1376 read_wakeup_threshold and 3219 write_wakeup_threshold i saw entropy min around 3590 and goes up to 4096 max and resets. But builds slow as in like above it took a lot more ui messing with to accumulate.

With 1376 read_wakeup_threshold and 3220 write_wakeup_threshold i saw entropy min 4096 and 4096 max and resets. But builds slow as in like above it took a lot more ui messing with to accumulate. Strangely in this setup 4096 entropy never drops under usage for a sec kind of like what happens in the next setup below.

Bring Seeder into the mix after reseting randomize_va_space and read_wakeup_threshold and write_wakeup_threshold. Booted i see 4096 entropy which in past seeder wasnt doing that. It was keeping it high but hadnt been keeping it at 4096. Now i watch and mess with ui and it will drop for a split sec to 3900 range and immediately back to 4096. :Good:

Same setup as last paragraph but 1376 read_wakeup_threshold and the 4096 never drops under use even to 3900.

I don't know what all this means as the big picture but if I use one of those setups with seeder or without is fine but for example with seeder, if its set in one of these ways that 4096 never drops even under use of entropy drawing tasks will it have any adverse effects and is it actually using the entropy when I see 4096 isn't dropping under use.

Thanks for entertaining my question whomever can answer me. Please comment on another post if your only going to say seeder doesn't work or placebo. I know I feel and see the differences when entropy empties too quick or is maintained. Please keep the spam out of this discussion forum.

Edit: currently on Galaxy S3 sprint version on freegs3 and ktoonsez kernel KT747. So android 4.1.1. I did try an early version on 4.2.1 but not a recent one.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk