Working on some dark mods for my Xperia XA, and I can't figure something out:
Certain things change dynamically, like the status bar and Settings category text, etc, and usually the value in the xml to make that happen is either colorPrimary, colorPrimarydark, or colorAccent. Since light theme is always used by default on LP and higher, these colors are usually pretty dark. But that usually makes undesirable effect of dark-on-dark text for settings, depending on the primary colors used by the theme applied, (screenshot). I want to make the dynamic color a light one. I tried colorPrimaryLight, but always get error that no matching resource found, (maybe Google got rid of it in N or something). Anybody know a good value to make that happen?
Also, Xperia N has a reminder function in settings where a notification drops down from action bar when you have airplane mode on, etc. I can't find that function in styles or layout. Anybody know what it's called?
levone1 said:
Working on some dark mods for my Xperia XA, and I can't figure something out:
Click to expand...
Click to collapse
It depends on what theme you set so you need to modify any corresponding assets in the theme...
...and I've changed these two in SystemUI/values/drawables somc_status_bar_background_dark, somc_status_bar_background_light to point at @drawable/status_background
XperienceD said:
It depends on what theme you set so you need to modify any corresponding assets in the theme...
Click to expand...
Click to collapse
I got that, and have done that with individual thrmes - https://forum.xda-developers.com/crossdevice-dev/sony/customize-xperia-themes-computer-t3602560 - I'm more wondering in general if there's a value that tends to be light, (where the 3 I mentioned tend to be dark)... Thanks
levone1 said:
I got that, and have done that with individual thrmes - https://forum.xda-developers.com/crossdevice-dev/sony/customize-xperia-themes-computer-t3602560 - I'm more wondering in general if there's a value that tends to be light, (where the 3 I mentioned tend to be dark)... Thanks
Click to expand...
Click to collapse
Not sure what to suggest then.
XperienceD said:
Not sure what to suggest then.
Click to expand...
Click to collapse
Did you get that by referring to a '?color' value, or setting to a set rgb value, (does it change with the theme values)?
XperienceD said:
Not sure what to suggest then.
Click to expand...
Click to collapse
I did the same on main dashboard by setting text color in styles... I could do the same throughout, but hoping for a light color dynamic.
levone1 said:
Did you get that by referring to a '?color' value, or setting to a set rgb value, (does it change with the theme values)?
Click to expand...
Click to collapse
An rgb value in the android asset.
New question
So I'm currently trying to port XZ2 lock screen widget, (called 'xperialoops clock'), from another system dump to my stock X Compact, (8.0). I found all smali files in SystemUI (smali/com/sonymobile/keyguard/plugin/sonyclockloops), and copied the folder to my SystemUI, along with all drawables and xmls referred to in the files. Then recompiled, and decompiled, and matched up the public ids. Recompile was successful, and boots fine, but no visible changes or other options. I also replaced Lockscreen settings apk in /system/app. I'm guessing I need to also port in other files, like maybe 'clock view', etc, but I'd rather not spend hours on something someone else could set Mr straight on in a few minutes, so putting it out there... Any ideas? ( @SXUsr, @venkat kamesh, @niaboc79, @lubik1, etc...)
Thanks
Update - I got it to show in lockscreen settings, but choosing it causes SystemUI crash. I see that, events though I copied arrays for loops into my /res/values/arrays, still there's no public id created for it. Any ideas?
Update - decompile and recompile solved that, but still same result...
Bump in case anyone has insight to this. Here is located of crash. Seems like java conflict with the loops small files. Any way to deal with this?
Code:
10-14 20:10:08.061 628 663 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-14 20:10:08.493 20336 20336 E AndroidRuntime: FATAL EXCEPTION: main
10-14 20:10:08.493 20336 20336 E AndroidRuntime: Process: com.android.systemui, PID: 20336
10-14 20:10:08.493 20336 20336 E AndroidRuntime: android.view.InflateException: Binary XML file line #6: Binary XML file line #6: Error inflating class com.sonymobile.keyguard.plugin.sonyclockloops.SecondHand
10-14 20:10:08.493 20336 20336 E AndroidRuntime: Caused by: android.view.InflateException: Binary XML file line #6: Error inflating class com.sonymobile.keyguard.plugin.sonyclockloops.SecondHand
10-14 20:10:08.493 20336 20336 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance0(Native Method)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance(Constructor.java:334)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.createView(LayoutInflater.java:647)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:790)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:730)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:863)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.plugin.sonyclockloops.SonyClockLoopsKeyguardComponentFactory.createKeyguardClockPreviewView(SonyClockLoopsKeyguardComponentFactory.java:29)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerController.createClockView(ClockPickerController.java:486)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockItem.initView(ClockItem.java:68)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockItem.initWithClock(ClockItem.java:61)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerView.addClock(ClockPickerView.java:294)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerView.createViews(ClockPickerView.java:213)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerView.initPages(ClockPickerView.java:156)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerController.createClockPickerView(ClockPickerController.java:281)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerController.displayClockPickerView(ClockPickerController.java:267)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.ClockPickerController.startClockPicker(ClockPickerController.java:95)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.systemui.lockscreen.LockscreenClockController.displayClockPluginPicker(LockscreenClockController.java:104)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.StartClockPickerTouchListener.startPicker(StartClockPickerTouchListener.java:177)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.StartClockPickerTouchListener.-wrap1(Unknown Source:0)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.clock.picker.StartClockPickerTouchListener$LongPressCompletedRunnable.run(StartClockPickerTouchListener.java:217)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:789)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:98)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.os.Looper.loop(Looper.java:251)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6589)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Unsupported dependency class com.sonymobile.systemui.lockscreen.LockscreenLoopsController
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.systemui.Dependency.createDependency(Dependency.java:333)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.systemui.Dependency.getDependencyInner(Dependency.java:320)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.systemui.Dependency.getDependency(Dependency.java:309)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.android.systemui.Dependency.get(Dependency.java:381)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.plugin.sonyclockloops.SecondHand.<init>(SecondHand.java:180)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: at com.sonymobile.keyguard.plugin.sonyclockloops.SecondHand.<init>(SecondHand.java:144)
10-14 20:10:08.493 20336 20336 E AndroidRuntime: ... 34 more
10-14 20:10:08.497 1177 3694 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
10-14 20:10:08.500 20336 20336 I Process : Sending signal. PID: 20336 SIG: 9
...
or,
https://pastebin.com/5wac1qE0
levone1 said:
Bump in case anyone has insight to this.
Click to expand...
Click to collapse
As said in another thread, I believe it's now a matter of looking at folders such as Values-21 etc, that's just a theory based on modding with Substratum though.
SXUsr said:
As said in another thread, I believe it's now a matter of looking at folders such as Values-21 etc, that's just a theory based on modding with Substratum though.
Click to expand...
Click to collapse
Thanks, I got it... https://forum.xda-developers.com/showthread.php?p=78081055#post78081055
Related
I got the following blur accounts configured.
- Linked In
- Facebook
- YouTube
- Picasa
- Corporate Sync
- Google
- Twitter
The problem is that when the contacts are synced from the above account, I cannot go to settings of the contact list like "display option" menu. It force closes on me. I have monitored the logcat then i found out that something in android.os.Async has array out of bound index.
I have tried having only one account i.e. Corporate Sync it works fine. Then I add Google account, nothing happens. As soon as I add any of the social network accounts the contacts got force closing. One thing to note that in the list i cannot open those contacts which have some social network contact associated plus the social network contacts itself?
I have tested the same with some custom ROMs floating on the forum plus the stock SBF. But strangely older version 4.1.83 works fine.
Any clues?
theintelligent said:
I got the following blur accounts configured.
- Linked In
- Facebook
- YouTube
- Picasa
- Corporate Sync
- Google
- Twitter
The problem is that when the contacts are synced from the above account, I cannot go to settings of the contact list like "display option" menu. It force closes on me. I have monitored the logcat then i found out that something in android.os.Async has array out of bound index.
I have tried having only one account i.e. Corporate Sync it works fine. Then I add Google account, nothing happens. As soon as I add any of the social network accounts the contacts got force closing. One thing to note that in the list i cannot open those contacts which have some social network contact associated plus the social network contacts itself?
I have tested the same with some custom ROMs floating on the forum plus the stock SBF. But strangely older version 4.1.83 works fine.
Any clues?
Click to expand...
Click to collapse
Did you install the new Google+ app that was leaked? I know some people were having FC issues with their contacts after installing it.
Most likely would get more responses in the Q&A section.
Sent from my MB860 using xda premium
ghost_og said:
Did you install the new Google+ app that was leaked? I know some people were having FC issues with their contacts after installing it.
Click to expand...
Click to collapse
No that is not the case.
Sent from my MB860 using xda premium
Phalanx7621 said:
Most likely would get more responses in the Q&A section.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Please move this thread to Q&A section.
Sent from my MB860 using xda premium
This is not a development thread. Please use the correct forums.
kennethpenn said:
This is not a development thread. Please use the correct forums.
Click to expand...
Click to collapse
woah, ur a mod now? that's crazy!
keep up the good work!
So no clues?
theintelligent said:
So no clues?
Click to expand...
Click to collapse
For those of you who are interested below is the error
Code:
10-14 15:10:36.479 12395 12608 W ResourceType: getEntry failing because entryIndex 223 is beyond type entryCount 199
10-14 15:10:36.479 12395 12608 W ResourceType: Failure getting entry for 0x7f0200df (t=1 e=223) in package 0 (error -2147483647)
10-14 15:10:36.489 12395 12608 W dalvikvm: threadid=12: thread exiting with uncaught exception (group=0x40018560)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
10-14 15:10:36.489 12395 12608 E AndroidRuntime: java.lang.RuntimeException: An error occured while executing doInBackground()
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at android.os.AsyncTask$3.done(AsyncTask.java:200)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:274)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:125)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:308)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:138)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1019)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Top level element must be ContactsSource
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:133)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:104)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.model.ContactsSource.ensureInflated(ContactsSource.java:98)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.model.Sources.getInflatedSource(Sources.java:341)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.model.Sources.getAccounts(Sources.java:286)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.ui.ContactsPreferencesActivity$QueryGroupsTask.doInBackground(ContactsPreferencesActivity.java:348)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.ui.ContactsPreferencesActivity$QueryGroupsTask.doInBackground(ContactsPreferencesActivity.java:333)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at com.android.contacts.util.WeakAsyncTask.doInBackground(WeakAsyncTask.java:45)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at android.os.AsyncTask$2.call(AsyncTask.java:185)
10-14 15:10:36.489 12395 12608 E AndroidRuntime: at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
Hey guys, I don't know if this is 100% the right section to post this.
I just started to "theme" WhatsApp.
It's another version of "Yorzua" i used to "port" this theme.
It's just for personal usage. I decompiled his Themed version. (I used his one, to put his theme to the updated WhatsApp-Version.
I made it to "solve" some issues that appeard while recompiling.
I put the images to the new version of WhatsApp. Most of the theme is working.
The App is running fine. I changed the Appname for my girlfriend^^
Now to my problem.
I can use everything. But when i receive a picture (havn't tried it with other media yet) and i try to open it afterwards it loads, loads, loads and fc's.
Now here is my problem. In school I had C#. But that's 2 years ago^^ And since then i havn't done anything except a little programm.
I don't know how to find the issue now. Is there any way to debug this on my phone and see which file got a problem?
Okay, i just made a logcat while doing the same step.
I hope someone got a clue and might help me. Thanks in advance
PS: I removed the unimportant parts
Code:
09-22 16:22:22.959 21964 21964 I dalvikvm: Could not find method com.whatsapp.MediaView.a, referenced from method com.whatsapp.df.a
09-22 16:22:22.959 21964 21964 W dalvikvm: VFY: unable to resolve static method 3123: Lcom/whatsapp/MediaView;.a (Lcom/whatsapp/yz;Ljava/lang/String;Landroid/content/Context;)Landroid/content/Intent;
09-22 16:22:22.959 21964 21964 D dalvikvm: VFY: replacing opcode 0x71 at 0x006c
09-22 16:22:23.989 21964 21964 D AndroidRuntime: Shutting down VM
09-22 16:22:23.989 21964 21964 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x40f95300)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: FATAL EXCEPTION: main
09-22 16:22:23.994 21964 21964 E AndroidRuntime: java.lang.NoSuchMethodError: com.whatsapp.MediaView.a
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at com.whatsapp.df.a(df.java:65)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at com.whatsapp.zn.onClick(zn.java:2)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.view.View.performClick(View.java:4211)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.view.View$PerformClick.run(View.java:17267)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:615)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:92)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:4898)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:511)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1006)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)
09-22 16:22:23.994 21964 21964 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
09-22 16:22:24.034 2544 2664 E android.os.Debug: [email protected] > dumpstate -k -t -z -d -o /data/log/dumpstate_app_error
Hey folks,
I've already started this thread in the Gear S2 sub, but apparently no one can help me there:
https://forum.xda-developers.com/gear-s2/help/gear-s-phone-app-crashes-t3575667
Any help is highly appreciated!
I'm running on the recent MX rom (6.0.1) based on the .291 stock.
Logs is needed for debug if anything crashes.
iXaidyiu said:
Logs is needed for debug if anything crashes.
Click to expand...
Click to collapse
I don't know if this is what you need or if I did it correctly, but here's a debug log I've made via SDK (see attachment; I've roughly inserted the time from starting the app to crashing. I just don't really know how to read code/logs ...)
As far as I can say, this is the relevant part:
03-29 22:01:04.659 18133 18133 E AndroidRuntime: FATAL EXCEPTION: main
03-29 22:01:04.659 18133 18133 E AndroidRuntime: Process: com.samsung.android.app.watchmanager, PID: 18133
03-29 22:01:04.659 18133 18133 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/samsung/android/feature/FloatingFeature;
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.watchmanager.sdllibrary.FloatingFeature.getEnableStatus(FloatingFeature.java:11)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.twatchmanager.log.LoggerUtil$Builder.<clinit>(LoggerUtil.java:95)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.twatchmanager.util.HostManagerUtils.startPluginActivity(HostManagerUtils.java:551)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.callPluginActivity(HMConnectFragment.java:377)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.callPluginActivityWithDelay(HMConnectFragment.java:365)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.access$200(HMConnectFragment.java:67)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment$1.handleMessage(HMConnectFragment.java:315)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at android.os.Looper.loop(Looper.java:234)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5526)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.samsung.android.feature.FloatingFeature" on path: DexPathList[[zip file "/data/app/com.samsung.android.app.watchmanager-1/base.apk"],nativeLibraryDirectories=[/data/app/com.samsung.android.app.watchmanager-1/lib/arm, /data/app/com.samsung.android.app.watchmanager-1/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: ... 13 more
03-29 22:01:04.659 18133 18133 E AndroidRuntime: Suppressed: java.lang.ClassNotFoundException: com.samsung.android.feature.FloatingFeature
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.Class.classForName(Native Method)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
03-29 22:01:04.659 18133 18133 E AndroidRuntime: ... 14 more
03-29 22:01:04.659 18133 18133 E AndroidRuntime: Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack trace available
03-29 22:01:04.661 4105 7141 D ActivityManager: New dropbox entry: com.samsung.android.app.watchmanager, data_app_crash, d2aadc2f-d5ff-4528-a9bd-95d85b1002d3
03-29 22:01:04.671 4105 7141 W ActivityManager: Force finishing activity com.samsung.android.app.watchmanager/.setupwizard.SetupWizardWelcomeActivity
03-29 22:01:04.718 4105 8050 E InputMethodManagerService: Ignoring shouldOfferSwitchingToNextInputMethod due to an invalid token. uid:10197 token:null
I had the same problem. There's no solution, it's related to the xperia x systemui used in existenz and the other .291 custom roms (like MX) in the development area. The only .291 customized rom that works with the gear s2 is the miui rom.
I've tried ALL, so if you want your gear working with a xperia marshmallow rom, use the stock one with root.
If the rom uses the xperia x system UI, the clock's app won't run.
It works without problem with all the lollipop roms, with stock marshmallow and with the new lineageOS rom.
Hope this solves your question. It's an awesome clock and works flawlessly with other phones with custom roms.
Is there no workaround? Can't I somehow switch the SystemUI?
There's a thread with systemUIs for the Z2, but I haven't tried to switch to other so I can't say, sorry
Actually I'm in LOS waiting for the solution to bluetooth and reboot issues, it seems the last (with MIUI but you have to pay to have a full working rom) custom ROM with development for our Z2.
I've purchased an Oneplus3T these days and I'm waiting for it now. I love my old Z2, with me since 2014 summer, but the private driver development from Sony and the end of updates from the manufacturer have cut his wings.
I've switch 'cause I hope op3t follows other terminals from this brand, like op1,2, etc, witch today have active development 3/4 years later because manufacturer releases his blobs without restriction for the community.
I'm disappointed with Sony in this aspect. Yes, I know there's a Sony Android Open Source proyect, and really good android developers like Alain Jerpela working on it, but without the full support from Sony and it's blobs (is normal too, Sony pay lot of money for private solutions to his hardware), is very difficult to wait much more from this phone.
My best wishes finding a solution to use your gear with a .291 custom rom, maybe you can write to niaboc and ask him, his rom is awesome and deeply knows the xperia z2 framework.
Best wishes, dude
I switched to Lineage and it works like a charm.
Thanks!
I have an Lg G5 (H850), unrooted and fully up to date.
A few months ago I began to have trouble with the Clock app. It crashes several times during use.
I've been able to deduce that this problem occurs when Android Wear is installed, and it makes no difference if my Lg G Watch R is connected to my phone or not.
Another event that seems to trigger Clock crashing is when my phone toggles between service and WiFi, but I cannot be sure if that's the cause.
Here are the failed solutions I've tried:
- Install previous version of Android Wear dating back to before the issue started
- Cleared Data/Cache from Clock app
- Tried to disable Clock, but button is grayed out
- Installed Google Clock. Made no difference
- Disconnected watch, but problem persists
- Reset the watch to manufacturer's
I should add (although I am not sure it's a bug) that every time I clear data/cash from Clock, a new alarm appears set (though tuned off) at 7:00 am January 1st. I've never set this alarm, and whether I leave it there, delete it or switch it on and off (so it changes to current date) doesn't make a difference.
I am including a copy of LogCat that shows the crash. Unfortunately I do not know what to do with the information it provides.
Thanks for any help anyone can provide.
--------- beginning of crash
07-31 10:26:09.541 10690 10690 E AndroidRuntime: FATAL EXCEPTION: main
07-31 10:26:09.541 10690 10690 E AndroidRuntime: Process: com.lge.clock, PID: 10690
07-31 10:26:09.541 10690 10690 E AndroidRuntime: java.lang.IllegalArgumentException: Receiver not registered: [email protected]
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:1047)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1332)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:608)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gM(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gJ(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.d(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c$2.onConnected(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.f(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.dU(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.b(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.g(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$b.hy(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$a.handleMessage(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6247)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762)
Unexpected solution
After months of fiddling with this problem, I accidentally came across information that lead me to solve another problem and through it; fixing this issue I described.
Kinda silly to answer my own post, but it might help people out there.
While live monitoring Logcat, I decided to toggle WiFi on and off to see what the phone did. My Lg G5 has always been pretty slow to connect.
I noticed that, upon turning WiFi on, my phone went through the whole list of "saved" networks before even attempting to connect to the available ones.
I had a LOAD of saved networks. Most of them from countries I visited.
I cleaned up the list, removing most networks I had saved et voila! Not only did my phone started connecting to WiFi instantly, but my clock app stopped crashing.
I hope this helps someone out there.
Hello everyone,
I hope thats the correct forum to post this question. I tried to find something through google search but it seems that there are only some stackoverflow development questions on that topic, which do not help a lot.
I have a MI9 (MIUI Global 10.2.30 stable) without root. Now I wanted to remove some default system apps and found this tool here: github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/6.6.2
I followed this list (and tailored it to my own needs): gist.github.com/Biswa96/81fe477079fa5279f7cfd7b98d5519c7
After finishing my de-bloating I realized that Google Calender (and also system calender) does not start any more. All I get is the error message "Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority"
I tried to reinstall Google Calendar (and also all the removed bloat apps) but it doesn't help. Here is also the log file from adb logcat:
Code:
09-24 17:07:29.395 1441 2654 I ActivityManager: Start proc 29460:com.google.android.calendar/u0a99 for service com.google.android.calendar/com.google.android.syncadapters.calendar.CalendarSyncAdapterService caller=android
09-24 17:07:29.396 4352 4472 D PowerKeeper.Event: notifyAMProcStart processName: 10099 reason: com.google.android.calendar, pid:0
09-24 17:07:29.397 28323 28323 D Cal:D:AllInOne: onStart()
09-24 17:07:29.397 28323 28323 D Cal:D:AllInOne: onResume()
09-24 17:07:29.398 28323 29459 I Cal:D:Utils: setGoogleAccountsSyncable(): NOT syncable before, set it syncable
09-24 17:07:29.400 28323 28323 D AndroidRuntime: Shutting down VM
09-24 17:07:29.400 28323 29465 I FA : Tag Manager is not found and thus will not be used
09-24 17:07:29.400 28323 28323 E AndroidRuntime: FATAL EXCEPTION: main
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Process: com.android.calendar, PID: 28323
09-24 17:07:29.400 28323 28323 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {com.android.calendar/com.android.calendar.homepage.AllInOneActivity}: java.lang.SecurityException: Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3828)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3860)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1831)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Looper.loop(Looper.java:201)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6815)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Caused by: java.lang.SecurityException: Failed to find provider com.android.calendar for user 0; expected to find a valid ContentProvider for this authority
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.IContentService$Stub$Proxy.registerContentObserver(IContentService.java:779)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1988)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.ContentResolver.registerContentObserver(ContentResolver.java:1977)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.calendar.homepage.AllInOneActivity.onResume(AllInOneActivity.java:571)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1413)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.Activity.performResume(Activity.java:7400)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3820)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: ... 11 more
09-24 17:07:29.400 28323 28323 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.server.content.ContentService.registerContentObserver(ContentService.java:340)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.content.IContentService$Stub.onTransact(IContentService.java:76)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at com.android.server.content.ContentService.onTransact(ContentService.java:262)
09-24 17:07:29.400 28323 28323 E AndroidRuntime: at android.os.Binder.execTransact(Binder.java:733)
09-24 17:07:29.400 28323 28323 E AndroidRuntime:
09-24 17:07:29.401 28323 29459 I Cal:D:Utils: setGoogleAccountsSyncable(): NOT syncable before, set it syncable
09-24 17:07:29.402 589 589 E SELinux : avc: denied { find } for service=miui.mqsas.MQSService pid=28323 uid=10024 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mqs_service:s0 tclass=service_manager permissive=0
09-24 17:07:29.402 28323 28323 E MQSEventManagerDelegate: failed to get MQSService.
09-24 17:07:29.403 4352 4472 D PowerKeeper.Event: notifyAMCrash packageName: 0, pid:28323
09-24 17:07:29.403 29460 29460 E ndroid.calenda: Not starting debugger since process cannot load the jdwp agent.
09-24 17:07:29.404 1441 3632 W ActivityManager: Force finishing activity com.android.calendar/.homepage.AllInOneActivity
09-24 17:07:29.405 1441 3632 D ActivityTrigger: ActivityTrigger activityPauseTrigger
09-24 17:07:29.407 28323 28323 I Process : Sending signal. PID: 28323 SIG: 9
09-24 17:07:29.407 1441 3527 D ActivityManager: report kill process: killerPid is:28323, killedPid is:28323
Does anyone has an idea how to fix it?
I had the same issue... I managed to solve it.
Code:
pm install-existing com.android.providers.calendar