yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] The Gingerbread Man:
Spend a couple of dollars to support Franco and purchase the app then join the beta channel and update play store version and find the option and long press to set on on boot, probably costs you less than an hours wage or make a script for free
[Nexus 5 Original Android Development] nexusmaniac:
Franco, are you thinking of changing the font in fku to match the new roboto font in KitKat? (Just asking not requesting :) )
[Nexus 5 Original Android Development] Carbon Trooper:
Franco, this is sorcery. You possess magical powers.

The color calibration on this kernel is phenomenal, just bought the FKU app from the play store. Thanks :highfive:

One question, if I get an OTA update, should I flash a stock kernel, update via stock rooted ROM, and then reflash your kernel?

PS, sorry if this was mentioned before. 200+ pages are a pain to go through.
[Nexus 5 Original Android Development] davy917:
You can do it manually like any other kernel via or get the FKU app, or a free tweak app like Trickster if you don't want to buy yet. Not sure whether or not Trickster will show this function but it usually covers most of the bases.
[Nexus 5 Original Android Development] franciscofranco:
Of course:

echo X > /sys/class/timed_output/vibrator/amp

Or use an app that supports that.

I thought for a while where would be the best place to use the Roboto Condensed (its not new at all, its been on Android since 4.0 AFAIK), but I didn't find any place where the font fit on my app.

:)

Depends, you only need to go back to stock boot.img if an OTA wants to flash an update Kernel or the same for other partitions that have been changed by you or something else. Best thing to do before an OTA is flash back to stock boot.img and stock system.img, all your apps will be intact.
[Nexus 5 Original Android Development] SpOuK-3-:
Well, we know what's in the kernel... We are following franco since the Nexus S I think...

All you have to know is... Flash it :)
[Nexus 5 Original Android Development] GNEXc:
Hey Franco, a little suggestion.. Would you mind adding the range we can set for the audio on your app? E.g. (0-20) or (0-15) .. Want to avoid entering a too small or too big a number. Tks
[Nexus 5 Original Android Development] the1dynasty:
Thanks for the reply... I shared my initial thoughts of this kernel and tagged you on G+... I'm totally new to your kernel and I'm liking how it has my phone feeling... But there is a trial period with anything new for me and then I'm all in... I'll buy the app in a few days when I decide if I'm gonna stay with this kernel or not... The 15min window doesn't allow enough time to really see how something like this will work out...

I have another issue/question... I'm getting Play Services FC'ing when trying to view photospheres on G+... I never had this issue with stock kernel... So I'm trying to figure out if its something I can fix on my end or wait for an update for this kernel... I do have ART turned on and haven't had issues like this before...

I've wiped data on everything I can think of and nothing seems to help... Thanks for any help!! Just wondering if this has already come up or not... If you need a log, let me know and I'll try to get you one ASAP...
[Nexus 5 Original Android Development] franciscofranco:
Long press - read the description.

Nothing to do with the Kernel.

Don't use ART.
[Nexus 5 Original Android Development] alanwyl:
[MENTION=3292224]franciscofranco[/MENTION]

Could you include this for the sake of readability of the change log?

http://pastie.org/pastes/8486107/text

and

<?xml-stylesheet type="text/xsl" href="./changelog.xsl" ?>

in the xml
[Nexus 5 Original Android Development] franciscofranco:
I mean, will that affect the way my XML Parser on the app reads the changelog.xml? That's the whole point of having a .xml file instead of a plain text file.
[Nexus 5 Original Android Development] psp9000333:
managed to get this with heavy usage at the 8 hour mark.

I know it doesn't show anything, but trust me, I did play some games.
[Nexus 5 Original Android Development] aeroseek:
It seems to occur with or without slight uv. I just happened to be uv this time around.
[Nexus 5 Original Android Development] TJKV:
Okay I have responded inline again with my suggestions. Hint: follow the links to the logcat and last_kmsg :)
[Nexus 5 Original Android Development] PetritH:
I thought Franco fixed it on r44
[Nexus 5 Original Android Development] Tzfardaya:
True, but since we know that there are issues with the kernel, don't undervolt and confuse the situation further... Since we can't tell if your sod was caused by the UV or the kernel glitch it may just get snarked or ignored... ...
[Nexus 5 Original Android Development] wendiko:
Every time I reboot it comes back to stock no matter what I wait.

I was using vomer init.d before just erased the /etc/init.d file.

What should I do?
[Nexus 5 Original Android Development] aeroseek:
yep I've removed it
[Nexus 5 Original Android Development] Tzfardaya:
By deleting the script in the init.d folder, you no longer have anything setting your options on boot... So you need to use the fku toggle for each option your changing.. (or put another script to do the same back in the init.d folder)

---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------

That's why I don't set voltages for reboot... I know what works and it's not hard to set them manually... If I spend the time to dial them in better, I'll have to put the values in a script to run instead...
[Nexus 5 Original Android Development] franciscofranco:
Well I'm trying to figure out the cause by reverting some patches at a time.
[Nexus 5 Original Android Development] wendiko:
---------- Post added at 08:40

I see but if I manually set the values in each toggle wasn't it supposed to stick when I reboot? I'm ticking the box to do that. Looks like it's not saving what I am doing and always go back to default
[Nexus 5 Original Android Development] thucoisao:
i'm running Mahdi Apr 9 build, lastest Franco's kernel, walkman player (ported from Z2), V4A, volume as 50% and mp3 files. please help.
[Nexus 5 Original Android Development] chikimonke:
Thanks for testing. The audio bug portion was setup to only go to that page when selected, but something must have gotten borked when I was playing around with stuff. Franco has also mentioned that he doesn't need certain information, so some of these fields will be removed too. The thoughts that I have for this keep getting bigger in my head and I feel like I'm quickly reaching the end of my knowledge ?
[Nexus 5 Original Android Development] thucoisao:
i was did a clean flash.
[Nexus 5 Original Android Development] Technecium:
[MENTION=3292224]franciscofranco[/MENTION] .. you may recall the cpu spike during long audio playback times, 6 hrs @ 300mhz and 1-2 hrs @ 1+ghz.

I mentioned it had returned after you rebased. Because of the spike I had been using r35 but decided to test r44 today.

Just letting you know it no longer happens on r44.

Great work!
[Nexus 5 Original Android Development] venelar:
Can someone recommend a good per app mode setting for gaming? Getting some lag on riptide gp2 with the new r44 (but hey, no sod!)
[Nexus 5 Original Android Development] blackrobin88:
Is it me or r 44 not as buttery as r39
[Nexus 5 Original Android Development] eak1080:
Holy #%@& Franco, are you bored at work this week or something...?

?

My N5
[Nexus 5 Original Android Development] franciscofranco:
Decrease max cpu freq to around 1,5GHz and increase thermal throttle point to 70.

Just you.

Android is my work.
[Nexus 5 Original Android Development] laureanop:
SOD on 44 . No undervolt, hot plug at 10. Here's the logs

https://www.dropbox.com/s/684a1acirtp2ffg/2014-04-10_21.23.zip

---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------

Man, other than the occasional SOD, 44 is a beauty performance and battery wise
[Nexus 5 Original Android Development] blueren:
Franco - The most stable kernel was actually the one which u re-based. r3x something :P It was uber smooth and had a very awesome batt life. Sometimes I wonder.. all these patches you merge, do they have a huge noticeable difference? It all seems fine when u stack up a few patches at a time, then it comes crashing down with a single bad patch. :( All of r4x series are plagued with sod. Trying r44 now :good:
[Nexus 5 Original Android Development] franciscofranco:
Its ok, gotta play a little to see the results.
[Nexus 5 Original Android Development] TJKV:
I know what you mean! Would love to learn all there is to learn out there, from scripting to web centric languages to C and Java etc but no time :/

For SlimKat ROM and USB OTG users using stickmount:

Incidentally, I have just made a script that automatically adds these changes into franco's ramdisk for use with SlimKat. Purpose is to automatically mount OTG drives and make them visible in Settings->Storage. This is integrated into SlimKat's kernel but requires a ramdisk edit from that commit in other kernels. This means we don't need stickmount etc to mount supported partitions. But NTFS still requires stickmount, the ROM doesn't include ntfs-3g unfortunately.

Is anyone interested in this? Keep in mind I don't know any scripting, I just looked at some perl script and mashed at my keyboard till it worked. Not a prettied up process but works, modified boot.img boots fine. Will share it here if someone wants this. (Runs on linux)
[Nexus 5 Original Android Development] big_adventure:
Good plan, that last part.
[Nexus 5 Original Android Development] Akath19:
As long as what Franco wants isn't very difficult and you reach the "end of your knowledge" (although I think a person's knowledge is endless), I can write a small webapp that'll fulfill all your requirements.

Send me a PM if you want with the details, I've been wanting a small programming project for a while, management is so f{}€¢[€÷<£<; boring!!!!
[Nexus 5 Original Android Development] big_adventure:
Well, AAC offers two advantages over MP3: it is much more efficient per bitrate than the much-older, designed-by-comittee MP3 standard (so 128kbps AAC captures nearly as much detail as 256kbps MP3), and MP3 is artificially capped at 16khz, so if your music has frequencies over that and if your headphones (and ears) can support it, the signal is zero'd above that. OK, to be fair, humans, though theoretically capable of processing up to around 20khz, mostly don't do so all that well, so this isn't necessarily a huge deal, but it is real.
[Nexus 5 Original Android Development] RobbieL811:
Yeah. I'm interested. I would like to mess around with it a little bit. Do you already have a boot.img built with the changes included? That would be awesome. Sometimes I use Kecinzers boot.img from his AOKPK ROM which is FK but he adds auto OTG mount. Send me a link please.

Sent from my Nexus 5
[Nexus 5 Original Android Development] MBQ_:
Nice to an 'in the groove' Franco doin' what he does best.

Good job across the board man.

Respected kernel and app developer, answerer of questions, a prominent figure on Google Plus, and an extremely respected member of [and on] XDA
[Nexus 5 Original Android Development] KuChar_:
Just got SoD on r44 :(

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] Wenzo2:
:'( log?
[Nexus 5 Original Android Development] P.Mobile:
yea i just got it also.. first time since i flashed r44.. have to be up in a few hours.. will post a log tomarrow.. nite all!
[Nexus 5 Original Android Development] TJKV:
Okay grab the mkbootimg from here and put it in ~/bin and do a "chmod +x mkbootimg" to it.

Then use the attached stuff to do the editing on a boot.img. Needs to be called boot.img ONLY, just move it into the folder and run the perl script by doing "perl modify.pl". You will get a file "newboot.img" that you can use.

Like I said not pretty at all, no error catching etc. But I just did it on r44, works fine. I don't want to upload the actual boot.img though, prefer it if people modify it themselves from the kernel downloaded from franco's server.
[Nexus 5 Original Android Development] RobbieL811:
OK. I'll try to mess around with it some tomorrow night. I might PM you if I have some questions if that's ok. It's like 2:30 am here on the east coast US & I gotta be up at 6:00 to go to work. Lol.

Sent from my Nexus 5
[Nexus 5 Original Android Development] TJKV:
Yeah sure no problem. If you know scripting then feel free to make it better etc.
[Nexus 5 Original Android Development] baedaa:
Logs seem to be useless in this case otherwise the problem could have already been located
[Nexus 5 Original Android Development] shinesthru:
What this thread needs:

http://goo.gl/AV3rIk
[Nexus 5 Original Android Development] GtrCraft:
You have clearly no idea how this works
[Nexus 5 Original Android Development] stocaprimo:
I'll stick with r38 for a while... :\
[Nexus 5 Original Android Development] daniel84cs:
SOD on R44 revert to R38 for now.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Ladaga:
r38 is the last stable version...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] granets:
What do you guys do to get SOD's. I have not had any problems. Can you please tell me what you do, so I can replicate?
[Nexus 5 Original Android Development] gee2012:
If users knew what triggered the SoD they would avoid it ;) I think its not only the kernel causing the issue but maybe a conflict with other installed software like custom frameworks and its modules, maybe kernel patches (dalvik, bionic, linaro etc) or maybe OV/UC settings. Who knows. Its funny that not all users suffer from this issue.
[Nexus 5 Original Android Development] castaway1:
i think all users are affected but SoD is appear too random. Even franco had one.
[Nexus 5 Original Android Development] kecinzer:
I had SOD too already.
[Nexus 5 Original Android Development] hello00:
yup same here
[Nexus 5 Original Android Development] alcurtis93:
I keep getting them all the time. Leave my phone a few minutes and try to turn it on and it's dead. Have to keep holding the power button until it eventually reboots. Going to stock kernel for now
[Nexus 5 Original Android Development] nldxda:
Sod on r44

Stock ROM, xposed, updated GPU drivers, no changes to kernel settings

Spoiler content hidden.
[Nexus 5 Original Android Development] baedaa:
yep, because it's the 9000th person that got the information is his log franco needs.

enlighten me, grand wizard
[Nexus 5 Original Android Development] Ben36:
I've never had SOD. Lol
[Nexus 5 Original Android Development] fredfox_uk:
Me neither :) over 4 days up time on R40.
[Nexus 5 Original Android Development] arbi97:
Have one SoD ( Only on r43 ) and that's all! Don't know, how you get it 2-3 times and more!

Use -50mV, Vibration 75 and some audio settings, gamma profile and that's all!!

P.S Sorry for my bad English!!
[Nexus 5 Original Android Development] laureanop:
I thought it could be user error so I went back to my favorite 32 and no SOD. Then I went back to 39-43 and I got SOD within 5 hours. Then I flashed latest Bricked with positive results. Today I flashed 44 and I got an SOD fairly quickly. I think there's enough logs that we can figure out what's causing this issue.
[Nexus 5 Original Android Development] The Gingerbread Man:
If raising your minimum CPU speed doesnt work I don't know what to suggest.
[Nexus 5 Original Android Development] sirovai:
Wow, SoD everywhere...

Sure Franco will fix theme!
[Nexus 5 Original Android Development] Momotani-Hitoshi:
[MENTION=3292224]franciscofranco[/MENTION]

Are there any plans for encryption support/fix in future franco kernels? R32 was the last version to work. I know you don't encrypt your device so it be difficult to find a solution. Been posting kmsg logs of new releases, but not sure if its useful to you or just creating forum post noise. Wondering if I should keep waiting, stick with R32 until next android update or just move on back to stock.
[Nexus 5 Original Android Development] neobuddy89:
[MENTION=3292224]franciscofranco[/MENTION],

SOD may be result of following commits, revert these:

https://github.com/franciscofranco/hammerhead/commit/fc2bc63fca7f5d9f85d47219fcf3ba8f67cf35ee

https://github.com/franciscofranco/hammerhead/commit/534fc557bbb7a00783e98070651e6a46875620f3

https://github.com/franciscofranco/hammerhead/commit/cb6aa8ccaf49571446f422ddb6dc3b6e0612556a

Had issue with these and seems like CAF kernel is not yet ready for these backports or needs more fixes.
[Nexus 5 Original Android Development] icethegreat:
Delete

edit: i seriously need coffee
[Nexus 5 Original Android Development] icethegreat:
Just got a SOD with r44. On stock kernel settings and latest Purity. Hope this helps.

Additionally, I was on instagram loading a video when it went bonkers and FC. I put the phone down and hit the power button. Minutes later I pick up again and would not wake...

https://docs.google.com/file/d/0B0sQ_20IROYcZ1BwWnh5UEc5Szg/edit?usp=docslist_api
[Nexus 5 Original Android Development] gparmar76:
Its crazy...I haven't gotten a single SOD on any of the latest kernels...and I tried all of them...I do use all stock settings though...only things I change are the audio options and screen color profiles...the audio clipping issue seems to be gone in r44 so things look good so far.
[Nexus 5 Original Android Development] granets:
A good find. I did speculate that there could be something CAF related, because after Francisco added CAF commits again, problems started rising surfacing.
[Nexus 5 Original Android Development] hellsgod:
These commits aren't from CAF. I'm using these in my project, too and no SOD occured since then.

hells
[Nexus 5 Original Android Development] big_adventure:
What were you doing when it happened? Did you lock the screen manually? Did it time out? How long was it off when you tried to click it back on? For how long did you try to click it back on? It looks like you tried plugging it in - did that do anything (doubt it, since you still hard rebooted)?

Sorry - my bad, you edited as I was writing. I can see the video start in the log. Thanks for the details. Did you try plugging it in, as I stated?
[Nexus 5 Original Android Development] icethegreat:
Yea, i added some info on my original post. Instagram f/c on me, i put it to sleep, about 3 mins later when i went to wake it up it would not wake. i tried plugging it in a couple times to try and wake it but nothing.
[Nexus 5 Original Android Development] Koragg618:
Wow nice to see another FRC member here; Team 1325 says hi!

Sorry for OT
[Nexus 5 Original Android Development] neobuddy89:
Apologies, if I am not clear.

These commits are not from CAF.

They are backported from 3.14 mainline kernel to help with SMP/hotplug operations.

However, seems that this backport may have a conflicting patch in our source or not ready due to any other missing patch.

I reverted these and SOD was completely fixed. Best is to give a try instead of making claims. :good:
[Nexus 5 Original Android Development] akaHardison:
Back to here.Finally franco take seriously on Screen on delay.It bother me all the time since using your kernel.(Bricked old version has this problem too.)
[Nexus 5 Original Android Development] big_adventure:
[MENTION=528371]icethegreat[/MENTION]

You wake the phone up at 6652.

There is some wireless comms, then your video starts at 6718.

You plug in power at 6804.

At 7091, you go screen off.

Between 7126 and 7440, you can see the battery charge up to 85 (max17048 is the fuel gauge)

It looks like it tries to exit suspend a couple of times, but puts itself straight back into suspend. It never tries to activate the touch panel or the backlight, and never logs a normal resume event:

[ 7457.124541] dhd_set_suspend: Remove extra suspend setting

[ 7458.700504] dhd_set_suspend: force extra Suspend setting

[ 7458.711106] dhd_get_suspend_bcn_li_dtim beacon=100 bcn_li_dtim=3 DTIM=1 Listen=10

[ 7459.515698] dhd_set_suspend: Remove extra suspend setting

[ 7461.180133] dhd_set_suspend: force extra Suspend setting

[ 7461.199214] dhd_get_suspend_bcn_li_dtim beacon=100 bcn_li_dtim=3 DTIM=1 Listen=10

Here is what a successful resume (and then a suspend) should look like :

<6>[ 204.635592] active wakeup source: event0-775

<6>[ 204.635612] active wakeup source: alarm_rtc

<3>[ 204.635623] PM: Some devices failed to suspend

<6>[ 204.710286] PM: resume of devices complete after 74.650 msecs

<4>[ 204.712611] Restarting tasks ... done.

<6>[ 204.733069] PM: suspend exit 2014-04-07 10:18:07.147796655 UTC

<6>[ 204.787134] [Touch] touch on

<6>[ 204.787954] mako_hotplug: resume

<4>[ 204.798215] dhd_set_suspend: Remove extra suspend setting

<6>[ 204.937282] max17048_work: rsoc=0xB4C6 rvcell=0x0CFF soc=93 v_mv=4158 i_ua=232891 t=263

<6>[ 204.983280] mdss_dsi_panel_on

<6>[ 205.203798] lm3630_backlight_on

<6>[ 206.173464] bcm2079x 0-0077: 10,62

<6>[ 208.080057] slim_clk_pause: data channel active

<6>[ 220.109907] slim_clk_pause: data channel active

<6>[ 230.140061] slim_clk_pause: data channel active

<6>[ 232.703024] lm3630_backlight_off

<6>[ 232.777213] mako_hotplug: suspend

<4>[ 232.783350] dhd_set_suspend: force extra Suspend setting

<4>[ 232.802216] dhd_get_suspend_bcn_li_dtim beacon=100 bcn_li_dtim=2 DTIM=3 Listen=10

<6>[ 232.934600] mdss_dsi_panel_off:

<6>[ 232.957187] [Touch] touch off

That came from my dmesg - you can see the wakeup event, the tasks start, all kinds of stuff. You can also some data, then the you can see me manually go back to screen off. I highlighted the dhd suspend stuff for clarity.

After that, your charger flip-flops a bit.

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

I analyzed it for you above - basically, the kernel logs shows nothing particularly useful (to me) except, perhaps, the absence of restart events.
[Nexus 5 Original Android Development] doomed151:
Hello guys, I've been wanting to use franco.Kernel as my daily driver but there's something that keeps making me go back to ElementalX. It seems that the interactive governor doesn't sustain max cpu frequency during continuous heavy load.

I usually test by playing back a Hi10P video (1920x1080, 24 fps, FLAC audio) using MX Player (RGB 16-bit color format, Use speedup tricks checked). Here's the result with franco.Kernel (2.42 GHz max freq):

The playback is smooth for a second (where most of the cores sit at max frequency, probably because of touch boost) then gets very choppy shortly after. About CPU 3 and CPU 4 having low usage, I don't know.

Now let's take a look at ElementalX (2.49 GHz max freq):

Notice that 3 of the cores actually stay at max frequency. Video plays smoothly with only a few dropped frames here and there.

So is there somehow a way to configure the governor so that it behaves like elementalx? Thanks in advance.

EDIT: Found the issue! The culprit was thermal throttling. I raised it to 80 and everything runs good.
[Nexus 5 Original Android Development] EarlZ:
I've been getting a lot of SOD on V44
[Nexus 5 Original Android Development] Technecium:
I stand corrected, it still happens :{
[Nexus 5 Original Android Development] big_adventure:
I had a headache once. Franco, make it better!

Seriously - do you want to maybe add a little here? What you were doing, what is your configuration, can you recreate them, etc.?
[Nexus 5 Original Android Development] EarlZ:
Whatever is the stock v44 configuration, I didnt change anything aside from color control. Phone was not used.. Got an SMS.. SOD but LED kept blinking..
[Nexus 5 Original Android Development] tcat007:
No SOD here, tried every update at least 24 hours. Flashing Purity 4/6, Banks minimal 4/11, and Franco r44 now to see if I can get one. Maybe it's the fact I don't use phone data, I only use Wi-Fi.
[Nexus 5 Original Android Development] coolnow:
Got my first SOD on this phone this morning. Was on r42 and went to sleep. Woke up with alarm ringing, WhatsApp notification LED flashing and screen not turning on. Nothing changed, no undervolt, no colour control, no volume boost, no vibration adjustment (was too tired to tweak it after a long day out) and running on Dalvik without Xposed. My rom is the latest version of PA.