yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cmstlist:
Not at all. The issue I posted is on stock 4.3 with the latest franco nightly. The user who quoted me with the same issue is on CM but I am not.

However in light of the information posted, next time this happens to me I will go check the current CPU speed to see if it is similarly stuck.
[Samsung Galaxy Nexus] mpokwsths:
Some people here are highly disrespectful on the work of CM...

CM maintains over 100 devices so it's absolutely natural to have bugs on a new version of CM. Some devices would be dead if it wasn't CM who resurrected them (HP Touchpad / android for example).

Bugs? At least it takes them a couple of days to correct them.

On the other hand the giant named Google never fixed the SystemUI mem leak on 4.2.2 (CM10.1 improved that significantly). Or the SODs some people experienced in 4.2.1. Or the deterioration of internal NAND performance (lack of TRIM) on stock Nexus devices until recently.

So some bugs in the first versions of CM are absolutely tolerable and fixed within days whereas some of Google's bugs are intolerable and never fixed (until a new version of Android at least)...
[Samsung Galaxy Nexus] blackhand1001:
Not to mention this a nexus phone so cm for the most part is rock solid stable on these.
[Samsung Galaxy Nexus] hipwell:
could somebody tell me how to use the terminal commands from the first post? I want ti enable fast charge and the volume boost but i have put the commands stated into adb but the commands arent recognised. Or do i not put them into adb?
[Samsung Galaxy Nexus] kaluoshi:
Easy way, use Franco Kernel Updater (it's on sale too for this week with 25% off and is the best way to support francisco) or Trickster Mod apps, you can tweak all with a GUI. For the terminal way, you can install Terminal Emulator and execute commands from phone (execute "su" command before the ones in op from the terminal to operate as root or you can't be able to nd get permission denied from terminal emulator)
[Samsung Galaxy Nexus] eduncan911:
I've been wondering what benefits that Franco kernel app had. Been far too busy to "check it out."

But this post, the fact I can enable USB fast charge (and it now charges with my car's inadequate USB charger), and it is 25% off, SOLD ME!

Purchased a few minutes ago, enabled fast charge, rebooted, went out to car and confirmed: it freakin' charges now!!!

Man have I missed the boat on that app in the past. Thanks man for this post!

(I'll +1 when I get to a desktop)
[Samsung Galaxy Nexus] AbhishekS:
PGM love for 4.3 kernels?
[Samsung Galaxy Nexus] osm0sis:
Module support can be added back (and some kernels already have). Francisco is toying with the idea on the N4 currently.

Google disabled it as a security risk, so there's a lively debate about whether we should go with their reasoning or not.
[Samsung Galaxy Nexus] hipwell:
Thanks mate, bought Franco updater its a great ap.

Loving my combination of stock 4.3 with Franco and root.
[Samsung Galaxy Nexus] Edward Stanbury:
PSX ROM and FK blows my mind so fast ! :D
[Samsung Galaxy Nexus] okanb3:
Is that PSX really great? I found it very similiar to RasbeanJelly
[Samsung Galaxy Nexus] Edward Stanbury:
I think PSX has some stuff from rasbean it says that in the thread description and he use to post the Roms in rascarlos thread :)
[Samsung Galaxy Nexus] okanb3:
I saw that after my post, yeah. But then i'll ask you, why you use PSX instead of Rasbean? Why you are choosin' PSX?
[Samsung Galaxy Nexus] Prasad:
Feel like a nub asking for PSX ROM link... But I googled it and PlayStation Roms came up o.@

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] okanb3:
Here you go
[Samsung Galaxy Nexus] Prasad:
Thanks! Isn't there a page or site for discussing this rom and it's changes?

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] okanb3:
Aand here it is too!
[Samsung Galaxy Nexus] Edward Stanbury:
something new and sleek thought it would give it a try and just ended up falling in love with it haha ;)
[Samsung Galaxy Nexus] okanb3:
Well, i'll definetely giving a shot :)
[Samsung Galaxy Nexus] osm0sis:
Hmm I just hit 48h uptime and suddenly my phone felt stupid fast again. Checked the logcat and fstrim had run. So we got that goodie on the GN too! Guess I should update my fixed version by removing discard from the mounts that get trimmed. Anyone know which ones get trimmed? I haven't been able to find anything definitive so far in my search.

Edit: Looks like it's "all write mounted filesystems" according to this Anandtech article that examined the code in vold manager and posted some sample fstrim output.. so generally /cache and /data. I may or may not leave discard enabled for system then since it's generally read only and wouldn't get trimmed by fstrim, but also experiences few writes so technically might not need discard anyway. The xda article quoting Anandtech nicely highlights the conditions required for fstrim to be triggered.

http://www.xda-developers.com/android/yet-another-reason-to-update-to-android-4-3-trim-support/

http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices
[Samsung Galaxy Nexus] AutomaticFailure27:
I wanna say /system and /data. Only clue I had was when I restored lagfix with titanium backup and ran it, it only allowed me to run the /cache trim. After, reinstalling lagifx, I could wipe all 3... So, not too sure if those are the ones Google intended but it's a possible clue non the less.

Edit: Damn, you edited yours before I could post mine. Lighting Osm0sis!

Sent from my Nexus 7
[Samsung Galaxy Nexus] AbhishekS:
I asked it again, got no reply so asking again. Did a search too but somehow didn't find anything useful.

Is PGM supported on 4.3 Franco kernels?
[Samsung Galaxy Nexus] Pkt_Lnt:
[MENTION=4544860]osm0sis[/MENTION] replied to you right below your original question! :rolleyes:

Your post # 43051

http://xdaforums.com/showpost.php?p=44813724&postcount=43051

osm0sis reply post # 43052

http://xdaforums.com/showpost.php?p=44815815&postcount=43052
[Samsung Galaxy Nexus] AbhishekS:
Oh. My bad.

Tapatalk somehow directly brought me to this page.

Thanks for linking to it. :)

So can we expect PGM in the near future or are the devs still confused over it?

Some kernels have enabled module support, and they are working fine.
[Samsung Galaxy Nexus] dracon6ai:
I'm waiting for a PGM answer also. One of the features I miss most from the 4.2 days. I know other kernels support it but other kernels don't run as good as Franco. Been living without it but would really love to see it come back.

***Laziness is nothing more than the habit of resting before one gets tired!***
[Samsung Galaxy Nexus] blackhand1001:
Is there going to be another release soon to fix compatibility with cm. The speed is great but it has occasional freezing and then a bootloop about a minute later.
[Samsung Galaxy Nexus] bigknowz:
BFQ

Since there is no BFQ in r390, does anyone have a full list of the tunables from r384? I only have the following:

# bfq tweaks

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty

echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle

echo 0 > /sys/block/mmcblk0/queue/iosched/raising_max_time

echo 2000 > /sys/block/mmcblk0/queue/iosched/raising_max_softrt_rate

# raising_max_softrt_rate is 7000 default, in case there are issues
[Samsung Galaxy Nexus] pkgnex:
That's all of them...
[Samsung Galaxy Nexus] bigknowz:
BFQ

Sorry, I was referring to these other settings:

back_seek_max

fifo_expire_async

fifo_expire_sync

low_latency

max_budget

max_budget_async_rq

quantum

raising_coeff

raising_min_idle_time

raising_min_inter_arr_async

raising_rt_max_time

timeout_async

timeout_sync

weights
[Samsung Galaxy Nexus] pkgnex:
Sorry, I don't remember the actual values, but we left these all at their default values, so they should be fine even without visibility via the app.
[Samsung Galaxy Nexus] dracon6ai:
Are you on Franco's r390 or Os' r390. Franco's has SR enabled which caused reboot issues for some. Os' version has SR disabled and works like a champ.

***Laziness is nothing more than the habit of resting before one gets tired!***
[Samsung Galaxy Nexus] osm0sis:
Thanks! That was definitely the big problem with r390 since all the f.K default voltages were predicated on SR being disabled. :)

v3 of my r390-fixed just went up. It removes the discard mount option for cache and data since now with JB4.3 the volume daemon (vold) built-in fstrim will be handling them every 24-48h provided you plug-in at night. This should hopefully improve I/O speed somewhat. I left discard in for system since it doesn't get trimmed, and this shouldn't affect much since we don't write to system regularly.

http://d-h.st/users/osm0sis/jb4_3/tuna/

Previous version had 145 d/ls. :good:

Now on to grouper.. ;)
[Samsung Galaxy Nexus] pkgnex:
As always, you're The Man, Os!
[Samsung Galaxy Nexus] blackhand1001:
Thanks so much. Installed it tonight and so far so good. We'll see how it goes but I have a good feeling.
[Samsung Galaxy Nexus] namtombout:
:thumbup:
[Samsung Galaxy Nexus] sotoskawasaki:
I know its off topic but what 4.3 roms are you people using? Any suggestions?
[Samsung Galaxy Nexus] pkgnex:
r390 "osfix" is running like a champ for me (as expected).
[Samsung Galaxy Nexus] osm0sis:
Haha apparently we missed some info when Francisco merged boype's excellent timer_slack commit:

http://xdaforums.com/showpost.php?p=44899678&postcount=5249

Guess I'm looking at a v4 of "osfix" :p

Edit: On second read, looks like there are more commits required on the zImage side as well.. :( I left a note on Francisco's github.

Edit 2: Yup there are a bunch of cgroup errors in the logcat this should fix. :good:
[Samsung Galaxy Nexus] blackhand1001:
I unfortunately had a freeze today on o's version today. Was hoping it would solve my issue. I switched to fancy kernel until I know the issue is fixed.
[Samsung Galaxy Nexus] mixtapes08:
Edit. Found it
[Samsung Galaxy Nexus] osm0sis:
That's pretty vague, there, big guy. ;) How can something be fixed when you don't even describe what happened or how to reproduce it?
[Samsung Galaxy Nexus] Ladaga:
The freeze only produce with screen off. I haven't got more idea of the problem
[Samsung Galaxy Nexus] osm0sis:
Screen off directly after boot? Some devices can't handle disabling Content Adaptive Brightness after the boot sequence. This was mentioned a few pages back along with the init.d script to use to turn it off safely. It's also included in my color settings script on my GN settings post, linked in my sig.
[Samsung Galaxy Nexus] Ladaga:
No, I have a normal use of my phone but in some moment I turn off my screen and then freeze, I can't wake up it.

I can't give you more information sorry...
[Samsung Galaxy Nexus] osm0sis:
Yes you can... your kernel settings, for one, and also whether you are using r390 or my latest r390-fixed.
[Samsung Galaxy Nexus] Ladaga:
Default settings in both cases, no problems with r390 only freezes with your last 390-fixed jeje
[Samsung Galaxy Nexus] osm0sis:
Well it sounds like what was happening with r390 because SR was on, so my guess is something retarded with voltages pertaining to you, since I've been running my custom voltages (lower than the defaults) on r390-fixed (which has SR disabled) for a few weeks now with no problem.
[Samsung Galaxy Nexus] :
CM10.2 nightlies :) here: get.cm/?device=maguro
[Samsung Galaxy Nexus] Edward Stanbury:
Ditto :P
[Samsung Galaxy Nexus] UlbaWan-:
I've a boring issue...

I had root with ARHD with the stock kernel but when I flashed franco, I lost root (Binary SU not updated and I can't upload this : I got an error...) I tried to flash the osfix kernel and I reflash the clockworkmod su from their website with cwm : impossible to get root... :(
[Samsung Galaxy Nexus] kaluoshi:
Flash SuperSu 1.51 over it
[Samsung Galaxy Nexus] UlbaWan-:
Funny ! I tried to install from google play before your answer and it didn't worked. After readed your answer I tried the flashable zip and it worked.

Thanks BigBrother1984 :good:
[Samsung Galaxy Nexus] Ladaga:
Then... Can I solve it enabled Sr?
[Samsung Galaxy Nexus] dracon6ai:
Noticed something today, I flashed Golden Kernel to see how it was and I noticed CAB off doesn't reboot my device anymore on boot up. I'm thinking it might be because it was set to off by default but if that's the case why isn't it set to off by default for Franco? If it would get rid of all these random reboots people get (including me for awhile) because they didn't know about it then that would be a huge plus in stability. Just my 2cents. :)

***Laziness is nothing more than the habit of resting before one gets tired!***
[Samsung Galaxy Nexus] franciscofranco:
r391:

* Add fsync toggle back

* Disable Smartreflex calibration which would cause some frequency steps to be overcalibrated wrongly and causing overheat

* Enable modules support so Touch Control will work again

* Properly set up Timer Slack

* Merge some patches from Android gerrit with some fixes

* Re-code Sound Control from scratch and now it will boost the hardware register directly and will boost accordingly. If you're using FKU (which has not yet been updated for this change) setting the Headphone boost to 0 disables the boost, setting it to 1 enables the boost. 2 and 3 values won't do anything at all. This approach will enhance the Volume and will prevent bugs like low volume on calls etc.
[Samsung Galaxy Nexus] :
So are you going to update the FKU app to change the headphone boost option? Since values 2 and 3 won't do anything, it'd make more sense for the option to be an off/on option.
[Samsung Galaxy Nexus] franciscofranco:
Exactly. There are more options coming like mic gain and possibly earpiece and speaker just gotta find out which registers do what. Also maybe make use of the integrated DAC for better sound quality. We'll see, I didnt have more time to test, I spent yesterday night testing this new approach and went to bed at 8am.

Sent from my device
[Samsung Galaxy Nexus] Fenvarien:
Thanks for your hard work and the great development for this device! :) :good:

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] vlasis_myr:
What do you mean by this: Enable modules support so Touch Control will work again. I'm asking because pgm still not working, so what is touch control...?

Στάλθηκε από το Galaxy Nexus μου
[Samsung Galaxy Nexus] franciscofranco:
Pgm is touch control. I enabled modules on the Kernel, the rest depends on the developer of that module, not me.

Sent from my device
[Samsung Galaxy Nexus] vlasis_myr:
So i apologise for my wrong...keep the good work man and thanks for the quick reply...greetings from Greece!

Στάλθηκε από το Galaxy Nexus μου
[Samsung Galaxy Nexus] stevensoaj:
Now I could be wrong, but I don't think its actually CAB being on that causes the reboot. I believe its CAB being changed from off to on or on to off while the screen is off that causes the reboot. If that's true, then you'd still have people reporting the problem regardless of what the default setting is.

Edit: This also helps explain why using an init.d script to set CAB on boot works without causing reboots.
[Samsung Galaxy Nexus] :
Is the overheating issue still there?
[Samsung Galaxy Nexus] RohanM:
deleted
[Samsung Galaxy Nexus] Sik-1:
U are in the wrong thread, an u should b using the r178 seeing ur on a N4
[Samsung Galaxy Nexus] styr:
You still need to revert this for PGM to work.
[Samsung Galaxy Nexus] Schneewitzchen:
Hey Franco,

after your update to #391 your app doesn't show up the values in the governor control section!

Osmosis edited the #390 to show these values.
[Samsung Galaxy Nexus] Astug:
Set another governor, then set it back to interactive, now the values will show up.
[Samsung Galaxy Nexus] mpokwsths:
... and lose the improved (especially under load) touch responsiveness. Don't do it Franco... :cool:
[Samsung Galaxy Nexus] Schneewitzchen:
Thx, but this is just an intermediate solution! After rebooting the device or flashing a new kernel, all values aren't there again.
[Samsung Galaxy Nexus] :
...better than killing the power button and the volume rocker.
[Samsung Galaxy Nexus] thegtfusion:
No hard feelings, but I don't know what all this PGM hype is about. There is a power button for a reason! (And optional volume wake)(no offense pgm dev :) )

