yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] bdwilk:
Bwahaha. Well I will use my phone. It charges to 100 so I'll charge it to 100. I will not baby it praying it lasts for years. This isn't my first phone, and I promise it won't be my last. It's like buying a sports car and driving 20mph because you want it to last forever when you never got to enjoy it in the first place. Quit worrying about this stuff and use your device.
[ONE Original Android Development] uudruid74:
No. The phone knows its at 100% and turns off the charging circuit. Otherwise it could make the battery explode!

Android goes one step further. It's not good to keep a LiIon battery at 100% as it will decrease the life of the battery. So, it switches to battery mode and starts running off the battery while showing 100% charge. Once you unplug it, it will slowly drop the shown charge level down to the actual.

There is nothing wrong with charging overnight

---------- Post added at 12:26 AM ---------- Previous post was at 12:20 AM ----------

So you are saying that if I charge my battery to 100%, after 2 years I will only have 80% of my battery left.

So, I should make my battery last longer by only using 80% of the battery. Wait ... isn't that the same thing as having a battery that is already damaged down to 80%? You only gain years down the road when charging to 100 would leave you with less than 80, while your 80 will last maybe 4 years like that.

A new battery is like $10 or so and takes maybe 10 minutes to replace. I can do that once every couple years.
[ONE Original Android Development] Gawd:
End this battery charging discussion already

For further info, read here
[ONE Original Android Development] SaurabhMumbaiOneS:
Ahh...Sorry for sparking such a conversation in Original Development thread. But hey, thanks for all the info and now I know what to do :highfive:
[ONE Original Android Development] counterfeit187:
Good to use with Android 7.1.2?
[ONE Original Android Development] ziepicwaffle:
Yep using with idprophecy 7.1.2 with no problems.
[ONE Original Android Development] :
How much SOT you get with this combo?
[ONE Original Android Development] sakarya1980:
Hi, i have a problem with our r45 Kernel. My phone stuck in the Bootloop when i use your FK updater :( View attachment 4119334

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] CooperBrick:
Because this kernel is for lineage based rom not for oos
[ONE Original Android Development] sakarya1980:
R45 is for oos?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] se7enlyn:
Yes each and every build is made for lineage os only

Edit : No each and every build is made for lineage os only
[ONE Original Android Development] Timmmmaaahh!:
No, for COS, not OOS. Hence the "[LineageOS]" in the title, it's all COS/CM/LOS (all the same family) based. Read the OP again. OOS isn't even mentioned.

You meant 'no', lol.
[ONE Original Android Development] se7enlyn:
Yes, I meant No, :laugh:
[ONE Original Android Development] ziepicwaffle:
Say about 5 hrs SOT, lasts the whole day. Have 10%remaining. Mostly on LTE, use Facebook, messenger, Snapchat, 1hr of Spotify. In my books it's pretty good :D.
[ONE Original Android Development] franciscofranco:
Over 9000 hours.

This Kernel isn't for OxygenOS on this device... -_-
[ONE Original Android Development] Бахрам Байрамза:
can you add hid patches and add patches for support WIFI ADAPTER to Franco Kernel? I'm using Nethunter addon.
[ONE Original Android Development] sabrefresco:
That's disappointing. :rolleyes: I was expecting at least 9001.
[ONE Original Android Development] neverone:
[MENTION=3292224]franciscofranco[/MENTION], this may be a newbie question, but I don't seem to find the solution. I'm on latest LOS 10/04 (made a clean flash), and just a few days ago I updated your kernel to r49, and am using both FK Manager and Naptime. I seem to have problems with Bluetooth not being constantly on (I need it to be constantly on to connect to my Garmin watch). I know BT connectivity is a known issue with LOS and that it can be fixed by disabling system profiles in phone settings (which I did). However after some time during the day I notice that it turns itself off. I think the problem may lie with Naptime, and how aggressively it turns some system functions off, but I'm not sure completely. I also adjusted per app profiles in FK Manager, but I didn't touch bluetooth settings nor the Garmin app settings.

Any chance you could help me out? Thanks!
[ONE Original Android Development] DerRomtester:
Doze could affect that

