Related
It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...
Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.
ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?
i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...
Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...
I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either
My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list
Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?
Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!
I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...
Anyone, anything?
Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR
I still have this problem.
I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.
The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something
I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.
It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR
Ah yes it works! Beautiful beautiful!
Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere
I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?
use the right starup.txt file
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
atomiq said:
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
Click to expand...
Click to collapse
not exactly sure....when u tried each cab, did u completely uninstall and delete all traces of each build including the fsck files? alot of times if not, and u try to install a new one, itll stick pick up the old data and mix with the new and cause issues. The one to try thats the easiest is the AOSP. data and service works off tops without doing anything.
try this...whatever cab u got in there..uninstall it...then ...go into file explorer or whatever and delete any and all traces of the previous build. after that, if u have clear temp or clean ram, use that. then soft reset.
get the build cab of ur choice, but id recommend the AOSP for the quickest start. download it to root of storage card which is /storage , not in a folder in storage(example /storage/programs). it has to b in the root. then install. then soft reset. once it boots back up, go to the android icon. press it..then update all the new files for the build b4 ur first boot up. u should see the tab to let u update. after update complete, then press run android...and hopefully any little issues or residual files are gone and u can complete the startup or bootup of android. let us know if that didnt wrk for ya.
ok now boots, and works fine
i'm using AOSP 2.1 updated
EDIT MY INTERNET WORKS NOW, LOL,
I'm having the same exact error on my AT&T Tilt 2 with stock ROM. I downloaded the AOSP into the storage/programs folder of the SD card, installed it to the SD card, then ran the update. After the update, I got the "Failed to mount the SD Card. Cannot Continue" error. I uninstalled the program and got rid of everything ans started from scratch with the same error.
Any idea?
Okay.... I've tried this a few times with no luck. Here is what I have:
AT&T Tilt 2 with stock ROM. I started with a fresh Hard Reset this morning (due to problems with Good Mobile Messaging) and loaded the AOSP file to my micro SD card (\Storage Card\ProjectAndroid 2.1AOSP 042610.cab). I ran a level 3 CleanRAM, then double clicked on the AOSP file on the SD card using TotalCommander. The file asked where to load it to and I chose the SD card. It successfully installed and I did a Soft Reset using the red reset button behind the battery cover.
Once turned back on I go to Start and press Project Android. Once loaded up, I went to Menu and Update. It updated successfully in about 5-10 minutes and I then clicked Run Android. The screen goes black and runs a bunch of script until it gets to this:
Welcome to Vogue Linux
Running an fsck on SD card
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Logical sector size is zero
mount:mounting/dev/block/mmcglkopl on/sdcard failed: Invalid argument
Failed
Failed to mount the SD card. Cannot continue
/bin/shi can't access tty; job control turned off
It then freezes at this point and stays there. I've uninstalled and removed all sources of the files (that I could find) and started from scratch several times and it does the same thing each time.
Is something wrong? Am I missing something simple?
ROM Version: 1.59.502.3 (67150) WWE
Rom date: 09/25/09
Radio Version: 4.48.25.20
Protocol version: 61.39tc.25.30U
is there any other info you need?
i did use this formatter
http://www.megaupload.com/?d=287HD74A
extract, install, open, select your unit, click on option, select full erase ON
let ir run..
this promise to fix this error acording to a forum that i read
outside of XDA, it can also throw that same error if you are using
a SLOW storage card.
pls report what happened so we help other people with the same issue..
The error message is normal. Just ignore it unless the thing wont boot overnight
thebulletfromhell said:
The error message is normal. Just ignore it unless the thing wont boot overnight
Click to expand...
Click to collapse
So just leave it there and let it keep running? I'll give it a try.....
sethjamto said:
So just leave it there and let it keep running? I'll give it a try.....
Click to expand...
Click to collapse
No joy..... it hung up on the same screen that I quoted above for over 5 hours. I soft reset and then uninstalled the software. I guess if I'm destined to have Android, then I'll just go out and buy an Android based phone.....
i guess you didnt tried the FORMATTER that i've posted
anyways
maybe you should wait for the release of HTC VISION
or wait much looooooonger a couple of years for an official android rom
for our poor htc rhodium..
good luck.
(I posted this in general, but I think there's too much technical info for any user to be able to assist. I realize this isn't development related, but delete the post if it's too off-topic please.)
Over the past few months since 'Grocery iQ' has been out, I have been trying to install it. Despite trying it on several different ROMs on my old G1 and now several different ROMs on my Slide (including now Froyo) it seems that it doesn't like to install. From my experience it is the biggest direct-download from the Market that I have come across weighing in at 8.01MB - by 'direct-download' I mean that the application itself is downloaded entirely from the Market and the size I reference isn't from 'additional' files downloaded to the SD card after running the program.
Everytime I try to install it the system just says 'Installation Unsuccessful' and one time I got an error code: -18 (on Eugene's Froyo Kanged RC1). Fortunately I'm fluent enough with the device to have my SDK setup and I grabbed a logcat from the adb server. Using what debugging mind-set I've had from coding I was able to find the problem is:
Code:
D/VoldCmdListener( 122): asec list
I/PackageHelper( 1703): Size of container 10 MB 8401843 bytes
D/VoldCmdListener( 122): asec create smdl2tmp1 10 fat {} 10010
E/Vold ( 122): ASEC file '/mnt/secure/asec/smdl2tmp1.asec' currently exists - destroy it first! (No such file or directory)
W/Vold ( 122): Returning OperationFailed - no handler for errno 98
E/PackageHelper( 1703): Failed to create secure container smdl2tmp1
E/DefContainer( 1703): Failed to create container smdl2tmp1
What exactly is happening here? It almost looks like it's trying to create a secure environment for the install or the program uses copy-protection. Can someone please elaborate on this - hopefully a dev?
Thanks!
That's odd, it installed fine for me on SlideM4
How much free space do you have? Are you doing the install over WiFi?
After doing some research I believe that ASEC is part of the copy protection scheme used in a2sd on Froyo.
r0man said:
How much free space do you have? Are you doing the install over WiFi?
Click to expand...
Click to collapse
I have 95.51MB free >.> And I'm not sure why WiFi or 3G would matter, but I've tried both ways (unintentionally).
r0man said:
After doing some research I believe that ASEC is part of the copy protection scheme used in a2sd on Froyo.
Click to expand...
Click to collapse
Interesting. I'm not using A2SD though since my SD card is formatted entirely FAT32 (Froyo didn't like my card being FAT32+EXT3+Swap), but I wonder if Froyo A2SD runs entirely on FAT32? It would be complicated for Google to require people to partition their SD cards now that Froyo has A2SD built-in.
nbetcher said:
I have 95.51MB free >.> And I'm not sure why WiFi or 3G would matter, but I've tried both ways (unintentionally).
Interesting. I'm not using A2SD though since my SD card is formatted entirely FAT32 (Froyo didn't like my card being FAT32+EXT3+Swap), but I wonder if Froyo A2SD runs entirely on FAT32? It would be complicated for Google to require people to partition their SD cards now that Froyo has A2SD built-in.
Click to expand...
Click to collapse
Downloads over networks that aren't stable like 3G can cause bad downloads.
Froyo runs a2sd entirely on the SD card, if the app doesn't have the proper line of code specifying whether to go to SD card or internal memory I think that it won't install properly on Froyo, not sure though.
r0man said:
Froyo runs a2sd entirely on the SD card, if the app doesn't have the proper line of code specifying whether to go to SD card or internal memory I think that it won't install properly on Froyo, not sure though.
Click to expand...
Click to collapse
I'm still not sure whether it tries to use the FAT32 partition for A2SD (which I doubt since it cannot do symlinks among other stuff) or EXT2/3 on the SD card if present.
Anyways, I was fiddling with the settings more on the phone and there's a new option in the "Settings" that is "Cyanogenmod Settings." In there you can tell it whether to install to your SD card or not (it's not like the old checkbox for A2SD). I told it internal storage and the program still failed to install for the same reason.
nbetcher said:
I'm still not sure whether it tries to use the FAT32 partition for A2SD (which I doubt since it cannot do symlinks among other stuff) or EXT2/3 on the SD card if present.
Anyways, I was fiddling with the settings more on the phone and there's a new option in the "Settings" that is "Cyanogenmod Settings." In there you can tell it whether to install to your SD card or not (it's not like the old checkbox for A2SD). I told it internal storage and the program still failed to install for the same reason.
Click to expand...
Click to collapse
That is weird because I was gooing to tell you to go into CM settings and make sure to select internal. Maybe it is just the app???
sultan.of.swing said:
That is weird because I was gooing to tell you to go into CM settings and make sure to select internal. Maybe it is just the app???
Click to expand...
Click to collapse
No - no one on the market has made any comment regarding the problem. In fact everyone is saying how they love the program (minus the occasional moron).
I've had this same problem with my G1 and on a couple other ROMs on the Slide. R0man said it installed for him though on SlideMR4
Installed on my MR1V4-Remix over 3G fine. Did you try an ADB install through the SDK?
I can post for u if u wanna try that.
Sent from my MR1 V4 Remix 3G using Tapatalk
Fordude said:
I can post for u if u wanna try that.
Click to expand...
Click to collapse
Post the APK? That would be great. Thanks!
nbetcher, Froyo doesn't put the full app on SD card, just the majority of the files.
GroceryIQ
Really basic:
1. download
2. copy/move to SDK tools directory
3. From SDK tools directory (where file is downloaded) type this:
adb install com.coupons.GroceryIQ.apk
Hope this helps!
Fordude said:
GroceryIQ
Really basic:
1. download
2. copy/move to SDK tools directory
3. From SDK tools directory (where file is downloaded) type this:
adb install com.coupons.GroceryIQ.apk
Hope this helps!
Click to expand...
Click to collapse
Thanks for the upload. I already have an ADB environment setup, but unfortunately this method did not change the error. ADB returned:
Code:
pkg: /data/local/tmp/com.coupons.GroceryIQ.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
ADB's logcat shows the same error as before (when installed using Market).
Slightly off topic, but you do ask about it, and I don't think I've seen it answered here, but in one of Eugene's thread, they do state that Froyo's inherent a2sd is all handled on FAT32 partitions. And I think on Eugene's Froyo release, it specifically runs into issues if you have an EXT partition... Just some anecdotal info.
froyo has apps2sd built in so no partitioning of the card is required. Just straight fat32 which is what it should be by default. This makes sense because the mainstream user isn't going to have a clue on how to partition an SD card and that just wouldn't be very user friendly...
And yes the froyo CM rom will have issues if your card has an ext but Eugene said apps2sd doesn't even work on the rom anyways. It's there but it does nothing.
nbetcher said:
Thanks for the upload. I already have an ADB environment setup, but unfortunately this method did not change the error. ADB returned:
Code:
pkg: /data/local/tmp/com.coupons.GroceryIQ.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
ADB's logcat shows the same error as before (when installed using Market).
Click to expand...
Click to collapse
The apk is corrupted, apparently.
r0man said:
The apk is corrupted, apparently.
Click to expand...
Click to collapse
Nope. I used the same APK as Fordude (whom was able to install the program) provided through a reliable channel. If we took MD5Sums of both files I'd bet $10 that they're both the same.
After researching this extensively I'm coming to the conclusion that:
* This is a protected app; and
* Protected apps are broken on CM6/Espresso at the moment; OR
* There is some mis-configuration with Eugene's ROM; OR
* The kernel that is being used doesn't support a new(er) version of the dm_crypt api/module and/or the usage there-in with Froyo.
The last one in that list is the most likely, in my opinion. Many things like the camera are the first things to break in these major system upgrades since the software is using different APIs than the kernel module supports. (Remember that the kernel being used is still from the ORIGINAL shipment of this phone - 2.6.29, which is now over a year old and was specifically compiled for Espresso-stock.)
While I don't expect his ROM to be finished, I don't think this is something that anyone is even specifically aware of yet. It would be nice to know what Eugene thinks of this though.
Thanks for the help guys. Hopefully this will provide the community with some more information to make Froyo come to us quicker.
If we took MD5Sums of both files I'd bet $10 that they're both the same.
Click to expand...
Click to collapse
MD5Sum of the file I provided 38bef197bcd5133a20abf845e241ff18
This is my first for anything like this. I have a Sprint HTC Touch Pro 2, and want to put the latest version of XDANDROID on it. But, have no clue which version or where to start. I would like to eventually get in to building on my own. Could someone please help get me started?
TheCasper said:
This is my first for anything like this. I have a Sprint HTC Touch Pro 2, and want to put the latest version of XDANDROID on it. But, have no clue which version or where to start. I would like to eventually get in to building on my own. Could someone please help get me started?
Click to expand...
Click to collapse
to get started, it really doesn't get any simpler than downloading the latest FRX03 from here:
http://sites.google.com/site/androidport/downloads
(i'd recommend the RAR version, so you can unzip it into your SD card faster)
after that, just use WM's file explorer navigate to andboot and run haret.exe and you're "done"
----
(optional) with a little bit of more effort, go into the top sticky of this forum, and update to the latest Kernel (1253). the current Kernel in FRX03 from Dec 20 is (i believe) 1232.
It's sort of that easy, but I had this same question before I did it too. It would have been nice if the FAQ said this explicitly.
If you download the rar archive, it will extract out in its own subdirectory, e.g.
XDAndroid2.2Froyo.XXxxXX/andboot/...
The first thing I do is move the andboot subdirectory to the root of the SD card.
The next thing is to edit the andboot/startup.txt file to match your phone. I guess you can use the XDAndroidStartup utility to take care of this instead, but the first time I tried that it failed because of that silly runtime dependency.
If you want to use the startup utility, and it gives you an error and refuses to run, you need to install the updated net framework like it talks about on this page:
http://sites.google.com/site/androidport/startup-utility
Thanks guy I will give it a try and post if I have questions. I love the design/setup of my TP2 but I hate the windows OS.
Need more help My phone is getting stuck and the XDANDROID start up image/video thing
TheCasper said:
Need more help My phone is getting stuck and the XDANDROID start up image/video thing
Click to expand...
Click to collapse
Just let it do its thing, boots can take 5-10 min!
Kind of got it working, but have no idea how to use it fun stuff.
quick question, do I always have to have the sim card out when running ANDROID?
TheCasper said:
quick question, do I always have to have the sim card out when running ANDROID?
Click to expand...
Click to collapse
If your phone is in GSM mode, you'll want it in. Check your startup.txt, you'll need force_cdma=0 in there.
If you're on CDMA, I believe you do have to have the SIM removed, yes. Also, the above command should have a 1 instead of 0.
^^ I'm not positive about that piece, but I do know that Android on our phones will only recognize one or the other - GSM or CDMA. Maybe we'll get it to recognize both one day, I saw an entry for it in the RIL...
I do know that I have CDMA. Plus how do update the kernel, where do I put it?
TheCasper said:
I do know that I have CDMA. Plus how do update the kernel, where do I put it?
Click to expand...
Click to collapse
You simply replace your existing kernel and modules.
So delete the existing zImage/modules-xxxx.tar.gz, and put in the new zImage/modules-xxx.tar.gz. Don't rename the modules file, but be sure the zImage file is named just that - zImage.
The files go where you run haret.exe from - typically the root of the SD, or in /andboot.
UH-OH, not sure what happened. I reformated my SD card to do a new run since I found what I wanted. Now it seems like I can do everything but make calls in WM6.5. What do I do
TheCasper said:
UH-OH, not sure what happened. I reformated my SD card to do a new run since I found what I wanted. Now it seems like I can do everything but make calls in WM6.5. What do I do
Click to expand...
Click to collapse
Android should have no effect on WinMo (assuming you're using haret/install on your SD). Plus, this really isn't a place to get help with WinMo.
Do the usual - soft reset, hard reset, reflash of stock ROM.
arrrghhh said:
Android should have no effect on WinMo (assuming you're using haret/install on your SD). Plus, this really isn't a place to get help with WinMo.
Do the usual - soft reset, hard reset, reflash of stock ROM.
Click to expand...
Click to collapse
I know, I'm trying to put android on it and I am using haret from the SD card. I'm just not sure if this is will effect android or is a common problem. Thanks though, I have been going through those things while i wait.