yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nemotheblue:
Re: Post by user splus in Franco.kernel thread

Sorry to post in this forum, but I don't have the minimum post count yet to post in the development forums :(

I read a post today by splus which I found very interesting,

but I wanted to learn more so I did a lot of Googling about the parameters of the interactive governor. Unfortunately, I kept finding the same few beginners' guides to the different governors available, explaining and comparing their capabilities. There was no advanced explanation of the parameters or their possible valid values.

I found this post by RootzWiki user abqnm, which shed a little more light on the hispeed_freq parameter, and input_boost also. From what I've read on various sites, the input_boost seems to be a binary parameter, so setting it to 1 should jump the CPU up to the frequency specified in hispeed_freq immediately upon detecting a screen touch event. This would make your GNex feel a bit more responsive, without having to wait for the CPU to hit load, but it could negatively affect battery life. In my case, running 729/1612 with hispeed_freq set down at 1036MHz (1037000 in governor control), it's not that big a jump and opening a couple of apps would likely push my speed up beyond it soon anyway, so the battery hit would probably not be much.

As splus said:

so using 1036000 in governor control would correspond to the next step down, 729MHz. I know it's easy enough to stick on an extra 1000 for safety, to ensure we hit the right steps, but I'd be curious to know the exact kHz values we could be using.

I'm off to start experimenting with undervolting these new CPU freqs, and my 512GPU Core to reduce my temps a bit.

In case anyone asks, I'm on stock JRO03C w/Franco r220 512GPU.
[Samsung Galaxy Nexus] osm0sis:
Very good post! Welcome to XDA! :good:

I'll link to your post on the franco thread just so it gets a couple views from people there.

Edit: I see that you've actually been here awhile! Go help a few more people so you can contribute in the Dev forum. ;)
[Samsung Galaxy Nexus] nemotheblue:
Yup, that's me... total lurker! I usually defer to the wisdom of the devs and seasoned members, and 99% of the time if I've had a problem/question re my Nexus it's already been posted and there are whole conversations for me to read and digest. I hate the idea of clogging up a thread with a "me too" or "thanks" post, so generally if I don't have something useful to contribute I keep quiet and hang in the shadows. I only come out to feed.

So basically, I'm a knowledge vampire.

That's enough OT... Franco stuff!

I've previously read droidphile's governors thread to which splus linked in their reply to your repost in Franco.kernel. In post #2, containing the governor tweaks (which I found very useful) even droidphile seems to have the wrong idea about the "hispeed_freq" parameter, stating:

The same section also omits any mention of the "input_boost" parameter.

My undervolting is going well. Inspired by the voltages on rogersnm's signature, I'm currently running these:

1612 - 800 mV
1536 - 750 mV
1420 - 750 mV
1305 - 750 mV
1228 - 725 mV
1036 - 725 mV
729 - 700 mV
384 - 700mV

CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV

IVA -
266 - 600 mV
133 - 600 mV

I added an extra 100mV to the seemingly rock bottom CPU voltages for safety, but I'll try to reduce them gradually. I've been stable for over 40 hours so far on this setup. With r220, Franco really seems to have nailed it!

BTW, thanks for reposting in the Franco.kernel thread :highfive:
[Samsung Galaxy Nexus] osm0sis:
Fantastic. Keep us updated on your progress with voltages, seems like you're doing a great job!

Also, happy to help! :D
[Samsung Galaxy Nexus] vomer:
I'm trying these too. So far so good!
[Samsung Galaxy Nexus] splus:
Hi nemotheblue. Good post and findings!

I'm just looking at those voltage values you wrote - are you sure you turned off the SR?

If you haven't don't turn it off with those voltages because you'll get an instant reboot, they seem super low.

Rogersnm wrote and fiddled a lot with voltages, some very good posts.

Better go back to stock voltages, turn off the SR, and then go little by little down with frequencies. When adjusting each frequency best is to set that particular frequency as min (or max if it is higher) frequency so the CPU actually uses it.

And when you get a reboot then just use 25mV higher than the one with reboot.

I'd suggest to have fsync turned on when you fiddle with voltages because that will lessen the possibility of loss of data when phone reboots.

Another thing to have in mind is that even some combinations of frequencies do not work together. Some frequency might work OK with certain voltage with certain max/min frequencies but might not with other min/max frequencies. It looks like the actual change from one frequency to another (and depends from which to which) can determine a lot if a voltage is stable or not.

Also, it apparently very much depends on a ROM you use - different ROMs will probably need readjustment of voltage table.

Undervolting actually won't help much with battery life, smart reflex does a very good job already. It would help most if you game a lot or use your phone heavily, so then when higher frequencies are used the phone would get less hot and use slightly less power.

Otherwise, and especially if you change ROMs, I'd say it isn't worth the trouble.
[Samsung Galaxy Nexus] droidphile:
Since there's lot of info to cover, mistakes can happen. I'll correct it if something is wrong.

Anyhow, if you check the interactive governor code,

if (!hispeed_freq)

hispeed_freq = policy->max;

This means if kernel default for the value of hispeed_freq=0, then it's assigned to policy_max aka scaling_max.

hispeed_freq is kinda like max_load_freq for ondemand.

Btw, input_boost is not available for interactive governor 'designed' for i9100 GS2 with Exynos chip. I don't know about Gnexus' Omap. Since i take one of the GS2 kernel as reference, governors params are kinda specific to i9100 and exynos architecture.
[Samsung Galaxy Nexus] nemotheblue:
@splus Wow, thanks for joining in on my little thread! Rest assured, before I started my tinkering I turned SR off and fsync on. I've read all 2306 pages of the Franco.kernel thread :eek: and avidly followed several conversations within it. I don't mind being a bit adventurous and trying out tweaks and mods; I just prefer to let other, more educated people try it first! I'm a measure twice, cut once kinda guy.

I followed rogersnm's undervolting saga in the Franco thread up to a couple of weeks ago, and recently caught up with his linaro thread, but I was as amazed as you seem to be at the tiny numbers he's currently reporting.

That being said, the voltages I reported were totally stable for me the last 3 days, until tonight. Tonight, I went to a double bill of Batman Begins and The Dark Knight - 5 hours in a huge, sold out cinema with easily 1,000 people. By the second movie, the room temperature was in the high 30s, if not 40C. I got an email, had a read, tapped back to inbox and BAM! The screen froze for about 3 seconds, then rebooted. The crazy thing is, I tried an hour later to reapply the undervolt and it froze straight away. I'm back on SR for a while, but I might try again tomorrow.

My original intention with the undervolting was just to drop the CORE, because I'm getting great performance from the 512GPU, but I notice the area under the camera on the back of the phone can get pretty hot if I'm playing games or watching a video for >30mins. Granted, I don't do that too often, but I figured it'd be nice to eliminate the extra heat. Once I saw the power saving calculations in rogersnm's chart, I was convinced to go the whole hog. The jury's out...

@droidphile Thanks for taking the time to reply. I didn't mean to sound like I was attacking your guide; I'd just read conflicting information from multiple other sources and played the numbers. I was labouring under the false assumption that all interactive governors are created equal. Is there some kind of official/original reference/guide/man page for the governors and their parameters, or are you devs left to interpret the code for yourselves?

I must admit, I'm more confused than ever now. I just can't reconcile your explanation with splus' claim that hispeed_freq=1037000 is the sweet spot for getting interactive to use the intermediate freqs up to a max well above 1036MHz???
[Samsung Galaxy Nexus] splus:
Yeah, if you do some gaming and more intensive stuff then it might be worth to find some good voltage values.

Still, those voltages seem pretty far from what hardware would be capable of running so that makes me think the SR check box wasn't really displaying its actual state somehow.

If you were using Franco's app did you check the last tab to see if mV values at certain frequencies were the same as in your table? If yes then I'm just amazed you were able to run it that way...

Anyway, good luck with further undervolting, please post your stable voltages when you find them...

If you have higher OC CPU frequency as max value in interactive (I'm talking about GNex, every chipset behaves differently) then it looks to me that if you set hispeed_freq to 1228000 the CPU would often just stay at that frequency, as if the system decides that it's enough to finish the job. But if you set it to 1037000 then it often determines it is not enough and scales the CPU to higher frequencies, and then you get the CPU to actually use higher frequencies as well.

Other direction would be to set hispeed_freq to even higher frequencies and that'll definitely make it more responsive but at a battery life cost.

The most responsive system would be that CPU goes to max whenever there's something happening. Google actually said at their IO that they tuned JB to go to max frequency at any touch but if you use the stock kernel and check CPU Spy charts you'll see that CPU goes initially only to 700 MHz.

There are other parameters, but it's all about finding a sweet spot for performance and battery life...

Needless to say, tuning all those governor parameters is greatly dependent on available frequencies, programmatically implemented governors and its parameters (which can be changed, a kernel developer can design and implement his own governor and its parameters) and especially chipsets and the way they behave. Every device is very different...

I think we would have better performance if there would be less frequencies in a kernel than currently in Franco's, but if the CPU is really efficient at scaling frequencies up and down through many steps all the time then maybe not.

Either case life goes on and I'm looking forward to see that new Batman myself in couple of days! :-)
[Samsung Galaxy Nexus] nemotheblue:
Fine folk of XDA,

Apologies for my long absence! I wasn't abandoning the thread; I got a call to work on a short film and had an insane 10 days of 13-16 hour working days and my brain was just too tired in the evenings to keep up with testing and tweaking. Plus, I needed my phone 24/7 stable to handle the continuous flow of calls, texts and emails from the production office.

So, I reverted to SR and dropped my max freq to 1228 and had no problems.

Catching up on the Franco thread tonight, I read a post by daggerxXxsin saying

I'm currently trying these out on 729-1228 with SR off and fsync on, along with the following:

CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV

I'm gonna leave IVA alone on SR. I never really noticed any difference undervolting it before, and I figure if I'm pushing my MPU voltages so low, I'm just begging for crashes so it's best not to mess with anything that would affect I/O.

I'm currently running r225 512GPU, and I had some wifi issues where the indicator would frequently switch from blue to grey and lose the connection. However, having read some frequent posts in the Franco thread, I've switched from CWM to TWRP, wiped caches and reflashed Franco so I'll wait and see if the problem resurfaces.

BAH! Screw it, I just refreshed the Franco thread and r230 is out. Gonna flash and see how I get on...
[Samsung Galaxy Nexus] osm0sis:
Hi again nemo, just stumbled on this thread again :p

Wondering what posts indicate that CWM vs. TWRP recoveries would make a difference for the booted OS's Wifi/Google Services connectivity?

As I understand it JB in general just has a bit of a Wifi problem vs. ICS and even with ICS the Galaxy Nexus does vs. any other phone. I'm currently having acceptable Wifi using franco 241 (which has a new IO scheduler which makes things feel extremely snappy).
[Samsung Galaxy Nexus] nemotheblue:
I'm pretty sure all I based that decision on was this discussion in the Franco.kernel thread. In retrospect, kinda half-baked but I must say I'm impressed with this recovery anyway!

I'm still following the thread religiously, rocking M5 at the moment though I'll likely jump on the first 512GPU nightly that comes out. I spent hours yesterday reading the MiNCO and MiNCO+ threads, very carefully backed up, then flashed v4 and immediately ran into this major roadblock and ended up reverting. Further study is required...
[Samsung Galaxy Nexus] osm0sis:
A few things come to mind with that storage problem:

1) Maybe that the sdcard bin (as is also in franco's cwm zips) is installed and messing things up weirdly. You'll need to push the stock one back (first post of franco.Kernel thread iirc).

2) A recent ROM Manager bug where .nomedia files were getting placed in the /sdcard/ top level folder, so you might want to investigate that with adb shell (though this would be weird considering you say you're using TWRP and ROM Manager is CWM).

3) Go to Apps > All > MediaStorage, Force Stop and clear data+cache. Reboot to have MediaScanner rebuild the MediaStore.

Edit: Just saw your post in the linked thread... looks like you tried 2+3... so try 1?
[Samsung Galaxy Nexus] nemotheblue:
Very clever! Way to think outside the box, ossie :highfive:

I should have time to try again tonight, so I'll let you know how it plays out. While I'm at it, I'm excited to try out DarkJelly's inverted gapps, but I'll make sure to tackle the storage problem before flashing any apps/mods
[Samsung Galaxy Nexus] nemotheblue:
So I couldn't wait! :D

I was unable to shake the feeling I might have just had a bad download of MiNCO, so I grabbed a fresh copy before I began. Flashed the ROM, Gallery worked fine. Flashed a navbar/battery icon mod, Gallery still ok. Gapps, no problem. Inverted apps, smooth sailing!

I now have a fully functional, customised ROM and no storage problem whatsoever. I must've just borked the first MiNCO download...

All's well that ends well :)
[Samsung Galaxy Nexus] osm0sis:
And I successfully tricked you into making your 10th post, so my work here is done! :laugh:

Now come join us in the main thread :good:
[Samsung Galaxy Nexus] nemotheblue:
Nice one! :highfive:
[Samsung Epic 4G Touch] WhiteWidows:
Just a heads up in case you don't go outside of the ET4G forums is XBMC is working on our phones. Im streaming 1080p mkv's smoothly.

http://dl.miniand.com/miniand/xbmc-android/xbmcapp-armeabi-v7a-debug-20120714.apk

[YOUTUBE]56lzkBnCFqU[/YOUTUBE]

Xbmc Source Code: https://github.com/xbmc/android
[Samsung Epic 4G Touch] MoHoGalore:
Sweet app. Looks good and not just for videos. :D

Sent from my SPH-D710
[Samsung Epic 4G Touch] WhiteWidows:
Waiting for my MHL to get back here so I can test it on the big screen. Now to get mhl working on aosp
[Samsung Epic 4G Touch] MoHoGalore:
That's where I could see it being beneficial. Tad small otherwise. Did you notice that out won't go below two folders from root? Just an observation.

Sent from my SPH-D710
[Samsung Epic 4G Touch] WhiteWidows:
I didn't poke around root level but i am streaming from my NAS perfectly
[Sony Ericsson XPERIA X10 Mini] sliddjur:
So my girlfriend got a X10 Mini (E10).

It came with 1.6 Cupcake, so I updated to official 2.1 and then rooted. Then installed nAa kernel and installed miniCM on her phone.

Seems to run smooth so far. But the anti-aliasing settings seems to be very off. It's hard to see the text.

But, there are some "bloatware" that she will not need and will probably press and mess up phone settings. Like the theme chooser, spare parts, terminal emulator, DSPManager, etc...

I know you can disable the shortcuts, but they still take up space. Yeah I know you can uninstall with what-you-call-it-app

But are there other roms that have minimal apps installed? It's her first smartphone, and I want her to be able to install and try a lot off apps. I saw the MIUI, but doesnt look like its stable yet.

Are there any stable 4.x roms yet?

There are so many Gingerbread roms to chose between, and there are quite a few ICS roms too! Don't know where to start really :)

So - whats important for her;

- Smooth and stable

- Easy

- A lot of space
[Sony Ericsson XPERIA X10 Mini] SmG67:
If you want smooth and stable, stick with GB, all the ICS-ROMS have some trouble with lag, often with waking up and receiving calls, not to mention the missing hardware-acceleration with encoding en decoding video.

Try MiniCM7 or DingerDX on the nAa GB kernel.

If you want to get rid of things like spare parts and dsp-manager, you can do so in Settings - Applications, or remove them manually from system/apps with a file-explorer with root access.

By the way: You may call that bloatware, but since they're all installed in system/app and not in the user-application space (data/app) they won't take away any space for user-installable apps, because the /data is on a different partition in the internal storage. And ofcourse you can always enable A2SD in settings - Cyanogenmod settings - Applications for more application-space.
[Sony Ericsson XPERIA X10 Mini] sliddjur:
Yeah thanks. I have installed miniCM for her, and we'll see if she's coming back from vacation in a week whining or not.

Are there any good MIUI roms?

I tried Miui on my blade and its nice.

All you would need is MIUI with Airdroid app and I think she can handle android :)
[Sony Ericsson XPERIA X10 Mini] SmG67:
Unfortunately :( The only real MIUI Rom is based on an ICS rom, which is not very stable and has not been updated in a while either. I would love to see a GB-based MIUI, but i guess everyone is too excited about ICS and JellyBean to do anything with GB anymore.
[HTC EVO 3D] aerodriquez:
I've been trying to get this damn ROM onto my Evo3D since yesterday morning! I've got HBOOT 1.50 with S-ON, 4EXT Recovery to for flashing, but each time I select the MeanROM .zip and try to flash it, the process gets aborted within seconds! I've tried searching around Google, THIS forum, and a couple others, as well as videos on YouTube and I've come to no avail. Anything that I'm absentmindedly missing here?

If you need anymore info just lemme know!

Please & thanks in advance!
[HTC EVO 3D] coal686:
Two suggestions:

1. Such a quick abort implies a problem with the download. Maybe try to download again.

2. Ics Roms usually bootloop for people who are s-on, so I recommend you get s-off.

Sent from my ICS 3VO with Tapatalk 2
[HTC EVO 3D] aerodriquez:
So I figured out that my MacBook unzips the download as soon as it's done, automatically. Is it the same if I just zip it back and copy it to my sdcard?
[HTC EVO 3D] coal686:
I would think so and you could try it. It would be best I would think if you can find the original file on your hard drive.

Sent from my ICS 3VO with Tapatalk 2
[HTC EVO 3D] Flashalot:
What browser are you useing if stock then it used to happen to me but I switch to Firefox and.it stoped

Phone:HTC Evo 3D CMDA

HTC Sense:3.6

Software number:MeanROM ICS v1.9

Kernel version:?????

Baseband version:1.06.00.1216

Build number:1.13.662.2_RC

HBOOT:1.50 S-on

Recovery:4EXT Recovery Touch v1.0.0.5 RC5
[Galaxy S III General (US Carriers)] bud951:
Well I got my brand-new Samsung galaxy S3 (off contract) and I’ve been playing around the last couple of weeks streaming video and whatnot and to my surprise I get the dreaded text message from AT&T stating that I just got throttled. This is the first-time and I am PISSED!! I am SURE this has been covered before but it’s the first time for me. I had no idea exactly how much they throttled you by until now. I mean you can’t do anything once they tightened the noose. I am grandfathered in with an unlimited LTE plan also which really makes it that much more irritating. Well I guess I need to download that app that finds free hotspots. I am in the San Antonio Texas area and we have good mobile data coverage down here so I have to wonder if there are any providers offering a truly unlimited non-throttled or less throttled 4g (of some kind) data plan. I know that Sprint is just getting their LTE service fired up and they are offering an unlimited plan in my area and technically I am not under contract right now which I made abundantly clear to the AT&T employee that I was speaking with (ranting to) like she cared. Does Sprint pull the same crap that AT&T does? Do I have any options? Thanks in advance.
[Galaxy S III General (US Carriers)] AttachedSilver:
Sprint just deployed their LTE recently and I've seen data speeds around 30+ MB/s reported by users in Texas
[Galaxy S III General (US Carriers)] erichj:
We have unlimited data at Sprint. I've never been throttled even when I spent a month on roam and used like 35GB.
[Galaxy S III General (US Carriers)] TheDiabolicaL1:
I'm a moron. Nm.
[Galaxy S III General (US Carriers)] s1mpd1ddy:
When I'm throttled on att ... my data speed goes from LTE to regular 3G , which is more then enough to stream video and music. How slow are you getting?
[Galaxy S III General (US Carriers)] bud951:
LTE? How are speeds?
[Galaxy S III General (US Carriers)] bud951:
I went from almost 50mbs down to .5mbs down and up! Its enough to do little stuff but that's not the point. Its just unacceptable to be THAT limited on an UN-limited plan. Ive been with them 10 years since they were SWB and Cingular Wireless and Ive never come close to 5 gigs until now. How do we stream video and other data intensive stuff on 5 lousy gigs a month? Sprint offers Unlimited LTE in my area NON throttled according to Sprint rep. I will go to Sprint store tomorrow and see how fast it is. I am not under AT&T contract so I can shop around. The plan im on is almost as much as the unlimited Sprint plan so no big price difference. Is there a catch to Sprints data service? Do they start charging extra or or limit download size or cut you off if you tethering or anything? Is Sprint a good alternative to AT&T? Sprint seems the logical choice if thier speed is equal or near AT&Ts. Is AT&Ts call quality better or Sprint? Inst Sprint CDMA? Info greatly appreciated. Thanks.
[Galaxy S III General (US Carriers)] aznmode:
Lucky. Tmo goes to edge which is Max .08mbps
[Galaxy S III General (US Carriers)] stupidchicken03:
Im grandfathered in for unlim data for Vz. 14 days into my billing cycle sitting with 94.7 GB :)
[Galaxy S III General (US Carriers)] saccityp:
Good god, may I ask what you use all that data doing? I'm getting 10mbs on sprint.
[Galaxy S III General (US Carriers)] winterstormhaku:
To answer you question there are no gimmicks with Sprint when it comes to unlimited data. There plans really are unlimited and I live in Atlanta where my 4gLTE just activated and I am very pleased with the speeds. I'm loving Sprint right now.
[Galaxy S III General (US Carriers)] flawedlegacy:
Since the 5th, I've switched to Sprint. Coverage blows in stl, but blown past my 2gb cap I had with att and living that so far. Some coverage and I will be set!
[Galaxy S III General (US Carriers)] corythug:
If I had lte on sprint I'd be all over it. But 3g by me is horrible and no service whatsoever at my house really kills it. So I recently switched to att where my coverage is awesome and my 3g is easily 8x faster on average. If lte on sprint ever comes to my area I will certainly reconsider my choice. Until then ill live with my 5gb att cap.
[Galaxy S III General (US Carriers)] defnow:
5. something gbs........ throttled
[Galaxy S III General (US Carriers)] erichj:
I live in Jefferson City, MO and we aren't slated for LTE until later this year.