yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
Dude, that would totally fry your phone. Don't run that!!!!

jk. Yeah it's fine. I wouldn't use semicolons though. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Haha had me going there for a sec :p Do the semicolons actually make any difference?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Swede2008:
Thought the semicolons ended the statement.

Does echo 1 > /sys/class/backlight/s6e8aa0/acl_set; set the CAB to disabled?
[Samsung Galaxy Nexus] The Gingerbread Man:
And just to be sure here to create the init.d folder on stock rom the init.d folder needs to be data/local ? I'll need to create it as stock doesn't use init.d scripts

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
You're right, they end the statements but the semicolons are technically optional. I leave them in. As for CAB, it's a normal Boolean. So 0=disabled, 1=enabled.

No no you crazy person. ;) Always and only /system/etc/init.d/ - I'm stock too, but that's one of the (many) reasons to love f.K, it adds init.d to all ROMs. Then put your scripts in the directory and do the perms all at once with chmod -R 755 /system/etc/init.d

I have that chmod command in my init.d scripts but commented out just as a reminder to make sure I've got them set and what the command is. :good: :)
[Samsung Galaxy Nexus] Swede2008:
Awesome! Now there isn't that lag with the screen settings at boot. I must admit, that always kinda bugged me :silly:
[Samsung Galaxy Nexus] osm0sis:
Sorry, a little hard to understand you.. :(

Are you talking about permissions like root? If so, let me guess, you're using Superuser? Superuser is crazy buggy since JB4.1 and ChainsDD the dev never did anything about it, so most people switched to SuperSU by Chainfire, which works great.

OT: Has anyone else ever thought it was funny that both the su apps are by guys with 'chain' in their handles? I always thought that was such an odd coincidence.. :p

Yup, that delay is what got me looking into init.d in the first place. ;)

Then I discovered things actually look better contrast/color wise when any of them get set on boot, so it was actually the only way to fix the terrible colors on my device.
[Samsung Galaxy Nexus] billykxda:
It's been a few weeks since I've used a Franco kernel. The last was r300 with CNA ROM.

I am now running Muzzy's 4.2.1 ROM and found battery life on the stock kernel to be less-than-stellar. Just re-installed FKU and r342. I notice the performance difference right away. I hope to see the battery savings I've come to expect from Francisco's kernels.

A few quick questions:

- Under the color control, I swiped the screen and inadvertently set the bottom slider to some wacky number. Are the default settings 190, 195, 215? Just checking.

- What's up with these new color multipliers? These are different from Francisco's default settings of the past few months.

- Is the volume increase setting still a default, non-displayed setting?

- Is enhanced audio still a default, non-displayed setting?

Thanks!

Good to be back!
[Samsung Galaxy Nexus] osm0sis:
1) Yep.

2) Yup, he adjusted his "Franco Recommended Defaults" with JB4.2.

3+4) All sound control stuff has been removed since it was far too buggy. Franco has said he'll be adding in a hardcoded headphones volume boost in a future build, but as such there likely won't be any control for it.
[Samsung Galaxy Nexus] Ma7moud90:
Can't download 4.2 nightly builds from the free kernel updater app :(

and Play Store shows it hasn't been updated since october

I can't buy the paid app because Google doesn't allow paid apps in my country :(

I downloaded and flashed r342 manually but i wanted an easy updater for later
[Samsung Galaxy Nexus] cap'nC:
I think he's talking about a bootloop that happens when he unlocks the phone after the toast message triggered by superSU/superuser about FKU getting permissions.
[Samsung Galaxy Nexus] billykxda:
As always osmOsis - thanks dude.
[Samsung Galaxy Nexus] osm0sis:
Ah thanks, I can see that now that I reread it.. :good: Alright, so it reboots once Franco gets root, which would clearly indicate you've got a bad setting or voltage screwing things up. Wipe f.Ku data+cache. I'd still recommend SuperSU with the toasts off over Superuser since it could also be causing this (and also in general, unless you like using buggy apps ;)). And uninstall PGM if you have it since it's the other main offender for reboots at the moment.
[Samsung Galaxy Nexus] superbobup:
It has also happened for me before on Trinity, and one person suggested it may be because of CAB...I don't think it's voltages or a weird Franco/TKT app issue but I can't say for sure. Also happens with PGM uninstalled
[Samsung Galaxy Nexus] jcmm11:
If you're using twrp then you have options other than adb. Mount system then use the built in file manager to change permissions and prevent the script from running.

I also check for the existence of a given file before changing it. So my init.d scripts tend to have commands of the format:

if [ -e /some/file ]; then

echo "value" > /some/file

fi

Edit: as far as pgm goes I've had no issues, other than it not applying on boot, ever since I uninstalled then reinstalled it (installing the kernel in between).
[Samsung Galaxy Nexus] whitewallman:
It's already been noted that the latest Franko.kernel updater force closes when checking leankernel updates, correct?
[Samsung Galaxy Nexus] thegtfusion:
damnn the minooch site is down. can anyone upload r342 for me? :D
[Samsung Galaxy Nexus] yellowdie:
Sad day, unfortunately, the free app is lower on Franco's priority list, so it won't get updated until the paid app is done with it's rewriting. :( Sorry, but manual flashes may be your best bet.

I said it's CAB and I still think it is. It's hit or miss for some people. I know with my phone I can replicate your exact issue any time I want by checking the "Disable CAB" checkbox and rebooting. So just uncheck that and you should be swell.

Yeppers.

Works for me.
[Samsung Galaxy Nexus] Shadow-Nexus:
Hey Franco nice work with the newest update on fku

Also I really like your Rebooter app could you maybe in the future implement then reboot options in Fku?

Thanks!
[Samsung Galaxy Nexus] Khrushy:
Much of the text in your app is amusingly worded, so I was poking around in places I hadn't bothered before to see what they said.

When I hit the LeanKernel button I didn't manage to read the toast entirely when it appeared, so I hit it a second time. :P
[Samsung Galaxy Nexus] superbobup:
Ha I can never remember who said what anymore :p and yes, I can reproduce it too if CAB is turned off, but I swear it's happened with CAB turned on.

All this reboot and SOD **** seems to happen with controlling the display (CAB and color control). Maybe Google just wants us to use their colors :D
[Samsung Galaxy Nexus] bradm23:
Not sure if this was seen. I'm sure it wouldn't hurt to include this option. Thanks again
[Samsung Galaxy Nexus] MaLiXs:
lastest franco r342 zip : http://www.sendspace.com/file/51fybc
[Samsung Galaxy Nexus] thegtfusion:
Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] garuhhh:
After reflashing ROM (without wiping my data), everything seems well. No more reboots, at least for the past 10hrs or so. Previously, I had 3 reboots with my phone just doing nothing with r342, so it was really not a kernel issue.

Back to the usual buttery goodness!
[Samsung Galaxy Nexus] KJW979:
Using r342 with Eclipse, no reboots, SOD's, or lag, running really smooth. Haven't fiddled with voltages yet, probably tomorrow. Thanks Franco for all your work, much appreciated.
[Samsung Galaxy Nexus] Exostenza:
Ran 342 all day and my phone is about to die before the end of the day! My phone has never died on me before and I usually have about 40 percent at the end of the day. No rogue applications or different use than normal... :(
[Samsung Galaxy Nexus] kyokeun1234:
Wait until kernel settles into the os. The first day of the kernel has always bad battery life IMO
[Samsung Galaxy Nexus] Khizar:
i had that issue with r335.. havent had it with r342, yeah its eating more battery than older versions but not by much
[Samsung Galaxy Nexus] gianton:
I noticed a small increase in battery drain with r342 too, but it's a lot smoother than previous versions.
[Samsung Galaxy Nexus] Khizar:
yeah i am currently using it with stock settings and it feels alot smoother
[Samsung Galaxy Nexus] Exostenza:
I've been flashing every kernel iteration I can get my hands on by Franco and have never had to wait for the kernel to "settle" in.

On another note I just tried Airkernel to see what is going on with other kernels and it is so choppy and slow I came crying back to Franco 342 with the bad battery life. :)
[Samsung Galaxy Nexus] Khizar:
why not use a older version that has better battery life if r342 doesnt work good for you?

---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------

you should wait for 5-10 mins after flashing a kernel for it to settle down.. after that you can mess with it all you want and not have issues.. as for bad battery life on the first day, if i get bad battery life on the first day i will get on all days
[Samsung Galaxy Nexus] Khrushy:
Except for the fact that for (at least) the first charge cycle after flashing a new kernel your battery calibration has potentially no &%#king idea what it's real reading is, so basing your judgements off that is silly.
[Samsung Galaxy Nexus] Jar3112:
Via .zip

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
my judgement is based on my experience, so its not silly its a fact
[Samsung Galaxy Nexus] sago62:
sorry, a silly question...what is tku?
[Samsung Galaxy Nexus] Khizar:
its fku not tku.. its the franco kernel updater app
[Samsung Galaxy Nexus] sago62:
Sorry...thanks:D
[Samsung Galaxy Nexus] splus:
Ever since I'm roaming on 3G, in Franco kernel app I get a message "you need Internet connectivity for this" in the kernel updater part.

But the thing is that I'm connected to Internet.

Everything else can access internet just fine.

Franco, any chance you can look this up, please? It looks like it doesn't recognize Internet connection if roaming...

Xylon ROM, btw.
[Samsung Galaxy Nexus] Khrushy:
Dude, coming into a thread for a Kernel and essentially saying "Just go with your first reactions about battery life", despite the fact it's well documented that you get inaccurate battery readings for at least the first cycle after flashing a new kernel, is undoubtedly silly.

If it's your experience, and you want to work like that, then great, you do that all you like, but don't go encouraging others to just have knee-jerk reactions without testing it properly themselves.
[Samsung Galaxy Nexus] sago62:
I understand ... depends on FKU! if I uninstall fku, the kernel works fine, as soon as I install it creates problems ... I did the test 2 times! In fact, my girlfriend uses the same kernel + rom with trickster and it works great ...
[Samsung Galaxy Nexus] Joplisan:
I have to agree here, based on my experiance. I usually charge the phone after changing the kernel to reset battery and get a fresh start. That first run is always realistic for me. If it's bad, it will always be bad - if it's good, it will stay good. I'm not saying that it works for everyone, but it definitely works for me, too.
[Samsung Galaxy Nexus] Khizar:
jfyi first impression = 1-2 days which is plenty to test a kernel IMO.. like i said before i was getting bad battery life on r335 but i kept using it and overnight my phone died and this was after a full charge.. btw this isnt just for franco its true for all the kernels i have tried if i get bad battery on the first day i will keep getting battery life nothing changes even after charging the phone and using the phone for more than 3-4 days... and if on the other hand i get good battery life on the first day then i will keep getting good battery life
[Samsung Galaxy Nexus] garuhhh:
I spoke too soon! had another reboot just now. I don't really understand any of the logs in the last_kmsg. I will try wiping all my data later tonight, and see if any improvement. and again, all my APN settings are gone, I had to manually restart the phone to get them back.

@osmosis, I don't use PGM. sorry, I missed your previous question.
[Samsung Galaxy Nexus] Khizar:
lol tbh i didnt say its true for everyone but i think Khrushy thought i did.. in all my posts i was sharing MY experience, which i have had after flashing different kernels.. i didnt say everyone is gonna have the same experience as me.

---------- Post added at 01:28 PM ---------- Previous post was at 01:26 PM ----------

hmm.. i was getting random reboots on r340 but on r342 i experienced freezes and reboots ONLY when i messed with voltages, atm i am using stock settings and have no issues
[Samsung Galaxy Nexus] moe6:
Update: Dirty flashed fixed it. I have no idea what the hell was making it **** itself after flashing, I definitely don't think it's kernel related either as someone mentioned. Just posted it in case it was an app issue, which is definitely not the case now.
[Samsung Galaxy Nexus] seriousia:
Anyone having screen not responding problem after any call or when you try to wake up device.

Try multitouch on the screen it works and bring your touch back :D
[Samsung Galaxy Nexus] Pasquale91fg:
Not work the link for Download Kernel ( 4.2.x)
[Samsung Galaxy Nexus] rnenjoy:
Just flashed 342 using the latest franko updater (just recieved an update to that app). And my phone now refuses to boot. I just see a Google logo.

Using latest Phandroid.

---------- Post added at 11:28 AM ---------- Previous post was at 11:17 AM ----------

Redid it now, and now it worked.
[Samsung Galaxy Nexus] HyvelTjuven:
I have this as well, I was on Xylon 0082 and flashed the latest nightly. Now I can't get past the google logo.

I guess there's nothing to do but to re-flash.
[Samsung Galaxy Nexus] tobitronics:
Noticed that switching from normal to quick settings drop down animation is laggy. Running stock 4.2.1 anyone else with this problem?
[Samsung Galaxy Nexus] MrRevhead:
R342 is also causing random reboots and/or freezing on my GNex (JOP40D), usually within the first minute of booting into the OS.

Flashed back to R328 for now and everything is running fine like before.
[Samsung Galaxy Nexus] shawnaye:
Guys my wifi keeps on reconnecting itself.

Basically I'm using it fine. Then I lock it. And when I unlock my phone. I see the wifi icon missing then come back.

Wifi is kernel related right?

But strange that no one has this so far.
[Samsung Galaxy Nexus] kyokeun1234:
Hm that's weird...

Did you uncheck avoid poor WiFi connection?
[Samsung Galaxy Nexus] shawnaye:
Yeah. Now my wifi is just switching off every single time my screen is off. Weird...
[Samsung Galaxy Nexus] moe6:
I had this issue as well a few pages ago, haven't got the time this week to really delve into whether it's an app, ROM or the kernel itself however :(
[Samsung Galaxy Nexus] garuhhh:
I'm also running stock 4.2.1, but I don't have this.
[Samsung Galaxy Nexus] osm0sis:
Do you use Superuser or SuperSU?

You've got a bad setting with voltages or something. Wipe f.Ku data+cache and try upgrading right away so you're starting fresh.

Have you been running with fsync off and got a freeze/reboot recently? My guess is the setting for Wi-Fi sleep policy got corrupted. Try turning it to when asleep and then back to always.
[Samsung Galaxy Nexus] Khrushy:
Is there any way in a k_lastmsg to tell which frequency was to blame for a reboot? I've been running the same voltages for around 5 days now without issue, but I just had a soft reboot, and I can't seem to tell from the k_lastmsg which frequency it is that decided it wants more juice. . .
[Samsung Galaxy Nexus] sago62:
i have supersu....thanks
[Samsung Galaxy Nexus] shawnaye:
I think you just saved my life :angel::angel:

Haha,i had fsync off a week ago, just to try and see if i get I/O improvements.

But i just did a full wipe last night, why is something i did a week ago bothering me now?! :confused::confused:
[Samsung Galaxy Nexus] osm0sis:
Unfortunately no. Best way to isolate is lowering your max OR raising your min until it's stable, that or going through the frequencies on performance governor by setting them as your max and then stress testing with a game/benchmark.

Try giving f.Ku "fresh" permissions by removing it from the list in SuperSU. I also recommend turning off the toasts they cause lag. If that doesn't work try reinstalling SuperSU then reinstalling f.Ku.

Well maybe it wasn't the fsync then. Some ROMs have the policy default to off when asleep. Maybe it's a random settings derp from Xylon.
[Samsung Galaxy Nexus] Khrushy:
Many thanks Os. Trial and error to find the culprit it is then!
[Samsung Galaxy Nexus] sago62:
nothing to do! I uninstalled update supersu, I uninstalled FKU, I rebooted the phone .... I finally updated supersu and installed FKU ... does not work!nothing to do!

this does not happen if you restart charging with active daydream ....:confused: wait for new version of FKU ...:crying::o or unlock the screen before shutting down ....
[Samsung Galaxy Nexus] shawnaye:
Strange world we live in my friend. No one's complained on xylon nor here though.. only me :silly:
[Samsung Galaxy Nexus] osm0sis:
Very bizarre. Post a logcat and last_kmsg up from when it happens.

Edit: Wait is SuperSU on your ROM? If so you can never really uninstall it. Clear data+cache on it instead.

Are you using PGM (slide-to-wake)?

BusyBox installed to /system/xbin/?
[Samsung Galaxy Nexus] sago62:
Yes,it's in rom ... I already canceled 100 times the cache + data ... it seems that if FKU takes the permissions with the screen off does not work ... if it unlock the screen ,permits arrive and it works ...strange:banghead:
[Samsung Galaxy Nexus] osm0sis:
So try a different ROM or do a clean reflash of your current ROM? I don't think anybody's having this problem but you... :(
[Samsung Galaxy Nexus] sago62:
I left image 4.2.1 .... It all started last update FKU .... if I uninstall FKU, everything works with Franco ... ok,i don't you disturb...thanks
[Samsung Galaxy Nexus] punkeroso:
Do you put your phone in airplane mode? What I noticed is that the WiFi is acting like this after disabling airplane mode. If I reboot the phone, WiFi is acting as it should.

I've never had the time to investigate more about this issue.
[Samsung Galaxy Nexus] arhung:
May I ask why Franco disable the calibration? It seems the calibration is better than us to under the voltage ourselves.:)
[Samsung Galaxy Nexus] osm0sis:
You misunderstand. Franco disabled SR on CORE (GPU+other components) a long ways back because those other components were causing Wi-Fi and signal dropouts when SR calibrated them too low. Everything is more stable without SR on CORE. This is also what allows every phone to run 512GPU now.

Similarly, he just hardcoded a couple frequencies outside of SR because they are more stable this way (537MHz especially), and 192MHz is hardcoded for the voltage savings since SR can't calibrate lower than 830mV (which is what 384MHz is already at).
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Getting good battery life on r342. Battery Widget Reborn? is showing 58 minutes per 1% drop right now. WiFi always on, Background Data on. It dynamically updates, so if i start streaming Bluetooth, it will drop, but since last night, doing nothing but some email/SMS, it looks good.

384/1228/537 Off/729 Input/1036 Hi-Speed/Interactive-Deadline at the moment. Stock voltages and SR, CAB On (unchecked).

Battery stuff is the great mystery on Android, to me. You read so much stuff. Delete this after flashing, no don't, it's a myth. A 100% charge wipes everything out anyway, etc... I just charge to 100% whenever I do any flashing updates, and leave it on the charger while doing so...works for me.

RF
[Samsung Galaxy Nexus] bradm23:
Franco, any chance putting in cfq for testing... Cfq has been the best io for me lately
[Samsung Galaxy Nexus] supernova_00:
Holy **** dude, give it a rest! You asked three times in 24 hours! Yesterday at 05:09 PM and 09:41 PM, then again today at 11:14 AM
[Samsung Galaxy Nexus] b1337:
Switch to a kernel with that i/o then
[Samsung Galaxy Nexus] bradm23:
To be honest this thread moves so fast things can easily be overlooked. I was hoping to hear some feedback from Franco, but thanks for the kind words. ;)
[Samsung Galaxy Nexus] sago62:
I finally installed trickster and now it works fine ... I'm sorry but ...
[Samsung Galaxy Nexus] windsor:
@osmosis, can you share to us about your fku settings... Please :D
[Samsung Galaxy Nexus] alexdemonumber3:
He posted them a few pages back. Search the thread for share settings
[Samsung Galaxy Nexus] franciscofranco:
Nop, CFQ is mostly for rotational disks, not worth it here.

I tried to follow your line of discussion but it was a bit hard. So whats that permission problem? My app doesn't ask for any SuperSu permission on any screen on/off, theres no background service in the app that listens to that even and starts pushing root commands. Beside you I've never seen anyone with that problem so without more info I can't help you. I got my app installed in 4 different devices and I never have any problem so I dunno, I'm don't do magic. :)
[Samsung Galaxy Nexus] creeve4:
How do I get CIFS working with r300? Does anyone have a CIFS module that will work with this version?
[Samsung Galaxy Nexus] franciscofranco:
CIFS is not enabled in this kernel and it will never be, sorry.
[Samsung Galaxy Nexus] Mrc527:
Franco, can you enable /proc/config.gz for the new 4.2 kernel too?

Thanks! :D
[Samsung Galaxy Nexus] franciscofranco:
Shoot, I missed that, sorry 'bout that.
[Samsung Galaxy Nexus] bradm23:
Thank you for taking time and answering my question. I didn't know that it was typically for rotational devices, however isn't this what Google uses as default?

I have tried 80% of the nightlies, and just recently i tried out a new ROM which had stock kernel as default. It was surprised how smooth it was when it came to scrolling. There was zero jitter when a scroll was slowing down and i pinpointed it to the cfq i/o. After seeing that i began to think how great of a combo it would be in fk. As an example, any time i use any kernel with dead line, scrolling is smooth until it starts to slow down. Before it almost stops you can tell there is a small amount of jittering.
[Samsung Galaxy Nexus] sago62:
simple, if ignition does not unlock the screen, the phone will shut down and restart, it shuts down and reboots ... but if the release, everything works fine ... if I remove the phone FKU all goes well .... sorry for English ....:D
[Samsung Galaxy Nexus] creeve4:
Why do you not want to include CIFS support?
[Samsung Galaxy Nexus] davec1234:
That answer isn't good enough?

I think his time is better spent developing as opposed to answering the same damn questions over and over asked 20 different ways.

Don't like it? Run another kernel.
[Samsung Galaxy Nexus] creeve4:
Easy killer... I'm just asking.

I was not aware he had answered this question before (I have seen it asked several times, but not answered). Can you tell me where I can find Franco's answer?

Franco,

What kind of problems was CIFS causing that prompted you to remove it?
[Samsung Galaxy Nexus] malaroth:
I won't bother Grand Master Franco with this, osm0sis is there any way for the latest nightly to beam me to the mother ship? I kid I kid! Thanks again Franco and company for your work creating such a smooth kernel.

Sourcerized 4.2 r2 + Franco FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] osm0sis:
Franco, I think he means if he doesn't unlock the phone after boot then it bootloops. It only does this for him with f.Ku installed.

Sago, you need to make a logcat and post it with the last_kmsg after you get one of these reboots. I asked you for these twice now since they're the only way Franco might be able to figure out what's wrong.
[Samsung Galaxy Nexus] malaroth:
Actually I was wondering what rom you're running on your s3 and n7 Franco. I'm personally having zero problems on my Gnex but my dad wants the same rom on both devices and is stuck using lk on LS.

** edit meaning bringing him over to Franco.kernel if possible.

Sourcerized 4.2 r2 + Franco FTW! Keep the Magic alive!