Happy downloading
http://download.cyanogenmod.org/?device=hlte
Looks like they skipped M9, and went straight to M10.
what a coincidence, i was fed up of my stock phone having a few annoyances caused by me, i thought i'd give CM a try before stock 4.4.4 is out.
I flashed M10, it appeared after i refreshed the page, so far so good, am having some waking up issues, literary, phone delays waking up a few seconds when physical buttons are pressed from deep sleep.
we'll see, all that sucks is no s'pen features in mind , i dont know much alternatives and it is going to require some researching, and yea, pen is detected as a Mouse cursor, weird.
As now nightly is available anyone tried ???
Related
Guys, a week ago my ohone started to act strange.
Randomly it does't detect the letter I'm trying to press on the screen. if i switch it to landscape it works perfectly, and when I go back to portrait the problem is still there.
It gets fixed by it's own or if I restart the phone, but it's starting to be annoying.
I'm on the stock Rom btw.
Same problem
I've been having the same problems but I think it has only happened to me when I use custom ROMs such as Cyanogenmod or Coredroid. When I went back to stock I don't remember it happening.
I was running Coredroid V8.1 a few weeks ago and didn't like it because the font looked terrible but I think the keyboard didn't give that problem, it was with an older version of CD. Right now I am using Cyanogenmod 7.0 and it happens a lot and gets annoying. I now for a fact that is not hardware since the keyboard will work normally on landscape and other stuff will respond to the touchscreen.
Still trying to see if there is some sort of fix or to use a new keyboard. Installed GO keyboard and same thing happened, now using Swiftkey X and it happened also but now I took the protective case to see if that has something to do with it LOL.
Well first of all I'd like to say I love cyanogenmod, and was very pleased when i installed it and all the ATT/google bloatware hassle disappeared. So anyway it started about a week ago, I would finish making a phone call or doing whatever on the phone, and then lock it.. Then when I go to use the phone again sometime later by pressing the power button to turn the screen back on, the screen stays black and is completely unresponsive, leaving me with only 2 options.
1.pull the battery and reboot that way
or
2.press the home/power buttons simultaneously for a few seconds to restart it.
This problem has been occurring more and more frequently and I'm getting to the point where it's happening so often I'm possibly going to use my backups to revert to the stock OS that it originally came with, which I'd rather not do if at all possible. Should I try an older version of cyanogenmod 10.1? Or Is there A new version for the samsung rugy pro? I know this is a relatively obscure, unpopular model, but its what I've got and I'm please with it.
So a little bit about my phone, and versions installed;
SGH-i547 (Samsung Rugby Pro)
Android version 4,2,2
Kernel version: [email protected] #1 fri mar 15 18:58:44 UTC 2013
Cyanomod version- 10.1.-20130315- UNOFFICIAL - commance
I;m not sure what I've done wrong, maybe a particular app is causing interference, but I'm not sure which one it would be. I am considering installing an older version of CM 10.1, such as ALPHA 4 here http://forum.xda-developers.com/showthread.php?t=2067214, but I would like some opinions and suggestions from the forum first before I attempt anything. I'm pretty knew to the scene and I really don't know. Something is definitely causing the screen to freeze, and it must be just the screen because if i have music playing it will still play while the screen is frozen. I would greatly appreciate any advice/suggestions leading towards a resolution to this issue.
Thank you very much.
Same problem
Master YI said:
Well first of all I'd like to say I love cyanogenmod, and was very pleased when i installed it and all the ATT/google bloatware hassle disappeared. So anyway it started about a week ago, I would finish making a phone call or doing whatever on the phone, and then lock it.. Then when I go to use the phone again sometime later by pressing the power button to turn the screen back on, the screen stays black and is completely unresponsive, leaving me with only 2 options.
Click to expand...
Click to collapse
I have both: same attitude towards CM and same problem. I am also a total newbie to rooting/flashing/etc issues, but I'd love to continue using my CM 10.1 with Samsung Rugby Pro (SGH-i547).
So please, could you help me to solve this awkward issue?
Thanks!
I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?
TeChNoC4AzY said:
I have had my oneplus one for about a month now. And for the first time I dropped it. About 2 feet. And my friend kicked it about a foot to prevent it from hitting the tile and It landed on flat carpet. The phone has a small dent on the lower left corner and screen has 2 small scratches that I only can see in sunlight. So I've been using my phone and every once and awhile it will go insane and the touchscreen will move on its own and press things. I hope this isn't an issue cause of dropping it.. I have a warranty but have alot on this opo already. Is there a possibility it's software?
Click to expand...
Click to collapse
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
OTA Announced today. Change log has a fix for turning on in pocket, but not for the unresponsive screen.
Actually I have had similar behavior and I'm using slimkat 7 now. This morning I couldn't enter even pin code as my phone didn't allow some presses. Numbers 1,2,4&5 weren't registered at all. Same time I couldn't use pull-down menu as it bounced back up after 1cm pull. Also when trying use power menu all options were unable to register. I force shut down phone twice and still same thing. Then I just wiped whole screen with moist cloth. And problem solved.
So there was something invisible holding my screen like finger or something.
I have had similar incident couple times earlier. When writing or so on....
Sent from my Oneplus One via Tapatalk
keileruno said:
The Touchscreen failure you have sounds a lot like the problem I had from time to time with mine (without dropping).
There are also other bugs with the screen:
- unresponsive screen (-> reboot fixes temporarily)
- weird behavior like you descrive (ghost touches)
- fast typing not getting recognised
These problems will be fixed with the next 2 OTAs (both in august).
Wait if the fixes do work for you. If not it has definatly something to do with the accident.
Click to expand...
Click to collapse
How much longer do you think it will be before the new Ota releases.
TeChNoC4AzY said:
How much longer do you think it will be before the new Ota releases.
Click to expand...
Click to collapse
search the forum the ota is out if you know how to use adb sideload
The ghost touches lasted for 30 seconds today.. Anyone else having this to?
Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.
Chris.fowler said:
Yes it's annoying the crap out of me, seem to have the least amount of issue running slimkat with sensei kernel. Every other kernel seems to either leave the screen completely unresponsive a min after boot, or touch becoming increasingly less as time/process load increases. Really hope this issue is fixed soon.
Click to expand...
Click to collapse
Best thing is to go back to the XNPH22R Kernel. For me it fixed the frozen screen completly.
http://forum.xda-developers.com/showthread.php?t=2780725
It won't work with 30O though. 25R is working with 22R Kernel.
All other kernels are not working very smooth for my device. The OTA fixing this issue is anounced for August. No releasedate has been set though.
Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone
Chris.fowler said:
Is that kernel compatible with an aosp ROM lime slim or am I going to have to put a cm ROM bck on the phone
Click to expand...
Click to collapse
CM 11S kernels are only for CM 11S. 22R is a CM 11S kernel.
My phone has been alright today. Except for afew freezes. But I Wana Stay with cyanogenmod 11s. I think it will be updated soon. I really can't wait for Android L. Will android L be with cyanogenmod as well?
Great now the middle of my screen us touch dead........ Ughh
Well now all seems fine.. But earlier screen in center was dead and phone was non stop Ghost touching... Even after restarts. Sigh. This update needs to release already....
Hello
playya said:
search the forum the ota is out if you know how to use adb sideload
Click to expand...
Click to collapse
It won't update itself?
It's a known issue.. Vote it on Jira!https://jira.cyanogenmod.org/browse/BACON-145
I'm about to throw my phone, this is VERY irritating.........
It keeps Ghost touching non stop. I should of never got one.
TeChNoC4AzY said:
It keeps Ghost touching non stop. I should of never got one.
Click to expand...
Click to collapse
Install the 22R OTA and Kernel.... then you can easily wait for the fix...
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
thelestat said:
I have the same issue here, rebooting a couple of times sometimes works, to get the touch working again in recovery. Makes not difference though if you do a full wipe (system/ cache/ dalvik/ data etc) and flash the 11s stock/ m9 nightlies the problem is still there.
I've had to stop using the phone as the touch screen issues make it unusable most of the time
Click to expand...
Click to collapse
It's weird...I flip back between AK and the stock CM kernel, and the touchscreen works for maybe an hour, then it goes completely dead again (including when in recovery). And the touchscreen is dead no matter which recovery I use, whether it be TWRP or CWM.
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
demkantor said:
Consider going pure stock and resetting tamper flags, if it keeps acting up you should be able to RMA it
Click to expand...
Click to collapse
I've got it back to working by messing with the kernel a little bit. How's the progress with the LOGO partition going? I saw that in the other thread, you almost bricked your OPO
Yeah it was an unfortunate mistake on my behalf while digging into it deeper, luckily all worked out in the end
Haven't had the chance to make more progress, the wife and I had our first child on Friday and I still have one more week of finals left (until I'm done with college for good!)
I hope to have some more time this next week to figure the rest out, I'm sure its doable but I don't want to risk anything before I know more!
Touch screen unresponsive
Any solution to this problem? Running 11.0-XNPH30O
Android 4.4.4 that was updated two days ago.
The touchscreen becomes unresponsive every hour or two and need to force turn off the phone by holding down the power and restarting.
Have had the phone for a little over a week and annoyed by little issues here and there. The orientation change (when turning phone for auto rotate) on a picture takes too long. Speaker phone was a problem initially, fixed with an update and now this touch screen unresponsiveness.
Doesn't matter if it's Synaptics or not. cyanogenmod and one plus need to figure out a solution and not sell a buggy phone on the most important features of a touch screen phone. ITS TOUCH SCREEN.
If I don't see a fix in 48 hours, I'll be returning the phone or selling it on eBay.
treChoy said:
Hey guys,
So we all know that Synaptics has kinda screwed us over with the touch screen driver. My screen often comes unresponsive; in that case, I just wait it out for a few minutes, and it's back to normal.
Today was not the case.
I'm running CM M9 with AK kernel. The screen stopped working, and after a few minutes of not working, I did a hard reset. One interesting thing though is that the power menu didn't pop up, even though it usually does when the power button is held for ~2 seconds.
I was thinking, 'no big deal, right?' But when I booted up, the screen was responsive for maybe 5 seconds, and then it just shut down. Reboot after reboot after reboot, these results repeated.
So I pulled the stock boot.img from the M9 .zip and flashed it in Fastboot. When I booted up, I didn't even get those 5 seconds of grace time where the screen was responsive. Even after waiting 15 minutes, the screen seemed to be dead.
I decided to re-flash the ROM in TWRP. Even though my touchscreen wouldn't function in the actual Android system, it would always function whilst in TWRP. Again, this was not the case. Only the bottom navigation bar would register touches. Everything else was dead.
I'm going to flash CWM and see how everything goes. But please, can someone point me in the right direction, say, if my touchscreen is still dead after re-flashing? Thank you so much...
Click to expand...
Click to collapse
treChoy said:
I've got it back to working by messing with the kernel a little bit.
Click to expand...
Click to collapse
I've got a touchscreen dead zone at the bottom, just all the navbar area. I wonder if it could be possible to get it back to working by messing with the kernel as you did. Which kernel and tweaks.
Thanks.
Edit: now the dead zone has extended to the hardware buttons. I have to rotate the screen 180° in order to be able to use the navbar.
Thanks
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.
This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.
I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet
I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.
I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:
I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet
Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.
So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk