yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Ümit:
How do I that?

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showpost.php?p=15869868
[Nexus 4 Original Android Development] emperatour:
i have installed latest franko kernel nightly on krt49h kitkat rom. i used franko kernel updater latest version color setting and my screen is over saturated now. i set stock from the list but i think this is not the kitkat default. is that? or it means stock for franko setting? what is the coloe values for stock google image(4.4) and paranoid android ?
[Nexus 4 Original Android Development] bokagavrilov:
Stock its stock-google settings
[Nexus 4 Original Android Development] gtanner00:
I'm sure that suspend frequency does make a difference if you are someone who has syncing wakelocks (like Facebook, email, etc) which need to run in the background. If you limit the speed to 702mhz then it will use less power than 1512

For people with no wakelocks it shouldn't make a difference since the CPU never needs to ramp up during sleep.
[Nexus 4 Original Android Development] hardwareadictos:
What is this???

Sending from Nexus 4 with OmniRom powered by Franco Kernel
[Nexus 4 Original Android Development] steviewevie:
Stock in FKU always used to be Franco's stock, not Google stock, unless something has changed.

Sent from my Nexus 4.
[Nexus 4 Original Android Development] debnath:
Hey I am using the nexus 5 experience ROM ( http://xdaforums.com/showthread.php?t=2545838) and my N4 root breaks after I flash r200 or r201. Does it has something to do with FK ramdisk stuff talked in this thread?

Any pointers to have FK running on the ROM?
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Exactly the same stats here...Would be curious to know... :confused: Used to get an amazing battery backup on CM 10.1 (good old days when CM didn't drift to CAF) using the same apps installed as of now on latest omni but battery drains a lot faster then before...thought there would be rouge app but that isn't the case...
[Nexus 4 Original Android Development] crozbomb:
jesus christ this version is making my battery last long, usually charge once every second day but im on 47 hours and 44% battery left, i estimate i'll get another day without charging using normally.
[Nexus 4 Original Android Development] :
I bought BBS and noticed the main wakelock is msm_hsic_host. I googled and it seems to be kernel related. I didn't have any wakelocks before r201. If I flash an earlier version will it fix the problem or do I need to do anything else?
[Nexus 4 Original Android Development] Akath19:
That's a normal wakelock on any N4 so there's nothing you can do about it.
[Nexus 4 Original Android Development] :
I am checking Kernel Wakelocks though, is there something else I need to check to validate my Deep Sleep is OK?

Also, that doesn't sound right. Something did change. I didn't install anything and only updated FK to r201 and then my problem started. With r200 I had maybe 2-3% drop overnight and now it's over 10%!
[Nexus 4 Original Android Development] Akath19:
I haven't noticed a bigger battery drain on r201 but others have so I can't help you there.

Kernel wakelocks can only be fixed by kernel devs, you should only concern yourself with Partial wakelocks which are basically apps misbehaving.

Check if there are any strange Partial wakelocks, that's the only thing I can think of.
[Nexus 4 Original Android Development] Bill Gamble:
Flash the latest SuperSU zip in recovery:

http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
[Nexus 4 Original Android Development] chrisgtl:
Just gone back to #200 and battery is instantly better and as as smooth as #201. Not bothered about the call delay so will stick with this beast.
[Nexus 4 Original Android Development] bust1337:
Same here
[Nexus 4 Original Android Development] lotherius:
Bluetooth issue?

Anyone had issues with Bluetooth?

I'm running stock 4.4.2 with Franco.

I use my in-car bluetooth for calls & audio over my Sony stereo, as well as to connect to a Bluetooth OBD-II diagnostic connector. Mostly just the audio, for incoming calls.

The last few weeks I've been noticing that bluetooth is turning itself off every one or two days, randomly. Once it turns itself off, I CANNOT turn it back on without rebooting the device. The toggle simply won't turn on, whether from quick settings or from the bluetooth menu. I have to reboot the device when this happens. This is dangerous, of course, because incoming calls do NOT come over my stereo because bluetooth has turned itself off AGAIN, and I can't turn it on without rebooting.

Was wondering if anyone knew about this problem and if it was Kernel related or a problem with the stock 4.4.2?
[Nexus 4 Original Android Development] RootTheMachine:
Those stats are due to the fact that your phone is a phone. Nothing you can do about it.
[Nexus 4 Original Android Development] anshumandash:
That's a kitkat problem. Google will need to fix these Bluetooth issues. It's a problem with the Bluetooth driver in kitkat.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Matze5800:
Airplane mode.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] sordna:
By the way, it's impossible that you didn't have ANY wakelocks. We always have various wakelocks occuring, it's part of normal operation of the device. The issue is if they become excessive. Anyway, try flashing back to r200 and see if the wakelocks are much different or not.

But to be sure it's the kernel, you may need to do several tests back and forth. I was on r199 for a very long time, and some nights I had ever 10% drain, some nights less than 2%, without any change, which was quite frustrating, but in my case it was the email services going wild and I could see that even in the android battery settings. I think that the battery settings is the first thing to check, followed by app and services wakelocks. Kernel wakelocks have less impact to battery drain than apps and system services. The kernel by itself doesn't do much if the phone is idle, it's the system services that trigger the kernel to do stuff, at least as I understand, so seeing a kernel wakelock is more of the symptom, rather than the cause.
[Nexus 4 Original Android Development] Ümit:
Which is better r199 or r200? I used r199. It was very good but my phone rebooted after 300 hours.

I have r200 never used.

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] donteo:
Same here #200 battery is much much better thatn #201
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Ok, then what is this? it it normal? 11% battery drain in just 3 hours.
[Nexus 4 Original Android Development] _artem_:
11% in 3 hours? ololo 18% in just 1 hour with only 25 mins SoT.
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Very good, but if you could see my screen on time is negligible.
[Nexus 4 Original Android Development] _artem_:
I ment couple of r's ago I was over 15 hours on battery with 5 hours SoT and still had 45-55%. But on r201 my n4 will be at the same 45-55% in just couple of hours
[Nexus 4 Original Android Development] donteo:
True story r201 is the most battery hungry kernel i use with default settings
[Nexus 4 Original Android Development] musa47:
What??? 5h SOT and you're still left with 45-55% juice with previous version?
[Nexus 4 Original Android Development] dhurk:
Perappmode's notification message not showing everytime,is this mod working everytime or do we must start FKU app everytime after restart thr phone?
[Nexus 4 Original Android Development] svnhvn:
Really?

This was mine. Default settings with full mobile data, disabled location services, contact and gmail auto sync.
[Nexus 4 Original Android Development] svnhvn:
And this too..
[Nexus 4 Original Android Development] donteo:
Its with r201 ?
[Nexus 4 Original Android Development] Grakel:
I get at least twice that with faux kernel on eco mode. Not so smooth but...

Dont get me wrong Im not saying anything about any kernel being better than other. I just see that there is something eating battery on 201.
[Nexus 4 Original Android Development] donteo:
There will be r202 soon i think master Franco always give us the best kernel :laugh:
[Nexus 4 Original Android Development] Micoolef:
from my understanding, this wakelock occurs when your phone is connecting to cell towers. If you are always connected to WiFi this wakelock should drop. it was present on previous iterations of FK so reverting will not solve it. I also don't think it's something that can be fixed within the kernel and I haven't heard of any specific solution. It may be a modem issue.

BBS is really good for managing your battery drains. The items on the list are always jargon, but a quick search of Google or XDA will have forums of people discussing what they think the cause is and possible solutions.

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

It's Google Search waking your phone 20 times in 3 hours.

BetterBatteryStats > Partial Wakelocks > I guarantee NlpcollectorWakeLock will be at the top, draining the crap out of your battery. Turn off location reporting and this should be resolved (unless you use location reporting). If that's not it, it might be location services in general or Google Now.
[Nexus 4 Original Android Development] avi.laza:
Where is the download link?

Can't find it on the OP:banghead:
[Nexus 4 Original Android Development] leather.face:
Hi :) ... This is the download link and you find this in the OP post ... I wish a nice evening! :)

