Database Info

ZTE V975

Hi all.
I have a new ZTE V975 and i have it root and with gapps but i have a problem with Play Store compatibility. "Financial" apps aren´t compatible with the phone. I think that it is a location problem in build.prop
The problem is that i dont know modify it.... can someone see this build.prop archive to see if can change it to improve compatibility?
If someone want to see it i can upload it.
Thx.

gargamelxda said:
Hi all.
I have a new ZTE V975 and i have it root and with gapps but i have a problem with Play Store compatibility. "Financial" apps aren´t compatible with the phone. I think that it is a location problem in build.prop
The problem is that i dont know modify it.... can someone see this build.prop archive to see if can change it to improve compatibility?
If someone want to see it i can upload it.
Thx.
Click to expand...
Click to collapse
Hi gargamelxda,
I've got the same phone and noticed the same thing with certain apps on the play store. Basically what I found was the device was missing a bunch of Google support files that were in GAPPS zip. Now I wasn't able to flash the GAPPS.zip file through the built in recovery as it wasn't signed correctly for this phone and there is no custom recovery available yet.
What I ended up doing is extracting the GAPPS zip file to my SD card then used the root explorer function in ES File Explorer to mount /system as RW and move the majority of the extracted /system files to the same location in the device root /system folder. Couple of things to remember though:
1) Don't overwrite anything that's already there (there was only 2 or 3 files already there by memory)
2) If the folder already exists don't copy the whole folder but rather all the files under that folder as you may either stuff up the folder permissions or create a new folder as the android file are case sensative (eg the folder "Apps" is different to "apps")
3) There are some apk files you won't want to copy like the "onetimeinitializer.apk" file as it will run the google first time initialization next time you reboot which may stuff up your settings (although if you're planning on doing a factory reset after doing this it should be OK and all the changes you've made will stick as they're in the /system folder). I also found that if I copied "LatinIMEDictionaryPack.apk" and "GoogleTTS.apk" they would constantly crash after the reboot.
4)Make sure you set the permissions after you're done copying to "-rw-r-r--" for the files and "drwxr-xr-x" for any new folders you create. you can do this individually with ES File Explorer but if you're ok with linuix command line you can do it in batches (eg all files with the apk extension) via the Android Terminal Emulator app or ADB Shell over a USB connection to a PC. I don't remember the exact command lines I used but if you do some searching on this forum you'll find them easy enough.
After a reboot the apps should now be available to install (at least they were for me) via the Play Store.
Usual disclaimer - If you stuff this up you may brick your device and I'm in no way responsible for it.
Hope that helps
Cheers
Browney

I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !

GlennRunciter said:
I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !
Click to expand...
Click to collapse
Some Qs about this phone,
Does is sync. with google server ? for example does the gmail contacts sync. ok to the phone ?
Did anyone tried to install an email apk (like touchdown) and sync. with exchange server ?
popular apps like whatapp & waze works fine ? any issues with other apps ?
Does the phone has a notification Led ? can it be configured by app. to indicate with desiered color per incoming event ?
thanks!

google play
GlennRunciter said:
I spent a few days trying to install Google Play the cyanogenmod way, following instruction on a spanish site similar to what other's have posted here. The idea is to mount the readonly systemfolder using the bootloader and insert/write systemapps into system/apps
I succeeded but for some reason launching google play was killed instantly by some resident app on the phone.
On the MIUI forum somebody called Eric Xiang built a google play apk that kills the resident blocker and installs googleplay !
xttp://en.miui.com/thread-3998-1-1.html
I now have a fully operational V975 (4.2.2) with the latest official build B06 and google play.
Out of the box the phone is unlocked but not rooted.
To root it, install xttps://dl.dropboxusercontent.com/u/15286951/update.zip using the bootloader (vol+ and power on, when v975 wakes up release power but keep vol+ pressed for a few seconds more, then browse to update.zip. Obviously you preloaded the zip on a sdcard.
If ZTE release firmware B08, you'll have to root it again.
Battery life is excellent, as well as speed, camera, GPS fix is instant. I had a iocean X7 that i killed trying to get the gps working, but v975 feels a lot faster vs the X7's MTK 6589 quadcore 1.5ghz. Granted there's less pixels to move around.
One caveat : iCoyote does not install because of binary incompatibility ? This is an x86 device.
I also discovered the existence of AmazonMarket. Not as complete as GAPPS, but a nice fallback market. And most of the google stuff is installable by apk anyway, so living without GAPPS was not as bad as it looked.
Thx to Eric Xiang, his app prolly opens up all androidphones to googleplay, chinese phones can flood the rest of the world now
the above was two days of research guys, enjoy it !
Click to expand...
Click to collapse
Hey
I'm going to get this phone in the next few days. As far as I know, for 99%, I'm not going to have Google Play on it.
What is the easiest way to install Google Play on it?
I already downloaded B06 since I want to have the latest build.

New ROM´s
Hi, i aplied root, instaled recovery and now search custom ROM´s, Where are thete?

help
Hi... how to root zte v975?
Please help..

Linux on Dex open beta enrollment

https://www.linuxondex.com/beta-registration

does say "Note9 and Tab S4 devices," i signed up this morning with the hope it will come out for s9+ also

Link does not work for me

Hope will work on my s9+ with dockless dex(In pie update). That will be a game changer for our device

No luck for S9+ yet
If only I could trick the play store and download the app

Leonidas87 said:
No luck for S9+ yet
If only I could trick the play store and download the app
Click to expand...
Click to collapse
https://www.apkmirror.com/apk/samsu...inux-on-dex-beta-1-0-38-android-apk-download/

I already sideloaded the apk and it doesn't work on S9/+. The app checks if you have a supported firmware.
I decompiled the apk on my linux machine and am searching where the check is being performed. to see if i can bypass it.
The response message you get is defined as a string that translates back to an id. This id i traced back to EntryActivity.smali alongside a const v2, whatever that might be. Inside this .smali file there are multiple references to versions, processor so this seems to be where the check is called.
Is there anybody here that actually has programming knowledge that could point me in the right direction on how to do this? I've never really looked into the inner workings of an app before, nor did i ever really program anything except some small python projects.

Aerox912 said:
I already sideloaded the apk and it doesn't work on S9/+. The app checks if you have a supported firmware....
Click to expand...
Click to collapse
If you are on android 9 the app opens and lets you use it. I have not loaded a Linux image yet to fully test it.
If you guys missed out on the Android Beta 9 enrollment early today I have uploaded the OTA update here .
https://forum.xda-developers.com/galaxy-s9-plus/how-to/official-android-9-beta-download-t3867703

I installed it on my S9+ and I can't get it to run "Linux on Dex requires device to have the latest software to support some features."

https://www.androidauthority.com/samsung-linux-on-dex-beta-923435/ Looks like the linux apps for this need to support ARM 64-bit architecture.

Leonidas87 said:
No luck for S9+ yet
If only I could trick the play store and download the app
Click to expand...
Click to collapse
Build.prop (?)

Linux image cannot be downloaded on s9+
I have OneUI beta installed on my s9+ and in the official link, the store says the device is not compatible. When you download it via APK mirror, it doesnt allow you install the linux image. The error message is as follows "the web page at lxd-wv=a.samsungknox.com could not be loaded because net:: ERR_CLEARTEXT_NOT_PERMITTED"

Try to download Linux images from :
https://webview.linuxondex.com
Please tell us if it works

Aerox912 said:
I already sideloaded the apk and it doesn't work on S9/+. The app checks if you have a supported firmware.
I decompiled the apk on my linux machine and am searching where the check is being performed. to see if i can bypass it.
The response message you get is defined as a string that translates back to an id. This id i traced back to EntryActivity.smali alongside a const v2, whatever that might be. Inside this .smali file there are multiple references to versions, processor so this seems to be where the check is called.
Is there anybody here that actually has programming knowledge that could point me in the right direction on how to do this? I've never really looked into the inner workings of an app before, nor did i ever really program anything except some small python projects.
Click to expand...
Click to collapse
S9+ on Android P beta, signed up and accepted for LinuxOnDex beta, installed the apk from apkmirror, downloaded the image and extracted to LoD directory. On starting terminal mode I see this in logcat:
Code:
11-29 22:44:17.901 E/AndroidRuntime(23999): FATAL EXCEPTION: main
11-29 22:44:17.901 E/AndroidRuntime(23999): Process: com.samsung.android.lxd, PID: 23999
11-29 22:44:17.901 E/AndroidRuntime(23999): com.samsung.android.lxd.processor.LxdException: undefined model: SM-G965F, star2lte
11-29 22:44:17.901 E/AndroidRuntime(23999): at com.samsung.android.lxd.a.g.c(ModelTypeUtils.java:77)
11-29 22:44:17.901 E/AndroidRuntime(23999): at com.samsung.android.lxd.a.g.a(ModelTypeUtils.java:40)
so it (was) in ModelTypeUtils.java which has been renamed to a method 'c' in class 'com.samsung.android.lxd.a.g'.
But, I'm going to guess that this needs root access to do its low-level linux things, so the edited apk might need to be signed by Samsung to work

Was super excited there for a moment, I downloaded and unzipped the file to the lod folder in my s9+. The app recognized the file and allowed me to create the container. For using linux visually I needed to use DeX but everytime i clicked run black screen appears and immediately crashes. If u r persistent it is just black screen with "please wait".

Linux on Dex S9+ support
Does anyone find a workaround to make Linux on Dex work on the S9+? When loading the container with the Ubuntu image it get sutck on "Please wait" with a black screen...
Btw i'm using the beta 2 with hotfix of Android pie for S9+ with apkmirror Linux on Dex Beta version.

Skimi said:
Does anyone find a workaround to make Linux on Dex work on the S9+?
When loading the container with the Ubuntu image it get sutck on "Please wait" with a black screen...
Click to expand...
Click to collapse
same results here on S9+...
I've downloaded apk and ubuntu 16 image but after loading container and connecting DEX i see only "Please wait..." notification.
(hint: after installing, uninstalling and one more time installing LoD program won't start - i had to delete LoD folder first)

Are you using a official dex accessory or some generic brand?

Skimi said:
Are you using a official dex accessory or some generic brand?
Click to expand...
Click to collapse
Generic with full support for DEX (android desktop works just fine)

I also use acrobat generic adapter with full support for dex, it could be that Linux on Dex it's only supported by the original adapters...

Google Play without Bugs and NETFLIX + ROOT!!!

How to have all Google Play and its services ERROR-free running on our Mate 30 and Mate 30 Pro at a single touch (without Widevine certificate) and with ROOT.
(Netflix only works without certificates, as until now, BUT IT WORKS !!!)
http://www.vmos.com/
Download the APK, install and emulate android WITHOUT problems and with many possibilities ... you can even mess with Xposed !!!
By: Juankar.carrillo (LEON, SPAIN) [emoji2958]
Enviado desde mi Pixel 2 XL mediante Tapatalk

Did anyone try this ?

Yes
viruz1225 said:
Did anyone try this ?
Click to expand...
Click to collapse
Short and sweet... I used on the ZTE Axon 10 Pro
It is android 5.1 rooted running inside your phones operating system.
It works.
You can get to it from your own system and vice versa...
Kinda like running Linux inside of Windows, not dual boot...
Fun to play with, yet not really useful...
No, your actual android is not rooted!
You are relying upon that the app is safe and I have found no one yet to approve this function and the OS 5.1 is very very modified...
But that said: It did work as he said with limitations....I removed it! On my Huawei Mate 30, no way. Too nice of a phone!

I tried to run Bolt (formerly Taxify) on my Mate 30 Pro.
Although it take some time to load VMOS, the functionality I need is satisfactory ?

kreso75 said:
I tried to run Bolt (formerly Taxify) on my Mate 30 Pro.
Although it take some time to load VMOS, the functionality I need is satisfactory ?[/QUOTE
You don't need Vmos to run Bolt.
Click to expand...
Click to collapse

It does not work for me, except if I install "Shared directory error fix" from this thread.
However, when I install the fix, other app stopped working.

kreso75 said:
It does not work for me, except if I install "Shared directory error fix" from this thread.
However, when I install the fix, other app stopped working.
Click to expand...
Click to collapse
I know your issue. I can share with you my GMS apks:
http://s.go.ro/vsk9niug
In this combination 99.99% of aps works.

Do I have only to install those APK's or is there a special installation procedure (like run lmzplay or something similar)?

kreso75 said:
I tried to run Bolt (formerly Taxify) on my Mate 30 Pro.
Although it take some time to load VMOS, the functionality I need is satisfactory ?
Click to expand...
Click to collapse
I used this

kreso75 said:
Do I have only to install those APK's or is there a special installation procedure (like run lmzplay or something similar)?
Click to expand...
Click to collapse
I tried to install your app (Sparkasse...) and it is not working.

badmania98 said:
I tried to install your app (Sparkasse...) and it is not working.
Click to expand...
Click to collapse
Yes, the problem is with "4.SharedLibrary-com.apk.1mirror.gmapjar-1-v1.0.apk".
When I uninstall this (see attached screenshot), Sparkasse app works, but Bolt is automatically uninstalled.
When I try to install Bolt via adb, I'm getting the following:
Code:
adb install "ee.mtakso.client_CA.5.45-528_minAPI16(arm64-v8a,armeabi,armeabi-v7a,mips,x86,x86_64)(nodpi)_apkmirror.com.apk"
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: failed to install ee.mtakso.client_CA.5.45-528_minAPI16(arm64-v8a,armeabi,armeabi-v7a,mips,x86,x86_64)(nodpi)_apkmirror.com.apk: Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY: Reconciliation failed...: Reconcile failed: Package ee.mtakso.client requires unavailable shared library com.google.android.maps; failing!]

Patched Photo Pro 1.2 for non-official systems

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...

Roborock app on a custom ROM

Hi, if anybody is using the Roborock app from playstore installed on a custom ROM, can you share which ROM are you using?
I tried a few ROMs about a year ago, but the app kept crashing.
Roborock – „Google Play“ programos
„App“ gali valdyti „Roborock“ dulkių siurblius iš bet kur, kur yra daug funkcijų.
play.google.com

Did you ever do a LOGCAT to get the very reason why the mentioned app crashes?

xXx yYy said:
Did you ever do a LOGCAT to get the very reason why the mentioned app crashes?
Click to expand...
Click to collapse
I'm no expert with logcat, but I see this:
[04-25 14:38:21.785 20823:20823 W/System.err]
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.tuya.sdk.log.LogPlugin" on path: DexPathList[[zip file "/data/app/com.roborock.smart-1/base.apk"],nativeLibraryDirectories=[/data/app/com.roborock.smart-1/lib/arm, /data/app/com.roborock.smart-1/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]
Attaching the logcat, filtered by "roborock"

My guess is that problem is that mentioned app expects a lib ( what houses the named class ) to exist but that lib doesn't exist elsewhere within Android OS in use, at least not it /system nor in /vendor partition.

xXx yYy said:
My guess is that problem is that mentioned app expects a lib ( what houses the named class ) to exist but that lib doesn't exist elsewhere within Android OS in use, at least not it /system nor in /vendor partition.
Click to expand...
Click to collapse
That would be my guess also, thank you for the logcat suggestion.
If I understand this correctly, the app tries to search for the lib in /data/app/com.roborock.smart-1/lib/arm folder.
Maybe someone who uses the roborock app, could share the contents of this folder? or check if the files match the ones I have:
libTuyaSmartLink.so libjscexecutor.so
libc++_shared.so libjsijniprofiler.so
libcloudsignature-lib.so libjsinspector.so
libfb.so libnative-filters.so
libfolly_futures.so libnative-imagetranscoder.so
libfolly_json.so libnetwork-android.so
libgdx-box2d.so libreactnativeblob.so
libgdx.so libreactnativejni.so
libgifimage.so librrcodec.so
libglog.so libtuyammkv.so
libglog_init.so libv8android.so
libimagepipeline.so libv8executor.so
libjingle_peerconnection_so.so libvorbis-jni.so
libjnimain.so libyoga.so

Hi, i had same crashing problem, but version 2.4.18 is working stable. You can try it. For me is problem solved.

junke17 said:
Hi, i had same crashing problem, but version 2.4.18 is working stable. You can try it. For me is problem solved.
Click to expand...
Click to collapse
Thank you for the reply, version 2.4.18 crashes for me also, what rom are you using?
Edit: version 2.3.46 seems to be working for me.

I have same problem. None of the suggested versions working for me.
If I use roborock app on LineageOS 18.1 official it is working fine. If I try to use it on LineageOS unofficial 19 or 20, it is not working, crashing every time. All ROM are not rooted. Anybody have an idea how to fix it? Or is it a ROM fault?