yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] wilson289:
I have a great idea, how about these hecklers here compile a FAQ page themselves and link you so that you can add it to the OP? That way, they can spend the hours and hours of time finding every particular question that every other person has and provide it for everyone else with their free time (seems like they have a lot of it)! Meanwhile you (Franco), can do what you're best at (dev) :D. Flashign r9 right now, super excited!
[Nexus 6  Original Android Development] blueren:
This is still happening? I believe this was fixed in the latest FKU update. Are you using PAM?
[Nexus 6  Original Android Development] wimmetje:
Flashed r9 :thumbup:
[Nexus 6  Original Android Development] blueren:
*Thumbs Up* Along the same lines, what are the chances of you adding a SElinux Enforcing / permissive toggle within the app? If it's security issues, maybe add a warning to the users about the implications?
[Nexus 6  Original Android Development] Nocturnal86:
Are you live vewing the min frequency with system monitor? Or are you just using FKU to view min frequency? (FKU shows you the active min frequency which changes dynamically as you touch the screen so it can/will be different than viewing the live min frequency with an app while the phone is idle)
[Nexus 6  Original Android Development] codygs83:
No worries man.

These issues were already discussed here and I believe have been corrected by yourself in recent updates.

I havent used it in awhile and probably won't for some time to come simply for personal preference.

But just wanted to let you know as always your work is top notch and is always appreciated.
[Nexus 6  Original Android Development] kergefarkas:
There was some discussion about this that some ROMs have built-in performance profiles that override franco's/FKU's settings.

If I remember correctly, you need to disable those built-in in the ROM, and FKU should work just fine.
[Nexus 6  Original Android Development] zephiK:
There's already an app for that, https://play.google.com/store/apps/details?id=com.mrbimc.selinux
[Nexus 6  Original Android Development] noneabove:
Nvm, maybe it was my battery level.. Even though power saving hadn't kicked in, its going above 1.7 now
[Nexus 6  Original Android Development] big_adventure:
Still the same issue

Hi Franco,

I'm still experiencing a strange problem, one which has changed slightly from before.

A while ago, I posted that min_cpu_freq was forcing itself to 1728mhz on every boot. Here was the scenario: Boot phone, wait ANY amount of time over a few minutes (so, long enough for "boot completed"), open FKU, go to CPU Manager tab, Min CPU freq was 1728. Setting it back to 300 took care of that, no blood, no foul, until reboot. Configuring 300 and ticking set on boot changed nothing - rebooting the phone would come back with 1728mhz, only with set on boot still ticked.

Checking CPU states in BBS, after an hour or more of run time would show only 1958mhz (my max), 1728mhz (the min decided upon by... something) and Deep Sleep as used frequencies - so it's not just a display artifact, on boot, my min freq is setting itself too high.

I cleared FKU data, rebooted, and everything seemed fine on one boot - min was 300, as expected. This was running r7.

However, the next time I rebooted, flashing r8, min_cpu_freq was now forced to 1190, 20 minutes after boot. The only states used were between 1190 and 1958, plus Deep Sleep.

Manually setting it back to 300 worked until the next boot - just this morning, when I flashed r9. Min CPU was fixed at 1190 20 minutes after boot. I set it back, and it stays set (I check frequently to ensure this).

Something is causing this, I don't know what it is. My ROM is stock, I'm encrypted, the only mod I have is the power.shamu.so to force D2TW (before your app supported it), I don't have any other CPU or system control apps - no Trickster, no CPU anything, nothing of the sort. The only settings configured in FKU are Charging LED disable, max CPU 1958 and RGB values - everything else is bone stock. I have Greenify running, just to hibernate Facebook and 3 games that won't shut up even if notifications are turned off.
[Nexus 6  Original Android Development] kergefarkas:
Those seem to be the kernel default values, which are set every time you flash the kernel.
[Nexus 6  Original Android Development] rauschkugl:
But isn't the setting there to show and set the minimum frequency that can be reached?

When I understand correct you display the frequency that is present when fku is loaded which just would be wrong in that context.

The info text also says that this is the minimum frequency that the cpu supports.

This happens only when fku is opened the first time after reboot for me. If I then set the min frequency to 300 and open the app again different times after that the min frequency will always stay at 300.

I also had this and min frequency was set to 1700. But this was also the min frequency used until I set it back manually. It never went down to 300 before that and my battery died within 3 hours sot.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] ScumDroid:
For all your hard work. Thanks man.

Confirmation number: 3W183235421151425
[Nexus 6  Original Android Development] GoldfishTX:
Please forgive the OT post, but what do you have to be grateful for? I can't imagine that all the time you put into something you're obviously passionate about is extremely lucrative. It's not like you are stacking up cash while people's lives are ruined by your kernel. It's a hobby. Modding your phone doesn't matter. It's not important at all, and it's totally unneccessary. Instead of celebrating the fact that we all get to buy expensive phones and break them for fun, people here are crying about a bug in a piece of FREE software, when 99.9% of them don't even understand what a kernel is or how it works. These people need to step away from their computers, go outside, and stop being keyboard cowboys. Keep up the good work.
[Nexus 6  Original Android Development] dtroup64:
Just wanted to thank you for the ridiculous amount of work you're putting into this. My N6 is just about perfect.

Confirmation number: 6JU19783UN598141A
[Nexus 6  Original Android Development] Svid:
Humm sorry for the totally noobish question but where you donate to him to get confirmation number?
[Nexus 6  Original Android Development] occtec:
PayPal ;)
[Nexus 6  Original Android Development] Svid:
Sorry i was awake the whole night my brain is fried :)
[Nexus 6  Original Android Development] poczynek:
Sorry if this has been asked before - I searched and there was nothing under 'wake gestures' - but any chance of wake gestures implemented like lean and flar's? I'm just addicted to sweeping up to wake as I think it's way more intuitive than double tap. And there's no discernable battery drain.
[Nexus 6  Original Android Development] kergefarkas:
I'm almost 100% sure franco said he won't implement sweep to wake, only DT2W, which is already implemented.
[Nexus 6  Original Android Development] poczynek:
Bummer.
[Nexus 6  Original Android Development] kergefarkas:
If I remember correctly there are some apps that enable that feature as well (or mods).
[Nexus 6  Original Android Development] TheySaidWhat?!:
Speaking of mods, I would to ask a question about the FK updater app. I got the paid version and the file manager shows an option to flash a G app zipfile in my download folder?! Can the app be used for zips other than updates when manually selected in the file manager?!
[Nexus 6  Original Android Development] poczynek:
Not that I've seen? Flar's implementation is great - would love it on Franco's.
[Nexus 6  Original Android Development] paychex:
Something else is causing it. Otherwise everyone's min would be stuck there.
[Nexus 6  Original Android Development] cobyman7035:
Ah finally no more jumpy cores

R9 FTMFW

But cores 0 and 1 don't hit 300mhz much wen idling

Can't have every thing lolz

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] Fadakar:
Anyone having trouble with themes failing to install?
[Nexus 6  Original Android Development] garylgray:
Yeah I was. I think some things may have been left out in this kernel. I'm using the new Sensei R49 and everything works.

Battery and performance aren't as good as Franco's R9 tho.

I'm sire Franco will have it all worked out for R10. Can't wait. ?
[Nexus 6  Original Android Development] kergefarkas:
Yes, me too. I already posted this to the CM12 thread, since I tought it is ROM related and not kernel issue.

http://xdaforums.com/showpost.php?p=58294242&postcount=405
[Nexus 6  Original Android Development] wmfreak:
Use SELInux mode from playstore to change to permisive and themes will install
[Nexus 6  Original Android Development] inffy:
It seems the r9 really made the battery better. I can already see much lower idle drain.

Great job
[Nexus 6  Original Android Development] LillieBennett:
Yeah! Keep on keep'n on! I love your attitude, this is computing not a political committee! I'm an old dinosaur burned out developer and agree completely!

