***Disclaimer: I am NOT responsible for what you flash on your tablet or damage caused by what you flash on your tablet.
Credits: Koush and TeamDRH
Kernel developers, you may use this zip file as a template for your kernel installs. It will extract the current boot.img, unpack it, combine ramdisk with your zImage and flash it. It should make your kernels a lot easier to distribute among different roms and the users will be able to flash a new kernel without waiting for us to repackage it.
Usage:
Add your zImage into the /kernel folder of the zip
Add your wifi module into the /system/lib/modules/ folder of the zip.
Profit
I have tested this by flashing Motley's 2.5.8 on my AOKP build and it worked flawlessly.
Enjoy!
Download
jermaine151 said:
***Disclaimer: I am NOT responsible for what you flash on your tablet or damage caused by what you flash on your tablet.
Credits: Koush and TeamDRH
Kernel developers, you may use this zip file as a template for your kernel installs. It will extract the current boot.img, unpack it, combine ramdisk with your zImage and flash it. It should make your kernels a lot easier to distribute among different roms and the users will be able to flash a new kernel without waiting for us to repackage it.
Usage:
Add your zImage into the /kernel folder of the zip
Add your wifi module into the /system/lib/modules/ folder of the zip.
Profit
I have tested this by flashing Motley's 2.5.8 on my AOKP build and it worked flawless.
Enjoy!
Click to expand...
Click to collapse
Awesome, way to go Jermaine! Been thinking about doing this too, but never got around to it. Great work. I will definitely use this as a secondary CWM zip for users so they can try it with other ROMs. I will also be coming out with a version of the kernel that removes all the Asus power mode stuff (conditional compile) so you can just run a plain vanilla kernel without that stuff. Should be better for you I think. Let me know what you think.
_motley said:
Awesome, way to go Jermaine! Been thinking about doing this too, but never got around to it. Great work. I will definitely use this as a secondary CWM zip for users so they can try it with other ROMs. I will also be coming out with a version of the kernel that removes all the Asus power mode stuff (conditional compile) so you can just run a plain vanilla kernel without that stuff. Should be better for you I think. Let me know what you think.
Click to expand...
Click to collapse
That sounds awesome Motley! Thank you.
Hi Jermaine, I think the zip file got truncated by XDA after the upload. Has been happening to me to. Can you link it again? Thanks!
_motley said:
Hi Jermaine, I think the zip file got truncated by XDA after the upload. Has been happening to me to. Can you link it again? Thanks!
Click to expand...
Click to collapse
I'll upload it to my host. I have to wait a bit because my computer is building right now. Should be up in 15-20 mins.
Edit: Nevermind. My build crashed. LOL. Link is posted.
Sent from my Galaxy Nexus using Tapatalk 2
jermaine151 said:
I'll upload it to my host. I have to wait a bit because my computer is building right now. Should be up in 15-20 mins.
Edit: Nevermind. My build crashed. LOL. Link is posted.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you sir!
_motley said:
Thank you sir!
Click to expand...
Click to collapse
You're welcome!
Any chance of someone cooking up a EOS compatible version of motley's 2.5? I switched from aokp for a minute so I could play with cornerstone. I'd really like the 1.8 though?
Sent from my TF201
using XDA
I haven't ran this rom, so I can't say for sure. I can't find anywhere where they state which kernel they are using, since it isn't stated I am assuming it is stock.
That said, my guess is that you can do the following. If you try it, let us know how it works. The ROM has to have init.d support...not sure if it does,
1) Do a backup in CWM so you can restore your boot.img quickly if necessary.
2) Flash the zip in this thread that Jermaine posted. The beauty of AnyKernel is that it just takes the zImage (kernel) and tucks it inside the resident initramfs (aka ramdisk) without making any changes to it, and then also copies in the wifi module. While it is called AnyKernel, Jermaine and I would probably call it AnyROM LOL...since this method will allow kernel devs to stop creating specific installs for each ROM.
3) Make sure it runs ok, if not go to step 6
4) go to /system/etc/init.d (if it doesn't already exist, the rom doesn't likely support init.d). Check with the ROM dev and ask him to add it.
5) create a script file "51_oc" within the init.d folder that sets the OC mode stuff. If "51" is taken, use another number else. Make sure the script file permissions are set to allow "Execute".
filename: /system/etc/init.d/51_oc
file contents:
Code:
#!/bin/sh -x
#This is 1.8 Performance mode - motley kernel Habanero
echo 5 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
6) If it doesn't work, just restore your boot.img (selective restore) from the CWM backup or flash the rom again without a data wipe to get back where you are right now.
First, thanks for anykernel for tfp. It has advantages over supplying the ramdisk as well.
Although i don't dev, it seems to me that using anykernel isn't touching ramdisk except kernel. Because of that, be it a dev or a user, cannot change ramdisk contents through a cwm zip, but must do so either by doing it from src, or by unpacking/repacking that ramdisk, eventually sharing it. Am i correct?
Thanks.
bk201doesntexist said:
First, thanks for anykernel for tfp. It has advantages over supplying the ramdisk as well.
Although i don't dev, it seems to me that using anykernel isn't touching ramdisk except kernel. Because of that, be it a dev or a user, cannot change ramdisk contents through a cwm zip, but must do so either by doing it from src, or by unpacking/repacking that ramdisk, eventually sharing it. Am i correct?
Thanks.
Click to expand...
Click to collapse
I'm not positive that I completely understand what you're asking but this doesn't mess with the ramdisk. It extracts the current kernel and ramdisk from the device. Then it separates the 2. Then it combines the untouched ramdisk with the new kernel and flashes them back to the device.
Great !!
I thought that that would be the solution to deal with different kernel ramdisks.
The only point people need to know is that as this doesn't modify ramdisk, but just update the zImage file, if the initial ramdisk doesn't have init.d support, it won't add it.
We had to clarify this on my phone's forum, as some people complained about 'bugs' that were in fact just a correct behavior of AnyKernel.
Thanks Jermaine!
jermaine151 said:
I'm not positive that I completely understand what you're asking but this doesn't mess with the ramdisk. It extracts the current kernel and ramdisk from the device. Then it separates the 2. Then it combines the untouched ramdisk with the new kernel and flashes them back to the device.
Click to expand...
Click to collapse
If one would like, or need, to provide ramdisk tweaks, apart from the kernel (zImage) one cannot use anykernel to do it. Instead, one would need to release the whole ramdisk. Sorry i wasnt able to get this clearer.
bk201doesntexist said:
If one would like, or need, to provide ramdisk tweaks, apart from the kernel (zImage) one cannot use anykernel to do it. Instead, one would need to release the whole ramdisk. Sorry i wasnt able to get this clearer.
Click to expand...
Click to collapse
You can use AnyKernel as a starting point and then manipulate the ramdisk while it's in /tmp before combining it with the new zImage and flashing it. I did this type of thing with my Ext4All mod on the Droid Incredible. You can download one of my scripts from here and disect it:
http://forum.xda-developers.com/showthread.php?t=1315372
Edit: Here'a snippet of how I use sed to manipulate the ramdisk and change the mounting parameters:
#extract ramdisk
mkdir /tmp/ramdisk
cd /tmp/ramdisk
gunzip -c ../boot.img-ramdisk.gz |cpio -i
#edit file
sed -i '/mount ext3 mmcblk0p1/c mount ext4 mmcblk0p1 /data nosuid nodev noatime nodiratime data=writeback noauto_da_alloc' init.inc.rc
sed -i '/mount ext3 mmcblk0p2/c mount ext4 mmcblk0p2 /cache nosuid nodev noatime nodiratime data=writeback noauto_da_alloc' init.inc.rc
sed -i '/mount ext3 \/dev\/block\/mmcblk0p1/c mount ext4 /dev/block/mmcblk0p1 /data wait nosuid nodev noatime nodiratime data=writeback noauto_da_alloc' init.inc.rc
sed -i '/mount ext3 \/dev\/block\/mmcblk0p2/c mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev noatime nodiratime data=writeback noauto_da_alloc' init.inc.rc
#build new ramdisk
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
CWM recovery is powerful and has a lot of these editing tools built in and can be ran via a script while in recovery. There isn't much that you can't do.
Nice jermaine, thank you very much.
I had a feeling this was possible, Anykernel is indeed powerful. Would you agree to edit first post with this "template"? It's a great resource, imo.
bk201doesntexist said:
Nice jermaine, thank you very much.
I had a feeling this was possible, Anykernel is indeed powerful. Would you agree to edit first post with this "template"? It's a great resource, imo.
Click to expand...
Click to collapse
You're welcome. This isn't really a part of AnyKernel. It's just what you can do with extra scripts in recovery flashable zips. The goal for this AnyKernel thread is so that when Motley, Shaky, etc., release a kernel, if they put it in AnyKernel, we don't have to have separate versions for every rom.
jermaine151 said:
You're welcome. This isn't really a part of AnyKernel. It's just what you can do with extra scripts in recovery flashable zips. The goal for this AnyKernel thread is so that when Motley, Shaky, etc., release a kernel, if they put it in AnyKernel, we don't have to have separate versions for every rom.
Click to expand...
Click to collapse
I'll keep that in mind and do some research. Having these tools here, with root, it's actually genious. Thanks again!
_motley said:
I haven't ran this rom, so I can't say for sure. I can't find anywhere where they state which kernel they are using, since it isn't stated I am assuming it is stock.
That said, my guess is that you can do the following. If you try it, let us know how it works. The ROM has to have init.d support...not sure if it does,
1) Do a backup in CWM so you can restore your boot.img quickly if necessary.
2) Flash the zip in this thread that Jermaine posted. The beauty of AnyKernel is that it just takes the zImage (kernel) and tucks it inside the resident initramfs (aka ramdisk) without making any changes to it, and then also copies in the wifi module. While it is called AnyKernel, Jermaine and I would probably call it AnyROM LOL...since this method will allow kernel devs to stop creating specific installs for each ROM.
3) Make sure it runs ok, if not go to step 6
4) go to /system/etc/init.d (if it doesn't already exist, the rom doesn't likely support init.d). Check with the ROM dev and ask him to add it.
5) create a script file "51_oc" within the init.d folder that sets the OC mode stuff. If "51" is taken, use another number else. Make sure the script file permissions are set to allow "Execute".
filename: /system/etc/init.d/51_oc
file contents:
Code:
#!/bin/sh -x
#This is 1.8 Performance mode - motley kernel Habanero
echo 5 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
6) If it doesn't work, just restore your boot.img (selective restore) from the CWM backup or flash the rom again without a data wipe to get back where you are right now.
Click to expand...
Click to collapse
Motley thanks for trying to help me out. I really want to get the hang of this because I love 1.8 (curtiousy of you) but I want to try some other roms. Unless I'm misreading I don't see the part in your instructions where it deals with the kernel I want to flash. Say for instance I want to use your 1.8 kernel on cm9. After I flash cm9, what do I do before flashing the anykernel zip? It jermaines OP it says remove copy zImage of the kernel you want to use into the anykernel zip. However, if I look in the zip of your kernel, all that exist's is the blob file and some scripts. This is the first device I've ever had where blob files have even been mentioned so I don't know how to get the zImage out of it. Also when dealing with kernels for my nookcolor and touchpad it's always been a uImage, what the difference? I know its alot of questions but I really appreciate the help.
Sent from my EPAD using XDA
newellj79 said:
Motley thanks for trying to help me out. I really want to get the hang of this because I love 1.8 (curtiousy of you) but I want to try some other roms. Unless I'm misreading I don't see the part in your instructions where it deals with the kernel I want to flash. Say for instance I want to use your 1.8 kernel on cm9. After I flash cm9, what do I do before flashing the anykernel zip? It jermaines OP it says remove copy zImage of the kernel you want to use into the anykernel zip. However, if I look in the zip of your kernel, all that exist's is the blob file and some scripts. This is the first device I've ever had where blob files have even been mentioned so I don't know how to get the zImage out of it. Also when dealing with kernels for my nookcolor and touchpad it's always been a uImage, what the difference? I know its alot of questions but I really appreciate the help.
Sent from my EPAD using XDA
Click to expand...
Click to collapse
Jermaine's instructions you mention are really for kernel devs, so don't worry about those extra steps unless you want to learn to package stuff up yourself. The CWM kernel install zip he posted in the OP is my 2.5.8 1.8GHz kernel using the AnyKernel method. The boot.img contains two things, a ramdisk (initramfs) + the kernel binary. the ramdisk is the customized part of these ROMs. The AnyKernel method will not alter your ramdisk. It just unpacks/repacks the boot.img and replaces the zImage at flash time. For any ROM, all you need to do is flash the AnyKernel zip (like the one in the OP) and it will give you the zImage (kernel) that the kernel dev has prepared for you.
I also have some other news on this front...and this was a decent segue for this. You may want to try this zip as well (you can try both and see what works better). I am hoping Jermaine will give it a spin and give his input (tickle, poke LOL). Let me know what you guys think.
New beta for non-stock ROMs! Recommended for advanced users and ROM developers until we flush out and identify any issues or improvements that need to be made
View attachment motley_tfp_generic_2.6.1_beta.zip
I have modified the kernel code to conditionally compile based upon a config switch called CONFIG_ASUS_OVERCLOCK_MODES. When turned OFF, this allows me to easily compile and release a version of the same kernel base that is generic without the Asus performance modes (system_mode). This will make the kernel behave like a regular kernel that works properly with SetCPU, No-frills, ROM Control etc. on non-stock ROMs. The generic kernel still runs fine on stock, but the Asus modes no longer will change the CPU frequency, but only set the core_cap_level voltage.
At boot, I still recommend running the following script with init.d or a ROM dev can also integrate into your initramfs init.cardhu.rc somewhere. For example, AOKP may already be good to go with this.
Code:
#!/bin/sh -x
# Generic kernel settings
echo 1300 /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
Since the frequency defaults to to max (1.8GHz), you may want to set it in the init.cardhu.rc script with something like this. For example: 1.6GHz.
Code:
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1600000
_motley said:
Jermaine's instructions you mention are really for kernel devs, so don't worry about those extra steps unless you want to learn to package stuff up yourself. The CWM kernel install zip he posted in the OP is my 2.5.8 1.8GHz kernel using the AnyKernel method. The boot.img contains two things, a ramdisk (initramfs) + the kernel binary. the ramdisk is the customized part of these ROMs. The AnyKernel method will not alter your ramdisk. It just unpacks/repacks the boot.img and replaces the zImage at flash time. For any ROM, all you need to do is flash the AnyKernel zip (like the one in the OP) and it will give you the zImage (kernel) that the kernel dev has prepared for you.
I also have some other news on this front...and this was a decent segue for this. You may want to try this zip as well (you can try both and see what works better). I am hoping Jermaine will give it a spin and give his input (tickle, poke LOL). Let me know what you guys think.
New beta for non-stock ROMs! Recommended for advanced users and ROM developers until we flush out and identify any issues or improvements that need to be made
View attachment 1013277
I have modified the kernel code to conditionally compile based upon a config switch called CONFIG_ASUS_OVERCLOCK_MODES. When turned OFF, this allows me to easily compile and release a version of the same kernel base that is generic without the Asus performance modes (system_mode). This will make the kernel behave like a regular kernel that works properly with SetCPU, No-frills, ROM Control etc. on non-stock ROMs. The generic kernel still runs fine on stock, but the Asus modes no longer will change the CPU frequency, but only set the core_cap_level voltage.
At boot, I still recommend running the following script with init.d or a ROM dev can also integrate into your initramfs init.cardhu.rc somewhere. For example, AOKP may already be good to go with this.
Code:
#!/bin/sh -x
# Generic kernel settings
echo 1300 /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
Since the frequency defaults to to max (1.8GHz), you may want to set it in the init.cardhu.rc script with something like this:
Code:
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 1600000
Click to expand...
Click to collapse
Awesome Motley! Should that last line be:
Code:
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_[color=red]max[/color]_freq 1600000
Related
Tripnraver and Fanboys that wants to start trouble follow this Link! If you want to clear up the Discussion and stop fighting write me a PM and if not stay at Modaco, i even post the link for you all
Open TripNHome
XDA Users stay here and help collecting some nice X10 Tweaks to help the whole Community, every Dev/Cooker knows other Tweaks so i would like to invite all to share there best Tweaks here. Above i post some basic Tweaks and a example File how it looks like.
build.prop Tweaks
# Network
HTML:
ro.ril.hep=1
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.telephony.call_ring.delay=1000
# Product
HTML:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
# Performance
HTML:
dalvik.vm.startheapsize=48m
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-flags=m=y
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=200
windowsmgr.max_events_per_sec=300
VM Tweaks
HTML:
echo 95 > /proc/sys/vm/dirty_ratio
echo 20 > /proc/sys/vm/vfs_cache_pressure
echo 4096 > /proc/sys/vm/min_free_kbytes
echo 1 > /proc/sys/vm/oom_kill_allocating_task
echo 60 > /proc/sys/vm/dirty_background_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 2000 > /proc/sys/vm/dirty_writeback_centisecs
Minfree Tweak
HTML:
echo 1536,3072,4096,15360,17920,20480 > /sys/module/lowmemorykiller/parameters/minfree
SD Card Tweak
HTML:
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo 2048 > /sys/devices/virtual/bdi/default/read_ahead_kb
build.prop Tweaks go to system/build.prop
other Tweaks go to system/etc/install-recovery.sh
I attached 2 sample files with these Tweaks included.
shall we edit these even if running 3.6?
bodomfan said:
shall we edit these even if running 3.6?
Click to expand...
Click to collapse
No
10 Characters
Wolfbreak said:
No
10 Characters
Click to expand...
Click to collapse
Lol ok,dumb question really.its probably all included ,iv posted a request in the rom thread
im liking v3.6 atm similar to 3.5,you got any new plan sfor releases,it would be kwl if you could get achotjans green signal bar in there as he said you have his permission and also the samsung galaxy s type gingerbread battery icon,would look sexy and very gb
You can flash the Addon yourself if you like it i dont need to include it. The ROM Style will stay same, all Theme modifications the Users can flash themself like they want it becouse everyone likes different i wont touch the Theme, everyone can flash what they want becouse i cant make a Theme everyone will like becouse thats just not possible, some like Blue, some like Carbon.....
BTW this doesnt has something to do with this Thread so please keep it clean
Wolfbreak said:
You can flash the Addon yourself if you like it i dont need to include it. The ROM Style will stay same, all Theme modifications the Users can flash themself like they want it becouse everyone likes different i wont touch the Theme, everyone can flash what they want becouse i cant make a Theme everyone will like becouse thats just not possible, some like Blue, some like Carbon.....
BTW this doesnt has something to do with this Thread so please keep it clean
Click to expand...
Click to collapse
ok thanks
10 characters
Hopefully you can create flashable zip for us.
Thanks Wolfbreak!!
You can edit buildprop w the flashtool or w rootexplorer, depending on which rom you are running, some of these tweaks may already be implimented!!
Zip file is too easy!! Explore research have fun.... just make a back up first....
Best regards,
Chris
Sent from my X10 TripNMiUI-Iris using XDA App
Already did it manually using Flashtool and Root Explorer.
But for others who need quick progress, WB should create flashable zip for them.
AND
If can, maybe WB should consolidate addon such as Bravia Engine, FPS uncap, xLoud, Audio Fix, in one flashable zip.
Hi wolfbreak
I was changing the tweaks u had given
I was changing the below tweak
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
and i found that max num of touch was 4 instead of 2 by default.... does this mean anything?
2Wolfbreak : according to this http://www.linuxinsight.com/proc_sys_vm_oom_kill_allocating_task.html I wouldn't do this "echo 1 > /proc/sys/vm/oom_kill_allocating_task". Placing 0 performs better, and prevents some unexpected FCs.
awesome man.>!!!
Thats a good initiative I was thinking of starting something like this for past two day but was wait that some actual dev to start it and i will contribute more.
ohk so here are one or two simple tricks from my side.
those who don't want to mess with install-recover.sh and prefer keeping the init.d style work
here is how you can enable init.d support.
add one line at end of your install-recovery.sh
Code:
# trying run-parted
/system/xbin/busybox run-parts /system/etc/init.d
some more tweaks which might overlap with the existing tweaks posted here...
http://forum.xda-developers.com/showthread.php?p=16441133#post16441133
Note : as usual non of the credit to me all credit to Dev's.
Request
Can someone point all guides of framework customization and howtos related to that at one place.
stuff like replacing the background image to adding a reboot option and simmilar stuff.
all links at one place would be just fine for new dev's (don't get angry if its already there and i missed it, coz there are chances of it too...)
So what do these tweaks actually do?
*improve* your phone will be the sarcastic answer, but forgive me if I won't blindly apply tweaks without having at least some idea as to what they are doing?
anantshri said:
Can someone point all guides of framework customization and howtos related to that at one place.
stuff like replacing the background image to adding a reboot option and simmilar stuff.
all links at one place would be just fine for new dev's (don't get angry if its already there and i missed it, coz there are chances of it too...)
Click to expand...
Click to collapse
If u need help PM me.
blueowl0708 said:
So what do these tweaks actually do?
*improve* your phone will be the sarcastic answer, but forgive me if I won't blindly apply tweaks without having at least some idea as to what they are doing?
Click to expand...
Click to collapse
That's actually a good question i will see what i can help you with then later on other remaining could be answered by otheres.
# Product
HTML:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
This tweak is basically a build.prop tweak which is making system aware of a dual touch capable system.
# Performance
HTML:
dalvik.vm.startheapsize=64m
dalvik.vm.heapsize=64m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-flags=m=y
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=150
windowsmgr.max_events_per_sec=80
These are basically VM related tweaks first making heapsize 64M i.e. larger default is smaller. also this last line makes your system more responsive i keep something higher then 250 in place of 80.
VM Tweaks
HTML:
echo 95 > /proc/sys/vm/dirty_ratio
echo 20 > /proc/sys/vm/vfs_cache_pressure
echo 4096 > /proc/sys/vm/min_free_kbytes
echo 1 > /proc/sys/vm/oom_kill_allocating_task
echo 60 > /proc/sys/vm/dirty_background_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 2000 > /proc/sys/vm/dirty_writeback_centisecs
VM Tweaks basically change min free bytes and kill level's of application used internally by android for memory management.SD Card Tweak
HTML:
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo 2048 > /sys/devices/virtual/bdi/default/read_ahead_kb
This is a simple tweak which specifies the read ahead buffer which is by default 128Kb effectively making your SDCard i/o faster.
Hope these could clarify your doubts remaining ones wolf or others might give a try to explain.
a flashable zip file would be nice
ive been trying to place my own tweaks within the install-recovery.sh file however when i flash zip the file seems to have changed however nothing actually takes effect. new to this side of things so could just be a schoolboy error lol. can say if i use the simple install-recovery.sh file from Z's uncap fps or even yours from your rom and flash it.. it all works well! if i try to edit any of yours and flash again.. nothing happens! wat am i missing?
KERNEL FOR SM-N9005 - SNAPDRAGON 800 MODEL
Successfully changed SELinux status to permissive. Able to restore apps with Titanium Backup with data without force closes.
This is the stock samsung kernel source, but changed the SELinux policy from enforcing to permissive.
In the settings app, it still shows as "Permissive", see the attached image.
Flash at your own risk. Please have an available flashable tar file of a working boot.img just in case, however it works fine on my phone!
Link to stock kernels: http://forum.xda-developers.com/showthread.php?t=2459328&highlight=stock+roms
Known Issues
Wifi and exfat external storage not working
WiFi not working. To fix: modify build.prop ro.securestorage.support=true - Change to false. WiFi works on reboot (Thanks to freeza)
ExFAT external storage not working. To fix: Use https://github.com/dorimanx/exfat-nofuse
Download Here: https://www.dropbox.com/s/8ze2xzk2mcbagyc/DJT_N9005_KERNEL.tar
TODO:
- Add ExFAT to kernel
- Add Busybox / init.d capability
- Add CPU overclocking
For other kernel devs, there is new feature in Snapdragon 800 mtd where you need a different version of mkbootimg tools.
More Information
Some more info:
In the build config specified by Samsung, there is the following:
Code:
CONFIG_SEC_RESTRICT_ROOTING=y
CONFIG_SEC_RESTRICT_SETUID=y
CONFIG_SEC_RESTRICT_FORK=y
CONFIG_SEC_RESTRICT_ROOTING_LOG=y
And the build notes for the kernel say this:
$ make VARIANT_DEFCONFIG=msm8974_sec_hlteeur_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
And if we look at the SELINUX Makefile:
Code:
ifeq ($(SEC_BUILD_OPTION_SELINUX_ENFORCE),true)
EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true
endif
My guess is that because we are "supposed" to build with the SELinux flag, then the Makefile picks this up and sets ALWAYS ENFORCE to true. So I am now rebuilding kernel now to try it without that line.
it dose not work on my stock rom
After flashing over Omega ROM 1.0 i lost WIFI (could not activate it) and external storage access.
Still SELinux was indeed permissive and data restore with Titanium was working.
bubbl3 said:
After flashing over Omega ROM 1.0 i lost WIFI (could not activate it) and external storage access.
Still SELinux was indeed permissive and data restore with Titanium was working.
Click to expand...
Click to collapse
Thankyou I will look at fixing this. I also realised lost wifi.
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
Thankyou I will look at fixing this. I also realised lost wifi.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Woa, how can you able to flash kernel with locked bootloader ?, how do i create tar and boot.img from the zImage ?
Thanks
rheza02 said:
Woa, how can you able to flash kernel with locked bootloader ?, how do i create tar and boot.img from the zImage ?
Thanks
Click to expand...
Click to collapse
boot.img consists of the kernel and ramdisk. You need ramdisk compiled from source, or ripped from a current working boot.img.
Then use tool mkboot to package zImage and ramdisk into boot.img (not just any mkboot, there is a special one updated for usage with snapdragon 800).
Then just use tar command in linux: tar -cvf mykernel.tar boot.img
Then flash in odin
Does this work with SM-N900W8 version?
Sorry for Out of topic,
do you compile the boot.img with the dt.img ?
Thanks
rheza02 said:
Sorry for Out of topic,
do you compile the boot.img with the dt.img ?
Thanks
Click to expand...
Click to collapse
Yes...
Use this:
https://github.com/xiaolu/mkbootimg_tools
Can you please do it for SM-900 version also ?
Sent from my SM-N900 using XDA Premium 4 mobile app
How do we make the modules for wifi and external storage ?, I able to compile my own kernel now. but can't access external storage and wifi.
rheza02 said:
How do we make the modules for wifi and external storage ?, I able to compile my own kernel now. but can't access external storage and wifi.
Click to expand...
Click to collapse
I'm wondering the same thing brother. I want to open a thread regarding kernel compiling but don't know where to do it or where to get help. Feel so stuck.
Then my dev environment died on me and make started throwing me errors randomly after I did apt-get upgrade.
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
I'm wondering the same thing brother. I want to open a thread regarding kernel compiling but don't know where to do it or where to get help. Feel so stuck.
Then my dev environment died on me and make started throwing me errors randomly after I did apt-get upgrade.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Do you have google+ ?, can we chat while doing this. hehe!
rheza02 said:
Do you have google+ ?, can we chat while doing this. hehe!
Click to expand...
Click to collapse
Yeah I will send you a PM
Hi, I'm in the same boat as you guys. I have compiled a kernel successfully and while WiFi works, sdcard/exfat doesn't.
We need to figure out how to get to the bottom of this! Oddly enough, kernel modules are no longer in /system/lib/modules. I guess they're baked into the kernel?
feel free to add me on google+. my xda username @ gmail
freeza said:
Hi, I'm in the same boat as you guys. I have compiled a kernel successfully and while WiFi works, sdcard/exfat doesn't.
We need to figure out how to get to the bottom of this! Oddly enough, kernel modules are no longer in /system/lib/modules. I guess they're baked into the kernel?
feel free to add me on google+. my xda username @ gmail
Click to expand...
Click to collapse
How did you get wifi working???
Sent from my SM-N9005 using xda app-developers app
And what about Exynos kernel?
Code:
parentDir
|-- mkbootimg
|--/XXDEV-ramdisk/
+--/Kernel-folder/
Code:
makeKernel
Code:
#!/bin/sh
export KDIR=`readlink -f ../Kernel-folder/`
if [ -z ${1} ]; then
echo "Enter the device code"
exit 1;
else
export DEV=$1
fi
case $DEV in
XXDEV) export DEFCONFIG="XXDEV_defconfig";
export RDIR="XXDEV-ramdisk";;
*) echo "Not a valid device"
exit 2;;
esac;
cd $KDIR;
echo "Making $DEFCONFIG";
if [ -z $3 ]; then
make $DEFCONFIG ARCH=arm || exit 3;
nice -n 10 make modules -j4 ARCH=arm || exit 4;
nice -n 10 make -j4 ARCH=arm || exit 5;
else
echo "Bypassing kernel make."
fi
find -name '*.ko' -exec cp -av {} ../$RDIR/lib/modules/ \;
chmod 644 ../$RDIR/lib/modules/* ;
cd ..;
cd ./$RDIR
pwd;
find . | cpio -o -H newc | gzip -9 > ../$RDIR.cpio.gz
cd ..
./mkbootimg --kernel $KDIR/arch/arm/boot/zImage --ramdisk $RDIR.cpio.gz -o boot.img && echo "Made boot image."
tar cf ./Finished/Kernel-$2-$DEV.tar boot.img
echo "Made Kernel-$2-$DEV.tar"
exit 0;
Code:
parentDir/makeKernel XXDEV whateverVersionNumber
Now stop pestering me, I'm not a helpdesk. All of the above is easily found if you search for it.
I've managed to fix both sdcard(EXFAT) and WiFi
THIS IS A SCRIPT TO HAVE SWAP AND NOT A ROM!
I tested the swap on "CM10.x" by volk204 but there isn't a reason it shouldn't work on other rom versions.
version 1.0 13/11/2013 18:29 GMT+2
I experienced some lag with my wave due to its low ram memory. So after testing a few things i found myself more comfortable with setting up swapfile on sd card(NAND memory); after few minutes this terminal becomes really smooth. (It strangely is faster than setting it up on the phone memory, atleast for me)
The idea is mine, but checking around i found that many other script were made. I got the sleep line to boot part idea from "Defiant07 @ XDA" (http://forum.xda-developers.com/showthread.php?t=2359182). Everything else (as simple it is it's all mine)
Swap is the *nix term for virtual memory, that maybe many are familiar with on windows.
You set up a partition/file and use that as virtual memory. It will be much slower than real ram, but it will be much faster than reloading everything from disk everytime.
Code:
#!/system/bin/sh
# This script was authored by Defiant07 @ XDA. If you use/redistribute it, eve$
# Thanks to zeppelinrox most of all, but also many thanks to dk_zero-cool & gu5$
# Much thanks to pikachu01 @ XDA for permission to use the sysctl tweaks from T$
# Read Karl Marx!
# Nearly entirely modified by skyglow
swapfile="/storage/sdcard0/swapfile"
#swapsize in KB
swapsize=524288
swappiness=90
vfs_cache_pressure=100
dirty_background_ratio=5
dirty_ratio=20
dirty_writeback_centisecs=500
dirty_expire_centisecs=200
while [ ! "`ps | grep -m 1 [a]ndroid`" ]; do sleep 10; done
if [ ! -f "$swapfile" ]; then
dd if=/dev/zero of=$swapfile bs=1024 count=$swapsize
mkswap $swapfile
fi
# sleep 30
# mkswap $swapfile
swapon $swapfile
busybox sysctl -e -w vm.swappiness=$swappiness
busybox sysctl -e -w vm.vfs_cache_pressure=$vfs_cache_pressure
busybox sysctl -e -w vm.dirty_background_ratio=$dirty_background_ratio
busybox sysctl -e -w vm.dirty_ratio=$dirty_ratio
busybox sysctl -e -w vm.dirty_writeback_centisecs=$dirty_writeback_centisecs
busybox sysctl -e -w vm.dirty_expire_centisecs=$dirty_expire_centisecs
exit 0
Requirements
Superuser rights on terminal to change permission and copy this file
Configuration
1) set up "swapfile" field to where you want your swap
2) set up "swapsize" field to an appropriate value in KB! ( i think you should try values over 307200 => 300MB to have performance improvements)
(SD or NAND version)
SD version
size=512 MB
position=sdcard root
NAND version
size=300MB
position=bada application partition
How to install
1) Download the right zip from this page
2) Extract the file from the zip
3) Upload the file in some way on the phone
4) Become superuser
5) move it to "/system/etc/init.d"
6) this file should keep hits name "99myswap"
7) change permissions of "99myswap" to 755
8) change its rights to "root:shell"
9) done, next reboot your swap will be set up automatically
P.S.
How to check if swap is activated:
Open terminal
cat /proc/swaps
Swap filename should be displayed with the right size
[ADDED DEBUG SCRIPT]
Possible problems
1) System hangs on cyanogen loading screen ( rotating circle)
INVESTIGATING
2) Battery charge lasts less.
Any kind of virtual memory use more electrical power to perform write/read on disk (SD). This is a side effect of swap.
3) File format
*NIX file format is LF and not CR-LF (for reference why this happens http://en.wikipedia.org/wiki/Newline#Representations)
You can't edit the file with windows notepad, but use something else such as notepad++ and save it in LF coding.
4) System is slower
Possible causes are:
a) you have applications on the same filesystem where you placed the swap
b) your memory (such as SD card) is too slow. Swap will work, it will just go much slower. Try it with a better sd. I tested it with a class 4 and class 10 sdcard and they both speed up. I don't have any possibility at the moment to test a class 2. (reference http://en.wikipedia.org/wiki/Secure_Digital#Speeds)
5) How to change permissions (thanks Eltjo for copy paste from your answer)
Open terminal
Type: su
Type: cd /system/etc/init.d
Type: chmod 0755 99myswap
Type: chown root:shell 99myswap
6) zRam
On my mobile it's faster if i disable zRam from Settings > Performance > Memory Management > zRam .
Anyway i think outcome may change. Try both solutions.
could be possible to use free nand memory as swap instead of sd card?
cfernr said:
could be possible to use free nand memory as swap instead of sd card?
Click to expand...
Click to collapse
I added the NAND version that installs itself in the bada partition. If you installed the sd version remember to remove the swapfile.
darklight2k2 said:
I added the NAND version that installs itself in the bada partition. If you installed the sd version remember to remove the swapfile.
Click to expand...
Click to collapse
lets try both, thank you very much
no problem.
DEBUG REQUEST
Who had the loading screen on cyanogen circle may tell me which sd card class have?
The following procedure do not install the script, it just will work till reboot.
may them try to upload the script in a generic directory such as /storage/sdcard0 and execute it with
su
cd /storage/sdcard0
sh ./99myswap
I'd like the output of that command and the resulting /proc/swaps
then use the phone, (play/call/charge/reboot)
next boot start the script again please and tell me the resulting /proc/swaps again
Thank you for the help
seems work on my phone.
installed swapfile on nand and ram increased 30mb, but low improvement in real performance.
need to change zram options, but cant find this on my phone, maybe due to language discrepancy. can you explain better?
thank you a lot
I also cannot find zram a options under B.U.X V3.1 (4.3.1 CM10.2) by Tigrouzen
If you don't have the menu for zRam it's disabled by default. To see it you should enable all developer settings.
Settings > About phone > Build number (tap 7 times)
Some more tweaks will unlock.
saltcushy said:
I also cannot find zram a options under B.U.X V3.1 (4.3.1 CM10.2) by Tigrouzen
Click to expand...
Click to collapse
Unfortunally i didn't test that rom yet but i think the procedure above will work.
darklight2k2 said:
If you don't have the menu for zRam it's disabled by default. To see it you should enable all developer settings.
Settings > About phone > Build number (tap 7 times)
Some more tweaks will unlock.
Unfortunally i didn't test that rom yet but i think the procedure above will work.
Click to expand...
Click to collapse
tested and I have to say this is necessary if you want to enjoy a few extra mb in this phone.
I recommend nand swap because everybody have 300-400 unused mb in bada apps partition.
disabling zRAM seems also recommendable.
I hope everybody take care of this script for future ROM releases
*** I will decrease swappiness to 70 or 60, I think it is enough.
darklight2k2 said:
no problem.
DEBUG REQUEST
Who had the loading screen on cyanogen circle may tell me which sd card class have?
The following procedure do not install the script, it just will work till reboot.
may them try to upload the script in a generic directory such as /storage/sdcard0 and execute it with
su
cd /storage/sdcard0
sh ./99myswap
I'd like the output of that command and the resulting /proc/swaps
Thank you for the help
Click to expand...
Click to collapse
i've a samsung class 10 32gb.
i've not run the script with sh command, just copied it to /system/etc/init.d (aplied chmod and chown) and reboot the phone. after that it hangs on CM circle on first boot and have to re-install the rom. wipe data/factory reset didn't help.
best regards
JonasVFC said:
i've a samsung class 10 32gb.
i've not run the script with sh command, just copied it to /system/etc/init.d (aplied chmod and chown) and reboot the phone. after that it hangs on CM circle on first boot and have to re-install the rom. wipe data/factory reset didn't help.
best regards
Click to expand...
Click to collapse
To try to solve it i need to know what happens when executed with the sh command
darklight2k2 said:
To try to solve it i need to know what happens when executed with the sh command
Click to expand...
Click to collapse
after installing the rom again it can boot the first time but hangs on the second like everybody else
running with sh it runs ok
JonasVFC said:
after installing the rom again it can boot the first time but hangs on the second like everybody else
running with sh it runs ok
Click to expand...
Click to collapse
that's why i said not install in the problem request
problem is with chown, just run the chmod 755. didn't run chown command last time and it booted second and third time
edit: nevermind, it hanged again
darklight2k2 said:
that's why i said not install in the problem request
Click to expand...
Click to collapse
i did it with 2 different ways....with a fresh install between and both hang
JonasVFC said:
i did it with 2 different ways....with a fresh install between and both hang
Click to expand...
Click to collapse
You're just posting and posting what happens but not what i asked you to do to five me information.
darklight2k2 said:
You're just posting and posting what happens but not what i asked you to do to five me information.
Click to expand...
Click to collapse
i did what you asked, read again, i ran it with sh: it runs fine!! creates the swapfile and outputs some parameters that are in the script like swapiness and others....
JonasVFC said:
i did what you asked, read again, i ran it with sh: it runs fine!! creates the swapfile and outputs some parameters that are in the script like swapiness and others....
Click to expand...
Click to collapse
Hi, @JonasVFC.
I understand you've been running the Swap version of Android v2.1 Volk204. How do you get it?.
Yo, if I install the file in the directory 99myswap indicating the first page, but I get that the system does not start, stays on constantly CM logo.
A greeting.
chapito said:
Hi, @JonasVFC.
I understand you've been running the Swap version of Android v2.1 Volk204. How do you get it?.
Yo, if I install the file in the directory 99myswap indicating the first page, but I get that the system does not start, stays on constantly CM logo.
A greeting.
Click to expand...
Click to collapse
May you guys try the following attached file please?
when it hangs may you post the logfile created in the phone directory ( you can get it from bada)
Q&A for [ROM] Gohma 2.0 - 12/15/2014 [Android Wear]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Gohma 2.0 - 12/15/2014 [Android Wear]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Alynna said:
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Click to expand...
Click to collapse
I'll have a fix shortly, sorry!
Alynna said:
It appears that the vibration and other settings are not active in Gohma 2.0
From my research it seems that the /system/etc/rc.d/01tweaks file never gets to run.
I have been messing around with my watch to find a place to trigger execution of that directory but haven't found one yet.
Where did you put an initialization for it last time?
Click to expand...
Click to collapse
The init.d/rc.d directories seem to be run from the /system/etc/install-recovery.sh file. Look there and you should see the run-parts command. Which btw okibi, is ingenious, using the stock recovery script to provide init.d support in the face of a kernel that doesn't support it natively.
What software compilation are using Gohma 2.0? I´ve been testing and I have the corrosion problem with a Lg G watch (1,4 volts between pins while being out of the charger), perhaps the base isn´t a "finished-on-Y" compilation?
Nice work, 0 lag everywhere!
Bootloop
While I was running the windows installation to upgrade to 2.0, the program crashed, and the rom is stuck in a bootloop. I can boot into fastboot, and the recovery, but nothing. Any help?
tharrllz said:
While I was running the windows installation to upgrade to 2.0, the program crashed, and the rom is stuck in a bootloop. I can boot into fastboot, and the recovery, but nothing. Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54250887
Toolkit should work to get back to stock lollipop.
Still a bug
There is still a little bug in gohma 2.1, but I fixed it in the script.
SOMETHING sets the governor back to userspace/787200 about a minute into the watches' boot.
I logged in and watched it occur.
However the other parameters now stick.
I fixed it with the following:
#!/system/bin/sh
/system/xbin/sysrw
##############################
# BEGIN CUSTOM USER SETTINGS #
##############################
# increase vibration intensity
# default is 80
echo 85 > /sys/class/timed_output/vibrator/amp
# default is 20
echo 175 > /sys/class/timed_output/vibrator/driving_ms
# switch from userspace to ondemand governor
# echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# Defer change until later, see enforcer below.
GOV=ondemand
FREQ=1094400
# set dpi (default is 240, smaller number means smaller text)
setprop ro.sf.lcd_density 200
##############################
# END CUSTOM USER SETTINGS #
##############################
# improve sd cache
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi
# improve block speed
for node in `busybox find /sys -name nr_requests | grep mmcblk`; do echo 1024 > $node; done
# gpu rendering
busybox mv /system/lib/egl/libGLES_android.so /system/lib/egl/libGLES_android.bak
busybox sed -i '/0 0 android/d' /system/lib/egl/egl.cfg
# adjust minfree
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
# improve file system mounts
busybox mount -o remount,noatime,nodiratime,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /
busybox mount -o remount,noatime,nodiratime,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /sys
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /system
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /data
busybox mount -o remount,noatime,nodiratime,nodelalloc,noauto_da_alloc,data=ordered,nobh,barrier=0 -t auto /cache
# improve transitions
if [ -e /data/data/com.android.providers.settings/databases/settings.db ]; then
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 0.5 where name = 'transition_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 0.5 where name = 'animator_duration_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update system set value = 1 where name = 'window_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 0.5 where name = 'transition_animation_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 0.5 where name = 'animator_duration_scale'"
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update global set value = 1 where name = 'window_animation_scale'"
fi
# enable sysctl tweaks
busybox sysctl -p /system/etc/sysctl.conf
/system/xbin/sysro
# Wait around for the system to change the governor and change it back, then exit when we're sure its set.
# This function will remain running for a minute to enforce the change, until it's sure the system won't change it back.
enforcer () {
X=0
while [ $X -lt 12 ]; do
if [ ! `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor` = $GOV ]; then
echo $GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $FREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
X=0
else
X=$(($X+1))
fi
sleep 5
done
unset X
}
enforcer &
Alynna said:
There is still a little bug in gohma 2.1, but I fixed it in the script.
SOMETHING sets the governor back to userspace/787200 about a minute into the watches' boot.
I logged in and watched it occur.
However the other parameters now stick.
I fixed it with the following:
Click to expand...
Click to collapse
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
myke66 said:
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
Click to expand...
Click to collapse
I log into the phone using:
adb shell
and check that the /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor remains 'ondemand'.
I noticed when I logged in with gohma 2.0 and 2.1, that this would get switched back to 'userspace' after a little less than a minute.
I'm not sure the 01tweaks file was even executed in 2.0. Definitely is executed in 2.1, but, something else in the system was changing the scaling settings back to defaults.
if its not working, the file above will be 'userspace', if it does, it is 'ondemand'.
Also, I have set my default top speed to 1.0ghz which is why wear launcher is probably snappier. This MAY have an impact on battery life, but probably not too much because the watch remains at about 300mhz whenever idle.
You can check /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies for valid values for the FREQ variable. Lower numbers probably mean marginally better battery life.
myke66 said:
I reinstalled using your additional governer tweak, is there any way to check and make sure its working? Seems to have made a noticeable improvement, it reduces some random lag i was getting with Wear Mini Launcher
Click to expand...
Click to collapse
A handy utility that you can sideload on our watch is PerfMon by Chainfire:
http://forum.xda-developers.com/showthread.php?t=1933284
If your frequency fluctuates from 300 to 1190, then you are on ondemand governor.
---------- Post added at 12:19 PM ---------- Previous post was at 11:50 AM ----------
Alynna,
Thanks for the enforcer mod. For some reason after installing your mod, the governor was still on userspace/787200. After playing around I changed sleep from 5 to 10 and now it works great.
:good:
The standard 5.0 ROM version has a new sleep function that turns off the watch display if it hasn't moved for 30 minutes. This is driving me nuts as I always put my watch next to my monitor while I'm working so I have to keep waking it up or I miss notifications.
Is this "feature" in this ROM and if so, is there any way to turn it off or extend the timeout ?
Thanks
i'm looking at the rom and kernel.
the kernel looks like it has more option/tweaks.
i know both dont work together a bit normal cause the rom is a bit the same it are tweaks and no visual changes
i think kernel looks better. in way of functions.
just this rom has also more cpu steps? 300-1.1ghz?
cause if im right stock just is locked on 778mhz? and even with wear control app seems like i can't change it (i mean i don't realy know cant see if power save or balanced governers do any thing). need to check with a app how fast my cpu is running.
This ROM had been great! One question: Does the reset option in the watch settings properly reset and keep gohma tweaks? I tend to flash allot of ROMs on my phone and have been flashing my watch back to stock then each time as well as reflashing gohma. Stock recovery here. See no real reason for custom when everything is done using adb and computer.
Nandrew said:
This ROM had been great! One question: Does the reset option in the watch settings properly reset and keep gohma tweaks? I tend to flash allot of ROMs on my phone and have been flashing my watch back to stock then each time as well as reflashing gohma. Stock recovery here. See no real reason for custom when everything is done using adb and computer.
Click to expand...
Click to collapse
Yup. Just reset between phone ROM flashes.
Any update or thoughts on if we can find a way to make this ROM stop pumping out the 1.74 volts to our wrists via the metal contacts? Just discovered the whole issue of corrosion via the voltage emitted from the watch while being worn. I checked mine, running this ROM, and sure enough: it's live. 1.74 volts of electricity going into your wrist while you wear this thing. LG claims to have sent out a software fix a while back.
Thanks for the development & work on this ROM! Hopefully an "ah-ha" moment can be had and get this issue solved!
To think some people actually pay to have electricity run thru their body.. LG didn't consider it a feature? Lol
No corrosion here.
Gohma 2.2 - NEED DOWNLOAD
Jake's site to download the rom seems to be acting up. The download is extremely slow and keeps failing. I am in desperate need of this excellent ROM!! Does anybody have an alternate download link for Gohma 2.2? Any help is greatly appreciated.
Quick question? Installed 2.2 and everything runs fine except Perfmon only shows one core active. If I run the adb script I can turn the others on but for some reason by default one one core is up after a reboot. Any help.
kwd114kwd114 said:
Quick question? Installed 2.2 and everything runs fine except Perfmon only shows one core active. If I run the adb script I can turn the others on but for some reason by default one one core is up after a reboot. Any help.
Click to expand...
Click to collapse
The 01tweaks script on 2.3 didn't work for me either. Ondemand and frequency are correctly set, but only one core. Couple of workarounds:
1. Set the cores directly using adb commands from your PC.
2. Sideload kernel adiutor from the play store (nice kernel tuner app that works on our watch, dev is active on XDA)
3. Or modify the 01tweaks script to set the cores within the enforcer part of the script (right after $GOV and $FREQ are set)
Code:
# Wait around for the system to change the governor and change it back, then exit when we're sure its set.
# This function will remain running for a minute to enforce the change, until it's sure the system won't change it back.
enforcer () {
X=0
while [ $X -lt 12 ]; do
if [ ! `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor` = $GOV ]; then
echo $GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $FREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1" > /sys/devices/system/cpu/cpu1/online
X=0
else
X=$(($X+1))
fi
sleep 5
done
unset X
}
enforcer &
Hello! After many years without development, today I'm sharing a new kernel with ZRAM and swap support for this device.
The kernel is based upon weritos' Cyanogenmod 13 kernel source code and should work on both rev. 1 and rev. 2 devices.
Installation procedure is as follows:
1. Download the latest TWRP, kernel build and modules.
2. Install the kernel and TWRP from ADB shell (the device must be booted into Android) or a terminal app:
Bash:
su (from a terminal app; not required from ADB shell)
cat </path/to/TWRP_image> > /dev/block/mmcblk0p13
cat </path/to/kernel_image> > /dev/block/mmcblk0p8
reboot recovery
3. Install the kernel modules:
Bash:
mount /dev/block/mmcblk0p21 /system
unzip -o </path/to/modules.zip> -d /system/lib/modules
4. Done! Reboot into Android.
NOTE: The < and > symbols should never be issued within the commands!
Version Information
Status: Beta (Bluetooth, camera recording and screen recording do not work.)
Created: 2021-05-11
Last Updated: 2021-05-12 (Import and enable Ultra KSM driver.)
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
@Krush206 it's saying can't open zip file on the last step, how to fix??
SerjSX said:
@Krush206 it's saying can't open zip file on the last step, how to fix??
Click to expand...
Click to collapse
fixed it, I was supposed to write:
Code:
unzip -o /sdcard/modules.zip -d /system/lib/modules
instead of:
Code:
unzip -o /storage/emulated/0/modules.zip -d /system/lib/modules
in TWRP terminal.
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not. @Krush206
not working
Turkish developers said:
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
Click to expand...
Click to collapse
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
SerjSX said:
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not.
Click to expand...
Click to collapse
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Krush206 said:
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Click to expand...
Click to collapse
Hi, thanks for your response. Just did i and looks like it worked, 59 total swap, used 58, and free 541.
Are you sure you checked the correct line? The total should be 255 (256), not 59.
can you compile a kernel for overclocking in stock room or cm 11 please our quttro needs it now
overclock kernel pls
Sorry for the delay. The battery of my device has swollen, so I cannot really check whether overclocking is possible or not.
However, though overclocking may be possible, it may cause system instability and crashes.
I could probably have a look at the code and see how to get it done, but I cannot post results and would not recommend overclocking.
The battery in my device was swollen, I found a battery and the best software for this device is 4.1.2. I want to try overclocking for this version. Bide 4.1.2 also does not play hd videos in the original software. Is there a code or a mod for this?
1.5 Ghz overclock pls
any update?
If you two, @Fever070720, @Turkish developers, are still looking into overclocking, please, send the output of the following command:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq