Related
Q&A for [FreeXperia Project] AOSP Android 5.x.x
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FreeXperia Project] AOSP Android 5.x.x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Getting issues with modem from logcat:
Code:
<6>[ 224.145049] pil-q6v5-mss fc880000.qcom,mss: mba: loading from 0x0d100000 to 0x0d13a000
<4>[ 224.151677] ------------[ cut here ]------------
<4>[ 224.155406] WARNING: at kernel/irq/manage.c:428 enable_irq+0x60/0x74()
<4>[ 224.161837] Unbalanced enable for IRQ 413
<6>[ 224.165888] Modules linked in:
<6>[ 224.165915] [<c010bf04>] (unwind_backtrace+0x0/0x11c) from [<c0194c58>] (warn_slowpath_common+0x4c/0x64)
<6>[ 224.165932] [<c0194c58>] (warn_slowpath_common+0x4c/0x64) from [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c)
<6>[ 224.165950] [<c0194c9c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c01f3d7c>] (enable_irq+0x60/0x74)
<6>[ 224.165972] [<c01f3d7c>] (enable_irq+0x60/0x74) from [<c01312fc>] (pil_boot+0x7d8/0x9cc)
<6>[ 224.165990] [<c01312fc>] (pil_boot+0x7d8/0x9cc) from [<c013374c>] (mss_start+0x24/0x5c)
<6>[ 224.166009] [<c013374c>] (mss_start+0x24/0x5c) from [<c0162fc8>] (subsystem_get+0x94/0x168)
<6>[ 224.166030] [<c0162fc8>] (subsystem_get+0x94/0x168) from [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c)
<6>[ 224.166047] [<c0145094>] (msm_ipc_load_default_node+0x30/0x6c) from [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8)
<6>[ 224.166065] [<c014a428>] (msm_ipc_router_ioctl+0xf0/0x2b8) from [<c0764cc8>] (sock_ioctl+0x228/0x278)
<6>[ 224.166086] [<c0764cc8>] (sock_ioctl+0x228/0x278) from [<c0263074>] (vfs_ioctl+0x28/0x3c)
<6>[ 224.166103] [<c0263074>] (vfs_ioctl+0x28/0x3c) from [<c0263ab8>] (do_vfs_ioctl+0x484/0x574)
<6>[ 224.166119] [<c0263ab8>] (do_vfs_ioctl+0x484/0x574) from [<c0263bf0>] (sys_ioctl+0x48/0x74)
<6>[ 224.166138] [<c0263bf0>] (sys_ioctl+0x48/0x74) from [<c0105ea0>] (ret_fast_syscall+0x0/0x30)
<4>[ 224.166149] ---[ end trace 1ffe67af4bf01ba1 ]---
<3>[ 224.205132] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -284491765
<3>[ 224.212540] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to bring out of reset
<3>[ 224.219243] modem_notifier_cb: sysmon_send_event error -19
<3>[ 224.224639] M-Notify: General: 5
<3>[ 224.227804] msm_ipc_load_default_node: Failed to load modem
I reported this over in the kernel thread http://forum.xda-developers.com/showpost.php?p=57625416&postcount=23 it appears everything is still broken.
Also Wifi kills the whole system:
Code:
I/WifiHAL ( 652): Initialized Wifi HAL Successfully; vendor cmd = 103
D/wifi ( 652): Did set static halHandle = 0xafa4e040
D/wifi ( 652): halHandle = 0xafa4e040, mVM = 0xb505c280, mCls = 0x300ec6
E/wifi ( 652): getStaticLongField sWifiHalHandle 0xa06f381c
D/wifi ( 652): array field set
W/Adreno-EGL( 198): <qeglDrvAPI_eglDupNativeFenceFDANDROID:6527>: EGL_BAD_PARAMETER
W/SurfaceFlinger( 198): captureScreen: failed to dup sync khr object
E/audio_a2dp_hw( 241): adev_set_parameters: ERROR: set param called even when stream out is null
F/libc ( 652): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4300001 in tid 1595 (WifiStateMachin)
I/WifiNative-HAL( 652): Waiting for HAL events mWifiHalHandle=-1348149184
D/wifi ( 652): waitForHalEvents called, vm = 0xb505c280, obj = 0x300ec6, env = 0xafd22320
E/wifi ( 652): getStaticLongField sWifiHalHandle 0x9aa39b1c
I/DEBUG ( 238): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 238): Build fingerprint: 'Sony/aosp_d5803/aries:5.0.2/LRX22G/root12250659:userdebug/test-keys'
I/DEBUG ( 238): Revision: '0'
I/DEBUG ( 238): ABI: 'arm'
I/DEBUG ( 238): pid: 652, tid: 1595, name: WifiStateMachin >>> system_server <<<
I/DEBUG ( 238): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4300001
I/DEBUG ( 238): r0 04300001 r1 b3f279f8 r2 b3f1a885 r3 ffffffa8
I/DEBUG ( 238): r4 00000000 r5 04300001 r6 00000000 r7 b3f27dcc
I/DEBUG ( 238): r8 b3f1a885 r9 a1e4b400 sl 00000001 fp 130337c0
I/DEBUG ( 238): ip b3f27f20 sp a06f3820 lr b3f1dd4d pc b3f1dd4c cpsr 600d0030
I/DEBUG ( 238):
I/DEBUG ( 238): backtrace:
I/DEBUG ( 238): #00 pc 00007d4c /system/lib/libwifi-service.so (getWifiHandle(wifi_interface_info*)+5)
I/DEBUG ( 238): #01 pc 00007d53 /system/lib/libwifi-service.so (getHalInfo(wifi_interface_info*)+2)
I/DEBUG ( 238): #02 pc 0000b37d /system/lib/libwifi-service.so (wifi_get_link_stats+28)
I/DEBUG ( 238): #03 pc 0000421d /system/lib/libwifi-service.so
I/DEBUG ( 238): #04 pc 0003623d /data/dalvik-cache/arm/[email protected]@[email protected]
E/Sensors ( 4229): sns_smr_util.c(104):Unable to initialize service 256 with QCCI, timed out (10000 ms)
E/Sensors ( 4229): sns_sam_mr.c(1016):Unable to initialize service 0 with QCCI
E/Sensors ( 4229): sns_sam_mr.c(1111):Unable to acquire service handle 0
E/Sensors ( 4229): mag_cal.c(1603):mag_cal_sam_init: Unknown UUID(1) 00000000-0000-0000
E/Sensors ( 4229): mag_cal.c(1608):mag_cal_sam_init: Unknown UUID(2) 0000-000000000000
E/Sensors ( 4229): sns_sam.c(4432):Failed to register algorithm service 16 with SAM
I/DEBUG ( 238):
I/DEBUG ( 238): Tombstone written to: /data/tombstones/tombstone_01
I/ServiceManager( 196): service 'connectivity' died
I/ServiceManager( 196): service 'servicediscovery' died
W/Sensors ( 2552): sensorservice died [0xacc5e0c0]
I/ServiceManager( 196): service 'updatelock' died
I/ServiceManager( 196): service 'notification' died
I/ServiceManager( 196): service 'devicestoragemonitor' died
I/ServiceManager( 196): service 'location' died
I/ServiceManager( 196): service 'country_detector' died
I/ServiceManager( 196): service 'search' died
I/ServiceManager( 196): service 'dropbox' died
any reason aries isn't built ? at least not that I could find on the fxp open source repo.
https://github.com/CyanogenMod/andr...mmit/61f48baf5669c2a21b0a510515c985dec87617b5
fixes this problem
The guide for building AOSP is not clear for certain points,
For devices with Qualcomm wireless hardware, you need to build a Prima or Pronto WLAN module in order to get Wi-Fi working. Follow the instructions below to do this.
Then compile the module by entering the device specific command listed below.Which should we follow for z3-compact, as device is not mentioned:
Prima?
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j12 -C M=$PWD CONFIG_PRIMA_WLAN=m CONFIG_PRIMA_WLAN_LFR=y KERNEL_BUILD=1 WLAN_ROOT=$PWD
Once the compilation is finished, the wlan.ko module can be found in the prima folder.Where do we put wlan.ko ?
Also,
the guide for AOSP has the kernel and wifi repos in the local manifest, does it build them during compilation or do we have to build them manually|separately, and then copy the kernel and wifi module before compiling ROM?
Thank you for your time,
hoping to see a fully working AOSP soon, keeping fingers crossed.
As it is a shame to see a phone with great HW and design dragging behind the rest.
I hope to see Sony advance and reach full capabilities
Any news about a working camera for 3.10 kernel and AOSP rom ?
Envoyé de mon Xperia Z3C en utilisant Tapatalk
Hi there,
Am on COS 12, running Sygics navigation maps ver 15.2, the moment I install Xposed for Lollipop they stop functioning and crash?
If I have Xposed install earlier they wont get installed?
Using the xposed-sdk21-arm-20150430 and XposedInstaller_3.0-alpha2.apk, any solutions, suggestions why, since need both?
Had no issues when was on ktkat CM 11S.
Thanks.
Same problem here.
Sygic has to fix it. There was already a discussion in the Xposed Discussion thread.
Latest working Sygic version is 15.0.4, any newer version will crash with xposed.
If you open Xposed > Log, you can see the error.
Older Log:
Code:
04-15 12:57:01.055 I/DEBUG ( 302): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-15 12:57:01.055 I/DEBUG ( 302): Build fingerprint: 'htc/htc_europe/m7:5.0.2/LRX22G/482424.2:user/release-keys'
04-15 12:57:01.055 I/DEBUG ( 302): Revision: '3'
04-15 12:57:01.055 I/DEBUG ( 302): ABI: 'arm'
04-15 12:57:01.055 I/DEBUG ( 302): pid: 15210, tid: 15210, name: com.sygic.aura >>> com.sygic.aura <<<
04-15 12:57:01.055 I/DEBUG ( 302): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
04-15 12:57:01.065 I/DEBUG ( 302): r0 0000000c r1 24000000 r2 beb0fc4c r3 00000002
04-15 12:57:01.065 I/DEBUG ( 302): r4 b6f93de4 r5 b75832c8 r6 b5304a54 r7 00000000
04-15 12:57:01.065 I/DEBUG ( 302): r8 b7582c98 r9 00000000 sl beb0fc50 fp 13292640
04-15 12:57:01.065 I/DEBUG ( 302): ip b5214411 sp beb0fbc0 lr b5214439 pc b5214448 cpsr 000b0030
04-15 12:57:01.065 I/DEBUG ( 302):
04-15 12:57:01.065 I/DEBUG ( 302): backtrace:
04-15 12:57:01.065 I/DEBUG ( 302): #00 pc 001fb448 /system/lib/libart.so (art::Field_get(_JNIEnv*, _jobject*, _jobject*, unsigned char)+55)
04-15 12:57:01.075 I/DEBUG ( 302): #01 pc 0001b8b3 /data/dalvik-cache/arm/[email protected]@boot.oat
Edit: On Google+ Sygic says that they know that there are problems with custom roms and xposed, but it is low priority right now...
As you posted Sygics know about the problems with Custom Roms, which Rom would you suggest to flash for OnePlus One which wont have a conflict with Sygics and Xposed framework?
Thanks.
Please read what the others have written above you, before posting.
Sygic conflicts directly with Xposed, regardless of which ROM you use (including the stock ROMs). Sygic also conflicts with custom ROMs, even when Xposed is not installed.
To answer your question: None.
I contacted Sygic today and they basically told me they're not handling it.
It's purely the fault of Xposed so they don't really care.
My current solution is MultiROM. If I need GPS navigation, I just reboot to a minimal ROM where Sygic works without any issues.
I have the same issue. Only version that works for me is 15.0.4 or lower. but these versions don't support the 2015 maps.
As my phone (nubia) has a customised UI that is what is causing sygic to break. I have completely uninstalled xposed and have the same issue. So its definitely sygics issue. I will email their support, hopefully they can release a fix. If enough people complain to them about the issue that aren't using xposed then hopefully they will have to listen.
Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance
camelek said:
Hi,
For long time I had broken camera (purple tint but workaround fix with more copper tape doesn't work) and finally I bought some camera for replacement.
After replace, of course no more purple tint, but on the same system/software/everything - camera apps working one time only. Just take the shot and app (whatever it is, with one exception*) closing with report box.
* Instagram - because go to edit mode after taking picture, not crashing.
I thought - problem with new camera only? But no - taking picture with front camera has the same issue right now.
Doesn't matter ROM (I tried: AICP Marshmallow nightly, XenonHD based Lollipop and Marshmallow, ResurectionRemix based on MM).
Somebody has any idea how this could be fixed?
Full logs from shot taken by base camera app with front and back camera attached.
I think crucial part is here:
Code:
03-23 13:28:38.283 210 210 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-23 13:28:38.283 210 210 F DEBUG : Build fingerprint: 'htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys'
03-23 13:28:38.283 210 210 F DEBUG : Revision: '0'
03-23 13:28:38.283 210 210 F DEBUG : ABI: 'arm'
03-23 13:28:38.284 210 210 F DEBUG : pid: 8063, tid: 8619, name: mm_camera_poll >>> /system/bin/mediaserver <<<
03-23 13:28:38.284 210 210 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x149
03-23 13:28:38.285 749 2723 W NativeCrashListener: Couldn't find ProcessRecord for pid 8063
03-23 13:28:38.303 210 210 F DEBUG : r0 00000101 r1 ffffffff r2 b48402fc r3 80000000
03-23 13:28:38.303 210 210 E DEBUG : AM write failed: Broken pipe
03-23 13:28:38.303 210 210 F DEBUG : r4 afc6a800 r5 af476940 r6 af47694c r7 af476944
03-23 13:28:38.303 210 210 F DEBUG : r8 af475000 r9 b6008024 sl af476938 fp afc6a800
03-23 13:28:38.303 210 210 F DEBUG : ip b483fdb4 sp a71d68d0 lr b481f735 pc b481ef36 cpsr 40070030
03-23 13:28:38.311 210 210 F DEBUG :
03-23 13:28:38.311 210 210 F DEBUG : backtrace:
03-23 13:28:38.311 210 210 F DEBUG : #00 pc 00049f36 /system/lib/hw/camera.vendor.msm8960.so (android::util_get_Hal_obj(camera_device*)+5)
03-23 13:28:38.311 210 210 F DEBUG : #01 pc 0004a731 /system/lib/hw/camera.vendor.msm8960.so (release+52)
03-23 13:28:38.311 210 210 F DEBUG : #02 pc 000046d5 /system/lib/libimage-jpeg-enc-omx-comp.so (handleMessage+164)
03-23 13:28:38.311 210 210 F DEBUG : #03 pc 0003f5f7 /system/lib/libc.so (__pthread_start(void*)+30)
03-23 13:28:38.314 210 210 F DEBUG : #04 pc 00019ccb /system/lib/libc.so (__start_thread+6)
but I don't know how to fix or even go deeper with debug.
Any help?
Thanks in advance
Click to expand...
Click to collapse
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs
donkeykong1 said:
You flashed all kinds of ROMs which have one thing common - camera crashes after taking shot. You could find that out if you read those ROM threads. Try a Sense ROM, and see if the issue remains, but I'm 100% certain it's a bug all those ROMs have in common
dey tuuk ur juurbs
Click to expand...
Click to collapse
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Well, backup your current ROM and flash any Sense or GPE ROM and try. I know that all CM or AOSP ROMs have that crashing camera bug
dey tuuk ur juurbs
camelek said:
I will update with some "stock" ROM but for sure, there wasn't any problem with taking pictures (or series of pictures) before I switched camera. With the same ROM after hardware was changed - I get those problem.
Click to expand...
Click to collapse
Try with cameringo app first...
Ok, quick summary:
Cameringo (even Lite version) working fine, but I think it's again similar trick is used in Instagram - because always after taking picture there is "picture taken" intent/screen and after press back (or camera button in Instagram) camera is reinitialized. But this app doing this so quick that it's fully acceptable.
With stock ROMs I've came through some hell ride as using AICP or RR my /data was as F2FS partition. So backup whole storage, changing fs, flashing old Lollipop - long story short: never more Anyway camera working fine with HTC app or Lollipop ROM (like Venom), but this unfortunately is not an option, going back to easy hackable system because of camera.
Anyway, thanks for suggestions.
Disclaimer:
I am not responsible for the outcome of you flashing this software, please backup your current boot partition before flashing this kernel.
Click to expand...
Click to collapse
While I will take some credit for this work, I am not a Developer; I'm a hobbyist - I'll accept any help I can get to improve this kernel.
Downloads are in the download section
Source RUSTY-VNS
Credits:
@twicejr
@kwoktopus
Changes from stock:
2017-03-16 No-Root
2017-03-16 Root
3.10.102
Optimized build flags
Intelliactive CPU Governor
RustyKernel-EMUI4.1_hi6250-2017-03-17
RustyKernel-PA6.0.1_hi6250-2017-03-17 - Lockscreen bug, disable lockscreen security before flashing (PIN/Patten/Password)
Intelliplug Hotplug
Thunderplug Hotplug
PA 6.0.1 Support
Known bugs:
Kernel Adiutor:
Code:
big: Failed to load frequencies
. They're running, just not being logged.
PA version has a lockscreen bug - disable secure lockscreen before flashing
XDA:DevDB Information
P9 Lite Kernel, Kernel for the Huawei P9 Lite
Contributors
Carlyle_f
Source Code: https://github.com/carlyle-felix/RUSTY-VNS
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2017-03-17
Beta Release Date: 2017-03-16
Created 2017-03-16
Last Updated 2017-03-17
Reserved
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
You can make oeminfo l31c636
pilgrim011 said:
Great job, finally some kernels showing up! Please consider making a version with USB OTG and double tap to wake enabled. I like that you have two versions - with and without root.
Click to expand...
Click to collapse
Thanks man, I will look into OTG. Also, next releases will all have root
Sent from my HUAWEI VNS-L31 using Tapatalk
http://cloud.tapatalk.com/s/58cb6f4e67c55/RustyKernel_hi6250-2017-03-16.zip
Testers please leave feedback
Intelliplug and thunder plug hotplugs
Sent from my HUAWEI VNS-L31 using Tapatalk
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
dariomrk said:
Since this kernel supports PA, does it support LineageOS 13, or 14/RR?
Click to expand...
Click to collapse
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
dady000 said:
I think this should work for CM13 because it shares the same ramdisk and kernel cmd options but it probably won't work on LineageOS 14. I tried to flash the Avsky's kernel for LOS14 on PA and it didn't work.
Click to expand...
Click to collapse
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
No, not yet, I will try it later. What I tried is the Avsky's kernel.
What are the advantages of using this kernel? And how do you install it? Noob here
SALVO9 said:
What are the advantages of using this kernel? And how do you install it? Noob here
Click to expand...
Click to collapse
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Carlyle_f said:
Hi, please don't think I'm trying to be funny or mean, if you don't know what you'll gain/lose by flashing a kernel rather steer clear of doing it.
I cannot stop you from doing it anyway but do me a favour and google it first, do some research and see what it's about.
I only advise you not to do so ignorantly because it gives you control of things you don't usually have control of and this has the potential to destroy your device and I really don't want that for the users of my work.
cheers. :good:
Click to expand...
Click to collapse
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
SALVO9 said:
I understand your concern and appreciate it, but I NEVER do anything to my device without knowing EXACTLY what I'm doing.. I'm not a total noob, I actually know how to do many things to my phone. I am just not used to kernels since there are almost no custom kernels for p9 lite and I was asking which are the benefits of this one
Click to expand...
Click to collapse
Alright, the benefits of this kernel is listed under changelog in OP
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
So this one worked for you on PA? I haven't actually tested.
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Delete
dady000 said:
Okey I flashed it and I when I enter the pattern to unlock the device, it just deletes and won't let me in. Kmsg below:
Code:
<13>[ 157.734222s][pid:1,cpu0,init]init: Starting service 'keystore'...
<3>[ 157.838409s][pid:3526,cpu0,keystore]tc_client_ioctl(3526, keystore): invalid cmd!
<6>[ 158.002014s][pid:3526,cpu0,keystore]keystore[3526]: unhandled level 1 translation fault (11) at 0x00000020, esr 0x92000005
<1>[ 158.002014s][pid:3526,cpu0,keystore]pgd = ffffffc02b1d9000
<1>[ 158.002044s][pid:3526,cpu0,keystore][00000020] *pgd=0000000000000000
<4>[ 158.002044s][pid:3526,cpu0,keystore]
<4>[ 158.002044s][pid:3526,cpu0,keystore]CPU: 0 PID: 3526 Comm: keystore Tainted: G W 3.10.102-g247a5fe-dirty #9
<4>[ 158.002075s][pid:3526,cpu0,keystore]task: ffffffc012da2280 ti: ffffffc024370000 task.ti: ffffffc024370000
<4>[ 158.002075s][pid:3526,cpu0,keystore]PC is at 0x7f795c6bd8
<4>[ 158.002075s][pid:3526,cpu0,keystore]LR is at 0x7f795c77cc
<4>[ 158.002075s][pid:3526,cpu0,keystore]pc : [<0000007f795c6bd8>] lr : [<0000007f795c77cc>] pstate: 20000000
<4>[ 158.002075s][pid:3526,cpu0,keystore]sp : 0000007fc690e9c0
<4>[ 158.002105s][pid:3526,cpu0,keystore]x29: 0000007fc690e9c0 x28: 0000000000000000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x27: 0000005587463180 x26: 0000005587463000
<4>[ 158.002105s][pid:3526,cpu0,keystore]x25: 0000007f79563000 x24: 0000007fc690eb60
<4>[ 158.002105s][pid:3526,cpu0,keystore]x23: 0000007f795f7010 x22: 0000007f79562060
<4>[ 158.002136s][pid:3526,cpu0,keystore]x21: 0000007f7956b000 x20: 0000007f7956b020
<4>[ 158.002136s][pid:3526,cpu0,keystore]x19: 0000007f79542000 x18: 0000007f79be8064
<4>[ 158.002136s][pid:3526,cpu0,keystore]x17: 0000007f795c6bbc x16: 0000007f795dbf48
<4>[ 158.002136s][pid:3526,cpu0,keystore]x15: 0000000000000000 x14: 0000007fc690e528
<4>[ 158.002166s][pid:3526,cpu0,keystore]x13: 000000000000002e x12: 0000007fc690e340
<4>[ 158.002166s][pid:3526,cpu0,keystore]x11: 0000007fc690e468 x10: 0000007fc690e42c
<4>[ 158.002166s][pid:3526,cpu0,keystore]x9 : 0000000000000037 x8 : 0000000000000042
<4>[ 158.002166s][pid:3526,cpu0,keystore]x7 : 0000000000000000 x6 : 0000000000000dc6
<4>[ 158.002166s][pid:3526,cpu0,keystore]x5 : 00000000000003f9 x4 : 0000000000000037
<4>[ 158.002197s][pid:3526,cpu0,keystore]x3 : 62d66a6aeb09d6ff x2 : 62d66a6aeb09d6ff
<4>[ 158.002197s][pid:3526,cpu0,keystore]x1 : 0000000000000000 x0 : 0000007f79541fe8
<4>[ 158.002197s][pid:3526,cpu0,keystore]
<13>[ 158.004302s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killed by signal 11
<13>[ 158.004333s][pid:1,cpu0,init]init: Service 'keystore' (pid 3526) killing any children in process group
<6>[ 158.647033s][2017:03:17 17:46:27][pid:1266,cpu0,Binder_5]binder: 767:1266 transaction failed 29189, size 100-0
<6>[ 158.650329s][pid:921,cpu0,ConnectivitySer]binder: 767:921 transaction failed 29189, size 328-0
<6>[ 158.839477s][pid:767,cpu0,system_server]binder: 767:767 transaction failed 29189, size 84-0
<7>[ 158.987701s][pid:419,cpu0,kworker/u16:3]wifi wakeup cmd send,wakelock cnt 2
<7>[ 159.137084s][pid:419,cpu0,kworker/u16:3]wifi sleep cmd send ,wakelock cnt 1
<4>[ 159.336730s][pid:0,cpu1,swapper/1]CPU1: Booted secondary processor
<7>[ 160.057189s][2017:03:17 17:46:29][pid:465,cpu1,hisi_hcc]wifi wakeup cmd send,wakelock cnt 1
<7>[ 160.063507s][pid:1222,cpu0,wpa_supplicant_][W][vap:0]{wal_cfg80211_get_station::rssi -54.} [F:1205][L:5254]
<38>[ 160.066101s][pid:297,cpu0,logd.auditd]type=1400 audit(1489769189.267:220): avc: denied { sendto } for pid=1222 comm="wpa_supplicant_" ppid=1 ppid_comm="init" path="/data/misc/wifi/sockets/wpa_ctrl_767-1" scontext=u:r:init:s0 tcontext=u:r:system_server:s0 tclass=unix_dgram_socket permissive=1
<6>[ 160.142639s][pid:785,cpu1,Binder_1]hisi_vibrator_enable,value=0
Click to expand...
Click to collapse
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock before flashing kernel. huge security breach but should satisfy those who are okay with slide to unlock for now.
Carlyle_f said:
Hi, please attach both dmsg and kmsg. Also to make it easier is there anything you can do with this logcat i got when i tried it on PA.
Logcat:
Code:
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 E libteec : Shared Memory is used by a pending operation
03-17 20:56:51.588 4263 4263 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4263 (keystore)
03-17 20:56:51.589 461 461 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 20:56:51.589 461 461 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 20:56:51.690 461 461 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 20:56:51.690 461 461 F DEBUG : CM Version: 'unknown'
03-17 20:56:51.690 461 461 F DEBUG : Build fingerprint: 'huawei/pa_hi6250/hi6250:6.0.1/MTC20F/dady03072055:userdebug/test-keys'
03-17 20:56:51.690 461 461 F DEBUG : Revision: '0'
03-17 20:56:51.690 461 461 F DEBUG : ABI: 'arm64'
03-17 20:56:51.691 461 461 F DEBUG : pid: 4263, tid: 4263, name: keystore >>> /system/bin/keystore <<<
03-17 20:56:51.691 461 461 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
03-17 20:56:51.696 461 461 F DEBUG : x0 0000007f851c1fe8 x1 0000000000000000 x2 d5fa989020823a5f x3 d5fa989020823a5f
03-17 20:56:51.696 461 461 F DEBUG : x4 0000000000000037 x5 00000000000003f9 x6 00000000000010a7 x7 0000000000000000
03-17 20:56:51.696 461 461 F DEBUG : x8 0000000000000042 x9 0000000000000037 x10 0000007feda4d68c x11 0000007feda4d6c8
03-17 20:56:51.696 461 461 F DEBUG : x12 0000007feda4d5a0 x13 000000000000002e x14 0000007feda4d788 x15 0000000000000000
03-17 20:56:51.697 461 461 F DEBUG : x16 0000007f8525af48 x17 0000007f85245bbc x18 0000007f85867064 x19 0000007f851c2000
03-17 20:56:51.697 461 461 F DEBUG : x20 0000007f851eb020 x21 0000007f851eb000 x22 0000007f851e2060 x23 0000007f85276010
03-17 20:56:51.697 461 461 F DEBUG : x24 0000007feda4ddc0 x25 0000007f851e3000 x26 000000556cc44000 x27 000000556cc44180
03-17 20:56:51.697 461 461 F DEBUG : x28 0000000000000000 x29 0000007feda4dc20 x30 0000007f852467cc
03-17 20:56:51.697 461 461 F DEBUG : sp 0000007feda4dc20 pc 0000007f85245bd8 pstate 0000000020000000
03-17 20:56:51.699 912 1090 W NativeCrashListener: Couldn't find ProcessRecord for pid 4263
03-17 20:56:51.716 461 461 F DEBUG :
03-17 20:56:51.716 461 461 F DEBUG : backtrace:
03-17 20:56:51.716 461 461 E DEBUG : AM write failed: Broken pipe
03-17 20:56:51.716 461 461 F DEBUG : #00 pc 0000000000001bd8 /system/lib64/libteec.so (TEEC_ReleaseSharedMemory+28)
03-17 20:56:51.716 461 461 F DEBUG : #01 pc 00000000000027c8 /system/lib64/libteec.so (TEEC_FinalizeContext+80)
03-17 20:56:51.716 461 461 F DEBUG : #02 pc 0000000000002eb4 /system/lib64/hw/keystore.hi6250.so
03-17 20:56:51.716 461 461 F DEBUG : #03 pc 0000000000010038 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster16Keymaster1EngineD2Ev+24)
03-17 20:56:51.716 461 461 F DEBUG : #04 pc 0000000000012720 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD2Ev+164)
03-17 20:56:51.716 461 461 F DEBUG : #05 pc 00000000000127d8 /system/lib64/libsoftkeymasterdevice.so (_ZN9keymaster20SoftKeymasterContextD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #06 pc 0000000000011a4c /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD1Ev+120)
03-17 20:56:51.716 461 461 F DEBUG : #07 pc 0000000000011a70 /system/lib64/libkeymaster1.so (_ZN9keymaster16AndroidKeymasterD0Ev+12)
03-17 20:56:51.716 461 461 F DEBUG : #08 pc 0000000000007a50 /system/bin/keystore (main+2016)
03-17 20:56:51.716 461 461 F DEBUG : #09 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
03-17 20:56:51.716 461 461 F DEBUG : #10 pc 0000000000007c20 /system/bin/keystore
03-17 20:56:51.762 461 461 F DEBUG :
03-17 20:56:51.762 461 461 F DEBUG : Tombstone written to: /data/tombstones/tombstone_04
Also the only quick workaround i found was removing pin/password/pattern unlock. huge security breach but should satisfy those who are okay with slide to unlock for now.
Click to expand...
Click to collapse
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
dady000 said:
Yes, I got the same logcat. Nothing I can do with it. I didn't attach whole dmesg because it's apparent that it is issue with keystore, no other errors shown in dmesg/kmsg.
Click to expand...
Click to collapse
hi can you please try the new build before i include it in OP:
https://forum.xda-developers.com/devdb/project/dl/?id=23699
Considering kernel is essential to make your device work, if you put a incompatible kernel on your device, what are the consequences?
Will the recovery still be bootable considering it has its own partition. In case the recovery is bootable, I'm willing to test on my VNS-L31.
Also in that case i could try on other roms, example CM13, Los14, etc...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
klte-common (shared by all klte* devices): LineageOS/android_device_samsung_klte-common
klte: LineageOS/android_device_samsung_klte
klteactivexx: LineageOS/android_device_samsung_klteactivexx
kltechn: LineageOS/android_device_samsung_kltechn
kltechnduo: LineageOS/android_device_samsung_kltechnduo
klteduos: LineageOS/android_device_samsung_klteduos
kltedv: LineageOS/android_device_samsung_kltedv
kltekdi: LineageOS/android_device_samsung_kltekdi
kltekor: LineageOS/android_device_samsung_kltekor
Kernel source code:
LineageOS/android_kernel_samsung_msm8974
My picks:
https://github.com/haggertk/cm_build_stuff/blob/lineage-18.1/picks.sh (other than the open device/kernel changes on gerrit)
Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
BuildModelklteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8klteactivexxSM-G870FklteaioSM-G900AZ, SM-S902LkltechnSM-G9006V, SM-G9008VkltechnduoSM-G9006W, SM-G9008W, SM-G9009WklteduosSM-G900FD, SM-G900MDkltedvSM-G900I, SM-G900PkltekdiSC-04F, SCL23kltekorSM-G900K, SM-G900L, SM-G900S
Downloads:
https://androidfilehost.com/?w=files&flid=321278
Installation Instructions:
Download latest build
Boot into recovery
Lineage recovery images are included in the download section and that's what I support. If you feel like using TWRP and something isn't working then take it up with the TWRP maintainer
If not updating from one of my earlier unofficial builds, then format/system, /data, and /cache
For Lineage recovery:
Format -> Format data/factory reset (this does /data and /cache)
Format -> Format system partition
For TWRP figure it out. And no, "wipe data" isn't the same as formatting data
Install LineageOS zip
If this is your initial installation of LineageOS 18.1, then flash any addons (e.g., gapps)
Reporting Bugs:
DO NOT even think about reporting bugs if you are running a custom kernel, Magisk, or Xposed
Grab a logcat after the problem has occurred
If there is a random reboot then grab /proc/last_kmsg. A logcat AFTER the reboot will be worthless
Note which build AND device you have
Read the thread, at least the last month's worth of posts. Don't report things that others already have.
Compatibility Notes:
Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. It was kind of broken in 17 and we likely won't merge the changes to add it back in for 18. I'm not going to pick the open changes to re-add support because I'm not going to deal with "but it worked on haggertk's unofficial builds" bug reports after we eventually go official. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
Donations:
I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
Reserved -- just in case.
Tx so much for keeping our beloved S5 alive
Thank you Mr. @haggertk for keeping our old S5 up to date.
It's not mentioned in the OP @ the present but could you tell me please if SELinux is set to Permissive or Enforcing?
If it's SELinux Permissive would you say that it's not ready to be used as a daily driver with important user accounts @ the present?
***
curiousrom said:
Thank you Mr. @haggertk for keeping our old S5 up to date.
It's not mention in the OP @ the present but could you tell me please if SELinux is set to Permissive or Enforcing?
If it's SELinux Permissive would you say that it's not ready to be used as a daily driver with important user accounts @ the present?
***
Click to expand...
Click to collapse
Hi
I already flashed and it is enforcing
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)
Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).
Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):
AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION
TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)
Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)
RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1
Thank you. And if anyone built with signature spoofing, please contact me. We still have no convenient method to patch android 11 after building.
ttesty said:
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)
Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).
Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):
AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION
TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)
Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)
RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1
Click to expand...
Click to collapse
This seemed to fix a few of the problems. Some of the problems might not be exclusive to the ROM - rather GAPPS etc:
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
Just installed this. Smooth af.
Once again thanks a lot Mr Haggertk for bringing android 11 to our beloved Samsung Galaxy S5. Here are some screenshots made with my SM-G900F
Thanks for all your hard work <3
gaindelioide said:
...Here are some screenshots made with my SM-G900F
Click to expand...
Click to collapse
Thanks for the effort but 2 comments:
You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.
Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?
How does the Settings panel looks like?
***
And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
Pretty stable. I get a lot of these messages for many different applications and during boot time. Probably normal page faults (data missing from memory).
12-30 00:24:14.808 0 0 F : pgd = d4dbc000
12-30 00:24:14.808 0 0 F : [00000000] *pgd=00000000
12-30 00:24:14.808 0 0 W Pid : 32432, comm: hone.app2sd.pro
12-30 00:24:14.808 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:24:14.808 0 0 W : PC is at 0x7215022a
12-30 00:24:14.808 0 0 W : LR is at 0x72150227
12-30 00:24:14.808 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600e0030
12-30 00:24:14.808 0 0 W sp : be853ce0 ip : 00000000 fp : be853d4c
12-30 00:24:14.808 0 0 W : r10: 136b32c0 r9 : ade4ce00 r8 : 00000000
12-30 00:24:14.808 0 0 W : r7 : 00000000 r6 : 136b32c0 r5 : 00000000 r4 : 00000000
12-30 00:24:14.808 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:24:14.808 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:24:14.808 0 0 W Control : 10c5787d Table: 14dbc06a DAC: 00000015
12-30 00:24:14.808 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:24:14.808 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:24:14.808 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:24:14.808 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:24:14.808 0 0 W : Exception stack(0xd222bfb0 to 0xd222bff8)
12-30 00:24:14.808 0 0 W bfa0 : 717b4f84 00000000 00000000 00000001
12-30 00:24:14.808 0 0 W bfc0 : 00000000 00000000 136b32c0 00000000 00000000 ade4ce00 136b32c0 be853d4c
12-30 00:24:14.808 0 0 W bfe0 : 00000000 be853ce0 72150227 7215022a 600e0030 ffffffff
12-30 00:29:17.388 0 0 F : pgd = d8634000
12-30 00:29:17.388 0 0 F : [00000000] *pgd=00000000
12-30 00:29:17.388 0 0 W Pid : 4629, comm: verycallcontrol
12-30 00:29:17.388 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:29:17.388 0 0 W : PC is at 0x7215022a
12-30 00:29:17.388 0 0 W : LR is at 0x72150227
12-30 00:29:17.388 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600b0030
12-30 00:29:17.388 0 0 W sp : be854930 ip : 00000000 fp : 132bb498
12-30 00:29:17.388 0 0 W : r10: 132bc0a8 r9 : ade4ce00 r8 : 00000000
12-30 00:29:17.388 0 0 W : r7 : 00000000 r6 : 132bc0a8 r5 : 00000000 r4 : be8529b8
12-30 00:29:17.388 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:29:17.388 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:29:17.388 0 0 W Control : 10c5787d Table: 1863406a DAC: 00000015
12-30 00:29:17.388 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:29:17.388 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:29:17.388 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:29:17.388 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:29:17.388 0 0 W : Exception stack(0xd86b9fb0 to 0xd86b9ff8)
12-30 00:29:17.388 0 0 W 9fa0 : 717b4f84 00000000 00000000 00000001
12-30 00:29:17.388 0 0 W 9fc0 : be8529b8 00000000 132bc0a8 00000000 00000000 ade4ce00 132bc0a8 132bb498
12-30 00:29:17.388 0 0 W 9fe0 : 00000000 be854930 72150227 7215022a 600b0030 ffffffff
12-30 00:29:17.616 0 0 E [SSP] : proximity_open_calibration - Can't open cancelation file
12-30 00:29:17.616 0 0 E [SSP] : set_proximity_threshold - SENSOR_PROXTHRESHOLD
How's the gaming performance? Has anyone tested it with PUBGM or CoDM?
curiousrom said:
Thanks for the effort but 2 comments:
You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.
Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?
How does the Settings panel looks like?
***
And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
Click to expand...
Click to collapse
Hi curiousrom,
Thank you for yours advices. Could you please tell me precisely what you mean with the "Settings panel"? The QS panel or the General Settings panel?
I can tell you that since I flashed the ROM I have not had any particular issue worth a mention in my system. Only WhatsApp crashes from time to time. The phone app is behaving the way I expected it. The sensor is functioning properly since I do not see a black screen anymore after a call. With LineageOS 17.1 that still persist.
I will stay in touch through this thread for reporting any misbehavior of the system. Mr Haggertk is really doing a great job for the owners of our legendary device Samsung Galaxy S5. I own an SM-G900F.
Some of the unhandled page faults on startup (there are many):
[ 60.743339] CPU: 1 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 60.743345] PC is at 0x7118e758
[ 60.743348] LR is at 0x7118e755
[ 60.743353] pc : [<7118e758>] lr : [<7118e755>] psr: 60000030
[ 60.743355] sp : 92bec890 ip : 00000000 fp : 92bec904
[ 60.743359] r10: 92bec940 r9 : ac1f1400 r8 : 00000000
[ 60.743364] r7 : 137cbb60 r6 : 00000000 r5 : 00000000 r4 : 57fb4540
[ 60.743368] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 70831754
[ 60.743374] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 60.743379] Control: 10c5787d Table: 2489c06a DAC: 00000015
[ 60.743399] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 60.743410] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 60.743419] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 60.743429] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 60.743435] Exception stack(0xe3acdfb0 to 0xe3acdff8)
[ 60.743440] dfa0: 70831754 00000000 00000000 00000000
[ 60.743446] dfc0: 57fb4540 00000000 00000000 137cbb60 00000000 ac1f1400 92bec940 92bec904
[ 60.743452] dfe0: 00000000 92bec890 7118e755 7118e758 60000030 ffffffff
[ 60.778394] Thread-1: unhandled page fault (11) at 0x00000000, code 0x005
[ 60.778402] pgd = e489c000
[ 60.778591] [00000000] *pgd=00000000
[ 67.835852] Pid: 2836, comm: APIGuard3Backgr
[ 67.835860] CPU: 2 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 67.835867] PC is at 0x7d48bc70
[ 67.835871] LR is at 0x712ba17f
[ 67.835877] pc : [<7d48bc70>] lr : [<712ba17f>] psr: 000f0030
[ 67.835880] sp : 7b20aa80 ip : 00000000 fp : 00000060
[ 67.835885] r10: 00000000 r9 : a9774e00 r8 : 00000000
[ 67.835891] r7 : 12cd26e8 r6 : 12cd24b8 r5 : 12cd2708 r4 : 710feac8
[ 67.835897] r3 : 70f53c50 r2 : 12cd2708 r1 : 00000000 r0 : 00000003
[ 67.835904] Flags: nzcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 67.835910] Control: 10c5787d Table: 1e69406a DAC: 00000015
[ 67.835932] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 67.835945] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 67.835957] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 67.835969] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 67.835976] Exception stack(0xdecdffb0 to 0xdecdfff8)
[ 67.835982] ffa0: 00000003 00000000 12cd2708 70f53c50
[ 67.835990] ffc0: 710feac8 12cd2708 12cd24b8 12cd26e8 00000000 a9774e00 00000000 00000060
[ 67.835998] ffe0: 00000000 7b20aa80 712ba17f 7d48bc70 000f0030 ffffffff
Minor issue. When logging in to my wifi which is wpa enterprise it requires a domain name as the phase 2 authentication defaults to MSCHAPV2 and has no option for "do not authenticate". Since I don't know my domain name is there a workaround?
haggertk said:
...
All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
Click to expand...
Click to collapse
See S5 Odin Flashable Modem & Bootloader and S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat.
***
It seems like my SC-04F doesn't show charging when I plugged in. The % goes up after rebooting.
Baseband: SC04FOMU1XQH1 (latest)
ROM Build: kltekdi, build 20201225
These are the logs when I only wiped System and Cache. I later formatted Data and it's still the same.
Thank you for your work!
e: Logcat: https://pastebin.pl/view/4de644ca
dmesg is the uploaded file.
e3: after formatting. Had to have Magisk to get dmesg log
dmesg: https://pastebin.pl/view/46bc06dc
logcat: https://pastebin.pl/view/1d2b50a8
Hey @haggertk, I have a SM-S902L. Can I use the rom for SM-S900L for my device? If not would you be so kind and add support for my model? I had been waiting for lineage 17.1 for quite some time now and installed an unofficial build to get android 10. I just found this amazing thread which is a way for me to get android 11. Please consider my request. Thanks