yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Foggy79:
Hi all,

I have this weird thing when changing the max CPU frequence... I set it to 1.5Ghz max, switch the "set on boot" flag, and after a while (or a reboot), my settings are back to default 2.23Ghz... Not sure why it always gets reset to default... I'm on r32
[Nexus 5 Original Android Development] vomer:
did you wait a minute or so after boot before checking?
[Nexus 5 Original Android Development] ChazzMatt:
cell reception/internet issues

Are you on stock ROM and just rooted, or are you on a custom ROM? If on a custom ROM, just reflash the ROM and it will put back the kernel it uses, which is not Franco. However, reception problems are not kernel-related.

What might solve your cell reception/cell internet problem is flashing another radio/modem. Or just re-flashing the one you have:

Nexus 5 Modems

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

For instance, since the Nexus 5 was released, Qualcomm/Google has supplied the D820 (North America) Nexus 5 with FIVE different modems. People call them 12, 13, 15, 17, and 23 -- based on the last two digits of the file name. "23" is the newest, which should be the best. But, some claim they get better reception with the older "15" than newer "23". Stuff like that. So, experiment. They all work with 4.4.2.

The international Nexus 5 model (D821) only has one modem release. So, if you have that model, all you can do is re-flash to see if that solves your problem. You'll find them all in that thread.
[Nexus 5 Original Android Development] franciscofranco:
That's not so good :p Its ok, it happens.

I'm in Spain? Last time I was in Spain it was almost 2 years ago.

Removing the logger from the Kernel config you'll end up with no logcat at all. To disable logcat you have to add a hook in the driver to make it return 0 all the time. Check my logger.c I added that.

Ups!! How did that end up missing xD I'll push a fix. Hows the rest of the app though? Lots of memory optimizations, improved perappmodesService, drawer now shows the active tab in an highlight etc etc

Can you try with increased thermal throttle threshold? 70 please, then let us know your experience.

Not sure at this point, but its something I can think about.

Nah I made no changes to that.
[Nexus 5 Original Android Development] lightstar3103:
Is the fast charge working well with the r32 ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] vomer:
The app does feel snappier and polished this time around :) the active tab was a good idea - looks much cleaner now.

edit - I should add if you click "load profiles" then it duplicates files on the SD card. Perhaps it should replace?
[Nexus 5 Original Android Development] edwinpang:
GPU voltage control possible?
[Nexus 5 Original Android Development] :
Yes
[Nexus 5 Original Android Development] :
Aaah shoot. I guess I mixed Spain and Portugal up.

Okay, I give you my permission, too.

See you later!
[Nexus 5 Original Android Development] cobyman7035:
R33 final out yet?

Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
[Nexus 5 Original Android Development] norcalsfinest:
You tell me. The link is in the OP and FKU would tell you too
[Nexus 5 Original Android Development] franciscofranco:
It does not duplicate for me...

Nope, one voltage control is enough problems for me already.
[Nexus 5 Original Android Development] franciscofranco:
Just pushed the fix, hope its online in the next 30m-1h. Probably the last beta before production build, still have two bugs to fix:

* vibration gets stuck in a "enable/disable" mode if user sets 0 or 1 in the input box

* if a user clicks set on boot colors before setting a profile the colors won't be set to boot

After these two and merging the latest translations we're good to go v11,3 production then I'll be able to work on other exciting things like the promised shell script loader which I postponed to v11.4.
[Nexus 5 Original Android Development] vomer:
weird, I will try again in the new build :good:
[Nexus 5 Original Android Development] Foggy79:
Yup, it's weird, I underclock it and when I check a few hours later its back to default speed :confused:
[Nexus 5 Original Android Development] vomer:
what app are you using?
[Nexus 5 Original Android Development] imablackhat:
R32.

Random reboot? Closed my flip case. And felt it vibrate. Kmesg is huge. Here's last bit.. Any ideas?

26092.418919] r4:00000001 r3:c22a6540

[26092.418933] [] (_cpu_down+0x0/0x344) from [] (cpu_down+0x38/0x54)

[26092.418949] [] (cpu_down+0x0/0x54) from [] (hotplug_suspend+0xd4/0x130)

[26092.418958] r4:00000001 r3:00000003

[26092.418975] [] (hotplug_suspend+0x0/0x130) from [] (process_one_work+0x170/0x5b4)

[26092.418984] r7:c01023dc r6:c229a700 r5:f668c000 r4:f666db80

[26092.419004] [] (process_one_work+0x0/0x5b4) from [] (worker_thread+0x1b4/0x4dc)

[26092.419023] [] (worker_thread+0x0/0x4dc) from [] (kthread+0xc4/0xd0)

[26092.419041] [] (kthread+0x0/0xd0) from [] (do_exit+0x0/0x850)

[26092.419051] ---[ end trace fefd15fa9f1f6574 ]---

[26095.712022] mdss_dsi_panel_off:

[26096.121956] [Touch] touch off

[26101.502553] Watchdog bark! Now = 26101.502545

[26101.502688] Watchdog last pet at 26090.502277

[26101.502761] cpu alive mask from last pet 0-1

[26101.502830] Causing a watchdog bite!

No errors detected

Boot info:

Last boot reason: wdog_bark
[Nexus 5 Original Android Development] franciscofranco:
Yeah that's fixed on r33-test, will be pushed to production soon.
[Nexus 5 Original Android Development] P.Mobile:
hey i was running the latest r33 test build but was having that ram issue some people was having so i flashed faux kernel for the time being. once the ram thing is all good i will be going rite back to franco kernel.. my question is will i have to flash the stock kernel then back to franco.. or is it ok just to flash rite over faux kernel?? thank ya!
[Nexus 5 Original Android Development] chikimonke:
You actually probably should have flashed the stock kernel before switching from franco to faux. That said, I personally always flash back to stock before switching kernels, just to make sure the new kernel has a clean slate and I can properly evaluate it.
[Nexus 5 Original Android Development] lolerpro8:
Um.. No. Every time you flash new kernel, you will clean everything that was from the past kernel.
[Nexus 5 Original Android Development] Foggy79:
franco.Kernel updater
[Nexus 5 Original Android Development] vomer:
Working great! BTW Love that % feature in status bar when boot img is downloading :D

---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------

clear app data - re apply options and try
[Nexus 5 Original Android Development] semcosweeper:
[MENTION=3292224]franciscofranco[/MENTION] donation sent for all your hard work. Keep it up as my phone loves it
[Nexus 5 Original Android Development] BTT8:
A little odd topic, but what is the latest version of twrp for our beloved nexus 5?
[Nexus 5 Original Android Development] P.Mobile:
yea everyone says something diff..i have seen kernel devs in the past say its best to flash stock kernel b4 bcause of the ramdisk.. then people say u dont need to.. i did it just to be safe:good:
[Nexus 5 Original Android Development] chikimonke:
As I understand it, that's not always the case with the RAM disk. Some kernels use a custom RAM disk, others do not touch it. If you had a kernel installed that had a custom RAM disk, then flashed a kernel that doesn't touch the RAM disk, you could run into compatibility issues. Last I knew, franco does have a custom RAM disk, and faux does not, so you may see issues. All of this may have changed, but this used to be the case, hence why I flash stock kernel between custom kernels.
[Nexus 5 Original Android Development] lolerpro8:
*some* Kernel devs use zImage injectors so they keep the ramdisk compatible. So they think it will keep the settings from old kernel talen from ramdisk. They are wrong. Flashing stock kernel is a waste of time and really if you think, yoi are aggain flashing "different" kernel then before.
[Nexus 5 Original Android Development] jmaddr:
http://techerrata.com/browse/twrp2/hammerhead
[Nexus 5 Original Android Development] Foggy79:
Will try, thx!
[Nexus 5 Original Android Development] nexusmaniac:
Have you pushed another update after this one? I just had another one 5 mins ago :)
[Nexus 5 Original Android Development] franciscofranco:
That's the one I pushed! ;)
[Nexus 5 Original Android Development] nexusmaniac:
I had one before that that missed out the color set on boot and now this one has it back :) :good:
[Nexus 5 Original Android Development] mendozaram:
Its already online? The one that i can see have "last modified" date -> 2014-01-27 05:21	6.5M
[Nexus 5 Original Android Development] nexusmaniac:
We're taking about the fku app not the kernel ;)
[Nexus 5 Original Android Development] schizophrenia:
i went a bit farther to 75 and it seems better now.

i shall try 70 later.

thanks for the tips
[Nexus 5 Original Android Development] carlos_online:
Hello guys, sorry to ask this, too hard to follow a soooo popular thread!

