yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] The Gingerbread Man:
I'm quite satisfied that behaviour is as expected with using the stand alone per app mode. Don't worry about the refund its fine honestly enjoy the small amount for the hard work you put in :)

Just need to get those fixes over to fku now. You said to ask again later about the toast message and briefly going quad core mode while switching between per app mode and system settings, do you have time now?

Edit

Just as a thought, would it be possible if a person were to have paid version of per app mode then fku would open it instead of the fku version, maybe if there were a way to have an invisible desktop icon too, like SuperSu. Would be quite cool. Maybe same sort of thing for nexus colour control app
[Nexus 5 Original Android Development] WettbackMartyr:
Yes I am. Sorry to have left that out.
[Nexus 5 Original Android Development] Polv89:
Thanks a lot franco, you are The best

;)

Inviato dal mio Nexus 5 (by Nexusarena.it)
[Nexus 5 Original Android Development] SedyBenoitPeace:
[MENTION=3292224]franciscofranco[/MENTION] I quote again my post just in case you didn't read this...thanks for all!
[Nexus 5 Original Android Development] gamerZ1:
Here are the logs for random reboots on 5GHz band.You have it in the attach.
[Nexus 5 Original Android Development] franciscofranco:
Ok so that happens because some devices have async CPUs which means that even if I change the freqs to cpu0 those won't be migrated to the other cpu nodes so I have to online them all, change the freqs and then the Hotplug drivers will take them down again. That's the reason.

Yes that's a good idea, I can do that for users who prefer to use the standalone apps instead the parts inside FKU.

I didn't overlook I just don't know what to say anymore :( I cannot reproduce the issues, no matter how hard I try it! There were tons of audio patches since r32, but I cannot pinpoint to X or Y patch because I can't reproduce!

I have no clue. I use 5GHz on my room and I don't have any issue at all. Wi-Fi drivers are also stock.
[Nexus 5 Original Android Development] gamerZ1:
I will make a video you to see the bug.
[Nexus 5 Original Android Development] SedyBenoitPeace:
Ok thanks for all franco! If you want a beta tester for audio tests I'm here... I think that I will revert to the r31...also if I'm sad because on the other releases there is less battery consumption! My other wish was also on the patches for wifi with high traffic but unfortunately I need to stay on r31! Thanks in every case!

Inviato dal mio fantastico Nexus 5 con Franco's kernel
[Nexus 5 Original Android Development] franciscofranco:
Let's hope it works better on r35, wish I should be releasing in a couple hours!
[Nexus 5 Original Android Development] FAdrums:
https://www.youtube.com/watch?v=r1nNdTyDZEs&feature=youtube_gdata_player

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] GtrCraft:
I just installed omnirom with multirom and evety time I try to change the governor, the phone crashes. And the governor is always performance :confused:
[Nexus 5 Original Android Development] hello00:
my phone reboots randomly every time i use gps when connected on usb car charger. does anybody have this problem?
[Nexus 5 Original Android Development] franciscofranco:
Log.
[Nexus 5 Original Android Development] franciscofranco:
Somehow you're doing something really wrong.
[Nexus 5 Original Android Development] Momotani-Hitoshi:
attached my last_kmsg, not sure how useful it is because I am forced to (power + vol down) reset the phone for it to turn on. I can't even access it with usb cable.

R34 works on the encrypted N5 until it goes to sleep and will never turn back on until force reset. I used the paid FKU to install the kernel. Running stock 4.4.2 rooted. Removing/Restoring franco R34 using the FKU app, my N5 sleeps and turns on normally again.
[Nexus 5 Original Android Development] GtrCraft:
Just did the same on stock, everything goes fine. I think its a rom or kernel issue :rolleyes:
[Nexus 5 Original Android Development] franciscofranco:
Not Kernel for sure as nowhere sets performance as governor.
[Nexus 5 Original Android Development] franciscofranco:
Yeah the log doesn't tell me anything. You have to capture the log while reproducing the error.

cat /proc/kmsg > /sdcard/kernel_log.txt

Then while that is running turn the display off to reproduce the problem. Then force the reboot and get the log file for me.
[Nexus 5 Original Android Development] GtrCraft:
Deleted omnirom, missed your kernel already too much :good:
[Nexus 5 Original Android Development] jordirpz:
Francisco, about Xbox drivers, whats meaning it please? Can i ll connect my wireless joystik Xbox? Thanks

vía n7II r-paco
[Nexus 5 Original Android Development] franciscofranco:
Yes, that's probably it. I don't have a controller so cannot say, but I enabled the Kernel drivers for that.
[Nexus 5 Original Android Development] The Gingerbread Man:
That makes perfect sense, thanks for the explanation! I really like the idea of using fku to open your other full stand alone apps, just like the current functionality of system monitor!

Chances are its for wired controllers, I'd be very surprised if you got the wireless ones to work without having the nesesary USB wireless thingy for it to work on a windows machine using USB otg cable with it

Edit

Also Franco, as the new per app mode doesn't have a thread I can see, I just wanted to let you know on my nexus 7 2013 I can't save any per app modes. Instead of save button there is show/hide system apps
[Nexus 5 Original Android Development] franciscofranco:
http://xdaforums.com/showthread.php?p=51040307

That's the thread. Weird, I might've borked something when I created the tablet layout. Can you rotate your display and see if the action bar is correctly set up? I'll push an update soon for that bug, thanks.
[Nexus 5 Original Android Development] Momotani-Hitoshi:
Okay, I ran that command line, logged it until it went to sleep & stopped working. Attached.

Hope you can see something that is causing the issue with encryption.
[Nexus 5 Original Android Development] The Gingerbread Man:
Huh now really was a case of 'your holding it wrong'! Rotated to landscape and I had back up / load profiles, then rotated back to portrait and now the save button has decided it wants to show up in both lay outs. Wierd

Edit, same with custom paths

Anything else with it I'll post in the proper thread.
[Nexus 5 Original Android Development] franciscofranco:
Nope, its my derp!

In another note, do you like the "Rate it" overlay bar? Its pretty slick, doesn't obstruct the experience while "warning" users to rate the app.
[Nexus 5 Original Android Development] franciscofranco:
Yeah it seems the Kernel gets stuck at PM: syncing filesystem... which is when the power management layer flushes any outstanding writes to the file system so something is derping with the encryption which probably has some different permissions etc. One question, has FK ever worked fine with encryption or is it a recent problem? Can you try with r32?
[Nexus 5 Original Android Development] The Gingerbread Man:
Just updated my post to report same sort of thing using custom paths thing. Yes I do like your rate it over lay, its much less intrusive than quite a lot of apps which I can find annoying as they don't let you go to do what your intentioned on doing without first performing another action or dismissing it only to find next time you use the app you get the same dialogue. Top notch in that department :D
[Nexus 5 Original Android Development] Momotani-Hitoshi:
Bought FKU app yesterday so I've only used R34 so far. It does work on my N5 without encryption.

I'll try R32 and test.
[Nexus 5 Original Android Development] franciscofranco:
Yes, it will have the same bug on all panels. I'll fix it today/tomorrow. Thanks for the words, don't forget to leave a rating, every bit helps! :)
[Nexus 5 Original Android Development] Tzfardaya:
... Again with the teasing...

You Sadist you....

*vibrating in anticipation of a new kernel to play with...*
[Nexus 5 Original Android Development] IRX120:
Sorry if this has already been asked, but on r34 I have like 300-400mb of available ram and apps constantly get closed in the background, is this kernel related?
[Nexus 5 Original Android Development] drdrewdown:
it's a known concern at the moment
[Nexus 5 Original Android Development] The Gingerbread Man:
Done! Also bought your nexus colour control app today (payday joys!) so your next coffee with Mr Göllner is on me :)
[Nexus 5 Original Android Development] Magiya1988:
DriveDroid Support

This would be awesome in the Kernel :victory:
[Nexus 5 Original Android Development] franciscofranco:
Its been in the Kernel since r33...
[Nexus 5 Original Android Development] bmakk2055:
Is the per-app mode in the kernel updater the same as the per app mode app?
[Nexus 5 Original Android Development] jmartino5920:
Indeed.

Sent from my Nexus 5
[Nexus 5 Original Android Development] The Gingerbread Man:
Mostly, the UI is different and you can set custom paths to specific things if you know where to find them. The basic functionality is the same though.
[Nexus 5 Original Android Development] franciscofranco:
No offense but I have already answered that post 10 times, quick search will find the answer for you.
[Nexus 5 Original Android Development] bmakk2055:
Thanks
[Nexus 5 Original Android Development] franciscofranco:
Pushed r35:

* Increased minimum brightness a notch so that it doesn't look too low with auto-brightness (please test this out and give me feedback)

