Related
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
They must also fix
1)Choppy browser with and without flash.....
2)Random freeze of the gingerbread launcher...
slateac said:
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
Click to expand...
Click to collapse
I think it was posted that the reboot fix was coming, but not the loss of data.
Maybe I am just a lucky one, but I have had Nexus S since release and have only had a "random reboot" once; and no data signal loss issue AFAIK like Engadget has described. I have owned three Nexus Ss.
There are other issues, though, making it clear 2.3 is not bug free.
fchipm said:
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Click to expand...
Click to collapse
and they didn't even give us XDA credits
Perhaps 2.4 is coming sooner than planned and the fixes will be implemented in that? Just a wild guess.
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
i'm hoping they fix the quirky back button as well. that thing is driving me crazy!
I recommended the nexus s to my girlfriend, but seeing all these issues are making me regret it :\ there are no fixes/workarounds?
Sent from my SPH-D700 using XDA App
aaaaaand... 10char
Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item.
Click to expand...
Click to collapse
that was fast.
Weird. I haven't had a single one of the issues described in any form. However, the browser issues do make me angry.
Glad there is a hotfix on the way (for the issues mentioned, that is, not necessarily the browser issues)!
The only issue that regularly bothers me is the vanishing ringtone one. It's not exactly critical from a utilitarian standpoint, but I think it's stupid that I should have to root and move files around my phone in order to set a custom ringtone. Still, I'm far too happy with pretty much everything else to switch.
I think one major sticking point with the Nexus S is that we have a fairly lengthy list of at least semi-common issues, but in several cases it's not clear whether those are hardware- or software-related. This is troublesome because the latter may be reasonably expected to get fixed in OTAs, while the former will probably only ever be resolved through workarounds, if at all.
I would be very pleased if Google were more transparent about what it's working on, or at least aware of, even if they (understandably) don't want to commit to fix dates. As a user, just knowing the basic nature of these problems and that they are being acknowledged would go a long way towards improving customer satisfaction in my book.
SooSpecial said:
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i read that there will be an ota update, but (maybe its a noob question) if your rooted will you still receive the update, and if so will it unroot the phone??
Fix the GPS!!!!!
Fix the keyboard: http://www.youtube.com/watch?v=RUZdvr6Pdjk
Discussed more in depth at this thread: http://forum.xda-developers.com/showthread.php?t=932838&page=13
So yea... my DVP locks up every once in a while, crashes, etc. Is this normal? I'm getting kind of annoyed and ready to do an RMA, but I can't be without a phone (obviously).
Just curious if I'm the only one or not.
Depends on what you mean by once in a while. Short answer is a rather high percentage of 16GB DVPs have major stability/lockup issues (lots of threads here about it), most 8GB are fine. Supposedly Dell will release a firmware update in the next couple weeks to adress it.
Yea, I have a 16GB so I guess that may be my issue.
Any location for the announcements from Dell on the issue? I'd love to see that update sooner than later.
HerculesSAS said:
Yea, I have a 16GB so I guess that may be my issue.
Any location for the announcements from Dell on the issue? I'd love to see that update sooner than later.
Click to expand...
Click to collapse
Best thing to do is watch the boards here and follow Dell on Twitter. Most DVP news on Twitter comes from @LionelAtDell (http://twitter.com/lionelatdell) and on the #dellvenuepro hashtag (http://twitter.com/#search?q=#dellvenuepro)
Mine's 8gb and it locked up quite often, up to couple times a day. I started to think about returning..
Since NoDo my DVP has started to lockup randomly too. Before it was just with wifi, but now it seems rather arbitrary. Hopefully the firmware update will bring this one down too.
Mine was locking up primarily while in marketplace on wifi, then while charging. Now it's locking up while Zune is playing. Funny how it started locking up more after my 30 day refund warranty was up. I'd love to get my money back, but Dell says I can't. Now I'm waiting to see what my attorney general has to say about it.
It's ironic that when I viewed this link through my phone, it locked up my phone.
*sigh*
HerculesSAS said:
So yea... my DVP locks up every once in a while, crashes, etc. Is this normal? I'm getting kind of annoyed and ready to do an RMA, but I can't be without a phone (obviously).
Just curious if I'm the only one or not.
Click to expand...
Click to collapse
You are not the only one suffering with the random lockups. It is getting quite irritating with or without the no-do update. I am still randomly getting the lockup while charging but "especially" when using Internet Explorer. From my experience, using the browser seems to be much worse with the no-do update on my phone. I cannot tell you how many times the frozen/lockup situation occurred to me within a 5 minute span. Loading a site, freeze. Opening a tab, freeze. scrolling through a site, freeze. The phone basically works whenever it wants to work. I'm sorry but this is absurd and I hope the new update will solve these issues. If not, many people including myself will be extremely unhappy.
It seems after the recent Bell 0.37.23 update there are less items in the usage statistics under Battery Manager. It used to display the % of battery that apps used. Now it only shows Display, Phone Idle, Cell Standby, Voice Calls. Is anyone else experiencing this?
Yeah I noticed that last night. Was wondering what happened....
Don't like it this way.
Well that sucks. It was a good way to see if apps were running in the background and chewing battery.
What are you guys using from the Market to replace this missing feature?...
Sent from my MB860 using XDA Premium App
I've noticed the same issue on my phone. I emailed Motorola for support on Tuesday but haven't heard back a response yet. I also reported the issue with Bell and they just directed me to Motorola. Glad to see I'm not the only one with the issue though. Makes it sound more intentional than a bug.
Just got this response from Motorola:
"Looking into our data base on our end, I'm not showing anything being shown as a known issue. A lot of changes has been made to the device, unfortunately if the options are no longer available that would indicate a change after the update.
I hope this was helpful, if you have any other questions or concerns feel free to contact Motorola at 800-461-4575 or you can visit our website to find our FAQ's user guides and much more.
Thank you for choosing Motorola, and have a great day!"
Pretty much a completely useless response. Maybe the Gingerbread update in "late summer" will help to resolve the issue.
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.
Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
dbal said:
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
Click to expand...
Click to collapse
Thanks for your answer. Basically, the problem as I see might be related to GBoard or Moto Display, as you say.
Also, I don't know if you've checked the logs I uploaded, but there are a lot of OMX decoding errors, I'm almost sure that there's no hardware failure there.
I'm now going to unlock Bl and see what's up with a custom ROM.
Sent from my Moto G Play (4th gen.) using Tapatalk
------
EDIT: Before proceeding, disabled Moto Display. Will give more feedback later.
Anyways, flashing again got the issue completely gone. Maybe your theory is the most appropriate.
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
dbal said:
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
Click to expand...
Click to collapse
BTW, I've already disabled Moto Display. I haven't fell asleep yet and it's 7 am here. Tomorrow I'll keep testing and hope it doesn't fail anymore. If not, I'll go for Bl unlocking and get rid of this Motorola's buggy attempt of softly modded AOSP.
Sent from my Moto G Play (4th gen.) using Tapatalk
Here I've uploaded a screencast of what appears to be related to the bug and shows clearly it's a software bug related to the video render in Marshmallow.
https://youtu.be/qhmUN43y0Pk
Sent from my Moto G Play (4th gen.) using Tapatalk
facuarmo said:
and shows clearly it's a software bug related to the video render in Marshmallow.
Click to expand...
Click to collapse
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
dbal said:
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
Click to expand...
Click to collapse
Sometimes, life's about taking the risk.
I've unlocked BL, flashed recovery and installed AOKP.
Now, no flickers found.
Prove:
https://youtu.be/T3e8-6dnyl0
Hope you like guys, and you take the risk too. Flashing a ROM solved everything.
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
dbal said:
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
Click to expand...
Click to collapse
I've compiled a kernel based on Squid2's sources with the fixed SELinux setup, then you should see no flickers so far in any ROMs.
Mine's working without any flicker, but I've only tested in Custom ROMs. Maybe you can try on stock?
https://forum.xda-developers.com/g4-play/development/kernel-somefeak-moto-g4-play-t3544556
Good luck and sweet flashes! :fingers-crossed: