Develop Bugs

Disabling compcache on MCR 3.1 ?

How would i disable compcache on modaco custom rom 3.1 without using the kitchen?

Edit your /system/init.d/ramzswap.sh and comment out the following lines (by putting a "#" sign in front of them.)
Once your file is edited, it should look like this:
Code:
/system/xbin/insmod /system/lib/modules/tun.ko
#/system/xbin/insmod /system/lib/modules/lzo_decompress.ko
#/system/xbin/insmod /system/lib/modules/lzo_compress.ko
#/system/xbin/insmod /system/lib/modules/xvmalloc.ko
#/system/xbin/insmod /system/lib/modules/ramzswap.ko disksize_kb=131072
#/system/xbin/swapon /dev/block/ramzswap0
#echo "10" > /proc/sys/vm/swappiness
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Once you've saved the file, reboot your phone and you're good.

I tried doing the same thing. I commented out those exact lines and when I reboot it shows I still have a swap file, just half the size it was before. Huh?

Help with init.d script

I'm trying to tweak my smartass governor settings at boot via an init.d script & sysfs, but everytime I reboot the settings don't take effect. If I run it in the terminal it works fine and sticks, just not at boot. Any ideas why? The permissions are set right. Does the governor get loaded after init.d and overwrite my settings with default? Here's my script.
#!/system/bin/sh
echo "998000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sleep_wakeup_freq
echo "614400" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sleep_max_freq
echo "2" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sample_rate_jiffies
echo "128000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
echo "40" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/min_cpu_load
echo "65" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/max_cpu_load
echo "30000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/awake_min_freq
Sent from my PC36100 using Tapatalk

Usually the init scripts will set the governor to ondemand after the init.d scripts are ran. You'll have to unpack the boot.img and look through them to see where it is being set.

Damn. So something I can't do from my phone while laying in bed at 6am. I'll rip it from my phone and tear it apart tomorrow and find it. Thanks!!
Sent from my PC36100 using Tapatalk

finadil said:
Damn. So something I can't do from my phone while laying in bed at 6am. I'll rip it from my phone and tear it apart tomorrow and find it. Thanks!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
you could have the script spawn another one that waits for it to change the governor and then changes it back, not as clean but it would work without having to modify the boot.img.

Its not so much changing the governor as tweaking its default values. I was feeling lazy so I took the latest sz kernel (which is what I use), extracted it, edited its init scripts so it uses SA as default and my values rezipped and flashed (so it'd mkbootimg). It boots using SA but again its using its own defaults. Guess the only options are recompiling the source with edited values or a post load script?
Sent from my PC36100 using Tapatalk

Try this
Btw, you'll have issues with your rampup step. It has to be a multiple of 38400. So 115200.
Code:
#!/system/bin/sh
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/smartass/sleep_max_freq ];
then
echo "998000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sleep_wakeup_freq
echo "614400" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sleep_max_freq
echo "2" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/sample_rate_jiffies
echo "128000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
echo "40" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/min_cpu_load
echo "65" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/max_cpu_load
echo "30000" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/awake_min_freq
fi;

[Q] enabling/disabling USB from console ?

Hi,
Does anyone know how i can enable/disable USB functions from a terminal emulator?
i have tried:
Code:
echo 0 > /sys/class/android_usb/android0/enable
to disable the driver completely, as well as
Code:
setprop sys.usb.config none
However /sys/class/android_usb/android0/enable is always 1 and /sys/class/android_usb/android0/functions is always mass_storage,adb (even when selecting "charge only") and the current state remains unchanged.
The phone is rooted, so permissions should not be a problem.

LG google stock Thefor G4

Woops Cant edit title now Lol.
Anyway, with the system img changing thing for BL locked users, would it be possible to modify a system img and create some sort of stock theme?

If you have access to the Send Command tools and you are running LP then you can modify the system.img.

Also on MM is possible to change things on system partition with send command.

ObiDanKenobi said:
Also on MM is possible to change things on system partition with send command.
Click to expand...
Click to collapse
I think i might start learning how and how to modify stock apps and etc, cus i really want a Google Stock theme for our device, on BL lock, like the G2 has a theme (Although its a rom, but its from where i got the idea)

Someone has done exactly that here: http://forum.xda-developers.com/g4/orig-development/bl-lock-ul-android-6-0-marshmallow-t3459260. They used another theme though
Trimis de pe al meu LG-H815 folosind Tapatalk

ObiDanKenobi said:
Someone has done exactly that here: http://forum.xda-developers.com/g4/orig-development/bl-lock-ul-android-6-0-marshmallow-t3459260. They used another theme though
Trimis de pe al meu LG-H815 folosind Tapatalk
Click to expand...
Click to collapse
Yeah, I'm using that lol
it gave me the idea that maybe its possible to bring back one of the best themes on the G2, really, that theme was amazing.
Anyone wants to work with me on this?
Anyway, this is the theme i want to make for the G4:
http://forum.xda-developers.com/lg-g2/development-d802/rom-google-edition-release-thread-t3262929
(Unless someone that is actually good in this and is willing to risk his G4 does it before me lol )

And Crap i realised i cant do this anyway for two reasons:
1. H815L root injecting for 6.0 isn't possilbe
2. even if it were possible i have no Linux on my PC.
So rip this idea ;-;

You do not have to inject root. I changed for instance the parameters of the governor, getting a much smoother and battery friendly device.
I have no Linux machine either, I have a virtual machine running Linux where I do the dirty work.

ObiDanKenobi said:
You do not have to inject root. I changed for instance the parameters of the governor, getting a much smoother and battery friendly device.
I have no Linux machine either, I have a virtual machine running Linux where I do the dirty work.
Click to expand...
Click to collapse
Teach me the ways Sempai, pls.

Ha ha, that was a good one. I will lay out some steps, but you have to do the dirty work yourself:
First and foremost you have to have a linux (virtual) machine. Using that machine you will be able to
1. extract the system.img from your phone
2. you have to mount the img on the linux file system,
3. you copy the /system/init.qcom.post_boot.sh to your machine (or you edit in place with Linux)
4. at the end of the file you put the following code
# Added modifications by Dan
#
# IO for device and msd
# (switch to cfq sched, set read ahead
echo 256 > /sys/block/mmcblk0/bdi/read_ahead_kb
echo "cfq" > /sys/block/mmcblk0/queue/scheduler
echo 16 > /sys/block/mmcblk0/queue/iosched/back_seek_max
echo 512 > /sys/block/mmcblk1/bdi/read_ahead_kb
echo "cfq" > /sys/block/mmcblk1/queue/scheduler
echo 16 > /sys/block/mmcblk1/queue/iosched/back_seek_max
# Tuning Transmission Control Protocols.
echo "cubic" > /proc/sys/net/ipv4/tcp_congestion_control
echo 1 > /proc/sys/net/ipv4/tcp_timestamps
echo 1 > /proc/sys/net/ipv4/tcp_sack
echo 1 > /proc/sys/net/ipv4/tcp_window_scaling
#echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/boost
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
echo 1248000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time
echo 85 600000:70 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
echo 480000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate
echo 480000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif
echo 0> /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load
echo 384000 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
#echo > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration
echo 95 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load
echo 1824000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time
#echo 633600 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
echo 90 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads
echo 240000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate
echo 480000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load
# Adjust input parameters
echo 1 > /sys/module/cpu_boost/parameters/input_boost_enabled
echo 0:600000 1:600000 2:600000 3:600000 4:0 5:0 > /sys/module/cpu_boost/parameters/input_boost_freq
echo 0 > /sys/module/cpu_boost/parameters/boost_ms
echo 40 > /sys/module/cpu_boost/parameters/input_boost_ms
echo 0 > /sys/module/msm_performance/parameters/touchboost
5. you copy the file back (or you save if you edited in place).
6. you unmount the image from your linux system
7. you copy the system.img to your internal sd on the phone
8. you push the system.img the phone using send_command
9. profit.
that's it. As you can see there is not much to it

ObiDanKenobi said:
Ha ha, that was a good one. I will lay out some steps, but you have to do the dirty work yourself:
First and foremost you have to have a linux (virtual) machine. Using that machine you will be able to
1. extract the system.img from your phone
2. you have to mount the img on the linux file system,
3. you copy the /system/init.qcom.post_boot.sh to your machine (or you edit in place with Linux)
4. at the end of the file you put the following code
# Added modifications by Dan
#
# IO for device and msd
# (switch to cfq sched, set read ahead
echo 256 > /sys/block/mmcblk0/bdi/read_ahead_kb
echo "cfq" > /sys/block/mmcblk0/queue/scheduler
echo 16 > /sys/block/mmcblk0/queue/iosched/back_seek_max
echo 512 > /sys/block/mmcblk1/bdi/read_ahead_kb
echo "cfq" > /sys/block/mmcblk1/queue/scheduler
echo 16 > /sys/block/mmcblk1/queue/iosched/back_seek_max
# Tuning Transmission Control Protocols.
echo "cubic" > /proc/sys/net/ipv4/tcp_congestion_control
echo 1 > /proc/sys/net/ipv4/tcp_timestamps
echo 1 > /proc/sys/net/ipv4/tcp_sack
echo 1 > /proc/sys/net/ipv4/tcp_window_scaling
#echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/boost
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
echo 1248000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time
echo 85 600000:70 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
echo 480000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate
echo 480000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif
echo 0> /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load
echo 384000 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
#echo > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration
echo 95 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load
echo 1824000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time
#echo 633600 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
echo 90 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads
echo 240000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate
echo 480000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif
echo 0 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load
# Adjust input parameters
echo 1 > /sys/module/cpu_boost/parameters/input_boost_enabled
echo 0:600000 1:600000 2:600000 3:600000 4:0 5:0 > /sys/module/cpu_boost/parameters/input_boost_freq
echo 0 > /sys/module/cpu_boost/parameters/boost_ms
echo 40 > /sys/module/cpu_boost/parameters/input_boost_ms
echo 0 > /sys/module/msm_performance/parameters/touchboost
5. you copy the file back (or you save if you edited in place).
6. you unmount the image from your linux system
7. you copy the system.img to your internal sd on the phone
8. you push the system.img the phone using send_command
9. profit.
that's it. As you can see there is not much to it
Click to expand...
Click to collapse
Is possible to modify /system/init.qcom.post_boot.sh for disable the 2 big core or keep them to a low frequency on the system.img of MM?

Yes there is: you should add at the end of the file the following:
echo 0 > /sys/devices/system/cpu/cpu4/online
echo 0 > /sys/devices/system/cpu/cpu5/online
I missed the biggest opportunity to test this stuff, I was lazy and did not make a image with the cores disabled. Wednesday the phone went into bootloop, but now I have no way of copying the image into the internal storage to send it via send_command. After a couple of hours of trying to mount the sdcard in download mode, I gave up, and now the courier will pickup the phone to go to LG service center, as I have warranty.
I kept on asking some people how to change/create a tot file for these situations, but until now I got no info, so if the bootloop hits, you have to have the img file already on your internal storage. Even then, when the cores are disabled using post_boot.sh there is no guarantee that it will work, but I missed the chance to test this.

[Q]build.prop connect USB ?

Hello,
What command should be put in build.prop so that to the connection PC it passes directly on USB connection, and have direct mode developer.
Thank you in advance

Do you mean USB debugging?
If so, a quick google search results in this being your best bet:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop

Thank you,
But I have well these orders in build.pop!
But there is always by default charge battery and not USB connection!
(NB: I direct work in I compile of Roma, thus do not modify via ADB