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
Hello, I have been experiencing an intermittent issue, that is become very frustrating when trying to do anything with the phone; text messaging is unusable at this time.
This issue has happened on the original version of android, and current version which is the KANG Milestone 2. I also have Franco Kernel. This is a GSM model running on USA AT&T. It has happened everywhere. At home, work, etc. It doesn't matter if I am close to another electronic device, if I am holding the phone, etc. Sometimes I can go days without having this issue, but it seems like lately it has increased.
I uploaded a youtube video, but cannot post the link, if someone can post it for me. here is the information after the website address watch?v=HbCs9_JUQFE
Basically it will keep inputting buttons or key presses, or switch my homescreen, etc. If it were a hardware issue wouldn't it happen all the time?
Anyone with advice or have had that issue? If you need anymore information I can try to get it to you if the phone will work with me.
Thanks!
I may be wrong, but it looks like there's something wrong with the digitizer. A wire maybe coming loose or you could have more problems than that. I'd go get it swapped out if I were you. Could be a simple fix, could not. Why risk opening your phone when its still in warranty?
i got an issue with random inputs on my galaxy nexus too.
i activated the setting to show touch-inputs in developer-options and recorded a small video
as you can see i happens along the right side of the screen and you pretty much can´t do anything while this is happening (when you´re in an app, the screen will just scroll around like crazy and do random stuff.
edit: new users can´t post working links...
hxxp://youtu.be/Jh_pv3Y6_k0
Looks like a hardware defect, that one you'll want to send back.
Hello everyone! I just want to start off saying I love reading this site not only because it's so informative,but yall really help each other out. After stalking these forums extensively, I've come to the conclusion (well hopefully) that I'm the only one experiencing these issues with my tablet. First off, I love this tablet. I just feel like samsung half baked everything about it. The software Is buggy and so is the hardware (I work at an electronics store, and let me tell you, the samsung rep knows all of my problems.) It's rather unfortunate cause this is a very expensive tablet and I was expecting it to run like it's something premium. Lol, I thought.
first off is the display. I know it's gorgeous, but has anyone noticed when you're In an application like Google drive, s note, or even Facebook that the screen dims and brightens automatically? It also happens when I use swype on drive and applications like fb.
Second, the pen input/snote. In snote, has anyone had the issue where, for example, you would write a large area of text (or even smaller area), you cut it then paste it somewhere later in the note. Then, once you start writing again, anything similar to what you just cut out (for example i'll use the the word world). I'll write wor, but when I write the rest, ld, it erases that and shows me the paste symbol there. This is extremely frustrating as I'll be in class on my 3rd or 4th page of notes and this will happen (almost wants me to use my geek squad protection, almost). Yes, even after I clear the clipboard it still happens. I also have a screen shot attached to the other very common error I get in snote, or even in Sketchbook for galaxy. Action memo constantly crashes, I could just open a memo, stare at it for a few seconds and it will "unfortunately stop". ( Or, I mean, it could just be my face, but I would feel better if it was samsungs fault )
third, they keyboard. You would think the tablet with an 8 core (or at least soon to be) processor can handle it. Nopee. Swype just lags after a day or so of use. Not fun. Then, when I use the spen throughout the day, when I change the keyboard method to handwriting recognition it just dissappears. Doesn't even want to let me put one thing in. I've tried turning off the spen detection for the keyboard keyboard and I still get the same issue. When things like like this start popping up, it's time for a reboot. Which I have to do about once or twice twice a week.
Has anyone experienced these things before? Or did I just get my hopes up too high and samsung has failed me?
Thanks
oh and everything is up to date, nothing is custom besides the font, which has no Impact on these problems.
the kb was too laggy for me. i've switched to thumb kb and use tha kb switch app to auto select the samsung kb when I whoop out the spen.
I really think samsung rushed this thing out to beat the ipad release and planned on patches for anything they find.
I have seen some other posts on this before but they all suggested disabling hardware overlays. The problem is that occasionally, after some time, the video player on the note 10.1 2014 (or any video on full screen for that matter) has this really weird graphical glitch where everything just flickers or freaks out. It is not just the video but the entire screen just glitches while the video is playing. Now disabling H/W overlays does work but the problem is that it completely slows down my device and makes it really laggy rather than the normal snappy feel after the kit kat update. I had to return this thing so many times and I don't want to return it if I don't have to but I rather have a functional device rather than one that will die later. The problem fixes itself when I restart the device. But apparently it is due to some issue with the device not recognizing whether to get the video from the GPU or CPU or something like that. It is just really annoying and I just wanted to find a way to fix it maybe by updating the full screen video thing or anything at all. Otherwise I would want to return it. If everyone else has this problem then I figure it is because of the update, but if some of you don't then I think it is something with my device rather than the software. Any help would be appreciated. Thanks!
philuminum said:
I have seen some other posts on this before but they all suggested disabling hardware overlays. The problem is that occasionally, after some time, the video player on the note 10.1 2014 (or any video on full screen for that matter) has this really weird graphical glitch where everything just flickers or freaks out. It is not just the video but the entire screen just glitches while the video is playing. Now disabling H/W overlays does work but the problem is that it completely slows down my device and makes it really laggy rather than the normal snappy feel after the kit kat update. I had to return this thing so many times and I don't want to return it if I don't have to but I rather have a functional device rather than one that will die later. The problem fixes itself when I restart the device. But apparently it is due to some issue with the device not recognizing whether to get the video from the GPU or CPU or something like that. It is just really annoying and I just wanted to find a way to fix it maybe by updating the full screen video thing or anything at all. Otherwise I would want to return it. If everyone else has this problem then I figure it is because of the update, but if some of you don't then I think it is something with my device rather than the software. Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
I have the same problem at times, couldn't figure out so I just reboot and it works fine.Its a pain in the ass to do but it only takes less then a minute to reboot so it doesn't bother me to much.What kernal are you using?
ya it is not that big of a deal if that I only have to restart it once in a while but I was just worried this was a sign of a deeper issue or something. Like my hardware is messed up or something. Or something is loose in my tablet. I don't want it to get worse or anything. I rather get a replacement while still within the period to return it if I can (I have a 3 month return policy for instances like this). If it is more of a software thing and people just deal with it, I can live with that until they update it or something.
Also I am not too sure what you mean by kernal. It says the kernal version is 3.4.39 or something like that. Its kit kat.
Also if anyone is NOT experiencing these issues as well and they have an unrooted tablet that has been updated to kitkat and they use it regularly lemme know.
I've had this phone for about 5 months now and one thing thats been bothering me for most of the time is the phones touch sensitivity. Lately also it appears to be getting worse.
Phone is completely stock
I am on Pie and I have the newest update.
I am not rooted
I am not using a screen protector
I do not have huge hands or particularly fat fingers
first I don't use a lock on my phone, so I swipe up to unlock it. Most of the time it take multiple swipes to unlock, most of the time its 2 or 3 but sometimes up to 5 if not more. Is this livable sure but let me tell you it's getting really really annoying after just 5 months.
Scrolling on the phone has always been odd, it feels choppy at times, especially when scrolling in apps like facebook or the browser, scrolling outside of apps seems ok. Its like it's missing some of my inputs or applying some sort of acceleration or deceleration based on how fast you swipe and its just doing it poorly. Now again this is just an inconvenience but still...coming from a Note 8 the scrolling was always smooth..never once did I notice it being choppy.
So these two I just chalked up to how the software was implemented..it was what it was
So fast forward to now....I'm noticing even more issue with the touch sensitivity....words dont type right , I often miss spaces when typing, I thought it was my bad typing but now I really think it's missing some of my inputs because its worse than just my bad typing. The worst is when I go to correct words and hit the right word on the top of the keyboard is misses the word. It doesn't always put it it..it misses the touch and it does this a lot.
If I try to highlight something it will at times highlight the wrong row or word...every now and then it will highlight something not even close to what I was trying to highlight, like another part of my hand accidentally touched another part of the screen, but it didn't. I try to duplicate this when it happens and I cant.
In the same vein, sometime I touch something on the screen to open a link or something like that and it will touch something else close but not what I was trying to touch, again sometime something not even close will register like I accidentally hit something somewhere else...again I cant duplicate it.
It will register touches when I'm not touching the screen, just holding the phone....I think maybe I accidentally "touched: the edge of the screen but also I can never duplicate the action
Im at a point here to I feel like there is either something wrong with the screen on my phone or I need to turn to rooting to see if the issue really is software and maybe its been fixed by the community.
I came here to check about rooting but I thought I would ask the question first and see what people thought about the issue. I did a search and there definitely seems to be others having similar issues and a lot of those people seemed to be having screen issues. So maybe it really is a hardware issue and I should just skip the root and talk to google?
I have almost the same issue. Any solutions !?!
Try a factory reset and see if that helps any. If it doesn't, contact Google; a warranty replacement may be in your future.