yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] husky69:
Various options disabled?!?

Hi!

Just installed b9 on my OPO which runs CM11S stock 44R ROM and drifted off in memories of bright, crisp sound on my i9305 two years ago.

But - when I open the Boeffla Config app I realized there are many an option greyed out, including all GPU options ("not implemented in this kernel"), equalizer and all setting down that page, notification LED, touch wake, knock-on and touch LED settings.

Just being curious - is this known / on purpose or is it more likely there is a problem with my ROM?
[ONE Original Android Development] 99x:
It's normal, those features are not supported/available on the OPO.
[ONE Original Android Development] Aavion:
at least not yet

Gesendet von meinem 1+ One
[ONE Original Android Development] andip71:
It is known and on purpose.

Everything not configurable is not implemented in the kernel.

And some stuff will even never be possible on the opo due to hardware differences that are partly quite significant.

So, all is good ☺

Andi
[ONE Original Android Development] DjDiabolik:
I have a "Little" problems whit this 2.0 beta 9 (Add information.. i not have the 44S obviously... i again the 38R CM11s) :)

Some hours ago i need to charge my 1+1............. i choose to not use the stock value after some members have reported to me it's been used a value of 900mA.... i have set the value at 1100mA and i have attached my opo to my AC charger.

During this i have notified on config app this value:

AC Charger - xxxxx mA (900) SL when xxxxx it's the mA used at that time......... What's appened ? I have set 1100mA and my 1+1 continue to use the stock value to 900mA ??

During same charging i have try to raise this value....... i have try to raise to 1500mA but nothing append.... on main page i continue to read 900mA inside the ( ).. It's a bug ?? The slides it's not working ?? or i need to turn on this value whit some switch ??

I have this dubs because with beta 8 i have watched and whit this value set to 1500mA I saw that this value was observed.... because i have this problems ??

Otherwise it's not a big problems for me........ the CM has started the rollout for next OTA 44S....... in about some days i need to flash back the stock kernel for complete this OTA.. after that i wait for a 3.0 beta 1 for my 1+1 :)
[ONE Original Android Development] andip71:
It should be working fine.

The only "trick" is: first set the sliders, then plug your charger.

If you change anything with the charger attached already, it will not get active until you next time plug your charger.

Andi
[ONE Original Android Development] Franc38:
About the charging you already got the answer from Andi, so I sure won't add anything useful.

However, if like many around here, don't feel like waiting the OTA for 44S gets deployed in your place, you could just flash it manually in recovery.

Either the update alone : http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip

or the full rooted ROM : http://www.mediafire.com/download/mz7qmw44cpmi74n/Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip

I did take the first option. In this case you just have to reflash your superuser app (super_su, I presume) and in my case, re-download it from playstore for whatever reason...

Nothing difficult nor risky and it really works well with Boeffla beta9 ! (After 2days 8 hours and 3h screen on, I'm still at 24% battery with zzmove - yank battery, while maintaining a crisp and smooth performance all the way).
[ONE Original Android Development] DjDiabolik:
mmmmmmmmmmmm... ok... but for example i have set to use 1200 before to attach my 1+1 to AC and the value it's not been respected..... ok the value can't be changed in realtime and now i know it :)

[MENTION=2828729]Franc38[/MENTION]

I have the last stable of SuperSU already installed.......... sometime i have also updates to latest beta.......... now i'm stay to use the SuperSu 2.16 with Pro feature....
[ONE Original Android Development] Mash87:
Are you using the stock charger and cable?
[ONE Original Android Development] Franc38:
The charge current is also a function of the hardware of the charger. It's a limiting factor that the kernel as to operate with.

about SuperSu, the thing is that after flashing the OTA, it's gone (normal since the OTA is not "pre-rooted") but then, in my case, even reflashing it in recovery didn't totally work and I had to install it from the playstore. No biggy, but be ready for that in case you chose to go this route to 44S.
[ONE Original Android Development] DjDiabolik:
No no no.. wait wait :) this is a misundestand around here:

I have charged my 1+1 before to install this OTA :) when I noticed this i'm still again on 38R with 2.0beta 9 and config app 2.1.52 and with superSU correctly working at all.......... I have received and installed the OTA 44S this afternoon and now i'm stay wating for first beta for this 44S.
[ONE Original Android Development] Aavion:
for me, all settings stick fine between reboots with default profile. using 44S stock rom with Integrated cm superuser...

