Weird shell problem - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I have this weird problem with the shell on the device itself where the cursor is couple spaces off the actual typing position, so it is quite confusing. I'm running KyanROM 1.28. I tried it in "terminal emulator", "Connectbot" and "ROM toolbox", same problem so I believe it is not an application related, it is either shell binary problem or some system settings. See the screenshot. I was typing there "ls -l" and cursor is couple positions to the right.
Any idea what could be the problem or suggestion how to troubleshoot it?

Mines the same way, on every rom I've tried. Maybe it's supposed to be like that?
Sent from my SGH-I747M using Tapatalk 2

corythug said:
Mines the same way, on every rom I've tried. Maybe it's supposed to be like that?
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
I know it wasn't like that before, I just don't know when exactly it broke.

anyone solved this yet?

Related

Flipped capacitve touchscreen input

So I've been experiencing an odd issue intermittently. I'll be using my phone normally, and out of the blue, the touchscreen input gets flipped along the vertical centre axis in portrait mode. this flip remains when i change the phone to landscape mode (the issue itself doesn't flip). It's an odd phenomenon that disappears once I reboot, but I thought I'd record and upload for all your curiosities' sakes.
http://youtu.be/GEwfa1GYLj4
I've got the same problem but it doesn't go away when I reboot...
Can anyone help?!
Experienced the same issue. Rebooted and it was fine. Unnerving to say the least.
Have you tried a factory reset? And/or reflashing ROM
Sent from my Desire Z using xda app-developers app
I've tried rebooting, tried resetting to factory settings and now I will attempt to reflash the ROM.
From the power of google it appears that this is an issue with a lot of tablets and that it's a driver issue. Mine happened only after I replaced a faulty lcd so that would make sense. I'm still not confident on how to fix it though!
Doubt that reflashing is going to help, then. If you can get the device to run a recalibrate you may be in business.
Installing a nandroid on my WinMo TP2 there was a calibrate app in the ROM that ran in the command line before the GUI loaded up. Hopefully you can find something like that.
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
CORRECTION
it was not the nand version but the version that loads from WinMO with Haret. Maybe you can look at one of these files and extract the calibrate code or find out where it came from.
Sent from my Desire Z using xda app-developers app
igor45 said:
CORRECTION
it was not the nand version but the version that loads from WinMO with Haret. Maybe you can look at one of these files and extract the calibrate code or find out where it came from.
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Thanks Igor - that's the most constructive answer I've found to the problem.
Having said that, I'm not sure I possess the neccessary skills to extract the calibrate code and secondly I still hold out hope that it's a driver issue. The reason I say that is because the old lcd was working fine in so much as left and right worked ok (just the display and colours that were ruined) and the problem only started when the new screen went in!
But I guess that still leaves me needing to extract lcd driver files.......
yw
...been googling the issue and it seems that you can get Android to force a recalibrate. IF you're rooted and handy with adb or terminal emulator.
...now that might not fix your issue BUT it might.
Google for ts_calibrate and ro.calibrate
Sent from my Desire Z using xda app-developers app
igor45 said:
yw
...been googling the issue and it seems that you can get Android to force a recalibrate. IF you're rooted and handy with adb or terminal emulator.
...now that might not fix your issue BUT it might.
Google for ts_calibrate and ro.calibrate
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
Well I'm not rooted... yet! But I've been working on it (looks like I need a goldcard...) I'm not especially handy with adb but I can follow instructions and have a very small amount of common sense
So I'll try it!
Thanks again for your help man - very much appreciated.
Make sure that you use the gfree method from the wiki page for rooting. And read n re-read before you do it for a flawless and easy root.
Sent from my LG-C710h using xda app-developers app
Any luck? facing the same issue
Hi, I am a noob and wondering what is the solution to this problem?
After installing the TeamBURST ROM on my andoird the screen is working fine in the bottom half but the upper half has the y-axis flipped.
Appreciate any inputs that point me in the right direction (I just started rooting and flashing yesterday so fairly know but I do know coding).

Notification bar bug on 4.0.4 IMM76I

Hi
Have anyone encountered the notification bar bug where at times the bar can only be pulled down to half of the screen only ?
So far I am not able to replicate the bug
Sent from my Galaxy Nexus using xda premium
Not me. But I do notice maps running alot
Sent from my Galaxy Nexus using XDA
No offense but if you can't replicate it then there is no use discussing it.
Sent from my Galaxy Nexus using Tapatalk 2
scoobdude said:
Not me. But I do notice maps running alot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
App bug, not 4.0.4 bug.
dplate07 said:
Hi
Have anyone encountered the notification bar bug where at times the bar can only be pulled down to half of the screen only ?
So far I am not able to replicate the bug
Click to expand...
Click to collapse
Happened to me just 1 time and I too haven't replicated it. Reboot fixed it.
scoobdude said:
Not me. But I do notice maps running alot
Click to expand...
Click to collapse
This has always been the case.
prinzhernan said:
No offense but if you can't replicate it then there is no use discussing it.
Click to expand...
Click to collapse
Why? What if someone else has seen it and/or been able to replicate it?
martonikaj said:
Why? What if someone else has seen it and/or been able to replicate it?
Click to expand...
Click to collapse
Because if you can't replicate something, it's not a bug. It could be something with a certain users own environment/setup.
I've never had that occur, so unless one were to go line by line, app by app to see what's causing it, how can you call it a bug? It could be another app that's causing the issue.
Sent from my Galaxy Nexus using Tapatalk 2
greeced said:
Because if you can't replicate something, it's not a bug. It could be something with a certain users own environment/setup.
I've never had that occur, so unless one were to go line by line, app by app to see what's causing it, how can you call it a bug? It could be another app that's causing the issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Unless you understand the nature of the bug, perhaps you are not reproducing the correct conditions for it to occur.
That blanket statement is fairly inaccurate.
Happened to me before, it's due to the rotation sensor getting confused. It thinks it's in horizontal mode; just turn it to the side and back vertical again and it clears it right up. Nothing major.
adrynalyne said:
Unless you understand the nature of the bug, perhaps you are not reproducing the correct conditions for it to occur.
That blanket statement is fairly inaccurate.
Click to expand...
Click to collapse
Agreed, however the same can be said if you call something a bug without evidence to support it.
The word "bug" is used far too often in my opinion.
It's just like when you file a bug report for cyanogen nighties, they require you to be able to replicate it, for it to be considered an issue.
Sent from my Galaxy Nexus using Tapatalk 2
scoobdude said:
Not me. But I do notice maps running alot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Open maps once and let it find your location. That should keep it from showing up in your recent apps all of the time.
Sent from my Galaxy Nexus using Tapatalk 2

Tfs shell "little problem"

Hi....... Im using Tsf shell on my Samsung s3. The only problem I have is that every now and then the shell loads up., just like when you turn the phone on...*It happens when I use an app and then try to go back to my home screen... Most times it's okay but every now and then the shell needs to load......... It only takes about. 10 second to load and then all is ok
Happens when I use various apps or sometimes when the phone is on standby
Anyone else having this problem
Any advice*Sent from Samsung S3
tuffpro said:
Hi....... Im using Tsf shell on my Samsung s3. The only problem I have is that every now and then the shell loads up., just like when you turn the phone on...*It happens when I use an app and then try to go back to my home screen... Most times it's okay but every now and then the shell needs to load......... It only takes about. 10 second to load and then all is ok
Happens when I use various apps or sometimes when the phone is on standby
Anyone else having this problem
Any advice*Sent from Samsung S3
Click to expand...
Click to collapse
Same thing happening to me every now and then. Haven't found out an exact cause or fix for it yet sorry. Best email the devs directly. Just it hasn't bothered me enough yet to go and moan at them about it.
Sent from my GT-I9300 using XDA Premium HD app
This happens when you run out of RAM.
Sent from my GT-I9300 using Tapatalk 2
Try this one: settings > developer opt > uncheck "dont keep activities"
Hit thanks if i helped your problem
Sent from my ST26i using xda premium

Freeze instead of force close

********UPDATE*********
Thanks to hardcore,I found a fix in another thread
forum.xda-developers.com/showthread.php?t=1843837&page=4
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Ever since Jellybean instead of apps force closing as they normally would my phone becomes unresponsive and reboots after 2-3 minutes.It gets quite annoying and I wanted to know has anyone else has been getting this issue. I have wiped dalvic/cache also factory data reset,I am unable to do anything in anycut,the phone automatically goes through freeze process,any ideas on how to fix issue?
got the issue too. Only on tw based roms tho. why i only **** wit cm10/aokp. And anycut doesnt work completely with jb yet. You have to use the anycut widget instead
Thanks for the response I guess the only way to stop the problem is not to have a tw Rom,I guess I might just have to bit the bullet on that one,im not really into flashing roms I'm only rooted for hotspot and system settings to change certain things
Sent from my SPH-L710 using xda premium
Could always setup the dualboot to have stock and an aosp rom
Okay I might have to look into that, thanks for the quick responses I thought I was the only one, my friends have s3 to add well and was not experiencing issue,I can see now that's for top them not having stock Rom
Sent from my SPH-L710 using xda premium
You could also find out what process is causing the bad behavior, what's not playing nice, and remove or freeze that app. You could also try to do a fresh install of your rom.
I was getting the same issues, but I found out that Maps social pin-point (Latitude) was causing my issues and unchecked all of the options related to check-ins and location sharing. No problems since.
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Sent from my SPH-L710 using xda premium
brianhot1 said:
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Click to expand...
Click to collapse
For that specific problem, it was trial and error, but a logcat would help. At the time, I couldn't figure it out. I believe there's an app to help read logcats.
Okay thanks
Sent from my SPH-L710 using xda premium
I found one app that was freezing for me I cleared data and uninstall updates for play store, the issue still happens sometimes though
Sent from my SPH-L710 using xda premium
Download Fast Force Close it really helped with the extremely frustrating freezes.
https://play.google.com/store/apps/details?id=com.issess.fastforceclose
Sent from my SGS3!
Cool so how exactly would the app help me if you don't mind me asking I see that it produces the fc would that help in fixing the freezing issue? And if so then how
Sent from my SPH-L710 using xda premium
Any update? It still happens?
Sent from my SPH-L710 using xda premium
Did you use the app? It seems that the app triggers a force clse popup if (im guessing here) a certain amount of time has gone by (like the OS itself does, but maybe shorter) or whenever an app goes unresponsive (it comes up instantly)
So either way, its supposed to fix the force close dialog not showing up for you.
I have our installed but I guess im still working on how to use it, I'm going to try to run it in the background
Sent from my SPH-L710 using xda premium
Update!!!!! Thanks to http://forum.xda-developers.com/member.php?u=336619
Thanks for the tips guys. This was also irritating me to no end on several Samsung roms. I think it happens on the Note and S3 too. Maybe even the S2.
My solution was:
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Sent from my SPH-L710 using xda premium
Great tip. Had never heard of this before.
Sent from my SPH-L710 using xda app-developers app

[Q] so this is something I have never seen...

Has anybody ever seen a yellow screen that looks very similar to custom recovery, and says
"Device has detected a hardware reset"
I can take a picture when I get home, it doesn't do anything to me, but in one specific application if I try one specific command it sends me to this screen. I just reboot and then it optimizes applications and throws me back in as though nothing had happened.
Thoughts?
Xiutehcuhtli said:
Has anybody ever seen a yellow screen that looks very similar to custom recovery, and says
"Device has detected a hardware reset"
I can take a picture when I get home, it doesn't do anything to me, but in one specific application if I try one specific command it sends me to this screen. I just reboot and then it optimizes applications and throws me back in as though nothing had happened.
Thoughts?
Click to expand...
Click to collapse
It happened to me. I sort of just shrugged it off though.
I think it's related to the root method tried, which one did you use?
AdriVelazquez said:
It happened to me. I sort of just shrugged it off though.
I think it's related to the root method tried, which one did you use?
Click to expand...
Click to collapse
I used the one click root
Isn't that the "demigod" thing we had back in the beginning? It's in the ATT forums. Can't remember what it meant at the moment though.
Sent from my LG-LS970 using xda premium
I had this issue when I did my root method. But try engine's method which hasn't effected my phone yet.
Sent from my LG-LS970 using xda premium
I get it sometimes, usually when playing ingress and running Pandora one at the same time.
Sent from my LG-LS970 using Tapatalk 2
cowfodder said:
I get it sometimes, usually when playing ingress and running Pandora one at the same time.
Sent from my LG-LS970 using Tapatalk 2
Click to expand...
Click to collapse
Exactly when it happened to me, Ingress.
Sent from my LG-LS970 using xda app-developers app
That's the kernel crash handler if in not mistaken
Sent from my LG-LS970 using xda app-developers app

Categories

Resources