Database Develop

[Q] Help with my app

Hello, I have just released my first app called College Football Fight Songs. It is obviously an app that plays all of the college football fight songs. I am a beginner programmer with little experience and have been testing it on a Nexus S 2.3.4 throughout my development. It has worked perfectly even after releasing the app on the Market.
The only problem is that for some reason, it does not work on all devices for whatever reason. I am very confused and don't quite know what to do. It has been made for Android 2.1 and up, and works perfectly on my Nexus S.
The problem with other devices is that when either going to another screen, or going back from a screen, it force closes.
I would like any feedback regarding this problem, or any criticism that you can offer on my app, thanks!
Because I do not have very many posts, I cannot post a link to the Market or even a QR code, but if you just search "College Football Fight Songs" or "Eric Carboni" in the Market, my app is there.
Thanks

Can anyone help?
Sent from my Nexus S using XDA Premium App

ericcarboni said:
Can anyone help?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I'll take a look later tonight after the kids go to sleep and see if I can recreate the fc. If it is in the market have you looked at the error reports and the stack traces?
Sent from my Nexus S using XDA Premium App

I grabbed it quick.....some initial impressions:
It's huge. You should reduce the package size if possible. Make each conference downloadable as a package possibly. You can leverage the market for this. 30 MB is a *large* app especially if I only want a few fight songs.
Since I can't recreate the fc I'll ask a few questions.
How are you handling the player resources in your onPause and onResume methods ?
How are you allocating new resources to play? Are you checking if it is already in use and calling stop before trying to play?
Do you have any error reports that you could post the stack trace from?
Sent from my Nexus S using XDA Premium App

First I just wanted to say thanks for taking the time to help me out with this. Also, I want to say how amazing your NFC Task app is: I've had it for a while now and I've been using it with some key chain tags. I love it.
Yes, I know it is huge. In fact, it is one of the biggest apps I have on my device. After I fix this problem, I will work on making each conference downloadable.
Right now, with my experience with Java, everything I have done with the playing and pausing is really basic. I am not checking if it is already in use to stop it before playing. Right now I have this -- once you are in the 'now playing' screen, I have the onPause method to stop each song from playing. I assumed there was a simpler way to do this..
But anyways, right now, there is one error report that I've gotten. I don't really understand it, but right now all I've gotten out of it is that the error is on the onPause action.
This is the stack trace for that report:
java.lang.RuntimeException: Unable to pause activity {com.carboni.fightsongs/com.carboni.fightsongs.BIG12}: java.lang.NullPointerException
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3348)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3305)
at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:3288)
at android.app.ActivityThread.access$2500(ActivityThread.java:125)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2044)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:893)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:651)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.carboni.fightsongs.BIG12.onPause(BIG12.java:159)
at android.app.Activity.performPause(Activity.java:3842)
at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1190)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3335)
... 12 more
Any other help you can give me is greatly appreciated, thank you very much

ericcarboni said:
First I just wanted to say thanks for taking the time to help me out with this. Also, I want to say how amazing your NFC Task app is: I've had it for a while now and I've been using it with some key chain tags. I love it.
Yes, I know it is huge. In fact, it is one of the biggest apps I have on my device. After I fix this problem, I will work on making each conference downloadable.
Right now, with my experience with Java, everything I have done with the playing and pausing is really basic. I am not checking if it is already in use to stop it before playing. Right now I have this -- once you are in the 'now playing' screen, I have the onPause method to stop each song from playing. I assumed there was a simpler way to do this..
But anyways, right now, there is one error report that I've gotten. I don't really understand it, but right now all I've gotten out of it is that the error is on the onPause action.
This is the stack trace for that report:
java.lang.RuntimeException: Unable to pause activity {com.carboni.fightsongs/com.carboni.fightsongs.BIG12}: java.lang.NullPointerException
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3348)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3305)
at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:3288)
at android.app.ActivityThread.access$2500(ActivityThread.java:125)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2044)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:893)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:651)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.carboni.fightsongs.BIG12.onPause(BIG12.java:159)
at android.app.Activity.performPause(Activity.java:3842)
at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1190)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3335)
... 12 more
Any other help you can give me is greatly appreciated, thank you very much
Click to expand...
Click to collapse
Calling pause / stop in the onPause is probably best. You can likely stop it instead of pausing it. The garbage collection should take care of freeing the resources as long as they are not in use when the Activity finishes.
This is the relevant error:
Code:
Caused by: java.lang.NullPointerException
at com.carboni.fightsongs.BIG12.onPause(BIG12.java:159)
I am guessing this is where you are accessing the player object in the onPause() method. However for whatever reason the object is null. It's a good idea to do a null check on the object itself before operating on it.
For operations like this I'd also recommend a try / catch and logging the exception via Log.d or Log.e so that if there is an issue you can pull it from logcat. You can call Lod.d("TagName", "Error and info you want to print") as well we e.printStackTrace() assuming you've named the Exception that is caught e. This will help log info for users (or yourself) for more useful debugging info.
Essentially you want to prevent your app from crashing on non show stopper exceptions. By wrapping these operations in try/catch blocks you're able to gracefully handle the exceptions and move on with your application without FCing.
Using try/catch blocks is really cheap (from an operational perspective) for small apps like this. The catch is the most expensive part, but it will really help you to gracefully handle issues that arise and eliminate force closes.
If you're having trouble tracking down the issue I'll take a look at the source if you want to zip/rar it up and send it over.

Which operations would I wrap a try/catch around?
Thanks for all your help, I think I might send you the source code eventually if I can't figure it out.
And I have a question: why would the app work perfectly on Gingerbread but not other phones with Froyo? Just curious to why this is

ericcarboni said:
Which operations would I wrap a try/catch around?
Thanks for all your help, I think I might send you the source code eventually if I can't figure it out.
And I have a question: why would the app work perfectly on Gingerbread but not other phones with Froyo? Just curious to why this is
Click to expand...
Click to collapse
Honestly - wrap any operations that may result in an exception being thrown (within reason). Depending on your experience this may or may not be something you'll be able to see easily or not. You'll learn quite a bit by trial and error
Generally though if you're dealing with resources that may or may not be available (even if they should *always* be available) it doesn't hurt to wrap them in a try/catch in case an exception is thrown.
Any time you are parsing potentially invalid input and / or casting data it's good to try/catch and handle any exceptions that may creep up.
Some of the audio code (libaudio or libmedia) was changed from Froyo to Gingerbread - you're also working with potential issues from Rosie(Sense)/Touchwiz/Blur. Most of these frameworks make alterations to the subsystems in some form or another and do not always behave in the same manner as an AOSP rom 100 % of the time. You're also dealing with varying devices with varying amounts of resources and multiple services competing for these resources.
In the SDK documentation the classes themselves will show what exceptions are thrown - these are thrown to prevent the app/subsystem from crashing or getting unexpected results. It is your job as the developer to catch these exceptions and handle them.
Obviously it's wasteful to try/catch everything - there's no reason, for example, to try catch the overloaded ++ operator for an integer. If you are doing string manipulation on user input though then you should be doing some sanity checking / handling of exceptions as you may get completely unexpected and bad data.
Any time you are dealing with system resources you'll want to verify that the resource did properly get assigned and handle the exceptions that it may throw as a good practice though.
For example, when you play a media file you are counting on:
The DSP device being availble
The handle to the device being appropriately acquired
The resource to be played being present and properly allocated
The playing of this resource to be properly executed by the subsystem
If any of these things goes wrong then an exception is going to be raised by the subsystem so that it can be handled in your application. If you do not handle the exception your app crashes and you FC. If you handle it though you can deal with it as is appropriate and move on (e.g: inform the user there was an error, log the exception and move on).

ich habe das gleiche problem!!

I've been working on it; do you think using a try/catch for the exceptions that need it will solve the problem completely?
Sent from my Nexus S using XDA Premium App

ericcarboni said:
I've been working on it; do you think using a try/catch for the exceptions that need it will solve the problem completely?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, assuming you're not doing something crazy with the object or resources - your app is FC's because an exception is being raised and not handled. By catching and handling the exception (assuming there isn't an issue with the underlying code) you are able to programmatically deal with these issues.

