yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kerngehirn:
I highly doubt that. I think fku is requesting permission constantly. The notification normally appears when I change settings and fku requests permission from superuser.

My superuser app has never done that before and doesn't bring up notification from other root apps.

---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------

I don't use per app settings.

---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------

Thanks for searching the post. That's not what I did. My settings make sense.

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------

Thanks for searching the post. That's not what I did. My settings make sense.
[Nexus 4 Original Android Development] Bill Gamble:
I suggest clearing fku app data then rebooting.
[Nexus 4 Original Android Development] limeaide:
If you are not using per app power modes did you check the disable per app modes in settings?

Barring that I doubt its fku and either rom or super user related.
[Nexus 4 Original Android Development] jyuuken:
Hi guys i have been using this kernel and attached is my battery.usage with h+ always on. Settings are sligthly speedy and deadline. uv -100. im at 18% Do u think i can improve on battery further? Thanks!
[Nexus 4 Original Android Development] jyuuken:
SOT is 2hrs and 53 mins
[Nexus 4 Original Android Development] Gokh:
No, nothing changed with kernel settings
[Nexus 4 Original Android Development] Shano56:
I get that after tapping -25mV in the f.Ku app a couple times , seems to flood superuser with a bunch of requests.. Workaround is to disable toasts in your superuser app settings.
[Nexus 4 Original Android Development] Redneck Trash:
[MENTION=5141720]kerngehirn[/MENTION] I probably should've had a cup of coffee before checking the forums. For whatever reason I thought it was happening with all your apps that needed superuser permission. My mistake.
[Nexus 4 Original Android Development] kerngehirn:
I thought of that. But then I thought how the app data could possibly affect the superuser requests.

But it worked. Thanks. I hate to do that. I undervolt every CPU speed with a different amount of mV.
[Nexus 4 Original Android Development] Shano56:
No need for coffee after flashing Franco kernel, the vibrator is enough to wake a mummy xD
[Nexus 4 Original Android Development] 777.300:
Switch of notification for the FKU app in SuperUser.

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] JeffyLube0:
This address might be useful :

01010010 01100101 01110100 01100001 01110010 01100100 01100101 01100100

Very subtle ;)
[Nexus 4 Original Android Development] nuwan32:
Hey guys I gotta couple problems. If anyone is experiencing something similar let me know.

1. Sometimes, very rarely my battery does not charge fully. I leave it on charge over night and it only charges up to 89% this happens like once a month maybe. I don't have any battery saver options on and fast charging is off. My phone doesn't get hot either so that's not the problem.

2. Every time I restart my phone fku preferences get reset to defaults. I don't have clear app data checked or anything either so it's really annoying, having to reset settings each time I restart the phone.

Any help is appreciated, also I'm on the latest beta with pa 3.65
[Nexus 4 Original Android Development] mjehan:
Franco are you using the new leaked 0.83 radio ? Any feedback would be helpful.
[Nexus 4 Original Android Development] drawde40599:
Everyones radio experience is going to be different, 83 worked great for me for data speeds, but killed battery and distorted phone calls. Others in radio thread say its perfect, . Its one those things u have to try yourself
[Nexus 4 Original Android Development] drawde40599:
What have already tried to fix? I thought i remember seeing franco reply to someone else using that same rom, that it was rom issue
[Nexus 4 Original Android Development] nuwan32:
Well I've tried to fix both but I don't know what to do to fix it
[Nexus 4 Original Android Development] drawde40599:
If was me and no one else was reporting issue in this thread or PA thread, i would start fresh, uninstall the app, reboot, make sure its not still in data/data /(it has "hidden" there for me in the past) remove SU permissions, reboot reinstall app c if that fixes it. If not i would make a backup of rom, do a FULL wipe and c if that fixes it .(im assuming u already tried dirty flash) If still not working id blame the ROM (no one here has the issue) and try on stock or AOKP or another stable rom. Thats just me and what i would do . Hope that helps

Edit! U r using this build of franco kernel right? Not one of the others?
[Nexus 4 Original Android Development] SpasilliumNexus:
I have a question about USB Fast Charging on the N4 with this kernel. I'm still learning new things about this phone as I just got it about a week ago.

On my S3, when USB FC is enabled, I can't access my phone's files via USB on my PC until I turn off Fast Charging. On my N4, whether USB FC is enabled or disabled, I can still access my phone's files via USB on my PC. Is that how it works normally on the N4?

Thanks in advance.
[Nexus 4 Original Android Development] wathefak:
When usb fc enabled you could try disconnecting and connecting, the second time you connecting your phone via usb, it won't be accessible.
[Nexus 4 Original Android Development] nuwan32:
Yea I'll try uninstalling the app, but I don't wanna do a clean install, it's too much work and not worth the effort :p
[Nexus 4 Original Android Development] franciscofranco:
Hey guys, still on vacation but I just wanted to drop by to release r164 which is what I've been testing for the past 10 days. I didn't code anything during the vacation so I'm just sharing it. If Google drops 4.3 on Wednesday this should be the last release for 4.2.2.

By the way I'll be on vacations until the 29th, I won't be much active on XDA until then so keep the thread clean and happy. Help each other :)

r164:

* Slight change on how the Hotplug driver takes care of the cpus. The deciding algorithm is the same with 0 changes, but now cpu0 load decides if cpu2 comes online or stays offline and cpu1 load decides the same for cpu3. So its as if cpu0 was tied to cpu2 and cpu1 to cpu3, theoretically speaking.
[Nexus 4 Original Android Development] anazhd:
updated :D gonna give some feedback soon
[Nexus 4 Original Android Development] ShinnAsuka:
Did anyone have trouble using auto flash from the latest FKU app update? Just tried updating to r164 and auto flash just hanged... Had to download the zip first then press on the notification once it finished downloading to flash it...
[Nexus 4 Original Android Development] franciscofranco:
Worked fine here.
[Nexus 4 Original Android Development] drmclove69:
Keeps happening to me where my phone randomly reebots and then right after it starts up, FK app is updating. Don't think its a coincidence anymore since its happened every time now.
[Nexus 4 Original Android Development] ShinnAsuka:
Maybe it was just random... I'll try again on the next nightly :)
[Nexus 4 Original Android Development] Shano56:
Love how you say vacations xD have a fun time!
[Nexus 4 Original Android Development] marocampos:
Yeah, same thing happens to me, but it's more often. I expected some forced shut downs, where the screen just turned off and the phone didn't turned on. I had to connect it to the charger to make it come back to life
[Nexus 4 Original Android Development] nuwan32:
What happened to you, 1 or 2? I never get forced shut downs or random reboots thankfully. Also it might be worth mentioning I'm uv'd -125 mV across the board
[Nexus 4 Original Android Development] marocampos:
Just 1. I'm also undervolted -125 mV, but I think my problem must be the battery, as all forced shutdown I got were when battery level was 10% or less.
[Nexus 4 Original Android Development] anazhd:
For problem number 2, did you check the set on boot options ?
[Nexus 4 Original Android Development] Hypoxic1:
Same. And I just uninstalled FKU & reinstalled fresh a few hours later.

Tried "auto-flash" & it just rebooted (nothing happened in notification bar). Tried to just "download," but can't find it in my phone ANYWHERE.

FKU issue:

Restoring per-app settings on a fresh install loads ALL of the per-app settings that I had ever made. I made around 45, lets say. Then I BACKED UP PER-APP SETTINGS. Then I ended up changing values around & deleted a few of those per-app settings over time. So now I've got around 20 per-app settings. Clicked backup settings again.

Uninstalled FKU. Installed FKU and clicked restore per-app settings & it loaded all of the original 45. Included in those were those other 20 that had updated values. So it looks like the old per-app settings are not really deleted. Made it a pain to check each one.

So, DELETE PER-APP SETTINGS only removes from list but keeps the xml file insteading of truly deleting it.
[Nexus 4 Original Android Development] Nocturnal86:
So r164 enable the 3 core option when needed? Or has that always been happening? I just payed for system monitor and noticed this and I thought that r163 would go from 2 to 4 cores only.
[Nexus 4 Original Android Development] nuwan32:
Yea as I said on my first post,I have.
[Nexus 4 Original Android Development] :
You answered your own question FYI, yes r163 has two modes 2 and 4 cores, seems r164 has three modes 2,3 and 4 cores
[Nexus 4 Original Android Development] Nocturnal86:
Thank you. Guess whats left to see if that improves battery and performance a bit!
[Nexus 4 Original Android Development] albundy2010:
164 is behaving strange. Cleared app data and rebooted to rule that out.

It doesn't online the other cores as quickly as it should. The cpu hits a high enough load and they are still offline. Happens in reap world usage like loading up the new maps or earth.

Also the speed seems to get stuck at 1350 instead of going to up to 1512.

Even when I fired up AnTuTu it took about 3-5 seconds to online the cores. And it maxed out at 1350. No temp issue either.

I have no per app settings and that service is disabled. No other kernel apps or scripts etc running.

Since franco said he was running this for 10 days I though maybe it was a Derp on my part but now I doubt that.

Anybody else notice this?

Maybe the local build franco has been testing is different than the one he pushed as 164 is my other guess.

Edit. Flashed back to 162 and everything is running as normal. No settings changed.
[Nexus 4 Original Android Development] LMR1200:
Hi all, does anyone else also have too loud headphone volume when calling? I tried the option in FK updater at Headphone volume and set to -11. Didn't work for me. Also have searched everywhere at xda, but nothing found.

The headphone volume is still too loud when calling. BTW, when playing music, it's perfect! So, only too loud when calling.
[Nexus 4 Original Android Development] ghul21:
Had two ota for the #164 ?!? :what:

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] vecino:
FKU (latest testing) issue: I set max GPU speed to 200MHz - change is ok but after reboot phone is GPU again set to 400Mhz.
[Nexus 4 Original Android Development] limeaide:
I also had issues updating via the auto flash. Took me three tries to get it to work.

Sent from my Nexus 4
[Nexus 4 Original Android Development] RiThBo:
Franco - would it be possible to add a "while charging" profile please?

EDIT: BTW - I also had issues with auto-flash
[Nexus 4 Original Android Development] alucard8888:
Same here, its too loud even in the lowest volume.
[Nexus 4 Original Android Development] otariq:
Just had a random reboot trying to pull a log cat for the first time. I'm using terminal emulator and tried to push the log cat to the SD card it creates a file but its at 0bytes and terminal just says waiting for device what am I doing wrong?
[Nexus 4 Original Android Development] Pure Drive GT:
R164 unusual behaviour

[MENTION=3292224]franciscofranco[/MENTION]

After reading this I cleared app cache and data then uninstalled app, flashed r164 manually with fastboot, freshly installed FKU with stock settings and wanted check the above mentioned issue. To check this I just ran System Monitor and started Minion Rush, immedeately I noticed the lag and the reason was that only two cores where onlne cpu0 and cpu1 and both hopping only up to 1.4 (1.35) GHz, exactly how described above. Either we both are derping big time or something went slightly wrong with the kernel.

If you see this before your "vacation" get over don't spend too much time searching for some bug, simply enjoy your time off and be assured that, if this really is a kernel issue, we still have r163 which is quiet brilliant.

BTW: Do any of you people have reboots/crashes when closing games? Sometimes when I close a game by going back or with the exit button of the game itself my phone simply freezes or crashes and then reboots. This is very irritating and it also happens that I lose some settings after, for example Wallpaper. This does not happen if I exit with home button are swipe away in recent apps. This problem has happenes to me with WindUp Knight and Muffin Knight. I'm 99% sure it's not kernel related but I would simply like to know if other people have this issue and on what roms they are. I use CM10.1.2
[Nexus 4 Original Android Development] drawde40599:
Seeing same behavior here, it's acting like 1350 is max
[Nexus 4 Original Android Development] Redneck Trash:
I'm not seeing this issue.
[Nexus 4 Original Android Development] Hypoxic1:
YES! I, too, have this exact same issue with Defense Zone 2 HD. The game has a "QUIT" button within it & does same thing you described.

stock ROM & r163 - Latest FKU - no UV
[Nexus 4 Original Android Development] drawde40599:
Try watching it with floating cpu monitor on that app, i didn't think i was either it was acting normal then about 5-10 min later it started doing like that guy described, ill look at it more tomorrow.
[Nexus 4 Original Android Development] Redneck Trash:
My max is the default 1512 and clearly my CPU ramps up to that.
[Nexus 4 Original Android Development] albundy2010:
Cpu stats won't tell you the story. It hits 1512 plenty during boot and the initial media scanning load stuff up phase. But it will Derp soon after. .

Seems something is going wrong once it starts the new hotplugging with the paired cores. Haven't dived in and test it enough to pinpoint it

But no doubt about its there is a derp in that kernel build.

After reading your post I froze the franco app and flashed back on 164 again.

As somebody just said. ( sorry to lazy to go back out this reply to look at who) watch in in real time.
[Nexus 4 Original Android Development] hencke:
[MENTION=4499330]otariq[/MENTION]

Remove the adb. Adb is for when you have the phone connected to your computer and want to run the command from the computer. Basically with your command your phone is waiting for you to connect another android device. So if you just remove the adb-part of the command it will run locally.
[Nexus 4 Original Android Development] Taxiback:
Does the AUTO-FLASH not work any more, I have v10.1.1.2 and all it seems to do when I press AUTO-FLASH is download the file, talking of which, were does that file go as I've downloaded it at least 6 times.
[Nexus 4 Original Android Development] albundy2010:
Your method of determining that there isn't a problem just is not a useful way at all to see what the cores are doing in this case at all.

It's actually completely useless.

Two more screens to make it even more clearer than it already was.

First is 162. Second is 164
[Nexus 4 Original Android Development] Hypoxic1:
LOL, exactly! I'm going to be out of storage space soon! :silly:
[Nexus 4 Original Android Development] drawde40599:
Should go to, Sdcard/
[Nexus 4 Original Android Development] alanwyl:
I was surprised to see the img show up in the backup after I use auto-flash. Good job Franco.
[Nexus 4 Original Android Development] Pure Drive GT:
On default settings my phone simply did not hit 1.5 not even at/after boot but then I changed treshold to 0% so that all cores would be online and now it hits 1.5 again. No clue what is going on. But even with 4 Cores going up to 1.5 Ghz and max 400Mhz GPU Minion Rush lags at the intro and after just a little bit this is of course compared to r163. I have no clue what's going on, I'm simply sharing my observations.
[Nexus 4 Original Android Development] :
I noticed this awhile back, it lags even on 0% High Load on Minion Rush but everything else works beautifully and battery life is improved so I don't see the problem. On stock N4 kernel its smooth as well as other phones stock kernels such as Note 2
[Nexus 4 Original Android Development] Pure Drive GT:
Stop the ass kissing

LIKE I SAID THIS IS COMPARED TO R163, GUYS PLEASE STOP THIS FRANCO KERNEL IS PERFECT BS, IF SOMEONE REPORTS ANY KIND OF ISSUE LOOK INTO IT SINCERELY AND THEN MAYBE IT MIGHT BE HIM DERPING OR NOT, BUT DON'T IMMEDIATLY TRY TO BRUSH IT ASIDE.

The only way we can help Franco is to give him honest, precise oppinions and observations so that he can evaluate it. If so many Nexus 4 users are reporting the exact same issue suddenly accuring with this new build DO YOU REALLY BELIEVE ABSOLUTELY EVERYTHING IS JUST FINE??? Obviously something has been changed and it behaves differently, so we got to find out why and if it is on the user side or if it really is in the kernel code.

One last time, if you are having no issues whatsoever don't treat any user who reports an error, yes it may be his wrongdoing, as a Noob/Fool/ungrateful bastard because he is not appreciating FK. If it's a nooby question, well you can also just answer in a funny sarcastic way if you like, as long as he get's his answer :)
[Nexus 4 Original Android Development] carlosmg2:
Just wanted to say that Minion Rush, lags the same with this, stock or any other kernel. The game is not well made or optimised, son don't take that game as a benchmark...
[Nexus 4 Original Android Development] albundy2010:
I think he may have been saying that playing the game is not a good way to judge the performance. That it always runs like crap on the nexus 4.

And that the kernel ( as in franco kernel or any kernel in general not just the latest 164) is not at fault for that game lagging.
[Nexus 4 Original Android Development] Pure Drive GT:
When the **** did people forget to read... 1. Minion rush is an EXAMPLE / 2. THIS IS COMPARED TO R16****in3 /

Play Minion rush with R163 Is just fine, verry little lag at the intro but hen fine. ---> Cores going all online when needet to.

Play Minion rush with R164 lags way more at intro and then continues to lag a bit while playing, check with System Monitor why, tadaa Only two cores online and capped at 1.35GHZ

HAS ASBSOLUTELY EVERYONE NOW FINALLY UNDERSTOOD THIS ISSUE ???!!!???

I really think people stop reading **** if it does not start with: "oh franco kernel is so awesomezzzz i wish i could load it into my brainzzz so that it would finally have some kind uf functionality ...."
[Nexus 4 Original Android Development] asm19:
Not entirely true! I used 4.2.2 + r163 and had lag, now with the 4.3 + stock kernel have no lag when playing. So, I think it is not the game...
[Nexus 4 Original Android Development] ben_pyett:
Whilst I agree with your sentiment with regards accurate and honest reporting.

Take a chill pill and respect the forum. No need to raise your voice.
[Nexus 4 Original Android Development] simorangkir_dcs:
Ittt's awessooooome!
[Nexus 4 Original Android Development] jyuuken:
And i think u need to chill down a little. Coz ur wayyyyy over reacting **bangs head
[Nexus 4 Original Android Development] franciscofranco:
Yeah the delete doesn't delete the actual backup file. I'll think about an implementation to do that properly.

Strange, I didn't have any problems with that. I'll search for what it is. I don't have any of that reboot problem when quitting games. I'm on stock rom. Unless it happens on stock its a CM/rom derp.
[Nexus 4 Original Android Development] Svid:
I'm having an issue with the latest nightly. I cannot change CPU govenor. Changing it in FKU and keeps reseting to interactive.
[Nexus 4 Original Android Development] :
Dude you could have done a F**KING SEARCH before making stupid assumptions, I made the same report about this when I was on r163, I never said it was perfect only place I noticed performance issue was this specific app and unless you have OCD its not a big issue and he's aware of it cause some guy made a big deal about it.

I love how people make a big deal out of nothing, go get a bloody life, and stop imagining people are replying in funny/sarcastic ways, learn to comprehend what you read and confirm if the issue has been posted before you pretend to be analyzing/investigating in a productive manner
[Nexus 4 Original Android Development] Hans QC:
Weird problem

This morning I had my N4 in my backpocket without it being locked. When I took it out the screen had turned red (like a red filter covering the screen). I suppose an option has been enabled like some of the ones you find under Development but I couldn't find anything. Are there options in FKU that would result in this kind of screen ?

Everything, save for the navigation bar, is red. When I reboot the phone the problem starts after entering the PIN-code.

Any suggestions ?
[Nexus 4 Original Android Development] franciscofranco:
I don't see how is that Kernel related.
[Nexus 4 Original Android Development] Bill Gamble:
Are you using Lux? That sounds like Astronomer mode.
[Nexus 4 Original Android Development] lorolouis:
Why some of you guys think that always a newly popped rXXX+1 will be better than already good enough rXXX ?

Sometimes it is just experimenting a new stuff.

Stick to 163 / 122 and wait, or calm down, test the latest and report the issues (not with UPPERCASE text) :)

However, the FKU app +1 updates should be always better, agree.

It turns bad when it s**ks like this ... but again you are allowed only to praise

Franco or to explain quietly the problems observed.

Sounds like a joke, but this is the reality of such things and their threads where one is giving thousands are taking.
[Nexus 4 Original Android Development] RockBoyEmy:
Franco, dunno why, but today when I had the notification of the new build, as always I just selected "autoflash" and let the phone do everything. Turns out that after the download, my phone rebooted and entered in a bootloop. I don't think it was ROM related, because I never had problems with my PA and your kernel, and I've been using yours since the beginning now... I had to do a full wipe, cuz I tried to open recovery mode and to flash the r163 zip that I had in the phone, but it was still doing the bootloop. Now, it’s fine, but I am still on r163, reflashed the ROM and installed everything. What to you think was this? :/
[Nexus 4 Original Android Development] Hans QC:
Thanks! That was the problem. I thought it was some FKU setting.
[Nexus 4 Original Android Development] manulemaboul:
R164 working as it should here, it just seems to take a bit long to online the core when hitting the threshold, so I've just lowered it by 10% to compensate :).

I like this new hot plug behavior :)

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Original Android Development] RockBoyEmy:
I've got another problem: am I the only one that has never seen any changes in the headphones settings? I can choose whatever option I want, whether the volume boost or the headphones gain, there's no difference in the sound output. Never was.
[Nexus 4 Original Android Development] Pure Drive GT:
Ok thx. And about the reboot issue, this seems to happen on any rom including stock. Mainly with Games in Landscapemode and only when exiting the game with exit button build in the game (won't happen if home button presses or recents). This is 100% not kernel related, it is simply a general rom bug, just wanted to know if people have found a way to avoid/fix this issue :)