yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] mblaster:
Unfortunately not on Nike... I got into the installer by removing the key pressed check and i could not do anything. After 2 minutes there was a message that it had been hung up for more than two minutes, so i am not sure if it was the keys not working or the menu crashing. I will have another try with loserskaters method.

€: OK, i get into the menu with loserskaters init, but the menu gets shifted up on the screen by messages like:

[somenumber] mdp irq on already on 4 4
[anothernumber] mdp_dma_to_mddi: busy
...

I can trigger those errors by pressing keys. They get more and more if I press keys randomly. No interaction with the menu is possible, I even can't get rid of the warning dialogue...
[Touch CDMA Android Development] SuperJMN:
I installed two different builds and it happened the same: the touch screen doesn't work. Any solution?
[Touch CDMA Android Development] Kiiv:
You can try to use an older kernel like Timmey said.

But I didn't tried myself ^^
[Touch CDMA Android Development] SuperJMN:
I give up :( Too many incompatibilities with Polaris for the moment. I hope DZO and vilord could test our devices.

I no longer have any functional Android because of the sleep/audio/wifi lockups.

Please, help us. Our forum is dead since there are no more updates.
[Touch CDMA Android Development] mblaster:
Short question on istalling apps through the menu/installapps_script:

The apps go in a folder named ./data/app and this folder goes in androidinstall.tar? Then the apps are installed on boot? Right?

€: OK, forget about that- I think the way to do this is in an androidupdate.tar in ./system/app (at least it worked with the update for eclaire and the live themes)
[Touch CDMA Android Development] vilord:
okay i figured out that kaiser and polaris use the camera key instead of volume up.

Nike has a totally crazy matrix keyboard so it'll take me a little while to get that implemented.

Can someone with a kaiser or polaris test the original initrd.gz with the camera key held down at bootup to see if it launches you into the menu?

I'll bring it up on my polaris this evening so long as nothing comes up to keep me at work for 10 hours again...

wifi is up to the build dev to handle now, but data/voice should be working, and I'll investigate why it isn't.
[Touch CDMA Android Development] GriloVirante:
I just tried on my POLARIS to boot HRET keeping the camera button pressed and pressing it multiple times. The effect is the same like with the volume-up, with the only difference that the camera button is actually "perceived". That means that every time I press it, a "^[[1" appears on the screen. But no effect, so that I end up in:

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

Failed

Failed to reach system.img on SD card

I tried to press the camera button during the 40" of screen apparently locked (when HARET is launched in WinMo, but no black Linux screen is yet on) and even afterwards, in teh 10-15 seconds it takes to the init process of Linux to get to the above error messages.

Sorry for the bad news, please don't leave us alone! :)
[Touch CDMA Android Development] vilord:
darn... well i'll have to fix that asap (tonight).

For Nike's with the 20-key, try the attached initrd.gz (unzip first)

i don't have a nike so i have *no* idea what will happen, if anything.
[Touch CDMA Android Development] Vagabondage80:
I held the camera button down on my kaiser as I loaded Haret, but no effect. I also tried loserskater's fixed init but it prevented Haret from loading at all (froze on blue bar).

Frustratingly I only need to boot into Haret once so I can set up my wifi. After that I would just use Nand.

I appreciate all the hard work here, though. Thanks everybody!

EDIT: Okay, vilord, the initrd you just posted worked right away! Booting now.
[Touch CDMA Android Development] GriloVirante:
@Vagabondage80, watch out the "freeze" on the blue bar. On my polaris teh blue bar of WinMo when launchign Haret lasts no less than 40 seconds, then the black Linux screes starts scrolling OK. Did you wait so long at least?
[Touch CDMA Android Development] ritzky:
vilord, while u're at it, i wonder if u can give us nike users a solution regarding our issues with waking the device after sleep set to 1, since it is the only mode which gives decent battery life. after it sleeps, no button will wake the device. Thanks a bunch! :)
[Touch CDMA Android Development] mblaster:
Don't know for sure, but I think for some builds it got better for me when undoing the changes from commit 69e429d80c61b6507d8011ee2f7836cd0455fcaa in the kernel. But i have not applied this to a more recent kernel yet...

I could track it down to that commit because I had two precompiled kernels, one with working suspend, one without, and this was the only change in code relevant for powermanagement in between.

Hope this helps...

@vilord: trying the initrd
[Touch CDMA Android Development] garringm:
@vilord is this initrd supposed to work through haret, if so does this install to nand.

On another note I have been trying the nand norootfs install with loserskaters nbh files. I think there is an issue with accessing files in /system/bin I get a lot of issues that says file does not exist. I try to use adb shell and get a cannot execute /system/bin/sh file does not exist, but I look in tar file and all these files are there. Could this be part of the problem with no data on a tilt.
[Touch CDMA Android Development] mblaster:
OK, It doesn't work yet. I would suggest the following change in init:

read -s -n[COLOR="Red"]4[/COLOR] -p "Press dpad up to launch the installer" -t 5 keypress
if [ $? -eq 0 -a "$keypress" = "[COLOR="Red"]^[[A[/COLOR]" ] ; then

I have no linux box around to make the initrd atm, otherwise I would have tried myself.

€: My suggestion doesn't help either...
[Touch CDMA Android Development] Vagabondage80:
Should there be wifi when booting with Haret? I tried out the Tattoo build (which was great) but was unable to start wifi. I have a kaiser.
[Touch CDMA Android Development] vilord:
wifi is up to the system to handle. If it works in the system it'll work no matter haret or nand boot... I'll have to investigate why it doesn't work with tattoo.
[Touch CDMA Android Development] Taluven:
@Vilord:

Been trying to use the .nbh files from the 1st page, model 100 AT&T Tilt. They all give me the same error when trying to flash them to nand. I get "Unable to update your device, Incompatible model#". I only get this error when using the vogue images on teh 1st page. I am sure they are incompatible with my tilt, but was wondering if this is something you could look into.

I really like the idea of the new method of loading and currently have a donut build going with some of the initial tinboot images. If there is anything you can do, it would be appreciated.
[Touch CDMA Android Development] loserskater:
You can't flash a different model phone's NBH to yours. You should be careful with that because you could brick your phone.

If you read through the thread or look in the kaiser (which is what the tilt is called) threads you'll see that I've got these working on the tilt. If you're on AT&T's network you won't havea data connection. Its currently being looked into though.
[Touch CDMA Android Development] Taluven:
Thanks loserskater,

I do read the kaiser threads a lot, but didn't see the correlation, I will have to go back and read them again I guess.
[Touch CDMA Android Development] flaviusio:
Hi!

I have a Polaris 100 and with Eclair 2.1 and the new way of booting android(without rootfs) my phone stuck after creating the new data file and it says this:

"ANDROID [ 79.382590] init: Unable to open persistent property directory /data/property errno: 2"

Can I use this system on my phone?
[Touch CDMA Android Development] Vagabondage80:
vilord,

I appreciate you taking a look at it. I've booted up your tattoo build both as haret and nand, and it's the build I've been looking for since I got here. The wifi is the only problem, as it says "Unable to start Wi-Fi" on both. I don't have a data plan, so this is pretty essential for me. Thanks for all your great work.

EDIT: I've tried multiple builds, but no wifi.
[Touch CDMA Android Development] lupick:
kaise hang on boot

Dear All.

on my kaiser I'm traing to install eicar on ext2 sdcard using latest basefile.

it hang on

A N D R O I D

I've tried to keep pressed camera or volup but no luck

same issue with tatoo build

Any Idea?!?

thank you

L.
[Touch CDMA Android Development] loserskater:
Try taking out the battery when it gets there and then boot back up. If that doesn't work try reflashing the nbh again.

same thing with persistent property directory. Try reflashing the nbh
[Touch CDMA Android Development] rzk333:
tried that on 16key nike, still no progress:

Checking for partition...
mkdir: cannot create directory '/system': file exists
Nike detected
Press dpad up to launch the installer
sh: 2: unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
[Touch CDMA Android Development] lupick:
thanks for you reply but I'm traing to install android on SD Fat32/ext2/ext2/Linuxswap partition.

so acording with first post I have on my nadboot dir only:

Basefiles (default.txt edited for kaiser)

androidintsall.tar

androudupdate.tar (240x320 fix)

but it hang always on ANDROID, holding camera button or not

what I'm missing?

thaks L.
[Touch CDMA Android Development] vilord:
okay i need some new information before I can get this to work.

I need a kaiser and a polaris user that has a booting android phone (not with my methods) to do this:

open an adb connection to your phone (you'll have to get things running with a different initrd first)

while true; do cat /sys/class/vogue_hw/keys ; sleep 1 ; done

While that is running hit various keys on the phone and tell me what numbers show up related to which keys (i.e. what do you get from camera, power, volume, etc)

a nike user could try this for me too, but i'm guessing we'll just see 0 all the time... for nike, if someone has it booting up to a failed state and they can try hitting dpad up/down/left/right and enter (if you have an enter key), what shows up on the screen? do you just see ^~ or something, or do you see [[A2 or something like that?

Thanks, hopefully we can get this going soon, then i can focus on the data and sleep issues for nike/polaris
[Touch CDMA Android Development] garringm:
On my kaiser / tilt all I get it a number that continues to scroll, the buttons don't seem to be affecting anything

248 is the number

Your help is much appreciated you are the man

It is not 248 it is 249
[Touch CDMA Android Development] rishie:
I am getting 6 when I press camera key on my kaiser with the above script (randomly I am getting 2, but if I keep the camera key pressed, I get 6 printed continuously)

Values printed for the Keys:

Dpad Up - 16

Dpad Left - 64

Dpad down - 8

Dpad right - 128

Power key - 1

Camera Key - 6

Remaining keys giving 0 all the time....
[Touch CDMA Android Development] rzk333:
dpad up ^[[A

dpad down ^[[B

dpad left ^[[D

dpad right ^[[C

voldn ^[[26~

power ^[[4~

other buttons ^@
[Touch CDMA Android Development] galky:
polaris

Hi,

for polaris you push power button, and boot menu works(NAND and SD).

The issue is that Wifi is not working now.

I try several builds.

So it seems not depending on the system?

Regards
[Touch CDMA Android Development] vilord:
garringm, your phone maybe has an older kernel on it?

rishie, you're getting 6 and sometimes 2 because camera shallow press == 4, camera hard press == 2, and most of the time you have a shallow press before a hard press.

I think i'll switch things over to the power button so everyone is the same (kaiser doesn't have volume up)...

nike will 100% need to be done differently...

does whomever has a nike 16-key... you don't have an enter key, do you?
[Touch CDMA Android Development] Yaantra:
Looking forward to your patched file. Cannot wait to run Myn's latest warm donut on my Kaiser... Thanks
[Touch CDMA Android Development] myn:
The previous rootfs dynamically supported each device (Kaiser, vogue, Polaris) etc by assigning a specific sysinit.rc. This was nice. 1 rootfs for many devices.

I just released my latest iteration of Warm Donut and now have to include separate updates to sysinit.rc for different devices to address the separate configurations.

Are there any plans to consolidate some of the common references and/or bring it back to support all devices?

I know my users are very confused. Now having to install base, than install multiple updates just to get it running.

Thanks
[Touch CDMA Android Development] mssmison:
No there is not. There are two files that need to be changed between vogues and devices with wifi. a small update.tar is all that is required.
[Touch CDMA Android Development] Yaantra:
Would you please instruct as to how to apply your attached init file to the initrd.gz? Thanks in advance, and sorry for the noobish question
[Touch CDMA Android Development] SuperJMN:
I circumvented the problem flashing my device (Polaris). It works like a charm.

But I have a question:

If I have a filesystem composed of 3 partitions (FAT32, Ext2, Ext2), which option should I choose in the Android Installer (menu based) to install the system using the two Ext2 partitions? (one for system, other for data)
[Touch CDMA Android Development] Yaantra:
See that's something i can't do as i need exchange calendar support for work everyday. Really waiting for a full exchange support on Android before i make a somewhat permanent shift.
[Touch CDMA Android Development] ritzky:
i'm using 16 key nike, the enter key would be the center of d-pad, i guess... using the old method voldn is working just fine, though.. Thanks
[Touch CDMA Android Development] garringm:
To be real honest its not the installer I am having problems with, loserskaters nbh files work quite well on my tilt. And with the original rootfs based installers that seemed to only be for a short time the volume up did work for me. well it was actually the right soft key next to the dpad. Its the lack of data when using these nbh's that is keeping me from using android installed to phones ROM
[Touch CDMA Android Development] lupick:
Worn email on sqps missing - cannot install it!!

wrong thread
[Touch CDMA Android Development] tatnai:
system on sdcard, and data on sdcard. ironically, the sdcard options that say ext2 do not install to ext2, they will place the data.img and system.img into the andboot folder.
[Touch CDMA Android Development] vilord:
okay I've uploaded new nbh files, zImage, and initrd.gz to the following:

https://sourceforge.net/projects/androidhtc/files/2010-02-04

I have *no* idea if polaris actually works booting from nbh, it might blow up your phone! I'm just throwing it all out there (this includes a bunch of work by Martin over the past weeks)

Using the new zImage and initrd.gz from that location, you should be able to get to menu from the camera key on kaiser and polaris, from volume-up on vogue, and from up-arrow on nike (please let me know if this is true or not!)

This should work with either haret or nbh booting.

If all is good I'll update the OP.
[Touch CDMA Android Development] tatnai:
is resolution still stored in the .nbh, and if so, what is the resolution and difference between voguenbh.zip and vogueeclairnbh.zip? any changes to these from the Jan 29 files?
[Touch CDMA Android Development] mblaster:
Works on Nike 20Key, but the menu jumps up and down due to some error messages. Nonetheless it is perfectly usable. Nice work, thanks!
[Touch CDMA Android Development] kokEA:
Doesn't on my 16key :/

Nonetheless there is some progress here too. I am now able to get into the menu by pressing up, but not any further. I can't seem to press the "ok" button in the welcome screen with any key.
[Touch CDMA Android Development] mblaster:
On 20key it is done with the Enter key, which you lack. Perhaps it is possible to remap this to Dpad center?
[Touch CDMA Android Development] garringm:
Is working on my tilt now even have a data connection on your sense tattoo build. One small thing though can you do the nbh files with tilt keyboard enabled or is there a command I do in terminal to change this.

Tried the eclair stuff this time it works as its supposed to. I am having issues getting logged into market with both sets of nbh files. Keep getting message Can't establish a reliable connection I will try again later. Now I can get up to speed with the rest of the community.
[Touch CDMA Android Development] mblaster:
I also have some improvements on data connection. Modem app tells me now that i got an ip. In the browser the up arrow in the 3g logo keeps on blinking, but not the down arrow... seems like i have a one way connection now :-)
[Touch CDMA Android Development] j101399j:
Edit - Ok it's working, I tried one more time, moved everything into /sdcard/andboot and just held the camer button all the way down for about 2-3 minutes and the menu loaded. Cool; thank you for the great work !!!

I am in no way complaining, just hoping to give some feedback, hope it helps and amaybe a question; thank you for the great work

I've got an AT&T tilt just downloaded the new 2-4-2010 basefiles and the ([Android] Eclair 2.1 Fully working, tweaked for vogue, UPDATED) androidinstall.tar.

Using HaRET (not flash) and no matter where I place the files or what key I press, I can't access the menu.

I have pressed the camera 1/2 press and full press quickly and held it till the boot says can't find system.img; I have also tried the right soft key (android volume up), power key, up on the d pad and so on and all with of the following file locations

1. all in /sdcard

2. all in /sdcard/andboot

3. Basefiles in /sdcard and andinstall.tar in /sdcard/andboot

4. all in /sdcard/android

5. Basefiles in /sdcard/android and androidinstall.tar in /sdcard/andboot

Yea I know a lot of tries

I have also tried to get the key numbers with the "while true; do cat /sys/class/vogue_hw/keys ; sleep 1 ; done" command in adb after entering adb shell and I just keep getting

cat: can't open '/sys/class/vogue_hw/keys': No such file or directory

Maybe I'm missing something basic? Anyone with a tilt that has had this working, please advise?

PS I would like to stay away from Nada (I know it great and have tried :D ) but I need some windows programs and must go back every once in a while
[Touch CDMA Android Development] cyburke:
PLEASE pardon my ignorance here on this one... i've flashed my Vogue before and running an NSFAN rom presently.

i've been playing w/ the Android ROMs out now, but always via SQSH on SDCard...

does the NoMoRootfs method actually install Android to my device and wipe WinMo completely off of there - or is this something else that I'm not fully aware of yet?

reason, i want to play w/ the WarmDonut latest release but it's not running via standard SQSH on my SDCard so i figured i would try the NoMoRootfs method he has uploaded - but not totally sure what it does!!

thank you for the quick response which will surely answer my question.

:)
[Touch CDMA Android Development] dzo:
Polaris does work but you need to press the power button rather than cam button to get into the installer.

I also wrote a script to make all possible combinations of kaiser panel types/resolutions and keyboards. Get them from here:

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
[Touch CDMA Android Development] flaviusio:
We should thank them for the hard work and "how tired their brains are" and I think our fingers is the last think we should worry about.

Many other things must be adjusted(BT,WIFI,GPS...) and improved and they are more important than the button we must press.

This is my opinion....and btw,I have 10 fingers :)),so I'm not complaining!
[Touch CDMA Android Development] prairiefire:
Thanks Dzo!
[Touch CDMA Android Development] zc2:
Change old system to the new way

I'm trying to adapt the old Ion build to the "new way" on my Tilt. I copied the files from the rootfs to system as instructed, but I don't understand what should I do with that sysinit.rc. Vilord says "modify the sysinit.rc a bit", what exactly that "bit" is?

If I do nothing with the file (except uncommenting the etc symlink creation), the system boots, but never goes to the GUI.
[Touch CDMA Android Development] loserskater:
You beat me to it... I was going to make a script myself.

Thanks
[Touch CDMA Android Development] a5ehren:
I'm having a problem - here's my bootlog

sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 532/65536 files, 83185/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 11/65536 files, 8286/262144 blocks
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory

After that I get

VOGUE ANDROID [83.509803]
init: unable to open persistent property directory /data/property errno: 2

but it doesn't get into the bootlog for some reason. I used the latest basefiles to install via haret on a normal SD Card (just a big FAT partition). Any ideas?
[Touch CDMA Android Development] mssmison:
Activating the menu has nothing to do with long pressing, it's just checking to see if you happen to be pushing the button when it checks.

The reason we moved away from the 'press down to enter the installer' idea was for faster seemless booting. We've removed the additional 3 seconds of boot by changing it to this way. The plan is to make android boot seemlessly like it would on a standard android device.

And we can all appreciate working on it for two hours. I have days where I'm literally rebooting my phone every 5-10 minutes for hours at a time, while I'm working on updates, new builds, kernel updates etc.
[Touch CDMA Android Development] vilord:
dzo: polaris and kaiser should both be using camera with my latest kernel updates from this morning.

regarding nike 16key: This will unfortunately need a little more work *sorry* basically the two methods I have to access the keys are

1) direct GPIO access from dzo's /sys/class/vogue_hw/keys (only works for non-matrix buttons)

2) indirect access from what are standard keyboard commands (up, down, left, right, enter, etc)

kaiser, polaris, vogue all use direct GPIO, as they don't have an enter key.

nike 20key has an enter key, so it uses indirect.

nike 16key uses all matrix buttons AND it has no enter key... so I have to fix #1 to work with matrix buttons, or #2 to fake an enter key...

maybe I can use some kind of && or something to get what I want from matrix, but it'll take a bit to get right.

Why do I have it set up for hold-down-the-button? Because it is easier for me to hold down the button while it is booting than it is to wait for the right moment to push it and forget and miss it.

In the next rev, I'll include a hint that shows 3 secs before it be pressed.
[Touch CDMA Android Development] vilord:
this forum is poop. post + mirror (tsop) = poop
[Touch CDMA Android Development] jamezelle:
lol bored huh?:p
[Touch CDMA Android Development] mrkite38:
I'm no expert, but go back to that post and check the part about uncommenting a symlink. I think that may be what you're missing (because I just did the same thing.) :o
[Touch CDMA Android Development] zc2:
No, I've modified the line with the symlink right away, because it was clearly specified.

I'm confusing about all the other changes I need to do in the sysinit.rc file.

Currently, I found out the userinit.sh is missed.

I've copied it to the /system/bin folder and changed the sysinit.rc in the line where it mentioned.

Also, there need (?) to be change the path to /lib/libhtcgeneric-ril.so

Probably, that's it.

So, the system starts properly now, except the following issue:

When I use the newest zImage (after 2010-01-14), GPS does not work at all.

Even the GPS icon is not shown.

How can I fix that?
[Touch CDMA Android Development] mssmison:
nothing other than the symlink of /etc should stop you from booting up.