Regards lather.face :cool:
[Nexus 4 Original Android Development] svnhvn:
Of course.
[Nexus 4 Original Android Development] svnhvn:
Yes, every person has their own liking. Me? I don't like sacrificing my phone performances too much.
[Nexus 4 Original Android Development] :
Following my previous posts saying r201 killed my battery life (after not installing any app or changing any system/app setting): I restored r200 using FKU app. Back to perfect health again, six hours in deep sleep and I'm down 1% (with r201 I was down 7-8% in that period of time). I don't know what r201 changed but it definitely affected my battery life in a bad way.
[Nexus 4 Original Android Development] Cantacid:
Suspended frequency maybe! Trying restoring that back to 702 or whatever it used to be.
[Nexus 4 Original Android Development] Togno85:
My battery Life is bad whit The r201

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Thank you. What you said is very true, I always knew that this ain't a kernel bug and was just seeking some suggestions. And for those who were facing battery drain like me, this could be the reason :

http://androidandme.com/2014/01/new...-includes-support-for-turn-based-multiplayer/
[Nexus 4 Original Android Development] 777.300:
No problems here, running r201 with great battery life and very smooth with suspend freq at 702Mhz.

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] kurtph1969:
Yes, I have had a few SODs recently and I put it down to auto update from the play store. Thanks for the reminder
[Nexus 4 Original Android Development] Andre_Vitto:
Working with mahdi rom?
[Nexus 4 Original Android Development] svnhvn:
Great news.
[Nexus 4 Original Android Development] benrees21:
I'm on Vodafone UK as well and get full signal indoors constantly. Have you checked the Vodafone forum to see if there is work being carried out on the mast you connect to?

A Nexus b!tch called Ben (Work that one out :P) AOSPA!! Franco Kernel!!
[Nexus 4 Original Android Development] NoLunchBox_:
On battery: 12h 37m

On screen time: 5h 41m

Second day with Franco's kernel R28. Yes I get data drops but I get 3 bars MAX in my house on a good day and that's 2G lol

I have bad signal yet I still manage to get pretty damn good battery life.

So kudos to Franco. On stock I was getting barely 3h on screen time.

*Oh and sorry no screenshots. The app didn't let me post them for some reason*
[Nexus 4 Original Android Development] Taxiback:
No because as soon as I revert to stock I get a good signal, so unless they're looking through my window and disconnecting the transmitter every time I flash franco's kernel I'm at a loss. ;)
[Nexus 4 Original Android Development] Vangelis13:
Surely Franco is open to learning new things (and is capable of finding them himself) but he has repeatedly said no to swipe - gesture features. And this one in particular looks fairly similar to what he has turned down in the past.
[Nexus 4 Original Android Development] pqee:
They're misreading your post. They think you're asking for swipe to wake. You're just trying to help Franco out with swipe detection to help save battery as he's indicated in the past.

It's funny because swipe detection should save battery while swipe to wake eats battery.
[Nexus 4 Original Android Development] kitch9:
If you never use music, books etc etc make sure you at least open the apps once to sign into them.... There's a bug in the rom that seems to drain battery if you don't.

You need to sign into every Google app to stop it....
[Nexus 4 Original Android Development] Chochiwpg:
I typically run the stock kernel on all the ROMs I flash, but Franco's kernel is the only other kernel I would put on my phone for daily use. I personally prefer the vibration intensity and the volume enhancement that I get on Franco's kernel over stock. When I have my phone in my winter jacket I can actually feel the vibration and hear the sound loud and clear. Those are the main reasons I will run Franco.

For smoothness and battery from my own personal experience I can't differentiate between stock and Franco's kernel. Stock kernel battery life, smoothness and signal strength run fantastic for me. I typically have my phone on for 15hrs and still have 50% battery before I go to bed at night. I get very similar battery and smoothness from Franco's kernel as well.

For me the difference isn't in the battery life, it's in the sound and vibration and it's for supporting Franco and the development community. I got a Nexus to test out everything the Dev's produce. Some kernels have glitches, some ROMs have glitches, but the fun is to test and work out the glitches and improve upon what Google has created.

Great job Franco, keep up the good work, I will always be willing to test out new Kernel's. We got a Nexus for a reason right ;)
[Nexus 4 Original Android Development] Martin_Ro:
For the data drops:

Is there a chance, that they are related to the changes in the USB drivers as the Modem is connected as USB device maybe ?

Just asking because I have seen in the CM gerrit that they also have tested some patches in the USB driver, so if you have picket (some of) them to, maybe the culprit is there ?

For the rest of your planned changes:

Sounds amazing but I have a small concern about the tap/swipe thing isn't that easy to archive.

The smaller problem will be, that the system will also get a "scroll swipe" if you use the keyboard swipe function so it will Online the second cpu without any need.

But what I fear more is, that the swipe to scroll function will need to much delta on the move to get the swipe as a swipe so that the user experience could be a "lag".

So i would suggest to make this "delta" of fingemovement be editable (by your app).

Also on the "throttle" side:

Is it possible that the throttling comes more from gpu then cpu?

Is there a "cpu only" benchmark where we can test this ?

I ask because I would think that the gpu has way more work then the cpu on a game like nfs etc. so maybe the throttling or disabling of cpu cores wouldn't bring that much.

Also maybe this could explain why there has been reports of broken phones (red light of death) after benchmarking. If you look only onto the temperature of the cpu and throttle this, if it gets to hot, maybe the gpu is, what's really burning...
[Nexus 4 Original Android Development] undercover:
No. Data issue is from Google. Why it only started happening recently? God knows.

It's happening on Gnex too. Looks like it's something to do with 4.2 and up updates.

Sent from my fridge. Make:LG Model:N4
[Nexus 4 Original Android Development] Chochiwpg:
I would also like to add from my previous post that the advantage of running Franco's kernel is the fact that Franco is active in this forum as well and you can report bugs directly to the developer and he fixes them almost immediately. Which to me in itself is fantastic. I may be happy with the stock kernel, but for others that aren't you can't go and contact the Google developers directly and have them fix your issues for you.

This is what is great about the community and developers like Franco. They are here to make our devices better, they listen to the community and constantly push fixes and updates. You don't get that with stock.
[Nexus 4 Original Android Development] Taxiback:
We understand that, but I don't get why we get people posting that r28 should be the milestone when it quite clearly has bugs for a lot of us. If franco lives somewhere with a good signal he might believe them and we end up with a milestone that doesn't work for a lot of us.
[Nexus 4 Original Android Development] Chochiwpg:
You would have to ask Franco that question. Maybe he feels R28 is the closest iteration of the the kernel to being milestone. It may not be perfect for everyone using the kernel, but maybe the pros outweigh the cons and the majority of users aren't having issues. Could just be a couple more tweaks away from a milestone. I don't know.

I personally haven't had any issues with R28, it's working great for me. Maybe not so well for others. If it isn't working well for others the best thing to do is catch some logs and report the problems that you are having so Francisco can look into them.
[Nexus 4 Original Android Development] Taxiback:
I can't provide any logs as I've had to go back to stock for now as I need my Nexus as a phone not a Nintendo DS. I use it for my work. Reading back I would say it's 50/50 with people having data issues, doesnt read like the majority are happy with it as it is. If it was I'm sure it would be a milestone already.
[Nexus 4 Original Android Development] djemgee:
What ROM are you using with r28 coz I get lag with the stock ROM :confused:
[Nexus 4 Original Android Development] Taxiback:
Stock, just like me, no lag here. Coming from a Galaxy S3 the Nexus seems like a rocket ship, smooth as butter.
[Nexus 4 Original Android Development] necksis:
By people saying r28 should be a milestone is their way of saying it is stable. People also ask for sweep2wake, but you don't see Franco putting that in. Franco knows what he wants the kernel to be, and as you can see from the list he posted yesterday he also knows what he wants for a stable release. Seeing that this isn't the first kernel Franco has developed I'm pretty sure he'll get a good sense as to when something is stable. r28 has been fine for me, and I'd personally classify it as stable, but other users are having issues so I'm sure he'll continue to hammer out the bugs. He won't release a milestone just for the sake of releasing it.
[Nexus 4 Original Android Development] Mahdi786:
I should report you for being so rude, I don't see your name on top of thread so who the f*** are you to tell other people to get out, go and get a life and stop reporting such little things.
[Nexus 4 Original Android Development] Chochiwpg:
I am running R28 with MiNCO, don't notice any lag.
[Nexus 4 Original Android Development] djemgee:
Hmmmm I've flashed the stock kernel before so maybe that cause a glitch I'll try and flash r28 straight on and see if makes any difference
[Nexus 4 Original Android Development] Vangelis13:
Latest rasbean, flawless combination.
[Nexus 4 Original Android Development] Bill Gamble:
If you don't want to wait for the update, you can download the Google-signed apk from here:

http://www.androidpolice.com/2014/0...player-new-google-drive-api-preview-and-more/
[Nexus 4 Original Android Development] The Zel:
Sure mate

N⁴
[Nexus 4 Original Android Development] Puneet Singh Chauhan:
Thanks for quick response. PA Gapps are now updated and I installed it from there. :good:

http://xdaforums.com/showthread.php?t=2397942
[Nexus 4 Original Android Development] jabbeboy:
Where do i download all the color profiles ?
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showpost.php?p=49140614&postcount=53651
[Nexus 4 Original Android Development] jabbeboy:
Thanks :)
[Nexus 4 Original Android Development] slugger09:
OK am I doing something wrong, haven't used Franco in a while but I go into color profile to change colors, I go into Load and damn all happens, where did all the profiles go that used to be in there?
[Nexus 4 Original Android Development] Mercado_Negro:
Your answer, right above your post.
[Nexus 4 Original Android Development] rohit297:
No, mahdi rom has sift reboot issue with this kernel
[Nexus 4 Original Android Development] The Zel:
Really? Didn't know that, sorry :silly:
[Nexus 4 Original Android Development] boeder9:
I'm on r193 and the latest f.k updater, I can't seem to find the "Turn high performance sound" option under Kernel Settings, all I see is "headphones volume boost", "headset gain boost" and "mic gain"

Also, my Gamma color control increase from 1-4 then make jumps like 28, 39, so I can never set the red mids to 21 for eg. The RGB control also doesn't go beyond 255. Not sure if it's meant to be that way but I've seen app review where the dial looks different.
[Nexus 4 Original Android Development] Bill Gamble:
That's because there is no such setting in f.Ku... at least not on the Nexus 4.
[Nexus 4 Original Android Development] svnhvn:
This latest beta FKU set on boot setting won't stick after reboot. I guess 10 minutes is enough for kicking it right?
[Nexus 4 Original Android Development] Bill Gamble:
It should be sufficient to wait until f.Ku has been granted su rights.
[Nexus 4 Original Android Development] spec0071:
It does affect mine,a lot. What to do?

Franco r201 on Purity ROM 4.4.2
[Nexus 4 Original Android Development] zorginho:
Because there isn't that option! U can set headset gain boost to -5 to increase the volume and sound strenght

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] svnhvn:
How long (on your device)?
[Nexus 4 Original Android Development] Bill Gamble:
On my device, it sometimes takes up to a minute for the SuperSU toast announcing the granting of su status to f.Ku to appear. The leisurely pace seems to be a product of KitKat.
[Nexus 4 Original Android Development] svnhvn:
I just gave 15 minutes and nothing happened. Must set all my settings manually.
[Nexus 4 Original Android Development] Bill Gamble:
Are you saying that f.Ku isn't being granted superuser permissions?
[Nexus 4 Original Android Development] svnhvn:
Dunno what's exactly happened mate, but if i clear FKU's data it's always ask SuperSU permission and of course i granted it.
[Nexus 4 Original Android Development] Bill Gamble:
Are you Greenifying f.Ku?
[Nexus 4 Original Android Development] svnhvn:
Of course no. And FKU also listed in my startup apps on my device.
[Nexus 4 Original Android Development] Ümit:
r199 stock settings. 19 percent on one night without using.

Time for back to stock kernel :(

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 4 Original Android Development] alanwyl:
Clearly something is running in the background. That's the beauty of TRUE multitasking in Android.
[Nexus 4 Original Android Development] :
Yup, no way you lose 19% without something that's not allowing your device to enter deep sleep. Time to get BetterBatteryStats and see what it is. I lost 3% the last 10 hours using r200.
[Nexus 4 Original Android Development] svnhvn:
There's obviously something derped on your side dude..
[Nexus 4 Original Android Development] Ümit:
But I clean always the ram memory for I sleep. It's not enough?

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi