Database Info

[Q] Google Talk crashes when clicking a link

Trying to open any links sent to me via Google Talk crashes the app with the generic "Unfortunately, Google Talk has stopped."
I just flashed Android Revolution HD last night.

Did you do "Superwipe" before flashing this ROM?

I did, it said there were no problems.

So, as an update, I SuperWiped twice and re-flashed. Gtalk still crashed when clicking a link.
I decided I'd use BeejiveGT as a "for now" solution. Clicking a link in there, however, still crashed the program. BUT! Beejive was nice enough to leave a crash report. Hopefully someone smart can tell me what's going wrong and how to fix it
Report collected on Wed Jun 20 07:51:32 EDT 2012
System Info :
==============
deviceID= 355066040364582_c799cf5d0e73e026_GTALK
versionName= 3.5.7
deviceModel= HTC Sensation 4G
osBuildBrand= tmous
deviceOS= 4.0.3
deviceDisplay= IML74K
deviceHost= ABM011
deviceBuildID= IML74K
deviceBuildModel= HTC Sensation 4G
deviceBuildUser= root
deviceManuacturer= HTC
apphash= PKF6dH2ES10HzdnU940CXA==
Total Internal memory : 1233059840
Available Internal memory : 240840704
Stack :
=======
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.htc.HtcLinkifyDispatcher/com.htc.HtcLinkifyDispatcher.HtcLinkifyDispatcherActivity}; have you declared this activity in your AndroidManifest.xml?
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1634)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1510)
at android.app.Activity.startActivityForResult(Activity.java:3244)
at com.beejive.im.controller.AbstractBeejiveActivity.startActivityForResult(AbstractBeejiveActivity.java:151)
at android.app.Activity.startActivity(Activity.java:3351)
at com.beejive.im.controller.AbstractBeejiveActivity.startActivity(AbstractBeejiveActivity.java:145)
at android.text.style.LinkifyURLSpan.onClick(LinkifyURLSpan.java:73)
at android.text.method.LinkMovementMethod.onTouchEvent(LinkMovementMethod.java:212)
at android.widget.TextView.onTouchEvent(TextView.java:8776)
at android.view.View.dispatchTouchEvent(View.java:5579)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1983)
at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1442)
at android.app.Activity.dispatchTouchEvent(Activity.java:2414)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1931)
at android.view.View.dispatchPointerEvent(View.java:5759)
at android.view.ViewRootImpl.deliverPointerEvent(ViewRootImpl.java:2963)
at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2522)
at android.view.ViewRootImpl.processInputEvents(ViewRootImpl.java:862)
at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2531)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:4944)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
Cause :
=======
**** End of current Report ***
Click to expand...
Click to collapse

Same problem
Also experiencing the same problem on the desire S after installing the ICS RUU update. Anyone know of a solution?

[Q] Google Play Store Doesn't Open

So, in the end of the past year I have finally got to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, because this replica comes with almost no internal space, although I thought I was removing only unnecessary apps. I removed two that should not have been removed, the phone started to act erratically, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my first moment of despair, I tried to solve it, throwing everything back on it, that stopped the blinking screen and showed the apps shortcuts on the main screen again. Then I started removing one app at time interspersed with a reboot. After removing what I didn't want left, except the only two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed up internal space, only to discover that it simply didn't open anymore.
At first it would load, then show the upgrading screen (from market to play store) and when I tapped *continue" the app would just shutdown, and I was back at the app launcher, then I tried again just to even attempt open the app, the screen would change to the loading, but very quickly, it would shutdown again.
After my second moment of despair, I tried installing apps via ADB, and it worked, and so did the apps, every app that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, which was not an update but it was better than have to install anything via ADB. Then I tried to launch one of those apps, only to discover that my browser would crash with a F/C when I tapped save in the download pop-up.
After weeks searching for solutions and for any clue in this issue, I discovered that within the Dropbox's application directory contained a lot of .txt files.
Reading these files, I discovered what is causing the malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this.
Following below are some examples of the .txt files:
Location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3690)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or how to solve it? I really want this to work and despite it is taking up all of my free time, and I cannot come up with a solution.
Thanks in advance
Sorry for the bad English.
Hugo Bler

