yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] bud77:
Wow, thanks for the explanation, I never understood it that way !

What is the limit (in ma) in your implementation ?

Trickster only offers a checkbox, without value like the screen you posted on your first tests (synapse if I recall ?)
[ONE Original Android Development] CamoGeko:
Well it looks like this thread is off to a flying start...

Just had to pop in and see things taking off again for you mate, on a different device. Hope you're enjoying it! :D
[ONE Original Android Development] xTremePower:
Tested with LiquidSmooth, work's perfectly !
[ONE Original Android Development] DespairFactor:
I think I have found my best performance/battery settings on the newest version, takes about an hour and a half of charge to drop 1% with approx 25-30 minutes screen on. This is insanity, I will post my settings in a bit for others to test.
[ONE Original Android Development] whoa718:
Hurry up
[ONE Original Android Development] apb_axel:
Oh yes, next version of UKM will have full control of intellithermal like fauxclock :D.
[ONE Original Android Development] ak:
@apb_axel

intelli thermal v2 have diff path, do you have checked my friend?

im ready for beta testing.
[ONE Original Android Development] Vortex1969:
Im having no problems running Mahdi with stable ak. Things are running smooth and fast for me..[emoji6]
[ONE Original Android Development] SleemLDJ:
I've just cleared data of synapse and rebooted phone.

Only thing I will change is governor to slim.
[ONE Original Android Development] 9600pro87:
What's Color Enhacement for JDI panel? How does it work?
[ONE Original Android Development] fards:
been having a look at the data drops tonight,

looks like LowPowerMode and timing might be responsible.

Can anyone try

persist.radio.no_wait_for_card=1

in build.prop and see if it makes any difference for them?

I've been having issues with "no connection" especially when resuming from lpm, and this seems to have fixed it, but other factors could be responsible for the increase in performance.
[ONE Original Android Development] alquimista:
Just wanted to say that this kernel is a must have for those on CM11s.

I ate my own hat and got a 1+1 from my mate. Tried all the other kernels out there and ak is the dogs bullocks on battery performance and tweakability.

Ta very much for all the great work.

Ta,

ALQI
[ONE Original Android Development] bud77:
The error is actually from nova launcher, not the rom ;)
[ONE Original Android Development] SleemLDJ:
Surprising how Nova Launcher can reboot the phone while I'm tearing rubber in real racing 3..lol.

I'll keep an eye out for it.

Although, since clearing synapse data, it hasn't forced reboot.
[ONE Original Android Development] osmosizzz:
Not sure if it's a placebo effect but 38 has better sound quality through headphones than 39. Much crisper. But I do get this thing when I turn the screen off that the audio sticks and it sounds somewhat like static.

Sent from my OnePlusOne
[ONE Original Android Development] digweed4me:
Insane battery life on the latest stable kernel
[ONE Original Android Development] elementalfusion:
Wow that's insane! Care to share your settings?
[ONE Original Android Development] Ferranza:
+1
[ONE Original Android Development] digweed4me:
No just a stock setting and in kernel faux and interactive governer with liquid smooth rom and art runtime
[ONE Original Android Development] LookedPath:
Just had another random reboot with latest stable version of this kernel and latest sabermodded slim.

During the reboot I was updating some apps with the Play Store.

Here is the last_kmsg.

Stock settings with -15mv of global undervolt and with F2FS filesystem.
[ONE Original Android Development] jgcaap:
Isn't art slower than dalvik on these version of Android? According to what I tested is not worth to change yet
[ONE Original Android Development] Tunasty:
It's that app's fault ;) lol

-Tunasty
[ONE Original Android Development] digweed4me:
No art runtime is faster than dalvic you can see that by running quadrant on dalvic and art ,art will get you 3000 more and it's good on battery too.
[ONE Original Android Development] MojoManagement:
Seems like apps got corrupted while running? Could be related to a kernel bug especially with using F2FS
[ONE Original Android Development] gulp79:
Just to report, i'm on F2FS (using CM11 nightly) and never had a reboot.

