yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Knox316:
WHat version should I use with the latest CM12.1 Nightly?
[ONE Original Android Development] Eru Ilúvatar:
The latest v.251 ;)
[ONE Original Android Development] FSadino:
[MENTION=3685904]ak[/MENTION] kernel is for all CM12.x
[ONE Original Android Development] Knox316:
New-TC? I have the new TC and ak updater tells me there is a new build available..
[ONE Original Android Development] expiredd:
Will 251 version with TC CM fix drain more battery? that's why there's two different versions? :confused:
[ONE Original Android Development] laulau42400:
Good question ☺

Tapaltak and Lollipop ? One+ & cm12.1
[ONE Original Android Development] FullWipe:
AK 251 --> old touch firmware --> bad touch responsiveness --> good battery life

AK 251 NewTC --> New touch firmware --> good touch responsiveness --> more battery drain

Depends by what you want ;)
[ONE Original Android Development] JaylanPHNX:
Actually old touch drivers only means possible bad touch responsiveness. If you haven't had the bad problems some have been dealing with, then to don't need to use the new TC version.

From my SlimTab Pro 8.4
[ONE Original Android Development] ak:
its normal, new tc kernel isn't officially supported by updater.
[ONE Original Android Development] Knox316:
But which one has more battery drain?
[ONE Original Android Development] kai.man:
@ak: 251 works fine for me in cooperation with kantjer's latest slim-bacon 5.1.1 from this afternoon. Thanx a lot for your always great and incredible work. :good:
[ONE Original Android Development] FullWipe:
Have you read this post? --> http://xdaforums.com/oneplus-one/orig-development/kernel-ak-t2832168/post60939857
[ONE Original Android Development] Knox316:
Thank you :)
[ONE Original Android Development] expiredd:
If I can survive with Lollipop radio active bug, then I guess I'm in for new touchscreen firmware.
[ONE Original Android Development] return.of.octobot:
I've been using 248TC, before I update to 251, I'm wondering what the chances are that the synaptics drivers are responsible for the miscellaneous power consumption that my battery stats have been reporting, I've been trying to trace the issue all week as it's begun to overtake my display in terms of consumption, and it just dawned on me that the touch drivers may very well be the culprit. I don't know why it took me so long to consider this, but I guess I assumed that any extra battery drain encountered from the drivers would be included in the 'screen' stats category.

If that's the case, I've got no problem going without as although I am noticing a touch response improvement, I wasn't experiencing serious problems to begin with.
[ONE Original Android Development] chikimonke:
You won't see it in the screen on time in battery stats, because I believe the drain actually comes from the screen off gesture detection. Some have reported that turning off screen off gestures has brought the battery drain almost back to what the old drivers had, but you still get the better responsiveness. That said, I don't think there is any hard evidence of this, so it could all be placebo. But yes, your higher battery drain in recent days is almost certainly the new touch driver (which CM themselves have reverted for this very reason)
[ONE Original Android Development] :
It's confirmed that new touchscreen firmware results in consuming +35mv Cpu overall voltage. Thats the reason for battery drain.
[ONE Original Android Development] return.of.octobot:
Thank you for the comprehensive answer, will be reverting to base 251, hopefully that will clear things up for me.
[ONE Original Android Development] sash89:
Hey guys!what's the best scheduler to choose?
[ONE Original Android Development] Formhault:
Stick with the default scheduler. I think it's good enough.

---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------

What?

I undervolt my CPU by 55 mV overall, and the touchscreen driver doesn't interfere with that.

I think you meant the new touchscreen driver makes it so that the battery drains faster (30mA per hour when idling)? We know that... we're waiting for Synapsis / Cyanogen to release a new driver. Not sure if they're even working on another one, though. :laugh: :(
[ONE Original Android Development] sash89:
Yeah,but sometimes it takes more to wake up the screen!why is that happening?and how is your sot with the new tc guys?
[ONE Original Android Development] :
Yeah, it's 30mA. Not mV.

http://review.cyanogenmod.org/#/c/98677/
[ONE Original Android Development] Formhault:
Not sure about the wake up thing. I disabled all screen-off gestures (which includes double tap to wake, which is said that, if disabled, the touchscreen - with the new driver - doesn't consume as much power). So wake up by power button is pretty instantaneous :silly: .

Battery life... isn't so stellar. Well, not like it was excellent before, anyway...

Right now I'm at 41% with 2h44m of SOT. 3G data / Wi-Fi active all the time (mostly on Wi-Fi). Actually, I'd say this is pretty good. Unplugged the charger like 12 hours ago.
[ONE Original Android Development] a63548:
You are truly amazing AK!. Love your kernel so much :D. Especially appreciate you integrating the color profiles! :) Just everything is perfect in my opinion.

Also wanted to post that I updated the slimdevs mirror to include all your old kernels, and the current. Will be keeping it up to date as you release :)

