yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Last condolence to CM11s and CM11

Hi all,

although the CM11s and CM11 kernel are already end-of-development, I want to give a lost condolence to them and implement the new touch screen drivers there as well.

So finally, both kernel are available in a really last final version 2.8. stable.

Version

2.8 stable (final)

15.05.2015

Touch screen driver updated to version 14001227 (backported from official CM12.1 kernel branch)

And not forget to say: These builds come untested by me, as I do not have them anymore on my dev phone. So if someone reports an issue with it, I would take the liberty and remove them again.

Enjoy

Andi
[ONE Original Android Development] ricardowec:
When I get the red notice in the app telling me there is a new build, I normally flash it without doubt, nevertheless when I flashed Beta 15 I get stuck in the boot logo.

Anymone with the same problem?

I am on latest Blisspop with latest modem.

Cheers

Edit: I returned to beta 12 (my previious kernel flash), and it now boots without issues.
[ONE Original Android Development] andip71:
The thing is (unfortunately): You can only use up to beta13.

CM put changes in the nightly of 14.05. which break custom kernels. And the change is not backwards-compatible.

And this is why I even stated this in bold letters on the change log.

Means: Until Blisspop has also merged these CM changes in, you can only use up to beta13.

Reiterating again (till I get shot, hehe): I know why I always only use official CM only, nothing else :)

Andi
[ONE Original Android Development] kalpik:
Just checked your updater-script, and it's not flashing *anything*. So much for you noticing differences! Placebo works in mysterious ways ;)

The only way to be on the new touchscreen firmware is by flashing a kernel that has the firmware header file. Also, this is a stark reminder that you shouldn't be blindly flashing zips on the internet ;)

ui_print("****************************************");
ui_print("* Script generated by JRummy Apps Inc. *");
ui_print("* Follow us on Facebook! *");
ui_print("* http://www.facebook.com/JRummyApps *");
ui_print("****************************************");
ui_print("");
ui_print("");

show_progress(1.000000, 0);
ui_print("Mounting filesystems...");
run_program("/sbin/busybox", "mount", "/sdcard");
set_progress(0.100000);

ui_print("Extracting files...");
package_extract_dir("sdcard", "/sdcard");
set_progress(0.300000);

ui_print("Setting permissions...");
set_perm(1000, 1000, 0660, "/sdcard/fw/emmc_appsboot.mbn");
set_perm(1000, 1000, 0660, "/sdcard/fw/file_contexts");
set_perm(1000, 1000, 0660, "/sdcard/fw/logo.bin");
set_perm(1000, 1000, 0660, "/sdcard/fw/NON-HLOS.bin");
set_perm(1000, 1000, 0660, "/sdcard/fw/rpm.mbn");
set_perm(1000, 1000, 0660, "/sdcard/fw/sbl1.mbn");
set_perm(1000, 1000, 0660, "/sdcard/fw/sdi.mbn");
set_perm(1000, 1000, 0660, "/sdcard/fw/static_nvbk.bin");
set_perm(1000, 1000, 0660, "/sdcard/fw/tz.mbn");
set_progress(0.400000);
set_progress(0.500000);
set_progress(0.700000);

# Unmounting filesystems...
run_program("/sbin/busybox", "umount", "/sdcard");
set_progress(0.900000);

set_progress(1.000000);
ui_print("****************************************");
ui_print("* Install Complete! *");
ui_print("****************************************");
[ONE Original Android Development] andip71:
Thanks for the analysis Kalpik, I expected it a bit to be placebo.

But I did not look at the flash script to see, actually it just sets permissions but does no flash operation.

Yes, Placebos work magic sometimes :)

Andi
[ONE Original Android Development] andip71:
Look here, about the new touchscreen drivers:

https://twitter.com/AndroidPolice/status/599200334196551680

Note, I have implemented these new drivers in ALL my kernels (CM12.1, CM12s, CM11s, CM11, CM12.0 and Oxygen OS) today in new updates!

Time to update, or? (but be careful with the fact custom roms need to be updated first with CM code of 14.05., otherwise you will run into bootloops).

Andi
[ONE Original Android Development] Garrret:
Hey. I would like to see in future updates more options in boeffla sound. I mean as much as in boeffla kernel for galaxy s3. We all need easy way to Change microphone gain while recording video. For now, we can only change gain for calls.
[ONE Original Android Development] andip71:
Come on, search the thread please.

I WOULD also like to see more. But I cannot implement something as I have no documentation on the used audio chip.

