yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] liba2k:
Software Keyboard

Can you please add the software keyboard to the next image?

I can't find how to enter some characters using the nike 16 keys keyboard.

Thanks.
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
I got it from the official linux machine type database:

http://www.arm.linux.org.uk/developer/machines/download.php

It looks like Kaiser has two mtypes, and 1724 is the second of these. Nike in this list is listed at 1852.

But hell if it works I don't really care, I just noticed the discrepancy.

There are two things bugging me at the moment - needing USB connected to start Android, and the lack of (16-key Niki100) keyboard for SMS. I've pulled down the latest git tree but the msm stuff doesn't seem to be in there (and the instructions in the first post of this thread seem to be incomplete).

What can I do to fix these problems?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
No problem! I just wanted to say if you change the machine types you're going to have a loot of problems, and as you say, if it works, who cares? :)

The problem is not on the keyboard, but on the sliding functions of Android. If you open the keyboard Android thinks the lid is closed, then puts the image on portrait, because it thinks you're running it on a G1. If you close the lid, the screen rotates as if you open the keyboard on the G1, then it lets you type. You can close the lid a bit, just so the screen rotates to landscape, then you can type with the keyboard. I know, it's impossible to use it that way on a daily basis, but you can see what I mean if you try it. To fix that you need the android sources, and recompile the thing without taking care of the slider for sms (or without taking care of the slider anywhere). That's what I was trying to do, but my android sources don't want to compile, so I haven't done that just yet (and I don't really know too much about android userspace either)

About the USB, it's easy, disable usb support on arch/arm/mach-msm/common.c

I haven't done that because I don't want to screw dzo's work when pushing changes to the git and because I'm trying to make usb work too, but I sometimes disable it if I need to look at dmesg, as usb drops a lot of messages to it and makes it harder to read..

On the Wiki you have the instructions to clone the git: http://wiki.xda-developers.com/index.php?pagename=Nike_Kernel_Build

After you clone the tree, you have to do a "git checkout -b htc-vogue origin/htc-vogue" on the kernel directory to get the vogue branch, wich is what we use for vogue, kaiser, polaris and nike. Then, you'll find nike files on arch/arm/mach-msm on your kernel dir.

The only wrong thing in the wiki is that you need a more recent toolchain or the compilation will fail with a "Segmentation Fault" message. Instead of downloading the arm-2008q1 toolchain, you will need, at least, arm 2008q3, wich is what Im using. It's on codesourcery too, I found it googling.

By the way, did you have any problems when pulling latest changes? The git admin keeps telling me there seems to be a conflict with one of my commits, but I'm able to clone, to pull and to push without warnings, and don't know where the error is, if there's still any...
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
OK thanks for that tip about the USB.

Re: the keyboard stuff...from what you have said it sounds like we have the open/close sensing reversed... surely we want it to think the lid is open if the keyboard is out? Maybe I have misunderstood you. I'll take a look at the code anyway and see if I can figure it out.

Checking out the git trees seems to have worked for me. By the way here's a link to the latest toolchain, if you can update the wiki page:

http://www.codesourcery.com/sgpp/li...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
The exact problem is that it doesn't matter what you do, the thing will always run bad. I mean, if you inverse the lid switch behaviour (on board-htcnike-keypad.c, just above the power button control), you can get the keyboard to work while it's open. BUT, the screen will be rotated, so you'll have it in landscape while you type, and on portrait while it's closed. There was an application for android elsewhere, that was called Spare Parts. With that you could change the sliding behaviour to follow the phone sensors or the lid. As we don't have the sensors (accelerometer for being precise), that was a temporary fix I used, but that was on the cupcake images I think, and disappeared when we started using the sdk. So, in the end, we need to compile our own images, or do a good mix of the sdk and cupcake builds :)

By the way, thanks for the link, I'll update the wiki now.

Regards!
[Touch Dual, MDA Touch Plus ROM Development] McLin:
I hate this sh*t yaffs2 module... Sorry but I need one more day, but then it work...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, I've enabled some power saving features on the kernel, but I don't know if they are really making a difference or not, so I thought you could test it too. With previous kernels, android drains quite a lot of battery, more or less a 20% for each 1% on Windows Mobile. This may make a difference or may not, but it's worth a try...

Regards!

EDIT: Second run, forgot one little thing... http://rapidshare.com/files/213697782/zImage
[Touch Dual, MDA Touch Plus ROM Development] McLin:
New Image Here the Image with cramfs filesystem...
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
Well, if anybody finds it useful at all I just compiled a kernel which is from yesterday's git tree but disables USB so you don't need it connected to the computer to boot. I just tried it, it works and even boots without a SIM card installed :)

It doesn't have biktor_gj's recent additions though.

http://paperairoplane.net/android/no-usb/zImage
[Touch Dual, MDA Touch Plus ROM Development] matiu:
Hi guys!

First of all, thank you for all that you make for porting linux android on our device. ;)

But there are some problems:

1) touchscreen crash after a while;

2) camera still don't work;

3) battery drain fast;

4) internet doesen't work;

5) phone doesn't work very well.

If you fix this problems I promise a donation at all the team. :)

I LOVE Android. :D
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks biktor, i think it made a difference. seems to run slightly cooler.. about 10% battery use every hour, i think.
[Touch Dual, MDA Touch Plus ROM Development] meisterlampe2000:
You should not forget that Windows Mobile is still running in the Background - At least some core Processes might be active & consuming CPU time.

I´ll wonder if an emulation can be efficient...And i think 10:1 is a good checkmark ;=)

You´ll get this done soon !!! Thanks
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
its not an emulation :) once haret boots linux, it takes over and winmo is no longer running at all.
[Touch Dual, MDA Touch Plus ROM Development] paranoidpenguin:
maybe it's a stupid question, but what should I do with the cramfs image? I can't boot it
[Touch Dual, MDA Touch Plus ROM Development] McLin:
Copy it in root of sdcard, and overwrite the exist... Anybody have same problem?
[Touch Dual, MDA Touch Plus ROM Development] cunter:
I had to delete your data.img and copy the data.gz from biktor_gj's bootkit. Then your system.img worked. But I don't see any difference to biktor system. It looks and behaves the same.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, the image works fine, even seems a bit faster, but I personally can't use it, because it's missing the Developer tools (the terminal emulator is there), and Spare parts. btw is an older version or something? on settings -> about phone it says build 121975, while we were using 130444 on the previous image...

Regards!
[Touch Dual, MDA Touch Plus ROM Development] McLin:
I did not include the new radio image, did I should modify the image or you do it?

Just dev tools?
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
sound wouldnt work for me with mclins image -did anyone else get this? and the messaging program was the same as the old one (cant type)
[Touch Dual, MDA Touch Plus ROM Development] McLin:
oh and I did include amazon mp3, pacman, terminalemulator, thats the reason why the data.img is include in the zip. I must move the files over there.

I using the same Version like in my signature...
[Touch Dual, MDA Touch Plus ROM Development] paranoidpenguin:
It's working with biktor_gjs bootkit. First time the phonesetting, like providers are detected correct. But the internet seems to be dead now.

Is there a possibility to enable the softwarekeyboard again? Or is there another chance to get special symbols like @ or : to be written?
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
I'm using the cupcake version of android which seems to have the onscreen keyboard built-in. Otherwise I find even when my 16-key keyboard works some of the keys don't produce anything useful on multiple presses - often multiple presses will just backspace.
[Touch Dual, MDA Touch Plus ROM Development] McLin:
Im stupid, take the wrong image, that is the reason...

Here is the roght Version, but I installed the apps in data, so wie must bind the data.img...

data.gz is usefull that all work fine;)
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
That is a problem with board-htcnike-keypad.c, and If you tell me exactly what happens and when happens I will fix it... nobody came with this problem so far, but the behavior you comment is a kernel problem I would be glad to fix (nike keypad driver is a biig nasty hack I did in two days..)

@McLin: No problem man, downloading new version now, I will post results later! By the way, my android sources got to compile, so if I find a way to fix the sms thing I'll put an image or the compiled files here...

Regards!

EDIT: Image boots fine like previous, but, data.img should be ext2fs. You can use the data.gz from my bootkit instead of whatever you're using (wich doesn't boot from initrd). For the rest, this is the new build, but it still has problems, for example, not reading contents from sd (music, pictures...), missing dev tools & spare parts, and radio interface layer doesn't seem updated, as no sound comes from the device...
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
Oh man, I see what you mean. What a mess! But I don't know if I could come up with something better in a hurry.

I'll try some things and figure out what works well on my 16-key, and send you a patch by PM you can integrate into your own tree.
[Touch Dual, MDA Touch Plus ROM Development] McLin:
Add data.gz in my previus post, you can install dev tools via adb...

Dev Tools
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
The problem I have with the keyboard driver is the different layouts and possibilities of each type of keypad wich I can't test for more than my own layout, but I know how I did the hack, so I know, more or less, how to fix the possible issues you get. I've left it behind for a while (I'm laaaazyyy), but I guess it needs major rewriting, sooner or later :)

Anyway, if you need some info just ask, the code in the end is quite easy to follow (it's just a bunch of switches with a timer), I'll be taking a look to see if I can make it a bit smaller and efficent..
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
This is my understanding of the code:

1. There can be no more than 5 possible keycodes from any button

2. The keycodes you have put into the maps are global, no context sensitivity

3. Because the code simply returns the keycode from a designated place in the map, you can only return built-in keys rather than shifted values (i.e. no bitshifted stuff like for "@")

I'm not sure why I'm getting backspace from the 0 key, it looks like it is only that key at the moment, perhaps some boundary condition not being checked properly... I also had a look at some of the other keyboard drivers to see if anyone is doing it better, if I remember correctly I think the Titan keyboard code could be used with some modification. I'll keep looking into it.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
The code is based on kaiser's keypad. This problem shouldn't exist if we all had 20key Nikes, but 16key keypads have between 2 and five different types of keypresses. The problem with shifted values is that each key has a different length on 16 key maps, and using a flag bit for each key would make the code be enormous, and the kernel wouldn't handle it well (tested, module crashed when loading, or after typing on different circunstances). I thought maybe a solution would be to insert another item on the matrix, wich would have always the shifted bit enabled, but it's a mess to implement it without breaking the entire module..
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi Mclin, reality is, I can't use adb since I can't connect through usb or bluetooth, but doesn't matter as I can always mount the image and add the applications myself. Anyway, I wanted to ask, how did you build the image? I've been trying to get a bootable image based on the sources, but can't get it to boot, neither to show at least the bootlogo.

If I pick your image, I extract the files to a directory and rebuild it to a new system.img it boots, but if I pick, say, a system.img compiled from the sources for arm, even if the binaries work, the image doesn't boot. In the same way, if I use, for example, G1 or Sapphire dumps, I can't manage to boot either. Setprop crashes, servicemanager crashes, everything crashes all the time. Is there any guide I can read out there or any suggestion?
[Touch Dual, MDA Touch Plus ROM Development] McLin:
I take diffrent instruction on web to compile.

First thing I use for G1 (HTC Dream) source.

First

then put the images to emulator /tool/lib/images and boot, then I pull all files from /system and /data via adb.
[Touch Dual, MDA Touch Plus ROM Development] matiu:
Can someone upload the latest bootkit?

Mine doesn't work. :(
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
In case you didn't see it, there has been a crash on the forum. They have restored a backup from yesterday, but some posts have been lost.Check this: http://xdaforums.com/announcement.php?f=404

@Ohookins: I'm rewriting part of the keypad driver, to fix your issues on 16 key mappings, and to be able to use shifted values. When I get it to do all the things I want it to, I will post a build for you to test.

Regards!
[Touch Dual, MDA Touch Plus ROM Development] graey:
Can't wait to test it :D
[Touch Dual, MDA Touch Plus ROM Development] stadros83:
Is there some pictures or videos to show us how Android looks like on the Niki ?
[Touch Dual, MDA Touch Plus ROM Development] McLin:
@biktor_gj

Should you need the Files? I can boot it on my G1, the new build images cant boot in Emulator anymore...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
You mean from my image?

I have two sets of files now, when I compile the Android sources, it makes the out folder with both the image files (system.img, ramdisk.img etc), and the dumped folders from whete it builds the images (/system /data etc).

I also have been able to dump the system folder from the emulator, (when it gets stucked on the logo I can connect through adb, upload a busybox and make a tar file from the system image), but that doesn't boot either. So, at this point, I think I have the files, but I'm unable to make it boot on the nike, but maybe I'm missing something. The only thing I really need is to make it boot on the nike. Any ideas on how to do that?
[Touch Dual, MDA Touch Plus ROM Development] McLin:
I look around
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, I have a new build for testing.

Only changes to the keypad driver. Removed quite a lot of crap, and added a "left shift". now you can type caps, numbers, and a lot of symbols for the numbers and * key (such as !@#$%&/()=-_...)

20Key Nikes: use alt key

16Key Nikes: use "mail" key

It's not finished yet, so there might be some things not working well, but you can test and tell me what's going wrong, mostly for 16 key nikes since I can't test them myself but for 20keys too.

http://rapidshare.com/files/215554873/zImage

Regards!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
hey thanks biktor, nice changes. mail key works for caps and symbols!

you missed out the power button though :)
[Touch Dual, MDA Touch Plus ROM Development] McLin:
wow how did you compile this image? Is it a regular Android image or for Hardware Specified?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
hmmm... I guess it's a regular image from the cupcake branch. I only did a "make", after changing the sms application thing for the sliding-rotated-keyboard disable... are you getting problems with it?

Didn't even use another toolchain or anything...
[Touch Dual, MDA Touch Plus ROM Development] McLin:
This is Interesting, Storie the new Firmware runs fine on my G1, but I didnt find the failure, I will need 1 or 2 days to debug this... Is that ok for you?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
No problem! meanwhile I'll be working on the kernel, and see if I can find why the key_end doesn't want to work anymore...

Regards!
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Ok, now the keypad should work better.

Fixed the Power button, for some reason it didn't want to declare itself from the keypad matrix anymore (it was doing it without a problem before). I also fixed the problem with at least 20k nikes, where after pushing shift the first letter appears in caps, the second doesn't, and all the rest appear ok.

Rapidshare: http://rapidshare.com/files/216084082/zImage

If you tell me everything is working good I'll push the changes to the git for everyone
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
everything perfect here, flawlessly working on the 16key :) !
[Touch Dual, MDA Touch Plus ROM Development] McLin:
tell me which files you need / modified from your image... I think I have it.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Great news!

There are just two things that are essential:

The RIL libraries from 03/01 android build (libreference-ril.so and libril.so on /lib), with normal ones gsm isn't working, at least on my tries.

the brf6300.bin firmware, that needs to be placed at /system/etc/firmware

This is for the bluetooth, and it's not working yet, but it will be needed anyway

And I think it was already there, but just in case, the Dev tools and Spare parts.apk's, no more...
[Touch Dual, MDA Touch Plus ROM Development] McLin:
right, 2morrow I will upload new images...
[Touch Dual, MDA Touch Plus ROM Development] excogitation:
Don't know if this is up to date, but here you can find additional changes to system.img (userspace).
[Touch Dual, MDA Touch Plus ROM Development] McLin:
New Images...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Still hangs at boot on the android logo... :(

I'm going to try an alternate build based on the latest changes, and this time compiling it for the sdk (make PRODUCT-sdk-sdk) and see if I can get it to boot just in case it was some kind of bug...

@exco: It's a bit old, but it has the modifications for the vogue camera (wich is the same as nike's), so it will be useful :) thanks!
[Touch Dual, MDA Touch Plus ROM Development] McLin:
And when you plug you USB in and boot?
[Touch Dual, MDA Touch Plus ROM Development] paranoidpenguin:
even with usb connected it hangs at bootlogo
[Touch Dual, MDA Touch Plus ROM Development] Alienfreak:
Mine also hangs at the android logo. The logo blinks one in a while but even when I wait like 20 minutes nothing happens besides that :(
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
could somebody tell me wich constalation of android files and zimages works best for now? cause i got about 3 "ready to use" bootkits and 3 zimages, too.

could someone pls post link to latest and stable bootkit and zimage?

thx in advance..
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
You have them on the wiki, at the bottom:

Last available bootkit:http://rapidshare.com/files/211389157/Bootkit_03_20_2k9.rar

Last available kernel: http://rapidshare.com/files/216084082/zImage
[Touch Dual, MDA Touch Plus ROM Development] uhoo:
Works great on my Neon200 20-key with the latest bootkit (March 20) and the latest zImage. I don't even need USB plugged in to boot. Big thanks to all involved! I get the same 'hanging on the Android screen' with the latest system.img, even with USB in, though.

One little (big) problem. The Alt and Enter keys don't work on the screen lock page, so I don't have a Menu button and I can't unlock without a reinstallation. Is this specific to the neon or are Nikes having this problem too? The other keys all work fine so it's a bit strange.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
I replaced the android menu key on 20 key mappings so it uses the camera button for all types of phones. I should update that on the wiki :)

USB support is disabled on last kernel, so it shouldn't be a problem to boot without it anymore. I'm still waiting dzo's patch for usb to re-enable it though
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
thx for that link to latest and stable image and bootkit files...

got a 20 keys niki300... somehow my hardware keyboard wont work! cant type any sms and stuff...

its the same problem like it was bevor... in default.txt i choosed option for 20key nike...

i`d like to give android a "everyday use" try but without hw keyboard... this wont work...

is there any hint ive missed? dont understand where my problem is because it works for other people with 20key nike
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
hmmm... did you try on anything wich is not the messaging appliacation? For example... on the terminal? The messaging application doesn't work for nike. We're trying another approach (at least McLin and I) by compiling android from the sources to fix that, but the messaging application is the only thing wich doesn't work (from the keyboard side), since it thinks it's running on a htc g1..

By the way, git is updated with the keyboard changes. I also started a little on the h2w driver, but it's still **** for now :)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] mferrare:
Hi,

I tried the latest bootkit and have these problems:

The phone finds my network (PCCW in Hong Kong) on bootup but does not establish a 3G data connection. A previous bootkit (about a month ago) had this working. Sometimes it would come up automatically and sometimes I needed togga. But now no banana. With or without Togga. The APN is set correctly. I checked with the settings on my E71.

If I go to the wireless settings and search for networks the search fails. Same goes for network selection. I do manage to remain registered to PCCW though.

I can't make calls. When I dial I immediately get a 'call ended' screen.

I can't receive calls. The phone rings but the call is then dropped as soon as I press the answer button.

Just wondering if others have seen this behaviour. And wouldn't mind some pointers on digging more deeply into it. If there's a log somewhere or if I can terminal into the phone and see what's going on.

Thanks

Mark