yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] abhibnl:
Well i bought mine in India in December. and the new drivers were not reliable at all.
[ONE Original Android Development] suaverc118:
Sorry for not understanding. For the latest BlissPop that is dated for today, I can use alpha 13 and not beta 1 correct?
[ONE Original Android Development] kalpik:
You can use either. Works fine.
[ONE Original Android Development] andip71:
GPU control coming soon...

Hi,

quick "sneak peak" of GPU control that will come very soon...

You can define min and max GPU frequency with sliders, just as with CPU.

Basically you can select both limits from the set of available frequency steps 27, 200, 330, 389, 462, 578 and 657 (= overclocking) MHz.

And you can change the GPU governor if you wish to change it.

I will have to release a new set of kernels for it, just to fix a known bug in simple_ondemand governor. But basically all comes to you when I release a new app...

Stay tuned :)

Andi
[ONE Original Android Development] gianton:
Awesome work mate, but as you I believe that GPU OCing is not adding anything in perfomance. On the other hand Down clocking has a large benefit in battery life. Anyway it's always nice to have control of everything on our device.

Thanks again for your hard work.
[ONE Original Android Development] andip71:
This is exactly my point.

I set currently both min and max GPU Freq to 27 MHz only. For me, fluid enough for normal usage, and I would expect some battery saving, hopefully.

So, I also use it only for UC. But then it was not difficult to also put an OC step in for the other guys :)

Andi
[ONE Original Android Development] DanteGR:
[MENTION=1045701]lordbo[/MENTION]effla

Many thanks for your hard work mate. Really appreciate it.

Hope one day you will decide to bring your awesomeness to HTC devices (M9 maybe?)

Anyway, a little something to keep you going.

Confirmation number: 1D808824SU713543A

Take care my friend :)
[ONE Original Android Development] andip71:
Thanks so much, buddy. Just saw your donation and really want to say thank you. Especially as it is not a "standard-donation".

And let's see... most likely is still a Galaxy S5. But time will tell. I am - so far - quite happy with the OPO. It will be my main phone also in the next future...

Cheers

Andi
[ONE Original Android Development] magnamentis:
sure, as i wrote "it looks like it", means there is nothing i found which would proof it true or untrue. it was a general observation and an impression resulting from it. further the date of purchase does not necessarily have to coincide with the date of production. often it does but nobody knows how much time devices are on stock, in a store transfered from one country to another if need is greater somewhere and a batch was too large in another. there are many factors. anyway thanks for the info because beside the fact that we cannot change much about it, however it might be it's still good to have input from as many sides as possible to eventually get a greater picture.
[ONE Original Android Development] DanteGR:
[MENTION=1045701]lordbo[/MENTION]effla

Always happy to help excellent devs and especially nice people mate.

More to come in the future.

Well deserved.

Swiftkeyed from my OPO A0001
[ONE Original Android Development] skodaslx:
[MENTION=1045701]lordbo[/MENTION]effla

What is the difference between the two 44s modems on your site? They seem to have the same size.

With the "Full...." I can revert everything that comes with the alpha modem from the CM12 nightly? So that I'm able to use a 4.4.4 rom again?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Original Android Development] andip71:
Yes. The full modem also flashes tge second partition that comes with the L modem.

At least that is the technical explanation. I didn't need it so far...

Andi
[ONE Original Android Development] KINGDROID25:
Flashed latest test and got sod for like 30 mins, man I freaked.. Was on ondemand and row.. Is this common
[ONE Original Android Development] abhibnl:
What's that secret "Not a standard donation"? :p

Well that's true. But this older driver is really nearly perfect. Everything is working as it should. And my phone's build date is Nov 15 as per the package. Not sure if that's of any significance or not but i guess new batch shouldn't be answer to the issues. Also, i'm hearing on the fresh batch, there's no Cyanogen logo at all.
[ONE Original Android Development] andip71:
Of course not. I never had a sod for weeks...

But also you give no more details, no kernel version, rom used, detail configuration, so nobody can comment on it.

It was a donation significantly higher than the average.
[ONE Original Android Development] dy2592:
Awesome progress

Do I use alpha 13 or beta1 for CM12?
[ONE Original Android Development] gianton:
Beta 1 for latest 01/06 official nightly or any ROM based on it.
[ONE Original Android Development] andip71:
I use beta1 together with official cm12 nightly.

Andi
[ONE Original Android Development] skodaslx:
Thank you.

Now I feel save to test CM12 with the new modem, because with that zip I can easily go back to 4.4.4.

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Original Android Development] dy2592:
Thank You. I just actually saw his #1752 post. Somehow I overlooked it.

---------- Post added at 08:50 PM ---------- Previous post was at 08:30 PM ----------

So is the new Temasek sm v4.5 rom appropriate for the beta1 kernal?
[ONE Original Android Development] DanteGR:
Is it based off the official cm12 nightly? If so yes.
[ONE Original Android Development] dy2592:
I'm still trying to find out ...
[ONE Original Android Development] marcowind80:
Is beta2 released? I'd like install multirom.
[ONE Original Android Development] andip71:
Not yet. It is ready, but we have a big go live in my company this afternoon, after this is finished, I will upload.

Andi
[ONE Original Android Development] Setting.Out:
Take your time.. ;)

Is there any chance I could test the non "s" version?.. I was having issues on stock and want to try a nightly... Thanks
[ONE Original Android Development] andip71:
beta2

Hi guys,

finally the promised beta2, which is mainly a maintenance update (for both 1.0 and 2.0 kernels). Both have the same change log.

Version 1.0-beta2

/

Version 2.0-beta2

12.10.2014

Fixed Kexec hardboot not working

Increase CPU voltages by 25 mV for the overclocking freqs to increase OC stability for many

Update the flash binary in the boeffla-kernel-reset recovery script, bump to version 3.1

Rebased to latest CM source commits

Either download from the kernel homepage, or try the load&flash function in Boeffla-Config for your convenience.

Enjoy

Andi
[ONE Original Android Development] NickosD:
Even better....
[ONE Original Android Development] osmosizzz:
So far so good. Haven't had time to rest the system under gaming stress because I haven't had the time, however everything simms to be running smooth and without a hutch

Sent from my OnePlusOne
[ONE Original Android Development] skydayzer:
Was about to ask about kexec... Decided to read through to see if it has already been ask... Thanks for fixing it..
[ONE Original Android Development] osmosizzz:
Anyone have a link or something that I can use or have any idea of the settings to in the memory settings. We have 3GB of ran and not much of it in getting used. I mainly have 1.5 free at any given moment even with a few apps opened. I'd like to be able to have more apps sit in memory without them redrawing (surpringly, even with 3GB RAM and still having 700MB free, apps still redraw)

Sent from my OnePlusOne
[ONE Original Android Development] _Beni_:
Which apps are you using? Never ever had redraws. Are you reading the memory? Only boeffla config prints the right values.

Anybody knows how the poweron lock works? If i hold the hand on the front camera it just wound't wake up, amazing but will it be poweronable in complete darkness?
[ONE Original Android Development] Han-Droid:
Hi, sorry for OT... I thought a new kernel might have fixed it but is anyone experiencing this error:

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-375

Well... I do...what about you, Lord?

Weren't you on congstar with 3311 as voicemail number?
[ONE Original Android Development] NickosD:
Maybe it's a rom thing?
[ONE Original Android Development] pantmunu:
OK.

Intelliactive clocked at 2.8 GHz

Zen scheduler 256

That's all . I might be able to squeeze 2 more hrs out of it.

Seriously amazing work. Sticking with this one.

Thank you very much sir.
[ONE Original Android Development] suaverc118:
I'm not understanding how to download this. I click the download link but nothing is highlighted to download. I'm on the OPO
[ONE Original Android Development] jgcaap:
What's amazing about 4 hours screen when you can get 10?
[ONE Original Android Development] pantmunu:
Nothing actually .but I'm glad and thought I should post it here. And show people what kind of battery life I got running this kernel.
[ONE Original Android Development] Ankit Tulsian:
10 hours SOT. Are you serious? Please share your settings and kernel on which you got it. If I could even get 8 hours I will be more than happy.
[ONE Original Android Development] berdey:
Finally come to bacon, I like this one.

:victory:
[ONE Original Android Development] otisman:
10 sot pretty easy if you charge after 15 hours total lol and that's not tuning anything

---------- Post added at 05:01 PM ---------- Previous post was at 04:52 PM ----------

It pretty good those are real life numbers plus no tuning no UV only oc and your at 35% much alohas

---------- Post added at 05:37 PM ---------- Previous post was at 05:01 PM ----------

Much alohas lord for the cm update to beta too also
[ONE Original Android Development] jgcaap:
Ah =p the governor you are using is not prepared for this chip. Kills battery unnecessarily

Got this on ak kernel. But basically you need to tune, boost touch (lower to 1ghz) and insert governor interactive.

1hour and 30 min of charge..

I can pass this record. But for now only with ak kernel.

On this one, which is very well built I got only 8hours and 30 min.
[ONE Original Android Development] Vonnegut:
Quoting this post just because it shows the reason why ZRAM is totally useless for the OPO.
[ONE Original Android Development] kalpik:
Yes, it's based on cm12. The beta1 kernel should be fine to flash with it.

Sent from my A0001
[ONE Original Android Development] dy2592:
I thought it had to have a release date of 1/6

Sent from my Oneplus One using the Tapatalk app.
[ONE Original Android Development] DanteGR:
To be honest both Beta 1 and Alpha 13 will be ok. Just flash away you won't have any problems with either one.
[ONE Original Android Development] HaTrED_:
I'm using that combo mate: Tema sm 4.5 & 3.0 beta 1

Flawless!
[ONE Original Android Development] dy2592:
Excellent! Can u share what kernel settings you are running?

Sent from my Oneplus One using the Tapatalk app.
[ONE Original Android Development] HaTrED_:
There you go: governor zzmoove optimal, fiops scheduler, 1024 read ahead, 2 cores always on, slightly uv - 50mv

That's it! [emoji106]

Works great with my setup.
[ONE Original Android Development] gondsman:
Too bad about the touchscreen driver, I must be one of the few people with exactly the same hw as the CM devs. To me the old driver (the one from 33R) was completely unusable, with ghost touches every few minutes. The newer one (the one included in 44S) is much better, no more ghost touches or absurd issues. I find the latest revision to be better yet: no ghost touches and now the scroll is much more "predictable". What I mean is that with the 44S driver sometimes when I want to scroll just a bit the page scrolls a million lines or when I give a strong flick it only moves a bit. With the latest driver the scroll feels more natural, it works as my brain expects it to work.

I guess having the two drivers be selectable at runtime (with a reboot) is not an option, isn't it?

Thanks anyway!
[ONE Original Android Development] amjath:
Can anyone please post the Boeffla configure apk, I could not download it from their site.
[ONE Original Android Development] andip71:
Why not, what is the problem?

I really don't want old files spread around somewhere else.

This is technically not possible, as it is not a driver but a firmware which loads too early in the start process to make it configurable.

Let's hope they release a firmware that fits all one day.
[ONE Original Android Development] amjath:
I dont know the chrome in android as well as stock browser keeps asking which app to use instead of downloading even though i give "Always"
[ONE Original Android Development] andip71:
And you are sure you tried to download this file?

http://boeffla.df-kunde.de/bc/2.1.61_boeffla-config-v2.apk

Andi
[ONE Original Android Development] kurtextrem:
Wow, i thought I'm the only one thinking like that and therefore wasn't sure if I'm only imagining. but yes, I feel the same. I kept the old-new kernel for now.
[ONE Original Android Development] andip71:
Yes, I would not have reverted it back if there were not people whose phones were almost unusable (again) with these drivers.

So I think I needed to be fair and sacrifice a slightly improved experience for some users in order to bring other users back to a working state.

I personally did not feel any difference, so I am anyways in the middle.

Let's see what the next touchscreen update will bring for us.

Andi
[ONE Original Android Development] amjath:
Yeah same. Still the link opens in chrome from tapatalk and chrome keeps opening multiple tabs. I think I should download it in PC at home then transfer it
[ONE Original Android Development] andip71:
That is really weird.

What about this link, does this work for you?

https://www.dropbox.com/s/2epphwdz9ubfgr7/2.1.61_boeffla-config-v2.apk?dl=1

Andi
[ONE Original Android Development] Mandrake2010:
Beta17 on Cm11s alla OK but i see GPU default max freq 657Mhz ....i nave used Antutu (balance) 2880 but drop gain in RAM and GPU.

I dont have interest in benchmark but it is normal the 3d test drop 2000/3000 point with GPU at 657?

Inviato dal mio A0001
[ONE Original Android Development] andip71:
What you see is only the POSSIBLE max GPU frequency.

However, the kernel is configured to not use it.

So, it will not be used unless you want so (with the next app).

In order to prove this, you can find which frequency is used for how long in this file:

/sys/class/kgsl/kgsl-3d0/devfreq/trans_stat

It will show you, this overclocking frequency step exists, but is never used (so far).

And for the question about benchmark drop or gains: I do really not care and trust benchmarks unless they show 50% difference in some runs. It is normal, benchmarks are not accurate.

Andi
[ONE Original Android Development] amjath:
same bro not working. BTW Thanks
[ONE Original Android Development] andip71:
Ok, then it seems all your browsers have an issue with downloading an apk.

Last try then:

https://www.dropbox.com/s/kvvjpfhupju2c6k/2.1.61_boeffla-config-v2.apk.zip?dl=1

This is now the apk in a zip file. You have to unzip first.

Andi
[ONE Original Android Development] xanthrax:
Hi Andy, damn nice kernel, thank you, good job!

Sent from my Darkside of 1+1
[ONE Original Android Development] Fenvarien:
I experienced this chrome behavior too. Try a long 'click' on the download link until a menu pops up. Then choose 'save link' and chrome will download just fine. ;)
[ONE Original Android Development] Almayce:
Or you can "request desktop site" in Chrome. It usually works when something is not working for me. Also nice workaround for mega links, you don't have to get the app like it says, just request desktop site and you're good to go :)
[ONE Original Android Development] DanteGR:
[MENTION=1045701]lordbo[/MENTION]effla

Just had a soft reboot (didn't ask for pin) using cm12 alpha 13 kernel on latest Slimsaber LP. Using interactive standard gov and underclocked @1,7 ghz. All rest default.

Boeffla debug attached.

Any idea?

Thx in advance mate.

https://www.dropbox.com/s/qr1fkwcaj...8.txt?dl=0/URL]

Swiftkeyed from my OPO A0001
[ONE Original Android Development] amjath:
Few Bugs:

Play/Pause is not working using Music player

When Volume Up/down is pressed via headset, display wakes

When screen is off and volume up is pressed on phone, Music track skips and then screen wakes.
[ONE Original Android Development] Goggle81:
[MENTION=4006892]amjath[/MENTION]:

What ROM du you use. All your bugs are features of some roms I know :)
[ONE Original Android Development] cerealguy:
Which version do you use on BlissPop, mate?? :)

Sent from mine BlissPopped 1+1 Bamboo Edition
[ONE Original Android Development] Roman91:
all solved in the last cm12 build (not kernel related)
[ONE Original Android Development] Texan1:
[MENTION=947981]Lord Boeffla[/MENTION]

Just trying your 3.0 beta1 kernel and noticed that graphical glitches are back on my phone, these were solved by reverting partial-update feature that I believe you incorporated into your kernel (slimsaber rom has this revert partial update feature and solved graphical issues - http://xdaforums.com/showpost.php?p=57719971&postcount=8543). The graphical glitches go away if you go into Developer Options and tick 'Disable HW overlays' but this setting doesn't stick after a restart and has to be enabled each time.

Is there any reason you haven't reverted this commit again?
[ONE Original Android Development] Roman91:
how to reproduce them?

cm12 official build +3.0b1 without any glitches
[ONE Original Android Development] miguepereira77:
Have it as well but they are random...difficult to reproduce...I thought was ROM related (CM's official nightly) not kernel (boeffla's beta)...
[ONE Original Android Development] Texan1:
If you don't get them you won't be able to reproduce. For some reason a specific issue that some users were affected by around 44S update. Can be solved in two ways - Disable HW overlay setting upon every reboot, or revert partial update feature which slimsaber rom has done, and also Lord Boeffla did a few kernel revisions ago.
[ONE Original Android Development] amjath:
I'm using LiquidSmooth, when I use stock kernel it was working properly. Adding this kernel making issues.

CM12 build by who? Does that ROM have off screen gestures?
[ONE Original Android Development] andip71:
Yes, the main reason was: I wanted to be in line with official CM12 code again. I cannot believe, CM team will longer-term not do something about it.

It also seems, not everyone is affected, as I have never seen them.

Hm, hard one... I usually like to be close to stock. Ok, we will see for next beta.

It is not kernel related as such! My kernel uses 100% stock code for panel driver and 99,9% stock code for gpu driver.

Andi
[ONE Original Android Development] andip71:
Important question:

Did you have these graphical glitches only on CM12 or also previously on CM11 or CM11s?

I would really need to understand that...

Thanks

Andi
[ONE Original Android Development] Texan1:
I never had them at all until I updated to 44S, ever since then, no matter what rom or kernel I use they are there unless I go into Developer Options and tick Disable HW overlays, which gets rid of them completely. As mentioned, [MENTION=1228651]fusionjack[/MENTION] reverted those commits in his rom and it got rid of the issue, same as when you reverted them a few revisions ago :good:
[ONE Original Android Development] andip71:
Was asking to find out, when I put it back in, whether it would also fix issues on cm11 or cm11s for some.

As I never saw it, I wanted to find out.

Andi
[ONE Original Android Development] Texan1:
No probs Andi, it definitely fixed the issue for users who were affected, if reverting that commit(s) doesn't cause any other issues (I haven't seen any) would be great if you could revert again as then it opens up people who have the issue to be able to use your kernel. Thanks :good:

