Database Users

The new ROM

I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?

As far as i am aware absolutely no issues whatsoever have been "fixed".
This "new" ROM is simply the latest version being shipped in worldwide devices.

The weekly calendar issue seems to be fixed.

kasperknop said:
I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?
Click to expand...
Click to collapse
I don't know what has been fixed and I can't comment on the problems you listed since I've never experienced them but I can tell you what works better for me:
1) the keyboard is much more accurate. I was reasonably happy with the keyboard on the last ROM but this one is much easier to use.
2) the proximity sensor now works every time I make or receive a call. This was a bit hit or miss for me with the last ROM and would fail more often than it worked.
3) Battery life seems much better. Again, I was pretty happy with this on the last ROM but it just seems to last a lot longer now. I had network issues today (nothing to do with the phone, it must have been a problem with 3 in London today because my 3G dongle was down as well) and was expecting my battery to die relatively quickly. However, despite this and the fact that I was playing with the phone more today (because of the new ROM) my battery is holding about 20% more than I would expect it to hold at this point in the day. I haven't bothered with the patch to turn off the data connection either so my phone should be doing more now.
I can't comment on much more. I experienced the new bug with the inbox and SenseUI but that was dealt with by locking the phone. I also had some trouble connecting to my Exchange server but that was dealt with with a couple of soft resets. Everything is generally going quite well.

kasperknop said:
I am about to download and install the new .48 ROM, but what excatly did they fix?
Are people sending and recieving all sms'es and calls now?
Are the buggy volume control fixed?
What about the big waiting time when launching the messenger app with people who have a long sms-history?
Click to expand...
Click to collapse
I have installed the new 1.48 rom today.
and I don't think they fixed anything. I still got a red blob on my pictures. And I still wait up to 45 seconds for replying sms. When the sms-history is long.!!!

I've installed it today as well (dutch version). A pity that you 've to reinstall all apps. No prob for me, as I'm still try to explore the phone.
Anyway connecting, installing etc everything was flawless, even the link with Exchange.

hmm,.. well,.. no issues so far
I've flashed the .48 over my belgian HD2 yesterday using the goldcard approach, I've got to say that I've yet to see any real improvement or bugfixes,...
The lockscreen acted up for a while but then mended itself automagicly and has been a good boy since.
Opera seems more responsive but that could very well be just me fooling myself.
Same goes for the keyboard, I caught myself noting 'hey, this seems a bit more sturdy than before'. This can all be attributed to perception, though
It works and the itch to be up to date has been scratched.. all in all I'd recommend it.

where do i get this rom, offical site please

Is this an official ROM?
Where can this be downloaded? How do you flash it?

Get the ROM from links in http://forum.xda-developers.com/showthread.php?t=592954
Just installed it and personally think the touch screen is more accurate

Eoinoc said:
Get the ROM from links in http://forum.xda-developers.com/showthread.php?t=592954
Just installed it and personally think the touch screen is more accurate
Click to expand...
Click to collapse
Think or know, is it night & day better mate?

Hi
Can anyone tell me if they have kept all the software that was on 1.43, for example, ms office.
If someone can tell us what they have removed or added, that would be great.

parv1 said:
Hi
Can anyone tell me if they have kept all the software that was on 1.43, for example, ms office.
If someone can tell us what they have removed or added, that would be great.
Click to expand...
Click to collapse
AFAIK they haven't added or removed any applications.

sunking101 said:
Think or know, is it night & day better mate?
Click to expand...
Click to collapse
I installed 1.48 last night and I think its night and day better than then old 1.43 rom.
Screen is less sensitive (which is good) because it makes the keyboard easier to use, less multiple key hits etc.. so you can actually type more accurately. I still get the odd moment where they keyboard appears to spaz out, but I think this is still down to accidentally breathing on the screen or looking at it in a funny way.. man that screen is so sensitive sometimes..
I also found that rotating and typing with both thumbs in landscape mode made for a very compelling typing experience because the keys are slightly larger and further apart which makes hitting multiple keys at the same time even harder to do.
Once you have used the device for a day or so (to build up its dictionary of words that you use alot) its becomes really very quick to rattle off very long texts.
Its still not quite perfect, but its a huge improvement over the previous rom.

Epic Keyboard Misses Keys

Hello guys!
Just got my Epic a few weeks ago to replace the old Moment.
Unfortunately.. I like everything about the phone except the main reason I got it over the Evo.. the keyboard. It seems to drop keys a lot, and I know for a fact I pressed them.
For example I can open up a text and type "lalalalalalalalalalalala" and it will drop a l or a or two. It's extremely annoying, the main reason I opted for the keyboard was for good accuracy when replying to emails for work..
As anyone else experienced this issue? Is this a software glitch or is hardware related? If this is a hardware problem.. I will be trading in for the Evo since I'm still within my 30 days.... not to mention the much better support Evo has for updates.. oh and my Network Based Location doesn't work.. wth really? So no location based app can find me with the real gps off. Why couldn't it of been HTC Epic 4g..
Anyways any input on the hardware keyboard would be greatly appreciated.

Sadly, this is a issue with the Epic's keyboard.
All of the Epic's i've played with have this problem, and I think its a combination of hardware and software.
Typing very quickly will cause it to lag and skip a few letters. You have to slow down about 2seconds and it will be fine.

Yeah, I was in the IRC talking to some people and it came off that its a known issue, happens in recovery to (although not quite as bad).. must be a hardware issue.. very disappointing considering the selling point to this phone over the evo is the keyboard mainly.
Does the keyboard have a buffer setting in the kernel somewhere? Maybe a seasoned developer would know haha, my gut tells me this is a buffer issue, you type to fast the buffer will fill up, and a letter or two will drop. Seems logical..

Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought

mikeschevelle said:
Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought
Click to expand...
Click to collapse
IF I hit the A and S key at the same time it properly puts in "as"..when I slide "asdfghjkl" it misses a few characters..its not too big of an issue for me as I don't type that fast but there is definitely something :/
Out of curiosity I also tested the same thing on an Samsung Intercept..and Intercept is not effected..

Seems like my keyboard has gotten worse over time. I can't type a word without missing a letter. Really annoying.

I have the same problem with mine. I figured it's a hardware issue and not really so much an issue with lag. I can hit a key and it just won't show up period so that's not lag.

I'm glad I don't type that fast.

It does it to me whether typing fast or not. Every time I send a text I allot myself time for corrections because I know every time it misses 1-2 letters. It's pretty annoying. Not only that but i'm constantly getting unsent txt errors with this phone...never had that problem before.

Ever since ditching Swype for Ultra keyboard I haven't had this problem. I have it enabled so that its auto correct system works for the physical keyboard as well.

I've also had this problem. Very annoying especially being a fast typer. I feel like it is mostly a software issue too. It would be nice to have one of the great developers here take a look into it. This is my biggest problem with the epic.

Yeah it is particularly sad, especially considering that phones like the G1, Motorolas Devour & Cliq (*Puke, my old phone*) as well as other mid-range phones could type flawlessly. Yet one of the best phones in the world IMHO and you can't even type as fast as you'd like.
I'd also like to start a bounty for this soon, I'd be glad to donate to any developer that tracked down the issue and abolished it. (Unless its a hardware issue, in which case were just screwed.)

I am starting to get it as well. Seems to be a known issue but very annoying. If it gets any worse I am just going to get a single piece phone case and say goodbye to the keyboard forever. Sucks to say it but there is no point in using a keyboard that is inaccurate to the point that I need to go back and correct things when I know I typed it correctly the first time

Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.

Yeah I noticed I need to slow down. I come from the touch pro 2s sick keyboard.
Sent from my SPH-D700 using XDA App

Gotta say I was having the same problem... then someone here said to try ultra keyboard... and for some reason it has stopped missing the keys.. so I do believe it is more of a software problem. I am on the 24 hour trial and so far it works.
Sent from my SPH-D700 using XDA App

I personally believe this is a software buffer issue with this particular keyboard.
Every physical keyboard needs a buffer, even on your PC. I think if we could increase the buffer on our Epic's keyboard driver which is built into the kernel we could alleviate this problem.
If a actual Dev would be willing to check it out that would be awesome! Not sure if Froyo still has this problem.
I agree with the disappointment... my Moment never missed a beat texting with the keyboard or writing an email, my Epic with all of its potential drops the ball in this department currently.
I hope it can be fixed. And no the solution is NOT to type slower..

I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings

muyoso said:
Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.
Click to expand...
Click to collapse
no its not the problem..I did a test by pressing both "a" and "s" key at same time and it registered as "as"..if that was the problem it wouldn't have registered that
Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
I just disabled swype and did the "asdfghjkl" test and it worked flawlessly...I then re-enabled swype and it still worked fine :/ (running the dj29 froyo rom)..we may need more testing into this I guess?

Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
Sometimes I use swype whenever I need to type a short message. It's the best of both worlds. Sad if you need to disable one of the features just to get the keyboard to work properly.
EDIT: Look at the fail rate when typing ab for a solid minute on my KB:
Abababababababababaababababababababababababaabababababababababababababababababababbaababaababababababababababababababababababaabababababababababbabababbababbabababababbabaababaabbababaababababababababababababababababababbaabababababababaababababaababababaabababababababaabababababababababababaabababababababaababababaababababababababaabababababababababababababbabababababababababababababababababaababababb
This is with swype disabled.

Gingerbread issues

Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.

very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.

by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?

yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.

Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?

sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.

I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).

^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.

RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.

[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..

Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!

I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.

[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.

If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.

The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1

I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.

A little situation...

Recently I discovered that every time I use Bluetooth headphones, the left-upper corner of the BB Priv does not "detect" the touch.
For my relief, I found our vía Dev options that physically the screen does detect my touch but somehow the OS stop registering until a few hours after I turn Bluetooth off or restart the device.
I know this is a software flaw in need to be fixed by BlackBerry but I would like to know if this is happening to anybody else or should I begin deploying an army of emails to BlackBerry.

There are dedicated threads about this issue on CrackBerry

can you tell me which thread? i have this problem also

Yes please, as an update, I avoided much possible using bluetooth and yes, it is for connecting a headset, in my case a LG Tone Pro.

http://forums.crackberry.com/showthread.php?t=1058388
Here's one, some people are saying it has to do with FB Messenger

Wonder if it has something to do with Chat Heads, I think they by default spawn in the top right corner. I've never noticed the issue myself, and I do use bluetooth occasionally, but I always disable Chat Heads immediately whenever I install/reinstall messenger.

I've noticed it seems to need a few taps on the top edges of the screen - I wonder if it's just a design and manufacturing compromise those? It's a curved screen and as a result the touch points will be handled slightly differently to that of a flat screen.
Maybe something that can be solved with software..

adaimespechip said:
I've noticed it seems to need a few taps on the top edges of the screen - I wonder if it's just a design and manufacturing compromise those? It's a curved screen and as a result the touch points will be handled slightly differently to that of a flat screen.
Maybe something that can be solved with software..
Click to expand...
Click to collapse
In my case, I know that Android did register the touch by using the dev options tools, this has to do on how BlackBerry programmed their Android version, but I already installed February Bulletin and hope that BlackBerry applied their own hotfix.
Will tell you soon.

AT&T confirmed that the problem with Priv and other Android device is related with older version of FB Messenger.
I found it odd because in my case was triggered using a Bluetooth device but o well, at least that was resolved.
You need to delete FB Messenger app data first and unistall it via App settings and you need to re install again.
Apparently Facebook already resolved the faulty code that messed with the screen input.

TheGeeZus said:
Recently I discovered that every time I use Bluetooth headphones, the left-upper corner of the BB Priv does not "detect" the touch.
For my relief, I found our vía Dev options that physically the screen does detect my touch but somehow the OS stop registering until a few hours after I turn Bluetooth off or restart the device.
I know this is a software flaw in need to be fixed by BlackBerry but I would like to know if this is happening to anybody else or should I begin deploying an army of emails to BlackBerry.
Click to expand...
Click to collapse
No problems with me yet. I regularly use BT headphones.
Sent from my STV100-3 using Tapatalk

Screen sensitivity & recalibration

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?