https://developer.android.com/training/monitoring-device-state/doze-standby.html
[ONE Original Android Development] franciscofranco:
The Kernel doesn't touch any of that. Maybe you need to unoptimize Garmin's app on your phone to be able to bypass doze (same happens on Android Wear's app).
[ONE Original Android Development] neverone:
It seems that both [MENTION=4804871]DerRomtester[/MENTION] and you were right. Doze settings in Naptime app andn in the OS itself seem to have been interfering with BT settings. In the Naptime's settings I put Garmin's app on a whitelist, and in battery optimization settings I turned battery optimization off for the app, and so far, BT seems to be working fine and it doesn't turn off on itself.

On the other hand, it's interesting that in Naptime's whitelist I can only select one app. How so?
[ONE Original Android Development] franciscofranco:
Platform limitation, nothing I can do. That's only for allowing a specific app to request sensors changes if you disable the sensors through Naptime.
[ONE Original Android Development] neverone:
That's a shame. Well thanks anyways for pointing the right direction again! :)
[ONE Original Android Development] franciscofranco:
I try! :) there's still so much to learn.
[ONE Original Android Development] franciscofranco:
Just a little FYI I pushed a new version of Servicely. It goes very well with Naptime and it's free. XDA apk is ad-free, but the Play Store version has full screen ads every once in a while. Enjoy: https://xdaforums.com/android/apps-games/root-servicely-installed-apps-services-t3076769
[ONE Original Android Development] DJPRMF:
Great work porting this to LineageOS... Thanks!

One quick question, the cores stay in idle when the screen is on, but they go offline when the screen is off, right?

If not, this doesn't affect the battery a little? (im still testing the battery part, BTW :) )

Thanks
[ONE Original Android Development] Timmmmaaahh!:
Agh, help! My battery is draining because of all the Franco apps I have installed! XD

Hah, thanks. Giving that one a whirl as well.

Sizzled with Bacon
[ONE Original Android Development] BishnoiAkshay29:
FKApp shows that oops no kernal is available for your device ?
[ONE Original Android Development] sohansonu:
He didn't release the update for the latest weekly release. You'll have to wait m8.
[ONE Original Android Development] erfan komidjani:
hi franco :)

thanks for the support of OPO.

franco can you fix the low brightness of the torch and the mechanical sound of camera (during closing the camera app or turing of the torch)

thanks :good::good::good::good:
[ONE Original Android Development] BishnoiAkshay29:
The app also doesnt show which version of kernal i have installed
[ONE Original Android Development] ScuZziE:
I just flashed latest LOS nightly version 14.1-20170424 and franco kernel updater is telling me that only version r1 is available. Should I proceed to flash that kernel or wait for the next update? Is version r49 compatible with Nougat v7.1.2?
[ONE Original Android Development] se7enlyn:
Flash R49
[ONE Original Android Development] sohansonu:
Cause after updating, the kernel here wiped. Did you reinstall r49?
[ONE Original Android Development] pauliprokki:
Works fine!
[ONE Original Android Development] franciscofranco:
Hmm... it works fine here. What app version do you have?

Anything else?

Hmm... do you have the latest app version? As soon as I flashed the latest LineageOS build and booted up my app told me to flash r49...
[ONE Original Android Development] Gautham0123:
I installed the kernel starting with r49 in OnePlus One Lineage OS 7.1.1. But in the app i get "No FK available for your Android version, Most likely coming soon". I tweaked with other settings but I do not know if they are working or not.
[ONE Original Android Development] ScuZziE:
I am using the latest app version. Not sure where has gone wrong but I downloaded R49 from your webserver and flash it manually. Everything works perfectly fine as intended and the app is now telling me that I have the latest kernel installed. :cool:
[ONE Original Android Development] :
That is fixed by flash Hybrid blob and another custom kernel such as lightning oos blob kernel
[ONE Original Android Development] Vorshim92:
multirom with patch kexec hardboot is not more supported by francokernel? :(
[ONE Original Android Development] JJohnson1988:
Breaks encryption, so, no.
[ONE Original Android Development] guille26:
Could you elaborate, please?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] franciscofranco:
Word of advice, forget about it. The name of that mod alone makes me shiver to what's, most likely, a recipe for disaster.
[ONE Original Android Development] donalgodon:
Forgive my ignorance, but does Franco's kernel include merges for updated versions of the upstream linux?
[ONE Original Android Development] Wombat:
I can confirm WiFi problem with the r1&r2.

WiFi does not re-enable after sleep unless rebooted, stock kernel works fine.

64GB White OPO China with CM11
[ONE Original Android Development] franciscofranco:
No, they are pointless.

