Related
Hi all,
I have a Verizon LG G4 running the new VS98628A update on Android 6.0, but am posting in the General G4 forum for better exposure and since I doubt the problem has anything to do with Verizon.
For the past two days, I have received constant toast notifications at the bottom of my screen that just say
Code:
* OK *
and I can't figure out what is causing it. No new apps have been installed.
I am also experiencing high battery drain, although I am not sure if it's related. The notifications persist after a reboot.
Has anyone else seen this before? Any ideas?
Hello!
I have the same exactly issue (even now that I am writing on)
Device is LG G4 H818
Perhaps you could try to disable NFC?
I don't use NFC and it has been disabled the entire time I've had the issue.
I'm not rooted, and I haven't been able to find an app like EnhancedToast to label the notifications with whatever app is causing them, and I haven't found any clues in the system logs.
Stock messages app? Settings, notifications, all the way at the bottom "Display message on screen", select whatever preference there that you want.
Mine ( Verizon HTC 10) just started doing this yesterday, changing that setting seems to have fixed it.
*Edit- NM, I am still getting it.
Logcat can help here
I've already checked the system logs and can't find any entries corresponding to the toast notifications. Is there anything else I should be looking for?
InsipidMonkey said:
I've already checked the system logs and can't find any entries corresponding to the toast notifications. Is there anything else I should be looking for?
Click to expand...
Click to collapse
First get adb running on your pc.
http://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424/post68249027
(check faq #3)
Exec this on your pc:
adb logcat > logcat.txt
Let it run while some of the ok message appeared and then use CTRL + C to abort.
You now have a file logcat.txt on your pc.
paste the whole content on http://paste.omnirom.org
Add the link here.
.
Ok, I ran logcat several times and found the following event associated with the toast notifications. Interestingly, the notification text has changed from the original "* OK *" to "*-OK-*" today.
12-19 10:02:44.190 1220 1234 D WindowManager: addWindowToListInOrderLocked: win=Window{c7f2ae u0 Toast} Callers=com.android.server.wm.WindowManagerService.addWindow:2615 com.android.server.wm.Session.addToDisplay:169 android.view.IWindowSession$Stub.onTransact:124 com.android.server.wm.Session.onTransact:131
12-19 10:02:44.190 1220 1234 V WindowManager: Free window: Adding window Window{c7f2ae u0 Toast} at 13 of 18
Click to expand...
Click to collapse
Any idea what this is or what's causing it?
Code:
12-19 10:02:44.087 3470 3470 I [SystemUI]NetworkController: Change in state from: connected=true,enabled=true,level=3,inetCondition=1,iconGroup=IconGroup(Default Wi-Fi Icons),activityIn=false,activityOut=false,rssi=-47,lastModified=12-19 10:02:39,ssid="***********"
12-19 10:02:44.087 3470 3470 I [SystemUI]NetworkController: to: connected=true,enabled=true,level=3,inetCondition=1,iconGroup=IconGroup(Default Wi-Fi Icons),activityIn=false,activityOut=true,rssi=-47,lastModified=12-19 10:02:39,ssid="**********"
12-19 10:02:44.161 438 1203 D BandwidthController: [LG DATA] No such appUid: 10226
12-19 10:02:44.161 438 1203 D DnsProxyListener: App 10226 tries DNS query. Accept family:0 protocol:0
12-19 10:02:44.169 21587 21619 D OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
[COLOR="Red"]12-19 10:02:44.190 1220 1234 D WindowManager: addWindowToListInOrderLocked: win=Window{c7f2ae u0 Toast} Callers=com.android.server.wm.WindowManagerService.addWindow:2615 com.android.server.wm.Session.addToDisplay:169 android.view.IWindowSession$Stub.onTransact:124 com.android.server.wm.Session.onTransact:131
12-19 10:02:44.190 1220 1234 V WindowManager: Free window: Adding window Window{c7f2ae u0 Toast} at 13 of 18[/COLOR]
12-19 10:02:44.297 1220 4273 V WindowManager: Looking for focus: 15 = Window{cc9d48f u0 StatusBar}, flags=-2122055608, canReceive=false
12-19 10:02:44.297 1220 4273 V WindowManager: findFocusedWindow: Found new focus @ 7 = Window{b5c17ff u0 com.google.android.googlequicksearchbox/com.google.android.apps.gsa.velour.dynamichosts.VelvetThemedDynamicHostActivity}
12-19 10:02:44.307 1220 4273 D PowerManagerServiceAO: acquireWakeLockInternal: lock=145297574, flags=0x2000000a, tag="WindowManager", ws=WorkSource{10226}, historyTag=null, uid=1000, pid=1220
12-19 10:02:44.307 1220 4273 D PocketDetection: updateScreenWakelockState: mScreenWakeLockList.add(SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE android (uid=1000, pid=1220, ws=WorkSource{10226}) uptime = 0)
12-19 10:02:44.307 1220 4273 D PocketDetection: updateScreenWakelockState: mScreenWakeLockList.add(SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE android (uid=1000, pid=1220, ws=WorkSource{10226}) uptime = 0), mIsScreenWakelockAcquired = true
12-19 10:02:44.313 21587 21619 I Adreno : QUALCOMM build : ac1ef73, I86756fd4a8
12-19 10:02:44.313 21587 21619 I Adreno : Build Date : 10/05/15
12-19 10:02:44.313 21587 21619 I Adreno : OpenGL ES Shader Compiler Version: XE031.06.00.00
12-19 10:02:44.313 21587 21619 I Adreno : Local Branch :
12-19 10:02:44.313 21587 21619 I Adreno : Remote Branch :
12-19 10:02:44.313 21587 21619 I Adreno : Remote Branch :
12-19 10:02:44.313 21587 21619 I Adreno : Reconstruct Branch :
12-19 10:02:44.319 21587 21619 I OpenGLRenderer: Initialized EGL, version 1.4
12-19 10:02:44.415 459 617 E ThermalEngine: [GPU_MON] Gpu Clock is back to idle state ( 600000000 Mhz )
12-19 10:02:44.415 459 617 E ThermalEngine: [GPU_MON] ACTION: GPU - [GPU_MON] Setting GPU[0] to 600000000
12-19 10:02:44.415 459 617 E ThermalEngine: ACTION: GPU - Setting max_pwrlevel to 0
12-19 10:02:44.471 21587 21620 I HOTLINE_SERVICE: Now Processing g
12-19 10:02:44.550 21587 21620 I HOTLINE : Processing Backlog : 5 p: 8192
12-19 10:02:44.574 21587 21620 I HOTLINE_SERVICE: Now Processing aa
12-19 10:02:44.627 21587 21620 I HOTLINE_SERVICE: Now Processing v
12-19 10:02:45.012 1220 3370 D InputDispatcher: notifyMotion - action=ACTION_DOWN(0), id=0, tooltype=1, deviceId=4, source=0x1002, policyFlags=0x0, flags=0x0, metaState=0x0, buttonState=0x0, edgeFlags=0x0, eventTime=213408382823000, downTime=213408382823000,
12-19 10:02:45.013 1220 3369 D InputTransport: channel 'b5c17ff com.google.android.googlequicksearchbox/com.google.android.apps.gsa.velour.dynamichosts.VelvetThemedDynamicHostActivity (server)' : action=ACTION_DOWN(0), id=0, tooltype=1, deviceId=4, source=0x1002, flags=0x2, edgeFlags=0x0, metaState=0x0, buttonState=0x0, downTime=213408382823000, eventTime=213408382823000, pointerCount=1
steadfasterX said:
You now have a file logcat.txt on your pc.
paste the whole content on http://paste.omnirom.org
Add the link here.
.
Click to expand...
Click to collapse
As said paste the whole file not a subset only.
As said do not paste it here but on a paste service like the one I mentioned.
So try again. Wait until the toast message appeared and just do this once:
adb logcat -d -b all > logcat.txt
Then follow the above steps to provide the log.
I tried but the paste was too large for omnirom or pastebin, so I just copied the relevant parts and a truncated version.
I have attached a zipped txt file of the full output of logcat -d -b all captured right after a toast notification. Please let me know if you need any other info.
Thank you for the help!
As an update: these notifications stopped showing up a few days ago. I assume an app update fixed the issue, but I still have not been able to narrow it down as several apps updated automatically.
InsipidMonkey said:
I tried but the paste was too large for omnirom or pastebin, so I just copied the relevant parts and a truncated version.
I have attached a zipped txt file of the full output of logcat -d -b all captured right after a toast notification. Please let me know if you need any other info.
Thank you for the help!
Click to expand...
Click to collapse
Hm I was able to check this from my smartphone only but I was not able to find a toast message in the log.. Strange. But when this is gone we cannot investigate further.. Let us know when this happens again.
Sent from my LG-H815 using XDA Labs
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
Hi,
i have unlocked bootloader and flashed official twrp, everything works, but i wanted to try some GSI so flashed havoc os 2.0 pie and got a bootloop with this error:
Code:
--------- beginning of system
04-16 11:44:38.751 596 596 I vold : Vold 3.0 (the awakening) firing up
04-16 11:44:38.752 596 596 V vold : Detected support for: exfat ext4 ntfs vfat
04-16 11:44:38.757 596 596 D vold : Tearing down stale mount /mnt/phh
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop3: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop0: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop7: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop1: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop6: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop4: No such device or address
04-16 11:44:38.758 596 596 W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop5: No such device or address
04-16 11:44:38.759 596 596 I vold : [libfs_mgr]dt_fstab: Skip disabled entry for partition system
04-16 11:44:38.762 596 596 D vold : VoldNativeService::start() completed OK
04-16 11:44:38.763 596 600 D vold : e4crypt_init_user0
04-16 11:44:38.764 596 600 D vold : e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 1
04-16 11:44:38.764 596 600 D vold : Preparing: /data/vendor_de
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/vendor_de): Read-only file system
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/vendor_de: Read-only file system
04-16 11:44:38.764 596 600 D vold : Preparing: /data/system/users/0
04-16 11:44:38.764 596 600 E cutils : Failed to mkdir(/data/system/users/0): No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare /data/system/users/0: No such file or directory
04-16 11:44:38.764 596 600 E vold : Failed to prepare user 0 storage
04-16 11:44:38.780 601 601 I /system/bin/tzdatacheck: timezone distro dir /data/misc/zoneinfo/current does not exist. No action required.
04-16 11:44:38.784 596 599 I vold : Found disk at /devices/soc/7864900.sdhci/mmc_host/mmc1/mmc1:aaaa/block/mmcblk1 but delaying scan due to secure keyguard
04-16 11:44:38.985 610 610 I BOOT : MSM target '', SoC 'QRD', HwID '293', SoC ver '65536'
04-16 11:44:38.998 611 611 W DRM_BOOT: file: '/sys/module/drm/parameters/vblankoffdelay' or perms doesn't exist
04-16 11:44:39.542 675 675 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
--------- beginning of crash
04-16 11:44:39.630 701 701 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
04-16 11:44:39.631 714 714 E getcolorid: tp info = 31373201d1533101
04-16 11:44:39.631 714 714 E getcolorid:
04-16 11:44:39.631 714 714 E getcolorid: colorid = 32
04-16 11:44:39.644 676 676 I [email protected]/: [email protected]/backup: Hal starting main loop...
04-16 11:44:39.645 676 676 I [email protected]/: [email protected]/backup Hal is starting up...
04-16 11:44:39.647 717 717 I lowmemorykiller: Using in-kernel low memory killer interface
04-16 11:44:39.652 676 676 W ServiceManagement: Can't efficiently wait for [email protected]::IHealth/default, because we are called from the only binder thread in this process.
04-16 11:44:39.659 707 707 I irsc_util: Starting irsc tool
04-16 11:44:39.660 708 708 I rmt_storage: Shared memory initialised successfully.
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst1: 0x4a /boot/modem_fs1
04-16 11:44:39.660 708 708 I rmt_storage: Registering modemst2: 0x4b /boot/modem_fs2
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsc: 0xff /boot/modem_fsc
04-16 11:44:39.660 708 708 I rmt_storage: Registering fsg: 0x58 /boot/modem_fsg
04-16 11:44:39.660 708 708 I rmt_storage: 4 GPT partitions found
04-16 11:44:39.661 708 708 I rmt_storage: Capset success!
04-16 11:44:39.666 707 707 I irsc_util: Num of entries:292
04-16 11:44:39.668 676 676 I ServiceManagement: getService: Trying again for [email protected]::IHealth/default...
04-16 11:44:39.668 707 707 I irsc_util: Ending irsc tool
04-16 11:44:39.669 676 676 W ServiceManagement: Waiting one second for [email protected]::IHealth/default
04-16 11:44:39.676 712 712 D PcbaConfigSet: Before, get, [ro.boot.hwversion=], [ro.boot.hwc=], [ro.boot.hwlevel=], [ro.product.cert=], [ro.product.name=treble_arm64_bvN]
Patched boot din't worked.
So, i reflashed with ./flash_all and tried again, flashing also magisk, this time asked me for password, hitted cancel and then selected factory reset.. stuck in twrp
Tried other combos with always flashing stock rom but nothing worked, every time i got bootscreen i get bootloop with the error above(tried also pixel experience, same issue).
This is my first device with treble so maybe i'm a bit noob, someone could help me?
Have you tried the GSI ROM posted in this forum? Also try to flash the stock ROM and see if you didn't broke something.
Does havok has A/B partition support?
SnoopDoggyStyleDogg said:
Have you tried the GSI ROM posted in this forum?
Click to expand...
Click to collapse
Yes, ive tried also pixel experience P because a thread said it's totally compatible.
SnoopDoggyStyleDogg said:
Also try to flash the stock ROM and see if you didn't broke something.
Click to expand...
Click to collapse
After doing exactly the same operation?
I've tried to switch slot(to the one that contain stock) but I got bootloop, so yes, I think the process I've done broke something.
SnoopDoggyStyleDogg said:
Does havok has A/B partition support?
Click to expand...
Click to collapse
Yes, I've downloaded arm64 a/b
Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
-internal storage showed as 8 gb
These are common to all GSI or only to havoc?
mac12m99 said:
Ok, i've managed to install havoc waiting some minutes and ignoring the error, these are the issues i've found:
-camera don't work(even with magisk mi a2 camera)
-torch don't work
-notch not recognised
These are common to all GSI or only to havoc?
Click to expand...
Click to collapse
try and enable all permision for the camera app from settings if the error says can't connect to camera
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,
Jordan~Kurniawan said:
try and enable all permision for the camera app from settings if the error says can't connect to camera
Click to expand...
Click to collapse
Tried but nothing, i have black screen btw, no error is displayed
Jordan~Kurniawan said:
yes notch is an issue on all GSI I've been trying so far, I've been unable to find a way to add a padding to the statusbar so the icon gets cut on the corner,
Click to expand...
Click to collapse
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?
mac12m99 said:
Tried but nothing, i have black screen btw, no error is displayed
As i've read, notch info is inside build.prop, so maybe copying notch info from stock do the trick
Do you know some 9.0 gsi that are mostly working?
Click to expand...
Click to collapse
maybe, for what I've understand we need to manually edit the system ui apk
I'm only trying the 8.1 GSI because i think that what would work the most
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it
Jordan~Kurniawan said:
maybe, for what I've understand we need to manually edit the system ui apk
Click to expand...
Click to collapse
ah ok
Jordan~Kurniawan said:
I'm only trying the 8.1 GSI because i think that what would work the most
Click to expand...
Click to collapse
trying RR Oreo..
Jordan~Kurniawan said:
I'll try to look into that notch thing and ask some devs
because i haven't read anyone talk about it
Click to expand...
Click to collapse
Ok thanks:good:
What about internal storage space issue?
PS
i've found that wiping data from twrp or fastboot cause always a bootloop, the right way is to flash userdata.img from stock rom.
After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.
mac12m99 said:
After trying some roms i've understood that:
-only P roms support notch correctly, but all P roms have camera and torch not working(and probably wrong storage space)
-O roms work perfectly but notch is not recognised at all, it's like to have a fullscreen device
I don't know how, but 1 time i managed to get havoc os camera working, unfortunally i wanted to flash twrp to get gapps but i've messed up...
Maybe security patch matter when installing gsi? I'm not sure but i think i was on september update.
Click to expand...
Click to collapse
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time
Jordan~Kurniawan said:
i read somewhere that we need to set SElinux to permissive to make the camera work (idk why) gonna try this soon, you can test this if you have the time
Click to expand...
Click to collapse
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first
mac12m99 said:
In fact i Remember to have launched "setenforce 0"
I Will try in the weekend because in these days i dont have much time.
Please tell me if you Will try first
Click to expand...
Click to collapse
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
edit:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9
Jordan~Kurniawan said:
do you have any idea about vendor partition?
because some say that not every vendor put everything in there, something crucial like camera lib can still be put on system by the vendor (in this case its Xiaomi) thats why when we flash gsi somethings may not work
because the vendor partition (sometimes) does not contain everything we need
Click to expand...
Click to collapse
Can be, i will look into this weekend, but oreo gsi works so i don't think.
Jordan~Kurniawan said:
I've been reading few articles about treble and gsi.
apparently, we won't be able to use camera and maybe other things on android 9.0 if we don't have the source for it. it would take a serious hacking involved to make android 9.0 work with 8.1 vendor image.
so our only option is to wait for a developer to work on 9.0 gsi and patch for our device
but it's maybe a waste of time because our device are promised to have at least 2 major android updates
android 9 and 10 and devs probably would be better off using the official firmware and extract blobs from it rather than hacking an oreo libs to work with android 9
Click to expand...
Click to collapse
Consider that in this thread a lot of people reported that camera work(and someone that don't).
I think all depends on phh patches version that the build use, but thats the first treble device i own so i don't know much about treble, sorry .
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
Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com
09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse
MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.
MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.
12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse
Bug....the touch does not work and it seems to reboot intermittently
Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?
MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!
Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.
Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770
20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
Hello, what changes between this rom and the stock based roms ?