What were the two apps removed?
H_Bler said:
So, in the and of the past year i've get to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, 'cause this replicas come with almost none internal space, althogh I thought I was removing only unecessary apps, I removed two that wasn't sopposed to be removed, the phone bricked, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my depair, I tried to solve it, throwing everything back on it, what stopped the blinking screen and showed the apps shortcuts in the main screen again. Then I started removing one app at time interspersed with a reboot, after removing what I didn't want lefting only that two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed internal space, only to discover that it simply didn't open anymore, at first it would load, then show the upgrading screen (from market to play store) and when I touched "continue" the app would shutdown, and I was back at the app luncher, then I tried again just to it don't even open, the screen would change to the loading, but in notime it would shutdown again.
After my second despair, I tried installing apps via ADB, and it worked, and so did the apps, everyone that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, wich wasn't an autoupdate but it was better than have to install anything via ADB. Then I tried it, only to discover tha my browser would crash an FC when I thouched save in the download pop-up.
After weeks seeking solutions and searching any clue in the phone root directories, if found the Dropbox directory that contain a lot of .txt files.
Reading this files I discoverd what is causing de malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this, following below are some exemples of the .txt files:
location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3690)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or How to sove it? I really want to this, it's taking all my free time, and I can't come up with a solution.
Thanks in advance
sorry for the bad english.
Hugo Bler
Click to expand...
Click to collapse
Hello Hugo, total noob here. Thanks for informing us of your issue. I'm almost near the rooting process, I'm pretty sure we have the same unit. Just out of curiousity, what were the two apps you removed that caused your phone to malfunction?
I'm still stuck with rooting the device because everytime I use the DOOMTOOL I get up to the point where it says, "read only memory"... As previously discussed in the other thread: http://forum.xda-developers.com/showthread.php?t=2061069&page=4
Thanks for all your inputs... I'm so confused with these China clones

It seems to me you should just do a factory reset if that is an option.

Yeah...
rpjwalter said:
It seems to me you should just do a factory reset if that is an option.
Click to expand...
Click to collapse
I've tried that, three times actually, after I pushed back those two apps in the /system/app directory, I did a factory reset, but it didn't work :/

SOLVED.
H_Bler said:
So, in the end of the past year I have finally got to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, because this replica comes with almost no internal space, although I thought I was removing only unnecessary apps. I removed two that should not have been removed, the phone started to act erratically, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my first moment of despair, I tried to solve it, throwing everything back on it, that stopped the blinking screen and showed the apps shortcuts on the main screen again. Then I started removing one app at time interspersed with a reboot. After removing what I didn't want left, except the only two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed up internal space, only to discover that it simply didn't open anymore.
At first it would load, then show the upgrading screen (from market to play store) and when I tapped *continue" the app would just shutdown, and I was back at the app launcher, then I tried again just to even attempt open the app, the screen would change to the loading, but very quickly, it would shutdown again.
After my second moment of despair, I tried installing apps via ADB, and it worked, and so did the apps, every app that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, which was not an update but it was better than have to install anything via ADB. Then I tried to launch one of those apps, only to discover that my browser would crash with a F/C when I tapped save in the download pop-up.
After weeks searching for solutions and for any clue in this issue, I discovered that within the Dropbox's application directory contained a lot of .txt files.
Reading these files, I discovered what is causing the malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this.
Following below are some examples of the .txt files:
Location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3690)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or how to solve it? I really want this to work and despite it is taking up all of my free time, and I cannot come up with a solution.
Thanks in advance
Sorry for the bad English.
Hugo Bler
Click to expand...
Click to collapse
SOLVED.
The issue was caused by lack of a system application, the application "donwloadprovider.apk".
The problem was identified by comparing the "/system/app" directory in two similar devices, and noticing that the application was missing.
The solution:
Copy the application from the working device(A) to a computer.
Push via ADB the application to the malfunctioning device (B) "/system/app" directory.
Reboot device B.
Thanks Everyone for the help.
Especial thanks to Chico_PinoyCracker, Since he's the owner of "Device A".
Thanks Man.

