Database Develop

auto rotate function disabled? (solved)

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.

How to Root in Cyanogen 4.04?

Hello everyone, I apologize in advance if I've posted this in the wrong section. Ok so here is my problem, I recently got Cyanogen 4.04 (Latest stable release) on my phone. I was gonna try out the overclock app from the App market but it doesn't let me open it because i'm not ROOT. I thought users are always ROOT in modded ROM, are they not? If not then what should I do to ROOT? I used the one click method for root at the begining (to install cyanogen) and Haykuro SPL Update. Thanks.
p.s I am a complete noob so please go slow.

If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.

NeoBlade said:
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
Click to expand...
Click to collapse
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?

pooranimator said:
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
Click to expand...
Click to collapse
type su into the terminal emulator and see what is says. if you were able to flash a custom rom then your phone is rooted, you could've gotten a bad download.

Download Better Terminal from the Maket and as david mentioned, type in "su" then press enter to see if you have root access.

if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..

mikespy said:
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
Click to expand...
Click to collapse
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #

B-man007 said:
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
Click to expand...
Click to collapse
Thanks for the help....
I actually did download better terminal and when i typed in su and hit enter. It went to the screen your talking about and since i had just installed SetCPU it asked if i wished to allow i clicked yes. So i asume i have rooted correctly and guess the "overclocking" program on the market might just not download on my phone correctly with the cyan 4.0.4.

Thanks
Thanks to all of you for your replies. I think I know what the problem was. The OverclockWidget is a Widget...duh silly me. I was trying to open it as a regular app and was failing. Added it as a widget on the first screen and now everything works. I have one quick unrelated question, while downloading the latest experimental release of Cyanogen I read at the bottom of the post in read that the users should not use any Apps2SD while using Cyaogen's latest release because the ROM does it by itself or something like that. What does that mean?
@mikespy- tap and hold for a sec on your screen and add the OverclockWidget widget on your screen then tap to open. That's how you open the OC util.

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

anybody know how to get ad-hoc wifi to work on the rooted legend?

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.

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