Is this kernel compatible with CyanogenMod? Any colors problems?
[Nexus 5 Original Android Development] bobmarsh72:
This is my search on tapatalk... Have you got search?
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Is the volume not controllable problem only for r33test or is it on r32 also? Because I opened Soundcloud today and played some song and my ears almost blew up before I pulled my earbuds out. Jeez.

I'm hoping it's not something else on my system that's conflicting.
[Nexus 5 Original Android Development] MoJo:
I'm on r32 since it was released - no problem with volume control.
[Nexus 5 Original Android Development] P.Mobile:
hey Franco found a new review of your color control app.. just was posted today!! fresh off the press :) http://www.youtube.com/watch?v=IJRosk-t634
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Maybe it's a CM issue... not sure what I'm dealing with.
[Nexus 5 Original Android Development] Bobtehblob:
Are you using cm? I've seen you in the cm11 thread. It's on r32 as well, sound cloud is one of the apps that gets locked into full volume. The sound patches required to fix this unfortunately break compatibility with stock rom, so Franco only merged some of them. I've just gone back to an older build of vanir for now (19th) and everything is fine again. The 18th or 19th build of cm is more than likely one of the last builds before these patches were merged.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Thanks! Yeah, it looks like one of the CAF changes broke volume control. For those who want volume control for media to work properly, the options seem to be to stick to CM kernel, or try this Non-CAF patch for custom kernels. Note the patch breaks some features of the kernel like color control.
[Nexus 5 Original Android Development] G8D:
Unrelated but:

what's the navbar app he's using?
[Nexus 5 Original Android Development] bobby janow:
I thought it looked like Pie controls with 3 panels, the left one being go back.
[Nexus 5 Original Android Development] franciscofranco:
Yeah latest CM nightly also uses a different audio_hal which needs obviously Kernel support, but that Kernel support breaks stock so no go for me :(
[Nexus 5 Original Android Development] nexusmaniac:
[MENTION=410271]fransisco[/MENTION]franco hi, in your app when you go to the gamma control tab in the colour section you can't swipe back to the main drawer, is this by design? Because it's slightly annoying :)
[Nexus 5 Original Android Development] juancaperez2000:
After day with slimkat and latest test my phone start to get problems with ram memory and get really unresponsive
[Nexus 5 Original Android Development] Delacor:
I remember good old S2 Dorimanx days, there was ONE Kernel for SAMMY + CM roms, is there no Workaround for this...?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] chenleicpp:
What to need an app that can switch double tab screen on,can somebody recommended one thanks

来自我的 Nexus 5 上的 Tapatalk
[Nexus 5 Original Android Development] michaelsplus:
Franco, I'm loving your work. Battery life is great and I love the stability and to be able to just flash and really trust your magic.

The new update to FKU really is great.