Of course Wi-Fi works fine after sleep. Wi-Fi drivers are 100% stock, no change what-so-ever. This is for stock firmware, if you're using CM11 then you're on your own.
[ONE Original Android Development] Wombat:
Stock firmware is CM11/CM11S etc this isn't for ColorOS??

I'm running the OTA update for the OPO CM11S and with this kernel the WiFi will not re enable after more than 10 min in sleep. This is with WiFi settings not set to stay on while sleeping (battery saving), with stock kernel WiFi re-enables itself fine.
[ONE Original Android Development] franciscofranco:
Stock is CM11S yes.

Sorry I can't help you, it works fine on my device, I can't debug that, specially since I didn't do any change what-so-ever to Wi-Fi.
[ONE Original Android Development] giaur:
Are ntfs and exfat supported?
[ONE Original Android Development] franciscofranco:
NTFS yes.
[ONE Original Android Development] giaur:
Sorry, can't use your kernel. Tried on MoKee, after flashing Android System UI FC, then bootloop. I even can't unlock screen. As I can see, they prepared their own kernel, perhaps their rom is incompatible with CM's recent kernel. Did you tested it on other roms? Or only CM is supported?

I reverted original MoKee boot.img and again everething works.
[ONE Original Android Development] franciscofranco:
As I said before, this is for stock firmware, CM11S.
[ONE Original Android Development] giaur:
Ok so I can't use it.. too bad, but I'm not planning to return to CM currently.
[ONE Original Android Development] Ok_Kaleidoscope5109:
Can anyone confirm this on r2? I'm doing a battery test right now (idle test), so I don't want to disturb my phone.
[ONE Original Android Development] gro95qg:
I had a boot loop after install :/
[ONE Original Android Development] tonu42:
Working fine for me.
[ONE Original Android Development] Ok_Kaleidoscope5109:
Installing the OTA right now. Hopefully Franco kernel still works :)
[ONE Original Android Development] boober78:
Flashed yesterday. Great to have you here. Hopefully the color control will be operational soon, because some say there is a yellow tint. I am not experiencing it myself.
[ONE Original Android Development] gro95qg:
Which rom ?
[ONE Original Android Development] tonu42:
The only ROM that is supported by this kernel. Cm11s, which ships with the international version. If you are using another ROM bug reports don't belong here because franco only supports CM11s.
[ONE Original Android Development] franciscofranco:
Most likely not, because I had to revert a patch for it to work on the 22S, I'm finishing booting then I'll most likely have to re-revert that patch!

EDIT: actually r2 works fine on the new OTA, that patch that I reverted still borks boot if I apply it again, so maybe CM forgot something on userspace side, that's my guess.
[ONE Original Android Development] franciscofranco:
Nah, double tap to wake code is unchanged, most likely the usual user error or something.
[ONE Original Android Development] gro95qg:
ok thank you :good:
[ONE Original Android Development] Red5:
Yeah, when is cm11s gonna be updated?
[ONE Original Android Development] zephiK:
That was posted 2 days ago on the OPO forums.
[ONE Original Android Development] LiquidSolstice:
To be honest, I much rather prefer the cleaner-looking "4G". H and H+ are not "4G", no matter how much American carriers try to convince us it is. "LTE" just looks really strange to me in the title bar.
[ONE Original Android Development] zephiK:
Would you rather have "4G LTE?" http://img.tapatalk.com/d/14/07/27/ugugyqu6.jpg :p most other devices like G3/S5/M8 all have 4G LTE
[ONE Original Android Development] simo.scorpion:
hello francisco, yesterday I flashed the r9, this morning when I woke up the imei was unknown, fortunately rebooting is back in place, using your kernel since r7, but this is the first time that has happened to me.
[ONE Original Android Development] oscarmalo:
thanks franco jeje the best kernel :)
[ONE Original Android Development] clock51:
Inviato dal mio One

Idem simo.scorpion
[ONE Original Android Development] E_n_T:
just to be certain. i have just rooted my 1+ not changed into another rom. still using cm11s. this kernel will work on it? i have experience from flashing befor ebut i just need to be deadcertain so i dont screw up. thanks in advance :)
[ONE Original Android Development] b3ta:
Yep, it will work. Just flash it through custom recovery
[ONE Original Android Development] armini0:
Flashed this after unlocking bootloader, rooting etc.

Too bad I was not able to find if a wipe data/dalvik cache was needed before flashing. I guess this isn't? I just did a nandroid back-up and flashed the zip through CWM (philz edition) without any wipes, it booted fine. After that changed Runtime from Dalvik > ART, so I will test this a bit :)

Keep up the good work!
[ONE Original Android Development] franciscofranco:
Yes its magic. Little gnomes woke up and ate your imei while you sleep. Thats called LittleGnomeOmFGboostThingyPowerInteliDriver.
[ONE Original Android Development] franciscofranco:
Im aware. That is because of the lateste scheduler patches from CM. Its a very rare race condition which I will investigate further when Im back home :)
[ONE Original Android Development] E_n_T:
What should i use for rgb control?

Edit: trickster did it.

Skickat från min One via Tapatalk
[ONE Original Android Development] armini0:
Does anyone have recommended trickstermod settings for this kernel? currently running the default and -25mv on MPU across the board
[ONE Original Android Development] lordlambda:
Running r8 with same settings. Runs well! Would like to edit the hotplug settings but trickstermod does not allow it... Have to buy flu :rolleyes:

Gesendet von meinem One
[ONE Original Android Development] zephiK:
Think of trickster as a universal remote. It works for everything, but not always ensuring it has access to everything. If you like the idea of trickster, and like Franco kernel. Buy fku, you won't be disappointed. Plus you get per apps mode giving you different configuration set ups based on what app is being used
[ONE Original Android Development] jcpq:
This kernel runs great on mahdi rom?
[ONE Original Android Development] lordlambda:
As I said. Will buy it soon

Gesendet von meinem One
[ONE Original Android Development] zephiK:
Search the thread or go back a couple pages and you'll know how to make Franco boot on mahdi.
[ONE Original Android Development] bp328i:
I'm running CM11S and mine says LTE, you can use Gravity Box for this change.
[ONE Original Android Development] CooperBrick:
Ho Franco, i have a problem with the kernel manager

After a fresh install if i see the CPU input is 1728mhz@60ms input booster, but if i use the "balanced" profile in the app It becomes 1497mhz@150ms, and this profile gets applied every time with the app profiles.

So what is the real "balanced" profile?
[ONE Original Android Development] guille26:
Thank you. Do you have any tip about how to increase flashlight bright? Maybe modifying some file?

Thanks again

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] DJPRMF:
The flashlight is already in the "max"….

There is nothing to change there, i think...

If isn't bright enough, or is a problem with the LED or is already where is supposed to be :)
[ONE Original Android Development] arifnasirshaikh:
Deleted
[ONE Original Android Development] guille26:
Other ROMs have a much brighter led, I don't know if it's because the ROM or the kernel, that's why I asked it.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Timmmmaaahh!:
Have you tested this properly? I've done some extensive brightness testing before. Brightness looks excellent on FK to me.
[ONE Original Android Development] franciscofranco:
1497mhz@150ms is the default. What rom are you on? I apply those values after the boot is completed (check init.fk.rc) so maybe rom's init is overwritting it. Kinda hard to guess.

No idea, it seems good to me as it is.
[ONE Original Android Development] mad.jack10:
Think the torch brightness is ROM/camera related, most lineage based ROMs have a dull torch but if you flash candy7 ROM you'll notice a huge difference in the torch brightness :svetius:
[ONE Original Android Development] Timmmmaaahh!:
I believe it's most definitely something in the kernel (which can be different in a ROM as they usually include a kernel). Flash a different kernel and you'll have another brightness, I've concluded that in my testing. I think it's coupled to a related property, not per se a 'flashlight brightness' setting directly. It's indeed most likely camera related but I've not found anything directly related to this. Samsung seems to have included a setting for this in their S7 devices, if that could be ported it would be awesome. When searching around, there are a few theories to be found. Some hint to the following values in build.prop:

ro.media.capture.flash=led

ro.media.capture.flashMinV=3300000

ro.media.capture.torchIntensity=200

ro.media.capture.flashIntensity=210

But I have no idea if those work and which settings are acceptable! I've not tried this because I won't risk breaking my device for something as silly as torch brightness. If anyone feels like trying it, I won't be held responsible if you forget everything because you turned your device into a standard issue MIB memory eraser (then again, you wouldn't remember so either way I'm good). The above values are intended for the Micromax A110. Others hint to tweak mA values, which seems like an even more dangerous game. I'll leave it to the kernel experts. Though I would appreciate it if you didn't blow up our devices, Franco. I really would. Thanks!
[ONE Original Android Development] guille26:
Ok, thanks for answering.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] franciscofranco:
:good:
[ONE Original Android Development] JJohnson1988:
I really appreciate how Franco doesn't add unnecessary crap to the kernel. Things aren't tacked on "just because" they can be.

