yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Fihlvein:
Milliseconds? It took around 2 secs a few times when I tried a bit a moment ago. Reminds me of GS2 "feature" which I try to forget. This ones seems inconsistent. But I just tried briefly, will test more.
[Samsung Galaxy Nexus] rabhw:
It's hard to tell from your video whether any of your wakes were given enough time for the device to enter deep idle. Some of them were obviously too fast (too close together) to enter sleep, so no lag is visible, not even on my device.

The lag seems to be when the device is coming out of deep idle, which is why I left a gap of quite a few seconds between my wakes in my demonstration video.

Anyways, like Fihlvein and some others have said, it varies from wake to wake, but it can be fairly delayed sometimes.
[Samsung Galaxy Nexus] ro_explorer:
You're right ... the so called lag is inconsistent but in my case the longest one is barely there to say so.

I've removed the video due to an error .. I'll upload another one shortly (after I'll remove my e-mail address from the unlock screen :) ).
[Samsung Galaxy Nexus] Redflea:
Clearly not a consistent issue...would help if anyone experiencing this posted governor, OC if any, etc. I have never seen this on 9 or 9.1, with the default governors, and not even when I enabled cpu.1 sleep.
[Samsung Galaxy Nexus] nbeebe24:
I must just have a lucky device, as I have not experienced any sod's, lag, or random reboots with any of the kernel releases. I am on aokp 13 and it is very snappy, stable and just down right great! My only complaint is battery life (which is 100 percent because I can't put the phone down). Great job Franco! Once again, I appreciate all your work
[Samsung Galaxy Nexus] ro_explorer:
Ok .. so, this time, device at sleep for at least 5 minutes, hotplug enabled (as described in OP): http://www.youtube.com/watch?v=P8SpU1tiYBQ

Obviously, the first unlock was a little slower compared to the others (this is the hotplug stuff for sure) but other than this ... everything is OK.

P.S.: Sorry for the focus hunting but in such low light as is now in my living room the cheap camera is showing its price.
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for the feedbacks! I'll drop another build in a few.
[Samsung Galaxy Nexus] droidholic:
One small thing I've noticed with builds #9 and #9.1 is that if I am on the phone while tethering, my internet suddenly becomes slow and is barely usable. However, if I get off the phone, everything runs fast again. My hunch is that it may have to do with the way the kernel is handling heavy tasks but I could be wrong. Nonetheless, I am still enjoying this kernel though.
[Samsung Galaxy Nexus] jknisley:
I had this problem right out of the box on my old Gnex, and I had to take it back because the hissing and popping was *horrible.* The new one that I got was just fine. You might consider a nandroid and flash back to stock and see if it repeats it, because there's a bit of a known defect with a subset of these guys.
[Samsung Galaxy Nexus] sirj00:
I added a couple of tweaks to his kernel a while back in

build.prop and ever since I haven't gotten one single lag.

I'm on the road now but if u look at one of my posts from earlier

Posts u will see what I added.
[Samsung Galaxy Nexus] aron7awol:
This post is right on. I never had any lag on 7, 7.1, or 8 using interactive governor. A friend of mine did have lag #2 on 7.1/8 with ondemand, but once he switched to interactive it was perfect for him.

Kernel 9 created lag #1, and 9.1 did not get rid of it. Maybe 9.2 will. In the meantime, I'll stick with kernel 8 with interactive as it is perfect.
[Samsung Galaxy Nexus] daandman:
Found it: :D
[Samsung Galaxy Nexus] sirj00:
Internet speed definitely increased for me, fantastic.

I too must have a great phone cause every build I install always

works without a hitch.

I got 6hrs run time today on battery running 4g all day with 6 hrs streaming

Pandora and surfing this site. That's outstanding, very happy.
[Samsung Galaxy Nexus] XeQtuR:
Animal of a Kernel!!!!

