I don't know if it is the ROM or kernel issue but on cm10.1 linaro built I seem to be getting major slowdowns ever since b37. Would run great for about 8 hours or so, then it starts feeling choppy. Recents button would take good 4-5 seconds to bring app list, notification drawer feels laggy as well.
Sent from my Nexus 4 using xda app-developers app
I don't know if it is the ROM or kernel issue but on cm10.1 linaro built I seem to be getting major slowdowns ever since b37. Would run great for about 8 hours or so, then it starts feeling choppy. Recents button would take good 4-5 seconds to bring app list, notification drawer feels laggy as well.
Sent from my Nexus 4 using xda app-developers app
I am on official nightly and b39 and i notice this lag too, it happens even when I don't UV. I might try stock CM kernel first and see whether the lags exist too.I don't know if it is the ROM or kernel issue but on cm10.1 linaro built I seem to be getting major slowdowns ever since b37. Would run great for about 8 hours or so, then it starts feeling choppy. Recents button would take good 4-5 seconds to bring app list, notification drawer feels laggy as well.
Sent from my Nexus 4 using xda app-developers app
Can someone here tell me how to undervolt? I've never done it before. Thanks!
Sent from my Nexus 4 using Tapatalk 2
Hi Motley, thank you for such a brilliant kernel! Just one question, on b39 I'm getting around a 16 minute 'alarm_rtc' wakelock and I haven't had the alarm on at all? :/ Just wondered if you knew what was causing this?
Thanks in advance
Oh and one other question, I have a high wake lock (around 40 minutes) of:
'GTALK_ASYNC_CONN_com.Google.android.gsf.gtalkservice.AndroidEndpoint'
This only ever seems to appear overnight and never in the day. I have signed out of Google talk and uninstalled the app, I have the 'backup my data' un-ticked and I only have two gmail accounts synced. Has anyone else experiencing this or know the cause? Help would be appreciated
Sent from my Nexus 4 using xda premium
Hi Motley, thank you for such a brilliant kernel! Just one question, on b39 I'm getting around a 16 minute 'alarm_rtc' wakelock and I haven't had the alarm on at all? :/ Just wondered if you knew what was causing this?
Thanks in advance
Oh and one other question, I have a high wake lock (around 40 minutes) of:
'GTALK_ASYNC_CONN_com.Google.android.gsf.gtalkservice.AndroidEndpoint'
This only ever seems to appear overnight and never in the day. I have signed out of Google talk and uninstalled the app, I have the 'backup my data' un-ticked and I only have two gmail accounts synced. Has anyone else experiencing this or know the cause? Help would be appreciated
Sent from my Nexus 4 using xda premium
No, I do not. I'm also having issues with GPS. It has been very cloudy here, but I've never had issues on n4 before. Basically it acquires signal fast but seems to freeze on a location when navigating, before saying that signal was lost. Usually have to force turn it off and on to get it working.
Sent from my Nexus 4 using xda app-developers app
Same. And no problems with data speed, or drops. Battery life better than ever.
With B39 I noticed that I didn't receive incoming messages/notifications if I use WLAN and display is off. After turning on display all messages are coming in. With GSM/UMTS connection notifications are working with screen off - LED is flashing But no hsic wakelocks at the moment and nice battery life.
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