[PORT][HELP NEEDED] MIUI 6 Port from Mi4W

Hey there, I'm trying to port MIUI 6 from MI4 to our OnePlusOne. Of course it bootloops and maybe someone here may got some idea.
What I did :
On base ROM ( CM11 M11 ), deleted
/system/app
/systel/priv-app
/system/media
/system/font
/system/framework
I replaced by the ported ROM ( Mi4/MI3W MIUI 6 5.1.23 )
I added missing libs from port to base without replace
I replaced libdvm.so and libjavacore.so by the one from ported rom
I replaced framework.jar with the one from CM 11 ( base ) ROM.
(I didnt get to fix errors from framework until replace it entirely)
I edited bootclasspath to the one from MIUI 6 kernel
I replaced updater-script permissions set
Here's the log : http://cjoint.com/?EBsm3ZvDkv7
Main error for me :
F/libc ( 3863): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3863 (zygote)
Here's the ROM : https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
Base link : http://download.cyanogenmod.org/get/jenkins/86415/cm-11-20141008-SNAPSHOT-M11-bacon.zip
Port link : https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing ( Uploading )
Thanks for any help or suggestion.

If you do upload, I would be grateful
Thanks

The libnetcmdiface errors are bogus material. You can, more often than not, ignore those.

MrColdbird said:
The libnetcmdiface errors are bogus material. You can, more often than not, ignore those.
Click to expand...
Click to collapse
Yes. I saw this. Thanks for reply anyway
luigirenna said:
If you do upload, I would be grateful
Thanks
Click to expand...
Click to collapse
I will upload it
Tapatalké depuis mon OnePlus One MIUI !

@Kingzak34
off topic Q
Which version of AK you are using with MIUI 5 on OPO?

sajid533 said:
@Kingzak34
off topic Q
Which version of AK you are using with MIUI 5 on OPO?
Click to expand...
Click to collapse
77 CM11

Miui V6
try to see here
http://en.miui.com/thread-84084-1-1.html

luigirenna said:
try to see here
http://en.miui.com/thread-84084-1-1.html
Click to expand...
Click to collapse
I saw this, but it's broken, and doesnt even work with multirom.
I want to try to port myself for now.
I didnt not upload my work yet, cause I started over from scratch, and I didnt fix enough for now.

I am also experimenting with Mi4W rom to make a port. trying in multi rom. stuck in boot step

sajid533 said:
I am also experimenting with Mi4W rom to make a port. trying in multi rom. stuck in boot step
Click to expand...
Click to collapse
Boot animation or before ? Got logcat ?

V6
I tried the version, actually the Wi-Fi and the camera did not work.
I guess with a logcat active (I hope) to see why it does not work.
There are problems with shutting down.
but it's a good start.:good:

Here is my last-kmsg file when I booted with miui 6 with official miui5 rom boot.img
No bootloop. No boot animation
Just stuck at one+ logo
https://mega.co.nz/#!Ghp01JwB!sK6FhYyf6xYZ2c_OgdI66fvoCrv6rAooCek71Ty3jmI
Sent from my One+ using XDA Free mobile app

My ROM is uploading.

Kingzak34 said:
My ROM is uploading.
Click to expand...
Click to collapse
Problem solved? how?

No its not solved. It's still on the same state.
Dalvik VM starts working then fatal signal from libc
Tapatalké depuis mon OnePlus One MIUI !

Here will be the ROM when uploaded :
https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
WARNING : Remember that ROM doesnt boot and it's only for work.
I updated logcat on 1st post. Here we are for now.

Kingzak34 said:
I saw this, but it's broken, and doesnt even work with multirom.
I want to try to port myself for now.
I didnt not upload my work yet, cause I started over from scratch, and I didnt fix enough for now.
Click to expand...
Click to collapse
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??

jamal2367 said:
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??
Click to expand...
Click to collapse
stop talking.
Kingzak34 said:
Here will be the ROM when uploaded :
https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
WARNING : Remember that ROM doesnt boot and it's only for work.
I updated logcat on 1st post. Here we are for now.
Click to expand...
Click to collapse
this mostly refers to missing resources, but i'm not quite sure atm :/
Code:
F/libc ( 3894): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3894 (zygote)
maybe to:
Code:
D/idmap ( 3992): error: no read access to /vendor/overlay: No such file or directory
and:
Code:
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-2.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-2.apk'
try move this stuff to data and reboot, want to see the log if the files are present

OldDroid said:
this mostly refers to missing resources, but i'm not quite sure atm :/
Code:
F/libc ( 3894): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3894 (zygote)
Click to expand...
Click to collapse
For this one, I must give some search on internet, I saw many people having this but didnt find solution for now.
OldDroid said:
Code:
D/idmap ( 3992): error: no read access to /vendor/overlay: No such file or directory
Click to expand...
Click to collapse
There is no overlay folder or file in vendor folder of both ROM. I think it can be ignored. ( But I may be wrong )
OldDroid said:
Code:
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-2.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-2.apk'
try move this stuff to data and reboot, want to see the log if the files are present
Click to expand...
Click to collapse
These, are written in the bootclasspath of MIUI ROM ( so it's looking for it ), but doesnt exist in the ROM. I saw same kind of errors on a working ROM, so I think it can be ignored too.

jamal2367 said:
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??
Click to expand...
Click to collapse
I want to work on my ROM. I need my phone working so I use mine that works with multirom.

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

Question Camera problem

Hi guys, I have a problem with my camera, it doesn't work anymore in aosp and in miui it only opens in video recording mode and with monochrome colors, on gcam everything works, but with monochrome colors too, I've done everything I could imagine trying to fix this, but nothing went right, does anyone have an idea what it is?
I have the error log when I try to open the camera, if anyone can help, I appreciate it.
io.reactivex.exceptions.OnErrorNotImplementedException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
at io.reactivex.internal.observers.LambdaObserver.onError(Unknown Source:13)
at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:25)
at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(Unknown Source:47)
at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(Unknown Source:8)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(Unknown Source:13)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(Unknown Source:0)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: com.android.camera2.vendortag.VendorTagNotFoundException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:61)
at com.android.camera2.vendortag.VendorTagHelper.setValue(Unknown Source:4)
at com.android.camera2.compat.MiCameraCompatQcomImpl.applySaturation(Unknown Source:24)
at com.android.camera2.compat.MiCameraCompat.applySaturation(Unknown Source:2)
at com.android.camera2.CaptureRequestBuilder.applySaturation(Unknown Source:10)
at com.android.camera2.MiCamera2.setSaturation(Unknown Source:34)
at com.android.camera.module.Camera2Module.updateSaturation(Unknown Source:44)
at com.android.camera.module.Camera2Module.consumePreference(Unknown Source:258)
at com.android.camera.module.BaseModule.accept(Unknown Source:85)
at com.android.camera.module.BaseModule.accept(Unknown Source:2)
at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:8)
... 9 more
Caused by: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)
at android.hardware.camera2.impl.CameraMetadataNative.setBase(Unknown Source:17)
at android.hardware.camera2.impl.CameraMetadataNative.set(Unknown Source:14)
at android.hardware.camera2.impl.CameraMetadataNative.set(Unknown Source:4)
at android.hardware.camera2.CaptureRequest$Builder.set(Unknown Source:6)
at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:19)
... 19 more

Can You fix it ?

pudiste solucionar el problema? I have the same error

Hey guys! I also got this problem. Could you solve it? And if yes how did you do? Thanks for answears! I burnt my phone and I needed to replace two camera sensor. But now I got the shame issue.

I have same problem, any idea?

Anyone solved this? I have the same issue

allblacks19992 said:
Anyone solved this? I have the same issue
Click to expand...
Click to collapse
Test vendor image or the full fastboot rom