View attachment 842359
[Samsung Galaxy Nexus] meilstone:
Can someone tell me how to enable hotplug? because in #9 it was enabled soo that cpu1 is turnt off. but in #9.1 its turnt off. but i would like to have it enabled again.
[Samsung Galaxy Nexus] ro_explorer:
read the OP (first post) ... is in the #9 changes.
[Samsung Galaxy Nexus] Dr_Ownage:
give this a go
[Samsung Galaxy Nexus] daandman:
I've done this but how do we know if it's effective?
[Samsung Galaxy Nexus] meilstone:
well i can read that. but i needed the instructions with the terminal emulator.
[Samsung Galaxy Nexus] gzub:
I'm out and about right now so I can't post it, also I am doing this on a Windows box so I don't know if I can generate a Unix diff for you...
[Samsung Galaxy Nexus] mikespe:
I'll have to try that. I usually only fix perms when I flash new Gapps. Never had to do it on other Franco's kernels....

Thanks

Sent by an Android Guy using an iPad...
[Samsung Galaxy Nexus] mikeandjaimie:
This is exactly same as me, cept started before 221.. Could run upto 1.8 on 512 before, now I'm having problems with reboots on 384 down to 1.5.. Seems I'm getting reboots these days on almost every freq above 1.2. I've changed no settings in franco app from what I used to use as defaults, but now I've tried every gov and freq combination I can think of... Never undervolted or played with anything like that
[Samsung Galaxy Nexus] jcmm11:
http://gnuwin32.sourceforge.net/packages/diffutils.htm
[Samsung Galaxy Nexus] Smokuevo:
Still the latest kernel not booting on cm 10 :-)
[Samsung Galaxy Nexus] soapinmouth:
I'm having same issue, getting reboots as low as 1.2ghz on latest
[Samsung Galaxy Nexus] EvoRocker:
Are there optimal settings for color control?
[Samsung Galaxy Nexus] GeekMcLeod:
Hey Franco, any update on when we could possibly be seeing another test build for CM10-based roms? I'm usually not one to ask this but I miss having your kernel on my phone. I always found it gave me the best performance and battery life.
[Samsung Galaxy Nexus] fatappel:
r221's running like a beast. Fast, efficient and smooth with bigxie's deoxed ota 4.1.1. Never thought I'd be using a "stock" rom but I've been able to flash enough mods to make it my own. The only custom rom feature I'm missing is the ability to adjust and set the auto-brightness levels. Stock is just too dim so I'm running 100% at all times. Not sure how much code and work is involved in writing this feature into your app franco but it would be much appreciated. Thanks for your work and thanks for considering.
[Samsung Galaxy Nexus] franciscofranco:
That doesn't help a bit. Logs? I can overclock to 1.8ghz and no issues.

Tomorrow or something, busy with sgs3 today.
[Samsung Galaxy Nexus] gzub:
Attached are the diffs...
[Samsung Galaxy Nexus] mikeandjaimie:
What exactly you need and how to get? I get them quite regularly, I'm sure I can submit a few heh
[Samsung Galaxy Nexus] franciscofranco:
Awesome, thanks a bunch.

I need dmesg logs. Battery pulls wipe the log so you have to get me the log after the reboot without taking the battery out. But if its crashing on 1.2ghz something is really really bad. What rom are you using?
[Samsung Galaxy Nexus] franciscofranco:
Yeah that was actually very useful, thanks for the effort!
[Samsung Galaxy Nexus] joeski27:
You know you guys I feel compelled to jump in and make a quick comment here. I've been a relatively long-time follower/user(and paid-app user!) of the franco kernel, and specifically I've been following this no-boot-CM10-franco-kernel issue for the past few days as I've just recently started rocking the Euroskank nightlies (now that both the nightlies are getting more feature-packed and that other apps are updating for JB). And I must say, that seeing the amount of contribution, collaboration and effort going on with this specific custom kernel issue is a classic case of both what Android is and how awesome this community is. I think its safe to say that Android users and developers are by far some of the most enthusiastic and passionate tech fans out there, and (though I may not have tons of technical expertise to contribute) I'm certainly glad to be a part of it. Keep it up guys! :cool:
[Samsung Galaxy Nexus] mikeandjaimie:
Bigxies 4.1.1 atm.. No mods installed. And I haven't gotten 1.2 reboots (yet) but currently running 384/1.5 on 384GPU with max screen off 1.2. Fsync, wifi pm_fast, high performance sound on and never touched uv or anything else. I get no reboots during stress tests in setcpu or benchmarks, but random reboots when checking forums, sending/receiving texts, etc... Usually stuff NOT cpu intensive..

. I've tried 1.9 to 1.5 all gov but lazy, and 512 and 384GPU... Wiped cache and dalvich... Reflashed with full data wipe and format /system and then flash of kernel from app after installed. Just did a fix permissions as well. Anything anyone else can suggest?

What's the command or app to get dmesg? Sorry not well versed in android/nix commandline reference.
[Samsung Galaxy Nexus] GeekMcLeod:
I would not mind knowing this, or how to find anything else that would be useful. I don't know much about anything but this is one thing I want to learn about. Just can't seem to find anything that seems good to learn about android rom/kernel coding.
[Samsung Galaxy Nexus] depths:
I like

180

192

230

rgb gamma

-4

0

5

-10 trinity contrast

1.2 OMAP4 gamma

But you'll have to find what works for your screen and your eyes.
[Samsung Galaxy Nexus] superbobup:
Well if it's crashing when it's OC'd then I think you may have your issue there:p:rolleyes:
[Samsung Galaxy Nexus] spaceman860:
With root explore go to /proc/last_kmsg and then you can save it or upload it to drop box or adb pull /proc/last_kmsg

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] mikeandjaimie:
If you read any of my previous posts, I could run 512gpu 1.8ghz with any governer flawlessly with no issues until recent changes... Read all posts before you make comments or roll your eyes at anyone.
[Samsung Galaxy Nexus] Mattymat:
I'm getting these as well, but I'm also new to this kernel.
[Samsung Galaxy Nexus] superbobup:
Whoaaaa. No need to get so pissy. Sometimes people overlook basic things like clock speed was too high. No one is trying to pick a fight man, just trying to help geez
[Samsung Galaxy Nexus] metalspring:
It's most likely the sound boost, I believe some jb roms have it preset to 3 and 2 or 3 doesn't work well with some headphones. Try setting sound boost to 0 or 1 (May need to edit one of the /etc/init.d scripts)
[Samsung Galaxy Nexus] Culex316:
Had my first random reboot ever in over 3 months of using your kernels (since I got this phone)

Here is the link to the last_kmesg

https://docs.google.com/open?id=0B9DcPJCiP10ncnBBYm5ZVEVpeHc

It happened as I was opening the Facebook app on my phone.

I am running Stock Jelly Bean 4.1.1, stock radio, CWM, your latest nightly r221 with interactive, min CPU 384mhz max 1228mhz.

Hopefully this can be of help.

Edit: Just noticed I'm not the only one.
[Samsung Galaxy Nexus] mikeandjaimie:
This has been an ongoing problem for many versions now. You can't just jump on the last message without following what's been happening and reply... I've been stepping down from 1.8 and trying each governor with different settings. Something around 196 broke me :(
[Samsung Galaxy Nexus] franciscofranco:
You linked me a dmesg log of cm kernel.
[Samsung Galaxy Nexus] LNJ:
Here's my UV values if anyone is interested:
[Samsung Galaxy Nexus] crazybone21:
Dear Mr. Franco,

May I please request for a tun.ko module for this kernel so we can use our DroidVPN please?

Thank you very much...
[Samsung Galaxy Nexus] Culex316:
oh ****, sorry about that

here is the correct one.

https://docs.google.com/open?id=0B9DcPJCiP10nYXp3dWNfOTk0cTg
[Samsung Galaxy Nexus] dirwdirw:
no ad-hoc wifi @ r221 kernel?
[Samsung Galaxy Nexus] momomok:
Isn't ad-hoc wifi depending on ROM support?
[Samsung Galaxy Nexus] Coffeebeans:
This has probably been answered in this thread already, but does the wifi pm fast setting improve only improve wifi performance when the screen is off or does it improve it all the time? Also, the boot animation does not seem to work for me on r221. Did jellybean change the way boot animations are handled? Thanks for the awesome kernel and app.
[Samsung Galaxy Nexus] dirwdirw:
oh, it looks like yes...
[Samsung Galaxy Nexus] thehero21:
confirming: cm-10 and franco is working

FYI: i can confirm, cm-10 works under/with the franco kernel:

root@android:/ # uname -a

Linux localhost 3.0.31-franco.Kernel-nightly-512GPU #221 SMP PREEMPT Wed Jul 18 16:18:04 WEST 2012 armv7l GNU/Linux

rom is:

[CM10][Jellybro] Maguro Nightly Kangs -> cm-10-20120719.1556-SKANK-maguro.zip

i had to overwrite the zImage in the cm-10 boot.img with the franco zImage.

summary: seems to be a (temporarly?) problem in franco's initrd(ramfs).

greetings
[Samsung Galaxy Nexus] sago62:
Is problem of ramdisk?i think yes...
[Samsung Galaxy Nexus] Michealtbh:
Imoseyon managed to get his Lean Kernel working with CM10, which I believe had the same problem
[Samsung Galaxy Nexus] Segnale007:
@franciscofranco, seems the kernel has some issues with CM10 0.2 since after installed it gets stuck on boot.

Logcat after installed the kernel

I/DEBUG ( 122):
I/DEBUG ( 122): memory map around fault addr deadbaad:
I/DEBUG ( 122): befdf000-bf000000 [stack]
I/DEBUG ( 122): (no map for address)
I/DEBUG ( 122): ffff0000-ffff1000 [vectors]
I/ServiceManager( 116): service 'media.audio_flinger' died
I/ServiceManager( 116): service 'media.player' died
I/ServiceManager( 116): service 'media.camera' died
I/Netd ( 5147): Netd 1.0 starting
E/BandwidthController( 5147): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/BandwidthController( 5147): runIptablesCmd(): failed /system/bin/ip6tables -t raw -N bw_raw_PREROUTING res=256
I/mediaserver( 5146): ServiceManager: 0x2a008ce0
I/AudioFlinger( 5146): Using default 3000 mSec as standby time.
I/CameraService( 5146): CameraService started (pid=5146)
I/AudioPolicyManagerBase( 5146): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger( 5146): loadHwModule() Loaded primary audio interface from Tuna audio HW HAL (audio) handle 1
I/AudioFlinger( 5146): HAL output buffer size 176 frames, normal mix buffer size 1056 frames
I/AudioMixer( 5146): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
D/MDnsDS ( 5147): MDnsSdListener::Hander starting up
D/MDnsDS ( 5147): MDnsSdListener starting to monitor
D/MDnsDS ( 5147): Going to poll with pollCount 1
[Samsung Galaxy Nexus] franciscofranco:
Tun is already included.
[Samsung Galaxy Nexus] thehero21:
yes, initrd is a ramdisk (a compressed cpio archive).
[Samsung Galaxy Nexus] hotnikkelz:
HI guys, I have a problem unrelated to the kernel I believe.

My Galaxy nexus just REFUSES to charge unless it is off :'( it is frustrating as hell. IT has to be software i think because when I start from scratch for it starts charging again. Anybody knows what can be causing this?
[Samsung Galaxy Nexus] TEK112:
Do a full wipe and load a new ROM. I have seen that happen before and that was the only consistent fix. Just make backups.
[Samsung Galaxy Nexus] hotnikkelz:
Whoa. Everyone else is having success with Bigxie's JB rom. I did that already but it seems like that is the ONLY solution. I was hoping there was a better one thanks
[Samsung Galaxy Nexus] lwclam:
One of my CPU is offlined itself. How to make it online again?
[Samsung Galaxy Nexus] fatappel:
Sorry this is off topic but the same thing happened to me. It was frustrating and want to help. It's a hardware issue, not a software. Your usb input connector tongue on your phone is bent. Use the tip of a knife to carefully bend it back into the correct position. Tongue should lie directly in the middle of the port.
[Samsung Galaxy Nexus] The Gingerbread Man:
Ensure your using a power mode with both cores enabled. Switch to Franco full power then what ever after although all francos power modes are duel core powered as he said he didn't wanna mess about with turning cpu1 on and off all the time the the system does this its self. Check if you set up anything forcing a single cpu mode and delete it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I'll see if I get this ramdisk compatible with CM10 today, no promises though, thanks for all the help with the diffs, and logs. When everyone contributes everyone benefits.
[Samsung Galaxy Nexus] hotnikkelz:
I tried what you said and it SEEMS to have worked. Will monitor it though to see whats up. Thanks for your help. Sorry Franco and all, that i went off topic :)
[Samsung Galaxy Nexus] renaud:
Look at my last commits

