[OnePlus X Android Development] Nachiket.Namjoshi:
FAQ's

FAQ

Q. Does it work on any ROM of Lolipop (Android 5.x.x) ?

A: I dont know. It should. Technically. Since this is in testing phase would you care to try and post on the thread?

Q. HOLY FUUUU, THIS KERNEL BURNT MY DEVICE, BRICKED MY OPX !!!!! Y u do dis? i crie ;-;

A: Ah, Sorry, I didnt mean to. maybe you did not do at least 1 of the following:

Did not flash kernel correctly as written in the instructions

Did not read disclaimer

U lying

Q: Doesn't boot with Sultan's CM, why?

A: Sultan's Source and mine dont see eye to eye. Head over here for explanation.

Q. Which ROMs Does it support then ?

A: Any MM (Android 6.x.x) based ROM (AOSP & CM), Please test on 5.x ROMs if you can

Q. Why this kernel takes so much time to boot?

A: Take a look at THIS post.

Q. Whats up with new bootloader only support from beta-3.8.1 ?

A: Thats because new update brings several things with it. We've been using LP blobs on MM and even with N.

Several bugfixes were needed now since we have new blobs, we have much more options.

Q. What happens if I give current above 2200 while using `setcurr` utility?

A: Nothing, It wont accept.

Q. I Switch off my `Force Fast Charge` but it turns on after every reboot, WHY?

A: It is configured to do so, If you want to disable fastcharge behaviour, set your charging current to 0 using setcurr utility.
​

Known Issues

Issue: In OOS version, USB MTP doesnt work (PARTIALLY FIXED)

Workaround: Try toggling USB Debugging (enable if disabled or vice versa, thanks to @feligoni) if doesnt work, report in thread. post #108

Workaround2: Set Selinux to permissive.

Issue: In OOS version, left hw button doesn't work on some devices (FIXED)

Workaround: Swap buttons and try again (thanks to @dadaz007 ) if it still doesnt work, use sw buttons till the issue is fixed. post #95

Issue: Doesnt Boot. Stuck on Blank Screen with LED glowing.

(FIXED)

Workaround: I dont know what mode this is as such (Please educate me). Now for the solution, AFAIK, this is caused due to

kernel upgrade. Please do the following. It should boot.

Clear Your Dalvik/ART Cache and reboot.

If the device still goes into this mode,

Hold down Vol Down+Power Button for 10 seconds.

The device will reboot into recovery, reboot to system from recovery.

The mode discussed above is what I call: ColorOS Mode and will be refered as the same until somebody tells me what exactly that is.

In this mode, we have all the system partitions mounted as well as latest kmsgs and logs and stuff. pretty useful. I will post a

detailed procedure on how to get logs in this mode. Since they will be useful for me for further development.

​

Recommended Configurations:

Battery Friendly:

Max Freq: 1036MHz (for real. NO lags)

Min Freq: 300 Mhz

CPU Governor: elementalx/impulse

CPU BOOST:

Sync Threshold: 422/652 MHz

Input Boost Frequency: 652/729 MHz

My personal Settings Screenshots

​

Performance:

Set everything to max. and for cpu gov use "performance".

just kidding. TODO

​

My Request:

Please, provide logs if you are about to post a bug. Also dont request for any features. If you want features, this is probably the right thread for you.

Please DO NOT report bugs with OOS version if:

You are using OOS 2.x

you are using any tweaks that are meant for CM/AOSP based ROMS

Also read this post.

FEATURE USAGE:

SETCURR

Open terminal emulator

Enter Following:

su

You need to be root

setcurr <current-in-mA>

It switches to the specified current for charging

Valid Range:Upto 2200

NOTE: Set it to 0 for Default behaviour.