Related
Is there a good way to get the current version of Cyanogen up and running on the SDK emulator? I have several people that complain about my application widget closing when they open or close the keyboard. The logs show nothing pertaining to my application and the only thing they all have in common is a stock G1 with Cyanogen 4.2.6 and no home screen manager. Many others with non-modded G1's do not have this problem.
I'd like to test it out in the emulator since I now only have a Droid
I found some instructions with an image file to use for this, but it was for a very old version of Cyanogen.
do a nandroid backup and then copy the files from it in to the directory of a virtual device you have already created
then all shall be good
Is there a good source to snag a existing nandroid backup of 4.2.6? I don't have a G1 or any other device to run a nandroid backup on. Too bad too cause I just shipped out my old HTC Magic a few days ago. Now all I have is my Droid.
I'll search around for one and report back if I locate one.
just did a dump for you
http://code.google.com/p/cyanogen-updater/downloads/list
itl be up in a few minutes
You just need to make a yaffs2 image of the /system folder from cyan's update.zip. The boot.img is already in the zip.
Search for mkfs.yaffs2.
That nandroid backup works perfectly in my AVD 1.6 emulator. Thanks so much for building that for me. I can test all my apps against Cyan now
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?
pcm2a said:
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?
Click to expand...
Click to collapse
Yes, you can run anything on the emulator like that
I also found out that trick a few days ago. The only problem I have is that I do not get an Internet connection.
Does the SDK simulate wifi, 3G or is there just another fictive network device? I've got DroidWall and Y5 installed. Furthermore I've got sometimes problems to start my wifi after rebooting (problem by manual copied wpa_...cfg, I guess).
I am not really sure where to search. I will investigate the stuff in the paragraph above but perhaps you've got another few hints for me?
btw: I've got 4.2.13, but that shouldnt make a big difference, should it?
Anybody has found a fix for internet Issue for Cyanogen system.img file and Android SDK emulator?
Regards,
Oscar.
I've been searching both google, and the xda forums all day trying to find a solution for this problem. I want to test certain functionalities of ROMS in the emulator. The problem is that I'm unable to get past the bootscreen animation on any ROM.
All the guides I've found are for Roms based on 1.5 and earlier.
My method thus far has been to nandroid backup my system, paste the system.img into a copy of the 2.1 API folder located in "platforms".
It's obviously trying to load the system, because it's showing the custom boot sequence, but fails at some point and goes into a loop.
Thus far, I've tried upping the RAM, Cache, and heap limit of the emulator, but to no avail.
So, I'm fairly new to Android myself and am still learning things daily. My first two thoughts are:
1) Aren't there some drivers in the system.img that are going to be device specific? So, you'll have to swap out the Eris stuff and insert some 'goldfish' drivers or whatever they call the emulated arch?
2) Logcat is your friend. Logcat it while it's booting up. That should give you some clues.
3) If you figure this out, please post the steps so that anyone else who wants to do the same will not have to start from scratch.
4) Isn't this fun?
gnarlyc
Indeed, will logcat it tonight and see what I can find through that.
I was looking for a way to make custom rom running in the emulator.anyone got a working 2.1 rom for emulator?
First thing, If you smoke, go grab your smokes, if you drink coffee, go grab a cup. This is usually a painless process but not always.
You will need HSPL installed, as well as a Class 4 or better sd card.
Before i begin i want to thank the following; with out them it would not be possible.
cr2
NetRipper
dcordes
Markinus
LeTama
Cotulla
dan1j3l
tsamolotoff on s200
Parad0XUA
Cass
http://forum.xda-developers.com/showthread.php?t=719646
THANKS GUYS!!
What you will need is the installation copy of the build that you will be using, the latest zImage and your sdcard.
The latest Android build can be found here: Its under the standard builds section.
http://gamesquare.co.uk/
And the latest Zimage can be found here:
http://cotulla.pp.ru/leo/Android/
I personally recommend the dan1j3l's Froyo build.
Down load both the zimage and the build.
Format your sdcard, select default settings and unselect the quick format option.
After the formatting is done (about 20 mins)
extract the contents of the Froyo build to your sdcard.
Located in the folder "android" you will find a file names zimage, replace it with the one you downloaded.
WITH YOUR USB PLUGGED INTO A POWER SOURCE, reboot your phone.
As soon as you can, using the built in file manager if u have one, navigate to the android folder, select the program CLRCAD, (it will not do anything that you can see)
Then select the Zharet program.
Lay the phone down!
Sit back and wait, you will see text fly across the screen, the flash might flash, screen might fade and then come back.
Once linux is done loading and mapping out the hardware, android should be up and running.
Sign in to google and your contacts will sync if you have any on there.
Android is not perfect yet BUT it has come an amazing way since the beginning of the month.
I am using the current settings in WM, if you can do the same and you should have no problems.
SA TMOBILE HD2
HSPL2, I know HSPL3 is/has been out and is recommended, but is there any advantage in using it, i don't want to change if i don't need to
Radio 2.10.50.26
O.S. 5.2.21908 (21908.5.0.93)
Manila 2.5.20161332.0
Energy.Leo.21908.Sense2.5.Cookie.Jul.16 (absolutely love the energy roms, always updated and he includes the program to back up all settings making the update flashes a pleasant experience)
i ALWAYS TASK 29 before all roms!
CLASS 4 or better sd card.
When ever you want to load android, you must do so by selecting the two files mentiond above after a clean boot and always clrcad.exe first.
Sometimes android will not boot correctly, remember it was not designed for this phone.
Also all settings you make, programs you download, ect will stay in android
Pictures and such will be shared between android and wm.
Trying...
I'm installing it now per your instructions. A couple of concerns you might be able to help me with. I could not find the program CLRCAD in any folder, ok I couldn't find an android folder either. I went to my SD card where I had extracted the froyo & copied over the Zimage, I didn't see a Zharet program but I did see a haret file that looked like a program so I clicked on it and it started to download Linux! I hope I did it correctly even though it seemed slightly different. am I going to run into trouble not having run the CLRCAD?
Thanks for all your hard work.
Guess I answered part of my question. It did not install correctly. I'll look for a CLRCAD and retry.
cant believe im back in the winmo forum once again.ran HARET froyo last night on my HSPL2 Leon RoM,and wow.with wifi i was browsing,playing 3d games(flawless compare to my EVO 30fps capped),and watching youtube.really loving it.glad no one bought my HD2 but now its a keeper.
BigB4400 said:
I'm installing it now per your instructions. A couple of concerns you might be able to help me with. I could not find the program CLRCAD in any folder, ok I couldn't find an android folder either. I went to my SD card where I had extracted the froyo & copied over the Zimage, I didn't see a Zharet program but I did see a haret file that looked like a program so I clicked on it and it started to download Linux! I hope I did it correctly even though it seemed slightly different. am I going to run into trouble not having run the CLRCAD?
Thanks for all your hard work.
Guess I answered part of my question. It did not install correctly. I'll look for a CLRCAD and retry.
Click to expand...
Click to collapse
I Found CLRCAD ( I think I was just a little sleepy last night when I was trying this) I ran it and it loaded correctly. Wow it seems to run great! I am running Touch-X Extreme ROM and have some issues with the phone(it doesnt work, I have no antenna). I will try loading energy's rom (since so many people have got the phone to work well with his) and see how well it works out.
Good luck!
Do we really need to format our SD card? If we don't what would happen to the data already on there?
is the "zimage" provided for both dan's froyo and desire v4?
which files do i replace with the new zimage?
After a few days of use, this build seems to run fine. Except for a few things. 1) my phone tends to run real *hot* after using Android. And second, after about 5 min of idling the screen goes black and there seems like there's nothing I can do about except to reboot. I can't even push any of the bottom buttons, that doesn't work either. on. It will run just fine as long as I don't let it sit to long without touching the screen. Is this normal or am I doing something wrong? I can't wait for a even more stable build.
why cant i sign into google and other networks and why is it running overclocked? help me out yall got daaaamn lol. thanks
Is Paradoxua's Froyo build more stock than daniel's? Because daniels' uses ADW, which I'm not too fond of.
Also, is anyone else experiencing weird scrolling issues? Like you flick down a list and it's supposed to go flying down, but it only goes down like a tiny bit.
Another issue, when the screen turns off while you're connected to PC, the phone seems to disconnect too. I assume this is a WinMo issue because in WinMo when you connect your phone to your PC the screen is always on.
Thread moved to General.
i got my hd2 to load android just fine.. but the screen is very dim.. any ideas??
maybe you can toggle the backlight settings in winmo.. idk. it works for the tp2.
I always get the green screen or death or it enters android and quickly says powering off. And shuts off.
jaadamoo said:
i got my hd2 to load android just fine.. but the screen is very dim.. any ideas??
Click to expand...
Click to collapse
you need to make sure automatic light is off in win mo before you boot up android and i always leave it at around 60% and it works fine.
I have also been having some scrolling issues. It goes down a tad bit and if you hold the screen for a fraction of a second too long after first setting your finger on the screen, then it acts as if you did a holding touch.
Also the 3g is very very slow, kinda makes the market place useless since it takes for ever to download something. Wifi downloading is working.
New zimage file
Try replacing your current zimage file with this one.
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
Just replace/override it on your sd card.
Also delete your cache folder and your data file.
You will loose your information inside of android, like doing a reset of the OS.
Check this http://cotulla.pp.ru/leo/Android/ often, fair warning many people are having problems with the newer image marked(7-25)
Some roms or radios wont work for sure!
I am now running MIRI rom wm6.5 V17.6 with radio 2.12.50.02.2 and I must say very impressive how far you devs have come in a few weeks. Phone is working with audio and WIFI. I had stock rom TMO 2.13 installed with radio 2.10 and although Android loaded and ran fine I did not have audio during calls,they sounded robotic at times or no audio at all. I am not sure if it was the radio upgrade or switching the ROM to MIRI that did the trick. I have been playing with phone for approximately six hours nonstop and it has been solid...
Gen. Y DualBOOT Implementation
Does the app work well the newer builds?
Btw a very BIG thank you all the guys working on this, you guys are freaking AWESOME!
acessford101 said:
Try replacing your current zimage file with this one.
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
Just replace/override it on your sd card.
Also delete your cache folder and your data file.
You will loose your information inside of android, like doing a reset of the OS.
Check this http://cotulla.pp.ru/leo/Android/ often, fair warning many people are having problems with the newer image marked(7-25)
Click to expand...
Click to collapse
Thanks, I was using the Jul 19 zImage.rar file. I'm about to try this one and see if it makes a diff.
anyone know how to get the data connection to work for T-Mobile on the Android desire v5? I go into APN settings but it always requires a username and password but t-mobile doesnt use a username/password for apn.
This isn't my post but I have very same problem and thought i'd bring it to this thread see if anyone happens to have same issue or has solution?
Hi guys,
I've been trying out different android builds but after a while it won't boot in android anymore.
I run the CLRAD and HaReT, it show the command lines and then freezes on the HTC screen.
It is not the first time I'm launching it, everything is allways set up the way I like it and then I want to reboot a final time and it freezes. (first boot only takes 10 min.) Then I have to take out the battery to reset, but everytime after it freezes, tried waiting for +1 hour but no changes.
When I delete all the android files from my SD card and copy the original ones it restarts again and I have to setup everything again.
I tried new wm roms (Miri HD2 wm6.5.x) different radios (now 2.12.50.02.2),
the new HSPL3 but nothing seems to solve this.
edit: now I'm trying to use the mdeejay froyo HD v3.7 rom
I've searched the forum and other users seem to have the same problem, but no solutions have come forward. The people replying allways seem to think it is the first boot that takes 10 min. but it's not that. First boot works fine.
Click to expand...
Click to collapse
What builds have you tried? What memory card are you using (class and size)?Did you format your memory card to FAT32? You could also try deleting app data folder on your storage card, as each time you use a build a bit of it may be left in this folder( it does no harm and will re-create itself straight after). Have you tried any android boot loaders e.g MSKIP android loader v5. No-one else had replied so thought id try and share what little knowledge i have. If you have been asked all this 20 times over, Sorry!
I am using 8gb mem card came with htc Fat32 (formated it using win and htc both)
Win build is dutty's com2 3.14 latest rom
Mdeejay 2.3 Revolution android version.
had jmz's bootloder
Tried everything u said nothing happened...
Trying now MSKIP's boot loader, with fresh installation lets see...
Ur effort time and help is always appreciated thanks Funkdat
maybe because OS's weren't designed to run on a SD card??? Sell your hd2 and get a galaxy s phone.
I feel your pain. Very very frustrating and you feel you have tried everything. Time consuming too.
What bothers me a bit with those builds is that they load up the HTC logo so actually don't see what is happening during bootup. I wonder if you couldn't bypass that?
that wud have been big help if i could see what is actually happening but the Big HTC Logo screen is hiding everything and i am just sick of it.
Well if i could only burn the ROM into HD2 that would have been much better so wouldn't have to worry about anything i have to format my storage card every time or either delete everything on the sd card to make it work duno which file is it causing this error but i hope some one will come up with solution...
CHeers
still the same tried everything...
Hi there,
You do understand that the HD2 was not made nor meant to run Android and that all the Android ROM's are third party ones and unofficial ?
You did not say whether or not you tried to install on the internal memory and not the card ?
Bye,
Itamar
supermaster said:
This isn't my post but I have very same problem and thought i'd bring it to this thread see if anyone happens to have same issue or has solution?
Click to expand...
Click to collapse
did you try starting it, deleting the data.img and starting it again?
nrfitchett4 said:
maybe because OS's weren't designed to run on a SD card??? Sell your hd2 and get a galaxy s phone.
Click to expand...
Click to collapse
Oh the contradiction. You say that, yet you use it too
"Android Playground: HyperDroid 1.6"
You gonna sell your HD2? (now for the crickets )
This might seem stupid, but have you tried deleting the Android folder from your SD card? Or modify this line in startup.txt:
set cmdline "rel_path=Android"
to
set cmdline "rel_path=/"
The problem might be that because of rel_path, it's looking for your android ROM in the "Android" folder. And some applications create that folder (Google goggle for example) to save information. I had an issue quite similar to yours. Now editing startup.txt is the first thing I do in a build. I currently have 5 different builds, one for every day of the week! haha.
Hope this helps!
rr5678 said:
did you try starting it, deleting the data.img and starting it again?
Oh the contradiction. You say that, yet you use it too
"Android Playground: HyperDroid 1.6"
You gonna sell your HD2? (now for the crickets )
Click to expand...
Click to collapse
not at all. I actually rarely boot into android and when I do, I keep my android builds on a seperate sd card. But I'm also not on here starting threads complaining that android won't boot properly on my winmo phone.
That's why its my playground. I am not trying to make android my daily driver.
karendar said:
This might seem stupid, but have you tried deleting the Android folder from your SD card? Or modify this line in startup.txt:
set cmdline "rel_path=Android"
to
set cmdline "rel_path=/"
The problem might be that because of rel_path, it's looking for your android ROM in the "Android" folder. And some applications create that folder (Google goggle for example) to save information. I had an issue quite similar to yours. Now editing startup.txt is the first thing I do in a build. I currently have 5 different builds, one for every day of the week! haha.
Hope this helps!
Click to expand...
Click to collapse
there's only 5 days in a week???
nrfitchett4 said:
not at all. I actually rarely boot into android and when I do, I keep my android builds on a seperate sd card. But I'm also not on here starting threads complaining that android won't boot properly on my winmo phone.
That's why its my playground. I am not trying to make android my daily driver.
Click to expand...
Click to collapse
Well that's true. Android isn't really that stable enough to run often - especially when I see that it sucks down 500mA of power. That leads to 2 hours of battery.
(speaking of separate SD cards, I still have to send my faulty 16GB back to HTC )
I'd post to the ROM section but I'm not yet sufficiently "priv'd" for that so figured I'd start here as it will also solve my problem of not having enough posts to post there.
I'm trying to generate my own CM7 update.zip using JackpotClavin's stuff so that I could try to work the sound and video issues (ultimately I'd like to get the bluetooth going as well but that may be solved by some of the kernel work that appears to already be underway)
I've got the build running in a fresh VM but I'm obviously missing something as when I flash my build it gets stuck in an boot loop on the Cyanogenmod splash screen (comes up, spins for s few seconds and then recycles)
I'm able to get into adb shell and flash back JackpotClavin's update.zip and recover fine but I'm trying to figure out what's wrong with my update.zip file (as a side note, I've also ordered the stuff to build myself a factory cable so if I really screw myself I can get back to the fastboot to put something workable back down)
So, the steps I've taken are:
-Setup a 64bit Ubuntu 11.10 environment
-downloaded the CM7 repo
-Copied the proprietary github repo to .../android/system/vendor/amazon/blaze
-Copied the device gitbub repo to .../android/system/device/amazon/blaze
-Did the copy of the cyanogen_blaze.mk to vendor/cyanogen/products/ and edited the androidproducts.mk in there too as specified per the ROM thread
I then did a "brunch blaze" after setting the build environment to fire off a build and it chewed for hours with no obvious errors (none that caused an exit of the build) at least and in the end I had an update-cm-7.2.0-RC0-blaze-KANG-signed.zip that seemed good.
I flashed that to the device and that's what got me in the boot loop. Anyone have any ideas on what I missed in generating the build?
Well enough spewing, if anyone can help to get me going that would be great and thanks to JackpotClavin for the work to date.
Can you get a logcat dump? Sounds like it's getting pretty far.
Sent from my Nexus S using XDA App
Will do, I copied it aside when it was stuck in the loop and will post when I'm done with the current task and get back to a place where I can get to the sdcard contents. JackpotClavin sent back a note saying that he added some clearing of a couple of the partitions into his version of the ROM and that might be the difference so I'm off trying that now. More in a bit.
awesome. very excited. keep up the good work guys.
whistlestop said:
I'd post to the ROM section but I'm not yet sufficiently "priv'd" for that so figured I'd start here as it will also solve my problem of not having enough posts to post there.
I'm trying to generate my own CM7 update.zip using JackpotClavin's stuff so that I could try to work the sound and video issues (ultimately I'd like to get the bluetooth going as well but that may be solved by some of the kernel work that appears to already be underway)
I've got the build running in a fresh VM but I'm obviously missing something as when I flash my build it gets stuck in an boot loop on the Cyanogenmod splash screen (comes up, spins for s few seconds and then recycles)
I'm able to get into adb shell and flash back JackpotClavin's update.zip and recover fine but I'm trying to figure out what's wrong with my update.zip file (as a side note, I've also ordered the stuff to build myself a factory cable so if I really screw myself I can get back to the fastboot to put something workable back down)
So, the steps I've taken are:
-Setup a 64bit Ubuntu 11.10 environment
-downloaded the CM7 repo
-Copied the proprietary github repo to .../android/system/vendor/amazon/blaze
-Copied the device gitbub repo to .../android/system/device/amazon/blaze
-Did the copy of the cyanogen_blaze.mk to vendor/cyanogen/products/ and edited the androidproducts.mk in there too as specified per the ROM thread
I then did a "brunch blaze" after setting the build environment to fire off a build and it chewed for hours with no obvious errors (none that caused an exit of the build) at least and in the end I had an update-cm-7.2.0-RC0-blaze-KANG-signed.zip that seemed good.
I flashed that to the device and that's what got me in the boot loop. Anyone have any ideas on what I missed in generating the build?
Well enough spewing, if anyone can help to get me going that would be great and thanks to JackpotClavin for the work to date.
Click to expand...
Click to collapse
lucky you... i can't even get my environment to boot. I have a core i5 w/ 16gb of ram.
Ok, not sure whether what Jackpot said helped or not. I did the following:
-I unzipped the update.zip that I generated
-I then edited .../META-INF/com/google/android/updater-script and added the lines
format("ext4", "EMMC", "/dev/block/mmcblk0p10");
format("ext4", "EMMC", "/dev/block/mmcblk0p11");
after the existing line below
format("ext4", "EMMC", "/dev/block/mmcblk0p9");
-I then zipped back up the directory to make an updated update.zip file and then copied it to the sdcard partition and went through the CWM recovery installation and booting again (as an aside, I'm going to look into making an edit to CWM for the near term until they fix things up to work with the touch screen and see if I can have it always boot to CWM and then just wait for 10sec and if no button presses then I'll continue the boot (not sure if that'll work but it would sure be a lot easier than all of the switching between the stock and CWM recovery images.
-I then flashed back the stock recovery image and rebooted and this time I got to the actual CM7 desktop but after a few seconds it reset and I was back at the CM7 loading screen (so like before but I seem to get to the login screen faster now such that I see it before the reset happens)
-I then captured the two attached files (the output from logcat and dmesg)
I'm going to go unzip my update.zip and Jackpot's update.zip and see if I can track down the difference there.
As always, any help is greatly appreciated.
pyrostic said:
lucky you... i can't even get my environment to boot. I have a core i5 w/ 16gb of ram.
Click to expand...
Click to collapse
Are you running Native or in a VM? I can point you at the pages I followed to get to where I'm at if that helps. I'm doing Ubuntu 11.10 64bit in Fusion on a Mac with 2GB and 2 cores and seem like I'm close. Post here if you want me to dump in the steps and links I used to get you farther.
No luck on the changes proposed by JackpotClavin. I'm pulling the repo's again and rebuilding overnight and will try again in the morning. I'm down to all of a couple of files that are different between my build and his so I'm close.
goodluck
Sent from my Kindle Fire using xda premium
whistlestop said:
No luck on the changes proposed by JackpotClavin. I'm pulling the repo's again and rebuilding overnight and will try again in the morning. I'm down to all of a couple of files that are different between my build and his so I'm close.
Click to expand...
Click to collapse
Hope this works.I'd love to have sounds and you tube working
Sent from my cm7 kindle fire using xda premium
Veritass said:
Hope this works.I'd love to have sounds and you tube working
Sent from my cm7 kindle fire using xda premium
Click to expand...
Click to collapse
Yep me too. That's why I figured I'd start the process of getting my own build going so that I could try to push the ball forward as JackpotClavin has finals the next few weeks. Build's done but I have not been able to test yet (the day job has gotten in the way) Maybe tonight if I get a chance (the new build is done and I've made the hand patches so just need to do the testing)
SUCCESS (at least in getting a build that mimics where JackpotClavin left off) I'm now off building a new version with a couple of possible flags thrown for the build that might help the sound and video issues. More in a bit...
whistlestop said:
SUCCESS (at least in getting a build that mimics where JackpotClavin left off) I'm now off building a new version with a couple of possible flags thrown for the build that might help the sound and video issues. More in a bit...
Click to expand...
Click to collapse
Success with sound?
Nope not yet but thats my current quest. Right now I just have what JackpotClavin has going (which of itself took me a few days to get working reliably) First try today on sound was a no go but I have another build going now so will check in the morning to see if I'm any closer.
Quick update as I'm heading out to work. Sound is working (at least I can play an MP3 and it plays) I'm going to test things out today and if everything sound wise seems to be working then I'll post the new update.zip tomorrow.
I'm now off to look at the video issue. I at least know that we're missing a library so now I need to see how to go about getting into place (not sure if I missed copying something from the original ROM or if I need to toggle some more flags to get it built)
Fantastic News.
Excellent work.
whistlestop said:
Quick update as I'm heading out to work. Sound is working (at least I can play an MP3 and it plays) I'm going to test things out today and if everything sound wise seems to be working then I'll post the new update.zip tomorrow.
I'm now off to look at the video issue. I at least know that we're missing a library so now I need to see how to go about getting into place (not sure if I missed copying something from the original ROM or if I need to toggle some more flags to get it built)
Click to expand...
Click to collapse
OMG if you post the update today im going to be so happy!
Couldn't be greater, keep up your good job, millions are waiting !
SOUND WORKS! he pm'ed me a beta test. as he doesnt want to release and brick peoples kindles. but It worked fine! Sound is on! wifi works. Video doesnt work still but you can watch youtube videos from the youtube app. havent tryed netflix yet. but so far its good!
That's freakin' awesome!! Major props to you guys.