maemo.org - Talk - [Android] Another Android port: NITdroid

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)

Re: Another Android port: NITdroid

Quote:

Originally Posted by jogorman (Post 254001)

When enabling wireless, and going into WIFI settings, I get a device freeze followed by a shutdown. I grabbed the logcat:

With supplicant

Code:

E/bluetooth_common.cpp(  741): dbus_func_args_timeout_valist: D-Bus error in ListBondings: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)

D/SettingsWifiEnabler( 1112): Received wifi state changed from Enabling to Enabled

I/ActivityManager(  741): Displayed activity com.android.settings/.WirelessSettings: 623 ms

I/ActivityManager(  741): Starting activity: Intent { action=android.intent.action.MAIN comp={com.android.settings/com.android.settings.wifi.WifiSettings} }

I//system/bin/wpa_supplicant(  795): CTRL-EVENT-STATE-CHANGE id=-1 state=2

V/WifiMonitor(  741): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]

V/WifiStateTracker(  741): Changing supplicant state: INACTIVE ==> SCANNING

D/SettingsWifiEnabler( 1112): Received wifi state changed from Enabling to Enabled

Without supplicant

Code:

I//system/bin/wpa_supplicant( 1205): CTRL-EVENT-SCAN-RESULTS  Ready

I//system/bin/wpa_supplicant( 1205): CTRL-EVENT-STATE-CHANGE id=-1 state=1

D/SettingsWifiEnabler( 1170): Received wifi state changed from Enabling to Enabled

V/WifiStateTracker(  780): Connection to supplicant established, state=INACTIVE

I/ActivityManager(  780): Starting activity: Intent { action=android.intent.action.MAIN comp={com.android.settings/com.android.settings.WirelessSettings} }

D/SettingsWifiEnabler( 1170): Received wifi state changed from Enabling to Enabled

I/ActivityManager(  780): Displayed activity com.android.settings/.WirelessSettings: 540 ms

I/ActivityManager(  780): Starting activity: Intent { action=android.intent.action.MAIN comp={com.android.settings/com.android.settings.wifi.WifiSettings} }

I//system/bin/wpa_supplicant( 1205): CTRL-EVENT-STATE-CHANGE id=-1 state=2

V/WifiMonitor(  780): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]

V/WifiStateTracker(  780): Changing supplicant state: INACTIVE ==> SCANNING

D/SettingsWifiEnabler( 1170): Received wifi state changed from Enabling to Enabled

I get the same thing.

Re: Another Android port: NITdroid

Quote:

Originally Posted by andreww (Post 254018)

It's very likely just something stupid I did, but I couldn't get the new release to run out of the box. The rootfs was missing a lot of seemingly important stuff, like /init, /sbin/adbd, and some other misc files (which seem like they might be obsolete).

I though these were supposed to be inside the kernel now or something.

Anyway, it is not working for me either. so I am guessing either the directions are wrong, or there is a glitch with this release...

Edit: Nope, still won't boot...

Edit 2: I am such an idiot, forgot the external card had to be removed... AND I FLASHED THE WRONG KERNEL. I am a complete fool....

Re: Another Android port: NITdroid

Are you sure you remembered to remove the card in external slot???

Re: Another Android port: NITdroid

Quote:

Originally Posted by Thesandlord (Post 254092)

Yes, now the new kernels contains an embedded RAM filesystem as other Android devices (G1) which contains init and the other files in /, the userspace tarball that you must untar to mmcblk0p3 contains:

/cache
/data
/nokia
/system

So installation remains the same but you have to flash the new kernel, if you have extra stuff than the above in mmcblk0p3 it simply it is not used.

If you flash the debugging kernel in this release the wifi driver will not load or will hang the device as it is compiled for the normal kernel, I had to figure out how to ship different modules for the debugging kernel yet.

The debugging kernel disables all logos and animations and as usual enables screen console output so if you have problems please try next the debugging kernel and report back.

As there are many new features please report any problem as I probably don't check every single thing. Thx!

Re: Another Android port: NITdroid

This embedding the ram fs in the kernel will probably have problems with 770, since you can only have a kernel up to 2MB. How exactly is it done and where can i get the init?

Re: Another Android port: NITdroid

Quote:

Originally Posted by solca (Post 254100)

Got it. For some reason, the kernel I flashed to yesterday was the same as the one I had before. Downloaded it again, made sure the file was different, flashed it and am trying it now.

Thanks again!

Re: Another Android port: NITdroid

Works now - using the non-debug kernel.

For some reason I find this release to be slower. Is there a reason why Android seems so much more sluggish than Maemo? Is it because it is running off the flash card?

Thanks

Re: Another Android port: NITdroid

I just updated to the newest release 02Jan. And found some issues
1. wireless doesn't work
dmesg shows that it fails to request_firmware, 3826.arm

2. cannot use adb with it
i am using linux in vmware under windows, and previous it works great, but now, it is sluggish when i connect the usb cable, and make my linux responds slowly. dmesg under linux:
[ 2266.959538] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 2267.366669] usb 2-1: not running at top speed; connect to a high speed hub
[ 2267.366713] usb 2-1: config 1 has 1 interface, different from the descriptor's value: 2
[ 2267.385657] usb 2-1: configuration #1 chosen from 1 choice
[ 2267.399854] scsi9 : SCSI emulation for USB Mass Storage devices
[ 2267.402649] usb-storage: device found at 5
[ 2267.402654] usb-storage: waiting for device to settle before scanning
[ 2272.972216] usb 2-1: reset full speed USB device using uhci_hcd and address 5
[ 2273.459676] usb 2-1: device descriptor read/64, error -84
[ 2274.428339] usb 2-1: device descriptor read/64, error -84
[ 2274.661102] usb 2-1: reset full speed USB device using uhci_hcd and address 5
[ 2277.184100] usb 2-1: device descriptor read/64, error -84
[ 2277.780263] usb 2-1: device descriptor read/64, error -84
[ 2278.013089] usb 2-1: reset full speed USB device using uhci_hcd and address 5
[ 2278.849655] usb 2-1: device descriptor read/8, error -84
[ 2279.169490] usb 2-1: device descriptor read/8, error -71
[ 2279.332287] usb 2-1: USB disconnect, address 5
[ 2279.332287] scsi 9:0:0:0: Device offlined - not ready after error recovery
[ 2279.332287] usb-storage: device scan complete
[ 2285.071326] usb 1-1: new high speed USB device using ehci_hcd and address 6
[ 2285.501987] usb 1-1: config 1 has 1 interface, different from the descriptor's value: 2
[ 2285.513084] usb 1-1: configuration #1 chosen from 1 choice
[ 2285.517470] scsi10 : SCSI emulation for USB Mass Storage devices
[ 2285.523473] usb-storage: device found at 6
[ 2285.523481] usb-storage: waiting for device to settle before scanning
[ 2288.617149] usb 1-1: USB disconnect, address 6
Meanwhile, if connected with usb, the n810 will reboot continously(seems).

3. no suid on /system
thus i cannot get the right permission to run logcat, or some other utility.

Am I the only one meeting those issues? Thanks.

Are

Re: Another Android port: NITdroid

I feel it is slower to boot up than earlier version, but there is only few things it is possiblle to nagg about. _Really_ impressive work solca! :)