Deal: You get me an official register specification for the WDC9230 audio hub - then I try to implement more :D

Without that docu, it is impossible.

Andi
[ONE Original Android Development] tracerit:
How do we find out the CM code? I'm using Euphoria 5.0.2 from March 29. I flashed the updated CM12 3.4 kernel and it does feel better with single touches, but with multitouches, it still gets wacky. By wacky, I mean it still acts like this: https://www.youtube.com/watch?v=Hen-EMaA_QY

(here's my old Nexus 5 with much better multitouch performance https://www.youtube.com/watch?v=0Cw_9rp58yw)
[ONE Original Android Development] kalpik:
Beta15 (the one with the new touch drivers) probably won't work on Euphoria, since it hasn't been updated to incorporate the new ramdisk changes. If you really want latest touch drivers with Euphoria, you'll need to flash an anykernel based kernel (I know AK is anykernel based, and has the latest touch drivers).
[ONE Original Android Development] andip71:
You can only find out when you follow both the source code repos of your favourite rom and official cm. And check what your rom provider already merged in.

Or, he maintains excellent change logs.

But it is a bit hard most of the time. You rarely know what you get with custom roms.

About multitouch: I cannot say much to it. I never had touchscreen issues. And I did nothing special but just implementing the latest drivers released last night. For me, these drivers feel good, but as said - I never had significant issues. Nevertheless I believe these are the best touch drivers ever so far for the OPO.

Andi
[ONE Original Android Development] Grigster:
The kernel is just mind-blowing!!!

The Wi-Fi activation and connection are much faster (compared to the previous edition)plus the touchscreen is more responsive.

One thing I have to mention is that the "Lionheart" governor causes me reboots in combination with Heavy UV, but "Smartmax" with Heavy UV doesn't - I think this is because of the much more aggressive frequency ramping of the first one, though the latter one is much smoother (strange, I know).

Anyways, thank you, [MENTION=947981]Lord Boeffla[/MENTION], for this such great "core". :highfive: :good: :victory:
[ONE Original Android Development] _Beni_:
the reboots are caused by undervolting. Changing the governor should not solve the problem, it just stays less time at high (instable) frequencies.

If you really need to undervolt try to reduce the Max Frequency to 1500mhz or less. But the advantages of undervolting are nearly useless, the phone can crash at any time.
[ONE Original Android Development] Grigster:
I get what you mean but I've been testing my hypothesis and it appears that I was right.In spite of this, Medium UV is much more stable and it doesn't cause any reboots at all.

Currently, I'm testing the Power Save mode from CM11S to see how many hours it can add to the Screen-On Time.
[ONE Original Android Development] ricardowec:
Dear Lord,

Could you and/or ZZ advice whether the current version of the Kernel be applied to Bliss after the new build in http://xdaforums.com/showpost.php?p=60756187&postcount=1222
[ONE Original Android Development] kalpik:
Yes, beta 15 is fine for the latest bliss.

Sent from my A0001
[ONE Original Android Development] Hussainally:
Beta 15 gave me bootloop on 12.1..nuclear rom

Oops understood.. Rom not updated
[ONE Original Android Development] abhibnl:
After my tests on the new added governors, well pegasusq seems it's not as battery friendly as it was on s3. Lionheat, as expected, is performance oriented. Nightmare governor on the other hand is good. Providing a good balance between performance and battery however it's comparable to interactive so switched to interactive again. Anybody else who might have tested the governors, please feel free to share your thoughts/results.

Sent from OnePlus One
[ONE Original Android Development] kurtextrem:
I found out the same about PegasusQ. I haven't owned a S3 in the past, but I've compared it to zzmove - optimized. PegasusQ speeds up faster, comes down slower and spends a lot of time on the highest freq. By the way, is the hotplugging native from PegasusQ? I heard it has native hotplugging.
[ONE Original Android Development] abhibnl:
I don't think so. The native hotplugging is only for exynos chips. On opo it uses the default mpdecision hotpluging.

BTW a different question, i've been thinking to give slimkat a try but just wanted to make sure before flashing, would cm11 kernel work with slimkat build 9? The last stable build.

Sent from OnePlus One
[ONE Original Android Development] spanish33:
I actually like Pegasusq. In Boeffla-Config app I changed the governor profile to tunable and decreased the frequency_for_responsiveness variable to 1497600 to try to help with battery.
[ONE Original Android Development] eak1080:
On 05Q with latest kernel. Touch screen is stellar so far. Will update in a day if I run into any issues.
[ONE Original Android Development] fmc000:
Today's nightly kernel has a different checksum than Yesterday's but there are no related commits in the changelog. Does this mean that there's an updated ramdisk in it?
[ONE Original Android Development] kalpik:
Even if you compile the same code twice, you'll get a different checksum, so that's not the correct way to look for changes. Look at the commits, that's the best place :)
[ONE Original Android Development] the wiper:
Hello all, on the euphoria Rom, I cannot exceed the beta version 13 of the kernel, 14 or 15 it is bootloop, an idea? :(
[ONE Original Android Development] kalpik:
Yes, you need to wait for the ROM to be updated.

Sent from my Oneplus One
[ONE Original Android Development] the wiper:
OK I am going to wait, thank you very much the friend.:good:
[ONE Original Android Development] andrea90:
Am I the only one with bad wifi performance? Many reconnections also with good signal.

I've CM12S with latest Boeffla Test kernel...
[ONE Original Android Development] andip71:
Seems like? Nobody else was complaining so far.

And for me it is just as always, rock stable wifi.

Maybe restart your wifi router, change the wifi channel etc. This sometimes helps wonders.

Andi
[ONE Original Android Development] Fenvarien:
Same here, I really like the new governor options, especially PegasusQ.

I tweaked it to use 1190400 for frequency_for_responsiveness and 1 for io_is_busy. The result is a quite battery friendly and still smooth setup.
[ONE Original Android Development] abhibnl:
Well could you elaborate what io_is_busy 1 is for?

Well i'm on CM11s and the latest drivers are rock solid.
[ONE Original Android Development] Fenvarien:
io_is_busy 1 determines that during IO operations the cpu frequency is kept up even if the regular cpu load would allow the governor to lower the frequency.

Setting this flag to 0 can possibly save a little bit of battery life but all IO ops are potentially slowed down by the lowered cpu frequency resulting in reduced smoothness.
[ONE Original Android Development] joefso:
boeffla-kernel-4.0-beta15-CM12.1-bacon.recovery does not work with Slim-bacon-5.1.1.alpha.0.1-UNOFFICIAL-20150515-0638, it causes a bootloop. it appears that AK 246 is working
[ONE Original Android Development] ethanon:
Unusual heating problem while charging using the latest kernel update, using standard kernel settings
[ONE Original Android Development] andip71:
Can be, slim is not the reference.

If it works, fine. If not, you need to switch kernel.

Not here, just charged. Sure no process is/was active during the time, which caused the heat?

Cause nothing changed in the kernel code regarding charging.

Andi
[ONE Original Android Development] joefso:
alrijght, just wanted to see if I could help in anyway to find out why - if required.
[ONE Original Android Development] vandizzam:
Same for me on latest cm12.1 nightly. Temp went up to 70 Celsius. Had to disconnect. I switched to cm12s to check if the rom is the problem.

Maybe only people affected with the bad touchscreens are overheating with the new kernel?
[ONE Original Android Development] andip71:
Sorry, appreciate you think that.

But technically it does not make sense ☺

Andi
[ONE Original Android Development] ethanon:
I never had touch screen problem yet the over heating, I will try charging again with all back ground apps hibernated..

---------- Post added at 09:33 AM ---------- Previous post was at 09:05 AM ----------

Heating problem again with no apps running in the background.. Please help
[ONE Original Android Development] andip71:
First: I didn't make the touch drivers.

Second: I do not have a heating problem.

Hence - I cannot help.

Revert to kernel version before and check if it is different again.

And to be more scientific - what does heating problem mean for you? How many C? What is the charge current flowing? Etc etc.

Andi
[ONE Original Android Development] Fenvarien:
With Boeffla-Kernel beta 15 and CM 12.1 (latest build) the battery life is just amazing. No temperature problems or other hiccups.
[ONE Original Android Development] tsimitsangaz:
Excellent job with 12s and latest test kernel Boeffla Kernel Master , as usual since my Samsung S3 you are delivering amazing support and knowledge to the people but I dont wanna to mess-up with kernel settings and I want to leave it as default so what about battery life ? is it going to be the same as stock?
[ONE Original Android Development] slebit:
I haven't really had any problems with this kernel since I started using it for about 4 months ago when I bought this phone. I haven't even tried any other kernels. That is how happy I have been with this one!
[ONE Original Android Development] tsimitsangaz:
ok after some testing with 12s and latest test version I found that with zzmove governor optimal profile and fiops scheduler 512 oneplus is flying and battery looks neat till now. any other suggestions?
[ONE Original Android Development] nicolahaye:
Just flashed the beta 13 as I read it was the last one with no battery drain and my OPO is flying ! Zzmove optimal and fiops with a 2048 read ahead. Thanks for your work lord boeffla :)

Edit : also thanks for the app :)
[ONE Original Android Development] ethanon:
Sorry the unusual heating was due to some other problem may be as I am facing the problem with stock kernel too.. danke schoen.
[ONE Original Android Development] Fenvarien:
Disabling DT2W and the proximity check seems to mittigate the battery drain. After the negative side effect the new touchscreen firmware is going to be reverted with the next nightlies. "Causing 30mA sleep current. Revert until new version is ready" http://xdaforums.com/showthread.php?p=60802745

http://review.cyanogenmod.org/#/c/98677/
[ONE Original Android Development] mak725:
Many changes in changelog nightly forma kernel ,hopefully I address the battery drain of the new firmware

---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------

Good news to hear that ;)
[ONE Original Android Development] Fevves:
OK, since I'm on CM11S, I do hope [MENTION=947981]Lord Boeffla[/MENTION] will give it a chance, once it's stable and ok to put another final (2.9) ver for us "poor" One+1 KK lovers cause of http://review.cyanogenmod.org/#/c/98677/ ;)
[ONE Original Android Development] ivan0909:
Help please, I cant use this kernel with lastest CyanideL, and I've uploded Firmware, but ROM doesnt boot. Any idea?

I tried also to flash Beta15 in lastest NucelaROM and same.
[ONE Original Android Development] abhibnl:
Seems like CM11s kernel will receive a last 2.9 as well! [emoji12] [emoji12]

Sent from OnePlus One
[ONE Original Android Development] lou2s:
Meanwhile I flashed back to beta13 to get some good sleep.

8hr with 0% drain!
[ONE Original Android Development] Stroky:
My idle drain is the same as everytime. Strange that some people have such a high consumption.
[ONE Original Android Development] davebugyi:
Even CM acknowledged the drain and reverted the changes. You probably have DT2W disabled.
[ONE Original Android Development] andip71:
I just committed the 55 patches of last night into a new version of the kernel, compiling just now.

Yep, sadly I will have to follow CM and revert the touchscreen drivers in all kernels again.

It is sad, because with the new drivers the touchscreen really felt smoother (although I never had any significant problems with it).
[ONE Original Android Development] andip71:
Sure, that is the reason I will not pull the kernel.

In the revert comment, it was mentioned CM team is awaiting new improved touchscreen firmware. So we will see soon...

Andi
[ONE Original Android Development] Stroky:
Thats right, DT2W is disabled since i've got my One.

For me the Idle Drain over Night and when i use the Phone is the same as usual.

So i will stay on this version:good:
[ONE Original Android Development] brisac:
So what's the final decision? Pushing new kernel with reverted touch screen drivers or waiting for cm new firmware?
[ONE Original Android Development] andip71:
Pushing new kernel with reverted touchscreen drivers but new WIFI drivers (for cm12s, cm12, cm11s, cm11, Oxygen OS).

Pushing new kernel with reverted touchscreen drivers but new WIFI drivers and all other 53 patches of last night for cm12.1.

Andi
[ONE Original Android Development] Mayday_XL:
Danke Andi.

*** Mayday@O+O ***
[ONE Original Android Development] molonad:
Oh thank you, i must say that I Dont really see any difference in screen touch, so I dont Care if it is in or not, but if it caused battery drain i would like to use new kernel which have reverted this touch driver, new kernels are already up or not? Thanx Lord
[ONE Original Android Development] andip71:
Not yet up. But compiled and in a final testing round...

Andi
[ONE Original Android Development] brisac:
Okay. Thank you very much for ur work and effort :D
[ONE Original Android Development] andip71:
Updates to ALL kernels

Hi all,

so here we go again, after CM team officially reverted the new touch screen drivers due to the high idle drain of 30 mA.

CM12.1 -- Version

4.0-beta16

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

18.05.2015

Latest touch screen driver reverted again, due to high idle battery drain of 30 mA

Updated wifi drivers to LA.BF.1.1.1_rb1.22

Updated with latest 55 official CM kernel commits as of 17.05.15

Ramdisk updated to official CM12.1 version of 18.05.15

CM12s / COS12 -- Version

3.0-beta8

18.05.2015

Latest touch screen driver reverted again, due to high idle battery drain of 30 mA

Updated wifi drivers to LA.BF.1.1.1_rb1.22

