Re: Another Android port: NITdroid
 

Okay, looks like i finally made some progress... I have a framebuffer console on 770 and its working fine up to finding the partition... Waiting for root device... and that's it. Maybe the MMC driver is not initialized properly, but i can't see the messages more than the page above it. Solca, do you know of any way to get them? adb is not working yet :)

Re: Another Android port: NITdroid
 

That is what I figured but how do I gain root? What user am I logged in with when Android starts?

Re: Another Android port: NITdroid
 

@cyrus: I was able to ping using adb

Map update: Looks like there is a preview release of Open Street Map Viewer.

Location seems to be very inaccurate, off by a few miles, which I am blaming on the WiFi driver. Remember, there is no GPS yet. Slow in downloading tiles, sometimes crashes. Once again Im blaming the driver.

http://www.anddev.org/openstreetmap_...t2967-s30.html

Also, the WiFi complains about a calibration tool. Says "Device will operate sub-optimal." I am guessing that this is some binary blob, so we can't use it?

Re: Another Android port: NITdroid
 

Hey all. Just came across this thread today. Looks like you have been up to some really cool stuff.

I did an install on my N810. Running into a problem I did not see anyone report, so I thought I would detail my installation method (to make sure I did not screw something up) and the issues that I am seeing.

To install, I took the 1GB MicroSD card I had, and split it into three partitions. The first is a FAT16 partition set to 128Meg. 2nd is just one sector. 3rd is the rest of the card with a ext3 fs on it. I uncompressed the files (tar -xjpvf /rootfs_nitdroid.tar.bz2) onto it. I then used the flasher from Linux on the N810 (after booting it holding down the application switch button while it was attached to the computer via USB). Flash seemed to go fine. I then was able to put the MicroSD card back in the N810 and boot up android.

Android seems to boot fine, and is very responsive.

On boot, Android reports and error. "Application Settings (in process com.android.settings) is not responding. With options "Force Close" and "Wait". Happens each time.

I am able to connect to a wireless network fine, however no network access appears to work. I tried the "setprop net.dns1 <ip>" Through the devtools->Terminal Emulator. (Is that the right place to try that?) with no luck.

After running for about five minutes, the device turns off. Settings that were changed are saved.

Anyone has any things I should try, of if I did the install wrong, I am all ears. I was a bit confused by the "Internal MMC" instruction. I am assuming that was to mean the slot for the MicroSD slot, as I don't know how to gain access to the internal memory to the level I would be able to reformat/repartition it. So if I got that wrong, please let me know which method I should be taking.

Thanks
Jim

Re: Another Android port: NITdroid
 

@jogorman:

It booted from external SD? WTF? I though it could not...

You do the setprop net.dns1 from adb. Connect the tablet to the computer, go to your adb directory, and type "adb shell" for Windows, "sudo ./adb shell" for Linux. Then, you basically have a kind of Telnet to the tablet.

Re: Another Android port: NITdroid
 

I get that

"Application Settings (in process com.android.settings) is not responding."

As well.

Re: Another Android port: NITdroid
 

That was the only way I knew to partition the file system. Unless I missed something fundamental.

Thanks for the info about the ADB, I will try that tonight and see if that helps.

Jim

Re: Another Android port: NITdroid
 

Just a quick update, ADB shell was able to let me get online in browser just fine. (Amazing how much faster that is the then standard browser.)

Still crashes the same however, and the DNS settings do not persist between sessions like the other settings I had changed did.

Re: Another Android port: NITdroid
 

Put your tablet into RD mode.
Don't know about the dns though.

Re: Another Android port: NITdroid
 

That's good news! Which kernel version have you running?

I don't know how to look above the current page specially if the kernel is panic-ed, I think it's not possible without a serial console. But you can create a script that redirects the output to a file to check later, the catch is that you need a working storage driver, probably the MTD driver works and you can redirect to the initfs or rootfs maemo partitions. You can instruct the kernel which program runs with the init= parameter.

BTW I had done some mistakes on the N800 support, hopefully will finish soon the next kernel and userspace with some finished improvements and bug fixes (dns, home button, etc).

Thanks for all the feedback ppl! :cool: