Related
Cifs manager, any got out could build a working cifs.ko file?
Sent from my LG-D955 using XDA Premium 4 mobile app
tutreak said:
Cifs manager, any got out could build a working cifs.ko file?
Sent from my LG-D955 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for knocking a 9 month old Thread , but I am trying to make Cifs Manager work for my Gflex.
i'm running Android 4.4.2 , Kernel 3.4.0 Build KOT49I.D95520a .
I've Downloaded the Kernel Source tar.gz from LG : LGD955_Gflex_Kikat_V20a_Kernel.tar.gz
And I just cannot seem to produce a cifs.ko module that is succesfully loaded with insmod on the device.
I keep getting this in dmesg: no symbol version for module_layout
I was trying to use this thread for instructions: http://forum.xda-developers.com/showthread.php?t=2531407&page=3
and this http://forum.xda-developers.com/showthread.php?t=2531407&page=3
@TheWizardOfROMs Maybe if you have some time you can give some useful advice
@ forrestgump2000 How did you do it for LG G2 ? It should be almost the same for the Gflex, could you perhaps lend a hand? Please?
I am trying to build it on Mac OSX , installed with macports gcc4.9 , using CROSS_COMPILE=/Downloads/android-ndk-r10c/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/bin/arm-linux-androideabi- , ARCH=arm,SUBARCH=arm
make EXTRA_CFLAGS=-fno-pic M=fs/cifs Tells me about some versioning , then I run make modules before to create that file and then it doesn't complain.
Running out of ideas..... (will try a Ubuntu VM soon if nothing works...)
Thank you!
2nd really need this for off device storage
Work documentation
I've sent an e-mail to LG , let's see what happens....
"
Dear LG OpenSource Team,
I am currently trying very hard to compile a new module for my current kernel:LGD955_Gflex_Kikat_V20a_Kernel.zip
My work environment is the following:
Vmware Ubuntu 14.01 LTS , gcc 4.8
I have unpacked your kernel source and tried the following:
cp arch/arm/configs/z-open-com-perf_defconfig .
make z-open-com-perf_defconfig prepare headers_install scripts ARCH=arm CROSS_COMPILE=arm-linux-androideabi- O=build KERNELRELEASE=3.4.0-perf-g551cabf
make menuconfig ARCH=arm CROSS_COMPILE=arm-linux-androideabi- O=build KERNELRELEASE=3.4.0-perf-g551cabf
Chosen Network File System Support -> CIFS (M) and saved.
make modules ARCH=arm CROSS_COMPILE=arm-linux-androideabi- O=build KERNELRELEASE=3.4.0-perf-g551cabf
adb push fs/cifs/cifs.ko /data/local/modules/
chmod 644 /data/local/modules/cifs.ko
insmod /data/local/modules/cifs.ko gives this Failure Message : … failed (Exec format error)
dmesg has this message inside: no symbol version for module_layout
A little info after building the module:
[email protected]:~/Downloads/kernel$ modinfo build/fs/cifs/cifs.ko
filename: /home/adi/Downloads/kernel/build/fs/cifs/cifs.ko
version: 1.78
description: VFS to access servers complying with the SNIA CIFS Specification e.g. Samba and Windows
license: GPL
author: Steve French <sfr[email protected]>
srcversion: 3F86E0A9406EADE34D14793
depends:
intree: Y
vermagic: 3.4.0-perf-g551cabf SMP preempt mod_unload modversions ARMv7
parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (int)
parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64 (int)
parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256 (int)
parm: cifs_max_pending:Simultaneous requests to server. Default: 32767 Range: 2 to 32767. (int)
parm: enable_oplocks:Enable or disable oplocks (bool). Default:y/Y/1 (bool)
[email protected]:/ # uname -r
3.4.0-perf-g551cabf
[email protected]:/ # uname -a
Linux localhost 3.4.0-perf-g551cabf #1 SMP PREEMPT Tue Apr 29 00:20:47 KST 2014 armv7l GNU/Linux
I am running out of ideas , could you please help ? What am I doing wrong? I love this Phone and want to learn more about it’s inner workings but when compiling a module fails , it leaves me a little hopeless…
Thank you in advance,
With kind regards,
Adrian
"
Fingers crossed
Hi! I don't know where to start but I need some help.
I develop for the Samsung Galaxy Music (GT-S6010/L/12) and it had stock 4.1, and I've built cm 10.1 and cm 11.0
Well, the problem is that I haven't been able to fix bluetooth for months so that's why I'm asking for help. I will try to give as much information as possible.
So I suppose the main problem is the change of the bluetooth stack from bluez to bluedroid that made the problems. Actually on cm 10.1 and cm 11.0, I can get bluetooth activated but will face issues trying to send or receive files, so it's practically not working :-/
The device uses the broadcom bcm21654 chip and for wireless I think it uses the bcm4334
So the only fixed I've tried is apply this commits into the kernel:
https://github.com/pawitp/android_k...mmit/db7edee95ba440e9c19439e43bb0464a0c1ea382
https://github.com/pawitp/android_k...mmit/23d47cdd2d415836b2d4d1eccbf6dc622bf8dbd6
And apply this to the source (for cm 10.1) or this (for cm 11.0)
Those fixes works for the Galaxy Pocket Neo and Galaxy Grand Duos, BUT, for my device, by just enabling CONFIG_BCM_BT_LPM in the kernel's defconfig, makes the phone to freeze when activating bluetooth:crying: I've already taken logcats and kmsg but they don't seem to be pretty usefull
Here is the kmsg at the moment of freezing (full avaible here):
Code:
<6>[ 160.767547] AUDCTRL_SetAudioMode_ForMusicPlayback mode 4, pathID 1
<6>[ 160.767547] AUDDRV_SetAudioMode_Speaker mode=4, app 2, pathID 1
<6>[ 160.767578] AUDDRV_SetAudioMode_Speaker: mixOutGain 0xfffffe0c, mixOutGainR 0xfffffe0c, mixBitSel 5, mixBitSelR 5
<6>[ 160.767608] AUDDRV_SetAudioMode_Speaker pathID 1 outChnl 0x8 inChnl 0xc0
<6>[ 160.767608] mixInGain 0x0, mixInGainR 0x0
<6>[ 160.767639] AUDDRV_SetAudioMode_Speaker pathID 1 outChnl 0x4 inChnl 0xc0
<6>[ 160.767639] mixInGain 0x0, mixInGainR 0x0
<6>[ 160.767669] setExternAudioGain mode 4, app 2
<6>[ 160.767669] extern_ihf_set_gain gain_mB=400, pmu_gain_enum=0x3f
<6>[ 160.768096] org_suspendedPowerOnAMP 0 suspendedAmpUse 4
<6>[ 161.077636] bcm_bt_rfkill_setpower: blocked Low [POWER_OFF]
<6>[ 161.090850] bcm_bt_rfkill_setpower: unblocked High [POWER ON]
I've already tried many things but with no success. Does porting bluez to cm 10.1 and cm 11 is an option?
Also I want to make clear that I'm not an experienced developer, I'm just a high school student with nearly 17 years old, so I don't know too much about coding or solving this kind of problems, any help is appreciated.
Also, the device tree and kernel source are avaible on my github
Should you find yourself in a legit need to change the mac address (for testing, debugging etc), a simple 'busybox ifconfig wlan0 hwaddr' won't work (returning auth errors).
It looks like the mac address needs to be encoded into /persist/wifi/.macaddr
Backup the .macaddr file and issue the following:
Code:
echo -e "\x00\x11\x22\x33\x44\x55" > /persist/wifi/.macaddr
Turn the wifi off and on and the resulting MAC will be 00:11:22:33:44:55
If you want to emulate an Apple device (can obviously be anything but this was easy to extract), the following script will give you a random MAC:
Code:
#!/system/xbin/bash
apple=( 00:03:93 00:05:02 00:0A:27 00:0A:95 00:0D:93 00:10:FA 00:11:24 00:14:51 00:16:CB 00:17:F2 00:19:E3 00:1B:63 00:1C:B3 00:1D:4F 00:1E:52 00:1E:C2 00:1F:5B 00:1F:F3 00:21:E9 00:22:41 00:23:12 00:23:32 00:23:6C 00:23:DF 00:24:36 00:25:00 00:25:4B 00:25:BC 00:26:08 00:26:4A 00:26:B0 00:26:BB 00:30:65 00:3E:E1 00:50:E4 00:61:71 00:6D:52 00:88:65 00:A0:40 00:C6:10 00:F4:B9 00:F7:6F 04:0C:CE 04:15:52 04:1E:64 04:26:65 04:48:9A 04:54:53 04:69:F8 04:DB:56 04:E5:36 04:F1:3E 04:F7:E4 08:00:07 08:70:45 08:74:02 0C:15:39 0C:30:21 0C:3E:9F 0C:4D:E9 0C:74:C2 0C:77:1A 0C:BC:9F 10:1C:0C 10:40:F3 10:41:7F 10:93:E9 10:9A:DD 10:DD:B1 14:10:9F 14:5A:05 14:8F:C6 14:99:E2 18:20:32 18:34:51 18:9E:FC 18:AF:61 18:AF:8F 18:E7:F4 18:EE:69 18:F6:43 1C:1A:C0 1C:AB:A7 1C:E6:2B 20:78:F0 20:7D:74 20:9B:CD 20:A2:E4 20:C9:D0 24:24:0E 24:A0:74 24:A2:E1 24:AB:81 24:E3:14 28:0B:5C 28:37:37 28:5A:EB 28:6A:B8 28:6A:BA 28:CF:DA 28:CF:E9 28:E0:2C 28:E1:4C 28:E7:CF 28:F0:76 2C:1F:23 2C:B4:3A 2C:BE:08 2C:F0:EE 30:10:E4 30:90:AB 30:F7:C5 34:12:98 34:15:9E 34:36:3B 34:51:C9 34:A3:95 34:C0:59 34:E2:FD 38:0F:4A 38:48:4C 38:C9:86 3C:07:54 3C:15:C2 3C:AB:8E 3C:D0:F8 3C:E0:72 40:30:04 40:33:1A 40:3C:FC 40:6C:8F 40:A6:D9 40:B3:95 40:D3:2D 44:2A:60 44:4C:0C 44:D8:84 44:FB:42 48:43:7C 48:60:BC 48:74:6E 48:D7:05 48:E9:F1 4C:7C:5F 4C:8D:79 4C:B1:99 50:7A:55 50:EA:D6 54:26:96 54:4E:90 54:72:4F 54:9F:13 54:AE:27 54:E4:3A 54:EA:A8 58:1F:AA 58:55:CA 58:7F:57 58:B0:35 5C:59:48 5C:8D:4E 5C:95:AE 5C:96:9D 5C:97:F3 5C:AD:CF 5C:F5:DA 5C:F9:38 60:03:08 60:33:4B 60:69:44 60:92:17 60:C5:47 60:D9:C7 60:F8:1D 60:FA:CD 60:FB:42 60:FE:C5 64:20:0C 64:76:BA 64:9A:BE 64:A3:CB 64:B9:E8 64:E6:82 68:09:27 68:5B:35 68:64:4B 68:96:7B 68:9C:70 68:A8:6D 68:AE:20 68:D9:3C 6C:3E:6D 6C:40:08 6C:70:9F 6C:94:F8 6C:C2:6B 70:11:24 70:14:A6 70:3E:AC 70:48:0F 70:56:81 70:73:CB 70:CD:60 70:DE:E2 70:E7:2C 70:EC:E4 74:81:14 74:E1:B6 74:E2:F5 78:31:C1 78:3A:84 78:6C:1C 78:7E:61 78:9F:70 78:A3:E4 78:CA:39 78:D7:5F 78:FD:94 7C:01:91 7C:11:BE 7C:6D:62 7C:6D:F8 7C:C3:A1 7C:C5:37 7C:D1:C3 7C:F0:5F 7C:FA:DF 80:00:6E 80:49:71 80:92:9F 80:BE:05 80:D6:05 80:E6:50 80:EA:96 84:29:99 84:38:35 84:78:8B 84:85:06 84:8E:0C 84:B1:53 84:FC:FE 88:1F:A1 88:53:95 88:63:DF 88:C6:63 88:CB:87 8C:00:6D 8C:29:37 8C:2D:AA 8C:58:77 8C:7B:9D 8C:7C:92 8C:FA:BA 90:27:E4 90:3C:92 90:72:40 90:84:0D 90:8D:6C 90:B2:1F 90:B9:31 90:FD:61 94:94:26 94:E9:6A 94:F6:A3 98:03:D8 98:5A:EB 98:B8:E3 98:D6:BB 98:E0:D9 98:F0:AB 98:FE:94 9C:04:EB 9C:20:7B 9C:29:3F 9C:35:EB 9C:F3:87 9C:FC:01 A0:18:28 A0:99:9B A0:ED:CD A4:31:35 A4:5E:60 A4:67:06 A4:B1:97 A4:B8:05 A4:C3:61 A4:D1:D2 A8:20:66 A8:5B:78 A8:66:7F A8:86:DD A8:88:08 A8:8E:24 A8:96:8A A8:BB:CF A8:FA:D8 AC:29:3A AC:3C:0B AC:7F:3E AC:87:A3 AC:BC:32 AC:CF:5C AC:FD:EC B0:34:95 B0:65:BD B0:9F:BA B4:18:D1 B4:F0:AB B8:09:8A B8:17:C2 B8:44:D9 B8:78:2E B8:8D:12 B8:C7:5D B8:E8:56 B8:F6:B1 B8:FF:61 BC:3B:AF BC:4C:C4 BC:52:B7 BC:67:78 BC:6C:21 BC:92:6B C0:1A:DA C0:63:94 C0:84:7A C0:9F:42 C0:CE:CD C0:F2:FB C4:2C:03 C8:1E:E7 C8:2A:14 C8:33:4B C8:69:CD C8:6F:1D C8:85:50 C8:B5:B7 C8:BC:C8 C8:E0:EB C8:F6:50 CC:08:E0 CC:20:E8 CC:29:F5 CC:78:5F CC:C7:60 D0:03:4B D0:23:DB D0:25:98 D0:33:11 D0:4F:7E D0:A6:37 D0:E1:40 D4:9A:20 D4:F4:6F D8:00:4D D8:1D:72 D8:30:62 D8:96:95 D8:9E:3F D8:A2:5E D8:BB:2C D8:CF:9C D8:D1:CB DC:2B:2A DC:2B:61 DC:37:14 DC:86:D8 DC:9B:9C E0:66:78 E0:AC:CB E0:B5:2D E0:B9:BA E0:C9:7A E0:F5:C6 E0:F8:47 E4:25:E7 E4:8B:7F E4:98:D6 E4:C6:3D E4:CE:8F E8:04:0B E8:06:88 E8:80:2E E8:8D:28 EC:35:86 EC:85:2F F0:24:75 F0:99:BF F0:B0:E7 F0:B4:79 F0:C1:F1 F0:CB:A1 F0:D1:A9 F0:DB:E2 F0:DB:F8 F0:DC:E2 F0:F6:1C F4:1B:A1 F4:37:B7 F4:F1:5A F4:F9:51 F8:1E:DF F8:27:93 FC:25:3F FC:E9:98 FC:FC:48 )
array=( 1 2 3 4 5 6 7 8 9 0 a b c d e f )
newmac=\\x${array[$RANDOM%16]}\\x${array[$RANDOM%16]}:\\x${array[$RANDOM%16]}${array[$RANDOM%16]}:\\x${array[$RANDOM%16]}\\x${array[$RANDOM%16]}
vendor=$(echo "${apple[$RANDOM%406]}"|sed 's/:/\\x/g')
echo -e "\x$vendor$newmac" > /persist/wifi/.macaddr
Can be combined with Tasker if you want to randomize it every time Wi-Fi is turned off/on.
*NOTE - this has been tested on KitKat 4.4.4 - not sure if it still works on 5.x
Android Open Source Project 7.1
Nougat
for
Samsung Galaxy Tab 10.1
(p4wifi / GT-P7510)
(p4 / GT-P7500)
(p4tmo / SGH-T859)
Customizations:
busybox
init.d scripts
stagefright ffmpeg codecs
Kernel features:
CPU overclock (1.2Ghz - 1.6Ghz)
CPU voltage control
CPU temperature readings
GPU overclock (400Mhz)
L2 cache optimization
F2FS
SELinux
Voodoo Sound
USB Charging
Updated WIFI driver
ZRAM backports
sdcardfs
Working:
Video
Audio
Wifi
3G / Cellular
- Insert a sim card before power on
GPS
Bluetooth
- Audio playback: working
- File transfer: working
Sensors
Encryption
Not working / Known issues:
Camera
- Photos: Working, flash not working
- Video recording: 720p not working
Incompatible/unsupported apps:
Many app developers do not support this device anymore. For these apps you have three options:
Use previous versions of the app which were compatible with this device.
(APKMirror.com hosts many previous versions of apps.)
Try the incompatible app anyways. It may run under NEON emulation. Emulation is very slow. The ideal way is to use previous versions of the app which are compatible with this device.
Contact the app developer and ask them to maintain support for Tegra 2 devices.
Installation:
Backup all data
Install TWRP 3.0
Wipe cache, dalvik cache, system, data
Install the ROM
Optional steps:
- Install gapps pico
- Install phh Superuser
Boot the ROM
Enable on screen keyboard by toggling "Show input method"
Installation issues:
- If it freezes when installing the ROM then use TWRP 2.8.7.0.
Downloads:
Download Page
TWRP
TWRP 3.0
GApps
for Android 7.1 - 7.1.1
- P7500-open_gapps-arm-7.1-pico-20170119.zip
for Android 7.1.2
- P7500-open_gapps-arm-7.1-pico-20170416.zip
Root methods:
Magisk
https://forum.xda-developers.com/apps/magiskphh's SuperUser
1. https://superuser.phh.me/superuser.zip
2. phh's SuperUserCCMT SuperSU
http://forum.xda-developers.com/apps/supersu
Change log:
Code:
20171005
- NEON emulation fixes
- Revert to stock sqlite
20170914
- BlueBorne patches
- System WebView 61.0.3163.81
20170807
- Update to android-7.1.2_r28
- System WebView 60.0.3112.78
- Update to sqlite 3.19.0
20170506
- Update to android-7.1.2_r8
- System WebView 58.0.3029.83
- NEON emulation speed improvements
20170422
- Optimize hwui properties
- Limit dex2oat threads
- Fix NEON emulation bug
- System WebView 57.0.2987.132
- Add back Browser app
20170415
- Update to android-7.1.2_r2
- Fix SystemUpdateService wakelock
- Disable search bar option for Launcher3
- Better GPS locking
20170320
- NEON emulation
20170307
- Update to android-7.1.1_r24
- Substratum theme engine
- Signature Spoofing
- kernel fixes
20170214
- Update to android-7.1.1_r15
- Update system webview to 56.0
20170118
- Update to android-7.1.1_r12
- Fix hwcomposer
- Update sqlite
- Remove Music app / Add Apollo app
- Widevine support
20161229
- Add WallpaperPicker app
- Fix glitchy wallpapers
- Enable productivity mode for file browser
- Enable lightweight doze
- Update F2FS
Donate:
via Paypal
XDA:DevDB Information
Android 7.1.2 Nougat, ROM for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Alpha
Created 2016-09-30
Last Updated 2017-10-05
Nougat Tips:
Enable USB file transfer:
Built-in file manager:
Settings > Storage > Explore
SystemUI Tuner / Navigation Bar Tuner:
Pull down notification shade
Long press settings gear
Split screen:
Long press Overview button
Switch to last app:
Double tap Overview button
Stock Browser app crash when downloading files
- Settings > Apps > Browser > Permissions > Enable Storage permission
Chromium browser for Tegra 2 devices
Chromium 56.0Last known non-NEON versions of Google apps:
Chrome 49.0
Gboard 6.0.69
Maps 9.44
Google Play services 10.0.84
Google Play services 10.5.42 beta
When using previous versions of apps, disable auto updates:
Error reporting guide:
Saying "it doesn't work" is not helpful. I cannot see what your problem is from here.
Save and upload the system logs from your device so that I can see what happening on your device.
How to save system logs:
Root the device.
Install SysLog.
Reboot the system.
Reproduce the problem.
Open Syslog app and save the Kernel Log and Main Log.
Send me the log files stored in /sdcard/Syslog.
Share the files on Google Drive or another similar service.
Then PM me a link to the files. Please describe exactly what the issue is.
Downloading and testing, thanks @ decatf
P4 version,
1. Sim not detect so 3G / Cellular not work..
2. baseband not show..
3. phh's SuperUser not install
Hi decatf,
first of all *thanks a lot* for bringing Android 7 to our device, this is brilliant! Quick question: any specific reason that you suggest phh's SuperUser instead of Chainfires SuperSU?
Kind regards,
mistersixt.
Ok, looks pretty promising already, the steps I did:
- Ran Titanium Backup for all user apps
- Rebooted into TWRP 3.0.0.0
- Full wipe
- Installed aosp-7.0-p4-20160929.zip
- Installed todays OpenGapps (pico)
- Installed phh's SuperSu
- Reboot
- TitaniumBackup first did not get root access
- Installed phh's App from Play Store
- Reboot
- Titanium Backup does get root access now
So far it feels smooth, no errors or force closes... I am pretty impressed . I will test the SIM card this evening as I don't have a spare one with me right now.
Thanks again decatf!!!!
Kind regards, mistersixt.
Good
Sent from my Alps U685Q using XDA Labs
---------- Post added at 10:04 AM ---------- Previous post was at 09:56 AM ----------
Oh, so fast
Sent from my Alps U685Q using XDA Labs
Ok, first small issue: I cannot get AdAway adjusting the hosts file, when trying to flash the AdAway systemless package in recovery it fails with error 4 or something (although I don't know whether the systemless is necessary here), and when running the AdAway App itself it fails with:
Code:
...
09-30 11:21:15.916 2081 2081 E linker : normalize_path - invalid input: "null", the input path should be absolute
09-30 11:21:15.916 2081 2081 W linker : Warning: unable to normalize "null"
09-30 11:21:15.917 2079 2079 D su : sending code
09-30 11:21:15.950 2083 2083 E linker : normalize_path - invalid input: "null", the input path should be absolute
09-30 11:21:15.950 2083 2083 W linker : Warning: unable to normalize "null"
09-30 11:21:16.014 2082 2082 D su : child exited
09-30 11:21:16.017 2083 2083 D su : client exited 0
09-30 11:21:16.036 2081 2081 D su : starting daemon client 10079 10079
09-30 11:21:16.067 2086 2086 E linker : normalize_path - invalid input: "null", the input path should be absolute
09-30 11:21:16.067 2086 2086 W linker : Warning: unable to normalize "null"
09-30 11:21:16.130 2086 2086 D su : connecting client 2080
09-30 11:21:16.171 2005 2005 D ICU : No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
09-30 11:21:16.173 2087 2087 D su : remote pid: 2080
09-30 11:21:16.222 2089 2089 D su : remote pts_slave:
09-30 11:21:16.276 2090 2090 D su : remote uid: 10079
09-30 11:21:16.336 2091 2091 D su : remote req pid: 1420
09-30 11:21:16.399 2092 2092 D su : remote args: 1
09-30 11:21:16.466 2096 2096 D su : su invoked.
09-30 11:21:16.486 2094 2094 D su : waiting for child exit
09-30 11:21:16.503 2097 2097 W su : hacks: Testing (com.keramidas.TitaniumBackup:0:10064)
09-30 11:21:16.552 2098 2098 D su : db allowed
09-30 11:21:16.617 2099 2099 W su : hacks: Testing (com.keramidas.TitaniumBackup:10079), 44451
09-30 11:21:16.652 2039 2039 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
09-30 11:21:16.658 2039 2039 D AndroidRuntime: CheckJNI is OFF
09-30 11:21:16.709 2101 2101 D su : 10079 /sbin/su executing 0 /system/bin/sh using binary /system/bin/sh : sh
09-30 11:21:16.839 2039 2039 D ICU : No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
09-30 11:21:16.911 2039 2039 W art : Failed to stat, will retry: /data/dalvik-cache/arm/[email protected]@[email protected]: No such file or directory
09-30 11:21:16.977 2005 2005 E memtrack: Couldn't load memtrack module (No such file or directory)
09-30 11:21:16.977 2005 2005 E android.os.Debug: failed to load memtrack module: -2
09-30 11:21:16.979 2005 2005 I Radio-JNI: register_android_hardware_Radio DONE
09-30 11:21:17.007 2039 2039 E memtrack: Couldn't load memtrack module (No such file or directory)
09-30 11:21:17.007 2039 2039 E android.os.Debug: failed to load memtrack module: -2
09-30 11:21:17.010 2039 2039 I Radio-JNI: register_android_hardware_Radio DONE
09-30 11:21:17.013 1420 1774 E AdAway : Exception:
09-30 11:21:17.013 1420 1774 E AdAway : org.adaway.util.CommandException
09-30 11:21:17.013 1420 1774 E AdAway : at org.adaway.util.ApplyUtils.copyHostsFile(ApplyUtils.java:186)
09-30 11:21:17.013 1420 1774 E AdAway : at org.adaway.service.ApplyService.apply(ApplyService.java:427)
09-30 11:21:17.013 1420 1774 E AdAway : at org.adaway.service.ApplyService.doWakefulWork(ApplyService.java:102)
09-30 11:21:17.013 1420 1774 E AdAway : at com.commonsware.cwac.wakeful.WakefulIntentService.onHandleIntent(WakefulIntentService.java:100)
09-30 11:21:17.013 1420 1774 E AdAway : at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:67)
09-30 11:21:17.013 1420 1774 E AdAway : at android.os.Handler.dispatchMessage(Handler.java:102)
09-30 11:21:17.013 1420 1774 E AdAway : at android.os.Looper.loop(Looper.java:154)
09-30 11:21:17.013 1420 1774 E AdAway : at android.os.HandlerThread.run(HandlerThread.java:61)
09-30 11:21:17.095 2117 2117 D su : sending code
09-30 11:21:17.105 2119 2119 E linker : normalize_path - invalid input: "null", the input path should be absolute
09-30 11:21:17.105 2119 2119 W linker : Warning: unable to normalize "null"
09-30 11:21:17.121 2119 2119 D su : client exited 0
09-30 11:21:17.134 2118 2118 D su : child exited
Regards, mistersixt
I can't download it
Sent from my Alps U685Q using XDA Labs
mistersixt said:
Hi decatf,
first of all *thanks a lot* for bringing Android 7 to our device, this is brilliant! Quick question: any specific reason that you suggest phh's SuperUser instead of Chainfires SuperSU?
Kind regards,
mistersixt.
Click to expand...
Click to collapse
SuperSU doesn't work anymore on this device. Chainfire sold it to CCMT. Some shadowy mysterious group. So who knows what kind of support it will receive from here on out.
phh Superuser works. It seems that some apps can't detect it right. It's the only option that works right now.
To use Adaway you need to mount /system as read/write.
Code:
mount -o rw,remount /system
Install hosts file.
Set /system back to read-only.
Code:
mount -o ro,remount /system
decatf said:
To use Adaway you need to mount /system as read/write.
Code:
mount -o rw,remount /system
Install hosts file.
[/CODE]
Click to expand...
Click to collapse
Thanks a lot, that did the trick.
One more thing: I cannot overclock the CPU, although Kernel Adiutor is showing a max frequency of 1400 Mhz for example the CPU is stuck with a max frequency of 1000 Mhz, and here and there I see messages like:
Code:
E P3 PowerHAL: Error opening /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied
.
Regards, mistersixt.
mistersixt said:
Thanks a lot, that did the trick.
One more thing: I cannot overclock the CPU, although Kernel Adiutor is showing a max frequency of 1400 Mhz for example the CPU is stuck with a max frequency of 1000 Mhz, and here and there I see messages like:
Code:
E P3 PowerHAL: Error opening /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: Permission denied
.
Regards, mistersixt.
Click to expand...
Click to collapse
It works for me.
Kernel Adiutor sets the permissons on that to read-only for some reason. The default in Android is r/w (0660). So it ends up preventing everything else from using that sysfs file unless they also change the permissions before writing it. This breaks the default behavior. Kind of strange.
Code:
# logcat -s "Control"
09-30 11:25:43.201 2965 3172 I Control : chmod 644 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
09-30 11:25:43.206 2965 3174 I Control : echo '1400000' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
09-30 11:25:43.252 2965 3175 I Control : chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
09-30 11:25:43.285 2965 3177 I Control : chmod 644 /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
09-30 11:25:43.289 2965 3179 I Control : echo '1400000' > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
09-30 11:25:43.320 2965 3180 I Control : chmod 444 /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
09-30 11:25:43.328 2965 3182 I Control : saved /sys/devices/system/cpu/cpu%d/cpufreq/scaling_max_freq0
Hello,decatf.Can you send me some apps supported AndroidN[emoji12]
通过我的 GT-P7510 上的 Tapatalk发言
Cellular ain't working, cannot detect SIM card. Still testing the ROM, props to the dev! Also found white-on-white text.
For p4wifi I use the arm 7.0 Gapps?
So good,not any bugs
Sent from my Redmi 3S using XDA-Developers mobile app
Where can I find the latest twrp?
bmakk2055 said:
Where can I find the latest twrp?
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/devdb/project/?id=12880#downloads
Enviado desde mi XT1524 mediante Tapatalk
Sometimes it freezes when the device is locked... :/ but the performance and everything else is great
Hi all!
What is this?
This is my mostly-working Razer Phone 2 Kernel and TWRP device tree!
I've been reading threads where people are having issues compiling the Razer-provided source for the RP2 and figured I should post what I have so others can use it to help achieve a fully working source-built kernel.
I'm also including a set of scripts to repack a Magisk-patched boot.img so you can iterate on building a new kernel rapidly, and am including a prebuilt magisk-patched boot.img with the custom kernel so we can QA other features while focusing on the known-broken things.
Also also, I'm including an exfat kernel module (not built into kernel for now) so that can be tested too!
Click to expand...
Click to collapse
Why is this mostly-working?
I've tested many features on this kernel and so far the only feature *not* working is the microphone. (Audio recording, haven't tested in-call audio)
This kernel is a mashup of Razer's source and a few other OSS repos from CAF - specifically the TFA98XX driver, and the audio-kernel repositories, so there's a bit of integration left to do to get all the audio features working.
I also had to edit the defconfig to get the DTB to build, and have to build with some special flags to use the prebuilt DTB compiler (dtc) since the one included in the source isn't capable of compiling the FIH DTBs inside the Razer-provided source (correct me if I'm doing something wrong here, but this was how I ended up getting it to work).
The kernel parameter skip_initramfs has also been renamed to skip__initramfs to break the silly bootloader skipping the ramdisk (and thereby breaking Magisk). This means you don't need to run Magisk's binary patch to rename that kernel argument to make Magisk or TWRP work.
Keep in mind, though, that this means if you use this kernel with a 100% stock ramdisk, you'll only ever get recovery since new Android ramdisks only contain recovery! (Thanks Dees_Troy for the refresher course!)
If you're familiar with the new audio-kernel CAF stuff, please let me know! I could use your assistance getting the microphone working.
It seems like the microphone isn't working because of some mismatches between the in-kernel msm audio drivers and the Razer customized drivers in the vendor partition.
I get errors like
Code:
[31269.485217] send_afe_cal_type cal_block not found!!
in dmesg when attempting to record audio. This seems isolated to the q6afe drivers in the kernel (specifically here: https://github.com/thecubed/android_kernel_razer_sdm845/blob/master/techpack/audio/dsp/q6afe.c#L1593 ) not playing nice with the prebuilt snd_soc_sdm845 kernel module.
Click to expand...
Click to collapse
Where do I get this?
See here for the TWRP device tree (and detailed instructions on how to set up your build tree): https://github.com/thecubed/android_device_razer_cheryl2
See here for just the kernel source: https://github.com/thecubed/android_kernel_razer_sdm845
See here for a kernel-less boot.img skeleton that you can drop your newly minted kernel into and repack with mkbootimg: http://downloads.codefi.re/thecubed/aura2/kernel/magisk_custom_kernel_skel.tar.gz
See here for a prebuilt boot.img with this custom kernel which includes Magisk: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_9.img
See here for an exfat module you can insmod from a booted phone with custom kernel to try mounting exfat SD cards: http://downloads.codefi.re/thecubed/aura2/kernel/exfat_module.tar.gz
See here for a stock Magisk-patched boot.img for when you're done playing with this: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk.img
Click to expand...
Click to collapse
How do I use this?
First off, this isn't for the average user. This kernel is *under development* and is not fully working yet. This means don't try this kernel on your mom's phone, your neighbor's phone, or any device that you aren't comfortable developing for.
Secondly, to test this, you'll need to be oem unlocked. There's plenty of guides to do this, but be aware that it erases all data on your phone when doing so. You could try using adb backup first, but I didn't have much success with that.
I'd suggest looking at the first link in the Where do I get this section and reading the README for the device tree as it'll have the most detailed instructions.
The gist is you'll need to download a minimal OmniROM manifest, add some lines to a file in .repo/local_manifests/cheryl2.xml, and run mka kernel to get a kernel image.
After that, you'll want to use mkbootimg to build a bootable magisk-patched boot.img, which you'll flash to your device with fastboot flash boot_X path/to/boot.img (where X is the active boot partition).
Once you've got the Image.gz-dtb file from your $OUT/obj/KERNEL_OBJ/arch/arm64/boot/Image.gz-dtb you'll want to repack it into a magisk-patched boot.img
Repacking the boot.img can be done with this command:
Code:
mkbootimg \
--kernel Image.gz-dtb \
--ramdisk boot_magisk.img-ramdisk.gz \
--cmdline 'console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xA84000 androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user' \
--base 0x00000000 \
--pagesize 4096 \
--kernel_offset 0x00008000 \
--ramdisk_offset 0x01000000 \
--second_offset 0x00f00000 \
--tags_offset 0x00000100 \
--os_version 8.1.0 \
--os_patch_level 2018-10 \
-o ../boot_magisk_custom.img
Click to expand...
Click to collapse
FAQ
Does this have TWRP?
No. This does not have TWRP. The device tree is for TWRP eventually, and to make compiling the kernel easier (since Android kernels don't like compiling outside of Android's makefile system anymore)
Does this have Magisk?
Yes! It's "pre-patched" too, as long as you're using my prebuilt one above.
Do I need the custom kernel to use the exfat module?
Yes. This is because the Razer stock kernel has module signing forced. I don't have Razer's kernel module signing key so I can't compile kernel modules for the stock kernel. My kernel has module signing set to allow mismatched signatures, so both the Razer modules in /vendor/lib/modules (required for sound) and my exfat module can coexist.
Why is exfat not compiled into the kernel?
Laziness, primarily. Actually, in this case I just didn't want to add extra variables to testing the kernel. If adding exfat into the kernel directly causes other issues it could potentially derail my quest to get this kernel up to par with the stock kernel.
Why did other kernels not boot?
Most likely due to incompatible audio-kernel revisions, or dtb issues. I'm not sure, but getting this kernel to compile required a bit more hacking than it should have.
Are you working on TWRP for Razer Phone 2?
Yep. Look for another post once the kernel is good to go. I aim to get encryption support working too, unless Dees_Troy beats me to it
Is audio still not working?
I'll update the post to remove the WIP tag and the section about audio as soon as it's working.
Is anything else not working?
Feel free to download and test to let me know what else isn't working and I'll add it to the OP.
Click to expand...
Click to collapse
Acknowledgements
Special thanks to Rashed97 and Dees_Troy for all their help.
Click to expand...
Click to collapse
y u quote OP?
Thanks for your work! Looking forward for a stable version. Wanna help but RP2 is currently my only working phone..
u sir,deserve a beer,thanks for working rp2 and not to forget other devs who help u along the way,we will wait patiently,cheers!!!!
Thank you.
Interesting discovery just now, seems that the stock kernel gives the same 'error' in dmesg when recording audio (but obviously audio recording still works).
Code:
[ 1365.950315] send_afe_cal_type cal_block not found!!
This could mean that Razer doesn't have a calibration profile for the microphone anyway (interesting, wonder if there's an opportunity to improve recording quality here?) and that I'm barking up the wrong tree re: calibration mismatches.
I've also confirmed that I get the same 'ASoC: no backend DAIs enabled for [backend name here]' messages in the stock kernel when brute force trying all PCM inputs with:
Code:
for f in `seq 1 80`; do tinycap /sdcard/wavs/device-$f.wav -D 0 -d $f -r 48000; done
It's also (very) possible that I don't understand how tinycap works.
I dumped the list of PCM inputs/outputs with:
Code:
for f in `ls -d /proc/asound/sdm845tavilsndc/** | grep pcm`; do echo "$f : `grep 'id' $f/info`"; done
and
Code:
cat /proc/asound/pcm
on both kernels (stock and custom) and they seem to match.
I'm thinking I should figure out how to record sound outside of android (from adb only) from stock kernel, and use that same test to try in the custom kernel. If I can find a test like that, I should be able to determine if I need to rename one of my DAI links to match whatever's baked into the XML files in /vendor/etc .
Any ideas?
Are you using the audio.a2dp.default.so driver?
Warrior1988: A2DP isn't in play here, and I'm using the stock /system and /vendor partitions, so any razer-customized tweaks are still present.
Currently, I've been working on figuring out the codec mappings to make sure that when audio is being recorded in the custom kernel that all the appropriate routing is set to enable audio from the tfa98xx chip (NXP amplifier, apparently supports digital microphones too?) or the wcd934x codec.
I'm not sure where the microphones are physically connected internally, so I'm working backwards from what gets enabled/disabled when recording audio in the stock kernel.
So far I have observed a few things (pardon my potentially incorrect terminology, the whole linux ASOC sound layer is new to me):
1. Audio in the stock and custom kernels is being captured by the mixer device called "SDM845 Media1", and it is capturing from SLIMBUS_0_TX input.
Code:
[Recording]
aura:/sys/module # cat /sys/kernel/debug/asoc/sdm845-tavil-snd-card/SDM845\ Media1/state
[SDM845 Media1 - Playback]
State: new
Backends:
No active DSP links
[SDM845 Media1 - Capture]
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 16000
Backends:
- SLIMBUS_0_TX
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 48000
2. You can also see when recording and not recording that in both kernels the SLIMBUS_0_TX input is wired correctly to the right mixer:
Code:
[Not recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: Off in 2 out 0 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
in "static" "Slimbus Capture"
in "static" "BE_IN"
[Recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: On in 2 out 1 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
out "SLIM_0_TX" "MultiMedia1 Mixer"
in "static" "Slimbus Capture"
in "static" "BE_IN"
Now that I've observed those things, I need to do a bit more research on how audio can get enabled/disabled on each of the chips that touch it.
For instance, in the custom kernel, I noticed that during recording sounds the DMIC* lines on the second tfa98xx aren't enabled. I haven't checked in the stock kernel yet - but if the tfa98xx chip is providing mic bias, it's possible that everything is wired right for input but since the mic bias isn't on, the mic isn't powered and thus we get no sound.
(Updated side note, why is Razer Phone 2 is using two TFA9888 chips? The tfa98xx.cnt firmware references TFA9892 which is mono only, too. I need to see a disassembly to figure out what chips it's actually using...)
Code:
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0034/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0035/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS1"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS3"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
Update: just noticed that this path doesn't exist on stock kernel. So the TFA driver I have doesn't match the one Razer is using. Interesting!
Also, I'm not sure why SLIMBUS_2 playback/capture aren't shown as 'dynamic DAI' linked (the '(*)' means it's a dynamic DAI)... Probably not important though.
Code:
aura:/proc/asound # cat pcm
00-00: MultiMedia1 (*) : : playback 1 : capture 1
00-01: MultiMedia2 (*) : : playback 1 : capture 1
00-02: VoiceMMode1 (*) : : playback 1 : capture 1
00-03: VoIP (*) : : playback 1 : capture 1
00-04: MultiMedia3 (*) : : playback 1
00-05: SLIMBUS_0 Hostless (*) : : playback 1 : capture 1
00-06: AFE-PROXY RX msm-stub-rx-6 : : playback 1
00-07: AFE-PROXY TX msm-stub-tx-7 : : capture 1
00-09: AUXPCM Hostless (*) : : playback 1 : capture 1
00-10: SLIMBUS_1 Hostless (*) : : playback 1 : capture 1
00-11: SLIMBUS_3 Hostless (*) : : playback 1 : capture 1
00-12: SLIMBUS_4 Hostless (*) : : playback 1 : capture 1
00-13: MultiMedia5 (*) : : playback 1 : capture 1
00-14: Listen 1 Audio Service (*) : : capture 1
00-16: MultiMedia10 (*) : : playback 1 : capture 1
00-17: MM_NOIRQ (*) : : playback 1 : capture 1
00-18: HDMI_RX_HOSTLESS (*) : : playback 1
00-19: VoiceMMode2 (*) : : playback 1 : capture 1
00-20: Listen 2 Audio Service (*) : : capture 1
00-21: Listen 3 Audio Service (*) : : capture 1
00-22: Listen 4 Audio Service (*) : : capture 1
00-23: Listen 5 Audio Service (*) : : capture 1
00-24: Listen 6 Audio Service (*) : : capture 1
00-25: Listen 7 Audio Service (*) : : capture 1
00-26: Listen 8 Audio Service (*) : : capture 1
00-27: MultiMedia9 (*) : : playback 1 : capture 1
00-33: MM_NOIRQ_2 (*) : : playback 1 : capture 1
00-34: SLIMBUS8_HOSTLESS Capture (*) : : capture 1
00-35: Slimbus4 Capture tavil_vifeedback-35 : : capture 1
00-36: SLIMBUS_2 Hostless Playback tavil_rx2-36 : : playback 1
00-37: SLIMBUS_2 Hostless Capture tavil_tx2-37 : : capture 1
00-38: MultiMedia6 (*) : : playback 1 : capture 1
00-39: USB Audio Hostless (*) : : playback 1 : capture 1
00-80: QUAT_MI2S_RX Hostless (*) : : playback 1
Meanwhile, we've reached out to Razer to see if they'll bless us with the full and complete kernel source this time
I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie
blackknightavalon said:
I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie
Click to expand...
Click to collapse
>simple question
>eta
pick one
Any progress on this kernel? I'm really curious now that we have pie.
No progress as of yet, I've been busy with work recently and Razer hasn't dropped source for the new kernel version (still 4.9 but a different patch level).
I'm hopeful that Razer will drop the complete source for Pie's kernel and I can backport that to the Oreo kernel for those who want to keep the old OS.
I haven't updated my RP2 to Pie yet so I can test out any changes once the source for the new kernel is out. I'll be sure to post here when I have any updates
Audio-kernel source is out! https://s3.amazonaws.com/cheryl-factory-images/audio-kernel-aura-2009.tar.gz
I'll be rebuilding my kernel very soon and testing.
https://s3.amazonaws.com/cheryl-factory-images/
Warrior1988 said:
https://s3.amazonaws.com/cheryl-factory-images/
Click to expand...
Click to collapse
Yup, I'm building it right now!
Yup, it works! I have fully working audio and microphone now. Seems like there's a bunch of DAI changes and some offset changes to calibration stuff that FIH added (ugh).
Please hold while I get the commit up on my Github, and I'll get a build with exfat going here in just a minute after.
Plan is:
- Github updates (readme changes, etc) UPDATE: done
- Upload this current build I just tested for anyone that wants it
- Add exfat module to kernel and rebuild / test UPDATE: exfat support works, BUT I need to recompile vold to support exfat. I can mount the SD card just fine, but Android doesn't understand that it's mounted because vold isn't tracking it
Also, <3 u razer, thanks
I'm bummed to hear about the layoffs, and I really appreciate whomever uploaded the source even after that. Hopefully Razer's phone team will grow again and get to make us a Razer Phone 3 at some point in the future.
For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
EDIT: Fixed link, 2AM is not kind to my typing skills
Awesome work! Very excited to try it out tomorrow.
Also sad to see your post about their layoffs. Pretty fun phone with much potential for future.
I think some of the reviews are pretty harsh given the penchant of Pixel / Samsung / Apple worship out there.
Anyway, thanks so much for this.
thecubed said:
For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
Click to expand...
Click to collapse
Thank you for this!
It's showing up "Not found" on the download link though.
jal3223 said:
Thank you for this!
It's showing up "Not found" on the download link though.
Click to expand...
Click to collapse
Fixed the link in my previous post - sorry about that!
I'll be updating the OP tonight too when I get home from work.
Looking good! Is the sound as good as stock (or maybe better, considering the low volume crackling we get)?
Hoping to give this a shot soon, as soon as I figure out rooting on 9.0. I saw a thread about it, but nobody answered my question there, and light digging through threads didn't turn up an answer, so trying this kernel will have to wait a bit. Makes me miss the HTC root days, when finding out about root was a simple yes or no situation... lol.