Hi,
My dad's tablet started acting strange after he updated to cyanogenmod snapshot m6. The home button doesn't work, quick settings bar doesn't open and the quick search by swiping the home button up doesn't open. I tried updating to the latest nightly, but no effect. I also tried going back to an older nightly but it didn't help. Clearing cache not working either. Anyone an idea how to solve these annoying issues?
Thanks
Edit: Also when you unlock the screen, it skips the security and when I click on an item after searching Google with Google now only opens a new tab I'm chrome, not loading the link.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Jiddeee said:
Hi,
My dad's tablet started acting strange after he updated to cyanogenmod snapshot m6. The home button doesn't work, quick settings bar doesn't open and the quick search by swiping the home button up doesn't open. I tried updating to the latest nightly, but no effect. I also tried going back to an older nightly but it didn't help. Clearing cache not working either. Anyone an idea how to solve these annoying issues?
Thanks
Edit: Also when you unlock the screen, it skips the security and when I click on an item after searching Google with Google now only opens a new tab I'm chrome, not loading the link.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should probably post this to CMs Google+ community.
Related
So weird problem started a couple days ago. When I'm navigating using Google Maps, it only shows the bird's eye view instead of the 3D view that I'm always used to?
I've looked all over in the settings and can't figure it out.
Anyone suggestions?
I THINK tap the blue arrow.
psykhotic said:
I THINK tap the blue arrow.
Click to expand...
Click to collapse
Right, NORMALLY that would do it, but it doesn't in my case. So frustrating. WTF?
I tried seeing if I could get the problem and couldn't. Instead all my maps turned grey
Reset the data and cache of that app and see if that fixes it.
Sent from my SGH-T999 using xda premium
Don_Perrignon said:
Reset the data and cache of that app and see if that fixes it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
That is what worked for my wifes phone at first. I had to delete cache and data, then uninstall and install the app again. Seems to have fixed it for a while now. The screen was also flickering a lot while in navigation.
OhioDroid80 said:
That is what worked for my wifes phone at first. I had to delete cache and data, then uninstall and install the app again. Seems to have fixed it for a while now. The screen was also flickering a lot while in navigation.
Click to expand...
Click to collapse
Just tap the compass (red and white) top left.
Haizum74 said:
Just tap the compass (red and white) top left.
Click to expand...
Click to collapse
This didn't work for me. I had to delete the cache from app settings to get it to work again.
seanvree said:
This didn't work for me. I had to delete the cache from app settings to get it to work again.
Click to expand...
Click to collapse
well.... have you tried using two finger, swipe downwards...
I had this problem recently.
You must get a fix on GPS signal to have the mode revert from bird's eye view.
But if you still experiencing the issue, clear the cache, uninstall Google Maps and reinstall. Lock on a GPS signal and it will go back.
Make sure you have clicked on the blue arrow as well so that's not causing it either.
Hello! Since I can't post this in Sprint Galaxy Note II Original Android Development until I posted ten times so this is really for CyanogenMod 11 nightlies ROM experts.
I'm using nightly CM11 2/22/14 with plasma kernel. This issue has to do with a headphone jack while plug in and using either Apollo or any other music player. If I open another app the sound goes off but when I close the app the sound comes on. This is also true with using the status bar, when I move the status bar down sound goes off and comes back on when status bar goes back up. The same is also true if the phone goes to sleep.. again sound goes off.
There is no problem with the sound system when I unplug the jack. I haven't had this problem in the past with the Official CM11 ROM. Does this has something to do with nightlies? I tried using Soundabout and other music players but still no luck.
Anyone out there experiencing the same or know how to fix this? Any help would be grateful! Thanks in advance.
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
jplecher said:
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
Click to expand...
Click to collapse
It was the nightly! Seemed to be working fine now! :good:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Sorry just back from vacation... yes still using CM latest nightly 2/24.
Has this problem been fixed in the latest cm11 builds?
Blabah said:
Has this problem been fixed in the latest cm11 builds?
Click to expand...
Click to collapse
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Google Play Music's volume cuts off when Google Hot word detection if ON...
I had the same issue... and have tried multiple CM nightlies with the same result. it was driving me nuts. As soon as i changed to another application Or checked the status bar the sound would mute. You are correct in turning OFF the Google "hot word" detection which turns off "OK Google" as the solution to the problem. Not sure if the problem is on Google's end OR in the CM's Team's ROM?
Thanks,
NH Apache said:
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Click to expand...
Click to collapse
Headphone sound issue fix CM11
I found a fix that worked for me. Install AGNI CM OC kernel. During install, check off the 2nd option for sound engine. Not the one that says '(recommended)'. Worked for me, all is good now.
I have two identical phones that do the same exact thing. When I press the back button or the play store menu button, it crashes. every time.
I can, however open the menu by swiping right. I can also go back by pressing the back softbutton.
Both phones are the same with the same firmware and version. It doesn't do this on my nexus 7 using the same account.
I'm having this same issue. Did a factory reset and that didn't change anything. I'm wondering if the new version of Play is just broken with the OG :/
woxxy said:
I'm having this same issue. Did a factory reset and that didn't change anything. I'm wondering if the new version of Play is just broken with the OG :/
Click to expand...
Click to collapse
It is. On 4.1.2 Jellybean the Google Play Store crashes everytime when the left top tab is clicked using Sprint LS970 LG Optimus G. Flash Cyanogenmod 11 4.4.4 KitKat ROM and the crashing wont happen anymore.
RegKilla said:
It is. On 4.1.2 Jellybean the Google Play Store crashes everytime when the left top tab is clicked using Sprint LS970 LG Optimus G. Flash Cyanogenmod 11 4.4.4 KitKat ROM and the crashing wont happen anymore.
Click to expand...
Click to collapse
Same force close here on stock LGOG.
I just made it a habit of swiping instead of pushing the tab.
Open up playstore
Then from left side of the screen, swipe to the right. That the only way you'll see the settings and my apps section
Sent from my LG-LS970 using XDA Free mobile app
So the Google app updated for me today and now when I click on the search bar and search for something. As it loads the results the app will force close. Even does it when using voice search. I have cleared all app data and that works for a short time, but it resumes force closing again. I am completely stock unrooted. Anyone else having issues?
jdawg0024 said:
So the Google app updated for me today and now when I click on the search bar and search for something. As it loads the results the app will force close. Even does it when using voice search. I have cleared all app data and that works for a short time, but it resumes force closing again. I am completely stock unrooted. Anyone else having issues?
Click to expand...
Click to collapse
I had the same problem. Most of the time there was no force close dialog, the app just closed. It was about as annoying as bugs get. I didn't really nail down the issue. I think it was due to the theme I had installed. I went back to stock + cataclysm without a theme and haven't had any issues since.
If you have a theme installed maybe remove it and see if it fixes it.
Sent from my Nexus 5X using Tapatalk
Thanks for the advice, but as I stated I am completely stock and not rooted
Hi all,
After updating my unrooted OP3 to official Nougat, I am noticing that Google app can no longer run in the background. That is, any Google Now or Google search that I do in the phone dissappears from the multi-tasking windows as soon as I navigate away!
I tried clearing Google app's cache, data, opted out of the beta program. Doing so does get the app to run in the background as it should but only for a few minutes before the issue persists.
I reported the issue as a bug to OnePlus days ago but no response yet!
Can anyone help with this please?
try removing google from aggressive dose. go to battery, click the three dots on top right side and you can disable aggressive dose from there.
bonham1988 said:
try removing google from aggressive dose. go to battery, click the three dots on top right side and you can disable aggressive dose from there.
Click to expand...
Click to collapse
Thanks.
Aggressive dose isn't enabled.
Actually, I have even tried freezing the app from the multi-tasking windows (clicking the lock toggle at the tip right corner of Google app window) and even that doesn't work.
a77med said:
Thanks.
Aggressive dose isn't enabled.
Actually, I have even tried freezing the app from the multi-tasking windows (clicking the lock toggle at the tip right corner of Google app window) and even that doesn't work.
Click to expand...
Click to collapse
The lock toggle is useless. Half of the time apps are cleared even after that lock. But still your situation seems quite odd. Are you using updated version and if your rooted you can try uninstalling the app and reinstalling it.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
The lock toggle is useless. Half of the time apps are cleared even after that lock. But still your situation seems quite odd. Are you using updated version and if your rooted you can try uninstalling the app and reinstalling it.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
The thing is that I'm not rooted. First phone not to touch since the Galaxy S ?.