Database Develop

SU app broken since Donut.

Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.

hettbeans said:
Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.
Click to expand...
Click to collapse
Are you sure you didn't load the wrong rom and you lost root?

supremeteam256 said:
Are you sure you didn't load the wrong rom and you lost root?
Click to expand...
Click to collapse
Uhh, yeah. I have root, all the apps id already given permission to still work. Its new ones that do not.

Have you tried to push su back or run enable superuser to see if that will help?

supremeteam256 said:
Have you tried to push su back or run enable superuser to see if that will help?
Click to expand...
Click to collapse
I don't know what either of those means. If you could provide some instructions (terminal commands, etc) that would be great.
Thanks in advance.

Try this first.
Code:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite

Alright, I will try that in a little while when I am at a computer. Thanks

hettbeans said:
Alright, I will try that in a little while when I am at a computer. Thanks
Click to expand...
Click to collapse
Also in the mean time you can try the superuser whitelist in the market to see if that will work.

Hey, formatting my SD card seems to have fixed it, but thanks for the help.

no problem

Most of my apps get a force close msg

I have the latest cyanogen rom. The apps were working fine before when I had first installed the rom the first time. I tried to install the flash player mod and it just froze the launcher so I had to wipe and reinstall a fresh cyanogen rom and now I am getting most of my apps telling me to force close them.

This didn't work for me but I had a different issue completely, but I read elsewhere that it may fix the chain force-closes. So download this file, then in a terminal emulator run:
su
sh /sdcard/fix_permissions.sh
See if this helps.

is there a location I am to put the file to all I am getting is sh: can't open /sdcard/fix_permissions.sh sorry I am kinda new to all this so please bare with me and ty for the fast reply/ help.

ok wierd it's fixed now all I did was reboot the phone and everything is working now

slvr69tiger said:
ok wierd it's fixed now all I did was reboot the phone and everything is working now
Click to expand...
Click to collapse
I'm guessing this is your first Android phone, so let that be a lesson to you... when you have any issues, the first thing to do is reboot. If they still persist, it's time to do a full wipe and reflash.

[Q] Magnetometer - Need for calibration

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?

Keyboard Issue's, how to solve them!

Hi Guys,
This is driving me crazy. A lot of people, who are too lazy to search. Well, here you go.
Allright, you brought your Xperia X1 with android. Now, there is a problem. Once in a while, the keyboard does not respond, only action is a reboot. HELP?
Allright, lets get started.
Download this package:
http://www.mediafire.com/?cp1o1glxjo145pu
Install a android of your choice(just normally).
Unpack, and copy all (yes, all) contents to you SD card.
Move the turbo or Monster kernal to the NKBoot Map, click yes to replace any excisting files.
On your computer, open up the readme, and read it carefully.
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
That will remove your current modules, and at the next boot, they will be replaced.
Reboot, and proceed with step 5 and the rest. Follow the guide excactly, then you're good!
Have a nice evening!

Not Test, But Thanks You !!!! I Need

sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks

yes it is. just reboot after the error, then the new modules will install!

Just thinking ... a dev might know it this is possible ...
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

Kurt Krummbein said:
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
Click to expand...
Click to collapse
Don't know if this could be a good option. Because I have had some freezes when runing the script. And sometimes the screen changes it orientation.

thomskipsp said:
After step 4(after you entered 'su') type this:
rm /lib/modules* -rf
Click to expand...
Click to collapse
casualt said:
sorry to say but when i folled your guide to just after step 4 when typing the -rf
it says cannot remove read only file system
is that normal?
thanks
Click to expand...
Click to collapse
Shouldn't it be?:
After step 4(after you entered 'su') type this:
rm /lib/modules/* -rf
mind the /
Anyway, I tried both ways, and rm /lib/modules/* -rf seems to work, but I can't load back into CWM if I install a kernel with seperate keyboard modules. I think I mess up the exact order of installing normal, removing modules, replacing kernel, restarting. Hope this will work
http://forum.xda-developers.com/showthread.php?t=1072387

Yes. I can restart keyboard after freeze. Although with eggy monster kernel, my screen is rotated 90degrees after that.
No. I can't get back into CWM, after I switched to a kernel with seperate modules.
The original kernels of Honeycomb v3 both worked.
I tried the kernels with seperate modules of this post and i tried the ygge kernels.
Can this be solved? No. But apparently, there is a workaround http://forum.xda-developers.com/showthread.php?t=1072387.

when I type "sh /data/opt/autostart.sh" and press Enter, I get this error:
"insmod: can't read '/lib/modiles/microp-ksc.ko': no such file or directory
insmod: can't read '/lib/modiles/microp-keypad.ko': no such file or directory"
Can you help me?.
Where is kovsky keyboard modules????
I using ygge kernels with HoneyComb Froyo V.3
PS: sorry I used the same post in several threads

Proximity sensor error

Hello,
I have been using XZ for two years now with no problems and started flashing about a year ago.
Now, my first problem came when I wanted to connect my phone with a bluetooth headset. It works fine until I turned off the screen and placed it into my pocket. After investigating the possible issues, it seems to come from the proximity sensor.
First tried to install another ROM, as maybe the error came from there but it was to no use.
Then I tried dialing *#*#757....... the sensor will be off, if I block it, it will say on, but when I unblock it it stilll says "on".
So I went to try to turn off the proximity sensor completely, as every apk i tried didn't fix the error.
The other fix I found was an Xposed framework.
I followed the instructions of installing ExistenZ_Y but when I tried to flash the ROM it said "can't mount /system" and had to go through recovery to flash a stock ROM. The problem is that even now, when I enter TWRP and try to flash the xposed-v78-sdk22-arm it still says it can't mount the system. I tried going to the terminal and typing "mount -o rw,remount /system" but to no avail, it won't mount the system as rw.
So here I come, after searching every thread I could find, to know if someone could help me in any way.
Many thanks in advance

Ash.VIII said:
Hello,
I have been using XZ for two years now with no problems and started flashing about a year ago.
Now, my first problem came when I wanted to connect my phone with a bluetooth headset. It works fine until I turned off the screen and placed it into my pocket. After investigating the possible issues, it seems to come from the proximity sensor.
First tried to install another ROM, as maybe the error came from there but it was to no use.
Then I tried dialing *#*#757....... the sensor will be off, if I block it, it will say on, but when I unblock it it stilll says "on".
So I went to try to turn off the proximity sensor completely, as every apk i tried didn't fix the error.
The other fix I found was an Xposed framework.
I followed the instructions of installing ExistenZ_Y but when I tried to flash the ROM it said "can't mount /system" and had to go through recovery to flash a stock ROM. The problem is that even now, when I enter TWRP and try to flash the xposed-v78-sdk22-arm it still says it can't mount the system. I tried going to the terminal and typing "mount -o rw,remount /system" but to no avail, it won't mount the system as rw.
So here I come, after searching every thread I could find, to know if someone could help me in any way.
Many thanks in advance
Click to expand...
Click to collapse
add the line:
gsm.proximity.enable=false
to the end of the file build.prop located in /system, reboot, and the sensor will be disabled.

Pyramid Head said:
add the line:
gsm.proximity.enable=false
to the end of the file build.prop located in /system, reboot, and the sensor will be disabled.
Click to expand...
Click to collapse
I am trying to disable the proximity sensor by editing the build.prop file as suggested but with no luck. Is there any other solution? I am using RRemix Rom v5.8.2

akisg said:
I am trying to disable the proximity sensor by editing the build.prop file as suggested but with no luck. Is there any other solution? I am using RRemix Rom v5.8.2
Click to expand...
Click to collapse
As far as my knowledge goes no there isnt... Maybe with an app but i dont know
PS: Damnnnn thats an old post

Pyramid Head said:
As far as my knowledge goes no there isnt... Maybe with an app but i dont know
PS: Damnnnn thats an old post
Click to expand...
Click to collapse
Tried some that use light sensor (which is working) instead of proximity sensor but still no luck...
How hard can it be to disable one sensor?
PS: I know, found it during a forum search so no need to open a new one

akisg said:
Tried some that use light sensor (which is working) instead of proximity sensor but still no luck...
How hard can it be to disable one sensor?
PS: I know, found it during a forum search so no need to open a new one
Click to expand...
Click to collapse
Dont know man, are you sure you entered the command exactly as i wrote?
If yes try to find the command inside the build prop on your own and edit the true part to false
eg: gsm.proximity.enable=true --> gsm.proximity.enable=false

Pyramid Head said:
Dont know man, are you sure you entered the command exactly as i wrote?
Click to expand...
Click to collapse
Yes, i added this "gsm.proximity.enable=false"
without quotes at the end of build.prop file. Is that a universal command or xperia z specific ?

akisg said:
Yes, i added this "gsm.proximity.enable=false"
without quotes at the end of build.prop file. Is that a universal command or xperia z specific ?
Click to expand...
Click to collapse
i havent tried it on another phone but it must be universal

Pyramid Head said:
i havent tried it on another phone but it must be universal
Click to expand...
Click to collapse
maybe it's not applicable in nougat? thanks for the help btw, i'll keep searching for a solution

akisg said:
I am trying to disable the proximity sensor by editing the build.prop file as suggested but with no luck. Is there any other solution? I am using RRemix Rom v5.8.2
Click to expand...
Click to collapse
That is also the only way I found. The easiest way is to go through adb. You go 'adb pull /system/build.prop' modify it on your computer then go 'adb push build.prop /system/'. It worked for me. It didn't solve every problem but sure did help a lot!
If that does not work, maybe it isn't your proximity sensor? I know there are apps that can "write" the info that your proximity sensor info is either 0 or 1 (or in between), but that didn't work for me, maybe with you it will

What rom are you using? I edited build.prop file from phone and saved successfully. I tried some apps but no luck. I wonder if that command maybe is different in nougat roms