Features
Google 3.4 base. All stock features are of course supported (camera, OTG, NFC etc.)
It's in the feature list but does it really work??
Up untill now there is no Kernel with working USB-OTG, and there are even specualtions that the hardware doesn't support ist at all.
im getting a yellowish screen with this kernel. will it disappear as time goes on?
It's in the feature list but does it really work??
Up untill now there is no Kernel with working USB-OTG, and there are even specualtions that the hardware doesn't support ist at all.
+1
Thank you to the previous poster who quoted the op, I already read that. But I wanted to know if anyone had any real life experience with it working. As this poster mentioned, I haven't heard of anyone who has it working.
Nothing has changed in the area of GPU, panel, color adjustments etc. Are you using some over method to control colors?
Good to see you back Motley! Just to report working great on Paranoid Android
View attachment 1524092
Sent from my Nexus 4 using Tapatalk 2
Interesting. That's faux's app right? I have been using System Tuner and the min/max look correct there as I would expect. I do see the min frequency jump up peridically in System Tuner due to the powerhal 1.026GHz on touch (project butter). Does faux's reset kernel replace the powerhal back to the stock version? I wonder if you have some conflicting pieces and parts after flashing his kernel and then this one. This kernel is much closer to stock than his and I have only tested with the stock powerhal library.
Good to see you back Motley! Just to report working great on Paranoid Android
View attachment 1524092
That would explain why SetCPU would jump to 1026 minimum (for project butter). Since the system will be at a higher minimum clock then the battery life is impacted correct?
https://play.google.com/store/apps/details?id=eu.chainfire.perfmon
Sent from my Nexus 4 using Tapatalk 2
Couldn't get to boot on cm, i thought i read it was compatible?
___
Sent from my Phone...
Couldn't get to boot on cm, i thought i read it was compatible?
___
Sent from my Phone...
Did you use the any kernel zip or the boot.img flash? The latter definitely won't work since the whole ramdisk is replaced with the aosp version. You should not need to repack if using the any kernel zip, at least one would hope they use the same ramdisk offset as stock. I will take a look later at the CM ramdisk if it doesn't work.
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
#!/system/bin/sh
# Show the current configuration and the checksum
cat /sys/devices/platform/mipi_lgit.1537/kgamma_red
cat /sys/devices/platform/mipi_lgit.1537/kgamma_green
cat /sys/devices/platform/mipi_lgit.1537/kgamma_blue
R: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
G: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
B: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
#!/system/bin/sh
# Set data color pro presets from shared Google spreadsheet (thanks user acer73!)
# Use LG presents as your starting values and then adjust columns 6 & 7 from the spreadsheet
echo "397 114 21 118 0 10 4 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "394 114 21 118 0 7 4 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "389 114 21 118 0 5 1 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
#Set the complimentary RGB values for this calibration
echo "248 248 248" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
echo 1 > /sys/devices/platform/mipi_lgit.1537/refresh_screen
#!/system/bin/sh
# Set LG presets (motley stock) - i.e. popular partial revert of Google's tweaks just before release
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
#!/system/bin/sh
# Set stock Google presets (from kernel source code)
echo "332 64 68 118 1 0 0 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "332 64 68 118 1 0 0 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "364 32 35 116 0 31 16 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
#!/system/bin/sh
# Set faux Google presets (not sure why his numbers differ)
echo "460 64 68 118 1 32 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "461 64 68 118 1 33 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "445 32 35 116 0 32 96 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 1 > /sys/kernel/fast_charge/force_fast_charge
echo 0 > /sys/kernel/fast_charge/force_fast_charge
/sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
/sys/devices/system/cpu/cpufreq/interactive/input_boost
/sys/module/msm_thermal/parameters/throttle_temp
/sys/module/msm_thermal/parameters/min_freq_index
/sys/module/msm_thermal/parameters/thermal_debug
/sys/module/auto_hotplug/parameters/debug
/sys/module/auto_hotplug/parameters/disable_load_threshold
/sys/module/auto_hotplug/parameters/enable_load_threshold
/sys/module/auto_hotplug/parameters/enable_all_load_threshold
/sys/module/auto_hotplug/parameters/min_sampling_rate
/sys/module/auto_hotplug/parameters/sampling_periods
/sys/module/auto_hotplug/parameters/max_online_cpus
/sys/module/auto_hotplug/parameters/min_online_cpus
echo "90" > /sys/class/timed_output/vibrator/amp
echo "70" > /sys/class/timed_output/vibrator/amp
adb shell dmesg | grep PVS