yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] vomer:
LMAO shhhhh :silly: :cyclops: xda is more important
[ONE Original Android Development] badluckclinton:
Could I get a link to those N5 settings, please and thanks? :laugh:
[ONE Original Android Development] zephiK:
http://pastebin.com/AeYXQZeR do note that the gpu settings aren't present. adjust them in FKU.

Also I would not undervolt down to 650... it might work and might not, it varies on your phone.

Thats what I like to hear :p
[ONE Original Android Development] Spl4tt:
What's that nice skin you have there?^^
[ONE Original Android Development] zephiK:
http://xdaforums.com/android/themes/theme-l-ready-t2802979 my favorite Android L theme, free as well.

My favorite feature of this theme is the themed gapps.
[ONE Original Android Development] Saythis:
Just to add... here is the N5 flashable variant modified for OPO.
[ONE Original Android Development] vomer:
thanks for posting this - but guys treat this as a test/initial version as it was originally designed for the N5.

I will be putting the OPO through it's paces to see what we can get once I have the device :good:
[ONE Original Android Development] jarjar124:
Can't wait.
[ONE Original Android Development] vomer:
:D :good:

I have some exciting new plans for VomerTweaks! Stay tuned :)
[ONE Original Android Development] badluckclinton:
So... just flash this over the stock 11S combined with Franco?
[ONE Original Android Development] zephiK:
Just so you know there are several lines in that script that has options that are available on the N5 but not on the OPO.

