Database Users

Slow gsensor switching

If your slow on this freshly official installed froyo do this trick. Its a bit buried on this forum so its a bonus for those who haven't come acroos it.
Switching from landscape to portrait takes about 5 senconds. Heres the fix. Its not my find so don't bite my head off! (ducks)
Go to settings, display. Scroll all the way down to "Horizontal Calibration". Place your phone on a level surface that has a ledge. I used my window ledge on my room. Place the phone flat on its face. Lcd screen facing the surface. You should be looking at the battery cover. Not place it so the bottom half of the screen sticks out a bit from the ledge so u can hit the calibration button on the screen. Once it does its calibration, DONE! Fixed gsensor 5 second lag!
MOD EDIT: Added credits for you. Next time, do it yourself!
Original credits to abrognlie here: http://forum.xda-developers.com/showpost.php?p=11552644&postcount=163
and styckx here: http://forum.xda-developers.com/showthread.php?t=964866

Awesome, never knew that and it does work. Thanks!

Thanks. Just tried it and it works.
Sent from my SPH-D700 using XDA App

totally works!!!! but edit ur post cuz it says NOT instead of NOW lol

betterment66 said:
totally works!!!! but edit ur post cuz it says NOT instead of NOW lol
Click to expand...
Click to collapse
Done. Swipe suk0rs. But its the best. Lol.

Lol! Thats why I ducked. I knew I was going to get chewed up for not posting the credits.

Worked great, thanks.
Sent from my SPH-D700 using XDA App

you know, I think I just figured something out. A while back when the first leaks of froyos came out, some people were having gsensor lags while others were not. I was one who did have a bad laggy gsensor. And I noticed that my windows xp machine would sometimes detect my phone with odin and other times it would not. Then one day when I was going to flash, my pc did not detect it. I grabbed the phone while still being connected to the usb line and flipped it to remove the battery cover. When I flipped it to remove the battery cover my pc made a ding noise and "walla!" , odin detected my phone again. Then I assumed my epic had a bad wiggly usb port on my epic. But it wasnt! When I removed the battery cover and flipped it over lcd screen up, odin dropped the connection. I noticed the pattern right there and then.I was successfully able to make odin detect and not detect my epic by just flipping the phone screen facing up and then screen facing down. That explains why some people are flashing and then have a working gsensor while others, it's broken after a flash. The gsensor has some relationship with the hardware and software in the flashing process. In such a way that it gets calibrated after a flash depending on how the phone is laid down while its being flashed.
Everyone, do this simple test. Next time you odin or use the new samsung tool to flash, lay the phone down with the screen facing the surface and battery door facing up towards your view. Let it flash and see if your gsensor works flawlessly. I bet it will.
So in a nutshell. Flashing screen facing down gives you a good working gsensor. Flashing screen facing up gives you a broken laggy gsensor.

abduljaffar said:
you know, I think I just figured something out. A while back when three first leaks of froyos came out, some people were having gsensoe lags while others were not. I was one who had it. And I noticed that my windows xp machine would sometimes detect my phone with odin and other times it would not. Then one day when I was going to flash, my pc did not detect it again. I graded the phone and still connected to the usb line, I flipped it to remove the vary cover. And my pc made a ding noise and "walla!" , odin detected my phone again. Then I figured its a bad wiggly usb port on my epic. But it wasnt! I flipped it over lcd screen up and odin dropped the connection. I was successfully was able to make odin detect and not detect my epic by just flipping the phone screen facing up and then screen facing down. That explains why some people are being a working gsensor while others it's broken after a flash. The gsensor has some relationship with the hardware in such a way that it gets mia calibrated after a flash depending on how the phone is laid down.
Everyone, do this simple test. Next time you odin or use the new samsung tool to flash, lay the phone down with the screen facing the surface and battery door facing up to your view. Let it flash and see if your gsensor works flawlessly. I bet it will.
So in a nutshell. Flashing screen facing down gives you a good working gsensor. Flashing screen facing up gives you a broken laggy gsensor.
Click to expand...
Click to collapse
You know this actually does make alot of sense.
I calibrated mine face down and it is fine now, but I hope somebody else can give this a shot for you.

and mine refuses to work, switches to landscape when face down and leaves me in landscape mode when facing straight up. Tried to do it with auto rotate off and it wont switch to landscape now. Starting to hate this phone.

tenaciousj said:
and mine refuses to work, switches to landscape when face down and leaves me in landscape mode when facing straight up. Tried to do it with auto rotate off and it wont switch to landscape now. Starting to hate this phone.
Click to expand...
Click to collapse
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.

bjhill2112 said:
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.
Click to expand...
Click to collapse
Just did it, seems snappier but not really fast by no means.

bjhill2112 said:
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.
Click to expand...
Click to collapse
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?

The face down horizontal calibration worked for me, on stock EB13. Rotates in less than half a second, it's pretty quick.
The terminal trick stopped working for me for some reason :/ I've always used connectbot, once you su the first time it doesn't ask for root anymore after that.

murso74 said:
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?
Click to expand...
Click to collapse
I used connectbot

murso74 said:
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?
Click to expand...
Click to collapse
Just type "su" at the console

If the upside down calibration dont work, root and do the command line stated above a few post.

[Q] Weird ADB Swipe Activity?

Recently got the 2013 Nexus 7 as a replacement to my cracked 2012 one.
I was messing around with ADB and fastboot (the device is unlocked and rooted with TWRP) when I discovered something which I think is a bug.
If you turn on the "Pointer location" feature from Developer options, and then run an ADB input swipe command like:
Code:
adb shell input swipe 755 1655 1100 1655
Then the device somehow manages to jump back to the "X" shaped bootup animation, without actually turning off.
I'm pretty sure this isn't deliberate, but is it just me? Also, is this already discovered?
Freddy

Backing up a Nexus 4 with broken digitizer

So I have a Nexus 4 with 4.2.2. I dropped it yesterday morning in the dirt this morning, it fell out of my bag maybe 2 feet off the ground.
There is a small scuff on the left upper corner and the lower half of the touchscreen no longer works. Only buttons on the top half of the screen respond. The display is completely intact though, not shattered and displays images just fine. Since the lower half screen is unresponsive, I can't enter my SIM PIN or unlock my phone.
My skill level in this area is pretty low. Enabling LTE is pretty much the most technical thing I've done with this phone.
I do have twrp but it appears I do not have USB debugging enabled. I've been googling this mess and experimenting with adb and fastboot for the last hour but haven't been able to make any progress backing up my phone or enabling USB debugging. I was thinking if I could at least enable USB debugging at least I could use Control Android or something right?
I'm able to connect using adb but I must be using incorrect syntax. I've tried every command I have come across and always get a not found error. Is there some other referance I should be using - I started with developer.android.com/tools/help/adb
~ # ←[6nadb devices
adb devices
/sbin/sh: adb: not found
~ # ←[6n
C: \adt\ sdk\ platform-tools>fastboot devices
0047e1b856555005 fastboot
I will be getting a new phone but my primary concern is there are a handful of text messages from my boss sent me literally minutes before I dropped my phone and he is now unreachable for the next week.
Is there any possibility the digitiser came loose and that's why only half of the screen doesn't work? I need to buy a #5 torx driver anyways but I don't want to open it up if its not a viable solution.
Any other suggestions?

Just boot into TWRP and type 'adb pull /sdcard/' in a console. Recovering text messages I'm not sure how to do, might be doable through a shell.
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
also maybe useful
http://www.modaco.com/topic/302958-backup-messages-the-adb-way/

[Q] major problem

Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance

skalicioustimes said:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
Click to expand...
Click to collapse
I would find the correct firmware for your tab (from the Samsung site) and reflash the full Odin tar. If that doesn't help I'd contact Samsung about the issue.

Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?

skalicioustimes said:
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
Click to expand...
Click to collapse
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.

Yes unfortunately the Tab 4 has been opened.
By disconnecting and reseating the battery sockets i believe the warranty is void. The back has been opened.
I find if i get the device running momentarily then by gently plexing "twisiting" the unit in my hands can cause the screen to switch back to normal.
But soon after the dreaded horizontal and vertical lines appear then the device becomes frozen again, the intermitent lines jump around the screen with whatever is in the background leaving the display frozen.
Only solution is to gently open up the device and disconnect the battery and then reconnect again.
This is only a temporary solution as the problem reappears very soon after.

moonbutt74 said:
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Click to expand...
Click to collapse
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..

skalicioustimes said:
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
Click to expand...
Click to collapse
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m

moonbutt74 said:
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
Click to expand...
Click to collapse
I'm unsure about your suggestions, as i don't know were to locate those commands.
I have done a factory reset, so i am just waiting for the device to charge before attempting to load new firmware through Samsung Kies which i downloaded through this link... http://www.samsung.com/uk/support/usefulsoftware/KIES/#versionInfo
are the commands you suggested within the Samsung Kies software?

ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m

moonbutt74 said:
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
Click to expand...
Click to collapse
When i was having the problems initially, i could not for the life of me get into recovery mode using the button combo's. Eventually i did get into recovery, so as a last resort i cleared cache, and done a factory reset. Now it is booting up as normal but i was going to use Kies on windows to see if it is a software issue.
So were do i go about getting
adb
logcat -d
mount
ps
dmesg.
And what would you suggest as a step by step guide from were i am at now?
Note: i haven't physically messed with the device to see if the Horizontal and Vertical screen issue is still there.
Thanks

XDA search bar
adb install

moonbutt74 said:
XDA search bar
adb install
Click to expand...
Click to collapse
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.

skalicioustimes said:
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
Click to expand...
Click to collapse
You're not supposed to revoke adb debugging.
Look, i'm at a loss, the thing is, do you blow more cash on a quess, or cut your losses.
As to learning how to use adb, XDA searxh box, using adb.
m

not a bother.
thanks for your help :good:

skalicioustimes said:
not a bother.
thanks for your help :good:
Click to expand...
Click to collapse
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m

moonbutt74 said:
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
Click to expand...
Click to collapse
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there

skalicioustimes said:
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
Click to expand...
Click to collapse
dude are you on hangouts ? if so pm me.

moonbutt74 said:
dude are you on hangouts ? if so pm me.
Click to expand...
Click to collapse
sent you a message on hangouts. thanks

Flashed the stock kernel using Odin, i hope that gets rid of the screen issue :fingers-crossed:

Well 3 hours later and the Tab is going good
My daughter is delighted that it's sorted and she hopes it stays that way
Many thanks to Moonbutt74 for your time and effort, it's very much appreciated.
Would you say that it's good to go? And is there anything else i need to do to the device before handing it over to her?
Cheers

Navigation buttons stopped working (software issue)

Hello, just to make no doubt: I made factory reset (even twice), but after rebooting, hardware buttons stop working after some period of time. After cleaning the phone with MiAssistant, everything comes back to normal - however not for a long time, so it's not physical issue, I guess. I though it was a fault of vibration tool app, which was running in background, but now I am confused. Maybe U know what is going on, or if it is present on other devices too. A2017G
please really

BurakSefaSenturk said:
Hello, just to make no doubt: I made factory reset (even twice), but after rebooting, hardware buttons stop working after some period of time. After cleaning the phone with MiAssistant, everything comes back to normal - however not for a long time, so it's not physical issue, I guess. I though it was a fault of vibration tool app, which was running in background, but now I am confused. Maybe U know what is going on, or if it is present on other devices too. A2017G
please really
Click to expand...
Click to collapse
I noticed that they get broken when you change the phone's resolution. This might fix it for some time, but I have no idea why this happens
Enable MiPop
Download a terminal app, write
su
hit Enter
wm size 1080x1920
hit Enter
wm size 1440x2560
hit Enter
Now, what I think is weird is that the keys actually seem like an extension of the touchscreen, not like for example the OP3T's which don't break when you change resolution. So if your capacitive buttons break, then your touchscreen should too?
You could also try flashing LOS or whatever (and test if the issue is still there) then do the procedure in my guide to return to stock.