Currently undervolting -100.
[ONE Original Android Development] ak:
f2fs

:D

f2fs: update to latest version 3.4.y [20140903]

* 6f69935 f2fs: support 3.4 by Jaegeuk Kim - 1 year, 3 months ago linux-3.4
* 5b1cbad f2fs: need fsck.f2fs if the recovery was failed by Jaegeuk Kim - 7 days ago
* 60b1580 f2fs: handle bug cases by letting fsck.f2fs initiate by Jaegeuk Kim - 7 days ago
* 7cb5d0f f2fs: add BUG cases to initiate fsck.f2fs by Jaegeuk Kim - 7 days ago
* ba88ebd f2fs: need fsck.f2fs when f2fs_bug_on is triggered by Jaegeuk Kim - 7 days ago
* 3258dd6 f2fs: remain inconsistency information to initiate fsck.f2fs by Jaegeuk Kim - 7 days ago
* 4081363 f2fs: introduce F2FS_I_SB, F2FS_M_SB, and F2FS_P_SB by Jaegeuk Kim - 7 days ago
* b73e528 f2fs: reposition unlock_new_inode to prevent accessing invalid inode by Chao Yu - 11 days ago

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
# On branch ak-11.0-nightly
# Your branch is ahead of 'origin/ak-11.0-nightly' by 3 commits.
# (use "git push" to publish your local commits)
#
# Changes to be committed:
# modified: Documentation/filesystems/f2fs.txt
# modified: fs/f2fs/checkpoint.c
# modified: fs/f2fs/data.c
# modified: fs/f2fs/dir.c
# modified: fs/f2fs/f2fs.h
# modified: fs/f2fs/file.c
# modified: fs/f2fs/gc.c
# modified: fs/f2fs/inline.c
# modified: fs/f2fs/inode.c
# modified: fs/f2fs/namei.c
# modified: fs/f2fs/node.c
# modified: fs/f2fs/node.h
# modified: fs/f2fs/recovery.c
# modified: fs/f2fs/segment.c
# modified: fs/f2fs/segment.h
# modified: fs/f2fs/super.c
# modified: fs/f2fs/xattr.c
# modified: include/linux/f2fs_fs.h
[ONE Original Android Development] MojoManagement:
@ak

Could you setup and push experimental branch for pull requests, i will have some soon?
[ONE Original Android Development] ak:
ok no problem, i have reorganized makefile flags, if the kernel booting new branch will be online. :highfive:
[ONE Original Android Development] ak:
I have shared my invites but only one for now no one is used and two and i have 1 day left, I'm sorry for those I sent the link but can expect lost.

There is someone who needs it.
[ONE Original Android Development] ak:
ok done:

https://github.com/anarkia1976/AK-OnePone/commits/ak-11.0-nightly-experimental

kernel boot and it work like an Anguilla! :D
[ONE Original Android Development] gulp79:
Give us the capitone!
[ONE Original Android Development] MojoManagement:
Nice ! :good::laugh:

I think we need still some more flags, although this is very fine tuning :D
[ONE Original Android Development] MultiCulti:
hm ... no reboots with Miui since .35 ... stock values coming with kernel

good job [emoji106] [emoji106] [emoji106]
[ONE Original Android Development] ak:
test kernel see git for changelog (nightly branch)

View attachment ak.040_b02.opo.cm11.zip

Only CM11/AOSP roms.
[ONE Original Android Development] MultiCulti:
I'm your man to test cm11s version on Miui [emoji13] [emoji16]
[ONE Original Android Development] edgarf28:
+1

I'm also running (the official) MIUI, because it's by far the smoothest ROM I've tried on my OPO.
[ONE Original Android Development] samflorin:
I also had a random reboot. last_kmsg is @ https://www.dropbox.com/s/ocbkl6opmsdj1pi/kmsg.log?dl=0 . Was opening Facebook when it happened.

Rom: CM Nightly from 08.Sep.2014

Kernel: Ak 039

UKM installed but not active, no changes done to the kernel (uninstalled Synapse).

---------- Post added at 02:47 PM ---------- Previous post was at 02:24 PM ----------

Does not boot on latest CM Nightly. Phone randomly rebooted at various boot steps (at some point i've reached "Android is upgrading" part after flashing the nightly). Rolled back to 39 which booted the phone successfully.
[ONE Original Android Development] Ferranza:
No reboots with cyanhacker ....

Inviato dal mio SM-P905 utilizzando Tapatalk
[ONE Original Android Development] MojoManagement:
Is working well :)
[ONE Original Android Development] samflorin:
kmsg with phone frozen once lockscreen appeared:

https://www.dropbox.com/s/6pwzxj7q34ifnij/kmsg-040b2.txt?dl=0

kmsg with phone hanging mid-boot:

https://www.dropbox.com/s/dx0bd2exgl0u6dc/last_kmsg.txt?dl=0
[ONE Original Android Development] ak:
This freeze are difficult to track ... Please post also ROM and configuration.

The Kernel don't have all nightly cm11 patches for retro compatibility reason.

Your log report

[ 78.717533] [00000000] *pgd=00000000 [ 78.718042] [ 78.718232] Pid: 2537, comm: BootAnimation [ 78.718430] CPU: 0 Tainted: G D (3.4

Boot animation???

Strange

Sent from my One A0001
[ONE Original Android Development] samflorin:
CM11 20140910-NIGHTLY

042 test kernel which hangs

039 kernel which boots successfully

No synapse/UKM installed but not used

I have also tested crDroid (my secondary ROM) which also freezes on lock screen (then screen goes black and phone reboots). Rom is from here: https://plus.google.com/communities...6/stream/258ea079-afa4-42de-8cb4-3dc466c1b60d (build 3)

What other information would be of use to troubleshoot this?
[ONE Original Android Development] jgcaap:
Second day with 0.38 for cm11s no reboots no SD and now with -50mv rock and solid
[ONE Original Android Development] ak:
Ok ... I have to verify with last madhi no problems.

Sent from my One A0001
[ONE Original Android Development] samflorin:
Updated my initial post with additional info. Besides, i don't think Mahdi has the latest CM changes (crDroid is also CM based and b3 should have commits from 2 - 3 days ago from CM nightly).

Any user using nightly can report his experiences please?
[ONE Original Android Development] dgjenkins:
Test kernel boots and is running just fine for me w/Mahdi 0903, which I believe is most recent unless I missed something. Only been a few minutes so hard to tell long term stability but so far so good!
[ONE Original Android Development] samflorin:
09.03 Mahdi with 042 kernel boots for me without issues. Just gave it a spin as secondary rom.
[ONE Original Android Development] gulp79:
I'm also on CM11 20140910-NIGHTLY with F2FS.

With v40, i've got a lot of reboot, returned to AK v39, all ok, then i've reistalled v40 and now is all ok :)
[ONE Original Android Development] samflorin:
I've tried the same. Sometimes it boots sometimes it does not. Not consistent at all.
[ONE Original Android Development] clock51:
Mahdi rom and AK 039 uv -50, 24 hours Perfect as smooth as oil
[ONE Original Android Development] skydayzer:
CyanHacker with AK version ak.038.opo.cm11 Smooth No UV just the stock settings and with normal usage switching between wifi and 3g/H+
[ONE Original Android Development] gulp79:
i've got another reboot:

http://pastebin.com/tX06Yp3q

on CM11 20140910-NIGHTLY
[ONE Original Android Development] inzaghi75:
Which govenor is the best one to set?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] anybuddy:
You're quite some time at xda so you should know, there is no best. Whats the best for me doesn't mean the best for you. Test it out. Every day another Governor so you can try what fits your needs ;)

--------------------------------------------------

Gesendet von meinem Schinken

ROM: | Sabermodded Slim | Kernel: | AK |

If I've helped you, please press the Thanks Button!
[ONE Original Android Development] SleemLDJ:
I'm still having horrible reboots while gaming. Can someone please take a look at my log files in this zip folder?

It has Logcat, Kmsg and dmesg.

https://db.tt/gWwnvLHN

Thank you.
[ONE Original Android Development] kkk12345:
ghost touch

Okay so I have not experienced any ghost touch before, both stock cm11s and PAC ROM (currently using) but now ghost touches suddenly comes out(I can see them because I always had the option "Show touches" in developer options on).

This happens once I tick the box smart2cover and apply in synapse with ak kernel. My touch inputs are still sensed but along with many other multiple touches occasionally. So I turned off that option and then my touch input can hardly be recognised, a reboot fixes this. I was able to reproduce this problem multiple times. Tested on ak kernel 038 and 039 with latest ukm
[ONE Original Android Development] jgcaap:
benchmarks do not say the truth. The ART on kitkat is a underdevelopement version. The real version comes on android L. Perhaps on this machine we not notice such diferences but on lower end devices, you'll see that starting an aplication takes more time, but the apps after beeing loaded are fast. But this is not for all apps...

Well what matters in the end is the good experience. :)
[ONE Original Android Development] samflorin:
+1
[ONE Original Android Development] venky716:
Hmmm, I beg to differ. ART is definitely faster even in it's beta stage.

I've run it on all my phones and can see the difference. Apps load faster, scrolling is more responsive etc.

And no it is not a placebo thing, there's a simple explanation, with ART apps are pre compiled with dalvik it gets compiled when you open the app (JIT) this causes a slight delay. There are plenty of articles and youtube videos with actual proof.

For me though I'm convinced ART is faster, right now I've all my ROMs on ART except one, CM11S, I can see the difference in performance when I switch (MULTIROM).
[ONE Original Android Development] jgcaap:
I believe in you. But the app start takes longer trust me. If you search around you'll find that.

The loading after the app is open its better, that's why you get better speed at most of everything. But not all apps are optimized. The art on Android L is diferent from Art of kit kat as it has matured.

In gs2 I tried to use art. Took alot of time to create each file in the start up or after each update, not as fast as creating each dex files of dalvik. When using had the pros of low memory use, after app open was faster the app processing power. But was slower to start an app, and not yet optimized for each app.

So what I thought was, wait and use dalvik till comes a mature os where devs develop mature apps for art. =)
[ONE Original Android Development] ak:
In summary:

users with reboot problems, have you cm11 nightly + f2fs?

Every reboot have:

[ 231.325767] wlan: [1948:E :HDD] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan

[ 260.416822] type=1400 audit(1410363480.942:23): avc: denied { read } for pid=6775 comm="ea.games.r3_row" path=2F6465762F6173686D656D2F64616C76696B2D4C696E656172416C6C6F63202864656C6574656429 dev="tmpfs" ino=10653 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:init_tmpfs:s0 tclass=file permissive=1

so the problem is related to "permissive=1"

something is changed from ramdisk/rom side.

People with problems have to report:

- rom

- kernel

- fs