CM12.0 -- Version

3.5 stable (final)

18.05.2015

Latest touch screen driver reverted again, due to high idle battery drain of 30 mA

Updated wifi drivers to LA.BF.1.1.1_rb1.22

CM11s -- Version

2.9 stable (final)

18.05.2015

Latest touch screen driver reverted again, due to high idle battery drain of 30 mA

Updated wifi drivers to LA.BF.1.1.1_rb1.22

CM11 -- Version

2.9 stable (final)

18.05.2015

Latest touch screen driver reverted again, due to high idle battery drain of 30 mA

Updated wifi drivers to LA.BF.1.1.1_rb1.22

Enjoy

Andi
[ONE Original Android Development] r0hit.s3n:
M using the 29.04.2015 Euphoria, so the updated kernel for that rom is beta13. m I right?

Tapatalked from

My OnePlus +

Devil Inside©
[ONE Original Android Development] andip71:
Correct.

Andi
[ONE Original Android Development] karthiksitian:
Boeffla-Kernel, will it support multi boot rom..i am getting error while injecting the kernel boot.img
[ONE Original Android Development] andip71:
The support is built in, but untested as I personally never use multi boot.

There are some specialists around here for sure, that can help.

Andi
[ONE Original Android Development] magnamentis:
the term: "same as everytime" is no valid value. if your drain has always been on the higher end compared to what was possible, it might well be that all remained the same, while those used to an idle drain of 1-2% in 8-10hours have definitely seen a negative impact of the new touchdrivers. i myself love the new responsiveness, almost up with what my nexus 5 and noteII provide, but still it's a high price we pay for it. i'll keep a nandroid to compare touchyness hahah... directly and decide later whether to stay on current till solution arises. BTW i have always been able to reduce the touch issue by choosing higher idle cpu frequencies and higher touch-boost values and performance gpu gov and 2 cores always on which even then came with a price in battery on idle, but not that high. so it seems that with each touch-improvment we get some downsides, at least for some. conclusion. the basic problem is hardware and all software fixes fall under the fact that every medal has two sides :)

EDIT: my consumption went form 1-2% in 8-10h up to 12-13% during the same period of time with nothing else changed but that update
[ONE Original Android Development] Stroky:
For myself it is an valid value!

My idle drain is as usual in the night 0,1%/h and the average about 4 -5 days of usage is at 0,8%/h

And the new Touchscreen Software didnt change anything in my case!
[ONE Original Android Development] magnamentis:
yes, tending to the same solution, rom is perfect, kernel is perfect and battery life is abundant for me. in case i have to choose i let it be as it is before going back to double and tripple missed letters and icon touches. a pity that we have to choose but albeit the touch thingy was somehow bearable for the last few months, this is the best touch-experinece i ever had on this device and since heat is a factor in this ( hardware definitely )i have no better option, because if i park my motorbike for 2-3 minutes in plain sunshine in southern spain, the display freezes for minutes until the wind cools it down to a level where it's responsive again.
[ONE Original Android Development] OmegaBlaze:
Boeffla, what ROM would you recommend using with your Kernel?
[ONE Original Android Development] andip71:
I have CM12s on my main OPO, and most of the time CM12.1 latest official nightly on my dev OPO.

Andi
[ONE Original Android Development] Hexxer:
Hi,

i did not understand why everybody revert this patch. What when Synaptic take 5 Weeks to make it better? One Day, one week or 4 weeks with that ****ing display isnt it worth. 1%/hour battery drain compared with an "unusable" display? Ask me: What do you want? In unresponive screen like a brick in a wall or battery drain and 33 instead of 45% rest of the day.
[ONE Original Android Development] andip71:
That is why you can still use the kernel version before, which has the patch still in.

I did not revert it as there might be users that still want it.

Personally, I do not feel good when I know a patch causes more battery drain as this can be a really big programming error in the end (nobody knows), going over some limits the hardware can take. Just playing worst case scenario.

So, I for myself, prefer to wait - especially as I never had significant issues.

Andi
[ONE Original Android Development] karthiksitian:
Confirmed,multi boot not working....
[ONE Original Android Development] andip71:
Then you need to change kernel, or live without it.

I cannot test myself (because I do not like the feature at all) + it is not important for me.

I just know, in the past people used it and I did not change anything. So I am surprised.

But - would be interested with which kernel version is was working still... if someone knows?

Andi
[ONE Original Android Development] karthiksitian:
no , i just checked it..i am happy with kernel for gaming performance,multi boot not required