Database Develop

Voice Search Broken, says "Can't reach google at the moment."

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.

[Q] Insertcoin Issue

Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks

nonameguy321 said:
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
Click to expand...
Click to collapse
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.

385
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?

nonameguy321 said:
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
Click to expand...
Click to collapse
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.

majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
majmoz said:
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
Click to expand...
Click to collapse
Maybe I should have left out the part of the front facing camera not working.. or created that as a separate topic.
The one that I'm really having issue with is the Insertcoin Konfig settings not actually applying themselves.. tweaks on other ROMs worked without a problem..

[Q] Note 4 Lag and Fingerprint not working - tried everything

Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks

I have the Same Problem

I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?

Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?

So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.

'To Start Android, Enter Your Pin', no keyboard

So I have seen a few threads depicting this bug/error/whatever it is, that when starting Android it asks for a PIN, no keyboard shows up at all.
I recently changed my password, and I guess absentmindedly checked yes to asking for a password on boot. However, after the device's first reboot with the new password, I can't enter anything when it asks me to. On the bottom of the screen, there is an 'Emergency Dialer' button, but I cant even press that. Is there any way to fix this? I can decrypt the system through TWRP with the password just fine, so I know it's the right password, I just cant enter anything on the Android side of things. I saw some suggestions being flashing a keyboard (no idea how to do that), reflashing the ROM, even using an OTG cable (which I have, no keyboard though) but I don't want to mess up the device any more by doing any of these if it was somehow to mess with the password or encryption. Any suggestions, or idea as to why this happens? Any help is much appreciated.
Update: I tried to flash a Nandroid backup from before I started having this issue, and its still asking for a PIN.
Update 2: Wiped /system/, flashed ROM and STILL have the pin screen. TWRP still decrypts with the current password, not the one from the Nandroid backup.

I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.

Anova's Origin said:
I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.
Click to expand...
Click to collapse
Gave that a shot, reflashed my ROM both dirty and clean, restore from a very old nandroid backup, nothing has worked..
Did a system wipe and I'm still having the issue.

If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.

Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Click to expand...
Click to collapse
If a physical keyboard is the last option, I'll have to wait until tomorrow to get one I guess (I only have a laptop).
I know there's a way to use adb to input keyboard commands, but although I know I had debugging on it doesnt work on whatever this screen is called.
Thanks for the help though!

Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.
Click to expand...
Click to collapse
Would deleting the Swiftkey folder from /system/app or /data/app mess up anything? I'm pretty sure that Swiftkey is the culprit here.

No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.

Anova's Origin said:
No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.
Click to expand...
Click to collapse
Uninstalled it through file manager, and still no keyboard came up.
This is the most stubborn issue I have ever encountered, quite literally done everything.. except using a physical keyboard but even then, this issue shouldn't have persisted if I've wiped this many times..

You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.

Anova's Origin said:
You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.
Click to expand...
Click to collapse
Flashed a brand new rom instead, got keyboard up but it's telling me that my pin is incorrect. Still stuck

Wrong password at boot is a far more common problem. Fix

For me, turning off display and turning it back on popped up a keyboard, when it was an issue. Somehow fixed at one point.

Luckily i recently acquired the oneplus 3t and in one of my actions in preparing the device for daily use i had the same issue after I install a [MOD] zip, the only quick fix that work 4 me was boot in twrp recovery and wipe factory reset system dalvik / art cache, install oneplus 3t firmware
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/
just keep good 1 or 2 backups b4 u go crazy (or look for revert file) :fingers-crossed:

did you guys figure this out

Unable to unlock my lock screen after installing xpoosed.

Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.

Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk

bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?

Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk