• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[KERNEL][N5X] FrancoKernel ⚡️- r64 - 7th December - Oreo & Pie

Search This thread

franciscofranco

Recognized Developer
Dec 9, 2010
24,725
136,413
Carcavelos
I don't think I'm doing anything unusual, I just press the download button and the download notification immediately shows 100% and will just keep going until I force close FKUpdater. Maybe it's something on my end? I don't have a crazy setup. Running Pure Nexus, no xposed.

Can you grab me some logs?

adb logcat | grep com.franco.kernel

Thanks.

EDIT: are you sure it consumed your data? Because I just tested with a malformed URL, producing the same "100%" notification like yours and it doesn't download anything even if I leave it there. I'm seriously boggled and without some logs (not sure if the logs I asked will show anything though) I can't even understand, because the URL I pass down is the same for every other user (and for myself too) and it works fine - and it's the same method I use for years, without hiccups too.
 

Attachments

  • 042716045518.png
    042716045518.png
    125.4 KB · Views: 186
Last edited:

crafty35a

Senior Member
Aug 16, 2012
60
18
I'm not near a computer right now but I pulled this with the catlog app. I killed the app a couple of times so that will be part of what is logged- let me know if you need anything else! I can pull logs via adb in the morning if it makes a difference.
 

Attachments

  • 2016-04-27-00-05-27.txt
    2.5 KB · Views: 6

franciscofranco

Recognized Developer
Dec 9, 2010
24,725
136,413
Carcavelos
I'm not near a computer right now but I pulled this with the catlog app. I killed the app a couple of times so that will be part of what is logged- let me know if you need anything else! I can pull logs via adb in the morning if it makes a difference.

Duh, that's the Free apk, not the paid one. The free version is outdated and not working with the updated server set-up. I'll be updating it asap, probably until the end of the week. Anyway, I'm sorry if it wasted 2gb of your data. Although that sounds kinda odd to me since it's basically downloading 0 bytes from a non-existent url, I hope that's some reporting bug.
 
Last edited:
  • Like
Reactions: MaLiXs

sgravel

Senior Member
Jul 1, 2008
74
14
Some users reported Haptic Vibration setting wasn't restoring on boot using FKUpdater. I just can't reproduce it. Can anyone with this issue let me know which values to->from are you using?
From the default (think it's 18) to 50. Probably kinda high, I know. I'm on Pure Nexus, and it's not been sticking on reboot for any build since the kernel was available for the 5x. Thanks!

Sent from my Nexus 5X using Tapatalk
 

pkadavid

Senior Member
May 12, 2011
272
74
Austin, TX
From the default (think it's 18) to 50. Probably kinda high, I know. I'm on Pure Nexus, and it's not been sticking on reboot for any build since the kernel was available for the 5x. Thanks!

Sent from my Nexus 5X using Tapatalk

I'm on 50 as well. 18 is so low that the motor can't properly start spinning when receiving a message. E.g. at 50, it buzzes twice and at about the same intensity as stock. At 18, it feels like a different pattern but one that is sporadic along with very light. Feels like it's dying.

For what it's worth, the values stuck for me on restart using both the newest version of FKU and the previous. On stock.
 

sgravel

Senior Member
Jul 1, 2008
74
14
I just tested and it sticks just fine. I rebooted more than 10 times, always worked. Sorry.
just updated my app and rebooted to see. No luck, but I hadn't let it prompt for root access again after the update and before rebooting, so I will try again now that I've done that. If that doesn't work, I'll try clearing data on the updater app. I think I read a few posts ago that that worked for someone. Thanks!

Sent from my Nexus 5X using Tapatalk

---------- Post added at 01:12 PM ---------- Previous post was at 12:59 PM ----------

just updated my app and rebooted to see. No luck, but I hadn't let it prompt for root access again after the update and before rebooting, so I will try again now that I've done that. If that doesn't work, I'll try clearing data on the updater app. I think I read a few posts ago that that worked for someone. Thanks!

Sent from my Nexus 5X using Tapatalk
Clearing data in the updater app did the trick. Thanks for a great kernel!

Sent from my Nexus 5X using Tapatalk
 

dumbhorse

Member
Mar 12, 2016
24
3
Uppsala
ackl.one
Nothing sticks for me. Not in previous version or updated one. FKUpdater doesn't seem to run at boot. At least it doesn't ask for su. :(

Edit: I use Xposed though so maybe I brought this on my self. :victory:

Sent from my bullhead using XDA Labs
 
Last edited:

kiden

Senior Member
Feb 3, 2010
170
88
Chicago
For me I can replicate it like this:

1. Fresh install of ROM or app. (Clearing data works)
2. Open and go to kernel settings.
3. Change value from 18 to 60 or 50 or anything that you like. I've tried with many higher values and the issue persists.
4. Flip the switch to set on boot.
5. Reboot and it works.
6. Go back into the app, change value from what you set it to before to anything else.
7. Reboot. Now it's not what you set it to either time, but 18 which is the default.

I get the toast notification every time so the app is running at boot. Hope this helps!
 

franciscofranco

Recognized Developer
Dec 9, 2010
24,725
136,413
Carcavelos
For me I can replicate it like this:

1. Fresh install of ROM or app. (Clearing data works)
2. Open and go to kernel settings.
3. Change value from 18 to 60 or 50 or anything that you like. I've tried with many higher values and the issue persists.
4. Flip the switch to set on boot.
5. Reboot and it works.
6. Go back into the app, change value from what you set it to before to anything else.
7. Reboot. Now it's not what you set it to either time, but 18 which is the default.

I get the toast notification every time so the app is running at boot. Hope this helps!

I just reproduced it following your steps. No idea why it happens though. I'll post about it when I find more info.
 
  • Like
Reactions: gerbig

ulxerker

Senior Member
Jul 6, 2015
4,141
1,083
Google Pixel 5
For me I can replicate it like this:

1. Fresh install of ROM or app. (Clearing data works)
2. Open and go to kernel settings.
3. Change value from 18 to 60 or 50 or anything that you like. I've tried with many higher values and the issue persists.
4. Flip the switch to set on boot.
5. Reboot and it works.
6. Go back into the app, change value from what you set it to before to anything else.
7. Reboot. Now it's not what you set it to either time, but 18 which is the default.

I get the toast notification every time so the app is running at boot. Hope this helps!

I just reproduced it following your steps. No idea why it happens though. I'll post about it when I find more info.

I also checked against. After each change of any setting you do, you have to disable and re-enable the switch for applying on boot again, no matter if you did it already before. This way it works so it isn't really a critical issue.
 
  • Like
Reactions: linqdesires

franciscofranco

Recognized Developer
Dec 9, 2010
24,725
136,413
Carcavelos
For me I can replicate it like this:

1. Fresh install of ROM or app. (Clearing data works)
2. Open and go to kernel settings.
3. Change value from 18 to 60 or 50 or anything that you like. I've tried with many higher values and the issue persists.
4. Flip the switch to set on boot.
5. Reboot and it works.
6. Go back into the app, change value from what you set it to before to anything else.
7. Reboot. Now it's not what you set it to either time, but 18 which is the default.

I get the toast notification every time so the app is running at boot. Hope this helps!

Just found the issue!!!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 237
    Hi all.

    Compatibility:
    It should work on any rom by following this logic:
    Builds (starting with r1) are Android 6.0.1 Marshmallow only.
    Builds (starting with r17) are Android 7.0 Nougat only.
    Builds (starting with r28 up to r37) are Android 7.1.1 Nougat only.
    Builds from r38 up to r44 are for Android 7.1.2 Nougat
    Builds from r45 up to r48 are for Android 8.0.0 Oreo.
    Builds from r49 are for Android 8.1.0 Oreo.

    Download:
    https://francokernel.app

    Installation:
    Flash the zip in your recovery
    or
    Auto-flash from Franco Kernel Updater app

    Features:
    1 - Legendary battery life
    2 - Flash & forget
    3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
    4 - Bypasses the verified boot flag for Android Pay compatibility (root still breaks Android Pay but that's your own problem)
    5 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
    6 - Support for FKUpdater's Performance Profiles
    7 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
    8 - Seemless integration with my app FKUpdater
    9 - No crap placebo patches, or "magical" optimizations
    10 - Probably more, check my github for all the details - the code speaks for itself

    Changelog:
    https://francokernel.app
    Scroll down, choose your device & select the latest release to see the changelog.

    Source:
    https://github.com/franciscofranco/bullhead

    Follow me on the interwebs
    Google+
    Twitter

    Google+ FK community
    https://plus.google.com/u/0/communities/117966512071636110546

    Kernel Manager for Franco Kernel demo

    Disclaimer to moderators:
    Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.

    Cheers!
    157
    Current r1 is not yet complete, I think it only lacks sound control, but it's pretty much done.
    Took me a little while to find the right balance, this little bastard lags easily, but this Kernel is pretty much a "clone" of FK for the 6P so I'm sure you'll have some fun with improved battery life.

    FKUpdater will be updated tomorrow to support this Kernel and the final r1 release will also be out.
    Any feedback about UI responsiveness and anything else that comes to mind, now's your chance to talk.

    Two things to note though, EIS video stabilisation is enabled automatically with FK, just check your Camera app and you'll see it, and FK ships with a slightly cooler display colour temperature, and a very slight saturation boost.

    I wasn't supposed to work on this device because I didn't want to shell out 450 euros for a device I wouldn't use outside Kernel/app development, but in the end I did it for you.

    Enjoy it & you're ducking welcome.
    43
    New Franco Kernel version for the Nexus 5X

    r35
    1. Offload a lot of background daemons to the system-background group, which only allows them to run on cpus 0, 1 and 2, freeing all other cores, specially the big cluster. This will reduce needlessly cpu wake-ups from idle, and largely reduce processing power requirements from cpu 3, 4, and 5 (4 and 5 are part of the big cluster, which uses a lot of energy)
    2. Lower power consumption from the big cluster by lowering the occurence of sample rate which'll in turn make the big cluster cpus less nervous and say in lower frequencies more often. In contrast little cluster is a little more forgiving and scales up a little easily. Since the little cluster uses 4 times less power, this is just fine
    3. Tweaked Performance Profiles, Power-saving now turns off the big cluster to save precious power, but the little cluster will be boosted for longer during input touch events

    zip: https://kernels.franco-lnx.net/Nexus5X/7.1/anyKernel/fk-r35-anykernel2.zip

    Franco Kernel Manager & Updater is the best companion for this Kernel (https://play.google.com/store/apps/details?id=com.franco.kernel)

    If you don't (yet) have my full featured app you can always just download its free counter part which lets you seamlessly and automagically update Franco Kernel on your device. It's free and my cat approves! (https://play.google.com/store/apps/details?id=com.franco.kernel.free)

    I also strongly suggest you install Naptime (https://play.google.com/store/apps/details?id=com.franco.doze), for free, to achieve the best battery life through out the day. Try it, you won't be disappointed!
    39
    Alright r46 is out. Rebuilt everything from scratch like I should've done in the first place. Everything should be fine now. Sorry for the delay, been busy with lots of things and rebuilding the entire tree on top of the vanilla sources is just tiresome and a pretty long process.
    You can auto-flash it with my app http://get.franciscofranco.xyz or manually through the links in the OP.
    36
    Ok similar to what I've been doing to the 6P, 6 and 5, we are now able to flash r5 onwards on any available rom. This is not yet available through FKUpdater (it needs an update, working on it), but you can download it from my server and play with it. Instructions below and in the OP:

    Download:
    Flash the latest release in your recovery:
    http://kernels.franco-lnx.net/Nexus5X/6.0/anyKernel/
    If you're already on r5, or newer, disregard the messages below - if not:
    * If you're on stock rom + r4, or older, you should be flashing stock boot.img first, then r5, or newer;
    * If you're on a custom rom + r4, or older, you should dirty flash the rom (or extract its boot.img and fastboot flash it) and then r5, or newer;

    Installation:
    1 - Flash the bloody zip on your recovery

    As for the changes compared to r4 I added more ways to prevent memory starvation, reduced power consumption during screen off and other security related patches.

    You're ducking welcome.