krohnjw said:
Yes, assuming you're not doing something crazy with the object or resources - your app is FC's because an exception is being raised and not handled. By catching and handling the exception (assuming there isn't an issue with the underlying code) you are able to programmatically deal with these issues.
Click to expand...
Click to collapse
I have done a few, and now it works on a 2.2 emulator, but not on a 2.1, or a 2.2 Galaxy S.. Do you think if I send the project to you, could you take a quick look at it? You've been a lot of help, I appreciate it

How can I add my service into remote and start it which I injected by Xposed?

Hello everyone,,,
I recently hooked an app, and I've found some methods that I can call them in it, like I hooked a before onCreate method in the main activity, then I can call some method as well. That's perfect.
But I want to call them via my app, I can do it through BroadCast, but the broadcast can't run more than 10 seconds, it's very bad run some big task, and sometimes I prefer a result can be returned.
So seems it's wonderful I can add my service in the remote app and start it, but the problem is it isn't in the `AndroidManifest.xml`.
By the way, how can I get the ClassLoader from the remote app, I am not sure it will be working if I got the ClassLoader.
Welcome to correct me!
Thank you all. Waiting for your opinions.
Feel free to contact me with email [email protected] or Wechat(id:imwangshiqi)

Gmail app keeps kicking out/closing

I have a brand new kindle fire 7, just did the steps for installing Google play store, installed a few apps but the gmail app won't stay open and work.... What do I do now?

Same with me. I would love to find the answer to this. Thanks.

I'm having the same problem... Have tried most of the standard attempts to fix it. It did refresh the messages initially, but it still opens, then immediately closes. (Still shows it's running and have cleared that, rebooted, etc). Very frustrating! (Sorry.... probably the wrong thread, but's happening on my new Fire 8HD 2017 too)

Getting the same error here, so I did a logcat on it:
Code:
E/DatabaseUtils(15437): Writing exception to parcel
E/DatabaseUtils(15437): java.lang.SecurityException: Permission Denial: reading com.android.providers.downloads.DownloadProvider uri content://downloads/all_downloads/73 from pid=15497, uid=10016 requires android.permission.ACCESS_ALL_DOWNLOADS, or grantUriPermission()
E/DatabaseUtils(15437): at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:539)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:452)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.enforceFilePermission(ContentProvider.java:443)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.openTypedAssetFile(ContentProvider.java:388)
E/DatabaseUtils(15437): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:313)
E/DatabaseUtils(15437): at android.os.Binder.execTransact(Binder.java:446)
W/GAV2 (15497): Thread[Background tasks,5,main]: dispatch call queued. Need to call GAServiceManager.getInstance().initialize().
--------- beginning of crash
E/AndroidRuntime(15497): FATAL EXCEPTION: Background tasks
E/AndroidRuntime(15497): Process: com.google.android.gm, PID: 15497
E/AndroidRuntime(15497): java.lang.SecurityException: Permission Denial: reading com.android.providers.downloads.DownloadProvider uri content://downloads/all_downloads/73 from pid=15497, uid=10016 requires android.permission.ACCESS_ALL_DOWNLOADS, or grantUriPermission()
E/AndroidRuntime(15497): at android.os.Parcel.readException(Parcel.java:1548)
E/AndroidRuntime(15497): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime(15497): at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:148)
E/AndroidRuntime(15497): at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:691)
E/AndroidRuntime(15497): at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1080)
E/AndroidRuntime(15497): at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:921)
E/AndroidRuntime(15497): at android.content.ContentResolver.openFileDescriptor(ContentResolver.java:778)
E/AndroidRuntime(15497): at android.content.ContentResolver.openFileDescriptor(ContentResolver.java:733)
E/AndroidRuntime(15497): at android.app.DownloadManager.openDownloadedFile(DownloadManager.java:1040)
E/AndroidRuntime(15497): at ene.a(SourceFile:636)
E/AndroidRuntime(15497): at ene.a(SourceFile:439)
E/AndroidRuntime(15497): at com.google.android.gm.job.DownloadCompleteJob.a(SourceFile:40)
E/AndroidRuntime(15497): at eks.run(Unknown Source)
E/AndroidRuntime(15497): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(15497): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(15497): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(15497): at android.os.HandlerThread.run(HandlerThread.java:61)
It appears that com.google.android.gm doesn't have the permissions it needs (ACCESS_ALL_DOWNLOADS), so I tried to grant this permission with:
Code:
adb shell pm grant com.google.android.gm android.permission.ACCESS_ALL_DOWNLOADS
but I got:
Code:
Operation not allowed: java.lang.SecurityException: Package com.google.android.gm has not requested permission android.permission.ACCESS_ALL_DOWNLOADS

Anyone find a solution to this?

Try disabling "Download attachments" under Gmail's account settings while disconnected from WiFi.

Zeranoe said:
Try disabling "Download attachments" under Gmail's account settings while disconnected from WiFi.
Click to expand...
Click to collapse
Yes, I tried that...

Having the same issue. Can we downgrade the gmail app or something?

cduced said:
Having the same issue. Can we downgrade the gmail app or something?
Click to expand...
Click to collapse
Nope - characteristic if the underlying components that Gmail relies on. Can't downgrade those; will either fail or immediately self-updating to latest version. Look to another mail client (many fine options in Play Store) or use web interface.

gmail app quits
same problem - same with inbox spp. starts for few seconds then goes away. is still running but not in screen!
---------- Post added at 04:51 PM ---------- Previous post was at 04:38 PM ----------
just got off the phone with Amazon. needless to say they do not troubleshoot Google's apps! Nice guy, second tier informed him. so either Google fixes this or we are SOL! Maybe if we get a long enuf thread here! Anyone here work for Google?

carlscheider said:
same problem - same with inbox spp. starts for few seconds then goes away. is still running but not in screen!
---------- Post added at 04:51 PM ---------- Previous post was at 04:38 PM ----------
just got off the phone with Amazon. needless to say they do not troubleshoot Google's apps! Nice guy, second tier informed him. so either Google fixes this or we are SOL! Maybe if we get a long enuf thread here! Anyone here work for Google?
Click to expand...
Click to collapse
Unlikely either party will pursue a 'fix' as Amazon and Google don't pursue mutual business objectives or cross validate apps. Especially hacks. Best option IMO is to consider a different mail app (there are many fine alternatives in the Play Store) or use the Gmail web interface (spartan but serviceable).

thanks
that makes perfect sense. i do use an email app but prefer gmail direct.
i will hold out hope. Had the same problem with Amazon's washington post - it finally fixed itself! found i could sometimes get it to work by just shutting it off normally.
i used to be a cto - crappy code lives forever. no attention to zero defect.
appreciate the wisdom. saves a few frustrating calls.

carlscheider said:
that makes perfect sense. i do use an email app but prefer gmail direct.
i will hold out hope. Had the same problem with Amazon's washington post - it finally fixed itself! found i could sometimes get it to work by just shutting it off normally.
i used to be a cto - crappy code lives forever. no attention to zero defect.
appreciate the wisdom. saves a few frustrating calls.
Click to expand...
Click to collapse
I suspect (but have no direct evidence to support) a new dependency on a core Google component not included with the basic Play Store install for this device (FireOS v5 in general). Haven't peeled back the onion to identify root cause as I do not run FireOS on any of my devices. Do have temporary access to a 'stock' HD 8. Will take a look if time permits.
Could simply be a version mismatch on Android code shared between FireOS and Google components. That would be a tougher fix on unrooted devices.

Davey126 said:
I suspect (but have no direct evidence to support) a new dependency on a core Google component not included with the basic Play Store install for this device (FireOS v5 in general). Haven't peeled back the onion to identify root cause as I do not run FireOS on any of my devices. Do have temporary access to a 'stock' HD 8. Will take a look if time permits.
Could simply be a version mismatch on Android code shared between FireOS and Google components. That would be a tougher fix on unrooted devices.
Click to expand...
Click to collapse
I am a little surprised too. You can download it from the Play Store from the tablet so it's not to do with compatibility I don't think. I had the same problem earlier with Weather Underground and I downgraded a few versions and it worked. Could be an update Amazon snuck by us too. The tablet kicks you out right after you setup Gmail. It's like you can do everything else except read your Email. It even still sends you notifications. I thought it was working after my reset an hour ago because of the notifications. I tapped the icon, it went to setup and when it got to the inbox, it kicks me out. I'll reinstall it later using an older version and see if it works. I don't worry about auto update as I don't let my play store apps auto update.
EDIT: I recall when I had my Fire 7 working, you could go back a few versions of an app and update it from the play store to most recent and that fixed the issue. Perhaps try that?

Old version - good thinking
Didn't realize I could do that. I grew up coding assembly language on an IBM 50 - left when Smalltalk and C++ were all the rage.
I will stop auto updates and see about getting an older version.
I am kind of amazed that Amazon allows this "side loading" - it isn't really a root - just a sidestep.
Glad it works. The Fire 8 is a marvelous little gadget for the price. It will change EVERYTHING - like FIRE..
And it makes Jeff just a bit richer - like he needs it.
Many thanks.

cannot regress in Fire
carlscheider said:
Didn't realize I could do that. I grew up coding assembly language on an IBM 50 - left when Smalltalk and C++ were all the rage.
I will stop auto updates and see about getting an older version.
.
Click to expand...
Click to collapse
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.

carlscheider said:
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.
Click to expand...
Click to collapse
Older versions are also available on APKMirror. Not that it matters as it would seem an underlying dependency is missing. Becomes a cat-and-mouse game. Consider using a different mail app or the Gmail web interface.

Davey126 said:
Older versions are also available on APKMirror. Not that it matters as it would seem an underlying dependency is missing. Becomes a cat-and-mouse game. Consider using a different mail app or the Gmail web interface.
Click to expand...
Click to collapse
Damn shame no one these days has built in POP options anymore. I'd take a totally manual interface over an app any day.
---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------
carlscheider said:
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.
Click to expand...
Click to collapse
Google is good about putting updates across all versions. If that is the case with Gmail, no older ones will work.
Gmail used to work. I did have it on the tablet a while back. Though I never reinstalled it after I did my first reset.

Davey126 said:
Look to another mail client (many fine options in Play Store) or use web interface.
Click to expand...
Click to collapse
You were right, there are other email apps that are fine... Thanks.

Would having root allow one to give the gmail app the proper permissions?

Continuous Input

I don't know if someone can help with this or had a similar thing happen, but here goes:
- phone in pocket for about 20 minutes in -35 degree C weather (not a good idea, I know)
- flashlight was flickering on and off after returning
-Bixby key was remapped, so I deleted the remapping app
-phone started repeatedly making requests to Bixby voice assistant, which was worse
-followed the instructions someone else on this forum posted here: https://forum.xda-developers.com/t/how-to-remove-oem-bloatware-from-s8-s8.3654687/ which got rid of Bixby
-phone started making repeated requests to Google voice assistant
-factory reset, seems to work. deleted Bixby again because why not
-starts making repeated requests to Google voice assistant again 2 days later
-disable google app, this seems to make the phone usable again
-still can hear that whatever input keeps causing the requests is happening when using headphones. messes with bluetooth, etc., sounds like the "volume down" tone.
Has anyone else had this happen/know what the "ghost" input is so I can try to quarantine it?
TLDR: Phone got cold, now produces ghost input continually that I want to disable/isolate.

Pixel 5 @Android 11 - Camera 0: Error clearing streaming request: Function not implemented (-38)

Hello,
I'm developing an app using the back camera. It works on many different devices and Android versions but on a Pixel 5 it seems to fail.
I get these errors:
E/CameraCaptureSession: Session 0: Exception while stopping repeating:
android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): cancelRequest:459: Camera 0: Error clearing streaming request: Function not implemented (-38)
at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:1009)
at android.hardware.camera2.impl.ICameraDeviceUserWrapper.cancelRequest(ICameraDeviceUserWrapper.java:99)
at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:1251)
at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:578)
at android.hardware.camera2.impl.CameraCaptureSessionImpl$2.onDisconnected(CameraCaptureSessionImpl.java:789)
at android.hardware.camera2.impl.CameraDeviceImpl$7.run(CameraDeviceImpl.java:245)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: android.os.ServiceSpecificException: cancelRequest:459: Camera 0: Error clearing streaming request: Function not implemented (-38) (code 10)
at android.os.Parcel.createExceptionOrNull(Parcel.java:2387)
at android.os.Parcel.createException(Parcel.java:2357)
at android.os.Parcel.readException(Parcel.java:2340)
at android.os.Parcel.readException(Parcel.java:2282)
at android.hardware.camera2.ICameraDeviceUser$Stub$Proxy.cancelRequest(ICameraDeviceUser.java:732)
at android.hardware.camera2.impl.ICameraDeviceUserWrapper.cancelRequest(ICameraDeviceUserWrapper.java:97)
Those errors don't come from my own code but from the internal camera2 library. For some reason, `onDisconnect`, the library tries to call `cancelRequest` but it seems that the phone doesn't implement that function.
How could I go about it?
Is there any way to change the version of camera2 used?