extSdCard Permissions changed on its own? - General Questions and Answers

I've been having an odd issue for a little while. However, it wasn't a problem until just recently. I have an Samsung Galaxy Note 3 (SM-N900A) that is running 5.0 Rooted through SafeStrap (mind you that barely works and if I boot into it I go boot loops now, whole other issue).
One afternoon I tried to take a picture of my daughter using Snap Camera and notice this error across the bottom saying that it cannot access the sd card. Odd, just set it to default storage and forgot about it. Fast forward several weeks and I go to move pictures around in my QuickPic gallery just as I always do. From main storage to SD card. Just got done taking video and pictures of my daughter at the carnival and go to move them to the SD folder reserved for her pictures. The move is near instantaneous and I back out of the QuickPic Camera folder and the folder that I moved it to its thumbnail doesn't update. WTF, click on it and the pictures and videos are not there. Moved on to file recovery app I have and it only finds half of ONE PICTURE.
I am livid.
Spent majority of last night and this morning looking at fixes. Went back to try and re-run SD Card Access fixes from the app store and they said it was already fixed. Edited the platform.xml , no love, entry was already there... no extra spaces or anything. FX File explorer when clicking on Media Card and going to delete/move something tells me that the action failed. Choosing the top right menu and hitting Enable Write Access takes me to the Storage Selection screen, choose SD Card, hit "Select "SD Card"" (Root directory), and it tells me that "the selected location is different than the location of this storage. Go and select the root blah blah."
Now if I go and restart the phone it works as intended for about the first maybe two minutes. Moving files/taking pics etc. After that for some reason it throws out the same errors.

Try looking into the dmesg log when the error happens maybe it can give some information about it.
Also try accessing your sdcard from a differernt path such as /mnt/media_rw/sdcard1 or similar.