- settings changed
[ONE Original Android Development] jgcaap:
Was almost going to do that today... Staying on stock for now. BTW isn't it better to swappiness be at 0%?
[ONE Original Android Development] TEW999:
[MENTION=3685904]ak[/MENTION] i seem to have come across and issue which may also be attributes to some people having random reboots/freezes. Basically the first core is capped to the maximum that the user sets but cores 1/2/3 run freely up to the maximum clock you have implemented of 2880000mhz. I have found this out by running your latest beta kernel and madhi. CPU stats were found out by checking show cpu info in developer options. Kernel settings are stock untouched
[ONE Original Android Development] ak:
this is very interesting, what governor do you use?
[ONE Original Android Development] TEW999:
At the time in was using interactive and noticed a spike upto 2880000mhz so I switched to performance to see and yep core 0 running at 2457400 and cores 1/2/3 running at 2880000mhz. Perhaps you could implement [MENTION=3332811]faux123[/MENTION] snake charmer for krait CPU's
[ONE Original Android Development] samflorin:
I think you misquoted me.
[ONE Original Android Development] ak:
I have to check but i never see spyke to max frequencies. is Something changed into stock MPD?
[ONE Original Android Development] TEW999:
I'm not sure my friend but I certainly didn't change any kernel settings other than the governor which in did to confirm this issue. I have also just ran antutu using interactive and monitored the cpu activity and the same again happened
[ONE Original Android Development] MojoManagement:
It really goes over max_frequency set
[ONE Original Android Development] TEW999:
At least I'm not going mad the eh? Haha. I'm sure this will be sorted soon :)
[ONE Original Android Development] ak:
with stock mpd?

from the begin? why users never reported?

what version of kernel?

can someone post cpu stats?
[ONE Original Android Development] TEW999:
Well ibhave only had my OPO a week and have been trying to find the best setup. I stumbled across this issue by accident in all honesty. But can reproduce flawlessly with every hotplugging option MPdecision, autoSMP and intelliplug. I'm running you're mates experimental kernel
[ONE Original Android Development] MojoManagement:
latest nightly I am using

mpd, intelliplug...
[ONE Original Android Development] ak:
so how i can reproduced?
[ONE Original Android Development] AcmE85:
Looks like an updated touch panel driver has been freshly merged!

http://review.cyanogenmod.org/#/c/72720/
[ONE Original Android Development] TEW999:
You need a cpu frequency monitoring app or if you're using madhi enable show cpu info in developer options and it will show you on an overly in the top right hand side of the screen.

---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------

Also just another I have taken showing my max cpu settings in synapse and the overlay showing the issue
[ONE Original Android Development] ak:
thanks a lot, now i have to find when begin and where is the problem.
[ONE Original Android Development] TEW999:
Glad I could help :) if I knew more about coding I would help also but unfortunately my knowledge is very limited. Good luck
[ONE Original Android Development] fards:
For those using dalvik have you tried enabling the multi thread optimisations in build.prop? Did it work? Is there any difference?
[ONE Original Android Development] Roymik:
AK kernel v40 experimental, keeps rebooting when opening heavy app like facebook for the first time(clean flash)

RoM : Temasek v135.1

Uv - 100, smartmax_EPS,autoSMP,Arch power.

Same settings with ak39 gives no reboot.

Here are 2 kmsg
[ONE Original Android Development] DerRomtester:
I think your uv is a bit high. But if it worked before i dont know what the error is. Kmsg shows no errrors detected. :confused:
[ONE Original Android Development] magnamentis:
not sure if this is helpful but the following config performs flawless:

runtime 2 days with up to 3 hours of uninterrupted heavy load, zero issues monitored with system monitor flying monitor.

want to add that i had huge trouble on 038 stable and had to use stock kernel for a day until 0.39+ came out

- CM11 20140908 nightly

- ak.039_b03.opo.cm11

- slim governor

- 422min 2572max frequency

- mpd, touch boost, hyst=0

- OV 5mv globally

- 2048 read ahead, row I/O

- tcp = cubic, fsync enabled, fast charge @ 2000mA

- VM Heap 768MB

- selinux set to permissive ( was set to enforcing agains my long term settings without me doing it ? ) changed it back to permissive now.
[ONE Original Android Development] mrsim:
may i ask when updating to a new stable version of AK kernel and UKM...do i just download and flash them or do i need to do any wipes before installing

