maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   [Android] Another Android port: NITdroid (https://talk.maemo.org/showthread.php?t=25410)

Thesandlord 2008-12-16 02:12

Re: Another Android port: NITdroid
 
Hey solca, just a question. Is there a way to update the userspace without flashing back to maemo? Im having problems flashing just the kernel in Linux, requiring me to use the complete reflash in Windows.

solca 2008-12-16 02:45

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Thesandlord (Post 249803)
Hey solca, just a question. Is there a way to update the userspace without flashing back to maemo? Im having problems flashing just the kernel in Linux, requiring me to use the complete reflash in Windows.

Flashing just the maemo kernel is very easy:

sudo ./flasher -f -F RX-44_DIABLO_4.2008.36-5_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -R

Hope that helps.

Thesandlord 2008-12-16 03:02

Re: Another Android port: NITdroid
 
The image from Nokia would not flash from Linux. no idea why. The kernel that meizirkki posted works fine though.

The new release is good, more smooth and WiFi is (slightly) better. It crashes a little more, but the trade offs are worth it (like a home button!). Pictures, Notepad, IM still don't work. I got my GMail to sync with the crappy Email app. I wish Google would release their apps, its just wrong for them not to...

jcl 2008-12-16 03:13

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by solca (Post 249802)
Hi!

I upload a new kernel and userspace, it fixes some problems reported here (DNS, Home button, etc.) I made several mistakes in the N800 support, hopefully it will be closer to work on those devices.

I'm refactoring the userspace so new NITdroid releases are more in line with the new (unreleased) selector and with user persistent settings (/data). Too this refactoring will permit live updates.

In the meantime report something :D

Enjoy!

Kudos on an excellent release,
this is definitely becoming an useable system.
Congratz again.

Is video (apart from sound) supposed to be working?

cyrus 2008-12-16 03:46

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by solca (Post 249802)
Hi!

I upload a new kernel and userspace, it fixes some problems reported here (DNS, Home button, etc.) I made several mistakes in the N800 support, hopefully it will be closer to work on those devices.

I'm refactoring the userspace so new NITdroid releases are more in line with the new (unreleased) selector and with user persistent settings (/data). Too this refactoring will permit live updates.

In the meantime report something :D

Enjoy!

Can you post the updated patch on your website? Also, the link to the userspace patch is broken.

Thanks

jcl 2008-12-16 04:16

Re: Another Android port: NITdroid
 
Application installation seems broken:
from shell, from browser crashes&reboots
Any other means?

Found a solution myself:
sudo ./adb push xxx.apk /data/app

For those interested, great android app:
http://dacp.jsharkey.org/

cyrus 2008-12-16 04:31

Re: Another Android port: NITdroid
 
Anyone had success mounted the external card? I get device not found.

jogorman 2008-12-16 04:51

Re: Another Android port: NITdroid
 
12-15 Userland & Kernel update.

Seems to be working great. Update to the userland and kernel flash went off with no problems at all. I was able to use the e-mail application to connect to an IMAP server just fine, browser is working great, home button is working good as well. I noticed that if hold down the power button, I can shut it off now as well. Goes a long way to making this useful.

An interesting thing I tried was to install an application. It came up with an error stating a SD card is needed. Any ideas?

And that bring up the other point I was thinking about as well. I am running the userland off of SD card. Is that odd? I have read some posts on here which make it sound as if that should not work. Myself, I am at a loss as to how else I would have fdisked and partitioned the disk. Can anyone fill me on on that process? If I can run the userland off of internal memory, I would be interested in giving that a try as well, I just don't know how to access the disk to set it up. (I have been using the SD card in my Linux machine directly, doing any changes, then putting it back in the N810.)

When I go to system information, the device reports free "internal phone" memory at over 700Meg, but no SD card seen. Any pointers on how to do this same set up on internal memory so I can use the SD card for installing apps would be great.

And any troubleshooting that might be useful that I can do as well. This project is coming out great, thanks for the hard work.

Thesandlord 2008-12-16 05:06

Re: Another Android port: NITdroid
 
Ok, this is good news, but its making me mad. I believed that you can't boot Android with a external card, so I partitioned the internal card. Now, it seems that it does not matter which card it is! It would be so much easier to use the external card, that is for sure...

On a different topic: For some reason, my tablet keeps rebooting while charging. I thought it was a hardware problem, but ever since I started running Android, no more reboots. Haha maemo, you can't hold me for ever!!

pycage 2008-12-16 07:55

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Thesandlord (Post 249810)
The image from Nokia would not flash from Linux. no idea why. The kernel that meizirkki posted works fine though.

I think you have to unpack the FIASCO image (the .bin file) with --unpack with the flasher and then flash the kernel image file directly. I did it this way to bring back my N810 to maemo and it worked.

zehjotkah 2008-12-16 13:47

Re: Another Android port: NITdroid
 
so now the home button works... but how do we quit a program?

solca 2008-12-16 17:33

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by cyrus (Post 249819)
Can you post the updated patch on your website? Also, the link to the userspace patch is broken.

Thanks

Both patches plus config for kernel regenerated to match latest release and link fixed.

solca 2008-12-16 17:34

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by zehjotkah (Post 249894)
so now the home button works... but how do we quit a program?

You don't need to, Android automatically will kill programs when needed.

kender 2008-12-16 19:55

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by jcl (Post 249821)
Application installation seems broken:
from shell, from browser crashes&reboots
Any other means?

Found a solution myself:
sudo ./adb push xxx.apk /data/app

I have the same problem, I tried making the partitions bigger, but no luck, I think it must be something about permissions as the error says that the temporary file can't be created (today I found out that they are store in /data/local/tmp

Thanks for the trick, it worked for me :D

(Running latest release with Home button supported and so, thanks again Solca)

skorianez 2008-12-16 20:33

Re: Another Android port: NITdroid
 
I want android in my N800 !!! :p

The keyboard issue seems to be solved by:
http://www.dotphone.org/viewthread.p...extra=page%3D1

best regards for all.

Bundyo 2008-12-16 21:30

Re: Another Android port: NITdroid
 
Now I'm trying on my N800 at least to see what i should get at the end :)

Problem - doesn't boot at all - blinking and stuff, ADB working, logcat shows its choking on media...

Code:

I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
W/AudioSystem( 1185): AudioFlinger not published, waiting...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
W/AudioSystem( 1185): AudioFlinger not published, waiting...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/        ( 1344): ServiceManager: 0xaab8
E/AudioHardwareALSA( 1344): Unable to attach mixer to device AndroidPlayback: No such file or directory
E/AudioHardwareALSA( 1344): Unable to attach mixer to device default: No such file or directory
E/AudioHardwareALSA( 1344): Unable to attach mixer to device AndroidRecord: No such file or directory
E/AudioHardwareALSA( 1344): Unable to attach mixer to device default: No such file or directory
I/DEBUG  (  587): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG  (  587): Build fingerprint: 'nokia/nit/nit/:1.0/TC3/eng.solca.20081215.185205:eng/test-keys'
I/DEBUG  (  587): pid: 1344, tid: 1344  >>> mediaserver <<<
I/DEBUG  (  587): signal 11 (SIGSEGV), fault addr 00000010
I/DEBUG  (  587):  r0 00000000  r1 ab749e8c  r2 0000ac78  r3 00000000
I/DEBUG  (  587):  r4 0000ac78  r5 ab753080  r6 ab753be4  r7 00000000
I/DEBUG  (  587):  r8 0000ac78  r9 00000000  10 00000000  fp beab8b3c
I/DEBUG  (  587):  ip 00000018  sp beab8a98  lr ab715d30  pc ab722ff8  cpsr 00000010
I/ServiceManager( 1185): Waiting for sevice media.audio_flinger...
I/DEBUG  (  587):          #00  pc ab722ff8  /system/lib/libaudio.so
I/DEBUG  (  587):          #01  pc ab715d2c  /system/lib/libaudio.so
I/DEBUG  (  587):          #02  pc ab716044  /system/lib/libaudio.so
I/DEBUG  (  587):          #03  pc ab713c8c  /system/lib/libaudio.so
I/DEBUG  (  587):          #04  pc ab0116be  /system/lib/libaudioflinger.so
I/DEBUG  (  587):          #05  pc ab011828  /system/lib/libaudioflinger.so
I/DEBUG  (  587):          #06  pc 0000875c  /system/bin/mediaserver
I/DEBUG  (  587):          #07  pc afe1e0aa  /system/lib/libc.so
I/DEBUG  (  587):          #08  pc afe0b09c  /system/lib/libc.so
I/DEBUG  (  587):          #09  pc b0000d70  /system/bin/linker
I/DEBUG  (  587): stack:
I/DEBUG  (  587):    beab8a58  00000003 
I/DEBUG  (  587):    beab8a5c  afe20821  /system/lib/libc.so
I/DEBUG  (  587):    beab8a60  ab749e88  /system/lib/libaudio.so


gte619n 2008-12-16 21:51

Re: Another Android port: NITdroid
 
Hey guys,

I'm having a ton of fun tracking the progress of the project on this forum and had a quick question. I think I read on another thread or forum that NITdroid would not be able to include the Google Apps (Mail, Cal, Contact, etc) because of licensing issues?

Is that true?! SAY IT AIN'T SO!!

Thanks! Evan

qole 2008-12-16 22:02

Re: Another Android port: NITdroid
 
Thanks Bundyo, I want to see someone with an N800 get this debugged before I attempt it.

solca 2008-12-17 00:27

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Bundyo (Post 250001)
Now I'm trying on my N800 at least to see what i should get at the end :)

Problem - doesn't boot at all - blinking and stuff, ADB working, logcat shows its choking on media...

Bundyo:

Thanks for trying and debugging this! right now I'm uploading an experimental userspace without the media (ALSA sound) part, can you check again on your N800?

(If you get 404 is still uploading as my Internet is not very fast)

This one should go past the mediaserver crashing on N800...hopefully...

EDIT: this is in the regular userspace now.

Vid 2008-12-17 00:47

Installing NITdroid from Diablo
 
I don't have access to a Linux system right now, but I was able to install the latest NITdroid directly from diablo. To make this work, you must install bzip2 and e2fsprogs on Maemo first. Note that I had to grab e2fsprogs from chinook, as there doesn't seem to be a .deb for diablo. Just install from

Code:

deb http://repository.maemo.org chinook free non-free extras
Next, you need to download the latest kernel and filesystem from http://guug.org/nit/nitdroid/. Fire up an xterm, and get a root shell using your favorite method (`sudo su' works for me). To repartition the internal flash, use the following commands:

Code:

sudo su
sfdisk -uM --no-reread /dev/mmcblk0
# In sfdisk, use the following commands
,356,C
0,0
,,L
,,
y

# sfdisk exits.  At the command prompt, type:
reboot

After the reboot, start another xterm and get a root shell. Then use the following commands to build new filesystems and flash the kernel:

Code:

sudo su
mkdosfs /dev/mmcblk0p1
mkfs.ext3 /dev/mmcblk0p3
mount /dev/mmcblk0p3 /mnt
cd /mnt
bzcat /path/to/rootfs_nitdroid.tar.bz2 | tar -xpvf -
cd /
umount /mnt
fiasco-flasher -k /path/to/zImage-nitdroid-n8x0 -f
reboot
# Don't forget to remove the mini-SD card!

Note that Android will reboot every 5 min or so as I haven't figured out a way to enable R&D mode using fiasco-flasher, so you'll need to fix that with adb from a Linux system. But this was enough to get me up and running right away :) Great work Solca! And thanks to b-man for the idea that I could get this working without a Linux host too ;)

Bundyo 2008-12-17 00:50

Re: Another Android port: NITdroid
 
flasher --enable-rd-mode

;)

Okay Solca, it works without sound... :) I'll test more now :) Btw, found FM Radio and Camera drivers in the kernel, would they work if compiled with...?

Nah, can't unlock it :( Which key is "Menu"

Thesandlord 2008-12-17 01:14

Re: Another Android port: NITdroid
 
Menu is the menu key, duh!

Sound does not really work at all, so you are not missing out on anything. If somehow camera, GPS, brightness, light sensor, sound, power management, etc could be enabled, that would be great. Does Android work with Bluetooth GPS?

Bundyo 2008-12-17 01:21

Re: Another Android port: NITdroid
 
My Menu key is opening Power menu, maybe it shouldn't...

I managed to unlock it with monkey, though it seems touchscreen is not working too.

Thesandlord 2008-12-17 01:23

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Bundyo (Post 250077)
My Menu key is opening Power menu, maybe it shouldn't...

I managed to unlock it with monkey, though it seems touchscreen is not working too.

You used monkey? So you just randomly waited for monkey to press the menu key? LOL...

Anyway, android is "supposed" to work with non touch devices also, so...

Bundyo 2008-12-17 01:25

Re: Another Android port: NITdroid
 
Not so much randomly - --majornav 100 :) Happened almost instantly.

Why do i have touchscreen if i'm not able to use it? :)

solca 2008-12-17 01:27

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Bundyo (Post 250077)
My Menu key is opening Power menu, maybe it shouldn't...

I managed to unlock it with monkey, though it seems touchscreen is not working too.

I included a binary at /nit/bin/evtest to see what your keys are so I can create a custom keymap for your device, too I need the output of /proc/bus/input/*

Too which touch screen driver uses the N800? I need to patch it to support BTN_TOUCH events.

Bundyo: very well done! Thanks to you we're closer to N800 support.

Bundyo 2008-12-17 01:39

Re: Another Android port: NITdroid
 
Code:

# /nit/bin/evtest /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "retu-pwrbutton"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 116 (Power)
Event: time 1229477816.291900, type 1 (Key), code 116 (Power), value 1
Event: time 1229477816.463806, type 1 (Key), code 116 (Power), value 0

Code:

Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "Internal keypad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 1 (Esc)
    Event code 28 (Enter)
    Event code 62 (F4)
    Event code 63 (F5)
    Event code 64 (F6)
    Event code 65 (F7)
    Event code 66 (F8)
    Event code 103 (Up)
    Event code 105 (Left)
    Event code 106 (Right)
    Event code 108 (Down)

Event: time 1229477745.181793, type 1 (Key), code 63 (F5), value 1
Event: time 1229477745.187988, -------------- Report Sync ------------
Event: time 1229477745.432433, type 1 (Key), code 63 (F5), value 0
Event: time 1229477745.432433, -------------- Report Sync ------------
Event: time 1229477750.102691, type 1 (Key), code 62 (F4), value 1
Event: time 1229477750.107208, -------------- Report Sync ------------
Event: time 1229477750.245025, type 1 (Key), code 62 (F4), value 0
Event: time 1229477750.245025, -------------- Report Sync ------------
Event: time 1229477752.593719, type 1 (Key), code 1 (Esc), value 1
Event: time 1229477752.594848, -------------- Report Sync ------------
Event: time 1229477752.752807, type 1 (Key), code 1 (Esc), value 0
Event: time 1229477752.752807, -------------- Report Sync ------------
Event: time 1229477759.210723, type 1 (Key), code 28 (Enter), value 1
Event: time 1229477759.211913, -------------- Report Sync ------------
Event: time 1229477759.354369, type 1 (Key), code 28 (Enter), value 0
Event: time 1229477759.354369, -------------- Report Sync ------------
Event: time 1229477762.145995, type 1 (Key), code 105 (Left), value 1
Event: time 1229477762.147186, -------------- Report Sync ------------
Event: time 1229477762.330840, type 1 (Key), code 105 (Left), value 0
Event: time 1229477762.330871, -------------- Report Sync ------------
Event: time 1229477762.935821, type 1 (Key), code 103 (Up), value 1
Event: time 1229477762.936675, -------------- Report Sync ------------
Event: time 1229477763.096557, type 1 (Key), code 103 (Up), value 0
Event: time 1229477763.096588, -------------- Report Sync ------------
Event: time 1229477763.644378, type 1 (Key), code 106 (Right), value 1
Event: time 1229477763.645507, -------------- Report Sync ------------
Event: time 1229477763.830932, type 1 (Key), code 106 (Right), value 0
Event: time 1229477763.830963, -------------- Report Sync ------------
Event: time 1229477764.357391, type 1 (Key), code 108 (Down), value 1
Event: time 1229477764.358245, -------------- Report Sync ------------
Event: time 1229477764.518432, type 1 (Key), code 108 (Down), value 0
Event: time 1229477764.518462, -------------- Report Sync ------------
Event: time 1229477766.590972, type 1 (Key), code 66 (F8), value 1
Event: time 1229477766.592468, -------------- Report Sync ------------
Event: time 1229477766.799682, type 1 (Key), code 66 (F8), value 0
Event: time 1229477766.799682, -------------- Report Sync ------------
Event: time 1229477767.328460, type 1 (Key), code 64 (F6), value 1
Event: time 1229477767.329284, -------------- Report Sync ------------
Event: time 1229477767.510619, type 1 (Key), code 64 (F6), value 0
Event: time 1229477767.510650, -------------- Report Sync ------------
Event: time 1229477767.961303, type 1 (Key), code 65 (F7), value 1
Event: time 1229477767.962432, -------------- Report Sync ------------
Event: time 1229477768.166869, type 1 (Key), code 65 (F7), value 0
Event: time 1229477768.166900, -------------- Report Sync ------------


Bundyo 2008-12-17 01:40

Re: Another Android port: NITdroid
 
Code:

Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "TSC2301 touchscreen"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      0
      Min        0
      Max    4096
      Fuzz      4
    Event code 1 (Y)
      Value      0
      Min        0
      Max    4096
      Fuzz      7
    Event code 24 (Pressure)
      Value      0
      Min        0
      Max    2048
      Fuzz      2

Event: time 1229477849.902465, type 3 (Absolute), code 0 (X), value 1640
Event: time 1229477849.903777, type 3 (Absolute), code 1 (Y), value 2114
Event: time 1229477849.904235, type 3 (Absolute), code 24 (Pressure), value 298
Event: time 1229477849.905944, -------------- Report Sync ------------
Event: time 1229477849.932464, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 1229477849.932494, -------------- Report Sync ------------
Event: time 1229477851.559539, type 3 (Absolute), code 0 (X), value 832
Event: time 1229477851.560790, type 3 (Absolute), code 1 (Y), value 1144
Event: time 1229477851.561248, type 3 (Absolute), code 24 (Pressure), value 221
Event: time 1229477851.562927, -------------- Report Sync ------------
Event: time 1229477851.585632, type 3 (Absolute), code 1 (Y), value 1139
Event: time 1229477851.586547, type 3 (Absolute), code 24 (Pressure), value 220
Event: time 1229477851.587005, -------------- Report Sync ------------
Event: time 1229477851.611694, type 3 (Absolute), code 0 (X), value 851
Event: time 1229477851.612701, type 3 (Absolute), code 1 (Y), value 1143
Event: time 1229477851.613189, type 3 (Absolute), code 24 (Pressure), value 218
Event: time 1229477851.614868, -------------- Report Sync ------------
Event: time 1229477851.637817, type 3 (Absolute), code 0 (X), value 895
Event: time 1229477851.638702, type 3 (Absolute), code 1 (Y), value 1199
Event: time 1229477851.639160, type 3 (Absolute), code 24 (Pressure), value 213
Event: time 1229477851.639495, -------------- Report Sync ------------
Event: time 1229477851.663940, type 3 (Absolute), code 0 (X), value 968
Event: time 1229477851.664825, type 3 (Absolute), code 1 (Y), value 1296
Event: time 1229477851.665283, type 3 (Absolute), code 24 (Pressure), value 212
Event: time 1229477851.667419, -------------- Report Sync ------------
Event: time 1229477851.689941, type 3 (Absolute), code 0 (X), value 1064
Event: time 1229477851.691039, type 3 (Absolute), code 1 (Y), value 1406
Event: time 1229477851.692260, type 3 (Absolute), code 24 (Pressure), value 216
Event: time 1229477851.693420, -------------- Report Sync ------------
Event: time 1229477851.716155, type 3 (Absolute), code 0 (X), value 1191
Event: time 1229477851.717071, type 3 (Absolute), code 1 (Y), value 1530
Event: time 1229477851.718231, type 3 (Absolute), code 24 (Pressure), value 221
Event: time 1229477851.719360, -------------- Report Sync ------------
Event: time 1229477851.742278, type 3 (Absolute), code 0 (X), value 1359
Event: time 1229477851.743163, type 3 (Absolute), code 1 (Y), value 1656
Event: time 1229477851.743591, type 3 (Absolute), code 24 (Pressure), value 231
Event: time 1229477851.743957, -------------- Report Sync ------------
Event: time 1229477851.768371, type 3 (Absolute), code 0 (X), value 1550
Event: time 1229477851.769378, type 3 (Absolute), code 1 (Y), value 1796
Event: time 1229477851.769805, type 3 (Absolute), code 24 (Pressure), value 235
Event: time 1229477851.770171, -------------- Report Sync ------------
Event: time 1229477851.794494, type 3 (Absolute), code 0 (X), value 1746
Event: time 1229477851.795440, type 3 (Absolute), code 1 (Y), value 1917
Event: time 1229477851.795898, type 3 (Absolute), code 24 (Pressure), value 248
Event: time 1229477851.796234, -------------- Report Sync ------------
Event: time 1229477851.820587, type 3 (Absolute), code 0 (X), value 1943
Event: time 1229477851.821502, type 3 (Absolute), code 1 (Y), value 2039
Event: time 1229477851.821929, type 3 (Absolute), code 24 (Pressure), value 272
Event: time 1229477851.822265, -------------- Report Sync ------------
Event: time 1229477851.846710, type 3 (Absolute), code 0 (X), value 2151
Event: time 1229477851.847656, type 3 (Absolute), code 1 (Y), value 2152
Event: time 1229477851.848113, type 3 (Absolute), code 24 (Pressure), value 355
Event: time 1229477851.849761, -------------- Report Sync ------------
Event: time 1229477851.872833, type 3 (Absolute), code 0 (X), value 2343
Event: time 1229477851.873779, type 3 (Absolute), code 1 (Y), value 2228
Event: time 1229477851.874206, type 3 (Absolute), code 24 (Pressure), value 310
Event: time 1229477851.875305, -------------- Report Sync ------------
Event: time 1229477851.901214, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 1229477851.901244, -------------- Report Sync ------------
Event: time 1229477852.095031, type 3 (Absolute), code 0 (X), value 2669
Event: time 1229477852.096008, type 3 (Absolute), code 1 (Y), value 2555
Event: time 1229477852.096435, type 3 (Absolute), code 24 (Pressure), value 251
Event: time 1229477852.097137, -------------- Report Sync ------------
Event: time 1229477852.121063, type 3 (Absolute), code 0 (X), value 2618
Event: time 1229477852.121978, type 3 (Absolute), code 1 (Y), value 2549
Event: time 1229477852.123168, type 3 (Absolute), code 24 (Pressure), value 295
Event: time 1229477852.124328, -------------- Report Sync ------------
Event: time 1229477852.147186, type 3 (Absolute), code 0 (X), value 2497
Event: time 1229477852.148071, type 3 (Absolute), code 24 (Pressure), value 289
Event: time 1229477852.148498, -------------- Report Sync ------------
Event: time 1229477852.173278, type 3 (Absolute), code 0 (X), value 2338
Event: time 1229477852.174163, type 3 (Absolute), code 1 (Y), value 2529
Event: time 1229477852.174590, type 3 (Absolute), code 24 (Pressure), value 258
Event: time 1229477852.175079, -------------- Report Sync ------------
Event: time 1229477852.199401, type 3 (Absolute), code 0 (X), value 2166
Event: time 1229477852.200347, type 3 (Absolute), code 1 (Y), value 2478
Event: time 1229477852.200775, type 3 (Absolute), code 24 (Pressure), value 273
Event: time 1229477852.201110, -------------- Report Sync ------------
Event: time 1229477852.225524, type 3 (Absolute), code 0 (X), value 1966
Event: time 1229477852.225982, type 3 (Absolute), code 1 (Y), value 2484
Event: time 1229477852.226348, type 3 (Absolute), code 24 (Pressure), value 283
Event: time 1229477852.226684, -------------- Report Sync ------------
Event: time 1229477852.251617, type 3 (Absolute), code 0 (X), value 1776
Event: time 1229477852.252075, type 3 (Absolute), code 1 (Y), value 2506
Event: time 1229477852.252441, type 3 (Absolute), code 24 (Pressure), value 268
Event: time 1229477852.252868, -------------- Report Sync ------------
Event: time 1229477852.277740, type 3 (Absolute), code 0 (X), value 1612
Event: time 1229477852.278228, type 3 (Absolute), code 1 (Y), value 2464
Event: time 1229477852.278594, type 3 (Absolute), code 24 (Pressure), value 248
Event: time 1229477852.278930, -------------- Report Sync ------------
Event: time 1229477852.303863, type 3 (Absolute), code 0 (X), value 1463
Event: time 1229477852.304351, type 3 (Absolute), code 1 (Y), value 2426
Event: time 1229477852.304687, type 3 (Absolute), code 24 (Pressure), value 273
Event: time 1229477852.305053, -------------- Report Sync ------------
Event: time 1229477852.329925, type 3 (Absolute), code 0 (X), value 1339
Event: time 1229477852.330413, type 3 (Absolute), code 1 (Y), value 2360
Event: time 1229477852.330749, type 3 (Absolute), code 24 (Pressure), value 313
Event: time 1229477852.331207, -------------- Report Sync ------------
Event: time 1229477852.356078, type 3 (Absolute), code 0 (X), value 1247
Event: time 1229477852.356567, type 3 (Absolute), code 1 (Y), value 2277
Event: time 1229477852.356933, -------------- Report Sync ------------
Event: time 1229477852.385589, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 1229477852.385619, -------------- Report Sync ------------
Event: time 1229477854.002776, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 1229477854.002807, -------------- Report Sync ------------


Bundyo 2008-12-17 01:41

Re: Another Android port: NITdroid
 
Code:

# cat /proc/bus/input/*           
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="retu-pwrbutton"
P: Phys=
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="Internal keypad"
P: Phys=spi1.0/input-kp
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=1680 7 c0000000 10000002

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="TSC2301 touchscreen"
P: Phys=spi1.0/input-ts
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=event2
B: EV=b
B: KEY=0
B: ABS=1000003

N: Number=0 Name=kbd
N: Number=1 Name=evdev Minor=64

Code:

<6>[    2.454162] omapfb: ls041y3 rev 8f LCD detected
<6>[    2.454620] omapfb: configured for panel ls041y3
<6>[    2.468536] omapfb: DISPC version 2.0 initialized
<6>[    2.468749] omapfb: RFBI version 1.0 initialized
<6>[    2.489288] omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
<6>[    2.489532] omapfb omapfb: s1d1374x: setting update mode to auto

Okay, off to bed :)

solca 2008-12-17 02:04

Re: Another Android port: NITdroid
 
Push this to your N800 to fix the keypad:

$ sudo ./adb push Internal_keypad.kl /system/usr/keylayout

I'm patching the touchscreen driver, will post a new kernel at the usual place.

EDIT: the kernel have been patched, source patch updated too.
EDIT2: this key layout for N800 is part of the regular userspace now.
EDIT3: this new userspace (20081216) should fix the app install problems too.

soupus 2008-12-17 04:51

Re: Another Android port: NITdroid
 
I'm still trying to get my n800 to boot. I'm using the most recent kernel/rootfs (just downloaded it off Solca's page about 20 minutes ago), but it still seems to be dying at the animated android screen. When I use adb shell, I can't run logcat (it just hangs) however DMESG seems to be claiming that I'm using the wrong FAT filesystem on my other partitions. Which of the multiple FAT options should I set the type as in fdisk for those partitions? Thanks again guys!

Quote:

<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
<3>FAT: bogus logical sector size 65535
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
<3>FAT: bogus number of reserved sectors
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
<3>FAT: bogus logical sector size 65535
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
<3>FAT: bogus number of reserved sectors
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
<3>FAT: bogus logical sector size 65535
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
<3>FAT: bogus number of reserved sectors
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
<3>FAT: bogus logical sector size 65535
<6>VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
<6>warning: `app_process' uses 32-bit capabilities (legacy support in use)
<6>mmci-omap mmci-omap.0: Spurious IRQ 0x0001

Bundyo 2008-12-17 06:04

Re: Another Android port: NITdroid
 
What about the no-sound userspace? :)

Looks like it is the no-sound one :)

cyrus 2008-12-17 06:43

Re: Another Android port: NITdroid
 
solca:

Where are you building this kernel? Within scratchbox (maemo sdk).

meizirkki 2008-12-17 06:54

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by soupus (Post 250115)
I'm still trying to get my n800 to boot. I'm using the most recent kernel/rootfs (just downloaded it off Solca's page about 20 minutes ago), but it still seems to be dying at the animated android screen. When I use adb shell, I can't run logcat (it just hangs) however DMESG seems to be claiming that I'm using the wrong FAT filesystem on my other partitions. Which of the multiple FAT options should I set the type as in fdisk for those partitions? Thanks again guys!

FAT filesystem to the first partition of the mmc like this:

mkfs.vfat /dev/sdb1

it worked for me.. :)

Thesandlord 2008-12-17 06:58

Re: Another Android port: NITdroid
 
I used Gparted. Very easy to use and understand, and can even be used directly on tablet. For me, command line is last resort, because there is so much that could mess up.

meizirkki 2008-12-17 08:09

Re: Another Android port: NITdroid
 
gparted on tablet should do the job too, but if you want to use Gparted, at least do it from computer. I heard there are some issues with pb:s gparted hack. Easiest way to make fat-fs is just type "mkfs.vfat /dev/mmcblk0p1" on tablet. -It's even easier and faster than doing it with Gparted.

Bundyo 2008-12-17 09:17

Re: Another Android port: NITdroid
 
Looks like everything works in N800 now. WiFi and the time too.

pycage 2008-12-17 09:25

Re: Another Android port: NITdroid
 
Quote:

Originally Posted by Bundyo (Post 250141)
Looks like everything works in N800 now. WiFi and the time too.

This is great news. Yesterday I tried the then latest version on my N800 and it didn't come past the flashing robot boot splash.

Bundyo 2008-12-17 09:41

Re: Another Android port: NITdroid
 
Nah, the time is not working, got fooled by the NTP :)

spjndizzy 2008-12-17 11:13

Re: Another Android port: NITdroid
 
Thanks Solca for your hard work. Thanks to Bundyo as well. Its working on my N800. I just need to type in order to enter my ssid for my network.

I look forward to further improvements. It's very impressive so far.


All times are GMT. The time now is 23:07.

vBulletin® Version 3.8.8