Develop Bugs

Testing help required!

Hey folks, I've had a report from the Play Store that my app is crashing on Glides, but I can't get a log from the users. If any of you would be so good to test out the function and see if you have issues, and then grab me a log of the crash, I would be really grateful.. Will increase your thanks meter of course.
My app thread is here and the latest release is in post #3
When the app opens there is the option at the top to go to Android TTS settings. Apparently, clicking on this causes a crash.
Thanks in advance
brandall

See below

Looks like photo didnt attach... Trying again
Sent from my SAMSUNG-SGH-I927R using xda premium

Aquethys said:
Looks like photo didnt attach... Trying again
Click to expand...
Click to collapse
Thank you. I'm wondering if the problem is only with stock, unrooted, but there aren't too many of those on XDA..!

brandall said:
Thank you. I'm wondering if the problem is only with stock, unrooted, but there aren't too many of those on XDA..!
Click to expand...
Click to collapse
Indeed. Right when I opened the app it requested su access.
Btw, good work
Sent from my SAMSUNG-SGH-I927R using xda premium

Aquethys said:
Looks like photo didnt attach... Trying again
Sent from my SAMSUNG-SGH-I927R using xda premium
Click to expand...
Click to collapse
Aquethys said:
Indeed. Right when I opened the app it requested su access.
Btw, good work
Click to expand...
Click to collapse
Thank you If root is detected, su access is requested for advanced functions. Full busybox commands by voice are in the making!

I downloaded the one from the appstore and that one is working well as well. Got it to learn my name and tell me the time and toggle WIFI on and off. Working fine so far. Yes it does ask for SU. No crashes so far. Is the beta any different?

No problems here. Runs smoothly and recognizes commands.
Running stock rooted.

Tested it on a used Glide I just bought and haven't had time to root yet. Running stock 2.3.5 that was factory reset a couple of days ago. No problems accessing any menu or sub-menu item. Guess I just haven't had time to put enough crap on it to make it unstable.

dudejb said:
I downloaded the one from the appstore and that one is working well as well. Got it to learn my name and tell me the time and toggle WIFI on and off. Working fine so far. Yes it does ask for SU. No crashes so far. Is the beta any different?
Click to expand...
Click to collapse
Pyho said:
No problems here. Runs smoothly and recognizes commands.
Running stock rooted.
Click to expand...
Click to collapse
oldnoob said:
Tested it on a used Glide I just bought and haven't had time to root yet. Running stock 2.3.5 that was factory reset a couple of days ago. No problems accessing any menu or sub-menu item. Guess I just haven't had time to put enough crap on it to make it unstable.
Click to expand...
Click to collapse
Thanks guys, it's appreciated - strange that the crash can't be replicated - there must be some other issues on the devices that are having problems.
The beta release is still a while away and will contain many more advanced features for full device control by voice. It's strange bug reports like this that slow me down! At least I can move on from this one now.
Thanks again, your thanks meters have increased.
brandall

Maybe the user who posted about the crash removed the Pico service

brandall said:
Thanks guys, it's appreciated - strange that the crash can't be replicated - there must be some other issues on the devices that are having problems.
The beta release is still a while away and will contain many more advanced features for full device control by voice. It's strange bug reports like this that slow me down! At least I can move on from this one now.
Thanks again, your thanks meters have increased.
brandall
Click to expand...
Click to collapse
1 one feature I would love to see is the ability to add something in the calendar via voice. I hear Siri can do that and would love to see that on Android.

Nardholio said:
Maybe the user who posted about the crash removed the Pico service
Click to expand...
Click to collapse
I should have code to catch that and stop the crash - Why I'm even more puzzled that a crash could happen at all....
dudejb said:
1 one feature I would love to see is the ability to add something in the calendar via voice. I hear Siri can do that and would love to see that on Android.
Click to expand...
Click to collapse
This feature is working well on my test devices - it'll make an appearance in a couple of releases time, after I've had chance to test it on multiple users calendars and multiple calendar apps.

Ok I just tested my theory. With Pico TTS uninstalled it tries to open settings, which freezes and FCs, and it dumps you right back in your app. Your app does not crash. Honestly if this is the bug, I'd say it's user error and not your fault.

Nardholio said:
Ok I just tested my theory. With Pico TTS uninstalled it tries to open settings, which freezes and FCs, and it dumps you right back in your app. Your app does not crash. Honestly if this is the bug, I'd say it's user error and not your fault.
Click to expand...
Click to collapse
Good work Thank you. I assume the crash also may extend to the Pico engine (or perhaps any other) having installation corruption of some kind.
Thanks again to everyone who replied and tested, it's really appreciated. I think I can safely say 'not guilty!'.
Cheers
brandall

