yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] LiquidSolstice:
Or instead, since some users aren't having any issues at all and AK clearly uses his own kernel on his ROM of choice without problem, why don't you let him call it whatever he'd like? Yeah, I have rebooting issues on some of his kernels but only on some ROMs. The mistake you're making is calling this a free "product". It's not a product. It's a gift; a collaborative coding contribution to the open source community. Thus, terms like "reliable end product" don't mean anything here.

AK will label his builds whatever his own internal workflow dictates they should be named. He didn't ask for the software naming convention police to audit his builds, and frankly, if you're not contributing to his git, you don't need to have a say in what they are or are not labeled.

And for your reference, CM has labeled many broken builds "Stable" even though they are not; this is because CM's code might feature-freeze at "stable" but device-specific code is anything but.
[ONE Original Android Development] abhi08638:
Can also confirm that I've never had a RR for any of the kernel versions including v60 and up on cm11. The problem is users are using unstable builds of lollipop where the code is constantly changing and sometimes conflicting with the kernel

sent from my amazingly awesome OnePlus One with Stereo Mod

Don't forget to hit thanks!
[ONE Original Android Development] rOck4n:
So it's safe If I flash AK.072.OPO.SKULL.CM12.zip using CM11S stock? I don't have to use a previous version?
[ONE Original Android Development] LiquidSolstice:
For now, yes. [MENTION=3685904]ak[/MENTION] doesn't support you doing this, but thus far, it seems the majority of his CM12 kernel releases have been working just fine on certain 11 and 11S builds. Try it and find out; the worst that will happen is you reflash your stock ROM without wiping and you'll be back to where you started.
[ONE Original Android Development] david23c:
Can replicate this on my OPO too. CM12 temasek 3.8 with ak v.072

I'll post ksmg once I restore my phone.
[ONE Original Android Development] Texan1:
Graphical glitches. Screen jitters up and down, especially noticeable when scrolling. It's a genuine issue that has been reported by others (I'll try and track down the thread info). It can be solved by enabling Developer Options and then enabling "Disable HW overlays" which fixes it, but then as soon as you reboot the phone this setting doesn't stick and you have to enable it again.

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] DerRomtester:
Yep just flash it.

The kernel should work fine on cm11/cm11s

Look at franco kernel: He is using cm12 source code for his cm11 kernel. The only big difference between cm11 and cm12 kernels is the ramdisk. But with anykernel ramdisk you are able to use this kernel on cm11/cm11s/cm12.
[ONE Original Android Development] ak:
The title of this thread is clear:

> OnePlus One > ONE Original Android Development

so if you do not want problems just use the whole stock, it is not difficult.

in line my answers:

rebooting issues = yes

deep sleep problems = no

network and wifi issues = no

I expect from a developer contributions serious, not just criticism.

i have changed the title.

thanks

ak
[ONE Original Android Development] xxBrun0xx:
Have had all of these issues on latest blisspop stable ROM. Clean flashed, no other mods. Would love to help troubleshoot if you'd like. Not sure what you would need, but let me know if you want to fix this stuff.
[ONE Original Android Development] smint86:
For me, v0.72 runs absolutely stable so far (Temasek v3.8). Mostly stock settings, 2 cores always on, ksm on, few other optimisations.

---------- Post added at 05:54 PM ---------- Previous post was at 05:04 PM ----------

I shouldn't have said anything. First random reboot... https://www.dropbox.com/s/tuiesvl83fftgpu/last_kmsg-2015-01-01.17.52.49.txt?dl=0
[ONE Original Android Development] Mojar7070:
Hey, you made me curious. What would be the benefits of have 2 cores at all times?? Faster wakeup?? No SOD?? More responsive during screen off times?? I'm sure battery is affected as well.

Sent from my A0001
[ONE Original Android Development] Rkr87:
I never had any issues but I think a few users has music stuttering issues while the screen was off on 1 core, I believe they enable 2 cores while screen off to work around that issue.

Powered by Bacon
[ONE Original Android Development] _Sasan_:
It seems you and some others here took my comments as insulting or offensive message . I'm sorry if It was sounding in that way. It was my humble opinion about the title and thought that it might be misleading. I was not complaining about the bugs either. As you mentioned I would switch to a kernel that would not make any problem for me. Anyway this is a development thread and sorry about it. Thanks for your hard work once again and good luck.
[ONE Original Android Development] osmosizzz:
Lol I have music issues with all 4 cores on. It's a cm12 thing... Can't wait til it gets fixed
[ONE Original Android Development] ak:
Im working also today for free and for all fantastic guys of this thread:

https://github.com/anarkia1976/AK-OnePone/commits/cm-12.0-msm_bricked

fixed.

No problem you can feel free to expose your opinion.
[ONE Original Android Development] abhi08638:
Constantly hotplugging and unplugging cores drains more battery than keeping it on and letting it scale freely

sent from my amazingly awesome OnePlus One with Stereo Mod

Don't forget to hit thanks!
[ONE Original Android Development] fiz:ik:
But when the screen stays off for a longer time period... it would be battery friendlier to have only 1 core online or am I wrong?
[ONE Original Android Development] f100cleveland:
Right, that's the beauty of show-p's mpd. You can set that to limit it to 1 core only when screens off.
[ONE Original Android Development] f100cleveland:
[MENTION=3685904]ak[/MENTION] just curious why you decided to go back to stock toolchain? Trying to isolate bugs to not be related to tc?

https://github.com/anarkia1976/AK-OnePone/commit/24020d778f53ee657fb30755de3c176149d31bd0
[ONE Original Android Development] ak:
Yes its made only for trouble purposes.

Sent from my A0001
[ONE Original Android Development] ommadawn-xda:
V.074? ?
[ONE Original Android Development] ak:
new kernel online

[ CM12 CAF KERNEL - v.074 SKULL ED. ]

A kernel based on CAF CM12 Bacon branch.

CM12: AK.074.OPO.SKULL.CM12 > CM12

[ SMALL CHANGELOG ]

fixed bug with hotplug driver

merged latest cm12 patches

+ other fixes

ecc ecc

git for full changelog.

Ps: i have used the latest linaro 4.9.3 12.2014 A15 Optimized TC, for testing purposes.

[ FULL CHANGELOG ]

Project name: AK KERNEL
anarkia1976 - Kernel Version: AK.074.OPO.SKULL.CM12
anarkia1976 - msm: bricked_hotplug: clean get_rate and switch to msm_cpufreq_get_freq
anarkia1976 - msm: bricked_hotplug: fixed bug related to ambient display
anarkia1976 - Revert "msm8974: panel: color: tuning colors based on users experience"
Steve Kondik - msm8974-oppo: Display driver update/cleanup
anarkia1976 - Kernel Version: AK.073.OPO.SKULL.CM12
andip71 - CPU hotplug, writeback: Don't call writeback_set_ratelimit() too often during hotplug
andip71 - cpufreq: smartmax: adjust default configuration to OnePlus One
andip71 - cpufreq: intellimm: fix issue with updating tunable multi_phase_freq_tbl
anarkia1976 - ak-bacon-build: give to Linato an Happy New Year
Abhishek Singh - wcnss: Fix for Static analysis issues
Kaushik, Sushant - msm: wlan: Fix dangling pAdapter pointer in HDD.
Shiju Mathew - msm: thermal: Optimize locking in thermal frequency mitigation thread

Please press thanks button.
[ONE Original Android Development] ommadawn-xda:
Downloading right now! ?
[ONE Original Android Development] ak:
do you want v073?
[ONE Original Android Development] ommadawn-xda:
No, no, 74 is fine! ?
[ONE Original Android Development] gianton:
Thanks for your continues work mate, appreciate it!

Happy new year!!
[ONE Original Android Development] xlollomanx:
Just for report that is all OK on cm11s with lastest version!! Nicely surprised that is no more needed to set gamma 1 on synapse to get colder colour

P.s. Happy new year!!

Sent from my Oneplus One
[ONE Original Android Development] Spaulding89:
Thanks for this great update my friend [MENTION=3685904]ak[/MENTION] running good till now. Tomorrow I will report more

Sent from my lollipopped Bacon with loaded AK Kernel
[ONE Original Android Development] HamsterHam:
How do I get the log to report a bug? I have had a reboot on 0.74.

Attached: last_kmsg and dmesg

Hoping that is correct.

Yeah, with 0.74 I cannot use it as phone reboots every few mins on Temasek's UNOFFICIAL Build ROM.
[ONE Original Android Development] zaphodbeeb:
f2fs temasek 0.74

All running well with no fc's as primary and secondary multirom, both f2fs-all and mixed f2fs configurations. :)

Sorry, fc's on both primary and secondary.:(

Testing with Temasek 3.9 currently. Will report and supply ksmsg report if I find problems.

Hi, please find the attached adblogcat. I flashed 0.74 on f2fs (system as ext4, clean install) along with Temasek 3.9, Temasek gapps, supersu and just let be. After a bit got fc and reboots. Anyhow please see attached adblogcat (not the whole thing, just over the time the device fc and rebooted). Hope it helps.
[ONE Original Android Development] sleepy222:
For temasek ROM. Try turning off the feature accidental wake up in display setting if you have it on. This was causing reboot issues for me.
[ONE Original Android Development] crazynitro:
audio glitch

quick question;

is the audio glitch still present in the new update?
[ONE Original Android Development] namelus:
Two Questions,

1) can you install this with paranoid android?

2) Does this kernel include the 44s patch (the lte to H drop calls?)

Thank you.
[ONE Original Android Development] akarol:
Can anyone confirm that the Gamma slider seems booked for setting 1 in 0.74.
[ONE Original Android Development] NickosD:
No need to set it to 1 anymore. It's fine with the stock settings

Sent from my bacon!!!!!

---------- Post added at 08:26 AM ---------- Previous post was at 08:19 AM ----------

1) Did you even did a small research about the kernel? Search the answer yourself.

2) That's happens to all roms and with all kernels. It is how it is for a reason. And also, that's not a kernel fixable. It's from rom.

Sent from my bacon!!!!!
[ONE Original Android Development] HamsterHam:
Turning off ambient display I think works.
[ONE Original Android Development] ak:
Its resolved into the latest kernel. :good:
[ONE Original Android Development] Beaster:
Latest update looking very good!

Got a reboot after i received a hangouts notification.. Ambient display was on.. Will post log if it happens again

AK thx for your work. Enjoy the first days of 2015 with your family. Kernel development can wait for a few days!

Happy new year to all, guys!
[ONE Original Android Development] ak:
Last kmsg doesn't report problems related to kernel.
[ONE Original Android Development] ak:
Thanks a lot. Enjoy the new year. :D
[ONE Original Android Development] Rkr87:
How's this for some idle drain?! :)

This is on 070, should I dirty flash my rom before trying to upgrade to 074?

Powered by Bacon
[ONE Original Android Development] ak:
Not necessary.
[ONE Original Android Development] Criton30:
as I know, if we need to upgrade the kernel, flashing ROM is not necessary, only flashing the new kernel is the right way, or I am wrong?
[ONE Original Android Development] nicholaschum:
Yeah, we figured after all kernels that were up to date were acting strange with us....thanks for clarifying though :)
[ONE Original Android Development] ak:
View attachment cm11s-boot-030.img
[ONE Original Android Development] aleksik:
Thanks! I'm guite new OPO user, came from S4. How to flash a .img? Or is there a .zip version of it, would be easier :)

Sent from my OnePlus One
[ONE Original Android Development] ak:
adb reboot bootloader

fastboot flash boot
[ONE Original Android Development] Poesini:
I am pretty interested in this... Is it supported everywhere (I mean, /system /data /cache and if they are, others)?

And how can I flash to F2FS because I remember when I had my Z1 that TWRP supported mkfs.f2fs , but I didnt find the command here

Thanks man
[ONE Original Android Development] bud77:
Right now, it's not useful, there is no recovery supporting F2FS yet

Official TWRP supporting it is on the way
[ONE Original Android Development] aleksik:
Okay, now I have no idea what to do. I just copyed the kernel.img to the synapse folder and tried to restore it in Synapse. All it did was it turned off my phone and now it won't turn on at all.. I can't get any life to it, no boot, no recovery, no fastboot mode, nothing. Please, do you have some advice for me? :crying:
[ONE Original Android Development] dictionary:
Try long pressing the power button for about 10-15 seconds. The device may still be on, just not seem like it. Then go into recovery again.
[ONE Original Android Development] aleksik:
It doesn't turn on whatever I try. I have hold the power button for 30,60 and even 120sec and nothing.. It won't even react to charger. If I connect it to my PC it shows 4 different drives: G:, H:, I: and J:. I can only access drive G: (63,9mb) which has 2 folders: image and verinfo. Other drives give some errors. Is there anything I can do? I would be very happy if someone can help me, because right now I'm out of ideas..:crying:
[ONE Original Android Development] ak:
step:

recovery

- hold power for 30 sec

- press vol down + power until you feel vibration and than leave everything

do you have a custom recovery?

otherwise:

fastboot

- hold power for 30 sec

- press vol up + power until you feel vibration and than leave everything

which was the level of charge?

did your phone unlocked?
[ONE Original Android Development] aleksik:
Tried both recovery and fastboot, but my phone doesn't turn on. It doesn't vibrate or anything. I had installed Philz recovery. When it turned off the battery level was about 50%. If you mean is my bootloader unlocked, yes it is. This is very frustrating! When I connect my phone to PC it is recognized as QHSUSB_BULK.
[ONE Original Android Development] Vortex1969:
Here is a link to a thread with the same state you are now in. If I find anything else I will send you a PM.

Hope it helps and good luck.

http://xdaforums.com/showthread.php?p=54560542
[ONE Original Android Development] ak:
http://xdaforums.com/oneplus-one/help/oneplus-one-qhsusb-bulk-t2806255

https://forums.oneplus.net/threads/rom-official-paranoid-android-for-the-one.43581/page-25

see this:

http://xdaforums.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696

you have to go into fastboot and then flash the right kernel or bootloader:

@DSwissK... what you need to flash is the aboot.img to the aboot partition (I'm not sure if it helps, just guessing), because this is the bootloader partition. Hopefully this gets your device running again...

fastboot oem device-info
[ONE Original Android Development] shaker2k:
Long time Franco user. Trying AK for the first time.

This thing likes to sleep! I have full location on high accuracy. Goggle now from any screen on. All syncs on.
[ONE Original Android Development] ak:
Ok no problem ...

I have personally tested synapse and I have flashed kernel without problems.

AK@A0001
[ONE Original Android Development] ludester:
Why must you switch back to stock kernel? I flashed straight from Franco to this one and haven't had any issues.
[ONE Original Android Development] chikimonke:
You don't HAVE to flash back, but if you run into problems, don't report them until you have tried flashing stock kernel then AK.

On a side note, why all the sudden concern, from multiple people, about flashing to the stock kernel? It takes almost no time at all to do, and can all be done in the same recovery session. Whenever I update anything (ROM, Gapps, kernel...) I wipe dalvik, cache and system. Then I flash the latest of everything, reboot, and I'm good to go. I very rarely run into any major issues. Use TWRP and you can select up to 10 things to flash all at once, makes it very easy. (This wasn't aimed at you [MENTION=704109]ludester[/MENTION], just happens to be in my reply to your post)
[ONE Original Android Development] Alin CG:
A request if possible ...can you add a option to lower vibration strength... Thx
[ONE Original Android Development] ak:
You can use trickster.

AK@A0001
[ONE Original Android Development] Rkr87:
Usually, I only asked as on the post for v072, ak stated a clean kernel flash was required (dirty flash rom then flash kernel).

Powered by Bacon
[ONE Original Android Development] Criton30:
so for v074 I should dirty flash my rom then flash the kernel? sorry but I dont understand that correctly...
[ONE Original Android Development] Rkr87:
No, that's the question I just asked ak, it's not required for this version.

Powered by Bacon
[ONE Original Android Development] Criton30:
there is something wrong with the v074....after flashing the new kernel , the stock trebuchet launcher closing everytime with fc...
[ONE Original Android Development] bissa:
which version work with AOSP based rom?
[ONE Original Android Development] jesterpaul:
Not the kernel. Works here.

Sent from my Sonic Open Kang
[ONE Original Android Development] Criton30:
back to 072 stock launcher working fine....
[ONE Original Android Development] dev0lver:
that is some problem with the rom, kernel has nothing to do with apps

but if it works on v72, maybe it's some interference between them

did you tried reflash of the rom and then v74 kernel, to see if the same happens ?
[ONE Original Android Development] Criton30:
I dont want to reflash the rom
[ONE Original Android Development] dev0lver:
make backup, dirty flash it, and check

with backup to restore, there is no problems to go back
[ONE Original Android Development] Criton30:
if I install the newest Temasek CM12 ROM, should I install UKM and Synapse too?
[ONE Original Android Development] Rkr87:
If you're dirty flashing the rom you don't need to reflash ukm or reinstall synapse. If you're clean flashing the rom you will need to.

Powered by Bacon
[ONE Original Android Development] kipue:
Hey AK, it is still not resolved as far as I could test (Tema 3.9+your 74)

No big deal though :) It's all dirty flashed so could be my problem
[ONE Original Android Development] singhz905:
How do I fetch the log for the random reboot i got?
[ONE Original Android Development] shure2:
Second that, got a cheeky reboob
[ONE Original Android Development] smint86:
Use synapse, tools tab. Saves logs to your storage, logs folder.

I got one random reboot using v0.74 with Temasek v3.8 so far.

Settings:

- min 2 cores online

- max 2 cores screen off

- sound profile loudness

- ksm activated

- rest stock

Phone did sleep whole night without problems, plugged into charger, powered on. Unplugged the charger in the morning, used the phone for about 20 minutes. Approximately 10 minutes after screen off, it rebooted.

