Rooted JM5. Tried /system/bin/sensorcalibutil_yamaha, but can't open it with Root Explorer 2.11(I click on it and nothing happens).
The problem is that in games I have to turn the phone a bit right to be in straight.
SOLVED!
forum.xda-developers.com/showpost.php?p=6999499&postcount=8
post 8 and 9 helped. I've done it using terminal emulator(the first line in #8 isn't needed).
Related
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Have you installed a rooted rom? or just trying to see if you have root access on the stock rom?
Jeremy.Bentham said:
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Click to expand...
Click to collapse
Try using the nexus-addon-0.1-signed.zip
http://forum.xda-developers.com/showthread.php?t=636795
I always thought that digital compass of our galaxy s wasn't very accurate. Yesterday I've tried to compose *#0*#, go to "Sensor" and... WHAT!?!?! "Need for calibration 2". I thought it was a problem of my phone, so I tried with another GS, and got the same result. I've also tried to calibrate it with many compass apps, but nothing... Anyone knows the solution?
Wave your phone for some time in 8-figur moves.
Xacky said:
Wave your phone for some time in 8-figur moves.
Click to expand...
Click to collapse
I've tried with no results... On two different Galaxy S
rotate your phone..
factory
what about factory reset?
EDIT 1:
Update: quick method
delete ms3c_yamaha.cfg located in /data/system/
and if there is a backup file delete it too
then plug your phone to pc or just use terminal emulator (Device must be rooted)
write following:
adb shell
su
/system/bin/sensorcalibutil_yamaha
hit Enter
wait for finish then rebooot phone and all works like a charm!
Can anyone post video of proper compas calibration?
statistic said:
what about factory reset?
EDIT 1:
Update: quick method
delete ms3c_yamaha.cfg located in /data/system/
and if there is a backup file delete it too
then plug your phone to pc or just use terminal emulator (Device must be rooted)
write following:
adb shell
su
/system/bin/sensorcalibutil_yamaha
hit Enter
wait for finish then rebooot phone and all works like a charm!
Click to expand...
Click to collapse
I've found that simply deleting ms3c_yamaha.cfg located in /data/system/
does the trick. Then *#0*# shows that everything is working OK...
Facing the same problem but..
facing the same problem but I don't see ms3c_yamaha.cfg in my /data/system. I'm using Galnet MIUI. Does it have a different file system?
waving my phone in a large "8" does calibrate my phone for a while...but after sometime it starts showing wacky directions again...
Runing GingerReal and averything works just fine....
mahatasin said:
waving my phone in a large "8" does calibrate my phone for a while...but after sometime it starts showing wacky directions again...
Click to expand...
Click to collapse
I have i9003 & face the same problem on my phone, I have to calibrate every time before using the GPS or compass.
I9000 with CM9 (ice cream sandwich)
statistic said:
what about factory reset?
EDIT 1:
Update: quick method
delete ms3c_yamaha.cfg located in /data/system/
and if there is a backup file delete it too
then plug your phone to pc or just use terminal emulator (Device must be rooted)
write following:
adb shell
su
/system/bin/sensorcalibutil_yamaha
hit Enter
wait for finish then rebooot phone and all works like a charm!
Click to expand...
Click to collapse
Seems like Icecream sandwich does not have this files at that location... does anyone know what should be done for cayonogemod 9 or icecream sandwich?
I have to open a new thread here because I can't still post in the android section, by the way I've tried to follow the instruction found in this post for solve the keyboard freezing problem but I when I launch the script it says that he can't find the 2 files it have to launch, and opening the folder by the terminal or by my ubuntu I can't found the 2 files
/lib/modules/microp-ksc.ko
/lib/modules/microp-keypad.ko
anyone knows why?
a member wrote on the same post that he had the same problem, so he have deleted some files and have run the new kernel...how can I launch the device with another kernel?
thank you
Hi,
answer is easy (well, for those who looked behind the scenes), at boot, the system checks if the kernel-modules on the sdcard are different from the installed in /lib/modules ... and due to the fact that the kernel version is the same (just with the keypad drivers optional as modules), the unpacking of the tar.gz-archive is skipped.
You have two options now, use the 'Terminal Emulator' and do a:
su
rm /lib/modules/*
and reboot your phone, or copy the two modules from the tar.gz in ubuntu.
Ciao
Kurt
I have tried the first before opening this thread without any result, now I'm retrying
ehm...now the script runs...but I can't use the onscreen keyboard and everytime I enter an app the screen rotates...is it normal?
and if I press camera button it doesn't return to the home
Hm, rotating the screen is not normal ... just if he thinks you pulled out the 'real' keyboad.
I think, the camera button of Honeycomb froyo is prepared for camera usage ;-).
Hm, perhaps, best solution at the moment would be, to run the unload-load-script when the phone is waking up from sleep mode. So, when keypad is lost, the user can send to sleep with the power button an immediately switch it on again ... and additionally, the script can run when a call comes in ... don't know if these events can get picked up and the event-handlers can be changed, just thinking ...
Ciao
Klaus
I've had this problem for a while, but I always managed to "fix" it by using Milestone 2 Debounce.
Now that I've rolled back to CM 7.2.4b (I was using CM10), I can't seen to use it. My HW keyboard keep repeating letters, and when I try to load the module inside Milestone 2 Debounce, I get the error: "Problems executing shell commands as root! Is this device rooted and are insmod/rmmod binaries available?". My device is rooted (obviously) and I had granted M2 Debounce root privileges. I've googled for insmod / rmmod but couldn't find anything useful.
Isn't anybody else having this problem with Milestone / CM7? Any idea on how to fix it? Maybe kadablan could enable debounce natively in CM7
guaycuru said:
I've had this problem for a while, but I always managed to "fix" it by using Milestone 2 Debounce.
Now that I've rolled back to CM 7.2.4b (I was using CM10), I can't seen to use it. My HW keyboard keep repeating letters, and when I try to load the module inside Milestone 2 Debounce, I get the error: "Problems executing shell commands as root! Is this device rooted and are insmod/rmmod binaries available?". My device is rooted (obviously) and I had granted M2 Debounce root privileges. I've googled for insmod / rmmod but couldn't find anything useful.
Isn't anybody else having this problem with Milestone / CM7? Any idea on how to fix it? Maybe kadablan could enable debounce natively in CM7
Click to expand...
Click to collapse
it happend to me, when i moved back to milestone (after using xperia mini pro for 3 months) and flashed 7.2.3, and it still happend even on 7.2.4. havent been using the hw keyboard since then but today i used it, and to my surprise, it worked fine. now, i did notice that it also happens when on openrecovery console (the last one, with 2ndboot) and i tried flashing froyomod, and it didnt happend there (but the rom was unusable compared to 7.2.x) so, i moved back to 7.2.4b and used the virtual kb instead... dont know how it got fixed (dont know IF it is fixed)
im gonna check that debounce app, didnt knew it existed
sorry for my english
how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...
hitlab1 said:
how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...
Click to expand...
Click to collapse
I hate to say this since I'm not a moderator, questions need to go into the Question/Help thread.
Also, you need to read the post (located in this General thread) and do a little search and research to help you. I'm even nice enough to provide you a link (http://forum.xda-developers.com/showthread.php?t=2686652) which is the Official - the 4.4.2 update - discussion thread.
However,
To begin, you must be on NB4 (the small update that happened a few weeks ago. Also, if you have NOT installed the 4.4 leak, and didn't really do anything to your phone but only rooted.
or
You didn't even root your phone, just can't get passed the 27% of the OTA update, please follow these instructions:
USER BEWARE, THESE INSTRUCTIONS WILL ROOT YOUR PHONE. I'M NOT RESPONSIBLE FOR ANY DAMAGES YOU CAN CAUSE. THIS IS (please forgive me, my caps lock was on) to help you get the update.
1 ) On you Windows computer, go to http://www.kingoapp.com/
2) Download Kingo and install.
3 ) Make sure you have the required Samsung drivers installed also so your phone can communicate with your computer (use the USB 3.0 cable that came with you phone).
4 ) before you connect with the computer:
A ) go into setting (in your phone) and turn on USB debugging. If you don't know how to turn that on, there is instructions within the Kingo software itself.
B ) Set your screen timeout option for 10 minutes.
C ) Also remove your lock screen to none.
5 ) With your phone on, attach the USB cable. It should connect (you'll hear multiple sounds)
6 ) The Kingo software should recognize your phone and give you the option to Root. Please do so (this will not trip your KNOX flag).
7 ) Pay close attention to your phone's screen while going through the rooting process, popups will happen and you will be asked to click approve various functions that is required for root.
8 ) After root is successful, detach you phone. Go to the Google Play store and download Root Explorer. I have the premium version (it worth the few dollars, plus it helps out the programmers).
9 ) Open Root Explorer (or any file manager with root access) and go to /system/csc/
10 ) Look for feature.xml.bak. If this exists, delete feature.xml and rename feature.xml.bak to feature.xml
11 ) See if dexdump is in /system/xbin/ if not down Download dexdump from Jakman85 - http://forum.xda-developers.com/showpost.php?p=51440984&postcount=313
12 ) Copy dexdump to /system/xbin and set correct permissions. Root Explorer will request the directory to be made r/w temporarily while the file is inserted then put it back r/o, however you still need to set the correct permissions for that individual file. The best way is tap and hold another file already in that directory and select permissions and see how to properly set the dexdump permissions. Make sure the permissions match the other files.
13 ) Check for Update and let it do it's thing, or you can sideload the 2400258.zip file (you can download this from a link earlier in another thread) and install it from stock recovery from your sccard.
Note : on first startup after upgrade I did not have touch screen access but the S-PEN did work. However, you can simply restart the phone to get the screen working with touch.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app