Plus the voltages are the N5 voltages, not OPO (its commented out so this line shouldn't matter but should be adjusted incase someone was to use them)

Edit: I don't mean to disrespect but I wouldn't be flashing that file, theres a couple invalid paths as they were valid paths on the N5 but not the OPO.
[ONE Original Android Development] Saythis:
I changed most of the options to correspond to the N5. The only ones that correspond are the GPU clock, color balance and vibration.

#!/system/bin/sh

sleep 25

# vomer_tweaks

# CPU

echo 1267000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# Voltage

# echo "700 700 795 805 825 835 845 865 875 910 925 955 995 1050 1065 1080 1095 1125 1150 1175" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

# GPU
echo 330000000 > /sys/devices/fdb00000.qcom,kgsl-3d0/kgsl/kgsl-3d0/max_gpuclk
echo 25 > /sys/module/msm_kgsl_core/parameters/up_threshold
echo 15 > /sys/module/msm_kgsl_core/parameters/down_threshold

# Governor

echo 120000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo 250000 > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
echo 95 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 1190000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 729000 > /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq
echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 960000 > /sys/devices/system/cpu/cpufreq/interactive/sync_freq
echo 90 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

# Hotplug

echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/load_threshold

There is the extent of what applies to the OPO.

Here is what doesn't apply:

# Vibration

echo 75 > /sys/class/timed_output/vibrator/amp

# Color Control - VomerBalanced

# Red Positive = /sys/module/dsi_panel/kgamma_rp
echo "0 12 19 30 39 48 56 72 83 105 118 126 121 114 109 102 93 73 63 54 40 33 20" > /sys/module/dsi_panel/kgamma_rp
# Red Negative = /sys/module/dsi_panel/kgamma_rn
echo "0 12 19 30 39 48 56 72 83 105 118 130 121 115 114 102 82 76 63 54 40 33 20" > /sys/module/dsi_panel/kgamma_rn
# Green Positive = /sys/module/dsi_panel/kgamma_gp
echo "0 12 19 30 39 54 61 78 84 107 123 132 117 110 108 97 90 71 61 52 45 37 21" > /sys/module/dsi_panel/kgamma_gp
# Green Negative = /sys/module/dsi_panel/kgamma_gn
echo "0 12 19 30 39 54 61 78 84 107 121 130 119 112 107 99 76 72 57 50 45 37 21" > /sys/module/dsi_panel/kgamma_gn
# Blue Positive = /sys/module/dsi_panel/kgamma_bp
echo "0 12 19 30 39 48 56 72 83 105 121 126 119 112 107 99 91 71 63 53 44 36 22" > /sys/module/dsi_panel/kgamma_bp
# Blue Negative = /sys/module/dsi_panel/kgamma_bn
echo "0 12 19 30 39 48 56 72 83 105 121 134 119 113 110 98 78 72 59 50 44 36 22" > /sys/module/dsi_panel/kgamma_bn
# White Point = /sys/module/dsi_panel/kgamma_w
echo "32" > /sys/module/dsi_panel/kgamma_w
[ONE Original Android Development] zephiK:
For

echo 729000 > /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq

Thats a invalid path, you can view it with root explorer. The file does not exist. In the OPO, it is listed under CPU-boost not Governor controls. So in order for that value to be assigned in the script, its in a new location.

For hispeed_freq, the frequency for 1.2GHz is 1190400; whereas, the N5 is 1190000 (for consistency purposes). I use FKU and 1190MHz assigns to 1190400.
[ONE Original Android Development] Saythis:
Ah, you are right. My bad haha. Those would appear to be the only one though?
[ONE Original Android Development] newellj79:
Sorry if I missed it but 14 is compatible with the 33 ota right?
[ONE Original Android Development] venky716:
Yes.

Also saw the interview, now I finally have a personality behind all this awesomeness [emoji16]

1+1=Awesome
[ONE Original Android Development] zephiK:
Yup, and so is r13.

Umm, I don't remember exactly. I already found the path for cpu boost. I'm going to go flash it up and make sure everything checks in.

I know for sure:

GPU. Cpu boost. Cpu freq for that one particular setting... I'll have one up and running, its the same config I ran before. I just never converted the script over :p
[ONE Original Android Development] Saythis:
Well cool :D thanks man. I didn't mean to offend anyone or anything with that. Was mostly trying to push that script because it is really nice.
[ONE Original Android Development] zephiK:
Hehe I understand, sorry if I came off strong. You didn't offend anyone, did that zip actually flash? I noticed in the script that it checks your build prop if it contains "bacon"... a lot of the newer OTAs contain "A0001" as the product name and not "bacon"

I'm cleaning up the script and whatnot and then I'll upload it, after that I'll need feedback on how to improve or any lag they may be encountering. I may start off with 1.2GHz at the base since 1.2GHz flies on my phone as it is.

Will probably add a Per-App-Mode afterwards for those apps that need the higher frequency to prevent the phone from lagging.
[ONE Original Android Development] Saythis:
It flashes, It's based it off the stock CM11S build.prop. According to the logs it seems to ignore the incorrectly specified entries.

Edit:

I'll gladly help you test it and 1.2GHz sounds like an awesome baseline since it flies on my phone as well.
[ONE Original Android Development] zephiK:
Yup because they don't exist. Try the ones I just set up, you'll have to delete the two files added so it can override (see bottom of post).

-----------

Alright here is the modified script from [MENTION=1363323]vomer[/MENTION] that was used on the Nexus 5. I've posted this in the past and was able to achieve quite nice battery life and it was my preferred set up right after Franco's default settings out of the box for his kernel.

The settings are more or less the ones from http://xdaforums.com/oneplus-one/or...-kernel-r1-t2800871/post54291066#post54291066 which can be manually inserted into FKU if you own the app.

Since that post was made awhile ago, additional changes were also made.

Some of the changes I made include:

- Increased the vibration to the maximum value possible on the OnePlus One.

- Disabled FSync System Call

Since its always asked, what is the battery life?!

Results: http://i.imgur.com/xbV5bkd.png

http://i.imgur.com/RccfKni.png

Note: Just because I was able to get this battery life doesn't mean you can either. It depends on what you do with your phone in terms of daily usage and your cellular signal.

Voltages are left stock because not all chips are made equally. Just because I can UV to a certain amount doesn't mean that you can too. Tinker around with what UV best fits you, or just leave it stock. The choice is yours ultimately.

This is just the beginning and they were settings from the Nexus 5 which is powered by a Snapdragon 800 processor. Additional settings will be tweaked around with and I'm sure we can achieve better results than the ones I've achieved from the time of that screenshot.

Please provide feedback if you encounter any lag/issues/etc. If you're encountering lag, be more detailed in terms of which apps are causing lag.

If you do encounter lag, set up a Per-App-Mode and set the CPU frequency to 1.5GHz using FKU.

Or just overall boost up the CPU Max to 1.5GHz. In my personal experience, 1.2GHz is sufficient enough to not have any scrolling lag or switching from 1 app to the next.

Download: https://www.androidfilehost.com/?fid=23622183712461143

https://192.227.135.147/get/VomerTweaks/OPO/flashable/vt_zephik_v1.zip (another link)

To remove the script, just delete 51-vomertweaks.sh from /system/addon.d and /system/etc/init.d/01VomerTweaks.
[ONE Original Android Development] jarjar124:
I can rarely get that where I live due to poor reception. Always 2-1 bars
[ONE Original Android Development] zephiK:
Hm :( I get pretty good reception in the part of Brooklyn I'm in. Hopefully this set up balances it out for you
[ONE Original Android Development] jarjar124:
Average is 4-6 hours. Still better than my N5 lol :) On their site it says excellent coverage in my area, but I consistently get one to two bars. Sometimes even none in certain locations in the house. Strange.
[ONE Original Android Development] zephiK:
[MENTION=4468902]Saythis[/MENTION] Observations, thoughts?

Strange indeed, I get full bars :x it gets spotty and gives me yellow signal at times still though.
[ONE Original Android Development] cashyftw:
Just flash this, correct?
[ONE Original Android Development] zephiK:
Yeah in your preferred CWR. Make sure if you have any kernel tweaking apps that they're not set on boot including FKU/Trickster/Whatever else you use. You can use those apps to do any changes on the fly as well as change the settings of voltages if you would choose to do so.

If u have FKU, I highly suggest making Per-App-Modes to bump up the CPU frequency for apps/games that require the extra power (mainly games). Overall browsing, emails, text, etc should be perfectly fine with 1.2GHz thats why its the default.
[ONE Original Android Development] jlevy73:
Did you get better reception with your N5 in Brooklyn?
[ONE Original Android Development] MICa.fighter:
Check your apn settings, try another one if you can. It might help getting a better reception. I would also contact the support of your network provider, since they say excellent coverage. They should look at the apn settings too amongst other things.
[ONE Original Android Development] hughfollett:
Congrats! You're going to love it!
[ONE Original Android Development] Saythis:
So far I've noticed a significantly less drop in battery usage over the last few hours of using it. I'm planning to get a full charge and then run it ragged tomorrow through some daily usage testing. So far though it seems promising.
[ONE Original Android Development] JFK1997:
Hey guys,

First, thanks for porting vomertweaks. I still habe 2 questions:

- Should i reflash the tweaks in case oft kernel vor Rom update?

- In Settings - performance the max frequency is 1.2 GHz, but in the system monitor in fku there are always te 4 cores online (->hotplug 0) but some of them are going still up to 2.5 GHz. Is this right? I flashed with Twrp 2.7.1.1 over Cm11s with Franco r14 in case this helps.

Thanks for your hell. Stay awesome! ;)
[ONE Original Android Development] Saythis:
For me what I've noticed is that it keeps all of the cores active but keeps them extremely efficient at switching between clock speeds. Then when the phone screen is turned off they go into deep sleep. Basically instead of having a single or dual set of powerful cores you have four lesser clocked cores to handle multithreading. Which seems to be improving performance and battery life quite a bit for me so far.

If you flash an update over your current you will lose this script since it is in system/etc/init.d. This means you will need to refresh it when you update or switch to another rom. The cores should stay around 1.2GHz at all times almost.
[ONE Original Android Development] hellfire666:
I never had reception issues with this device maybe its a hardware problem
[ONE Original Android Development] jarjar124:
Got the same. Might be the walls blocking some of my reception since when I'm near a window it is always 2 bars. Otherwise it's 0 to 1 bar.
[ONE Original Android Development] shapethelola:
can you make that one public, I cant view it :(
[ONE Original Android Development] gro95qg:
work on last update ?
[ONE Original Android Development] zephiK:
No need to reflash the tweaks on a kernel or rom update, a backup script is included in the zip file so it doesn't get erased. If it does get erased during a ROM update and your settings don't stick then reflash it and let us know so we can fix the backup script.

Edit: my text was inside the quote tags. Fixed.

As mentioned above, no need to reflash the zip on a rom/kernel update.

If you want more details about the setup, read http://xdaforums.com/oneplus-one/or...-kernel-r1-t2800871/post54270696#post54270696 and the pages after it. Some highlights,

The way I like to think of the set up is instead of running 2 cores on and then hitting the "oh I need help button!" to activate cores 3/4, it will always have 4 cores on but if all 4 cores are on at the full frequency then obviously your phone is going to be using more battery life. If its running lower clocks but with the additional 2 cores on all the time that would normally be powered off, then the balance between good battery life and performance still remains.

See http://xdaforums.com/oneplus-one/or...-kernel-r1-t2800871/post54291066#post54291066 instead.

Yes it works on XNPH33R.
[ONE Original Android Development] noobhero:
Sir! On R14 and latest OTA. With a pressy plugged in and the pressy app disabled, the phone recognized the pressy as a headphone and there'll be no sound from the speaker when I make a call. fine one R13.

Sent from my A0001
[ONE Original Android Development] zephiK:
Attach a kmsg,

Did anyone test this with a aux cable? I remembered people in the past saying they had issues with connecting to a aux cable but haven't heard anyone report back as of r14.
[ONE Original Android Development] toge64:
Not entirely related by my Xiaomi Pistons now work with r14!
[ONE Original Android Development] gro95qg:
thanks
[ONE Original Android Development] kabauterman:
I have a big problem with franco kernel, I'm on r14 but same was on r13.

If the phone is running for a while and I get a call, I hear nothing, the Phone-Speaker is just silent.

I need to restart to phone to make a proper call.

Settings where nothing special and no UV.
[ONE Original Android Development] Brembo109:
[MENTION=1978554]zephiK[/MENTION] Thanks for your advanced help and pointing new members the right direction. Very appreciated. Will test your script and report back. Many thanks to Franco and all the other helpful guys, too. Nice community here. I'm glad I switched from my M7 to the OPO

Edit: is it appreciated to switch to a dedicated threat to discuss your specific modified script?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] zephiK:
I'll have to ask the other guys I work with about making another thread if we choose to do so.

