Hi,
I have a problem where every so often the screen will randomly wake up. It's like a notification has come in but it hasn't
I've tried GSAM Battery Monitor and it looks like Maps is responsible. Not sure why it is doing it though or how to stop it without disabling Maps and I don't want to do that as I use the latitude background features.
It's annoying when it lights up the room randomly at night!
Anyone have any ideas?
this has existed since 4.0 on the G-nex, i forgot the fix, but maybe check the q&a forum of the g-nex...
It could be Google Now notifications
Sent from my Nexus 4 using xda premium
It's not Google Now. When it happens there are no pending notifications at all.
Several posts on the GNex forum discuss the kernel but it seems this might be a bug in 4.2
I'm getting this too, it happens on my N7 too but only after the 4.2 update
I have this too. It's supposed to be a bug in Android 4.2
Already logged with Google: http://code.google.com/p/android/is...=ID Type Status Owner Summary Stars&start=400
Related
Hello,
I am not allowed to post in the developers thread and advised to ask here.
I have used Xylon-Rom before, did today a clear installation (factory reset, cleared all caches + data) and have some issues with the actual b2-build:
-white statusbar -> when trying to change it, xylon settings crash.
-Xylon PIE -> can't get it to work. When enableing it, nothing happend.
-Customizsation of Notification light -> where are the settings for it?
Thanks if someome can give me some advises.
Regards
Robsterboy
Hey there man, the white status bar is a known issue in the latest stable and sadly there is no simple fix for it, I'd advise just waiting for the new release which is bound to be any day now.
Once you've enabled pie did you switch to expanded desktop mode? It can be difficult to get pie to appear with the navbar still there.
Edit: the led settings are at settings->XY tools->and then LED at the bottom
Sent from my Nexus 4 using xda app-developers app
I read so many complaints and issues with this ROM.
I just got my Nexus 4 last week. I rooted it right away, and installed Xylon 02-23 build, with Matrix kernel v7.0
I have zero issues at all. No problems, not one reboot in a week, no FC. No status bar problems. Maybe I got lucky, but everything just works as expected.
Battery life, with this kernel has been great. On average heavy use workdays 12 - 15 hours total usage, with constantly getting 5h On Screen time each day. On weekends with WiFi getting a full day easily.
Sent from my Nexus 4 using xda premium
Some of the issues are hard to spot cause you don't realize they're issues, ROMS like Slimbean and Paranoid Android are rock solid, some of the issues I encountered last I used Xylon were a memory leak (RAM would get used up and wasn't coming back at a certain point, either that or the recents RAM wasn't reporting properly), Mixcloud wasn't streaming music with the browser, PIE implementation is buggy and is invisible at times (same as Carbon and Rootbox) etc worst is the dev is a ghost in his thread
Thanks Sliming,
LED now works fine
Okay. Now have to wait until new Beta will be released.
Regards
Robsterboy
Hi all,
I have a problem with the Play Store on my Nexus 7 what is bugging me since I got the device and that I never experienced on any other Android device I own(ed). This problem has been present from the beginning with any version of Android (got the Nexus 7 with 4.2.1 and got the 4.2.2. update quickly) and Play Store. Even the brand new 4.0 version that has been rolled out just yesterday (the bright one with the new tile design) showns this error.
The problem is this: in 3 of 4 cases when I hold my device in portrait mode and start play store and update an app, the screen constantly "flashes" every second while downloading, it´s that graphical "zoom in" effect that you get when you open an app. The problem is that I can´t leave this screen with the "back" button, it simply doesn´t work and the page keeps on flickering and showing that strange effect. Only the "home" button helps. After downlaoding and installing the update, everything woks fine.
What I already tried to get rid of the problem (none of them did help, though..):
- deleted cache and data from paly store, uninstalled update of play store, so Android reinstalled updates
- tried new version 4.0 of play store
- deleted, rebooted and reinstalled gmail account on Nexus 7
Anyone experienced this glitch? Any hints on how to solve this?
Thanks a lot,
Markus
Try stopping Downloads and Download Manager in Apps > All and clearing cache and data for them. Then reboot and try Play again.
My nexus been doing the same thing since new but in landscape mode only, annoying, but never bothered me too much. I just try to remember to keep portrait mode while updating.
Sent from my Nexus 7 using xda premium
Exact same issue here's. No idea what's causing it
Sent from my Nexus 7 using XDA Premium HD app
samo samo
Kusie said:
Hi all,
I have a problem with the Play Store on my Nexus 7 what is bugging me since I got the device and that I never experienced on any other Android device I own(ed). This problem has been present from the beginning with any version of Android (got the Nexus 7 with 4.2.1 and got the 4.2.2. update quickly) and Play Store. Even the brand new 4.0 version that has been rolled out just yesterday (the bright one with the new tile design) showns this error.
The problem is this: in 3 of 4 cases when I hold my device in portrait mode and start play store and update an app, the screen constantly "flashes" every second while downloading, it´s that graphical "zoom in" effect that you get when you open an app. The problem is that I can´t leave this screen with the "back" button, it simply doesn´t work and the page keeps on flickering and showing that strange effect. Only the "home" button helps. After downlaoding and installing the update, everything woks fine.
What I already tried to get rid of the problem (none of them did help, though..):
- deleted cache and data from paly store, uninstalled update of play store, so Android reinstalled updates
- tried new version 4.0 of play store
- deleted, rebooted and reinstalled gmail account on Nexus 7
Anyone experienced this glitch? Any hints on how to solve this?
Thanks a lot,
Markus
Click to expand...
Click to collapse
mine does same thing, portrait or landscape. every time the download pct increases, causes flash on right-side text. also did in v.3 of store.
PIA! Tried clearing cache and data, no change.
dond624 said:
mine does same thing, portrait or landscape. every time the download pct increases, causes flash on right-side text. also did in v.3 of store.
PIA! Tried clearing cache and data, no change.
Click to expand...
Click to collapse
This still happening for you all? Mine is pretty bad on my new nexus 7. Never noticed it before.
flicker
belogical said:
This still happening for you all? Mine is pretty bad on my new nexus 7. Never noticed it before.
Click to expand...
Click to collapse
I've been playing with roms and kernels lately, settling on Buttered Grouper 4.2.2 with Franco kernel r65. Just noticed the other day that Play Store flickering is gone. Coincidence?
Dond624
This has been happening since I got the Nexus on release day. Thought it was normal behavior LOL. Completely stock -> Stock 4.3 ROM rooted/M-Kernel a61.
belogical said:
This still happening for you all? Mine is pretty bad on my new nexus 7. Never noticed it before.
Click to expand...
Click to collapse
Wow, it´s still present on the NEW Nexus 7 ? Unbelievable, maybe time to jump off the Nexus bandwagon ... most people think it´s a huge advantage to have a nexus and always the newest android version, but to me it´s more and more a disadvantage. When 4.3 came out half of my apps stopped working, and i had to wait several days and even weeks (heck, some are STILL not compatible with 4.3) to use them again...
Does anyone else experience the sleep of death bug (akin to what happened with Netflix) after having connected your HDTV through Slimport for a short while? It seems to happen regardless of what I'm doing on my phone, just having it connected for a short moment will cause it.
This is on stock Android 4.3 (JWR66V), whereas it was working just fine for me on 4.2. My phone is rooted, but there's nothing running that requires root access while this problem occurs.
Also, I'm using the "official" Slimport adapter, i.e. the only one that existed for quite a while.
Would hate having to send my phone back in, but alas that's what I'll do if it's just affecting me.
I've the same issues since 4.3 Everything was fine before with 4.2.2. When i unplug slimport from nexus4 i cant activate display anymore.
This hapepns sometimes after cahring, too.
So i think your device is ok, just an 4.3 fault like many other bugs
Thanks for the reply. So I'm not completely alone with this!
But I do find it odd that I could not find any existing discussion of this topic elsewhere on the net.. are there just not that many people making use of the HDMI feature or is the majority of people simply unaffected by this problem?
I'm not sure. I've the same issue with charging. I misspelled this on my first post. Same situation, unplug charging cable and i can't activate the display. I found a workaround for this issue, I unplug it only when the display is on. The latest OTA doesn't fix it. Maybe we should create a bug report on googles bug tracker.
There is a thread about this issue in Googles mobile support forum. You should post there, too. So maybe we get more attention about this serious problem. I can't post links yet, search for: "After 4.3 Android updated, the Nexus 4 always shuts off randomly !!! HELP!!!"
I'm having this issue with my Nexus 7 II. Very annoying, can't watch a movie without it disconnecting. Any fix for this?
Currently not, I hope that Kitkat will fix this
I'm having the same problem on 4.4
Does anyone know how to fix this?
Thanks in advance
Same here on 4.4 but it only happens when my photo is low on charge.
E.G when there's low charge slimport works o.k but when I unplug it the phone dies and requires me to push the power button for 10 seconds to get the photo to work again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Maybe we should dump Logcat to get the reason why it dies. It tried it several times but with no luck. When i received System log ouputs via adb, the phone doesn't die.
Gesendet von meinem Nexus 4 mit Tapatalk
was found a solution for this problem?
My Moto360 has started not displaying a card notification when receiving a message via WhatsApp. All other notifications are vibrating and switching on the display with card, but WhatsApp it just vibrates.
I have tried uninstalling and re-installting whatsapp, tried re-syncing the apps, but WhatsApp continues not to switch the screen on ... any ideas?
You haven't blocked whatsapp from showing notifications on your 360? Its easily done by accident. You might have swiped then clicked on block this app. If you go into your wear settings, then blocked apps, check to see whatsapp isnt there.
Sent from my SM-G920F using Tapatalk
Nope, checked that .. nothing in the Blocked Apps. The phone vibrates, so it is getting the notification, but unlike all the other apps which vibrate and switch the screen on, this just vibrates. When I wake the screen, the notification is shown
Yeh, sorry, when I re-read your post I realised you couldn't have whatsapp in the blocked list if you are getting the vibration. #facepalm ?.
I had a similar issue with not receiving cards for my outlook work emails on a different device to my 360 a while back, it turned out to be an app I had used to set a custom vibration pattern for my outlook notifications. Im guessing that if you had a similar app installed you would have checked that.. also Im sure you would have tried a restart of your 360..
I think the problem is with your 360 as your phone is clearly pushing the notification to your 360 if you are getting the vibration. I know an app resync usually fixes most issues but as you've tried that what about a factory reset of your moto 360? I know its a bit drastic but I don't know what else to suggest.
Sent from my SM-G920F using Tapatalk
Tried a reset as well ... the funny (annoying part), is that the screen on notification did work for a while, and then just suddenly stopped, withouth me installing anything, so not so sure it is an issue with the Moto 360, as all other notifications pop up ..... WhatsApp is the only one that does not
Yeh thats really odd. Maybe someone else will have a suggestion that can fix it. What version of the 360 do you have? Ive got the smaller mens 2015 version. I'm at the end of my tether with it tbh for other reasons. The lag on the the device is so bad for me its virtually unusable by the end of my working day. Im gonna sell it and get the watch urbane instead.
Sent from my SM-G920F using Tapatalk
I have the 1st Gen, and to be honest I am more than happy with it, even with the outdated processor in there, don't really get that much lag with it .... and taking it off charge at 7 in the morning, and putting back on around 10pm ... still gettng about 40%+ battery left.
Surprised the 2nd gen (2015) version that you are having lags with it, have heard it was supposed to be rock solid
What other issues you having?
I get "android wear has stopped working" at least twice a day. Which means it can crash without me knowing so i miss notifications and calls throughout the day. Thats my biggest gripe at the moment. Then the lag progressively gets worse throughout the day, the only way i can fix it is to do a reboot but at its worst it can take 2-3 minutes for me to get into settings then another few minutes for each option in settings to load before i can choose restart device. I tried a factory restore last night but its already crashed 3 times today..
When i compare it to my other smart watch my 360 doesn't have that 60fps smoothness when navigating the interface. I did read that if you disable ambient then the lag isnt so bad but i like having ambient on.
I'm planning on making a YouTube video of how bad it is over weekend.
Sent from my SM-G920F using Tapatalk
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
albie999 said:
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
Click to expand...
Click to collapse
Thanks for the reply. I think I'll try out your suggestion now. Need my watch working, I've come to really rely on my watch for notifications as I can't have my phone on during working hours. It got so bad today with the lag and crashes I had to use my Razer Nabu instead of my Moto360.
Fingers crossed, I'll let you know how it goes [emoji106]
Sent from my SM-G920F using Tapatalk
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
albie999 said:
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
Click to expand...
Click to collapse
As the moto 360 2015 doesn't have a cable, its wireless charging only, how would you reflash a previous version of wear? Im kinda stumped lol
Last night I did another factory reset and i uninstalled a lot of apps that i didn't want running on my moto. Some apps seem to have a companion wear app for their mobile equivalent that automatically install.. Well ive taken a lot of crap off and i have seemed to have fixed the stability issue. Also i can use my device albeit with a small amount of lag. This i can live with for now, it seems that moto knows about "always on" causing lag on some devices. I'll hold out for an update to fix it [emoji106] [emoji3]
Sent from my SM-G920F using Tapatalk
Ah, should have said .. it is not Android Wear on the watch, but the companion android wear on the phone that I installed an older version. Don't believe you can actually change the version on the actual watch
I have ambient mode off, wifi off (dont really see the point) and tilt to wake off ... as it kept coming on when I changed gear in the car lol
install quick for wear
i know it's an old thread, but i still have the problem in android wear 2.0.
whatsapp notifications are extremely unreliable. it's like the developers do every single thing their own way.
i set my watch to show notifications until i swipe it away or down, the very few times whatsapp actually shows the notification it goes away after a few seconds.
the notifications do work, as i can manually swipe to the notifications and they're there. they just refuse to show automatically.
i'm not a heavy user, so i get few notifications of which most of them are from whatsapp. so my watch functions more like a normal watch.
Whattsapp issues wear 2.0
I too get a buzz but no card till I manually swipe up anyone managed to fix this whattsapp support are useless auto gen email each time
Hello,
Every time i am driving my car i am using Blitzer for speed cameras and Amigo for warnings on the speed limit. Since i updated the S10+ with Android 11 i have noticed that as soon the display goes dark, both apps stop working. With this, i mean they both lose GPS connection so i do not receive any warning. Did not have any problem before the update, now i do not know what to do. I've tried everything. They are both NOT battery optimized, with all permissions granted, an still nothing works. What is worse is that even the GPS connection is not so stable as before. It takes a lot more time to get a GPS signal although i did not change any setting.
Does anyone had the same problems?
Thanks in advance!
Later edit
So, for those interested, i have solved the problem for both apps.
For Amigo (by TomTom) the solution i have found it was switching the Location permission from "Only when it's in use" to app to "Always". It started working again in the background.
For Blitzer.de i have the solution by accident. The culprit was a Bixby routine that was suppose to start the app as soon as it was connecting to my car's bluetooth.
As soon as i started the app manually everything started to work again in the background.
I would like to point out again that both apps were working just fine until i have updated to Android 11.
Hope that my findings will help also someone else having similar problems.
Happy Easter !