Feature creep seems to be a plague that causes more problems than provides benefits.
[ONE Original Android Development] luckasa:
What about Kernel with kexec hardboot patch? I'm interested in Multiboot Lineageos. Thank you very much!
[ONE Original Android Development] ichigo696:
As Franco said, it breaks encription
[ONE Original Android Development] luckasa:
Ok. Then I must try others multiboots utilities like efidroid.
[ONE Original Android Development] DerNoobikeks:
App showing me this, worked fine 1 hour ago.

Reinstalling App didn't help.

EDIT: Fixed
[ONE Original Android Development] Timmmmaaahh!:
It would be great if you posted how you got it fixed. This may help other users that encounter this in the future. You can also make it more search friendly by typing out some core words of the error like "no FK available". Awesomesauce!

Sizzled with Bacon ?
[ONE Original Android Development] DerNoobikeks:
It was a issue with the HTTPS certification of francos website. Nothing specific to me ;)
[ONE Original Android Development] Gawd:
"The software utility Cron is a time-based job scheduler in Unix-like computer operating systems. People who set up and maintain software environments use cron to schedule jobs (commands or shell scripts) to run periodically at fixed times, dates, or intervals."
[ONE Original Android Development] LPW00:
Delete
[ONE Original Android Development] franciscofranco:
:highfive:
[ONE Original Android Development] mkhcb:
Anyone knows of a simple way to have fk-rXX.zip automatically renamed to something like kernel.zip?

I would like to have CyanDelta flash the newest kernel each time I update LOS. Currently to accomplish this, I need to manually update CyanDelta's settings with each update, since the file name always changes with the version #.

Maybe someone has already written a script for this and would like to share?
[ONE Original Android Development] franciscofranco:
I'll add that feature for a future app release.
[ONE Original Android Development] mkhcb:
You are amazing! Thank you! Hopefully you can also add an autodownload feature.

Thanks again!
[ONE Original Android Development] franciscofranco:
Auto-download? What do you mean?
[ONE Original Android Development] mkhcb:
Honestly, I will just be happy to have the static file name.

However to answer your question, it be cool if we can also have the app automatically dl (if enabled in the settings) any new version of the kernel (as it checks for updates). That way, the file is automatically saved to cyandelta folder or whatever folder we use to update our rom. I understand this can be technical, so feel free to ignore it.

Thank you for even responding to my post. Now many devs would. I'll stop bothering you now. Thanks for everything :)
[ONE Original Android Development] franciscofranco:
I don't think that's a good idea. It's an easy recipe for disaster. Notifying about a new update it's good enough in my books ;) About the file name I'll probably implement it.
[ONE Original Android Development] mkhcb:
Ok, thank you! :)
[ONE Original Android Development] unyk13:
First time using your kernel on LOS 14.1. Wanted to share some things i observed. I initially tried it on omnirom 7.1.2 & it went into a bootloop(unsupported?). It is running fine on LOS right now, but the first time I flashed the zip & rebooted the phone turned off after showing the bootlogo & was about to load into the OS. Is this normal behaviour?
[ONE Original Android Development] mohaimed:
anyone experiencing problems with wifi connectivity?? my wifi, although stays connected, does not get the speed
[ONE Original Android Development] vicky2131:
Can someone report here if the latest lineage May8th build works with r49? there seems to be a lot of new kernel related commits. [MENTION=3292224]franciscofranco[/MENTION] Just letting you know about the latest commits
[ONE Original Android Development] jeycop:
I flashed newest LOS +gapps + r49.

No errors since 2 5 hours :p
[ONE Original Android Development] hmzuleta:
Can confirm.
[ONE Original Android Development] franciscofranco:
Never seen that before.

WiFi drivers are the same as on LineageOS. Doesn't seem like Kernel related, just some random thing.

I know about the commits. They are just tiny fixes, nothing to jump about.
[ONE Original Android Development] sohansonu:
There seems to be a problem after flashing FK in the latest nightly. It seems to heat up more when compared to the stock kernel.
[ONE Original Android Development] franciscofranco:
Not really.