Related
In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks
cengator said:
In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks
Click to expand...
Click to collapse
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App
superchilpil said:
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App
Click to expand...
Click to collapse
Thanks. Yeah, I know what zipalign and deodexing are. If a dev says his rom is "optimized, zipaligned, and deodexed," he is doing something additional besides those two. I'm wondering what that might be.
Generally image optimization. Although some dev's actually do improvements such as stripping the extra localizations. Stock images are already optimized unless you edit them, well all the ones I've check anyway.
i do all kinds of stuff and still don't know what zipaligned means/does
When devs say they optimized there rom or framework etc... It means they ran a tool such as apk manager (what I use) to compress all the images in an apk to be the smallest size they can get them without losing quality. This will speed up the build for maximum performance and less ram usage.
Other people say there apks are Reengineered. This means that there apks have all unused lanuages removed for even better performance.
Odexing means Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes). Odexed builds such as stock roms cannot be themed for the most part.
Zipalign is an archive alignment tool introduced first time with 1.6 Android SDK (software development kit). It optimizes the way an Android application package (APK) is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting is lesser amount of RAM consumption when running the APK.
Hope this helps,
Incubus
Wow! Thank you very much! That is very informative. Regarding deodexing, other optimizations being equal, would an odexed rom have greater performance than a deodexed rom?
Sent from my ADR6300 using Tapatalk
incubus26jc said:
When devs say they optimized there rom or framework etc...
Click to expand...
Click to collapse
What does the difference in framework mean?
I found this website( http://androidforums.com/incredible-roms/155282-incredible-rom-list.html ) to try and find some new roms to use, because i'm stuck at the white screen of death on my Dinc. See this post if you want to help ( http://forum.xda-developers.com/showthread.php?t=1023358 )
BUT my actual question is what does framework mean? Are all of those "frameworks" listed compatible with my phone? I know that the Dinc uses the "Sense UI"...are these the same? Can I install "vanilla" framework ROMS on my Droid Incredible? If I do, is there certain things that won't work? Sorry for all the newbish questions, but I'm already soft bricked and want to know before I go messing around with stuff again. Seems I only knew just enough to get me into trouble and bring me to a white screen, and I don't want to do further damage.
Thanks a ton.
I've seen a lot of new member here. I hope this thread might help them decide what ROM are best for them and reduce the number of question. however, I won't mention any rom in this forum to keep this thread from my subjective point of view. you should see the development section by yourself to find your best suited rom for you.
OK. lets get straight to the topic. this is some things that you should consider when you choose a custom rom. I'll divide the guide into three main parts two make everything is easy to understand. the parts are performance, style, and additional consideration.
##PERFORMANCE##
Click to expand...
Click to collapse
1. debloatware
debloatware is a process to remove considered useless apk from the system. every rom has different degree of debloatware. a hight degree debloatware means you'll have only use a little of ram space for system app. however we'll lost some of sync function like kies synchronization if we remove all bloatware from the system. make sure that you still have all the app you need from stock rom in your custom rom.
2. deodexed vs odexed
Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.
ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it is tend to more stable and consume less internal memory and a execute faster. it is also faster since the system doesn't have to build dalvik cache at boot process. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.
DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. the system also might a little bit slower since the system need to build a lot of dalvik-cache when the phone start.
3. custom kernel
a custom kernel could give you a huge boost of performance. for the most basic one, you should choose a kernel with init.d support. we'll need it to run a lot of performance tweaks. if you're seeing a custom kernel, you should look into these point:
- custom governoor
custom governoor will give you a lot of option to set your device performance. you can set the performance as hight as possible or save your battery as long as possible by set the correct governoor.
- custom scheduler
its almost same with custom governoor. however it manage I/O on your device. it won't give you a huge boost on performance but you should consider it as your main consideration.
- droidwall support
- a2sd and swap support
- additional feature
- bug and rom compatibility
not all custom rom compatible with all custom kernel. make sure that your custom kernel is compatible with your rom.
4. performance tweak availabilty
for a basic consideration, make sure that your rom have a performance tweak. otherwise, you'll got only a themed rom with stock performance. if you're a performance person, make sure your rom is have these tweak.
- memory management optimization
- hsdpa optimization
- kernel and I/O optimization
- gps optimization
- internet speed optimization
these tweaks are could be found at build.prop, init.d, sysctl.conf, and gps.conf.
5. additional tweaks
there are also some additional tweak you should consider if you want to install a rom. the commonly used are:
- bravia engine
- sound enhancement
6. performance app
some ROMs offer performance tweak app like ROM manager inside it. you should consider these app if you're a performance person
##STYLE##
Click to expand...
Click to collapse
1. theme
this is a very subjective topic. you should choose a rom with a topic suit with your style.
2. degree of customization
every rom has certain degree of customization. if you're a themed person, you should consider these point for your rom.
- EDT tweak for statbar customization
- ROM'S lab
- customizer app
- theme availability
3. ROM special app
some of ROM have special app for their rom. they're specially developed for only certain roms and comes with special names and various function. these app will give you a huge power for style and performance customization.
##ADDITIONAL CONSIDERATION##
Click to expand...
Click to collapse
1. update availability
some ROMs are good but they're left undeveloped. you won't get an update for your rom. you should choose a rom with a continous update from the dev to ensure you get the best rom for you.
2. dev support
not all ROM maker are really a dev. some of them just a wannabe dev with a theme modified rom skill. you can't expect them to solve the bug in their rom. you should choose with a good reputation and high skill.
3. rom size
this is not a huge issue. if you have a slow internet connection, a smaller rom is better for you. smaller rom also means a big degree of bloatware. the system will be lighter than the other rom.
4. rom base
some of rom are using old firmware (--KL) while some other are using newer firmware(--LB or newer). you should aware of these stuff since not theme and mod available in our forum are compatible with all firmware. new firmware will give you more stability but in most case you can't have custom bootanimation.
5. multilanguage
this is not a huge issue but you should consider it as well. not all rom support japanese, chinese, arabic, spain and latin fonts.
DISCLAIMER: REMEMBER THAT YOU'LL NEVER GET ALL IN ONE PACKET ROM. ALL ROMS HAVE THEIR STRENGTH POINT. YOU CAN'T EXPECT ANY DEV TO MAKE "A PERFECT" ROM FOR EVERYONE. IF YOU DON'T SATISFY WITH YOUR ROM REMEMBER THAT YOU CAN ALWAYS CUSTOMIZE YOUR ROM BY YOURSELF.
Reserved for dunno
just in case
This thread really help me to create my own custom rom with world best future ......... many many thanks for the great thread .....
Sent from my GT-S6102 using Tapatalk 2
If i use to create odexed rom is it support all tweaks ..
And if i costmize only systemui /firmwork * (deodexed)
With odexed rom its support or not...
Sent from my GT-S6102 using Tapatalk 2
if you want a customizable theme you can make your systemUI.apk as a deodexed apk. if your apk have classes.dex inside it you'll need to delete systemUI.odex from your system.
Can i add a link to this in FAQ bro?
This is basic but very useful for newbies
yes sure...
which rom in your openion is preferrable
which hit high ends
explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
wat r ur expectations from a rom?
explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
that is an unending debate, anyway for me
stability - stock ROM
I already have all my tweaks needed for my rom. If anyone asked "what rom do you like?" I'll answered "just a stock rom but with a better graphic and sound driver". however, I'm afraid we've to build it from source to get it
More questions
Great explanations bro, specially for nobs like me
My questions are:
1- How can I know if the ROM totally support Arabic-Language?
I live in Saudi Arabia and My SGY comes with XXLC1 stock ROM.
2- Is there any other stocks than XXLC1 ROMs I can use and still support Arabic and Modem-settings in my region?
I notes that most if not all custom ROMs based on Different stocks than mine.
I know, it sounds like I answered my first question in the second one, but still I need more clarifications.
3- Now I'm using REMIX ROM with [email protected] Kernel, based-band S5360XXLC1. Still, I can't have full Arabic interfaces and
my browsers cant read Arabic too. I wounder why?
Sorry for the very nob questions and Thank you very much.
Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
There are plethora of tools in the chef section.
Sent from my Go Senseless Classic Conflagration Evo
Angelus359 said:
Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
Click to expand...
Click to collapse
The best tools to use to start learning to make create your own roms is use the kitchen,it will zipallign and deodex all that good stuff,like the guy above me said, theres alot of other guides and tools here that will help you with your venture....
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Reserved for any common questions, or general information.
red_can_soda said:
Reserved for any common questions, or general information.
Click to expand...
Click to collapse
Nice bud, I'll have to see if it works on Lollipop TW
Using it in pvs bin 0 lol
So far so good. Make sure to set permissions to 755
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
kevp75 said:
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
Click to expand...
Click to collapse
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
red_can_soda said:
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
Click to expand...
Click to collapse
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
kevp75 said:
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
Click to expand...
Click to collapse
Forgot I had that there... Lol. Threw that in a while back so init.d would operate with a 100% stock boot.img
@kvp75, can I drop this into Phoenix Rom?
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
It will work with any galaxy note 3 using Qualcomm hardware.
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
red_can_soda said:
Drop this file in your /system/etc folder, replacing the stock one.....
Click to expand...
Click to collapse
Lmao....Cob
kevp75 said:
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
Click to expand...
Click to collapse
All good, I went ahead and did it anyway, it's def making a difference, battery life was not great but now it's better! Thanks for all the hard work guys, keep it up! I'll reflash DomPop again soon, it was unstable for me but Phoenix has been great
This activated all cores and set to performance... when i selected interactive the min value was 422... Am I doing something wrong? Everything stock and rooted 442
Edit. .. Ok I changed from interactivex to interactive and that fixed gov problem but all cores activated and min set to 422... Is that right?
Yes, minimum is 422 MHz because the l2 cache is bumped into action at that speed (as opposed to not being so at 300) and the voltage is the same.
In short, 300 is no5 used because 422 is faster, and without the extra hit on battery
Will this work with 4.4.4 w/o any issues? Been thinking on trying it on but I don't want it to mess anything and re-install stuff.
d-wad,
I cannot give you a definite answer there, as I have not yet looked at anything in 4.4.4.
If you can provide me a copy of the post_boot file for 4.4.4, I can take a look at it and see. I can't imagine why anything would have changed in this file, but you never know. All it takes is one line of code to cause something to go a little wonky for you.
Thanks, and just shoot me a PM.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated file and link... I recommend using this file or implementing these items into your current set up. Many of the changes are critical errors existing in the stock post_boot file, or simple optimization enhancements for our devices.
How to revert?
Sorry... TOTAL NOOB here...Do I just copy the orig file somewhere else, and drop this in place as you instruct? ( may have answered my own Q)
Seems a wise precaution.
I am running effortless rom rev 8 (lovin it too)
Hey Guys,
I thought while waiting for the first custom kernels that maybe i should have a look at the interactive values and try to tweak them based on this way:
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
So i took a script from @Alcolawl and modified it to work with our device. Many thanks for his scripts.
I adjusted the values to our snapdragon 820 as the original scripts are for the nexus 6p which runs with a snapdragon 810. (octa on the 810 vs quad-core on the 820)
I´d highly recommend to try these values as it gave me a significant boost in battery life. here is a screenshot:
https://drive.google.com/file/d/0BxbxiBXaZVu-N1lsRTMyZ2hsY1k/view?usp=sharing
https://drive.google.com/file/d/0BxbxiBXaZVu-N1MzamRvM2FVZlk/view?usp=sharing
BIG UPDATE: with base 1.80 i´m not able to trick the touch/Input boost from htc´s pnpmgr with a chmod command like i did before. so all versions since Butterfly v11 will disable pnpmgr completely.
that means if you Play high end games and your device overheats like crazy please Report back. i had no Problem until now.
also there are now 2 versions. the oc one is for overclocked cpus with elementalx. without oc is for the default clock speeds.
here are explanations on what the 2 different stragies do:
Butterfly - A culmination of all strategies, provides smoothest performance of all currently published settings, though battery savings are a little more modest. Excellent for light and moderate users; heavy/marathon users might want to check out a different setting profile as it gets battery intense with heavy usage.
GhostPepper - Uses a quantized, frequency-aligned parametric curve to influence low core clock rates while providing extremely smooth transitions from each clock rate and exceptional battery life. Good for light to medium usage and multitasking.
So basically there will be two ways of applying this mod.
First one is via scripts. this allows to set parameters outside of the interactive governor controls like cpu boost, editing of pnpmgr, min/max frequencies etc. so basically there´s more control.
Second one is via EX Kernel Manager. I will upload the profiles and you can apply them directly into the app. This will however only affect the tunables of the interactive governor. Touchboost has to be set manually for the profile to work exactly as intended.
when the phrase "elex" is in the zips name it is for use with ex kernel manager app (loading profile in governor options screen.
so to try the script method follow these steps. (and before do a nandroid as always)
1. download the attched file.
2. unzip the file, choose the correct script (oc if you have overclocked)
3. with a root explorer or terminal copy the file to system/su.d
4. set the correct permissions (rwxr-xr-x)
now you may either choose to change the settings temporary (step 5A) until the next reboot or permanently upon each reboot (step 5B)
5A. rename the file to 50ghostpeppertenv3.sh
use any script manager and run the script from this location (system/su.d)
alternatively use any terminal emulator app with the following commands
su
cd system/su.d
sh 50ghostpeppertenv3.sh
Be advised that the script takes in its current state 60 seconds to be applied. So the changes need a minute to be applied.
now check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this: "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully
- the values changed with each update. what´s important to check is just the generel layout
5B. (-if you did the temporary approach beforehand remove the .sh)
- it should look like 50ghostpeppertenv3 (make sure there are now spaces at the end)
reboot and check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this : "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully.
-- the values changed with each update. what´s important to check is just the generel layout
Important!!!
if you run permissive and run into no signal issue due to this look here
if you should run into a no signal issue where your baseband shows as unknown under software status ( currently on custom roms eg leedroid) you have to put a script to system/su.d that sets selinux to permissive. attached is such a script.
unzip it. copy it to system/su.d
set the same permissions as the ghostpepper script and your good to go.
running in terminal the command "getenforce" should return permissive.
Second method via Elemental App:
1. Download the desired profile from the attachments
2.Extract the Profiles from the zip
3. Choose the Overclocked(oc) version if you overclocked
4.Copy the file to sdcard/ElementalX/gov_profiles
5. Open the app and apply the values
let me know if it brings a little battery boost for you. you may also let me know if you face performance issues.
Thank you and have fun testing it.
Changelog:
Ghostpepper:
v1: Initial Release
v2: Tweaking The Script so the values will get applied properly on all roms
adding a permissive script in case of getting enforced
v3: Removed touchboost so the profile may unleash its full potential <<--- results in overall slower device.
v4: Added back short input boost
v4withtb: Added back original touch boost from htc
v8: New try on getting the interface smooth and disabling touchboost (minimal stutter remains)
v8withtb: same as v8 touchboost is still active
v9: only one version with touchboost now. tweaked target loads (lower freqs are used more), short input boost
there are now two files inside the zip.
v10: try to further improve frequency usage, less aggressive scaling
v11: fix in case Little cores might get stuck at highest clock
Butterfly
v4: Initial Release
v4withtb: Initial Release with original touch boost from htc (extremely smooth)
v6withtb: tuned the values and kept touchboost from pnpmgr, kernel touch boost is disabled, extremely smooth for me
v7: less aggressive scaling, performance should be really good while reducing less power than v6
v9: basically scaling is tuned to respect the crossover effieciency point from big and little cluster
v11: updated to work on base 1.80
- disable pnpmgr completely because the chmod trick for disabling pnpmgr´s touchboost is no longer working
- enable msm_thermal and core_control
v12: tweak some values to work better with the new base
v13: hotfix as i made a mistake in the previous version
credits:
thanks to @Alcolawl for the script template
also thanks to @soniCron for the original thread
reserved
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Captain_Throwback said:
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Click to expand...
Click to collapse
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
gusoldier said:
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Click to expand...
Click to collapse
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Freak07 said:
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Click to expand...
Click to collapse
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
gusoldier said:
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
Click to expand...
Click to collapse
yeah. I can try this later. But compared to my nexus 6 and my pixel c the 10 is about as smooth.
Freak07 said:
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
Click to expand...
Click to collapse
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
P.S. You didn't answer my question about why you're not using su.d instead of init.d?
Captain_Throwback said:
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
Click to expand...
Click to collapse
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Or is it just like "sleep 30"?
Edit2: it is indeed. thank you again.
Freak07 said:
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Click to expand...
Click to collapse
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Captain_Throwback said:
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Click to expand...
Click to collapse
yeah you´re right. thanks for the reference and the hint. i knew about it but didn´t remember i could use this see my edited last post. with sleep 30 it´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Freak07 said:
yeah you�´re right. thanks for the reference and the hint. i knew about it but didn�´t remember i could use this see my edited last post. with sleep 30 it�´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i�´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Click to expand...
Click to collapse
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Captain_Throwback said:
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Click to expand...
Click to collapse
Okay i'll edit it to 60.
This is what I'm talking about. Every Chip has a pvs bin. The higher the bin the lower the voltage for a certain cpu frequency.
And every bin has its own voltage table.
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
rav101 said:
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
Click to expand...
Click to collapse
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Freak07 said:
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Click to expand...
Click to collapse
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
rav101 said:
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
Click to expand...
Click to collapse
How did you recover? Full Wipe?
Delete
Freak07 said:
How did you recover? Full Wipe?
Click to expand...
Click to collapse
Yeah, I tried a dirty wipe but that didn't work so had to do a full wipe.