Envoyé depuis mon Galaxy Nexus
[Samsung Galaxy Nexus] lwclam:
Thanks for your reply.

But I did not enable any power modes, is it the problem?

p.s.: I'm using r221-JB
[Samsung Galaxy Nexus] mikespe:
So people are supposed to read back to 196 JUST to learn YOUR problem? The guy tried to help you so say THANK YOU!

Sent by an Android Guy using an iPad...
[Samsung Galaxy Nexus] gzub:
I actually haven't even tried the CM10 stuff yet, I just figured that was an area I could help out with...

Geoff
[Samsung Galaxy Nexus] superbobup:
Thank you for the kind words but I'm sure I was a bit quick when addressing his issue. It seemed quite trivial and didn't include any previous posts so I had assumed it was the first one. Even though I read all the thread, I should have checked for previous posts anyways before addressing the issue. I'm sure can just focus on the kernel now :cool::thumbup:
[Samsung Galaxy Nexus] pwvandeursen:
Franco, any views on the CIFS issue? thanks!

thanks
[Samsung Galaxy Nexus] The Gingerbread Man:
No if you have no power modes then you should still be in duel core mode by default. You could always create a 1228 - 384 interactive single core mode false power mode and set on boot then select it and it should definitely work. Unless what ever you were doing at the time earlier only required 1 core as I think the read out for cpu cores is a live read out of what is active at the time

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Pajorve:
Hello friends, someone could tell me what the best configuration for the kernel Jelly Bean? What I want better performance on the drums and which frequencies I use both the OC and in undervolting ... And the best governor, but Pegasusq, ondemand, grateful for the responses and thank you!

:D:D:confused::confused:
[Samsung Galaxy Nexus] The Gingerbread Man:
Stock values 1128 - 384 interactive and allow smart reflex to do its thing as it works pretty well

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] IAmAN00bie:
Interactive governor (pegasusq isn't available on this kernel). What I did was set my min to 729 MHz and undervolt it to 600mV, and set my max to 1228 MHz undervolted to 800mV.
[Samsung Galaxy Nexus] Pajorve:
Thanks my brother .... I made the change and will test how the battery behaves in this setting. I use Kernel for Jelly Bean and he has pegasusq yes. Hugs!

:D:D
[Samsung Galaxy Nexus] Pajorve:
Thanks my brother .... I made the change and will test how the battery behaves in this setting. I use Kernel for Jelly Bean. Hugs!
[Samsung Galaxy Nexus] sway40:
Not to bad, stock battery and overclocked to 1.5. Screen on time isn't too bad but standby time is awesome.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Pajorve:
Hello my friend, Very good the time battery. Whats configuration your use?

Fantastic

:D:D
[Samsung Galaxy Nexus] sway40:
Nothing special, just ondemand, and overclocked, Wi-Fi overnight mostly 3g, no 4g.

Sent from my Nexus 7
[Samsung Galaxy Nexus] pinke123:
So if I want to flash this kernel and I'm running JB 4.1.1 JRO03C should I use the latest kernel from the JB link (franco.Kernel-r221-512GPU) or should I use the one from the milestone 4 link (franco.Kernel-milestone4)? Thanks guys!
[Samsung Galaxy Nexus] nikulogical:
M4 is based on ICS, try the r221.
[Samsung Galaxy Nexus] superbobup:
Milestone 4 = ICS, use the JB kernel link :)
[Samsung Galaxy Nexus] Pajorve:
Really is a Great... thanxs you!

