{
"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 14.1 (Android 7.1.2) for the Amazon Fire HD8 2016/2017
Disclaimer:
Code:
/*
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
IMPORTANT NOTES BEFORE INSTALLING THE ROM:
As usual, you need to be unlocked to install this ROM.
This ROM is in beta status so don't expect 100% stable ROM.
This ROM is only compatible with the Fire HD8 2017 (douglas) and the Fire HD8 2016 (giza). All questions related to other devices will be reported and ignored.
KNOWN ISSUES:
Hardware Decoding is not working (OMX - 1080p video playback).
Volume keys behave weirdly.
Photos/Video recordings aren't working.
Encryption (Disabled).
INSTALLATION:
Boot to TWRP.
Wipe system, cache and userdata.
Install the ROM zip.
(OPTIONAL): Flash G-Apps package.
(OPTIONAL): Flash root (Magisk/SuperSU).
Wipe Dalvik Cache.
Reboot and enjoy!
DOWNLOADS:
ROM (Fire HD8 2017 - douglas): lineage-14.1-20210826-UNOFFICIAL-douglas.zip | md5sum: 2b7f37a42755e5191e6249217bcb24fe
ROM (Fire HD8 2016 - giza): lineage-14.1-20210826-UNOFFICIAL-giza.zip | md5sum: 909932efcc3edcc0b249d06037cc8643
Open GApps: https://opengapps.org/?arch=arm64&api=7.1&variant=pico
Source Code:
https://github.com/mt8163-dev
Special Thanks:
SPECIAL THANKS to @FreakyyLike for donating me douglas.
@Lorisson for testing the ROM (douglas).
@Iovaduck for testing the ROM (giza).
XDA:DevDB Information
LineageOS 14.1 for the Amazon Fire HD8 2017/2016, ROM for the Amazon Fire HD 8 2017/2016
Contributors
Rortiz2
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader + TWRP
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 7
Beta Release Date: 2020-11-26
Created 2020-11-26
Last Updated 2021-08-13
Changelog
2021-08-26 [douglas] [giza]
Updated wpa_supplicant_8 HAL.
Now building libwifi-hal-mt66xx.
Rebased the kernel source to the latest Amazon sources (Fire_HD8_7th_Gen-5.3.7.3.tar.bz2).
Set build characteristics to tablet.
Dropped prebuilt lights HAL, now building it.
UID_SYS_STATS are fully functional now.
[KERNEL]: Upstreamed Power/PM drivers.
Synced with LineageOS sources (cm-14.1).
2021-08-13 [douglas] [giza]
Fixed WebView crashes (Chrome should work).
Spoofed Fingerprint (uses Pixel XL's fingerprint now).
Increased ZRAM to 786MB (+250MB ~).
Dropped deprecated dhpcd.
Synced with LineageOS sources (cm-14.1).
2021-07-11 [douglas] [giza]
Added support for the Fire HD8 2016! (initial common build).
Added a lot of performance tweaks to the kernel.
Enabled ZRAM (uses LZ4).
2021-06-14
Updated vendor blobs to 5.6.8.0.
Fixed UID_SYS_STATS (+ performance).
Removed audio logcat spam (+ battery life).
Limited background processes.
Enabled ZRAM.
Fixed microphone.
Updated Security Patch to 2021-05-05.
Synced with LineageOS sources (cm-14.1).
2021-01-30
Fixed external SDCards.
Synced with LineageOS sources (cm-14.1).
2021-01-05
Updated Security Patch to DEC 2020.
Enabled USB tethering interface (rndis0) in the overlay.
Disabled Encryption from Settings.
Enabled Doze (Deep Sleep).
Enabled offline charging.
Introduced libinit.
Synced with LineageOS sources (cm-14.1).
2020-11-30
Fixed Prime Video and other Amazon apps.
Changed product brand to google to pass play-certification.
Fixed some out of memory GL crashes (app crashes).
Enabled BLE.
Some updates related to storage (still not working).
Fixed OTAs.
2020-11-28
Fixed Video Playback (SW).
Fixed Audio.
Disabled Camera (no more battery drains).
[KERNEL]: Fixed warning when releasing active sync point.
2020-11-26
Initial Release.
Audio is not working at all (due camera).
DRM should be working (L1).
SDcard does weird stuff.
Video Playback is broken aswell (due camera).
Volume keys are swapped sometimes.
TODO LIST
[fixed] Audio working without problems - camera was causing weird issues.
[fixed] DRM seems to be working - LP legacy libraries were causing weird libc fatal crashes.
[partially fixed] OMX is partially working - SW decoding is working fine. HW decoding is broken as of now.
[fixed] Wi-Fi working - Been working without problems since the first build.
[fixed] BT working - Same as Wi-Fi, always have been working without problems.
[todo] Camera not working - Videos and Photos aren't working. Enabling camera causes issues with Audio and OMX (SW).
[fixed] External SDCard - There are some mounting issues (vold related?) - External SDCard is working without problems now.
[todo] Deep Sleep - Pending to enable Doze and see if it improves the Deep Sleep. Still not working, big battery drains.
[todo] Volume keys are working weirdly - They're sometimes swapped.
Reserved (3)
Will try later today and report.
Downloading...
I'm still not able to play music with Doubletwist or watch movies with Tubi. File Manager+ also doesn't see the SD card properly. It just says that a 128GB card is an empty 673 MB one. Odd.
Just a quick test after installation, Amazon Shopping still does not work
Installing now and will report with any useful info that may be needed. A great Thanksgiving gift!
Adb logcat shows (permanently) crashing mediaserver:
Code:
11-27 23:54:31.380 8802 8802 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x54 in tid 8802 (mediaserver)
11-27 23:54:31.380 192 192 W : debuggerd: handling request: pid=8802 uid=1013 gid=1005 tid=8802
11-27 23:54:31.447 8812 8812 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-27 23:54:31.447 8812 8812 F DEBUG : LineageOS Version: '14.1-20201126-UNOFFICIAL-douglas'
11-27 23:54:31.447 8812 8812 F DEBUG : Build fingerprint: 'Amazon/cm_douglas/douglas:7.1.2/NJH47F/3feda29ce4:userdebug/test-keys'
11-27 23:54:31.447 8812 8812 F DEBUG : Revision: '0'
11-27 23:54:31.447 8812 8812 F DEBUG : ABI: 'arm'
11-27 23:54:31.447 8812 8812 F DEBUG : pid: 8802, tid: 8802, name: mediaserver >>> /system/bin/mediaserver <<<
11-27 23:54:31.447 8812 8812 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x54
11-27 23:54:31.447 8812 8812 F DEBUG : r0 00000000 r1 00000003 r2 ffb56404 r3 f6ac6a65
11-27 23:54:31.447 8812 8812 F DEBUG : r4 f5fcffc0 r5 f3149184 r6 00000000 r7 00000001
11-27 23:54:31.447 8812 8812 F DEBUG : r8 00000000 r9 00000000 sl 00000000 fp ffb56510
11-27 23:54:31.447 8812 8812 F DEBUG : ip f314b834 sp ffb563e8 lr f3135b9d pc f6ac6a6c cpsr 000f0030
11-27 23:54:31.452 8812 8812 F DEBUG :
11-27 23:54:31.452 8812 8812 F DEBUG : backtrace:
11-27 23:54:31.452 8812 8812 F DEBUG : #00 pc 0005da6c /system/lib/libcameraservice.so
11-27 23:54:31.452 8812 8812 F DEBUG : #01 pc 00014b9b /system/lib/libcam.client.so (_ZN7android15NSDisplayClient13DisplayClient15restoreBufCountEv+18)
11-27 23:54:31.452 8812 8812 F DEBUG : #02 pc 000150f1 /system/lib/libcam.client.so (_ZN7android15NSDisplayClient13DisplayClient6uninitEv+24)
11-27 23:54:31.452 8812 8812 F DEBUG : #03 pc 00008d19 /system/lib/libcam.device1.so (_ZN7android14Cam1DeviceBase17initDisplayClientEP18preview_stream_ops+56)
11-27 23:54:31.452 8812 8812 F DEBUG : #04 pc 0000775b /system/lib/libcam.device1.so (_ZN7android14Cam1DeviceBase16setPreviewWindowEP18preview_stream_ops+34)
11-27 23:54:31.452 8812 8812 F DEBUG : #05 pc 0005ce7b /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl22disconnectCameraDeviceEv+138)
11-27 23:54:31.452 8812 8812 F DEBUG : #06 pc 0005d05d /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl18hasFlashUnitLockedERKNS_7String8EPbb+100)
11-27 23:54:31.453 8812 8812 F DEBUG : #07 pc 0005d101 /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl12hasFlashUnitERKNS_7String8EPb+28)
11-27 23:54:31.453 8812 8812 F DEBUG : #08 pc 0005bf41 /system/lib/libcameraservice.so (_ZN7android16CameraFlashlight14findFlashUnitsEv+140)
11-27 23:54:31.453 8812 8812 F DEBUG : #09 pc 0004ff13 /system/lib/libcameraservice.so (_ZN7android13CameraService10onFirstRefEv+302)
11-27 23:54:31.453 8812 8812 F DEBUG : #10 pc 00000eb3 /system/bin/mediaserver
11-27 23:54:31.453 8812 8812 F DEBUG : #11 pc 00000d47 /system/bin/mediaserver
11-27 23:54:31.453 8812 8812 F DEBUG : #12 pc 00016ca1 /system/lib/libc.so (__libc_init+48)
11-27 23:54:31.453 8812 8812 F DEBUG : #13 pc 00000c2c /system/bin/mediaserver
11-27 23:54:31.603 584 767 W NativeCrashListener: Couldn't find ProcessRecord for pid 8802
11-27 23:54:31.603 8802 8808 D AMZ-lsc_mgr2_thread: [changeThreadSetting] sensor(1), tid(8808), policy:(expect, result)=(0, 0), priority:(expect, result)=(0xfffffffd, 0xfffffffd)
11-27 23:54:31.603 8802 8808 D AMZ-lsc_mgr2_thread: [doThreadFunc +]
11-27 23:54:31.606 584 622 I BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
11-27 23:54:31.613 192 192 W : debuggerd: resuming target 8802
11-27 23:54:31.616 288 288 I ServiceManager: service 'media.player' died
11-27 23:54:31.616 288 288 I ServiceManager: service 'media.resource_manager' died
11-27 23:54:32.240 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:32.240 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:32.240 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:32.241 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.242 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:33.242 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.242 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:33.243 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:284): avc: denied { read } for name="FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:285): avc: denied { open } for path="/sys/devices/platform/battery/FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:286): avc: denied { getattr } for path="/sys/devices/platform/battery/FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:34.244 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:34.244 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:34.244 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:34.245 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:34.943 8818 8818 I mediaserver: ServiceManager: 0xf5e90520
11-27 23:54:34.944 8818 8818 I CameraService: CameraService started (pid=8818)
11-27 23:54:34.945 8818 8818 I CameraService: CameraService process starting
11-27 23:54:35.166 8818 8818 D AMZ-IspDrv: [IspDrvImp] getpid[0x00002272],gettid[0x00002272]
Besides that: A very snappy, fast nice ROM. Awesome work @Rortiz2 ! Did not test that much yet but I am already impressed by the speed compared to what I had installed before. Again, thanks.
Youtube, amazon prime, netflix not working go service updated
Thanks for the ROM. Here's my initial testing feedback...
I tested a video, but could not get any playback.
I couldn't get any audio working with either RadioDroid or AntennaPod. Also, the battery drain was relatively fast.
A logcat was showing issues with the Camera Service crashing constantly. So, referring back to the feedback on the Alpha version, I rebooted to TWRP, and deleted:
/system/lib64/hw/camera.mt8163.so
/system/lib/hw/camera.mt8163.so
... and now ... SUCCESS!
RadioDroid and AntennaPod are both working correctly.
My bluetooth speaker was working well.
Also, I was able to get an mp4 video playback working on a 1080p mp4 video. I only sampled the video, but it seemed to be working fine.
The camera app is not showing anymore (certainly related to my deletion of critical files for this app).
It'll take more time to get additional feedback on the battery life.
The SDCard is funky. It's volume label appears to be jibberish. Some apps find it OK, other apps have trouble seeing my SDCard.
Thanks again.
Great feedback! I also did this workaround and can now enjoy music. Thank you for the information. Another issue related to the sound, I realized in Setting>Sound, I could not move the bar to change the sound level. This issue also gone. I think sound related issue has solved. If SDCard issue solved, I can enjoy music on my SDCard. And I can see Images with Gallery that are on SDCard. Waiting for solving the SDcard issue.
Modelo l5s83a
Hola, mi tablet es la modelo l5s83a. Ahora tengo puesta lineage 15.1, quisiera poner esta versión la 14.1. Puedo instalarla? Estoy buscando haber si mi modelo es del 2017 pero no lo encuentro. Se que es de 8th generación. Gracias, un saludo.
KaTze87 said:
Hola, mi tablet es la modelo l5s83a. Ahora tengo puesta lineage 15.1, quisiera poner esta versión la 14.1. Puedo instalarla? Estoy buscando haber si mi modelo es del 2017 pero no lo encuentro. Se que es de 8th generación. Gracias, un saludo.
Click to expand...
Click to collapse
Esto es para la HD8 2017.. Tu tienes el modelo 2018 así que estás buscando esto: https://forum.xda-developers.com/hd8-hd10/orig-development/lineageos-14-1-fire-hd8-2018-t3936242
Also please use english..
Enviat des del meu WAS-LX1A usant Tapatalk
New build is up
2020-11-28
Fixed Video Playback (SW).
Fixed Audio.
Disabled Camera (no more battery drains).
[KERNEL]: Fixed warning when releasing active sync point.
Note: You should be able to install this version using the built-in LineageOS OTA updater though I don't know if will work. If somebody updates using the OTA app let me know if works correctly.
GoodSoul said:
Adb logcat shows (permanently) crashing mediaserver:
Code:
11-27 23:54:31.380 8802 8802 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x54 in tid 8802 (mediaserver)
11-27 23:54:31.380 192 192 W : debuggerd: handling request: pid=8802 uid=1013 gid=1005 tid=8802
11-27 23:54:31.447 8812 8812 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-27 23:54:31.447 8812 8812 F DEBUG : LineageOS Version: '14.1-20201126-UNOFFICIAL-douglas'
11-27 23:54:31.447 8812 8812 F DEBUG : Build fingerprint: 'Amazon/cm_douglas/douglas:7.1.2/NJH47F/3feda29ce4:userdebug/test-keys'
11-27 23:54:31.447 8812 8812 F DEBUG : Revision: '0'
11-27 23:54:31.447 8812 8812 F DEBUG : ABI: 'arm'
11-27 23:54:31.447 8812 8812 F DEBUG : pid: 8802, tid: 8802, name: mediaserver >>> /system/bin/mediaserver <<<
11-27 23:54:31.447 8812 8812 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x54
11-27 23:54:31.447 8812 8812 F DEBUG : r0 00000000 r1 00000003 r2 ffb56404 r3 f6ac6a65
11-27 23:54:31.447 8812 8812 F DEBUG : r4 f5fcffc0 r5 f3149184 r6 00000000 r7 00000001
11-27 23:54:31.447 8812 8812 F DEBUG : r8 00000000 r9 00000000 sl 00000000 fp ffb56510
11-27 23:54:31.447 8812 8812 F DEBUG : ip f314b834 sp ffb563e8 lr f3135b9d pc f6ac6a6c cpsr 000f0030
11-27 23:54:31.452 8812 8812 F DEBUG :
11-27 23:54:31.452 8812 8812 F DEBUG : backtrace:
11-27 23:54:31.452 8812 8812 F DEBUG : #00 pc 0005da6c /system/lib/libcameraservice.so
11-27 23:54:31.452 8812 8812 F DEBUG : #01 pc 00014b9b /system/lib/libcam.client.so (_ZN7android15NSDisplayClient13DisplayClient15restoreBufCountEv+18)
11-27 23:54:31.452 8812 8812 F DEBUG : #02 pc 000150f1 /system/lib/libcam.client.so (_ZN7android15NSDisplayClient13DisplayClient6uninitEv+24)
11-27 23:54:31.452 8812 8812 F DEBUG : #03 pc 00008d19 /system/lib/libcam.device1.so (_ZN7android14Cam1DeviceBase17initDisplayClientEP18preview_stream_ops+56)
11-27 23:54:31.452 8812 8812 F DEBUG : #04 pc 0000775b /system/lib/libcam.device1.so (_ZN7android14Cam1DeviceBase16setPreviewWindowEP18preview_stream_ops+34)
11-27 23:54:31.452 8812 8812 F DEBUG : #05 pc 0005ce7b /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl22disconnectCameraDeviceEv+138)
11-27 23:54:31.452 8812 8812 F DEBUG : #06 pc 0005d05d /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl18hasFlashUnitLockedERKNS_7String8EPbb+100)
11-27 23:54:31.453 8812 8812 F DEBUG : #07 pc 0005d101 /system/lib/libcameraservice.so (_ZN7android35CameraHardwareInterfaceFlashControl12hasFlashUnitERKNS_7String8EPb+28)
11-27 23:54:31.453 8812 8812 F DEBUG : #08 pc 0005bf41 /system/lib/libcameraservice.so (_ZN7android16CameraFlashlight14findFlashUnitsEv+140)
11-27 23:54:31.453 8812 8812 F DEBUG : #09 pc 0004ff13 /system/lib/libcameraservice.so (_ZN7android13CameraService10onFirstRefEv+302)
11-27 23:54:31.453 8812 8812 F DEBUG : #10 pc 00000eb3 /system/bin/mediaserver
11-27 23:54:31.453 8812 8812 F DEBUG : #11 pc 00000d47 /system/bin/mediaserver
11-27 23:54:31.453 8812 8812 F DEBUG : #12 pc 00016ca1 /system/lib/libc.so (__libc_init+48)
11-27 23:54:31.453 8812 8812 F DEBUG : #13 pc 00000c2c /system/bin/mediaserver
11-27 23:54:31.603 584 767 W NativeCrashListener: Couldn't find ProcessRecord for pid 8802
11-27 23:54:31.603 8802 8808 D AMZ-lsc_mgr2_thread: [changeThreadSetting] sensor(1), tid(8808), policy:(expect, result)=(0, 0), priority:(expect, result)=(0xfffffffd, 0xfffffffd)
11-27 23:54:31.603 8802 8808 D AMZ-lsc_mgr2_thread: [doThreadFunc +]
11-27 23:54:31.606 584 622 I BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
11-27 23:54:31.613 192 192 W : debuggerd: resuming target 8802
11-27 23:54:31.616 288 288 I ServiceManager: service 'media.player' died
11-27 23:54:31.616 288 288 I ServiceManager: service 'media.resource_manager' died
11-27 23:54:32.240 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:32.240 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:32.240 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:32.241 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.242 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:33.242 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.242 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:33.243 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:284): avc: denied { read } for name="FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:285): avc: denied { open } for path="/sys/devices/platform/battery/FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:33.431 5053 5053 I Thread-12: type=1400 audit(0.0:286): avc: denied { getattr } for path="/sys/devices/platform/battery/FG_Battery_CurrentConsumption" dev="sysfs" ino=19392 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
11-27 23:54:34.244 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:34.244 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:34.244 584 618 I CameraManagerGlobal: Connecting to camera service
11-27 23:54:34.245 584 618 E CameraManagerGlobal: Camera service is unavailable
11-27 23:54:34.943 8818 8818 I mediaserver: ServiceManager: 0xf5e90520
11-27 23:54:34.944 8818 8818 I CameraService: CameraService started (pid=8818)
11-27 23:54:34.945 8818 8818 I CameraService: CameraService process starting
11-27 23:54:35.166 8818 8818 D AMZ-IspDrv: [IspDrvImp] getpid[0x00002272],gettid[0x00002272]
Besides that: A very snappy, fast nice ROM. Awesome work @Rortiz2 ! Did not test that much yet but I am already impressed by the speed compared to what I had installed before. Again, thanks.
Click to expand...
Click to collapse
Hi,
I know mediaserver it's constantly crashing in the background but I don't know how to fix that crash.
I tried a lot of stuff with the same result (no success) so I ended up nuking out camera in the latest build.
I guess the problem it's related to libhal_effects.so since I always see before the libc crash:
Code:
11-27 20:57:26.840 3230 3230 D AMZ-Hal_Effects: >HalEffects
11-27 20:57:26.840 3230 3230 D AMZ-Frosted_Glass: >FrostedGlass
11-27 20:57:26.840 3230 3230 D AMZ-Frosted_Glass: <FrostedGlass
11-27 20:57:26.840 3230 3230 D AMZ-Hal_Effects: <HalEffects
11-27 20:57:26.840 3230 3230 D AMZ-Hal_Effects: >~HalEffects
11-27 20:57:26.840 3230 3230 D AMZ-Hal_Effects: <~HalEffects
Regards.
dontpanic-xda said:
A logcat was showing issues with the Camera Service crashing constantly. So, referring back to the feedback on the Alpha version, I rebooted to TWRP, and deleted:
/system/lib64/hw/camera.mt8163.so
/system/lib/hw/camera.mt8163.so
Click to expand...
Click to collapse
Oh. Thank you!
Actually I forgot to delete those files and I have a very weird behavior: Firefox crashes all time, as well as Kodi. Youtube stuck on a white screen with some widgets all around. The tablet is very unstable
I deleted the files and now everything is OK, like the Alpha version
--
ciao
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
Rortiz2 said:
2020-11-28
Note: You should be able to install this version using the built-in LineageOS OTA updater though I don't know if will work. If somebody updates using the OTA app let me know if works correctly.
Click to expand...
Click to collapse
Upgrading using OTA: I let you know
---------- Post added at 12:51 PM ---------- Previous post was at 12:47 PM ----------
Rortiz2 said:
I tried a lot of stuff with the same result (no success) so I ended up nuking out camera in the latest build.
Click to expand...
Click to collapse
You're a wise man
And thanks again for you hard work: now I have a perfectly usable tablet
--
ciao
Rortiz2 said:
2020-11-28
Note: You should be able to install this version using the built-in LineageOS OTA updater though I don't know if will work. If somebody updates using the OTA app let me know if works correctly.
Click to expand...
Click to collapse
The OTA updater has detected and downloaded the version but gave an error when I tried to install it
I've got TWRP 3.3.1-0
So I did a reboot in recovery and manually install the zip downloaded by the updater
I did an installation on the previous version, wiping only cache and dalvik
Everything is OK but Amazon shop still does not work and Firefox is still lagging a little bit
*Edit*
Regarding Syncthing, it's possible sync only folders in the internal memory., despite the app can access the SD
--
ciao
Overall Impressions: Very Good So Far!
NTGDeveloper said:
Installing now and will report with any useful info that may be needed. A great Thanksgiving gift!
Click to expand...
Click to collapse
Gotta say this ROM is already working pretty well in general. I can't wait to see what else can come.
For my testing, I used a 16GB Fire HD 8 Douglas for the build that was released on November 28th, and I also flashed the first beta build on a 32GB Fire HD 8 Douglas as well. The 16GB had Magisk root and both installations included OpenGApps "Nano" package as that is what I prefer for the majority of my ROM installations. Even though the "pico" package was
I won't be mentioning my issues on the first build since those have already been addressed in replies to this post, so my focus is on the new build from today. Since I already had the first beta build installed on a testing tablet, I used the built-in LineageOS updater and it detected an update and even downloaded the update, but then showed a silent notification reading "LineageOS 14.1 - Nov 28, 2020 Install Error". I have attached a picture for reference. Because of this failure, I just rebooted the device into recovery mode and flashed the image manually using ADB Sideload, without doing a clean installation. (In other words, I didn't wipe anything before or after sideloading the ZIP file in TWRP, other than Cache and Dalvik after flashing) When I flashed the image, it seemed that Magisk 21.0 popped up in the log and even patched the boot image. That's pretty cool since I don't recall ever seeing that before. I then rebooted my system, and I gotta say, it took a while to load, but it eventually put me on the lock screen with the notification, "Finishing Android Update"! That was good to see, and everything seemed like it was before. So, without further ado, let's finally get to testing the ROM itself.
For testing ROMs, I like to follow a basic method that I came up with on my own, and my testing is compiled with a variety of different tasks. I will list only the issues that I encountered since my testing can be a little comprehensive. While I am not done with my testing yet, I will share my results after spending a good couple of hours with my device.
Volume Control: Backwards when in portrait orientation at first, but after rotating, it was fixed.
Bluetooth: Cannot pair a Bluetooth speaker (Specifically a Google Home Mini) because of incorrect paring pin. See Screenshots below (Bluetooth1.png and Bluetooth2.png) It seemed to prompt me to enter a pairing PIN, but did not give me a place to enter a code. However, on a device like this, I shouldn't enter a PIN. It should show me a pin to match with the device (or something similar to that).
Browser: Playing 1080p video on YouTube using the built-in browser gave me a stutter every once in a while, but I won't blame it on the ROM, and I believe that it has something to do with the hardware in the tablet itself (or my internet connection, which is gigabit with Comcast and an Arris S33 Modem and Nest Wifi Router). I was loading some websites built on the WordPress framework and while they loaded, I experienced some graphical glitches with them. Again, I'm not sure if it is the browser in the ROM or the device, but still, something to note.
Camera: There was no camera app on the launcher, so I attempted to load it through the lock screen, but it was a white screen, presumably attempting to load the app, but then it just brought me back to the lock screen as if it crashed. But, I had a screen lock turned on. So, when I unlocked my device, the camera app asked for my location, so when I allowed the permission, it actually crashed.
So those are my initial bugs, but I'm far from being done with this ROM. I have a whole lot of plans and tests and I can't wait to help out even more.
Related
Hi,
last week I decided to update an old falcon (european XT1032) I had at home, with already unlocked bootloader and cm11 installed.
I formatted everything in order to install latest cm13 nightly, but I discovered I had a too old bootloader.
So I updated bootloader to latest version (41.1A) and updated to latest TWRP (2.8.6.0).
So I installed CM13 nightly, wiping everything.
It booted succesfully, but I have a problem: wi-fi doesn't work.
It cannot be activated nor deactivated. It stay forever in "activating wi-fi" with the on/off button grayed out.
Also, in wi-fi advanced properties, the mac address is 02:00:00:00:00:00, which is a fake address.
It seems android cannot initialize properly the wi-fi chip.
Haven't tried yet to insert a sim card, or use bluetooth, or else... maybe they don't work too.
I tried to look to into the official cm13 thread, but it seems I'm the only one facing this problem.
I wanted to try cm12.1 also, but their downloads are no longer available in the get.cm site (404 error).
Tried with different builds of latest nightlies, also wiping system and data a lot of times, but nothing changed.
What is wrong with my falcon? Did I bricked it somehow? I have no idea on what went wrong...
I tried to rollback to a previous bootloader, but I cannot install it anymore: it says (bootloader) Preflash validation failed
(it seems to be a protection: I cannot install previous bootloader versions)
Thanks.
Don't try to downgrade your bootloader it could brick your device!!!
Try it again with latest TWRP (2.8.7.0)!
Andus1988 said:
Don't try to downgrade your bootloader it could brick your device!!!
Try it again with latest TWRP (2.8.7.0)!
Click to expand...
Click to collapse
I updated TWRP to latest 2.8.7.0 (notheme version), I wiped all (system, data, cache), I downloaded and installed latest nightly.. tried with or without gapps...
everytime it's always the same...
I tried inserting a sim; data connection works. Everything else works (even bluetooth).
The only thing that's not working is wi-fi, and mac address is still 02:00:00:00:00:00.
I really don't know what to do... because I don't understand what may be wrong. :crying:
Have u already tried your phone in another wifi?
Andus1988 said:
Have u already tried your phone in another wifi?
Click to expand...
Click to collapse
It's no matter of a wifi network... The wifi doesn't start at all.
Here's a logcat trace when I try to switch on wifi:
Code:
01-11 23:28:49.394 4610 5010 E WifiHW : Failed to write wlan fw path param (Operation not permitted)
01-11 23:28:49.394 4610 5010 E SoftapController: Softap fwReload failed
01-11 23:28:49.395 4858 5117 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '20 softap fwreload wlan0 STA' failed with '400 20 SoftAP command has failed'
01-11 23:28:49.395 4610 5010 W CommandListener: Failed to retrieve HW addr for wlan0 (No such device)
01-11 23:28:49.399 4610 5010 D CommandListener: Setting iface cfg
01-11 23:28:49.400 4858 5117 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '22 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 22 Failed to set address (No such device)'
01-11 23:28:49.400 4858 5117 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
01-11 23:28:49.400 4858 5117 E wifi : Could not read interface wlan0 flags: 19
01-11 23:28:49.400 4858 5117 E WifiNative-HAL: Could not start hal
01-11 23:28:49.400 4858 5117 E WifiStateMachine: Failed to start HAL
01-11 23:28:49.411 4858 5117 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
01-11 23:28:49.413 4858 5117 E WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
01-11 23:28:49.501 7077 7077 I wpa_supplicant: Successfully initialized wpa_supplicant
01-11 23:28:49.503 7077 7077 I wpa_supplicant: rfkill: Cannot open RFKILL control device
01-11 23:28:49.503 7077 7077 E wpa_supplicant: Could not read interface p2p0 flags: No such device
01-11 23:28:49.504 7077 7077 I wpa_supplicant: nl80211: deinit ifname=p2p0 disabled_11b_rates=0
01-11 23:28:49.504 7077 7077 E wpa_supplicant: Could not read interface p2p0 flags: No such device
01-11 23:28:49.504 7077 7077 E wpa_supplicant: p2p0: Failed to initialize driver interface
01-11 23:28:49.513 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:49.614 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:49.714 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:49.815 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:49.915 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.016 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.116 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.217 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.317 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.418 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.518 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.619 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.719 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.820 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:50.921 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.022 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.122 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.223 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.324 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.425 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.525 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.625 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.726 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.826 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.927 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:51.969 229 289 I ThermalEngine: Sensor:batt_therm:30200 mC
01-11 23:28:52.027 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.128 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.228 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.329 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.430 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.530 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.540 4612 5032 D audio_hw_primary: out_standby: enter: stream (0xb7227038) usecase(1: low-latency-playback)
01-11 23:28:52.595 4612 5032 D hardware_info: hw_info_append_hw_type : device_name = speaker-lite
01-11 23:28:52.630 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.731 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.831 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:52.932 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.032 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.133 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.233 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.334 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.434 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.535 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.635 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.739 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.840 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:53.940 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.041 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.142 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.242 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.343 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.443 4858 5117 E WifiHW : Supplicant not running, cannot connect
01-11 23:28:54.443 4858 5117 E WifiMonitor: startMonitoring(wlan0) failed!
01-11 23:28:54.446 4858 5117 E WifiStateMachine: Failed to setup control channel, restart supplicant
01-11 23:28:54.446 4858 5117 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
01-11 23:28:58.842 4858 4880 I ActivityManager: Config changes=480 {1.0 ?mcc?mnc it_IT ldltr sw360dp w592dp h336dp 320dpi nrml land finger -keyb/v/h -nav/h s.6 themeResource=null}
01-11 23:28:58.849 4858 5099 I InputReader: Reconfiguring input devices. changes=0x00000004
01-11 23:28:58.849 4858 5099 I InputReader: Device reconfigured: id=3, name='synaptics_dsx_i2c', size 720x1280, orientation 1, mode 1, display id 0
01-11 23:28:58.851 4858 5099 I InputReader: Reconfiguring input devices. changes=0x00000004
01-11 23:28:59.055 4858 4892 I WindowManager: Screen frozen for +289ms due to Window{5fcb052 u0 com.android.settings/com.android.settings.SubSettings}
01-11 23:28:59.456 7156 7156 W ueventd : type=1400 audit(0.0:15): avc: denied { search } for uid=0 name="/" dev="mmcblk0p29" ino=2 scontext=u:r:ueventd:s0 tcontext=u:object_r:unlabeled:s0 tclass=dir permissive=0
01-11 23:28:59.474 4610 5010 E WifiHW : Failed to write wlan fw path param (Operation not permitted)
01-11 23:28:59.474 4610 5010 E SoftapController: Softap fwReload failed
01-11 23:28:59.475 4858 5117 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '23 softap fwreload wlan0 STA' failed with '400 23 SoftAP command has failed'
01-11 23:28:59.475 4610 5010 W CommandListener: Failed to retrieve HW addr for wlan0 (No such device)
01-11 23:28:59.476 4610 5010 D CommandListener: Setting iface cfg
01-11 23:28:59.477 4858 5117 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '25 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 25 Failed to set address (No such device)'
01-11 23:28:59.477 4858 5117 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
01-11 23:28:59.477 4858 5117 E wifi : Could not read interface wlan0 flags: 19
01-11 23:28:59.477 4858 5117 E WifiNative-HAL: Could not start hal
01-11 23:28:59.477 4858 5117 E WifiStateMachine: Failed to start HAL
01-11 23:28:59.480 4858 5117 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
01-11 23:28:59.588 7157 7157 I wpa_supplicant: Successfully initialized wpa_supplicant
01-11 23:28:59.590 7157 7157 I wpa_supplicant: rfkill: Cannot open RFKILL control device
01-11 23:28:59.590 7157 7157 E wpa_supplicant: Could not read interface p2p0 flags: No such device
01-11 23:28:59.590 7157 7157 I wpa_supplicant: nl80211: deinit ifname=p2p0 disabled_11b_rates=0
01-11 23:28:59.590 7157 7157 E wpa_supplicant: Could not read interface p2p0 flags: No such device
01-11 23:28:59.590 7157 7157 E wpa_supplicant: p2p0: Failed to initialize driver interface
Fix broken wifi in CM13
sigitm said:
...update an old falcon (european XT1032) I had at home, with already unlocked bootloader and cm11 installed.
I formatted everything in order to install latest cm13 nightly, but I discovered I had a too old bootloader.
So I updated bootloader to latest version (41.1A) and updated to latest TWRP (2.8.6.0).
So I installed CM13 nightly, wiping everything.
It booted succesfully, but I have a problem: wi-fi doesn't work.
It cannot be activated nor deactivated. It stay forever in "activating wi-fi" with the on/off button grayed out.
Also, in wi-fi advanced properties, the mac address is 02:00:00:00:00:00, which is a fake address....
Click to expand...
Click to collapse
Did the same today. Came from PAC-ROM 4.4.4 with base CM11. Bootloader update to 41.1A, flash, no wifi. I managed to fix it. Don't know if every step is necessary but this is how I did it. Use TWRP as the recovery, not the CM one.
Download CM12.1 stable from the CM website
Reboot to recovery, do a factory reset
Flash CM12.1 stable
Reboot and go through the setup wizard steps, wifi should work, log into your wifi
Reboot to recovery
Flash CM13 nightly
Reboot
Now wifi should work in CM13. Seems to be something it carries over from CM12.1 that's needed.
Solved!
blu2lz said:
Did the same today. Came from PAC-ROM 4.4.4 with base CM11. Bootloader update to 41.1A, flash, no wifi. I managed to fix it. Don't know if every step is necessary but this is how I did it. Use TWRP as the recovery, not the CM one.
Download CM12.1 stable from the CM website
Reboot to recovery, do a factory reset
Flash CM12.1 stable
Reboot and go through the setup wizard steps, wifi should work, log into your wifi
Reboot to recovery
Flash CM13 nightly
Reboot
Now wifi should work in CM13. Seems to be something it carries over from CM12.1 that's needed.
Click to expand...
Click to collapse
Thank you blu2lz, you saved my day!!
Now it works perfectly!
Oh my. I have the same trouble on the Moto G LTE (XT1039). Problem is, there never was as stable CM-12.1…
still faulty
sigitm said:
Thank you blu2lz, you saved my day!!
Now it works perfectly!
Click to expand...
Click to collapse
I have exactly the same fault with the funny Mac address... 02:00:00 etc on 13.1 downgraded to 12.1 after a factory reset..
Mac address now " unavailble"
Deleted everything, formmated, went back up to 13.1 Mac address still 02:00:00:00
Gutted.. this must be a hardwear fault? lots of people are getting this from the MM update.
blu2lz said:
Did the same today. Came from PAC-ROM 4.4.4 with base CM11. Bootloader update to 41.1A, flash, no wifi. I managed to fix it. Don't know if every step is necessary but this is how I did it. Use TWRP as the recovery, not the CM one.
Download CM12.1 stable from the CM website
Reboot to recovery, do a factory reset
Flash CM12.1 stable
Reboot and go through the setup wizard steps, wifi should work, log into your wifi
Reboot to recovery
Flash CM13 nightly
Reboot
Now wifi should work in CM13. Seems to be something it carries over from CM12.1 that's needed.
Click to expand...
Click to collapse
Its still the same. Waiting for a fix
same here with my Swipe Konnect Pro.
Hello there! I do own a Swipe Konnect Pro [MT6582] I' m a very experienced porter. And i ve flashed more than 120+ custom roms on my SKP [without any single bug], and almost many roms on various devices incl. MT6582, MT6572 and others. And even on crappy crapdragon chipsets. Anyways, the bugs i always get while flashing a CM13 roms are 1. WiFi doesn't turn on! 2. BT doesn't turn on! 3. WiFi mac address shows dummy 02:00:00:00:00:00:00 Please sort it out palz.. Thanks in regards.
how to fix this issue? i am having the same problem in my moto g
after dirty flashing from cm13 20161022 nightly to 20161028, i have got this problem too. so my moto g is now dead?
[solved] as next post...
poran123 said:
how to fix this issue? i am having the same problem in my moto g
Click to expand...
Click to collapse
have you got this fixed?
i hope you have got TWRP back up and you did backup /persist folder.
WiFi and BT hardware address are ruined because /persist folder is gone. You need to restore it. However, TWRP cannot restore /persist folder though it formats this folder anyway.
Solution:
Get presist.ext4.win from backup, use WinZip to extract all files and folders inside persist.ext4.win
Use USB connection to copy all to Moto G's Download folder.
Use Root Explorer to copy all back to /persist
If you don't have backup of /persist folder, then your original WiFi and BT hardware address have gone. There is a workaround: http://forum.xda-developers.com/showthread.php?t=2619553
Hope this helps.
hi all i compiled cm for my device (galaxy a5). Now I'm stucking at bootantimation. Anyone knows how to fix system server crash?
I recently created a shim for libsensorservice coz i gor dlopen failed to locate sysmol "symbol"......
USEFUL LOGS:
Logcat restricted
Code:
--------- beginning of crash
01-02 02:14:35.000 1115 1115 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1115 (system_server)
01-02 02:14:35.025 1327 1327 E : debuggerd: Unable to connect to activity manager (connect failed: No such file or directory)
01-02 02:14:35.076 1327 1327 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-02 02:14:35.076 1327 1327 F DEBUG : CM Version: '14.0-20161002-UNOFFICIAL-a5ultexx'
01-02 02:14:35.076 1327 1327 F DEBUG : Build fingerprint: 'samsung/a5ultexx/unknown:7.0/NRD90U/4dbc0adedb:userdebug/test-keys'
01-02 02:14:35.076 1327 1327 F DEBUG : Revision: '2'
01-02 02:14:35.076 1327 1327 F DEBUG : ABI: 'arm'
01-02 02:14:35.076 1327 1327 F DEBUG : pid: 1115, tid: 1115, name: system_server >>> system_server <<<
01-02 02:14:35.076 1327 1327 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-02 02:14:35.076 1327 1327 F DEBUG : r0 00000000 r1 00000000 r2 00000000 r3 00000000
01-02 02:14:35.076 1327 1327 F DEBUG : r4 bee13b28 r5 9c453c04 r6 00000000 r7 00000000
01-02 02:14:35.076 1327 1327 F DEBUG : r8 bee13ae0 r9 9c453c04 sl 9c453c94 fp 9c453cdc
01-02 02:14:35.076 1327 1327 F DEBUG : ip b2c32d88 sp bee13aa8 lr b44ca9b9 pc b44ca0d2 cpsr 600f0030
01-02 02:14:35.081 1327 1327 F DEBUG :
01-02 02:14:35.081 1327 1327 F DEBUG : backtrace:
01-02 02:14:35.081 1327 1327 F DEBUG : #00 pc 0000c0d2 /system/lib/libutils.so (_ZNK7android12SharedBuffer7releaseEj+1)
01-02 02:14:35.081 1327 1327 F DEBUG : #01 pc 0000c9b5 /system/lib/libutils.so (_ZN7android7String85setToERKS0_+28)
01-02 02:14:35.081 1327 1327 F DEBUG : #02 pc 00009453 /system/lib/libsensorservice.so
01-02 02:14:35.081 1327 1327 F DEBUG : #03 pc 0000957d /system/lib/libsensorservice.so
01-02 02:14:35.081 1327 1327 F DEBUG : #04 pc 000084db /system/lib/libsensorservice.so
01-02 02:14:35.081 1327 1327 F DEBUG : #05 pc 0000bc0b /system/lib/libsensorservice.so
01-02 02:14:35.081 1327 1327 F DEBUG : #06 pc 0001acf7 /system/lib/libandroid_servers.so
01-02 02:14:35.081 1327 1327 F DEBUG : #07 pc 0001ac85 /system/lib/libandroid_servers.so
01-02 02:14:35.081 1327 1327 F DEBUG : #08 pc 00c8dd7d /data/dalvik-cache/arm/[email protected]@[email protected] (offset 0xbec000)
01-02 02:14:35.741 381 381 E : eof
01-02 02:14:35.741 381 381 E : failed to read size
01-02 02:14:36.437 365 365 E Zygote : Exit zygote because system server (1115) has terminated
01-02 02:14:36.651 1341 1341 E : Failed to open libdatactrl, some features may not be present.
01-02 02:14:36.811 1334 1334 E QCOM PowerHAL: Unable to open prefetcher: dlopen failed: library "libqti-iop-client.so" not found
01-02 02:14:36.811 1334 1334 E QCOM PowerHAL: Failed to get prefetcher handle.
Full logcat: http://pastebin.com/Kp0hky9g
Thanks in advance
anyone?
I Have Successfully Ported MIUI 8 From Galaxy S4 Exynos Variant 32bit
Started building from source instead
Bugs Need to be fixed
Code:
--------- beginning of crash
01-05 20:11:42.003 2664 2664 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2664 (main)
01-05 20:11:42.004 2438 2438 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
01-05 20:11:42.004 2438 2438 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
01-05 20:11:42.004 2438 2438 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
01-05 20:11:42.054 2438 2438 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-05 20:11:42.054 2438 2438 F DEBUG : CM Version: 'unknown'
01-05 20:11:42.054 2438 2438 F DEBUG : Build fingerprint: 'samsung/aicp_ha3g/ha3g:6.0.1/M4B30X/3c24405d17:userdebug/test-keys'
01-05 20:11:42.054 2438 2438 F DEBUG : Revision: '0'
01-05 20:11:42.055 2438 2438 F DEBUG : ABI: 'arm'
01-05 20:11:42.055 2438 2438 F DEBUG : pid: 2664, tid: 2664, name: main >>> /system/bin/dex2oat <<<
01-05 20:11:42.055 2438 2438 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-05 20:11:42.063 2438 2438 F DEBUG : Abort message: 'art/compiler/oat_writer.cc:627] java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack trace available'
01-05 20:11:42.063 2438 2438 F DEBUG : r0 00000000 r1 00000a68 r2 00000006 r3 00000000
01-05 20:11:42.063 2438 2438 F DEBUG : r4 b6f6ab88 r5 00000006 r6 b6f6ab38 r7 0000010c
01-05 20:11:42.063 2438 2438 F DEBUG : r8 b6bf1d22 r9 bef67bb9 sl b6bf1d29 fp b6bf1d2b
01-05 20:11:42.063 2438 2438 F DEBUG : ip 00000000 sp bef67b10 lr b6763255 pc b67659b8 cpsr 20070010
01-05 20:11:42.096 2438 2438 F DEBUG :
01-05 20:11:42.096 2438 2438 F DEBUG : backtrace:
01-05 20:11:42.096 2438 2438 F DEBUG : #00 pc 0004a9b8 /system/lib/libc.so (tgkill+12)
01-05 20:11:42.096 2438 2438 F DEBUG : #01 pc 00048251 /system/lib/libc.so (pthread_kill+36)
01-05 20:11:42.096 2438 2438 F DEBUG : #02 pc 0001bfcb /system/lib/libc.so (raise+10)
01-05 20:11:42.096 2438 2438 F DEBUG : #03 pc 00018875 /system/lib/libc.so (__libc_android_abort+36)
01-05 20:11:42.096 2438 2438 F DEBUG : #04 pc 0001650c /system/lib/libc.so (abort+4)
01-05 20:11:42.096 2438 2438 F DEBUG : #05 pc 002a154f /system/lib/libart.so (_ZN3art7Runtime5AbortEv+274)
01-05 20:11:42.096 2438 2438 F DEBUG : #06 pc 0008f749 /system/lib/libart.so (_ZN3art10LogMessageD2Ev+872)
01-05 20:11:42.096 2438 2438 F DEBUG : #07 pc 0008c1f3 /system/lib/libart.so (_ZN3art7BarrierD2Ev+366)
01-05 20:11:42.096 2438 2438 F DEBUG : #08 pc 002c671f /system/lib/libart.so (_ZN3art10ThreadList4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+194)
01-05 20:11:42.097 2438 2438 F DEBUG : #09 pc 002abd67 /system/lib/libart.so (_ZNK3art10AbortState4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+314)
01-05 20:11:42.097 2438 2438 F DEBUG : #10 pc 002a14a3 /system/lib/libart.so (_ZN3art7Runtime5AbortEv+102)
01-05 20:11:42.097 2438 2438 F DEBUG : #11 pc 0008f749 /system/lib/libart.so (_ZN3art10LogMessageD2Ev+872)
01-05 20:11:42.097 2438 2438 F DEBUG : #12 pc 00288a33 /system/lib/libart-compiler.so
01-05 20:11:42.097 2438 2438 F DEBUG : #13 pc 00284ff3 /system/lib/libart-compiler.so (_ZN3art9OatWriter15VisitDexMethodsEPNS0_16DexMethodVisitorE+254)
01-05 20:11:42.097 2438 2438 F DEBUG : #14 pc 00284c8d /system/lib/libart-compiler.so (_ZN3art9OatWriter19InitOatCodeDexFilesEj+240)
01-05 20:11:42.097 2438 2438 F DEBUG : #15 pc 00283d15 /system/lib/libart-compiler.so (_ZN3art9OatWriterC2ERKNSt3__16vectorIPKNS_7DexFileENS1_9allocatorIS5_EEEEjjiPKNS_14CompilerDriverEPNS_11ImageWriterEPNS_12TimingLoggerEPNS_7SafeMapINS1_12basic_stringIcNS1_11char_traitsIcEENS6_IcEEEESN_NS1_4lessISN_EENS_17TrackingAllocatorINS1_4pairIKSN_SN_EELNS_12AllocatorTagE6EEEEE+468)
01-05 20:11:42.097 2438 2438 F DEBUG : #16 pc 00011be5 /system/bin/dex2oat
01-05 20:11:42.097 2438 2438 F DEBUG : #17 pc 00007033 /system/bin/dex2oat (main+2026)
01-05 20:11:42.097 2438 2438 F DEBUG : #18 pc 00016335 /system/lib/libc.so (__libc_init+52)
01-05 20:11:42.097 2438 2438 F DEBUG : #19 pc 00006770 /system/bin/dex2oat
01-05 20:11:42.175 2664 2664 W main : type=1701 audit(0.0:136): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel reason="memory violation" sig=6
01-05 20:11:42.178 2438 2438 F DEBUG :
01-05 20:11:42.178 2438 2438 F DEBUG : Tombstone written to: /data/tombstones/tombstone_00
01-05 20:11:42.224 2453 2453 E art : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Failed to generate image '/data/dalvik-cache/arm/[email protected]@boot.art': Failed execv(/system/bin/dex2oat --image=/data/dalvik-cache/arm/[email protected]@boot.art --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/org.apache.http.legacy.boot.jar --dex-file=/system/framework/org.dirtyunicorns.utils.jar --dex-file=/system/framework/patchrom-core.jar --dex-file=/system/app/miui/miui.apk --dex-file=/system/app/miuisystem/miuisys
01-05 20:11:43.887 2453 2453 D ICU : No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
01-05 20:11:44.137 2453 2453 I Radio-JNI: register_android_hardware_Radio DONE
01-05 20:11:44.220 2453 2453 I SamplingProfilerIntegration: Profiling disabled.
01-05 20:11:44.222 2453 2453 D Zygote : begin preload
01-05 20:11:44.224 2453 2453 I Zygote : Preloading classes...
01-05 20:11:45.197 2453 2453 E Minikin : addFont failed to create font /system/fonts/NanumGothic.ttf
01-05 20:11:45.199 2453 2453 E Minikin : addFont failed to create font /system/fonts/DroidSansFallback.ttf
01-05 20:11:45.199 2453 2453 E Minikin : addFont failed to create font /system/fonts/MTLmr3m.ttf
01-05 20:11:45.412 2453 2453 V DngCreator_JNI: DngCreator_nativeClassInit:
01-05 20:11:46.827 2453 2453 I art : Thread[1,tid=2453,Native,Thread*=0xb4c74400,peer=0x12e5be20,"main"] recursive attempt to load library "/system/lib/libmedia_jni.so"
01-05 20:11:46.827 2453 2453 D MtpDeviceJNI: register_android_mtp_MtpDevice
01-05 20:11:46.828 2453 2453 I art : Thread[1,tid=2453,Native,Thread*=0xb4c74400,peer=0x12e5be20,"main"] recursive attempt to load library "/system/lib/libmedia_jni.so"
01-05 20:11:46.829 2453 2453 I art : Thread[1,tid=2453,Native,Thread*=0xb4c74400,peer=0x12e5be20,"main"] recursive attempt to load library "/system/lib/libmedia_jni.so"
01-05 20:11:47.779 2453 2453 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-05 20:11:48.391 2453 2453 I System : Loaded time zone names for "" in 32ms (27ms in ICU)
01-05 20:11:48.451 2453 2453 I System : Loaded time zone names for "en_US" in 60ms (18ms in ICU)
01-05 20:11:48.845 2453 2453 I Zygote : ...preloaded 3863 classes in 4621ms.
01-05 20:11:48.845 2453 2453 I art : VMRuntime.preloadDexCaches starting
01-05 20:11:48.913 2453 2453 I art : VMRuntime.preloadDexCaches strings total=317779 before=10521 after=10521
01-05 20:11:48.913 2453 2453 I art : VMRuntime.preloadDexCaches types total=28582 before=9344 after=13243
01-05 20:11:48.913 2453 2453 I art : VMRuntime.preloadDexCaches fields total=125182 before=38077 after=51510
01-05 20:11:48.913 2453 2453 I art : VMRuntime.preloadDexCaches methods total=214853 before=71519 after=88232
01-05 20:11:48.913 2453 2453 I art : VMRuntime.preloadDexCaches finished
01-05 20:11:48.945 2941 2941 D idmap : error: no read access to /vendor/overlay: No such file or directory
01-05 20:11:49.003 2453 2453 I Zygote : Preloading resources...
01-05 20:11:49.157 2453 2453 W Resources: Preloaded drawable resource #0x1080096 (android:drawable/toast_frame) that varies with configuration!!
01-05 20:11:49.202 2453 2453 I Zygote : ...preloaded 86 resources in 199ms.
01-05 20:11:49.202 2453 2453 I Zygote : ...preloaded 0 resources in 0ms.
01-05 20:11:49.234 2453 2453 D libEGL : loaded /vendor/lib/egl/libGLES_mali.so
01-05 20:11:49.243 2453 2453 I Zygote : Preloading shared libraries...
01-05 20:11:49.258 2453 2453 D Zygote : end preload
01-05 20:11:49.258 2453 2453 I art : Starting a blocking GC Explicit
01-05 20:11:49.269 2453 2453 I art : Explicit concurrent mark sweep GC freed 1010(49KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 13MB/22MB, paused 100us total 11.220ms
01-05 20:11:49.273 2453 2453 I art : Starting a blocking GC Explicit
01-05 20:11:49.283 2453 2453 I art : Explicit concurrent mark sweep GC freed 388(15KB) AllocSpace objects, 1(28KB) LOS objects, 39% free, 13MB/22MB, paused 97us total 10.547ms
01-05 20:11:49.285 2453 2940 I art : Starting a blocking GC HeapTrim
01-05 20:11:49.286 2453 2453 I art : Starting a blocking GC Background
01-05 20:11:49.379 2453 2453 I Zygote : System server process 2942 has been created
01-05 20:11:49.383 2453 2453 I Zygote : Accepting command socket connections
01-05 20:11:49.390 2942 2942 I InstallerConnection: connecting...
01-05 20:11:49.391 2442 2442 I installd: new connection
01-05 20:11:49.419 2953 2953 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.419 2953 2953 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.421 2953 2953 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.425 2953 2953 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.425 2953 2953 E dex2oat : Failed to create runtime
01-05 20:11:49.426 2953 2953 I dex2oat : dex2oat took 8.203ms (threads: 4)
01-05 20:11:49.429 2442 2442 E installd: DexInv: --- END '/system/framework/org.cyanogenmod.platform.jar' --- status=0x0100, process failed
01-05 20:11:49.469 2955 2955 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.470 2955 2955 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.472 2955 2955 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.479 2955 2955 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.479 2955 2955 E dex2oat : Failed to create runtime
01-05 20:11:49.481 2955 2955 I dex2oat : dex2oat took 12.580ms (threads: 4)
01-05 20:11:49.484 2442 2442 E installd: DexInv: --- END '/system/framework/org.cyanogenmod.hardware.jar' --- status=0x0100, process failed
01-05 20:11:49.524 2957 2957 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.525 2957 2957 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.528 2957 2957 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.538 2957 2957 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.538 2957 2957 E dex2oat : Failed to create runtime
01-05 20:11:49.541 2957 2957 I dex2oat : dex2oat took 17.213ms (threads: 4)
01-05 20:11:49.545 2442 2442 E installd: DexInv: --- END '/system/framework/services.jar' --- status=0x0100, process failed
01-05 20:11:49.609 2959 2959 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.610 2959 2959 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.615 2959 2959 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.623 2959 2959 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.624 2959 2959 E dex2oat : Failed to create runtime
01-05 20:11:49.627 2959 2959 I dex2oat : dex2oat took 18.721ms (threads: 4)
01-05 20:11:49.631 2442 2442 E installd: DexInv: --- END '/system/framework/ethernet-service.jar' --- status=0x0100, process failed
01-05 20:11:49.700 2961 2961 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.701 2961 2961 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.706 2961 2961 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.716 2961 2961 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.716 2961 2961 E dex2oat : Failed to create runtime
01-05 20:11:49.719 2961 2961 I dex2oat : dex2oat took 19.602ms (threads: 4)
01-05 20:11:49.723 2442 2442 E installd: DexInv: --- END '/system/framework/wifi-service.jar' --- status=0x0100, process failed
01-05 20:11:49.786 2963 2963 I dex2oat : Adjusted thread count (for runtime dex2oat): 4, 4
01-05 20:11:49.788 2963 2963 I dex2oat : /system/bin/dex2oat --compiler-filter=speed
01-05 20:11:49.793 2963 2963 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Only the zygote can create the global boot image.
01-05 20:11:49.801 2963 2963 E dex2oat : Dex file fallback disabled, cannot continue without image.
01-05 20:11:49.802 2963 2963 E dex2oat : Failed to create runtime
01-05 20:11:49.805 2963 2963 I dex2oat : dex2oat took 19.133ms (threads: 4)
01-05 20:11:49.809 2442 2442 E installd: DexInv: --- END '/system/framework/patchrom-server.jar' --- status=0x0100, process failed
01-05 20:11:49.810 2942 2942 I InstallerConnection: disconnecting...
01-05 20:11:49.811 2442 2442 E installd: eof
01-05 20:11:49.811 2442 2442 E installd: failed to read size
01-05 20:11:49.811 2442 2442 I installd: closing connection
01-05 20:11:49.813 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:49.882 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:49.888 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:50.355 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:50.357 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:50.456 2942 2942 W art : No image location found for Dex2Oat.
01-05 20:11:50.508 2942 2942 I SystemServer: Entered the Android system server!
01-05 20:11:50.561 2942 2942 I SystemServiceManager: Starting com.android.server.pm.Installer
01-05 20:11:50.564 2942 2942 I Installer: Waiting for installd to be ready.
01-05 20:11:50.564 2942 2942 I InstallerConnection: connecting...
01-05 20:11:50.564 2442 2442 I installd: new connection
01-05 20:11:50.564 2942 2942 I SystemServiceManager: Starting com.android.server.am.ActivityManagerService$Lifecycle
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.708 2942 2942 I ActivityManager: choosing minFree values for 32 Bit
01-05 20:11:50.721 2942 2942 I ActivityManager: Memory class: 288
01-05 20:11:50.836 2942 2942 D BatteryStatsImpl: Reading daily items from /data/system/batterystats-daily.xml
01-05 20:11:50.879 2942 2942 I AppOps : No existing app ops /data/system/appops.xml; starting empty
01-05 20:11:50.958 2942 2942 I IntentFirewall: Read new rules (A:0 B:0 S:0)
01-05 20:11:51.004 2942 2942 I FeatureParser: can't find ha3g.xml in assets/device_features/,it may be in /system/etc/device_features
01-05 20:11:51.009 2942 2942 D AppOps : AppOpsService published
01-05 20:11:51.010 2942 2942 I SystemServiceManager: Starting com.android.server.power.PowerManagerService
So in Need For Help to fix those bugs then the rom will be released immediately and This Rom is based on AICP by tincho5588
XDA:DevDB Information
MIUI 8 Port, ROM for the Samsung Galaxy Note 3
Contributors
omarilzz, tincho5588
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-12-24
Last Updated 2016-12-24
Very thanks
Reserved
When your rom uploaded?
tnx for port rom. android LP or MM ?
ok i found this ( i dont know about port or fix bug , just find it with google , sorry if not help you i dont know a lot of Port and build Custom rom ) :
1- SystemUi Carsh : wrong permissions
2- Clear Cache and Dalvik Cache
maybe help :
http://forum.xda-developers.com/showthread.php?t=2759479
http://www.zopomobile.com/forum/thread-439-1-1.html
Mohamad313 said:
Very thanks
Reserved
When your rom uploaded?
Click to expand...
Click to collapse
after i fix those 2 bugs
rasoulia said:
tnx for port rom. android LP or MM ?
ok i found this ( i dont know about port or fix bug , just find it with google , sorry if not help you i dont know a lot of Port and build Custom rom ) :
1- SystemUi Carsh : wrong permissions
2- Clear Cache and Dalvik Cache
maybe help :
http://forum.xda-developers.com/showthread.php?t=2759479
http://www.zopomobile.com/forum/thread-439-1-1.html
Click to expand...
Click to collapse
my rom is 6.0.x MM
Screen shot please
Mohamad313 said:
Screen shot please
Click to expand...
Click to collapse
i cant mate it reboots directly after booting and showing force close
Ok we waiting
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
look at this i think u forgot sth to do
and i have question , we had miui 5 which fully worked with air command is it possible to add aircommand to this rom ?
Kernel LOG
@tincho5588 @deadman96385
Miui 8 is One step a head i posed a log from kernel to fix random reboot and the three apps FC
So Help please
RYAN SHAY said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
look at this i think u forgot sth to do
and i have question , we had miui 5 which fully worked with air command is it possible to add aircommand to this rom ?
Click to expand...
Click to collapse
i Will add all u want but i want to fix the kernel reboot issue and force close first so we can at least have a booted rom and i used this already while porting XD
RYAN SHAY said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
look at this i think u forgot sth to do
and i have question , we had miui 5 which fully worked with air command is it possible to add aircommand to this rom ?
Click to expand...
Click to collapse
It will be almost impossible to add aircommand to this ROM since it's not based on TW ROM
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
Thanks a lot mate for your work I hope this will be our Christmas gift
Alexjudge999 said:
It will be almost impossible to add aircommand to this ROM since it's not based on TW ROM
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
Thanks a lot mate for your work I hope this will be our Christmas gift
Click to expand...
Click to collapse
nothing is impossible and yes merry Christmas
It's for N9005? and this custom have multilanguage?
beepoff15 said:
It's for N9005? and this custom have multilanguage?
Click to expand...
Click to collapse
No. Its for exynos version
Sent from my SM-N900 using XDA-Developers mobile app
beepoff15 said:
It's for N9005? and this custom have multilanguage?
Click to expand...
Click to collapse
It's for SM-N900 but there is already a MIUI 8 ROM for SM-N9005
@omarilzz When will it come Miui v8. Waiting impatiently please send me pleaaaaassseee i said im waiting and we waiting
what the point of spending time port crappy ios ripped off os to beautiful great aicp
better if import features from oneplus phones or motorolla
Abandoned War Place said:
what the point of spending time port crappy ios ripped off os to beautiful great aicp
better if import features from oneplus phones or motorolla
Click to expand...
Click to collapse
If you think that the MIUI is just a copy paste from IOS then you know nothing about it
lordondi said:
@omarilzz When will it come Miui v8. Waiting impatiently please send me pleaaaaassseee i said im waiting and we waiting
Click to expand...
Click to collapse
if god wills it the rom will be bugless ^^ but the problem that all apps crash when rom boots and i cant find any dev to help i messaged them all and no help so am stuck at no point the rom boots but all apps crash and self reboots
Hi All,
I have recently (as in the past three or four days) have noticed my pixel 2 is crashing. I will be in the middle of anything really - watching a youtube video, last time I was preparing to log into a skype meeting... first the screen brightness increases to maximum and the system in unresponsive, then a moment later I am kicked out to the lock screen and I will need to re-enter my password (instead of just fingerprint scanning) because it thinks I have just power cycled my phone. I downloaded the logcat and had a look through it:
Code:
~/Desktop$ adb logcat > logcat.txt
^C
~/Desktop$ grep "Build fingerprint" logcat.txt
12-09 09:53:19.394 4247 4247 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 11:43:20.845 17233 17233 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 13:30:49.843 27809 27809 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 15:16:55.320 6546 6546 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 16:20:28.016 16032 16032 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 17:52:01.305 27423 27423 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 18:15:46.459 4530 4530 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 21:01:27.411 19212 19212 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 22:08:47.234 29161 29161 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 23:25:52.732 5523 5523 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 00:38:09.041 16731 16731 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 10:57:36.963 16230 16230 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 11:34:07.681 32519 32519 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 12:53:14.116 17878 17878 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 15:59:41.529 4502 4502 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
There was 15 crash reports, all of them looking *very* similar to this one:
Code:
12-10 12:53:14.021 32534 17875 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x702df0eaea in tid 17875 (netd), pid 32534 (Binder:32534_2)
12-10 12:53:14.116 17878 17878 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-10 12:53:14.116 17878 17878 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 12:53:14.116 17878 17878 F DEBUG : Revision: 'MP1'
12-10 12:53:14.116 17878 17878 F DEBUG : ABI: 'arm64'
12-10 12:53:14.116 17878 17878 F DEBUG : pid: 32534, tid: 17875, name: netd >>> /system/bin/netd <<<
12-10 12:53:14.116 17878 17878 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x702df0eaea
12-10 12:53:14.116 17878 17878 F DEBUG : x0 000000702e873904 x1 000000702df0eaea x2 000000000000007e x3 000000702e873900
12-10 12:53:14.116 17878 17878 F DEBUG : x4 000000702df0eb68 x5 000000702e873982 x6 0000000000000000 x7 0000000000000000
12-10 12:53:14.116 17878 17878 F DEBUG : x8 000000702df0eb68 x9 0000000000000004 x10 000000702e873900 x11 00000000ffffffff
12-10 12:53:14.116 17878 17878 F DEBUG : x12 000000702f594418 x13 0000000000000000 x14 000000702f400000 x15 0000000000000000
12-10 12:53:14.116 17878 17878 F DEBUG : x16 000000646dc47420 x17 00000070afae1b70 x18 00000070afbbf000 x19 000000702e830180
12-10 12:53:14.116 17878 17878 F DEBUG : x20 000000702de133f8 x21 000000702e873900 x22 000000702de13588 x23 000000702df0eb68
12-10 12:53:14.116 17878 17878 F DEBUG : x24 000000702df0eaea x25 0000000000000005 x26 000000702df11588 x27 000000646dc14930
12-10 12:53:14.116 17878 17878 F DEBUG : x28 000000702e80fdc0 x29 000000702de133d0
12-10 12:53:14.116 17878 17878 F DEBUG : sp 000000702de13380 lr 000000646dc14564 pc 00000070afae1c58
12-10 12:53:14.132 17878 17878 F DEBUG :
12-10 12:53:14.132 17878 17878 F DEBUG : backtrace:
12-10 12:53:14.132 17878 17878 F DEBUG : #00 pc 000000000001dc58 /system/lib64/libc.so (memcpy+232)
12-10 12:53:14.132 17878 17878 F DEBUG : #01 pc 000000000006c560 /system/bin/netd (android::net::DnsTlsSocket::sendQuery(android::net::DnsTlsSocket::Query const&)+192)
12-10 12:53:14.133 17878 17878 F DEBUG : #02 pc 000000000006c0fc /system/bin/netd (android::net::DnsTlsSocket::loop()+308)
12-10 12:53:14.133 17878 17878 F DEBUG : #03 pc 000000000006c96c /system/bin/netd
12-10 12:53:14.133 17878 17878 F DEBUG : #04 pc 0000000000083114 /system/lib64/libc.so (__pthread_start(void*)+36)
12-10 12:53:14.133 17878 17878 F DEBUG : #05 pc 00000000000233bc /system/lib64/libc.so (__start_thread+68)
Looking at this I see that all of the backtraces end at libc.so (in memcpy). I assume that the crash is actually in /system/bin/netd because it seems much more likely than an crash originating in libc... I do have all my apps/updates installed/up to date and this is a new issue for me. I have had this phone for over a year now and have not had any issues such as this in the past...
I am wondering if anyone has seen this problem before? Solutions? Is this a new bug that may have come in a recent system update?
Thanks for your attention
Anyone seen this before?
How about advise on how I should proceed?
Sent from my Pixel 2 using Tapatalk
eanema said:
Anyone seen this before?
How about advise on how I should proceed?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Found this while Googling for my same issue. Pixel 2 XL with the latest December update, rooted with Magisk, running Nova Launcher and the same symptoms. It seems to happen more and more (had the phone for 2 weeks only!). It can happen while streaming Spotify or just having it in my pocket. If it crashes in my pocket the screen is unlocked and on the launcher, where my icons start moving around in my pocket or I dial someone by accident.
Build fingerprint: google/taimen/taimen etc etc. fault addr... (netd), pid 11785.
Well, it seems that there is at least one other person who is experiencing this issue.
I should also mention that I am not using a rooted phone, and it is up to date. Hopefully I will have some time to investigate this further... But it sounds like an issue with core OS software. Biggest problem is that I'm not certain how to debug this problem. Any advise would be good. I am a Linux developer, but not an Android developer...
Sent from my Pixel 2 using Tapatalk
I'm neither, but funnily enough after crashing all day yesterday it hasn't crashed once today. No reboot, no uninstall or anything. Same spotify and bluetooth etc.
I have made some progress. So after downloading some more of my log I read past the crash report until there was a break in the time record, and noticed what happened after:
12-27 11:48:02.756 19158 11278 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x758af06aea in tid 11278 (netd), pid 19158 (Binder:19158_2)
12-27 11:48:02.870 11282 11282 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-27 11:48:02.870 11282 11282 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181205.002/5086253:user/release-keys'
12-27 11:48:02.870 11282 11282 F DEBUG : Revision: 'MP1'
12-27 11:48:02.870 11282 11282 F DEBUG : ABI: 'arm64'
12-27 11:48:02.870 11282 11282 F DEBUG : pid: 19158, tid: 11278, name: netd >>> /system/bin/netd <<<
12-27 11:48:02.870 11282 11282 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x758af06aea
12-27 11:48:02.870 11282 11282 F DEBUG : x0 000000758c080684 x1 000000758af06aea x2 000000000000007e x3 000000758c080680
12-27 11:48:02.870 11282 11282 F DEBUG : x4 000000758af06b68 x5 000000758c080702 x6 0000000000000000 x7 0000000000000000
12-27 11:48:02.870 11282 11282 F DEBUG : x8 000000758af06b68 x9 0000000000000004 x10 000000758c080680 x11 00000000ffffffff
12-27 11:48:02.870 11282 11282 F DEBUG : x12 000000758c1f2c18 x13 0000000000000000 x14 00000000000000e4 x15 0000000000000000
12-27 11:48:02.870 11282 11282 F DEBUG : x16 0000005804039420 x17 000000760cb9fb70 x18 000000760cc7d000 x19 000000758c068c80
12-27 11:48:02.870 11282 11282 F DEBUG : x20 000000758ae0b3f8 x21 000000758c080680 x22 000000758ae0b588 x23 000000758af06b68
12-27 11:48:02.870 11282 11282 F DEBUG : x24 000000758af06aea x25 0000000000000005 x26 000000758af09588 x27 0000005804006930
12-27 11:48:02.870 11282 11282 F DEBUG : x28 000000758c0f2e00 x29 000000758ae0b3d0
12-27 11:48:02.870 11282 11282 F DEBUG : sp 000000758ae0b380 lr 0000005804006564 pc 000000760cb9fc58
12-27 11:48:02.886 11282 11282 F DEBUG :
12-27 11:48:02.886 11282 11282 F DEBUG : backtrace:
12-27 11:48:02.886 11282 11282 F DEBUG : #00 pc 000000000001dc58 /system/lib64/libc.so (memcpy+232)
12-27 11:48:02.886 11282 11282 F DEBUG : #01 pc 000000000006c560 /system/bin/netd (android::net:nsTlsSocket::sendQuery(android::net:nsTlsSocket::Query const&)+192)
12-27 11:48:02.886 11282 11282 F DEBUG : #02 pc 000000000006c0fc /system/bin/netd (android::net:nsTlsSocket::loop()+308)
12-27 11:48:02.886 11282 11282 F DEBUG : #03 pc 000000000006c96c /system/bin/netd
12-27 11:48:02.886 11282 11282 F DEBUG : #04 pc 0000000000083194 /system/lib64/libc.so (__pthread_start(void*)+36)
12-27 11:48:02.886 11282 11282 F DEBUG : #05 pc 00000000000233bc /system/lib64/libc.so (__start_thread+68)
12-27 11:48:02.957 19244 19441 W NativeCrashListener: Couldn't find ProcessRecord for pid 19158
12-27 11:48:02.977 19244 19377 E mDnsConnector: got -1 reading with start = 0
12-27 11:48:02.978 19244 19364 E NetdConnector: got -1 reading with start = 0
12-27 11:48:02.978 19244 19364 E NetdConnector: closing stream for netd
12-27 11:48:02.978 19244 19377 E mDnsConnector: closing stream for mdns
12-27 11:48:02.979 19244 19364 I NetworkManagement: onDaemonConnected()
12-27 11:48:02.979 19244 19364 E NetdConnector: Communications error: java.io.IOException: Connection reset by peer
12-27 11:48:02.979 19244 19364 E NetdConnector: closing stream for netd
12-27 11:48:02.980 19244 19364 E NetdConnector: Error in NativeDaemonConnector: java.io.IOException: Connection reset by peer
12-27 11:48:02.980 19244 19377 E mDnsConnector: Communications error: java.io.IOException: Connection refused
12-27 11:48:02.981 19244 19377 E mDnsConnector: Error in NativeDaemonConnector: java.io.IOException: Connection refused
12-27 11:48:02.990 19244 19263 I BootReceiver: Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
Click to expand...
Click to collapse
I found this in the "--------- beginning of system" section, I assume that means that the crash was fresh enough to still remain in context of the system log, not the crash log... anyways, the last line there says that the tombstone was copied to DropBox, so I am guessing that this whole problem might be due to my recent installation of DropBox? Really not sure, but I have uninstalled it and I'll see if I still experience crashing.
I sure would like to be able to get a copy of that tombstone file. I might end up rooting my phone just to get a copy of it... kinda stupid that you need root on your phone to download a Tombstone file.
Had nothing to do with DropBox... It has crashed twice since my last post, both with the same crash in netd
Same issue here after updating to Dec patch.
Rooted, pulled the tombstone file... Makes no sense to me. Hope it helps.
OK well I'm glad we are both seeing the same sort of issues. Thanks for the tombstone file, it didn't give me anymore information unfortunately. Google code is all closed source so I can't assume that the source for netd is the same as pure android/android.org.
I have created a thread on google's product forums. Hopefully someone from google will notice it and report it to the developers
https://productforums.google.com/forum/#!topic/phone-by-google/utccQUTgVrA;context-place=forum/phone-by-google
We shall see how this unfolds. Maybe I will just install LiniageOS on my phone if it doesn't get fixed soon...
I contacted google's support line and they walked me through submitting a bug report. Details are posted on the google forums link above.
I face the same issue even with Nov updates.
eanema said:
Anyone seen this before?
How about advise on how I should proceed?
Click to expand...
Click to collapse
Remove the private DNS entries it should fix the issue
Interesting, thank you for the response @jegavelan, much appreciated! At least others have found & reported this problem too.
I have been using Ad Guard for a very long time, I hadn't even considered that that was the problem. Well, I should not say that is the problem, but it is triggering a new bug in netd...
https://www.reddit.com/r/GooglePixe...uard_officially_releases_its_own_dns_service/
People have reported it on January 1/2/3
https://issuetracker.google.com/issues/122277459
https://issuetracker.google.com/issues/122141885
So, new question: issuetracker.google.com? Is this where google wants their bugs reported to?
jegavelan said:
Remove the private DNS entries it should fix the issue
Click to expand...
Click to collapse
I came back to update and say that my phone is crashing constantly again, and I suspect either my network monitor notification (also in the logs) or possibly the privateDNS option that I set to adguard.
On my LAN my dhcp server hands out a local and then recursive to adguard, so i'm going to turn off privatedns in the settings and see how that goes!
So 29 hours later, no crashes... which has happened before, but i'm feeling optimistic!
another 24 hours and NO CRASHES at all! I'm going to add a thanks to jegavelan's post. Cheers!
The January OTA update has been out for a few days now. I just installed it. Has anyone seen netd crash with this new patch installed? I have no idea what all is included in the new patch, the bulletin doesn't have a whole lot of info...
Well, it didn't take more than an hour and my phone crashed again. Maybe next month...
jegavelan said:
Remove the private DNS entries it should fix the issue
Click to expand...
Click to collapse
Fixed for me :good:
This is a Google software issue rather than the DNS server? Possible fix in Feb patch?
The adguard DNS server saved me from installing an extra app.
Yes, this is definitely a problem in google's core OS software. The fact is, it doesn't matter if the DNS server responded with terrible profanity instead of the IP address of the server you were looking for, netd should not crash...
Ya, ad guard is a good service. I use it on my wifi router in the house so I don't have to do it on every device. I have been dealing with the crashes as a reminder that it's broken, rather than removing the ad guard DNS servers from my router
Sent from my Pixel 2 using Tapatalk
Hello Folks,
My camera app has started crashing and will not start.
force quit and try again
clear app cache and try again
clear cache, restart phone and try again
clear cache, restart phone in safe mode and try again
TWRP Recovery, clear all cache, restart and try again
Here are a few lines from an adb logcat...
Code:
--------- beginning of crash
03-13 22:19:53.877 7993 7993 E AndroidRuntime: FATAL EXCEPTION: main
03-13 22:19:53.877 7993 7993 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 7993
03-13 22:19:53.877 7993 7993 E AndroidRuntime: java.lang.NullPointerException: Attempt to read from field 'java.lang.String kvs.a' on a null object reference
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at kvq.a(PG:34)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at fur.a(PG:10)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at fur.b(PG:14)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at czu.run(PG:9)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at iai.run(Unknown Source:2)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at kdg.run(PG:3)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
03-13 22:19:53.877 7993 7993 E AndroidRuntime: at kcd.run(PG:6)
...
03-14 10:19:56.706 3176 3478 I CameraManagerGlobal: Connecting to camera service
03-14 10:19:56.708 3176 3478 E CameraManagerGlobal: Camera service is unavailable
...
03-14 10:20:01.801 2300 24651 W ServiceManager: Service media.camera didn't start. Returning NULL
...
03-14 03:08:32.799 17827 17827 F DEBUG : pid: 17768, tid: 17768, name: android.hardwar >>> /vendor/bin/hw/[email protected] <<<
03-14 03:08:32.799 17827 17827 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xf4db7184
03-14 03:08:32.800 17827 17827 F DEBUG : r0 000000ff r1 f4db717c r2 00000003 r3 ed262000
03-14 03:08:32.800 17827 17827 F DEBUG : r4 0007ffff r5 f490de80 r6 ed262000 r7 00000058
03-14 03:08:32.800 17827 17827 F DEBUG : r8 ed200000 r9 ed201f1c r10 ed201f1c r11 00000230
03-14 03:08:32.800 17827 17827 F DEBUG : ip 499d81e0 sp ffad8898 lr 000006f9 pc f4d6e114
03-14 03:08:32.818 17827 17827 F DEBUG :
03-14 03:08:32.818 17827 17827 F DEBUG : backtrace:
03-14 03:08:32.818 17827 17827 F DEBUG : #00 pc 00069114 /system/lib/libc.so (arena_dalloc_bin_locked_impl+132)
03-14 03:08:32.818 17827 17827 F DEBUG : #01 pc 00069089 /system/lib/libc.so (je_arena_dalloc_bin_junked_locked+12)
03-14 03:08:32.818 17827 17827 F DEBUG : #02 pc 00087b99 /system/lib/libc.so (je_tcache_bin_flush_small+248)
03-14 03:08:32.818 17827 17827 F DEBUG : #03 pc 0007cfd1 /system/lib/libc.so (ifree+536)
03-14 03:08:32.819 17827 17827 F DEBUG : #04 pc 0007d247 /system/lib/libc.so (je_free+70)
03-14 03:08:32.819 17827 17827 F DEBUG : #05 pc 00009c65 /system/lib/vndk-sp-28/libutils.so (android::SharedBuffer::release(unsigned int) const+24)
03-14 03:08:32.819 17827 17827 F DEBUG : #06 pc 0000a36d /system/lib/vndk-sp-28/libutils.so (android::String8::~String8()+14)
03-14 03:08:32.819 17827 17827 F DEBUG : #07 pc 00065701 /system/lib/libc.so (__cxa_finalize+132)
03-14 03:08:32.819 17827 17827 F DEBUG : #08 pc 0001827b /system/lib/libc.so (exit+10)
03-14 03:08:32.819 17827 17827 F DEBUG : #09 pc 0008aebf /system/lib/libc.so (__libc_init+50)
03-14 03:08:32.819 17827 17827 F DEBUG : #10 pc 00000b2b /vendor/bin/hw/[email protected] (_start_main+38)
03-14 03:08:32.819 17827 17827 F DEBUG : #11 pc 00000306 <anonymous:f54f5000>
I have submitted a few feedbacks to Google on the app crash pop-up.
Hope someone can help.
Paully
Google Pixel (sailfish)
Android 9 BUILD PQ2A.190205.003
Camera app version 6.1.021.220943556
Did you try any 3rd party camera apps?
Donz7733 said:
Did you try any 3rd party camera apps?
Click to expand...
Click to collapse
Yes, Open Camera... which just stays on a black screen and freezes.
I have just flashed the latest Google stock Pixel image March 2019 and the camera is still broken.