* Random BT disconnects during deep sleep should be fixed

* Merged a couple of misc patches from CAF

* It should now work fine with the latest Carbon rom nightlies

* Enabled XBox controller drivers

Also please test audio again, the reverts I made for BT random disconnects *might* be causing those weird audio glitches during screen off playback. As usual, feedback is welcome!
[Nexus 5 Original Android Development] Tzfardaya:
Wheee, the torture ends... until r36.. ;)
[Nexus 5 Original Android Development] Rehab4Life:
Omg this was what was impairing my smartwatch lolol. Thanks for the Bluetooth patch was just about to go crazy
[Nexus 5 Original Android Development] Tzfardaya:
sweet, pebble works fine now?
[Nexus 5 Original Android Development] Momotani-Hitoshi:
I tested with R32 and it worked with my encrypted N5. It's now able to sleep and wake up normally. Hopefully you can find what the difference is between R32 and R34, maybe fix it in a future release. Should I try R35?
[Nexus 5 Original Android Development] franciscofranco:
Ok that makes more sense to me. Please try r35.
[Nexus 5 Original Android Development] Rehab4Life:
For the time being. Going to do the dishes and she if it disconnects.
[Nexus 5 Original Android Development] tcat007:
R35 lowest brightness perfect in dark room.
[Nexus 5 Original Android Development] xanaxdroid:
Thanks for the update. Love Carbon but love it with your kernel even more.
[Nexus 5 Original Android Development] EstarlinMReyes:
As I can see all the Audio issues are fixed, thanks Franco.
[Nexus 5 Original Android Development] Rehab4Life:
Still disconnecting with Bluetooth. After like 5-8mins of deep sleep

Also can I downgrade kernels by just flashing them in the app? Or is that bad?
[Nexus 5 Original Android Development] semcosweeper:
Hey [MENTION=3292224]franciscofranco[/MENTION], I haven't been able to reproduce to take a video. When I auto flashed r35 and my phone booted up I unlocked it and my screen turned off. Turned it back on and unlocked and screen glitches went crazy with static lines everywhere so often I could barely see anything on my homepage. Waited about 30 seconds after glitches started and had to reboot to fix it. If it happens again I'll try my best to catch something for you. I never had this problem when others were experiencing screen flickering on past kernels also.

Stock ROM, r35 only changes speaker gain 5 and vibration amp 63, xposed with gravity box and advanced power menu

Thanks for all your hard work!
[Nexus 5 Original Android Development] Momotani-Hitoshi:
Nope. R35 has the same issue as R34 with encryption. Attached logs anyways in case it's of some use.

I'll revert back to R32 for the time being.
[Nexus 5 Original Android Development] Tzfardaya:
just set it to device only, google doesn't use the gps for it's location settings in apps, but other apps can use it to grab location...

or, you can use tasker to enable disable the location mode per app..

that's all it takes to "downgrade" all it is is just another kernel..
[Nexus 5 Original Android Development] donwhall70:
What exactly isn't working on the N5 with encryption enabled? I have encryption enabled and my phone is working perfectly fine.
[Nexus 5 Original Android Development] elite_gamer04:
Only issue I've had since r34 (more specifically the Brightness implementation changes) is that if your using Lux or equivalent, it makes everything so dark. I believe it was mentioned a toggle would be in FKU one day in the future :)
[Nexus 5 Original Android Development] rccar:
R35 didn't fix my brightness issues, when the screen dims (almost timing out) the screen looks off but if I touch it, it turns back on. That's how I can tell it's still on. I don't use auto brightness or any app such as lux. Anyone else?
[Nexus 5 Original Android Development] mibtnt:
Ahhhh so this is why my Bluetooth headset randomly cut off. I was going mental as to why my call randomly cut off a few times.

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] TrenchKato:
The auto brightness is better. But on the lowest setting or when the screen dims right before timeout half of my screen is still darker than the other.
[Nexus 5 Original Android Development] vomer:
Brightness looks better now on 35

Sent from my Nexus 7
[Nexus 5 Original Android Development] fugn:
thank you!!!
[Nexus 5 Original Android Development] peecs121:
Running awesome. Thanks!

Sent from my blazing fast Nexus running Carbon Rom/Franco Kernel
[Nexus 5 Original Android Development] perrocaliente:
Do you guys think that "multi core power saving" is something I should run with this kernel? I've looked it up and it sounds like it might be good but I'm not sure if it works well with Franco?
[Nexus 5 Original Android Development] psp9000333:
hey Francisco, you've nailed it in the head with performance on R35. amazing. I feel though even without fast charge on it charges faster than before. maybe me getting used to charging without fast-charge enabled. also it feels a bit hotter than before, also from maybe me charging while in use. now just for me to test battery life. keep up the awesome work.

---------- Post added at 06:37 AM ---------- Previous post was at 06:35 AM ----------

yeah, noticed that too. hopefully this isn't an issue in r36.
[Nexus 5 Original Android Development] fbf2201:
Confirm, BT disconnections are gone.

Thanks!

Edit: unfortunately not - but now with r36 test build
[Nexus 5 Original Android Development] abra5umente:
I still get a bunch of high end fuzz. :(

Sent from my Nexus 5 using PA 4.1 with franco kernel
[Nexus 5 Original Android Development] silvan g:
Yes you can :)
[Nexus 5 Original Android Development] ben_pyett:
Also getting severe graphics glitches on 35, 90% of screen dark whilst remainder had fuzzy garbage, obviously makes device unusable, had to on/off screen multiple times on 35 in order to revert back to 34, where all is good, I do use LUX ? Any ideas?

Kernel running on default settings.

Bugger
[Nexus 5 Original Android Development] ironjon:
Yes now looks much better :D
[Nexus 5 Original Android Development] Shane_IL:
Brightness is working great for me now, thanks for fixing, great kernel (I had a quiet few days and got over 48hours out of my battery yesterday).
[Nexus 5 Original Android Development] 5FOOTER:
Are you using softkeyz? If so I went back to the chrome ones and did a full reboot and its fine now.

Destro warlock on WOW burnall
[Nexus 5 Original Android Development] outofthisworld:
I use softkeyz and lux. Don't have and have never had display/brightness issues with r35 or any Franco release
[Nexus 5 Original Android Development] carlese:
Another user said that BT disconnections are still there.. Are you using a car system or something else? I want to try r35 but I am afraid of BT disconnections..
[Nexus 5 Original Android Development] graffix31:
Isn't Bluetooth disconnects a known stock problem? I know while driving my Bluetooth drops and reconnects a few times on the way to work. Has since day one. I remember reading its a problem and still hasn't been fixed. Is their something else going on?
[Nexus 5 Original Android Development] chrisch91:
Brightness level is so low now, i have to swipe much more ro right for the same brightness like on r34. So if i swipe it inadvertently to the end of the left side, i narrowly can pick it again.
[Nexus 5 Original Android Development] fbf2201:
something else in r33 and r34...
[Nexus 5 Original Android Development] carlese:
I never had disconnections with stock or r32.. In r33 and r34 I had them.. Let's see if r35 is good :)
[Nexus 5 Original Android Development] scissors_cut_paper:
Franco you're awesome. R35 feels a touch faster to me, audio glitches are no more (believe me, I've just spent the best part of 2 hours trying to induce them.) No issues to report, feels like a keeper so far.
[Nexus 5 Original Android Development] :
I'm still having problems with my Pebble though, it still seems to disconnect on r35 in deep sleep. Using omnirom's stock kernel I have no problems in that regard.
[Nexus 5 Original Android Development] carlese:
What about reconnection? My problem with r33 and r34 was that it wouldn't reconnect, and I had to reboot in order to make it work..
[Nexus 5 Original Android Development] abra5umente:
I hope my audio glitches are gone too *fingers crossed*

Sent from my Paranoid Francoed Nexus 5
[Nexus 5 Original Android Development] :
Reconnecting seemed to work better
[Nexus 5 Original Android Development] jdec529:
It's amazing how the same phone can vary so much between users. I haven't had any BT issues on the last few kernels and I use it everyday. Also no audio issues, but I have also been using viper4android the while time also. R35 seems to performing very well so far. Thanks again Franco.
[Nexus 5 Original Android Development] salomaoa:
[MENTION=334712]francisco[/MENTION]

After flashing r34 and r35 I noticed that when the screen dims (a few seconds before it turns off) it stays so dark I can’t see anything. In fact, it stays as darker as when it actually turns off.

This is a problem for me, as I use an app called “Gentle Alarm”. During the night I use my phone as a watch. “Gentle Alarm” dimms the screen to a very low brightness but enough to see the time displayed on screen.

