yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] linuxholgi:
Sad to hear that... seems my assumption is not too far fetched then.

I tried to plug it into my laptop to see what happens, on one occasion I go this in the logs:

Feb 1 10:25:52 linux-s38r kernel: [56466.163579] usb 3-1: new high-speed USB device number 4 using xhci_hcd
Feb 1 10:25:52 linux-s38r kernel: [56466.174959] usb 3-1: unable to get BOS descriptor
Feb 1 10:25:52 linux-s38r kernel: [56466.175606] usb 3-1: New USB device found, idVendor=0451, idProduct=d010
Feb 1 10:25:52 linux-s38r kernel: [56466.175614] usb 3-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 1 10:25:52 linux-s38r kernel: [56466.175620] usb 3-1: Product: OMAP4440
Feb 1 10:25:52 linux-s38r kernel: [56466.175623] usb 3-1: Manufacturer: Texas Instruments
Feb 1 10:25:52 linux-s38r kernel: [56466.175914] usb 3-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
Feb 1 10:25:52 linux-s38r kernel: [56466.175935] usb 3-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes

So I am not sure whether there is still hope or not, could also be a total corruption of whole flash including bootloader, which might be resurrectable?
[Samsung Galaxy Nexus] gaich:
Osmosis 900colorsettings works well, maybe the title needs renaming?

,
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I've based mine on that. Try with a different number on the front add a 0 maybe 990readahead

Is anyone else having issues with this?

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

I just tested on my gnex and is working great. It must be something on your end. Try checking the value directly on the file
[Samsung Galaxy Nexus] gaich:
Tried different names and even tried to add this command to osmosis file, nothing helps.

Maybe the permissions aren`t right?View attachment 1693870
[Samsung Galaxy Nexus] osm0sis:
If adding it to the working file doesn't work then you either typoed the command somehow or forgot the trailing extra blank line. The permissions are fine if it already works for everything else. ;)

joaquin's files look fine to me, so like he said, it's something you're doing.
[Samsung Galaxy Nexus] Degrated Shadow:
Is this in already? I want it very badly.

http://xdaforums.com/show....php?t=2044340
[Samsung Galaxy Nexus] parkson:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Been trying to keep up but its difficult. So many different configurations.

What is best set of gov control tunables? Current tunables are meant for n7?
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

^^This is mine current setup for testing:

These are for everyday use

Both are super stable and smooth, I'm just testing batt life with first ones....
[Samsung Galaxy Nexus] newbcake:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Noticed something similar. Running Xylon and 364. My phone started to have charging problems (10 minutes of charging after a reboot then just nothing) the phone would say it was charging but power just dropped. After that, I noticed my phone was hot and I opened up Trickster Mod which reported my battery was overheating so I unplugged my phone. After that my battery stayed around the 90-100s and refused to charge until I rebooted. Back to 361 it is
[Samsung Galaxy Nexus] alfiemenace:
returned my device to stock. and sh*t the colors are so bad. good thing there's franco kernel! :good:
[Samsung Galaxy Nexus] wrext0r:
I've got almost the same values here for testing. But for what does boost and min sample time exactly stand for? I can't figure out...

Pozdrav ;)
[Samsung Galaxy Nexus] vlc_marcos:
anyone???

Hello every one.

I have a question regarding WIFI. I have on my phone slim bean 4.2.1 and the last from franco.

So the situation is this, i have enable the option to have the wifi on all the times, also during sleep mode, you know what i mean, iam speaking about the option keep wifi on during sleep.

but the thing is that when the screen is off the wifi connection is lost. what should i do to make it really enable?
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Ahhh its nice to see my setup being used and tested, ahhhhh what a feeling lol, gotta love xda

---------- Post added at 07:00 AM ---------- Previous post was at 06:56 AM ----------

Boost - from my experience is when u touch the screen it automatically ramps the CPU up to hi speed on touch, we do not need touch this because well Franco already implemeneted that feature

Min_sample - from my understanding is how often u want the CPU to check the load for going down a step in frequency based on the load at the giving time
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

^^ Correct explained as I understand the situation.

And yes, testing your settins, no big issues so far. Smoothness is the same as my "everyday" setup, there are some glitches while scrolling Settings menu, activating multitasking but... it's almost undetectable in normal use. Nothing to bother really.

Waiting battery to end up to see results....

@wrext0r

Pozdrav :)
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Im also wondering about those minor glitches, no matter how much setups I try its like its always there,

I know every device is different so I'm on the quest to find this phones sweet spot :p:thumbup:

Its also affected by other parameters apart from the kernel so, but with these low level tunables its bring me back to my car tuning days and I'm loving it lol
[Samsung Galaxy Nexus] osm0sis:
ahd should be a multiple of tr, so give your test ones a try with ahd 45. :)
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Testing now, will report
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Poke it with a stick and call it lazy, failing that threaten with it with redundancy :thumbup:

Or you could try changing the wifi sleep options to something else then change back to always. Mess with WiFi optimisation or try pm fast in francos app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] punkeroso:
To keep the WiFi on even when the screen is off, you should avoid airplane mode or disable WiFi.

So, enable WiFi and reboot the phone, and then it will stay on even when on screen off.
[Samsung Galaxy Nexus] calibachrome:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

364 working great... Used my phone for 16 hours yesterday pretty heavily and still had 35% left by the time I got home and put it on charger. I do however have the OEM extended 2000 mH battery which isn't a huge difference from stock battery. However, this kernel is awesome. Anybody else care to share?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
It seems that every one gets great battery life except me..i'm gonna try a factory reset and leave my phone clear,without any app installed for some days. If battery drain is still high,i'll buy a new battery :( (my g nexus enter deep sleep and don't eat battery in idle,but i can't even reach 3 hours of screen on per day)
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

3 hours is not bad. The gnex isn't really good on battery. I usually reach 2,5 hours on 2000 mah, but I do listen to music for an hour or so.

I stopped wining about my battery, I just charge it when I can: at home, at work... Power outputs everywhere.
[Samsung Galaxy Nexus] doomed151:
This is the third time I mentioned about it: AndroidPIT.

It's not fair, I paid the same price as those who bought through Play Store yet I'm still stuck on 8.2.2 for a long time.
[Samsung Galaxy Nexus] joaquinf:
Chill out. I'm sure that francisco will push the update as soon as he can.

asking nicely > rant
[Samsung Galaxy Nexus] osm0sis:
Email franco. He isn't always reading the thread and is a bit forgetful about AndroidPIT. :good:
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I wondered that too. Doing some digging on both threads, I came up with:

Somebody shout out if those are incorrect. I don't mess with read_ahead_kb, it is at default 1024. I also saw some tweaks for row/cfq/deadline, but am totally lost on what everyone is trying with any of those.

RF
[Samsung Galaxy Nexus] doomed151:
Actually, I did ask nicely and even waited few days before asking again :(
[Samsung Galaxy Nexus] joaquinf:
Both tuneables are correct. The only difference is on the IO schedulers. On the gnex we are running ROW/512 and on the N7 cfq/512 is what most of us are testing, otherwise ROW as well
[Samsung Galaxy Nexus] RayGarden:
Happy with Battery Life of #364

1 Day + 3 hours on Battery (no charging)

2.30 hours Screen-On

11% left
[Samsung Galaxy Nexus] joaquinf:
In my opinion getting "upset" is never a good thing to do, specially if you a re trying to get something back. Try emailing francisco as osm0sis said, he is a busy guy and keeping up with everything he has must be exhausting. Hats off to him.
[Samsung Galaxy Nexus] linuxholgi:
My phone is definitely dead. It seems 364 killed it, died while hanging on the charger over night.

Be careful guys. Something like that caused by software, costing real $$ never happened to me before. And I flashed, hacked and modded a lot in the past 10 years. A $500 phone, 4 months old now just electronic crap :(.

Our Android devices can be modded a lot, but it can end expensive.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Bull****.

The GNex has a notoriously ****ty USB port, and no-one else's phone has died from the 364, or any other recent kernel.

ie: you're either a victim of random bad hardware luck or, more likely, you did something else wrong.
[Samsung Galaxy Nexus] aR_ChRiS:
Have you tried recovery mode or fastboot mode? If it's a software error then you can always revert back to stock as this kernel (same with other kernels) will not try to modify your bootloader info.
[Samsung Galaxy Nexus] osm0sis:
There is an outside possibility that while frozen up solid his battery+SoC overheated, and since things were locked up it exceeded the thermal throttle and reached the hardware limit of 110 degrees, or possibly even exceeded that, frying his components. Fact still remains that nobody else has had any freezes since r35x, so it was a random sh*t and/or weak silicon that doesn't necessarily happen to have anything to do with f.K and doesn't really belong in this thread.

There is a way to recover the "unrecoverable" over in one of the other sections. You do so directly with the OMAP4400. Time to go do some reading to see if you can salvage it.

Edit: My Google finger was itchy so here - OMAP Flash:

http://xdaforums.com/showthread.php?t=1640443

http://xdaforums.com/showthread.php?t=1760787

Good luck!

Edit 2: Updated links again to the actual sources.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

There is also an outside possibility of thunderstorms, high humidity, and gremlins stealing his megahurtzes.

F%%king gremlins.
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I had two freezes on r364 when Google Play tried updating apps immediately on boot.
[Samsung Galaxy Nexus] osm0sis:
That's odd. My N7 took a random reboot after trying to update Perfect Viewer to the latest version. After the reboot somehow it was uninstalled instead and I had to go in and reinstall it. Very weird that the Play Store/update process is somehow involved in both freeze/crashes, but our devices certainly didn't freeze up and hard-brick. More likely to be another of Google's JB 4.2 f*ckups.
[Samsung Galaxy Nexus] LibertyMonger:
Well this is normal when updating apps. My phone is always sluggish when updating and when updating multiple apps it is to be expected to know why it might freeze. At least for me anyway. Especially "updating apps immediately on boot"
[Samsung Galaxy Nexus] shreddintyres:
for those of you who are having difficulty setting read_ahead_kb via init.d if your rom supports init.d check the folder to make sure that there isnt an init.d script setting the value as is. Im running Xylon v18 in the init.d folder there was a script 98fruit it had the line:

echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;

i simply changed 2048 to 512 and it worked

theoretically you could just delete that line and create a new init.d file and use the following

#!/system/bin/sh

# chmod -R 755 /system/etc/init.d

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb
[Samsung Galaxy Nexus] galakanokis:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

One other poster mentioned that he had a similar problem to what the other guy mentioned with the dead phone after charging. Both mentioned very high temps but one was able to catch it.

Not saying it is kernel related but worth noting and keeping an eye on. More likely it is a USB port problem but you never know. I was on my charger for over 8 hours last night with no issues.

Only hang up I had was when I under volted and the phone went through some play store downloads. Without UV all was/is fine.

G
[Samsung Galaxy Nexus] LibertyMonger:
$500 phone? Wow they got you didn't they? Especially only 4 months ago. Mine was $350 6 months ago.
[Samsung Galaxy Nexus] osm0sis:
Should work the same since /sys/block/mmcblk0/ is a shortcut to the same place as /sys/devices/virtual/bdi/?:?/ but hey, if it works, it works. ;)

Also any phone running f.K should have init.d regardless of ROM because franco included the run-parts call in the ramdisk. That's why I have init.d working on stock ROM. :D
[Samsung Galaxy Nexus] lost_man10002:
Just came back to franco kernel and app been a while. 364 is working great on my phone with 4.2.1 cm10.1.
[Samsung Galaxy Nexus] osm0sis:
On a plan in Feb. 2012 mine was $149, then in Apr. 2012 it was only $49. Then 2 months later they discontinued it entirely, so they got me too, just not as badly.. I hate Telus with a passion.. :mad: Oh well, at least I got a Nexus out of them. ;)
[Samsung Galaxy Nexus] joaquinf:
Any good news about yours? do you know when is coming back? :D
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

If you're looking for more snappiness,i suggest to put go_hispeed_load to 80 and target_loads to 70. It's working fine on my phone,without eating more battery. Try it yourself and let me know!

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
UPS delivered it to Samsung Canada in St-Laurent, Quebec on Monday morning. No word since. Hopefully soon though! :)

Yeah that basically forces it to idle higher to keep the load that low. Faster yes, but definitely at the cost of battery.

This is how interactive works now: http://xdaforums.com/showpost.php?p=36974153&postcount=3416
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Check this

http://xdaforums.com/showthread.php?p=37251517
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I don't follow other devices thread,but thanks anyway. Even if it's maybe too aggressive,it seems that lags are gone and battery is the same. Try yourself (on galaxy nexus,please ;) )

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 06:47 PM ---------- Previous post was at 06:44 PM ----------

Try also min_sample_time set to 60000

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
We're not telling you to follow it, we're telling you to read it so you understand how interactive works now. Watch your attitude. Interactive works the same on both devices; that's why joaquinf, myself, and The Gingerbread Man have been retooling the tunables for them. If you want to help then you should at least know what you're doing when you adjust them like we do. Hence read.
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Of course i understand,in fact if you read carefully my previous post you can understand it,since i wrote that these settings are too aggressive (wrote by you in n7 thread). However,i would take them in consideration. Even if they seems too aggressive,there aren't negative results with this setup (15/80/0.7/45 or 60/15/70)

Inviato dal mio Galaxy Nexus usando xda premium

---------- Post added at 06:58 PM ---------- Previous post was at 06:54 PM ----------

Also,even if you are working on these tunables since a long time and i don't understand anything about development,i'm pretty sure that my feedback (even based on wrong tunables or parameters) can be useful. I'm not trying to teach you how to do your work,i was simply suggesting to try something. Easy,don't you think?

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
Right but it also doesn't change the fact that just because you don't own a N7 you aren't "too good" to read information in another forum that is applicable to all devices running the new interactive when we link to it.

You'll also notice we didn't ignore your information, in fact we agreed with you that it was faster, and told you why, but that it's probably not the best way to do it because you might as well set your min to 537MHz or 729MHz for the same effect.
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Well, after an day or so testing with your numbers, battery is slightly better than everyday numbers and I'm pretty satisfied with overall performance. 10h std by and 3:20h of display (with almost all internet connections on 3g) is good for me. Those glitches are present but, overall I'd say you've found verry good "backup" tunables for 364.

The problem with testing is that I can't use phone on wifi all day to see any improvements in that way.
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Actually, I have also had a freeze while running 364. I didn't post anything about it though because I have logging disabled and wouldn't even be able to provide any useful information. My freeze occurred when updating Supersu from the play store. Had to pull battery. Not necessarily kernel related, but I was running r364.
[Samsung Galaxy Nexus] osm0sis:
Play Store again.. hmm.. :eek::confused:

That one could also be SuperSU related though, things have happened like that before with it.

We'll have to see if JB 4.2.2 fixes this crap.
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I didn't said i'm not good to read :) i simply said i don't follow other devices thread,but i read your posts (the ones in the link posted by joaquinf)

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
Ah well we might be dealing with a "lost-in-translation" situation again, and if so, I apologize. "I don't follow other device threads," sounds like "I don't read things from other device threads," which of course would be arrogant. ;)
[Samsung Galaxy Nexus] Angelakaro:
Yeah,it's also my fault. Sometimes,writing in english, i make a lot of mistakes ,especially when i don't reread what i've just wrote :-/ That's why i edit very often my posts and all you are going to hate me :D
[Samsung Galaxy Nexus] creeve4:
Is there a consensus on scheduler? I've mostly run deadline, but have been trying row for the last few days. It is difficult to tell a difference.
[Samsung Galaxy Nexus] Jeffro1010:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I want to add to the play store update freezes. I have had multiple freezes just today attempting to update HD widgets. Update would download and attempt to install, then freeze with the screen on, everything became unresponsive. After a battery pull, same cycle multiple times. I finally flashed back to r361 and everything went smooth. On latest Rasbean (1/26), Franco 364 with all recommended Osmosis values, interactive (1305/348), ROW (15/95/.7/45/15). Sorry no log as I had to pull battery, but I have logging off as well...
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

:thumbup::p:D
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I saw a dead squirrel in the middle of the road... is Franco able to travel around the world in a night as fast as Santa Claus?!!?! (:P loving the awesomeness Franco keep it up)

Franco r364
[Samsung Galaxy Nexus] rossrogers:
Freezes / Slowing Down

Just to add to discussion I have also had some "slowing down" of my phone after long periods of time. Usually related to lets say having the screen off for a while (say an hour or more) and then upon waking the device it just seems very sluggish. This can be quickly fixed my changing the scheduler from Deadline to ROW or from ROW to Deadline. (basically changing the scheduler to anything other than what you have set already) I am not sure what that means.

I also do not get any freezes with play store, but when the phone is updating via playstore the phone does slow to a complete crawl until the operation is done. Maybe it is getting 100% priority or something?

I don't have logs or anything, but I can try. Since I don't think anything is actually failing i'm not sure it would show up.

I don't like comparing Kernels to others, it just feels rude. But lean kernel does not have this problem of random sluggish behavior, but it does still crash my 4G when the phone sleeps for a while so i stick with franco. I've always had issues with the phone being almost unresponsive while updating anything from the play store.

I do not undervolt, overclock, underclock. nothing. I am running 100% stock values the way franco pushed them out and only switch back and forth between Deadline and ROW for fun since I really can't tell a difference.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm nominating you for "Master Google Searcher" the awesome $hit you come up with is amazing

Franco r364
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Oh freezing stuff, totally forgot about that ... Happens to me also, not during the update, but after the update/s phone freezes for a few seconds (in best ways it become laggy).
[Samsung Galaxy Nexus] osm0sis:
SuperSU just updated to v1.04 and hopefully fixes any freezes on its part.
[Samsung Galaxy Nexus] timbck2:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I had what I'll call a "DDoD" (daydream of death) - my phone was left overnight on its charger and wouldn't wake this morning but it was on the Daydream screen rather than a black screen. I too didn't post about it before now because I had to pull the battery and thus had no log to post. It could very well have been doing a Google Play Store update, I have no way of knowing. Just another data point I guess. Running XenonHD 3.0 with Franco r364 here.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marcuso:
just want to add that i also get freezes during playstore-updates with 364 ... seems to happen only with some apps though - but with these 100% reproducable for me. Have now tried a couple of things and finally went back to 361 - with that it does not happen.

Even if it sounds strange - i am pretty sure it is relates to 364-kernel.

weird thing ;)
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

CONFIRMED. I got a freeze at 4.01 AM during UCCW update, it sucked off all my battery...
[Samsung Galaxy Nexus] mariachi202:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Yup. And after a battery pull, the phone takes a looong time to boot (seems like it's boot looping) and acts like its been factory reset.