yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] DespairFactor:
Oh, it's a feature in the new version. Nonetheless, [MENTION=3685904]ak[/MENTION] , can you please expose all settings in trickster? Synapse doesn't like me for some reason, it won't show any CPU info at all on my end.
[ONE Original Android Development] bud77:
I installed the 20b4 version this morning, and I'm really impressed by battery life

I used to drain 5% per hour for

my

daily use (with mahdi rom stock kernel), it went down to 3% per hour

And now I modified the values given by [MENTION=5169465]RIPng[/MENTION] (http://xdaforums.com/showpost.php?p=54608507&postcount=248) I hope to get even better results :D
[ONE Original Android Development] DespairFactor:
I hope it works well for you!
[ONE Original Android Development] Fruktsallad:
With these small changes to conservative, I find my phone to be far more fluent than with ondemand/interactive and even slim. Battery life is still great. YMMV.
[ONE Original Android Development] MojoManagement:
We should completely deCAF everything :rolleyes:
[ONE Original Android Development] jpswer:
Ignore me it looks like slim is up to date with the CyanogenMod repo...
[ONE Original Android Development] mca1490:
Im not able to install this I dunno why ¬¬ .. Im Running [OnePlus]MIUI V5 (KitKat) Build By Patchrom .. I flashed the stock kernel and then the CM 11 and Im stuck at the boot logo ..

What Im I doing wrong?

Just in case does anyone can provide me the stock kernel to see If im wrong?

thanks in advice!
[ONE Original Android Development] ak:
For patch ROM you have to sue cm11s ... You can read the first post for all q&a.

ak@a0001
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] you should update the UKM zip from your website to 3.4.2, as flashing that newer one fixed my audio problem. ;)

Send from my bacon.
[ONE Original Android Development] ak:
OK will be.

ak@a0001
[ONE Original Android Development] ralpheboyo:
New to the neighbourhood... Sup guys... Have the strangest issue... TWRP 2.7.1.1...custom slim build 7.9...install aosp kernel... And keep getting boot loop...
[ONE Original Android Development] mca1490:
Hmmm

Same thing I flashed first the rom

then this : CM11S Stock Boot/Kernel (XNPH25R) : Flash-able Zip -- flash_stock_oneplusone_cm11S_XNPH25R_boot.zip

then this: cm11s/stock: ak.039.opo.cm11s

then the last last UKM

Same boot loop
[ONE Original Android Development] Setting.Out:
Reflash your ROM, no need to wipe, then AK..
[ONE Original Android Development] mca1490:
Didn't work :rolleyes:
[ONE Original Android Development] jlevy73:
Which recovery are you using? If using TWRP use 2.7.1.1 not 2.8.
[ONE Original Android Development] mca1490:
Ok , I was using 2.8 , let me try again
[ONE Original Android Development] ak:
You can't flash v039 (only for >30) over 25R, you have to use old kernel version.
[ONE Original Android Development] ak:
Op update and uploaded new UKM 3.4.2.

[ TESTED WITH ROMs ]

Cm11 and Derivated ROMs

(flash cm11 kernel version)

pa

slim

slimdarkness

madhi

crdroid

pac rom

vanir

gummy Rom

mokee

liquidSmooth

slimsaber

miui - unofficial patchrom

cm11 Milestone

cm11 Nightly

aosb

Cm11s and Derivated ROMs

(flash cm11s kernel version):

cm11s - Rom Version > 30O

miui - Official Release
[ONE Original Android Development] galaxy s4 nutjob:
Thanks that worked
[ONE Original Android Development] kecinzer:
[MENTION=3685904]ak[/MENTION]

I tried compile nightly branch with partial display commit and its normaly working on AOKP.

Please consider to include it also.
[ONE Original Android Development] mca1490:
ok ,just installed ak.033.opo.cm11.zip and worked!

Music , camera and dt2w works , but is there any way to add the flashlight gesture to MIUI?

Thanks for your help ! :victory::victory::victory:
[ONE Original Android Development] ak:
Yes ... im testing int this moment with cm11 nightly and @RobbieL811 with slimsaber and seems all ok.

Im working also on intelli thermal for fix max/min freqs.
[ONE Original Android Development] ak:
You can try to enable it with synapse and see if working, but you have to have all necessary for launch torch.
[ONE Original Android Development] kecinzer:
Thats great news. I can't wait :).

