Related
Hi all,
Right after dealing with rooting and building recovery for the new device (the result is here) I've decided to try go further and port CM10.1. Of course I didn't wait that it appears to be an easy process but some things made me stuck literally on the first steps...
One of the main issues is the porting of HAL modules (/system/lib...). After I just copy RIL modules to the new build of CM10.1 and it worked I was happy and nearly decided that "all this is a piece of cake" but the next step become real pain in the ass: hwcomposer+EGL modules porting. The default software renderer basically works but the colors are incorrect (i.e. yellow instead of blue and so force and so long). When I'm trying to use libGLES_rhea.so from stock system - it does not work ('hwcomposer module not found'). If I try to use the stock libsurfaceflinger.so together with that files it becomes a complete mess:
dlopen("/system/lib/libandroid_servers.so") failed: Cannot load library: soinfo_link_image(linker.cpp:1673): could not load library "libsystem_server.so" needed by "libandroid_servers.so"; caused by soinfo_link_image(linker.cpp:1673): could not load library "libsurfaceflinger.so" needed by "libsystem_server.so"; caused by soinfo_relocate(linker.cpp:1013): cannot locate symbol "_ZNK7android14SurfaceTexture4dumpERNS_7String8EPKcPcj" referenced by "libsurfaceflinger.so"...
Click to expand...
Click to collapse
So the question is: Is there any description of the HAL modules porting (some links or documentation)? Or any other resources which can help me?
I'll be really appreciated for any help regarding this.
Regards,
BR
Until today, coriplus' EGL is still a trouble...
***Posting this on behalf of current CM developer for this device***
Source can be found at https://github.com/CyanogenMod
This is a unified build for Moto X
To build CyanogenMod for yourself you can follow http://wiki.cyanogenmod.org/w/Build_for_moto_msm8960dt
If you'd rather not extract files from the latest CyanogenMod build you can add vendor.xml to your .repo/local_manifests folder.
It's been confirmed to work on both the 4.3 and 4.4 bootloaders.
Details on Installing and downloading CyanogenMod can be found here: http://wiki.cyanogenmod.org/w/Moto_msm8960dt_Info
Official nightlies can be downloaded here: http://download.cyanogenmod.org/?device=ghost
Gapps: http://wiki.cyanogenmod.org/w/Gapps
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_moto_msm8960dt
Changelog: http://www.cmxlog.com/11/moto_msm8960dt/
Before you post a bug report:
Please ensure you have done a full wipe of data and formated system under Mounts and Storage.
If you have flashed parts for other versions you may need to do a full flash of the factory software for your model and start clean.
Do not report bugs in nightlies to jira.cyanogenmod.org
Enjoy!
Already known bugs
So, already known bugs:
1. Speakerphone did not work.
2. GPS sometimes do not find satellites.
3. Video camera have only CIF and QVGA resolution of video quallity.
Also, no external audio at all (speaker, ringer, etc) for the xt1030.
Sent from my unknown using Tapatalk
Rottgrub said:
Also, no external audio at all (speaker, ringer, etc) for the xt1030.
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Strange. Bootloader unlocked?
da900 said:
Strange. Bootloader unlocked?
Click to expand...
Click to collapse
Yep, unlocked boot loader. It seems to happen with all of the CM11 based ROMs on the Droid Mini.
That said, headphone audio works fine. I haven't tested bluetooth audio, but I can test that later today.
I'd be happy to run any tests, or provide logcat info if you like. Just let me know.
I am not a dev. Post logcat here. Dhacker will see it and will be able to isolate the problem.
Will this work on unlocked xt1055 US cellular CDMA version?
Sent from my XT1055 using Tapatalk
khanapurechait said:
Will this work on unlocked xt1055 US cellular CDMA version?
Sent from my XT1055 using Tapatalk
Click to expand...
Click to collapse
Codename: moto_msm8960dt
Also known as: ghost, obake-maxx
Vendor: Motorola
Release Date: 2013 Aug 23
Carrier: TMobile, International GSM, Verizon, US Cellular, Sprint
From the link in the OP it says it will: http://wiki.cyanogenmod.org/w/Moto_msm8960dt_Info
Hi I'm using the new PA google camera and I found that de back camera has the CIF QVGA and QCIF resolution and front camera has 1080p resolution, this may addres the issues taking videos with the back camera.
Hope this helps to developers.
I'm using Liquid rom right now.
Videocamera fix
Hi, guys and girls. Seems like I have managed to fix video camera to recocord 1080p and 720p videos and also front video camera, wich can record up to 720p now. I was rying to make front camera record also 1080p videos as on stock ROMs it can do so, but did not find a solution at the moment.
Proof is in the screenshots.
How to;
1. Download attached media-profiles.zip and extract xml file
2. Copy to Sdcard
3. Using any root file manager (I use RootExplorer) go to /system/etc
4. Copy downloader media-profiles.xml to this location and agree with the replacement.
5. Set permissions rw--r--r--
6. Reboot
7. Enjoy fully functional AOSP camera
P.S. If anyone is familiar with gerrit and/or github, please, add this fix to msm8960dt cm source code.
P.P.S. Finaly managed to add 1080p front camera recording.
da900 said:
I am not a dev. Post logcat here. Dhacker will see it and will be able to isolate the problem.
Click to expand...
Click to collapse
Appreciate the advice nevertheless.
Motorola driver decided to be a jerk, so the logcat took me longer than expected. This is the xt1030 Droid Mini, unlocked bootloader, running a clean install of CM11, no gapps package, as of a few days ago. Clean booted the phone, played with the volume controls, and sound ringtone selector.
The bug: No external audio at any point. Headphones work, however.
http://pastebin.com/Q4qjZYbv
If someone takes a look, and wants further tests, please let me know. Be happy to dig into the issue.
Cheers!
-- after rooting around --
Looking it over, since it seems to be horking out around here:
Code:
D/ALSADevice( 347): ALSA module opened
D/AudioHardwareALSA( 347): AudioHardware: DLOPEN successful for ACDBLOADER
E/ ( 347): 2 (No such file or directory) opendir /sys/kernel/debug/asoc/msm8960-tabla1x-snd-card/msm8960-snd-card failed
E/ ( 347): failed to get Peek and Poke names
E/ ( 347): [ACDB RTC]->rtc init done!->result [0]
E/ ( 347): [ACDB ACPH]->actp diag init done!
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -8
E/ACDB-LOADER( 347): done with conversion, anc config size is 148
I've included the contents of that directory structure in case it's useful. Looks like the directory it's looking for is at:
/sys/kernel/debug/asoc/msm8960-snd-card
But that's just a guess without looking directly at the code, which I may do.
http://pastebin.com/HdyCwLyx
Rottgrub said:
Appreciate the advice nevertheless.
Motorola driver decided to be a jerk, so the logcat took me longer than expected. This is the xt1030 Droid Mini, unlocked bootloader, running a clean install of CM11, no gapps package, as of a few days ago. Clean booted the phone, played with the volume controls, and sound ringtone selector.
The bug: No external audio at any point. Headphones work, however.
http://pastebin.com/Q4qjZYbv
If someone takes a look, and wants further tests, please let me know. Be happy to dig into the issue.
Cheers!
--
Looking it over, since it seems to be horking out around here:
Code:
D/ALSADevice( 347): ALSA module opened
D/AudioHardwareALSA( 347): AudioHardware: DLOPEN successful for ACDBLOADER
E/ ( 347): 2 (No such file or directory) opendir /sys/kernel/debug/asoc/msm8960-tabla1x-snd-card/msm8960-snd-card failed
E/ ( 347): failed to get Peek and Poke names
E/ ( 347): [ACDB RTC]->rtc init done!->result [0]
E/ ( 347): [ACDB ACPH]->actp diag init done!
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -8
E/ACDB-LOADER( 347): done with conversion, anc config size is 148
I've included the contents of that directory structure in case it's useful. Looks like the directory it's looking for is at:
/sys/kernel/debug/asoc/msm8960-snd-card
But that's just a guess without looking directly at the code, which I may do.
http://pastebin.com/HdyCwLyx
Click to expand...
Click to collapse
Guess I found a solution for you. Open zip with CM11 nightly. Go to system and find a folder called xt1080. Open it. You will see 3 folders. Extarct them. Then using any root file manager copy files from every folder to /sytem/bin, /system/etc, /system/lib. Extracted folders have the same names. Set permissions. Reboot.
da900 said:
Guess I found a solution for you. Open zip with CM11 nightly. Go to system and find a folder called xt1080...
Click to expand...
Click to collapse
Unfortunately, I've already tried those files with no luck. Appreciate the idea though.
Sent from my Xperia Sola using Tapatalk
Rottgrub said:
Unfortunately, I've already tried those files with no luck. Appreciate the idea though.
Sent from my Xperia Sola using Tapatalk
Click to expand...
Click to collapse
Then just extract the same files from your stock ROM.
da900 said:
Then just extract the same files from your stock ROM.
Click to expand...
Click to collapse
Tried that as well, unfortunately.
Sent from my Xperia Sola using Tapatalk
da900 said:
Hi, guys and girls. Seems like I have managed to fix video camera to recocord 1080p and 720p videos and also front video camera, wich can record up to 720p now. I was rying to make front camera record also 1080p videos as on stock ROMs it can do so, but did not find a solution at the moment.
Proof is in the screenshots.
How to;
1. Download attached media-profiles.zip and extract xml file
2. Copy to Sdcard
3. Using any root file manager (I use RootExplorer) go to /system/etc
4. Copy downloader media-profiles.xml to this location and agree with the replacement.
5. Set permissions rw--r--r--
6. Reboot
7. Enjoy fully functional AOSP camera
P.S. If anyone is familiar with gerrit and/or github, please, add this fix to msm8960dt cm source code.
P.P.S. Finaly managed to add 1080p front camera recording.
Click to expand...
Click to collapse
Is this working for anyone else? My camera still just freezes up when you try to record which is why I removed those resolutions.
---------- Post added at 08:27 PM ---------- Previous post was at 08:08 PM ----------
da900 said:
Guess I found a solution for you. Open zip with CM11 nightly. Go to system and find a folder called xt1080. Open it. You will see 3 folders. Extarct them. Then using any root file manager copy files from every folder to /sytem/bin, /system/etc, /system/lib. Extracted folders have the same names. Set permissions. Reboot.
Click to expand...
Click to collapse
Yeah the unified build isn't set up to recognize Droid Mini. Can you send me the output of:
adb shell
Code:
getprop
cat /proc/cmdline
dhacker29 said:
Yeah the unified build isn't set up to recognize Droid Mini. Can you send me the output of:
adb shell
Code:
getprop
cat /proc/cmdline
Click to expand...
Click to collapse
Happily. I appreciate you looking into it. I restored to stock 4.4, added root, and pulled the below:
xt1030 Stock 4.4: getprop
http://pastebin.com/F0AtmxXU
xt1030 stock 4.4: /proc/cmdline
http://pastebin.com/0ELEb8tk
Let me know if you need anything else.
da900 said:
Hi, guys and girls. Seems like I have managed to fix video camera to recocord 1080p and 720p videos and also front video camera, wich can record up to 720p now. I was rying to make front camera record also 1080p videos as on stock ROMs it can do so, but did not find a solution at the moment.
Proof is in the screenshots.
How to;
1. Download attached media-profiles.zip and extract xml file
2. Copy to Sdcard
3. Using any root file manager (I use RootExplorer) go to /system/etc
4. Copy downloader media-profiles.xml to this location and agree with the replacement.
5. Set permissions rw--r--r--
6. Reboot
7. Enjoy fully functional AOSP camera
P.S. If anyone is familiar with gerrit and/or github, please, add this fix to msm8960dt cm source code.
P.P.S. Finaly managed to add 1080p front camera recording.
Click to expand...
Click to collapse
Tried your solution and two things happend to me, the first one is that no longer had wifi and the second one is that did nit work your solution every time I opened the google camera failed.
did I miss something?
have google now?
if google now worked, this rom will be perfect!!!
http://www.cmxlog.com/11/moto_msm8960dt/
TiagoRigueto said:
have google now?
if google now worked, this rom will be perfect!!!
http://www.cmxlog.com/11/moto_msm8960dt/
Click to expand...
Click to collapse
It works and can be installed from google play
As the title say, someone got into my phone.
Now, i am not a geek but I have learned some stuff throughout the years since I've been using Android. Recently I have recognized some new system apps on my phone which they were not installed by me. I did'nt panic, quickly removed my sd card erased all content and set it up as new phone. I did'nt signed into google play store or downloaded any apps, and I have kept my sd card out of the phone. So I just used the phone for text message, and calls. Just for fun (since I knew that I will erase all the content, I choosed to be a developer and started remove permissions from a lot of apps and soon enough I found something interesting in my download folder which was a pdf file, which you will see in a moment.
English is not my first language but I understood that it has someones report maybe generated I dont know. But I have a few questions.
What is this about?
Who might have been created this?
Who is that for? (Some kind of a report?)
Thanks a lot!
(This is an extract from a pdf file)
`2020年01月02日 04:05:16 Product Model: BV5500Pro,android: 9 versionCode = Unable to start activity ComponentInfo{com.mediatek.camera/com.mediatek.camera.CameraActivity}: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked StackTrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mediatek.camera/com.mediatek.camera.CameraActivity}: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2947) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3101) at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78) at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java: 108) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:193) at android.app.ActivityThread.main(ActivityThread.java:6724) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911) Caused by: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:420) at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:405) at android.content.ContextWrapper.getSharedPreferences(ContextWrapper.java:174) at android.preference.PreferenceManager.getDefaultSharedPreferences(PreferenceManager.java:526) at com.mediatek.camera.common.relation.DataStore$SharedPreferencesWrapper.getPreferencesFromSco pe(DataStore.java:287) at com.mediatek.camera.common.relation.DataStore$SharedPreferencesWrapper. (DataStore.java:240) at com.mediatek.camera.common.relation.DataStore.getSharedPreferencesWrapperSync(DataStore.java :200) at com.mediatek.camera.common.relation.DataStore.getValue(DataStore.java:171) at com.mediatek.camera.common.mode.CameraModeBase.getDeviceUsage(CameraModeBase.java:274) at com.mediatek.camera.common.mode.ModeManager.createDeviceUsage(ModeManager.java:307) at com.mediatek.camera.common.mode.ModeManager.create(ModeManager.java:137) at com.mediatek.camera.CameraActivity.onCreateTasks(CameraActivity.java:198) at com.mediatek.camera.PermissionActivity.onPermissionCreateTasks(PermissionActivity.java:103) at com.mediatek.camera.QuickActivity.onCreate(QuickActivity.java:129) at android.app.Activity.performCreate(Activity.java:7136) at android.app.Activity.performCreate(Activity.java:7127) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927) ... 11 more
Hi
I'm not a pro too, but looks like a log file from an app written in Java for me... Not neccessarily a threat, it uses the camera and some standard system stuff, afaik. Can't tell you more either, sorry.
TL;DR : working photo pro for systems without Sony telemetry services: AFH
Hey guys I've been running a GSI of Descendant OS on my Xperia 5 II and I have been trying to get this photo pro app to work. All the versions I found on apkmirror crashes on launch, not to mention the ones that refuse to install. So after tinkering with some magisk modules I decided to decompile it and see what's going on inside. After a bit of log checking, I discovered some unimplemented telemetry functions which seems to be the cause of those crashes. After patching these the app runs like how it should be. I also removed the restrictions in AndroidManifests.xml that prevents the app to be installed on devices without com.sony.device lib, so any system should be able to install it just fine (not sure why Sony set restrictions for photo pro but not cinema pro).
Let me know if there's more issues to be solved
I've been running the APK from Photopro III for months and have had no significant issues. I got my APK from, I think, ADK.
2nd post down its from the Xperia 1 iii
@hx64 any chance for a patch for the latest version, or a guide as to how to patch it?
That would be awesome!
SeventhRaven said:
@hx64 any chance for a patch for the latest version, or a guide as to how to patch it?
That would be awesome!
Click to expand...
Click to collapse
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
hx64 said:
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
Click to expand...
Click to collapse
I tried working on that by simply removing the requirements (although I actually have zero development experience), but I would always get a parsing error (probably an issue with the signing? No idea how to do that properly) when trying to install it.
As for the unmodified version, I cannot install it at all, as it says it's not compatible. So a crash technically never occurs.
But I don't mind waiting for a patch. Just glad to see it's an option still.
SeventhRaven said:
I tried working on that by simply removing the requirements (although I actually have zero development experience), but I would always get a parsing error (probably an issue with the signing? No idea how to do that properly) when trying to install it.
As for the unmodified version, I cannot install it at all, as it says it's not compatible (using a custom ROM). So a crash technically never occurs.
But I don't mind waiting for a patch. Just glad to see it's an option still.
Click to expand...
Click to collapse
Oh I forgot to mention the install issues. There's a `use-library` line in the AndroidManifest.xml that requires the `com.sony.device` library which you'll need to remove in order to install it on non-official systems.
And be sure to use deCOMPILE tools first (it won't work if you deCOMPRESS and edit since a signature is required), google for apktool or check out the apklab github page. I have little java knowledge previously but in this case fortunately you don't need much
I'll try switching to my dev environment as soon as possible.
hx64 said:
Oh I forgot to mention the install issues. There's a `use-library` line in the AndroidManifest.xml that requires the `com.sony.device` library which you'll need to remove in order to install it on non-official systems.
And be sure to use deCOMPILE tools first (it won't work if you deCOMPRESS and edit since a signature is required), google for apktool or check out the apklab github page. I have little java knowledge previously but in this case fortunately you don't need much
I'll try switching to my dev environment as soon as possible.
Click to expand...
Click to collapse
Yeah I tried apktool and I guess I recompiled it with Android Studio. All I changed was setting the requirement for com.sony.device lib to false.
I'll try my luck with the tool you've linked, thanks!
hx64 said:
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
Click to expand...
Click to collapse
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
(I didn't touch anything else, though...so idk about analytics, but I firewall apps anyway so not like it can send anything)
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
Click to expand...
Click to collapse
Nice work!
Glad I could help xD
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
Click to expand...
Click to collapse
Any chance someone could do this for the Video Pro app (1.0.a.0.26)?
I took a shot at trying to mod the apk..
I successfully installed with the Manifest.xml library edit, but upon crashing here's my log:
Code:
04-27 16:54:12.702 8085 8148 E AndroidRuntime: FATAL EXCEPTION: IddManagerThread
04-27 16:54:12.702 8085 8148 E AndroidRuntime: Process: jp.co.sony.mc.videopro, PID: 8085
04-27 16:54:12.702 8085 8148 E AndroidRuntime: java.lang.RuntimeException: Not an implementation
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at com.sonyericsson.idd.api.Idd.addEvent(Idd.java:114)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.addAppData(IddManager.kt:99)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.handleMessage(IddManager.kt:88)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.access$handleMessage(IddManager.kt:17)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager$Companion$init$1$1.handleMessage(IddManager.kt:50)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
And this is where I get lost. Swapping the throw code in com.sonyerricsson.idd.api.Idd doesn't seem to solve the crashes, and I'm not sure where to go next. I don't see any HandlerThread or loop smali files, and in jp.co.sony.mc.videopro.idd.core.IddManager, I'm not familiar with the code in the lines where the errors are defined.
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
(I didn't touch anything else, though...so idk about analytics, but I firewall apps anyway so not like it can send anything)
Click to expand...
Click to collapse
Just installed your patched version on the latest Pixel Experience GSI (v414/June security patch) on a Xperia 1 III and it worked perfectly including bokeh.
Any chance you'll be sharing patched versions of more recent releases of the app?
Thanks!
Patched version of the latest (1.4.A.0.20-2621460) attached.
Thanks for your work around this @hx64.
@delfuhd I also could not untangle the logcat so I ended up replacing all instances of 'throw p0' in com.sonyericsson.idd.api.Idd with 'return-void' and there doesn't seem to be an issue (yet).
Is the app asking for some Sony exclusive features? I mean, do we lose something like postprocessing or image management? thanks!
Not working
Double post.
The 70mm lens causes the app to crash in Auto mode in every 1.4 and 1.5 version I tested. The only one that seems to work is the older 1.3 version.
Still here is the latest patched 1.5 version that I tried. Thanks for the guide above!
cari66eam said:
The 70mm lens causes the app to crash in Auto mode in every 1.4 and 1.5 version I tested. The only one that seems to work is the older 1.3 version.
Still here is the latest patched 1.5 version that I tried. Thanks for the guide above!
Click to expand...
Click to collapse
Thank you so much for providing the patched version!!! I'm on lineageos 20, no gapps etc. and the 1.2 works great. Haven't tried 1.3, but 1.4 and 1.5 don't work for me...
Hello. I'm "slightly" out of my depth here, unfortunately. The aforementioned app (Chess Tactics Pro) suddenly became "incompatible with my device" and so unavailable in play store, I therefore had to extract the apk file from another phone. In fact, I tried 3 different versions of this app. It installs alright and works to some extent, only when I want to use computer analysis function, it crashes. The crash report reads:
java.lang.UnsatisfiedLinkError: dlopen failed: library "liblrengine.so" not found
at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
at java.lang.System.loadLibrary(System.java:1664)
at net.lrstudios.android.chess_problems.chess.engines.LREngine.<clinit>(SourceFile:1)
at h.a.a.a.g.c.T(SourceFile:2)
at h.a.a.a.g.c.W(SourceFile:1)
at h.a.a.a.g.c.onOptionsItemSelected(SourceFile:8)
at androidx.fragment.app.Fragment.performOptionsItemSelected(SourceFile:3)
at c.j.d.k.A(SourceFile:3)
at c.j.d.f.k(SourceFile:1)
at c.j.d.c.onMenuItemSelected(SourceFile:3)
at c.b.k.c.onMenuItemSelected(SourceFile:1)
at c.b.p.i.onMenuItemSelected(SourceFile:1)
at c.b.p.i.onMenuItemSelected(SourceFile:1)
at c.b.k.j$b.onMenuItemClick(SourceFile:1)
at androidx.appcompat.widget.Toolbar$a.onMenuItemClick(SourceFile:2)
at androidx.appcompat.widget.ActionMenuView$d.a(SourceFile:2)
at c.b.p.j.g.h(SourceFile:1)
at c.b.p.j.i.k(SourceFile:2)
at c.b.p.j.g.O(SourceFile:3)
at c.b.p.j.g.N(SourceFile:1)
at androidx.appcompat.widget.ActionMenuView.a(SourceFile:1)
at androidx.appcompat.view.menu.ActionMenuItemView.onClick(SourceFile:2)
at android.view.View.performClick(View.java:7509)
at android.view.View.performClickInternal(View.java:7486)
at android.view.View.access$3600(View.java:841)
at android.view.View$PerformClick.run(View.java:28720)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8056)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)
Click to expand...
Click to collapse
The phone: vayu (Poco X3 Pro), stock rom, rooted with magisk. On another vayu with the same system (MIUI 11.5), unrooted, it works fine, as it does on 2 other phones with lineageos, both rooted, Android 10 and 11 respectively, and still available in play store. What am I missing? Do you have any ideas what I can try? What does the crash report say? Let me add that the app folder contains like 5 .apk files out of which I only installed base.apk . What are the other apks for? I hope someone can help me with this.
IMO the correct method to get the very reason why an app crashes is to do a LOGCAT.
Thanks. I'll look into it but for now I'm rather busy so it'll have to wait a bit.
It seems that a shared library file, liblrengine.so, is missing.
I appreciate your input but can't check if it works right now as in the meantime I've switched to LineageOS, used SAI to move the whole split package from another phone, but it doesn't work either, complaining that google play store might not be installed or sth to this effect. Anyway, I must install Android Studio and learn how to use logcat, cause other apps also give me problems.
Solved for now. Back to MIUI as LineageOS+MindTheGapps combo misses some dependencies apparently, so the app backed up by SAI wouldn't work there but it works fine in MIUI.