yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Sorry, never had that ever. Nor have I ever heard that.

But yee, sounds very weird...

Ok, never saw it. The Tapatalk thingy is true, but as I also have it on my s3 I did not pay attention to it.

Anyways, next kernel will have the partial updates again disabled to fix the glitches for you.

Change log should tell you everything, just look it up on homepage or directly in Boeffla Config app.

But I cannot confirm that from my side, snappiness normal for me.

Andi
[ONE Original Android Development] ZaneZam:
http://boeffla.df-kunde.de/bacon/boeffla-kernel-cm/cm12.0/changelog.htm
[ONE Original Android Development] miguepereira77:
Thanks [MENTION=947981]Lord Boeffla[/MENTION], yeah I'm really scary now...just realize I can't open links in chrome and my reboot menu doesn't show profiles now...temperature went from 35° to 45° in a second as well...I don't know what the hell is going on...this phone is mutating into something LOL!!
[ONE Original Android Development] andip71:
Oh oh.... ?
[ONE Original Android Development] DooshPastesh:
Thanks in advance for your personal support! That's impressive! Every dev should take example from you! (Sorry for my bad english). I used your kernel on s3, now my mother have it and still rocking solid! Keep going!
[ONE Original Android Development] KINGDROID25:
Cause that would help huh lol sorry bout that. On future rom kernel beta 16 ondemand and row
[ONE Original Android Development] andip71:
If you have this more often, try interactive governor instead of ondemand. Just for a test...

Andi
[ONE Original Android Development] dickenam:
[MENTION=947981]Lord Boeffla[/MENTION] I also have read your site (http://www.boeffla-kernel.de/index.php/kernel-settings) and am still a bit confused on the differences in hotplug profiles.

I was wondering if you could expound a bit on my earlier question. I sure would appreciate it! Great kernel BTW :thumbup:
[ONE Original Android Development] andip71:
Post 559 in this thread should give you the explanation you are looking for...

Dokumentation on homepage is indeed still very much focused on Galaxy s3.

Need to extend it to the opo specifics, just can't find the time these weeks...

Andi
[ONE Original Android Development] dickenam:
That was terrific, thanks so much Andi :good:
[ONE Original Android Development] Roman91:
http://review.cyanogenmod.org/#/c/83558/

This is for ad andi? :fingers-crossed:
[ONE Original Android Development] lchiocca:
I'm kind of curious on what exactly those synaptics firmware do... and since my reverse engineering skills need a bit of "training", I thought I would try and tackle it. I'm currently trying to figure out what the processor they are using. Does anyone know it? It could even be that the main arm processor would be used. Andi, would you have any details on this?
[ONE Original Android Development] andip71:
This is exactly the commit which was merged in the official CM12 branch and causing issues for some users.

So, it is exactly the firmware which I reverted out again to make people happy.

I think this is completely closed intellectual property. The firmware is byte code in a header file, and no, I currently have no details on the used processor.

I guess it will be kinda hard to find out more about what the individual fw updates do.

If you find something however, please let me know.

Andi
[ONE Original Android Development] lchiocca:
What I've got up 'til now:

* The firmware is exactly 96'000 bytes big

* It has very little strings in there (duh) but where are the ones I found:

** "S3508AR" - the synaptics product ID - what the "R" stands for, I don't know

** "DS5 R1.4.1" - probably the compiler that was used (probably Synaptics Design Studio 5 revision 1.4.1). If anybody has information about this, please tell me

** "I2C" - Well, it's using the I2C but, which it also used to upgrade the firmware ;)

It's really hard to get anything out of this. My current assumtion is that the firmware is actually a programmable logic controller (PLC) program. But this is really a bold assumption, since I've got nothing else on what the design studio is.

Edit:

Looking at the byte-code, it seems than an "instruction" is actually 32 bytes (!) long. All the modified blocks between all the version are a multiple of 32 bytes... never encoutered such a language.
[ONE Original Android Development] lchiocca:
Ok... I did a quick comparison between all the different synaptics firmware that were in our lord's git repo. Here's my findings:

* Initial version 14001201 (let's just call it "01") [06-Mar-2014]

* Version 02 introduced a lot of code changes [08-Mar-2014]

* Versions 03 [24-Mar-2014], 04 [08-Apr-2014] and 06 [26-Apr-2014] have the same code basis as 02 but with a different "configuration file"

* Version 13 introduced further code changes [29-May-2014]

* Versions 17 [18-Aug-2014], 18 [10-Sep-2014], 19 [12-Sep-2014], 20 [28-Oct-2014] and 21 [30-Oct-2014] have the same code basis as 13 but again with a different config file

* Version 22 changed code again [02-Jan-2015]

From the little I was able to find, the "config file" is probably some kind of sensitivity data.
[ONE Original Android Development] lchiocca:
I got a lot of details on the synaptics touchscreen at hand and I have to admit, it's not as "smooth" as it should be. Theoretically, it should be able to capture 10 fingers at once. But I can completely screw it up with a couple of simple tricks. Some of which I actually involuntarily do when using the phone. Try the following:

* download the synaptics touchexplorer (https://play.google.com/store/apps/details?id=com.synaptics.touchexplorer)

* go into the "touch/hover" screen

* Scenario 1): Try using 8 fingers - does it really keep the counter at 8? not on mine. But who really needs this ;)

* Scenario 2): Use one finger on the very left edge, swipe down and try to find how many pixels you have. I get 1914. Now do the same thing but when you get to the bottom edge go over the capacitive menu key... my pixel count goes all the way to 2033. Might screw up a lot of programs that check the screen size and get a touch event outside of the possible borders.

* Scenario 3) put two fingers of your left hard on the left side screen and keep them there. With the other hand touch the "back" capacitive key on the right side (NOT the back itself). All of a sudden the two points simply vanish. This scenario happens to me quite often but the other way round. I have my thumb-palm almost on the menu key but the touches with my fingers vanish.

Now it could be that these were fixed in the code-changes from the 22-version, I don't know.

(all of these tests were conducted on cm11s with beta17)
[ONE Original Android Development] andip71:
Easy test... quickly flash beta16 and redo the tests. Then you would see it.

However, it still does not make sense to make phones of other users almost unusable, so even if this touchscreen update provides some slight improvements to some people, breaking it for others would not be my route.

Nevertheless, would be interesting to get a test comparison from you with beta16... :D

Andi
[ONE Original Android Development] lchiocca:
Did that right now...

Scenario 1 (eight fingers): lot better. Stays between 7 and 8, where-as the version 21 jumped between 5 and 8.

Scenario 2 (touch outside of the screen): still there

Scenario 3 (touch beside capacitive keys): Fixed! Wow! That was actually one of the biggest issues I had when using the 1+1 one-handed.

Now I'm not asking you to change anything. Here another couple of interesting things: Did you know that 1+ have two synaptics chips depending on the production date? Hehe... yep... there is a version1 and a version2. That might explain why there are people that have certain symptoms and other don't ;).

For me (I don't know which version I have - you have to open it up) the version 22 works great (or at least a lot better). Looking at the "synaptics_dsx_fw_update.c" there is a way to manually update the firmware by placing the fw file at the right place which will get updated upon the restart. Would that be a viable solution as an option?
[ONE Original Android Development] andip71:
Yes, I see the driver obviously can load a fw from a file. Hm, but I am not brave enough to give it a try. In worst case it would destroy the touchscreen with a wrong and defect firmware.

Also we would need to convert the firmware from the header array into a proper file. Doable, but one little error and the consequences are again potentially huge.

However, I am thinking about another idea currently about making it switchable.

Not something I can follow very soon unfortunately. But food for thought indeed :)

Andi
[ONE Original Android Development] lchiocca:
I already converted the files... I like comparing binary files instead of hex strings ;) And I also notified cm about my findings (https://jira.cyanogenmod.org/browse/BACON-2619).
[ONE Original Android Development] andip71:
And where do you place the file? It must be under "synaptics/startup_fw_update.img". Question is - with which root path?

I am currently thinking about a solution to hold multipe firmwares to be selected even, and make them switchable in the app. Maybe I try a "poor man's solution" very soonish, depending on your progress with the file based firmware :)

Update: After more thinking this idea must be scratched unfortunately.

Also your idea with providing a firmware file does not work.

Reason is quite simple: When the kernel initializes (and the firmware flash happens at the very beginning), the only available filesystem is the root one created by the ramdisk. And the ramdisk is not something where you can put files in a sticky way. So my idea would not work, and also yours not...

Andi
[ONE Original Android Development] lchiocca:
I had the same question... I thought you might know the answer since you've played a lot more with the kernel than I have. I'll try to find out tommorrow.
[ONE Original Android Development] andip71:
See my update above, it would need to be included in the filesystem spanned by the ramdisk. But this is not writable for users, this filesystem is already defined during compile time. Sorry, not a possible way it seems.

Andi
[ONE Original Android Development] magnamentis:
QUOTING COMMIT COMMENT

3 days testing new firmware on franco kernel: improved multi touch experience. Sensitivity it's not improved and ghost touch with Swiftkey are back

QUOTE OF COMMIT COMMENT END

please elaborate why anyone would want that part in BOLD letters, i mean it's clearly stated and i don't even understand why it was merged without desperate need in the first place when considering those comments.

of course i'm not free of personal interests here, because that commit really spoiled my device and i'm very happy that the lord took care of it

---------- Post added at 06:03 PM ---------- Previous post was at 05:53 PM ----------

looks like you two are due for another donation soon, at least from me, that's for sure, a very promising heading IM not so HO haha..... JK
[ONE Original Android Development] schmitzekater:
Scenario 1) Counts even up to 10 and stays there,as long as fingers don't get to close.

Scenario 2) same for me.

Scenario 3) The two fingers stay, even if I press the back button. Then 3 touches can be seen.

My configuration:

Cm nightly from 06 Jan..

Boeffla Test 3.0 beta 1

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
New kernels... tomorrow !

Hi guys,

initially I wanted to release 3 new kernels (cm12, cm11 and cm11s) still today. And the kernels are also ready to ship.

However, I will hold them back for a few hours and release them tomorrow morning (morning CET time) as I will not be close to my PC anymore for the rest of the evening. And I do not have a good feeling releasing it without being able to give some support if there are unexpected issues.

Hope you understand and can wait for another approx. 12 hours :)

What you will roughly get tomorrow is:

CM12 and CM11 kernels updates with latest kernel patches of CM team

GPU frequency control improved and then ready to be activated

GPU freq control will also be included in predefined presets

Partial panel update disabled again to prevent rare graphical glitches

zzmoove upgraded to version 1.0-beta5 with a fancy new function (work-in-progress, but it already works quite well so far) - lots of work done by [MENTION=3279788]ZaneZam[/MENTION] in the past days on it

zzmoove is now able to use it's native hotplugging instead of mpdecision (like in the Galaxy S3 world), there will be a new hotplug profile to activate that - great collaboration with ZaneZam as well on that, really fancy feature

Kernel can now be configured to survive CM Rom updates, so no need anymore to flash kernel after a rom upgrade flash (can be activated/deactivated in boeffla config, as always)

Few internal bugfixes

Ramdisk updates...

Hope the feature list justifies the slight delay of my personal roadmap :)

Andi
[ONE Original Android Development] cd69:
Take all the time you need. This kernel rocks anyway ☺

Oneplus Nexus 5
[ONE Original Android Development] gondsman:
Well, I agree if that is what you experience, but we clearly have different hardware, as I'm not having ghost touches whatsoever with the new release. And I believe whoever was in charge of that commit has my hw and not yours, otherwise he'd have noticed the same. Let's hope the lord can make the firmware selectable someway, so we both can have the best experience with our devices.
[ONE Original Android Development] NOSTALGIA:
whats the best governor on this kernel?? my battery is eaten up. 87% nd i only have 33mins sot..
[ONE Original Android Development] singhz905:
For some reason even i'm not getting more than 5.5 hrs of sot with this kernel. I dont even know whether its good or not. As i see many people getting 8+ hours of sot. I am not a heavy user. I use tapatalk, whatsapp, fb or listen to music. I am using greenify for hibernating apps.

Im using blisspop 1.6 + boeffla latest with interactive (battery)
[ONE Original Android Development] Hexxer:
Hmmmm. Whats going on with "intelimm"? It is around 4 times slower in titanium Backup against" interactive ".

What gouvernor Do you advice?
[ONE Original Android Development] S1ay3r666:
Try SmartMax with deadline 512 ?
[ONE Original Android Development] magnamentis:
sorry but you did either not read or not understand my post or perhaps i was not clear enough.

the text in magenta is a comment made by a cm team member after the commit was merged and as far as that they did recognize it. that's what makes me wonder why they even merge something new which before that was without complaints for weeks, even though some of their own team mentioned problems with the commit. i mean if i have something working ( i did not see touch complaints for weeks ) i would try to improve it, no doubt, but if some interns face problems with it and bring it to my attention, i would postpone and reconsider and test further. and this has not much to do with who has which hardware, as long as they make one rom for one kind of device they have to take into account all variations, like for example cpu clockspeeds out of the box take into account all the various PSV levels. etc. etc.

so i agree to 90% with your statements and understand that you would like what's best for you but it cannot be at the price that others have to tap 4, 5 or 6 times to unlock their device and miss every 2nd or 3rd letter while texting etc. etc. that's trading minor improvements against major annoyance, exactly like [MENTION=947981]Lord Boeffla[/MENTION] stated and exactly the reason why he reverted. mainstream is not always best stream haha...
[ONE Original Android Development] vitokes:
Every time I flash boeffla 3.0 alpha 13 through twrp it begins to flash and then restarts twrp right into the menu and the kernel doesn't flash. Trying to flash on latest blisspop
[ONE Original Android Development] acidburn94:
Try zzmove optimal con scheduler zen:)
[ONE Original Android Development] DanteGR:
As I wrote [MENTION=3279788]ZaneZam[/MENTION] thread this is maybe my best battery cycle ever. Alpha 13 kernel with latest Slimsaber LP, zzmoove optimal gov, zen i/o sched, and cpu freqs 268mhz - 1.728mhz. All rest stock. Just loving it.

Swiftkeyed from my OPO A0001
[ONE Original Android Development] gondsman:
Sure, I understand and I agree. But I think the commit was merged before that comment, that's why I think that the maintainer didn't have any problems.

Anyway, the commit should stay reverted until a better way to handle it is available. I can live with a slightly older kernel for a bit.
[ONE Original Android Development] andrea90:
How to "speed charge" without original charger? I see the option in boeffla configurator but for me seems doesnt' work!

Help please :)
[ONE Original Android Development] NuLLV01D:
that only works when you plug your phone to a Laptop/PC.
[ONE Original Android Development] lchiocca:
For that third scenario: do NOT press the back button. Press it to the right. The entire section with the capacitive keys is touch sensitive. You shouldn't be getting three touches, but rather the first two touches get removed.

Update:

Here are the three scenarios with the version21:

Scenario1 - https://www.youtube.com/watch?v=rmygwFKg-WY

Scenario2 - https://www.youtube.com/watch?v=rm4YEezntbY

Scenario3 - https://www.youtube.com/watch?v=I9brM3EQTqs

---------- Post added at 07:32 AM ---------- Previous post was at 06:58 AM ----------

What about a kernel option that points to different firmware arrays? Something like:

synaptics_dsx_fw_update.c / fwu_rmi4_get_firmware_data(void) {

...

//original: firmwaredata = (unsigned char*)Syna_Firmware_Data_tpk ;

int synapticsFirmwareId = getBoefflaKernelIntOption("myTouchScreenTaste");

firmwaredata = (unsigned char*)Syna_Firmware_Data_tpk[synapticsFirmwareId];

}

and Syna_Firmware_Data_tpk would be "unsigned char Syna_Firmware_Data_tpk[][]".

What do you think, Andi?
[ONE Original Android Development] forzaferrari0:
I can't get more than 5 hours of screen on with the same configuration only the max frequency set to 2457..

In fact with any kernel i obtain more or less the same results
[ONE Original Android Development] The Ramblin Man:
I'll give these settings a go and report back tomorrow to give you another reference.
[ONE Original Android Development] andip71:
That was exactly my idea when I said, I think about making it configurable.

But: during load time of the driver, the driver needs to know which one to load. And for this it needs to look at some configuration, which is not possible as it is too early in the process.

I.e. there is no filesystem availabe to look something up, nor is there a way some configuration/app/whatever can write into a sysfs.

So, making it configurable is simple. But we have no way to make the driver decide on some criteria...

Well, this does not surprise me at all.

Most people completely overrate the impact of the kernel to the battery consumptionl. I would not rate it more than 10-15% in total.

The rest is really:

- apps, background processes

- data transfer for syncs

- rom specifics

- personal usage pattern (gaming, browsing, etc.)

So the remaining 85% really is made up by non-kernel related stuff.

So you would probably need to tackle the thing from anothre angle:

- betterbatterystats to check what keeps your device busy, etc

- disabling unrequired sync jobs

- checking deep sleep rates, wake locks...

Andi
[ONE Original Android Development] DanteGR:
Well it all depends.

For example how many apps do you have installed that sync in the background (FB, gmail, viber etc). Are you mostly on wifi or mobile data? Also, it's a different thing obviously when you are playing games or just browse the internet.

What i can comment on is just my personal usage pattern with the aforementioned setup.

About half of my day is on LTE (strong signal) and the rest on wifi (strong signal). I have all sorts of accounts continously syncing (fb, Google, whatsapp, viber, instagram, Dropbox and more) and mainly use the phone for messaging/browsing, a bit of YouTube streaming (almost never playing games).

There were instances in the past in which I had an app getting stuck trying to sync and thus draining the battery but a reboot is the cure for almost everything.

One last thing is that with the max cpu freq at 1.728mhz the drain is drastically less when the screen is on.

Maybe it's something to consider.

Hope this helps a bit ☺

Swiftkeyed from my OPO A0001
[ONE Original Android Development] emam damon:
[MENTION=947981]Lord Boeffla[/MENTION]

hi sir.are you going to release new kernels today?
[ONE Original Android Development] andip71:
Yes, during today. I am keeping my promises :)

I got a very good input yesterday in a German board, which I just put in.

After I tested it, I will ship the kernels out.

Andi
[ONE Original Android Development] forzaferrari0:
I checked with bbs, no wakelocks, deepsleep is ok and all the unrequited synchronizations disabled

I'll try to lower the max frequency

---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------

My usage is like yours, usually on wifi and just a little bit of gaming, max half an hour a day

I've no apps that drain my battery(checked on bbs)
[ONE Original Android Development] gmi78:
i'm confused....which kernel i use for eupheria rom, beta 1 or alpha 13??

thanks
[ONE Original Android Development] DanteGR:
Alpha 13 but beta 1 should also be ok i think.

Swiftkeyed from my OPO A0001
[ONE Original Android Development] lchiocca:
Please forgive me since my knowledge about the linux bootup is really tiny. If I get this right, boot.img-ramdisk is the first thing that is mounted as root, which then start init (and all the *.rc files). When is the firmware update process happening: before the ramdisk is mounted, inside the rc execution or after all of that?
[ONE Original Android Development] costcutter:
Hi, the boeffla sound app is force closing for me. The app stops if I try to open it after turning it "on" and always stops when I try to click advanced settings even if the app is "off".

Any ideas?
[ONE Original Android Development] andip71:
Boeffla-Sound app is NOT supposed to work on the OnePlus.

The Boeffla-Sound app is not developed by me, it is not maintained anymore and will therefore never work on OPO.

I think I need to place a message in the OP on that.

Use the Boeffla-Config app instead, it gives you all you need and possible for sound.

Andi
[ONE Original Android Development] andip71:
Ramdisk is first, it is the start of anything.

Then it spans the root file system (the content in the ramdisk, folders like sbin and so on), but it is spanned any time freshly. When you write something into this file system, it is not sticky. Next start uses the same fresh content again.

Then the ramdisk basically starts the kernel (zImage) which then initializes the driver.

So all the driver can see is the (sticky) filesystem of the ramdisk.

And even the sysfs is there but there is not yet a process started which would put the configuration in the sysfs.

So, henn and egg problem.

Andi
[ONE Original Android Development] costcutter:
Ah I see, I did search the thread but couldn't find anybody talking about it.

So using the Boeffla-Config app I only have access to the headphone and speaker volume, are there no features like DAC direct?

Thanks
[ONE Original Android Development] andip71:
No. The functionalities you talk about are functionalities of the Wolfson Micro Sound Chip wm8934 used in the Galaxy S3 phone.

The OnePlus uses a Qualcomm/Yamaha chip WDC9320, which does not have these features. Or maybe it has, then nobody knows really as there is no freely available technical documentation on that available.

Hence, only headphone and speaker volumes can be influenced at the moment.

Andi