BTW. You can also look at my linux upstream patch, may be you can find what causes not-booting-up :).
[ONE Original Android Development] Glatzi:
But use the link for 3.4.3 it got updated again ;)
[ONE Original Android Development] Glatzi:
Slightly offtopic but perhaps interesting for all users of the chinese OPO version:

Remove baseband restrictions
[ONE Original Android Development] Cris7ianO:
Hey you finally decided to get the one? Awesome you wont regret it :)

I think there have been issues with this version of twrp which lead to bootloop. You should try a prior version that should solve the problem I guess.

Sent from my 1+1
[ONE Original Android Development] LookedPath:
The issues were related to TWRP 2.8 so the bootloop shouldn't be caused by the recovery.
[ONE Original Android Development] NickosD:
For mahdi ROM I guess the aosp one,right?
[ONE Original Android Development] gordon.shameway:
Yes
[ONE Original Android Development] NickosD:
I downloaded the cm11 and it got in bootloop. Had to reflash rom
[ONE Original Android Development] thoiloidainhan:
Does the screen look yellowish to you guys at maximum brightness???
[ONE Original Android Development] Heisenberg:
Nope.

Transmitted via Bacon
[ONE Original Android Development] MojoManagement:
Stock kernel before flashing AK?
[ONE Original Android Development] ak:
What rom?

probably you have enabled sun read, cab or color enhancement.
[ONE Original Android Development] thoiloidainhan:
Liquid smooth and yes I have sunlight enhancement on. Thanks for the replies ak and timmaaa
[ONE Original Android Development] ak:
De nada.
[ONE Original Android Development] kecinzer:
I'm running self compiled b06 and so far so good ☺

I also have custom twrp 2.8.0.0 with f2fs support and have zero issues with it.

Odesláno z mého One pomocí Tapatalk
[ONE Original Android Development] jgcaap:
i must say AK that your kernel for now is the best as is the most features available, so i thank you for helping all users for free, but i hope to help you soon with a small donation.

I've been doing lots of tests now with version 0.39 and i am going to express my opinions about the CPU

These test were made by changing the following values.

On hot-plug i disabled:

CPU boost

Sync Threshold

Input Boot frequency

I made this in order to make the CPU usage only on the levels i want to test.

According to the tests i made, i found the minimum for the Chip version PVS 7 the following voltage:

268 Mhz - 630 mv

300 Mhz - 635 mv

400 Mhz - 635 mv

652 Mhz - 650 mv

729 Mhz - 680 mv

883 Mhz - 695 mv

960 Mhz - 705 mv

1036 Mhz - 740 mv

1190 Mhz - 750 mv

1267 Mhz - 770 mv

1497 Mhz - 875 mv

1574 Mhz - 885 mv

1728 Mhz - 910 mv

1958 Mhz - 955 mv

2265 Mhz - 1015 mv

2342 Mhz - 1030 mv

2419 Mhz - 1045 mv

2457 Mhz - 1050 mv

You'll notice that starting from 1.497 Mhz the voltage is exactly the same. why? According to my tests, snapdragon values are already at a minimum voltage, if i change to lower settings, it'll boot loop after a time. I took around 20 minutes on tests putting the device on extreme levels of stress cpu work, in order to see if would fail/bootloop/freeze.

The most interesting part is the capacity to lower voltage on lower Mhz, which i think we can explore here with other types of profiles. But with this values, everything is stable and no boot loops.

All tests were made on version 0.38 and 0.39.

In my opinion, is not necessary to change all these values, as hardware gets older, we'll have to input higher voltages with time, but we can extend life of things by lowering heat right?

Now the new test i am making is the best user configuration profiling for best battery saving+performance, best saving+balanced performance and going to share with you guys soon.

I hope that with this i am able to contribute with a good level of experience of usage of our phones.

In other to explain my philosophy of what i expect of my device. Is to keep my life simple. How?

1)Speed.

2)Good finalization

3)Keep the Rom clean from bad apps to "control" CPU+memory+etc (may i call this garbage?) and things simple, just configure what is necessary only once.

After Cpu configuration and testing, next stop will be memory. :)

See you soon everyone.
[ONE Original Android Development] chachin:
dude wtf I have pvs 7 and i tried to set the cpu bolt to 630 like yours and it rebooted.. It was going down to like -125mV lol
[ONE Original Android Development] jgcaap:
Wich is the rom and kernel version you are using?

well for me is pretty rock stable but try give a juice of more 10 mv to see if becomes more stable. i can go as low as 620mv, usualy give more 10 mv above minimum, same as i did with GS2.

But as i stated... is not worth to undervolt on these type of chips as they are pretty under volted already. We can try under volt the best possible but is not worth the time.
[ONE Original Android Development] ak:
thanks a lot my friend

your dedication is my best reward.
[ONE Original Android Development] chachin:
thanks for the info dude i'll go to maybe 640 and see if that works.. and if it does ill try 635 and if it dont reboot I'll leave it there :) will re-edit and tell you if it works on either mv :)
[ONE Original Android Development] jgcaap:
Guys need your help. Try configure the following configurations on memory

In GS2 i had some issues wich let me to learn alot about the memory configurations, and lost many ours of testing, i've seen how the kernel is configure, and wich i agree are good values. But each machine has its settings, since it changes with time, once there are more upgrades such as more memory and a faster processor, in orther to find those values we have to test and search better configurations for memory. I'm relearning how to set and test best configuration, but i remember that on GS2 there were some basic settings that helped me have a much faster phone. And since we got large Ram on our phones we should start to make use of it.

Small introduction:

dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)

This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.

According to the XDA article made by: Hero should be higher (vm.dirty_ratio=90;

vm.dirty_background_ratio=80)

Swapiness to 0 %

Control the tendency of the kernel to move processes out of physical memory and onto swap disk. We have SSD and this will worn out our SSD in my opinion, turing to 0 would be a good idea.

VFS cache pressure to 10%

Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.

(quoted from : http://xdaforums.com/showthread.php?t=1621808)

Whats your thoughts?

I am goind to test same configuration as Hero had to see how it'll workout. If you guys have better, please share :)

---------- Post added at 03:59 PM ---------- Previous post was at 03:52 PM ----------

1036 Mhz - 740 mv

1190 Mhz - 735 mv <---

1267 Mhz - 770 mv

increase here:

was my mistake i have set on 750 mv, perhaps thats what rebooting you :p

Great article on memory : http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.memory.html
[ONE Original Android Development] magnamentis:
this is what i think

i think this is one of the most interesting posts i've seen recently. could mean quite a leap forward in optimizing. interesting is that i, albeit it is indeed a good indicator for the kernel dev [MENTION=3685904]ak[/MENTION] to see what's possible with his kernel, i do not value undervolting very high. i'm even overvolting honestly speaking, even with my PSV8, but however this really got my attention and i will immediately go and spend some time right a way to play with the ideas to see what might be the benefits. thanks a lot for thia really fresh input.
[ONE Original Android Development] NickosD:
Yes. I have the phone for 2 hours. Should I see something important before flashing?
[ONE Original Android Development] magnamentis:
yes

check which version of OS is pre-installed because you cannot flash recent kernel version over .....25 rom version. of course you have to choose cm11s kernel version if you did not change the rom yet. if you flashed another rom ( recent version ) the above is obsolete, just don't forget to dowload UKM, UKM uninstaller in case something goes wrong, make a nandroid and i recommend synapse as kernel tweaking app for this device

EDIT: should you wish to switch to CM11 nightlies ( which i strongly recommend ) ( my opinion ) just wait for the next kernel update, because there are important commits reducing one of the only bugs of the device which can be ( not for everyone ) poor touch screen response ( slight lag etc. ) i currently use the cm11 kernel from this morning to check on the difference and indeed i'm desperately waiting for the next AK update because the touch response issue for the first time is 99% gone even on stock cm11 kernel for me. so what i'm saying is that these commits really make a difference concerning the touch response matter.
[ONE Original Android Development] NickosD:
So flash cm11 for mahdi and then ukm?
[ONE Original Android Development] jgcaap:
thanks!

i'm learning java, and one of my goals is to do a app to eliminate lags by using only the "necessary", basicly this app will require root needs and it'll set a balance between each app. I know there isnt a formula, but at least it'll be a hobbie for fun. The iphone Ios system has something wich really got my attention, wich was, everything is optimize by everydetail . A person when buys an iphone is not paying the processor or camara, it's paying for the high R&D they invest in to get everything in a simple and high level of thought.

HTC when makes roms, they try to optimize that way, according to my "user experience". I bold statement since i never actualy seen the settings, so i presume is optimized at that level.

For instance the Xperia line is also optimized that way, with someone using a brain, such as. the CPU has this capacity X, how much will it need to run app A, B or C.

On android, we can at least make our lifes better by finding the best setting for our device and kernel.

I trust AK since he is a dev wich is well known on the maket, and made till today great kernels, so his comments for me are the most valued. But anyone here that has a thought on these ideas please share, we can find something greater for everyone experience.

Thanks
[ONE Original Android Development] magnamentis:
hope you will succeed

the kernel tweaks which you have in mind are for a long time bothering me in the way that i feel that there is most probably a potential in them but since i have my set limits how far to go for it myself. so i shall keep in mind that someone is working on an app to optimize these settings, without that each one of us has to spend weeks to find out each detail with it's up- and down sides. i mean the more we tweak, the harder it gets to find the culprit should something start to misbehave and after all i have my devices to work with and not to kill the max. time :) thanks for your efforts and i will watch progress closely :) if you have things to test ( settings ) just pm me as long as it's not too many at one time. enjoy further

---------- Post added at 05:33 PM ---------- Previous post was at 05:29 PM ----------

UKM is only needed should you intent to use the synapse app ( strongly recommended )

UKM means "universal kernel manager" and is an integrated part of synapse to expose kernel features to the app ( i hope i got that right in terms )
[ONE Original Android Development] NickosD:
Well with mahdi rom I am still getting boot loops. I'll try later with another kernel. Tried not 11 and 11s
[ONE Original Android Development] NinjaPlease:
No issues with AK 040_b05 on the latest Mahdi rom for me. Working like a charm!
[ONE Original Android Development] gordon.shameway:
+1

Great work [MENTION=3685904]ak[/MENTION] !
[ONE Original Android Development] ak:
+1 with madhi, +1 with cm11 nightly last.
[ONE Original Android Development] jl2222:
What does eps stand for in the governors? Eg smartmax_eps
[ONE Original Android Development] MojoManagement:
extreme power saving
[ONE Original Android Development] ak:
Deleted

ak@a0001
[ONE Original Android Development] chikimonke:
Extreme Power Savings I believe

Edit: Double Ninja'd
[ONE Original Android Development] 9600pro87:
7 hours (i have 16% of battery left) of SOT with Mahdi rom 20140903 plus ak kernel v.040 b05

I use:

- interactive governor 300-2457mhz

- ROW 512kb sheduler

- intelliplug + touch boost balanced 4

- Stock kernel voltages

- msm-adreno-tz 200-578mhz for GPU

- Fsync and archpower enabled

WIFI always on except at night. 3 hours of call, browsing with Chrome, watching youtube and dailymotion videos, music, whatsapp.

Very big thanks for the great work!
[ONE Original Android Development] NickosD:
What's steps did you exactly followed to install at mahdi? I just flash and wipe cache and dalvik.
[ONE Original Android Development] ak:
What was your previous kernel ?

ak@a0001
[ONE Original Android Development] NickosD:
It's the stock one.
[ONE Original Android Development] gordon.shameway:
do a full wipe (wipe everything except internal storage), then install mahdi + gapps, then install ak for cm11 (not cm11s!!) and ukm, thats it.
[ONE Original Android Development] NickosD:
Any way without having to wipe? Just set up the whole thing....
[ONE Original Android Development] gordon.shameway:
Well, its kinda strange that it doesn´t work for you following the steps in op. I know, its PITA to set up everything again. Perhaps Full Wipe is the only solution.

Did you update TWRP to 2.8 ? If so, downgrad to 2.7 , as some users reported bootloops using newest TWRP

Perhaps try to :

- Dirty flash mahdi, so that the stock kernel is installed

- Wipe cache and dalvik

-Flash ak for cm11

- Flash UKM

- Wipe cache and dalvik

- REboot
[ONE Original Android Development] magnamentis:
depends :)

do you have the new rom up and running already or did you try to flash directly with kernel upon first flash of the new rom ?

i ask because you cannot flash new roms over stock cm11s without a total wipe and that would include data & sdcard0 to be save.

the answer to your question depends on the answer to my question. if the rom has already been up and running it will most probably be

a big aha... experience :) because without using wrong kernel ( by error download for example ) or any other accidental bad move on the user side