software updates

hi
I,ve just replaced a nexus7 2013 after i hit the multitouch problem,everything was fine with it whilst it was running build JWR66N,but then i got a notification to update to the latest version.
I was reluctant to do so,but eventually decided to take the plunge,so i updated,it put build JSS15Q on my nexus...result was terrible multitouch issues,basically the update had inflicted my "working perfectly tablet" with the dreaded multitouch issue,needless to say i was gutted.
My new nexus again comes with the JWR66N build,my question is,can i stop the tablet auto downloading the new update(JSS15Q),i know i don't actually have to install it,but i was told that if i power of my nexus,it will automatically install the update when i reboot,is this true?
Don't want to go anywhere near that JSS15Q update,or any future updates at all if possible.
To be honest,i'm not that interested in having bleeding edge versions,if my nexus works flawlessly on the JWR66N build then i could'nt care less if i never updated ever again,if it ain't broke,don't fix it.

You should look at the two posts in my signature. They will cover everything you need.
BTW the update won't automatically install when you reboot. You can also turn off the notification in the framework services configuration.

sfhub said:
You should look at the two posts in my signature. They will cover everything you need.
BTW the update won't automatically install when you reboot. You can also turn off the notification in the framework services configuration.
Click to expand...
Click to collapse
Okay,thanks Sfhub,can I just ask though,I have the jss15q update sitting in my notification panel,until I specifically allow it,will it just stay there,I mean,will it at some point install itself without any action by me.
What happens if I reboot,will that instigate the update process.
As long as I'M in control of when it gets installed I'm happy,I know it fixes the GPS issue,but I literally never use GPS,so I'm not bothered about fixing that.
Would really really appreciate some help on this,cheers pal

wildcat777 said:
I have the jss15q update sitting in my notification panel,until I specifically allow it,will it just stay there,
Click to expand...
Click to collapse
Correct
settings->apps->all->google services framework
uncheck show notifications
if you get tired of the notification (it'll probably get rid of other Google notifications also)
wildcat777 said:
I mean,will it at some point install itself without any action by me.
Click to expand...
Click to collapse
This shouldn't happen, though you might hit the notification by accident then panic and ask it to continue.
wildcat777 said:
What happens if I reboot,will that instigate the update process.
Click to expand...
Click to collapse
This won't happen.
wildcat777 said:
As long as I'M in control of when it gets installed I'm happy,I know it fixes the GPS issue,but I literally never use GPS,so I'm not bothered about fixing that.
Would really really appreciate some help on this,cheers pal
Click to expand...
Click to collapse
If you ever just want the GPS fix by itself with no other changes, the link is in my signature.
http://forum.xda-developers.com/showthread.php?t=2421373

Thanks Sfhub,really appreciate your quick reply and the info,that's really set my mind at rest.
Once again,cheers pal

Lagginess

Is anyone still getting this after the December update? I'm really starting to absolutely hate this phone

Nope

taz1458 said:
Is anyone still getting this after the December update? I'm really starting to absolutely hate this phone
Click to expand...
Click to collapse
I do sometimes when using YouTube, there will be stutter going to the home screen . No such issue in other apps. Sometimes the app switcher has some stutter but not too noticeable.

I have no lag and I am underclocked.

No lag here, don't think I've noticed even a stutter yet

Did u install any sketchy apps?

No lag for me either. I am using Kirisakura kernel with its default settings, which is great.

hilla_killa said:
Did u install any sketchy apps?
Click to expand...
Click to collapse
Negative. It seems to be tied to the camera for whatever reason. I use Facebook messenger a lot with a bunch of my racing buddies and snapchat and the lag happens a ton there

Facebook and Snapchat ate very resource intensive apps. You should uninstalling one or both and just see if lags remains. Im willing to bet lag-b-gone! My 3xl is snappy, no issues

OkayGK said:
No lag here, don't think I've noticed even a stutter yet
Click to expand...
Click to collapse
This for me also. Buttery smooth since day one.

taz1458 said:
Is anyone still getting this after the December update? I'm really starting to absolutely hate this phone
Click to expand...
Click to collapse
Are you using a different launcher?

My Pixel 3 XL is buttery smooth.

pyroelite said:
Are you using a different launcher?
Click to expand...
Click to collapse
Nova. Always have. Always will.

taz1458 said:
Nova. Always have. Always will.
Click to expand...
Click to collapse
Use Nova also and have for years. No lagginess since Dec update.

samnada said:
Use Nova also and have for years. No lagginess since Dec update.
Click to expand...
Click to collapse
It really seems like it's tied to the camera.

taz1458 said:
It really seems like it's tied to the camera.
Click to expand...
Click to collapse
In what way? My camera seems as quick as ever.

samnada said:
In what way? My camera seems as quick as ever.
Click to expand...
Click to collapse
I'm honestly not sure. I'm trying to pinpoint it. Sometimes it'll take forever to do anything, then the next time, it loads quick as hell. I'm baffled.

taz1458 said:
I'm honestly not sure. I'm trying to pinpoint it. Sometimes it'll take forever to do anything, then the next time, it loads quick as hell. I'm baffled.
Click to expand...
Click to collapse
There has been some very weird stuff going on with those running Nova. It's not been proven that it's the cause but there is a pattern showing up. I know you've been running it like forever, I get that. But perhaps Google is inadvertently breaking some things with their monthly updates. Why not try uninstalling Nova after backing up the settings and run stock launcher for a few days. Just to see if it makes a difference or not.

bobby janow said:
There has been some very weird stuff going on with those running Nova. It's not been proven that it's the cause but there is a pattern showing up. I know you've been running it like forever, I get that. But perhaps Google is inadvertently breaking some things with their monthly updates. Why not try uninstalling Nova after backing up the settings and run stock launcher for a few days. Just to see if it makes a difference or not.
Click to expand...
Click to collapse
I will give that a whirl. Does anyone know if there is a way to copy my layout to the pixel launcher?

taz1458 said:
I will give that a whirl. Does anyone know if there is a way to copy my layout to the pixel launcher?
Click to expand...
Click to collapse
I tried that a while back on my Nexus 5X and didn't see a way. But I'm sure things have changed so there might be now. If not then you'll only be stuck for a couple of days before you go back. Curious for your results on the lag and camera issue.

Question Safetynet api error

Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers.
Using magisk canary.

I just came here to post this exact question and you beat me to it. I'm having the same issue, but I did verify that SafetyNet passes using another app from the play store, so the issue seems specific to magisk.

terlynn4 said:
I just came here to post this exact question and you beat me to it. I'm having the same issue, but I did verify that SafetyNet passes using another app from the play store, so the issue seems specific to magisk.
Click to expand...
Click to collapse
What's the other app? As long as it's passing I guess that's all that really matters.

Konfuzion said:
What's the other app? As long as it's passing I guess that's all that really matters.
Click to expand...
Click to collapse
I used "Root and SafetyNet Checker" by BetterOpts

Here you go:
twitter.com/topjohnwu/status/1382563209995964418

xLexip said:
Here you go:
twitter.com/topjohnwu/status/1382563209995964418
Click to expand...
Click to collapse
Thank you

Oh well, that looks bad. May switch to iPhone if that's the case. Pixel phones lack performance and other Android phones have a quite bad software experience in comparison, oneplus included.
My plan was to switch to a pixel rom soon to have the best of both worlds like I did with previous OnePlus phones as well. Now I may not be able to do that without losing many features. Thanks Google!

deezid said:
Oh well, that looks bad. May switch to iPhone if that's the case. Pixel phones lack performance and other Android phones have a quite bad software experience in comparison, oneplus included.
My plan was to switch to a pixel rom soon to have the best of both worlds like I did with previous OnePlus phones as well. Now I may not be able to do that without losing many features. Thanks Google!
Click to expand...
Click to collapse
Per the link above, this is just an issue with Magisk app's API key, and the dev already has a fix. No reason to do anything drastic like switching to iPhone.

terlynn4 said:
Per the link above, this is just an issue with Magisk app's API key, and the dev already has a fix. No reason to do anything drastic like switching to iPhone.
Click to expand...
Click to collapse
Just saw it

xLexip said:
Here you go:
twitter.com/topjohnwu/status/1382563209995964418
Click to expand...
Click to collapse
A fix is out: t.me/lexipG/9937

xLexip said:
A fix is out: t.me/lexipG/9937
Click to expand...
Click to collapse
thanks man, you are man of culture

Do GPay, Netflix etc. work with Magisk now?

deezid said:
Do GPay, Netflix etc. work with Magisk now?
Click to expand...
Click to collapse
Yeah, like before.

Now he just needs to add back "Install to inactive slot(after OTA)" and we are all set lol

xLexip said:
Poprawka została wydana: t.me/lexipG/9937
Click to expand...
Click to collapse
Działa ! It works, thank you.

schmeggy929 said:
Now he just needs to add back "Install to inactive slot(after OTA)" and we are all set lol
Click to expand...
Click to collapse
I still have that option after updating the app.

terlynn4 said:
I still have that option after updating the app.
Click to expand...
Click to collapse
It is weird, some people still have others don't. It was temporarily removed in the last few updates for Google Pixel phones bootlooping. I have tried all 3, stable beta and Canary builds. All 3 have it missing.

Delete

schmeggy929 said:
It is weird, some people still have others don't. It was temporarily removed in the last few updates for Google Pixel phones bootlooping. I have tried all 3, stable beta and Canary builds. All 3 have it missing. View attachment 5282401
Click to expand...
Click to collapse
Strange. I'm on the same version of the app as your screenshot, but I haven't done the latest update of magisk itself so that's still on 22102.

terlynn4 said:
Strange. I'm on the same version of the app as your screenshot, but I haven't done the latest update of magisk itself so that's still on 22102.
Click to expand...
Click to collapse
Yeah don't update or you will be re-rooting the long way. Lol

Question Block 13 update?

I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?

I assume if your phone rooted, automatically updating will fail

It doesn't, and I lose root, that's what I thought last security update— which is why i'm concerned

christiebunny said:
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
Click to expand...
Click to collapse
Yes tap build 7 times for Developer Settings and disable automatic updatea

You could unlock the bootloader (which would require a device wipe) and then reinstall your current build of Android manually. That would be one of the only ways to officially disable automatic updates as well as update notifications.

I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
You may be able to delay it some buy factory resetting and some other things, but it's a big "maybe", and ultimately I don't think there's any way for you to avoid it.
biggiesmalls657 said:
Yes tap build 7 times for Developer Settings and disable automatic updatea
Click to expand...
Click to collapse
The OP you quoted says:
christiebunny said:
I've already got 'automatic updates' turned off, but that isn't stopping it.
Click to expand...
Click to collapse

roirraW edor ehT said:
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
Click to expand...
Click to collapse
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Maybe it was even the same person mentioning it 3 times, lol. Not really sure.
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or just a fluke situation.

Lughnasadh said:
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Didn't go back to check the posts.
Click to expand...
Click to collapse
I think I've seen more than one person report this too, but wasn't sure, and as I always say, I keep forgetting the old stuff. What was I talking about?
Lughnasadh said:
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or something else is going on.
Click to expand...
Click to collapse
I suspect (but pretty obvious) that they have ways of force-pushing updates through despite the automatic update setting (or it's broken in typical Google fashion), but I think it's the former.
Then I believe they made a command decision that the vulnerability is too bad and that they felt they must force it on everyone. Again, given Google's reputation, this could've easily been an accident as well - "who pushed the red button!?!?!?"
And then the further command decision to push over top of modded, or at least simply rooted, devices as much as possible. I wonder what happens in the case someone has truly modified their software more aggressively at the root level. It wouldn't surprise me if it would've still overridden in those cases.
While, of course, those would be questionable actions for them to take (if these are actually true in the first place), I either partially or mostly agree with them, but just on principle, I can't wholeheartedly agree with them. Somewhere in the 40%-99% range.
If true, hopefully this is a very rare occurrence and not going to be how it is from now on. I will wait patiently to observe how things go.

What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!

Annil said:
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Click to expand...
Click to collapse
V4A, at least in my case. I'm not updating until its compatible, or I find a better alternative.

96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
Android 13 cannot be modified is one reason...

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't

Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
Could you explain your theory on this?

christiebunny said:
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Click to expand...
Click to collapse
Compatibility seems remarkably intact, magisk works as intended, and there is no evidence of any change in what control you have.

96carboard said:
Could you explain your theory on this?
Click to expand...
Click to collapse
Modified SystemUI bootloops.

Tulsadiver said:
Modified SystemUI bootloops.
Click to expand...
Click to collapse
Ok? How are you modifying it?

96carboard said:
Ok? How are you modifying it?
Click to expand...
Click to collapse
Same way I always have.

Tulsadiver said:
Same way I always have.
Click to expand...
Click to collapse
That answer really doesn't help anyone.

96carboard said:
That answer really doesn't help anyone.
Click to expand...
Click to collapse
Any like these:
Stand alone Clock, Navbargone, Battery Icon Gone, etc. Mods
For stock rooted only. For most part, these cannot be flashed together. These mods use the SystemUI Patcher Module Template by @Jai_08 By @cool_modules on telegram. After Installing this module, your screen will relock after every reboot of...
forum.xda-developers.com