Edit - This is the thread where I originally saw the advice to disable HW overlay (OP refers to ghost touches as well which is a separate issue) - http://xdaforums.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
[ONE Original Android Development] andip71:
It will not cause issues for others, no question.

However, it is a performance optimisation, so it has in theory some negative impact on panel performance.

If this is noticable/measurable, I do not know. But I believe when using the phone normally (no gaming etc.), it will not create any user experience difference. And this is what counts, my kernel is not supposed to be for gamers anyways :)

You have a PM, Texan1.

Andi
[ONE Original Android Development] Eef:
Coming from AK kernel, I like this kernel very much! Do you recommend zzmoove or smartmax for most battery with little performance or even intellimm? Thanks! I do also like your config app! ?
[ONE Original Android Development] Roman91:
andi sorry for the OT question (or maybe not) :angel:

with my actual config I have a terrible battery drain under "miscellaneous"..

Expected drain 800mAh

Actual drain 1200mAh (+50%)

almost all services are off, also the SOT time is max 5h

I noticed when using the phone battery drains faster than with 44s.

Do you think it's all rom related?

PS also wakelock detector is not working with andoid 5.0 :crying:
[ONE Original Android Development] Notor1ouS-:
this kernel is so good, how can i marry it?
[ONE Original Android Development] Roman91:
buy to andi a ring with a diamond lol
[ONE Original Android Development] andip71:
This is, afaik, a known issue with battery consumption calculation of cm12.

In fact, it is not draining at all.

Well, that is also all I can currently comment on it :)

In Daleski75's thread was a lengthy discussion about it.

Hm, let me think. I will come back to you on that.

Just wonder what my wife will say then? :cyclops:
[ONE Original Android Development] amjath:
[MENTION=4574570]Roman91[/MENTION] bump, which cm12 is best with this kernel
[ONE Original Android Development] kalpik:
I can confirm a +1 on the graphical glitches. If you need me to test anything, let me know.

Sent from my A0001
[ONE Original Android Development] ZaneZam:
I guess she would say : take it! :D
[ONE Original Android Development] miguepereira77:
So, I posted this in CM's unnoficial thread and want to do it here as well just in case someone can help me, as I'm using [MENTION=947981]Lord Boeffla[/MENTION]'s kernel with the ROM:

"Hi guys, hope u can help me because this is the weirdest thing ever happened to me in all devices I had...So, yesterday, I fastbooted 44s to clean everything and I clean flashed CM's nightly...all went well (couple of hours of normal usage) but suddenly, when I dt2w...my home and menu on-screen buttons were gone...I enabled soft buttons and home and menu didn't work as well...I rebooted...nothing, wiped caches and dalvik...nothing...dirty flashed...nothing...So I have to factory reset and start again...all went well, and suddenly, few minutes ago, the same thing...Any clue? Because this goes beyond my knowledge...Thanks in advance"

Aprecciate any thought about it. Thanks again
[ONE Original Android Development] DooshPastesh:
I also had some glitches. Never had on CM s version. It started on lollipop (i've used only blisspop with boeffla) only with tapatalk ☺ it's not annoying. Visible one second or less. I don't se it now but few updates earlier. Especially when switching between tapatalk and other app by button function. It's look like some parts of screen are snowing like in old tv ?
[ONE Original Android Development] Mrj0to:
Hello [MENTION=947981]Lord Boeffla[/MENTION]

What are the changes between alpha9 and alpha13. Since I upgraded from Tema 3.8 with alpha 9 to Tema 4.5 with alpha 13 it seems a lot less snappy then before.

I'm using the same settings as before, didn't change anything..

Any clue what I can do?