yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] MICa.fighter:
It means

Well i kinda stated i recieved it through build.prop :D

Btw I modified Android version to L because there is a bug with the YouTube app, it won't show FHD option on 4.4.4. Modified it to L and FHD is back.
[ONE Original Android Development] zephiK:
Yeah I know I made the post about it :p gotcha.. you were trolling about the update.
[ONE Original Android Development] ShermCraig:
Guess I wasn't clear. I flashed the AOSP version OF FRANCO. Any assistance would be appreciated.
[ONE Original Android Development] MICa.fighter:
Flash the aosp version of franco again, then flash the su zip again. Reboot and check the logs of su app, make sure TB is not denied. Then run TB, and see if it works. It should ask for root rights. If TB says it couldn't acquire root rights, check su app log again.
[ONE Original Android Development] chr0m:
Oh I see :) I thought you had some special way to actually get the update :) So no evidence that it's even real then?
[ONE Original Android Development] MICa.fighter:
No real evidence atm. Thats the pont i wanted to make by trolling, the pic on the one forum might be build.prop'ed too.
[ONE Original Android Development] ShermCraig:
Before I proceed, would you suggest I reboot in between the flashing of the kernel and SuperSU Update?
[ONE Original Android Development] zephiK:
Flash Kernel, flash SuperSU. If you use TWRP, queue them together. No need to reboot in between.

Make sure your SuperSU is http://download.chainfire.eu/supersu
[ONE Original Android Development] chr0m:
I just changed mine to from 4.4.4 to L and I still can't choose 1080p in youtube :(
[ONE Original Android Development] zephiK:
I had the same problem.. /shrug, 4.4.2 will definitely do the trick.
[ONE Original Android Development] ShermCraig:
I had originally flashed the .img file (via flashify). I'm going to do as you say and download/flash the zip file. I'll report back....

Thank you again!
[ONE Original Android Development] drdrewdown:
the zip will work
[ONE Original Android Development] ShermCraig:
And... we're good! Thank you again [MENTION=1978554]zephiK[/MENTION] - you've been very helpful! :D:D
[ONE Original Android Development] Toaster Strudels:
[MENTION=3292224]franciscofranco[/MENTION] are kernel developers currently working on a fix for the terrible lag issues while typing? I can't seem to get through a text message without there being insane glitches and ghost touches - some are claiming this is a hardware problem now.
[ONE Original Android Development] chr0m:
These issues seemed to go away for my since Franco r13
[ONE Original Android Development] vomer:
Guess things appeared earlier than expected :)

Setup starts tonight and testing starts tomorrow! ;)
[ONE Original Android Development] mbudden:
:D:D:D
[ONE Original Android Development] jarjar124:
Shipping is insanely fast!
[ONE Original Android Development] paychex:
Why are people still so worried about battery drain? Does anyone have any problem making it through the day on a charge with this phone? Hell the one dude literally stared at his phone all day Also 33R fixed any battery issues for most.

---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------

I'm guess it's your settings in SSU. Click the check to disable root click it again and reboot. see if that works

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

My phone is great... I'm in no hurry
[ONE Original Android Development] mbudden:
Some of us don't like waking up noticing 10% of your battery has been eaten up just idling.

Not all of us spending all day looking at our phones with 6-9 hrs SOT.

Some of us want optimization.
[ONE Original Android Development] f100cleveland:
The guys on aosp build, do you notice that most the time, the phone wants to idle at 422? Mine won't settle down at 300. I thought r13 was supposed to fix that issue, but mine doesn't really ever use 300. If I swap another kernel, it'll idle at 300 like normal.

Thanks
[ONE Original Android Development] paychex:
Who doesn't charge their phone at night? There's a difference between optimisations--that are gonna happen at their own pace no matter how much anyone cries--and nitpicking.
[ONE Original Android Development] rogerstyo:
Turn the device off when not in use.
[ONE Original Android Development] vomer:
yes! very surprising :)
[ONE Original Android Development] Red5:
Oh, you're here. :banghead:
[ONE Original Android Development] sharp2G:
I can't wait to try out or official tweaks for the OnePlus One!
[ONE Original Android Development] :
If you need any help testing, I'd be glad to try out any settings :good:
[ONE Original Android Development] MICa.fighter:
I don't. The phone charges from 0 to 100 in about 2hrs. Let's say you sleep 8. That means your phone sits at 100% for at least 6hrs. If you do that every day your battery will degrade faster. These are pretty good articles in the subject:

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

http://batteryuniversity.com/learn/article/how_to_prime_batteries

http://batteryuniversity.com/learn/article/do_and_dont_battery_table
[ONE Original Android Development] LiquidSolstice:
...wow. You clearly know nothing about how Android phones charge. Those are articles aimed squarely at people with laptop batteries. Your phone most certainly does NOT sit at 100% for 6 hours. That's not how it works.

These phones and these batteries were made to be charged every night. It's not just the software that keeps your phone's battery healthy. Your battery is actually designed to deal with overnight charging. You're not the first person to fall for this, and I doubt you'll be the last.

There is not enough proof to believe that your phone's battery will significantly degrade over the three to four years worth of use (max) that you're going to get from it. I feel 100% confident in saying this right now; 4 years from now, I absolutely promise you that your battery's ability to hold its charge won't be affected by whether or not you charge overnight or not.

It's FUD like this that causes battery obsession.
[ONE Original Android Development] MICa.fighter:
You see you say there is not enough proof to believe that. I say there is not enough proof to believe otherwise. I think its better to be safe than sorry.
[ONE Original Android Development] LiquidSolstice:
It's your phone experience that you're ruining, not mine. I don't really care. I'm just going to make sure that no one falls for it like you did.

For reference, two things you should know; 1. your phone will never remain at 100%. Most modern battery circuits are smart enough to cut the power and let the battery die down to at least 95% or more (many Android phones will let it drop to 90% before allowing it to charge again) 2. You are already shortening the lifespan on the battery considerably by using a 2.1A charger, and I promise you, that has far more damaging effect on your battery than charging overnight, and even then, you still are doing such inconsequentially tiny damage to your battery that it's ridiculous to consider otherwise. That, combined with the heat of your environment and how much you try to use the device while its charging are the only real dramatic factors in ruining a battery.

If you don't use your electronic device (which contains the majority of your digital life and has dozens of its own processes that check for updates continuously) for 8 whole hours and you're upset that it's used 10% battery, that is 100% squarely your problem and Franco shouldn't have to waste even 10 seconds trying to figure it out for you.

EDITED because on second thought, this part was inflammatory and not needed.

Whatever makes you sleep better at night (no pun intended).
[ONE Original Android Development] MICa.fighter:
While i value your opinion, i prefer to believe in scientific studies and tests rather than opinions (I am not referring to my previous links) . I don't have the means to prove my point in a scientific way, so i don't think there is any point in further argument.
[ONE Original Android Development] Elvecio:
So...there are some fix in the Franco Kernel that are not available in the stock kernel on 33r?

I fight with those typing issues every minute of my day, it's really bad. And i can't even return my phone to Oneplus because i have to travel a lot the next month and i really need a good Android with me. I just have to live with them.
[ONE Original Android Development] paychex:
It's got a charge controller. Trickle charging is fine

---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------

Sorry about what? The possibility of losing 100mAh in two years without your lab condition charge methods? It seems a lot of people here have time to waste
[ONE Original Android Development] MICa.fighter:
I don't intend to convince anybody of my ideas. Its your phone use it however you like it.
[ONE Original Android Development] albyXR:
impressive battery drain, now i am with ak kernel and it's unbelievable..
[ONE Original Android Development] nadavar:
What's unbelievable, Franco's impressive drain or ak's impressive drain?
[ONE Original Android Development] albyXR:
franco! ak kernel is 1 hundred better for the battery life! even if all the people here will ay now: it depens of the usage, of what you do etc. bla bla bla.
[ONE Original Android Development] bradm23:
Have some respect for Franco and keep your comments about other kernels in their forums. If you like AK, use it and be happy. Franco puts endless hours of work and support into his kernel for free.
[ONE Original Android Development] sien1996:
Agree with [MENTION=2726001]bradm23[/MENTION] . I'm an AK kernel user but Franco has things that AK doesn't and vice versa. So respect to everyone and Flash On!

Sent from a Device codenamed Bacon!
[ONE Original Android Development] akarol:
I have charged my phones overnight for over decade now. And not one has had any battery issues. Not one. All batteries degrade with time and charge cycling, it's physics.