Gesendet von meinem 1+ One
[ONE Original Android Development] gianton:
+1 Same here, settings stick fine after a reboot with default profile. Running CM11s 44S with SuperSU 2.16.
[ONE Original Android Development] magnamentis:
thanks for helping narrowing things down

it's clear that not many have this issue, otherwise it would have been around already. there are 3 reasons why i thought it worth to bring it up:

a) its repeatable on my ONE

b) it has been many days the same throughout several nightlies

c) i've made a factory reset recently and therefore have no old residues which are often the cause

d) i'm on nightlies as mentioned so comparison is only possible to a certain degree but not 100%

further i've sent 9 log files to andi and soon ( next week ) we will know what's going on. there remains the possibility that:

1) recent nightlies contain changes which are reducing compatibility since they are not implemented in the kernel ( would not apply to CM11+ )

2) that i again have to go through a factory reset due to some userspace issues, while if it's userspace i have a suspect in mind. i've added one

specific xposed module which has a deeper impact than others and another is know to cause strange issues. reason why i want to see what andi says first is that all works well, i can switch to default and back to my profile and all is well until next reboot.

EDIT: just disabled xposed entirely, same result, read ahad and charging tweaks gone, everything else sticks ( BTW additional boot delay is on 60" )
[ONE Original Android Development] gro95qg:
work on 44s ?
[ONE Original Android Development] MMWolverine:
Actually I've noticed this as well. After reboot/power off system loads up and I get SoD. Reflashing kernel + SuperSu helps, but I never reported this due to the fact I use Xposed.
[ONE Original Android Development] el_alemany:
Same problem here....

Unfortunately, I have the same problem.

Phone seems dead, but can be restarted by pressing the power button for some seconds.

COS 13.0-ZNH0EAS2JK, Boeffla-Kernel-5.0-beta4 with internal superuser script applied.

Would some Logfile be helpful in finding the problem ?

Stefan
[ONE Original Android Development] Orphee:
No issue for me
[ONE Original Android Development] kryshnakishore:
How to solve this without unroot
[ONE Original Android Development] JackDidi:
ZZMoove optimal profile? Which one?
[ONE Original Android Development] xlollomanx:
If you're using xposed try with RootCloak.

Sent from my Oneplus One
[ONE Original Android Development] andip71:
Undervolting?

Overclocking?

Using a different governor than interactive?

Xposed?

How did you flash the rom? (did you properly do the OTA update or flashing an inoffical full rom...)

etc etc etc...

There can be many reasons for screen of deaths. These are some obvious ones.

When device does not wake up anymore, no log would help.

Also not for me. But I always do a very clean flash + use only apps I need + do not overclock, undervolt, use interactive etc etc etc.

Andi
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] cos13 full zip is out on cyngn support.
[ONE Original Android Development] Lookitfast:
Yes optimal or battery yank ;)
[ONE Original Android Development] JackDidi:
Thanks..hotplug setting which one you use?
[ONE Original Android Development] Lookitfast:
Optimized also
[ONE Original Android Development] guillermorojaz:
And finally came out

https://cyngn.com/support
[ONE Original Android Development] andip71:
Thanks guys. I have a website watcher that also informed be about it already.

So, I will do a last roundup to the COS13 kernel version today, replacing some stuff by versions of this firmware (debuggable image).

Then I will be quiet for almost 3 weeks, being on holidays soon.

Andi
[ONE Original Android Development] andip71:
Good morning,

finally also an update for the COS13 kernel:

COS13.0 -- Version

5.0-beta5

03.05.2015

Note: You should update to COS13 version ZNH0EAS2JK to use this kernel version !!

Change: Ramdisk updated with official debuggable image of ZNH0EAS2JK

Change: Enhancements to kernel build script

Enjoy

Andi
[ONE Original Android Development] kryshnakishore:
Its not working. Any other way?
[ONE Original Android Development] andip71:
When apps are not working due to root, it is nothing for a kernel thread discussion I am afraid.

Andi
[ONE Original Android Development] guillermorojaz:
Greetings Lord Boeffla.

Small question, which SuperSU should I use for this ROM?

EDIT.

This version worked well for me:

https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
[ONE Original Android Development] andip71:
You can use 2.65, maybe newer ones work too.

I personally do not recommend SuperSu at all. I try to avoid it where I can.

My configuration is my kernel + the zip flashed which enables inbuilt CM-superuser again. For me this is the top-notch configuration as it gives zero issues.

Andi
[ONE Original Android Development] Clark789:
Hello,

i have a short request: i gave my OPO to my son with COS 12.1 and now he likes to move to Marshmellow. And therefore i have some questions resp. requests:

1. Which one is perferable: CM13 or COS13? I think, most users here prefer CM13, don't they?

2. Can you please give me the latest download links for CM13 and fitting, smallest Gapps?

3. Andi, you mentioned a flashable zip for activating the inbuilt CM-superuser. Is it only necessary for COS 13 or for CM13 as well? Where can i download it?

Thanks in advance

for your help. I know, i can find it myself with a little bit more reading and googling, but i only have very few time at the time being and my son gets more and more annoying, because he has problems with COS 12.1 and play services. so, he wishes to move....

Regards

Clark
[ONE Original Android Development] kimikim0:
will this kernel fix the bug with check proximity wake up enable dont work on latest cos13 ? sorry i dont know it kernel or the rom problem
[ONE Original Android Development] inzaghi89:
No it doesn't. I'm mad at cyngn and OPO about this option doesn't work. Phone can wake up in pocket without any sign...
[ONE Original Android Development] andip71:
1) I use only COS on my daily. I believe it is something like a good snapshot, but maybe even more tested. At least I personally have the best feeling with it.

2) CM13 from download.cyanogenmod.org. I only take gapps freshly from here: http://opengapps.org

3) CM has it already in, it is only needed for COS13. The download to the enabler script is in the kernel download folder in another sub folder.

I do not even know there is such a bug. So the answer is quite clearly - No. I did not do anything on that (which I believe is anyways not a kernel but a rom issue).

Andi
[ONE Original Android Development] Renosh:
Actually they are asking if flashing your kernel can fix that bug, they're not saying it's your kernel causing it.

I find it extremely annoying myself and I'm waiting for next COS update hopefully they fix it
[ONE Original Android Development] andip71:
Was it the same on previous COS13 release, or only on latest release?

Andi
[ONE Original Android Development] Renosh:
It's the same on current and previous release. It's probably cause of how old the ZNH0EA branch is. It'll be fixed once they get to ZNH2K I'm assuming, it was fixed a couple months ago in nightlies
[ONE Original Android Development] guillermorojaz:
Please, excuse me ;)

I'm a little lost, I hardly had time to update COS13, could you guide me a little with the root? :eek:

Flashing the Kernel would Boeffla, but where the downloaded zip flashed Which Enables inbuilt CM-superuser? :confused:
[ONE Original Android Development] *Zapp*:
The zip to install with TWRP to enable CM/COS native root is in it's own folder in the kernel download section at the Boeffla-Kernel site.

Works great, but. Since I use Nova Launcher and it has root rights I have a constant # in the notification bar. Please tell me how to get rid of that.

/Jonas...

Skickat från min A0001 via Tapatalk
[ONE Original Android Development] guillermorojaz:
Grateful for the help :good:

I have already installed the Xpoder Installer (Xposed-V82-sdk23-arm), he has not given me problems. There is a module that disables the # of statusbar, called DisableSU, it worked with COS12.1. I try it and notice if it works with this new ROM.
[ONE Original Android Development] andip71:
In a clean way (without xposed crap) you cannot get rid of it.

But, who cares?

Andi
[ONE Original Android Development] guillermorojaz:
With this module eliminates # the Statusbar.

http://xdaforums.com/xposed/modules/mod-disable-su-indicator-cm12-t3056432

It works for COS13 :o
[ONE Original Android Development] heitoradv:
Sorry man

which profile you recommend for COS13?

Enviado de meu A0001 usando Tapatalk
[ONE Original Android Development] andip71:
Whatever suits your needs. There is a profile thread even, where all the configuration specialists are in.

I myself am pretty boring, I run the phone almost with Boeffla default settings.

Andi
[ONE Original Android Development] bloof:
You can create a theme with transparent png replacing the #.

I will try. Of course you have to do it for your own theme...

With apkeditor open the theme apk with FULL edit, then add (or replace) in overlays/com.android.systemui/res/drawable-xxhdpi a transparent png called stat_sys_su.png
[ONE Original Android Development] Wuhlifant:
Is there any way to get a shortcut or widget which quickly can change charging settings? My external battery packs can't provide that much mA charging compared to AC (but the opo recognizes it anyhow as AC and not USB)

Thanks
[ONE Original Android Development] waterdaan:
Thanks for sharing your kernel

I think my logcat is somehow broken

I'm using SuperSu

I don't know if that has something to do with the kernel.....

This is the last message that logcat gives me, it just stops after that.

I've tried to completely reflash the kernel, but that didn't help
[ONE Original Android Development] Leoxur:
with bloeffa I have this wakelock (the first)... I am already at 1h awake, is top much, I usually get 50m awake at 15% of battery
[ONE Original Android Development] Aavion:
Looks like some sensor-related wakelock... touchscreen? proximity sensor? dunno exactly, you may try to ask Google for it, maybe you'll get some insight about it...
[ONE Original Android Development] Leoxur:
I searched it on google bit no result, I nave never heard that wakelock
[ONE Original Android Development] issawillwin:
I'm on latest beta cos13 kernel.

bam_dmux_wakelock is pumping too much juice.

Is this kernel related or Rom related ? Thanks a lot
[ONE Original Android Development] andip71:
You can create mutliple profiles in Boeffla-Config which different charging settings.

Then you can place shortcuts for the profiles on your homescreen to switch them.

A widget is not the right thing here, but shortcuts are.

Logcat is not a kernel thing anymore since CM12.x already.

You would have the same wakelock with stock kernel, as my kernel does not add any wake locks.

This is a known wake lock that exists since the OPO exists.

Threads are full of it. It is triggered by the modem, not kernel related.

Andi
[ONE Original Android Development] andip71:
Hi all,

last maintenance update before I will disappear for 3 weeks for holidays:

Version 5.1-beta20

05.05.2016

Update: Updated with latest official CM kernel commits as of 05.05.16, 8am CET

Update: Ramdisk of official CM13.0 build of 05.05.16

Enjoy

Andi
[ONE Original Android Development] Fenvarien:
Thanks for your hard work and have a nice and relaxing holiday with your family! :)
[ONE Original Android Development] andip71:
Hi guys.

Time to say goodbye now for 3 weeks.

I am shortly departing to sunny Florida for my annual holidays.

This means:

I will read the forum but most likely not answer or only answer delayed.

There will be absolutely no kernel updates until I return

If things break in the meantime, they break - no way out :)

Have a goooood time!

Andi
[ONE Original Android Development] Lookitfast:
Enjoy my friend!!:highfive:
[ONE Original Android Development] magnamentis:
force systemless root or as was mentioned try root cloak while the first would be a proper solution. how to do that you find in the SSU threads.
[ONE Original Android Development] hellcat50:
Please have a look at "Langzeitbelichtung", because it's not working on COS 13 with your kernel (stock kernel works) (if you are back of course :) )
[ONE Original Android Development] kryshnakishore:
Thank u will find it
[ONE Original Android Development] Gawd:
Can anyone just install this App and let me know the readings (a screenshot would be appreciated) --> https://play.google.com/store/apps/details?id=com.acorilhas.opochargingcurrent

I'm just trying to figure out if the problem is with my adapter/cable/ROM/Kernel or is it just normal. But, I feel slow charging. I'm running CM13 by jgcaap (This ROM is so smooth) with Boeffla kernel v5.1-beta20 (makes it more fluid, thanks Lord Boeffla)

I'm also attaching my screenshot. I'm currently using a Samsung charger and Samsung Cable, because the original adapter from OnePlus just started behaving abnormally(like it would charge really slowly, would take 10h+), I still don't know why. I tried all pairs, OnePlus Adapter + OnePlus Cable, OnePlus Adapter + Samsung Cable, Samsung adapter + Samsung cable and Samsung Adapter + OnePlus Cable. The Samsung combination turned out to be the best. And this happened like 7 months ago. This Samsung combination was just working alright, but now it's kinda slow charging. I'm also attaching a picture of Samsung Adapter (its 5V @ 2A) and cable. So please help me figure out the problem.

Thank you for reading and spending your time on this. Any suggestion would be appreciated.
[ONE Original Android Development] andip71:
Really, can someone else try to confirm that?

Have no cos13 with me here yet, but it would be surprised if that is broken as I did not even touch the camera parts.

Andi
[ONE Original Android Development] hellcat50:
Sorry for the false warning, my file system was f2fs and after I changed it back it no longer crashes the app. quite strange though
[ONE Original Android Development] Aavion:
COS13 has problems with f2fs... I also had many strange things happen, when I was on f2fs after the upgrade from COS12.1.1 :D
[ONE Original Android Development] Droidalok:
I didn't try the app yet, but I faced a similar issue myself recently, turned out it was the OPO cable that was faulty. Replaced that and now the phone charges as it should. Try getting a new cable
[ONE Original Android Development] erorcun:
Hi Lord Boeffla,

Are you planning to use off-screen letter detect feature of our touchscreen? I don't know are you aware of it but it reports all the letters, but driver only consider m(0x6d) and w(0x77)
[ONE Original Android Development] andip71:
Not really, as assigning actions to it requires userspace support.

So we would need an app on top to do something with it.

What is your idea behind?

Andi
[ONE Original Android Development] erorcun:
Assigning words as an unlock code would be handy, and all the detection&unlock can be done on kernel side.
[ONE Original Android Development] zertyuiop:
Something new about my bug: after long investigations, I founded that it caused by ZZMove hotplug profiles. May be they are not compatible with Android 6 or only with COS 13, I can't check. I confirmed this bug on two my OPOs. Can someone else confirm this bug?
[ONE Original Android Development] andip71:
Then [MENTION=3279788]ZaneZam[/MENTION] might want to look into this during my absence. He is the zzmoove dev and owns this part anyways.

Andi
[ONE Original Android Development] Aavion:
afaik, bypassing the lock screen with an additional unlock method (like screen-off gestures) needs to be supported on ROM side, as the kernel has no way to interact with android's security settings. And allowing a userspace app to provide this feature would break android's security guidelines.

You'll need screen gestures as an unlock-provider in security settings, and this is nothing, a kernel could do. What a kernel may do is providing the basic support for that kind of feature (recognizing gestures).

Or is it possible for a simple app to register itself as an unlock provider? That way it might be possible to implement the desiered functionality by providing kernel side gesture recognation and app side unlocking based on these gestures. Dunno if [MENTION=947981]Lord Boeffla[/MENTION] is interested in looking into this? :D
[ONE Original Android Development] erorcun:
I mean that unlock code will simply turn on screen. But unlocking phone is easy too, you will add new key code, than handle it in some app (in this case it's Boeffla Config) and ta-da , done.
[ONE Original Android Development] ZaneZam:
sure as always will try my best andi. :)

[MENTION=6953974]zertyuiop[/MENTION] can u reproduce it with logs enabled and generate a debug file via boeffla app for me? would be great to know what ur setup is

and when exactly it happens. ;)

beside of that i have to state: i'm running zzmoove (and only this governor *g*) with native hotplugging (default setting) since months w/o issues

on COS12.1/13.0 (even with my bit experimental uber/linaro builds). well COS13 not that long but still weeks ;)

so if it is the culprit it might be some correlation with other settings/things u use (?). but lets see i anyway can't do much without any logs ;)
[ONE Original Android Development] zertyuiop:
Logs for [MENTION=3279788]ZaneZam[/MENTION]. I found this bug on all version of kernel, official and ZaneZam builds. With and without Xposed and SuperSU.
[ONE Original Android Development] ZaneZam:
eh thank u zertyuiop i see and now i must advice that u do not use any of the linaro/uber versions

(especially the u700 is experimental "as hell"!) when it comes to testing of stability!! :)

i also switched back to my preferred u531 as the u700 was (somehow expected) a bit "shaky"!

about the logs:

the kernel didn't crash in zzmoove so either it did indirectly or triggered from "extern" (system). even though i give your

used setup a try on my device with the mentioned u531 kernel. maybe u can do the same, i mean using the u531 ?

BUT if we wanna talk about this issue HERE then u HAVE TO use the offical build otherwise we have to stop.

Primary objective of mine: we have to keep official/unofficial things separated exactly because of such things! if the toolchain

or optimizations are the reason then we just "poisoned" lord boefflas thread, and we really don't want that, eh? (sry andi *g*)

Aaand before we going on in the other threads: if there are troubles with any of my builds then use the official ones they are

proven to be stable. thx for understanding [MENTION=6953974]zertyuiop[/MENTION]! ;)
[ONE Original Android Development] zertyuiop:
I will post same logs for the official version, If they can help. I only post logs from kernel I am using now. I also attached my settings for Boeffla-config.
[ONE Original Android Development] kryshnakishore:
Can we use our kernal on Resurrection remix rom?