In the past on the N5, it was just discussed in the official N5 franco thread.

Thank you for the kind words. Would love to hear feedback to further improve the settings, maybe even make the settings even more conservative to maximize even more battery life out of our oneplus one which already had great battery life out of the box.
[ONE Original Android Development] Brembo109:
Okay. For me there is no reason to separate it, but I feel like the threat gets a little bit cluttered when this discussions happens here either ☺. Will fully charge tonight and put the batterie to its limit tomorrow. Will see what results I get

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] noobhero:
Thanks will do.

When I get to do..

Cheers!
[ONE Original Android Development] JFK1997:
Hey,

Just wanted to share my experience eith vomertweaks. It gives me 1-2 h more SOT with same usage, gaming without lags is still possible altough i don't use per APP profiles. Good work!
[ONE Original Android Development] clock51:
the v r14 has the kexec patch? I can use on primary rom with "mod MultiROM"
[ONE Original Android Development] jarjar124:
Yes. It should have the patch
[ONE Original Android Development] Ky0sHiR0:
Can i flash vomertweaks on all kernels ? (i'm on SlimSaber actually with his kernel)
[ONE Original Android Development] zephiK:
No it is exclusive to Franco kernel because the paths are specific to Franco and those other kernels may not necessarily have the settings since other kernels don't have Franco hotplug algorithm.
[ONE Original Android Development] vomer:
All this without having the device!! Imagine the possibilities once I have this thing lol

Sent from my Nexus 7
[ONE Original Android Development] akarol:
Where do I find said tweaks?
[ONE Original Android Development] therebel88:
Giving this vomer tweaks a try...thanks!

If I flash the tweaks in recovery, how do I revert if I want to go back?

---------- Post added at 12:20 PM ---------- Previous post was at 12:20 PM ----------

https://192.227.135.147/get/VomerTweaks/OPO/
[ONE Original Android Development] abc123pro:
Hmm... I would guess reflashing the kernel would work? Not sure
[ONE Original Android Development] zephiK:
Read http://xdaforums.com/showpost.php?p=54995378&postcount=2143 at the bottom
[ONE Original Android Development] abc123pro:
I wasn't saying your flashable zip was the kernel. He asked how he would go about reverting the kernel settings after using your zip, and I suggested reflashing the franco kernel could work.
[ONE Original Android Development] sui81:
Must reflash the VomerTweaks zip after flashing a new FrancoKernel Build ?
[ONE Original Android Development] Ky0sHiR0:
How much SOT have u got ?
[ONE Original Android Development] JFK1997:
ATM i am at 2 1/2 h SOT in 7 h since unplugging and 60% left. I did stream 2h of spotify to a Bluetooth speaker in this time.
[ONE Original Android Development] zephiK:
If you read carefully. I quoted two posts, the one on the bottom talks about how to revert the settings. The one on the top quote answers the quote sui asked.

Please read my post guys. It explains everything that you have questions to.
[ONE Original Android Development] fiz:ik:
Well then :highfive:
[ONE Original Android Development] franciscofranco:
Yes I'll add that "fast charge" to allow the USB port to output more draw to the receiver.

You have apps fúcking you.
[ONE Original Android Development] tpcrackpipe:
Yup. It was Google play services wake lock. Had to disable SystemUpdateService$ActiveReceiver, SystemUpdateService$Receiver, SystemUpdateService$SecretCodeReceiver. That fixed it. Thank god other people have had this problem, made my life a lot easier.
[ONE Original Android Development] Expliciate:
r4 working great.

No issues whatsoever. :)
[ONE Original Android Development] MontAlbert:
the problem is actually a bug in CM11S where when a theme is applied it breaks the wifi settings- if i remember it's got to do with having a light holo theme (happened to me on Android L theme. )

The good news is that they have found the bug and it is resolved so the fixes will be in the current nightlies and will be released in the OTA update in July sometime

https://github.com/CyanogenMod/andr...mmit/335ac123b4578178aa330839c35444587fd8aeea
[ONE Original Android Development] franciscofranco:
Exactly.
[ONE Original Android Development] Devilman539:
I hope they add heads up as well. That's really the only feature I'd like added to cm11s everything else is golden.
[ONE Original Android Development] shaker2k:
Nope not apps (at least solely) . It's a problem with cm. It's fixed in the snapshot a and will be in the next OTA.

Edit talking about the deep sleep problem.

https://forums.oneplus.net/threads/...ing-an-answer-to-wakelock.50945/#post-2378232
[ONE Original Android Development] rebeccadri:
THX very goood work!

Gesendet von meinem One mit Tapatalk
[ONE Original Android Development] franciscofranco:
Well I don't have that problem, gladly :)

I'll work on the Fast Charge later today.
[ONE Original Android Development] Ok_Kaleidoscope5109:
Loll?
[ONE Original Android Development] ResistanceDown:
I'm getting this message right away when trying to use your app on my OPO. What can I do?
[ONE Original Android Development] giaur:
11S only, it's so sad
[ONE Original Android Development] shapethelola:
You need to buy the non-free one. That at least worked on my device with 11s. The free one didnt work for me either
[ONE Original Android Development] ResistanceDown:
I can just download and flash this manually without the app correct?

Also, when I flash it will my device be wiped?

Thank you
[ONE Original Android Development] shapethelola:
Yes, you can do that. The app is just a easier way to not look for the latest release in the forum and download it manually.

Nothing will be wiped from your phone
[ONE Original Android Development] Deadpool253:
I'm on stock and getting crazy drain. I know for a fact it's the software. Anyone know a fix for this until the next update? My battery life has been horrid Franco made it a bit better but it's still really bad. :'(
[ONE Original Android Development] indesisiv:
Please use either the search button or your eyes!!
[ONE Original Android Development] franciscofranco:
Yes, I'm so sad about it. :eek:
[ONE Original Android Development] Narhim:
same issue here... android OS ate up more than 40% of my battery. No idea where that came from, yesterday everything was normal :/
[ONE Original Android Development] abc123pro:
Well then to be fair, you answered someone else's question after quoting me and not that person. Just a misunderstanding I suppose [emoji1]

Anyway back on topic I tried AK kernel for a bit but ended up back here with the r14 release. Much appreciated
[ONE Original Android Development] zephiK:
Oh haha you're right. Tapatalk multi quote confuses me. Sorry about that. I'll tidy up the post and put up a faq instead of paragraph form later today.
[ONE Original Android Development] SleemLDJ:
Maybe someone has said this before but can there be a thread for vomer tweaks so that's averages like me don't get lost or confused. ?
[ONE Original Android Development] hughfollett:
[MENTION=1363323]vomer[/MENTION] is waiting for his device to arrive maybe
[ONE Original Android Development] jarjar124:
Yep. He just ordered it yesterday
[ONE Original Android Development] SleemLDJ:
Well.... Makes sense if he's waiting for his device to arrive first.

Thing is discussions on it is already going on in the kernel thread and people will miss vital information....

So might as well open a thread for that and start updating when he gets the device.
[ONE Original Android Development] krxz:
Do I have to set the values in fku on boot after flashing or is this not necessary?

I am asking because I first set the values manually in fku, clicked values on boot and after that I flashed the zip.

I mean I just want to be sure the settings work properly
[ONE Original Android Development] Tzfardaya:
feel free to add OPO chat in the fku and pam modes thread linked in my signature, It's where we were trying to keep track of all the n5 config settings, I keep meaning to add OPO settings to it as well (and have it moved)

Go into the /etc/init.d folder and delete the vomer settings file.. (can't recall the exact file name at this moment, but you should see it easily enough)

no.