Database Develop

[KERNEL] [xx/xx] [3.4.62] ★ AK ★ [v.0xx]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​I am not responsible for any damage to your phone.
Read before downloading or posting in the thread:
Proceed with caution if you have no experience.
[4.3] STABLE KERNELS
NB: NEW ANYKERNEL FORMAT:
- Flash base Kernel of your rom before using this new version!
STOCK
stock Kernel: JSS
stock Kernel: JWR
JWR ED.
ak kernel: AK.JWR.25+
Features: Link
Github Kernel: Link
JSS ED.
ak kernel: AK.JSS.25+
Features: Link
Github Kernel: Link
[4.3] EXPERIMENTAL KERNELS
JWR ED.
ak kernel:
Github Kernel:
JSS ED.
ak kernel:
Github Kernel:
THANKS:
Faux
Stratosk
Mathkid
Francisco
Morfic
RamGear
BytecodeMe
Eng.stk
Jlink38
Boype
Thracemerin
Motley-git
Showp1984
Myfluxy
Androlinroot
Hellsgod
Zyonee
All RC, RD and RT
DON'T FORGET THANKS, RATE AND DONATE BUTTON:

Kernel Features
AK FEATURES
* Baseline:
4.3 JWR and JSS
Linux 3.4.62+
Compiled with Latest Linaro 4.8.2 Toolchain
-O3 Optimizations
SELinux Security Inside
* Wifi Drivers:
New Prima wlan drivers: v3.2.3.92a
* Governors:
Ondemand (Default)
Ondemandplus
Interactive
Conservative
Intellidemand
Wheatley
Hyper
Smartmax
* Hotplug Governors:
Mpdecision (Default)
auto hotplug:
2 core min online with screen on
1 core online with screen off
720mhz max freq screen off - 384mhz mix screen off
boosted and married with interactive
intelli plug
* Schedulers:
deadline (Default)
cfq
noop
sio
bfqv2r6
Fiops
Row
* Read Ahead Buffer Size:
256/32 (Default)
* Cpu Freqs Range:
270Mhz
378Mhz
384Mhz
486Mhz
594Mhz
702Mhz
810Mhz
918Mhz
1026Mhz
1134Mhz
1242Mhz
1350Mhz
1458Mhz
1512Mhz
* Gpu Freqs with Boost Support:
Boost:
128Mhz
200Mhz
320Mhz (Default)
400Mhz
487Mhz
533Mhz
Freqs:
128Mhz
200Mhz
320Mhz
400Mhz
487Mhz
533Mhz (Default)
* Gpu Governors with min power enabled when into deep sleep:
Ondemand (Default)
Simple
Performance
* Thermal Drivers:
Qualcomm thermal (Default)
Faux Intelli thermal
* Sweep on phone:
sweep2wake, sweep2slip
* TCP Congestion:
Westwood (Default)
Cubic
Bic
Htcp
Hstcp
Hybla
Vegas
Scalable
Lp
Veno
Yeah
Illinois
Reno
* Others Features:
Fully merged with cm10.2
OTG support
A lot of Cpu IDLE patches
Enhanced squre root algorithm
Asyn IO latency optimized
LZ4 Compressor/Decompressor for ZRAM
Random and Entropy fixes
CGROUP Timer slack
PA Halfbreed color by defaultStrips a lot of debugsDisabled CRC software control
New Codel NetScheduler
Topology Features
Scheduler Power SavingBattery life Extender (BLX)
Added SQLB Allocator
Optimized ARM RWSEM
Optimized Lib string and memcop
Added optimized AES and SHA1 routines
Hotplug Control
Touch Filter Control
Led triggers Control
SAI Control
Wakelock Stats enhanced
Fast Charger
Eco Mode (2 core only)
Snake Charmer (Freq capped)
C0,C1,C2,C3 Deep sleep State Control
Dynamic Fsync
Vibration control
Faux Gamma control
Faux Sound control v3
Stratosk Voltage control
Temperature Toggle
Added Charger Notify

Other Features
AK OPTIMAL SETTINGS:
CPU Control
Min clock = 270 MHhz
Max clock = 1.512 GHz
CPU Governor = Hyper
Mpdecision = Off
Auto Hotplug = On
1 core min - 2 core max
screen off max 702Mhz
screen off min 270Mhz
I/O Scheduler = noop
SOC Control
C0 - On
C1 - On
C2 - On
C3 - On
NB:
(Note: N4 AP modem is very sensitive to some of the deeper sleep states,
if you experienced Green/Yellow AP Modem Watchdog Bark screens,
I recommend disabling C2/C3 states).
Voltage Control
Boost Voltages = Off
Undervolt based on CPU type (slow, normal, fast or fastest)
GPU Control
GPU Governor = Simple
GPU Clock = 400 MHz
GPU Vsync Toggle = On
Misc Control
Dynamic File Sync = On
TCP Congestion Control = Westwood
Vibration Control = 70
Screen Color
Factory Presets - LG Presets
Color Adjustments - R, G, B 255, 250, 245
Gamma Amp Adjust 0 - R, G, B 13, 20, 22
Gamma Amp Adjust 1 - R, G, B 0, 2, 3
Z-Control
Set On Boot - On for both
ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100% if ZRAM enabled, 0% if disabled
VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled
Dirty Ratio - 20% for both
Dirty Background Ratio - 5% for both
HOW POST PROBLEMS BY FAUX
1. To report all random reboots with associated /proc/last_kmsg
2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps
3. Participate in Forum discussions (all is beta here) with others without FLAMING or post useless information such as:
a) Phone doesn't boot (without providing any additional information, ROM versions etc)
B) phone is too hot (without providing any additional information, ie OC freq, UV etc)
AK SUPPORT FAUXCLOCK:
you can view chagelog directly from APP
you can download official and beta releases
Thanks a lot to Faux who created this great application!
THE OPEN BETA
The Open Beta system is designed to have the community help each other and the developers.
This way, all potential bugs are flushed out so the final released version will be stable and error free.
The more actively you participate in Beta Testing the better the final product will be
(you are really helping yourself to create a better community software).
Faux123​