OPO CM11s stock (XNPH33R) + AK.034 UKM v3.3.2
[ONE Original Android Development] omvir:
I'm on stock stable 39 and I don't have spikes to 2.8. Using mpd.
[ONE Original Android Development] chikimonke:
Flash and go, no need to wipe anything for a Kernel update.
[ONE Original Android Development] TEW999:
[MENTION=4021619]omvir[/MENTION] do me a favour and set your governor to performance and check cores 1/2/3 if they stay at the max freq that you said as opposed to to full throttle then it might help [MENTION=3685904]ak[/MENTION] track down the issue quicker
[ONE Original Android Development] RobbieL811:
Can't wait to try this! God I hope it fixes my touch issues!

Sent from my 1+1
[ONE Original Android Development] ak:
So I have tested problem become after v40,.... v39 is OK.
[ONE Original Android Development] Vortex1969:
+1 testes v39 as well and it was good.
[ONE Original Android Development] mrsim:
thanks mate
[ONE Original Android Development] TEW999:
Awesome. Quick and efficient in finding and tracking a problem. This is what beta testing is all about. Hope [MENTION=3685904]ak[/MENTION] can get the issue sorted easily and without hiccups
[ONE Original Android Development] edgarf28:
[MENTION=3685904]ak[/MENTION] any change we can get an updated CM11S kernel with the TouchPanel firmware from today maybe? :o
[ONE Original Android Development] Kingzak34:
[MENTION=3685904]ak[/MENTION] , I must say that I dont have any issue since I use your kernel, just perfect. And with UKM, it's even better. No reboot, no freez. And smoothness and battery life, THAAAANKS !

( Multirom with MIUI Official FR, CM11S and Some test ROMs, all with your kernel )
[ONE Original Android Development] ak:
Cm11s shipping branch dont have for now the update ... You have to wait ... I have see its Only for cm11.
[ONE Original Android Development] pantmunu:
When u say host =0 is that in intelliplug.. I'm kinda stealing your setting.. Hehe :cowboy:
[ONE Original Android Development] LookedPath:
From what I understood, the ones that are experiencing reboots have undervolted their CPUs, since the CPU reaches higher frequency in the latest kernel the undervolt makes it unstable causing reboots.

I kind of tested my theory by removing my 15 mV undervolt using sabermodded and latest AK's kernel v40 and the reboots that I previously had are gone.

I'm also using F2FS.
[ONE Original Android Development] TEW999:
I am inclined to agree with you [MENTION=4319459]LookedPath[/MENTION]. However people with a low PVS binned cpu might find it unstable at those speeds with stock voltage or may not even boot at all. All CPU's being different etc...etc...
[ONE Original Android Development] magnamentis:
already was going to apologize for the typo HYST not HOST but then i saw that typo was not mine :) :)

on topic. the settings there are a bit mixed up. albeit intelliplug should not be used with mpd, the touch boost can

indeed be used, albeit it's under intelliplug. in my opinion this should be more ordered under general hotplug settings like touch boost and

specific hotplug settings like intelliplug and underneath that title only settings which belong ONLY to intelliplug.

in short, if i did not get it totally wrong, the hysteresis value belongs to touch boost, thus not to intelliplug "only" might be an error since

i'm not that privy with all hotplug variations. however this setting is in my opinion giving quite a boost to touch screen responsiveness by

reducing the latency in general which as a sideffect seems to reduce touch latency in its wake.

it's very difficult to make final conclusions because albeit i have my touch responsiveness under good control, sometimes it still lags

without having changed something and a reboot brings back the better experience. however things ARE getting better each week let's say because i got my grounding issue solved ( motorbike plastic cradle ) was an issue and it's gone. and the annoyance got much more bearable and these settings help in the process.
[ONE Original Android Development] pantmunu:
Yeah. Sorry. Damn auto correct and yes.. I figured it out while I was playing. Touch responsiveness seems to be better now.. I'm gonna play with it for a while.. And tweak some more in your setting.

Thanks for the response..