Related
Is there a way to determine if the GPad I have is with the problematic camera module?
Out of the box, my gpad had 4.2.2, and prompted me to update to 4.4.2(v50020b).
How do I know if I will/will not have a nonfunctional back camera when I flash AOSP or CM, before actually flashing?
Sagaraut said:
Is there a way to determine if the GPad I have is with the problematic camera module?
Out of the box, my gpad had 4.2.2, and prompted me to update to 4.4.2(v50020b).
How do I know if I will/will not have a nonfunctional back camera when I flash AOSP or CM, before actually flashing?
Click to expand...
Click to collapse
When you type "dmesg", these are the names of the camera modules that work.
Main cam: s5k4e5ya
Front cam: imx119
Note: the name of the camera module that does not work is "ov5663".
Code:
[ 2.707977 / 01-01 00:00:02.691] usbcore: registered new interface driver uvcvideo
[ 2.708251 / 01-01 00:00:02.691] USB Video Class driver (1.1.1)
[ 2.710266 / 01-01 00:00:02.691] s5k4e5ya module init !!!
[ 2.710479 / 01-01 00:00:02.691] s5k4e5ya_sensor_i2c_probe: enter
[ 2.710906 / 01-01 00:00:02.691] msm_sensor_power_up : E sensor name is s5k4e5ya
[ 2.711212 / 01-01 00:00:02.691] msm_sensor_power_up : lgcam_commit on 121230
[ 2.711517 / 01-01 00:00:02.691] msm_sensor_power_up : lgcam_commit increase JPEG_ENC] on 130113 [
[ 2.711791 / 01-01 00:00:02.691] msm_sensor_power_up : lgcam_commit fix AF kernel crash on 130121 [
[ 2.765716 / 01-01 00:00:02.751] msm_sensor_power_up : mclk: 24000000Hz
[ 2.770965 / 01-01 00:00:02.751] msm_sensor_power_up : X sensor name is s5k4e5ya
[ 2.771179 / 01-01 00:00:02.751] msm_sensor_match_id: E
[ 2.771697 / 01-01 00:00:02.751] msm_sensor_i2c_probe s5k4e5ya probe succeeded
[ 2.816101 / 01-01 00:00:02.801] msm_server_update_sensor_info mctl_node_name[0] = video1
[ 2.816589 / 01-01 00:00:02.801] msm_sensor_power_down : E sensor name is s5k4e5ya
[ 2.817321 / 01-01 00:00:02.801] [CAM/I] msm_sensor_power_down: Revision [11] MSM_MAINCAM_RST_EN GPIO No.178
[ 2.819732 / 01-01 00:00:02.801] msm_sensor_power_down : X sensor name is s5k4e5ya
[ 2.820190 / 01-01 00:00:02.801] imx119_sensor_power_up: before request gpio, sensor name : imx119
[ 2.826477 / 01-01 00:00:02.811] imx119_sensor_power_up : X sensor name is imx119
[ 2.826782 / 01-01 00:00:02.811] msm_sensor_match_id: E
[ 2.827514 / 01-01 00:00:02.811] msm_sensor_i2c_probe imx119 probe succeeded
[ 2.827697 / 01-01 00:00:02.811] msm_eeprom_probe probe_fail
[ 2.828552 / 01-01 00:00:02.811] msm_server_update_sensor_info mctl_node_name[1] = video3
[ 2.829040 / 01-01 00:00:02.811] imx119_sensor_power_down
[ 2.829223 / 01-01 00:00:02.811] imx119_sensor_power_down : E sensor name is imx119
[ 2.830047 / 01-01 00:00:02.811] [CAM/I] imx119_sensor_power_down: Revision [11] MSM_CAM2_RST_EN GPIO No.179
[ 2.833190 / 01-01 00:00:02.811] imx119_sensor_power_down : X sensor name is imx119
[ 2.835021 / 01-01 00:00:02.811] msm_cam_server_request_irq IRQ Router hw is not present.
[
And in order to run dmesg through adb shell, I'll need to be rooted, right?
Yes
Code:
6>[ 1.272521 / 01-01 00:00:01.260] IR MCE Keyboard/mouse protocol handler initialized
<6>[ 1.272521 / 01-01 00:00:01.260] IR LIRC bridge handler initialized
<6>[ 1.272949 / 01-01 00:00:01.260] usbcore: registered new interface driver uvcvideo
<6>[ 1.272979 / 01-01 00:00:01.260] USB Video Class driver (1.1.1)
<3>[ 1.273284 / 01-01 00:00:01.260] msm_cam_i2c_mux msm_cam_i2c_mux.0: drv probe_log s
<3>[ 1.273315 / 01-01 00:00:01.260] msm_cam_i2c_mux msm_cam_i2c_mux.0: drv probe_log e
<3>[ 1.273651 / 01-01 00:00:01.260] msm_cam_server msm_cam_server.0: drv probe_log s
<3>[ 1.274169 / 01-01 00:00:01.260] msm_cam_server msm_cam_server.0: drv probe_log e
<3>[ 1.274291 / 01-01 00:00:01.260] s5k4e5ya module init !!!
<3>[ 1.274383 / 01-01 00:00:01.260] s5k4e5ya 4-0020: bus probe_log s
<3>[ 1.274383 / 01-01 00:00:01.260] s5k4e5ya_sensor_i2c_probe: enter
<3>[ 1.274414 / 01-01 00:00:01.260] msm_sensor_power_up : E sensor name is s5k4e5ya
<3>[ 1.274414 / 01-01 00:00:01.260] msm_sensor_power_up : lgcam_commit on 121230
<3>[ 1.274444 / 01-01 00:00:01.260] msm_sensor_power_up : lgcam_commit increase JPEG_ENC] on 130113 [
<3>[ 1.274475 / 01-01 00:00:01.260] msm_sensor_power_up : lgcam_commit fix AF kernel crash on 130121 [
<3>[ 1.327606 / 01-01 00:00:01.320] msm_sensor_power_up : mclk: 24000000Hz
<3>[ 1.332702 / 01-01 00:00:01.320] msm_sensor_power_up : X sensor name is s5k4e5ya
<3>[ 1.332733 / 01-01 00:00:01.320] msm_sensor_match_id: E
<3>[ 1.333160 / 01-01 00:00:01.320] msm_sensor_i2c_probe s5k4e5ya probe succeeded
<3>[ 1.333312 / 01-01 00:00:01.320] msm_actuator 4-0018: bus probe_log s
<3>[ 1.333312 / 01-01 00:00:01.320] msm_actuator 4-0018: bus probe_log e
<3>[ 1.333465 / 01-01 00:00:01.320] s5k4e5ya_eeprom 4-0028: bus probe_log s
<3>[ 1.376495 / 01-01 00:00:01.360] s5k4e5ya_eeprom 4-0028: bus probe_log e
<6>[ 1.376831 / 01-01 00:00:01.360] msm_server_update_sensor_info mctl_node_name[0] = video1
<3>[ 1.376983 / 01-01 00:00:01.360] msm_sensor_power_down : E sensor name is s5k4e5ya
<0>[ 1.377441 / 01-01 00:00:01.360] [CAM/I] msm_sensor_power_down: Revision [11] MSM_MAINCAM_RST_EN GPIO No.178
<3>[ 1.379119 / 01-01 00:00:01.370] msm_sensor_power_down : X sensor name is s5k4e5ya
<3>[ 1.379150 / 01-01 00:00:01.370] s5k4e5ya 4-0020: bus probe_log e
<3>[ 1.379241 / 01-01 00:00:01.370] ov5693 module init !!!
<3>[ 1.379302 / 01-01 00:00:01.370] ov5693 4-0040: bus probe_log s
<3>[ 1.379302 / 01-01 00:00:01.370] msm_sensor_power_up : E sensor name is ov5693
<3>[ 1.379333 / 01-01 00:00:01.370] msm_sensor_power_up : lgcam_commit on 121230
<3>[ 1.379364 / 01-01 00:00:01.370] msm_sensor_power_up : lgcam_commit increase JPEG_ENC] on 130113 [
<3>[ 1.379364 / 01-01 00:00:01.370] msm_sensor_power_up : lgcam_commit fix AF kernel crash on 130121 [
<3>[ 1.437591 / 01-01 00:00:01.430] msm_sensor_power_up : mclk: 24000000Hz
<3>[ 1.442718 / 01-01 00:00:01.430] msm_sensor_power_up : X sensor name is ov5693
<3>[ 1.442749 / 01-01 00:00:01.430] msm_sensor_match_id: E
<3>[ 1.443145 / 01-01 00:00:01.430] msm_sensor_match_id chip id doesnot match
<3>[ 1.443145 / 01-01 00:00:01.430] msm_sensor_i2c_probe ov5693_i2c_probe failed
<3>[ 1.443176 / 01-01 00:00:01.430] msm_sensor_power_down : E sensor name is ov5693
What's the verdict here?
You will need to install Terminal Emulator and give it root access in order to get "su" permissions to type "dmesg".
The log in my last post in this conversation was my dmesg output. It seems that I have both, s5k4e5ya as well as ov5693 modules. And I can confirm that my back camera works because I installed AOSP 5.0.1 today, and both the cameras are functional. Strange, no?
Sorry, I didn't see the log you posted.
Edit: The people without AOSP camera support have the ov5693. It doesn't matter if you have other camera modules also.
s5k4e5ya_i2c_probe failed
Deltadroid said:
Sorry, I didn't see the log you posted.
Hmm, ov5663 is known not to work, but yours is ov5693. Although, as long as you have s5k4e5ya, then it should be ok. The people without AOSP camera support don't have s5k4e5ya at all.
Click to expand...
Click to collapse
What if I have s5k4e5ya and it does not work?
I looked at the dmesg and found that it says, msm_sensor_i2c_probe: s5k4e5ya_i2c_probe failed
The main thing is if you have the ov5693. I made a mistake before thinking there was a ov5663. There is no ov5663.
---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------
Read this thread.
http://forum.xda-developers.com/showthread.php?t=3004451
Deltadroid said:
The main thing is if you have the ov5693. I made a mistake before thinking there was a ov5663. There is no ov5663.
---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------
Read this thread.
http://forum.xda-developers.com/showthread.php?t=3004451
Click to expand...
Click to collapse
ov5693 does not show up in mine. The dmesg only shows s5k4e5ya and says probe failed. I checked and apparently that's the supported driver, still doesn't work. I don't really know why :|, and now after I flashed the zip in the link you provided, I don't see any.
I restarted my gpad and i get this
Code:
PS C:\> adb shell dmesg |grep s5k4e5ya
<3>[ 1.885101 / 01-01 00:00:01.870] s5k4e5ya module init !!!
<3>[ 1.885192 / 01-01 00:00:01.870] s5k4e5ya_sensor_i2c_probe: enter
<3>[ 1.885345 / 01-01 00:00:01.870] msm_sensor_power_up : E sensor name is s5k4e5ya
<3>[ 1.948547 / 01-01 00:00:01.930] msm_sensor_power_up : X sensor name is s5k4e5ya
<3>[ 1.949584 / 01-01 00:00:01.930] msm_sensor_i2c_probe: s5k4e5ya_i2c_probe failed
<3>[ 1.949859 / 01-01 00:00:01.930] msm_sensor_power_down : E sensor name is s5k4e5ya
<3>[ 1.952880 / 01-01 00:00:01.930] msm_sensor_power_down : X sensor name is s5k4e5ya
PS C:\> ov5693
PS C:\> adb shell dmesg |grep ov5693
Maybe you could look through the entire log just to see if there is something else.
Deltadroid said:
Maybe you could look through the entire log just to see if there is something else.
Click to expand...
Click to collapse
Ok, did that and found something else:
Code:
<3>[ 1.924499 / 01-01 00:00:01.910] s5k4e5ya module init !!!
<3>[ 1.924591 / 01-01 00:00:01.910] s5k4e5ya_sensor_i2c_probe: enter
<3>[ 1.924743 / 01-01 00:00:01.910] msm_sensor_power_up : E sensor name is s5k4e5ya
<3>[ 1.924865 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit on 121230
<3>[ 1.924926 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit increase JPEG_ENC] on 130113 [
<3>[ 1.925018 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit fix AF kernel crash on 130121 [
<3>[ 1.982757 / 01-01 00:00:01.970] msm_sensor_power_up : mclk: 24000000Hz
<3>[ 1.988189 / 01-01 00:00:01.970] msm_sensor_power_up : X sensor name is s5k4e5ya
<3>[ 1.988342 / 01-01 00:00:01.970] msm_sensor_match_id: E
<3>[ 1.989074 / 01-01 00:00:01.970] msm_sensor_match_id chip id doesnot match
<3>[ 1.989227 / 01-01 00:00:01.970] msm_sensor_i2c_probe: s5k4e5ya_i2c_probe failed
so it says, the chip id doesnot match? so umm... does this mean I have the other chip? However, when I look at dmesg, I don't get the other chip as well. How can I find the name of the chip for sure?
saurjk said:
Ok, did that and found something else:
Code:
<3>[ 1.924499 / 01-01 00:00:01.910] s5k4e5ya module init !!!
<3>[ 1.924591 / 01-01 00:00:01.910] s5k4e5ya_sensor_i2c_probe: enter
<3>[ 1.924743 / 01-01 00:00:01.910] msm_sensor_power_up : E sensor name is s5k4e5ya
<3>[ 1.924865 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit on 121230
<3>[ 1.924926 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit increase JPEG_ENC] on 130113 [
<3>[ 1.925018 / 01-01 00:00:01.910] msm_sensor_power_up : lgcam_commit fix AF kernel crash on 130121 [
<3>[ 1.982757 / 01-01 00:00:01.970] msm_sensor_power_up : mclk: 24000000Hz
<3>[ 1.988189 / 01-01 00:00:01.970] msm_sensor_power_up : X sensor name is s5k4e5ya
<3>[ 1.988342 / 01-01 00:00:01.970] msm_sensor_match_id: E
<3>[ 1.989074 / 01-01 00:00:01.970] msm_sensor_match_id chip id doesnot match
<3>[ 1.989227 / 01-01 00:00:01.970] msm_sensor_i2c_probe: s5k4e5ya_i2c_probe failed
so it says, the chip id doesnot match? so umm... does this mean I have the other chip? However, when I look at dmesg, I don't get the other chip as well. How can I find the name of the chip for sure?
Click to expand...
Click to collapse
I think that your device has the unsupported camera module but your kernel is not detecting it properly. Ckret mentioned that he will work on fixing the other camera driver when he gets time from school. I would mark that other thread with the camera fix and give ckret some time to look at it. It seems like ckret knows what's wrong and what needs to be changed.
Deltadroid said:
I think that your device has the unsupported camera module but your kernel is not detecting it properly. Ckret mentioned that he will work on fixing the other camera driver when he gets time from school. I would mark that other thread with the camera fix and give ckret some time to look at it. It seems like ckret knows what's wrong and what needs to be changed.
Click to expand...
Click to collapse
alright, i have already subscribed to that thread, so I will just wait. The camera is not really important on the tablet, but still . Thanks again
Hello.
I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web.
Sometimes it happens that the smartphone freezes and I have to reboot by unplugging the battery. The "asdb logcat" log is attached (XXXX was http). How can I avoid this? Thanks.
01-17 04:00:45.572 502 520 D Tethering: MasterInitialState.processMessage what=3
01-17 04:00:45.579 502 623 D ConnectivityService: notifyType PRECHECK for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Got connectivity change, has connection: true
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Scheduling future, repeating update checks.
01-17 04:00:45.586 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: connectivity change: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: receiver: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.597 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: Checking XXXXXconnectivitycheck.gstatic.com/generate_204 on "FUSION", connectivitycheck.gstatic.com=216.58.205.163,2a00:1450:4002:80a::2003
01-17 04:00:45.598 502 5952 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.603 2842 2915 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.637 1596 2106 I PinnedContentDownloader: Started downloading pinned content.
01-17 04:00:45.639 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 phoneId=0
01-17 04:00:45.640 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 retVal=false
01-17 04:00:45.641 502 515 D TelephonyManager: getDataEnabled: retVal=false
01-17 04:00:45.655 1596 1596 I iu.Environment: update connectivity state; isNetworkMetered? false, isRoaming? false, isBackgroundDataAllowed? true*
01-17 04:00:45.659 1086 2304 D TelephonyProvider: getPreferredApnIdFromApn: for subId 1
01-17 04:00:45.660 1086 2304 D TelephonyProvider: Preferred APN: -1
01-17 04:00:45.664 502 5953 D NetlinkSocketObserver: NeighborEvent{elapsedMs=31948177, 192.168.0.254, [A491B129B92C], RTM_NEWNEIGH, NUD_REACHABLE}
01-17 04:00:45.670 4897 4897 D WeatherUpdateService: onCreate
01-17 04:00:45.678 4897 4897 D WeatherUpdateService: Service started, but shouldn't update ... stopping
01-17 04:00:45.681 4897 4897 D WeatherUpdateService: onDestroy
01-17 04:00:45.686 502 515 E GpsLocationProvider: No APN found to select.
01-17 04:00:45.695 1596 2106 I PinnedContentDownloader: Finished downloading pinned content.
01-17 04:00:45.697 1596 1690 I iu.UploadsManager: num queued entries: 0
01-17 04:00:45.699 1596 1690 I iu.UploadsManager: num updated entries: 0
01-17 04:00:45.700 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: isCaptivePortal: ret=204 headers={null=[HTTP/1.1 204 No Content], Content-Length=[0], Date=[Wed, 17 Jan 2018 03:00:46 GMT], X-Android-Received-Millis=[1516158045699], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1516158045648]}
01-17 04:00:45.701 502 623 D ConnectivityService: setProvNotificationVisibleIntent null visible=false networkType=MOBILE extraInfo=null highPriority=false
01-17 04:00:45.701 502 623 D ConnectivityService: NetworkAgentInfo [WIFI () - 124] validation passed
01-17 04:00:45.702 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.706 502 623 D ConnectivityService: sendStickyBroadcast: action=android.net.conn.INET_CONDITION_ACTION
01-17 04:00:45.712 1596 1690 I iu.SyncManager: NEXT; no task
01-17 04:00:46.116 502 621 D IpReachabilityMonitor: watch: iface{wlan0/11}, v{4}, ntable=[192.168.0.1/NUD_REACHABLE, 192.168.0.254/NUD_REACHABLE]
01-17 04:00:46.117 502 623 D ConnectivityService: Adding Route [fd2c:81a5:7139::/64 -> :: wlan0] to network 124
01-17 04:00:46.139 502 623 D ConnectivityService: notifyType IP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:46.202 1596 2106 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:46.567 502 623 D ConnectivityService: NetTransition Wakelock (NetworkAgentInfo [WIFI () - 123] cleared because we found a replacement network
01-17 04:00:46.692 2842 5345 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:53.442 502 623 D ConnectivityService: handlePromptUnvalidated 124
mimu88 said:
Hello. I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3312784
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Porting] CANNOT LINK EXECUTABLE < /system/bin/ file>: cannot locate symbol < ... >
Hi.
I encountered a problem while trying to port AOSP Extended v. 4.1 (Android 7.1.2, kernel 3.10.65+, MTK 6753) on my device (VOYO Q101, 2GB/32GB, kernel 3.10.65+, MTK 6753).
After successfully started the booting process (after one week of research, and a stupid line in /system/build.prop: ro.setupwizard.enterprise_mode=1 which caused stucking at logo), I have managed to get a logcat via adb. LOG (it's 8MB)
It is booting.. and booting... forever. It is not stucked, nor bootlooping. It is just booting (the "Google dots" animations running forever).
I have attached the log. There are a lot of CANNOT LINK EXECUTABLE <....> cannot locate symbol < ... > referenced by <...> and also a lot of:
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Write 56 bytes to slot 0, CCCI_H(0x0)(0x38)(0x801D000F)(0x0)
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from FS device
01-01 02:05:46.410 1451 1451 D ccci_fsd(1): Read 128 bytes from slot 0, CCCI_H(0x0)(0x80)(0x801E000E)(0x0)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): CMPT File name:Z:/NVRAM/NVD_DATA/ULMH_000 opid_map:0x00000013 Flag:0x00000100 Offset:34 Whence:-229154332 Length:16384
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): O: [1010103F282D2C35](0x00000100): (7 1)
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): F: 1: 1906 0
01-01 02:05:46.411 1451 1451 D ccci_fsd(1): C: 1: 0
[What I did]
- just copying the kernel from stock ROM (tried also: stock kernel + stock ueventd.rc +/- stock fstab): all caused bootloop or even stucked at logo. Just kernel change works good (at least till the actual stage) .
- compared with old .rc files. No replaces needed (in my opinion)
- From system/build.prop file I have DELETED all lines from ADDITIONAL_BUILD_PROPERTIES section (especially ro.setupwizard.enterprise_mode=1) - which took me 4 DAYS !!! to understand why it was stucked at logo .
- tried with and without patching with init.d (from porting ROM's website)
- tried to put the stock binaries mentioned in errors <CANNOT LINK ...> (/system/bin/mtk_agpsd, xlog) - not booting at all (it even stucks at logo...). Should I try with stock linker.so lib(64) ? But I think it will not boot at all (It really can't).
I hope for your help . Thanks!
up
I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
ada12 and me made a Telegram group for mi a2 lite developing, who wants to join can pm me or ada12.
I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog
It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.
reujea0 said:
It is clear from the log that there is an issue with gnss(Global Navigation Satellite System). SO location won't most likely work, for the time being try to disable/remove everything related to gnss, this should let you at least boot or go further in the boot process. I will investigate further.
---------- Post added at 05:35 PM ---------- Previous post was at 05:18 PM ----------
I think we might have to patchelf https://github.com/NixOS/patchelf to replace the dependencieng, like this https://github.com/LineageOS/androi...mmit/369faf695b355d1d341a09082272ef25d3ad3e7a . I don't really have the time, but try to patchelf this with some of the values in the logcat.
Click to expand...
Click to collapse
Whoa, thanks a lot i already have an idea on how to fix gnss and i will try to patch elf when i have time (tomorrow or so)
mac12m99 said:
I've never compiled for a treble device but as i know vendor tree is useless because all needed blobs are in vendor partition, you shouldn't take things from stock system.
In fact GSI works at 100% with only vendor libraries (ok, code is patched but that's not the point).
I think we should target GSI instead, researching and giving fixes for roms that have litte issues and compiling new ones (also for the joy of others device's owners).
If you don't think so please explain why, i'm open to dialog
Click to expand...
Click to collapse
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .
wertus33333 said:
Yes, you are right, all blobs needed for a gsi are in vendor partition. Many of those blobs are however, not needed or can be compiled open source with customisations like improved battery life/performance and an open source code.
Click to expand...
Click to collapse
Ok, i got it,
so you are trying to create a ROM that don't use vendor partition and have all needed blobs into /system?
wertus33333 said:
Also, to add new features which our hardware supports but xiaomi did not build into they'r software for license or other reasons, we need a completely source built kernel and an adapted rom. Additionally, a properly built and optimized rom with as much open source code as possible and improved from a ****load of developers around the world will always perform better than an overlay rom depending on features built from oem and therefore optimized for theyr stock rom.
Click to expand...
Click to collapse
Which features do you mean?
As i know all hardware features have to be implemented in kernel (like dt2w and fingerprint gestures) and all software features have to be implemented in ROM (like long press for flashlight, dt2s in statustbar ecc..).
Am i wrong?
wertus33333 said:
Also, you need files from system for a proper full vendor because you need some configuration files for the rom itself to adapt to the vendor blobs. Sometimes you can also fix a gsi by copying the right file (look logcat) from stock system to the gsi system partition .
Click to expand...
Click to collapse
This happens when OEM forgot to move something vendor, as i know .
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but i think it could be built.
mac12m99 said:
EDIT: looking at your logcat i found this:
Code:
F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
This is a fatal issue and probably the cause of bootloop, copying libaudiopolicymanagerdefault.so from stock may help but I think it could be built.
Click to expand...
Click to collapse
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.
reujea0 said:
I saw this one as well in the logcat, I do agree that it seems like it can't find the audioserver file, which would probably cause no audio. But I do not think that it causes the bootloop, not only can most roms cope with not finding some executables, but also it is not the one coming up forever towards the end of the logcat. This is an error it does not try to fix, in the logcat, the rom is trying to start the GPS over and over, which makes it bootloop, stuck at the omni logo. We either have to kill it in the boot.rc files temporarily to boot or to find a way to fix it.
Click to expand...
Click to collapse
Ok i got it, i hope you succeed
log interpretation
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
wertus33333 said:
I need help Building omnirom9.0 for daisy, got it to compile and boot (bootlooping bootanimation, logs can be found below) but need help in interpreting the logs.
Sources:
Kernel mi kernel with disabled verity and FEC
Devie combined msm8953-common and daisy (branch los15) from lineage build and adjusted to omni
Vendor took vendor from v10.0.1.0.PDLMIFJ, added everything to copy files, adjusted with apps and missing files from system and deleted the obsolete
OMNIROM
Logcat
Saw that some libraries are missing, will search them in vendor/system from stock and add them when i have time. If someone finds a solution for an error please copy&paste the line(s) in logcat leading to the solution, so me (and probably others) can learn from it and be of more use next time.
@ada12
@reujea0
@Hakkinan
Click to expand...
Click to collapse
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug
Thanks for the answer, last time i could not find the v10.0.2.0 vendor anywhere but if it is officially avaiable now i'll defenitely switch.
A telegram group would defenitely be of help and easier to communicate than here. More people reviewing/contributing to the code on github (i don't always really know what i am doing ) would also be useful (i'd be happy to add more people, just pm me if u want to).
I dont have that much time for continuing with the rom in the next 1-2 weeks but i'll defenitely continue as soon as possible.
ada12 said:
the interpretation is need globally to fix vendor error and issue with gnss(Global Navigation Satellite System). the source is no good .
I think the solution to speak regularry in work omni rom daisy , is create group Mi a2 lite dev in Telegram app . For exemple group telegram for Redmi note 5a( my secondary device ), have many help dev and good community .
you can see error here for your logcat :
1-08 15:44:04.528 463 463 E DrmLibFs: Error: Invalid config file
01-08 15:44:04.528 463 463 E DrmLibFs: Data path not parsed: Using default data path: /data/vendor/tzstorage/
01-08 15:44:04.528 463 463 E DrmLibFs: Persist path not parsed: Using default persist path: /mnt/vendor/persist/data/
01-08 15:44:04.740 479 479 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
01-08 15:44:04.750 479 483 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare /data/system/users/0: No such file or directory
01-08 15:44:04.750 479 483 E vold : Failed to prepare user 0 storage
01-08 15:44:05.583 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IHealth/default in either framework or device manifest.
1-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter64.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 D QSEECOMAPI: QSEECom_get_handle sb_length = 0xa000
01-08 15:44:05.703 570 570 D QSEECOMAPI: App is not loaded in QSEE
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/soter.mdt errno = 2
01-08 15:44:05.703 570 570 E QSEECOMAPI: Error::Loading image failed with ret = -1
01-08 15:44:05.703 570 570 E SoterUtils: QSEECom_start_app failed
01-08 15:44:05.704 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IGnss/default in either framework or device manifest.
01-08 15:44:45.509 708 708 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:44:50.519 718 718 W [email protected]: Failed to register IGnss 1.1 service: 1, try IGnss 1.0
01-08 15:45:05.518 729 729 E [email protected]: Could not get passthrough implementation for [email protected]::IVr/default.
01-08 15:45:15.550 751 751 E [email protected]: Error while registering gnss vendor hal service: 1
01-08 15:45:30.536 769 769 F linker : CANNOT LINK EXECUTABLE "/system/bin/audioserver": library "libaudiopolicymanagerdefault.so" not found
01-08 15:45:30.542 451 451 W hwservicemanager: getTransport: Cannot find entry [email protected]::IVr/default in either framework or device manifest.
01-08 15:45:30.543 771 771 D vndksupport: Loading /vendor/lib64/hw/[email protected] from current namespace instead of sphal namespace.
01-08 15:45:30.544 771 771 E VrService: hw_get_module vr failed: -2
01-08 15:47:30.685 906 906 E [email protected]: Could not get passthrough implementation for [email protected]::ILocHidlGnss/gnss_vendor.
01-08 15:47:30.685 906 906 E [email protected]: Error while registering gnss vendor hal service: 1
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
+ I see Vendor took vendor from v10.0.1.0.PDLMIFJ , is a beta rom pie for Daisy . I recommand change to vendor from v10.0.2.0 + fix after in source the other bug
Click to expand...
Click to collapse
Hello,
I was wondering if there is a Lineage OS distribution for Lenovo Tab 11 Pro with the reference TB-J716F. If not, is it possible for me to build one? I'm a noob in custom ROMs, but I'm willing to learn
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
Thanks, I'll check all of that once I managed to get my tab working.........
Ungeskriptet said:
LinageOS doesn't specifically support this tablet. You can however flash a GSI (Generic System Image) since this tablet supports Project Treble with this guide. Make sure you have updated to the latest ZUI update before flashing the GSI.
Right now I'm using Andy Yan's LineageOS GSI builds, they work great on this tablet
The GSI used to have some annoying bugs but after the latest ZUI 14 update they got fixed.
I tried making a normal LineageOS port, but it's really hard and the build process always takes very long. The errors are hard to understand too
Click to expand...
Click to collapse
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11
redblood252 said:
I managed to install LineageOS. But I cannot install twrp using your image.
These are my logs:
Code:
01-01 08:33:29.842 0 0 I init : starting service 'recovery'...
01-01 08:33:29.847 756 756 F linker : CANNOT LINK EXECUTABLE "/system/bin/vendor.qti.hardware.vibrator.service": library "android.hardware.vibrator-V1-ndk_platform.so" not found: needed by main executable
01-01 08:33:29.847 0 0 I init : Service 'vendor.qti.vibrator' (pid 756) exited with status 1
01-01 08:33:29.847 0 0 I init : Sending signal 9 to service 'vendor.qti.vibrator' (pid 756) process group...
01-01 08:33:29.847 0 0 I libprocessgroup: Successfully killed process cgroup uid 0 pid 756 in 0ms
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
01-01 08:33:29.882 755 755 W libc : Unable to set property "ro.twrp.version" to "3.6.1_11-0": error code: 0xb
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.boot' from uid:0 gid:0 pid:755: Read-only property was already set
01-01 08:33:29.882 0 0 E init : Unable to set property 'ro.twrp.version' from uid:0 gid:0 pid:755: Read-only property was already setunsupported, phys idx 0
01-01 08:33:29.900 755 755 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x10 in tid 755 (recovery), pid 755 (recovery)
01-01 08:33:29.902 758 758 F libc : failed to exec crash_dump helper: No such file or directory
01-01 08:33:29.903 755 755 F libc : crash_dump helper failed to exec
01-01 08:33:29.908 0 0 I init : Service 'recovery' (pid 755) received signal 11
Click to expand...
Click to collapse
You shouldn't need TWRP.
mikefnz said:
You shouldn't need TWRP.
Click to expand...
Click to collapse
Why not? All I have is stock rom recovery....
redblood252 said:
Why not? All I have is stock rom recovery....
Click to expand...
Click to collapse
Just need adb & fastboot
For example:
Download vbmeta.img from google
Reboot to fastboot
Open an cmd:
fastboot flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot flash system XYZ.img
fastboot reboot recovery
Make an factory reset
Reboot