yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] raphenucleus:
Sound boost only works when used with headphones; you won't notice a difference over the speaker. I haven't actually used high performance sound, but I assume the difference is subtle and that it depends on the song as well as the quality of the track. If these aren't your issues, use root explorer to navigate to /sys/class/misc/soundcontrol/volume_boost and /sys/class/misc/soundcontrol/highperf_enabled to see what the values are set at in the files to make sure the franco app is actually enabling those settings (a value of 0 is off for both settings, 1 is on for high performance sound, 1-3 are the possible enabled values for volume boost).
[Samsung Galaxy Nexus] tacosrdelicioso:
Skipped m4...flashed 180..
[Samsung Galaxy Nexus] eaglesport:
Having the best performance ever on 180. The 1500 slot combined with Wheatley Is absolutely amazing to say the least. Very smooth. Thanks a lot Franco.

edit: also on 512 gpu which is stellar and runs perfect on my phone. Battery has been great which is shocking but no surprise because Franco is a mastermind. Anyways, thanks, continue to improve and innovate these kennels. They keep getting better and better!

Swyped from my liquid Galaxy Nexus on the one and only Franco kernel.
[Samsung Galaxy Nexus] Shamrock13:
I still have the music issue on 180, sadly.
[Samsung Galaxy Nexus] ozymandiaz:
Ok, tried pushing from my pc, still no luck. tried changing from Eclipse to Liquid, no luck. (Wiped in between, no luck) Guess I'm just not meant to try 180. =( At any rate, loving milestone 4, I will keep trying the nightlies as they come out, really looking forward to trying wheatley. Keep up the great work, Franco!
[Samsung Galaxy Nexus] TEK112:
Miss post... sorry.
[Samsung Galaxy Nexus] neederishelp:
I did, it did it, then I flashed 180, wiped both caches, and then it still came up
[Samsung Galaxy Nexus] mike216:
Delete that zip and download another one then flash
[Samsung Galaxy Nexus] upther:
Wheatley performed well for me while streaming music through Rdio and using Runkeeper. There does seem to be a little lag when unlocking the phone though. We'll see how the battery does today.
[Samsung Galaxy Nexus] rgoyena:
Damn this nightly version is a keeper! Wow blazing fast on 1.5 512
[Samsung Galaxy Nexus] EDNYLaw:
Just wanted to report after reading through the GSM section where users seem to be getting lots of reboots on Wheatley. Running R180 Wheatley 19x - 15xx 512 GPU on AOKP based Patient Zero M2.5, not a single reboot, 3.5 hours of screen on and about 16 hours up time at 6% left. This is just a little lower than when I run 19x - 13xx with the conservative governor but I ran a ton of bench marking tests to stress the phone which I generally don't do and I'm sure, being the first cycle not everything has settled. For a highly experimental nightly this is amazing my quadrant scores (not that I place stock in them) went from 3400 to nearly 4000 and AnTuTu is over 7000, great work Franco, through your hard work, along with the other devs, you make this device constantly surprise me by making it better and better when I already thought it was amazing. Thanks again!

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] laureanop:
Same setup here on the 384 mhz gpu. No reboots or freezes. Outstanding job Franco !

Now flashing the 512 version

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] BlueDynamo:
I'm not sure if this has been reported, but r180 seems to have broken video hardware decoding on apps like Dice Player and MX Player. My MKV of The Dark Knight no longer plays (it worked fine on r175).
[Samsung Galaxy Nexus] mursepaolo:
OK just downloaded the FK app. This app seems more involved than others. Anyone have any settings advice for saving the most battery? I'm on stock 4.0.4 rooted, dedoxed, zip aligned.
[Samsung Galaxy Nexus] EDNYLaw:
19x to 15xx Wheatley Governor is the new hotness, smartreflex in Franco's app makes undervolting pointless. Basically, for me at least, Wheatley is a great combo of performance and battery savings. If you use the 15xx slot it will perform the tasks as quick as possible then go back to the C4 state which, from what I understand, is basically "at rest." Works pretty well for me, prior to R180 I was using conservative governor 19x to 13xx and it was pretty good performance and really nice battery. Other users may vary but that's what my phone has liked.

I might also suggest switching to Droid Th3ory's AOKP based Patient Zero ROM as his tweaks plus Franco Kernels make my phone fly but I don't sacrifice battery. I regularly get 4+ hours screen on time and like a day between charges (depending on what I'm doing of course).
[Samsung Galaxy Nexus] anuraj1:
Hmm, I can't get r180 to work either. Won't get past the Google logo. I guess I'll go back to M4 and give that a shot... unless anyone has any ideas?

EDIT: on AOKP build 38.
[Samsung Galaxy Nexus] laureanop:
Are the people having install issues with 180 wiping dalvik and cache ?

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] sway40:
180 works for me, and the franco app finally let's the multipliers stick on reboot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] anuraj1:
Yes, A complete wipe, including cache and Dalvik. Thanks for the reply though, I am stumped.
[Samsung Galaxy Nexus] mike216:
I'm stuck between the latest two! Love them both and find interactive governor to be lightning on these two builds
[Samsung Galaxy Nexus] mike216:
you don't need to wipe either cache. Franco's script wipes for you
[Samsung Galaxy Nexus] zeke1988:
I used the franco app auto update. No issues so far.
[Samsung Galaxy Nexus] stick1300:
Well, this was worth knowing! I had taken to downloading the kernels via the app, then flashing them myself, just so I could make sure and wipe the caches. Guess I'll go back to letting the app do the work.
[Samsung Galaxy Nexus] mike216:
You can tell that the script wipes because of the (Android is Upgrading) directly after the flash. I think that means the dalvik cache is being rebuilt or the apk's are being zip aligned?

I do know his and ezekeels wipe. I don't like having the app auto flash but that's just me,take care
[Samsung Galaxy Nexus] anuraj1:
I wish mine would get that far on r180. This is the first Franco Kernel that my device has had a problem with.
[Samsung Galaxy Nexus] mike216:
Did you delete it and try and download another?
[Samsung Galaxy Nexus] mike216:
This 180 is really good on 4g I don't believe my eyes loosing an average of 2 1/2% every 5 minute's. I usually loose 3-4%
[Samsung Galaxy Nexus] ozymandiaz:
I tried twice each for the 384 and 512, then downloaded on my pc twice and it failed each time. That was on eclipse with full wipe each time after the first, then once each way on liquid. M4 works very smoothly with either rom though.
[Samsung Galaxy Nexus] anuraj1:
Yup, tried autoflash with both 384 and 512 mhz, and also tried to download both files and manually flash each one. All of them hang on the Google logo.
[Samsung Galaxy Nexus] mike216:
Strange, what from? Franco uses his own ram disc so that's odd
[Samsung Galaxy Nexus] mike216:
That happens all the time I usually try 20×
[Samsung Galaxy Nexus] anuraj1:
You have to try to flash 20x before it takes?
[Samsung Galaxy Nexus] laureanop:
I'm stumped on this one as well. I installed both the 384 and 512 versions with no issues and no wipes. People over at the gsm thread are reporting the same issues.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] upther:
Had some Bluetooth connection issues on 180 today. Worked fine yesterday but I rebooted before bed last night and couldn't connect to my Bluetooth speaker at all today. Reinstalled 175 and all is well.
[Samsung Galaxy Nexus] buckley101:
I'm getting terrible battery life. I was using lean kernel. Switch to 180 when I saw the update. Gps is off and 4g has been off all day... Only wifi and little 3g. Not sure what the problem can be.
[Samsung Galaxy Nexus] gnexdude:
I have been running 180 since release with no issues so far. Battery seems good so far ...too early to tell though...what i CAN tell is it is smooth and super fast!!!
[Samsung Galaxy Nexus] pluto22:
The CW & Crackle aren't working for me but HBO Go & MAX work fine. I flashed AOKP b38 at the same time so now I don't know which is the culprit.
[Samsung Galaxy Nexus] Amphibliam:
Android OS is really high. Yours is 23%, mine is 4%. I would dl BetterBatteryStats. It's worth the $3. Check for partial wakelocks. That's why your battery life is bad I bet.

---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM ----------

Idk why you guys can't flash it. Just auto flashed the 384 and booting up now.
[Samsung Galaxy Nexus] BlueDynamo:
Yeah, I'm not entirely sure. Oh, well. Hopefully, we'll see a new nightly soon. I can deal with reboots, but video incompatibility is a fairly major issue for me.
[Samsung Galaxy Nexus] pluto22:
YouTube won't play either. :(

Edit: found my problem, see a couple of posts down.
[Samsung Galaxy Nexus] zeroxg4:
Youtube works fine here. On r180 512 gpu
[Samsung Galaxy Nexus] Amphibliam:
works fine here too. What ROMs are you people having these issues using?
[Samsung Galaxy Nexus] mike216:
No to download the kernel, lately its been working better from the phone. Sorry o thought you were saying you were having trouble downloading
[Samsung Galaxy Nexus] sway40:
Yeah youtube works on mine...im on cm9.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pluto22:
The CW app is the culprit for me.

Everything works after a reboot until I launch THE CW app. It fails to load properly and then my other video apps don't work anymore. I was able to repeat this 3 times in a row.
[Samsung Galaxy Nexus] anuraj1:
Dang, cant get past the Google logo with this one either. I want to try wheatley and 1.5 so bad!
[Samsung Galaxy Nexus] BlueDynamo:
Which application are you referring to?
[Samsung Galaxy Nexus] raphenucleus:
I believe he's referring to this app.
[Samsung Galaxy Nexus] mike216:
Holy **** dude this beast is crazy at 1536!
[Samsung Galaxy Nexus] buckley101:
There is no app called better battery stats
[Samsung Galaxy Nexus] mike216:
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats

Here is better battery stats
[Samsung Galaxy Nexus] pluto22:
Yup, that's the one. Anyone else have a problem after running that app?

UPDATE: There was a CW app update today and it no longer crashes my video.
[Samsung Galaxy Nexus] pluto22:
Since your an XDA user - search the forums for the better battery stats app thread and you'll find a treat from the developer.
[Samsung Galaxy Nexus] buckley101:
It isn't compatible with my phone. I'm guessing it is because I'm on 4.0.4
[Samsung Galaxy Nexus] buckley101:
Never mind, got it from the forum thank you! Now I just have to figure out what this is good for haha
[Samsung Galaxy Nexus] ibenjakinov:
Does this kernel include any display modifications like the ones from ch33kybutt's CMPlus kernel?

1. Screenstate modes to control settings for CPU Scheduler, Virtual Memory & Music Mode

2. Reduced regulator voltages to VAUX3 and VUSIM for reduced screen-on battery consumption
[Samsung Galaxy Nexus] mike216:
181 is good on battery but not on wheetley. At least for me. Very good using ondemand. I know where talking performance on these latest nightlys I'm just sharing my experience
[Samsung Galaxy Nexus] spectrumfox:
Can someone please explain what the new scaling governor settings are all about with Milestone 4 and the latest Franco.Kernel Updater?

The new settings in new order are:

Lazy

Interactive

Conservative

OnDemand

Performance
[Samsung Galaxy Nexus] mike216:
Lazy is similar to ondemand and is made to be better on battery. A Google search will explain the best better then I ever could :)
[Samsung Galaxy Nexus] spectrumfox:
I checked Google but only found old information on his previous kernels.
[Samsung Galaxy Nexus] mike216:
You could probably go on the old info available for lazy. At least the theory of it
[Samsung Galaxy Nexus] psyren:
Had some issues with the screen taking a little while to come on, but fixed by removing the screen off freq cap. Running 384 GPU, 192-1536 r180, SR on, Wheatley. Device is performing very well, temps are fine (59°C now), no reboots that I know of.

Edit: on AOKP b37.
[Samsung Galaxy Nexus] pluto22:
I noticed the same. According to CPU spy its even 50% 384 / 50% 1228 on wheatly, even when I just left the phone in the Franco app or on the home screen doing nothing but tapping the screen once a minute to keep the screen on. The power usage was 1% every 2mins.

I tried the same test with on demand and was 85% 384 / 15% 1228.

I then set the min to 192 on demand and started browsing and reading the forums for 30 mins and lost 1% every 3mins with the CPU hitting 75% 192 / 25% 1228.
[Samsung Galaxy Nexus] Yatkoos:
I'm also unable to get 180 and 181 nightlies to work. Both just stick at google logo. Tried auto and manual flash. I've never had an issue before.
[Samsung Galaxy Nexus] mursepaolo:
I'm not sure if this is a Verizon issue, but I just lost data connection. I can still text, but that's it. I'm on r180.
[Samsung Galaxy Nexus] TEK112:
It sounds more like the dreaded GNex 4G data drop issue.
[Samsung Galaxy Nexus] mursepaolo:
Yeah I just flashed r181 and still the same. What do I do?
[Samsung Galaxy Nexus] TEK112:
I would start with a cache and dalvik wipe and if that didn't work, I would reflash the 4.0.4 radios.
[Samsung Galaxy Nexus] mursepaolo:
Just did all that. No luck.
[Samsung Galaxy Nexus] Gahh Its Lee:
Give it a week if it does it continually call vzw and get a replacement sim if that doesn't help new device time activate.
[Samsung Galaxy Nexus] mursepaolo:
Dang new device? I just got this used last week. I hope this is a vzw problem.
[Samsung Galaxy Nexus] TEK112:
I wouldn't wait that long.

First, turn off phone, remove sim, reboot, turn off phone, reinsert sim and reboot.

If that doesn't work call them over the phone and ask if they can mail a sim to you to avoid having to flash to stock (don't tell them you are rooted). If that doesn't work or if the sim doesn't help, time to have it swapped out on warranty.

---------- Post added at 12:39 PM ---------- Previous post was at 12:38 PM ----------

You could always just call and ask for help.

Also, don't *228 your phone or it can't tank your sim.
[Samsung Galaxy Nexus] mursepaolo:
OK it magically returned. I'm new to GNex. Is this fairly common?
[Samsung Galaxy Nexus] mike216:
Yep that's the way this governor is designed. Grab system panel from the market and you'll see how the CPU throttles all the way up. Not all the time but it is built to finish the job quick and therefore save in the long run. The problem is if you read a lot like me then I feel this governor isn't for me but for gaming and heavy use its going to be good for you when it comes to saving battery
[Samsung Galaxy Nexus] mike216:
If I were the few that this is happening to then I would flash my rom over but this time manually (format boot) in recovery. Maybe the rom scrip your using had a minor bug and didn't format the boot properly. I'm fairly certain this will work.

To format the boot go to advanced,mounts and storage, Format boot,system then flash your rom. No need to wipe data
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea. If it drops out ALOT you may wanna call and try a new sim and do all that. I've been getting crazy drops and gotta order a replacement but need to wait 9 days
[Samsung Galaxy Nexus] mike216:
cool so ondemand at 192 gave you the most battery life? I'm hesitant about 192 for battery. All the CPU scaling seems it would be worse on battery. Your doing consistent testing though so your the perfect person to ask
[Samsung Galaxy Nexus] FlipFlops24/7:
ISSUE: Phone Reboots and Hangs on Boot Animation

