Related
Have just sent my 3rd Vario back to T-Mobile with this fault, and think I will be getting another brand new handset back in the post, but not convinced it is fixing the fault.
When I use the phone for texting or making calls or any function, the screen appears to crash as while lines appear on one side of the screen, and slowly spread over the screen making it not respond to the touch - even if I could see what was there.
A click of the power button bring the screen back OK sometimes, but often have to do this many times or pull the battery out.
Have I just had duff handsets??
are you overclocking? when did it start? what rom, software, programs are you running? etc
bbobeckyj said:
are you overclocking? when did it start? what rom, software, programs are you running? etc
Click to expand...
Click to collapse
Alas I can only answer a few of the questions as the pone is away being repaired / swapped out, but I am not overclocking, the ROM is what it came with 3 weeks ago from T Mobile, I had installed the Skype s/ware but have not run in more than once, and it certainly was not running when this fault occurs.
The fault appears 5 or so times a day, in differing forms of severity.
I don't use skype myself, so I don't know how it runs in the background. but I think you need to overclock to get it to work well, or use the newer made-for-slow-devices version. other than that, i find sometimes i try out a new app and this problem occurs (even if others use it with no problems). I don't know if it's possible to have a combination of progs/apps which will cause this? but the fact that this is your third occurrence definitely suggests a user created fault of some sort, what other software do you use?
I use Messenger a lot on it, but apart from Skype have not installed any other software - it is all as it comes out the box.
does this happen before you install skype? try the version for ppc with slow processors
Yes it did happen before Skype, and am using the version you mentioned.
i'm only aware of this happening with extreme overclocking, and bad software. so, sorry but i'm out of ideas. when you get it back hard reset and don't install the extended rom, see if that helps, if you've not added much to it it may be a problem with the hardware (assuming they keep sending you the same unit).
I don't think many people run a stock setting and use this site, but hopefully someone else will have had a similar problem and help...
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
Don't you all agree?
not really. what bugs are you talking about?
I have had a G1, Mytouch, and now the Nexus - I see and have no bug issues with my Unit...
If you could explain what bugs (or problems) you are having ... Is this your first Andriod ???
zachthemaster said:
Don't you all agree?
Click to expand...
Click to collapse
100% disagree.
My phone is amazing. What bugs are you experiencing?
Be more specific? before or after the ota? Mine is still kicking a## after the ota!
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
You don't have to reboot.
Just turn the screen off for 3 seconds and back on...
lol
Not everyone has this "touch screen accuracy" issue...
I haven't noticed any bugs that jump out at me. I would like them to improve the speech to text, and would love them to get the kernel with full RAM support out ASAP. I was sad this update did not have that. But, in a month when we get the next one I am confident and optimistic it will make it into it!
New RAM kernel.
Trackball/LED notification fix.
If its software the bottom row of buttons being difficult to register.
Those are all legit HW/SW issues that are unique to the N1 and need to be resolved.
New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error
Paul22000 said:
New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error
Click to expand...
Click to collapse
Whether you label it as a "bug" or not its still an issue.
Half the available RAM not being used.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Those are 2 out of the box gimpings of available hardware.
And one either HW problem or design flaw. In which case can be chalked up to "it is what it is".
xManMythLegend said:
Whether you label it as a "bug" or not its still an issue.
Click to expand...
Click to collapse
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
Half the available RAM not being used.
Click to expand...
Click to collapse
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
Click to expand...
Click to collapse
I don't remember this ever being possible? When did they remove it?
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Click to expand...
Click to collapse
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
How about the dots which indicate the screen you are on being off.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
The wifi is very buggy, bluetooth as well. There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not. E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...
gibosn6594 said:
How about the dots which indicate the screen you are on being off.
Click to expand...
Click to collapse
This is a bug yes. Introduced with this week's OTA.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
Click to expand...
Click to collapse
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
The wifi is very buggy, bluetooth as well.
There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not.
Click to expand...
Click to collapse
Can you give specific instances of issues with these?
E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...
Click to expand...
Click to collapse
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me
Paul22000 said:
This is a bug yes. Introduced with this week's OTA.
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
Can you give specific instances of issues with these?
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me
Click to expand...
Click to collapse
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.
gibosn6594 said:
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.
Click to expand...
Click to collapse
Ah yes, I have noticed that turning on wifi sometimes it just sits there and doesn't connect until I open up wifi settings. Definite bug.
Oh, exchange. Yeah, I have heard exchange is pretty bad on the N1 (or non-existant without the file from the dev forum?). I don't use it so I can't comment. But supposedly, there will be a Nexus One Enterprise edition with full Exchange support, and a physical keyboard So maybe this one is not aimed at people who rely on it.
Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.
Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
Ive had the Droid and N1 side by side which is when I realized its a design flaw or OS issue.
Both the RGB trackball and 512mb ram were both advertised as such. Including in the initial press conference. Those arent feature requests those are hardware limitations that have yet to be addressed.
The ram limitation has at least been acknowledged.
As for the LED/trackball. Its been a feature since the G1. Theres bunches of apps including the most popular messaging app that allow you to designate different colors and flash rates for LEDs for notifications.
N1 is great but before we can move forward I would like for Google to address these pretty significant things.
MT was a major feature add. But the 3g fix is still plaguing many users.
All in all N1/Android 2.1 are fantastic. Googles lack of communication frustrates too many people.
Maybe Im too used to games but good Devs are constantly in touch with users concerning bugs and issues and are pretty consistent with "update/bug fix" information and ETAs.
The fact that google is just getting phone support hiring going is pretty silly.
Im an early adaptor so I know the risks. But this really is a barely past Beta piece of hardware. I dont see the harm in other early adapters acknowledging that.
Frankly if it wasnt for users ((and haters)) *****ing and moaning non stop I dont think MT would have been put out and a 3g fix would have been put off.
The way Googles worked recently whining gets more results then sitting and waiting.
dbaboci said:
Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.
Click to expand...
Click to collapse
I agree.
Heres my primary issue.
The guys at google seem like a bunch of brilliant engineers but rely rounds of feedback to get things right.
There creative and quality control people are suspect IMO.
Engineers tend to be a snobbish anti-social bunch. You dont want that leaking into consumer products. The communication pitfalls of this month highly reflect that mentality. They need another layer. They seem to desire it though so thats good.
ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
Same here,,,,,I encountered this problem once, after I had updated (never tired before update)..
I received a Z17 a few days ago and have really struggled with it. The phone feels really good but I am finding operation really difficult - the screen seems excessively sensitive. Most of the time when I touch or sweep the screen it register multiple touches - I hear multiple ticks. More often than not the app just tapped on opens then immediately closes (not force closing just going into background). Operating the phone is near impossible.
Is there a way to re-calibrate the screen sensitivity?
Short video showing the problem - https://www.youtube.com/watch?v=qpP6t2C3xeM
Bee
I don't have that issue. My screen issue is that it's too dark. I have to put it over 75% brightness or higher. I have a Bluboo Maya Max that also have an LCD screen from JDI that is pretty bright at 25% level.
Brightness seems OK here - although I might not be the best person as I typically run my screens at minimum/very low brightness unless I am out in the sun.
The sensitivity issue is driving me nuts though.
Bee
Updated to latest software version (2.44) but this has not improved the situation.
I have noticed that this is worst when I pick up and use the phone after it has been sat for a while. Things settle down if I continue to use the screen for an extended period of time - it seems like the screen is hugely sensitive and is picking up static on my hands.
Hopefully there will be a way to recalibrate the screen, maybe once root, unlocked bootloader and custom roms all become possible.
Still surprised no one else has reported this issue. Really hoping to find a way to re-calibrate the screen sensitivity.
Here is a video showing the problem. Basically it is nearly impossible to use the phone when you first pick it up, it does seem to improve after continue use.
http://vid61.photobucket.com/albums/h62/boboskinsbee/VID_20170709_124811_zpsmm58kw6r.mp4
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Bee
i will receive my Z17 on Tuesday... then, for my part, i will answer again.
actually i have an off topic question: u can use google chrome?
if yes, how?
any other google apps?
loquenz said:
i will receive my Z17 on Tuesday... then, for my part, i will answer again.
actually i have an off topic question: u can use google chrome?
if yes, how?
any other google apps?
Click to expand...
Click to collapse
Yes - chrome works. You will need to get from apkmirror or similar.
Like others I tried installing google framework & play but this didn't work. Google music would run but unless you have local files you can't do anything with it.
I REALLY want to like this phone but so far it just isn't usable as a daily driver.
Bee
boboskins said:
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Click to expand...
Click to collapse
boboskins said:
Updated to latest software version (2.44) but this has not improved the situation.
I have noticed that this is worst when I pick up and use the phone after it has been sat for a while. Things settle down if I continue to use the screen for an extended period of time - it seems like the screen is hugely sensitive and is picking up static on my hands.
Click to expand...
Click to collapse
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
boboskins said:
Hopefully there will be a way to recalibrate the screen, maybe once root, unlocked bootloader and custom roms all become possible.
Click to expand...
Click to collapse
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental
Not just me!
Sort of pleased someone else has the same problem! Agree that it isn't fixed in RR. Hopefully there will eventually be a solution.
I tend to deal with it by holding the phone between my two palms (i.e. holding my palm fully across the screen) for a second or so when I pick the phone up after it has been sat for a while. This seems to reduce the sensitivity (or remove static build up?) and things work normally.
Of course this shouldn't be necessary and not something you want to do when trying to answer a call.
B
qwertius2 said:
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental
Click to expand...
Click to collapse
I have the same problem
qwertius2 said:
I have the same problem, exactly as you describe it! It appears that it's the Recent Apps button that has the problem (at least on my phone) as it is the only one that activates on its own. It also seems as if it "accumulates" button presses when left alone, so it has to "release" them during the first couple of minutes that you pick it up again. Then it is more or less ok.
I was hoping the same but this is not the case unfortunately. Problem is still there with the latest Resurrection Remix (5.8.4). It's a shame, it's a great phone otherwise but this bug is driving me mental
Click to expand...
Click to collapse
Friend did you solve the problem with the resurrection remix? . I have seen a new update that says something about a bug I hope is the solution.
Daken.
boboskins said:
Still surprised no one else has reported this issue. Really hoping to find a way to re-calibrate the screen sensitivity.
Here is a video showing the problem. Basically it is nearly impossible to use the phone when you first pick it up, it does seem to improve after continue use.
http://vid61.photobucket.com/albums/h62/boboskinsbee/VID_20170709_124811_zpsmm58kw6r.mp4
If you turn up the volume (and watch the red home indicator) you will hear/see that each touch is being registered multiple times.
Bee
Click to expand...
Click to collapse
Hello Boboskins
Can't access to your video
Sadly still not found a solution. I have tried RR (up until about 10 days ago) and now using Mokee. Appreciate your comments on the recent updates - I will take a look at the log in case the latest RR updates solve anything.
EDIT: Ursus91, just took a look and Photobucket appears to have stopped allowing 3rd party views. I will upload somewhere else and update the link once I am done.
@boboskins : thanks, it should be helpful to understand the problem you encounter. I'm not sure to understand. And I'm still waiting to use the phone every day
I have the same problem
Same problème here ! When i use the phone it seems it close app or back like i hit the button. :/ Really annoying :s
Hello,
I have the same problem too. The sole solution from GeekB is to return the phone for repairing...
I have it sometimes on the left button (in the major cases), the middle button has actually no problems, the right, sometimes.
I use the middle button to come back to "the main view" (icons) and then, the left button seems going alive.
I'm not sure it is a hardware problem
Edge gestures issue
Greetings!
I've just started using Nubia Z17 Lite and found out that the specific edge gesture to control the brightness level doesn't work on my unit. Does anyone know if this is a bug that can be resolved by an update or did anyone have the same issue and has fixed it?
I'm quite sure the problem isn't with the hardware because other edge gestures seem to work fine.
Thanks ?
Nubia Z17 black screen
Good evening. I own a Nubia Z17 8gb ram 128gb rom and today had a problem. His screen is black and the LED on the menu button is on. It obeys no command. He did not fall, everything perfect. Could someone help me with this problem?
I have 2 PH-1s one of them has this random issue that Essential support says is software related.
Would appreciate input from fellow owners
https://youtu.be/61TOTt7iERk
Sent from my PH-1 using Tapatalk
I had this happen to me today after the Oreo update, but it was perfectly fine with stock 7.1.1
Anyone else seeing this?
I have noticed ghost touches as well following 8.1 official update. They now happen about 1-2 times per day. Nothing changed from before except OS version. Didn't have this issue on the beta either.
Turning the screen off and back on fixes it temporarily, but it comes back.
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
I also got in touch with Essential support a few days ago for the second time. I can tell their support is from the US which I appreciate in a company, but this phone is agitating and their troubleshooting makes it worse. All manufacturers from Apple to Samsung may make you jump through these hurdles but it's same issues with this phone. I believe they know it. So why waste my time asking about water damage and drops? Come on. I'm going to do a hard reset since I took the latest update but have already switched back to my s8 as my DD. I'll check if turning the screen off and back on again fixes it. Even if it's briefly I could maybe live with doing that. I couldn't get any letters to register when typing a text in the standard messaging app.
I bet the issue has something to do with the hardware. Ceramic and titantium? I know my reception is so much worse when Sprint's network is being put to the test on the highways with the Essential when compared to the s8. It may just end up being the perfect media player in the car. 128GB of music and use it as the Waze/Google Maps device...
coolmaster121 said:
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
Click to expand...
Click to collapse
Good to hear. In Canada we don't have that option. Let us know when f the problem is fixed or if it happens again. Like I said in my case the issue really started on Oreo 8.1.
Could grip detection have something to do with this?
sam2c said:
Could grip detection have something to do with this?
Click to expand...
Click to collapse
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
dhorgas said:
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
Click to expand...
Click to collapse
Exactly... It keeps occuring more often than not.