yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dyndragon:
CM10 has some ramdisk changes that Franco said he will adjust for in the next build. He did not say when. Just wait.

Tried Trinity, too much crap (in particular, auto brightness doesn't seem to work right). Back to CM10 default kernel until Franco updates his JB kernel to make it work!
[Samsung Galaxy Nexus] The Gingerbread Man:
I love how you always say ****, for errors or just for fun. It amuses me how you can just say you don't under volt a single ****, made me smile

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Wing_Zero85:
thnx again ;)

Just for instance, i've managed to compile the kernel right with your useful tips (unwind frame issue), but there was another "error" the compiler gave me:

block/cfq-iosched.c:1513: error: void value not ignored as it ought to be

make[1]: *** [block/cfq-iosched.o] Errore 1

make: *** [block] Errore 2

I've had to comment the line you've added for the alias...
[Samsung Galaxy Nexus] franciscofranco:
You should be using my config that is exported to /proc/config.gz. Anyway you need to disable CFQ in the building process.
[Samsung Galaxy Nexus] Wing_Zero85:
Ah ok!

I thought i was doing something wrong...and indeed it is :P

I've purchased the kernel updater app, and I've tried to set the volume boost from 0 to 3...but nothing changed...when I receive a call volume is the same..maybe in jelly bean it doesn't work for some reasons?
[Samsung Galaxy Nexus] franciscofranco:
The volume boost is for headhphones, not for calls ;)
[Samsung Galaxy Nexus] Wing_Zero85:
Sorry,

I meant the speaker of the phone. When I receive a call I can barely ear the phone ringing if it is in my pocket...there is a way to boot the speaker volume??
[Samsung Galaxy Nexus] superbobup:
The volume boost is oy for the 3.5mm jack, meaning you need to have headphones plugged in ;)

You can try boosting speaker volume with volume+ but I'm not sure if it works on JB
[Samsung Galaxy Nexus] vomer:
Ahh ok thanks. May I ask which ROM? :p

Also the app just crashed when I tried to set power mode on boot (r220). I sent report via google.
[Samsung Galaxy Nexus] franciscofranco:
The rom I'm using it's a secret for now.

Which app version are you running? 5.8.2 doesn't crash that, I fixed that bug.
[Samsung Galaxy Nexus] vomer:
:O SECRET?! Fanco.ROM :D

Yup same version. It could be because of my ROM too if it is fine on your end.
[Samsung Galaxy Nexus] franciscofranco:
r221:

* Compiled with 4.6.x toolchain from Google

* Should boot on CyanogenMod Jelly Bean based roms

* Add Imoseyon's fix for random MAC id bug that plagues some users

* Merge Kalim's fix for toroplus compass bug

* Merge cynewulf's fix for a bug on the dock mode

* Reduced startup delay when enabling Wi-Fi

* Compiled for the cpu instead of compiling for the arch
[Samsung Galaxy Nexus] Wing_Zero85:
Thanks man!!
[Samsung Galaxy Nexus] vomer:
Thanks! Flashed :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Bavilo:
Hmm r221 still won't boot on cm10 based ROMs :-(
[Samsung Galaxy Nexus] hardeep:
holy ****... my wifi connects damn fast... :)))))))

running AndroidMe 1.2
[Samsung Galaxy Nexus] franciscofranco:
Can you get me a dmesg log plz.
[Samsung Galaxy Nexus] Bavilo:
Not at the moment sadly. As soon as I have access to my PC i 'll get you the log. That is if no one else is faster...
[Samsung Galaxy Nexus] dyndragon:
Sorry...still not booting on CM10. What do you need to troubleshoot?
[Samsung Galaxy Nexus] kuntau:
Sorry if this had been answered. What scheduler franco kernel use? And how do i change them?
[Samsung Galaxy Nexus] Bavilo:
He needs the dmesg log. I'd do it. But I'm on the road atm.
[Samsung Galaxy Nexus] franciscofranco:
I need the dmesg log when the device is booting because I need to see where it's failing.
[Samsung Galaxy Nexus] defconoi:
After flashing I had to pull battery on stock deodexed JB. Looked like a sod, placed back in and it eventually booted but took a lil longer, no problems since.
[Samsung Galaxy Nexus] nikulogical:
Same thing here..
[Samsung Galaxy Nexus] Bram77:
After flashing #221 on Paranoid Android (Cyanogenmod 10 based) my phone kept loading forever. So I pulled the battery, wiped cache and dalvik en flashed Trinity again. But now my phone still won't boot. What can I do to make it boot again. I did not make a backup before flashin #221 unfortunately.
[Samsung Galaxy Nexus] nikulogical:
This kernel also won't let me stream music with the screen off..
[Samsung Galaxy Nexus] dyndragon:
For some reason I'm having a lot of trouble getting a dmsg from my device. Last_dmsg doesn't exist in /proc after I pull the battery to reboot to recovery...and I can't get it live from the device while it's booting up either. Any tips?
[Samsung Galaxy Nexus] Ringo.C:
r221 is pretty good:p
[Samsung Galaxy Nexus] dyndragon:
Nevermind. I un-noobed myself.

See Dmseg file attached. and for good measure, kmsg while booting.
[Samsung Galaxy Nexus] superbobup:
Over WiFi? Try enabling PM fast for WiFi in the app :)
[Samsung Galaxy Nexus] Hanny:
if i remember well, it is sio. however it is the only scheduler in franco's kernel so you have no option :p

but FYI the easiest way for you to change an i/o scheduler is by using no-frills cpu control from the market. :)
[Samsung Galaxy Nexus] WitchMX:
Just flashed 221 on AndroidME 1.2 everything seems to be running fine. I come frome Bigxies Jb Rom +220 at 1.4 OC. So far AndroidME+221 seems a little snappier, no OC.

Definitively my phone loves Franco Kernel
[Samsung Galaxy Nexus] nikulogical:
Same thang.
[Samsung Galaxy Nexus] franciscofranco:
Could you please get me a logcat while booting as well? The dmesg/kmsg wasn't very specific. Thank you.
[Samsung Galaxy Nexus] dyndragon:
There's a lot of good crash data in here i think.
[Samsung Galaxy Nexus] superbobup:
Hmmm I can't say for myself as the latest I tried was 220 but everything was working fine...connection speed slow? Maybe try a different radio? Or maybe try messing with clock speed or different governor? What app doesn't play back when screen is off? I'm not sure if any of these will help, but they're just ideas that come to mind :o:o
[Samsung Galaxy Nexus] nikulogical:
It seems to be an issue with doods music streamer. Tiny shark works perfectly with this kernel without WiFi pm fast.

Funny doods music streamer worked with previous builds of Franco.
[Samsung Galaxy Nexus] pkelly517:
Yea! Been on lean kernel since JB because I was plagued.

Now I get to see how battery life compares.
[Samsung Galaxy Nexus] Guzmanus:
I'm getting bootloops on paranoidandroid 1.7 too with r221. Shall you need any more information, tell me.
[Samsung Galaxy Nexus] dyndragon:
Dmesg, last_kmsg, logcat -v time -d
[Samsung Galaxy Nexus] nuumuun:
just reflash the rom. make sure to save the "/system/pad.prop" file to restore your mode and dpi settings afterwards.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Weird. Are you using the latest bootloader and radio?
[Samsung Galaxy Nexus] nikulogical:
Yeah newest boot loader and radio from the jb ota
[Samsung Galaxy Nexus] Prod1702:
hey franco I am still unable to get your Kernel to boot with CM10. I am using Fits nightly KANG. I am on the latest version 7/17 ad the phone gets stuck in a bootloop each time. I have tried auto flash from your app and download and flash from recovery. Both of which puts the phone into a bootloop. I am trying this with the latest v221. Do i need to try this on a full wipe? I am looking forward to running your kernel again like i did on CM9.
[Samsung Galaxy Nexus] leontine:
Read some pages back....he's working on it!!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
I don't know why its not booting. It's obviously caused by the ramdisk so I need to either find out the changes I need to make it work or you can just unpack my boot.img, get the zImage and pack it to CM10's boot.img, done.
[Samsung Galaxy Nexus] Prod1702:
Sry for the post about not booting didn't see the report from someone already. How do I get you a log of the bootloop when I get home from work I will post one for you if you still need one.
[Samsung Galaxy Nexus] franciscofranco:
Nop don't bother, thanks.

Just pushed 5.8.3 app update

Galaxy Nexus

* Fix excessive Root requests when swiping through the tabs

One X

* Fix for reset CPU frequencies after swiping through the tabs

Should be up when Google refreshes the app list.
[Samsung Galaxy Nexus] lwclam:
After upgraded to 4.1.1 and using r220-JB

I found that USB fast charge is not working with USB port charging, how can I make it working? "Enable fast USB charge" enabled.
[Samsung Galaxy Nexus] defconoi:
I've noticed this too, im sure it'll get fixed
[Samsung Galaxy Nexus] ragnarokx:
After flashing r221, I got my first data drop ever on Jelly Bean. I'm hoping it's a coincidence. Anyone else? GSM GN, Bugless Beast latest build.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
Thanks Franco! Remember the power mode on boot crash I mentioned to you before? It is fixed in this version :D

---------- Post added at 10:31 PM ---------- Previous post was at 10:31 PM ----------

221 working excellent here! NO issues for about 6 hrs now.
[Samsung Galaxy Nexus] franciscofranco:
Good to know ;)
[Samsung Galaxy Nexus] armisis:
Question?

Could a Kernel Issue be a possible cause for my Gmail app no longer being able to download attachments?

I am now running the latest 221 on a Galaxy Nexus GSM with the v3 of the Jellybean Jellybelly build from ...Awesome...

Thank you,

Dave
[Samsung Galaxy Nexus] thuynh022:
I can't flash the 221.384 zip I downloaded with Franco's app in recovery. Keeps giving me an error and aborting.
[Samsung Galaxy Nexus] loudaccord:
just as a fyi... not sure why but it took about 8 to 10 minutes to boot the first time after flashing 221... everything is working fine now and I was patient. It was stuck on the Google logo for a loooong time. Just making a note for others.
[Samsung Galaxy Nexus] vomer:
Do a manual download from link in main post?

Mine didn't do this.... Booted pretty quickly. Could be your rom maybe.
[Samsung Galaxy Nexus] ajm786:
I am one of those not running JB yet; I'm still running the latest release of AOKP and franco kernel v191 (with the latest app update).

Whenever I reboot my phone, the app updater forgets all my settings and I have to reset them. It's highly annoying. I've read in this thread that clearing the app's cache entirely, uninstalling, reinstalling, and then setting all your options should resolve it...but it doesn't.

Any help on this? Thanks.
[Samsung Galaxy Nexus] franciscofranco:
Flash this: http://minooch.com/franciscofranco/Galaxy Nexus/CWM-SuperSU-v0.89.zip

Then update SuperSu app and update the binary. Should fix it.
[Samsung Galaxy Nexus] jeetS:
I auto flashed 221 512gpu and it booted up quickly. Running great no problems as usual. Used the latest Franco updater. On bigxies 4.1
[Samsung Galaxy Nexus] franciscofranco:
Just pushed 5.8.4 to Google Play:

5.8.4

* Fix FC swiping the tabs on Jelly Bean - blame Google for changing the permissions on scaling_min_freq and scaling_max_freq to 0440. The user group needs to have read permissions or the app can't read the file, thats why it causes the FC unless you're running a custom kernel with a custom ramdisk that overwrites the permissions. I hope this is fixed now in the app as it checks for permissions every time that its opened.
[Samsung Galaxy Nexus] ajm786:
Franco, thanks for responding. It still doesn't work. When I downgrade SU to the version you posted, it works fine. The moment I update the SU app and binary, it goes right back to not working.
[Samsung Galaxy Nexus] franciscofranco:
Awesome, at least you found something that works :)
[Samsung Galaxy Nexus] RiderOnSuzuki:
Just a small word to thank you for all thé job you're doing for us.

Thanks Mister !

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] thuynh022:
Manual download from OP works fine. In-app download still fails for me, no clue why.
[Samsung Galaxy Nexus] goldleader:
In-app auto flash to 221 seemingly failed for me, screen went blank and the phone never woke. Had to pull battery eventually, but after booting (yes, 221 had actually flashed) my phone is snappier than ever! Great work Franco! :-)
[Samsung Galaxy Nexus] itsDefying:
Hmm.. 221 seems to bootloop on my Nexus w/ PARANOIDANDROID 1.7 alpha.
[Samsung Galaxy Nexus] franciscofranco:
EHEH no **** sherlock :D
[Samsung Galaxy Nexus] :
(Edit)

Sorry I have a toroplus and we don't have paranoid jb. Its because its a CM base rom..
[Samsung Galaxy Nexus] VirtualXDriver:
Paranoid is actually Jelly Beans since version 1.6, but 1.7a is CM10-based, which is not (yet) compatible with this kernel due to issues in the ramdisk, as stated before.
[Samsung Galaxy Nexus] sway40:
haha this made me (and I don't use this term often bc I'm not a teen girl) LOL.

Sent from my Nexus 7
[Samsung Galaxy Nexus] Wing_Zero85:
Hi francisco,

r221 works like a charm! ;)

I have a doubt regarding some libs:

When you use an mhl cable for hdmi out (or the desktop dock) if u see a movie hardware accelerated (with any player at your choice) the subtitles aren't outputted to the TV but are visible only on the phone.

The Android framework does not have any interface for HDMI (MHL), so the HDMI output depends on manufacturer's implementation.

This limitation is hardware related, or software related? Do you think it is possible to do something to correct this issue?

Thanks,

WZ
[Samsung Galaxy Nexus] Hussainally:
Hey Franco..221 installed just fine on xenon HD ..very smooth no glitches .just finding my phone to be very hot now.came from stock kernel .just saying
[Samsung Galaxy Nexus] pwvandeursen:
Hee Franco,

its been mentioned a couple of times through out the thread but no official statement. will you ever consider supporting CIFS in your Kernel? I know it currently doesn't and there are a couple of ways to get it, but would love official support. any reason for not doing it?

would be great :D

Also I'm one of the users on PA and would love to have it supported by yours! I know it has issues (with the RAM part), but am sad at the moment I can't use yours. I feel a bit dirty to due to my adultery actions with the trinity kernel (do like his white levels through, the screen seems so much more vibrant).....

thanks again!

Patrick
[Samsung Galaxy Nexus] GeekMcLeod:
I, too, can't wait for CM Based roms to be compatible. I'm on PA as well and miss this kernel already. No matter what kernel I would try, I would always end up back on this one. Which just isn't possible as of yet. Hope this issue is resolved soon though! :D
[Samsung Galaxy Nexus] WitchMX:
I tried both, downloading zip from app and auto flashing and both work fine with #221 for me( AndroidME v1.2)
[Samsung Galaxy Nexus] smalss:
Quick question, will I get less battery if I flash the 512 GPU release of 221 compared to the 384 GPU release? I am guessing I will while playing games but what about just normal texting, web use, etc.?
[Samsung Galaxy Nexus] mariachi202:
Short answer: yes.

I had a significant impact on battery life when i used the 512 version. I would go so far as to say that even performance wise the 384 behaved much better. On 512 it always lagged and stuttered for me at least. No visual glitches whatsoever thogh.
[Samsung Galaxy Nexus] jcmm11:
If you were getting lag and stutter on 512 but not on 384 but no visual glitches I'd guess that your phone can't handle 512, although you're probably close to the edge.

For me, and from reports I've seen for others that can run 512 successfully, 512 runs smoother (although with jb the difference isn't as noticeable for most things) and is totally lag and stutter free. Battery impact compared to 384 is next to non-existent.

Bottom line, if you can run 512 (not everyone can) then go ahead and then judge for yourself. I think you'll find battery life to be almost identical.
[Samsung Galaxy Nexus] metalspring:
Look at your smart reflex voltages for gpu, copy them in the core undervolt menu without applying, then up the top one by 5, then disable smartreflex for core and apply your voltages, if it still lags raise the top voltage by 5-20 (raise by 5 each time you test)

That should work, I know with sr values on 512 I get glitches in benchmark apps but just raising my voltage by 5 makes it work perfectly
[Samsung Galaxy Nexus] metalspring:
btw Franco any idea when sio will be back in the jellybean kernels?

Also an issue with the app not reporting fsync properly, after a reboot it always says on even though I have it off

It works fine enabling and disabling fsync, it just doesn't report right after a reboot

And lastly 2 questions about r221

As far as the compiler toolchain, is this newest one basically Google's official version of linaro toolchain?

And what difference does compiling for the cpu rather than the arch do?
[Samsung Galaxy Nexus] LNJ:
Yeah FSync keeps turning back on after reboot.
[Samsung Galaxy Nexus] mariachi202:
The lags mostly appeared on the launcher, so maybe it has some incompatibility issues? Otherwise, the biggest difference that i've noticed is that the 512 variant behaves much more better when scrolling something with large amounts of data and things to redraw, although only by a tad better than the 384. For instance, a big screenshots thread or a website with images, etc.

It's unbelievable for me that battery life differences were virtually non existent for you.

The temperatures also jumped by a margin of 5-6 degrees with normal usage (tapatalk, calls, sms, mail) so on average the idle was around 50 and could easily jump to 70ish with light usage.

The main reason why i should use that variant is heavy gaming, which i don't really do, so...
[Samsung Galaxy Nexus] coolpages:
Ever since I started using JB r221, 384, I have had 3 or 4 Forced Reboots, and each time I would be just doing something normal, like reading a text file or perhaps looking at an article on Flip Board, and then I noticed that the Nexus seem to be frozen, unresponsive and I noticed at least twice, the screen brightens up momentarily and then it reboots.

The only notable change I made in the Franco updater is to change the CPU speed to 1612.

Rooted, JB Bixie 4.1.1 ROM,

Franco JB r221, 384GPU

Wheatly governor max CPU 1612, Min 384, no changes to default voltages.

Galaxy Nexus (GSM)
[Samsung Galaxy Nexus] muhsli:
It doesn't hit you that your CPU might not be able to handle that high frequency?
[Samsung Galaxy Nexus] LNJ:
If it freezes, the clock speed is too high. If it just reboots, the voltage is too low.
[Samsung Galaxy Nexus] coolpages:
Well, it freezes, then reboots.

So I guess 1612 is too high and 384 is too low.

But it was OK with 1536MHz and 384 MHz with Franco r220, so 384 should not be too low.
[Samsung Galaxy Nexus] franciscofranco:
We don't need SIO now, deadline works fine.

Didn't know about that fsync bug, thanks.

The toolchain is just 4.6 from the NDK, nothing about linaro.

I think it makes more sense compiling for the cpu than for the arch, but its extremely hard to notice any difference I believe.
[Samsung Galaxy Nexus] LNJ:
It's the first symptom that determines the issue. It freezes first....so clock too high.
[Samsung Galaxy Nexus] franciscofranco:
So if you increased your CPU max freq and you're now having reboots... it's pretty obvious what is causing the ****.
[Samsung Galaxy Nexus] Razer(x):
Bootloop on latest CM10 build
[Samsung Galaxy Nexus] franciscofranco:
Yes we know it doesn't boot on CM10.
[Samsung Galaxy Nexus] sago62:
Thank goodness you said .... I was going to put cm10kang ....
[Samsung Galaxy Nexus] ZiCoN:
I've been using 384/1228/interactive for a long time now, but with 221 it feels as if I've got some lag now, which I've never had before...
[Samsung Galaxy Nexus] Paragon_X:
I recently updated to 221 at 340 or whatever it is set. Anywho I use it with awesomebeats jellybelly rom and I had one cut out of data but it immediately connected. And even weirder I user tasker for gps, wifi and headphone plugin automate. The headphone task keeps cutting and popping up the dialog box as if I pulled it out and reconnected which I never did. The headphones are new so I suspect it can't be the connection. Either way I killed that task as it's not that important. I just wanted to share in case this could be an issue for future use. Other than that works great!
[Samsung Galaxy Nexus] franciscofranco:
Have no idea, seems like a random **** to be honest.
[Samsung Galaxy Nexus] decarre:
You're the best franco :)

Here my setting. For GPU and CPU volts :)
[Samsung Galaxy Nexus] vomer:
Thanks for those settings...did you notice a difference in battery? What about IVA?
[Samsung Galaxy Nexus] itsDefying:
Really? I wasn't aware that this was a known issue even on 221, seeing that the changelog said 221 should boot on CM10 roms. There was no need to be disrespectful in that post.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I wasn't disrespectul, I was joking like I do many times. Yes I wrote that in the changelog but after I posted it there were about 3 or 4 pages of users reporting that it didn't boot, so with a little search you would've seen that it was already reported.
[Samsung Galaxy Nexus] gzub:
Franco,

I was comparing the two ramdisks from your kernel and the CM10...

The one spot I see that might be an issue is that CM10 had to split the framework.jar file into a second one due to a limitation on the number of classes in a file (their customizations push JB over the limit I think). Your ramdisk does not have framework2.jar in the BOOTCLASSPATH in the init.rc...

Geoff
[Samsung Galaxy Nexus] itsDefying:
Well then in that case, sorry.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thuynh022:
I've also had issues with the headphones doing that, but it happens on Pandora for me. Started ever since I flashed 217. The only time it doesn't do that is when I plug it in and Google voice search pops up.
[Samsung Galaxy Nexus] Paragon_X:
Interesting. I'll dig a bit deeper.
[Samsung Galaxy Nexus] franciscofranco:
Ok thats USEFUL! Can you paste me that line from the CM ramdisk? Saves me the time of downloading, decompiling etc :) Thanks.
[Samsung Galaxy Nexus] decarre:
Yes when i play (ff3 dead trigger) i don t lost much battery

For iva i have

But i can t bench it for test no?

Wich app for bench volt IVA ?
[Samsung Galaxy Nexus] gzub:
This is the line from the init.rc:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar

Edit: I attached the three files that had differences, the BOOTCLASSPATH was the most interesting, the other changes are minimal.
[Samsung Galaxy Nexus] franciscofranco:
Thank you! I'll drop something to test in a bit.
[Samsung Galaxy Nexus] franciscofranco:
Can you attatch a full .diff file for me?
[Samsung Galaxy Nexus] mikespe:
Just flashed 221 and got my first reboot ever on a Franco kernel...had to do a battery pull & then reflashed 220...then perfect reboot. I did not make any changes in CPU or voltage...never had a chance since it was the reboot after flashing 221 where the problem occurred. Anyone else having this?

Sent by an Android Guy using an iPad...
[Samsung Galaxy Nexus] nikulogical:
What governor is most people using? On demand seems pretty decent in terms of performance and battery life. But interactive absolutely drains my battery more so than stock.
[Samsung Galaxy Nexus] Antob125:
Wheatley is a beast :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] WitchMX:
Have you tried fixing permitions? I had also my first two random reboots ever doing regular stuff but after I fixed permitions everything has been running flawlessly

Cheers
[Samsung Galaxy Nexus] CADude:
I use lazy for JB.
[Samsung Galaxy Nexus] ro_explorer:
Video time then :) ...

I have the hotplug enabled btw. I do not feel any king of annoying lag .. there is some, indeed, but is so unnoticeable I don't really care.

http://www.youtube.com/watch?v=HAph1xf6Uhc