https://www.dropbox.com/s/ybctrvp14ahogzm/last_kmsg-2015-01-02.11.11.10.txt?dl=0
[ONE Original Android Development] f100cleveland:
Ran v74 for over 12 hours without issue. Turned ambient display back on and first notification triggered a reboot. But I couldn't get that kmsg cuz it rebooted two times as I was trying to get the log. But here's the last one: http://pastebin.com/4369zYSY
[ONE Original Android Development] smint86:
Where do I find this ambient display setting? I don't think I have it activated but also can't find it in the settings. Maybe it's translated to german, idk.

Edit:

Nevermind. It's indeed translated into german, called “Inaktivitätsdisplay“ ;). And it was turned on, I'll turn it off until people say it's fixed.
[ONE Original Android Development] zaphodbeeb:
didnt work for me on ak074 and temasek 3.9 f2fs.:(
[ONE Original Android Development] flolep:
Yes. +1 on that one.

But, well, putting ambient display off for the time this issue is fixed is ok for me.

This issue is here since ak 068.

The three ak test versions were not rebooting with ambient display on but all the versions from ak 068 to last 074 are rebooting when a notification is received on the screen and if the phone is sleeping.
[ONE Original Android Development] Rockhound53:
Hi,

The reboot issue when ambient display is on is still there...

I have temasek 3.8 and the AK74 on my opo
[ONE Original Android Development] :
I don't think that is has something to do with ambient display. It was always disabled and my phone rebooted though. But it's true that reboots happen when notifications arrive.

I'm now on stock kernel for 1 1/2 days. No problems so far.
[ONE Original Android Development] thantos:
Agreed. I noticed the same thing when message notifications came in during screen off. Happened with Temesek CM12 and Euphoria-OS
[ONE Original Android Development] dustintinsley:
where is this ambient display setting?

---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------

disregard. appears this is a cm12 setting. i am stuck with cm11s due to my dependence on xposed framework.
[ONE Original Android Development] dayanandgp:
faced same issue with Liquid smoot CM12 ROM...thought i was alone but i guess many are facing similar reboots..
[ONE Original Android Development] zaphodbeeb:
plug your phone in and do adb logcat in terminal is the way I do it. There are also apps
[ONE Original Android Development] Alin CG:
I didn't have a single reboot so far ...AK 72 and now 74 + Temasek 3.8. Everything is smooth and fast :D. Thx AK
[ONE Original Android Development] Crazy-Silver:
How to clean all previous settings? (also from Boeffla kernel)
[ONE Original Android Development] jukiewalsh:
I know it used to be a problem for others but I never experienced it until now, is anyone else still having Wi-Fi disconnect during sleep. I wanted to confirm before doing clean flash again.
[ONE Original Android Development] M5devil:
I had constant reboots with ambient display on. Zero reboots since I turned it off. Go figure
[ONE Original Android Development] prstorero:
Has anyone successfully eliminated the music glitching on their device? I did some testing with the ROMs stock kernel and AK. Stock I couldn't stop it at all. After switching to AK again, I eliminated it for when the screen is on, but still always happens when the screen is off. Stock settings except changing min CPUs online to 2. I'm using euphoria ROM, music player is Spotify on normal quality. I found a section of a song that made a good test. I played through it 10 times with the screen off and on. When it was on, there was not a single glitch. When it was off, however, it happened every single time. I also tried raising the idle frequency, but that did nothing.
[ONE Original Android Development] kipue:
Indeed, I thought he meant that it was fixed, even with ambient display on.

No matter, as you say, we can turn it off (I did), and it's not a huge loss :)
[ONE Original Android Development] byAidan:
Have you tried AK recently? Music glitch has been fixed for me since 0.72/0.74 with all stock settings :D

I'm using this ROM if it helps:

http://xdaforums.com/oneplus-one/development/rom-bacon-lollinaro-t2948272

Let me know how it goes :)
[ONE Original Android Development] wayate:
Hi fellas.

I use ak kernel on last temasek cm12 rom. Its almost perfect except one thing.

In synapse, what does the message "scheckbox has failed" mean?

I get this when i try to tick in wake section, apply from init.d but it stays unticked when i reboot the apk.

Why can't i tick apply from init.d in synapse? And how can i fix it?

Thans for those who'll help.

Edit : fixed. I just followed the guide from apb_axel. Thanks anyway
[ONE Original Android Development] prstorero:
I guess you didn't read the whole post? I said I used AK a couple times haha [emoji14] and yes the latest version, but it still happens.