yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Zephyr101:
To be quite honest;

It was third period as a freshman in high school, being done with all of my work in pre-ap geometry, they allowed us to use our phones, having no other schoolwork to do, I got on my phone, upon turning the phone on, I remembered, that class is a dead zone for T-mobile, no HSPA+ much less LTE, and our school WiFi sucks when everyone is using it. I decided, I might as well update TWRP, because I for one, like to have everything updated, and I still had the .img file in my downloads, so I recalled how I flashed r33, by using your FKU app, and though, "Lol, y not?" and proceeded to tap auto-flash, the message then showed "enjoy your new kernel" I rebooted, only to find myself in a orange TWRP recovery, I thought it was weird and just ignored it, then I rebooted system and kept coming up to the same screen, so, naturally, in my attempt to fix it, I did a factory reset, and then rebooted only to find myself in that orange screen again, so then I did an advanced wipe to wipe EVERYTHING, cause I don't have common sense, halfway through the wipe I remembered, 'I HAVE A r32 ZIP IN MY DOWNLOADS, I JUST GOTTA INSTALL IT" and then I stared at my screen in shock, for I knew I was screwed and probably was gonna have to go back to stock. Either way, yeah, that's about it. I went through the rest of the day without my phone, and tomorrow I have a competition and so I needed to have my phone for that, and I was freaking out because I paid for this phone on my own and I was not about to let it get ruined by a simple mistake, so I went and proceeded to restore the factory image for the Nexus 5, and now I have everything back, and even updated TWRP in the process.

So yeah, that's the story, and well, yeah. Freshman here, hope you enjoyed this long story of how I messed up and continued to mess up to the point of having to restore the factory image. :silly:
[Nexus 5 Original Android Development] vomer:
Holy formatting batman....TL;DR :silly:
[Nexus 5 Original Android Development] Zephyr101:
I know! Long story :p
[Nexus 5 Original Android Development] jd1639:
I'm not going to quote zepher101, but what the? This is a development thread not story telling time.
[Nexus 5 Original Android Development] thegtfusion:
the last pages are about the app. -.- , read!

and yes there is an app. search in the play store : franco kernel updater.
[Nexus 5 Original Android Development] drdrewdown:
seriously? :o
[Nexus 5 Original Android Development] w0nder:
Last pages are only about updating kernel and bricking phone with FKU. I was driving my car sorry about that i have not enough time to read the last few pages

FKU is already usable for 4.4? Because APP discription only says 4.3
[Nexus 5 Original Android Development] franciscofranco:
Weird, it works for me, and I sent it to Jason, he observed no issues. I'll push r11 today which behaves correctly on the thermal front.

I usually don't stop support for Nexus devices unless its physically impossible for me. I'm just waiting for 4.4 Kernel sources to push updated FK for the other nexus.

Its normal that two cores are online, but its not entirely normal to see freqs jumping around like that unless you have some app doing background work like listening to some Spotify etc.

Multicast filtering was not set after all from what I read in the source.

I'm sorry about your issue, but its entirely your fault. You never saw me say that the current FKU would work correctly with the N5. I said the beta FKU works. Hope you find the fix.

No.

Well... I see what you mean, but I'm not really the guy that cares about that 6500k gamma thingy. If it looks good to my eyes that's what I'm gonna use, even if its not perfect Gamma. Although this was just a small change, everything will be configurable when I decode the gamma thing entirely.

I have not added yet to the beta FKU. Although I cgollner sent me the package yesterday and I'm gonna merge it back today.

You cannot, I never said there was color control interface -.-

1 - Speaker -> dunno, don't care much. Headphones -> yes

2 - You gotta search, I cannot advertise my app.

No it won't brick your phone if you use the proper beta FKU. I never said the current production app would work with the N5, why people don't read?

All LED work is stock on FK, something else derped and it wasn't the Kernel.

1 - If app drawer name is FKU then you're using the correct beta version.

2 - Not yet, next beta update will tell you that.

3 - Most options is to long press and tick the checkbox.

You're using the beta app, you can auto-flash just fine.

I can't post app stuff on the OP, its against the rules and I'll get banned. There is nothing I can add to the OP that will help others. Simple instructions in the OP are: flash through the bootloader or flash through the recovery, how hard is that? If people cannot comply to that simple instructions then they should not be here.

How is that Kernel related?

No - did you see me posting that it was compatible?

