Related
NOTE: This is a list of bugs for STOCK (NON-MODDED) ICS 4.0.3 & 4.0.4 (LC4, LD2, and LE2) (Most bugs from the initial LC4 leak fixed after the two major version leak updates) from DesignGears.
If you have flashed to ANY OTHER CUSTOM ICS 4.0 ROM, PLEASE WRITE IN THE DEVELOPERS' / ROM thread.
1 - 03/26/2012: When selecting "Contacts to Display" and selecting CUSTOMIZE LIST > Selecting ONLY Google Contacts (EXCLUDE G+).
Then you start typing someone's name, it returns contacts in SIM card and on Google contacts.
2 - 03/26/2012: Autocorrect on the included "Android Keyboard" doesn't work by pressing spacebar.....like it had been in previous 2.3.6. Even when changing setting to VERY AGGRESSIVE. FIXED IN UCLD2 LEAK
3 - 03/26/2012 [CONFIRMED] When deleting a message thread, the phone will freeze and turn into a blank screen (except notification bar) then the messaging app will close. FIXED IN UCLD2 LEAK
4 - 03/26/2012: [CONFIRMED] When using the "PHONE" icon to bring up dialer, contacts tab is no longer associated in it.
5 - 03/27/2012: 50/50 Users report more sensitivity on the touch screen, some report lack of sensitivity of touch.
6 - 03/27/2012: HOW TO take screen shot: Press AND HOLD ... VOL DOWN + POWER BUTTON for at LEAST 1-2 SECONDS. You will then be prompted to view the screenshot in notification bar / indicator.
METHOD #2 of taking screenshots: Press and HOLD Power button + HOME key.
7 - 03/29/2012: Some users report when tapping "RESTART" or "SHUTDOWN" on STOCK Power-button option, the phone will freeze. Either you have it or you don't. FIXED IN UCLD2 LEAK
7 - 04/02/2012: Users report echoing or unable to hear other party on an INCOMING call. This is a "hit or miss" bug.
8 - 04/02/2012: [CONFIRMED]Bluetooth stack in the new kernel has resolved a LOT of vehicle-to-android phone issue (static, drops, functions, etc.).
10 - 04/04/2012: [CONFIRMED BIG ISSUE] When creating a new contact in phone and setting it to GOOGLE CONTACTs; forcing a sync or auto-sync option will NOT push the contact to google servers for backup purposes. However, deleting or creating a contact while logged in on a full web browser will push it back to the phone via sync. FIXED IN UCLD2 LEAK
11 - 04/09/2012: [CONFIRMED] There are known issues with stock email app. Syncing unread/read e-mails will not push back to exchange server email client. Also emails me not completely send and stays "stuck" in outgoing box.
FIX (Thanks dixit):
This google thread shows the official issue and show that it was fixed officially in 4.0.4.
https://code.google.com/p/android/is...etail?id=23534
If you scroll down to post 51 you will see there is a link where someone put the two 4.0.4 APKs from a Spring Nexus S 4G which fixes this issue as explained above. So just go to that link, download the two Email/Exchange APKs, put them in System/App, correct permissions, remove your two Samsung Native Email APKs, and that will fix the issue of emails being stuck in the outbox.
Here is the direct link to those two APKs off Post 51
http://files.devphone.org/404mail/
11 - 04/15/2012: [CONFIRMED] When adjusting ringtone level in SETTINGS > SOUNDS, the ringtone level will not lower or raise; it stays at one level.
FIX: Adjust via volume rocker while in any other system screen (Home, MMS, etc) BUT NOT IN-APP. *Thanks petrochemicals!*
Here's what I found and posted in another thread...
So far so good except a few things:
1) I hate the fact that "contacts" are no longer visible in the dialer. Now I need another icon that I rarely use. The only option appears to hit menu and select contacts from there.
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
3) Can't use built in hotspot tethering anymore. This is something that I use with my tablet often. Any solutions other than a 3rd party app? If not, what app is everyone using for hotspot tethering?
4) Why in the world don't the signal bars turn green once fully connected? It's driving me crazy because normally that means its not connected to your Google account. This is the first time I've seen this (of MANY different Android phones). - This appears to be an ATT thing as other carriers and phones change the signal bars color when its connected to your google account (as it always should be).
Grey bars, works for for me; turning green = same color as battery = confusion to some it is acting as a double icon of ur battery? lol
I don't get a freeze in the menu.... I'm assuming you're talking about the built-in menu not a modded one? I just use the one that came with the ICS.
Hotspot tethering, you'll have to wait for a dev to mod that unless you are wanting an app for it.
I can tell you that I got my portable hotspot to work. It gave me numerous error messages though when I first went to set it up and the screen freezes when I turn it on. I went back to home and back to the hotspot settings and the toggle remained on. I changed the default password to all 9s bc I was getting an invalid password error. After that, I connected my old iPhone to the Skyrocket wi-fi.
I used to use Barnicle Wi-fi tether but it doesn't work now. Is there a difference between the stock portable wi-fi hotspot program on the phone and Barnicle? Im just curious if Barnicle masked the fact that the user was tethering.
Sent from my SAMSUNG-SGH-I727 using XDA
Yes, I'm referring to the built in power menu. I fixed permissions in CWM and still no go. Any ideas???
I find the keyboard to be a bit slow on the responsive side. Anyone else running into that or am I just trying to type too fast?
Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.
good job guys, keep up the troubleshooting so hopefully some devs will cook up a nice rom
fongz27 said:
Perform a Factory data / reset?
I find the new keyboard fairly responsive vs the old one; I just thought i typed too fast for the old one lol. This one actually keeps up and Swype keyboard tapping works more fluent as well.
Click to expand...
Click to collapse
I'll give that a spin. I did that once already to fix my home button problem, so I'll try and do another. But yea I use to use the ICS keyboard from the market on GB, and that was quick enough for me.
stuff I notice so far
I did notice the contact tab missing from dialer. The menu selected one doesn't allow right and left swipe for call/text. In the contacts app, the swipe works ok.
the only real problem for me, thus far, is when deleting SMS threads; messaging force closes.
Anyone else have that?
BTW thanks for starting this thread, wasn't sure where to post bugs - I think this may be usefull to keep them all in one spot.
Getting some odd behavior from Rom Mngr
Aside from other errors I got, when I ask ROM Mngr. to perform a task, I get a bunch of errors like "Messaging has failed," "Internet has failed," "com.google.xx" has failed. But then it goes and performs the request.
However! Whereas on 2.3.6 UCLA3, when requesting a backup via ROM Mngr., it would go straight to the backup whereas now, it goes into CWM and I still have to select Backup from the option there.
Deleting threads freezes my messaging also.
Sent from my SAMSUNG-SGH-I727 using XDA
Noticed a new one.
Not getting pictures with messages now, too.
Nvm. Damn - I hate bug posts. They come, they go.
The only thing I've noticed so far is I don't seem to get LTE in my house anymore. Boo...
I'm having issues with audio files. I can't use either Google Play Music, Samsung Music Player or Doubletwist to play audio. It creates duplicates which I believe corrupt the file itself.
Sent from my SAMSUNG-SGH-I727 using XDA
jayrod88 said:
2) The "power off" and "restart" options in the extended power menu (hold power button down) seem to lock up and freeze whenever I try to use one of these thus requiring a battery pull. Anyone else experiencing this?
Click to expand...
Click to collapse
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.
rjohnstone said:
I get it too, but there is no need for a battery pull if it freezes during a restart.
Press and hold the power button and the phone will restart after a few seconds.
It's a leak, not an official release, so I fully expected bugs.
Face unlock crashes a lot for me.
It fails o power on the camera and then the keypad doesn't respond for PIN input.
Requires a reboot.
Click to expand...
Click to collapse
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.
fongz27 said:
Did you do a complete ext4 wipe / format prior to ODIN ONE CLICK ?
Run factory data reset, then fix permissions and then reboot. Face unlock works perfect and pin input works.
Click to expand...
Click to collapse
Yep.
Face unlock does work... just not all the time.
have you done "improve facial recognition " if so how many additional pictures did you take?
Facial unlock is perfect for me. No problems whatsoever.
Sent from my SAMSUNG-SGH-I727 using XDA
Solution: I have installed swype, and it seems they use a different system for voice transcription which works just fine! However this still doesn't fix the issue for people who don't like swype. But my Mom does like swype so it works out.
Hello, I just got my Mom a LG Optimus T today, and I have successfully flashed the CM10 rom for my Mom's LG Optimus T. I trimmed it and it works great. I found out that these devices can't use the google now voice function, bummer.
But this thread: http://forum.xda-developers.com/showpost.php?p=36781540&postcount=126
Says that voice can work for google now through the keyboard mic. However the stock keyboard doesn't have one, so I installed swiftkey and the mic button gives an error when I long press it. Any Ideas? The keyboard voice functionality is kind of important to my Mom, she couldn't care less about the google now voice, just the keyboard. Thanks!
Edit: The keyboard Mic button doesn't show up for either stock or swiftkey keyboard when in google now, but it shows up in browser. Both keyboards give the same full screen "Exclamation Mark in a triangle" error when mic is pressed, when it's available in browser.
Do I have to downgrade my mom to ICS and lose Project butter to be able to have voice transcription on the keyboard?
Edit: I have installed swype, and it seems they use a different system for voice transcription which works just fine!
Electriccars said:
Solution: I have installed swype, and it seems they use a different system for voice transcription which works just fine! However this still doesn't fix the issue for people who don't like swype. But my Mom does like swype so it works out.
Hello, I just got my Mom a LG Optimus T today, and I have successfully flashed the CM10 rom for my Mom's LG Optimus T. I trimmed it and it works great. I found out that these devices can't use the google now voice function, bummer.
But this thread: http://forum.xda-developers.com/showpost.php?p=36781540&postcount=126 ...
Click to expand...
Click to collapse
Now, one can (well, almost but ...) have the whole hawg!
Here is how:
Buy (will not break the bank) the voice-search-assistant app.
Buy (creepers!) the paid version of Overlay (featured on recent portal!).
1. Create an app-profile for Google Search.
2. Drag the shortcut icon to the upper right corner.
3. Select voice-search-assistant.
4. Set minimum icon size, no text, transparent background, minimum visibility.
5. Reposition at upper right if need be.
6. Set start Overlay at boot.
Now when one clicks Google Now's mic icon, one gets the voice-search-assistant instead!
(Would love/prefer to do this as an Xposed/framework module. Means learning this API and doing some serious mid-level programming. Overlay does the job well enough, no need for other apps.)
Yeah, thanks but that's not the main issue. My mom just wants to have keyboard voice functions. Which only swype can give apparently. Otherwise she doesn't care.
But furthermore, it's not even an issue anymore! A few days after getting this phone for $20 off of craigslist, I saw an ad for 2 HTC sensations for only $180! At first I thought I was top late as he posted 6 1/2 hours before I saw it, but I text the guy, emailed him, the next morning I tried calling him, then I tried calling with a different phone and he answered! I talked to him and it turns out it was a mistake to answer, he had been trying to wait and text everyone at once later that night. But because he talked to me I was able to meet him after work. I had to wait with my sister 4 1/2 hours because he went to a get together with his family but it was worth it! Now, along with myself, my Mom and sister both have fantastic phones!
But this'll still be my brothers phone until we can get him a really good phone as well. And it's awesome when running jelly bean. thanks for trying to help!
And keep your eye on craigslist! You never know what luck you'll have.
Sent from my HTC Sensation using Tapatalk 2
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
Hi,
Just got my unlocked Pixel 4a today. No custom roms or anything. Android 11. Build RQ1A.201205.008.
I'm a bit of a minimalist, and I went through the keyboard settings for messages (it had this little emoji bar thing that also did the predictive words I wanted to get rid of). Also in that bar was the microphone for voice to txt. When I shut off those unneeded options and turned the dedicated numerical row on, the microphone disappeared. I've tried resetting the options to the best of my memory, but it still isn't back to where it was, and the microphone is still gone.
There is another microphone in the preview box, but that is a tap-and-hold-to-send-a-recording microphone. Not what I'm looking for. That works.
I checked permissions, Gboard has permissions. I checked the keyboard settings, voice to text is enabled. Anyone know the 'magic combination' of options to get this back? I use it frequently!! I'd hate to have to reset-to-factory just to restore this one feature.
Thanks!
I finally found it after much headaches. It seems the voice to text microphone is part of the "suggestion strip" that is under "Text Correction". No idea why this isn't integrated into the keyboard as it's own icon as it's been in earlier versions of Android.
If anyone has any recommendations on how I can potentially make that integration and get rid of the suggestion strip, please let me know.
I tried to reproduce the missing voice2text mic that you reported and failed.
I went to Gboard settings > text correction then:
Disabled show suggestion strip
Disabled next-word suggestions
Disabled emoji suggestions
Disabled sticker suggestions
Going back to the keyboard, the suggestion strip/stickers/GIF/clipboard/settings and the mic were all gone.
I re-enabled all the above and the mic reappeared, along with the other stuff.
One thing you could try short of factory reset is to go to the App Info for the Gboard, force stop, and clear the cache. Relaunch the keyboard to see if it brought the mic back.
---
Looks like you resolved it. I think this design change was made a few cycles ago and am not aware of any way to re-integrate it. You could try SwiftKey to see if that has the feature you want.
I think installing a different keyboard can be helpful here. Have you tried to do it? To be honest, it was one of the most significant problems that made me change a model of my phone. I did have a Samsung Note, and the problem with the Gboard was repeating very often. I have been browsing different sites to find a solution, but was never successful in it. One day, one of my sisters visited me and took my phone while I was in the kitchen. She fixed the problem instantly, would you believe it? I came to the room and was surprised after she showed me it. She said she visited https://techplugged.com/5-best-solutions-to-fix-the-gboard-not-working-error/ and followed all the instructions given there. I have forgotten about the problems with Gboard for a long time, but there were other reasons for me to change my phone to the latest iPhone.