:D
[Samsung Galaxy Nexus] nikulogical:
Those with greener tints in their display. Franco's settings looked better than stock but try this.

185, 165, 200

-4, 0, 5
[Samsung Galaxy Nexus] renna1992:
i'm running 188/163/199 and 11/13/7, works great for me :)

e: and i forgot: trinity contrast at -10
[Samsung Galaxy Nexus] CADude:
The best settings are Francos 180/192/200 -4,0,5 but with CAB turned off and Trinity Contrast at 5.
[Samsung Galaxy Nexus] franciscofranco:
Does this boot on CM10 or derivates?

http://minooch.com/franciscofranco/Galaxy Nexus/franco.Kernel-cm_test.zip
[Samsung Galaxy Nexus] XAviierG:
And it boots ! :)
[Samsung Galaxy Nexus] RayGarden:
Interesting "Nightly". Received from Francisco as an Alpha, this #223 and what about #222? :)

Interesting Theme as well.......wanna share?

Tnx

Ray
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco did I imagie your 'full power mode' was 1.5 ghz - 729mhz Wheatley governor? I just selected it and got 1.305 ghz - 729 MHz interactive governor.

I also tried the music power mode after and got severe lag in your app then a force close to which I submitted the report. Opened back up to find balanced power mode on, tried music power mode and this time it worked without force close.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thats not cool at all. Thanks.
[Samsung Galaxy Nexus] XAviierG:
Theme is DarkJelly by DarkKnight
[Samsung Galaxy Nexus] RayGarden:
i really didn't knew i can install a theme over a Stock ROM. I'm now going to search for it

Edit: not the Bigxie Stock Rom i see now. I'll wait for a while. Nevertheless......looking good for the moment, although it is not finished
[Samsung Galaxy Nexus] williamthegoat:
So is interactive the recommended governor on 221?
[Samsung Galaxy Nexus] The Gingerbread Man:
Yes or lazy, depends on how much battery you want really

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] williamthegoat:
What does Lazy do?
[Samsung Galaxy Nexus] The Gingerbread Man:
Its like the conservative governor. It keeps the CPU speeds down only scaling up speeds when it needs to. Its a modified version of on demand I think. Interactive when you do stuff it jumps the speed up to maximum and scales back down to what it needs. Both work well. Lazy doesnt lag but interactive is a little more snappy and responcive. Have a play and find what works for you.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spaceman860:
http://xdaforums.com/showthread.php?t=1369817

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] mikeandjaimie:
Hey franco, just got another reboot and grabbed the last_kmesg.. 384gpu 729/1.8 interactive. Nothing really cpu intense going on when it happened

http://db.tt/I7SEvtQg

Edit: http://db.tt/HZoRPd8M 1.7 lazy during netfix lol

Edit 2: on a roll tonight http://db.tt/pq7FNlkv 1.6 lazy netfix again... Dammit I just wanna watch my show lol
[Samsung Galaxy Nexus] franciscofranco:
r223:

* Fix for boot loop on CM10 type roms

* Add custom colors by default - no more yellow rubbish screen
[Samsung Galaxy Nexus] franciscofranco:
[ 190.060577] omap_thermal_throttle: temperature too high, cpu throttle at max 1612800

Maybe reboot due to temperature?
[Samsung Galaxy Nexus] GeekMcLeod:
223 boots on PA! Thanks a lot.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] mikeandjaimie:
Shouldn't the thermal throttle prevent that? I have the option to disable turned off... As I said, never had issues till around 217 I think it was and I ran 1.8 for days stable.. Ive also tried resetting all the toggles in app just to be sure they are set properly
[Samsung Galaxy Nexus] simms22:
if thermal throttle is 90-100C, you could still hit the 110C safety/shutoff temp. ive many times gone over throttle temp by 10-15C. your phone doesnt stop heating up as soon as you hit it. if your heating up fast enough, you can hit that 110C before your phone starts cooling down.