Database Info

[Q] Voice Search Resetting

So I'm having a really strange issue. I got my Atrix 2 a few weeks ago after owning the OG since it launched. I'm currently running 2.3.6 Stock Deodexed installed via CWM restore in bootstrap. Everything is working fine, except this: the Voice Search app, which I use a lot, continually reverts itself to default settings. As long as the app is running, it behaves normally, but when I kill the process, reboot the phone, or too much time passes, it seems to wipe out its own data. As a result, nearly every time I use it, I get this first run dialog asking me if I want to enable personalized recognition and a tutorial overlay. I've selected both options multiple times and the issue persists. A few things:
1) I'm not sure if this has been happening since the beginning, because I've been rooted and deodexed in some form or fashion since the 2nd day I had it. I don't remember initially having a problem, though. Maybe someone running straight stock with no mods could test this?
2) I use local data encryption for both the SD Card and the app storage, as required by my corporate exchange server. That's the only thing I can think of that might be causing this.
3) I've reinstalled the app multiple times.
4) It seems like Voice Search can't be moved to the SD card.
Anyone else having this problem?

KinglyCitrus said:
So I'm having a really strange issue. I got my Atrix 2 a few weeks ago after owning the OG since it launched. I'm currently running 2.3.6 Stock Deodexed installed via CWM restore in bootstrap. Everything is working fine, except this: the Voice Search app, which I use a lot, continually reverts itself to default settings. As long as the app is running, it behaves normally, but when I kill the process, reboot the phone, or too much time passes, it seems to wipe out its own data. As a result, nearly every time I use it, I get this first run dialog asking me if I want to enable personalized recognition and a tutorial overlay. I've selected both options multiple times and the issue persists. A few things:
1) I'm not sure if this has been happening since the beginning, because I've been rooted and deodexed in some form or fashion since the 2nd day I had it. I don't remember initially having a problem, though. Maybe someone running straight stock with no mods could test this?
2) I use local data encryption for both the SD Card and the app storage, as required by my corporate exchange server. That's the only thing I can think of that might be causing this.
3) I've reinstalled the app multiple times.
4) It seems like Voice Search can't be moved to the SD card.
Anyone else having this problem?
Click to expand...
Click to collapse
s a matter of fact, I have had it happen to me a couple of times too. I'm running lfabor's SC_V5 Update 2 though.
Now I shall reply to you statements / questions:
When I was running stock 2.3.5 or 2.3.6 I didn't have this issue.
I do not use encryption as its not required for my corporate sync (nor is my phone a company phone)
I have not tried to reinstall it, as I dont use very often, and only had to he issue happen a couple of times. This is also because lfabor placed it in the
system directory, and I've been to lazy to move it out.
The reason it can't be moved to SD is because the SD storage has to be enabled by the developer of the app.
Also note I am using swiftkey X for my keyboard, but if you are having issues with stock I don't think swiftkey is to blame.
I have not

I have had this issue TONS of times on a 100% stock not even rooted phone. I think there is just something screwed up, I dont think it's because of anything you did. My SD card is not encrypted, and I am also using Swiftkey X (but I doubt its swiftkey X). Infact I think it even used to happen before I started using swiftkey x.

I have the same issue, and I'm also using Swiftkey X. I'm sensing a pattern...
While I haven't empirically tested enough, I think the voice search might be resetting every time that Swiftkey gets updated (like with new language files, since that seems to happen quite often).
I'll try to keep track to see if there's a link there.

quasihellfish said:
I have the same issue, and I'm also using Swiftkey X. I'm sensing a pattern...
While I haven't empirically tested enough, I think the voice search might be resetting every time that Swiftkey gets updated (like with new language files, since that seems to happen quite often).
I'll try to keep track to see if there's a link there.
Click to expand...
Click to collapse
I'm not using SwiftKey, but I do use the ICS keyboard, so I tried uninstalling it and freezing Swype for good measure. It didn't seem to affect things, at least on my end.

I'm having the same problem. I installed the swiftkey x keyboard to give it a try but uninstalled it when I didn't like it. Have had the problems even since the uninstall. Currently using the stock keyboard with stock rom rooted.
Sent from my MB865 using XDA App

[Q] Uninstall issue with Android uninstaller

I have searched everywhere for someone having a similar problem and a fix, but for the first time on xda, I haven't been able to find one.
I have a Galaxy SIII on Verizon currently running Hyperdrive RLS13.
When I open the Application Manager, click on an app (any app, it doesn't matter whether I installed it from the Play Store or from an apk) and then click "Uninstall", it does nothing but goes back to the application list. It doesn't install, I get no error message, Settings doesn't crash...it just does nothing. It's the same as using the back button.
I CAN uninstall apps within the Play Store. Occasionally the uninstall button in the Settings will actually give me the confirmation pop-up to continue with the uninstall or to cancel it. But 90% of the time it doesn't and I have to use the Play Store.
I have done a clean flash once already and the issue still persists. My fiance who has the same exact phone as me (but in white) is also running Hyperdrive RLS13 and his phone is fine. In fact, I flashed Hyperdrive onto both our phones with the same exact SD card, using the same zip file.
I've been using custom ROMs for several years so yes, I've done all the obvious things, but I've reached the extent of my knowledge on what could be causing this. Can anyone tell me if they have heard of this issue before or a possible fix? I've never had this issue outside of Hyperdrive (I would post in the Hyperdrive thread but I don't have enough posts to reply in Development).

Have you tried flashing rls14. I would do your wipes and then flash the newest release.
Sent from my GT-P5113 using xda premium

I just downloaded it yesterday but I haven't flashed it yet - it's moving to my SD card right now. The only reason I posted for a fix though is because reflashing 13 didn't help... the issue just randomly started occuring about 3 weeks after I originally installed Hyperdrive. It makes me wonder what caused it.
I will be flashing 14 shortly and will report back.

Following a clean RLS14 flash, I still cannot uninstall within the Application Manager.
My fiance's phone (which I also updated to 14 as well this afternoon) can do so like usual.
So...any ideas?

workaround
assuming you nandroided coming from 13 to 14, just dont select those apps you want uninstalled to backup.
flash 14, restore apps, and only the ones you want will appear.
another workaround to try is install nova, long click the icon on a homescreen, select uninstall. not sure if this is a prime faeture though.

Well, sure - the even easier workaround is to just uninstall them with the Play Store, but I'd rather find out why this is happening.

So I've searched the web and the Hyperdrive thread and can't seem to find anything ANYWHERE. Any insight would be helpful. It seems to make sense that it could be a permissions issue maybe, but I don't know enough about building ROMs to know how to go about testing that.

[Q] CM 10.3 on Galaxy Tab p5113 on Restart Loop

Edited for the third time. Apparently Ididn't fix my problem.
So I'm running Cyanogenmod 10.3 on a Samsung Galaxy Tab2 10.1 (p5113***), and for some strange reason, my tablet keeps restarting randomly. I'd be reading a PDF or scrolling through some random app, and it'd suddenly freeze and the tablet would restart.
This all happened after I was typing a message on the Facebook app when it abruptly freezes and puts me through a restart loop that eventually ended. But when I finally got to startup without a crash, I'd see, almost immediately, a notification telling me that "Trebuchet has stopped responding", and my only option is to hit Ok. And I do, and most of the time, it crashes right afterwards.
At first, I was able to 'fix' (I think) this by freeing up space on my internal storage, because an app was on an update loop trying to install an update that was too big for whatever space I had left. I assumed it was eating up memory, space, and RAM and overwhelming my OS, so I uninstalled it and everything worked fine for most of the night. Later, I was reading a PDF file when Adobe just stopped working, froze, and put me through another restsart loop.
Also, I would like to point out that it is extremely difficult to turn this tablet off. It usually loops a few times before shutting down. Also, CM is updated to the latest STABLE update, which is not at all recent.
All this after Facebook crashed. I seriously have no idea what I do, and I would rather not reinstall CM, because it was an ADVENTURE trying to install it the first time, and I heard it's even more difficult and dangerous to uninstall and restore to factory settings. I'm not really good at this stuff.
Please help. Please.
*** Apparently my tablet is p5110, and the version of CM I installed was compatible with p5113, but it managed to work anyways, so I just shrugged and let it happen. And it has been working for the past 14 months, prior to the Facebook crash that started this mess.

Don't mean to bump, but I'm only replying to myself to show that my original post edit is now moot, because the problem resurfaced ... help.

I don't have a solution to you, but will share my own experience on the 5113. I have two of them. One has been stable since I bought it, except for a brief time when it had the awful first 4.2 update, eventually fixed by the MK3 firmware update. It's working fine. My other one has been a nightmare all year long, after six or eight months of stability after I bought it.
I've installed CM on in, in early June. Unstable.
I've installed Omnirom on it shortly afterward. It was more stable, but still not "stable."
Installed Ripper Rom. Worked of a couple days but was ultimately unstable.
I've recently flashed it back to the MK3 firmware via ODIN. It's still unstable.
I've determined it must be some hardware fault in the tablet, and I'm going to sell it for parts. I've bought an ASUS transformer TF701T tor replace it.
I wish you luck and hope your problem is software only. But I've heard many of these tablets go unstable after a while, and fear it is a hardware thing.
Marc

Android app issue

Hello,
We have a custom application that was developed outside of our org and we are in the process of obtaining the source so i am going to be vague but hoping someone can perhaps point me to some ideas until i get it.
When you install the application, run it, log in to it all works fine. You come back a day or 7 later for example and you now are brought immediately to a white window. This is where the login is supposed to be.
I haven't tried this on anything else but samsung devices so an s5 and s6 Android 6.0.1 and it happens on both. Both of these are old verizon phones.
To resolve it at least with these 2 devices is to go to settings/accounts and delete the account that gets setup as part of the application it seems. Once i do this and exit out of the app, open it back up i am brought to the login screen as i would expect.
For some the above does not work but simply clearing out the cache seems to resolve the issue.
Last, uninstalling and reinstalling the application has also worked for some.
for a period this worked without issue and then all of a sudden started doing this. We aren't certain if there was a change in android that resulted in this or what. Anyone have any ideas how to get us back on track here?
Thanks.

Google Assistant repeatedly stops working, claiming it's not the default assistant

Hey guys,
I recently bought a Chinese Android car head unit from a pretty random AliExpress seller. The unit is based on a chip that doesn’t have a lot of info about it on the web: AC8257 (Probably some sort of a MediaTek). I know those Chinese units and ROMs can be pretty funky, but this one actually works pretty well, both on the car side and the Android/Google apps side. However, I do have one small, yet very annoying problem that I can’t seem to solve on my own: Google app (Which includes the assistant) did not come preinstalled with the device. I’ve manually installed it from the app store, and until my first reboot, everything seemed to work fine. The assistant could be called both by a key-press and by “OK/Hello Google”. So far so good. The problem first appeared upon restarting the machine. When I tried calling the assistant, I got a message saying that Google assistant is not set as my default assistant (See attached photo). I went to the settings, and guess what, it seemed to be set as the default (See attached photo - No other option other than “None” were available anyway). I chose it again anyway, and indeed, it started working properly again. However, 30 minutes later, even without a reboot, it happened again. And again… You get the idea.
I did some googling (Both for the AC8257 and the assistant problem itself, contacted the seller and searched wherever I can, but the results were dull). I tried solving it by doing the following:
Using adb and root rights (Through ADB, not a permanent root), I installed the apk in priv-app, didn’t work. I then tried moving the Play store installation the priv-app, also did not work. I also tried disabling something called DuraSpeed, which, as far as I understand, is a performance enhancing tool by MediaTek that can sometimes cause this kind of thing, but that ,sadly, also did not help. In addition, I also tried resetting the device completely, to no avail. The only thing I didn’t try is installing a clean ROM and then installing OpenGapps, but that’s not possible right now (Couldn’t find any ROM for this device and CPU).
I know this might be a problem that is specifically related to my device/ROM, but as I can’t find a lot of info about it pretty much anywhere, I thought it might not be such a bad idea to ask this question in a more general forum.
Many thanks to you all,
Noam.

I have the same problem.
If you solve, tell us. Thanks!

Try to figure out what event took place at the 30 minute mark. Try to see what apk pops up in the cache when it crashes.
You can try clearing the system cache then the data of the apks used if that doesn't get it.
Try resetting network settings if communicating with bluetooth.
Eventually you'll find it if you keep playing with it... Androids wuv being played with.