There has to be a reg edit, the ones for the mogul dont work and this damn thing only stay on for like 7 seconds, pretty annoying to have to keep pressing the keyboard to get it to light back up, help
This would be nice. If any experts know of a fix we'd all appreciate it.
I have been trying to figure this out since 2 days ago. Any of the tweaks in the raphael forum do not work on the Sprint version of this phone. I will let you know if I figure this out. Otherwise if any one else figures this out please post it.
Sprint really basterdized this phone. To bad to (I still like it though), The GSM version has somemore features, and many of the users have already figured these issues out.
TheDempster said:
I have been trying to figure this out since 2 days ago. Any of the tweaks in the raphael forum do not work on the Sprint version of this phone. I will let you know if I figure this out. Otherwise if any one else figures this out please post it.
Sprint really basterdized this phone. To bad to (I still like it though), The GSM version has somemore features, and many of the users have already figured these issues out.
Click to expand...
Click to collapse
From what I read in other forums, they believe it's not a software fixable thing, but tied directly to the hardware. I don't understand anything of what that means, but I hope the gurus will figure something out.
The few seconds this keyboard stays lit is just ridiculous!
hey, try the Advaced Configuratio tool 3.2.
Under Input\Keyboard backlight timeout: default 10 sec.
I hope this tweak can help you
i have advance config and i set the timeout to 2 minutes.. the keyboard still goes off within 10 seconds... so that tweak in advance config does not solve it...
Can Anybody figure this out. This is driving me crazy. a couple of folks in the PPCGeeks forum said that maybe a driver needs to be written for the Sprint TP Back light Issue.
I would donate to the cause. This is very annoying.
yea i tried changing the registry keys for pervious WM devices and even thoug it registers the change its still the same very annoying
Yea, that and the software keyboard comming up ALL the frik time when you dont want it.
Nullkeyboard doesn't work to fix that anymore either. it brings up a big box.
It's a shame to find this thread. I've been searching the goggle all night and morning for a solution.
God I hate Sprint.
I found HKCU/ControlPanel/Backlight/QKeyLedTimeout in the registry and the default value was 10.. So I changed it to 20 first and it didnt do anything.. Tried to change it to 0 which normally means no timeout but that also didnt do anything.. So not sure what that Value is for..
I also did a search for 10 in the whole registry and didnt find anything that would even seem like a timeout on the keyboard.. So not sure where to go from here.. Anyone else find anything that works?
Currently there are no hacks/tweaks regarding the keyboard backlight.
It is frustrating, but they think it's written into a DLL file. Give them a bit of time, they will find it.
Just an FYI, most advanced config tweaks do not work at all.
They have not recommended it at all.
Yeah advanced config is a joke at the moment.... Someone needs to releases a touch pro specific one... it will be awhile yet prob though....
and sarin is absolutely correct... The KB backlight is Driver Based so that one will likely take quite a while too
I just press ctrl to get it back up, but its still frustrating.
Has anyone made any progress on this issue?
i had been trying to change some registry values to remedy the light timeout and now my KB lights do not turn on when i slide out the KB. if i press a button they will turn on.
**edit**
i just slid the KB in and out about 5 times in a row and now it works as it used to. i wonder how that happened??
Has anyone found a fix for this yet?
Same Thing
I have VZW and couldn't fix it either. Tried the Advance Config and that option didnt even work either. I would love to figure this out!
Thought I'd resurect this thread and ask if anything has been found that can extend the kb light. I tried ACT like the rest of you and while it worked beautifully on my gsm TP it of course works not on my sprint. I did notice that "HD tweaks" has a few useful tweaks that do work. Alas, no kb light function there of course since HD non physical.Lol. Seriously tho , is it wm or HTC that does not give us the option to change this? I can't think of anyone being of sane mind that would find a 7 sec timeout a good thing.
EDIT: I found the neukblight app and it is working well and getting the job done. Probably why this thread died, you all had already found it I suppose. Lol.
http://www.nuerom.com/BlogEngine/page/nueKBLight.aspx
Related
Well I [finally] got my Touch Pro yesterday at Verizon. Pissed at the RAM issue, I was hoping mine wouldn't be as noticeable (the lag).
I've been messing around with it, installing stuff, etc.. I've got a few questions though.
How can I disable the Wake On New SMS? The registry key isn't there and it's really bothering me.
I'd like to know how I can tweak it to run faster and less laggy, also. Considering the Wake on sms reg key wasn't on my VZW stock ROM, I didn't feel like bothering to look for other stuff because I didn't think it would be there.
Also, is there an extended battery for the VZW TP??
My battery did not last that long. It was down to around 20% after 15 hours (With slightly heavy use in the morning). Is there a battery that [preferably] doesn't need an extended back cover?
And how many of you would recommend returning mine and getting/hacking the Sprint one to work with Verizon? Is it a hard process? Doesn't seem it. i'm debating doing that, because this lag and stuff is just bull****.
Thanks in advance
I dont own a touch pro, but generally when windows doesn't have a reg key it'll default to some predetermined setting. So, my advice is to try creating the key and setting the sms setting you want. You have nothing to lose. If it doesnt work just delete the key you made.
Yeah I guess I'll try that later. Not really sure how.
I'm leaning towards getting the sprint one and switching it over to VZW.
Anyone know where/how I can get it for the, like, $300 I've seen? Or do I need to pay full $5xx for it?
Been reading this tutorial (link) on how to do it. People recommend using Live Search Cashback to get it in the $300s. Anyone have and info on what that actually is? Sorry for the noob-ish question, but I've never heard of Live Search Cashback before, lol.
Google is your friend.
I'm guessing this is what they refer to. http://search.live.com/cashback
Sweet! Thanks, I can't believe I never noticed this before. I'm sure I'll be using this a LOT now. Lol.
Well, thanks for that part.
Anyone have any feedback on using the sprint over vzw on vzw's network?
*edit*
Oh my God. The sprint has a white-ish silvery back and chrome sides.
NO WAY. NO.
That just completely turned my thoughts around on this.
Unless, can you switch out the faceplate for one with black instead of chrome and get a replacement black battery cover?
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Nothing physically wrong with the hardware, definitely an issue with our port. Not sure if anyone has nailed down the reason, but it seems to be if you're typing and some background process starts up, it can screw with the phone. I've also seen it where the keyboard appears to completely 'cut out' - nothing will be typed.
For both issues, sliding the kbd closed & reopening usually fixes it. This has fixed my issues 100% of the time when the kbd cuts out - however, it has not always resolved the repeat key bug...
I will try the keyboard slide. thanks.
I just had over 200 w's. LOL.
As long as I can stop it its tolerable.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Yep, I've seen it several times. It seems to happen when the CPU seems to be maxed out for whatever reason. My phone is usually sluggish and on screen buttons are slow to respond too when it's going on. I'm guessing the CPU is getting overloading and missing some of the hardware polling cycles. As a result it doesn't pick up the change in the button state and proceeds as if the button is still being held down. Aside from arrrghhh's suggestion of opening/closing the keyboard, pressing another key seems to interrupt the process (but it will happen again). For me, the main times I have run into the problem was when my phone was NOT overclocked. Certain apps (e.g. Super Manager) seemed to cause the issue more than others too.
Yeah, I have noticed that it only repeats a letter if I hold it. Now I only tap a letter a few times, for example if I want a few 2's I would push 2 a few times instead of holding it.
If it starts repeating what solves it for me is what arrrghhh said, slide the keyboard in and then back out.
I'm still not sure why this occurs though. Maybe the method it uses to emulate keyboard needs a bit of tuning
i believe the stuttering letter bug (hope this name will catch on ) is caused by something in the keyboard backlight commit as that is where is started. In gingerbread when you hold down a key it doesnt repeat it instead gives an option to use variations of that letter, because of this maybe in gingerebread this bug is not as annoying
iv used gingerbread but havnt taken any notice of wether i had the bug or not, its not as bad lately on the kernal i use but i will take not next time
That's an interesting observation, I thought the bug always existed but I can easily believe it has to do with the keyboard backlight. I was looking at that code the other day, it definitely looks suspicious.
Sent from my FRX06+ TP2 using Tapatalk
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
coolwater22 said:
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
Click to expand...
Click to collapse
It does *seem* like the bug was introduced around then. Not positive tho, wish there was a way of tracing/reproducing this issue.
Perhaps trying files from before backlight was added?
If I had the time to look back I would.... Maybe in the next few nights.
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
gallahad2000 said:
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
Click to expand...
Click to collapse
Also I have recently noticed that closing/opening the keyboard again seems to stop the progressing letters.
And when you open/close the keyboard the backlights go off then on. This is another observation which hints that the keyboard backlight commit is at fault. It also may be useful to note that when you shut the keyboard it doesn't stop the letters, it is upon re-opening when it stops.
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean ir up and see if they could remove the bug
Jandyman said:
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean it up and see if they could remove the bug
Click to expand...
Click to collapse
We look forward to your patch!
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Click to expand...
Click to collapse
Awesome. I'm sure he'll appreciate that .
FYI, I was going to bug you about this - if the caps/FN and kbd hooks should be in userland anyways, perhaps that rewrite should begin...?
I'm not so sure about caps/fn. I don't think there are any userland hooks for them. Or, haven't found them yet.
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
Click to expand...
Click to collapse
That's great to hear thank you highlandsun.
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
nicktheqwik82 said:
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
Click to expand...
Click to collapse
If you had searched the forums, you would have come across this, which will solve your problem.
Also, it's not flashable so unzip it and put the apk on your phone, install it, then run.
nicktheqwik82 said:
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
Click to expand...
Click to collapse
Try to find the HTC Calibrate.apk and push it to System/Apps... It'll Definitely Help!
Twolazyg said:
If you had searched the forums, you would have come across this, which will solve your problem.
Also, it's not flashable so unzip it and put the apk on your phone, install it, then run.
Click to expand...
Click to collapse
I ran the advanced search and couldn't find anything for the E3D. But thanks for the help and for the hand-slap dude.
nicktheqwik82 said:
I ran the advanced search and couldn't find anything for the E3D. But thanks for the help and for the hand-slap dude.
Click to expand...
Click to collapse
Really? After about 1.4 seconds I had 4 touchscreen issue threads (including this one.) pop up after searching "touchscreen issue" in the "search this forum" bar. Did you fix your problem?
No go.
Well the HTC Calibrate app did not work. I must say that it did help for sure, but the same dead spot issue keeps happening. OK, so now I have begun to look at replacement parts on Ebay. So just to get this straight, it is the digitizer/front glass assembly that registers touch, correct? As I said, there are no missing pixels or colors, so does that rule out the LCD? Or should I but both to be on the safe side? I really want this issue done and over with, so help me get this thing taken care of guys. Thanks to all you guys for the help. Also, if anyone has a digitizer and LCD assembly for a good price, let me know.
I had the same issue where the bottom quarter of my e3d hboot 1.5 didn't work I didn't have insurance so I took it in and the sprint manager said I wasnt the only one with the issue it's a htc issue I tried the calibration on different roms bit it would only give you calibration on the top half of the screen, spent swapped it out and I got a new e3d with hboot 1.5 of course but at least the touch screen is working.....hoped that helped you out cuz I searched everywhere and couldn't find a solution.
I was toying with that idea. Will the "watermark" from unlocking a 1.50 hboot version be a problem? Obviously I need to unroot. And also, I bought this phone from an individual just a few weeks ago after I got my first one stolen, will this be a problem? Any other thoughts on taking it back to sprint?
Yeah, it is really weird, it is exactly where the "Accept & Download" button is when making a market purchase. So, yeah it sucks, I have to rotate it horizontal every time I want to buy something
I have been having lots of touchscreen issues as well. Tried lots of different roms and kernels but no luck. Someone suggested formatting the SD card. I haven't had access to a computer so i just removed the card about an hour ago to test and so far i haven't had any issues.
Sent from my PG86100 using xda premium
i found a super old thread on this, but it didn't have any answers. rather than ressurect that one, figured i'd just ask here.
does anyone know how to disable the baked-in power saver feature in some Samsung Android phones? the one that dims the screen, turns off the keyboard backlight, and doesn't let you use the camera once you hit 15%(or 10%) battery left? can't stand that, for my own needs anyway!
i figure it might be an edit to the kernel source code, or something like that. i just don't know where to do that. I know it can be done tho, because i remember having some ROMs on the Epic 4G that had that junk disabled. guess i'll also see if some of those old devs. are still around. thx for any advice
Trying to figure out the same thing..
Anyone have any ideas?
I'm just gonna post the text off of an unsuccessful reddit post I made, go to sleep and hope I wake up to something good. Night everyone.
"imgur.com/a/4xjZW
Galaxy S3 INTL version. CM11 M12. Was actually experiencing this ever since I got CM on it at M7. Don't remember it being a thing on the stock ROM.
Anyone else ever get this? Suggestions, solutions, fixes, anything?
I'm guessing it's some sort of a driver issue? It's mostly when transitioning between something, as in from an app to home, the other way around and so on. But I also get it within apps as well. For example I don't think I ever had a clean image-fade to black-image transition in Asphalt 8 when waiting for a race. It always seemed to go off in those blocks. Sometimes it's happening really often, other times it seems to be pretty smooth."
I'm having something similar. Please help us.
Thank you
CM11
EDIT # 1 : Today I went to service center for this issue, and they said the problem in the motherboard issue. Sadly, I have to change the motherboard which cost me.
Anyone?