yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Tito2007:
Still having music pause for me at full volume.

Google play music

384-1305 frequencies

Stock voltages

No UV

192-320 kbps music quality
[Samsung Galaxy Nexus] rodmc123:
im experiencing a lot of SOD, almost every night. (im on r356 yet).
[Samsung Galaxy Nexus] epunk:
Please be less specific, such as not specifying which settings you're running, which ROM and not providing your logcat:P
[Samsung Galaxy Nexus] VeEuzUKY:
I beg U guys not throw rocks at me on this as this thread is almost 3700 pages long..

This kernel is on my Nexus and rocks!!!! Zero questions on that.. however, my humble question is, can I install Milestone6 on another other Tab running Android 4.1 (like the Galaxy Tab 8.9 I have running CM10 and/or AOSP ROMs) or a black hole will swallow my tab, then the universe, and then send us all to where 2012 didn't?:cyclops:

:DHappy New Year everyone by the way:D Franco, UR a genius.. UR code should be on every phone and Tab on the market! Cheers:good:
[Samsung Galaxy Nexus] aR_ChRiS:
You have to be on crack or meth to think that you can flash a galaxy nexus kernel onto your whatever tab you have.
[Samsung Galaxy Nexus] VeEuzUKY:
Thats why I asked.. the meth and crack I use really ****ty.. OK now I know.

..and by the way, long ago I installed the older Android 2.x Kernel in more devices than the one for that it was originally intended and it ran.. so, its the way things go, even though Android 2.x was way more flexible and forgiving on a wider range of hardware then 4.x is.. crack or no crack..

http://xdaforums.com/showthread.php?t=1049518
[Samsung Galaxy Nexus] -star-:
It worked sometimes, because there are some phones that have the identical hardware specs but with different names e.g branded s1 and the international s1.

And btw I faced this "problem" one or two times on ics, but it seems that it's also present on jb. I charge my nexus to100% and shut it down after the charging cycle. If I try to turn it on the battery is empty.

Stock rom and latest kernel.
[Samsung Galaxy Nexus] Jamdat33:
Bluetooth internet tethering to my tablet is still broken in latest nightly r357
[Samsung Galaxy Nexus] itasoulas:
345 and 348 were awesome! After last, things are getting more experimental :confused:
[Samsung Galaxy Nexus] alexdemonumber3:
Weird freeze while using Facebook and pulling down notification bar. :/ back to r356 for me, which runs like a champ!
[Samsung Galaxy Nexus] viewtifuljoe71:
I feel the same way. I running r345. I tried all of the experimental ones, but I keep coming back to that one.
[Samsung Galaxy Nexus] alfiemenace:
I don't get why that happened to you. You're choosing between r356 and 357 while the only thing that's changed is the sound thingy and you experience freezes??something must be wrong in your end.

Stock ROM, custom user.
[Samsung Galaxy Nexus] jcmm11:
Considering the difference between 356-357 highly unlikely that this was caused by the kernel. More likely it was a one-off. Then again I'd just blame Facebook. I hear that app is poorly coded anyway. Plus Facebook is just evil in any case :D
[Samsung Galaxy Nexus] malaroth:
Facebook is always frozen for me! Hurrah for TiBu bloatware freeze!

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] jhearrtot:
hi team and to franco!

my nexus previously runs on r356 and PA2.99 ver9 with LMT working perfectly even on previous franco kernel versions until today when i installed the latest nightly r357 via fKu app.

LMT service is running, but the gestures or pie control doesnt work anymore. tried clearing its cache, tried also wiping cache and dalvic cache, reflashed r357 manually, restored back to r356 even - but to no avail.

no other things/settings changed except updated to r357

your thoughts?

edit: installing the latest version of LMT worked perfectly with r357
[Samsung Galaxy Nexus] lesp4ul:
Last time i used 356, my fb was alright, notification pulldown alright as well. 1 thing made me back to 348 is ringtone/notif/alert volume way too low on 35x. Dunno, but 348 volume is higher on my phone (rasbean 21) :)
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I've had audio problems with r356 and r357. Note: r348 does not have this -

When I plug my phone into my home speakers or car speakers using an 1/8" audio cable (line out), the audio will switch back and forth between the external and internal speaker. This doesn't happen with every audio file. I listened to TWiT and it played entirely through the external speaker just fine...but when the next podcast played (BYOB Podcast), it cut in and out.

I run Misledz NexusLouder setup, but like I said above, r348 is fine. Does it have to do with the recently implemented headphone boost code in the kernel?

RasbeanJelly 12/30 Build.

RF
[Samsung Galaxy Nexus] shreddintyres:
are the file formats for the two audio files youve mentioned the same? (flac, mp3, ogg, etc) same bitrate? have you tried using different audio players?

i have yet to experience playback switching between line out and external speaker. and have yet to test 357 with aux cable. but on 356 audio only paused and resumed playing.
[Samsung Galaxy Nexus] malaroth:
Yes, the whole reason for 357 is the audio fix. Not sure exactly what the fix entailed whether a switch from hard coded level 3 audio boost to 2 or 1 or if there was much more coding involved that would suddenly make Facebook freeze. But again, some apps may not like the kernel. C'est la vie

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] ethanhunt123:
Still having sane audio issue
[Samsung Galaxy Nexus] Ronaldo Forenucci:
They are .mp3, don't know the bitrate. They are all downloaded with BeyondPod and I've been listening to them for years...same stuff. I just re-flashed r348, and am listening to the same podcast that cut in and out a few minutes ago...it is perfect with r348, no speaker switching. I'm plugged into a set of Logitech Z-680 5.1's with an 1/8" audio cable. This has never happened until r356. I didn't try anything after r348 until r356, so I don't know if r355, etc... had it too. Been 5 minutes since I started this post, and r348 is fine.

RF
[Samsung Galaxy Nexus] malaroth:
This is just my observation... but it does not seem necessary to keep repeating "it didn't work, I gave up and went back to a previous version". The point of this thread is to post issues that you have not been able to find a work around for (by searching the thread diligently) and to post solutions/logs/detailed reproduceable steps so the Dev and others can help to find a work around. Not everyone is experiencing all of the issues. Very sorry if you are and glad to help fix it if possible.

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!

---------- Post added at 11:49 AM ---------- Previous post was at 11:47 AM ----------

Ronaldo... r356 has the known audio issue. The latest 357 has the fix for it released 24 hours ago. Not sure if a logcat will show the problem but you say the song just stops? What does the player show?

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!

---------- Post added at 11:53 AM ---------- Previous post was at 11:49 AM ----------

Give osm0sis something for his hangover... customer service aisle 9 please

JBSourcery 4.1 Franco 357 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] allgsmnetwork:
LMT what is?
[Samsung Galaxy Nexus] CarlosAbia:
http://xdaforums.com/showthread.php?t=1330150
[Samsung Galaxy Nexus] armisis:
Is it a kernel issue when a tethered device cannot access the Internet if a vpn is active?

Using cm 10.1 latest nightly and r356.

Thanks,

Dave
[Samsung Galaxy Nexus] ChazzMatt:
Well, at least it's not a crazy audio issue. :victory:

(Where's a drum rim shot when I need it?)
[Samsung Galaxy Nexus] finesse:
I sincerely apologise, I have searched but not found.

Can someone please post the link to the osm0sis Franco settings (colour, voltage etc)
[Samsung Galaxy Nexus] viewtifuljoe71:
http://xdaforums.com/showpost.php?p=34951507&postcount=34564
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Going back to a previous, known working build, is valid, IMO, as it rules out the problem being with something else. Once a problem is confirmed, going back is the only solution *if the problem is one that affects daily use*. If I never used Line Out, I would stay on r357.

As for the second part: I know r356 had an audio issue (but another one, as I never had the pausing/stopping, because after flashing from r348, I immediately used Line Out and found the internal/external speaker switching). I also waited, and flashed r357 when Franco announced it, and it too has the same problem. So no, I never had the pausing (that I noticed, but it may well have manifested itself if I tried different scenarios), I had internal/external speaker switching through a Line Out cable.

So, if the ROM, Music Player, Content, and NexusLouder patch remained the same (and never exhibited the problem before with r348), and the only thing that changed was the kernel - from r348 to r357 - it's something in the kernel, no?

Just trying to help Franco see if he can confirm/find the problem, nothing else, cheers!

RF
[Samsung Galaxy Nexus] finesse:
thanks for your post!;)
[Samsung Galaxy Nexus] spitefulrain:
I was wondering why my desk speaker wasn't working right. But even though it wasn't loud, turning the phone volume down worked for me.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Can you explain in detail what you experienced? All my volumes were maxed, and I didn't try lowering the volume. On r348 now, all my volumes are maxed as well, and all is fine. Thanks for the input.

RF
[Samsung Galaxy Nexus] allgsmnetwork:
Benchmark RB 3d point 3700 at 1305 and S3 end note 2 4000 point :)

https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsInJ1LnJkbW9iaWxlLmJlbmNoIl0.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] jeetS:
Thats very interesting…Thats what the early versions of the MinCo ROM used to do. Vomer released an audio patch that fixed it. Its no longer a problem with MinCO but interesting that the exact same symptoms are showing up...
[Samsung Galaxy Nexus] franciscofranco:
The audio chip on this device is strange. I'll try to fix it, I think I know what is the problem in my code :)
[Samsung Galaxy Nexus] Ronaldo Forenucci:
You rock, my friend. The amount of work that you put into this stuff, for free and because of enjoyment, is amazing.

RF
[Samsung Galaxy Nexus] Angelakaro:
Never had audio/google play music problems with r356 nor r357

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] itasoulas:
never had the chance to thank you myself...awesome work! The frequency of updates is simply insane :silly: Thanks man :good:
[Samsung Galaxy Nexus] The Gingerbread Man:
Is there any chance this will make the over all volume louder when 60hz is boosted when playing from phone speaker? I know its too low to hear from the phone speaker but sounds better on head phones and the bass boost doesn't really work for really low notes

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spitefulrain:
On 357, when I plugged in the line out and played music it would rapidly switch between playing on the desk speaker and the phone speaker. Unplugging and plugging it back in changed nothing so I turned the volume down on the phone and it went away. This was last night. Earlier today though the music just stopped like it did on 356 if the volume was up all the way.

And on 348 all was fine too, I don't think the audio boost was in at that point
[Samsung Galaxy Nexus] The Gingerbread Man:
Also I would like to apologise to allgsmnetwork and everyone else here for making a **** of my self having a rant, my post got deleted and rightfully so by a moderator so sorry to who ever it was who had to deal with that, if I got reported I'm not surprised in all honesty. I was having something of a bad day, not that excuses help and more than anything else I feel perhaps maybe I might of lost some respect from you guys by showing off. So again I'll say sorry. Normally I'm I'll with helping less experienced guys and accumulated my this meter mostly like that.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yup! That's it. It's 2 now.

sound: reduce one step on volume boost because previous value was making some users have their music stop randomly.

https://github.com/franciscofranco/Tuna_JB_pre1/commit/e2f047dece3e38f20fa3d46c2ebdd4b4e09d3f9c
[Samsung Galaxy Nexus] Sparx639:
Yes but if you continued to read, I mentioned that I was also having the same problem with franco's kernel, I fixed my problem though
[Samsung Galaxy Nexus] shreddintyres:
Looks like 357 solved all issues i had with audio :good::highfive:

Thanks franco for all your hard work and continued support
[Samsung Galaxy Nexus] modifii:
Battery works quite longer with 356/357 than earlier builds. Attached results I got from 357 on stock kernel settings (including Gov/IO, clock speed, UV) and on EDGE. Screen on time 4:15hr is by far the best by my any android phone till now. And oh I started off at 98% battery (Battery Life Extender set on 98%).

Franco, you are master of kernel tuning.
[Samsung Galaxy Nexus] allgsmnetwork:
Exactly I reason so 'always help the less experienced and do not take them for a ride like that screenshot of the monkey and to thank all went over the edge and I made the report to the moderator otherwise only those users with the brain half continued.I hope you understand me...
[Samsung Galaxy Nexus] reaper000:
I think this one was the worst translation yet.

However, in all fairness, I'm sure my Italian would make allgsmnetwork laugh just as much if not more. I do like his point of helping the less experienced (like me).
[Samsung Galaxy Nexus] r47z:
357 is the best so far.
[Samsung Galaxy Nexus] peikojose:
357 works good (excellent battery life I can reach 4 hours of screen on time) but I still get artifacts with the sound.

PD: did I read screenshot of a monkey?
[Samsung Galaxy Nexus] nikulogical:
Screen shot of the monkey? LOL are you talking about my confession bear?

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] bat0nas:
Same here. I have SODs quite often.

Stock GSM ROM (4.2.1)+ always the latest franco nightly.

Any ideas?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
flash r348.. no SODs
[Samsung Galaxy Nexus] allgsmnetwork:
I had a single SOD #357 maybe too much UV is stable now, videos of you tube feel at low volumes also stock kernel in telephoning speaker good :confused :
[Samsung Galaxy Nexus] slayr76:
Been using r357 for 2 days now an not a single sod, so its a keeper this time.
[Samsung Galaxy Nexus] cryingrock:
been using r357 for one day and no problem so far, a bit smoother than r348. will keep using it:)