Now, the screen is so darker I can’t see anything.

Is there any way I can revert this?

Salomao
[Nexus 5 Original Android Development] momomok:
try these command in a terminal emulator:

su [ENTER]
echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer [ENTER]
[Nexus 5 Original Android Development] franciscofranco:
The minimum brightness is higher on r35 than on r34..........................
[Nexus 5 Original Android Development] rofik_gitara:
anyone have tried r35 work in touch control app?
[Nexus 5 Original Android Development] NeoEpsilon:
For me personally, R33's minimum brightness works best...

I work in a very dark room, and yet R35's minimum brightness is still too low... :(

The brightness in well-lighted room is good though...

Just my 2 cents... ;)

Thanx for your great works as always...
[Nexus 5 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] are there any issues flashing r35 on stock ROM that I should be aware of before I flash?
[Nexus 5 Original Android Development] franciscofranco:
r33's minimum brightness for the backlight led was stock, and I sincerely think it was too high. I may look at the code and figure out a way to not dimm the backlight too low, but if you don't like the feature you can disable it, the command is couple posts above.

No.
[Nexus 5 Original Android Development] GeekMcLeod:
Wrong thread. My bad.

Posted from under your bed.
[Nexus 5 Original Android Development] Tung_meister:
With r35 It's still possible to turn the backlight off completely with the backlight slider and rather than dimming after a period of inactivity the backlight goes off completely.
[Nexus 5 Original Android Development] Smoosh1:
[MENTION=3292224]franciscofranco[/MENTION] How about putting an option in the next release of FKU which allows the user to set the min. brightness, e.g. value 0 would be stock and like -3 would be the r35 setting.
[Nexus 5 Original Android Development] qsec:
BT reconnection to my car's BT phone system is still wonky. Sometimes i have to toggle BT to get it to connect. On 32 it works just fine for me.

No biggie.
[Nexus 5 Original Android Development] ben_pyett:
Upgraded again to 35 no issues after a few hours? What was that all about, glad I want alone with experiencing the graphical glitches...
[Nexus 5 Original Android Development] Tzfardaya:
seems the worst issues for bt on 33/34 was with LE devices, such as the pebble smartwatch... Yes, stock rom/kernel did (does?) have issues with certain devices, but I think that's more dependent on the individual device rather than the rom/kernel that our phones are using...

For me, I use 3 bt devices on a regular basis... one connects without issues, the second sometimes takes a second try to connect, and the third has to be forgotten and re-paired every time I want to use it... (that one's annoying) but it was the same on stock as with the various francos...
[Nexus 5 Original Android Development] granets:
I am sorry to report that the right channel still skipps on r35 when I pump up the volume above the stock values. To recreate - pump up the headphone volume boost in FKU (anything above 2 seems to get it to skip, a value of 1 also produces skipping at max volume. Gain is at 0), play some music, get volume to max or 1 notch below max and listen to the epic skipping... Going back to r32. Can I provide you with any type of log [MENTION=3292224]franciscofranco[/MENTION] to help you resolve this issue?

edit : here is a logcat. did it by raising volume while it started skipping and then recorded it. hope it helps.
[Nexus 5 Original Android Development] franciscofranco:
No, it just goes really dimm.

Maybe, maybe not, we'll see.

Ok I don't know at this point what might be. A Kernel log and logcat of that problem would be helpful, I don't know at this point.
[Nexus 5 Original Android Development] franciscofranco:
Yeah **** it, I'll start with a clean repo today, merging a gazillion patches from CAF is probably not a good idea, BT issues that I don't know where they started, audio with problems in the right channel, memory problems after using the phone for a while - I'm done :) I'll start after lunch, should just take a couple hours.
[Nexus 5 Original Android Development] granets:
Don't rush it :) We all love your work, but I'd rather you be happy, then frustrated that something doesn't work. As stated in your changelog r32 is the last "stable" release, so I concider the later releases sort of tests of new features, so it is expected there will be some issues with them. Take the day off, relax and start tomorrow in the clear. I can't wait to see what comes next. If you need testers, just say the word. Here to help you with what I can.

Have a nice day :)
[Nexus 5 Original Android Development] franciscofranco:
I'm not rushing, just don't want these later "experiments" to be like this - hate problems that I don't understand where they come from & why they are happening & cannot reproduce.
[Nexus 5 Original Android Development] PainfulLover:
And when you're full, work on the kernel.