So it appears I may have experienced my first hardware problem. Randomly I started having issues this evening with the Dragon, Fly! Game where the back menu would randomly appear while playing. At first I figured it was a terrible ad implementation added into the update that just went through for the game, but then i started experiencing the same issue in multiple applications. This has me worried. I am not running a custom kernel. Has anyone else had this issue yet?
bl4ckcontact said:
So it appears I may have experienced my first hardware problem. Randomly I started having issues this evening with the Dragon, Fly! Game where the back menu would randomly appear while playing. At first I figured it was a terrible ad implementation added into the update that just went through for the game, but then i started experiencing the same issue in multiple applications. This has me worried. I am not running a custom kernel. Has anyone else had this issue yet?
Click to expand...
Click to collapse
You know, that was happening quite often last night when my girlfriend was playing Bunny Shooter... I claimed she was accidentally hitting the back button, but it happened too many times to be her own fingers doing it.
I wonder if the buttons are just too sensitive?
I actually was playing a game, and accidentally hit the back button, and ended my game.
It's the reason I've always been a physical button fan for those four buttons.
I don't see any advantage at all to making them all capacative - too easy to hit accidentally, there's no deliberate "press" required.
geolemon said:
I actually was playing a game, and accidentally hit the back button, and ended my game.
It's the reason I've always been a physical button fan for those four buttons.
I don't see any advantage at all to making them all capacative - too easy to hit accidentally, there's no deliberate "press" required.
Click to expand...
Click to collapse
I know the reason... it saves a couple pennies in production, and, at least in theory, nonmoving parts are far less likely to break.
BUT, I also prefer physical buttons. Especially for ending a call and taking pictures.
I miss the trackpad my Moment had, too...
Related
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
So, this seems a little odd, but while in a game (like minecraft or scribblenauts) the touch input is delayed ONLY for specific things. Typing, swiping, etc are fine, but quick tapping on in game controls is delayed. For example, in baseball superstars I can key in the player name fine, but when I go to hit the bat swing icon to hit the ball, I have a 1 second delay.
The issue is consistent, which leads me to believe there is something set in the system intentionally causing the delay.
It doesnt happen in anything else. I can type and web browse and do other things just fine. I know its not the apps because I have 2 note 8.0 devices both setup same rom and everything and the issue is not present on the other one.
Ive done multiple resets, tested different roms and kernels, stock and otherwise, and no change.
I checked with showing touch inputs in developer mode and its showing every touch in all games and apps..... its just as if the games themselves are intentionally delaying the response to the input on certain functions.
Anyone have any advice?
phoenixbennu said:
So, this seems a little odd, but while in a game (like minecraft or scribblenauts) the touch input is delayed ONLY for specific things. Typing, swiping, etc are fine, but quick tapping on in game controls is delayed. For example, in baseball superstars I can key in the player name fine, but when I go to hit the bat swing icon to hit the ball, I have a 1 second delay.
The issue is consistent, which leads me to believe there is something set in the system intentionally causing the delay.
It doesnt happen in anything else. I can type and web browse and do other things just fine. I know its not the apps because I have 2 note 8.0 devices both setup same rom and everything and the issue is not present on the other one.
Ive done multiple resets, tested different roms and kernels, stock and otherwise, and no change.
I checked with showing touch inputs in developer mode and its showing every touch in all games and apps..... its just as if the games themselves are intentionally delaying the response to the input on certain functions.
Anyone have any advice?
Click to expand...
Click to collapse
I SOLVED IT
just fyi for anyone running into similar issues.
My issue was with magnification mode in the accessibility settings. Turning it off fixed the delay. I liked the feature but im glad its no longer an issue
Even- power saver on- can cause such issues
Sent from my GT-N7100 using Tapatalk 2
phoenixbennu said:
I SOLVED IT
just fyi for anyone running into similar issues.
My issue was with magnification mode in the accessibility settings. Turning it off fixed the delay. I liked the feature but im glad its no longer an issue
Click to expand...
Click to collapse
Thanks for causing and solving the problem!
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
LOCKDOC_UA said:
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
Click to expand...
Click to collapse
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
ddelamareuk said:
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
Click to expand...
Click to collapse
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
LOCKDOC_UA said:
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
Click to expand...
Click to collapse
I wouldnt surprised be surprised if there are still a few screen issues considering the update they pushed out to fix the initial issues but for me, I'm not really being affected. At least in games I just need to hit the corners a little faster so I'm not hitting the brake like ABS
For the most part, gaming wise, I think there are issues with certain games picking up the new nexus as a different device from the original. Hence why RR3 has a terrib resolution. Apart from that, everything looks and works great.
As a side note, if you haven't yet, install Ultimate Rotation Control (free) from the Play Store. Open it and set the mode to Auto Forced. Go back to your desktop, hold your nexus in portrait mode like a book and open RR3. When you see the EA blue logo, turn it into landscape and that should improve how RR3 looks. Should help in the short term
How can we solve it
So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.
SonarMonkey said:
So, I got my new Pixel XL (128 GB, Quite Black, Google Store), and activated it with Project Fi a few days ago. Today, I noticed a bizarre issue. So far, I'm only able to get it to occur consistently in the Play Store. When pressing the back button on the navigation bar to return to the previous screen, the phone locks up, but not completely. The app and the back button both become completely unresponsive to touch, the volume buttons do not do anything, but the overview, home, and power button still function as normal. Navigating away from the app, or turning the screen off and back on fixes it, but it happens consistently enough to be very irritating. However, I can't get it to happen consistently enough to isolate a cause, or to capture a screen recording of it. It seems, though, to be more likely that it is app related, but that also seems strange given that it is the Play Store. The only other correlation I can find is to the Keyboard (which I'm using GBoard). Sometimes, it seems to occur after using the keyboard to search the store.
Does anyone have any suggestions/tips/etc. on a way to deal with it? Its hardly a fatal issue, but strange, and I'm curious if anyone knows what this could be.
Also, a side question: is it even worth unlocking/installing mods/etc.? I got 5+ hours of SOT with my first full charge cycle, curious if anyone has any input.
Click to expand...
Click to collapse
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.
toknitup420 said:
I recommend unlocking so at least if you ever have a bad ota update you can still fix you're device with a new factory image. As far as the lag issues. I had something similar when Gboard first came out. What is you're current build. You may need to update you're phone.
Click to expand...
Click to collapse
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.
SonarMonkey said:
I'm on the May image, and all my apps are up to date (aside from staggered update I may not have received, always possible). I'll wait for the June image to come out tomorrow and see if that fixes it. Thanks for the input on both fronts!
Although, if I unlock the bootloader I may fall all the way down the rabbit hole, haha.
Click to expand...
Click to collapse
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.
toknitup420 said:
Nothing wrong with falling down the rabbit hole lol. Personally I run stock system with my mod pack. Gives me incredible battery cuz it's stock system but I also get to have some custom tweaks. Best of both worlds.
Click to expand...
Click to collapse
Any particular mods? I've been flashing/modding/etc since my Droid Razr M but reading around on the Pixel XL forums is the first time I've felt out of my depth again - all this A/B partition stuff, changes to the way root and GApps work, etc. seems so different.
Hi,
My phone sometimes doesn't respond when I try to wake up the screen. Double tap, power button, fingerprint, nothing works. The only thing I can do at that point is to force reboot. This is a pretty serious issue. When this happens I had to wait for it to reboot.
Anyone else having this issue?
I'm also experiencing this and I'm not able to reproduce it. It drives me crazy, I so wanted to like this phone
That has happened to me too. Probably 3 - 4x over the course of a little over two months of use.
HMD Global's software sucks. This will be my last "Nokia".
jason2678 said:
That has happened to me too. Probably 3 - 4x over the course of a little over two months of use.
HMD Global's software sucks. This will be my last "Nokia".
Click to expand...
Click to collapse
Their hardware is pretty good. Only if the bootloader can be easily unlocked... this would be a good phone.
I think I may have experienced what you're talking about. Most of the time for me, it seems to be a notification screen overlay issue. When it happens, I get no reaction on my screen until I brush from the top down, as if I'm pulling down the notification screen. After that, the phone rights itself and behaves normally.
I've experienced this in the past and recently. Not often, but sometimes. It seems to be camera-related.