Related
Hey, guys after hours of thinkering it seems i devised a fix (at least a temporary, i guess it can be better implemented), but still wifi works with turned on radio.
I will not be doing any scripts or whatever.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
K now the requirements:
1. nonworking sim card (or att sim card)
2. RSD lite 5.0
3. stock 4.1.2.6 SBF flash file
4. Installed drivers on the computer for rsd
5. GladRoot http://forum.xda-developers.com/showthread.php?t=1016060 than you very much Ririal
6. OTA update
7. Working adb shell (there are other ways too but i prefer this one so ill write how i did it)
8. SQL editor, i used SQLite database browser (get it online its freeware)
9. titanium backup (if you wish to backup things, YOU MUST NOT RESTORE the [SETTINGS/BLUETOOTH] Settings Storage 2.2.1 however.
10. turned debug mode on when using adb
The process:
1. backup your data
2. Flash the stock image with RSD lite as its written here http://forum.xda-developers.com/showthread.php?t=991072 thank you kennethpen
3. put in the nonworking/att sim turn on the phone use wifi to configure motoblur
4. do not download the update yet
5. obtain root as described here, use the 1.5.7 method tho since we will be updating the ota http://forum.xda-developers.com/showthread.php?t=1016060
thanks again ririal
6. download and install ota update
7. do the afterupdate with the GladRoot
8. still on wifi, set up google account, update market gmail etc.
9. use adb/root explorer to copy the /data/data/com.android.providers.settings/databases/settings.db file to your sdcard into a directory you made before (name doesnt matter) example:
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard-ext/test
10. put phone into airplane mode, turn off phone
11. put in your sim card, turn on
12. let it boot and wait a min or two
13. before sliding press and hold the off button and choose airplane mode (it is IMPERATIVE that airplane mode is turned on)
14. sign into motoblur again (wifi should still work - turn it on tho since your in airplane mode)
15. repeat step 9 but copy to a second directory (lets say test1)
16. turn airplane mode off - you will loose wifi and sign into motoblur again
17. repeat step 9/15 but copy to a third directory (lets say test2)
18. copy the files from test2 and test1 to your computer - obviously to two different folders (use mass storage setting or adb pull)
19. open up the settings.db with sqlite from the not working config (in our case the one in test2) go to browse data and table secure
20. find the entry wifi_country_code and the value will be the one of your country (at least so it was with me), change that value by double clicking on it to US
21. Save the file
22. copy to your sdcard via usb to a directory lets name it "works"
23.turn off your phone, and put in the nonworking/att sim card, power it up
24. register motoblur again blah blah (ye its annoying there are ways around but that comes later and we needed it for the ota update)
25. turn the airplane mode off (its imperative to do so)
26. now we use adb again:
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/works/settings.db .
chown system settings.db
chgrp settings.db
chmod 440 settings.db
cd ..
chmod 555 databases
exit adb shell with ctrl+d (in linux dont know about windows)
27. turn off phone, put in your sim card, turn on phone, register motoblur
28. most probably wifi will work for a moment than it will stop working and youll get a notifiaction lost data connection and something on (at least so it was for me)
29. use the wifi toggle on/of button to turn off and on the wifi a few times, than at the third or fourth time turn it off than on than immediately go into the browser and click on refresh as soon as you see the wifi icon in the notification tab. WiFi should work now, you can even turn it off and on with the wifi toggle button and it still works.
30. ANOTHER WARNING THO, THERE ARE QUITE SOME DRAWBACKS TO THIS METHOD (WHICH I HAVENT DISCOVERED ALL YET, TO BE HONEST BUT IM SURE THERE ARE QUITE SOME - SINCE WE DO NOT ALLOW THE SYSTEM TO EDIT THE SETTINGS.DB ANYMORE - BY CHMODDING THE PERMISSIONS), AN ISSUE I SAW IS THAT YOU CANNOT GO INTO AIRPLANE MODE ANYMORE - that is because the airplane mode state is saved in the same settings.db as the setting that blocks wifi, and if you just change that one and dont write protect the file and the databases folder the system just overwrites it again, so for now this is it.
AGAIN this is all on your own RISK, i cannot bi liable for anything out of the ordinary that happens, damages or whatsoever your phone or even you.
So now im awaiting responses if it works for you guys.
Oh and a few of the steps are just for backup purposes
Many thanks goes to Azuzu aswell, he was of great help all the time.
What about for the Canadian Bell Atrix can you please help us.
When I insert non working sim card into the phone, wi-fi working only once, after booting. Then when phone is going to lock, wi-fi is sleep and never work again. Is it instruction help to work with wi-fi during the day without rebooting? Thanks for instruction!
---
All is fine with Wi-Fi when it in Motoblur...
What about GPS?
May be needed to add GPS ON in this instruction?
Thanks guys. Its work for me. But too much DRAWBACKS. GPS does not work, settings are not saved
my friends you figured it all out like i did after a day of testing.
As i already said before there are some rather big probles that arise with this method, however for now this is the only way i found to having a working sim +wifi working.
Basically all the issues arise from the settings menu, since the settings from there are stored in the setting.db file that we disallow changing, due to this fact, i have devised a rather simpler way to do all the above + apply your specific settings - however you still wont be able to change them once you change the permissions.
1. gps state cant be changed as reported
2. ringtone/notification tone cant be changed
3. USB mode is stuck in NONE mode or the one you changed it to before doing read only
4. Possibly you cant pair new BT devices (havent tried that but i assume it might happen)
5. cant change lockscreen type (so if you pick fingerprint afterwards it wont change the lockscreen)
6. more possible problems, still if you want wifi you will endure some of those, they are however rather easy to fix, for people who dont change things all the time.
7. i found out that you have to turn off and on wifi (with the widget or in the networks menu) 2 times to make it work and it stops working if your phone changes the network from 3g to 3g or vice versa, however you just turn wifi off and on again and its fine (eventually you can just set your phone to 2g only or 3g only - either the dialer method or edit a config file - ill post that another time)
8. airplane mode not changing as stated above
So i did it like this this time:
lets assume you already have the phone 1.5.7 rooted (you can even have 1.2.6 rooted but the ota update brings nice features like longer battery, better fingerprint reader etc) and activated. NOW THIS SHORTENS THE PROCESS BY FAR and improves on the things that werent working before, it might lower battery life minorly but, well mine is still at 70% after ~16 hours so )
YOU WILL HAVE TO DO THIS ONLY ONCE (well at least until you want to change your ringtone hahaha )
1. Put in your working sim (just into the rooted atrix and the databases dir has to be read write like before, if you followed my guide above you have to go with adb shell to /data/data/com.android.providers.settings and write chmod 755 databases)
2. turn on phone in normal mode
3. set all your settings as you like and i really mean all - ringtones notifications - everything you can think of
4. turn all the networks on - wireless (it wont work but the state has to be on), bluetooth, gps - the thing is you can always turn them off, but if you write protect the file with them off you cant turn them on properly
5. pair your bluetooth devices (all of them) - havent tried yet if necessary but i think it is
6. reboot phone into normal mode, assure yourself that all the things are as you like
7. connect phone in debug mode, and set usb to none (it will stay in the none state, but you can always copy stuff with adb over, to your sdcard/internal phone mem as opposed to choosing mass storage mode where you have no adb access to them, but that is your choice ( you can manually change the state in the settings.db before making it read only, but i wont go into those details now)
Code:
adb shell
su
cd /sdcard-ext/test
cp /data/data/com.android.providers.settings/databases/settings.db .
ctrl+c/d to exit shell
8. connect phone in mass storage mode, open the settings.db file in the /sdcard-ext/test with the sqlite editor go to the brose tab, and secure, change the wifi_country_code value to ALL (last time i wrote US but ALL works fine so its more relaxed), save it
9. change the usb connection mode back to none
10. failure to chown and chgrp the settings.db to system and chmod it correctly can results in a soft brick
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/test/settings.db .
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
cd..
chmod 555 databases
reboot
11. the phone shoudl reboot now with all the networks turned on, you can use the widgets (or int he wireless menu) to turn off wifi and bluetooth (tested it myself and it works), havent tested gps turning off yet, but its no problem since gps turns on itself only when apps use it (maps etc, weatherbug can use it aswell, so might check into it if its permanently turned on than)
12. turn wifi off and on 2-3 times, than turn it on, it should be working now
Thanks for testing this out to confirm that it works at least
Anyhow if someone might get a clue what issues the command to change the wifi_country_code hes encouraged to share, so we can only fix that problem and there wont be these side effects than
you can however change all the settings by just editing the settings.db with the sqlite editor manually, youd have to figure out all the parameters and values yourself (some are fairly easy - for instance for usb mode, some can be rather hard - for instance ringtones, cuz you must have the path and everything)
EDIT, YOU CAN LEAVE OUT THE PAIRING BLUETOOTH DEVICES STEP, pairing works, i just tried it with an apple bluetooth kb, and its fine.
RacecarBMW i cannot say anything with certainty, since i dont have one to test it on, but probably the same method would work for the bell atrix (use the method in the post above, with the ALL value for wifi_country_code), however you have no sbf to flash and its way more dangerous that you will create a softbrick, so please be very careful and its all YOUR RESPONSIBILITY. I AM AND WILL NOT BE LIABLE FOR ANY ADVERSE EFFECTS.
We need to lock only some rows in db file or creating daemon which would keep these lines in memory. Is it posible with SQLite?
crnkoj Please change on step 10 in listing:
cd /data/data/android.providers.settings/databases
to
cd /data/data/com.android.providers.settings/databases
I do all steps and my GPS works fine... Thanks
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
loggin111 said:
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
Click to expand...
Click to collapse
you can just enter to another folder to /data/data/ directory with cd and run ls -l to view directory permissions.
chmod 755 databases
and something like 755 for settings.db
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
1.5.2
crnkoj said:
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
Click to expand...
Click to collapse
hi
does it work with 1.5.2 rooted?
i flashed sbf back from unroot 1.5.7 to 1.2.6 , i didn't gladroot because i had not wifi for update & after update.bat
so i stopped @ 1.5.2 & i cannot update anymore, please help me to activate my wifi.....
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
hey guys what wifi issues? i have a ATT on vodafone UK and i dont seem to see any issues.
crnkoj said:
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
Click to expand...
Click to collapse
Hi can this fix be on a custom rom? i mean it will be included on a custom rom..
ronaldo, use search ... http://forum.xda-developers.com/showthread.php?t=1010942&page=3 lucky you arent one of us who have this issue.
emorej, if you read my first post, it says i wont be doing any scripts/cwm flashable updates/custom roms. If anyone wants to implement this in his rom hes free to do so, he has to be careful tho, since basiically the script that updates it, has to change only the wifi_country_code ALL and than make the databases folder read only, it must not copy over a generic settings.db since there are user specific things in it.
Jartyn and i are trying to figure a more source problem related fix for the issue, but that will take quite some time i fear.
Here is an even better solution from akizakian
http://forum.xda-developers.com/showthread.php?t=1058260
Simplest Solution
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Mate you are mistaken, its two totally different issues you and i are talking about, yours is that 5ghz isnt working, mine is that wifi isnt working in certain countries at all. by copying the files you supplied my wifi again stops working, because there is a country lock within the moto atrix wifi drivers (the version doesnt matter, may it be 1.2.6, 1.5.2, 1.5.7 or 1.8.3, the issue you fixed with your method is only the nonworking 5ghz on the 1.5.2. leaked sbf)
ceo.mtcl said:
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Click to expand...
Click to collapse
The LG Optimus wifi drivers fixed my simunlocked wifi problem in qatar.
The other solutions that were being thrown around did not.
seems moto is gonna fix it with an update:
https://supportforums.motorola.com/thread/50598?start=15&tstart=0
Hi all -
I wrote a script and created a CWM update-flashable to perform a one-line install of the CM7 GPS Fix, documented here by jwleonhart. There were some complaints about jwleonhart's install instructions; it's a bit cumbersome and not trouble-free, especially for noobs. Please read the original thread for detailed instructions on what my script does; the script exactly does jwleonhart's instructions.
NOTE: EVERY VERSION OF THIS FIX MAKES SUBTLE BUT IMPORTANT CHANGES THAT MAY IMPROVE OR DEPRESS YOUR GPS FUNCTIONALITY. UNTIL A TRUE GPS DRIVER DROPS FOR THE VIBRANT (which at this point seems very unlikely) ALL WE CAN DO IS HACK AND TWEAK. NEWER VERSIONS MAY WORK BETTER OR WORSE THAN OLDER ONES! PLEASE POST WITH YOUR EXPERIENCE USING THE VARIOUS VERSIONS OF THE FIX, AND PLEASE BE CONSTRUCTIVE/HELPFUL WITH YOUR FINDINGS!
There are three separate ways to install: CWM, CWM with no gpsd, and via shell script.
CWM Installation
The easiest way to install the GPSFix files is to download and flash Vibrant_CM7_GPSFix_V1.4-CWM-signed.zip. All files will be copied over and read/execute permissions will be properly set.
NOTE: Flashable does NOT contain AngryGPS. There are some people who have better results without it, so I'll let you install that one on your own. You can find the APK at jwleonhart's CM7 Install Guide.
OPTIONAL: There's a no-gpsd version of the CWM flashable as well - if you want to use the gpsd from your current nightly, or mix and match. The GPS driver might get better in time, and who knows if down the line the gpsd bundled with the latest nightly is better than this one, pulled from Trigger Redux#13 (CM7 Nightly#54).
Script Installation
The script is available for users who want to customize their own GPS fix. It requires an extra reboot (since you can't just run the script after installing a new nightly), but you can easily add/remove files to the script to suit your own needs. Personally, I use the script to test new versions before they go into the CWM flashable.
Attached is the zip file with all the files and the shell script you need. Just extract the folder to your SD card; then in a terminal (ADB or terminal emulator with root), run these commands:
Code:
su # if you're not already dropped into superuser status
cd /sdcard/GPSFix
bash GPSFix.sh
It will automatically copy all the files (gpsd, secgps.conf, gps.conf, 90getgps_lto) to the right places, then set permissions those files, then reboot. AngryGPSmod.apk is in there but is not installed; I suggest try the GPS fix without AngryGPS first, then install it after if you don't get good results.
Script Contents
For those interested, here's the contents of the script..
Code:
#!/system/xbin/bash
FIXFILES="/system/etc/gps.conf
/etc/init.d/90getgps_lto
/system/vendor/bin/gpsd"
REMOVEONLY="/data/gps/lto.dat
/data/gps/lto2.dat
/data/gps/svstatus.txt
/data/gps/ltoStatus.txt
/data/gps/secgps.conf
/system/bin/agpsd"
mount -o rw,remount /system
echo "==================================================="
echo "======Vibrant CM7 GPS Fix One-Command Install======"
echo "=================by strictlyrude27================="
echo ""
# Delete previous fix files
echo "Deleting previous fix files..."
for file in $FIXFILES $REMOVEONLY
do
if [ -f $file ]; then
rm $file
fi
done
# Copy new files and set permissions
echo "Copying new files over..."
for file in $FIXFILES
do
fname=$(basename $file)
cp $fname $file
chmod 0755 $file
if [ $file == "/system/vendor/bin/gpsd" ]; then
chgrp shell $file
fi
done
echo "Rebooting device.. Enjoy GPS!"
echo "Install AngryGPSmod.apk manually if you want to."
echo ""
reboot
Credits
jwleonhart - writing up the CM7 install guide
roffee - finding the original GPS Fix for CM7
jad3675 - providing original Long Term Orbital download script
PLEASE go to their threads and hit their Thanks button. They did all the heavy lifting, I just packaged up their findings and work into a simple-to-use flashable.
"If I have seen far, it is because I have stood on the shoulders of giants."
--Isaac Newton
Changelog:
Code:
V1.5.1
-- renamed init-script to overwrite CM7's implementation of V3 of this fix
-- now offering "newgpsd" variant - contains gpsd from latest CM7 nightly
-- standard zip: faster locks, but more prone to randomly quitting working
-- newgpsd variant: slower locks, but more resilient GPS indicator [color="red"] still needs testing[/color]
V1.5
-- cleaned up script
-- now keeping LTO data named lto2.dat (used to rename to lto.dat)
-- lowering threshold for lto2 refresh to 3 days
V1.4 (all variants)
-- replaced lto.dat with lto2.dat - preliminary testing indicates survival after reboot and better TTFF
-- now using us.pool.ntp.org for the time server - if you're not in the US, please adjust your gps.conf accordingly
-- gps.conf tweaks - trading accuracy for TTFF for now..
V1.3.1 (all variants)
--set permissions on downloaded lto.dat to 755 (was 644) - i couldn't get
any birds in view before, now i can lock. give this a try if 1.3 doesn't work.
V1.3 (all variants)
--removed agpsd
--added 90getgps_lto - will fetch latest long term orbit data on boot
--hopefully these changes help get REPEAT locks faster - please let us know!
V1.2CWM-nogpsd
--same as V1.2CWM, but with no gpsd. This way you can use gpsd from
the latest CM7 nightlies, or whatever nightly gpsd worked best for you.
I will start collecting gpsd files and posting them for your convenience soon!
V1.2CWM
--created CWM flashable for your convenience! performs the EXACT SAME
as the script, so if you've already run V1.2, no need to flash V1.2CWM.
But, it could be useful if you tend to flash nightlies all the time.
V1.2
--changed all file permissions to 0755 - not sure how reading .conf files
worked if there wasn't any read permission. gets me a faster lock after
applying the script.
V1.1
--fixed typo - "chmod shell" should have been "chgrp"
--removed \t, \n - was not being interpreted by shell correctly
V1
--initial release
If I helped you with your CM7 experience, please hit the Thanks Button
im about to try this
Dear all -
Script was updated to V1.2. I noticed that no read permissions were set to the .conf files; my thinking is there's no way Android could read those config files without read permissions, so they weren't even doing anything.
That said, the latest script now gives permission 0755 (rwxr-xr-x) to all files. After running the script now, I get a lock after first reboot in about 25 seconds.
You can download V1.2 and start from scratch, or just copy/paste the latest script contents into your GPSFix.sh. Or, run the following commands at a terminal (ADB or terminal emulator with root):
Code:
su
mount -o rw,remount /system
chmod 0755 /data/gps/secgps.conf
chmod 0755 /system/etc/gps.conf
chmod 0755 /system/bin/agpsd
mount -o ro,remount /system
reboot
Also, I noticed 31 downloads (and there were 20-some in the original post) but only a total of 3 Thanks.. I'm kind of addicted to the Thanks button and don't ask for donations otherwise, please push it if I help make a better CM7 experience for you
do they work with MIUI ?
chuotcontodung said:
do they work with MIUI ?
Click to expand...
Click to collapse
Should work with any CM7-based ROM; I hope someone else can confirm, though; I only run vanilla CM7 and occasionally Trigger Redux.
Any chance to make it CWM-based ?
It'd be so much nicer to drop the zip into a SD root and just run it after every nighty installation.
strictlyrude27 said:
Dear all -
Script was updated to V1.2. I noticed that no read permissions were set to the .conf files; my thinking is there's no way Android could read those config files without read permissions, so they weren't even doing anything.
That said, the latest script now gives permission 0755 (rwxr-xr-x) to all files. After running the script now, I get a lock after first reboot in about 25 seconds.
You can download V1.2 and start from scratch, or just copy/paste the latest script contents into your GPSFix.sh. Or, run the following commands at a terminal (ADB or terminal emulator with root):
Code:
mount -o rw,remount /system
chmod 0755 /data/gps/secgps.conf
chmod 0755 /system/etc/gps.conf
chmod 0755 /system/bin/agpsd
mount -o ro,remount /system
reboot
Also, I noticed 31 downloads (and there were 20-some in the original post) but only a total of 3 Thanks.. I'm kind of addicted to the Thanks button and don't ask for donations otherwise, please push it if I help make a better CM7 experience for you
Click to expand...
Click to collapse
You need to add "su" to the first line of your installation instructions
ferhanmm said:
You need to add "su" to the first line of your installation instructions
Click to expand...
Click to collapse
I assumed you would be entering the terminal with root. I'll update that in the OP though, thanks.
svladimir said:
Any chance to make it CWM-based ?
It'd be so much nicer to drop the zip into a SD root and just run it after every nighty installation.
Click to expand...
Click to collapse
I don't know how to make an update.zip, but perhaps this will be a good time to learn! I'm way better at shell scripting which is why I went this route. I'll see what I can do, hopefully I can have a CWM flashable soon.. if anyone else can help me I would much appreciate it.
That said, note that you can still open an adb shell in recovery mode, so you could run the script after you flash the nightly. I haven't tried that, but I will soon.
strictlyrude27 said:
I assumed you would be entering the terminal with root. I'll update that in the OP though, thanks.
Click to expand...
Click to collapse
Lol yea but I guarantee you that if you didn't add it more than 20 people would ask
It turns out making an update.zip isn't so hard after all testing it now, if it works out I'll upload to OP. I'll keep the original scripts and stuff for posterity's sake.
Great efforts, wow
This is just great piece of development, a sure and simple cure for the GPS and the CM 7+ roms.
Now that you have created this script, one so simple, there will be leages of Vibrant Users who will be able to take advantage of your generousity and put this puppy to work.
Kudos and once again, great work.... W.0.W.
I can confirm, with the AngryGPS I was able to lock in with fast lock in up to Accuracy of 20 feet, picked up 8 of the 12 satellites in view.
Thank you very, very much....
Dear all -
V1.2CWM released! As requested, a CWM flashable zip has been created. It does literally the exact same thing as V1.2 (copies over the GPS files to the right locations, sets 0755 permissions on all files). You don't need to flash if you've already installed V1.2, but I would keep the zip on hand for when you decide to flash a new nightly.
As always, the Thanks button lets me know I'm loved
I plan on starting a gpsd database, seems that while all gpsd's are created equal, some are more equal than others so you can mix and match the gpsd from a previous nightly, rather than referring to the supermassive black hole that is the official CM7 Nightly thread.
And finally, I must point out that I did NOT create these fixes. All the credit and praise belongs to jwleonhart and roffee. I just packaged up their work into an easy-to-install package, those guys did the real work! Please find their threads in the Credits section of my OP and hit the Thanks button!
My phone refuses to download these. Annoying.
^ try getting astro, go to preferences and allow internet downloads.
Also, chrome to phone is amazing
s15274n said:
^ try getting astro, go to preferences and allow internet downloads.
Also, chrome to phone is amazing
Click to expand...
Click to collapse
I already did the astro thing.
Turned it on and off several times.
And I used chrome to phone to send the link, with the same result.
I swtiched over to Opera, and that eventually agreed to download it.
OP updated. I now offer a no-gpsd version of the CWM flashable, in case you want to keep your gpsd or mix and match with other nightlys. I'll put up a link to a Dropbox to store GPS drivers from every nightly.
Ironically, the fix used to work for me 100% of the time, but not anymore. I'm going to start experimenting with new gpsd's from CM7 nightlies; please also let me know of your own results!
EDIT: I wasn't getting locks, or was getting and losing locks with my fix. Tried #72 gpsd and the nogpsd flash.. 0/8 birds after 5 minutes. Reflashed my own fix. TTFF [time to first fix] 17 seconds, 7/10 satellites, 150 ft accuracy. After 1 minute, 20 foot accuracy. Rebooted. 0/10 after 5 minutes.
I wish I understood you, GPS. I wish I understood you.
very nice.. i tried right now..
before this, its takes serveral minutes to get a lock.
after this patch.
first 30 secs, In View 12 satts.
1 min, get in USE 4 satts, 25 meters accuracy.
2 min, get 6 satts, 7 meters accuracy.
Very fast!
Thanks!
Nice!!! It will be much much easier now to get GPS working after nightlies. Awesome!
Sent from my SGH-T959 using XDA App
This works but great the first day but
GPS seems to not even lock in the next day.
Dattack said:
This works but great the first day but
GPS seems to not even lock in the next day.
Click to expand...
Click to collapse
tell me about it. i put the damn thing together and i'm in the same boat. It's really hit or miss for me.
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Flashing back to v7 now to test this out.
:::EDIT::::
So far it is failing. I get to step 5 and I am not able to remount. Permissions denied.
Also your rar file has tripped my antivirus software.
Please post a link to any original instructions.
:::EDIT::::
Yep still fails completely at step 5. The root is not carried over at all.
These are original instructions. I emailed Dan (djrbliss). Your anti-virus picked up on one of the exploits contained in the .rar. Once you download even if your anti-virus removes one of the files the rest works fine. This is how I was able to keep root. It does work.
adding the ro.kernel.qemu=1 and the adb commands were from djrbliss.. the rest is all me
Just try the super1click.
in adb type "adb shell id" what is the output?
*Should read "uid=0(root) gid=0(root)" <--- if anything but, go back to /data/local.prop and make sure it is still there.. I might be crazy but think it disappeared once or twice on me..
then the S1C or just the adb commands from OP should work..
(Your anti-virus removed psneuter from the exploit folder.. not needed anyways)
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
Click to expand...
Click to collapse
if you have any other issues beep me on IRC freenode #lgrevolution
Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Click to expand...
Click to collapse
Glad to hear.. I was close to starting over from scratch to make sure I didn't miss something.. lol
Hmm, didn't work for me will try again later
Sent from my VS910 4G using Tapatalk
Edit: Got it working, typo for me too it's qemu not qenmu lol
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
drt054 said:
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Click to expand...
Click to collapse
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
---------- Post added at 10:02 AM ---------- Previous post was at 09:55 AM ----------
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
.
I flashed back using the tot file, rooted then proceeded from there. Once I fixed my ignorant spelling issues everything worked great. Now that I have renamed the prop file and rebooted sound seems to be working.
My issue is now battery. The phone with no use is eating battery like a thunderbolt. It has been off charger for 2 hours with no use and its down to 84%.
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
Yes if you already have the V8 update in order to gain root you have to go back to V7 Stock firmware. If you are on GingerVolt 2.0 you have to flash the V7 Firmware to get back to LG-STock and Stock Recovery. The LG1click does NOT work on the V8 update so there is no CWM-Recovery, or GingerVolt at this time until MT figures out how once again..
Haxcid said:
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
SORRY!!!.. like I said didn't realize it until it happened, lost vibration and went to check my voicemail and no sound. But made that /data/local.prop into a .bak file, rebooted and was fixed. MT said has something to do with that entry in place the phone thinks it is a terminal emulator instead of a phone or something like that..lol So hopefully this is only temporary.
There may be a new root out soon.. not by me, like I said by someone much smarter than me may have found a way.
Click to expand...
Click to collapse
Worked like a charm DRT thanks so much!
Here is what I did:
1) Flashed MTs ZV7 Rooted Stock (RevoZV7GBStock.zip)
http://forum.xda-developers.com/showthread.php?t=1348637
2) Created the local.prop file, etc.
3) Used MTs All-in-One tool to flash Stock Recovery (Option 5)
http://forum.xda-developers.com/showthread.php?t=1348557
4) Downloaded and installed the ZV8 update OTA
5) Used ADB to push files per DRT instructions
6) Rebooted
7) Confirmed that I still have root using Root Checked Basic!
A little bit different than DRTs posted method but I wanted to avoid having to use LGNPST, so at least I can confirm that this alternate approach works as well!
drt054 said:
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Click to expand...
Click to collapse
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Nckmsn said:
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Click to expand...
Click to collapse
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
elreydotcom said:
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Haxcid said:
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Click to expand...
Click to collapse
Ive been unable to get the adb part to work. I can't get the adb command line to come up on my pc. Anyway, so I'm on v7 unrooted with no sound. I have change the name of the prop file and even removed it but my sound wont come back. Do i need to complete the whole process for the sound to come back?
If you are unrooted you can't create the file, you need to get rooted first. Use the all in one package to root.
Sent from my VS910 4G using xda premium
Once I was able to finsh the entire process, I managed to rename the prop file and all sound came back. success!
Thanks
Made a post in another thread but any word yet I how we get CWM recovery from rooted zv8?
edit: MT let me know that I needed to recreate the prop file, reboot, and then choose the root option in his new all in one package for ZV8...worked like a charm!
Sent from my VS910 4G using xda premium
This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning
So from now on we will be able to flash future updates through recovery without wiping everything?
So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.
That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.
Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.
me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...
That's great. thanks for share.
Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.
Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?
I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.
I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.
Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
several more freezes. obviously not depending on any special app..
erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie
Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip
This thread will be used for the discussion of packaging the ouya store into a flashable zip for easy install onto CM10, or hopefully any other custom rom that might not have the ouya store on it (or dare I say phone! untested, just a thought).
---------------------------------------------
Notes:
The good news up front we have both the ouya and play stores running on CM10!
I was working on this a few days ago and was running into what looked like issues with the data/system/packages.xml file giving out the right permissions. Toast message FC about ouya framework, and tv.ouya permissions to uid="10032".
I flashed back to OTA to try the exposed play store. After playing with that for a bit I decided to go back to work on this so we can have both the play store and the ouya store working on both OTA and CM10. I flashed over the ouya bits and set perms and was getting ready to look at the logcat expecting the same errors... but the launcher came right up, asked for my login and into the play menu I went!
What changed? I said I was working on permissions in the /data/system/package.xml... well I forgot to wipe data before flashing CM10. I think that was the secret, it must have skipped some step that was causing the error as something it was looking for was already there.
In any event the store and framework are working... mostly. I am still having issues getting into the "discover" menu as I get a toast message that says something about "attempted read from closed stream". in logcat it looks like "error checking for update". so I think it may be that I'm working on old apk's from an old download.
There is also an issue with the controller mapping, home seems not to work and while testing shadowgun the x/y axis on the right thumb stick was reversed. I think I remember someone saying something about that.
In the end it turned out to be about the same process as getting google music to work on stock OTA. basically grab the framework and launcher apks and put them in system. (At least up to this point! lol) The Idea will be to use this to build a complete install zip without the need to have a data partition from OTA. Who knows what other issues this might cause as usually its not a good idea to keep data from different roms.
------------------------------------------------------
So manual step...
!!!This is for Dev purposes only, this does not work 100% yet!!!
If you want to give it a try and/or help solve an issue or 2, by all means continue!
-1. Make sure you have access to OUYA store on an OTA based rom.
0. Flash CM10 via cwm !!!DO NOT WIPE DATA!!!
http://forum.xda-developers.com/showthread.php?t=2348548
instructions on flashing the google apps are also there to get play store working.
1. I used the deodexed files from IncognitoMan's stock plus rom. Basically from /system/app/ grab anything that starts with "ouya" at this point I'm not sure all are need but this is what I did to get to where I'm at now... I will update as I test further on what all exactly is needed or not.
link to rom http://forum.xda-developers.com/showthread.php?t=2347214
a. ouya-framework.apk
b. OUYAKeyboard.apk
c. OUYALauncher.apk
d. OUYAOOBE.apk
e. OUYAWallpaper.apk
For each of these files copy over to sdcard
adb push ouya-framework.apk /sdcard/.
adb push OUYAKeyboard.apk /sdcard/.
adb push OUYALauncher.apk /sdcard/.
adb push OUYAOOBE.apk /sdcard/.
adb push OUYAWallpaper.apk /sdcard/.
Click to expand...
Click to collapse
2. Remount system in rw
adb shell
su
mount -o rw,remount /system
Click to expand...
Click to collapse
3. Copy over to /system/app/
cat /sdcard/ouya-framework.apk > /system/app/ouya-framework.apk
cat /sdcard/OUYAKeyboard.apk > /system/app/OUYAKeyboard.apk
cat /sdcard/OUYALauncher.apk > /system/app/OUYALauncher.apk
cat /sdcard/OUYAOOBE.apk > /system/app/OUYAOOBE.apk
cat /sdcard/OUYAWallpaper.apk > /system/app/OUYAWallpaper.apk
Click to expand...
Click to collapse
4. Set permissions.
chmod 644 /system/app/ouya-framework.apk
chmod 644 /system/app/OUYAKeyboard.apk
chmod 644 /system/app/OUYALauncher.apk
chmod 644 /system/app/OUYAOOBE.apk
chmod 644 /system/app/OUYAWallpaper.apk
Click to expand...
Click to collapse
5. Reboot.
reboot
Click to expand...
Click to collapse
6. Launch the "ouya launcher" from the app menu and log in.
All games you had from the OTA rom should be there.
Again issues:
Cant get into "Discover" menu in ouya launcher. - working on this now as this is obviously the deal breaker for most.
Controller keymapping. -biggest issue with this is home button mapping! in android settings the ouyaKeyboard is grayed out... ouya framework issue.
Some games show a ouya-framework fc 2-3 times as the game loads... but once the game is up its fine.
Some games might not like the high dpi.
Some games just wont open (paid?)... - thinking this might be related to the Discover menu issue.
irc, FreeNode/#ouya-dev
Thanks; khanning88 for CM10, IncognitoMan for deodexed OTA.
So on with the work then.
here is a pastebin of the logcat while clicking the discovery menu item. Looks like it gets the menu, kind of interesting how they are sending the list.
http://pastebin.com/wHPyvskN
the logcat from clicking the ouyaKeyboard setting in language/input
D/InputMethodPreference( 642): IME's Settings Activity Not Found: android.content.ActivityNotFoundException: Unable to find explicit activity class {tv.ouya.console.ime.keyboard/com.example.android.softkeyboard.ImePreferences}; have you declared this activity in your AndroidManifest.xml?
I/ActivityManager( 325): START {act=android.intent.action.MAIN cmp=tv.ouya.console.ime.keyboard/com.example.android.softkeyboard.ImePreferences u=0} from pid 642
Click to expand...
Click to collapse
^thinking this might be an issue with matching up activity and class in /data/system/package.xml... might have different userid tags?
Hey after doing this does the Ouya keyboard work?
professorpoptart said:
So on with the work then.
here is a pastebin of the logcat while clicking the discovery menu item. Looks like it gets the menu, kind of interesting how they are sending the list.
http://pastebin.com/wHPyvskN
the logcat from clicking the ouyaKeyboard setting in language/input
^thinking this might be an issue with matching up activity and class in /data/system/package.xml... might have different userid tags?
Click to expand...
Click to collapse
That looks like its just missing a preferences add-on apk or it needs an activity from Settings.apk that's missing.
So why the sudden halt? Everyone give up, get it working or lost interest?
I'd love to get my CM11 into a Hybrid with Ouya app's.