On the issue with min CPU frequency not sticking; show both the user static setting and the dynamic setting. Looks to be plenty of room in fku.
[Nexus 6  Original Android Development] stas333:
R9 is working great here.
[Nexus 6  Original Android Development] Krunk83:
Figured out how to stop the unlocking animations stuttering with custom kernel. Changed my DPI to stock and the stuttering has stopped. FYI for those who might have the issue (though I'm sure no one cares. Lol)

Nexus 6
[Nexus 6  Original Android Development] funcrusher:
I have it and have never changed my DPI. :/
[Nexus 6  Original Android Development] Krunk83:
Do you get it on the stock kernel too? I had no stutter on stock kernel.

Nexus 6
[Nexus 6  Original Android Development] funcrusher:
No, never on stock. Only on three custom kernels I've tried.

PM me if you want to compare notes on the issue.
[Nexus 6  Original Android Development] Circaflex:
Thanks franco for all your hard work. Loved your work since using it on hammerhead, your app is top notch and very polished. Thanks again for everything you have done for the nexus community.
[Nexus 6  Original Android Development] Beast84:
Now that you ask, it does seem more reliable. I never tried the power.so option, just the app but it seems like it's working better
[Nexus 6  Original Android Development] franciscofranco:
No, that is placebo. As I said before, couple pages ago, it doesn't matter, it's just a enable/disable option, nothing else.
[Nexus 6  Original Android Development] big_adventure:
I completely get that. I'm wondering what could cause it, however. As stated, I've got nothing on the phone that should be able to do such a thing.
[Nexus 6  Original Android Development] Beast84:
Well thanks for the clarification. I guess it is just placebo. I just noticed I can do the double tap faster with yours enabled. With the app, the second tap had to have a little delay. But either way, it works & it's nice to have. Thanks
[Nexus 6  Original Android Development] dan04103:
In regards to francos app, I have noticed if you select the setting you want before checking the box the setting stays. I always clear app data after an update and re-setup settings afterward. I get reliable results this way. Maybe this will help someone. Cheers!
[Nexus 6  Original Android Development] dhufford81:
Hey franco, love the app and the kernel. I appreciate all the work you do for this community of entitled tech illiterate non reading whiners. I've donated a few times and will continue to do so regardless of your attitude or comments. I deal with retards all day on PC's and laptops, it can be very trying on the patience. Just keep doing you bro.
[Nexus 6  Original Android Development] wrongway213:
Franco, a little bit of contrast to all the questions - just wanted to say r9 is great! Thank you on behalf of the crack flashing community for the merging the commits to work with theme engine and pie so I can run any ROM I wish with the kernel I personally feel my Nexus was meant to be run with. Nice to see the cores being tweaked as well, seems conservative is getting better SOT with each release but performance is just as snappy. This is why I like to use your app, when I flash your kernel, you have it optimized. Every release runs better than the last, and if it doesn't, it sure is fixed quickly.This release in particular gives me a very good feeling about the potential of the conservative governor. Excellent work as always.
[Nexus 6  Original Android Development] cobyman7035:
Anyone else cannot backup kernel? I save a backup in fku… exit app… go back into it.. The backup screen is empty?

Via my Le Pan 8" mini on Tapatalk⁴™ Pro
[Nexus 6  Original Android Development] wrongway213:
No issues here, I still have backups through r2.
[Nexus 6  Original Android Development] franciscofranco:
Fix your root permission for FKU.
[Nexus 6  Original Android Development] ironjon:
Agree, r9 is fantastic with conservative governor.

Excellent work Francisco!

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] paychex:
You have nothing on your phone you think would do that. But you have something that is.
[Nexus 6  Original Android Development] big_adventure:
OK, to recap...

If I clear data in FKU, this doesn't happen on the next boot. Ever - multiple tests here. But it does happen if I don't clear data first. And to take THAT a step further, if I clear data, then set colors and makes them set on boot (to the popular 237,235,250), my min CPU is fine, still 300. But if I set anything else that I've tried to set on boot, my min CPU gets messed up after the next boot, and stays that way until I manually set it back to 300.

This makes it hard to attribute the situation to another app, since it doesn't happen without modifications to FKU only.
[Nexus 6  Original Android Development] TheAnarchist1:
[MENTION=3292224]franciscofranco[/MENTION]

I did a forum search, and could only find two minute posts with no resolution about this issue. I have noticed occasionally while running this kernel that the screen of my device seems to split, with the right half presumably frozen, and the left half sort of working, but highly lagging. Typically a full reboot, or switching off the screen and switching it back on seems to momentarily fix the issue until it crops up again. Unless I am missing something. Would you be able to provide me with a few pointers as to what exactly could be causing the issue?

I am running a pretty basic configuration, minimal gapps, Pure Shamu 3.97, and your latest nightly.