Your derp, it sleeps just fine.

I never exposed readahead in the app. Default is 512kb.

Thanks for the feedback. I just need more time to fiddle with the gamma tables.

Don't use this with CM for now, they are doing their shít once again.
[Nexus 5 Original Android Development] franciscofranco:
Simple, if it says 4.3 then its only for 4.3. It will be updated very soon, I'm not a machine, unfortunately I gotta sleep and eat :p
[Nexus 5 Original Android Development] donkeyhitman:
I guess that I'm the only one who doesn't like the new colour calibration in r10. It's kind cool (bluish) to me. Is there a way to still have r10 butkeep the stock colour?
[Nexus 5 Original Android Development] franciscofranco:
No, its hardcoded.
[Nexus 5 Original Android Development] bleuxeon:
Regarding color management, I wich we could have control over RVB values at different level of grey scale. (typically 10)

Then I could probably release calibrated values for you to use on your device using my semi-proffessional calibration colorimeter : i1Display Pro

Theoretically color calibration should be processed per device, as each screen reacts differently.

But it would at least offer a much more accurate color correction than anything done by eye, and would lower overall deltaE.

But I even don't know if we have hardware control on the NEXUS 5 over those RGB values.
[Nexus 5 Original Android Development] zephiK:
Franco is working on it. He sent a email to LG yesterday to decode things related to the colors. Hoping for a response. You'll have access to them but it'll just take time, Franco only put the hard coded code for color changes. He didn't have to, but did. I appreciate them.

People need to understand that these things aren't done over night and Franco kernel is a work in progress. There's no need to request a feature or whatnot because he is already on it.

I'm not sure if you're new to Nexus devices or whatnot. But we've always had color control to control every aspect of colors including rgb gamma brightness etc. It's just going to take time. Just be patient and it'll all work out. Franco has already got a lot done in a short matter of time.

Sounds like you need an intern to get you food and energy drinks / coffee, any volunteers? :p
[Nexus 5 Original Android Development] sluflyer06:
For those of you looking through crazy # of pages to find things, you know you can change the posts per page. This entire thread is only 34 pages on my settings.

r10 is rockin btw.
[Nexus 5 Original Android Development] USHERROB:
You should be able to get phone to -75mv :) i have had luck setting that globally w/o reboots. Mines tweaked further though for testing :D
[Nexus 5 Original Android Development] franciscofranco:
Sure that all sounds very pretty, but we don't know what each gamma value represents in the table. Currently (I can be entirely wrong) its something like this:

panel-commands:

* around 7 or 8 different commands

* each command holds a bunch of bits, each hexdecimal value holds 4 bits, and theres roughly 36ish hex values in each command

* each command has an upper gamma level and a low gamma level

* AFAIK the upper 10-12 hexes are the upper, and the remaining hexex are the lower

* there's also a white point somewhere in the first commands (don't remember from the top of my head)

Most of this is assumptions based on some debugging (injecting values to the gamma tables from the userspace) and reading LGE commits to the panel device tree file and I can absolutely be wrong in some of those assumptions.

This is what I decoded so far. Kernel interface is dead easy to do, problem is figuring out what each value does through experiencing. I can push a simple gamma interface in the next update and leave it up to you users to figure out what each value means.
[Nexus 5 Original Android Development] Alfonso87:
Franco, guys, do you think i should wait some days to flash this kernel? I got my N5 yesterday :p i have made just 1 charging cicle :D
[Nexus 5 Original Android Development] theesotericone:
Two heads are often better than one. In this case I'm sure their will be hundreds of heads. Might be a really good way to go about it. With the usual disclaimer of please don't cry if your phone looks like crap because you played with it of course.
[Nexus 5 Original Android Development] catpunt:
Thanks for all your work, I love your kernels and I hope I wasn't coming across as accusatory, I do realize it was my own fault. I program firmware for consumer hardware at work so I am well aware of the risks.
[Nexus 5 Original Android Development] RTNDO128:
You're quite the asshat, aren't you? That zip is used to replace the AOSP dialer with the "Google Experience" one. It wasn't made as a fix for Franco's kernel.
[Nexus 5 Original Android Development] Audioboxer:
Is r10 running with some screen improvements? Not ran any of the official builds (only test builds) and either my screen looks much better or placebo effect is in place.
[Nexus 5 Original Android Development] :
You don't know what we were talking about, but never mind.

I'm not starting anything here.
[Nexus 5 Original Android Development] eep2378:
Do you mean color looks better(more white, less yellow), when you say screen improvements? If so, yes, Franco hardcoded some values in r10 to adjust/improve on color temperature.
[Nexus 5 Original Android Development] RTNDO128:
You're right, I have no idea. I posted in this thread stating that Franco's kernel wasn't working with an unofficial CM build. You give me a smartass response telling me to read, and that "It's a known bug and a flashable zip exists". This alleged fix you link to was to replace the AOSP dialer in m3dd0g's build with the Google Experience dialer. So please, fill me in.
[Nexus 5 Original Android Development] Tzfardaya:
should have read it... it was a comedy of errors... each mistake compounded on the last.. :P

I've done similar... forgot which device thread I was in, downloaded the latest kernel from that thread, then proceeded to install it on the wrong phone...

and since it wasn't a nexus, it wasn't quite as easy to recover from....

---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------

well, if franciscofranco asks for a story, I see no reason he shouldn't be indulged... :P
[Nexus 5 Original Android Development] PresidentMcCain:
Just had a HW_RESET (reboot) occur while the phone was in the pocket the whole time.

last_kmsg: http://pastebin.com/TBAcwppf
[Nexus 5 Original Android Development] salomaoa:
I'm facing a weird problem. Everytime I change the kernel settings, after a reboot I get a message in statusbar - acesso restrito modificado - (in english that would be something like "modified restricted access") and I found that kernel settings are reset to default.

What could be wrong with my phone?

BTW, I'm running cataclysm ROM

Salomao

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] jd1639:
Log cat or it didn't happen
[Nexus 5 Original Android Development] PresidentMcCain:
Ninja'd
[Nexus 5 Original Android Development] omvir:
11h 30m device up time, 2h 30m SOT, and 63% left. 1h of music. Wifi, LTE mix. Locations off. Lots of syncing. Loving r33.
[Nexus 5 Original Android Development] HenryDCase:
Thank you Franco, Gingerbread, and Vomer! R33 latest, 3g and wifi, location battery saving, UV 300@650/-25 the rest, and today I am highly impressed with my battery.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Andypandiiee:
How do u make the fku settings stay after reboot?
[Nexus 5 Original Android Development] Savant:
There is a little bookmark to set on boot but it'll help if you read the little tutorial fku gave you or being part of the beta program.
[Nexus 5 Original Android Development] franciscofranco:
Argh I'm gonna have to write a lot. So CAF/Qualcomm are finally moving to the Linux Kernel/ARM standards and they are slowly changing their trees. First they moved KGSL to devfreq, but I did not merge that because devfreq KGSL governors kinda suck so far and I started to lose frames and games were laggy too. Then they moved the CPU tables and Krait clocks to DTS (device trees) and therefore had to adapt a lot of their code. I did not follow that as well (of course tested it). This patch you posted is just moving the CPU/BW realted code to DTS and its logic, but there's actually no change in functionality per se.

Well... its a Kernel manager, its not meant for recoveries... obviously. You learned your lesson.

Yikes, there's no error log or panic log. It seems your hardware thought it would be a good time to reset :)
[Nexus 5 Original Android Development] Pete182:
I'd like to know if that's possible as well. I've just been backing up and restoring settings after rebooting
[Nexus 5 Original Android Development] franciscofranco:
Tick the "phone" icon in the option you want to set on boot. Kinda straightforward...
[Nexus 5 Original Android Development] JNewms:
Seriously? There is a big button next to each setting. Clicking it sets options on boot.
[Nexus 5 Original Android Development] david279:
So the default values for each property in the app are custom values or they come from the app. I just purchased the app and was wondering if those are the optimal values or just coming from the kernel. Great kernel BTW.

---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
[Nexus 5 Original Android Development] RobbieL811:
Those are the flash & forget settings. Unless you know a lot about tuning the kernel, they are probably the best settings for you. You can try to mess around with them some. Just make sure not to set them on boot until you are sure that they work good.

Sent from my Nexus 7
[Nexus 5 Original Android Development] dark_ente:
I know the feeling man, sometimes I make one stupid mistake after another, and the end result is end up with a dead phone/laptop for another two days.

The last time I remember using truecrypt to encrypt the whole hard drive, then I update my graphic cards using windows update, even though I know that it can cause bootloops.

Then bam! boot looped. Normally I'll go to recovery and using system restore to restore everything... but then truecrypt prevent windows from detecting my hard drive! I know I was fúcked! Then I have to create a bootable DOS USB, install truecrypt there to decrypt my hard drive which takes half a day. After that I run system restore, restore windows to one day earlier... you know the rest.

Some times a small mistake can cost you minimum a day or two. I was lucky I could decrypt my HDD in DOS. If my laptop couldn't boot with usb drive then I'll have no choice but format the HDD and start anew.
[Nexus 5 Original Android Development] GeekMcLeod:
If I'm not mistaken, when you first use the FKU app, it shows you what set on boot is.

Posted from under your bed.
[Nexus 5 Original Android Development] dark_ente:
Maybe you should make a fail-safe function to check if the img file is really a kernel, or anything with twrp or cwm or is a no go!
[Nexus 5 Original Android Development] HenryDCase:
Why? It's simple. PEBKAC.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
No.

Besides both recovery and kernel headers are the same so I can't even differentiate between both. I really don't care, it doesn't say anywhere about any damn recovery flash.
[Nexus 5 Original Android Development] marcusva79:
Probably an insanely re-tard question that will ruin civilization! Anyone have a link for the gamma settings that everyone put together and what is suggested to be the best? Sup Franco! Great work bro ::high five::
[Nexus 5 Original Android Development] GeekMcLeod:
Color profiles? Franco has them all in his app.

Or if that's only for beta still, vomers sig.

If I misunderstood, sorry.

Posted from under your bed.
[Nexus 5 Original Android Development] marcusva79:
If it is in app I have to buy it again. My old email got hacked from retarded target scam and had to set up a new one. I know you can't transfer it bought apps. Sux.
[Nexus 5 Original Android Development] omvir:
Wow the battery life on r33 is ridiculous.....

-Ly awesome!

I should have about 25 percent remaining at this time. But I have 41!
[Nexus 5 Original Android Development] :
Any battery saving tips? Getting terrible battery life...
[Nexus 5 Original Android Development] RobbieL811:
I am too bud. Idk what the heck I'm doing wrong! I have everything set up right & I'm not even getting 3 hr's screen on time! I just got a new warranty replacement yesterday & it's nowhere near the same as my old phone!

Sent from my Nexus 5
[Nexus 5 Original Android Development] neriamarillo:
What rom are you using? I'm getting awesome battery life. I'm using almost stock settings and on latest r33. Check for rouge apps that may be keeping your phone awake or a process keeping the CPU load high.
[Nexus 5 Original Android Development] RobbieL811:
Idk any way to check the CPU load but I am running Slim. Have all the bells & whistles switched to off. No sync, location, or data on. Only thing on is WiFi & I'm getting bad screen on & idle time.

Sent from my Nexus 5
[Nexus 5 Original Android Development] neriamarillo:
Use the FKU app and choose system monitor from within the app to check CPU load. You can have a floating widget also. I'm on slim too 2.6 rc2.
[Nexus 5 Original Android Development] :
I'm using stock ROM well pretty much. On PA I had amazing battery life 0.4% an hour while idle. Now I got 4% an hour. Many apps greenified as well :|
[Nexus 5 Original Android Development] franciscofranco:
Send me an email with your old email and I'll refund the purchase on the hacked account :)
[Nexus 5 Original Android Development] marcusva79:
Franco is there of just sending me a link to the new apk? Or it wouldn't work that way?
[Nexus 5 Original Android Development] franciscofranco:
Doesn't work like that.
[Nexus 5 Original Android Development] franciscofranco:
Pushed another r33-test build with some low level improvements and UV extra sensibility should be fixed (I hope). Enjoy and good night.
[Nexus 5 Original Android Development] vomer:
Time to test!

Also, Before anyone asks the millionth time : http://192.241.177.15/Nexus5/4.4/tests/

Sent from my Nexus 5
[Nexus 5 Original Android Development] Techimplant:
Alright..here comes a weird question

If an app crashes then who is to be blamed.. I mean what causes that.. I am on rooted stock + r33(feb6-beta test2) + ART ..And GT Racing 2 keeps on crashing as soon as it loads :rolleyes:
[Nexus 5 Original Android Development] RootTheMachine:
Nothing to do with the kernel. Does the app work with art?
[Nexus 5 Original Android Development] Techimplant:
Well I have doubts about that too..I think its ART issue only..thanks
[Nexus 5 Original Android Development] Technecium:
The same people who make baby Jesus to cry or it might be the bastard who takes one sock when you do laundry..

try logcat
[Nexus 5 Original Android Development] P.Mobile:
just got home from work perfect timing :) flashing now b4 bed.. thanks boss!!
[Nexus 5 Original Android Development] Techimplant:
Well I was about to grab the logcat but dont know how to :rolleyes::banghead:
[Nexus 5 Original Android Development] Technecium:
Google logcat

play store logcat

and I know it's coming so

Google pastebin
[Nexus 5 Original Android Development] Techimplant:
Well here is a log regarding the crash..I used an app called Catlog to capture..

https://www.dropbox.com/s/6s4wfvhb0bjkzcx/2014-02-08-11-45-03.txt
[Nexus 5 Original Android Development] albatros_1994:
UV fixed...back to my r32 values:good:
[Nexus 5 Original Android Development] Andypandiiee:
Its kinda hard to identify what the icon means when its just a symbol with no words or explanation on what it does. Looks more like a bookmark imo.
[Nexus 5 Original Android Development] bkai:
... hence the nice, informational overlays provided by fku after each time you clear its data (which you should also be doing after each update) ...
[Nexus 5 Original Android Development] Das IceDice:
What to look from last_kmsg.log if crash is caused by uv?

(I had crash and log said watchdog bark)
[Nexus 5 Original Android Development] h4m74ro:
Switched from r32 to r33 8.2. It seems like screen touches are "smoothly lagging" behind a lot. I can see it in g+ App while scrolling or in Chrome. :crying:

No boot settings.

Edit: pinch zooming too. I'm on Cataclysm with Dalvik.
[Nexus 5 Original Android Development] puska:
Some of the apps were crashing on me with to much UV so I put +25 and everything was good again.

Are you also undervolting?
[Nexus 5 Original Android Development] sjondenon:
On R32, my phone doesn't go to deep sleep. I stucks at maximum frequency. However when I turn the ariplane mode on, the problem is gone. When only using wifi, or only using network (3g) the problem is still existent. Therefore it seems that no specific application is involved.

I attached a screenshot of my wakelock detector app and cpu spy.

Does anyone know what might be the cause of this problem? Im running 4.4.2 stock.

EDIT:

The only suspicious app to me is flappy bird. I just reinstalled it and there is an improvement sine wakelock detector indicated that it is still using audio somehow. Now, it switches to 300 Mhz as the most used frequency rather tan the maximum frequency. However, still no deep sleep

EDIT 2: Here are my kernel wakelocks, can someone help me understanding them?
[Nexus 5 Original Android Development] peikojose:
Last r33 no apps running three cpu stuck at 2.3Ghz
[Nexus 5 Original Android Development] ben_pyett:
how soon after a reboot is this, you must leave it for a few minutes to settle down.

Have you wiped the days from FKU?
[Nexus 5 Original Android Development] Techimplant:
Nope I am on stock voltages..I have Underclocked a bit though at 1958 mhz..and thermal throttle at 70..thats it
[Nexus 5 Original Android Development] sohail77:
Sorry if this was asked b4 can we see a cm version or is there a cm version because r32 doesn't work on cm roms
[Nexus 5 Original Android Development] Enddo:
Just wanted to drop in and say that with the test 33 from feb 4th, im seeing ~30% increase in screen on time(and i got a lot of screen on time before)
[Nexus 5 Original Android Development] Techimplant:
Well give the r33 test img released on feb 6th a try..on that I am getting SOT of almost 5 hrs every time..dont know about the latest release though..havent tried it yet..
[Nexus 5 Original Android Development] starbriganza:
Lots of Random Reboots.

[MENTION=3292224]franciscofranco[/MENTION] I have r32 installed. I get lots of random reboots. Please help. I've attached a last_kmsg.txt
[Nexus 5 Original Android Development] Savant:
Maybe you're holding it wrong since I'm running same set up no lag its smooth like butta. [MENTION=3292224]franciscofranco[/MENTION] as per the usual thanks for the magic.
[Nexus 5 Original Android Development] ivan08v:
Having this reboot since last four r33 test including lastest one

http://pastebin.com/4CcfMjZQ

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] justibasa:
[MENTION=3292224]franciscofranco[/MENTION] New test seems to be running great so far. No lag and sleeps great. Thanks dude!