Closed marcolino7 closed 8 years ago
have you sent the report via android? It seems that other people can use it, maybe it's something related to your device/version and a stacktrace would help :)
Hi, It happen also on new Souliss APP version, it happen on my S4 (KitKat) and Note3 (Lollipop), both with Samsung Firmware. When app crash do not ask me for send the crash report. Let me know how to get stacktrace and other logs you need. I'm available to help you.
Marco
of course the stackstrace of the error would help me greatly: the problem is that I'm not able to reproduce it. It's probably a stupid mistake I made, but I need the log to understand it
Hi Alessando, I don't know whatis and how capture stacktrace. If you can help me, I can reproduce and capture.
Marco
We can start looking ionside your /Souliss folder inside SdCard...It should contain the App's log. Let's have a look
Ciao Alessando, I reproduced the issue, on Italian Lollipop Crash report is called "Cronaca", and I just sent one to google, I hope you can retrieve it. Meanwhile a deleted souliss.log an created a new one reproducing the issue. It is here attached. Let me know what else you need.
Marco souliss.txt
The included log doesn't contain any error. Now I'll check in Play console if I received your report. Thank you, we'll fix this :)
It arrived now!!! It's a problem with Fourier:
android.view.InflateException: Binary XML file line #179: Error inflating class com.pheelicks.visualizer.VisualizerView
at android.view.LayoutInflater.createView(LayoutInflater.java:640)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:750)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:813)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:821)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:821)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:821)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:821)
at android.view.LayoutInflater.inflate(LayoutInflater.java:511)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:668)
at android.view.LayoutInflater.inflate(
are you using xPosed?
Yes
azz. The problem comes from there. The Visualizer we're using for music mode (loaded when T19 panel is shown)seems not compatible with xposed
here it is!!
https://github.com/felixpalmer/android-visualizer/issues/5
I'm sorry this is the cause of your problem and it will be very difficult to fix it as it's not in code I wrote :(
Reading, seems that it could be related to Music Sync on Souliss APP. You could detect this exception and disable music sync. There is a lot of Samsung Device.....
I will try to do something, but I guess the problem is more related to xposed than to Samsung device itself.
Basically, xposed doesn't know the Visualizer used during music sync. Can you disable it temporarily in order to confirm my guess?
I cannot disable Xposed, on lollipo and samsung is flash in recovery, but tried on my Samsung TAB S and work.
Ciao Alessandro, I can confirm that issue is still present on RGB strip control
Same problem with stock Moto X 2014.
That is Android 6 problem from the new permission system. To record audio you also need to ask for that permission to the user. http://stackoverflow.com/questions/33494631/android-visualizer-error-only-in-android-6-0
It works if you go to AppInfo for this app; navigate to permissions and allow Microphone
yes, thank you @andrempo I shall find a way to explicitly ask for that permission on MM. Since it's an external lib
BTW, @marcolino7 only ited (KitKat) and Note3 (Lollipop) so this remains strange
should be fixed in 1.7.0
Opening a T19 detail to access slide for luminosity or music sync, the app crash. Let me know if and what more detail needed. Marco