This is the log file from FX File Explorer. 05-20 19:30:28.365 is where the error starts.
Android SDK: 21
Board: MSM8974
Build ID: LRX21V.N900AUCUEOC1
CPU: armeabi-v7a
Device: hlteatt
Fingerprint: samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC1:user/release-keys
Manufacturer: samsung
Model: SAMSUNG-SM-N900A
Product: hlteuc
Tags: release-keys
___________________
Error Log @ Fri May 20 19:30:37 CDT 2016: logcat -v threadtime -t 1000 -s nextapp.maui -s nextapp.fx -s AndroidRuntime -s dalvikvm
--------- beginning of system
--------- beginning of main
05-20 19:29:32.275 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:32.275 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:33.565 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:33.565 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:44.295 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:44.295 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:45.555 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:45.555 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:00.715 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:00.715 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:03.335 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:03.335 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:14.085 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:14.085 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:17.535 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:17.535 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:22.055 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:22.055 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:23.575 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:23.575 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:28.365 6795 12655 D nextapp.fx: Error removing partial file: Media Card/Download/13263869_10204654477881281_618831981940619113_n.jpg
05-20 19:30:28.365 6795 12655 D nextapp.fx: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.j.b(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.j.b(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.a.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.cm.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.ck.run(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.maui.k.d.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.maui.k.d.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Operation failed.
05-20 19:30:28.365 6795 12636 D nextapp.fx: nextapp.fx.operation.h: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.ch.b(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.a.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.a.b(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.n.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at java.lang.Thread.run(Thread.java:818)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.ck.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.maui.k.d.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.maui.k.d.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: java.io.FileNotFoundException: /storage/extSdCard/Download/13263869_10204654477881281_618831981940619113_n.jpg: open failed: EROFS (Read-only file system)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.IoBridge.open(IoBridge.java:456)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at java.io.FileOutputStream.<init>(FileOutputStream.java:87)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.h.<init>(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: ... 9 more
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: android.system.ErrnoException: open failed: EROFS (Read-only file system)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.Posix.open(Native Method)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.IoBridge.open(IoBridge.java:442)
05-20 19:30:28.365 6795 12636 D nextapp.fx: ... 11 more

SilntExecutnr said:
This is the log file from FX File Explorer. 05-20 19:30:28.365 is where the error starts.
Android SDK: 21
Board: MSM8974
Build ID: LRX21V.N900AUCUEOC1
CPU: armeabi-v7a
Device: hlteatt
Fingerprint: samsung/hlteuc/hlteatt:5.0/LRX21V/N900AUCUEOC1:user/release-keys
Manufacturer: samsung
Model: SAMSUNG-SM-N900A
Product: hlteuc
Tags: release-keys
___________________
Error Log @ Fri May 20 19:30:37 CDT 2016: logcat -v threadtime -t 1000 -s nextapp.maui -s nextapp.fx -s AndroidRuntime -s dalvikvm
--------- beginning of system
--------- beginning of main
05-20 19:29:32.275 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:32.275 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:33.565 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:33.565 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:44.295 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:44.295 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:29:45.555 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:29:45.555 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:00.715 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:00.715 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:03.335 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:03.335 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:14.085 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:14.085 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:17.535 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:17.535 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:22.055 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:22.055 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:23.575 6795 6795 D nextapp.maui: found:/storage/emulated/0
05-20 19:30:23.575 6795 6795 D nextapp.maui: found:/storage/extSdCard
05-20 19:30:28.365 6795 12655 D nextapp.fx: Error removing partial file: Media Card/Download/13263869_10204654477881281_618831981940619113_n.jpg
05-20 19:30:28.365 6795 12655 D nextapp.fx: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.j.b(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.j.b(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.a.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.cm.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.fx.dir.ck.run(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.maui.k.d.a(Unknown Source)
05-20 19:30:28.365 6795 12655 D nextapp.fx: at nextapp.maui.k.d.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Operation failed.
05-20 19:30:28.365 6795 12636 D nextapp.fx: nextapp.fx.operation.h: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.ch.b(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.a.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.a.b(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.operation.n.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at java.lang.Thread.run(Thread.java:818)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: nextapp.fx.ak: NO_ACCESS_WRITE_SECONDARY_STORAGE_SAF
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.f.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.bw.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.ck.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.maui.k.d.a(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.maui.k.d.run(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: java.io.FileNotFoundException: /storage/extSdCard/Download/13263869_10204654477881281_618831981940619113_n.jpg: open failed: EROFS (Read-only file system)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.IoBridge.open(IoBridge.java:456)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at java.io.FileOutputStream.<init>(FileOutputStream.java:87)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at nextapp.fx.dir.file.h.<init>(Unknown Source)
05-20 19:30:28.365 6795 12636 D nextapp.fx: ... 9 more
05-20 19:30:28.365 6795 12636 D nextapp.fx: Caused by: android.system.ErrnoException: open failed: EROFS (Read-only file system)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.Posix.open(Native Method)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
05-20 19:30:28.365 6795 12636 D nextapp.fx: at libcore.io.IoBridge.open(IoBridge.java:442)
05-20 19:30:28.365 6795 12636 D nextapp.fx: ... 11 more
Click to expand...
Click to collapse
Read only file system while it clearly shouldn't be.
I would take a look at how the filesystem is mounted.
Open up a terminal and run
Code:
mount
and post the output here.
Also run
Code:
dmesg
in the same terminal and post that output here as well.

Not sure what to do about dmesg. Tried output to .txt file and all it says is - waiting on device- and hangs with an empty file.
Here's mount:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1443228k,nr_inodes=126670,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1443228k,nr_inodes=126670,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1443228k,nr_inodes=126670,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1443228k,nr_inodes=126670,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.gn.android.compass-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue 0 0
/dev/block/dm-1 /mnt/asec/org.scummvm.scummvm-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1443228k,nr_inodes=126670,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware-modem vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:66 /data/sdext2 ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:66 /data/media/obb/com.aspyr.swkotor ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/knox-emulated fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1443228k,nr_inodes=126670,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/extSdCard vfat rw,dirsync,seclabel,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/extSdCard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #

The mounts seem alright, at least the ones concerning the sdcard.
As for dmesg, it seems running dmesg >
Code:
/data/local/dmesg.txt
should work and create a file under /data/local/ with the output.
Also did you try to navigate to /mnt/media_rw/sdcard1/ yet?

ruleh said:
The mounts seem alright, at least the ones concerning the sdcard.
As for dmesg, it seems running dmesg >
Code:
/data/local/dmesg.txt
should work and create a file under /data/local/ with the output.
Also did you try to navigate to /mnt/media_rw/sdcard1/ yet?
Click to expand...
Click to collapse
/mnt/media_rw/extSdCard is access denied unless I use the root access shortcut. Which then I do have control until it auto revokes my privileges from the built in root module.
EDIT: While I was there with root I deleted a file in the download directory and moved a couple things and restarted... The items are still in their original places and the deleted item is back and functional... wtf?
Here is the dmesg.

Related

Developer's zone for LG P690 a.k.a Optimus Net

Developers here :
deepss1
Aceximix
Requested developers to join the topic :
1) Karandeepdps
2) aj1234josh
3) prateek1992
4) Christianvari
Beta testers :
Yet to set beta testers.
PM me if you want to be a beta tester.
Only two beta testers.
Number of GB roms : 9
Number of ICS roms : 3 (camera not working)
Number of JB roms : 1 (with many bugs)
Aim - To solve ICS camera bug
Bugs solved -
Yet to solve any bugs.
Note :
1) Developers please do reserve posts for your contribution.
2) Also write your contribution for LG P690
3) For non P690 devs - If you want to develop for P690 make pm to me and get involved in development of P690.
There are many testers for ONet.
If you want you can buy us a beer
Contact me by mail or pm.
Email id - [email protected]
Reserved!!
Reserved!!
Direct to topic..:silly:
AS OF MY THIS LOG..I GUESS>>WE HAVE CAMERA HAL WORKING.. ANY FURTHUR IDEAS FROM YOU??
V/CameraHolder( 2101): open camera 0
I/CameraHAL( 2330): CameraHAL_GetCam_Info:
D/CameraHAL( 2330): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
I/CameraService( 2330): Opening camera 0
D/CameraHAL( 2330): qcamera_device_open: name:0 device:0x13e0c cameraId:0
D/CameraHAL( 2330): loading libcamera at 0xb000e5a8
D/QualcommCameraHardware( 2330): createInstance: E
I/QualcommCameraHardware( 2330): startCamera: camsensor name s5k5caga, flash 0
I/DEBUG ( 1482): #00 pc 0000b2f2 /system/lib/liboemcamera.so (isp3a_exit)
I/DEBUG ( 1482): #01 pc 000086f6 /system/lib/liboemcamera.so
I/DEBUG ( 1482): #02 pc 00008824 /system/lib/liboemcamera.so (cam_conf)
I/DEBUG ( 1482): 41628a28 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a30 a771dc71 /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a3c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a7c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a8c a77086fb /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a94 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a9c a7708829 /system/lib/liboemcamera.so
E/CameraHolder( 2101): fail to connect Camera
E/CameraHolder( 2101): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 2101): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 2101): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 2101): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 2101): at com.android.camera.CameraHolder.open(CameraHolder. java:131)
E/CameraHolder( 2101): at com.android.camera.Util.openCamera(Util.java:313)
E/CameraHolder( 2101): at com.android.camera.Camera$4.run(Camera.java:1246)
E/CameraHolder( 2101): at java.lang.Thread.run(Thread.java:856)
I/ServiceManager( 1477): service 'media.camera' died
W/Camera ( 2101): Camera server died!
V/camera ( 2101): surfaceChanged. w=320. h=427
I/ActivityManager( 1598): Displayed com.android.camera/.Camera: +2s851ms
I/CameraService( 2514): CameraService started (pid=2514)
E/CameraHAL( 2514): CameraHAL_GetNum_Cameras:
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: numCameras:1
Click to expand...
Click to collapse
Samsung galaxy pop have camera working and also p500 which is almost same configured to our p690
Hope we developers will solve this camera bug early.
Just little guidance from p500 and galaxy pop developers may solve our camera bug. So looking forward to camera bug and that too without any donations
Something good....
Now you can find lg optimus net forum in this website ----->>
http://www.fesilo.com/forum/lg-optimus-net-p690
So from now ask developers to post ROMs here so its easy to find ROMs for Optimus Net....
Any news? Hope they help Onet p690, please samsung pop and p500 developers
Sent from my LG-P690 using xda app-developers app

Can anyone help me read my logcat?

I just made a rom. It booted fine. Setup and started checking on it. It just reboot adn gone into a bootloop. Here I filtered main activity:
I/ActivityManager(12117): [email protected]
I/ActivityManager(13232): Memory class: 48
W/ActivityManager(13232): Unable to write /sys/module/lowmemorykiller/parameters/adj_killed_level
I/ActivityManager(13232): Config changes=1df8 {1 0 1.0 ?mcc?mnc en_US ldltr sw320dp w320dp h508dp 240dpi nrml long port ?uimode ?night -touch -keyb/v/h -nav/h s.2}
I/ActivityManager(13232): Config changes=8 {1 0 1.0 ?mcc?mnc en_US ldltr sw320dp w320dp h508dp 240dpi nrml long port ?uimode ?night finger -keyb/v/h -nav/h s.3}
I/ActivityManager(13232): System now ready
I/ActivityManager(13232): Config changes=200 {1 0 1.0 ?mcc?mnc en_US ldltr sw320dp w320dp h508dp 240dpi nrml long port finger -keyb/v/h -nav/h s.4}
W/ActivityManager(13232): Unable to start service Intent { act=com.sec.knox.eventsmanager.ContainerEventsRelayManager } U=0: not found
W/ActivityManager(13232): Unable to start service Intent { act=com.samsung.redexmobile.ReDexService } U=0: not found
W/ActivityManager(13232): mDVFSHelper.release()
I/ActivityManager(13232): [email protected]
As you can see, it looped.
Or see attachment for full logcat (renamed .zip to .txt)

Google Camera 4.2

Hi,
Is there a working apk somewhere?
Thanks
Sent from my A0001 using Tapatalk
APK Mirror: https://www.apkmirror.com/apk/google-inc/camera/camera-4-2-035-141213305-release/
Arthur4ik said:
APK Mirror: https://www.apkmirror.com/apk/google-inc/camera/camera-4-2-035-141213305-release/
Click to expand...
Click to collapse
Must install as system app?
Arthur4ik said:
APK Mirror: https://www.apkmirror.com/apk/google-inc/camera/camera-4-2-035-141213305-release/
Click to expand...
Click to collapse
Crashes right after I open it
Sent from my A0001 using Tapatalk
TheNerd said:
Crashes right after I open it
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
There is nothing you can do to fix that. It fails with NullPointerException (wtf?):
Code:
12-13 12:13:41.469 289 19172 E mm-camera: q3a_port_send_event_downstream: AEC event handler returned failure!
12-13 12:13:41.471 19035 19035 E AndroidRuntime: FATAL EXCEPTION: main
12-13 12:13:41.471 19035 19035 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 19035
12-13 12:13:41.471 19035 19035 E AndroidRuntime: java.lang.RuntimeException: java.lang.NullPointerException
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.error.UncaughtExceptionHandler$1.run(UncaughtExceptionHandler.java:29)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:751)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6126)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: Caused by: java.lang.NullPointerException
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.google.common.base.ExtraObjectsMethodsForWeb.checkNotNull(ExtraObjectsMethodsForWeb.java:4770)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.one.v2.autofocus.AfStateResponseListenerImpl.onCompleted(AfStateResponseListenerImpl.java:35)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.one.v2.core.ResponseListenerBroadcaster.onCompleted(ResponseListenerBroadcaster.java:50)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.one.v2.core.BasicFrameRequestProcessor$CaptureCallback.onCaptureCompleted(BasicFrameRequestProcessor.java:74)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.one.v2.stats.ProfilingCameraCaptureSession$ProfilingCaptureCallback.onCaptureCompleted(ProfilingCameraCaptureSession.java:49)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at com.android.camera.one.v2.camera2proxy.AndroidCameraCaptureSessionProxy$AndroidCaptureCallback.onCaptureCompleted(AndroidCameraCaptureSessionProxy.java:61)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.hardware.camera2.dispatch.InvokeDispatcher.dispatch(InvokeDispatcher.java:39)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.hardware.camera2.dispatch.HandlerDispatcher$1.run(HandlerDispatcher.java:65)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:751)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
12-13 12:13:41.471 19035 19035 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
12-13 12:13:41.471 279 19078 D QCameraParameters: update current cct value. old:-1, now:0
Use 4.1 instead (but movie recording won't work).
This is the last fully functional version for OPO, it does limit rear camera @ 13MP, and 5MP front (Nexus 5X/6P specs)
http://www.apkmirror.com/apk/google-inc/camera/camera-2-7-008-release/
I've run on CM13.1, and 14.1 (http://forum.xda-developers.com/oneplus-one/development/rom-resurrection-remix-t3507102) 7.1.1
LTBooster said:
This is the last fully functional version for OPO, it does limit rear camera @ 13MP, and 5MP front (Nexus 5X/6P specs)
http://www.apkmirror.com/apk/google-inc/camera/camera-2-7-008-release/
I've run on CM13.1, and 14.1 (http://forum.xda-developers.com/oneplus-one/development/rom-resurrection-remix-t3507102) 7.1.1
Click to expand...
Click to collapse
Very old version, outdated. I have 4.1 version, very good for panoramas.
giaur said:
Very old version, outdated. I have 4.1 version, very good for panoramas.
Click to expand...
Click to collapse
True enough, 4.1 is what I've been using, sans video. Simply shared the last fully functional version, which was released in August.
LTBooster said:
True enough, 4.1 is what I've been using, sans video. Simply shared the last fully functional version, which was released in August.
Click to expand...
Click to collapse
Can you link the version ? all works except for videos ?
sgronkia said:
Can you link the version ? all works except for videos ?
Click to expand...
Click to collapse
http://www.apkmirror.com/apk/google...amera-4-1-006-135988111-android-apk-download/
Correct, Google Camera 4.1 works except for video, for Android 7.0+, what are you running? You'll need a different version if on MM or LP.
LTBooster said:
http://www.apkmirror.com/apk/google...amera-4-1-006-135988111-android-apk-download/
Correct, Google Camera 4.1 works except for video, for Android 7.0+, what are you running? You'll need a different version if on MM or LP.
Click to expand...
Click to collapse
Tuga 7.1.1
sgronkia said:
Tuga 7.1.1
Click to expand...
Click to collapse
Then give it a go, try both. Personally I don't see any real difference (in results) between, 2.7 and 4.1 except for lack of video in 4.1 (I don't shoot much video) I believe they were just getting it ready for the Pixel phones.
2.7 (08.16) http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/
4.1 (10.16) http://www.apkmirror.com/apk/google...amera-4-1-006-135988111-android-apk-download/
LTBooster said:
Then give it a go, try both. Personally I don't see any real difference (in results) between, 2.7 and 4.1 except for lack of video in 4.1 (I don't shoot much video) I believe they were just getting it ready for the Pixel phones.
2.7 (08.16) http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/
4.1 (10.16) http://www.apkmirror.com/apk/google...amera-4-1-006-135988111-android-apk-download/
Click to expand...
Click to collapse
Thank you
Sorry, I tested it on my Nexus 5 (CM14), Not on OPO