This is a franco kernel thread, and not a PGM thread. Problems with PGM are the PGM app related, so discuss the problems of pgm there.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] bunnahabhain:
:victory:
[Samsung Galaxy Nexus] osm0sis:
In on vacation until next week. If Francisco doesn't read the email I sent him and make some of the ramdisk fixes I did before I get back, then I guess I'll do one based on r391 and send him another email. ;)
[Samsung Galaxy Nexus] niamul:
Where is the link to r391? It's not on the first page/post
[Samsung Galaxy Nexus] bigknowz:
OP

Default [KERNEL] [GPL] [GN] franco.Kernel r391

I hate big OPs.

Works on all roms. r390 and newer versions are ONLY for 4.3.

F.A.Q:

1. My device rebooted or crashed, how can I help?

A: Get me /proc/last_kmsg on pastie.org.

2. Battery sucks, my device is not entering deep sleep. FIX PLOX!

A: Fix it yourself, it's an app waking your device up not the kernel's problem

3. Signal is dropping since I flashed the kernel, amg u sucks!

A: The kernel has nothing to do with gsm/cmda signal. Make sure you have the latest radios

4. Do I need to wipe anything when flashing this kernel?

A: No.

5. Does this kernel has X or Y mod?

A: Learn to read, everything you need to know is in the features list, changelog or public repo.

Downloads:

Changelog:

http://minooch.com/franciscofranco/G...htly-changelog

4.3:

Nightlies: http://minooch.com/franciscofranco/GalaxyNexus/JB/4.3/
[Samsung Galaxy Nexus] niamul:
Bigknowz, thank you for the link. Unfortunately my xda app wasn't showing me the link

Sent from my Galaxy
[Samsung Galaxy Nexus] franciscofranco:
Its just a problem on the permissions of the govetnor files. I will fix in the next update.

Ive been spending a lot of time with my GF and not reading emails, I think I have over 120 unread *gasp* but don't worry I will sweep over them soon, my GF is going somewhere for a few days soon ;)

Sent from my device
[Samsung Galaxy Nexus] manjunath.rp:
What is the best setting for longer battery life? Coz I can't re-charge while I'm at office.

Advance Thanks for your reply.

By the way I'm using Samsung Galaxy Nexus. Vannila 4.3 with Franco kernel.
[Samsung Galaxy Nexus] :
Installed r391 over 391 this afternoon, just perfect.

+ Battery life

+ Speed

Couldn't get PGM to work though, but thats okay :)

Thanks alot!

Rinse
[Samsung Galaxy Nexus] The Gingerbread Man:
Enjoy your vacation! I have spent this weekend at a cider festival and getting me some wheels :D
[Samsung Galaxy Nexus] UlbaWan-:
Great perf with the last r391 update ! I don't know why but I have always a better feeling with the franco's kernel than others kernels... Others are fast and stable too but this one have something more... I don't know !

Anyway, Thank you franciscofranco !
[Samsung Galaxy Nexus] orlans21:
will this work on PA 3.99 JB 4.3 on sgh-i747?
[Samsung Galaxy Nexus] kaluoshi:
What? :eek: This is Galaxy Nexus forum/thread :confused:
[Samsung Galaxy Nexus] marcusva79:
Anyone having any WiFi issues with 391?
[Samsung Galaxy Nexus] 15israellai:
Here we go again! Bro, check the forum

.

LOL @ 391 over 391.

but you're right, 391 is giving me quite some improvements.
[Samsung Galaxy Nexus] psyren:
Turn your phone off.
[Samsung Galaxy Nexus] orlans21:
sry i meant to delete my thread after realizing i was in the wrong section
[Samsung Galaxy Nexus] thegtfusion:
I guess you didn't read my post.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] Spoderman:
Hello, one quick question.

Franco Kernel Updater is bugged the hell out, right?

It shows my CPU temp as 1ºC (lol) and the GPU clock at 400mhz (it's supposed to show 512 if im correct...)

Idk.. i'll install r391-osmod now :D

Edit: I fixed the problem (lol im dumb) but still, the app should give us the CPU temp :/
[Samsung Galaxy Nexus] franciscofranco:
I think I forgot to add something in the Kernel to get the CPU temperature from this device.
[Samsung Galaxy Nexus] Spoderman:
Nice, im glad you didn't remove that feature for good :D
[Samsung Galaxy Nexus] franciscofranco:
Nah its been a crazy summer for me and sometimes I forget one or two things by mistake and since I dont use my Tuna for anything I tend to overlook easier.
[Samsung Galaxy Nexus] greyhd:
Which file of the four do we pick? Flash in recovery?
[Samsung Galaxy Nexus] YudmudTR:
When will we get PGM, or we dont?
[Samsung Galaxy Nexus] Suxsem:
Hello and thanks for your work!

I have a request for you. I'm stuck with a very stupid problem from days: GET (MHL) HDMI TO WORK IN POTRAIT MODE!

When i connect the mhl adapter, the phone automatically goes in landscape mode. If i force the potrait mode with some app the phone and TV go in potrait mode but on the TV the image is 90° rotated.

I want it to works like the galaxy s2, where in potrait mode the phone just adds black bars on the TV and the layout is in potrait mode and not rotated, as it should be.

This is what i mean:

GALAXY NEXUS (WRONG):

GALAXY S2 (CORRECT):

I am an android (apps) developer and i played with kernel source a bit but i'm not able to find a way for fix this bug.

maybe at google they think that this is not a bug, but i think that in home environment (when we can't just rotate the TV) mhl should work like the galaxy s2. sorry for the bad english... hope for reply, thanks!

---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------

quoting you just to be sure that you notice my previous post, sorry :p
[Samsung Galaxy Nexus] schleppy:
Hey Franco, I found a repeatable bug on my GNex (4.2.2 OEM rom, rooted, nightly #384).

I'm trying to update to the 390 kernel (which I now realize I can't use in 4.2.2). I head to the franco.Kernel updated section of your app (paid version), and I don't see 390. If I swipe the left drawer out and go to leankernel updater, the app crashes immediately. I can repeat the crash over and over too.

My /proc/kmesg doesn't appear to have anything in it...
[Samsung Galaxy Nexus] pkgnex:
r390, per the top line of the OP, is for 4.3 ONLY.

---------- Post added at 12:57 PM ---------- Previous post was at 12:54 PM ----------

Os,

Weird thing is, r391 is working perfectly for me (the non-os-fix version). Govenror selection, parameter changes, everything.

Is there a reason it would work for me and not everyone else?

I did notice that Franco has gradually reduced the boostpulse duration interactive parameter default over the last few releases (was 100000, then 80000, now 60000). Do you have any insight on the rationale for this? I'm not complaining, phone seems just as fast with slightly better battery life now, just wondering.
[Samsung Galaxy Nexus] bigknowz:
Which one

You have a choice to flash image or zip, 391 is 4.3, 384 is 4.2.2.
[Samsung Galaxy Nexus] ChazzMatt:
NO PGM questions, PLEASE!

You have to go ask the PGM developer that question. Franco has done his part, enabling the module PGM uses. Anything after that is the DEVELOPER of the app.

As long as the PGM developer keeps his app and source code closed, Franco nor any other kernel developer can NOT fix anything with PGM. Every time a kernel is updated, the PGM developer has to update HIS app. It's the PGM developer at fault, NOT the kernel developer (as long as the correct module is enabled, which it is.)

So, STOP asking about PGM in this kernel thread. Go bug the PGM developer. :rolleyes:

This is not directed just at you, it is for all people who ask PGM questions in the wrong places. PLEASE leave us alone with the stupid PGM.

And THIS was posted just a couple page back, so you should know better...
[Samsung Galaxy Nexus] osm0sis:
As far as I know we aren't even using boost pulse. That said, Francisco did change it in the source on another device to match the original math by Google in the code for calculating it (based on timer_rate or something).