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] Recover from a soft brick

A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now

Thanks! Extremely happy you are deving for this phone

What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.

uskr said:
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
Click to expand...
Click to collapse
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.

Thanks! I am messing around with the APKs and scripts to get the webtop to work without the dock. So I wanted to make sure I was covered.

designgears said:
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Click to expand...
Click to collapse
I already did both adb pull of system and tar, but how did you do the retail dump?

lpsi2000 said:
I already did both adb pull of system and tar, but how did you do the retail dump?
Click to expand...
Click to collapse
tar dump as root of system

One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.

uskr said:
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
Click to expand...
Click to collapse
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;

designgears said:
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
Click to expand...
Click to collapse
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.

lpsi2000 said:
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
Click to expand...
Click to collapse
tap at the bottom right of the screen right above the search button

designgears said:
tap at the bottom right of the screen right above the search button
Click to expand...
Click to collapse
ahha, thank you. Now I know I am going crazy. I used it yesterday to wipe when the system was unstable on me after playing around with the framework. I am must have stumble on that by accident. I am wondering if this documented yet somewhere around here.
Also too bad we cannot get root from there yet.

Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.

realawill said:
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
Click to expand...
Click to collapse
No, I just made a bad edit and it was FC hell

IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.

designgears said:
No, I just made a bad edit and it was FC hell
Click to expand...
Click to collapse
Crazy....mine just would not reboot. But good to know that there is a way to recover. Love the phone but hate Motorola. Wish that it was easy as the Cappy.

Cool stuff. I may snatch the framework off the phone in stock form and make a batch package for this so folks can easily just double click to restore their framework and system app folder.
Good work DG...

I never get past that initial... Starting RSD protocol support screen. Is that fast boot? If so I'm a retard...
EDIT: I need the face palm sticky. It's not Volume UP...it's Volume Down. Reading comprehension for the loss...

azy8000 said:
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
Click to expand...
Click to collapse
I have done this several times now, it works

I soft bricked my Atrix earlier this morning, and used this to recover. The time limit is a serious pain!
I ended up needing to separate /system into 5 separate pushes of 30MB each in order to get them done in time.
Oddly, after restoring everything, the phone is no longer associated with my motoblur account, and I can't add it.
Also, I think there my be some files in /system that are unaccounted for by the filesystem, as there is 70MB more than what is present.
Edit:
Restoring the system fixed both above problems.

[q] kernels with keypad drivers as modules and cwm

hey did anyone manage to get the keys work with these kernels (KERNELS WITH KEYPAD DRIVERS AS MODULES) in any CWM build?
I try to load it using terminal like before but its not working
even the Gscript method is not working anymore, is there any other solution than restarting the device with KERNELS WITHOUT KEYPAD DRIVERS AS MODULES after each freez, the freez mostly happen after pressing the right option in the keypad or using setCPU

Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!

saobang3886 said:
Did you do all step remove old modules and make autostart for it? it work good for me. Try my build here http://forum.xda-developers.com/showthread.php?t=1068869, and follow this tut:
http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 for make kernels with keypad drivers as modules work!
Click to expand...
Click to collapse
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist

kerfooly said:
i did
what i did was i put the monster kernel with keypad drivers and when i boot android the keypad is already not working i go to terminal
i type ur first command box and then rite after that i type the second one(could be wrong because its written SU again?!) and then after i finish nothing happens and using the Gscript i load the script and it says files doesnt exist
Click to expand...
Click to collapse
OPP!
First, you should boot with kernel without modules keyboard, it easy to setting in first time. try setting all thing who make that build recommend!
Second, in stall Autostart and gScript app. copy autostart.sh to root of your sdcard. open terminal, remove old modules and copy autostart.sh to /data/opt like this post http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
Then open restart keyboard script in your computer, open Gscipt in your phone, add new script, tip name is restart keyboard. Script like the file you open in computer!
after that, restart to window mobile, copy kernel with keyboard as module to your boot folder, replace old file, then reboot and it will work!

Well, after setting up all the scripts for loading and reloading of the kernel modules and then removing all kernel-modules of the old kernel (that without the drivers als module), you have to reboot your device. As part of the boot process, the new kernel modules are copied from the tar.gz-file, without deleting the old modules, this step will be skipped from the boot script.
So.
1. prepare all scripts
2. remove the old modules
3. boot the new 'KEYBOAD-AS-MODULES' kernel with it's module-archtive in place
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory ... the works quite nice and is much cooler that trying to press vol-down in the right moment ... i renamed it then to no_recovery.txt ... makes getting to recovery quite relaxed ...
Ciao
Kurt

Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.

hopsakee said:
Well, this reads like the solution to my problem I adressed in this post http://forum.xda-developers.com/showthread.php?t=1195638.
But I don't understand. You mean I can just put an empty recovery.txt file into the npkboot directory. If I reboot with that file in place, CWM wil start?
If I rename the empty recovery.txt file into no_recovery.txt it will not start into CWM but start into Android.
Click to expand...
Click to collapse
Yep, here's the code from the init script that's in rootfs.img:
if [ -f /sdcard/npkboot/recovery.txt ]; then
so ... have fun with Android on your X1 .
Ciao
Klaus

Kurt Krummbein said:
On the other hand, the problem exists, that booting to CWM will fail with that kernel (somebody might correct me, if i'm wrong), but as a workaround this, you can put a file with the name 'recovery.txt' into the npkboot directory
Click to expand...
Click to collapse
Ik works. I start into CWM. But the volume buttons still don't respond, and I need those to navigate through CWM.
Anyone a solution other than switching back to standard kernel without seperate modules?

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

[MOD][DEPRECATED] eRecovery

Content deprecated and removed to avoid confusion.

updated: 31/7/2011 to remove 'lastresort' method
updated: 10/08/2011 to remove 'saveme' method
II. Instructions on how to use (applies to Nova)
If you're not a developer or cooker and you just want to know how this works, you're in the right place. Like I've said before, this MOD is already patched in Nova. Assuming the others will also follow these instructions, this is how to use it:
Method for booting directly into recovery:
Repeatedly press a physical key *
* For the key press method, it needs to be a physical key, not one of the capacitive buttons. It also needs to be pressed or released for the script to work, so do not hold it. Example: volume down, G, ... You need to press it before the boot animation and you have a 3 seconds time frame to do this so it's best if you just repeatedly press it every second or so.
This is it.
Now you can play around with less fear of having to flash firmware all the time.

Noejn said:
Repeatedly press a physical key *
Have a file on your microSD card called "saveme" **
Have a file on your microSD card called "lastresort" **
Click to expand...
Click to collapse
So, we can use either one of these three methods to boot into recovery?

evilenter said:
So, we can use either one of these three methods to boot into recovery?
Click to expand...
Click to collapse
Yes, but read the *s.

Is this only for the NOVA ROM? and can you post a link to your PayPal donation page, if you have on that is...

This is just amazing. Thank you so much, again, Noejn.

"saveme" or "lastresort" mus be empty files without any extension?

rgabi88 said:
"saveme" or "lastresort" mus be empty files without any extension?
Click to expand...
Click to collapse
Unless you change the detection scripts yes.

thx you for show us every detail!

i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care

sankhauaa said:
i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care
Click to expand...
Click to collapse
Can you share how have succeed to break it just to know and to avoid doing the same mistake.
Regards,
Me

sankhauaa said:
i already bricked my fone during restore through cwm recovry...will button method or file method working in my bricked fone without nova rom ? i cant check as i handover my ob to lg custmr care
Click to expand...
Click to collapse
Uhh, AFAIK you can't.

nice ...
thx man

Noejn said:
So, following the progress on this thread: [BRAINSTORM] Booting directly into recovery, I have devised a way that will surely help us in this department.
I will now split this into 2 sections:
1# post - MOD outline and guidelines for developers / cookers
2# post - Instructions on how to use (applies to Nova ROM)
I. MOD outline
Alright, so, first of all, you need to know this method is actually 2:
a) daemon hijack
b) postboot script hijack
Since redundancy is important I figured out it was best if we had a safeguard at least in two places. Also keep in mind that even though it partially uses the daemon hijack method, this is not a xRecovery like for SE XPERIA devices. This mod will get you in the true recovery in its own partition, it won't mount one on /system which for instance has quite some caveats (tricky to format /system...).
a) daemon hijack
While XPERIA devices hijack the usbcharge daemon, we don't have that binary on our OB. So I went looking for one who could be of use and I decided for the compass one.
So, first step: go to init.rc on the ramdisk, look for akmd2 daemon (compass) and change the entry to this:
Code:
service akmd2 /system/bin/akmd2
user root
group root
oneshot
Next step: rename your /system/bin/akmd2 to whatever, for example 'compass'.
Now, create an empty bash file and first, put there our microSD card file detection script (1st safeguard):
Code:
mount -t vfat /dev/block/vold/179:17 /mnt/sdcard
if [ -e "/sdcard/saveme" ];
then
rm /sdcard/saveme
reboot recovery
fi
As you can see, it will reboot to the real recovery, it won't mount one like xRecovery.
After that script, comes the second one for key detection (2nd safeguard):
Code:
cat /dev/input/event0 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck ];
then
reboot recovery
fi
Now, event0 is physical key. If you want this to work with capacitive buttons, switch to event1. And remember, it's not holding down the key while it boots, this implies either pressing or releasing, that's the only way to trigger event0.
And finally, we have to redirect to our compass daemon, so assuming you renamed it to 'compass':
Code:
/system/bin/compass
Voilá! Pretty easy isn't it?
Now let's go to the 2nd method.
b) postboot script hijack
While this is executed later at boot (already in the boot animation) it's also less dependent on /system.
It's fairly simple, just open this file: init.hub.post_boot.sh, and add to the ending:
Code:
mount -t vfat /dev/block/vold/179:17 /mnt/sdcard
if [ -e "/sdcard/lastresort" ];
then
rm /sdcard/lastresort
reboot recovery
fi
This will check for another file. There you go.
Now keep reading.
Important stuff
Q. Are there any pre-requisites for this to work?
A. Yes, you'll need busybox on the ROM at question.
Q. Can it be broken?
A. Yes it can. While for 90% of developers' actions it will work, sometimes it won't and you'll end up flashing firmware sorry. For example, if these conditions are assembled, it will break: a) no busybox; b) broken kernel / c) crucial service /system files missing.
Q. Do I need to do anything to get working this on Nova?
A. No, it's already been patched with this mod. Just read post #2.
Click to expand...
Click to collapse
Can one of this methods work on stock rooted firmware? How to do this? Can you guide me to do this? I'd like to have one of the two ways (maybe both, why not??) to boot into recovery...

i've tried to mod init.rc but at reboot the file returned original and don't work
why

Just tested it pressing G button, works fine. Thanks man this is great.

Please tell me where wrong, init.rc at root edit akm2 to root root and save, reboot and go back as before.
why whats wrong.
Thanks

[Q] solving keybord freeze on honeycomb froyo v3

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