---------- Post added at 09:11 AM ---------- Previous post was at 09:02 AM ----------

See that? Your current stops when the phone reaches 100‰.
[ONE Original Android Development] albyXR:
sorry guys, i was only answering to an user who ask me my feeling, having trying both kernel i only express my feelings..
[ONE Original Android Development] MICa.fighter:
So? I didn't said the current will continue. There are a number of factors which effect the degrading of ion based batteries. For example heat, voltage and depth of discharge.

---------- Post added at 03:52 PM ---------- Previous post was at 03:47 PM ----------

Its ok to express your feelings but do it in a respectful way on xda.
[ONE Original Android Development] ak:
Please please respect developers and please to everyone "don't go to my thread" for trolling if people have problems report to moderators.

ak@a0001
[ONE Original Android Development] Red5:
You know what else degrades batteries? A sledge hammer.

Now can we get back to discussing the kernel and how 38R is fake?
[ONE Original Android Development] MICa.fighter:
38R is fake: https://forums.oneplus.net/goto/post?id=4828668#post-4828668

View attachment 2914230
[ONE Original Android Development] mbudden:
Confirmed fake.
[ONE Original Android Development] LiquidSolstice:
Until you show me a smartphone battery that has actually degraded significantly specifically due to being charged overnight, your opinion is just that; an opinion. You won't find it because it doesn't exist, so in that regard, you're right, there is no point in further argument.

The original point still stands; if for whatever misinformed reason, you decide not to plug in your phone each night to charge, and you lose x% of battery life, that should absolutely be your problem and Franco shouldn't waste any time on trying to "fix" that for you.
[ONE Original Android Development] MICa.fighter:
I don't think franco kernel topic is the place to discuss battery degrading in detail. Btw that's why i avoided responding with long and detailed posts about that topic here, and kept the OT posts short. If you are interested i am happy to continue the discussion in pm or in a dedicated thread. And i really mean that. I like to be proven wrong because that means i learned something new. But i don't want to discuss it here in the expense of others. So this is my last post regarding battery degrading in this topic.

Paychex: check his pic again and pay attention to the voltage levels.
[ONE Original Android Development] paychex:
But none of them have anything to do with not charging your phone over night

---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------

I really hope that isn't happening
[ONE Original Android Development] vomer:
Thanks for the offer :) I do have a team helping me already! :angel:
[ONE Original Android Development] Tzfardaya:
DHL? Hope you don't have to fight with them like I did to have them actually deliver it...

Even the 2.1A charger won't damage the phone battery, it's still less than the 1C safety zone for this sized lipo pack. (3300mAh battery, nominal charge would be 3.3A, more than that is a "fast charge" less is a "slow charge")

Trickle charging lithium batteries is a huge no no... But leaving your phone on the charger overnight isn't tickle charging it.. (semantics, I know)

Charging type/speed/levels et al has been heavily debated in a howto save battery thread.

found here

All the lithium based dangers most people worry about have been "fixed" in cell phones via software and circuitry. Phones turn off well above the lithium discharge danger zone. Unless you have a phone with a minuscule battery, (<1000mAh) you're not going to find a "fast charger" to have to worry about charging speeds. The only real danger is parasitic loads while charging to 100%... Which is why phones stop charging at 100, discharge to 90—99% (depending on phone) then charge back to 100%, to minimize this risk.

Is it bad that I can't remember which test groups I belong to anymore... :P
[ONE Original Android Development] vomer:
Nope! went very smoothly. I like fedex but DHL's speed was shocking. Delivered 1 day before estimated date :eek: :good:

lol sometimes I get confused myself! :p
[ONE Original Android Development] :
Well I look forward to running your settings :)
[ONE Original Android Development] MICa.fighter:
Good news (mostly) : https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-39859

Steve fixed all power management issues he could find, we get the fixes in the next OTA.
[ONE Original Android Development] _Beni_:
Sounds nice, hopefully the SOD is also fixed
[ONE Original Android Development] vomer:
Thanks! :) they are in the hands of the testers now so should be out once I get some quality feedback ;)
[ONE Original Android Development] :
You should post screenshots later as a teaser!:p
[ONE Original Android Development] Red5:
Why do you want to give your phone blue balls?
[ONE Original Android Development] sharp2G:
Are your tweaks specific for Franco kernel or with other kernels as well, such as the stock kernel? Also, is there a thread or your tweaks or will discussion remain in this thread?
[ONE Original Android Development] zephiK:
You mean battery stats? :p