http://slimdevs.com/AK-Kernel/
[ONE Original Android Development] Formhault:
Sadly, it doesn't seem to work fine for me.

Oh well, I guess I'll have to wait for Cyanogen to do something about it...
[ONE Original Android Development] ak:
thanks a lot :good:
[ONE Original Android Development] lou2s:
Hi, after flashed to 251, had a few reboots this morning. And in GPU section of Synapse I found this error. Plz help...

P.S. already cleared synapse data, reboot in stock value, still the same...
[ONE Original Android Development] ak:
you have to clear synapse data/cache, and force stop.

please post last kmsg and detailed info.
[ONE Original Android Development] lou2s:
Thanks for your prompt reply, clear cache/data, fc was the 1st action I did. Didn't help though. Finally I flashed 251 again and it is fine now.

I flashed 251 last night and it was fine, and there was no red warning msg there. After the 2 self reboots this morning I saw the "android is updating apps x of x" msg as if the dalvik cache was cleared (which I didn't). I think something was corrupted since then.

Next time I will definitely copy last kmsg first. I guess this is too late now since I hv restored profile already...

Sent from my AK-Skulled Euphoria 1.1 A0001
[ONE Original Android Development] ak:
If you exp crash this can happen.

Sent from my A0001
[ONE Original Android Development] smolly:
Is the proximity sensor controlled by the kernel fw?

Mine is not working on v.251 (incl TC).

(The app "phone tester" can be helpful)
[ONE Original Android Development] ak:
no, you have to contact rom dev.
[ONE Original Android Development] guraki:
Dear AK which governor of your great kerne do you suggest for daily use?:)
[ONE Original Android Development] Stylo King:
The stock Interactive governor
[ONE Original Android Development] guraki:
What is your opinion about Intellimm???:)
[ONE Original Android Development] moosha:
Hey I get speed bin n PVS bin values as zero ....tried reflashing ...complete wipe n flash nothing helped...can anyone help me?TIA
[ONE Original Android Development] ak:
probably you have 0, its possible. Speed bin?
[ONE Original Android Development] Stylo King:
Try it, Experience it..

There is a full guide on governors out there..

BTW I prefer Smartmax..
[ONE Original Android Development] moosha:
I used to have different values ...I don't remember speed bin but my PVS was 8 ...now both are 0 :(
[ONE Original Android Development] ak:
Have you try to uninstalled reinstalled from recovery?

Sent from my A0001
[ONE Original Android Development] moosha:
Uninstall ukm ? Yes
[ONE Original Android Development] Naman Bhalla:
Did you flash UKM separately ? You don't need to do that.....

As far as I know, I think AK is asking if you tried uninstalling kernel via uninstaller zip in post 2? Uninstall by flashing it and then reinstall the kernel..... Wipe cache and dalvik before and after the process. That should help.
[ONE Original Android Development] moosha:
I have done all that several times ....even clean flashed

:(
[ONE Original Android Development] 1337jay:
Been running this kernel for a while now and I've been wondering how much do you undervolt? I'm using a custom profile with CPU at max 1.5Ghz and undervloted by -65mV overall. My PVS Bin is 8 and Speed Bin 3.

Battery life is already impressive with 2.5 days idle and 4-5 hours of SOT with Hearthsone, YouTube etc.
[ONE Original Android Development] poondog:
imo try to be safe with your undervolting. You can always try to get it far down as possible (to keep it stable) but as every hardware is different (they're made within rough guidelines on a massive production line) everyone will have different results

If thats stable for you now, I suggest keeping it. Remember that QCOM have designed the chipset and the voltages to work in tandem without fail. There's a link back somewhere to a post by dorimanx explaining why voltages should be kept as is
[ONE Original Android Development] dylanraga:
251 TC causing bootloops on cm12.1 5/25
[ONE Original Android Development] dharmabm:
You're sure kernel is the cause? Where is your log?

sent from my slim powered 1+1
[ONE Original Android Development] dylanraga:
I'll get it later. 251 regular boots fine, tried reflashing ROM nightly both 5/15 and 5/25, both bootloop on only the TC kernel, reflashing 251 regular boots fine, 248 TC bootloops as well
[ONE Original Android Development] Mayday_XL:
I have no bootloops with 251 TC and CM 05/25.

*** Mayday@O+O ***
[ONE Original Android Development] stryker09:
Running 251 with PA 20/05 and damn I've gotten the best battery life in months with my current setup. AK keeps surprising me. No bootloops, no weird stuff, only a camera bug but im cool with it.
[ONE Original Android Development] ak:
TC is the same of official one, i have only reverted synaptic commit, so no differences.

have you try to re-download the zip?
[ONE Original Android Development] ak:
I'm waiting your migration to One+ my friend. :D
[ONE Original Android Development] dylanraga:
logs
[ONE Original Android Development] ak:
No errors detected

no problems related to kernel. :good:
[ONE Original Android Development] dylanraga:
fixed it.

flashing the TC kernels while d2tw is disabled causes the bootloop. go figure.
[ONE Original Android Development] ohad129:
Nothing for N6?
[ONE Original Android Development] ak:
I need a phone + time [emoji1]

Sent from my A0001
[ONE Original Android Development] kantjer:
I'm sure if somebody donates the phone you will find the time [emoji12]
[ONE Original Android Development] sash89:
[MENTION=5325313]8mc34[/MENTION] can u provide a link to miui v6 stable for our phone buddy?
[ONE Original Android Development] sash89:
Guys,Any news about the touchscreen drain fix from cyanogen?does anyone know something about it?
[ONE Original Android Development] Stylo King:
CM didn't implement it yet
[ONE Original Android Development] poondog:
Boss will I see you with Nexus 5 2015? Or are you waiting another year?
[ONE Original Android Development] Formhault:
Could this be... the end to our Wi-Fi dropouts...
[ONE Original Android Development] shadow47:
I have been using smartmax. I used 251 without new touch drivers for a day. For me it seems 248 is giving better battery for the same setting than 251.
[ONE Original Android Development] Stylo King:
+1
[ONE Original Android Development] William2009:
Agreed
[ONE Original Android Development] kantjer:
That commit needs to be added to the ROM not the kernel. But thanks for the tip.

Making a SlimSaber build now with the commit included.

EDIT: Phone keeps rebooting every couple of minutes. Not a solution.

EDIT 2: tried again and now it seems to be OK
[ONE Original Android Development] ak:
I need scientific report .... [emoji6]

Sent from my A0001
[ONE Original Android Development] ak:
N5 2015 is interesting phone ... Do you think to pass to it?

Sent from my A0001
[ONE Original Android Development] poondog:
Yeah, LG Nexus 5 2015, according to:

http://www.androidpolice.com/2015/0...ler-and-a-5-7-inch-huawei-code-name-bullhead/

[MENTION=3301438]geko95gek[/MENTION] will join us

5.2inch is ideal imo (coming from my 4.7 inch m7)
[ONE Original Android Development] ak:
Mmm very interesting ... [emoji6]

Sent from my A0001
[ONE Original Android Development] kantjer:
@ak, did you remove UKM.sh installer with a specific reason from the UKM source?

Now after flashing the UKM standalone package UKM won't survive a dirty flash.
[ONE Original Android Development] Formhault:
Umm... Ak, are you considering downgrading to the Nexus 5...? :eek:
[ONE Original Android Development] Spaulding89:
Why downgrading??

You mean upgrading [emoji111]

Sent from my slimmed Bacon
[ONE Original Android Development] Formhault:
Oh, right. N5 2015 not 2014... I was thinking of the existing Nexus 5, lol.
[ONE Original Android Development] poondog:
Sorry for OT.. but I am also interested in seeing what Oneplus has this year, since they divorced from CM. I'm happy with my decision to hold out a bit for my new phone :P
[ONE Original Android Development] ak:
@kantjer

i have remove it to clean the installation, do you think it's more just to have it?
[ONE Original Android Development] kantjer:
I have reverted the commit for the standalone package because I needed to flash UKM with every ROM flash without it.
[ONE Original Android Development] CounterC:
Random reboot on 251, interactive governer.
[ONE Original Android Development] anjo88:
I will try it on my cm12s rom to seed if battery stays better since franco work is a little stopped i will give feedback in the next few thays. This rom have new touch screen driver right?
[ONE Original Android Development] ak:
Undervolt problems.

PS

Please post detailed info next time.

Thanks

Sent from my A0001
[ONE Original Android Development] ak:
This is a kernel Not ROM (use TC version for new synaptic drivers) .... If you want you can try but isnt supported , but if you want full support use Franco please.

Sent from my A0001
[ONE Original Android Development] anjo88:
I know man I'm just trying to have good touch and good battery life let's see what's happening now with your kernel thank you
[ONE Original Android Development] chachin:
YEP Du works fine with ak-Kernel :D
[ONE Original Android Development] evandena:
oh my god, the TC kernel is so nice. I finally have a fix *knock on wood* for my horrible touchscreen lag.
[ONE Original Android Development] Genericxx:
TC Kernel is really awesome. Did you recognised any extra drain? And have you got dt2w deactivated?
[ONE Original Android Development] CounterC:
Thanks! I will definitely give more info next time.

Another request: can you add powersave governer to GPU or is it useless?
[ONE Original Android Development] evandena:
I have it on, and have noticed drain. ProximityWakeLock has kept my phone awake since I flashed AK. I'll try turning DT2W off. Either way, my phone was so unusable without the TC fix, half the time I couldn't even unlock the phone.
[ONE Original Android Development] Jole7:
AK I noticed that with your latest kernel phone don't get warm at all i check that before report it.
[ONE Original Android Development] Genericxx:
Got the same problems. Currently the Touchfixer.apk that roams around solves it for me partially while using non-TC.
[ONE Original Android Development] Slavon-93:
Hello, everyone. I've updated from 248 to 251 with AK Updater app and now I'm having battery drain of 20mA average. On Ak248 it was about 10mA average in sleep. Is it normal? Battery Monitor says that "system" process is draining battery. CM12.1.
[ONE Original Android Development] evandena:
What do you mean solves it partially?

Were you getting drain with TC and DT2W disabled?
[ONE Original Android Development] Genericxx:
No, with disabled dt2w i got no drain. But i like dt2w so I've switched to non-tc kernel and using touchfixer.apk instead. Without my phone isn't usable if I had carried it in my pocket before.
[ONE Original Android Development] evandena:
And with the touchfixer.apk its as good as with TC kernel? I like dt2w as well, but a working phone is better! :D
[ONE Original Android Development] nhshah7:
The tc works much better for my phone than the app.
[ONE Original Android Development] ak:
It does not become hot? or do you mean the opposite?
[ONE Original Android Development] Genericxx:
TC works much better indeed
[ONE Original Android Development] evandena:
Did you have to turn anything else off? I turned off DT2W, but am still getting ProximityWakeLock drain. What about the "Prevent accidental wake-up" setting?
[ONE Original Android Development] Genericxx:
I've turned of that prevent accidental wakeup and all gestures and also dt2s
[ONE Original Android Development] Formhault:
I don't think we're getting a new touchscreen driver... http://www.androidauthority.com/oneplus-announcement-june-1st-shake-up-tech-industry-611429/

---------- Post added at 11:56 PM ---------- Previous post was at 11:52 PM ----------

I'm gonna have to steal that signature, sir. Hope you don't mind. :D
[ONE Original Android Development] evandena:
Crap, that's where I'm at and still having wake lock issue.
[ONE Original Android Development] Mecca EL:
Battery drain and reboot

I ended up turning off my wifi, and immediately the temp dropped on my device. If you look at the graph I posted, it's definitely an OS issue.
[ONE Original Android Development] aswinrulez:
I was having random reboots a lot in latest cm12.1 nightly and 251 kernel. Here are two logs. I split one log into 2 because the file size was too much. There is no specific scenarios where i got the random reboots. I had reboot twice when i turned on airplane mode, once while trying to call someone, ones while watching a video. I had abhi's profile set up. I don't use any profile now. Haven't had any reboot since then but would like to know what might be the reason for the reboots/
[ONE Original Android Development] jrn2k:
Same here..

Edit: i r baboon, not related to kernel..
[ONE Original Android Development] ak:
irq61 can be related to:

- proximity or others rom drivers

no kernel problem.
[ONE Original Android Development] Jole7:
I mean that doesn't become hot at all.
[ONE Original Android Development] acuicultor:
Hi, i'm start building kernels from source i'm just a Noob willing to learn and I will very grateful if someone can point me to some info to change/add splash logo on a kernel for our device. I really look for the answer on the net but I found nothing helpful for me. Thanks in advance

Sent from my Crispy Bacon

Sent from my Crispy Bacon
[ONE Original Android Development] ak:
Good ... Its probably related to the new opt flags.

Sent from my A0001
[ONE Original Android Development] Jole7:
Great work once again you are a pioneer.
[ONE Original Android Development] poondog:
You need to change your avatar/signature art again, its fire and ice!
[ONE Original Android Development] jrn2k:
[MENTION=3685904]ak[/MENTION] again thanks for the kernel with the updated TC! Got my new opo Saturday and it has exactly the same issue as my rma'd one.[emoji20]
[ONE Original Android Development] Formhault:
Most likely the same crappy circular vibration motor and display glue :) bastards.
[ONE Original Android Development] poondog:
I did not know about this :)

In their defence you only paid $400 vs HTC aus asking $1100 for the m9

let it go
[ONE Original Android Development] Formhault:
In their offence, the crappy Nokia my grandpa has has a vibrator that actually vibrates, without making everyone on a 10 meter radius freaking hear it.
[ONE Original Android Development] poondog:
I don't think I have ever held a OPO, to have the honor of hearing this
[ONE Original Android Development] Formhault:
They used a circular motor instead of a linear actuator. I miss how the Galaxy S4 / LG G2 vibrated, lol.
[ONE Original Android Development] venky716:
I'll take a circular motor over linear and save 300-800$ all day.

But that's just me. [emoji13]
[ONE Original Android Development] Formhault:
What? How much more expensive is a linear actuator? :eek: I thought it's like $1 or so...
[ONE Original Android Development] venky716:
Lol I meant the alternative of buying a flagship would cost that much more.

I try not to complain or find minor flaws when devices like this, moto g or even nexus (5 atleast) sell at very low profits compared to others.

Good camera, display ( I don't have those issues), speakers, build, performance, battery. I'm happy with my OPO, probably the only phone I've been completely satisfied with.

Sorry for the OT.

I'm done :)
[ONE Original Android Development] sash89:
F*** opo guys and their crappy phone!if i cannot use my f**** touchscreen it is a nonsense flagship!hope they fail soon
[ONE Original Android Development] Quasar:
Not sure if that really added to the dev conversation of this thread. If you don't like the phone, buy a new one.
[ONE Original Android Development] gordon.shameway:
Haha, word!! [emoji106]
[ONE Original Android Development] Formhault:
The vibrating motor (which is pure ****, since I never feel it in my pocket but all of my colleagues hear it vibrate when I receive a message) is the only thing that drives me up a wall right now. I just don't have the time to try & sell it and think about what other phone I could buy right now.

Oh, there's the touchscreen, as well. I'm not sure I can cope with huge battery drain for the rest of my life :laugh: .

Sorry for the OT, [MENTION=3475639]ak.[/MENTION] Drop another build & shut our mouths lol. Just kidding :(
[ONE Original Android Development] ak:
No problem, I like to see a relaxed thread ! :cool:
[ONE Original Android Development] sash89:
it is not about like the phone or not because if i bought it it means that i like it...but what i mean is that the touchscreen is the most important thing on the smartphone,and if it is not working as it shoult,i spent my money getting a crap,if u like using the phone with a non usable touchscreen it is your problem...but i don't find it fair for the consumer...sorry for the ot but i think we had enough with the touchscreen thing
[ONE Original Android Development] venky716:
They did a survey on reddit as well as by oneplus and only 2-3% reported of having them.

If you have major issue you should definitely do a RMA (which I've heard is hell). No point ranting here.

Just saying not everyone is on the same boat as you and for them this is a great device.
[ONE Original Android Development] nicesoni_ash:
Sweet, thanks mate.. Will test soon.. Appreciate it.

'Out of thanks' :(
[ONE Original Android Development] ak:
No problem ... thanks for support.
[ONE Original Android Development] funCrash93:
yeah that "Thanks" limit drives me crazy.! T_T

tried, no luck no Spirit no FM ... :(

at first tried original SpiritFM (it said my phone is compatible so I should try Spirit2) but it didn't work, could not start service.

then tried Spirit2 that says Qualcomm Init... and that's all,

and finally tried some other FM Radio app, that said not compatible...

so, no radio, no Spirit, no FM...

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Thanks [MENTION=3685904]ak[/MENTION] for as always a prompt reaction :)

enjoy your holiday :p
[ONE Original Android Development] nicesoni_ash:
Unfortunately it will take some time for me to test this, can you send a log to mike from your spirit app?

Just click on frequency write 7, it will collect details and then send.. Looks like they grounded the pin as mike expected.. bad news :(
[ONE Original Android Development] d13guit0:
Out oft thanks? Use tapatalk :D
[ONE Original Android Development] :
awesome, thanks

all instant messaging remains instant right. Like when not using phone you get them instantly, given dataconnection and such?

again this is really awesome timings :)