Thanks.

Pardon if I missed a post where this was resolved or discussed more.
[Nexus 6  Original Android Development] akellar:
Happens on stock to some people as well, not a kernel issue
[Nexus 6  Original Android Development] chrisg1548:
Hey guys, switched from elementalx to Franco and loving it but does this kernel have turbo charging enabled, asking because it seems that it charges slower on this kernel, any thoughts
[Nexus 6  Original Android Development] Krunk83:
This happens on stock DPI?

Nexus 6
[Nexus 6  Original Android Development] TheAnarchist1:
Thanks guys.

I have no clue about stock dpi. I am using whatever Pure Shamu comes set at. It is driving me crazy. I tried upping the device voltages a bit, figuring that maybe the device was too low (different devices different thresholds) and I am attempting to see how that works.

For those that are interested. I did a little digging into the dpi and I am at stock.

It seems to act up most when I am in the franco kernel app
[Nexus 6  Original Android Development] akellar:
Again, not kernel related http://xdaforums.com/showthread.php?t=2949162

Half of screen not working
[Nexus 6  Original Android Development] Damon13:
It happened to me when I switch from Elemental to FK, I had to reinstall the unencrypted stock kernel and start fresh with Franco. Remember to do a backup cause it will wipe your data and will need to start fresh. R9 is a beast and so far its been great!
[Nexus 6  Original Android Development] TheAnarchist1:
Once again [MENTION=3470254]akellar[/MENTION]

I appreciate the link, but I have already seen that, and it only seems to be happening on here for me. Not on any other kernel, so it may just as well be that. I have noticed that when it happens, all the voltages in the franco app bottom out completely.

---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------

Yeah.... I am unencrypted Damon. I did the whole flashing the force decrpytion boot, fastboot format userdata, started from scratch.
[Nexus 6  Original Android Development] franciscofranco:
It's a bug that exists even on 100% stock configuration. I'm mostly inclined to a bug on the video subsystem. Google + CodeAurora guys that work with Google butchered the MDSS (video/display) subsystem. I've read the entire commit history since the Google started to bring up Shamu's hardware, there are a couple interesting commit messages about some bugs they had but couldn't fix in time so they put a couple bandaids until the root cause it's fixed. We're not even using the full potential of the display power saving capabilities (called mdss idle power collapse) and there's a 10mA power hit by not having it enabled. There's nothing I can do about it, the video subsystem is a complete cluster**** of hard code. The only guy that claims to know the subsystem is Kondik. I don't even dare to try and fully comprehend it beyond the basic. Sorry dude, you gotta wait for the next OTA.

Uh? Turbo Charge is Kernel agnostic it works on all Kernels/roms. If you mean by USB fast charge I enabled it by default and it charges the same rate as flar's Kernel (900mAh).
[Nexus 6  Original Android Development] akellar:
So I've shown you proof that is happening to random people and not kernel related yet you continue to insinuate it's Franco related. Good luck then.
[Nexus 6  Original Android Development] TheAnarchist1:
[MENTION=3292224]franciscofranco[/MENTION]

Much thanks dude for the well-composed intellectual response! That is why I love using your kernels. Much more helpful than simply telling me yes or no, or leading me on to believe that it could be hardware related (sorry [MENTION=3470254]akellar[/MENTION]) . I am a person that wants to know, loves to know, what exactly is up with everything, rather than just going through yet another RMA.

So you are lead to believe that it is software then as well? I have been messing with settings attempting to reproduce, and for some reason it kept happening in your kernel app, no insinuations against your work or anything

Once again. I appreciate the response and let us hope for a sturdy 5.1! I really would hate to mess up my beautifully installed invisible shield (god knows they are a total hit or miss with installation) for something that is software :)
[Nexus 6  Original Android Development] franciscofranco:
I'm assuming that it's software, I don't know the real cause. I can be either right or wrong. What I know is that it happens regardless of the rom/Kernel you use. The rest is up to you.
[Nexus 6  Original Android Development] hondarider525:
Does anybody know if I update the kernel, if I have to run VomerTweaks again?
[Nexus 6  Original Android Development] michmeister:
Not to be rude but if it only happens on this kernel, seems the logical step would be to use different kernel.
[Nexus 6  Original Android Development] estanenmi:
franco.. thanx for ur amazing work in kernels... one future i think will be great is multirom can u do ur magic?

