TeamAmaze / AmazeFileUtilities-Issue-Tracker

Issue tracker for Amaze File Utilities
https://play.google.com/store/apps/details?id=com.amaze.fileutilities
26 stars 3 forks source link

Crash reported by Kevin #332

Closed amaze-issue-automation[bot] closed 7 months ago

amaze-issue-automation[bot] commented 11 months ago

Issue explanation (write below this line)

Copied my iTunes music library to my phone. Roughly 6500 songs equaling about 40 GB. Now no matter which song I press, I get the error below. I've tried restating my phone, but that made no difference.

Exception

java.lang.RuntimeException: android.os.TransactionTooLargeException: data parcel size 1770484 bytes
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1995)
at android.app.ContextImpl.startService(ContextImpl.java:1927)
at android.content.ContextWrapper.startService(ContextWrapper.java:834)
at android.content.ContextWrapper.startService(ContextWrapper.java:834)
at com.amaze.fileutilities.audio_player.AudioPlayerService$a.a(AudioPlayerService.kt:38)
at com.amaze.fileutilities.home_page.ui.files.m0.invoke(MediaFileAdapter.kt:17)
at x3.y.invokeSuspend(Extensions.kt:53)
at f8.a.resumeWith(ContinuationImpl.kt:9)
at v8.g0.run(DispatchedTask.kt:107)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
Suppressed: v8.e0: [n1{Cancelling}@5aface, Dispatchers.Main.immediate]
Caused by: android.os.TransactionTooLargeException: data parcel size 1770484 bytes
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:662)
at android.app.IActivityManager$Stub$Proxy.startService(IActivityManager.java:6213)
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1967)
... 16 more


Sent from my Galaxy

Krox-Ai commented 7 months ago

I know what's happening that is causing all these errors. ☆check and you will find what you need to fix this for all affected. Here it is. #1 A Google pixel Device is the easiest to unlock bootloader and root. #2 hackers and criminals are using services like G.A.T.T services that use Bluetooth low energy devices that use initial handshake to hack into any device. If it shows a name in Bluetooth pairing. Then it is hackable. (Much more involved with this and REALLY NEEDD TO BE FIXED. #3 Once said handshake is completed the hacker will then insert a newly created folder disguised as a normal folder in your devices file system that exactly clones its path. Now when they do this they are using a hidden pathway that is a su/sudoed/ clone/ fake system image therefore causing the Normal system checks to look right past the issues. So in order to fix this issue you need to understand that they can change the boot sequence to skip that on every restart. Best thing I can think is for everyone to turn on airplane mode, factory reset don't re-add any old accounts and start over with new accounts. I know that I figured this out via stock recovery history.

VishalNehra commented 7 months ago

Fixed with 1.92+ versions