Related
This is the Development and Downloads Thread for the ION Build of Android for our Kaisers.
Any Non Development Questions will be Ignored in this Thread
Only Development related content will be posted here.
All non development related questions need to be directed to this thread: Questions and Troubleshooting
First Thanks to Vilord for the work, and thanks to whoever he thanked (Martin, Okibi, etc etc)
Working:
Data Connection
Google Services
Call Waiting
GPU Graphics Acceleration
Work In Progress: (not by me)
Camera
GPS
WIFI
Instructions: (adapted from Vilord's vogue post)
For some people ROM and Radio make a difference in whether or not certain aspects of the phone work. I am using Shifu's 6.1 V08 WWE Naked ROM with Radio 1.65.24.36
Before I boot haret, while still in WinMo, I always complete 1 call, so I call my voice mail, then once it connects I hang up. I'm not sure if completing a call like this actually helps, but I do it anyway. If you are not able to make calls, try this step.
Step 1: Download the files:
-Download ExtractToRootOfSDCard.zip below and extract *everything* to the root of your SD card
-Download system-ion.img from below, rename it to system.img and put it in the root of your SD card
-Download zImage from below and put it in the root of your SD card
-Download the newest initrd.gz file, extract it to your SDCard and overwrite the initrd.gz file that was in the ExtractToRootOfSDCard.zip
Step 2: Run it!
-Run Haret, and it should boot into android.
Reports have shown that starting over with the fresh data file (data.gz) instead of using your existing data.img produces better results.
Be aware of the fact that it will take a long time to extract the data.img file from the data.gz archive during your first boot. It took about 5 minutes for me.
At first your orientation may not return to portrait mode after closing the keyboard, if this happens fix it by:
Going to Settings > Sound & Display > Under Display Settings UNCHECK "Orientation"
Download the system-ion.img file (then rename it to system.img put it in the root of your SD card)
Download the kernel aka zImage (then put it in the root of your SD card)
Download the latest initrd.gz file from Vilord's google code page
reserved for updates
reserved for updates
Thanks for the thread, I'll update this post later with my ION system.img that has the original key layout along with bash and busybox tools added. Other than that, it's the current one you posted.
For anyone new to developing Android, here's what to do (thanks to everyone for these scripts):
system.img
Code:
mkdir stock-system && mkdir temp
sudo mount -o loop system.img stock-system
genext2fs -d stock-system -b 300000 -a system.ext2
sudo mount -o loop system.ext2 temp/
[B]---Make Changes---[/B]
sudo mkfs.cramfs temp/ system.1.5.img
I've attached genext2fs as well (thanks dzo)
initrd.gz
Extract--
Code:
gunzip initrd.gz && cpio -i < initrd.cpio
Compress-- (within directory)
Code:
find ./ | cpio -H newc -o | gzip > ../myinitrd.gz
data.gz
Is simply a gzipped ext2 img file.
We've been putting busybox and bash into the initrd... since it doesn't take up much space it allows more customization of the initrd environment...
Could you let me know what of my vogue stuff doesn't work on kaiser and what you need to change to make it work? It may be easy to adapt the vogue stuff to be compatible with both.
Installed ok. With a couple notes:
During first boot, got stuck at the terminal screen with nothing happening after the Data.img was extracted.
Rebooted, booted fine.
Noticed that 320x480 looks retarded as a screen resolution for Kaiser
Reset resolution to 336x448 and rebooted.
Crashed in terminal with Oops #11 (seriously, thats what it said)
Reset resolution to 320x428 looks fine. I'll probably try a few higher resolutions to get more screen real-estate.
Also, I was initially not able to install items from the Market. They download fine, but when the 'install' starts, it throws an error. This may have to do with attempting to download two things at one time. I later retried the download and both items installed fine.
In initrd.gz/init file:
When it boots, it complains of "no telephony database. Will check for Android apn on next boot:"
Code:
SQLITE3="/bin/sqlite3"
[B]DB="/data/data/com.android.providers.telephony/databases/telephony.db"[/B]
if [ -e $DB ] ; then
if [ "`$SQLITE3 $DB 'SELECT numeric FROM carriers;' | grep 310995`" != "310995" ] ; then
echo Creating android apn
"$SQLITE3" "$DB" "INSERT INTO carriers VALUES(NULL, 'Android' , '310995' , '310' , '995' , 'internet' , '*' , '*' , '*' , NULL, NULL, NULL, NULL, 'null' , 'default' , 1);"
fi
else
[B] echo No telephony database. Will check for android apn on next reboot[/B]
fi
After that it says "chmod: 1000 no such file or directory."
Code:
if [ -d /data/app ] ; then
if [ -d /sdcard/AndroidApps ] ; then
echo Copying Applications
cp /sdcard/AndroidApps/* /data/app
[B] chown 1000 1000 /data/app/*[/B]
fi
fi
Example of Questions being asked in wrong thread
enatefox said:
...all the other stuff you said, then...
How can I debug bootup?
Click to expand...
Click to collapse
Please refer questions like this to the "Questions and Troubleshooting Thread"
enatefox said:
In initrd.gz/init file:
When it boots, it complains of "no telephony database. Will check for Android apn on next boot:"
Code:
SQLITE3="/bin/sqlite3"
[B]DB="/data/data/com.android.providers.telephony/databases/telephony.db"[/B]
if [ -e $DB ] ; then
if [ "`$SQLITE3 $DB 'SELECT numeric FROM carriers;' | grep 310995`" != "310995" ] ; then
echo Creating android apn
"$SQLITE3" "$DB" "INSERT INTO carriers VALUES(NULL, 'Android' , '310995' , '310' , '995' , 'internet' , '*' , '*' , '*' , NULL, NULL, NULL, NULL, 'null' , 'default' , 1);"
fi
else
[B] echo No telephony database. Will check for android apn on next reboot[/B]
fi
After that it says "chmod: 1000 no such file or directory."
Code:
if [ -d /data/app ] ; then
if [ -d /sdcard/AndroidApps ] ; then
echo Copying Applications
cp /sdcard/AndroidApps/* /data/app
[B] chown 1000 1000 /data/app/*[/B]
fi
fi
Click to expand...
Click to collapse
The chown line has been fixed and will be uploaded soon.
The no telephony database line should go away after first bootup. Does it not?
MBurris: the setupmodem.sh script you have must be an older version as I had already removed the lines you mentioned. Anything else?
now I understand, you want the stuff added back *in*
It is done, added to ppp-on-dialer where it belongs.
Also completely fixed the data.gz stuff by eliminating data.gz. Now the initrd will create a new data.img if there isn't one there.
support for data.img backups from bootup as well, just create a /sdcard/backup folder
@Vilord: Have you added the new stuff into your latest initrd.gz (on google download)?
Edit: After I used the latest files from google download all the files on my SD card are totally gone :s. I booted Android Original ION hero build, and back in Windows all files are gone on my SD card :s
Hi there, dunno if this belongs to the ION question and answer thread, but could anyone be able to make one of the roms with this:
http://android-unleashed.com/2009/06/htc-hero-theme-1-2-for-the-android-g1.html
Cause i think this theme would be very cool on this ion builds..
Still having issues with the phone not waking up.
Using pm.sleepmode=1, otherwise, as you know, the battery life lasts about 2 hours.
KAIS110
radem205 said:
@Vilord: Have you added the new stuff into your latest initrd.gz (on google download)?
Edit: After I used the latest files from google download all the files on my SD card are totally gone :s. I booted Android Original ION hero build, and back in Windows all files are gone on my SD card :s
Click to expand...
Click to collapse
I think this is due to corruption on the SD card, coupled with the creation of a large file (data.img). I'll post an updated initrd in an hour that has filesystem checking on the SD card before it tries to do anything else, that should avoid wiping out people's stuff.
EDIT: sorry, hit go advanced and post by accident and double posted
JeckyllHavok said:
Hi there, dunno if this belongs to the ION question and answer thread, but could anyone be able to make one of the roms with this:
http://android-unleashed.com/2009/06/htc-hero-theme-1-2-for-the-android-g1.html
Cause i think this theme would be very cool on this ion builds..
Click to expand...
Click to collapse
I'm with you. 3 threads and no real response at getting themes. I tried it myself by manually overwriting the apps, data files and framework as the update would but it hangs at boot or crashes mercilessly once the desktop appears beyond nonfunctional.
mburris, that's what prompted me to post the question about how to debug bootup. This is every bit a development issue. Those are signed apps that override the ION ones and they should "just work" so what's wrong and who's at fault . Plus it's hard for us to really troubleshoot users' issues with modems and startup without something better than dmesg. Then users can attach a log to their posts for us to look at.
Posted to the vogue people:
Okay the initrd.gz on google code has been updated yet again.
This time is a major update with repaired bell SMS (thank you Martin), new libgps (thank you Steven), and statically linked filesystem checks (that was me).
On my phone, it took about a minute to create a new data.img (*don't use data.gz!!!*)
You'll want to use martin's new zImage from here
MBurris, does it just work now, or is there still some tweaking for kaiser?
---
For themeing, it is *very* difficult to theme an ion build. Much easier to theme the opensource builds, but they aren't as fast.
For themeing, it is *very* difficult to theme an ion build. Much easier to theme the opensource builds, but they aren't as fast.
Click to expand...
Click to collapse
How difficult are we talking? Mssmision had two ION builds with Hero. What's involved?
Latest initrd and zImage:
336x448 resolution works again! SOOO much nicer than the non-4:3 included with the install package you posted...
Noticed the Blue LED blinks now... Something good coming?
Data, Market, Txt, calls, call-waiting, all work.
GoogleTalk works again,
runs SOOOO fast....
Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?
So 2 days ago guys from 4pda.ru ported android 2.2 on GT540, it is installed on sd card and you can choose between 2.1 and 2.2.
Here is youtube video:
And here is link on thread on 4pda:
PDA
so why would I need to switch between 2.1 and 2.2? I guess this is just a preliminary POC and a custom rom is now in the works.
can't wait! great job russians!
tong.po said:
so why would I need to switch between 2.1 and 2.2?
Click to expand...
Click to collapse
Maybe cos 2.2 isn't supporting FM/Camera/BT right now and is booted from SD.
Thank god for the Russians! And great job finding this.
Sent from my GT540 using XDA App
woo!
could someone make a tutorial?
as the translated russian is'nt easy.
flyboyovyick said:
woo!
could someone make a tutorial?
as the translated russian is'nt easy.
Click to expand...
Click to collapse
Lol 1+
Sent from my GT540 using XDA App
The Rom is not even released yet, nor it will be released soon. Its in I wouldnt even call it Alpha version yet.
You can find some info there:
http://twitter.com/#!/ZduneX25/status/6643977159708672
__________
Written with Tapatalk on GT540
gonna make a video and read tut of it
and some video of it working ofcourse!
ported only basic functions, engineer version posted atm... No final version...
Direct link to some work and explanation in russian is here: http://4pda.ru/forum/index.php?showtopic=200838 But it is stated as version for developers and professionals only, because it is lacks some functions, half working wi-fi, some problems with bluetooth and it's still in test mode. You will need to format your sd card, make your phone able to load in fastboot mode and one package for dual booting from above link.
You will need following apllications:
Dual boot loader from here: http://narod.ru/disk/122844001/ankuch2.2-oss.img.html
Copy of /system folder: http://narod.ru/disk/41926001/ankuch2.2.tar.html
1. Prepare your sd card
type of disk MBR;
part0/primary - fat16 - sdcard - 128MB+. No reason to create more;
part1/primary - ext2 - system - 256MB+, you can put more if you will put some applications in /system/app;
part2/primary - ext2 - data - 256MB+.
I recommend it to partition in 10/10/80.
If you got a big card and use phone to view video, you can make first partition bigger.
2. After SD card prepare, you will need to load and copy content of /system folder from ankuch2.2.rar archive
Making final phase in 2.1:
1. Mount /system in mode r/w (you can mount it, for example, from RootExplorer - select /system and press button mount r/w)
2. adb shell
3. su
4. mkdir /system/s8
5. mount -t ext2 /dev/block/mmcblk0p2 /system/s8
6. cd /system/s8
7. busybox tar -x -f /data/ankuch2.2.tar
Loading 2.2:
Enter fastboot mode
We load 2.2 - fastboot boot ankuch2.2.img
No loading animation yet, you will need to wait until will be filled content of /data folder
First load can take a long time, you can control it thru adb shell logcat.
adb, btw, I did in first time and from root it loads.
Sorry for mine english Fast translation
Problems and some solutions to avoid them:
1. How to put data transfer?
adb shell
stop ril-daemon
start ril-daemon
-- Can be some problems with APN not loading from SIM card, so you will need to put configuration manually.
-- Connection always will be like EDGE, even if really you getting HSDPA
2. How to get rid of lag in transitions?
Try this:
Spare Parts -> Window animations -> Off
Spare Parts -> Transition animations -> Off
Once I got bugged rild, loaded cpu to 100% and almost halted all apps, thats why from link in russian forum you will see some pics of processes.
You can turn it on:
Dev Tools -> Development Settings -> Show running processes
Changed those options too:
Dev Tools -> Development Settings -> Disable compatibility mode (requires to reboot device)
After this author does not get any hangs.
3. How to connect to Wi-Fi
It is required to copy from your 2.1 file wpa_supplicant.conf to /data/misc/wifi (in this file it is saved all your information about connections)
Change permisions from file chmod 777 /data/misc/wifi/wpa_supplicant.conf (author did not tested more secure permisions) or reboot device
rest in here -> Settings->Wireless & network->Wi-Fi (turn on Wi-Fi)
----- Announcements -----
Closed in favour of this thread.
As noted in the poll, interest is high enough in a union filesystem that it will be the next thing investigated. Unfortunately, anybody who wants to move from any version 1.x or earlier of this script will probably need to re-install everything for version 2.x, as the way the target filesystem is designed is going to change dramatically. Sorry.
There's a typo that jdkramar found, but I expect that most of you won't hit it (unless you've modified your /etc/sudoers), and those that will know enough to fix the script.
----- Your regularly scheduled post below. -----
For those users who have requested a full Linux on their Android device, I now present a relatively easily upgradable Ubuntu on the Motorola Atrix. It's not perfect, but it's surprisingly good.
There are a number of problems we have with the webtop environment that we would like to address in order to have "proper" Ubuntu, including (additional explanation below about each of these points):
The restrictiveness of the environment Motorola's set up (easy to bypass).
A lack of disk space to do anything (only having ~80 MB free really hurts).
An unwillingness to create a third Linux-based environment.
A non-functional apt/aptitude (easy to fix).
Note: This is different than the "webtop over HDMI sans dock" effort. If you're looking for that, please look at this other thread instead. Although unrelated, they shouldn't conflict with each other.
Caveats:
You will be hacking your device. The base script that modifies your device has been reasonably well tested and operates with a decent level of paranoia, so it is highly unlikely that the script will break anything. However, any software you install after you have access to a full Ubuntu presents a very real chance that you will either soft-brick your device or get it into an infinite reboot loop, particularly if you don't know what you're doing. Having a decent knowledge of Unix/Linux is recommended if you wish to proceed. You take full responsibility for what may happen to your device if you execute this script.
You'll need a rooted Atrix in order to do this*, although I doubt anyone's surprised about that. The attached setup script takes care of the steps in post #4, but you should note a few things:
Before you execute the script:
In response to the request that threads indicate whether or not this will work on any Motorola Atrix, it should. If you'd like verification, send me the output of "/usr/bin/dpkg-query -l" on your Atrix's unmodified Ubuntu, and I can double-check. So far, this is verified to work on:
AT&T (me! )
Bell
The script will create a 1 GB filesystem file in /data, so you'll need to have at least that much free space there.
Before running the install script, you'll need to have seven or less apps in the Media area. You can check this by going to Settings → Applications → Manage applications, then checking the Media area tab. The number of apps there will need to be seven or less. If you have more than that, temporarily uninstall apps or move them back to the phone (you can move them back after the script runs and reboots).
While you execute the script:
When the script asks question, it offers reasonably "sane" options by default (although it does try to be safe).
Resetting a filesystem file means that it will use the file that's already there, but set it back to match your original /osh partition. It's generally quite a bit faster than deleting it and recreating it, but deleting it is sometimes the right decision (like if you want to change its size).
The script asks about your MAC (mandatory access control) files because it can't be sure that you haven't altered your original files to your taste. If you have no idea what that sentence just said, pick either the very permissive or somewhat permissive MAC configuration files (the former should cause you fewer headaches).
If you haven't altered your AWN configuration (the tray at the bottom), I suggest you install the modified app launcher configuration (which is the default). If you have altered the configuration, the script won't ask, assuming that you'd like to keep your current one.
Since the setup script downloads Ubuntu packages on the fly (it made more sense than trying to have a giant archive with all of the packages embedded in it), the quality of your connection may result in the script dying partway through. If this happens, you should just be able to restart the script; it'll start again from the beginning, but nothing bad should happen as a result. If enough people report problems with downloading packages, I'll look into a workaround.
After you execute the script:
I've seen a couple of instances where on the first reboot to the alternate /osh partition where MotoBlur thinks that the SIM card has changed. Another reboot fixes this.
For those users who have used a previous version of the script, an upgrade script(s) are included to bring you up to the current level of what's automated.
For those users who have used a previous version of the script and made changes after that, the upgrade script(s) should be able to handle those changes gracefully.
If you want to uninstall:
Using adb with root access:
adb shell
su
cd /system/bin
mv mountosh mountosh.new
mv mountosh.orig mountosh
cd /data
rm ubuntu.disk
cd /home/adas/.gconf/apps/avant-window-manager
rm -r window_navigator
reboot
Once installation is complete, you can start playing with synaptic to install packages. You may need to be careful upgrading any of the -mot/~mot versioned packages, as that can break functionality. I'm still compiling a list of which packages can be upgraded versus which can be left alone (listed below).
Here's a brief runthrough of the type of operations you can do afterwards. Upon rebooting, the webtop screen now looks like this (note the altered set of icons in the tray):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Running synaptic brings up a list of available packages:
If we're looking for a decent image viewer, eog should do the trick:
Once we install it, Nautilus (the file manager) now has an interesting option in the menu for pictures, Open with "Image Viewer":
Selecting that brings up what you would expect (moved off to the side so that it doesn't take up the entire desktop):
I haven't yet tested upgrading to Ubuntu 9.10 yet (let alone Ubuntu 10.x), but everything else looks to work fine, with the usual caveats. Further updates to come as they're available!
Changelog:
1.0.6: "By default, Wget will assume a value of 10 seconds." my foot!
1.0.5: More fixes:
Having a space in the directory structure should no longer be disruptive to the script's behaviour.
Questions are now case-insensitive.
More tweaks to the somewhat permissive TOMOYO configuration files.
If the LXTerminal binary has been deleted (as appears to be the case on Bell), it is now re-installed.
The built-in package tester is now more resilient. It supports 1.4.26 and 1.4.52 properly.
The script now asks whether the dock should just be blown away with the replacement, rather than trying to make assumptions.
1.0.4: Quite a few fixes:
Rename upgrade scripts, so that people get less confused (hopefully!).
Tweak the check for whether it's already running from the filesystem file, since the earlier check didn't actually work (doh!).
/osh/data doesn't exist by default, so have the script stop assuming that.
Tweak the pulseaudio re-install so that it's a bit more reliable.
The expected list of packages to manipulate doesn't work for 4.1.26. Set it to the 4.1.26 numbers for now, and re-factor for 4.1.52 with the next revision.
Reroute /bin/ps' stderr to /dev/null so that it doesn't pollute stdout.
The set of unmount instructions at the end need to be split up, since you can rightfully get to the end while skipping some of the mount instructions.
Prior to attempting to alter /system, ensure that it's mounted read/write.
1.0.3: Not everybody runs batch files from the command line, so add a "pause" at the end so that users can see what happened.
1.0.2: Apparently, relying on the score that aptitude returns as the check for whether or not it's okay to auto-fix things is too unreliable. So, instead, opt for the (somewhat riskier, but should be reasonable) check of the number of packages to remove/install/upgrade/downgrade. The check can be made package-specific if need be, but I'd rather have a script that I can re-use later for other upgrades if I need it.
1.0.1: If the package management auto-fix doesn't go through, it's not likely that the script will be able to install gksu or synaptic either, so those steps need to be fixed.
1.0: The "very permissive" MAC option was broken. That's now been fixed, along with completing the automation of the entire process.
0.7.2: Added a check for having a free loop device, and also re-added a "very permissive" MAC option.
0.7.1: Removing /sbin/tomoyo-init appears to cause the X environment not to load at all, so disallow that option for now.
0.7: In addition to making it slightly more user-friendly (by adding questions for when the script isn't sure how to handle a situation), it now handles through to the initial dpkg installation.
0.5.2: Dump rsync's output to /tmp/rsync.out since it takes a really long time, allowing for users to tail the output if they know how. Also, run adb kill-server at the end of the script so that the adb daemon doesn't continue to run (which makes it really annoying to try and delete the directory).
0.5.1: 0.5 had a bug where it tried to check for a return from psneuter, which kills the adb connection (so no return value could be obtained). Instead, use whoami to verify whether or not psneuter succeeded in running.
0.5: The attached script should handle up through to the rsync phase automatically. There's a considerable amount of error checking, so it should be safe to use (I've uploaded a version of the script that should take you as far as the mountosh swapping, which means that you'll now be using a different Ubuntu partition than the default).
* This is a technicality, since the script hacks your device to be able to run commands over ADB as root.
----- Donation notes -----
If you want to donate, rather than to me, why not donate to the Japanese earthquake/tsunami relief effort instead? Here are a couple of (non-attributed) pointers if you don't know where else to look:
International Federation of Red Cross and Red Crescent Societies: no minimum; USD, CHF, EUR; Visa/MC
American Red Cross: $10 minimum (ouch); USD; Visa/MC/AmEx/Discover/Amazon
Canadian Red Cross: no minimum (?); CAD; Visa/MC/AmEx/PayPal
In regards to the above list, a bit of explanation:
The restrictiveness of the environment Motorola's set up (easy to bypass).
As shown in the above steps, renaming and/or removing /sbin/tomoyo-init is all it takes to disable TOMOYO Linux. Leaving it in place isn't necessarily a bad idea, since it means that any of the standard entry points into an Atrix are reasonably locked down. The TOMOYO configuration file that I'll shortly be attaching leaves certain executables completely unlocked (those that need to be able to run anything), but finding out what's hitting up against the limits is a simple matter of setting everything to run_level 2 and checking dmesg.
A lack of disk space to do anything (only having ~80 MB free really hurts).
As I note above, 1 GB isn't much either. On the other hand, what I'm going to look into when I have that mythical thing called free time is to use my internal contacts to get a copy of the kernel source code and then see if I can build myself a FUSE module. At that point, I should be able to pull off a union mount, which should help dramatically.
We haven't figured out how to repartition the Atrix's partition scheme, so we don't have much flexibility on making the existing partition larger. Creating a filesystem file in the Internal Storage would be nice, but a) that partition (p18) isn't available when mountosh runs, and b) it'd make it difficult, if not impossible, to cleanly USB mount the partition. Creating a partition on the SD card would be nice, but a) mmcblk1 isn't available when mountosh runs either, and b) there would be similar constraints if a user ever wanted to pull the SD card.
An unwillingness to create a third Linux-based environment.
I respect what the people who are trying to create a "clean" chrooted environment are trying to do, but it feels to me that there's the whole "throwing the baby out with the bathwater" aspect here, since there really isn't that much more to do beyond what Motorola's provided. Besides of which, some of what Motorola has done with their environment isn't possible to duplicate without taking the files (like the aiw (Android In Window) package). So I would prefer to take the approach of taking the chains off the existing system.
A non-functional apt/aptitude (easy to fix).
Not much to say here, right?
The script builds a larger disk using /data as its home. The primary advantage is that we have access to it at the right point during boot. The primary disadvantage is that we don't have anywhere as much as we'd like to have (since /data is 2 GB total). But, you work with what you've got!
Known package issues:
Be careful upgrading any of the -mot/~mot packages, as that can break functionality. I'm still compiling a list of which packages can be upgraded versus which can be left alone.
Can be upgraded with loss of functionality:
libnautilus-extension1-1:2.26.2-0ubuntu1-mot1
nautilus-1:2.26.2-0ubuntu1-mot1
nautilus-data-1:2.26.2-0ubuntu1-mot1
Upgrading these packages plus at least one additional package I've not yet fully identified breaks viewing mountable storage and the ability to unmount it.
xserver-xorg-core-2:1.6.0-0ubuntu14
Using the stock xserver-xorg-core 2:1.6.0-0ubuntu14 that's already installed without recovering /usr/bin/Xorg appears to lead to a loss of the status bar at the top. This particular issue is now handled by the script.
Cannot be upgraded:
gtk2-engines-1:2.18.1-0ubuntu1~mot1
This breaks aiw (Android In Window) so that there's no frame around the window and it can no longer be manipulated in any way.
xscreensaver-5.10-6-motorola1?
xscreensaver-data-5.10-6-motorola1?
xscreensaver-data-extra-5.10-6-motorola1?
This will likely break displaying aiw (Android In Window) as the unlocking mechanism for the screensaver. Still needs to be tested.
Archived notes:
The below steps are performed by the script in the first post, but in case you really wanted to know what's going on behind the scenes....
----- The setup script takes care of steps starting here. -----
From here on until noted otherwise, all commands are assumed to be run as root (so you either are root, or you're calling every command via sudo).
First, we should make sure that there's enough free space on the device:
/bin/df -h /data
There should be at least 1.0G under the Used column. If not, you won't have enough to create a decent disk. If so, then you can keep going:
/bin/dd if=/dev/zero of=/data/ubuntu.disk bs=1024 count=1048576
/sbin/losetup /dev/block/loop7 /data/ubuntu.disk
/sbin/mkfs -t ext3 -m 1 -b 2048 /dev/block/loop7
mkdir /tmp/osh
/bin/mount -t ext3 /dev/block/loop7 /tmp/osh
At this point, we've created a 1 GB disk file (1,024×1,024=1,048,576), formatted it as ext3, and mounted it in /tmp/osh. The next step is that we need to grab a copy of rsync so that we can perform our copy. I'll assume that rync is in /mnt/sdcard-ext for now:
mkdir /tmp/deb
/usr/bin/dpkg-deb -x /mnt/sdcard-ext/rsync* /tmp/deb
/tmp/deb/usr/bin/rsync -avx /osh/ /tmp/osh/
And now we have a duplicate of our /osh partition, but with more space this time (1 GB instead of 756 MB, which isn't great, but is a hell of a lot better). And, we know how to intercept the point in init.rc where /osh is mounted so that we can redirect it. Put the following into a file named mountosh.new, then copy it to /mnt/sdcard-ext. Here's the file:
Code:
#!/system/bin/sh
# Run mountosh.orig
/system/bin/mountosh.orig "[email protected]"
# Then, mount the filesystem file over the existing /osh
# partition.
/sbin/losetup /dev/block/loop7 /data/ubuntu.disk
/system/bin/mount -t ext3 /dev/block/loop7 /osh
After that:
mv /system/bin/mountosh /system/bin/mountosh.orig
cp /mnt/sdcard-ext/mountosh.new /system/bin/mountosh
chmod 0755 /system/bin/mountosh
chown 0 /system/bin/mountosh
chgrp 2000 /system/bin/mountosh
You can now reboot your device, and you should now boot into the new partition we've just created.
----- The 0.5 version of the setup script performs up through here. -----
Here, an interesting question pops up: do you want mandatory access control (MAC) in place? In my case, I don't have a problem with it, so I can provide updated TOMOYO configuration files that reflect that. If you would prefer to disable it completely, run the following commands:
rm osh/etc/tomoyo/exception_policy.conf
touch osh/etc/tomoyo/exception_policy.conf
rm osh/etc/tomoyo/domain_policy.conf
touch osh/etc/tomoyo/domain_policy.conf
and then reboot your device again. This configures TOMOYO so that it monitors nothing.
Next, we go through and install a series of packages which are either loaded in a broken state (because Motorola force-installed conflicting packages afterward) or packages which are expected to be present. Some of these packages have specific paths listed afterward; if there are, then those files need to be backed up before package reinstallation, then restored afterward. This is important.
coreutils
cpio
dbus
/etc/init.d/dbus
dbus-x11
/etc/X11/Xsession.d/75dbus_dbus-launch
dhcp3-client
findutils
gpgv
pulseaudio
/etc/pulse/daemon.conf
/etc/pulse/default.pa
udev
/etc/init.d/udev
xserver-xorg-core
/usr/bin/Xorg
You'll need to install each package with:
dpkg -i --root=/osh --force-overwrite <package>
At this point, we can now update the list of APT sources so that we can start querying the public Ubuntu depots. Edit your /etc/apt/sources.list to have these entries:
Code:
deb http://ports.ubuntu.com jaunty main universe multiverse restricted
deb http://ports.ubuntu.com jaunty-security main universe multiverse restricted
deb http://ports.ubuntu.com jaunty-updates main universe multiverse restricted
I would also recommend that you add this line to the bottom of your /etc/apt/apt.conf.d/05aptitude file, since the reality of the situation is that we still don't have much space (it'll turn off auto-installing packages that aren't necessary but are recommended):
Code:
Apt::Install-Recommends "false";
At this point, you should be able to run the following with no problems:
apt-get update
----- The 0.7 version of the setup script performs up through here. -----
If this succeeds, we can move on to running aptitude:
aptitude
It will complain that a number of package installations are broken. This is expected, as that's how Motorola built out the distribution. The current script executes the "default" solution, which at the time of writing is four uninstallations, one downgrade, and ten installs. Also make sure that no "unnecessary" packages are uninstalled, since some of them are actually necessary.
We can then install gksu and aptitude so that we have graphical access to the package repositories from aptitude.
----- The 1.0 version of the setup script performs up through here. -----
You my friend are incredibly good. This is insane
Edit: removed huge quote...
Might be a good idea to not quote the entire massive post.
Looking forward to seeing where this goes... How well does it run?
This is great. Can't wait to try it monday. Keep up the good work.
Sent from my MB860 using XDA Premium App
how does this perform vs the included webtop mode?
CC Lemon said:
Looking forward to seeing where this goes... How well does it run?
Click to expand...
Click to collapse
lasersocks said:
how does this perform vs the included webtop mode?
Click to expand...
Click to collapse
It is the included webtop mode - it's just a matter of pulling off some of the restrictions that Motorola put on it. I should probably tweak it just a bit more to where I'm happy with it, and then I'll be able to start making suggestions on what to install. One of the things that people would probably want most is synaptic (graphical package manager), for example, and I should just have a script that installs it for people.
if you get this working, can you make a video please? would be nice to see how it is.
pure genius
can u post a video about your work ? =)
Very good work! You should join the irc sometime.
freenode
#moto-atrix
Now with more scripting!
I've added a version 0.5 of a setup script that automates some of what happens (I've denoted how far in the process it performs right now). It should print out a user-friendly version of what it's doing, in addition to what it's failing on if it fails. Appropriate notes added in the first post as well.
Sogarth said:
Now with more scripting!
I've added a version 0.5 of a setup script that automates some of what happens (I've denoted how far in the process it performs right now). It should print out a user-friendly version of what it's doing, in addition to what it's failing on if it fails. Appropriate notes added in the first post as well.
Click to expand...
Click to collapse
I'll try again. Got up until mounting new partition. Created mountosh.new copied over to phone rebooted. Didn't mount. Didn't have anything in /sbin dir. Like losetup.
Back to .sbf now. Going to try script and give it another go.
I cant wait for my Atrix I'm getting more and more excited every day seeing whats happening here
Thanks a lot for this, especially that I'm not very advanced linux user
Does the usb mice and keyboard work properly? Or other usb-stuff?
dicksteele said:
I'll try again. Got up until mounting new partition. Created mountosh.new copied over to phone rebooted. Didn't mount. Didn't have anything in /sbin dir. Like losetup.
Back to .sbf now. Going to try script and give it another go.
Click to expand...
Click to collapse
Hmm... that's really, really strange.
Edit ubuntu.bad and comment out the reboot line, then. Should just be a matter of adding rem at the beginning of that line.
Also, you shouldn't have to use the sbf. Using the soft brick recovery instructions should be enough, since all you would need to do would be to rename mountosh to mountosh.new, then rename mountosh.orig back to mountosh to get the original state back.
Sogarth said:
Now with more scripting!
I've added a version 0.5 of a setup script that automates some of what happens (I've denoted how far in the process it performs right now). It should print out a user-friendly version of what it's doing, in addition to what it's failing on if it fails. Appropriate notes added in the first post as well.
Click to expand...
Click to collapse
Shouldn't for /f "tokens=*" %%l in ('%~dp0adb.exe shell "chmod 6755 /tmp/psneuter > /dev/null 2>&1 && echo PASS"') do set retval=%%l
be chmod 0755 ? Getting error can't execute psneuter. First I thought it was because I already had one in tmp from AROOT. Trying again now.
Sogarth said:
Hmm... that's really, really strange.
Edit ubuntu.bad and comment out the reboot line, then. Should just be a matter of adding rem at the beginning of that line.
Also, you shouldn't have to use the sbf. Using the soft brick recovery instructions should be enough, since all you would need to do would be to rename mountosh to mountosh.new, then rename mountosh.orig back to mountosh to get the original state back.
Click to expand...
Click to collapse
I was running Gingerblur. Wanted to start fresh. And it wasn't from running batch file. It was before you creating batch. Tried from first post instructions. No biggie. I'm having fun !!!
dicksteele said:
Shouldn't for /f "tokens=*" %%l in ('%~dp0adb.exe shell "chmod 6755 /tmp/psneuter > /dev/null 2>&1 && echo PASS"') do set retval=%%l
be chmod 0755 ? Getting error can't execute psneuter. First I thought it was because I already had one in tmp from AROOT. Trying again now.
Click to expand...
Click to collapse
No, it's actually chmod 6755 since it's setting u+s. What's a bug in there (and I'm about to upload a fixed version) is that /tmp/psneuter actually kills the connection immediately, so it can never return "PASS". I added in a user check afterward instead.
A fixed 0.5.1 uploaded.
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