yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] relaxable:
What I don't understand about that response: Naptime is requesting these accesses to Internet when it is just running in the background - there is no Naptime App, window, or notification open. Often this occurs after unlocking the screen while in another app or in the launcher. Did you design Naptime to display ads when Naptime is not foreground? Look, I understand the plight of developer (have been one myself; and I did purchase the FK App), but at least for me, ads are nothing more than an annoyance. (Seems you think that as well as you are suggesting a contribution to remove annoying ads - so they are there to try and motivate people to pay for the app as opposed to generate income?) There is less than zero chance that I will respond to a mobile ad, and about zero chance of an ad having any kind of 'un-clicked' impact on my brain. So, when you say "it's the ads, I don't have any control over that" - it would seem to me to be inaccurate - surely you have control of whether to include ads with your app,.? But this seems more sinister: ads being retrieved when the app is hidden? I have other apps that [would like to] display ads that are firewall blocked from Internet access, and they don't behave like this.

There are few apps that I can live without, and generally if my methods to block annoying ads don't work, I'd rather do without than pay to remove ads. But, in some cases where I find app particularly useful, or cases like your Kernel where my belief is that it takes a LOT of work, effort and skill to do and maintain, I like to support developer with $/pay for app.
[Nexus 6  Original Android Development] pkgnex:
It's kinda dead... but that's more an indication that everyone's happy, I think.

You've already optimized this kernel over the last 2 1/2 years to the point where all we really need is the ongoing upstream / security patches you provide (unless you want to start fiddling at the margins with stuff like OC). Between all the hooks you've baked into the kernel and the control app, there's really not much left to ask for...
[Nexus 6  Original Android Development] BigDig:
Can you make double tap to wake work while rooted with Magisk Su?
[Nexus 6  Original Android Development] bautrupp:
What's there to post about? I'm using your kernel on 3 devices and I'm very happy with it.
[Nexus 6  Original Android Development] SynisterWolf:
Ever thought of making a kernel for the Nexus Player or will it not benefit from your work like phones/tablets do?
[Nexus 6  Original Android Development] franciscofranco:
That's a good argument. Choice to use ads is exactly that, to annoy and make users "unlock pro". Maybe you're not the target, but there are users who don't care about sending me 5 bucks (since is a one time payment) which hides the ads and gives me some coins. I think from the ads alone I haven't made more than 80 bucks since September, and that's ok, they ain't there to make money directly, but indirectly. Ads pay really badly (the little ones at least), if it's a full page ad then it's more, but I haven't tried them.

About the rest you argue, this is how ads work:

1 - You initialize the ads service;

2 - You run adView.loadAds() which will then start to display ads into the adview. If they have been previously hot cached they'll be displayed faster;

3 - When the app goes to onStop() or onPaused() the ads are paused so there should be no connections to retrieve more ads. From this point on I have no control over what happens, that code is all closed source from the Play Services/Firebase. Ideally ads should stop every request until the app is resumed

What was reported are connections made even if the app has been "donated on" before, which is why I was puzzled and I responded so accordingly.

Dunno. That requires a sepolicy change and the current state of sepolicy injectors is bad, and the only one that works reliably everywhere is SuperSu's builtin supolicy.

I don't have a Nexus Player, the user base is small that it would be a waste of my time. Plus I don't think it's a good idea to mess with a device that's connected to a TV, would be really bad to crash it mid Netflix episode.
[Nexus 6  Original Android Development] gk1984:
Did you end Nexus 9 support long ago due to the small amount of users too? Would love your kernel on my N9 too but not worth anyone's time maintaining for a small user group if there's a lot of work involved.
[Nexus 6  Original Android Development] franciscofranco:
I never had a Kernel for the Nexus 9, that device was a waste of time.
[Nexus 6  Original Android Development] gk1984:
Oh, interesting. I thought I saw 1 release very early on. And yeah... Over priced and under powered with crappy build quality. I'm got mine on a black Friday sale for a deep discount and it had no issues, even performs well. But I know how much of a cluster **** that tablet was. I wouldn't have bought it if it weren't for the sale.
[Nexus 6  Original Android Development] gideonlfc:
Peace and quiet is always a good thing to have in a community. So if the thread is quiet then it means a lot of users are happy. My only request would be if you could enable dt2w by default upon flashing the kernel instead of having to enable the feature in the app.

Aside this I leave everything as it is and battery life and performance has been awesome on DU rom.

Bless u Franco!
[Nexus 6  Original Android Development] franciscofranco:
New Naptime 3.2 release

In the quest for perfecting Android's Doze mode and injecting all your devices with outstanding battery life during idle I've pushed a new release of my app which gives you a great feature if you don't want/cant' disable motion sensors.

Here's a better explanation, copy pasta from the app's What's new section:

Introduced a new feature to re-apply Doze after an wakeful event (motion detection, some app that fires an wakeful alarm and doesn't properly terminate, priority GCM messages that wakeup the device for longer than needed, etc). It'll re-apply Doze ~1 minute after the wakeful event. It's less intrusive than disabling motion sensors altogether.

This feature and disabling sensors are mutually exclusive for obvious reasons.

There's probably a bug or two in there that I haven't caught, so let me know!

Naptime is free, so download it asap: https://play.google.com/store/apps/details?id=com.franco.doze
[Nexus 6  Original Android Development] Gveric:
To be clear, I'll still get message notifications when my phone's screen is off, right?
[Nexus 6  Original Android Development] NLBeev:
Nexus 6. Lite stockROM 7.1.1 march update of Danvdh. Unencrypted​.

Flashed r65. All working smoothly.

Thx.
[Nexus 6  Original Android Development] pkgnex:
Yes.

I installed the update, and have still been getting notifications with my screen off all day.
[Nexus 6  Original Android Development] Gveric:
Thanks.
[Nexus 6  Original Android Development] jake.nissley:
Is anyone missing all sound on r65? I'm on the latest omni rom with the March security update and am missing sound on notifications, phone calls, alarms, etc. However, reverting to r64 fixed the problem.
[Nexus 6  Original Android Development] pkgnex:
Omni probably doesn't have the full March security update, then. r65 is working on stock rom with March security update, but nothing previous. Sounds to me like Omni missed something. Since r65 works on stock, you should check with the Omni rom dev or ask others in the rom thread.
[Nexus 6  Original Android Development] jake.nissley:
Ah OK! Thanks! I was just curious if anyone else had the same problem.
[Nexus 6  Original Android Development] pkgnex:
No problem! You can just continue using r64 until omni is fully updated - there's no harm, you'll just be missing a few security updates until then.
[Nexus 6  Original Android Development] kierren:
I am running stock Android and just updated to the March 2017 build. When I install FK r65 the device boots normally, but when I then install SuperSU the device hangs at the start animation. I have tried wiping the caches after flashing, and I have tried both the stable and beta versions of SuperSU. I have noticed a number of other people on here having problems with r64 and r65 in a similar manner. Is the developer working on a fix for this? Has anyone found a work around for this issue? Has anyone switched to a different super user app? I mainly use this kernel for the battery saving and red-shift, so without root capabilities I will need to switch back to the stock kernel.
[Nexus 6  Original Android Development] franciscofranco:
I didn't see anyone reporting such thing. I have nothing to do with SuperSu, don't touch anything related to it. I'm sorry but that seems a bit of a random event :(
[Nexus 6  Original Android Development] requiiiem:
Maybe you are using 7.0?
[Nexus 6  Original Android Development] pkgnex:
Order of operations is important. Since the systemless implementation, you need to:

Take the update

Flash SuperSU

Flash custom kernel AFTER SuperSU.
[Nexus 6  Original Android Development] rogconnect:
May I ask if this kernel have that split screen problems like that other kernel have? Even I used interactive governor.

Edited

Tested the split screen happened. Have to stick to stock kernel.
[Nexus 6  Original Android Development] githyanki:
Sorry, hardware issue. If you had caught the issue earlier, Motorola would have swapped your device out. Don't think they will anymore since it is so old now.
[Nexus 6  Original Android Development] rogconnect:
Sorry, it's not hardware issue. Reverted back to stock kernel and No such issue. It's a known issue with Custom kernel.
[Nexus 6  Original Android Development] githyanki:
It is a hardware issue that only comes up when using a kernel that is optimized more than stock. All of the settings on stock are scaled back to safer levels to prevent issues from occurring, such as the screen tearing.
[Nexus 6  Original Android Development] kierren:
Definitely on 7.1.1 :)

---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------

Just tried this, same thing. Just the boot animation forever.

---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------

Sorry, I left out some information. This is the same exact bug that has been happening on r64 as well. Here are posts talking about it:

https://xdaforums.com/showpost.php?p=70924755&postcount=9388

https://xdaforums.com/showpost.php?p=70930985&postcount=9407

https://xdaforums.com/showpost.php?p=70936255&postcount=9410

https://xdaforums.com/showpost.php?p=70938327&postcount=9412

https://xdaforums.com/showpost.php?p=70941304&postcount=9418

https://xdaforums.com/showpost.php?p=70943433&postcount=9420

https://xdaforums.com/showpost.php?p=70946320&postcount=9424

https://xdaforums.com/showpost.php?p=70959779&postcount=9433

https://xdaforums.com/showpost.php?p=70990899&postcount=9444

https://xdaforums.com/showpost.php?p=71006476&postcount=9445

https://xdaforums.com/showpost.php?p=71020890&postcount=9447

https://xdaforums.com/showpost.php?p=71047116&postcount=9450

https://xdaforums.com/showpost.php?p=71048500&postcount=9454

https://xdaforums.com/showpost.php?p=71063873&postcount=9457

https://xdaforums.com/showpost.php?p=71069174&postcount=9464

https://xdaforums.com/showpost.php?p=71077326&postcount=9465

https://xdaforums.com/showpost.php?p=71077856&postcount=9466

https://xdaforums.com/showpost.php?p=71225299&postcount=9479

On either r64 or r65 my phone never goes past the loading animation when it is rooted. Flashing back to r63 allows me to boot.
[Nexus 6  Original Android Development] pkgnex:
Well, if it's on 7.1.1 and you're flashing in the right order, then you're having the same issue that some users have been having since r64 (and some are not). I don't think Franco has figured this out yet, and I don't think anyone aside from Franco is going to be able to help on this one...
[Nexus 6  Original Android Development] githyanki:
I have noticed this occurs when I flash and boot while on the charger. Perhaps just a coincidence.....
[Nexus 6  Original Android Development] Jon.StatiK:
Anyone else have issues getting root to work? I installed it like I do with any other kernel and root isn't sticking. I usually flash, unsu, kernel, magisk, phh's su. Magisk is there but it's saying it's not rooted. Any ideas? Only kernel I've had issues with and I see other people are using it. At a loss.
[Nexus 6  Original Android Development] Didgeridoohan:
I don't think it's a kernel issue. Why are you flashing phh's with Magisk? Magisk uses its own MagiskSU.
[Nexus 6  Original Android Development] Jon.StatiK:
I've never been able to get 11.1 to stick and for some reason 10.2 with phh's flashable su was the only way I could get root.
[Nexus 6  Original Android Development] Didgeridoohan:
Even with v10.2 you wouldn't have to flash phh's since it installs topjohnwu's phh's fork by default.

But, like I said, not about the kernel... Take this to the Magisk forums if you'd like to continue troubleshooting.
[Nexus 6  Original Android Development] gk1984:
Try flashing the magisk uninstaller, boot, then reflash magisk and the modules you use.
[Nexus 6  Original Android Development] Jon.StatiK:
Interesting thing. I uninstalled magisk with zip, used osmosis unsu zip and flashed original rom boot img and rebooted to having root. Wtf.. Phh's was still there even though it was removed?
[Nexus 6  Original Android Development] The Doctor04:
ROM I am on finally updated to March blobs. Installed r65 Franco, and still same problems with r64.... Infinite bootloop. Normally wouldn't​ be too upset but I bought the pro version of the app and I haven't been able to use the last two updates. What can I do help show the problem? Same deal as everyone else reporting it...Get past pin code lock screen, starting Android hangs for about 60 seconds and then boot loops. Flashed back to stock PN kernel and boots right up. Any help would-be appreciated, thank you
[Nexus 6  Original Android Development] firewhank:
Is it possible to add the option to disable the bluesleep wakelock in the Franco app ?

My Nexus 5 with the Franco kernel has it
[Nexus 6  Original Android Development] githyanki:
Logs did help. A lot of people talk about this issue, but no logs. I don't think Franco can do anything by guessing.
[Nexus 6  Original Android Development] The Doctor04:
How do I pull a log for something that won't boot?
[Nexus 6  Original Android Development] rignfool:
What is your root solution...

Did you flash the ROM...Boot... Reboot recovery... Then flash kernel?

I know it shouldn't matter...But it might
[Nexus 6  Original Android Development] The Doctor04:
Rom, superSU 2.79, boot, restore, kernel
[Nexus 6  Original Android Development] githyanki:
https://xdaforums.com/showthread.php?t=1726238

Using adb works during boot.

adb logcat -v long > problem.txt
[Nexus 6  Original Android Development] The Doctor04:
ty...I will get rolling on that. Will post a long here soon

---------- Post added at 10:03 ---------- Previous post was at 09:22 ----------

So you got me thinking...I flashed without rooting first. dirty flash -> kernel -> reboot.....POW! Booted right up! Flashed SuperSu 2.79 and it worked. However, it took a littler longer than it did without root. Looks like we are rocking now! Hoping I don't have to redo all of this when r66 drops. thanks [MENTION=1112220]Ring[/MENTION]fool
[Nexus 6  Original Android Development] rignfool:
I don't know why... But I had the same issue with this kernel... It seems fine once it's made that first boot
[Nexus 6  Original Android Development] The Doctor04:
Did a few reboots now to make sure, and yeah, she fires right now without missing a beat. Thanks again!
[Nexus 6  Original Android Development] the_duck:
Just tried flashing the latest kernel on my Nexus running stock ROM, wouldn't boot...just stuck on boot screen. Reflashed image from Google to restore stock kernel and that worked fine. Think there's something with the latest Franco Kernel, I also had Elemental kernel purchased from a while ago, flashed that kernel and it worked fine and I'm running it now.

Really do want the Franco kernel to work, but don't have time to fidget with it too much...I did try to reflash ROM, Root, install Kernel and got stuck on Boot screen 3 times though. Strange was the first time it worked OK, but I wiped my cache & dalvik cache and that's where my problems began.
[Nexus 6  Original Android Development] gk1984:
Make sure your version of Android matches the requirements of the kernel. Should be 7.1.1 and r65 requires the March security update.

No one else reported any issues and it's working fine for me as well.
[Nexus 6  Original Android Development] the_duck:
I'm running "7.1.1 - N6F26U, Mar 2017" update.

You mentioned that nobody else is having problems, but just going up a few posts there's someone experiencing the same thing as I am (that's what prompted me to post my issues as well since the thread seems a little dead):

Perhaps r66 will work, I'll just run Elemental unless I find some extra time to try and get it to work. Before I wiped my system cache, it worked well...but that was only for a few hours. Perhaps I can just try to flash it so i can get the logs, what would be the best way of doing this if I can't get past the boot loading screen?
[Nexus 6  Original Android Development] The Doctor04:
Dirty flash your ROM, flash Franco, and reboot. I let it settle down for a few mins, booted back to TWRP and then flashed root. Working like a champ now
[Nexus 6  Original Android Development] rignfool:
You can also download flashfire from the playstore and give that a shot... It seems to be a bit more forgiving... But that's probably because the ROM has already booted the once
[Nexus 6  Original Android Development] the_duck:
That did it. Dirty flashed in NRT, let it reboot. Used NRT to flash Franco Kernel and also had the cache and dalvik formatted in this operation. Booted up fine, then used NRT to root and flash TWRP and reinstalled Franco App and confirmed kernel is running.

So trying to autoflash r65 from the Franco app after root causes the endless boot.but flashing kernel before root seems to do ok.

Thank you all for your help...It's been a few years running a custom kernel but now I want to maximize my N6, missed now snappy my phone could be.
[Nexus 6  Original Android Development] The Doctor04:
Franco will have to provide some more insight as to why flashing the kernel before root is the way to go. Maybe something changed on the SuperSu side, idk, but glad you got it working. I agree, Franco seems to be a little more zippy than Elemental X on the N6
[Nexus 6  Original Android Development] Danne9900:
Same problem with boot

Hello!

I have the same problem with r64-65 the only one working now is r63.

Running on latest version of pure nexus.

Tried every possible combination.

Also got the pro version of franco bit cant use it due to the boot loops. Please help Franco!
[Nexus 6  Original Android Development] rignfool:
Did you read the last couple of posts and flash root after the first boot?
[Nexus 6  Original Android Development] Danne9900:
Yes everything works until i flash supersu

---------- Post added at 12:49 PM ---------- Previous post was at 12:19 PM ----------

So now i have to have the old version and then i have No sound
[Nexus 6  Original Android Development] rignfool:
Ok... You didn't read the posts...

Flash whatever ROM/gapps... Flash root solution... Boot...

Wait... Wait some more...

Reboot, flash kernel...

---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------

@franciscofranco

Can I add another performance profile to the init script and toggle it with setprop?
[Nexus 6  Original Android Development] Danne9900:
i flash root first after rom and then boot up, everything works.. i wait for 1:34h then going in to recovery and flash kernel the phone will not boot up and the i have to flash r63 again.

If i do it the other way around it wont boot because i flashed root.

Something must be diffrent from r63-r65.
[Nexus 6  Original Android Development] rignfool:
What ROM?
[Nexus 6  Original Android Development] Danne9900:
Pure Nexus March update
[Nexus 6  Original Android Development] Prod1702:
happen to me a few times, since the wifi changes a few versions back I have not been able to connect to my 5ghz wifi network. I only see my 2.4ghz network. I know the 5ghz works since my wifes iPhone sees it and my tablet does. maybe it has to do with your problem as well.
[Nexus 6  Original Android Development] noneabove:
Nah looks way too blue to me
[Nexus 6  Original Android Development] blueren:
[MENTION=3292224]franciscofranco[/MENTION] - what sorcery does one+ use to get such ridiculously high battery time?
[Nexus 6  Original Android Development] holeindalip:
Location is on battery savings and location reporting is off
[Nexus 6  Original Android Development] Nocturnal86:
Yea it looks nasty blue. You can drop the first two numbers from 255 by 10-15 points and leave the last number at 255 it looks less yellow and not extreme blue tint
[Nexus 6  Original Android Development] zephiK:
For one, its using a 1080p screen.
[Nexus 6  Original Android Development] kergefarkas:
Yes. I used similar "blue tinted" setup on my GNex as well, but there was some gamma tweaking and other things as well. I don't know, to me honestly it doesn't look "blue tinted", more like extremely cold or IDK. But you can check the photo of the two phones side-by-side. I always prefered a much "colder" setting on TVs as well. The N6 still feels to warm and a bit yellow to me, even with these values. But I think it gives better and more eye-friendly whites, while maintaining the awesome black of amoled. And the other colors arent off either.

On the GNex currently I only have the CM inbuilt calibration possibilities, I tried to replicate them on the N6.

R: 40% G: 40% B: 50%

Gamma: -5 -5 +5 (RGB)

Edit: and yes, when you first enter these values it will take a couple of minutes to adjust your eyes to it. But after that, I think you will not really notice any blue tinting. But the original 255/255/255 is indeed extremely yellow tinted, like the GNex before. I'm not sure why Google tends to do that.
[Nexus 6  Original Android Development] ZiggSVO:
237 235 255 Looks good to me.

And check this post out:

http://xdaforums.com/nexus-6/orig-d...tic-kernel-t2954316/post57265483#post57265483

Sent from my Nexus 6
[Nexus 6  Original Android Development] kergefarkas:
Wow, thanks. First it seemed a bit way too dimmed, but after a couple of secs your eyes adjust perfectly. And white won't burn out your eyes.
[Nexus 6  Original Android Development] suku_patel_22:
I am using 230/240/255
[Nexus 6  Original Android Development] cobyman7035:
2.5hrs SOT… so far at 36%used… at this rate I wont need to charge my battery much… lol it will last me 3 days

I also use rgb 237.235.255… iphone ?5 colors

Via my NeXus™ 6 on Tapatalk⁴
[Nexus 6  Original Android Development] anuragvivek93:
Wow!
[Nexus 6  Original Android Development] aewig:
Everyone has a different screen and different preferences for white balance. I might suggest that people not happy with their calibration simply play with the RGB numbers themselves instead of trying to mimic what others are using. One person using a calibration tool on their particular screen doesn't mean you will get the same results if you apply the same values - from my experience as someone who owns a calibration device and gets different results on the same model of displays.
[Nexus 6  Original Android Development] numerouknow:
it looks like sensor_ind isn't letting my phone go to deepsleep

i searched a bit n found a lot of posts suggesting that its related to hangouts. but i do not have hangouts installed. on searching a little more found posts that linked it to sensors.qcom

to b honest i haven't checked if this is actually causing a severe battery drain but m assuming it will, considering my phone has been awake almost all the time.

this was not the case until yesterday.

ps: m on pure shamu b3.92 + franco kernel r4 + vomertweaks quadmode