INSTALL: Fresh and clean install of AOKP B38 with franco.Kernal Milestone 4 Stable

SUMMARY: My phone was working perfectly, then I tried to respond to a text message and it rebooted and hung at boot logo (thank God for Nandroids).

This happened to me yesterday as well after upgrading to Milestone 4. I wiped the phone, reinstalled AOKP B38 with francos kernel and BAM, it happened again. Yesterday I simply tried to open Gmail and it rebooted to the boot logo and hung there.

SOLUTIONS??:
[Samsung Galaxy Nexus] spinkick:
SUGGESTION: try a different rom with Franco's kernel.

INTERAGATIVE : do you overclock the cpu at all?
[Samsung Galaxy Nexus] FlipFlops24/7:
No overclocking at all. What's the next best ROM after AOKP? Would Logcat record the issue right before the phone reboots and hangs?
[Samsung Galaxy Nexus] alphanu22:
Black Ice
[Samsung Galaxy Nexus] spinkick:
I would use liquid smooth 1.4, its not the next best thing it's actually better.
[Samsung Galaxy Nexus] EDNYLaw:
I'm running Patient Zero by Droid Th3ory, it's an AOKP base, zero problems with any Franco kernel and DT's tweaks make this thing fast. It could also just be your device, if it's hw rev 9 and not 10 that could be it or your device might just not like this particular revision of the kernel, some people reported no success on r180 but success on r181 or vice versa or none, seems to be very device specific

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] FlipFlops24/7:
I'll try Liquid Smooth. However, since this has happened twice after two complete wipes and flashes of AOKP B36 and Francos milestone4, will logcat record what caused the reboot so I can send that to franco?
[Samsung Galaxy Nexus] spinkick:
Maybe?
[Samsung Galaxy Nexus] Mayze23:
^^This Black Ice is awesome & works perfectly with Franco's kernals
[Samsung Galaxy Nexus] shadowstewie:
There's a problem when I flashed over to Milestone 4. When I play Google Music through my aux cable on my head unit in my car, it will play the music for a couple seconds and then pause itself. It repeats doing that every time I hit play again.

I never had a problem on LeanKernel. Any ideas?
[Samsung Galaxy Nexus] stick1300:
Turn your volume down from max. It does that to me too. Turning it down, even one notch, fixed it. Plus, with your volume all the way up, the sound quality suffers (even through headphones/aux cable), so you're doing yourself a favor.
[Samsung Galaxy Nexus] upther:
If you're using Franco's app then you should go into the maximum sound volume hack and set it to 1 or 0.
[Samsung Galaxy Nexus] mursepaolo:
I don't know if this is another common issue, but just today I had a call on speaker and tried switching to handset. I heard some static then I was unable to hear them. However the call continued just fine when I put it back on speaker. This hasn't happened before.

Rooted 4.0.4 r181
[Samsung Galaxy Nexus] anuraj1:
I'll give it a shot tonight after work. I always manually install, and I wipe "system", but have never thought to wipe "boot".
[Samsung Galaxy Nexus] pluto22:
It really depends on what activities you are doing. I found cards games, browsing, email, etc actually stay at 192 the majority of the time so I get at least one more hour of screen on time (over 5 hrs screen on time with Bluetooth and wireless connected).

On a full charge if I play a graphic/CPU intensive games and drain the phone I get 3.5-4hrs. I haven't found much difference changing the min CPU or governor since it scales right up to max and sits there for a good portion of the time (note: forget about melting butter, at this point I can cook a steak on my phone ). I haven't tried wheatly yet on a graphic intense game from full charge to drained but it sounds like it may squeeze out some more time.

One of the great things about our phones and kernels is how easy it is to change the governor and clock speeds so you change it on the fly depending on your current usage. During the work day I run on demand or conservative @ 192 / 1284 since I mainly use email and I'm at a desk PC. At home I may change the min to 384 or 729 depending on how frequently I'm using the phone and for what apps but usually I just leave it at 192.

Hope this helps some.

Btw, I find it hard to believe anyone that says they consistently get 5+ hrs screen on if they are hard core gaming or on LTE. Even normal usage with 3G constantly on is hard to believe unless you are using something like Juice Defender (ex: 10hrs+ with 3G on and 5+ hrs of screen time), at least on the Verizon LTE version. :-)
[Samsung Galaxy Nexus] pluto22:
Makes sense, I'll give it a try when gaming. Sounds like it could add some battery and every little bit helps!

Thanks for the info!
[Samsung Galaxy Nexus] hyp3nitis:
I've had my nexus for 6 months and I have had the garbled font problem whole time. I did a clean wipe and did not restore anything and it still came back. IM on aopk 38

Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2
[Samsung Galaxy Nexus] StormCell:
I thought there was something wrong with my unit and was going to call Verizon. WTF is going on? Music is completely unusable now! Any fix??? Thnx!
[Samsung Galaxy Nexus] Gahh Its Lee:
If the volume boost is at 3 put it down to two or turn your volume on your phone down a click or two
[Samsung Galaxy Nexus] timbck2:
Liquid Smooth. And I wouldn't put it *after* AOKP, I'd rate them about equally.
[Samsung Galaxy Nexus] alphanu22:
just a fyi to all, if "Min cpu" is set anything other than 192 MHz, it takes forever to get it to Deep Sleep, leading to Battery Drain even tho screen is off- :cool:
[Samsung Galaxy Nexus] tallnerd1985:
I am in the same boat, had to revert back to build #166. I am not sure if this is getting overlooked by the million idiots that have to post "I just installed #181 and it works great, blah, blah, blah!". These threads are to be used to post issues with updates or concerns. If Franco wanted to hear if it even installed and worked, he would forgo his alpha testers before releasing it.
[Samsung Galaxy Nexus] Kylem:
Audio playback (Podkicker pro) stops randomly for me on milestone 4 running liquid 1.4. Screen on or off.

Reflashed MS3 and all is better. This a known audio bug with 4? Which nightly fixes it?

Edit: just read some more of this ever growing thread and learned that this is happening because my volume is maxed or boost is too high. Boost has always been at 2 since MS2 or so and volume is always maxed for loud road noise (I-5 sucks). The audio cutting off has never been a problem before I went from ms3 or n161+. It began at ms4, seems like a bug to me.
[Samsung Galaxy Nexus] andrew53517:
I'm not sure that is true... My device sleeps instantly with the 384 frequency. Anyone else care to comment on this?
[Samsung Galaxy Nexus] TEK112:
Your phone should always sleep. Even at high speeds, 700MHz and so on.
[Samsung Galaxy Nexus] laureanop:
My device sleeps instantly on 384 192 or 729 as long as I'm on on demand governor. The other ones are not as reliable.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] laureanop:
On demand proves to be the best governor every time for me. However, it doesn't like the 1400 and 1500 frequencies. Wheatley does a much better job with those

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] upther:
I believe Nightly 166 was the last kernel that didn't have this problem. I used to be able to set my max at 3 without a problem. Now I have to go down to 1 to avoid the stop playback issue.
[Samsung Galaxy Nexus] mikaeldalc:
I downloaded betterbatterystats and this is what I'm getting. Any ideas?
[Samsung Galaxy Nexus] sinik420:
lol to not reading the post, "And anyway, it is reset every time you unplug from power with a relatively full charge (thus why the battery usage UI data resets at that point), so this would be a much easier way to make it go away."
[Samsung Galaxy Nexus] Magnus_CA:
And lol to trying to make yourself sound like a smarty pants in your initial post and not giving credit to an article posted just three days ago.
[Samsung Galaxy Nexus] sinik420:
Removed- Off topic for kernel thread long enough