mahdi and this kernel do work together like a charm. perhaps you let us know the recovery you're using as well, because sometimes for reasons i was

never able to figure entirely in some cases there can something go wrong on that side. once i lost my imei and after repeating the process after flashing stock

image it worked. same procedure, different outcome :) that was the nexus 5 on november 6th 2013 when everything was quite in kids sandals :)

if you tried to install rom and kernel without the cleanest possible wipe ( i user format to be on the save side ) the culprit may lay in there.
[ONE Original Android Development] NickosD:
When I installed twrp, I did factory reset... Then flashed rom.
[ONE Original Android Development] magnamentis:
thin ice

yeah, often it's about terms. for example factory reset is not the same under all circumstance. without going into detail and start

a big discussion, just format instead of wipe and format data, system, sdcard and go from there. problem is, we all know it works but

we don't know why it does not for you at the moment. so take it as that we try to help, albeit you probably already know most of the steps :)

albeit a wipe will do in 99% of all cases, considering that you tried a lot already and did not achieve your goal as per now,

i would not be to minismalistic in choosing my means and choose the sledge hammer :) in this case that means formatting the partitions involved
[ONE Original Android Development] gordon.shameway:
So, which version of TWRP?

Edit: it really sounds like recovery is causing the problem.
[ONE Original Android Development] DJMartini:
I'm on AOKP with v40_b05 without any problems .... Good stuff!

I do have a question for best battery life. Would smartmax_eps be better than interactive_pro?

And for hotplug are people finding Intelliplug better than AutoSMP?

Just curious. Thanks!
[ONE Original Android Development] johnthepig:
Flashing either ak.039.opo.cm11s.zip or ak.040_b05.opo.cm11s.zip sends the phone into a boot loop, when using Paranoid Android 4.6-BETA1. Flashing just Paranoid Android alone works fine, but if I flash this kernel afterwards, the phone gets stuck in a boot loop.

I've flashed the kernel and UKM, in that order.
[ONE Original Android Development] gordon.shameway:
flash the kernel for CM11, not CM11s, and all should be fine
[ONE Original Android Development] johnthepig:
Nope. Still boot loop. I'm using TWRP 2.8.0, is that version stable?
[ONE Original Android Development] gordon.shameway:
TWRP 2.8 is causing problems at the moment, downgrade to 2.7
[ONE Original Android Development] NickosD:
Damn. The only thing I forgot to mention...

Downloading and I'll come to report back.
[ONE Original Android Development] johnthepig:
Downgrading to TWRP 2.7.1.1 fixed the problem, thank you!
[ONE Original Android Development] oriveradel:
Twrp 2.8.0 does NOT work if your device is encrypted
[ONE Original Android Development] chikimonke:
TWRP 2.8.0.1 just dropped. Not sure what the changelog is though.
[ONE Original Android Development] oriveradel:
Nice
[ONE Original Android Development] NickosD:
Flashed 2.7 something and booted. Thanks.
[ONE Original Android Development] gordon.shameway:
Is it encrypted by default? Can't imagine....
[ONE Original Android Development] funCrash93:
f2fs Support add promised.?

or TWRP Team was too busy.? :)

Send from my bacon.
[ONE Original Android Development] chikimonke:
Seems it was nothing of what we were hoping for...http://teamw.in/project/twrp2
[ONE Original Android Development] gordon.shameway:
[MENTION=3685904]ak[/MENTION] : perhaps you should mention in the OP to use TWRP 2.7 at the moment?
[ONE Original Android Development] funCrash93:
2.8.0.1 doesn't work as well?

Send from my bacon.
[ONE Original Android Development] chikimonke:
So I flashed it, and another issue I was having was with SuperSU installation. If I flashed SuperSU, it would complain that the binaries needing updating. If I told it to install with TWRP option, it still did the same thing. Using the "Normal" option worked. I just tried the latest SuperSU 2.08beta and it installed fine this time. Also, [MENTION=264345]ralpheboyo[/MENTION] just told me that he flashed the ak kernel no problem on 2.8.0.1 and no more bootloops. Go get 2.8.0.1, it seems to fix more than the changelog stated. http://techerrata.com/browse/twrp2/bacon
[ONE Original Android Development] gordon.shameway:
New changelog just says:

"Fix a bug that caused weird graphics and touch issues"