yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MBQ_:
Just added 'Advanced CPU settings'

Added information on:

-Sampling rate

-Up threshold

-Ignore nice load

-'Nice' load

-Frequency step(s)

:good:
[Samsung Galaxy Nexus] nitrogen618:
Q: What's better for performance, Cubic or Westwood?

Q: What's better on the battery, Cubic or Westwood?

Thanks!
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Cubic is preferred, and they don't tend to affect battery life
[Samsung Galaxy Nexus] mforminio7:
A study shown on two of them

"However, considering our results, in almost all cases the TCP Westwood’s performances were not better than the TCP Cubic’s ones, and it is possible to state that these results conﬁrmed what it can be expected comparing the two protocols from a theoretical view"

source here
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Already beat you to it ;)

But thank you for your help and better explanation :good:
[Samsung Galaxy Nexus] borizz27:
Suggestions

Can I make some suggestions?

Remove the "developer/coding mumbo-jumbo, because chances are, you won't understand nearly anything I'm saying" line. It's a bit condescending and if you make a mistake in your guide, you'll look like a right fool.

On to the guide:

Nice is like process priority in Windows. It goes from -20 to 19 where lower numbers mean increased priority. So if you renice a process to have low priority (nice 19), a scheduler that ignores "nice loads" will not scale up the CPU if only that nice 19 process is using 100% of CPU time. This is handy because when you set a process nice 19 you generally mean "This needs to run but I don't care when it is completed. Lowest priority". Ignoring that load when deciding if the CPU needs to speed up or down helps that.

However, I've seen people say that CPUs are most efficient in a power used for processing done manner when operating at maximum speed. So that means that you'd be better off quickly jumping the CPU to full speed, finishing the nice 19 process, and then quickly jump down to idle. This "ignore nice load" might actually cost battery life.

On to the TCP congestion avoidance algorithms:

TCP constantly tries to achieve maximum transfer rate. It does that with the help of the congestion control algorithm. TCP sends packets and requires the receipt of acknowledgement messages. When these messages keep coming in, that means the data is making it across, so the transmission speed is increased. When the transmission speed is so high that the connection can't handle this anymore packets will be lost and the acknowledgement messages will not be received. Then the avoidance algorithm lowers the speed again.

The rate and when this increases is determined by the sender. The congestion control algorithm does this. The congestion control algorithm has nothing to do with how fast you receive data, or what data you receive, it can't change that. It only changes how you send. The default is CUBIC, and it's the default for a reason: It's really good. My advice would be to leave it alone, but if you do decide to change it don't be surprised if you see no difference in performance outside of artificial benchmarks.

The TCP congestion control algorithm does not alter the battery life. It uses very little processing power. It might finish a transfer just a bit sooner because it can send more efficiently, and that might save some power. However, you'd have to be uploading all day for it to matter (and still I'd assume the powersavings will be small in comparison to the wifi or gsm radio being on). So, they don't really affect battery life.
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

^^^ thank you for this. I'll definitely change some things up. :good:
[Samsung Galaxy Nexus] Nephilim:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

In your ad blocking section I would like to recommend you add "adaway", much better app than adblock. It updates and applys new host files automatically each day.

I used to use adblock but switched months and months ago, adaway is just better. ;)

Sent from my AK Dummy Powered AOSPA Galaxy Nexus
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Never tried it. Hahah, but alright. Thank you

Edit: changed the OP a little, removed the text the user a page back suggested I do
[Samsung Galaxy Nexus] borizz27:
Oh, I forgot to tell you about IO schedulers.

Linux (the kernel) was written in a time where spinning disk hard drives were the norm (yeah, they're still working on it, but bear with me here). The problem with these hard drives is that while they can do a linear read with pretty amazing speed, they suck at random reads. This is because there is an arm with a read/write head at the end that has to swivel around to where the data is on the disk, and then it has to wait for the right data to spin under the arm for it to read. This swiveling and waiting is called seeking, and the time it takes to do is called seek time.

When you have a lot of concurrent reads going on (multiple things being read at the same time), this means that the data throughput grinds to a near stop because the head is moving around all the time.

IO schedulers try to optimize this by grouping up nearby reads so fewer costly movements have to be made. There's a few different takes on this, so let me explain a really simple one: You start at the inside of the disk. Sort all the queued reads into order from inside to outside of the disk. Then do them all. Done. Now move the head back and do it again (or start from the other end). Less time is spent moving, more time is spent reading data. Or with an example:

Say you want to read blocks 18, 94, 19 and 46. If you them in the order given you have to seek after 18 to 94, then almost all the way back to 19, then up to 46. That's 3 movements. Now if you reorder them, you get 18, 19, 46, 94. You only have to move twice now, from 19 to 46 and then to 94. That's faster.

Other schedulers try to anticipate reads (you read this part, you probably want the next part so we will wait a really short while to see if you do, then move on). The deadline scheduler tries to reorder reads for optimal access but aims to process each read within a certain time of it being queued. Really smart people have worked hard on these schedulers, and they're very cool pieces of code.

"But borizz27, there's no hard drive in my phone, it's all solid state memory with almost no seek times!" You're right. There isn't. "Then what's the point of the scheduler?" There isn't.

You'd be hardpressed to find differences between the No-Op scheduler (which does nothing, no op meaning No Operation) and any other scheduler on flash memory where the seek time for the next block of data in a linear read is the same as for the next block on the "other side" of the drive. This very fast seeks is the same reason you don't have to defragment SSDs, by the way.
[Samsung Galaxy Nexus] Orionstein:
Thank you very much. I've been wondering about the difference between Governers for awhile now - I'd usually just ended up going with whatever the rom recommended since I was never sure what the difference was between the different governers. Thanks for explaining these so I actually know what I'm setting my phone to...
[Samsung Galaxy Nexus] mforminio7:
Having trouble picking an io scheduler, stuck between so and row. Any thoughts or comments about which one has the edge?
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

ROW will give you faster read speeds, but writing to it will take longer, and SIO gives you a balance of both
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

What else do you guys want to see?
[Samsung Galaxy Nexus] Madaditya:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

How about a thread thats says which governer and i/o scheduler ppl used to run specific games flawlessly...

With the rom name and kernel...

Will help guess
[Samsung Galaxy Nexus] MBQ_:
Well, you have to take into account that whatever may be successful for one user, may not be as successful for another user, which can cause arguments, 'ROM and/or kernel wars' and many other unwanted things. That's why I always try to urge users to try them out prior to jumping to conclusions, if that makes sense(?) :)
[Samsung Galaxy Nexus] Shardzmi:
Thanks a lot! Really helpful post as I'm just beginning to dip my hands into ROMs and kernels and I was intrigued by the many performance choices ( while nobody seemed to explain them ! )
[Samsung Galaxy Nexus] Madaditya:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Hi Geeks ￼

Ok i have an issue..

When playing games like Templer un which use your accelerometer ..i.e motion sensor...

When i overclock to 1.4 pr 1.2 Ghz accelerometer dosent respond..ie am not able to move sideways in the game

For subwaysurfers touch responds badly..it responds almost whe am about to hit ￼

Kernel-LuPus v9(reported to be quite stable)

Rom-Ultimate HD 2.0.3

V6 supercharger by 'Zep'

Seeder by lambgx

What could be the issue?

I tried other apps which would test my accelorometer ..they give no errors..

Askin 2nd time..probably irrelevant to ask them in galaxy nexus section?
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

You're fine man, I have no problem answering. I'd try a different kernel, and maybe a different governor. Try fixing your permissions in your recovery as well. Come back in a few days with reports of whether it worked or not
[Samsung Galaxy Nexus] jeff5347:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

MBQ, was wondering something. I have es file and can get into the built.prop.. Will running pimp my ROM have a counteractive effect if I have gone and played w build.prop. one of the things I'm trying to fix is the proximity delay regarding telephone calls. I set the sensor to 25 in PMR but still when the phone gets pulled from my face it still takes 3-4 secs for the screen to come on. Don't know if this should be in this thread but I figured this was the best place

JB Sorcery + AK kernel = magical power
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Absolutely, never be afraid to ask me a question man.

What part(s) of the build.prop did you change prior to adding some pimp my ROM tweaks?
[Samsung Galaxy Nexus] jeff5347:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Umm let's see.. WiFi scan= 300, dalvik heap=316 and windowsmgr=275. I can't remember if there was anything else I think that's it. What I'm wondering is should I just tweak thru build prop and delete PMR or set the build prop to stock and tweak thru PMR.

PMR says set prox sensor to 25 for instant back on from a call but I still get 3 or so secs of a black screen

JB Sorcery + AK kernel = magical power
[Samsung Galaxy Nexus] MBQ_:
Your best bet would be to report that to the Sourcery team, or to the OP of Pimp my ROM
[Samsung Galaxy Nexus] MBQ_:
Thank you all so much for your kind words, and all the high votes you have given this thread, along with your questions, extra help, and especially for viewing this thread and reading it. It means alot to me.
[Samsung Galaxy Nexus] FoleyRose:
Very helpful post MBQ. I keep myself up to date with this post as it always contains new useful information. I also very closely follow Anarkia's thread on his Kernel, it's a gold mine of knowledge, if you can keep up with the 20 new pages a day. :silly:
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Ahaha I'm guilty of contributing to those 20 pages a day. :D

But thank you!! Glad I could help out
[Samsung Galaxy Nexus] dirtyreturn:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

This is the thread for this question I think. I'm having reboot problems with every kernel. Is there a universal rule for resetting before each flash? I guess my phone may get hot or overload or something. I don't know. Any things I should give a shot? More information needed for some help?
[Samsung Galaxy Nexus] MBQ_:
By 'reboot problems' what do you mean?

Is it bootlooping?

Is your phone freezing and rebooting?

?
[Samsung Galaxy Nexus] dirtyreturn:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

MBQsniper - my phone is doing a bit of both, freezing/rebooting. Regardless of the kernel and GPU frequency. Other phones I've had had never given problems 10-30 or so reboots per day. Would you suggest to start fresh? Probably the road to take?
[Samsung Galaxy Nexus] MBQ_:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

I'd go crazy. Hahah

Can you please tell me the recovery you're using, the device type you have, and the process of how you flash each ROM and kernel? Thanks
[Samsung Galaxy Nexus] Tex99:
just to share my experience :) for now i use cubic + deadline. i prefers performance, and i love this setting. when i turn on the screen after a long deep sleep, and i open contacts or message, there is not black screen or lag, i think because deadline doesn't close the app in cache for runnig the system very smooth, right ? :)

btw thank you for your guide, now it s easy to found the right settings for personal use. really great :)
[Samsung Galaxy Nexus] dirtyreturn:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

It drives me crazy. CWM / latest beta from thread. GSM nexus /from google play with wallet. I've flashed dirty and even coming from a clean install I believe I've had similar reboot problems. Edit- I don't think it should make much difference... I use apg to patch for pdroid. On other phones nothing compares to the amount of reboots.
[Samsung Galaxy Nexus] akellar:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

How about explanation of read ahead value?
[Samsung Galaxy Nexus] MBQ_:
Sure thing, Ill get on it
[Samsung Galaxy Nexus] MBQ_:
Depends on the priority of the task

youre welcome, glad I could help

Try to not use that patch, and flash a kernel. Maybe thats your problem
[Samsung Galaxy Nexus] MBQ_:
Update:

-Added information on the OnDemandPlus Governor
[Samsung Galaxy Nexus] MBQ_:
Update:

-Fixed spelling and grammar errors
[Samsung Galaxy Nexus] TheMysteriousOne:
hispeed_freq too, please!
[Samsung Galaxy Nexus] nitsua98:
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W

Hispeed_freq =hispeed frequency :p
[Samsung Galaxy Nexus] MBQ_:
Exactly. Hahaha
[Android Q&A, Help & Troubleshooting] fredphoesh:
Hello guys

Every day when I arrive home, my SGS3 has connected to some open network near my house. I never want it to do this automatically but can't stop it from happening. This never happens on my wife's I phone 4s...

I've set advanced settings to not notify me when an open network is nearby, but the damned phone keeps connecting to unwanted connections.

Any ideas how to stop that?

I'm on sgs3 with 4.1.2.

Thanks

Mark.
[Android Q&A, Help & Troubleshooting] UnrealZoidberg:
Try going in to Settings > Wifi and seeing if the network name is there. If it is, long press on it and select "forget network."
[HTC ChaCha] TheMrDanonek:
Hi,

I would like to have on your htc a cool rom, best that it be stable and fairly fast polished that you can recommend to me, I thought about this: http://xdaforums.com/showthread.php?t=1867463, but no active links in it, if someone could tell me refresh it?. Please answer quickly and that the CM10 is quite good and stable, what is going on and what is not, what should upload the rom does not want to change every now and then rom. Regards nice people :)
[HTC ChaCha] lolmop:
android 4.0.4 roboto

roboto rom is a rom based on cynogenmod9 (a.k.a android 4.0.4 'ice cream sandwich')

- it includes beats audio driver system

- it's stable

- it has a beats logo bootanimation

- it is made by luke arran

you can find the roboto rom here: https://github.com/lukearran?tab=repositories
[HTC ChaCha] TheMrDanonek:
and it is fast and polished?
[HTC ChaCha] lolmop:
fast

yeah it is very fast! and very smooth!

when you flash the .zip through CMW, the AROMA installer appears... from the AROMA installer you can choose what apps and sound and bootanimations and stuff you want in the ROM! it's magic :D

it's a realy awesome ROM!

but the only i dislike is that the 'facebook'-button is not working :(
[HTC ChaCha] TheMrDanonek:
the "facebook" and so I do not use, and the Meuse to replace it by something else this button do? ;) Thanks for the answer, and ask for the exact Meuse link to it? everything in it's on the button?
[Galaxy Note II Q&A, Help & Troubleshooting] barryb20:
Hi all,

Quick question, I noticed when browsing Engadget in landscape mode where there was dark black embedded video there appeared to be a faint grey ghost line that was about 10 or so pixels wide that would follow the image, mostly on the right hand side

It does appear to be on the S3 as well but a lot fainter as to not be noticeable

Anyone seen this?

I also noticed the white is not as uniform as on the S3

If this is just Amoled then that's okay :)

Thanks

Barry
[Galaxy Note II Q&A, Help & Troubleshooting] souravtarafdar:
xxxxxxxxxxxxxxxxx

nothing like that in note7100 for the same
[Sprint HTC EVO 4G LTE] Fuses:
The issue

If you flash new 3.15.651.16 JellyBean RUU and it only updates hboot to 2.09, phone might end-up in semi-bricked state.

RUU refuses to flash any other partition (even if bootloader is in locked/relocked state) so its impossible to return phone to stock rom.

Error message from fastboot flash zip is;

fastboot flash zip RUU.zip
sending 'zip' (659905 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)

What is causing this

Hboot fails to read ruu-info from new encrypted zip after hboot-preupdate and stops flashing process.

Solution

Solution is to flash firmware.zip from JellyBean OTA. Firmware.zip is "old style" zip file, hboot can open this zip and update radio and sbls.

Fix

- Download JB OTA firmware from http://unlimited.io/jewel.htm

- Download fastboot executable (google)

- Put all files in one directory

- Reboot phone into fastboot mode

- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock

- Enter commands

fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip

NOTE:

If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.

After this flash stock RUU again.

Permanent fix

- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:

Please report any success / failures into this thread. Also tell little bit information about your device, like;

- What hboot you had

- Was radio flashed through recovery

- Was hboot downgraded

- CID
[Sprint HTC EVO 4G LTE] Fuses:
-- Reserved --
[Sprint HTC EVO 4G LTE] corcgaigh:
Thanks for your work
[Sprint HTC EVO 4G LTE] andyjjc:
thanks fuses
[Sprint HTC EVO 4G LTE] scottspa74:
Wow fuses, this is gonna help A LOT of people. This community is really lucky to have your attention. Thanks. :thumbup::beer:
[Sprint HTC EVO 4G LTE] tankerkevo:
I ran this... Worked to a T. Debating whether or not to s-off...

But, this did in fact update my radios..

Phenomenal. Just to be clear with what I did...

Ran Fuses instructions. Then I did the RUU GUI update in Windows... back to stock, Tampered in bootloader removed. Testing the stock radios and what not, but so far it's perfect.
[Sprint HTC EVO 4G LTE] cloves:
*** Phone has to be RELOCKED****

I am not sure if I am successful or not right now. Phone is showing HTC black screen with green bar below it. The green bar is not ALL the way across, looks like 95% after running the commands. Not sure what to do so I issued "fastboot reboot"

Phone looks to be in bootloop so I got back into HBOOT.

First I relocked the phone. Rebooted. Then Rebooted into fastboot.

Then ran commands, screen shots are attached.

Seeing this message after running commands:

FAILED (remote: 90 hboot pre-update! please flush image again immediately)

Changes noticed in Bootloader:

My RADIO updated from 1.02.12.0427 to 1.12.11.1119

OpenDSP updated from OpenDSP-v25.1.0.32.0405 to OpenDSPv31.1.0.45.0815

Update:

Put the phone into fastboot and then ran the windows Jellybean RUU. Looked like the RUU got about 98% thru and then gave me a USB error. Then the phone rebooted and it looks like everything updated. Phone is booting into JellyBean. Should I retry installing the RUU?
[Sprint HTC EVO 4G LTE] thicklizard:
Cloves

Rerun the ruu. Just hit the up arrow and then enter
[Sprint HTC EVO 4G LTE] rpenrod23:
I don't personally have a need for this but I know others do so thanks! Nice to know this is there if needed. :thumbup:
[Sprint HTC EVO 4G LTE] cloves:
Thanks,

Everything looks good. Phone shows RELOCKED and 4.1 is running. Thanks for the fix!
[Sprint HTC EVO 4G LTE] leeoniya:
saved my ass. thanks!
[Sprint HTC EVO 4G LTE] aankush:
My 4G LTE was on HBOOT 2.09

Tried to S-OFF and downgrade HBOOT by DirtyRacun

Was stuck at a point where the screen went blank for a long time

After that the phone does not power on...

Even the PC does not detect it...

Help please...
[Sprint HTC EVO 4G LTE] corcgaigh:
Seek out soul shadow . He's usually in the stickied threads in original development. He seems to know a hell of a lot about this phone and bricks/semi bricks
[Sprint HTC EVO 4G LTE] Fuses:
Fastest way to get support for DirtyRacun is to join #unlimited channel on freenode.

Lets keep this thread clean, semi-brick on 3.15.651.16 stock RUU stuff only.
[Sprint HTC EVO 4G LTE] Indirect:
Well guys, time to add some info. If you lock and re-flash the RUU file and you get "SBL VERIFY FAILED" errors (but the RUU still completes) and you can't htcdev unlock (signature failed), you should use this fix. Helped me get my friend's phone S-off using Dirty Racun.
[Sprint HTC EVO 4G LTE] un1ocked:
is this true?

if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
[Sprint HTC EVO 4G LTE] scottspa74:
Um,...yes. if fuses posted it and it's about S-off,... it's true.
[Sprint HTC EVO 4G LTE] Fuses:
Yes it is true, but always download full stock RUU and use that. There is some problems with repacked firmwares.
[Sprint HTC EVO 4G LTE] Jeffrey4Free:
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
[Sprint HTC EVO 4G LTE] Fuses:
Probably windows dropped fastboot-drivers. Try installing drivers again or use Linux, ubuntu live-cd works just fine.
[Sprint HTC EVO 4G LTE] TurboX2:
Thanks a million

Thanks man.. you are a life saver.. i was trying to recover from a bad radio flash (constantly rebooting) by reverting back to stock.

when i did try to do the new RUU i had the "semi-brick issue"....

Did this simple step for flashing the OTA before the RUU and it fixed my issue!!! My phone is working again
[Sprint HTC EVO 4G LTE] AndrasLOHF:
What does OP mean by hboot ONLY update to 2.09. Mine went from 2.09.0000 to 2.09.4444. Is mine good?
[Sprint HTC EVO 4G LTE] Sloth:
.4444 is the DR hboot