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
Related
hi guys my auto rotate function got disabled when I was flashing cyan new recovery image and I don't know how to fix it I tried the directions on his thread and I guess I just don't understand them. I am on cyan 3.6.8.1. can someone explain in layman's terms how to fix it? thanks and have a great day!
Check your settings. In settings-->sound+display, on the bottom see if orientation is checked
it is checked. no rotation.
gtrplr71 said:
it is checked. no rotation.
Click to expand...
Click to collapse
Accelerometer might be broken. Try playing papijump.
what is papijump?
gtrplr71 said:
what is papijump?
Click to expand...
Click to collapse
A game lol. Search it on the market. It tests if your accelerometer is working. If the little red guy won't move no matter how much you turn the phone the you know the accelerometer is broken or that there is a software problem.
Its not broken. Go to crayogens Rom the stable ones thread and in the faq on the 1st paste there is a command u enter in the terminal to fix the auto rotate I ran into this problem a few times myself and it was easily fixed be the script
pistol4413 said:
Its not broken. Go to crayogens Rom the stable ones thread and in the faq on the 1st paste there is a command u enter in the terminal to fix the auto rotate I ran into this problem a few times myself and it was easily fixed be the script
Click to expand...
Click to collapse
Could be heres the script
20. My auto-rotate/accelerometer isn't working!
Not really the fault of the ROM, but here's how to fix it: Go into recovery, drop to console, "mount /data", then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
solved thanks guys
how did you guys fix this because the commands did not work for me and i have tried numerous times
If the commands don't work u might wanna wipe and reflash. I say just make sure the feature is on, then try the script again and if all fails the wipe and reflash. I hate to wipe myself so try to avoid it. Try the script in the terminal in recovery then reboot and try in terminal in rom itself and reboot.
Hi all,
trying to get my feet wet with some android hacking and thought getting my AR.Drone to work with my legend would be a good start. It requires connecting to the ad-hoc network created by the drone. The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root. I then found this app for the desire: code.google.com/p/desire-adhoc/ but the legend has a different wifi chip, so it didn't work. Attempting to reproduce what that app does I did
$ adb shell
# su -c 'insmod /system/lib/modules/tiwlan_drv.ko'
insmod: init_module '/system/lib/modules/tiwlan_drv.ko' failed (No such file or directory)
even though that file definitely exists. Am I missing something here, or is that part of the annoying restrictions still present even on the rooted legend? Ad-hoc wifi must be possible somehow, the wifi-tether guys managed to get it to work. Unfortunately their code is a bit over my head. Any pointers?
thanks
-felix
Do it from recovery mode. We don't have access to /system in normal usage of phone (you get used to it).
okay, I guess I have to learn how to bake my own update.zip.
still curious though, why am I getting "no such file or directory" if it's clearly there (and a similar method seems to work on the desire)?
I also tried this:
forum.xda-developers.com/showthread.php?t=754961&highlight=legend
Which is a quite cleverly hacked wpa_supplicant, but that resulted in no wifi at all any more, even though the patched supplicant is officially the same version. strange.
any clue how the wifi-tether guys do it?
No, those command work. Boot your phone to recovery mode, then mount the /system partition from the ClockworkMOD menu. then you can execute your commands, they should do it.
Also, questions like this shouldn't really be in the development section. Just so you know.
You got it all wrong guys... first you dont need to su -c as you already are root. Second... you need to load sdio.ko prior to tiwlan_drv.ko. And no we do not perform these in recovery mode
I thought he was editing files... Oh well, I'll read more carefully in future. Sorry guys.
EDIT:
Yeah, look:
The normal way is to edit /system/etc/wifi/tiwlan.ini as described e.g. here: projects.ardrone.org/boards/1/topics/show/1098 but /system doesn't seem writable even though I have root.
Click to expand...
Click to collapse
So he could edit from recovery mode. But, I was still an idiot, I said to do the insmod things from recovery. I am very sorry for wasting time here, I'll learn to read carefully and give proper answers.
Sorry
TheGrammarFreak said:
Also, questions like this shouldn't really be in the development section. Just so you know.
Click to expand...
Click to collapse
hmm, okay. I figured since I'm _trying_ to develop something...
well, next time.
BlaY0 said:
you need to load sdio.ko prior to tiwlan_drv.ko.
Click to expand...
Click to collapse
aaaahhh, that got me a bit further thanks! very confusing error message...
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Also I guess the confusion was my own fault since I rolled three different ways of doing one thing into the same post...
Oh man, I've said all the wrong things today. I'm so sorry. I'll just leave this thread now.
sanktnelson said:
so module loading works now, but the phone just reboots a few seconds after I set
"iwconfig tiwlan0 mode ad-hoc"
any further advice?
Click to expand...
Click to collapse
Yes. Loading modules just isn't enough in our case. You need to load firmware too before you bring interface up otherwise your system will reboot
Check Gratiend ROM thread or look into init.legend.rc for hints on firmware loading...
thanks. found this
/system/bin/tiwlan_loader \
-f /system/etc/wifi/Fw1273_CHIP.bin -e /proc/calibration \
-i /system/etc/wifi/tiwlan.ini
after googling init.legend.rc. doesn't seem to make a difference though. also tried using tiwlan.ini from the wifi tether guys, but no luck. device still reboots after setting ad-hoc mode. I guess I give up, there's no-one answering to my question on the wifi-tether google group either. i guess just because it's open source doesn't mean it's for the uninitiated...
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
BlaY0 said:
Try sleep for 1 or 2 seconds after you load firmware, then bring interface up or start wpa_supplicant.
I you are using patched wpa_supplicant I guess you will have one more obstacle. It supports only wext aware devices and I guess our driver is not wext aware...
Click to expand...
Click to collapse
I enter the commands by hand, so there's already a delay in between. And I'm doing this by hand precisely because the patched supplicant didn't work on the legend. I guess now I know why. Thanks for all the advice though.
exicar said:
I solved the problem by installing Cyanogenmod (all other tries failed)
Sent from my Legend using Tapatalk
Click to expand...
Click to collapse
I had a CM6 nightly installed and toyed around with it a bit, but I actually use my FM radio (I know, barely anyone else does...) so I need to use a HTC ROM. liked the CM6 in a lot of other respects though. still out of the question for now.
Also I would eventually like to contribute whatever comes out of this to a proper AR.drone app that requires root and nothing else.
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?
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
Hello everyone, I hope one of you can help me as I didn't really find any solution on the internet.
I got a Huawei Ascend P7 L10 and I absolutely love it, but I run into a problem every time that I try to install the Xposed framework on my device. The installer tells me that it "could not copy app_process to /system/bin"
I've looked a bit on the internet and found that it might be because of a permission problem within the /system folder but when I tried to change them my phone got stuck on the boot logo and I had to flash the ROM again to use my phone.
Does someone know how to solve that problem?
I'm of course on android 4.4.2 and tried different version of Xposed Installer 2.6 and 2.7) but nothing changed.
Thanks for the help.
Edit : I've also tried version 2.5 and both the automatic and manual flash of the installer, but couldn't get any of both working it always finished by a big "FAIL" written on the recovery screen.
Do you have root access?
I heard many problems with xposed on the p7 and personally think that it must be something with a whole device...
CCody said:
Do you have root access?
I heard many problems with xposed on the p7 and personally think that it must be something with a whole device...
Click to expand...
Click to collapse
Hello I do have root access (and I have all permissions on the /system/bin folder (at least I should have as I did chmod 777 /system/bin))
Can you post a logcat? You can try flashing it via the recovery first (you need to have a custom recovery, I'm guessing you do not, which is why the recovery installation failed when you tried it).
GermainZ said:
Can you post a logcat? You can try flashing it via the recovery first (you need to have a custom recovery, I'm guessing you do not, which is why the recovery installation failed when you tried it).
Click to expand...
Click to collapse
Oh i didn't know about the custom recovery, which one can I get (if there is any for my device of course)
Sorry about the newbie question but what is a catalog and how do I post it? (Never had to do/use that on iPhone :$)
PrimuSSaintS said:
Oh i didn't know about the custom recovery, which one can I get (if there is any for my device of course)
Click to expand...
Click to collapse
I don't know, check your device's forum.
PrimuSSaintS said:
Sorry about the newbie question but what is a catalog and how do I post it? (Never had to do/use that on iPhone :$)
Click to expand...
Click to collapse
Logcat*
There are many tutorials around such as this one. You can search for more if you don't prefer that method.
GermainZ said:
I don't know, check your device's forum.
Logcat*
There are many tutorials around such as this one. You can search for more if you don't prefer that method.
Click to expand...
Click to collapse
there it is
EDIT :
Problem solved, for the people that have the same problem than me, here is the solution :
Download BusyBox (playstore)
Download Terminal emulator
Then type this :
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
Click to expand...
Click to collapse
this will give you full access and you should be able to install Xposed framework (at least that worked for me) - Don't forget to disable the resource hooks in the settings panel as the numbers will be in green but it would still mark Xposed as uninstalled.
source :
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200&nocache=1&z=1143765179790447