yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] zelendel:
They do go into doze it is the reason you have to turn off battery optimization for each and every app one by one. Blocking internet connections and notifications defeats the whole purpose of having a smartphone.

After testing this with many people (you are more then welcome to test on your own) it has been proven that doze is more for people that bearly use their device. Not really for power users. There are even a few roms that are working on removing doze all together as they have found the same thing and advise people not to use any apps that mess with it and if they are using apps like Greenify or other doze apps then they are on their own and will not get support.
[Nexus 6  Original Android Development] franciscofranco:
Uh what? Apps do not go into doze mode. The system/framework does. Doze blocks a lot of different "pipes", that's why apps that rely on internet connection, or constant wakeups from idle won't perform those tasks. Apps that rely on internet connection to work on the background should use GCM anyway (which bypasses Doze, but it's very efficient). There are special Alarms that can bypass doze too, but they're not allowed to run in intervals smaller than 9 minutes.

What you just said about "roms" working to remove doze altogether raises a big alarm to me, and it actually frightens.

I don't know what kind of tests ya'll be conducting, but I don't buy any of it. Even your notion of doze is wrong...
[Nexus 6  Original Android Development] zelendel:
Might want to have a check on a few things. Many apps are not following goolges guidlines in this. Like the alarm I use. Bypasses Doze without using GCM (thankfully)

I am sure it does for you with your naptime app.

Believe what you will. It is simple common sense on why it does as I described. I just thought I would put my thoughts in on it. I will continue to remove all battery optimizations for all the apps I need to work without google thinking they know whats best. When their developers have no idea how the average person uses their device.
[Nexus 6  Original Android Development] dictionary:
It's a simple test really. Disabled doze, better battery. Enabled doze, crappier battery. For my use case. I understand someone who has an app that is in bed with doze won't agree, but there are a lot of us out here who get much better battery life when everything is disabled. *shrug*. Love your kernel BTW, lol. And I've bought your kernel app. ;)
[Nexus 6  Original Android Development] gk1984:
Did I come to the wrong thread...?
[Nexus 6  Original Android Development] dictionary:
It's a Doze Battle, lol.
[Nexus 6  Original Android Development] gk1984:
It's really something when someone asks for expert advice or an opinion, then starts an argument because the response isn't what they wanted to hear. It's the type of person you just let believe whatever they want no matter if they're right or wrong.
[Nexus 6  Original Android Development] dictionary:
I wouldn't really call it an argument so to speak, but rather both sides of the party voicing their opinions and/or facts. Franco expressed his, Zelendel his. I think the best way forward for the question poser is to try both ways themselves and see what works best for them. That's what I did. It's what we all should honestly. Didn't mean to come across argumentative
[Nexus 6  Original Android Development] pkgnex:
r63 is running like a champ on Feb security-patched stock 7.1.1 - -doze and all :p

Thanks, Franco.

(r62 ran on the stock Feb update ROM, too, so users looking to update to r63 without a ROM update will likely be fine this month.)
[Nexus 6  Original Android Development] franciscofranco:
My app Naptime has nothing to do with this, the only thing it does is force doze when the screen is off instead of letting the system wait 2 hours.

What I said is a fact, it's written in the documentation, and the fact that I have/had to deal with doze for my app 5217 (and numerous other events I needed for other apps) I know what I'm talking about.

The alarm you're describing is the only type of Alarm that is imune to Doze (Docs: https://developer.android.com/refer...Clock(android.app.AlarmManager.AlarmClockInfo, android.app.PendingIntent) ) but it's there exactly to make sure a real alarm fires off. You don't wanna go late for work do you? But that type of Alarm also puts an Alarm icon in the statusbar/quick settings next to the clock, so the developer won't be using that type of Alarm for anything else besides a real Alarm clock app. Any other type of Alarm will follow Doze's rule, and it can't be fired in under 9 minutes succession:

Note: Neither setAndAllowWhileIdle() nor setExactAndAllowWhileIdle() can fire alarms more than once per 9 minutes, per app.

Wakelocks are also blocked, and only GCM (now called FCM - Firebase Cloud Messaging) high priority messages can indeed bypass doze, but that's to ensure important messages are promptly delivered. That mechanism is HIGHLY optimized and the device goes back to idle/doze VERY quickly.

FCM is optimized to work with Doze and App Standby idle modes by means of high-priority FCM messages. FCM high-priority messages let you reliably wake your app to access the network, even if the user’s device is in Doze or the app is in App Standby mode. In Doze or App Standby mode, the system delivers the message and gives the app temporary access to network services and partial wakelocks, then returns the device or app to the idle state.

The only thing de-optimizing apps does is allowing them to acquire Partial Wakelocks during Doze mode, still, all the other rules apply such as running jobs and syncs will be deffered to the Maintenance Windows.

So all you're doing is allowing those apps to **** you by waking your device from Doze/Idle. Nothing else.

So yes, that theory that Doze is worse for your battery life is one of the biggest bull****s I've read on XDA. I really mean it. This is not personal, it's technical. I'm not pulling these things out from my arse, they are written in the public documentation and I've personally been hands down on my apps code to deal properly with Doze.
[Nexus 6  Original Android Development] dictionary:
It's just I don't understand how a gaggle of us are getting better battery life with things disabled. It's not trying to disprove you, or Google, but really and truly trying to find the reason why.
[Nexus 6  Original Android Development] Krunk83:
Yeah I know it wasn't working in fku. Thanks, guess I'll wait for the update.

nexus 6
[Nexus 6  Original Android Development] mrw1215:
Question to those who use Vomertweaks, do you use the dual core version or quad core version? Does it make any kind of difference in battery life and/ or performance?
[Nexus 6  Original Android Development] zephiK:
Theres a thread for that http://xdaforums.com/android/software-hacking/vomertweaks-perfect-balance-performance-t2873369
[Nexus 6  Original Android Development] kxhaz:
Yes and I did and for me it is perfect. Before I would leave my phone on the lowest notification volume because that was quieter than the vibration sound would make. I also noticed typing the feedback was very nice.
[Nexus 6  Original Android Development] noneabove:
Where were you when i had an M8.. jesus that things vibrator causes earthquakes!!! Glad to see the vibrator is adjustable on the n6 though, that's why i love nexus devices and devs like yourself! :D
[Nexus 6  Original Android Development] nixie2121:
I like this A LOT!!!

---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------

What about the min number? do you lower that at all? What do you set your high and low at?
[Nexus 6  Original Android Development] cobyman7035:
I'm in dual vomer script… stuttering using nova prime scrolling app drawer and home ? screens… I use flex iconic pack

Battery life us amazing tho… 2hrs sot with 73% battery left.. 18hrs since unplugged
[Nexus 6  Original Android Development] franciscofranco:
No point in using anything lower than 300MHz to be honest. I use the defaults.
[Nexus 6  Original Android Development] kergefarkas:
try 205/205/245 ;)
[Nexus 6  Original Android Development] you5urf:
franco you've done it again!! This kernel just reminded me why i picked up your premium app when i had the N4. Amazing work. This has been the only custom N6 kernel i have tried that doesn't lag in my specific use cases
[Nexus 6  Original Android Development] Krunk83:
Whoa

Do you use this?

nexus 6
[Nexus 6  Original Android Development] zephiK:
This might be my new favorite ;)
[Nexus 6  Original Android Development] dkotoric:
Im new to using kernel's how do i actually change this?

Sent from my Nexus 6
[Nexus 6  Original Android Development] zephiK:
Use a kernel tweaking app such as Trickster, Franco Kernel Updater (paid) to tweak the colors.
[Nexus 6  Original Android Development] dkotoric:
Damn this is awesome my screen is white white white, i dont have a note 4 next to me but its very close to note 4 now

Sent from my Nexus 6
[Nexus 6  Original Android Development] noneabove:
weird... it looks gross on mine, there must be different kinds of displays or something...
[Nexus 6  Original Android Development] angieri918:
Anyone having issues with wifi breaking? I keep getting kicked off and have to type in password again each time it does that.
[Nexus 6  Original Android Development] holeindalip:
Awesome job on r-5,no bs scripts or tweaks stock r-5 settings with adaptive brightness and full sync
[Nexus 6  Original Android Development] dkotoric:
I just switched to 215/215/250, i think i like that a lot

Sent from my Nexus 6
[Nexus 6  Original Android Development] blueren:
Na. It just takes awhile for your eyes to adjust. Try going back to 255/255/255 after awhile. You'll think your display is pure yellow :)

---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------

Just wondering.. Do you happen to have location services / location reporting off?
[Nexus 6  Original Android Development] franciscofranco:
It's not really a good test without 100% controlled lab environment. There are just too many variables every day that can pull the results to one way or another. And as I said before, doze only kicks 2 hours after the device has been stationary.
[Nexus 6  Original Android Development] zelendel:
I think that is where Google messes up. Lab environments are great for static tests that will get the same outcome. But when it comes to something like this lab tests don't really work. It has to be tested in a real world everyday environment. I can make doze look great in the lab. Works wonders. In real life. Not so much.

I mean really. The average person has at least 20 different notifications every hour at least. From all kinds of apps. Then you have apps that don't work with doze at all like Facebook. Even turning background data for the app off it still pushes notifications when in the background. It even bypasses your nap time app.

I understand what the documentation says, I have been going over this with the Google developer teams since they introduced doze and many found it causes worse battery life. To which I was told "the average person sees 5 notifications a day with less then 2.5 hours of screen on time" which we all know is bs. Yet running those numbers would make doze seem like a good idea.

I'm not being argumentative, just trying to figure this all out. I am also working on them messing up on the min temp for the device shutting down.
[Nexus 6  Original Android Development] gk1984:
I wonder how scientists and engineers feel about this... And how do you propose to rule out variables and collect reliable data?
[Nexus 6  Original Android Development] zelendel:
Oh im sure they will throw a fit. Dont get me wrong. There are setups that work in a lab. A mobile device OS that is used by millions in millions of different ways is not something that can be reliably tested in a lab enviroment.

To test this I ran my device for 2 weeks. One week with way it comes and 1 week with it all disabled. Then I had a few people do the same thing. When more then just you comes to the same conclusion then there is something to it.
[Nexus 6  Original Android Development] gk1984:
Placebo? Do you have data to review the results? Perhaps with peer review, someone can explain why it's happening and can further improve upon it.
[Nexus 6  Original Android Development] franciscofranco:
Pushed r64 with some changes I made after r63. Should help on power reduction by freeing cpu2 and cpu3 from dealing with some long standing daemons.
[Nexus 6  Original Android Development] MandoH:
Edit: Maybe it was the changes?..

Updated via fkupdater seemed to be stuck on boot.img so rebooted, put pin, and still seemed to take long to boot. Never done that before.
[Nexus 6  Original Android Development] franciscofranco:
Dunno. There hasn't been any change on the boot process or anything in between.

The changes won't kick in until ~30s after Android has booted up.
[Nexus 6  Original Android Development] MandoH:
Just checked again. I rebooted device and got stuck in boot loop.. Would not boot. Flashed 63 and boots normal
[Nexus 6  Original Android Development] franciscofranco:
I just auto-flashed, and booted fine. The changes I made were not even in the Kernel, they only run 30 seconds after Android is up and running and it's just "pidof" and some "echo" commands. Something is going on there.
[Nexus 6  Original Android Development] MandoH:
I just flash it in twrp
[Nexus 6  Original Android Development] toopty:
Auto Flash not working

I'm running the latest Beta of Franco Updater and Auto Flash does not work anymore. Anyone have suggestions on how to fix this?
[Nexus 6  Original Android Development] franciscofranco:
What do you mean "not working anymore"? I just auto-flashed fine.
[Nexus 6  Original Android Development] giannis_mathiou:
I also auto-flashed r64 with FK Updater and couldn't end boot process. I had to flash back to r63.

Is there any log I could provide to help?

Edit: Redownloaded and auto-flashed just fine this time. Previously I had screen lock with PIN, before download and auto-flash for second time I removed screen lock.
[Nexus 6  Original Android Development] Kiristiba:
Me2
[Nexus 6  Original Android Development] MandoH:
Re-downloaded and flashed in TWRP. All is good. Most likely bad download..
[Nexus 6  Original Android Development] franciscofranco:
I dunno. Will revalidate my servers cache, something's off.
[Nexus 6  Original Android Development] toopty:
When I try to flash the new updates from the app, I receive a message that says "There was an error trying to flash the zip. *shrugs*" I have used the feature in the past, I just received the message last night with the release of r63. Had the same issue with r64.
[Nexus 6  Original Android Development] pkgnex:
Flashed via TWRP with no issues here...
[Nexus 6  Original Android Development] franciscofranco:
That means the downloaded package either failed md5 check, or the downloaded .zip is corrupt. So to save you utter destruction I don't flash and show the error you just described.
[Nexus 6  Original Android Development] toopty:
That is interesting because I booted to TWRP and manually flashed the file that the app downloaded without any issues. So far no problems. I will download the file manually and flash again just to be sure. Thank you for the quick response.
[Nexus 6  Original Android Development] garywojdan81:
Flashed r64 just fine through the app for me
[Nexus 6  Original Android Development] franciscofranco:
Probably my server was acting up or something, dunno really, impossible to know.
[Nexus 6  Original Android Development] abaddon37:
I am getting stuck on the boot process as well. I downloaded once from app and downloaded once on my computer and moved file to phone.

Is there any log I can get to post here?

Nevermind, I think. I rebooted the phone, and it went through the boot process. I probably didn't wait long enough...
[Nexus 6  Original Android Development] franciscofranco:
Try again, I just re-uploaded a clean build + cleaned servers cache.
[Nexus 6  Original Android Development] abaddon37:
Tried it again with clean build. Had it run for about 40 minutes and it was still stuck on boot animation. Tried restarting again, and it still wouldn't boot. Flashed back to r63 successfully.
[Nexus 6  Original Android Development] NLBeev:
Today 8 February EU time 9:00 flashed r64. Runs as usual; no issue.

Nexus 6 with pre-rooted lite ROM of Danvdh Nougat 7.1.1.

Before update r63 to r64; flashed the speaker echo fix.
[Nexus 6  Original Android Development] franciscofranco:
I have absolutely no idea. As I said, the Kernel binary hasn't changed from r63 to r64, the change was only in a script that only runs ~30 seconds after the boot has been completed. I just auto-flashed and it worked ok. Not saying the problem is yours, but something is weird.

Anyway I cleaned servers cache, re-built the Kernel, re-packaged and re-uploaded. Try now.
[Nexus 6  Original Android Development] The Doctor04:
I as well was getting a boot loop on r64. Got back to r63 so no worries there. I am going to download the zip and try flashing in TWRP this time, previously I was using the app. Other than that it has been rock solid
[Nexus 6  Original Android Development] xdafalter:
Are you still on Pure Nexus ROM? I have this issue with Nitrogen ROM und 7th feb build and r64. I flashed echo/audio fix as well, else there was no sound in the past as Nitrogen hasn't updated this part, yet.
[Nexus 6  Original Android Development] mns:
Me too. Boot loop on r64, then back to r63.
[Nexus 6  Original Android Development] rignfool:
[MENTION=3292224]franciscofranco[/MENTION]

You should probably ask what root solution these people with bootloops are using...

When I tried your kernel with magisk... It would only boot every 3rd time or so... No rhyme or reason... Just a simple 'hold power to reset' would get the phone to boot...

And of course... No pstore logs for you any of those times...
[Nexus 6  Original Android Development] ryanallaire:
Yeah using phh or magisk seems to be finicky at times..
[Nexus 6  Original Android Development] liquidops:
Wifi issues with r52

First off, awesome work Francisco! Your kernel provides the longest battery life that I have seen.

The only issue I'm encountering is that after 5-6 days of use on r52, when I try to turn on wifi, the wifi settings freeze so that I can't turn it on or off. Also, the device doesn't connect to a network. The only solution is to reboot the device and everything works normally again. I'm running Android 6.0.1 MOB31K tupac4u ROM. I have tried flashing r51 and had a similar problem. Do you have any ideas on what I should try?
[Nexus 6  Original Android Development] Didgeridoohan:
Haven't had any issues with Magisk and MagiskSU together with Franco Kernel and I've been using Magisk and it's built in root solution for about 6 months now... I never use the app to flash my kernel though, so I can't say anything about that. Currently running r64 with Pure Nexus 01/21.
[Nexus 6  Original Android Development] The Doctor04:
Tried downloading r64 zip, download on phone and PC...Flashed all three in TWRP. Still boot looped. r63 running like a champ

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

