Related
I just got my $199 Ebay NC last night, and loaded CM7's newest nightly #13 on it.
Everything seems to be in working order, including market and whatnot, but there is one problem: some areas of the screen would become unresponsive. I noticed it repeatedly in three scenarios:
1. When the notification bar is pulled down, the "clear" button can be unresponsive
2. In market, the "install" and the subsequent "ok" to give permission buttons in an app page can be unresponsive
3. the search button on the top right corner of the market (the magnifying class) can be unresponsive
The weird thing is that the rest of the screen is fine, i.e. I can scroll up and down in the market, and I can click on individual notifications fine, but just those buttons are unresponsive.
I am using the Kernel that came with CM7, and LCD density is at default 161.
Any suggestions are appreciated.
Sounds to me like it is just the bad responsiveness of the NC around the edges of the screen? Stock, with Froyo, and now with CM7 that's been the case for me.
tarheeldan said:
Sounds to me like it is just the bad responsiveness of the NC around the edges of the screen? Stock, with Froyo, and now with CM7 that's been the case for me.
Click to expand...
Click to collapse
I see. Good to know Im not the only one having this problem.
Did you ever get this resolved? or just live with it haha
To fix the touch screen issues try Dalgrin's OC kernel over in the development forum. He fixed some of the touch screen issues with it...maybe it would fix whatever problem you are having. You can run at stock speeds if you want of course, just go to Cyanogen settings>performance>cpu and set it to stock.
pfcwintergreen said:
To fix the touch screen issues try Dalgrin's OC kernel over in the development forum. He fixed some of the touch screen issues with it...maybe it would fix whatever problem you are having. You can run at stock speeds if you want of course, just go to Cyanogen settings>performance>cpu and set it to stock.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried it and it "somewhat" helped. The problem inside the market is mostly gone, but the clear notification button is still buggy. Wondering if Nookie Froyo would make a difference.
Just saw this thread:
http://forum.xda-developers.com/showthread.php?t=980222
and tried out the app and it seems to work.
cuoreesitante said:
Thanks for the suggestion. I tried it and it "somewhat" helped. The problem inside the market is mostly gone, but the clear notification button is still buggy. Wondering if Nookie Froyo would make a difference.
Click to expand...
Click to collapse
If you notice the clear button also changes size. When it is big it's very easy to hit, but when it is small it has a very small area to hit. The upper left hand corner of the button seems to be the best location to hit.
Sent from my NookColor using Tapatalk
I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
CM7. Like Stock but...better!
DirkGently1 said:
CM7. Like Stock but...better!
Click to expand...
Click to collapse
+1
CyanogenMod is one of the best alternative ROMs out there. All the features of stock with a ton more added (along with bugfixes).
archinloaf said:
I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
Click to expand...
Click to collapse
agreed with cm7 (if you prefer the normal stock look) I personally don't like all that sense / miui stuff. now that the big bugs are fixed, i don't see why you shouldn't give it a try.
cyanogen 7 really is easily the best option. and with the newest battery increases and optimizations, its a no brainer to use cm7 over stock.
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
samson_420 said:
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
Click to expand...
Click to collapse
There were issues with MMS messages in the nightlies due to a merging conflict when they merged to the 2.3.4. This has been resolved for the last couple of weeks.
I'm not sure if that is what you were talking about.
How much free memory do you have on your phone?
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
qtipextra said:
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
Click to expand...
Click to collapse
Sorry. There are not any GB ROMs for the D4 that will work on ICS. The GB D4 ROMs there are are not compatible with the ICS kernel. Maybe if you can describe the issues you are having with ICS we can help you with those.
Sent from my XT894 using Tapatalk 2
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
qtipextra said:
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
Click to expand...
Click to collapse
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
kwyrt said:
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
Click to expand...
Click to collapse
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
qtipextra said:
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
Click to expand...
Click to collapse
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
azrael293 said:
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
Click to expand...
Click to collapse
I've been using AudioGuru for profile selection, but I would much rather be able to dynamically change the volume of notifications and ringer together from the hardware buttons instead of set profiles with defined volume levels at each.
I have not found an app yet that works on this phone/ICS that works to lock both volumes together.
Perhaps I will just have to wait until JB is officially released for our phones. But I really liked GB on my previous phone, its too bad I can't get a ROM to work from ICS to GB, considering that the phone was originally released with GB.
Another thing I don't like about ICS is the stock messaging only let's you save a maximum of 1000 messages per contact. I would prefer messages never get automatically deleted, and in ICS it cannot be disabled, you can only change the max number of kept messages.
If you attempt to downgrade the phone to official GB there is a very high risk of bricking the phone.
I'd recommend you stop trying to do this and instead try to either get used to ICS or to replace the bits you don't like with some 3rd party apps.
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
niko99 said:
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
Click to expand...
Click to collapse
did you try yourself before suggesting?
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
Yes you can (maybe) bring your phone back to life, but one thing that will definitely not happen is that Gingerbread ROM actually booting. The locked bootloader does not allow you to downgrade.
Do not even bother trying to downgrade it will waste your time and you may end up with a brick.
highlandsun said:
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Die Bruine said:
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
Click to expand...
Click to collapse
At least I know I am not the only one with the cursor jump issue. And yes, I notice it only happens to me when I open the keyboard and immediately start typing. I will have to start being patient and give it a few seconds before typing.
I've tried many different Volume apps, and even when locking volume settings are enabled, the volumes are not locked when I adjust it with the hardware volume rocker.
I did read that JB will be getting an official push to the D4, but they have not said when. ICS just doesn't set too well with me for some reason. Yes, it runs pretty smooth, but I don't like it's all black theme, some functionality that was left out, and the new widget being part of the app list doesn't always show new widgets immediately. I guess my biggest upset about it is that it seems rather... buggy or undeveloped. To me, GB seemed to be more developed and work the way you would come to expect an android OS to run now days, and ICS just isnt there yet. Hopefully JB will be better...
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
olegfusion said:
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
Click to expand...
Click to collapse
unless you borked your bootloader or had a hardware failure niko is right there is no way to hard brick your phone just by flashing roms/sbf's
as long as your bootloader is intact you are able to recover your device
All that said, there's no reason someone couldn't get a vanilla AOSP GB build working with the ICS kernel for use with safestrap. On the XDAndroid project we had a single Linux 3.5 kernel working for Froyo, GB, and ICS. It's not a slamdunk, but the amount of patching required isn't that bad.
Sent from my DROID4 using Tapatalk
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.
I use milaq's nightlies, and for my needs, it's more than adequate.