Hi All,
Running stock but rooted (with Xposed modules) 4.4.4 on Verizon Moto X with an unlocked bootloader. (Flashed this stock ROM: http://forum.xda-developers.com/showthread.php?t=2829123 )
Any time I try to do any activity with voice I get the error, "Can't reach google at the moment."
I get this error if I click the mic in google now and by clicking the voice text mic on the keyboard. Also, Touchless Controls doesn't respond.
After searching around forums I've tried some suggestions that worked with similar problems on other phones, but to no avail. I've tried:
- clearing data and cache of google search app and force stopping (lost my google now launcher set up in the process)
- removing my google account from the phone, rebooting to recovery, clearing cache and dalvik, rebooting and adding my account back
Thanks for any suggestions.
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
ericizzy1 said:
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
Click to expand...
Click to collapse
Hmm, interesting...
I'm thinking it's not a specific Xposed module... I just tried uninstalling xposed framework altogether and then wiping cache and dalvik for good measure. No luck.
But out of curiousity, these are the modules I have installed: GravityBox, Exchange Bypass For Xposed, SingalIconsAOSP, Unicon. Besides GravityBox, did you have any of these installed when you had the issue?
I hope this doesn't come down to just wiping, which it most likely will.
My droid maxx has had the same problem since the update to 4,4,4 I have tried everything including a fdr ( through twrp ). Nothing has worked ! Moto has offered me a new phone but I don't want a new one as mine is unlocked and rooted ( otherwise stock ). I think I'm going to unroot it, put back in the stock recovery and try a fdr through that...POS !!!
This may not help at all....but maybe worth a shot. If you try and it doesn't help, post back here and let everyone know so nobody else tries it.
You might have some luck by erasing baseband cache with fastboot:
fastboot erase modemst1
fastboot erase modemst2
You might have to re-activate afterwards. It is the only suggestion that might be relevant that you haven't tried already...
Good Luck....that would be a frustrating issue... :good:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
leffer said:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
Click to expand...
Click to collapse
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
tombaldwin6 said:
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
Click to expand...
Click to collapse
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
leffer said:
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
Click to expand...
Click to collapse
I will try both methods and post back. Thanks for you help !
So I took both suggestions tried them 1st. I tried erasing the the baseband cache's via fastboot. No luck. 2nd I reflashed the current 4.4.4 stock rom via HOM, Full FXZ ( no data saved). !st off what a pain in the ass it is to reset up these phones from scratch. I setup my Google account but I didn't let Google reinstall all my previous apps and there data. I then went into settings and arranged things how I like them. Cleared off my home screens, put a few of the apps where I wanted them. I then went into the play store and allowed all apps ( preloaded ) to update. I then went back into settings and went to touchless control. To my surprise it worked ! I then went about loading all my apps.The usual 1's everyone has ie: Elixir2, FX filemanager,Poweramp, MX Player,Chromecast Panasonic tv remote 2, Google Wallet, UE Miniboom and Few other nondescript. Then I checked touchless control again and It was still working. Then I decided to install twrp and its recovery via fastboot ( 2.6.31 ) let it root the phone for me. Here's where it gets dicey.. It was late and I had had it with this friggin phone. I went and loaded all my apps that required root,Superuser pro, Dsploit, Busybox pro,Android terminal emulator, Wakelock(full) all the usual's. Then I went through and disabled all of the bloat. Rebooted and switched the phone to ART The following morning I went to show a friend how I had fixed my phone and It no longer worked ?
So I FXZ'd again not saving any data. Reinstalled twrp , rooted . Then 1 by 1 I reloaded every single app back into the phone and checked google now between every single install. Also this time I didn't let any of the bloatware update. I planned on disabling it anyways so why bother. I didn't install any apps that require root except twrp, busybox, Dsploit and #mirrorenabler . Also it's currently back on Dalvic. So as my phone sits now touchless control and all of its functions are working again. It's obviously a rouge app or ART Runtime that did this and I will narrow it down in the next few days and report back.
Was handing off my phone to my son, moving on to an LG G2, I let him test it out under my account, he added his account and phone was a little sluggish since the extra account was taking up more RAM, so he hands it to me while I was in bed and needs help, I factory reset it thinking it would just wipe out my personal data and allow him to enter his, well it did, but now he lost Root and I am stuck on the 1st nightly with memory leak...
Any method available to reroot this phone when in 5.0 so I can continue upgrading with nightlies? Or am I in a world of hurt now?
Justatechie replied in another thread, THANKS!!
Thats not going to work, it only works with the stock atrix hd 4.1.1
Cm12 can be rooted by going into developer options on the phone,
under root access (its disabled by default)
Just tap on it and allow apps or app and adb and it should be all set.
Other people prefer to flash supersu by going into recovery, just download the latest and put it where you will find it when you use the recovery.
I completely forgot about that, I had enabled developer mode, but nothing else, thought the reboot into advanced options was default, which it was not and slightly had a panic attack.. Thanks for the save...
Running apps stay running after a flash...
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
sobitthen said:
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
Click to expand...
Click to collapse
Apps will continue to run if you reboot. This is not a bug but a feature from Lollipop
Well, as far as I understand, Dalvik does not exist anymore as the JRM is now ART, but there might be a cache associated as well ?
Anyway, on my previous phone (S4 mini plus), I used to recovery 20% performances after cleaning cache/dalvik once a month through the embedded recovery (well my phone was also rooted but I know that this could be done with full stock).
With my XZ1 Compact, I can't boot to recovery, I believe the feature is block by Sony (damn I miss root so much).
So, is there an alternate way to clear this cache ?
I have an issue since the latest firmware update where location and timer icons do not disappear from the status bar after they have been turned off, this is annoying, I hope a cache clear could solve this...
JackyJacks said:
Well, as far as I understand, Dalvik does not exist anymore as the JRM is now ART, but there might be a cache associated as well ?
Anyway, on my previous phone (S4 mini plus), I used to recovery 20% performances after cleaning cache/dalvik once a month through the embedded recovery (well my phone was also rooted but I know that this could be done with full stock).
With my XZ1 Compact, I can't boot to recovery, I believe the feature is block by Sony (damn I miss root so much).
So, is there an alternate way to clear this cache ?
I have an issue since the latest firmware update where location and timer icons do not disappear from the status bar after they have been turned off, this is annoying, I hope a cache clear could solve this...
Click to expand...
Click to collapse
Factory reset?
There is a handy app System UI tuner, you have to add a couple of cammands via ADB to get it to work on non-rooted. But it will get rid of unwanted icons.
Nope, the factory reset is not a solution, I just want to wipe cache, not data.
Thanks for the tool, but this wouldn't fix my issue that seem actually related to the latest firmware (I'm not looking for uninstalling apps from system).
JackyJacks said:
Nope, the factory reset is not a solution, I just want to wipe cache, not data.
Thanks for the tool, but this wouldn't fix my issue that seem actually related to the latest firmware (I'm not looking for uninstalling apps from system).
Click to expand...
Click to collapse
I wasn't talking about uninstalling apps from the system
Hello there, wondering would you share it here if you did find a solution?
Thanks
I can't get into recovery mode neither on XZ1c...
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance ?
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
dodjob said:
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance
Click to expand...
Click to collapse
Hmm, i will try this when I get home from work, thanx.
Benjamin_L said:
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
Click to expand...
Click to collapse
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
minnuss said:
Hmm, i will try this when I get home from work, thanx.
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
Click to expand...
Click to collapse
Let us know!
dodjob said:
Let us know!
Click to expand...
Click to collapse
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
minnuss said:
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
Click to expand...
Click to collapse
That sucks big time ? the only time I got a freeze was as I wanted to empty chrome beta cache. After the reboot, all went back as it should be...
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
minnuss said:
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
Adb root shell. Can't think of a way this could damage anything if you just set the one property
hacktek said:
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
Click to expand...
Click to collapse
Did you have device rooted for a while, or it was always stock ?
Benjamin_L said:
Adb root shell. Can't think of a way this could damage anything if you just set the one property
Click to expand...
Click to collapse
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
minnuss said:
Did you have device rooted for a while, or it was always stock ?
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
Click to expand...
Click to collapse
It's always been stock.
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
kaiwanted said:
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
Click to expand...
Click to collapse
Yes this happens when lots of I/o is done on the internal disk. I hope this is just a missing optimization and not a hardware issue. But let's bug xiaomi with it. I assume you also have the 64GB version?
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
I read a lot regarding how people brick their phone with TWRP and rooting, so for now I will not use this future. But to reset my phone I will think about. Anyway I need this phone to use all my applications, not only a couple of them, because of this freezing (.
Thanks for suggestions.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
kaiwanted said:
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
Click to expand...
Click to collapse
I did the same thing. Went through my application list, uninstalled everything I didn't need and the issue went away. I cleared like 5% of storage space with still over 50% left but it seems to have helped.
reflashed all stock, enabled camera 2 api using mi a2 toolkit (magisk method) and I have the same. Cleared everything and run flash_all.bat. enable cam 2 api again and still have the same issue. clean install of apps doesn't fix it. Any idea on how to fix the sudden freeze?
Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
if I completely root the device, I will still have the random freeze?
also, if I factory reset the device in the settings, the camera 2 api will be gone? thanks
minnuss said:
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
I did it via twrp and adb shell setprop persist...
No issues here at all.