They're specific to Franco Kernel only. It doesn't work on other kernels because they have different paths and whatnot. Also the results of the tweaks will not be the same on other kernels as they have other ways of handling cores (mpdecision/intelliplug/etc). Discussion remains in this thread.
[ONE Original Android Development] f100cleveland:
Are you guys seeing this same type of freq use?
[ONE Original Android Development] vomer:
lol you want to be teased? :D
[ONE Original Android Development] messher:
[ROM][OFFICIAL][4.4.4]OnePlus AOSP

Hi all,

i installed this rom and tried to use Franco Kernel r14 aosp, but with this kernel, the opo doesn't start.

It remains stuck in the logo 1+ screen.

Any help?

Thank you.
[ONE Original Android Development] dosiwi:
What ROM and what kernel?
[ONE Original Android Development] messher:
[ROM][OFFICIAL][4.4.4]OnePlus AOSP --> this Rom from Oneplus forum.

Franco Kernel r14 for aosp rom
[ONE Original Android Development] zephiK:
In your post I see Franco Kernel r14 aosp so I assume that means that you downloaded the aosp variant of the kernel.

I've read in the past where somebody asked the same question as you, and if you did indeed flash the r14 aosp variant then Franco Kernel is not compatible with your ROM.

I suggest switching to another ROM or just using the stock kernel supplied by your ROM. You can get your phone to boot again by reflashing your ROM zip which will then flash the stock kernel so your phone can boot.
[ONE Original Android Development] messher:
Yes, my phone is already ok, falshing the boot.img extracted from the rom.

But i would like to know if i can use the franco kernel.
[ONE Original Android Development] zephiK:
No you can't, not on that ROM if it doesn't boot using AOSP kernel on that rom.
[ONE Original Android Development] Tzfardaya:
So I should check my email?

Well, you've the wrong plumbing for me to enjoy being teased by you...

---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------

Fed-ex?

DHL?

You know I work for Purolator, right?
[ONE Original Android Development] sash89:
Guys any news about yellow tint on bottom?any fix?
[ONE Original Android Development] vomer:
lol purolator - "redirect" me some packages :rolleyes:
[ONE Original Android Development] DerRomtester:
Ni fix no rma. UV light doesnt work. You habe to live with that.
[ONE Original Android Development] sash89:
U guys having this issue too?
[ONE Original Android Development] MICa.fighter:
AFAIK you need the kind of UV which is used in a solarium.
[ONE Original Android Development] Salty Wagyu:
I've also got weird behaviour in the TCP Congestion field. When I installed latest Mahdi ROM and then FKU it would show a value of 0, I thought this was because there wasn't a busybox, so I installed Busybox on Rails, and it now shows "kernel/busybox:". Clicking on this gives the following choices:

.kernel/busybox:
can't
execute:
Permission
denied

FKU and Busybox on Rails had SuperSU permission. Hope this helps
[ONE Original Android Development] Overdose1986:
I HAD this issue, but now is gone after leaving my phone for about half hour under the morning sun
[ONE Original Android Development] sharp2G:
It never leaves. It's just harder to see over time because you get used to it.
[ONE Original Android Development] Overdose1986:
Neither my gf or my brother can't see any yellow tint with full brightness on a white screen

So isnt just me, actually I have 3 phones I can compare them together, there is no yellow tint anymore
[ONE Original Android Development] sharp2G:
Try using low brightness and be in a dark room. Sorry for bursting your bubble and this is getting OT :P
[ONE Original Android Development] chipstien:
So I'm not sure if this has been brought up but was using R14 on Liquidsmooth and was working great until I tried listening to Pandora. Plugged in my Bose headphones (no mic) and the sound was extremely low and mostly static. The static didn't go away when changing the headphone settings in FKU but the volume did change. Went back to the stock kernel and the headphones worked fine.
[ONE Original Android Development] k3mik4l:
I tried flashing Franco with liquid and all was fine until I tried making a phone call. I could not here anybody unless I enabled speakerphone. Thought it was the ROM but flashed a few other other kernels and the problem was gone. I flashed the AOSP version, tried the CM one for the hell of it and it wouldn't boot. Anybody using this on liquid with no issues with phonecalls?
[ONE Original Android Development] FuzeLearner:
This happens to me also and I'm on CM11S. Adjusting the headphone boost setting does the same for me, but if you reboot and then change the headphone boost while the music is playing it will work.

Additionally whenever I adjust the headphone boost settings the speakers no longer work. The headphone jack still works and the ear piece speaker works, but not the bottom two speakers. I use the headphone boost every day in my car. I make sure to not put headphone boost to set on boot and then just reboot my phone every time I get home. Rebooting makes the bottom speakers work again.
[ONE Original Android Development] webwude:
Quick question: does the paid version of the franco updater work with 1+1 / CM11S ? I purchased the updater long time ago and purchased yesterday a 1+1 64GB

Thank you for a quick reply, best regards

ww
[ONE Original Android Development] deathdark:
It should work. App Supports opo
[ONE Original Android Development] shapethelola:
Yes it does!
[ONE Original Android Development] Nomelas:
Mine has gone down significantly, I'm not just getting use to it, it actually is going away over time with moderate use. Some claim it goes away shortly some say it takes longer. Your mileage will vary but it can go away.
[ONE Original Android Development] mbudden:
Mine was really bad when I first got it.

It has almost gone away completely. Just a tiny sliver down at the bottom.
[ONE Original Android Development] Janny82:
Most of the last posts have nothing to do with Franco-kernel.

I am back to stock kernel, because I had several "black outs" when using Franco R14 with latest 33R. My phone went black and only long pressing the power-on helped.
[ONE Original Android Development] Tzfardaya:
That's nice.
[ONE Original Android Development] JFK1997:
I got mine a month a go back then i had an yellow tint now it is completely gone :D
[ONE Original Android Development] grilopt:
I tried to go back to stock using backup kernel from Flashify and the phone stays at Oneplus logo. Had to flash R14 again to boot it up. How did you manage to? Fastboot?

Tks!
[ONE Original Android Development] Tzfardaya:
I pulled the IMG from the stock tarball and used fastboot...
[ONE Original Android Development] dayanandgp:
Application crash - AOSP r14 release

Hi [MENTION=3292224]franciscofranco[/MENTION] i am getting application crash with latest FKU and r14 AOSP kernel.

My setup : Mahdi rom with latest FKU, Latest AOSP kernel (updated from your app) , VomerTweaks

Issue : Open FKU , Load a already saved personal colour profile , Hit apply, everthing is fine

Open FKU , Load a already saved personal colour profile ,Select "apply on reboot" option, Hit apply, FKU app crashes and restarts

I have attached the logcat below. Could you please let me know whats happening ? due to this i am not able to apply the Color profile on

every reboot :(

Thanks !!!!
[ONE Original Android Development] jarjar124:
I don't think the color profiles on the app works for our devices yet unless it is your personal profile.
[ONE Original Android Development] Janny82:
And I just reflashed the 33R update with TWRP.
[ONE Original Android Development] dayanandgp:
It was a personal profile. Just a typing mistake :)
[ONE Original Android Development] joaocadide:
I'm using CM11 nightlies and when I flash Franco Kernel using the Updater app, I lose root.

Is this a known issue?
[ONE Original Android Development] omvir:
I had that issue ... So I downloaded superSU and flashed it.
[ONE Original Android Development] Setting.Out:
Yes, well known issue.. ;)
[ONE Original Android Development] paychex:
that would make too much sense. seriously people https://cyngn.com/products/oneplusone/
[ONE Original Android Development] Salty Wagyu:
edit: Disregard, I should have tested longer, seems frequencies rarely ever go above 1.2GHz most of the time!

Trying out OPO Vomertweaks at the moment, it was suggested you can use per-app modes to increase the frequency beyond 1.2GHz if apps feel laggy still. Only problem is this doesn't seem to work - according to FKU System Monitor's background monitoring it is reporting a max of 1.2GHz

I also tried increasing max frequency in FKU, no dice. /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq are showing frequencies beyond 1.2GHz so I'm not sure if they're really applied or if System Monitor is faulty.

p.s. I used vt_zephik_v1.zip