yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] chourmovs:
i succeed booting and installing myn's release via haret and nomoroot menu on my pola100 but all the booting option were not functioning and i couldn't access the menu each time i boot, it apparition seems very odd...

maybe a bad synchronization when pressing volume button ...

is there a way to script apparition of boot menu with haret ??

also i couldn't choice where to install the system (by default in andboot but i wanted it in root of my sd card) and all the other line in menu were useless for me (giving error message)

Anyway, very good work from villord, dzo ,msmission, myn's and all androidonhtc community

you rule the area buddies !!
[Touch CDMA Android Development] vilord:
hey good point, I'd been planning to push out a repo for busybox with all my changes :)

I'll do that asap
[Touch CDMA Android Development] vilord:
chourmovs, the menu should come up with the camera button on your polaris :)

as for placement of the files, I'm not interested in supporting multiple locations at this time. feel free to move haret, zImage, initrd and default.txt to sd root, but the image files will stay in andboot.
[Touch CDMA Android Development] bzo:
great, thanks! :) I was playing around with it on a diamond, but it wasn't recognizing the key presses, so I figured some tweaks were needed with the keystroke mapping.
[Touch CDMA Android Development] chourmovs:
oups sorry i wanted to say camera button

but most of times, menu doesn't appear

when, and for how long, i have to press camera button exactly ?

after pressing run, before pressing run, after the double vibration ?
[Touch CDMA Android Development] dyetheskin:
i did as the 1s post said to do,tar file in andboot folder on top level of sd,flashed nbh through usb and through direct bootloader on my kaiser,no go except lots of code,tried left soft key and camera hoping installer would start,tried with myn's warm donut build
[Touch CDMA Android Development] tatnai:
there is a specific answer in my FAQs for this, how to flash to nand, see if you got all of the steps in there. (see my signature)
[Touch CDMA Android Development] vilord:
Are you all using the nbh files from the polarisnbh.zip and kaisernbh.zip sets? There was a late change that fixed entering the menu on polaris and kaiser...

-Jesse
[Touch CDMA Android Development] dyetheskin:
i have a kaiser and took the 480 version with panel2 from the 1st post of this thread
[Touch CDMA Android Development] chourmovs:
up

Please i'm getting mad trying without success

yesterday i succeed two times to get into the menu but today i can't find the right temporisation :confused:
[Touch CDMA Android Development] flaviusio:
Hi

I had the same problem with the new nbh files.When entering the menu and pressing up and down for the options,after a second or two it jumps to quit,so I had to choose quickly .I restarted many times and I managed to entered 2 or 3 times(randomly),then I've switched back to first nbh for polaris from here (I use panel type 3) and now is functioning well with the power button menu
[Touch CDMA Android Development] chourmovs:
i use zimage with nomoroots and i noticed that things goes better if i retire my battery on each reboot ...

maybe problem with sdcard init
[Touch CDMA Android Development] chourmovs:
i noticed that and problem is still present with zImage from 02/04/2010
[Touch CDMA Android Development] SuperJMN:
With my Polaris and runing HARET I get an unresponsive touchscreen.
[Touch CDMA Android Development] DmK75:
I also have this issue.

I install android via Haret, reset and replace zImage to make it work.
[Touch CDMA Android Development] SuperJMN:
Which zImage do you use? Could you give me a link?
[Touch CDMA Android Development] DmK75:
I upload zImage up.

WiFi issues are not solved yet? I also tried, change configs and "wlan_loader".

Unsuccessful. Maybe driver not find "sdcard" and cannot create calibration file?
[Touch CDMA Android Development] garringm:
Question, which part of my phone is everything installed on, I'm not sure of the specs on a vogue but on a kaiser I should have 128 ROM and 256 RAM once my system is installed I only have 87mb of available space left, I dont think the installers are using the proper space am I right
[Touch CDMA Android Development] chourmovs:
zImage 02042010 break nomorootfs, i take 02022010 from http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

you have to press power button just after running haret/defaut
[Touch CDMA Android Development] SuperJMN:
Thanks! I was writing using my Polaris and I didn't see the attached file! I booted with this zImage and now the touchscreen is working, but the data connection isn't initialized.

(Using haret to boot)
[Touch CDMA Android Development] NateReal:
im using haret.

and i put the androidinstall.tar along with an androidupdate.tar w/ all my basefiles all extracted in the root of my sd card. i press and hold the volume up button but nothing comes up. it continues booting normally. is there something im doing wrong?
[Touch CDMA Android Development] MiZi666:
try to half press the camera button...
[Touch CDMA Android Development] vilord:
new files are up here

I switched again the button to enter the menu (sorry folks!)

It is now the dpad middle button for all devices, including nike.

Still needs testing and maybe some tweaks, but if someone wants to give it a shot, that'd be great.

zImage and initrd.gz for the haret folks.
[Touch CDMA Android Development] Reddog80p:
What's the newest Vogue.zip contain? Changes? Updates? Fixes?
[Touch CDMA Android Development] vilord:
each of the zip files contains a set of nbh files for that device.

What is changed is to switch to a new method of accessing the keys for the recovery mode, as well to fix recovery mode for linux systems (it uses USB disk mode)

The updated key access method should fix accessing the menu from all of the various devices including the elusive nike 16key.

usb disk mode for windows machines and adb access from windows in recovery still isn't working right, and i'm still investigating why.
[Touch CDMA Android Development] myn:
Nice work :)

I also noticed there is a new version of the basefiles (02-04-2010). What's new/changed over the 01-29-2010 basefiles?

Thanks.
[Touch CDMA Android Development] moisha:
Came out to be an easy one. MrPaveL took time to summarize it here. May need to push older wlan.ko as I figured out was my issue.
[Touch CDMA Android Development] noside12123:
Doesn't work on my Kaiser.
[Touch CDMA Android Development] JeckyllHavok:
Hey vilord,

in your new package, is the eclair system tho one fromm mssmission or is it a new one?

BTW: new nbh doesn't work for my kaiser ( can't access installer)
[Touch CDMA Android Development] samtruman:
I can confirm, no working menu with camera or middle button...
[Touch CDMA Android Development] rzk333:
nike16 still answers on dpad up to start installer, menu enter still work weird - enter is "dpad up+center+down" in multiplie presses.
[Touch CDMA Android Development] manu33xtro:
Hi,

Well, no problem for the Polaris (100) with this new package (07022010) : The central dpad works very well for access to boot menu (I press in continue after the two vibrations).

Thanks Jesse...

I wait mssmison and you for wifi, bluetooth and gps in Polaris.
[Touch CDMA Android Development] tatnai:
new .nbh works fine on my vogue, center dpad works for everything.
[Touch CDMA Android Development] moisha:
In initrd I still see

if [ `cat /sys/class/vogue_hw/keys` = "32" ] ; then

That's a camera button on Kaiser (Tilt) and works for me every time I need it. I'm using haret.
[Touch CDMA Android Development] ritzky:
im using nike 16 key and the new files still not working for me. Still waiting :) if u find the solution, will it also work for our "unable to wake up from sleep" problem? thanks
[Touch CDMA Android Development] polyrhythmic:
Thanks again vilord, ported OpenEclair to Kaiser using the files from 04 Feb, using camera button works I installed to SD card partitions. I have my userinit.conf setup to use a swap partition, but it isn't working yet... I have yet to dig and find out exactly why.

Keep up the great work! I look forward to flashing Kaiser and we thank you for your support of the Kaiser device! I'll keep helping where I can :)
[Touch CDMA Android Development] rzk333:
use "pm.sleep_mode=0 no_console_suspend" and nike will normally turn screen on/off, but board side of phone will be hot as hell.
[Touch CDMA Android Development] ritzky:
if u look few pages back then u'll know that setting sleep mode to 0 did not put nike to sleep properly, and the battery drain way too fast. only setting it to 1 would solve the battery drain problem
[Touch CDMA Android Development] polyrhythmic:
FYI, theoretically you can now build androidinstall.tar from a non-Unix system... but I tried to build off my FAT32 partition and had serious permissions issues... I'm not sure if you can set permissions from a Windows (or other) setup.

EDIT: I can't use the middle button to launch either, rolling back to the camera-button zImage works just fine.

EDIT2: Can you please build a zImage with jnadke's Kaiser GPS updates incorporated with the camera-button fix? His kernel has excellent GPS but I can't launch the installer. Thanks again vilord!
[Touch CDMA Android Development] vilord:
I'll look at incorporating the GPS fixes asap, also gotta figure out why the buttons don't work for kaiser or nike... argh.

Also, PM me if anyone has an extra phone (GSM or bell.ca), one of our good developer's phone died and we need him back!
[Touch CDMA Android Development] jnadke:
Who's phone died?
[Touch CDMA Android Development] damianiw:
Thanks for your work here, I have a kaiser and have eagerly been watching the android threads, I can say I believe with haret and your NoMoRootfs I can have the best of both - Try Android, still keep windows until I'm happy enough to move fully.

I hope you get the kaiser buttons fixed so I can try :-) is there an older version where they were working ?
[Touch CDMA Android Development] polyrhythmic:
dzo has incorporated the GPS fixes, I've tested the zImage-11-02-10 and the GPS is working great! However, I still can't get into the menu. I do see the escape character ^@ when I press d-pad center, but no matter how I hold it I never see the installer.

EDIT: Also, I have swap enabled in my userinit.conf, but Android isn't using any swap. Is this somehow due to my custom android build, or have things changed with this new no-rootfs system?
[Touch CDMA Android Development] manu33xtro:
Hi polyrhythmic. I can see the boot menu when I press vol-up !! In fact no works for dpad in the nbh of DZO...
[Touch CDMA Android Development] polyrhythmic:
I haven't found a button that works for the new zImage yet... I'm sure it won't take long to fix.

I also have a fix to make in /initrd/bin/instscripts/fixperms:

Somewhere after line 60:

set_perm_recursive 0 0 0755 0644 /system

A few lines need to be added to fix the init.d scripts and the wifi files:

if [ -d /system/etc/wifi ]; then
set_perm 0 0 0755 /system/etc/wifi/loadit
set_perm 0 0 0755 /system/etc/wifi/wlan_loader
fi
set_perm_recursive 0 0 0755 0755 /system/etc/init.d
[Touch CDMA Android Development] mssmison:
mine :( last week
[Touch CDMA Android Development] jamezelle:
mine a week and a half ago :rolleyes:
[Touch CDMA Android Development] plemen:
lol mine went through the wash last week. I took it apart and let it dry and it came back to life. Last week was bad for us vogue folks.
[Touch CDMA Android Development] jamezelle:
the charger port on mine is garbage:rolleyes:....if i feel dangerous i might try to solder the port from the headphone splitter to my vogue:p
[Touch CDMA Android Development] Reddog80p:
You got a ERIS? Man! Your supposed to hold out for the NEXUS!!!! LOL....
[Touch CDMA Android Development] jamezelle:
yea but with a broken phone and a little tax money rolling around... i couldnt wait:p.
[Touch CDMA Android Development] polyrhythmic:
Well, I discovered the problem. In addition to needing the correct permissions set in /etc/init.d , AND a userinit.conf in /etc/ , you will need a /etc/userinit.sh to process the userinit.conf!

EDIT: I'm wrong, the init.d setup expects the userinit.sh in /system/sd/userinit.sh

FACEPALM

Don't know how I couldn't figure that out before. Now fixing for my 2.1 build!!

EDIT: Now that I look at it, the new system expects the SDcard mounted on /sd. I don't know if I'll break something by changing the mountpoint of sdcard to /sd... perhaps /sd should be symlinked to /sdcard? ... what will be most compatible going forward?

EDIT2: Found a bunch more stuff about building Eclair!!!! God this would have saved me a lot of time had I found it sooner. On the new init.d: http://xdaforums.com/showthread.php?t=627417 Eclair building FAQ: http://xdaforums.com/showpost.php?p=5435361&postcount=70

EDIT3: Ok, well I can run the sysinit service manually (/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d) after boot and it seems to work fine, it just takes a while. However, without running it manually I can see in ps after boot that the service has been started, but it must hang somewhere because it never sets up swap and I'm getting too many copybit errors in logcat to see if the init.d scripts are printing their error messages. Driving me absolutely crazy... if anyone gets this working properly please PM me!
[Touch CDMA Android Development] vilord:
If you use the sysinit.sh that was included in the tattoo build, you can just call out to it in your sysinit.rc like this:

service userinit /system/bin/userinit.sh
console

BUT: You must use my sysinit.sh from my tattoo image, the older ones won't block on startup.

Also, take a look in the sysinit.sh, it direct references some modules for the compcache, make sure the libs are in the right place
[Touch CDMA Android Development] vilord:
busybox

I've also posted my changes to busybox here:

http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/busybox.git;a=summary
[Touch CDMA Android Development] mssmison:
I had it working fine, follow vilords instructions.
[Touch CDMA Android Development] En1gma:
problem solved..
[Touch CDMA Android Development] polyrhythmic:
I'm trying to keep my OpenEclair port as close to the original G1 build as possiible, so I wanted to implement the init.d system that WesGarner and Cyanogen use. It took some changes in the installer fixperms and some editing, but I've got it working very closely.

One question I can't figure out, do we ever need an appfix script? It seems to be very important for builds on other devices but I've never had to use one.
[Touch CDMA Android Development] mssmison:
You mean the permissions fix script they use. It's in the installer :)
[Touch CDMA Android Development] polyrhythmic:
I know fix_permissions is in the installer, but I couldn't find appfix (renamed to .txt for the attachment).
[Touch CDMA Android Development] bzo:
thanks! Now I just have to figure out how to have replimenu recognize the center button on a diamond, which seems to map to a mouse button press
[Touch CDMA Android Development] Spalla:
I have trouble using androidupdate.tar. I went to the Installer and clicked on Update, and it says that it's been updated successfully, but when I load Android up, it's still the same as before. Does anyone here know why it won't update for me?

Edit: nvm, I got it to work. I installed the wrong update, that's why. <_<
[Touch CDMA Android Development] vilord:
I've updated the initrd and busybox.

Replimenu now uses /dev/input/event* devices, so you should be able to just use it without modification on diamond :D

Head over here for the latest
[Touch CDMA Android Development] Reddog80p:
Menu key on boot for the newest vogue nbh d-pad center :D and it even prompts you..how nice!
[Touch CDMA Android Development] polyrhythmic:
Sadly dpad-center still does not launch the installer on Kaiser. I still see ^@ every time I press dpad-center though!

I get a new message on screen, and I found it as the first line of my bootlog.txt:

sh: 1: unknown operand

EDIT: I also see something else new:

tsts_thread: address 0x48

I've attached my dmesg from andboot, maybe that can help. I'm going to try playing with readkey and see if I can get somewhere.

Thanks again vilord, the other initrd changes seem to work great!

EDIT2:

Ok, well I made myself a little init script that tests keys using readkey, and discovered the Kaiser keys are like this:

VolDn: 114

Volup: 115

IE: 102

Mail: 155

I couldn't get readkey to read the dpad keys.

So I changed init to launch the installer on 114 (VolDn, as before). This launches the installer! But then the installer scrolls off the screen as I get endless repetitions of this:

[105.12343] tsts_thread: address 0x48

(the 105... is the timestamp of course)
[Touch CDMA Android Development] MrPaveL:
Ok, i'm confirming this. I've exactly same problems on my KAIS100.

Pavel
[Touch CDMA Android Development] vilord:
I think I know where the kaiser problems are coming from... i'll look into them in the next few minutes.

If you're running nand all the way, use the attached vold.conf (there's an androidupdate.tar in there that should work) to gain the ability to turn on USB disk mode mounting from linux machines.

Rom builders: Please incorporate this into your roms
[Touch CDMA Android Development] rzk333:
same console spam on nike16
[Touch CDMA Android Development] vilord:
polyrythmic, mrpavel: I've uploaded new versions of the NBH files with both a kernel change to silence the tsts_thread messages and an initrd change to enter the installer with either volumeup or dpad center.

Only issue left is that the dpad keys do not report key_pressed separately from key_released, so it's possible that the arrows and selectors just plain won't work.

I could investigate fixing this bug in the kernel, or I could rewrite the readkey function again to watch key events instead of scanning the keyboard, but I'd rather not do either one if it isn't necessary... can you test? are you able to navigate the menu with this latest? it is here
[Touch CDMA Android Development] vilord:
rzk333: please give the new ones a shot from the link in the previous post, should silence the spam.
[Touch CDMA Android Development] tiagoclc:
d-pad doesnt work

D-pad buttons doesnt work with newest kaise NBHs files.

To select ok button at first window in installer menu, i have to open slide keyboard and press enter.

Then, i cant navigate. I only can highlight first option (1) and last option (10), by pressing VolUp and VolDn buttons.

Sorry about my english, its very poor.
[Touch CDMA Android Development] myn:
Very cool. I am hoping this works.

Kaiser/Polaris users does this work?
[Touch CDMA Android Development] vilord:
Thanks for the report. Kaiser keys suck. whoever had the bright idea to report keypressed followed *immediately* by keyreleased is making my life hard.

There isn't even a 10ms delay or anything, it is immediate, so my readkey functions never see the keypresses (they look at current key status, not eventing).

Solution is to fix the keypresses either with a tiny delay (would make it work unreliably), fix the keypresses so press is separately reported from release (may be impossible on kaiser), or switch readkey to use eventing (a few hours that I didn't want to spend on it)

Someone with a kaiser who can compile kernels... please try adding

input_sync(kbd_data.idev);
msleep(10);

to board-kaiser-keypad.c in between each of the lines that looks like this:

input_report_key(kbd_data.idev, keys[i].key,1);
input_report_key(kbd_data.idev, keys[i].key,0);

You should only need to apply it twice, on about line 385 and 388
[Touch CDMA Android Development] myn:
I see a new basefiles was released today.

Is there a changelog for zImage and initrd.gz?

Thanks
[Touch CDMA Android Development] myn:
I just tried the new basefiles (02-14-2010) on my vogue.

There seems to be an issue with the menu system. It sometimes doesn't register my dpad actions. I am having to click things twice and hit down/up many times.
[Touch CDMA Android Development] tatnai:
me too - the first time I tried getting into the install menu with 2010-2-14 it ignored me, never got in. worked the second time.
[Touch CDMA Android Development] rzk333:
yup, now menu working fine, thanks!
[Touch CDMA Android Development] moisha:
You nailed it, Vilord !

Holding dpad middle button calls up the simple menu, up/down navigation keys do work.

# git diff
diff --git a/arch/arm/mach-msm/board-kaiser-keypad.c b/arch/arm/mach-msm/board-kaiser-keypad.c
index 5176e92..fec8a7c 100644
--- a/arch/arm/mach-msm/board-kaiser-keypad.c
+++ b/arch/arm/mach-msm/board-kaiser-keypad.c
@@ -477,6 +477,8 @@ static void kaiser_jog_queuework (struct work_struct *data) {
move_camera_lens(2);
else {
input_report_key(kbd_data.idev, KEY_UP, 1);
+ input_sync(kbd_data.idev);
+ msleep(10);
input_report_key(kbd_data.idev, KEY_UP, 0);
}
}
@@ -485,6 +487,8 @@ static void kaiser_jog_queuework (struct work_struct *data) {
move_camera_lens(-2);
else {
input_report_key(kbd_data.idev, KEY_DOWN, 1);
+ input_sync(kbd_data.idev);
+ msleep(10);
input_report_key(kbd_data.idev, KEY_DOWN, 0);
}
}

Thank you.
[Touch CDMA Android Development] polyrhythmic:
Well done dudes!

Moisha do you mind posting that zImage you've compiled?
[Touch CDMA Android Development] dzo:
I fixed it even better by polling for the key release. New NBHs are on my site and changes are pushed to git.
[Touch CDMA Android Development] moisha:
Only after quick edit, compile, test and post (and a dinner :-), I'm reading board-kaiser-keypad.c and starting to wonder ... "What kaiser_jog_queuework has to do with dpad ?" :-).

I removed the previous edit and recompiled. Dpad keys still work. Thank you, guys.
[Touch CDMA Android Development] moisha:
Sure.

zImage with hw3d for Eclair

zImage with hw3d for Donut
[Touch CDMA Android Development] myn:
Whats this?
[Touch CDMA Android Development] moisha:
/sdcard/andboot/zImage - kernel with 3D acceleration driver enabled.

On 3D note - if you haven't try Live wall papers with the acceleration yet - the nice one I found is the "lines". It's a remake of the classic M$ screensaver. Well configurable, stable and fairly OK on the resources (or so I think :-)
[Touch CDMA Android Development] dzo:
This hw3d is for eclair only, use the regular kernel for donut.
[Touch CDMA Android Development] myn:
Thanks for confirming.
[Touch CDMA Android Development] polyrhythmic:
Thank you dzo, moisha,

The new kernel and .NBHs work great. I am running from NAND now.

Dzo, I noticed that Vogue gets the ahb_div=3 Host Bus overclock, I think that would be safe for Kaiser as well. I usually run with a ahb_div=2 OC ;) and have for months. Is there a reason Kaiser is sleep mode 1 and Vogue is sleep mode 0? Regardless, I get great battery life with the latest files.

Cheers and thanks again!
[Touch CDMA Android Development] bzo:
thanks again! I can confirm that your latest init/replimenu works great with the diamond out of the box.
[Touch CDMA Android Development] vilord:
yay! diamond is the big win here, since I don't muck about in your kernel at all. Does this mean it is working with raphael/topaz/etc too?
[Touch CDMA Android Development] myn:
Time to upgrade our vogues maybe ;)

I still believe BT, GPS and Camera don't work on those devices yet at least.

A nicer res screen would be entertaining.
[Touch CDMA Android Development] tatnai:
I'm holding out for an HD2 running Win Mo on sprint (dare I hope), that may be identical in hardware to the coming HTC supersonic (android), so I can upgrade my SERO android phone! sorry, off topic :D
[Touch CDMA Android Development] mssmison:
I wouldn't mind getting into the new 2009 touch cruise.. It looks like a good one.