Related
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!
Do you check virus from your phone ?
I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.
Only hangouts? I have that app disabled.in the app settings.
I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.
Hi everyone,
I have had the Moto G 2nd Gen for about 10 days now and I have noticed that notifications from several apps (Exchange email, Gmail, Whatspp, Facebook...) are either delayed by a few hours or don't come at all. This happens on both Wifi or my network. Has anyone else experienced this ?
I have tried the following with no success:
1- disable Wifi optimization
2- factory reset phone
3- Installed PNF No-Root and set hearbeat to 5min
4- Cleared data & cache of apps
My phone is not rooted running 4.4.4
Thanks
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
I have tried 1, 2 and 4 of your attempts to fix it to no avail.
Before I reset the phone all notifications showed the correct time that they should have come, for example if I slept the phone at 10:40 and a notification came at 10:44, I then woke the phone at 10:50 the phone would immediately buzz and sound but it would say the notification came at 10:44 in the notification draw.
However after the factory reset of the device in the same situation the notification draw would show 10:50 but I know that is wrong because WhatsApp for instance will say the correct 10:44 timestamp on the message in the app.
Notifications when the phone is awake come through perfectly every time.
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Mine is the same as yours XT1068 8GB Dual SIM Retail GB 21.11.14.titan_retgb.retbgall.en.GB retgb.
I also have the same problem with music, I also noticed this with chromecast, it seems to loose connection after playing one track.
I contacted Motorola assist and they said replace the phone. I'm not sure if replacing it will solve the problem, I'm guessing this is a software issue. I
I got it from Amazon UK, I'm thinking of returning this and going back to my Galaxy Nexus and wait for the new Nexus phone.
Because we have the same software version I more strongly suspect this is a software issue now, I'm not sure what to do, I don't really want to return the phone as I will be left phoneless and a replacement would just come with the same software.
Another option would be to re flash to a different software version (an international version) but that will invalidate the warranty.
Not really sure what to do, would be good hearing if any retGB people are not having any problems, if any are reading this thread? or if any non retGB are having this problem.
jay2the1 said:
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
[...]
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Click to expand...
Click to collapse
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
bhavin192 said:
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
Click to expand...
Click to collapse
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Been testing on 3G, after the phone is slept all notifications work perfectly for 10 minutes with the phone buzzing a second or 2 after my tablet, if you sleep the phone and send a message after 10 minutes the phone will only buzz after 30 minutes from being slept (ie the heartbeat).
I've reinstalled PNF app and will experiment more tomorrow, still not sure how I will fix WiFi but I think a little more experimentation is required (yet doesn't make sense why my tablet always works 100% and the phone doesn't when using the same router)
jay2the1 said:
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Click to expand...
Click to collapse
I agree with you that it has something to do with phone going to sleep. My WiFi router is Netgear. I have they same problem with every other WiFi network and also on 3G. I didnt have this problem on my previous phone Galaxy Nexus.
PNF doesnt seem to work at all.
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
anshumandash said:
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
Click to expand...
Click to collapse
I have posted this on the Motoral forums here https://forums.motorola.com/posts/dbb4806484
I have been experimenting again today, the problem is significantly worse on WiFi notifications are much slower than on 3G, the problem seems completely unreplicable, sometimes notifications come though aOK even after I have left the device sleeping for an hour (using WiFi) or sometimes the notification will be delayed for several minutes even if it has only just been slept (again using WiFi), 3G on the other hand there is a definite 10 minute cut off from sleeping the device.
I've had PNF installed since last night and it doesn't help WiFi at all, but 3G it might, I say might because sometimes after 10 minutes (even an hour later) if I send a notification I do receive it straight away (something that never happened before I installed PNF) but then sometimes it doesn't and it's delayed for several minutes again.
I will join the Moto forum and add my weight to that when I get back to my computer as you need to sign in with a Google account.
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
jay2the1 said:
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
Click to expand...
Click to collapse
I have also noticed that. It seems that many are having this issue, so far no reply from Motorola
Motorola might be investigating about it. Yesterday i went back to dalvik from art. I tested the notifications the while day. On Wi-Fi, i didn't see the delays any more. In 3g many tests were successful even after 1hr of deep sleep. Only at 4pm India time i found a delay of 22 mins for whatsapp notification. There i also realized that it had switched to 2g due to bad signal in that room. I was definitely having problem when i was on art. Last night i also got the ota for build 23. I see that the kernel is updated. I will monitor one more day and report here.
Motorola has at least seen the post even with no reply, I just hope they are busy behind the scenes working out what is wrong so they can fix it.
I've never used ART (I'm completely stock), and all the problems are still happening today, unfortunately Telegram is being DDoS'd today so haven't been able to test anything out.
It will be interesting to hear if the update you received helps in any way, esp with the updated kernel, since your retGB device received it hopefully ours may do soon too.
As far as I can tell it doesn't affect calls and SMS, but I simply don't use SMS or calls at all (WhatsApp ftw) so my testing has been the odd 'prank' phone call from my 2nd phone and it rings every time, but it's not enough to confirm if it's a fluke or if in fact it does not affect phone calls/SMS.
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
That's good news, hopefully the update has indeed fixed it, there's no indication when the update will hit the UK but if it does fix it then ASAP I hope.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
katkat911 said:
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
Click to expand...
Click to collapse
In a different thread Motorola amin had mentioned that they are investigating the notification delay issue. I don't see much delays after the update. There are few mins here and there, but mostly good. If you haven't received the update yet, check the ota thread and update manually. It's the same update. Then see if you find any improvement.
I got the OTA update yesterday and I'm still having the same issues
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.