I am on PN, latest build. Speaker phone bug is fixed on that ROM for everything but IP (hangouts, Skype, etc).
[Nexus 6  Original Android Development] xdafalter:
So I tried again this evening to use r64. I couldn't install via FKUpdater app, gave me: There was an error trying to flash the ZIP *shrugs* - I never had this before.

So I tried TWRP with the ZIP from backups folder.

First boot then went through bootanimation (last time was stuck in there, but no reboot), but screen stayed black. The last line of logcat was:

02-08 20:28:38.886 870 870 I kickstart: STATUS: Sahara protocol completed​

Phone seemed dead, as no more lines appeared.

Then I did adb reboot und adb logcat to give you a hint of what is going on with the full log.

What can I say, now it suddenly works with r64 :confused:

The only thing I did in between was to flash r62 in TWRP this noon.
[Nexus 6  Original Android Development] ryanallaire:
I just installed r64 via TWRP and everything is working fine, I did however have to reset my bootloader logs to get the right battery percentage reading...
[Nexus 6  Original Android Development] franciscofranco:
I'm puzzled :|
[Nexus 6  Original Android Development] tsjanda:
Running stock lite and r64 no issues at all in fact running very smooth
[Nexus 6  Original Android Development] garywojdan81:
Same here
[Nexus 6  Original Android Development] MysticKing32:
Plus one on the bootloop on r64. I flashed it then it went into the bootloop. One reboot later then the phone booted right up. No issues since. I will say I have recently started using magisk su (I had a situation where I left my wallet at home and I couldn't use Android pay to pay for my food at the restaurant LMAO) so I absolutely had to switch to magisk just in case that ever happened again. I'm pretty sure it has something to do with that because with r63 and chainfires su everything always worked fine. I switched to magisk before r64.

Anyone with chainfires su getting the bootloop on r64? That would definitely narrow it down
[Nexus 6  Original Android Development] Didgeridoohan:
I've used Magisk with Magisk superuser for 6 months together with Franco Kernel with no issues whatsoever. Right now I'm running Pure Nexus 01/21, Franco Kernel r64 and Magisk v11.1 with MagiskSU.

I always flash kernel in TWRP, so I can't say if it has anything to do with the app or not. Although I think I've seen reports of bootloops after flashing r64 in TWRP as well... I do download the kernel through the app though.
[Nexus 6  Original Android Development] bautrupp:
r64 running fine flashed through TWRP on stock rom since the minute FF uploaded it.
[Nexus 6  Original Android Development] MysticKing32:
O okay. That's my current setup as well Didger
[Nexus 6  Original Android Development] xdafalter:
Today after a reboot I ended up in a black screen again after bootanimation. Tried twice, now back on r62. Using Chainfire SuperSU.

Visible diffenece is, after bootanimation I get normally the kernelmessages via Chainfires LiveBoot, when I run into black screen there is no liveboot messages seeable before.
[MENTION=470754]Franco[/MENTION]: need another logcat? But seems the same as postet a few posts back.
[Nexus 6  Original Android Development] BigDig:
Same here. I flashed through the app though. No loops and such
[Nexus 6  Original Android Development] tsjanda:
OK ran into a problem. I got a reboot while using Twitter, after reboot had another reboot while in settings. I tried to get logs but none was recorded. I am running stock lite with r64 at the time reverted to r63 and have not had any reboots for over 4 hours. Now I am not saying r64 was unstable or the problem in fact it was very smooth and the reboots might not have been related to the r64 at all. I did reflash the speaker phone fix revised and it flashed without any errors. Phone seems smooth and snappy also I'm running the SuperSU root app not other mods or apps just stock lite ROM and and a few playstore apps. Will try and get logs next time
[Nexus 6  Original Android Development] franciscofranco:
Sorry about anything, but I don't know whats up with r64. I literally made no changes to the Kernel binary what-so-ever. I'm still trying to figure it out though.
[Nexus 6  Original Android Development] franciscofranco:
Just released Franco Kernel Manager & Updater 2.2. Slightly rebranded for moar downloads! Read my G+ post explaining whats changed: https://plus.google.com/u/0/+FranciscoFranco1990/posts/hsHNejwRRbb