Related
I have started this thread as a place to discuss random development thought that probably don't need their own threads, and as a place to discuss issues so other threads don't go too far off topic.
Table of Contents:
DBV for c6843: Posts 1 - 6
GPL: Post 7
F2FS: Post 8
wlan: post 9, 11 -
Optimisation Bookmark: post 10
Original Post 1:
First thought
@dbolivar Have you tried building you (DooMKernel) with CONFIG_DVB_CORE = y/m to see if you can get the TV function to work?
blueether said:
I have started this thread as a place to discuss random development thought that probably don't need their own threads, and as a place to discuss issues so other threads don't go too far off topic.
First thought
@dbolivar Have you tried building you (DooMKernel) with CONFIG_DVB_CORE = y/m to see if you can get the TV function to work?
Click to expand...
Click to collapse
Hi, good start. In fact I have, the differences in the kernel options between C6833 and C6843 (Brazilian model with digital TV) are:
Code:
47c47
< CONFIG_MACH_SONY_TOGARI_BRAZIL=y
---
> CONFIG_MACH_SONY_TOGARI_ROW=y
275d274
< CONFIG_ISDBT_TUNER_SMTEJ11X=y
325a325,327
> CONFIG_TOUCHSCREEN_CLEARPAD=y
> CONFIG_TOUCHSCREEN_CLEARPAD_I2C=y
> CONFIG_TOUCHSCREEN_CLEARPAD_RMI_DEV=y
Yes, I don't know why the Clearpad touchscreen is enabled for the C6833, but not for the C6843; I think it's just garbage (perhaps they made the togari defconfig based off honami, and corrected that when making the togari_brazil defconfig). It doesn't make any difference for me, disabling them keep the touchscreen (MAX1187) functions normal.
Well, back to the point: even when applying these differences to the ZU DooMKernel, the digital TV doesn't work. The app stays a long time in a black screen, and finally closes (FC). I investigated the kmsg and logcat, but nothing useful.
CONFIG_DVB_CORE is "m" by default. I tried insmod'ing every module in /system/lib/modules, but same result. I temporarily gave up, because I don't watch the crap they broadcast on the open TV here. But yeah, it would be good to have everything working...
dbolivar said:
Hi, good start. In fact I have, the differences in the kernel options between C6833 and C6843 (Brazilian model with digital TV) are:
Code:
47c47
< CONFIG_MACH_SONY_TOGARI_BRAZIL=y
---
> CONFIG_MACH_SONY_TOGARI_ROW=y
275d274
< CONFIG_ISDBT_TUNER_SMTEJ11X=y
325a325,327
> CONFIG_TOUCHSCREEN_CLEARPAD=y
> CONFIG_TOUCHSCREEN_CLEARPAD_I2C=y
> CONFIG_TOUCHSCREEN_CLEARPAD_RMI_DEV=y
Yes, I don't know why the Clearpad touchscreen is enabled for the C6833, but not for the C6843; I think it's just garbage (perhaps they made the togari defconfig based off honami, and corrected that when making the togari_brazil defconfig). It doesn't make any difference for me, disabling them keep the touchscreen (MAX1187) functions normal.
Well, back to the point: even when applying these differences to the ZU DooMKernel, the digital TV doesn't work. The app stays a long time in a black screen, and finally closes (FC). I investigated the kmsg and logcat, but nothing useful.
CONFIG_DVB_CORE is "m" by default. I tried insmod'ing every module in /system/lib/modules, but same result. I temporarily gave up, because I don't watch the crap they broadcast on the open TV here. But yeah, it would be good to have everything working...
Click to expand...
Click to collapse
I hadn't got around to diff'ing them I just noticed the DVB line and had a quick look at the brazil defconfig.
I guess there is a binary blob that is needed?
For some reason I have to include the clearpad stuff at the moment in the pimped kernel, I should dig to find out why so the kernel is a tad smaller.
blueether said:
I hadn't got around to diff'ing them I just noticed the DVB line and had a quick look at the brazil defconfig.
I guess there is a binary blob that is needed?
For some reason I have to include the clearpad stuff at the moment in the pimped kernel, I should dig to find out why so the kernel is a tad smaller.
Click to expand...
Click to collapse
Hmm very good insight about the binary blob... It's very possible. I have FTFs for the C6833 and C6843, I'll extract them and compare the file list.
I made it work!! Well, involves some manual steps, but it's a very good progress. I started by comparing the file listing in /system from stock C6833 and C6843 firmwares, and although there is no kernel blob, there ARE some files related to DTV, mostly dynamic libs (.so), some configuration, but most importantly, these two:
Code:
/system/bin/dtvsdserver
/system/bin/dtvserver
So, I insmod'ed every module related to DTV/DVB, and then started these guys... And the TV works! BUT, as soon as I quit the Mobile TV app, the process "dtvserver" is killed with a hangup signal, and opening the app again does not restart it, so I have to manually bring the dtvserver up first (otherwise the same previous issue happens, black screen and finally Mobile TV FC's).
I notice some DTV/DVB modules couldn't be insmod'ed:
Code:
insmod: init_module 'dib3000mc.ko' failed (No such file or directory)
insmod: init_module 'dib7000m.ko' failed (No such file or directory)
insmod: init_module 'dib7000p.ko' failed (No such file or directory)
insmod: init_module 'dib8000.ko' failed (No such file or directory)
insmod: init_module 'dib9000.ko' failed (No such file or directory)
insmod: init_module 'mpq-dmx-hw-plugin.ko' failed (No such file or directory)
insmod: init_module 'tuner-simple.ko' failed (No such file or directory)
But the modules are there, and they are the new ones... I don't get it why they can't be insmod'ed, perhaps something is missing from the kernel config? It could be one of the reasons.
Another thing I've been wondering, is why the DVB modules necessary for the Mobile TV are not loaded automatically, like the wlan module is, for instance. Perhaps a difference in the ramdisk? Something to investigate next.
dbolivar said:
I made it work!! Well, involves some manual steps...
Another thing I've been wondering, is why the DVB modules necessary for the Mobile TV are not loaded automatically, like the wlan module is, for instance. Perhaps a difference in the ramdisk? Something to investigate next.
Click to expand...
Click to collapse
Congrats on getting that far with the DTV, will make for a more complete device for the c6843 users that want to use custom ROMs
Any differences in udev or init.rc or whatever android uses?
Development using the GPL and GPL'd code
The GPL is a very powerful tool, as are the other OSS licences. One has to know how they are used and can/can't be enforced before publishing any code under these licences or modifying code that that been published under a OSS licence. Using a OSS licence brings with it risks and rewords, often these are one and the same.
When we do anything with Android [Linux] kernels we fall under the bounds of the GPL v2 that it is published under. Any modification to the kernel has to be published under the same licence, and we have to publish the newly modified source in a sate that can recreate the binary that you publish to the public/xda.
I'll leave you with this quote from http://programmers.stackexchange.com
...are you prepared to live by it, and let other people use what you've written, rather than just liking it because of what you can get out of it?
Click to expand...
Click to collapse
F2FS mount and sysfs options
Now that we have an F2FS-enabled firmware by default, I've been reading about the mount options and sysfs entries available. As many of us know, there are lots of tweaks out there for EXT4, but what about F2FS? Well, here is the official documentation from the Linux kernel:
https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
As for the mount options, I think only discard could be interesting (but it's questionable, some people say it's better to schedule a regular fstrim call instead). There are also some sysfs tunables which I think can have a noticeable impact in battery life, and performance. Testing them would require a lot of trial and error. I'm pasting them below for those who don't want to go through the full document:
Code:
================================================================================
SYSFS ENTRIES
================================================================================
Information about mounted f2f2 file systems can be found in
/sys/fs/f2fs. Each mounted filesystem will have a directory in
/sys/fs/f2fs based on its device name (i.e., /sys/fs/f2fs/sda).
The files in each per-device directory are shown in table below.
Files in /sys/fs/f2fs/<devname>
(see also Documentation/ABI/testing/sysfs-fs-f2fs)
..............................................................................
File Content
gc_max_sleep_time This tuning parameter controls the maximum sleep
time for the garbage collection thread. Time is
in milliseconds.
gc_min_sleep_time This tuning parameter controls the minimum sleep
time for the garbage collection thread. Time is
in milliseconds.
gc_no_gc_sleep_time This tuning parameter controls the default sleep
time for the garbage collection thread. Time is
in milliseconds.
gc_idle This parameter controls the selection of victim
policy for garbage collection. Setting gc_idle = 0
(default) will disable this option. Setting
gc_idle = 1 will select the Cost Benefit approach
& setting gc_idle = 2 will select the greedy aproach.
reclaim_segments This parameter controls the number of prefree
segments to be reclaimed. If the number of prefree
segments is larger than the number of segments
in the proportion to the percentage over total
volume size, f2fs tries to conduct checkpoint to
reclaim the prefree segments to free segments.
By default, 5% over total # of segments.
max_small_discards This parameter controls the number of discard
commands that consist small blocks less than 2MB.
The candidates to be discarded are cached until
checkpoint is triggered, and issued during the
checkpoint. By default, it is disabled with 0.
ipu_policy This parameter controls the policy of in-place
updates in f2fs. There are five policies:
0: F2FS_IPU_FORCE, 1: F2FS_IPU_SSR,
2: F2FS_IPU_UTIL, 3: F2FS_IPU_SSR_UTIL,
4: F2FS_IPU_DISABLE.
min_ipu_util This parameter controls the threshold to trigger
in-place-updates. The number indicates percentage
of the filesystem utilization, and used by
F2FS_IPU_UTIL and F2FS_IPU_SSR_UTIL policies.
max_victim_search This parameter controls the number of trials to
find a victim segment when conducting SSR and
cleaning operations. The default value is 4096
which covers 8GB block address range.
dir_level This parameter controls the directory level to
support large directory. If a directory has a
number of files, it can reduce the file lookup
latency by increasing this dir_level value.
Otherwise, it needs to decrease this value to
reduce the space overhead. The default value is 0.
ram_thresh This parameter controls the memory footprint used
by free nids and cached nat entries. By default,
10 is set, which indicates 10 MB / 1 GB RAM.
@blueether & @dbolivar :
our primary concern should be to get custom wlan (prima/pronto) drivers working on custom compiled kernel for stock ROMs.. once we have that there are a LOT of features which we can add!
so far I havent had much luck but you can find all my tests here
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_stock_4.3_wlan
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_stock_4.3_wlan_clean
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_z1_gpe_port_wlan
A bookmark
Worth the read @dbolivar
http://forum.xda-developers.com/showthread.php?t=2754997
DooMLoRD said:
@blueether & @dbolivar :
our primary concern should be to get custom wlan (prima/pronto) drivers working on custom compiled kernel for stock ROMs.. once we have that there are a LOT of features which we can add!
so far I havent had much luck but you can find all my tests here
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_stock_4.3_wlan
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_stock_4.3_wlan_clean
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/testing_z1_gpe_port_wlan
Click to expand...
Click to collapse
I'm giving it a try - downloaded the latest sources from CodeAurora and applied to your kernel (adjusting Kconfigs, Makefiles and defconfig). The compilation stops here:
Code:
drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.c: In function ‘wlan_hdd_send_avoid_freq_event’:
drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.c:574:18: warning: assignment makes pointer from integer without a cast
error, forbidden warning: wlan_hdd_cfg80211.c:574
make[3]: *** [drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.o] Error 1
OK, so I edited wlan_hdd_cfg80211.c and changed line 574 to add an explicit cast:
Code:
vendor_event = (struct sk_buff *)cfg80211_vendor_event_alloc(pHddCtx->wiphy,
Then it passes by this point, but stops in following lines with similar errors (not even pasting here). What I noticed from these errors it that CodeAurora's sources seem to be incompatible with Sony's kernel, because for instance, the function cfg80211_vendor_event_alloc is not defined anywhere (ran a grep over all *.c and *.h files in the kernel).
Comparing with a CM11 kernel, this function is also not defined anywhere, but the prima sources are very different, they don't call it. So I thought: let's use CM11's prima sources.
Bingo!
Compiled fine, booted, and with the correspoding firmware in /system/etc/firmware/wlan/prima, WLAN came up normally after boot. :victory:
Now you mentioned something about CM11's prima sources, from what I understood they are not ideal. Is that true? Because there are CM11-based custom kernels which implement intelliplug (dependent on custom WLAN drivers), for instance.
Hope it works for you. In this case, I'll put together a more organized how-to of what I did.
dbolivar said:
I'm giving it a try - downloaded the latest sources from CodeAurora and applied to your kernel (adjusting Kconfigs, Makefiles and defconfig). The compilation stops here:
Code:
drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.c: In function ‘wlan_hdd_send_avoid_freq_event’:
drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.c:574:18: warning: assignment makes pointer from integer without a cast
error, forbidden warning: wlan_hdd_cfg80211.c:574
make[3]: *** [drivers/staging/prima/CORE/HDD/src/wlan_hdd_cfg80211.o] Error 1
OK, so I edited wlan_hdd_cfg80211.c and changed line 574 to add an explicit cast:
Code:
vendor_event = (struct sk_buff *)cfg80211_vendor_event_alloc(pHddCtx->wiphy,
Then it passes by this point, but stops in following lines with similar errors (not even pasting here). What I noticed from these errors it that CodeAurora's sources seem to be incompatible with Sony's kernel, because for instance, the function cfg80211_vendor_event_alloc is not defined anywhere (ran a grep over all *.c and *.h files in the kernel).
Comparing with a CM11 kernel, this function is also not defined anywhere, but the prima sources are very different, they don't call it. So I thought: let's use CM11's prima sources.
Bingo!
Compiled fine, booted, and with the correspoding firmware in /system/etc/firmware/wlan/prima, WLAN came up normally after boot. :victory:
Now you mentioned something about CM11's prima sources, from what I understood they are not ideal. Is that true? Because there are CM11-based custom kernels which implement intelliplug (dependent on custom WLAN drivers), for instance.
Hope it works for you. In this case, I'll put together a more organized how-to of what I did.
Click to expand...
Click to collapse
great!
can you just fork my repo and shift to the branch which worked for you, then send pull request? i will investigate on the Z1...
and yes please do send the steps!
well if we get custom compiled WLAN modules properly working on custom compiled kernel for stock ROM then i can have features like intelli-plug, F2FS, AsyncFS and lots more on stock ROMs!
DooMLoRD said:
great!
can you just fork my repo and shift to the branch which worked for you, then send pull request? i will investigate on the Z1...
and yes please do send the steps!
well if we get custom compiled WLAN modules properly working on custom compiled kernel for stock ROM then i can have features like intelli-plug, F2FS, AsyncFS and lots more on stock ROMs!
Click to expand...
Click to collapse
Well I'm still learning my way around git & GitHub, so I think it will be faster if you just reproduce the steps below:
1) Copy Prima WLAN sources from CM11-based kernel:
I copied from SlimRom's kernel source. Put the sources under drivers/staging/prima.
2) Modify related Kconfig and Makefile:
drivers/staging/Kconfig
Code:
131,132d130
< source "drivers/staging/prima/Kconfig"
<
drivers/staging/Makefile
Code:
58,59d57
< obj-$(CONFIG_PRIMA_WLAN) += prima/
< obj-$(CONFIG_PRONTO_WLAN) += prima/
3) Modify defconfig:
I'm pasting every option related to WLAN. The Prima options should appear after a "make menuconfig".
Code:
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=y
CONFIG_NL80211_TESTMODE=y
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_INTERNAL_REGDB=y
# CONFIG_CFG80211_WEXT is not set
# CONFIG_WIRELESS_EXT_SYSFS is not set
# CONFIG_LIB80211 is not set
# CONFIG_CFG80211_ALLOW_RECONNECT is not set
# CONFIG_MAC80211 is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_PM=y
CONFIG_RFKILL_LEDS=y
# CONFIG_RFKILL_INPUT is not set
# CONFIG_RFKILL_REGULATOR is not set
# CONFIG_RFKILL_GPIO is not set
...
# CONFIG_WIFI_CONTROL_FUNC is not set
...
CONFIG_WLAN=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_LIBRA_SDIOIF is not set
# CONFIG_ATH6K_LEGACY_EXT is not set
CONFIG_WCNSS_CORE=y
CONFIG_WCNSS_CORE_PRONTO=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
CONFIG_WCNSS_REGISTER_DUMP_ON_BITE=y
# CONFIG_ATH_COMMON is not set
# CONFIG_BCMDHD is not set
# CONFIG_BRCMFMAC is not set
# CONFIG_HOSTAP is not set
# CONFIG_IWM is not set
# CONFIG_LIBERTAS is not set
# CONFIG_MWIFIEX is not set
...
#
# Qualcomm Atheros Prima WLAN module
#
CONFIG_PRIMA_WLAN=m
CONFIG_PRONTO_WLAN=y
# CONFIG_PRIMA_WLAN_BTAMP is not set
CONFIG_PRIMA_WLAN_LFR=y
CONFIG_PRIMA_WLAN_OKC=y
CONFIG_PRIMA_WLAN_11AC_HIGH_TP=y
CONFIG_WLAN_FEATURE_11W=y
CONFIG_QCOM_VOWIFI_11R=y
CONFIG_CONFIG_ENABLE_LINUX_REG=y
4) Include Prima WLAN firmware in kernel ZIP file:
Copy from a CM11-based firmware (I used PAC-Rom). Remember to set permissions as 644.
/system/etc/firmware/wlan/prima
Code:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin
5) Include wlan.ko in kernel ZIP file:
Actually I include every compiled kernel module, because we are using a different toolchain and they may benefit from it too. Remember that /system/lib/module/wlan.ko is a symlink, but in my test the target got updated accordingly.
dbolivar said:
Well I'm still learning my way around git & GitHub, so I think it will be faster if you just reproduce the steps below:
1) Copy Prima WLAN sources from CM11-based kernel:
I copied from SlimRom's kernel source. Put the sources under drivers/staging/prima.
2) Modify related Kconfig and Makefile:
drivers/staging/Kconfig
Code:
131,132d130
< source "drivers/staging/prima/Kconfig"
<
drivers/staging/Makefile
Code:
58,59d57
< obj-$(CONFIG_PRIMA_WLAN) += prima/
< obj-$(CONFIG_PRONTO_WLAN) += prima/
3) Modify defconfig:
I'm pasting every option related to WLAN. The Prima options should appear after a "make menuconfig".
Code:
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211=y
CONFIG_NL80211_TESTMODE=y
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_INTERNAL_REGDB=y
# CONFIG_CFG80211_WEXT is not set
# CONFIG_WIRELESS_EXT_SYSFS is not set
# CONFIG_LIB80211 is not set
# CONFIG_CFG80211_ALLOW_RECONNECT is not set
# CONFIG_MAC80211 is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_PM=y
CONFIG_RFKILL_LEDS=y
# CONFIG_RFKILL_INPUT is not set
# CONFIG_RFKILL_REGULATOR is not set
# CONFIG_RFKILL_GPIO is not set
...
# CONFIG_WIFI_CONTROL_FUNC is not set
...
CONFIG_WLAN=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_LIBRA_SDIOIF is not set
# CONFIG_ATH6K_LEGACY_EXT is not set
CONFIG_WCNSS_CORE=y
CONFIG_WCNSS_CORE_PRONTO=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
CONFIG_WCNSS_REGISTER_DUMP_ON_BITE=y
# CONFIG_ATH_COMMON is not set
# CONFIG_BCMDHD is not set
# CONFIG_BRCMFMAC is not set
# CONFIG_HOSTAP is not set
# CONFIG_IWM is not set
# CONFIG_LIBERTAS is not set
# CONFIG_MWIFIEX is not set
...
#
# Qualcomm Atheros Prima WLAN module
#
CONFIG_PRIMA_WLAN=m
CONFIG_PRONTO_WLAN=y
# CONFIG_PRIMA_WLAN_BTAMP is not set
CONFIG_PRIMA_WLAN_LFR=y
CONFIG_PRIMA_WLAN_OKC=y
CONFIG_PRIMA_WLAN_11AC_HIGH_TP=y
CONFIG_WLAN_FEATURE_11W=y
CONFIG_QCOM_VOWIFI_11R=y
CONFIG_CONFIG_ENABLE_LINUX_REG=y
4) Include Prima WLAN firmware in kernel ZIP file:
Copy from a CM11-based firmware (I used PAC-Rom). Remember to set permissions as 644.
/system/etc/firmware/wlan/prima
Code:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin
5) Include wlan.ko in kernel ZIP file:
Actually I include every compiled kernel module, because we are using a different toolchain and they may benefit from it too. Remember that /system/lib/module/wlan.ko is a symlink, but in my test the target got updated accordingly.
Click to expand...
Click to collapse
which branch did u test this with?
also can you please upload the correct firmware (/system/etc/firmware/wlan/prima) which worked for you?
DooMLoRD said:
which branch did u test this with?
also can you please upload the correct firmware (/system/etc/firmware/wlan/prima) which worked for you?
Click to expand...
Click to collapse
The branch from your kernel was master_kk-4.4.2. The Prima WLAN sources were, as I mentioned, from SlimRom's kernel, branch kk4.4.
I'm attaching the firmware to this post.
blueether said:
A bookmark
Worth the read @dbolivar
http://forum.xda-developers.com/showthread.php?t=2754997
Click to expand...
Click to collapse
Wow this is very nice! Follows the same line of research I've been doing, but this is more "elegant" and in-depth, especially because of all the benchmarks and other comparisons he has done. I'll try this approach myself on my custom builds.
One thing I noticed is that we may still have to use the "hammer" approach with the find & replace of the "-O" flags in *.mk and Makefiles I've been doing, because some of them have these flags hardcoded (i.e. they don't take the value from core/combo/TARGET_linux-arm.mk or other base files). I'll tip JustArchi in his thread about it.
Hi guys, I posted this in the general android section and have had no answer, maybe some one here might know?
I'm trying to build AOSP using CM 11's device tree for togari/togari_gpe and have hit a brick wall after solving the first few make errors.
I have to errors, that I suspect are the same problem:
The first is if I just build with make I get this error:
Code:
Import includes file: out/target/product/togari/obj/SHARED_LIBRARIES/copybit.msm8974_intermediates/import_includes
Import includes file: out/target/product/togari/obj/SHARED_LIBRARIES/libmemalloc_intermediates/import_includes
target thumb C++: libqdutils <= hardware/qcom/display/msm8974/libqdutils/profiler.cpp
target thumb C++: libqdutils <= hardware/qcom/display/msm8974/libqdutils/mdp_version.cpp
target thumb C++: libqdutils <= hardware/qcom/display/msm8974/libqdutils/idle_invalidator.cpp
target thumb C++: libqdutils <= hardware/qcom/display/msm8974/libqdutils/comptype.cpp
hardware/qcom/display/msm8974/libqdutils/mdp_version.cpp:33:27: fatal error: linux/msm_mdp.h: No such file or directory
#include <linux/msm_mdp.h>
^
Import includes file: out/target/product/togari/obj/SHARED_LIBRARIES/gps.msm8974_intermediates/import_includes
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libqdutils_intermediates/mdp_version.o] Error 1
make: *** Waiting for unfinished jobs....
and if I do make bootimage I get this:
Code:
make: *** No rule to make target `out/target/product/togari/kernel', needed by `out/target/product/togari/boot.img'. Stop.
I suspect that both stem from aosp not finding the kernel source?
kernel source is at ~/dev/aosp/kernel/sony/msm8974/ and I'm building in ~/dev/aosp
I'm also trying to build vanir aosp using the same device tree and kernel and make bootimage completes fine.
Any help would be great
Yo, @DooMLoRD, @blueether @dbolivar
You guys have probably registred that Geohot (iPhone, PS3 jailbreaker) has successfully rooted the Galaxy S5 (and can now claim the $18,000 bounty), but i just read that this one-click root tool should work on any device running a pre-June 3rd kernel, i.e Android 4.4.2. The question is, does it work on the Ultra? I'm aware that it's easy to root an UItra AS LONG as the bootloader is unlocked, but this thing circumvents that part, and roots it. I think.
Are there anyone here still left on 4.4.2 that can try?
More here: Click
LordManhattan said:
Yo, @DooMLoRD, @blueether @dbolivar
You guys have probably registred that Geohot (iPhone, PS3 jailbreaker) has successfully rooted the Galaxy S5 (and can now claim the $18,000 bounty), but i just read that this one-click root tool should work on any device running a pre-June 3rd kernel, i.e Android 4.4.2. The question is, does it work on the Ultra? I'm aware that it's easy to root an UItra AS LONG as the bootloader is unlocked, but this thing circumvents that part, and roots it. I think.
Are there anyone here still left on 4.4.2 that can try?
More here: Click
Click to expand...
Click to collapse
Can't say... Will have to test
Sent from my C6902 using XDA Free mobile app
DooMLoRD said:
Can't say... Will have to test
Sent from my C6902 using XDA Free mobile app
Click to expand...
Click to collapse
I made a thread here. It should work.
http://forum.xda-developers.com/showthread.php?t=2783982
RIN Kernel for D855/P/K | F400/K/S/L | D852
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve? (Features)
Built with sabermod 4.9 toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW (default)
SIO
TRIPNDROID
VR
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
TCP Congestion Algorithms
BIC
Westwood
Vegas
Veno
Yeah
HTCP
Cubic (default)
Reno
init.d support
intelliplug
intelli thermal v2
Memutil optimizations
Voltage control
SoundControl
OC to 2.7GHz and UC support
Cpu limiter
2-Way Call Recording support
Simple GPU Algorithm
Simple_ondemand GPU Governor fixed
exFat support
ntfs support (bugged)
Oversharpening fix
DriveDroid support
android logger sysfs toggle (disabled by default)
high priority workqueue
Many under the hood fixes
Stability
More to come
How to apply it? (Installation)
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D855/P/K, F400/K/S/L, D852
Custom Recovery
Stock or Stock based ROM (no AOSP)
How to flash the kernel?
Download zip
Place on internal or external SD
Reboot to recovery
Choose install zip
Search for the downloaded zip
Confirm flashing
Wipe cache
Reboot
Have fun
How to boot unbumped kernels?
Only needed for the img files prior version 1.7
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D855:
Code:
fastboot boot D855-rin-1.6.img # boot the kernel
F400:
Code:
fastboot boot F400-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes? (Changelog)
26.11.2014/1.8.5
Less frequency steps to UC (better performance for governors hitting each step)
Oversharpening fix (Credits to @Skin1980)
Kernel now flashed with dd within recovery
Added external radio-iris-transport module to fix fm radio
20.11.2014/1.8
lollipop support (credits to @Skin1980 and his rooted ramdisk)
build with sabermod 4.9
Graphite build flags
NTFS support
sysfs interface for android logger (Logger disabled by default)
TCP cong algorithms (BIC, Westwood, HTCP, Vegas, Veno, Yeah)
More frequency steps between 300Mhz and 2.7Ghz
17.11.2014/1.7.2
Raise max microvolt at cpu for pm8941 and pma8084 (Possible Green Screen Fix)
Additional warnings fixed
11.11.2014/1.7
D852 support added
images bumped
flashable zip
init.d support (busybox required)
AIO optmimizations enabled
intelli plug added (credits to @faux123)
****load of warnings fixed
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
17.08.2014
Support for F400 variants added
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from? (Download)
AndroidFileHost | xda | dev host | google drive | trialsrider1
Let me test!! (Beta Testing Community)
Google+ LG G3 Beta Testing Community
Show me the so(u)rce(ry)! (Source Code)
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
@Dreamxtreme
@guyd
@mosincredible
@tobitege
@AndroidUzer
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
@myfluxi
@trialsrider1
@Skin1980
@Lord Boeffla
@GuneetAtwal
@DooMLoRD
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the LG G3
Contributors
Tectas
Source Code: https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.8.5
Stable Release Date: 2014-11-26
Created 2014-08-14
Last Updated 2015-01-09
Any questions? (FAQ)
How can I toggle the android logger?
File Explorer Method:
Go with a root explorer to /sys/kernel/logger_mode and open the logger_mode file.
Remove everything inside that file and put the number 1 to enable and 0 to disable the logger into it and save the file.
Terminal Method:
Enable the logger
Code:
echo 1 > /sys/kernel/logger_mode/logger_mode
Disable the logger
Code:
echo 0 > /sys/kernel/logger_mode/logger_mode
My internal sd is not working, what to do?
Open adb shell or a terminal emulator and type
Code:
su
restorecon -v -R /data/media
Eccellent!first build for d855,I'm really happy for this!
Is it for 16g,32g or all version?
-------------------LG G3 [D-855]
recovery = stock..
kernel = stock..
rom = stock..
-------------------previous phones:
-ZOPO ZP990 = rom by me
-XPERIA PLAY = kernel by me
-LG L7 = change with xperia play
-MOTOROLA FLIPOUT = OC 1,2ghz
DanieleD'Ignazio said:
Eccellent!first build for d855,I'm really happy for this!
Is it for 16g,32g or all version?
-------------------LG G3 [D-855]
recovery = stock..
kernel = stock..
rom = stock..
-------------------previous phones:
-ZOPO ZP990 = rom by me
-XPERIA PLAY = kernel by me
-LG L7 = change with xperia play
-MOTOROLA FLIPOUT = OC 1,2ghz
Click to expand...
Click to collapse
Works on both.
Sorry I already posted in the source thread, prolly shoulda posted here. Can you do a 851 version? Or will this version work for 851?
Hello, good job, when F400K?
luchino71 said:
Hello, good job, when F400K?
Click to expand...
Click to collapse
When someone sends me the stock boot image for ram disk
Sent from my LG-D855
This can be useful?
https://dl.dropboxusercontent.com/u/30244475/boot.img
luchino71 said:
This can be useful?
https://dl.dropboxusercontent.com/u/30244475/boot.img
Click to expand...
Click to collapse
Yup, perfect, thanks
Thank you for your kernel :good:
So far so good....just test it and I will reporting to you if I found some bugs
1.0.1 is up, small ipv4 fix included
sweet thanks buddy
any chance of this working on the 851
I'd just like to say.. congrats for being the first in the OG Dev section! Bugged me not seeing anything here.
Congratulations for the First Custom Kernel for LG G3...
I wish LG G3 can use LOKI like G2
too bad we still can't boot custom kernel every reboot
btw Smooth Works you got here
awesome bro, just awesome
Good job,bravo
CheesyNutz said:
any chance of this working on the 851
Click to expand...
Click to collapse
Sure, just go to D851 original development section, download the zip of rin, extract the boot image and do the steps described here, just replace the image name to boot, but I'd recommend simply flashing the zip
Sent from my LG-D855
is there a way to make the phone boot on your kernel without a computer ? script or anything ?
Tapatalked from my LG G3
atxbang56 said:
is there a way to make the phone boot on your kernel without a computer ? script or anything ?
Tapatalked from my LG G3
Click to expand...
Click to collapse
Unfortunately not yet, the bootloader has to be more or less tricked to be able to boot the kernel.
Sent from my LG-D855
Tectas said:
Unfortunately not yet, the bootloader has to be more or less tricked to be able to boot the kernel.
Sent from my LG-D855
Click to expand...
Click to collapse
ok I understand (hope that this bootloader unlocked will come soon). so just other questions please :
- onDemand works well with your kernel ?
- is there any other usable governor for gpu ?
I think I'm gonna try to install adb and fastboot at work if I have a reboot or something like that.
thank you for your hard work for such a locked phone....
Tapatalked from my LG G3
Hi guys,
i have a little question.
I know Honor 7 16 gb ( always EU and Cina versions ) it doesn't have NFC sensor ....
Someone who owns the phone 64 gb, can try to test if the sensor works to read the NFC tag ...
Tnx
N.
nwzah said:
Hi guys,
i have a little question.
I know Honor 7 16 gb ( always EU and Cina versions ) it doesn't have NFC sensor ....
Someone who owns the phone 64 gb, can try to test if the sensor works to read the NFC tag ...
Tnx
N.
Click to expand...
Click to collapse
It can't read NFC Tag. There are 3 functionality of NFC:
1. Card emulation mode, allowing the NFC device itself to act as an NFC card. The emulated NFC card can then be accessed by an external NFC reader, such as an NFC POS terminal.
2. Read/Write mode, allowing the NFC device to read and/or write passive NFC tags and stickers.
3. P2P mode, allowing the NFC device to exchange data with other NFC peers; this operation mode is used by Android Beam.
And Honor 7 (PLK-AL10) functions only as a NFC emulator.
Hardware of H7 is work with full function,but Huawei locked p2p & r/w func by system.
you can download Taginfo in play store and it will be work. The native android support is destoried by huawei in stock rom
Hi, I try to use the app taginfo but p2p & r/w don't work... Can you indicated any other app.
Thanks
holti said:
Hi, I try to use the app taginfo but p2p & r/w don't work... Can you indicated any other app.
Thanks
Click to expand...
Click to collapse
Patch to enable p2p & r/w at rooted phone
Code:
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# TURNS_OFF_POLLING_ON_PLK.
-POLLING_TECH_MASK=0x00
+POLLING_TECH_MASK=0xCF
###############################################################################
# Force P2P to only listen for the following technology(s).
@@ -322,7 +322,8 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# DISABLES_RW_&_P2P.
-P2P_LISTEN_TECH_MASK=0x00
+# P2P_LISTEN_TECH_MASK=0x00
+P2P_LISTEN_TECH_MASK=0xC3
PRESERVE_STORAGE=0x01
XBOCT said:
Patch to enable p2p & r/w at rooted phone
Code:
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# TURNS_OFF_POLLING_ON_PLK.
-POLLING_TECH_MASK=0x00
+POLLING_TECH_MASK=0xCF
###############################################################################
# Force P2P to only listen for the following technology(s).
@@ -322,7 +322,8 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# DISABLES_RW_&_P2P.
-P2P_LISTEN_TECH_MASK=0x00
+# P2P_LISTEN_TECH_MASK=0x00
+P2P_LISTEN_TECH_MASK=0xC3
PRESERVE_STORAGE=0x01
Click to expand...
Click to collapse
Hi XBOCT,
thank you so much for your reply. But can you explain how can execute these lines of code. Need root access?
Thanks in advance!
Does this whole thread mean, that the Honor 7 has a NFC chip inside, but it's just not enabled or rather limited by the OS?!
NFC
The 64 GB has one, not the 16 GB one
wormix500 said:
Does this whole thread mean, that the Honor 7 has a NFC chip inside, but it's just not enabled or rather limited by the OS?!
Click to expand...
Click to collapse
holti said:
Hi XBOCT,
thank you so much for your reply. But can you explain how can execute these lines of code. Need root access?
Thanks in advance!
Click to expand...
Click to collapse
FULL NFC FOR PLK-AL10 (rooted)
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.
Tested on PLK-AL10 with 5.11.16 emui custom rom from:
http://club.huawei.com/forum.php?mo...=page=1&filter=typeid&typeid=2520&typeid=2520
Thanks to XBOCT
TO ENTER HUAWEI BEAM:
1. Edit /system/build.prop
2. Change:
ro.config.support_huawei_beam=false to true
3. Save and reboot phone
4. Look at SETTINGS-MORE-NFC
Thanks to tomssy:
http://club.huawei.com/forum.php?mod=redirect&goto=findpost&ptid=5449202&pid=118662160
waliej said:
FULL NFC FOR PLK-AL10 (rooted)
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.
Tested on PLK-AL10 with 5.11.16 emui custom rom from:
http://club.huawei.com/forum.php?mo...=page=1&filter=typeid&typeid=2520&typeid=2520
Thanks to XBOCT
TO ENTER HUAWEI BEAM:
1. Edit /system/build.prop
2. Change:
ro.config.support_huawei_beam=false to true
3. Save and reboot phone
4. Look at SETTINGS-MORE-NFC
Thanks to tomssy:
http://club.huawei.com/forum.php?mod=redirect&goto=findpost&ptid=5449202&pid=118662160
Click to expand...
Click to collapse
will you explan more about this i m confused how to enter this in file many txt are there
this also have to copy?
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.
warriorsach said:
will you explan more about this i m confused how to enter this in file many txt are there
this also have to copy?
Click to expand...
Click to collapse
Install Root Browser.
Go to /system/etc/
Click on libnfc-brcm_PLK.conf and edit in RB Text Editor.
Change digital values and save (they are at the end of file)
With Huawei beam do the same.
Restart phone.
You do not have to copy these files.
does the above method work with PLK-L01 too? (EU version)
thermalboyz said:
does the above method work with PLK-L01 too? (EU version)
Click to expand...
Click to collapse
No - only PLK-AL10 have NFC.
On 6.3.16 huawei beam does no more work, but nfc read works well
Hi! To read nfc tag is strictly necessary to do the root?
i've tried to substitite libnfc config file with the modify one by means of twrp, but it seems that this solution dont work
Inviato dal mio PLK-AL10 utilizzando Tapatalk
doongoo said:
On 6.3.16 huawei beam does no more work, but nfc read works well
Click to expand...
Click to collapse
With 6.3.16
install file Patch_6.3.16_NFC_Volte.zip with TWRP from:
https://userscloud.com/go/itil21gg5p59/
end restart phone
Thank to http://4pda.ru
http://4pda.ru/forum/index.php?showtopic=678766
waliej said:
With 6.3.16
install file Patch_6.3.16_NFC_Volte.zip with TWRP from:
https://userscloud.com/go/itil21gg5p59/
end restart phone
Thank to http://4pda.ru
http://4pda.ru/forum/index.php?showtopic=678766
Click to expand...
Click to collapse
Thank you but I really do not need it (have no another Huawei device, where it could be useful - I mean Huawei beam). In a meantime I already updated to 6.4.1 and made the same modification for NFC-tag reading. I can confirm it works also on this version.
Does the enhanced version (32Gb version a.k.a. Honor 7 Premium) have NFC functionality? I've read various reviews and they claim there's NFC. But when I opened the phone I cannot see any NFC over there. So what gives?
Does Honor 7 have NFC and does it support wireless charging?
Intro-
This is the stock kernel for the T-Mobile SM-P607T Samsung Note 10.1 (2014 Edition) with the following additional features:
Multiple flavors for SELinux preference
CIFS kernel support
NFS kernel support
Force Fast Charge support
Download Options-
Enforcing ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-enforcing-only-1.2.37.tar.md5
SELinux stock behavior, always enforcing
Permissive OPTIONAL - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-optional-1.2.37.tar.md5
SELinux mode can be change with setenforce command
Permissive ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-only-1.2.37.tar.md5
SELinux always permissive
Install-
Reboot into download mode
Open ODIN
Add the kernel file downloaded from link above to AP section
Click start!
How to mount cifs/smb shares-
REQUIREMENTS:
root
busybox
ability to read and follow directions
custom kernel with cifs support (ie the kernel above)
INSTRUCTIONS:
Open a terminal emulator or adb shell
Code:
su
Code:
mkdir /mnt/shares/*share_name*
Code:
busybox mount -t cifs -o username=guest,unc=\\\\*server_ip*\\*share_name*,ip=*server_ip* *server_ip*/*share_name* /mnt/shares/*share_name*
NOTES:
Make sure you replace *server_ip* in the instructions above with the ip address of your server, and *share_name* with the name of your shared folder.
You must mount your shares outside of /storage and /mnt/sdcard for all applications to have access. I have provided a public tmpfs for creating mount points at /mnt/shares.
---Your samba share will now be accessible by all programs/apps under the /mnt/shares directory on root.
How to use Force Fast Charge-
DISPLAY FORCE FAST CHARGE INFO:
Open a terminal emulator or adb shell
Code:
cat /sys/kernel/fast_charge/info
ENABLE FORCE FAST CHARGE MODE:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
SET CUSTOM FORCE FAST CHARGE LEVELS:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 2 > /sys/kernel/fast_charge/force_fast_charge
Code:
echo 1000 > /sys/kernel/fast_charge/usb_charge_level
Code:
echo 2100 > /sys/kernel/fast_charge/ac_charge_level
NOTES:
Force Fast Charge will be disabled by default
When setting custom levels for usb and ac force fast charge, use one of the available values listed when using the display info command above (in the examples I used the max values)
Additional info:
Code:
/*
* Forced Fast Charge - SysFS interface :
* --------------------------------------
*
* /sys/kernel/fast_charge/force_fast_charge (rw)
*
* 0 - disabled (default)
* 1 - substitute AC to USB
* 2 - use custom mA configured through sysfs interface (see below)
*
* /sys/kernel/fast_charge/ac_charge_level (rw)
*
* rate at which to charge when on AC (1.0A/h to 2.1A/h)
*
* /sys/kernel/fast_charge/usb_charge_level (r/w)
*
* rate at which to charge when on USB (0.460A/h to 1.0A/h)
*
* /sys/kernel/fast_charge/wireless_charge_level (r/w)
*
* rate at which to charge when on WIRELESS (0.650A/h to 1.2A/h)
*
* /sys/kernel/fast_charge/failsafe (rw)
*
* 0 - disabled - allow anything up to 2.1A/h to be used as AC / USB custom current
* 1 - enabled - behaviour as described above (default)
*
* /sys/kernel/fast_charge/ac_levels (ro)
*
* display available levels for AC (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/usb_levels (ro)
*
* display available levels for USB (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/wireless_levels (ro)
*
* display available levels for WIRELESS (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/version (ro)
*
* display fast charge version information
*
* /sys/kernel/fast_charge/info (ro)
*
* display complete fast charge configuration in human readable format
*
*/
Changelog
v1.0 - Initial release
v1.1 - Added Enforcing only version (build 21)
v1.2 - Added Force Fast Charge support (build 37)
Thanks/Credits-
mkasick - CIFS/NFS empty mount patch - http://forum.xda-developers.com/showthread.php?t=2106480
blue cat - permissive only patch - http://forum.xda-developers.com/galaxy-note-10-2014/development/kernel-stock-selinux-permissive-kernel-t3232814
chad0989 - force fast charge initial work - http://forum.xda-developers.com/galaxy-nexus/verizon-develop/kernel-patch-devs-force-ac-fast-charging-t1524020
faux123 - force fast charge extensions
yank555-lu - force fast charge note 3 port
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
itsita said:
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
Click to expand...
Click to collapse
I do not know how to adjust the voltage used for charging. Although you did give me an idea to implement the force fast charging kernel mod. I am currently building a test release with the added patches... let the experiments begin!!!
Updated OP
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
oneleft.ak said:
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
Click to expand...
Click to collapse
Thanks! Ill test and post results
Sent from my SM-P605 using Tapatalk
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
tabi304 said:
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
Click to expand...
Click to collapse
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
oneleft.ak said:
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
Click to expand...
Click to collapse
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
I also tried different odin versions but no success
File server error
tabi304 said:
I also tried different odin versions but no success
Click to expand...
Click to collapse
I see what you mean, it appears my file server is altering the file size upon upload.... I am looking into it right now- Will update this thread once it has been corrected.
UPDATE:
Okay, turns out it was the ftp program(FileZilla) I was using to upload the files to my file server. The files have been restored correctly and I have personally tested all three of the links by downloading from my file server and flashing in ODIN.
Thanks for the heads up guys and please let me know if you run into any further issues--
itsita said:
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
Click to expand...
Click to collapse
Maybe now you can finally get the chance to test the force fast charge options!!!
Is this kernel valid for P605 too? Surely not, but just asking....
How do you root the P607T? Also, whats the difference (in laymens terms) between the 3 versions?
Worked well thank you
Set my levels to this - hopefully it speeds up the charge a little
Fast charge mode : 2 - Use custom mA on AC and USB
Custom AC level : 2100mA/h
Custom USB level : 1000mA/h
Custom Wireless level : 650mA/h
Failsafe mode : 1 - Failsafe active (default)
Valid AC levels : 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100
Valid USB levels : 460 500 600 700 800 900 1000
Valid Wireless levels : 650 800 900 1000 1100 1200
I flashed the kernel from here, and followed the steps, when i go to check /sys/kernel/fast_charge/info to see if it worked, all i get is permission denied.
no matter what kernel ive used in the past on this tablet ive gotten "permission denied" like trying to set up linux deploy or linux on android. I am rooted, I am using a Permissive kernel, Busy Box installed. So what gives?
Can this be used in P605 ? TY !!
Istarth said:
Can this be used in P605 ? TY !!
Click to expand...
Click to collapse
Yes. It was also the kernel inside Pyrana v27.
zombie thread warning*
So as i understand it, you can use kernels for older roms on newer releases right?
So for example, im trying out an unofficial lineage os rom, and it does not have fast charge support baked in, nothing through kernel auditor or 3c toolbox that can be changed. Could I flash this kernel and add support to the rom that way? The dinosaur charging speeds on this thing is really inconvenient if I ever forget to charge it overnight.
Please, links down.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- you tell me
G9 Play - Ilitek (Work)
G9 Play - Himax (Dead)
G9 Play - Goodix, Chipone (untested)
G9 Power - Novatek (Work)
G9 Power - Focaltech (Untested)
E7 Plus - goodix,himax,chipone (Untested)
Install guide (Might not work):
To flash:
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Download:
GUAMP: MEGA
CEBU: MEGA
GUAM: soon
Reccomended ADB and Fastboot binaries:
platform-tools
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/100Daisy/android_device_motorola_guamp
Kernel source: prebuilt (for now)
Join our device chat in Telegram !
no link xda will remove anyways
gitdaisy applause circle:
https://t.me/GitDaisyShitposting
Donations:
paypal.me/100Daisy
Credits:
I want to say a big thanks to the testers @borraz
Hi! not work touchscreen in HImax.
condor323 said:
Hi! not work touchscreen in HImax.
Click to expand...
Click to collapse
contact me on Telegram @GitDaisy
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
jarchig said:
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
Click to expand...
Click to collapse
I will cover that issue in next release, then i will focus on bringing one image for all bengal devices released with A10 (G30 has vendor_boot and dt seems to not be compatible and kernel may be not compatible too)
currently i need to ship different prebuilts for all devices
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
@Mauricio Oliveira , you have the correct smartphone model (guamp). It is the same as mine.
However, there are several touchscreen variants and your application (cpu-z) does not show which variant you have.
Can you install the 'Device Info HW' application? Your touchscreen will show in the 'General' tab.
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
Another way to find out your touchscreen manufacturer is by connecting to your mobile using the ‘adb shell’ command.
From your desktop, run:
Code:
adb shell
and then
Code:
getevent
the command will show output like the following:
Code:
guamp:/ # getevent
add device 1: /dev/input/event2
name: "chipone-tddi"
add device 2: /dev/input/event0
name: "qpnp_pon"
add device 3: /dev/input/event1
name: "gpio-keys"
In this case, ‘chipone-tddi’ is the touchscreen manufacturer.
ok, obrigado pelo feedback .
Hello everyone on the forum... Thanks again my friend jarchig. I noticed that my screen variant is the same as yours... Read in your posts that you have successfully added commands to enable it. Could you teach step by step how to do this?
Thank you in advance.
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
did twrp work for anyone?
piperoman said:
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
Click to expand...
Click to collapse
I see that nobody respond to you...
I use the image from the link that you share, specifically RETLA. You must download the zip file, decompress it and you can see the vbmeta.img file
GitDaisy said:
contact me on Telegram @GitDaisy
Click to expand...
Click to collapse
it doesn't work for me too, the himax touchscreen ,guamp version, can you help me?
If the android version is 11 how does it work? mine has android 11 sorry i think there is no solution for me