Edit: nevermind, please ignore screenshot, sorry.
[Nexus 5 Original Android Development] :
This is a kernel feature. You can flash this kernel and enable it [KERNEL] [Jan 21] ElementalX-N5-0.26 via terminal.
[Nexus 5 Original Android Development] ConMcCRay:
LOVING the battery on latest test 33. At 50% and 3 hours 15 of screen time while using my phone ALOT. About 30 minutes off WiFi, Bluetooth on almost half the time streaming music.. Twitter, snapchat, G+, and playing flappy bird :D:D THANK YOU FRANCO.
[Nexus 5 Original Android Development] shreddintyres:
Look up touch control by bponury in the play store
[Nexus 5 Original Android Development] nexusmaniac:
I had the same problem on stock, I had 300MB of RAM left and everything became very sluggish :(

Edit: on r33v5, a reboot fixed it. Other than that the latest r33 is great for battery life!
[Nexus 5 Original Android Development] vomer:
It's a known bug on the latest test build.

Sent from my Nexus 5
[Nexus 5 Original Android Development] nexusmaniac:
Yep, I remember Franco said it just after he posted the .img but I didn't think that it would cause much of a problem because I still had quite a bit of RAM left... until a few hours ago :)
[Nexus 5 Original Android Development] Lownita:
Is phone still boot looping when switching to ART with franco kernel installed? I remember it happened some time ago.

Tapatalked from my Nexus 5
[Nexus 5 Original Android Development] JNewms:
That isn't specific to Franco kernel. ART is highly experimental and isn't meant to be used yet. One time it may work, the next it may not.
[Nexus 5 Original Android Development] silvan g:
On the last fku beta when you clear the app data the set on boot boxes keep selected, is that supposed to be? Because on previous versions it cleared that as well.
[Nexus 5 Original Android Development] Testraindrop:
ART has still nothing to do with the kernel.

It still does not bootloop on Franco kernel.

Last time it was xposed, but now it will revert to dalvik if you use it.

Gesendet von meinem Nexus 5
[Nexus 5 Original Android Development] Pete182:
Just got a random reboot paying the Nintendo ds emulator app. How do I find and upload the log?
[Nexus 5 Original Android Development] nexusmaniac:
/proc/last_kmsg
[Nexus 5 Original Android Development] franciscofranco:
Yes. You don't want to open the drawer when you're in the far off tab and still have the ability to swipe to the left tab. Both actions cannot happen so it only allows to open the drawer when you're in the first tab.

No, this is purely Kernel commits.

No that's not supposed to happen at all. I'll test and see if I can reproduce.
[Nexus 5 Original Android Development] P.Mobile:
cant wait for r33! im not feeling this kernel im running.. i so can see the differnce.. matter a fact ima just go back to r32 for now.. i wasnt having any problems with it :) i will never flash another kernel other then this one again!!
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
I suppose choosing between broken sound and color control is OK to me since I don't even listen to music on my phone. Just gotta remember to plug in headphones or sometime when I game.
[Nexus 5 Original Android Development] Alfablos:
Excuse me, did you uc or uv? How could you have such a result? :D
[Nexus 5 Original Android Development] ConMcCRay:
I only UV like -25 cause of the new voltage changes on r33 LOL
[Nexus 5 Original Android Development] Alfablos:
What Voltage changes? I uv -100 and limited to 1.5Ghz, still don't have as good resoult as your. But today I made a few changes. Will see tomorrow!
[Nexus 5 Original Android Development] Enddo:
because everyone uses their phone differently
[Nexus 5 Original Android Development] Circaflex:
just to make sure im using the right app i just bought the franco app in play store and when trying to use the screen color it says device not supported, just making sure this is right? i can use the free display app and it works
[Nexus 5 Original Android Development] jordirpz:
Please, is r33v5 this one? 2014-01-27 05:216.5M

Thanks

vía N7 r-paco
[Nexus 5 Original Android Development] mibtnt:
^u can also follow the instructions on the first page and join the testing team I think. I did that.

---

So wait. All this time when my phone vibrated an I saw bug report captured, I'm supposed to send it to franco? Well... :D I'm sure most are fixed in r33. I didn't get any the past two days anyway.

---sent from N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] franciscofranco:
Color control support for the N5 comes when I release v11.3 (currently in the beta channel). It should be released tomorrow, I'm mostly done with my tests and user tests.

Bug report its something else, its something from the system itself when it encounters a bug, its not Kernel related.
[Nexus 5 Original Android Development] mibtnt:
Awwww shucks. Figured I had another reason to contact u. :D:D jk

---sent from N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] ivan08v:
Random reboot using tapatalk on lastest r33 http://pastebin.com/aha80iei :thumbup:

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Undervolting too much?
[Nexus 5 Original Android Development] ivan08v:
-50 across and 635 con 300mhz, stable since last 10 nightlies or more, something like cpuidle and resuming crash? Some changes raising the minimum stable voltages? I'll test now with stock ones, thank you!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Rxpert:
No need to change what you're doing for cm.

Keep on keeping on Franco :thumbup:
[Nexus 5 Original Android Development] omvir:
Just like me, you have to under volt just slightly less. UV on r33 is different from r32(and below). You can't keep using the same undervolt settings from r32 on r33. Franco made changes in that area that no longer UV what we once could before.
[Nexus 5 Original Android Development] Tzfardaya:
no, don't keep keeping things on franco, if you keep too much on him he won't be able to get any work done and all our nexus devices will suffer the lack of new franco kernels...

:P
[Nexus 5 Original Android Development] vomer:
Also depends on your chip. My custom settings call for -50 across + 300MHz @ 650 and I did not get any issues. :cool:

---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------

I think he has to do more work to support CM which is why he is not bothering anymore... since CM decides to do it's own thing ;)
[Nexus 5 Original Android Development] omvir:
Hmm could that be because you were already undervolding slightly less than what you could have before?
[Nexus 5 Original Android Development] vomer:
Yup, I don't believe in harsh under volting. But in general every chip handles UV differently
[Nexus 5 Original Android Development] omvir:
Oh makes sense lol. My under volt settings were tested to be the lowest possible. So for r33 I was crashing like crazy. And yes, I think I have a #3 chip.
[Nexus 5 Original Android Development] dark_ente:
Same here and also crashes when I tried to apply r32 voltage settings. I don't have much time to test uv at the moment, can you test r33's lowest possible uv?
[Nexus 5 Original Android Development] omvir:
But the thing is, each device handles UV differently even if the same chip. What weere you undervolting on 32? So I can compare to mine.
[Nexus 5 Original Android Development] Bobtehblob:
The problem is that it will only get worse :( As CM sources stray further away from aosp, more and more things will break. Then when you start mixing these zips that replace older libs etc it's just a recipe for disaster. I learnt from the nexus 4 when this happened that it's best to just cut your losses and find a 100% aosp rom :(
[Nexus 5 Original Android Development] dark_ente:
Mine is 300mhz@605mv, 2265@960mv.

I find the lowest possible voltage then raise a little
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
True but isn't there someone maintaining CM compatible Franco kernel on the N4? I think someone us doing it for faux as well.
[Nexus 5 Original Android Development] chrisch91:
How can i use the scroll effect like the guy in both videos?
[Nexus 5 Original Android Development] jmartino5920:
I'm sure there is a savvy dev who wants CM and Franco to work harmoniously, and is willing to work out the BS to make CM and Franco compatible.

However, this is the OFFICIAL Franco.kernel thread, not the unofficial, tweaked for CAF (instead of AOSP) ROMs (including Stock Android 4.4.2) Franco.kernel thread.

Not saying you aren't welcome to ask questions or be a part of this community; however, just like the Nexus 4, which I owned, and the Nexus 7 (2013), Franco isn't going to go way out of his way to implement changes to his kernel which cause problems with the well established (and much larger) community of users.

For the longest time, CM was an AOSP "enhanced" ROM. Since the latter days of development for the Nexus 4, leading into the dev for the Nexus 7 (2013) and continuing with the incorporation of CyanogenMod as a company, CM has slowly but significantly strayed from its roots; the roots of Android as intended by the Android Open Source Project.

One can certainly live well inside their slowly changing take on Android (NO AOSP CUSTOM KERNELS ALLOWED!). However, as they continue to make commits that don't work with Google Source Code, Franco and AOSP kernel devs alike will be less and less willing and able to support this differentiated code.

As users, we have a choice...be loyal to a non-AOSP ROM (as Nexus users we have THE MOST OPTIONS WHEN IT COMES TO ROMS BTW)...or be loyal to a kernel which is founded upon the very principles which made the Android Dev community (AOSP) what it is today.

/soapbox

Franco.kernel FTW!

jmar

Sent from my Nexus 5
[Nexus 5 Original Android Development] cadbomb:
I am new to your kernels and come from another galaxy far far away, but I must say... I've read through every page of this thread, have now purchased FKU and signed up for beta, and greatly appreciate the community recognized dedication and professionalism you put into your work. You, sir, have my respect. (Low man on the totem pole, but appreciative none the less.) Keep up the good work and tolerance for all!
[Nexus 5 Original Android Development] caribouxda:
Is it normal that when screen on nothing running 2 cpu are always on switching frequencies 300/2.3 between the 2?
[Nexus 5 Original Android Development] ama3654:
I think your phone will crash if cpu stops working, there are some wonderful calculations going on at the background to make sure something moves when you touch the screen, its normal.
[Nexus 5 Original Android Development] webvictim:
2 cores online is normal for screen on with Franco's hotplug driver, yes. The frequency switch will be because some process or other (maybe the system monitor you use to report the CPU speeds) is doing work.
[Nexus 5 Original Android Development] monkey hung:
Is it worth wiping the cache and dalvik cache anymore? I just tried in TWRP and it keeps telling me that it failed.
[Nexus 5 Original Android Development] notbrodie:
it never was. just flash and forget

Sent from my Xoom
[Nexus 5 Original Android Development] Shano56:
The nexus 5 is better than the N4 in every way. I'm excited to see what Franco kernel can do for it :D
[Nexus 5 Original Android Development] sordna:
Please don't disable multicast by default, it's needed for some DLNA stuff, igmp proxying, etc.

At most it should be an option, hopefully setable by FKU :)