yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] polyrhythmic:
@lauyanyameric: sounds like the build didn't install correctly, check your bootlog.txt in your /andboot/ folder and post your findings in the thread for whichever ROM you're trying to install.

@dmulligan: AFAIK there's no ROM that needs multiple simultaneous upgrades. It would probably confuse users more than help them, many ppl have enough trouble with the install process as-is. Also, we already make ROMs that work for Wifi on Kaiser and also work for Vogue, like my polymod build. There's no need to make the installer install different files for each device.
[Touch CDMA Android Development] dmulligan:
Perhaps themes and such. I am thinking of this as a way to do custom builds in a lego like way.
[Touch CDMA Android Development] polyrhythmic:
Many parts of an Android ROM have to match... mismatched parts can cause all kinds of headaches. That's why ROMs are released in full packages, they're not as easy to build as Legos.

Metamorph already exists for the theming process and is very simple to create packages for. However, even with Metamorph you still need a 'matching' theme for each ROM -- Metamorph basically replaces system .apks with matching themed system .apks in a way that doesn't (usually) break Android.

Android is advancing very quickly atm, doing more than Metamorph does would be difficult because file paths change, layouts change, apk structures change even with minor releases.

Our non-native Android builds are getting a lot closer to the structure of native builds, but they're still not the same. That's why you don't see a ton of people creating ROMs for our devices -- the changes have to be made very carefully.
[Touch CDMA Android Development] sparky101747:
Does the current nbh have the 2-26 updates for the highspeed bluetooth?
[Touch CDMA Android Development] dmulligan:
Thank you for the explanation. I didn't realize that android modules are so strongly coupled.
[Touch CDMA Android Development] mrkite38:
Are you holding the button / screen to get into recovery mode?
[Touch CDMA Android Development] bdg55:
I have held every button i can find, plus the screen, no luck
[Touch CDMA Android Development] zc2:
i2c interrupt

I have flashed my old Android Ion v1.5 to NAND of my AT&T Tilt (KAIS100) and now each time I do soft reset, I can't boot. Instead I got tons of messages like "msm_i2c_interrupt: IRQ but nothing to do" during the initial booting process and I have to remove the battery to reboot properly.

Does anybody know a solution for this problem?

Another question - what's faster SD or NAND? I did series of tests, coping a 10Mb file to /dev/null and in my case SD is faster!

How to tell the installer to use my old ext2 data partition on the SD card instead of the yaffs2 data partition in the NAND?
[Touch CDMA Android Development] surgedesign:
Porting to the diamond???

I was wondering if one of the dev's or someone involved with this project could provide me with a bit of information. I'd like to know what would be involved in porting the files available to here to the diamond. I've modified the vogue nbh files and managed to flash them to my phone with my own custom androidinstall.tar on my storage card with no luck. Would appreciate some advice, thanks!
[Touch CDMA Android Development] mrkite38:
Check myn's thread, he had his build running on diamond.
[Touch CDMA Android Development] surgedesign:
Care to share a link to where it says his build is working on diamond? I'm thinking you might be slightly confused as to what I'm asking, I'm looking to port over the nomorootfs to diamond so that we no longer need to use haret and winmo. Rather what I want to do is directly boot android of the internal storage or nand memory.
[Touch CDMA Android Development] mrkite38:
EDIT: nvm, went and looked. MrPippy and the others in the diamond forum would be the ones to ask, unless dzo has looked at this.

And just for clarity's sake, nomorootfs was a... structural change to how we ran android, not a media change. that is, it's independent of nand/sd. So your questions should read, 'is it possible to run android from nand on diamond yet?'
[Touch CDMA Android Development] myn:
Boy would I Love to have NoMoRootFS for Diamond..
[Touch CDMA Android Development] mrkite38:
you mean nand, right, myn? ;)
[Touch CDMA Android Development] mssmison:
Considering how easy it is to open the tar files and edit the build prop there would be no sense in distributing two different builds..
[Touch CDMA Android Development] JacenSolo2001:
any possible solutions for the "Failed to reach system.img on SD Card" when trying to boot from haret?
[Touch CDMA Android Development] smarcin:
Help using Haret

Could someone please tell us how to use the files with Haret? Do we still use ext2 partitions, if so, how do we partition? Fat32, ext2, ext2? If so, do we still use 256MB for each ext2 partition, or is that too big now? Or, do we just use one Fat32 partition? Also, what do we choose in the installer if we are booting from Haret? Can we do an update if we are only using Haret? Thanks.
[Touch CDMA Android Development] JeckyllHavok:
Same on my kaiser, is there anything we'll have to change? I succesfully created "normal" android nbh's for my kaiser, but today when i try to creat new one for kaiser i got:

losetup: /dev/block/loop1: No such file or directory

Failed

Failed to find system.img on SD Card

(the android install.tar was succesfully packed into nand)

Hope jamezelle won't see me posting kaiser questione here ;-) , sorry my friend.........
[Touch CDMA Android Development] PaceyWhitter:
This looks great, looking forward to trying it soon.

BTW, love Dr. Strangelove, thought most people on this board were to young to remember the movie.
[Touch CDMA Android Development] plemen:
This is fantastic! Quick question - since the build.prop and lcd.density is in the tar file, whats the difference between the three nbh files in the first post?
[Touch CDMA Android Development] myn:
As I understand. NBH controls the resolution and the tar file (which contains the build.prop) controls the lcd.density. Vilord, please correct me if I am wrong.
[Touch CDMA Android Development] mssmison:
That is totally correct :)
[Touch CDMA Android Development] TheKartus:
EDIT: Nevermind, I just failed to read menus. Playing with the menus now.
[Touch CDMA Android Development] chourmovs:
interested too
[Touch CDMA Android Development] vilord:
So i didn't get a chance to test without nand installed, I'll have to try that... it should still give you the options for sdcard parts or extfiles. if you don't have nand partitions or sdcard partitions, it should default to extfiles (but again, I haven't had a way to test yet)

You still have the option of 2 ext2 partitions with size of your choice, 1 ext2 partition with data on the SD card, or 0 ext2 partitions (but now it doesn't autodetect for you, you get to make the choice)
[Touch CDMA Android Development] vilord:
GREAT question!

There is a very easy way!

Build the base image the way you like/use it (or for your target audience).

Then you can build an androidupdate.tar that only includes /system/build.prop, or only includes /system/sysinit.rc.

Take a look at the eclair thread, I dropped in a link to eclair240.zip which simply switches you to 120dpi instead of 160.

No more messing about with mounting and remounting and changing settings, just have people drop on the files and run the update option in the menu.

EDIT: The major advantage of this, is that normally you can leave the update file alone and just work in the base image for updates, no need to rebuild 6 times

FYI update will be hidden unless you actually have an androidupdate.tar in /andboot during startup
[Touch CDMA Android Development] jamezelle:
cool this is going to be great for themes:D just run the update to replace the framework-res or whatever so you can theme on the fly while keeping userdata in tact:cool:
[Touch CDMA Android Development] CyCLoBoT:
Alright so I have been trying to flash the ROM using this method and I have come farther than before. When I select the first option, Install System (Option 1), I get the following error messages:

Formatting...

Segmentation fault

Failed

Failed to format

unmount: can't unmount /system: Invalid argument

unmount: can't unmount /data: Invalid argument

What's causing this? I have a blank sdcard with 2 partitions (FAT32 and Ext2). On the root of FAT32 partition I have the andboot folder with the tar file inside it. I used the 320x480 nbh file to flash it first.
[Touch CDMA Android Development] vilord:
segfault? eew i was hoping never to see that.

you picked the SD partitions option for the locations, right?

this might be an e2fsprogs bug

Oh you don't have a data partition, that might be a bug in the menus that I was going to investigate later.
[Touch CDMA Android Development] manu33xtro:
Well well I can't flash my Polaris... Impossible to use any package !

I'm disappointed too...

Any chance to have maybe a .nbh for Polaris because all of the package for Kaiser or vogue works very well in Polaris but only (now...) with Haret !!!

Thanks and very good work I think
[Touch CDMA Android Development] CyCLoBoT:
vilord, was that directed towards my comment? If so, I selected NAND option for both system and data in the menu.
[Touch CDMA Android Development] JeckyllHavok:
@vilord:

I trie to make this running on kaiser.

First i got the:

Failed to found system.img on SD Card, and it stays with a blinking _

then i uncommented all the if system.img, ext2, sqsh things in

/tinboot/initrd-mini/init file and it goes over to Failed to find rootfs on sdcard

/bin/sh: can't access tty: job control turned off

then i come to a #shell

any idea how to fix?
[Touch CDMA Android Development] detour522:
one quick question... how long is it supposed to take to install the system for the first time? I d/led the basefiles and launched using the haret method but i've been sitting here with the screen printing some numbers for the past 20 minutes or so.
[Touch CDMA Android Development] JeckyllHavok:
Do you get just numbers?
[Touch CDMA Android Development] polyrhythmic:
I've talked to the DIAM/RAPH devs, they seem stuck on having a rootfs. Good luck convincing them otherwise.
[Touch CDMA Android Development] mrkite38:
Oh, lol... I didn't account for self-inflicted rootfs, I'm sorry.

EDIT: done laughing - why do they want rootfs?
[Touch CDMA Android Development] polyrhythmic:
What I heard is:

"ROM builders shouldn't have to worry about hardware drivers"

"We already have an automated build system, 15MB downloads to update a single file are not a problem"

"Not having a rootfs would confuse users"

Doesn't make sense to me, but I'm glad I don't have to deal with it. Thanks vilord!!
[Touch CDMA Android Development] mssmison:
I'm glad I convinced Vilord to get rid of it :) It was a good idea in the beggining when we were all just learning, but now that we have so many talented people putting out builds we don't need to worry about it :)

The goal with android on the vogue/polaris etc is to get it looking and running like it originally came with android. :)
[Touch CDMA Android Development] mrkite38:
Sooo it was a mistake to pickup a diamond today? :p Well, maybe I'll manage to convince them...
[Touch CDMA Android Development] polyrhythmic:
Let me know how you like it, I'm thinking of picking up a Tilt 2 since the price for an N1 on AT&T is still too high for me.

I think they'd have it much easier if they'd adopt our install system, they're having the same old hassels we did with squash files and multiple rootfs versions. A couple guys have asked how to port OpenEclair to DIAM/RAPH but since it would require them to make multiple mods to the rootfs it's more complicated than it should be.

Not to mention, being able to update builds with a tiny androidupdate.tar is quick, painless, and awesome.
[Touch CDMA Android Development] mssmison:
no mistake,

Just get rid of the rootfs yourself :) It's only editing the init script and moving path's files that you'll need to worry about.

Vilord already did the hard work, just follow his lead.. hehe

I've thought about picking one up as well.
[Touch CDMA Android Development] mrkite38:
Good point, I will try that very thing. :)

The extra 64MB of RAM and 20% better proc shouldn't hurt either!

Tthis one's probably a little beat up, but the Vogue will still be my day-to-day phone until diam has caught up android wise. $55 shipped, everything included. Not too bad. anyway.

</Off-topic>
[Touch CDMA Android Development] mssmison:
yeah that's a really nice deal :)

Let me know if there's anything I can help you with.
[Touch CDMA Android Development] mrkite38:
Likewise. Wonder how the legend rom would do on here?

We'll find out. :cool:
[Touch CDMA Android Development] mssmison:
you've got enough ram on that to use the other sense 2.1 build from the eris. It's faster than the legend build.
[Touch CDMA Android Development] sshark:
Kite - where did you find Diamond for $55 ?? I might grab one for myself ;)
[Touch CDMA Android Development] mrkite38:
Ebay, believe it or not. I found one that was a little worn (don't mind that!) listed a $45, no bids, with 12 hours left. I ended up being the only bidder and won it for $45 plus $10 shipping. Even if the esn's bad it'll be worth it. According to the post, though, everything works, there's the odd time where the screen blanks if it's kept in a pocket (which we're not supposed to anyway, right?) Lol... seems there must be something more wrong with it at that price! For reference the buy it now price was $90.

But I bet if you keep watching you can find another for 50-60, they're two generations old now. There was one with a working but cracked screen for $35. I can't believe how much people are asking for Apaches still, there were a number asking $100+! Ridiculous.
[Touch CDMA Android Development] myn:
I don't believe they have the 2.1 ported yet.

I tried MS's Legend on my wifes diamond last night for giggles and it failed with umteen errors.

But still

The diamond is certainly a fun device. You'll love the resolution and speed.
[Touch CDMA Android Development] mrkite38:
Well, the joke's on me - I was just looking at the listing to contact the seller for an update when I noticed... it's a touch pro. which is fine with me, I like keyboards. plus I get 512 MB ROM! nice. other than that they look pretty much the same

which is how I made the mistake in the first place.

:o

Off I go to the raph boards to read up...

/me gives himself "genius of the week" award
[Touch CDMA Android Development] smarcin:
Also check out the thread at PPCGeeks:

http://forum.ppcgeeks.com/showthread.php?t=104276

The thread here at XDA is more GSM-oriented, though the builds are merging somewhat...
[Touch CDMA Android Development] thoughtlesskyle:
mistake post please delete
[Touch CDMA Android Development] hrywko:
hello. how much free space do I need? I only have 512mb SD-card... and only 330mb free...
[Touch CDMA Android Development] mblaster:
If you use ext2 partitions it *might* work. Try something like 200MB Fat / 150MB ext2 / 150MB ext2
[Touch CDMA Android Development] hrywko:
can you explain me what is "ext2 partitions" and how to make it work...? :)
[Touch CDMA Android Development] JM-PDA:
I am no expert, but here is what I know...

Android runs on the Linux operating system.

Linux runs better with its native partitions (rather than using Windows FAT32 partitions).

When I first got started running Android, I ran without EXT2 partitions.

However, after creating and running Android with EXT2, it:

- ran much faster

- significantly reduced freezes and unplanned reboots

- data.img (your data file) significantly less likely to get corrupted.

Here is a good tutorial for creating EXT2 partitions:

http://xdaforums.com/showthread.php?t=619290

Let us know if any other questions.

Enjoy!
[Touch CDMA Android Development] hrywko:
Thx 4 the explanation. I will try that later. ^_^

Or I will buy 4gb SDcard ASAP =)
[Touch CDMA Android Development] iggypop:
right anyone got the answer to this one- i have created Fat32/ext2/ext2 on a new 2gb micro sd through gparted live -

problem is warm eclair stubbornly refuses to use the ext partititions and installs all to FAT32 ?

i am using odexed version of warm eclair for speed.

any ideas anyone ?

ian
[Touch CDMA Android Development] xpurtwitness:
mounting error

Hi, thought it was just about complete--but my TyTn II is hanging on:

init: Unable to open persistent property directory /data/property errno: 2​

Any ideas?
[Touch CDMA Android Development] KrisM22:
I just downloaded Vogue (Kaiser) for my Sprint Mogul (Titan).

I get the message "failed to reach system.img on sd card"

I saw this problem noted a few times earlier in the thread but I did not see a fix...

Help!

tnx! :D

I put andboot from Final on the SD card in /sdcard/ and got prob.

I added android from base files, with no change.

EDIT: I put rootfs.img from android into andboot, and that get by that - now I have great difficulty getting my keyboard to communicate with the installer.

EDIT: I can manage to get it to start the installer but it goes to message formatting... and just sits there forever... whether or not I tell it to clear data...
[Touch CDMA Android Development] thoughtlesskyle:
i have tried these builds on a mogul before to be honest its a waste of time, they simply dont have enough ram to run smoothly
[Touch CDMA Android Development] thanhnhan176:
You may not post new threads

You may not post replies

You may not post attachments

You may not edit your posts
[Touch CDMA Android Development] detour522:
this is the last line on my screen right now...

"[ 3876.321362] r5:00000000 r4:00000000"
[Touch CDMA Android Development] jamezelle:
just press up or down on the dpad it should bring up the menu that means its done then hit quit and it should load
[Touch CDMA Android Development] detour522:
wait... so how do i know when to press up or down on the dpad? do i need to look for a certain number? what do these numbers mean?
[Touch CDMA Android Development] drewden123:
he just means when those numbers show up and everything is stopped hit up or down to bring the menu back up and hit quit.
[Touch CDMA Android Development] SuperJMN:
Hi Vilord! Regarding Polaris, is it normal for it to vibrate two times after booting with HARET? I'm using the ext2 file system.

After HARET, the video mode enters really slow: It starts after 40 seconds after the progress bar is filled up.

Later, I didn't see any message waiting for a VolUp or VolDown :S it just hangs in the line that says:

I'm using all the files that you recommend (for haret folks, and a .tar in a /andboot/ subfolder).

Thanks for your great work!
[Touch CDMA Android Development] jamezelle:
try it again hold the vol up till it loads the menu then set where to install the system ext2 or sdcard(if you have the partitions) then hit install system when its done you might see a bunch of numbers hit up or down or what ever to show the menu again then hit quit it should boot into android
[Touch CDMA Android Development] SuperJMN:
No luck with my Polaris :(

NOTES:

- POLARIS (POLA100)

- /andboot folder into the root of the card.

- File System: 2 ext2 partitions just formatted (empty)

- basefiles.zip from http://sourceforge.net/projects/androidhtc/files/TheNewWay/basefiles.zip/download into /andboot

- Android 2.1 (mssmison's) from here: http://sourceforge.net/projects/androidhtc/files/TheNewWay/eclair.zip/download (DOWNLOADED a few minutes ago) also into /andboot.

- I hold Volume Up from the time that HARET starts to fill the progress bar until the error comes up: "Unable to open persistent property directory /data/property errno: 2"

- I don't release Volume Up during the process.

- default.txt: I renamed default-polaris.txt.

I don't see any installer :(
[Touch CDMA Android Development] jamezelle:
its just not recognizing your vol up, is what i see. hopefully vilord can fix that up for you guys
[Touch CDMA Android Development] vilord:
i think the problem is that polaris must not be registering the keys the way vogue does (i'm not sure if kaiser does either)

I'll have to modify the kernel a bit to get that going, I didn't realize it was vogue specific :(

In fact, i don't know if it even works with haret mode on a vogue... has anyone seen that work?

Jekyll, this stuff is based on the initrd folder, not the mini-initrd folder. mini-initrd is specifically for the nand-boot on vogue.
[Touch CDMA Android Development] Barogi44:
I can confirm it does work with haret. i never got a choice on where to install files so i just hit ok to the install system and the data. the only issue i have seen with the 2.1 build is that when you choose to power off the phone, it doesnt turn off it just hangs, and you have to use the soft reset button.
[Touch CDMA Android Development] ryomahino:
Can you please post, how you do that step by step and what files do you use?

I´m using a Kaiser.
[Touch CDMA Android Development] garringm:
On my tilt I could not get this NBH file to work it would flash but wouldn't let phone boot. as far as all the older NBH files I would have to use a different key to get into the recovery mode, cant tell if its the up on dpad or vol down. one of them two does it. Would be super great if someone could get these nbh files to work properly on tilt though.

As for developement in general the lcd density is set in the default.prop can the other display settings be set in there as well or is it only the nbh file that controls this, how about other settings such as the tilt keyboard
[Touch CDMA Android Development] JeckyllHavok:
i made a modified version of the new nbh for our kaisers, but i can't start the Install menu, i think there are some modifications needed to get this with our phone working
[Touch CDMA Android Development] Barogi44:
i have a vogue. it looks like kaiser isnt working yet and i just followed the exact instructions on post 1.
[Touch CDMA Android Development] Kiiv:
Exactly the same for me (on a Polaris) :( Tried with the tattoo build.

But I don't really know when I have to push Vol Up ^^ Before hit on "Run" or during progress bar, or during boot...
[Touch CDMA Android Development] smarcin:
Did you partition with Fat32, ext2, ext2 or just one Fat32?
[Touch CDMA Android Development] BigBadBuu:
Nice work on all of this--I'm getting lockups, though, once calibration ends.

I'm running via Haret, and tried both SD and EXT installations... :(

Herup~!
[Touch CDMA Android Development] mssmison:
if you check the init file it's reading keys for the vogue, it should just be a matter of adjusting those read values.. Though I think you'll have to do them in the installer source as well.
[Touch CDMA Android Development] loserskater:
I'm also looking into getting this working on kaiser... I found this in the init:

if [ `cat /sys/class/vogue_hw/keys` = "2" ]

is this the only thing that needs to be changed?
[Touch CDMA Android Development] krwilson:
The only way I have been successful to get the menu on my VOGUE is to rock back and forth on the volume UP and DOWN staring right after it starts to load LINUX. Then the menu pops up. I had no success holding the volume just UP or DOWN. Maybe I am missing something but it gets me to the menu!
[Touch CDMA Android Development] drkow19:
I'm using this new install method with mssmison's eclair build. It is really cool and I have no complaints. Thanks for all of your hard work on this, everyone involved.

I boot from Haret. Do I need the vogue-480.nbh file in my /andboot folder? I have it in there now and it works fine. That file is how we get the new openGL driver to work, but I just don't know if the Haret boot actually uses that file. Thanks.
[Touch CDMA Android Development] JacenSolo2001:
Any chance of posting your work for the Kaiser/Tilt once you get it perfected?
[Touch CDMA Android Development] mssmison:
you'll need a new zimage if your using the old method..

really though I'd suggest running from your nand as it's the fastest method.
[Touch CDMA Android Development] JeckyllHavok:
Sure, will post if it works