Techincal infos
* PLEASE NB:
Many of the documents and informations are taken by other threads,
so to prevent someone PM me with ...., I want to avoid saying:
"all credit to the authors".
Thanks a lot.​
C STATE POWER CONTROL
DOCs:
Faux123 - Manual for SOC power Control
Faux123 - SOC C-States demystified
Bigeyes0x0 - About C State
C0 (WFI) - Shallowest Sleep (default enabled)
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
C1 (Retention) - slightly deeper sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
C2 (Stand Alone Power Collapse) - deeper sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
C3 (Power Collapse) - deepest sleep
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
​UNDERVOLTING USERSPACE
DOCs:
Stratosk - About Undervolting
Stock kernel uses a paramater boost_uV.
By default, is added in voltages but it can be disabled.
The value of boost_uV is 0 for Slow bin chips and 25000 uV = 25 mV
for Nominal, Fast and Faster.
The boost_uV may be disabled using this command:
(= undervolting by 25000 uV in Nominal, Fast and Faster)
echo n > /sys/module/acpuclock_krait/parameters/boost
3 more paramater that handle undervolting:
- lower_uV: undervolting value for lower frequencies
- higher_uV: undervolting value for higher frequencies
- higher_khz_thres: above this frequency (default 1350000KHz) higher_uV will be used.
Else lower_uV will be used.
Undervolting value is subtracted from stock voltage. The final voltage for each frequency is calulated:
Vdd(final) = Vdd(core) + boost_uV - uV
So, to undervolt frequencies 384000-1242000 by 25mV and the other frequencies by 12.5mV use these command:
echo 25000 > /sys/module/acpuclock_krait/parameters/lower_uV
echo 12500 > /sys/module/acpuclock_krait/parameters/higher_uV
The higher_khz_thres maybe changed using this command (for example to use higher_uV from 981000KHz):
echo 918000 > /sys/module/acpuclock_krait/parameters/higher_khz_thres
Debugfs file (acpuclk/acpu_table) to show the acpu table frequencies and voltages.
For example to get the information about the current status use this command:
cat /sys/kernel/debug/acpuclk/acpu_table
CPU PVS: Fast
Boost uV: 25000
Boost uV enabled: No
Higher KHZ threshold: 1350000
Lower under uV: 37500
Higher under uV: 25000
CPU KHz VDD(stock) VDD(final) Difference
384000 875000 812500 -62500
486000 900000 837500 -62500
594000 925000 862500 -62500
702000 950000 887500 -62500
810000 1000000 937500 -62500
918000 1025000 962500 -62500
1026000 1050000 987500 -62500
1134000 1100000 1037500 -62500
1242000 1125000 1062500 -62500
1350000 1150000 1100000 -50000
1458000 1162500 1112500 -50000
1512000 1175000 1125000 -50000​

Nice. Gonna try it soon.

Yesssss
Sent from my Nexus 4 using Tapatalk 4

Word
Sent from my Nexus 4 using xda premium

So the party begins :fingers-crossed:

Fantastic
Sent from my Nexus 4

hell yeah! flashing now. it'll charge tonight, and I'll report back tomorrow with performance

Man this kernel is nice. Pretty smooth.
Sent from my Nexus 4 using Tapatalk 4

deleted

And the party started :thumbup::thumbup::thumbup: rated 5 stars as always
"using the search button won't get you killed"

w00t :victory:

ranasrule said:
TricksterMod is still the preferred app for changing kernel settings/parameters ?
Click to expand...
Click to collapse
Would like to know also. I prefer faux, but don't know if it will play nice.
Sent from my Nexus 4 using Tapatalk 4

Was waiting this kernel for my 4.3 baby....Thanks AK !

Whats is the difference between intelli hotplug and dynamic? Which is better?

TricksterMod is the preferred way to change kernel settings/parameters ?

Yes, it's in my eyes the best mod for kernel tweaks
GT-I9505 / Nexus⁴ Tapatalk

Just installed! Will come back with results as soon as I get them.

[Kernel][GPL][4.4.1/2][Jan 12][0.1.3] m_plus kernel for mako

m_plus kernel for Nexus 4 (mako)!
Hi All,
After deciding to more or less abandon m_plus for 4.3 due to issues with JSS and JWR build compatibility, I have returned to work on it for 4.4. Google has now pushed the official sources for KitKat so the fun begins.
Disclaimer: As usual, I am not responsible for anything that may or may not happen to your device as a result of using this kernel or any other flashable zips posted by me in this thread.
Kernel Features:
Based on the latest Google Source for 4.4.1 (no changes were made to the kernel for 4.4.2)
Built with the Linaro 4.7 toolchain (2013.11)
Undervolt Interface (Undervolt to 600mV)
Gamma Control Interface (faux123 & _motley interfaces only)
USB fast charge
KGSL Simple GPU governor
Dynamic fsync
Faux Sound v3.2
Krait Retention for Mako
TCP Congestion Control (veno (default), reno, bic, westwood, vegas, yeah, illinois, cubic)
Builds:
Sources: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_44_exp
Personal Request: If you plan to make unofficial builds with features not included in the builds posted by me, please don't link them in the thread, all this does is result in confusion especially if someone has a problem with something you have added, it is much easier for me to provide support if I know that everyone in the thread is running the same builds I am. If you want to make a kernel with these features, feel free to start another thread so that they can be discussed and supported as appropriate.
Note: Starting with build 0.1.0, m_plus will go back to being distributed as a flashable zip, it will come in 2 versions. Zips with names ending in _any are anykernel versions and should work on any ROM even those with a modified ramdisk, zips with names ending in _rd come packed with the stock ramdisk for those on pure stock who want to have insecure ramdisk and init.d support.
Regarding CM Compatibility: Starting with build 0.1.1, m_plus will be compatible with CM, zips with names ending in _cm will be compatible with CyanogenMod 11 on an experimental basis, this is no guarantee that every CM feature will work with these builds, nor is it a guarantee that I will continue to support CM depending on what they do with their kernel that may or may not make it incompatible.
CM Compatible Source: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_44_cm
Latest:
m_plus-0.1.3 January 12, 2014
Changes:
Fix for s2w being active with s2sonly and dt2w (thanks to show-p1984)
Previous Versions
m_plus-0.1.2 January 7, 2014
Changes:
GPU governor reverted to ondemand (if you prefer simple, see post 2)
Sweep2Wake, Doubletap2Wake, Sweep2Sleep only
kexec hardboot for multiROM support
m_plus-0.1.1 December 18, 2013
Changes:
TCP Congestion Control (added veno (default), reno, bic, westwood, vegas, yeah, illinois)
Faux Sound v3.2
m_plus-0.1.0 December 6, 2013
Changes:
Added Krait Retention for Mako (thanks faux123)
Updated sources to AOSP (android-msm-mako-3.4-kitkat-mr1)
test 5 (named boot6.img) November 28, 2013
Changes:
Updated faux sound to v3
test 4 (named boot5.img) November 23, 2013
Changes:
Dynamic fsync
Faux Sound including PowerAmp
test 3 (named boot4.img) November 22, 2013
Changes:
USB fast charge
KGSL Simple GPU governor (thanks to faux123)
test 2 (named boot3.img) November 21, 2013
Changes:
Insecure ramdisk
Enabled init.d support in the ramdisk (in order for it to work you must have busybox installed to /system/xbin and you must create the directory /system/etc/init.d)
Added Undervolt Interface
Added Gamma Control Interface (faux123 & _motley interfaces only)
See the download section tab at the top of this page.
Or see here: http://forum.xda-developers.com/devdb/project/?id=1660#downloads
Bug Reports:
Use the Bug Report feature at the top of this page.
Thanks:
Google
LG
Qualcomm/CodeAurora
CyanogenMod
_motley
faux123
show-p1984
franciscofranco
stratosk
anyone else I failed to mention (if you feel as though you deserved to be thanked by name, please PM me)
XDA:DevDB Information
m_plus kernel for mako, a Kernel for the Google Nexus 4
Contributors
thracemerin
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 0.1.0
Beta Release Date: 2013-12-06
Created 2013-11-20
Last Updated 2014-01-12

Setting custom Gamma settings via sysfs - thanks to faux123 for sharing his code
Warning: changing these values can be potentially be dangerous to your display if you make a mistake.
Important, please read!
There are ten digits in the string separated by one space
First digit is a checksum and is never stored. The checksum is simply the sum of the other 9 numbers. This is to make it harder to so the interface is respected and you are forced to think about what you are doing.
There are 3 sysfs interfaces for gamma, one for each color:
Code:
#!/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
Update:
Recently molesarecoming started opening this up and showing us what the values can be used to adjust. Franco then suggested that the white and grays should be swapped in moles original work. So, for init.d values using this interface, we have the following "banks" if values if we agree with Franco on the swap of the whites and grays.
Code:
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
(the zero in position 5's and the 2's in position 10 are recommended to be left alone since they are currently unknowns)
Minus the checksum, the 27 values mirror the 3 color arrays (3 x 9 = 27) in the actual LG LCD driver. Minus the unknowns, we are left with 21 values. Note that every one of the variables can have their value tweaked by color (saturation for red, saturation for green etc.), however, it is recommended that you start with all the values of one type being the same and then tweak from there if you really want to fine tune.
You have a lot of power in your hands even without fine tuning. Many will argue that fine tuning isn't required. If you look at the stock settings by Google in post 2, they took advantage of fine tuning for whatever reason. Even though many don't like these settings by Google, it shows how flexible the interface can be.
Instructions:
1) Start with a preset config (LG or Google) as shown further below. This is a set of 3 lines, 10 numbers for each line.
2) Tweak columns for their values as above. For example, we tweak contrast and brightness as in faux's original app. We could also do the same for saturation, blacks, whites, grays etc.
Example: start with LG presets with numbers to adjust:
Code:
383 114 21 118 0 10 4 80 48 2
383 114 21 118 0 7 4 80 48 2
383 114 21 118 0 5 1 80 48 2
3) Now update the checksum in column 1 (first digit = sum of last 9 digits)
Code:
397 114 21 118 0 10 4 80 48 2
394 114 21 118 0 7 4 80 48 2
389 114 21 118 0 5 1 80 48 2
4) Create a script inside a text file - my recommendation for your first test
Code:
#!/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
5) Run the script (or you can echo each line manually to test from adb if you prefer).
6) Turn the screen off and on for the gamma change to take effect.
7) Check the dmesg output for any clues and to see the output of the result.
8) Place the script into your /system/etc/init.d/ folder (or equivalent) for a permanent color change!
Screen refresh - this should only be called by apps or scripts while adjusting and testing colors "live" with the motley or faux sysfs interface. It should NOT be implemented on startup via init.d or by apps since it will compete with the normal power on process.
Code:
echo 1 > /sys/devices/platform/mipi_lgit.1537/refresh_screen
Presets:
Code:
#!/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
Code:
#!/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
Code:
#!/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
Voltage Control
Warning: Every chip is different, even those from the same bin may handle undervolting differently, proceed with caution until you know that your device can handle it.
Note: The minimum allowable undervolt is 600mV for all frequencies (this doesn't mean your device can handle this low voltage, see above)
The voltage table can be viewed by typing the following:
Code:
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
To make changes do the following:
Code:
echo 'X Y' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
For example: (set the voltage for 384MHz to 850mV)
Code:
echo '384000 850000' > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
For those of you who are interested, here are the default voltage tables from Motley b49: https://docs.google.com/spreadsheet/ccc?key=0AlgoC5O8VXsLdFU4U2xnSUxwUlNyQ05TVHF3ZDJCdXc&usp=sharing
USB Fast Charge
Turn on: (off by default)
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
Turn Off:
Code:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Simple GPU Governor Tunables - Thanks to faux123
Switching the governor: (options are simple, ondemand (default) & performance)
Code:
echo 'ondemand' > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/trustzone/governor
Simple tunables:
Code:
/sys/module/msm_kgsl_core/parameters/simple_laziness
Laziness: Adjusts the number of times the governor skips ramp down requests. (Higher = better performance, higher battery drain)
Code:
/sys/module/msm_kgsl_core/parameters/simple_ramp_threshold
Threshold: Adjusts the threshold to ramp up or down the GPU frequencies. (Lower = better performance, higher battery drain)
C State Information
(thanks to faux123 - more info here: https://plus.google.com/109078966818501160423/posts/9R8fjQdHDXD)
faux123 recommends C0, C1 and C3 here: http://forum.xda-developers.com/showpost.php?p=40151528&postcount=9775
C0 (WFI) - Shallowest Sleep (default enabled)
Code:
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
C1 (Retention) - slightly deeper sleep
Code:
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
C2 (Stand Alone Power Collapse) - deeper sleep
Code:
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
C3 (Power Collapse) - deepest sleep
Code:
enable: echo 1 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
disable: echo 0 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
TCP Congestion Control
Options: veno (default), reno, bic, westwood, vegas, yeah, illinois, cubic
Code:
echo 'cubic' > /proc/sys/net/ipv4/tcp_congestion_control
Sweep2Wake, Doubletap2Wake, Sweep2Sleep only
Sweep2Wake: (1 enable, 0 disable)
Code:
echo 1 > /sys/android_touch/sweep2wake
Doubletap2Wake: (1 enable, 0 disable)
Code:
echo 1 > /sys/android_touch/doubletap2wake
Sweep2Sleep Only: (1 enable, 0 disable) (sweep2wake must be enabled)
Code:
echo 1 > /sys/android_touch/s2w_s2sonly

Frequently Asked Questions
Q: My battery life has significantly decreased vs stock, why would this be?
A: It would be rather foolish of me to create a custom kernel that decreases battery life. In my experience battery life issues are generally related to something in userspace rather than in the kernel. My suggestion is to get Better Battery Stats (there are kitkat versions in the XDA thread) and provide a dumpfile of a few hours worth of idle/standard use for me to look at so that I can help you identify the problem, if it is in fact an issue with the kernel I will do my best to fix it.
Q: I got a random reboot, freeze, sleep of death, other bug, what do I do?
A: Please review this post: http://forum.xda-developers.com/showpost.php?p=23036410&postcount=1 and provide appropriate logs in the bug report tab at the top of the thread. I strongly advise that you remove your undervolt (if any) and attempt to reproduce the situation before posting as too much undervolting is often the cause.
Q: I saw a feature in another kernel that I'd really like for you to add to this one, how can I ask you to do that?
A: Go ahead and post it in the thread and I'll take a look, keep in mind that I would prefer to avoid filling the kernel with features that will be used by a very small number of users.

Test build 1 posted (boot.img format only until we're a little further along), see Download tab at the top of the thread.
It's basically just stock built with linaro, as a test to ensure everything went well. Builds with features will be coming shortly
Happy Flashing. :victory:
Note: This kernel is based on sources pushed for KRT16S, I'm not sure whether there will be problems with KRT16O or KRT16M builds as I didn't test them, the only problem that might be anticipated is that prima wlan was updated from 3.2.3.10 to 3.2.3.11 which may make WiFi not work, if this is the case let me know and I can put together a fix for that particular issue.

Loved your work .

Nice!

Awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[DEVICE:NEXUS⁴][ROM:BEERGANG][KERNEL:AK]​

Subscribed! Thank you for continuing the m_plus kernel @thracemerin

Feels like home again. Thanks thracemerin!
Sent from my Nexus 7 using Tapatalk 4

I'm using this right now, on KRT16O build. No problems with WiFi so far. :good:

saibz said:
I'm using this right now, on KRT16O build. No problems with WiFi so far. :good:
Click to expand...
Click to collapse
Good to know, thanks!
Sent from my Nexus 7 using Tapatalk 4

Long time no see!
Sent with Virtue

Finally! Was waiting for this thanks!
Sent from my Nexus 4 using Tapatalk

Nice to see familiar names here. Loyal user base here
Sent from my Nexus 4 using Tapatalk

Awesome, was using your kernel on 4.3, now on psx 4.4 so looking forward to trying this on that
Sent from my Nexus 4 using Tapatalk

One of the best kernels!Keep up the good work!:thumbup:

Keeping in mind the design principles of the previous m_plus versions (4.2.x and 4.3), what features would you guys like to see for 4.4?

thracemerin said:
Keeping in mind the design principles of the previous m_plus versions (4.2.x and 4.3), what features would you guys like to see for 4.4?
Click to expand...
Click to collapse
Undervolting (down to 600mV)
Dynamic fsync
Hotplug (control max. online CPUs)
Not sure if this is a feature which can be implemented in kernel. But I hate the Android default brightness control. You have to decide whether you use auto-brightness or manual one. I would like to see some control over auto-brightness as well. For example in many light conditions I would like to use a lower brightness than what is provided by auto-brightness. But when I go for manual brightness then I cannot even find the brightness control when I step out into the sunlight. So actually I would prefer to have auto-brightness but control the lower and upper limits and adjust the brightness adjustment sensitivity. Of course this would require also a change on the ROM since the ROM controls will disable brightness control when auto-brightness is active. But perhaps tuning the algorithm variables could be done via kernel variables or by very simple app then.
I just migrated to KRT16S factory image and looking forward to test this kernel.
These are just the features I would love most to see. Keep up the great work! Many thanks to you and also all the other kernel hackers allowing us to fine-tune where the Google default stops.

SkyBeam2048 said:
Undervolting (down to 600mV)
Dynamic fsync
Hotplug (control max. online CPUs)
Not sure if this is a feature which can be implemented in kernel. But I hate the Android default brightness control. You have to decide whether you use auto-brightness or manual one. I would like to see some control over auto-brightness as well. For example in many light conditions I would like to use a lower brightness than what is provided by auto-brightness. But when I go for manual brightness then I cannot even find the brightness control when I step out into the sunlight. So actually I would prefer to have auto-brightness but control the lower and upper limits and adjust the brightness adjustment sensitivity. Of course this would require also a change on the ROM since the ROM controls will disable brightness control when auto-brightness is active. But perhaps tuning the algorithm variables could be done via kernel variables or by very simple app then.
I just migrated to KRT16S factory image and looking forward to test this kernel.
These are just the features I would love most to see. Keep up the great work! Many thanks to you and also all the other kernel hackers allowing us to fine-tune where the Google default stops.
Click to expand...
Click to collapse
The 3 things you listed are things that make my list too.
As far as the auto-brightness, this is mostly handled by the OS, though I have noticed that stratosk did some tweaks to the kernel side driver that could result in better auto-brightness, I'll look into that one.

thracemerin said:
The 3 things you listed are things that make my list too.
As far as the auto-brightness, this is mostly handled by the OS, though I have noticed that stratosk did some tweaks to the kernel side driver that could result in better auto-brightness, I'll look into that one.
Click to expand...
Click to collapse
Don't forget gamma hack(faux's) and fauxsound and keep it ass minimal as possible just like on 4.3 :thumbup:

Poor Wifi - Optimal wlan config?

Wifi range is terrible and keeps disconnecting me, what's the best way to edit these settings?
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
# 0 implies no periodic wake up from IMPS. Periodic wakeup is
# unnecessary if Idle Scan is disabled.
gImpsModSleepTime=0
# Enable BMPS or not
gEnableBmps=0
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
# Valid values are 0-9, with 0 = Auto, 4 = 11n, 9 = 11ac
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# Assigned MAC Addresses - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=000AF58989FF
Intf1MacAddress=000AF58989FE
Intf2MacAddress=000AF58989FD
Intf3MacAddress=000AF58989FC
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
# WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=3
#Flag to enable HostARPOffload feature or not
hostArpOffload=1
#SoftAP Related Parameters
# AP MAc addr
gAPMacAddr=000AF589dcab
# 802.11n Protection flag
gEnableApProt=1
#Enable OBSS protection
gEnableApOBSSProt=1
#Enable TrafficMonitor
gEnableTrafficMonitor=1
#Set TracfficIdleTimeout
gTrafficIdleTimeout=3000
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=0
# Fixed Rate
gFixedRate=0
# Maximum Tx power
# gTxPowerCap=100
# Fragmentation Threshold
# gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM Enable/Disable
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# 802.11h support
g11hSupportEnabled=1
# CCX Support and fast transition
CcxEnabled=0
FastTransitionEnabled=1
ImplicitQosIsEnabled=1
gNeighborScanTimerPeriod=200
gNeighborLookupThreshold=76
gNeighborReassocThreshold=81
gNeighborScanChannelMinTime=20
gNeighborScanChannelMaxTime=30
gMaxNeighborReqTries=3
# Legacy (non-CCX, non-802.11r) Fast Roaming Support
# To enable, set FastRoamEnabled=1
# To disable, set FastRoamEnabled=0
FastRoamEnabled=1
#Check if the AP to which we are roaming is better than current AP in terms of RSSI.
#Checking is disabled if set to Zero.Otherwise it will use this value as to how better
#the RSSI of the new/roamable AP should be for roaming
RoamRssiDiff=3
# If the RSSI of any available candidate is better than currently associated
# AP by at least gImmediateRoamRssiDiff, then being to roam immediately (without
# registering for reassoc threshold).
# NOTE: Value of 0 means that we would register for reassoc threshold.
gImmediateRoamRssiDiff=10
# To enable, set gRoamIntraBand=1 (Roaming within band)
# To disable, set gRoamIntraBand=0 (Roaming across band)
gRoamIntraBand=0
# SAP Country code
# Default Country Code is 2 bytes, 3rd byte is optional indoor or out door.
# Example
# US Indoor, USI
# Korea Outdoor, KRO
# Japan without optional byte, JP
# France without optional byte, FR
#gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
gShortGI40Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
# SAP auto channel selection configuration
# 0 = disable auto channel selection
# 1 = enable auto channel selection, channel provided by supplicant will be ignored
gApAutoChannelSelection=1
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 127 dBm.
#
gEnablePhyAgcListenMode=128
#Preferred channel to start BT AMP AP mode (0 means, any channel)
BtAmpPreferredChannel=0
#Preferred band (both or 2.4 only or 5 only)
BandCapability=0
#Beacon Early Termination (1 = enable the BET feature, 0 = disable)
enableBeaconEarlyTermination=0
beaconEarlyTerminationWakeInterval=3
#Bluetooth Alternate Mac Phy (1 = enable the BT AMP feature, 0 = disable)
gEnableBtAmp=0
#SOFTAP Channel Range selection
gAPChannelSelectStartChannel=1
gAPChannelSelectEndChannel=11
#SOFTAP Channel Range selection Operating band
# 0:2.4GHZ 1: LOW-5GHZ 2:MID-5GHZ 3:HIGH-5GHZ 4: 4.9HZ BAND
gAPChannelSelectOperatingBand=0
#Channel Bonding
gChannelBondingMode5GHz=1
#Enable Keep alive with non-zero period value
#gStaKeepAlivePeriod = 30
#AP LINK MONITOR TIMEOUT is used for both SAP and GO mode.
#It is used to change the frequency of keep alive packets in the AP Link Monitor period which is by
#default 20s. Currently the keep alive packets are sent as an interval of 3s but after this change
#the keep alive packet frequency can be changed.
#gApLinkMonitorPeriod = 3
#If set will start with active scan after driver load, otherwise will start with
#passive scan to find out the domain
gEnableBypass11d=1
#If set to 0, will not scan DFS channels
gEnableDFSChnlScan=1
gVhtChannelWidth=2
gEnableLogp=1
# Enable Automatic Tx Power control
gEnableAutomaticTxPowerControl=1
# 0 for OLPC 1 for CLPC and SCPC
gEnableCloseLoop=1
#Data Inactivity Timeout when in powersave (in ms)
gDataInactivityTimeout=200
# VHT Tx/Rx MCS values
# Valid values are 0,1,2. If commented out, the default value is 0.
# 0=MCS0-7, 1=MCS0-8, 2=MCS0-9
gVhtRxMCS=2
gVhtTxMCS=2
# Enable CRDA regulatory support by settings default country code
#gCrdaDefaultCountryCode=TW
# Scan Timing Parameters
# gPassiveMaxChannelTime=110
# gPassiveMinChannelTime=60
# gActiveMaxChannelTime=40
# gActiveMinChannelTime=20
#If set to 0, MCC is not allowed.
gEnableMCCMode=1
# 1=enable STBC; 0=disable STBC
gEnableRXSTBC=1
# Enable Active mode offload
gEnableActiveModeOffload=1
#Enable Scan Results Aging based on timer
#Timer value is in seconds
#If Set to 0 it will not enable the feature
gScanAgingTime=0
#Enable Power saving mechanism Based on Android Framework
#If set to 0 Driver internally control the Power saving mechanism
#If set to 1 Android Framwrok control the Power saving mechanism
isAndroidPsEn=1
#disable LDPC in STA mode if the AP is TXBF capable
gDisableLDPCWithTxbfAP=1
#Enable thermal mitigation
gThermalMitigationEnable=1
#List of Country codes for which 11ac needs to be disabled
#Each country code must be delimited by comma(,)
gListOfNon11acCountryCode=RU,UA,ZA
#Maxium Channel time in msec
gMaxMediumTime = 6000
# 802.11K support
gRrmEnable=1
gRrmOperChanMax=8
gRrmNonOperChanMax=8
gRrmRandIntvl=100
# If set to 1, generate the p2p device address from primary mac address
# with the locally administered bit set
isP2pDeviceAddrAdministrated=1
#Enable Telescopic Beacon wakeup
gEnableDynamicDTIM=0
gIgnoreDtim=0
gTelescopicBeaconWakeupEn=1
telescopicBeaconTransListenInterval=2
telescopicBeaconTransListenIntervalNumIdleBcns=10
telescopicBeaconMaxListenInterval=3
telescopicBeaconMaxListenIntervalNumIdleBcns=15
END
# Note: Configuration parser would not read anything past the END marker

xinfernal said:
Wifi range is terrible and keeps disconnecting me, what's the best way to edit these settings?
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
# 0 implies no periodic wake up from IMPS. Periodic wakeup is
# unnecessary if Idle Scan is disabled.
gImpsModSleepTime=0
# Enable BMPS or not
gEnableBmps=0
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
# Valid values are 0-9, with 0 = Auto, 4 = 11n, 9 = 11ac
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# Assigned MAC Addresses - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=000AF58989FF
Intf1MacAddress=000AF58989FE
Intf2MacAddress=000AF58989FD
Intf3MacAddress=000AF58989FC
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
# WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=3
#Flag to enable HostARPOffload feature or not
hostArpOffload=1
#SoftAP Related Parameters
# AP MAc addr
gAPMacAddr=000AF589dcab
# 802.11n Protection flag
gEnableApProt=1
#Enable OBSS protection
gEnableApOBSSProt=1
#Enable TrafficMonitor
gEnableTrafficMonitor=1
#Set TracfficIdleTimeout
gTrafficIdleTimeout=3000
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=0
# Fixed Rate
gFixedRate=0
# Maximum Tx power
# gTxPowerCap=100
# Fragmentation Threshold
# gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM Enable/Disable
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# 802.11h support
g11hSupportEnabled=1
# CCX Support and fast transition
CcxEnabled=0
FastTransitionEnabled=1
ImplicitQosIsEnabled=1
gNeighborScanTimerPeriod=200
gNeighborLookupThreshold=76
gNeighborReassocThreshold=81
gNeighborScanChannelMinTime=20
gNeighborScanChannelMaxTime=30
gMaxNeighborReqTries=3
# Legacy (non-CCX, non-802.11r) Fast Roaming Support
# To enable, set FastRoamEnabled=1
# To disable, set FastRoamEnabled=0
FastRoamEnabled=1
#Check if the AP to which we are roaming is better than current AP in terms of RSSI.
#Checking is disabled if set to Zero.Otherwise it will use this value as to how better
#the RSSI of the new/roamable AP should be for roaming
RoamRssiDiff=3
# If the RSSI of any available candidate is better than currently associated
# AP by at least gImmediateRoamRssiDiff, then being to roam immediately (without
# registering for reassoc threshold).
# NOTE: Value of 0 means that we would register for reassoc threshold.
gImmediateRoamRssiDiff=10
# To enable, set gRoamIntraBand=1 (Roaming within band)
# To disable, set gRoamIntraBand=0 (Roaming across band)
gRoamIntraBand=0
# SAP Country code
# Default Country Code is 2 bytes, 3rd byte is optional indoor or out door.
# Example
# US Indoor, USI
# Korea Outdoor, KRO
# Japan without optional byte, JP
# France without optional byte, FR
#gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
gShortGI40Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
# SAP auto channel selection configuration
# 0 = disable auto channel selection
# 1 = enable auto channel selection, channel provided by supplicant will be ignored
gApAutoChannelSelection=1
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 127 dBm.
#
gEnablePhyAgcListenMode=128
#Preferred channel to start BT AMP AP mode (0 means, any channel)
BtAmpPreferredChannel=0
#Preferred band (both or 2.4 only or 5 only)
BandCapability=0
#Beacon Early Termination (1 = enable the BET feature, 0 = disable)
enableBeaconEarlyTermination=0
beaconEarlyTerminationWakeInterval=3
#Bluetooth Alternate Mac Phy (1 = enable the BT AMP feature, 0 = disable)
gEnableBtAmp=0
#SOFTAP Channel Range selection
gAPChannelSelectStartChannel=1
gAPChannelSelectEndChannel=11
#SOFTAP Channel Range selection Operating band
# 0:2.4GHZ 1: LOW-5GHZ 2:MID-5GHZ 3:HIGH-5GHZ 4: 4.9HZ BAND
gAPChannelSelectOperatingBand=0
#Channel Bonding
gChannelBondingMode5GHz=1
#Enable Keep alive with non-zero period value
#gStaKeepAlivePeriod = 30
#AP LINK MONITOR TIMEOUT is used for both SAP and GO mode.
#It is used to change the frequency of keep alive packets in the AP Link Monitor period which is by
#default 20s. Currently the keep alive packets are sent as an interval of 3s but after this change
#the keep alive packet frequency can be changed.
#gApLinkMonitorPeriod = 3
#If set will start with active scan after driver load, otherwise will start with
#passive scan to find out the domain
gEnableBypass11d=1
#If set to 0, will not scan DFS channels
gEnableDFSChnlScan=1
gVhtChannelWidth=2
gEnableLogp=1
# Enable Automatic Tx Power control
gEnableAutomaticTxPowerControl=1
# 0 for OLPC 1 for CLPC and SCPC
gEnableCloseLoop=1
#Data Inactivity Timeout when in powersave (in ms)
gDataInactivityTimeout=200
# VHT Tx/Rx MCS values
# Valid values are 0,1,2. If commented out, the default value is 0.
# 0=MCS0-7, 1=MCS0-8, 2=MCS0-9
gVhtRxMCS=2
gVhtTxMCS=2
# Enable CRDA regulatory support by settings default country code
#gCrdaDefaultCountryCode=TW
# Scan Timing Parameters
# gPassiveMaxChannelTime=110
# gPassiveMinChannelTime=60
# gActiveMaxChannelTime=40
# gActiveMinChannelTime=20
#If set to 0, MCC is not allowed.
gEnableMCCMode=1
# 1=enable STBC; 0=disable STBC
gEnableRXSTBC=1
# Enable Active mode offload
gEnableActiveModeOffload=1
#Enable Scan Results Aging based on timer
#Timer value is in seconds
#If Set to 0 it will not enable the feature
gScanAgingTime=0
#Enable Power saving mechanism Based on Android Framework
#If set to 0 Driver internally control the Power saving mechanism
#If set to 1 Android Framwrok control the Power saving mechanism
isAndroidPsEn=1
#disable LDPC in STA mode if the AP is TXBF capable
gDisableLDPCWithTxbfAP=1
#Enable thermal mitigation
gThermalMitigationEnable=1
#List of Country codes for which 11ac needs to be disabled
#Each country code must be delimited by comma(,)
gListOfNon11acCountryCode=RU,UA,ZA
#Maxium Channel time in msec
gMaxMediumTime = 6000
# 802.11K support
gRrmEnable=1
gRrmOperChanMax=8
gRrmNonOperChanMax=8
gRrmRandIntvl=100
# If set to 1, generate the p2p device address from primary mac address
# with the locally administered bit set
isP2pDeviceAddrAdministrated=1
#Enable Telescopic Beacon wakeup
gEnableDynamicDTIM=0
gIgnoreDtim=0
gTelescopicBeaconWakeupEn=1
telescopicBeaconTransListenInterval=2
telescopicBeaconTransListenIntervalNumIdleBcns=10
telescopicBeaconMaxListenInterval=3
telescopicBeaconMaxListenIntervalNumIdleBcns=15
END
# Note: Configuration parser would not read anything past the END marker
Click to expand...
Click to collapse
having the same issue. fresh install android O. did you ever find any info about this?

ElwOOd_CbGp said:
having the same issue. fresh install android O. did you ever find any info about this?
Click to expand...
Click to collapse
I can't remember if there was a solution but overall the Xperia SP wasn't good enough for my needs so I replaced it within the year.

Raspberry Pi Tank

This project sets Raspberry Pi on wheels (tracks in fact), allows to control tank remotely and get streamed video over internet.

Electronchik said:
This project sets Raspberry Pi on wheels (tracks in fact), allows to control tank remotely and get streamed video over internet.
Click to expand...
Click to collapse
Do you have a specific question about your project that you would like to ask?

How to set on raspberry pi 2 two pwm to control two motor ?
I have this code but one motor runing in 100% and one in ~ 60%
RobotControl.py
#!/usr/bin/python
# coding: utf-8
# Poczatek programu
import sys, tty, termios, os
import L298NHBridge as HBridge
speedleft = 0
speedright = 0
# Instrukcja wyswietlana uzytkownikowi
print("w/s: direction")
print("a/d: steering")
print("q: stops the motors")
print("p: print motor speed (L/R)")
print("x: exit")
# Przechwycenie przycisku wciśniętego przez uzytkownika
def getch():
import sys, tty, termios
old_settings = termios.tcgetattr(0)
new_settings = old_settings[:]
new_settings[3] &= ~termios.ICANON
try:
termios.tcsetattr(0, termios.TCSANOW, new_settings)
ch = sys.stdin.read(1)
finally:
termios.tcsetattr(0, termios.TCSANOW, old_settings)
return ch
print("\nchar is '" + getch() + "'\n")
# Inicjacja zapetlenia
# Zapetlenie zostaje przerwane, gdy uzytkownik wcisnie klawisz x
def printscreen():
os.system('clear')
print("w/s: direction")
print("a/d: steering")
print("q: stops the motors")
print("x: exit")
print("========== Speed Control ==========")
print("left motor: ", speedleft)
print("right motor: ", speedright)
print(char)
while True:
char = getch()
if(char == "\x1b[A"):
printscreen()
# Pojazd pojedzie do przodu, jesli uzytkownik wcisnie klawisz w
if(char == "w"):
# Synchronizacja predkosci silnikow
# Start pojazdu
speedleft = speedleft + 0.1
speedright = speedright + 0.1
if speedleft > 1:
speedleft = 1
if speedright > 1:
speedright = 1
HBridge.setMotorLeft(speedleft)
HBridge.setMotorRight(speedright)
printscreen()
# Pojazd pojedzie do tylu, jesli uzytkownik wcisnie klawisz w
if(char == "s"):
# Synchronizacja predkosci silnikow
# Obnizenie predkosci pojazdu
speedleft = speedleft - 0.1
speedright = speedright - 0.1
if speedleft < -1:
speedleft = -1
if speedright < -1:
speedright = -1
HBridge.setMotorLeft(speedleft)
HBridge.setMotorRight(speedright)
printscreen()
# Zatrzymanie silnikow
if(char == "q"):
speedleft = 0
speedright = 0
HBridge.setMotorLeft(speedleft)
HBridge.setMotorRight(speedright)
printscreen()
# Pojazd pojedzie w prawo, jesli uzytkownik wcisnie klawisz d
if(char == "d"):
speedright = speedright - 0.1
speedleft = speedleft + 0.1
if speedright < -1:
speedright = -1
if speedleft > 1:
speedleft = 1
HBridge.setMotorLeft(speedleft)
HBridge.setMotorRight(speedright)
printscreen()
# Pojazd pojedzie w lewo, jesli uzytkownik wcisnie klawisz a
if(char == "a"):
speedleft = speedleft - 0.1
speedright = speedright + 0.1
if speedleft < -1:
speedleft = -1
if speedright > 1:
speedright = 1
HBridge.setMotorLeft(speedleft)
HBridge.setMotorRight(speedright)
printscreen()
# Przerwanie wykonywania petli, zamkniecie programu i stop silnikow
if(char == "x"):
HBridge.setMotorLeft(0)
HBridge.setMotorRight(0)
HBridge.exit()
print("Program Ended")
break
# Wybrany przez uzytkownika klawisz zostaje zapisany jako pusty, jest to potrzebne
# do zapisania nastepnego wybranego przez uzytkownika klawisza
char = ""
# Koniec programu
Click to expand...
Click to collapse
L298NHbridge.py
# Import the libraries the class needs
import RPi.GPIO as io
import time
io.setmode(io.BCM)
# Constant values to set the max pwm speed.
# 40 will set the motor speed to 40% max.
PWM_MAX = 50
# Disable warning from GPIO
io.setwarnings(False)
# Motor Driver Dual H-Bridge connection configuration.
# Here you can change the wiring between the H-Bridge IN pins and the Raspberry Pi GPIO out pins.
# --- START CONFIG ---
# H-Bridge pin = GPIO
ENA = 4
IN1 = 27
IN2 = 22
IN3 = 24
IN4 = 25
ENB = 17
# --- END CONFIG ---
# Here we configure the GPIO settings for the left and right motors spinning direction.
# It defines the four GPIO pins used as input on the L298 H-Bridge to set the motor mode (forward, reverse and stopp).
leftmotor_in1_pin = IN1
leftmotor_in2_pin = IN2
io.setup(leftmotor_in1_pin, iUT)
io.setup(leftmotor_in2_pin, iUT)
rightmotor_in1_pin = IN3
rightmotor_in2_pin = IN4
io.setup(rightmotor_in1_pin, iUT)
io.setup(rightmotor_in2_pin, iUT)
io.output(leftmotor_in1_pin, False)
io.output(leftmotor_in2_pin, False)
io.output(rightmotor_in1_pin, False)
io.output(rightmotor_in2_pin, False)
# Here we configure the GPIO settings for the left and right motors spinning speed.
# It defines the two GPIO pins used as input on the L298 H-Bridge to set the motor speed with a PWM signal.
leftmotorpwm_pin = ENA
rightmotorpwm_pin = ENB
io.setup(leftmotorpwm_pin, iUT)
io.setup(rightmotorpwm_pin, iUT)
leftmotorpwm = io.PWM(leftmotorpwm_pin,100)
rightmotorpwm = io.PWM(rightmotorpwm_pin,100)
leftmotorpwm.start(0)
leftmotorpwm.ChangeDutyCycle(0)
rightmotorpwm.start(0)
rightmotorpwm.ChangeDutyCycle(0)
def setMotorMode(motor, mode):
# setMotorMode()
# Sets the mode for the L298 H-Bridge which motor is in which mode.
# This is a short explanation for a better understanding:
# motor -> which motor is selected left motor or right motor
# mode -> mode explains what action should be performed by the H-Bridge
# setMotorMode(leftmotor, reverse) -> The left motor is called by a function and set into reverse mode
# setMotorMode(rightmotor, stopp) -> The right motor is called by a function and set into stopp mode
if motor == "leftmotor":
if mode == "reverse":
io.output(leftmotor_in1_pin, True)
io.output(leftmotor_in2_pin, False)
elif mode == "forward":
io.output(leftmotor_in1_pin, False)
io.output(leftmotor_in2_pin, True)
else:
io.output(leftmotor_in1_pin, False)
io.output(leftmotor_in2_pin, False)
elif motor == "rightmotor":
if mode == "reverse":
io.output(rightmotor_in1_pin, False)
io.output(rightmotor_in2_pin, True)
elif mode == "forward":
io.output(rightmotor_in1_pin, True)
io.output(rightmotor_in2_pin, False)
else:
io.output(rightmotor_in1_pin, False)
io.output(rightmotor_in2_pin, False)
else:
io.output(leftmotor_in1_pin, False)
io.output(leftmotor_in2_pin, False)
io.output(rightmotor_in1_pin, False)
io.output(rightmotor_in2_pin, False)
def setMotorLeft(power):
# SetMotorLeft(power)
# Sets the drive level for the left motor, from +1 (max) to -1 (min).
# This is a short explanation for a better understanding:
# SetMotorLeft(0) -> left motor is stopped
# SetMotorLeft(0.75) -> left motor moving forward at 75% power
# SetMotorLeft(-0.5) -> left motor moving reverse at 50% power
# SetMotorLeft(1) -> left motor moving forward at 100% power
int(power)
if power < 0:
# Reverse mode for the left motor
setMotorMode("leftmotor", "reverse")
pwm = -int(PWM_MAX * power)
if pwm > PWM_MAX:
pwm = PWM_MAX
elif power > 0:
# Forward mode for the left motor
setMotorMode("leftmotor", "forward")
pwm = int(PWM_MAX * power)
if pwm > PWM_MAX:
pwm = PWM_MAX
else:
# Stopp mode for the left motor
setMotorMode("leftmotor", "stopp")
pwm = 0
leftmotorpwm.ChangeDutyCycle(pwm)
def setMotorRight(power):
# SetMotorRight(power)
# Sets the drive level for the right motor, from +1 (max) to -1 (min).
# This is a short explanation for a better understanding:
# SetMotorRight(0) -> right motor is stopped
# SetMotorRight(0.75) -> right motor moving forward at 75% power
# SetMotorRight(-0.5) -> right motor moving reverse at 50% power
# SetMotorRight(1) -> right motor moving forward at 100% power
int(power)
if power < 0:
# Reverse mode for the right motor
setMotorMode("rightmotor", "reverse")
pwm = -int(PWM_MAX * power)
if pwm > PWM_MAX:
pwm = PWM_MAX
elif power > 0:
# Forward mode for the right motor
setMotorMode("rightmotor", "forward")
pwm = int(PWM_MAX * power)
if pwm > PWM_MAX:
pwm = PWM_MAX
else:
# Stopp mode for the right motor
setMotorMode("rightmotor", "stopp")
pwm = 0
rightmotorpwm.ChangeDutyCycle(pwm)
def exit():
# Program will clean up all GPIO settings and terminates
io.output(leftmotor_in1_pin, False)
io.output(leftmotor_in2_pin, False)
io.output(rightmotor_in1_pin, False)
io.output(rightmotor_in2_pin, False)
io.cleanup()
Click to expand...
Click to collapse

Hello, I actually made one ,,tank,, when I was on school. Here is link with all instructions I used.

Mi5 - going in random reboots.

My Mi 5 2016 phone is going in for random reboots by itself. no regular pattern.
1) It's not full 6gb space is still available.
2) Is it possible that degraded battery is causing reboots, I still get 14-16 hour usage with calls. but it is lower when this was new. (This is assumption only).
3) DMESG files are below.
111117.719856] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.
[111117.727296] msm_pcie_enable: PCIe RC0 PHY is ready!
[111117.737561] msm_pcie_enable: PCIe: Release the reset of endpoint of RC0.
[111117.744813] wlan: [0:E :HDD] __hdd_tx_timeout: 1129: Transmission timeout occurred jiffies 4306049301 trans_start 4306049121
[111117.764617] msm_pcie_enable: PCIe RC0 link initialized
[111117.773472] PM: noirq resume of devices complete after 54.580 msecs
[111117.781277] PM: early resume of devices complete after 4.939 msecs
[111117.802622] pn548_resume --
[111117.812537] wlan: [0:F :WDA] WOW wakeup host event received (reason: PATTERN_MATCH_FOUND(9)) for vdev 0
[111117.812685] wlan: [0:F :WDA] uc 1646 bc 0 v4_mc 0 v6_mc 0 ra 0 ns 0 na 0 pno_match 0 pno_complete 0 gscan 0 low_rssi 0 rssi_breach 0
[111117.812851] __hif_pci_resume: Resume completes in wow mode
[111117.820177] PM: resume of devices complete after 38.861 msecs
[111117.826177] Restarting tasks ...
[111117.833216] healthd: battery l=84 v=4109 t=28.5 h=2 st=3 c=73 chg= 2020-11-01 13:14:53.173539509 UTC
[111117.885270] done.
[111117.885528] PM: suspend exit 2020-11-01 13:14:53.225954718 UTC
[111117.986113] PM: suspend entry 2020-11-01 13:14:53.326529718 UTC
[111117.986170] PM: Syncing filesystems ... done.
[111118.026953] Freezing user space processes ... (elapsed 0.038 seconds) done.
[111118.065199] Freezing remaining freezable tasks ... (elapsed 0.006 seconds) done.
[111118.071860] Suspending console(s) (use no_console_suspend to debug)
[111118.081339] SMBCHG: smbchg_restricted_charging: restricted_charging set to 0
[111118.083102] __hif_pci_suspend: Waiting for CE to finish access:
[111118.098202] __hif_pci_suspend: Suspend completes in wow mode event:2 device_state:0
[111118.098205] __hif_pci_suspend: Suspend completes
[111118.108154] pn548_suspend ++
link here swisstransfer<dot>com/d/dc27a402-3fb9-477a-857c-f4473a96f30e
(as a new user not allowed to add links hence sharing this dmesg file.)
I really need this device up and work reliably TIA.