Android 9+ for S7 with camera and fingerprint working properly

I've tested already many S7 (herolte) ROMs and couldn't find any that would have both working properly: camera and fingerprint.
For camera: all of the AOSP based ROMs stop working after about 20 minutes of video chat (sometimes even earlier). Then you have to reboot telephone to make camera working again. I have tried PixelExperience, LineageOS 17-19 and others I don't really remember names now. You can try it yourself by starting WhatsApp or Messenger video chat and waiting bout 20 minutes.
Quite irritating is the fact, that they never mention this issue in ROM summary page, you can only test it yourself or sometimes find reports from ROM users comments, that there's this issue, and it seems quite old and known issue.
For fingerprint: all the stock kernel based ROMs support for fingerprint functionality is partial. Some applications will work with it, but some will crash or just refuse to work like Keepass2Android. Sad thing to say is, that great ROMs like for example FloydQ and Lightheart have no issue with camera but they do with fingerprint.
For this one at least I've found some explanation by @ananjaser1211 why it's not compatible with the stock kernel:
"The 3rd party fingerprint bug is not related to safetynet. It's an incompatibility between the oreo auth tz server we use and the pie+ fingerprint hidl. We can't use the lineage fingerprint hidl. I've tried but it's not compatible with oneui. And we need such custom hidls in order to have working fp"
It seems that it's impossible at the moment to have both fixed. I believe it's a kernel-related thing.
Or maybe someone has found a ROM or a way to make both working correctly?
I think fingerprint was resolved in recent lineage builds, as they found a way to make a compatible hidl that resolves the mismatch we faced, however i had no luck implementing it in my ROM, AOSP components dont really love oneui much.
regarding the camera not working, this is due to a patch made in the camera HAL to bypass FDSAN issues, it does bypass the issue, but after a while of usage it will have issues with FD's and stop working (either not loading entirely or showing a green screen)
we faced this issue in FloydQ v4 or V5 i do not recall when i implemented that patch, however due to it being unstable i resorted to a different method of disabling FDSAN in the ROM itself, rather than fixing it in the camera driver, which is a hack, not really something lineage peeps are interested in.
in lineage this is done in source by setting FDSAN error level to "ANDROID_FDSAN_ERROR_LEVEL_DISABLED"
in OneUI Q it is done by setting "debug.fdsan=0" in prop, which samsung left exposed, however it is not the case for lineage and it needs to be done in the source
I've tested most of the available Android 9+ custom ROMs for S7 (herolte) just to be sure no one made one that would have fixed both camera and fingerprint. Here is my result:
ROMs with camera issue (camera stops working after 20 minutes of uninterrupted usage like in video chat):
PixelExperience 11 and 12 by @expressluke
Lineage 16,18,19 by @Ivan_Meler
DotOS by @expressluke
crDroid by @expressluke
Evolution X by @expressluke
aicp by @expressluke
ROMs with fingerprint issue (fingerprint in some apps like Keepass2Android and some banking apps won't work):
FloydQ by @ananjaser1211
Havoc-OS by @expressluke
ResurrectionRemix by @expressluke
LightRom by @yash92duster
Lightheart by @Skulldron
MKUltraBlack by @MKUltraBlack
NfeSuperleggera by @arcatarc
So to have both working correctly there is only one option: Stock / Android 8- ROMs.
Thank you @ananjaser1211 for the explanation. So the temporary fix for Lineage (and I guess other AOSP ones too) seems quite easy. I'll give it a try as it seems easier than fixing the fingerprint issue.
For me personally faulty video/camera makes ROM unusable in these days when video chats are so common. I can live without fingerprint in some apps, it is definitely less irritating than very unreliable camera. But it is of course a personal preference in the end.
ananjaser1211 said:
in lineage this is done in source by setting FDSAN error level to "ANDROID_FDSAN_ERROR_LEVEL_DISABLED"
Click to expand...
Click to collapse
I've tried disabling FDSAN on PixelExperience. It made camera work longer (like 30 minutes instead of 20 minutes) but still camera crashes after that. Here are logs that appear when camera crashes:
Code:
01-16 10:24:06.278 13467 14324 E SnapCam_CaptureModule: onError 1 4
01-16 10:24:06.280 13467 14324 D CompatibilityChangeReporter: Compat change id reported: 147798919; UID 10187; state: DISABLED
01-16 10:24:06.291 3682 13614 I chatty : uid=1047(cameraserver) HwBinder:3682_3 expire 5 lines
01-16 10:24:06.295 3621 14862 I chatty : uid=1047(cameraserver) [email protected] expire 22 lines
01-16 10:24:06.365 3608 3785 I nanohub : mergeDirectReportRequest - enable = 0 activate = 1 direct.rate = 0 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I nanohub : mergeDirectReportRequest - activate = 1 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I Sensors : batch(0) - accelerometer_sensor try to batching with 66667000
01-16 10:24:06.375 3682 3740 I chatty : uid=1047(cameraserver) HwBinder:3682_2 expire 7 lines
01-16 10:24:06.387 13467 13467 W System.err: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2267)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.submitCaptureRequest(CameraDeviceImpl.java:1161)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.setRepeatingRequest(CameraDeviceImpl.java:1234)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraCaptureSessionImpl.setRepeatingRequest(CameraCaptureSessionImpl.java:327)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.setAFModeToPreview(CaptureModule.java:2287)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:8107)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:4366)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.onPauseBeforeSuper(CaptureModule.java:4249)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CameraActivity.onPause(CameraActivity.java:1784)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Activity.performPause(Activity.java:8168)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1516)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4733)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4694)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4645)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:46)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Looper.loop(Looper.java:223)
01-16 10:24:06.389 13467 13467 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7664)
01-16 10:24:06.389 13467 13467 W System.err: at java.lang.reflect.Method.invoke(Native Method)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
01-16 10:24:06.390 3797 3839 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-16 10:24:06.391 13467 13467 D SnapCam_CaptureModule: onPause exit camera
01-16 10:24:06.392 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.395 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.398 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.399 3797 3907 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.400 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.401 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.402 3797 8733 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.406 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.409 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.410 13467 13467 D SnapCam_CaptureModule: closeCamera
Maybe it's also matter of camera software. @ananjaser1211 Do you know if it's possible to use stock camera on AOSP based ROMS and if it is, how much effort might that take?
Makowal said:
I've tried disabling FDSAN on PixelExperience. It made camera work longer (like 30 minutes instead of 20 minutes) but still camera crashes after that. Here are logs that appear when camera crashes:
Code:
01-16 10:24:06.278 13467 14324 E SnapCam_CaptureModule: onError 1 4
01-16 10:24:06.280 13467 14324 D CompatibilityChangeReporter: Compat change id reported: 147798919; UID 10187; state: DISABLED
01-16 10:24:06.291 3682 13614 I chatty : uid=1047(cameraserver) HwBinder:3682_3 expire 5 lines
01-16 10:24:06.295 3621 14862 I chatty : uid=1047(cameraserver) [email protected] expire 22 lines
01-16 10:24:06.365 3608 3785 I nanohub : mergeDirectReportRequest - enable = 0 activate = 1 direct.rate = 0 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I nanohub : mergeDirectReportRequest - activate = 1 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I Sensors : batch(0) - accelerometer_sensor try to batching with 66667000
01-16 10:24:06.375 3682 3740 I chatty : uid=1047(cameraserver) HwBinder:3682_2 expire 7 lines
01-16 10:24:06.387 13467 13467 W System.err: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2267)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.submitCaptureRequest(CameraDeviceImpl.java:1161)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.setRepeatingRequest(CameraDeviceImpl.java:1234)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraCaptureSessionImpl.setRepeatingRequest(CameraCaptureSessionImpl.java:327)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.setAFModeToPreview(CaptureModule.java:2287)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:8107)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:4366)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.onPauseBeforeSuper(CaptureModule.java:4249)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CameraActivity.onPause(CameraActivity.java:1784)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Activity.performPause(Activity.java:8168)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1516)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4733)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4694)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4645)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:46)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Looper.loop(Looper.java:223)
01-16 10:24:06.389 13467 13467 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7664)
01-16 10:24:06.389 13467 13467 W System.err: at java.lang.reflect.Method.invoke(Native Method)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
01-16 10:24:06.390 3797 3839 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-16 10:24:06.391 13467 13467 D SnapCam_CaptureModule: onPause exit camera
01-16 10:24:06.392 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.395 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.398 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.399 3797 3907 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.400 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.401 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.402 3797 8733 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.406 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.409 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.410 13467 13467 D SnapCam_CaptureModule: closeCamera
Maybe it's also matter of camera software. @ananjaser1211 Do you know if it's possible to use stock camera on AOSP based ROMS and if it is, how much effort might that take?
Click to expand...
Click to collapse
Regarding the error, this is a bit generic, the actual hal crash would be in data/tombstones probably, you have disabled fdsan, but did you revert the libexynoscamera "fdsan" patches, i.e the hacks that causes the green issue in the first place. since you disabled fdsan in the rom, you dont need these patches, you should check them in the vendor tree of the rom you are compiling, (generally speaking, using unmodified Note 7 fe libexynoscamera should be fine), after that, test the camera further and keep an eye on HAL crashes (not app crashes) , in theory there should be none. since as far as i know fdsan is the only fatal error on our hal
on the topic of using stock camera on AOSP, no it is not doable, samsung camera (and apps in general) have deep SEM/SEP hooks everywhere , in frameworks / helpers / libs, without having oneui source i dont see how someone can do it without losing half their hair.
Thank you so much @ananjaser1211 for the information. In this situation I'm seriously considering trying my best with your FloydQ compliation for herolte to help fixing fingerprint issue. Personally the cameras used in AOSP are not only faulty but also slow, and herolte is already old so I'm afraid there will be only less effort in future to do anything special for this device.
About the fingerprint I know you have already done some research in the matter. In FloydQ do you think that fixing existing fingerprint software would be easier or rather porting the one from AOSP? Do you have any hints for me where to start?
Makowal said:
Thank you so much @ananjaser1211 for the information. In this situation I'm seriously considering trying my best with your FloydQ compliation for herolte to help fixing fingerprint issue. Personally the cameras used in AOSP are not only faulty but also slow, and herolte is already old so I'm afraid there will be only less effort in future to do anything special for this device.
About the fingerprint I know you have already done some research in the matter. In FloydQ do you think that fixing existing fingerprint software would be easier or rather porting the one from AOSP? Do you have any hints for me where to start?
Click to expand...
Click to collapse
I did not dive into the fingerprint issue on floyd significantly (from testing fixes perspective) so there might be ways to fix it outside the hidl, but to summarize,
we use hero mcDriverDaemon / libmcregistry / libmcclient and vendor/app/mcRegistry,
these are only designed to work properly with OREO libbauth/libauth server (the blobs responsible for fingerprint), however, we dont use oreo bauth, we use the ones from pie (gracerlte) because the oreo ones does not load properly with pie and higher fingerprint HAL, in our case it is `[email protected]`
To test some fixes, i would first start by replacing the hidl used in floyd with latest compiled one from AOSP (making sure it is being compiled with android Q dependencies) and debug why it does not exec, because it "should" work, as this is more or less a generic hidl
once the hal executes, i put back oreo libbauth/libauth servers and try my luck.
i am working on V7 of that rom, so i might give the FP another shot, maybe i missed something when i tackled it last time.
@ananjaser1211 I've tried again with an official PixelExperience ROM and this time I did exactly as you said. I'm happy to say that it worked! I've tested it for over an hour. I finally have a ROM with both working Camera and Fingerprint
I suspect that the reason lays in this commit from git log:
Git:
commit 77e12d12a0c9659aed776332c0f1511c54d2b906
Date: Thu Aug 6 09:32:35 2020 +0200
universal8890: pin hexedited libexynoscamera3
* some fd close in loop causes android Q fdsan go mad
* binary patching them as nop fixes the issue
Change-Id: I56f409fde5902b5340291bb5d454a619cdd7d0a0
What I think happens here is after the binary was hexedited it doesn't close fds, so after some time there are too many open and the app crashes (even if fdsan is disabled).
Of course it is some workaround because fdsan is disabled now but well, good enough for me
Makowal said:
@ananjaser1211 I've tried again with an official PixelExperience ROM and this time I did exactly as you said. I'm happy to say that it worked! I've tested it for over an hour. I finally have a ROM with both working Camera and Fingerprint
I suspect that the reason lays in this commit from git log:
Git:
commit 77e12d12a0c9659aed776332c0f1511c54d2b906
Date: Thu Aug 6 09:32:35 2020 +0200
universal8890: pin hexedited libexynoscamera3
* some fd close in loop causes android Q fdsan go mad
* binary patching them as nop fixes the issue
Change-Id: I56f409fde5902b5340291bb5d454a619cdd7d0a0
What I think happens here is after the binary was hexedited it doesn't close fds, so after some time there are too many open and the app crashes (even if fdsan is disabled).
Of course it is some workaround because fdsan is disabled now but well, good enough for me
Click to expand...
Click to collapse
Fantastic to hear! and yes indeed the patch used to prevent fdsan from breaking camera also allows for FDs to say open i believe and after a while the camera breaks, Glad the workaround is working for you
Recently I started using this newly updated ROM of @Exodusnick . It is a Lineage 16.0 (Android 9) and has both camera and fingerprint working without issues so it meets my criteria (as in this topic title). Unfortunately higher Android versions of the same microG compilation do have camera crash issue after 20m usage, but Pie is ok and works for me.
Personally I'd definitely prefer some Android 9 with OneUI. I don't care about newest Android versions, just the ROM to be daily-usable (stable). Android 9 is required by one of my must-have applications this is the only reason why I put it as a minimum version. Unfortunately I don't think any Android 9 OneUI ROM for S7 exists with working fingerprint. @ananjaser1211 did your compilations of Android 9 had this fingerprint issue?

Trying to get the stock camera app to work under AOSP

Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
I read on here not too long ago that the stock camera app broke since Android 12 because of a storage permission, I think? The only ROM I know of that has the stock camera app is Lineage 18.1 by @Sjll, but I don't think that ROM is AOSP based.
I think a few of the experts here like, @Miustone, @Sjll, @bobbyamarthaa, @elmaleek03, (sorry for the tags guys) might be able to help.
The moment you (or anyone else) get that stock camera app working I am gonna install your ROM straight away, it's the only thing keeping me on the Stock ROM.
Please continue the great work!
grisu59964 said:
Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
Click to expand...
Click to collapse
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
grisu59964 said:
Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
Click to expand...
Click to collapse
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
BrandonMCMFG said:
I read on here not too long ago that the stock camera app broke since Android 12 because of a storage permission, I think? The only ROM I know of that has the stock camera app is Lineage 18.1 by @Sjll, but I don't think that ROM is AOSP based.
I think a few of the experts here like, @Miustone, @Sjll, @bobbyamarthaa, @elmaleek03, (sorry for the tags guys) might be able to help.
The moment you (or anyone else) get that stock camera app working I am gonna install your ROM straight away, it's the only thing keeping me on the Stock ROM.
Please continue the great work!
Click to expand...
Click to collapse
Thanks for tagging Me, glad to see some Life over here!
bobbyamarthaa said:
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
Click to expand...
Click to collapse
Trees are availble on many Places. I would suggest using the SODP Trees since everything works over there except for Mobile Data...
Miustone said:
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
Thanks for tagging Me, glad to see some Life over here!
Trees are availble on many Places. I would suggest using the SODP Trees since everything works over there except for Mobile Data...
Click to expand...
Click to collapse
SODP need to much modified to work perfectly.
and it removes all xperia exclusive features.
Thank you everyone for your replies! I've been active in background, working on the problem.
So far, I have created a shim for _ZNK7android6Parcel10readIntPtrEv and modified the references of libcacao_client to use libbinder.so and libhidlbase.so. Now the stock camera app starts, but it still won't work. It takes a few seconds before the message "Unknown error" appears on the screen.
No more exceptions in log, but I saw this:
Code:
10-03 12:25:42.968 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.platform
10-03 12:25:42.971 1691 4803 W ServiceManager: Permission failure: android.permission.HIGH_SAMPLING_RATE_SENSORS from uid=10064 pid=14151
10-03 12:25:42.977 14151 14194 I CameraManagerGlobal: Connecting to camera service
10-03 12:25:42.979 1336 1936 W ServiceManager: Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10064 pid=14151
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: Cannot read /data/user/0/com.sonyericsson.android.camera/shared_prefs/com.sonyericsson.android.camera.supported_values.4.xml
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: org.xmlpull.v1.XmlPullParserException: Unexpected end of document
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:1548)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:969)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.loadFromDisk(SharedPreferencesImpl.java:171)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.access$000(SharedPreferencesImpl.java:59)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl$1.run(SharedPreferencesImpl.java:140)
10-03 12:25:43.000 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.4
10-03 12:25:43.003 636 636 E SELinux : avc: denied { find } for pid=14151 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
10-03 12:25:43.003 14151 14194 I ServiceManager: Waiting for service 'cacao' on '/dev/binder'...
Is it possible that the cacao service is not running or cannot be found because of missing SELinux permissions?
I already set SELinux to permissive, but the only change was permissive=1 in the log.
bobbyamarthaa said:
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
Click to expand...
Click to collapse
I'm now using a mixture of elmaleek03s device tree and some additional changes for the stock camera app. The advise to head over to Telegram was already helpful as I got the hint with the shim there.
Miustone said:
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
Click to expand...
Click to collapse
I was active on android-hilfe.de, yes, but maybe I'm better known for my work back in the days on SE-world. I also dropped you a PM.
Currently, I'm using my Xperia 5 as my daily driver (keeping my old buddy alive) so I try not to ruin everything all the time. But I'm really curious what you are doing with DIOS.
grisu59964 said:
Thank you everyone for your replies! I've been active in background, working on the problem.
So far, I have created a shim for _ZNK7android6Parcel10readIntPtrEv and modified the references of libcacao_client to use libbinder.so and libhidlbase.so. Now the stock camera app starts, but it still won't work. It takes a few seconds before the message "Unknown error" appears on the screen.
No more exceptions in log, but I saw this:
Code:
10-03 12:25:42.968 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.platform
10-03 12:25:42.971 1691 4803 W ServiceManager: Permission failure: android.permission.HIGH_SAMPLING_RATE_SENSORS from uid=10064 pid=14151
10-03 12:25:42.977 14151 14194 I CameraManagerGlobal: Connecting to camera service
10-03 12:25:42.979 1336 1936 W ServiceManager: Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10064 pid=14151
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: Cannot read /data/user/0/com.sonyericsson.android.camera/shared_prefs/com.sonyericsson.android.camera.supported_values.4.xml
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: org.xmlpull.v1.XmlPullParserException: Unexpected end of document
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:1548)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:969)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.loadFromDisk(SharedPreferencesImpl.java:171)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.access$000(SharedPreferencesImpl.java:59)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl$1.run(SharedPreferencesImpl.java:140)
10-03 12:25:43.000 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.4
10-03 12:25:43.003 636 636 E SELinux : avc: denied { find } for pid=14151 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
10-03 12:25:43.003 14151 14194 I ServiceManager: Waiting for service 'cacao' on '/dev/binder'...
Is it possible that the cacao service is not running or cannot be found because of missing SELinux permissions?
I already set SELinux to permissive, but the only change was permissive=1 in the log.
I'm now using a mixture of elmaleek03s device tree and some additional changes for the stock camera app. The advise to head over to Telegram was already helpful as I got the hint with the shim there.
I was active on android-hilfe.de, yes, but maybe I'm better known for my work back in the days on SE-world. I also dropped you a PM.
Currently, I'm using my Xperia 5 as my daily driver (keeping my old buddy alive) so I try not to ruin everything all the time. But I'm really curious what you are doing with DIOS.
Click to expand...
Click to collapse
glad to see someone popping out here. sadly im no longer using bahamut since months ago, i hope this issue can be fixed in a near. ive already tried ask Sjll, but he gave no clue except including all the related camera files in the build process. thats why his builds has a dedicated stock cam ROM ZIPS.
elmaleek03 said:
glad to see someone popping out here. sadly im no longer using bahamut since months ago, i hope this issue can be fixed in a near. ive already tried ask Sjll, but he gave no clue except including all the related camera files in the build process. thats why his builds has a dedicated stock cam ROM ZIPS.
Click to expand...
Click to collapse
om, coba intip ini.
GitHub - moghn1/android_device_sony_j9110: This is the error tree
This is the error tree. Contribute to moghn1/android_device_sony_j9110 development by creating an account on GitHub.
github.com
maybe u can use this as refference grisu59964
he is the same person who has built a custom rom for xperia 1 on coolapk forum
There were changes done by @elmaleek03 on setup-makefiles.sh that look like the camera APK gets elevated rights. Do I need to call setup-makefiles.sh manually during build? Can anybody help me fully understand what is going on in this commit?
added missing proprietary files and fix camera crash · sony-msmnile/[email protected]
:)
github.com
As far as my research goes now, the camera app needs to be executed in the system_app domain rather than platform_app and I would like to change that.
Alright, I found the answer to my last question myself. setup-makefiles.sh is called by extract-files.sh. And the code from the commit is written to vendor/sony/bahamut/Android.mk for anyone curious.
I'm currently starting /system/bin/cacaoserver via adb shell to get a message why the service crashes.
I have no idea why there is nothing to see in the log during boot. But at least now there is the first progress since days. Stay tuned!
Current state: cacaoserver is now able to start. I went through a lot of missing files and then segfaults. Unfortunately, the cacaoserver does somehow not survive the boot phase and is not running any more when the camera app starts. When I start the binary manually, it stays alive.
If SELinux is not enforcing, the camera app will start, connect to the cacaoserver and then crash:
Code:
10-09 10:24:50.660 860 860 D Zygote : Forked child process 12098
10-09 10:24:50.660 1639 1743 I ActivityManager: Start proc 12098:com.sonyericsson.android.camera/u0a64 for pre-top-activity {com.sonyericsson.android.camera/com.sonyericsson.android.camera.CameraActivity}
10-09 10:24:50.691 12098 12098 E .android.camer: Not starting debugger since process cannot load the jdwp agent.
10-09 10:24:50.694 12098 12098 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
10-09 10:24:50.702 12098 12098 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10064; state: DISABLED
10-09 10:24:50.712 12098 12098 W .android.camer: ClassLoaderContext shared library size mismatch. Expected=0, found=1 (PCL[] | PCL[]{PCL[/product/framework/com.sonymobile.camera.addon_impl.jar*1938205956]})
10-09 10:24:50.719 12098 12098 V GraphicsEnvironment: ANGLE Developer option for 'com.sonyericsson.android.camera' set to: 'default'
10-09 10:24:50.720 12098 12098 V GraphicsEnvironment: ANGLE GameManagerService for com.sonyericsson.android.camera: false
10-09 10:24:50.720 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.721 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.801 12098 12119 I CameraManagerGlobal: Connecting to camera service
10-09 10:24:50.816 630 630 E SELinux : avc: denied { find } for pid=12098 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=1
10-09 10:24:50.866 1318 27514 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10064 pid=12098
10-09 10:24:50.885 12067 12070 D CacaoService: client create - pid:12098
10-09 10:24:50.885 12067 12070 I cacao : 2079724329205 pal.cpp (2611) 12070 I [INF] PAL_Create
10-09 10:24:50.888 12098 12122 E .android.camer: BypassCameraBurst_changeToPhotoMode: stop cacao ret=-111
10-09 10:24:50.888 12098 12122 D .android.camer: [Debug] BypassCameraBurst_changeToPhotoMode: burstNum=4
10-09 10:24:50.890 12098 12122 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
10-09 10:24:50.890 12098 12122 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 12098
10-09 10:24:50.890 12098 12122 E AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1870)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1826)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:776)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:96)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:86)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.BypassCameraController$OpenBypassCameraTask.doCameraDeviceAccess(BypassCameraController.java:1166)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-09 10:24:50.892 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.894 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.896 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.900 1639 12166 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-09 10:24:50.900 12098 12098 I DynamicAreaFilter: .init sSmoothFactor=0.9 screenSize.x=1080 screenSize.y=2520 mScreenHeight=2520 mLimitScale=71 mDynamicFilterType=2 mValidScreenHeightMin=252 mValidScreenHeightMax=1789
10-09 10:24:50.900 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.902 1639 4547 W ActivityTaskManager: Force finishing activity com.sonyericsson.android.camera/.CameraActivity
10-09 10:24:50.911 12098 12098 D SYMPHONY: Detected Symphony running as an Android application, using logcat for all debugging output
10-09 10:24:50.911 12098 12098 I SYMPHONY: [36mA t794df074f8 /local/mnt/workspace/pcgbait/docker.ci.tmp/build/aarch64-android-clang6.0/SecondParty/symphony/src/symphony/src/lib/internal/soc/topology.c:674 Could not resolve a cluster for cpu 7. The cluster may be offline. Power request will be ignored.[0m
10-09 10:24:50.920 12098 12122 I Process : Sending signal. PID: 12098 SIG: 9
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.944 957 2454 D [email protected]_lock: Release wakelock is released
10-09 10:24:50.973 12067 12067 D CacaoService: client delete - pid:12098
10-09 10:24:50.974 1639 1944 I ActivityManager: Process com.sonyericsson.android.camera (pid 12098) has died: fg TOP
10-09 10:24:50.974 1639 1746 I libprocessgroup: Successfully killed process cgroup uid 10064 pid 12098 in 0ms
The short life of the camera app process. 255 ms. Any hint solving those problems will massively improve my development speed, so please get in touch if you have a clue.
That is a very short life for a Camera App...
Rest in Piece Camera App - Lived for 255ms with SELinux set to permissive.
In all seriousness though, I really appreciate these updates please keep them coming.
grisu59964 said:
Current state: cacaoserver is now able to start. I went through a lot of missing files and then segfaults. Unfortunately, the cacaoserver does somehow not survive the boot phase and is not running any more when the camera app starts. When I start the binary manually, it stays alive.
If SELinux is not enforcing, the camera app will start, connect to the cacaoserver and then crash:
Code:
10-09 10:24:50.660 860 860 D Zygote : Forked child process 12098
10-09 10:24:50.660 1639 1743 I ActivityManager: Start proc 12098:com.sonyericsson.android.camera/u0a64 for pre-top-activity {com.sonyericsson.android.camera/com.sonyericsson.android.camera.CameraActivity}
10-09 10:24:50.691 12098 12098 E .android.camer: Not starting debugger since process cannot load the jdwp agent.
10-09 10:24:50.694 12098 12098 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
10-09 10:24:50.702 12098 12098 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10064; state: DISABLED
10-09 10:24:50.712 12098 12098 W .android.camer: ClassLoaderContext shared library size mismatch. Expected=0, found=1 (PCL[] | PCL[]{PCL[/product/framework/com.sonymobile.camera.addon_impl.jar*1938205956]})
10-09 10:24:50.719 12098 12098 V GraphicsEnvironment: ANGLE Developer option for 'com.sonyericsson.android.camera' set to: 'default'
10-09 10:24:50.720 12098 12098 V GraphicsEnvironment: ANGLE GameManagerService for com.sonyericsson.android.camera: false
10-09 10:24:50.720 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.721 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.801 12098 12119 I CameraManagerGlobal: Connecting to camera service
10-09 10:24:50.816 630 630 E SELinux : avc: denied { find } for pid=12098 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=1
10-09 10:24:50.866 1318 27514 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10064 pid=12098
10-09 10:24:50.885 12067 12070 D CacaoService: client create - pid:12098
10-09 10:24:50.885 12067 12070 I cacao : 2079724329205 pal.cpp (2611) 12070 I [INF] PAL_Create
10-09 10:24:50.888 12098 12122 E .android.camer: BypassCameraBurst_changeToPhotoMode: stop cacao ret=-111
10-09 10:24:50.888 12098 12122 D .android.camer: [Debug] BypassCameraBurst_changeToPhotoMode: burstNum=4
10-09 10:24:50.890 12098 12122 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
10-09 10:24:50.890 12098 12122 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 12098
10-09 10:24:50.890 12098 12122 E AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1870)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1826)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:776)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:96)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:86)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.BypassCameraController$OpenBypassCameraTask.doCameraDeviceAccess(BypassCameraController.java:1166)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-09 10:24:50.892 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.894 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.896 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.900 1639 12166 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-09 10:24:50.900 12098 12098 I DynamicAreaFilter: .init sSmoothFactor=0.9 screenSize.x=1080 screenSize.y=2520 mScreenHeight=2520 mLimitScale=71 mDynamicFilterType=2 mValidScreenHeightMin=252 mValidScreenHeightMax=1789
10-09 10:24:50.900 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.902 1639 4547 W ActivityTaskManager: Force finishing activity com.sonyericsson.android.camera/.CameraActivity
10-09 10:24:50.911 12098 12098 D SYMPHONY: Detected Symphony running as an Android application, using logcat for all debugging output
10-09 10:24:50.911 12098 12098 I SYMPHONY: [36mA t794df074f8 /local/mnt/workspace/pcgbait/docker.ci.tmp/build/aarch64-android-clang6.0/SecondParty/symphony/src/symphony/src/lib/internal/soc/topology.c:674 Could not resolve a cluster for cpu 7. The cluster may be offline. Power request will be ignored.[0m
10-09 10:24:50.920 12098 12122 I Process : Sending signal. PID: 12098 SIG: 9
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.944 957 2454 D [email protected]_lock: Release wakelock is released
10-09 10:24:50.973 12067 12067 D CacaoService: client delete - pid:12098
10-09 10:24:50.974 1639 1944 I ActivityManager: Process com.sonyericsson.android.camera (pid 12098) has died: fg TOP
10-09 10:24:50.974 1639 1746 I libprocessgroup: Successfully killed process cgroup uid 10064 pid 12098 in 0ms
The short life of the camera app process. 255 ms. Any hint solving those problems will massively improve my development speed, so please get in touch if you have a clue.
Click to expand...
Click to collapse
Really good work bro please keep it up with your work
Nice to see some one will work on stock camera for android 12 xperia 5
Best of luck for next progress
Short status update: It has been a rough few weeks for me in real life so I did not have so much time playing around and ruining my phone. I tried to make the Xperia 5 II stock camera app work, but that one freezes as soon as you capture something - without leaving a trace in the logs.
I also tried decompiling and modifying the Xperia 5 camera app and adding probably missing things to the manifest, but that did not improve anything.
My device bricked twice and I'm currently running out of ideas.
Maybe something worth thinking about is the fact that the error message from my last logcat
Code:
AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
belongs to com.sonymobile.cameracommon which maybe also does not start properly.
I'm not giving up yet, but I'm not too optimistic either.
grisu59964 said:
Short status update: It has been a rough few weeks for me in real life so I did not have so much time playing around and ruining my phone. I tried to make the Xperia 5 II stock camera app work, but that one freezes as soon as you capture something - without leaving a trace in the logs.
I also tried decompiling and modifying the Xperia 5 camera app and adding probably missing things to the manifest, but that did not improve anything.
My device bricked twice and I'm currently running out of ideas.
Maybe something worth thinking about is the fact that the error message from my last logcat
Code:
AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
belongs to com.sonymobile.cameracommon which maybe also does not start properly.
I'm not giving up yet, but I'm not too optimistic either.
Click to expand...
Click to collapse
I think xperia 5ii n xperia 5 have different camera drivers so face freezing during capture any images only slow motion video working in this app
I personally tried it so
Hello @grisu59964
Currently trying the same exercise now.
Could you please provide the shim you created ? I tried to find a github from you but no luck
About the permissions exceptions you are facing, did you try to go in permissive mode ?
Won't solve everything but should help.
nailyk said:
Hello @grisu59964
Currently trying the same exercise now.
Could you please provide the shim you created ? I tried to find a github from you but no luck
About the permissions exceptions you are facing, did you try to go in permissive mode ?
Won't solve everything but should help.
Click to expand...
Click to collapse
You can find my device tree on GitHub. https://github.com/grisumedia/android_device_sony_bahamut
Unfortunately, setting SELinux to permissive did not help either.

Categories

Resources