Edit: using stock 4.2.1 and just raised the CPU frequency a bit with other setting untouched
[Samsung Galaxy Nexus] Vangelis13:
Thanks but no thanks; I like keeping things clean. Plus, that's no sport. Either wipe & re-flash or not..

Long live Nova launcher backups & titanium backup!! :-D
[Samsung Galaxy Nexus] IMGetwired:
GAH -- Ears still burnin'! I can haz Voodoo sound?

Franciso,

Just wondering what kind of progress you might have made on this item ^^.

MORE IMPORTANTLY: Thanks for an excellent update w/ lucky #13! Nice app update and kernel update! I'm happy to support an excellent dev like you, and am excited about what is still to come.
[Samsung Galaxy Nexus] stellaryt:
Finally I bought the updater from market~coooool:D

Market system thought me using a Tmobile Gnex lol.So I can buy it~
[Samsung Galaxy Nexus] brunsbanjo:
what about smartreflex?

http://elinux.org/OMAP_Power_Management/SmartReflex
[Samsung Galaxy Nexus] aimetti:
Seems good so far. Can't notice any decrease in speed etc.

Browser mark went from 120k to 123k

Antu went from 7100 to 6400 (same as others)
[Samsung Galaxy Nexus] iamchucky:
Settings don't stick after reboot

Hi Franco, I am using the build #13 and I set the color and the overclock settings with with the latest franco.Kernel updater. But they don't stick after a reboot.

The files/value in the init.d are correct after a reboot but the actual color and the frequency doesn't stick.

Is there anything I can provide to help debugging this problem?:confused:

Edit: I am using bigxie's IML74K Android 4.0.3 Build 7-2
[Samsung Galaxy Nexus] Elganja:
running this exact setup... will have to do more testing

this kernel has been awesome for me... thanks Franco
[Samsung Galaxy Nexus] jetrii:
Android OS is eating up quite a lot of my battery. What tools are good for determining what is causing it?
[Samsung Galaxy Nexus] samizad:
I see Francisco didn't put a little sample picture in the kernel settings menu of the updater app. How are people picking the best colour settings? I change the numbers but my brain is too slow to notice the difference.

I am still testing the kernel 13 so no comments yet :)
[Samsung Galaxy Nexus] D_Magic:
Betterbatterystats, you can find it here on xda
[Samsung Galaxy Nexus] samizad:
There's a big thread about this here http://xdaforums.com/showthread.php?t=1387243

The consensus is that the % shown in the battery stats is meaningless unless you look at the whole picture. Do some proper calculations and you'll see that Android OS is responsible for 0.35 to 0.5% per hour of the battery drain, depending on how many and which apps/widgets you have running.
[Samsung Galaxy Nexus] franciscofranco:
Why do you want a sample picture? If you change the offset numbers you'll see a different in the second. Try setting 50 in the red field and you'll see what I'm talking about ;)
[Samsung Galaxy Nexus] Felixpau86:
Speed/smoothness: Not too much difference from 12 if at all.

Battery: Consumption is up compared to 12.

Everything else is great. Also bought app to support you... keep up the great work.
[Samsung Galaxy Nexus] bradm23:
A little curious if interactive or conservative gov is the better way to go. Seems like interactive yields better performance with a little sacrifice to battery. Just curious to what others have been having success with
[Samsung Galaxy Nexus] ellesshoo:
For those of us who like the flexibility/automation of shell/scripts and looking for the UV sysfs interface, here ya go.

Just substitute your own mV table values (below are the kernel's default). Shouldn't matter if you change the table in either cpu0/cpu1, it will apply to both of course. You should include all 5 values in descending order even ones you're not changing the value of.

echo "1300 1200 1100 1000 900" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1300 1200 1100 1000 900" > /sys/devices/system/cpu/cpu1/cpufreq/UV_mV_table

And of course if you want to read the values in the UV_mV_table:

cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

cat /sys/devices/system/cpu/cpu1/cpufreq/UV_mV_table

The output looks like this:

1350mhz: 1300 mV

1200mhz: 1200 mV

920mhz: 1100 mV

700mhz: 1000 mV

350mhz: 910 mV
[Samsung Galaxy Nexus] sirj00:
Hello Franco, Still running your kernel with axiom 2.4

Tried the leankernel yesterday while waiting on 13, and my phone

rebooted 3 times in less then 30 minutes.

Needless to say I'm running 13 and my phone feels right at home.

Great job as always, thank you.

Just curious, I get around 7hrs of battery life while Listening to Pandora

and surfing on 4g or wifi nonstop. If idle well over a day plus.

I'm very happy with this results, is 7 hrs about right?
[Samsung Galaxy Nexus] StuMcBill:
Yeah, definitely more battery drain in Nightly 13!
[Samsung Galaxy Nexus] franciscofranco:
I noticed it too. Time for digging ;)
[Samsung Galaxy Nexus] StuMcBill:
Excellent, look forward to the next release! :D
[Samsung Galaxy Nexus] dyndragon:
I've gotten down as far as 1050, 950, 800, 675 (note that I don't use the 1350mhz slot) and stable! These are some good chips here! I bumped everything up 25mV from there just to ensure stability. Anyone else stable lower?
[Samsung Galaxy Nexus] franciscofranco:
First kernel of 2013 :)

* Added ROW I/O scheduler for testing purposes. Its a IO scheduler from Qualcomm that prioritises Reads over Writes, thus the ROW name. I added it to my Mako kernel as well. Although deadline is still the default as ROW is only for testing.

* Some more audio changes hoping to fix the latest releases issues. Need feedback on this, if the issues are fixed, if the audio is louder than stock etc

EDIT: By the way just noticed this had more than 5 million views, almost as much as some popular Youtube videos! Kinda scary, but awesome feeling :)
[Samsung Galaxy Nexus] michi_1983:
thx Franco!

your app though says the md5 checksum doesnt match, so it wont apply from auto flash option.

greetz
[Samsung Galaxy Nexus] alfiemenace:
hey man, i flashed r358, booted then set i/o to ROW, then opened xda app and my phone just hanged and rebooted on it's own. after booting i was trying to post my kmsg here and post this message then it hanged again. here's my two kmsg for the two hangs. hope it helps!

then it happened again, third time. so i'm attaching 3 kmsg. here it is
[Samsung Galaxy Nexus] michi_1983:
confirmed, same here
[Samsung Galaxy Nexus] franciscofranco:
Nothing particularly interesting in the logs :(

Anyway don't use ROW if it fails for you, its merely experimental, but thanks for testing.
[Samsung Galaxy Nexus] Khrushy:
Tested ROW, locked up and rebooted in reasonably fast fashion. Twice.

Still travelling, so can't pull a kmsg sorry.

Back to deadline anyway.
[Samsung Galaxy Nexus] allgsmnetwork:
Thanks franco :) posting video you tube please :cool:
[Samsung Galaxy Nexus] osm0sis:
ROW worked here. Still finding deadline smoother though. :)
[Samsung Galaxy Nexus] modifii:
Using ROW, no reboots. No major difference in speed compared to Deadline though. Still too early to conclude.
[Samsung Galaxy Nexus] allgsmnetwork:
Tested ROW no problem at 1420,the benchmark with antutu great and good GPU...other governor interactive with ROW?
[Samsung Galaxy Nexus] franciscofranco:
Me too :)

Can anyone tell me hows the sound with this r358? Its absolutely fine for me.
[Samsung Galaxy Nexus] allgsmnetwork:
Same performance as the deadline but the audio call splits the ears too high :eek:
[Samsung Galaxy Nexus] The Gingerbread Man:
Is there any specific tests you want doing or anything?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
Can someone tell me if there is something unusual in my logcat and dmsg? Last post of this thread http://xdaforums.com/showthread.php?t=2055260&page=4 ,i am getting little freezes with franco r300 using aokp milestone 1
[Samsung Galaxy Nexus] franciscofranco:
Turn down the volume a little bit :p

If its high enough, if it has the bugs reported on last pages etc :)

Kernel log shows nothing wrong.
[Samsung Galaxy Nexus] calinoii:
Franco,I got those freezes with any rom even stock,when my phone heats a little ~60-65 degrees C. I got this issue with Lean kernel too.If I just flash another kernel than yours and lean,the freezes dissapear. :-??
[Samsung Galaxy Nexus] The Gingerbread Man:
OK so call volume seems OK I think, I don't have anything to like a car stereo to try playing music from to test for these pauses. I did notice the bug is still there with 60hz is boosted, the volume won't go above 50% but its probably a safety feature to stop the speaker getting blown. Headphones iv not tried yet but last couple of releases they have been fine. I tried my mini speakers quickly just now and the sound didn't cut out when I boosted volume to 100% with stock eq turned off which was bloody loud and had to stop before my neighbour's complain (I live in semi detached house)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] anshulajain:
Thats because you rock, franco...the Psy of Android world :):good:
[Samsung Galaxy Nexus] mmmcfc:
I'm on stock ROM with no UV or OC. Also haven't used any of the custom kernel features. Never experienced anything of the sort with previous versions, thankfully it hadn't happened again since I updated to 357 :)