Enviado desde mi Nexus 6 usando Tapatalk 2
[Nexus 6  Original Android Development] zephiK:
MultiROM isn't supported on the Nexus 6.
[Nexus 6  Original Android Development] wrongway213:
No, as long as the script stays installed, it's installed. You can always check your max freq to make sure it's lowered down to where it should be with VomerTweaks installed (1267) from stock Franco kernel (2649) to know if it's been applied.
[Nexus 6  Original Android Development] Mickey Meyers:
Whenever i install a theme, it says theme could not be installed :confused: running r9, on cyanogenmod nightlies.
[Nexus 6  Original Android Development] cmo220:
This certainly isn't a kernel or ROM bug. It happens to some phones, mine is one. I have no idea why. I"m thinking possibly something about that memory leak bug, but just a guess. I have that problem too. It's happened on complete stock and different ROMs and kernels. A good friend of mine had his N6 a week before me, and then started using this kernel since the day it came out has never seen the problem. I've seen thought it's a hardware issue so I have a new phone on the way just in case.
[Nexus 6  Original Android Development] gamewarden234:
Download a selinux mode changer from the play store and change to permissive
[Nexus 6  Original Android Development] christianrance:
Francisco,

Just reading through the latest comments. Thank you for all your hard work and time that you put into this project. Bugs or not your work is top notch. Just donated the max amount you offer. Keep it up!!!
[Nexus 6  Original Android Development] Cy_n_ic:
I also wanted to share my gratitude after seeing so much collaboration between kernel devs and rom devs alike to get everything up and running like it is so far. Teamwork will assure that this device continues to be epic for a long time to come.
[Nexus 6  Original Android Development] inffy:
No. It has nothing to do with selinux mode.

Old cm11 themes won't work with the cm12 theme manager
[Nexus 6  Original Android Development] stormtroopercs:
I have the same problem. It doesn't install cm12 themes at all. It says it fails to install. So it's not him doing it wrong, there is something not working correctly, kernel or ROM.
[Nexus 6  Original Android Development] soundneedle:
Shutdown

My nexus 6 has been shutting down after upgrading from r8 to r9. I'm also on the latest sinless rom. This has never happened before, but upgrading to r9 might just be coincidence. I've since downgraded back to r8 hoping it's indeed a kernel issue.

Anyone else getting shutdowns on r9? The only change from default settings (fk app) is enabled tap to wake and turned off led.

Ps... I missed my wake-up alarm today too since the nexus turned off... Battery was 100% so not a battery issue.
[Nexus 6  Original Android Development] Circaflex:
no such issue all day here.
[Nexus 6  Original Android Development] redsmith:
I have found that switching kernels allows me to install themes. I return to Franco after installing (or updating) a theme.
[Nexus 6  Original Android Development] wrongway213:
No need, you must be switching to a permissive kernel. Just download selinux mode changer from the play store and set Franco to permissive, then theme away
[Nexus 6  Original Android Development] kergefarkas:
I had the same problem, switching to permissive selinux solves it.
[Nexus 6  Original Android Development] cobyman7035:
With su? Or shud I just try uninstall… the reinstall again?

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] numerouknow:
+1

no issues whatsoever. moreover i can see that battery drain while idle is considerably less with r9.
[Nexus 6  Original Android Development] rivas741:
Im kind of a noob but, I have what I think is a bug/problem. When I go into CPU settings the Min and Max are both 1.7 GHz. I've cleared app data and reflashed r9 and the problem still persists. Is this normal?

I'm on r9 & on stock ROM.

Edit: wait nvm. I guess that's just how conservative governor works. ?
[Nexus 6  Original Android Development] inzaghi75:
Does this kernel supports led?
[Nexus 6  Original Android Development] kergefarkas:
Yes. You can enable/disable it in FKU.
[Nexus 6  Original Android Development] inzaghi75:
Yeah. But only for charging. I mean for notification. I'm using a 3rd party app.
[Nexus 6  Original Android Development] Ladduro:
Franco, do you see any problem greenifying your app? I dont use per app profiles and most likely will lose battery stats (I dont really care about them). Also I have color correction set up on boot, but it should not be affected by greenify.

If you have time to reply, please let me know.