maemo.org - Talk - [Android] NITDroid V2 Development Topic

maemo.org - Talk (https://talk.maemo.org/index.php)

- Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)

- - [Android] NITDroid V2 Development Topic (https://talk.maemo.org/showthread.php?t=49811)

Re: [Android] NITDroid V2 Development Topic

Thanks guys for your effort!

I installed NITDroid for the first time and things that I noticed are:

- market didn't work from beginning (endless downloading), but now, from unknown reason to me, it works :rolleyes:
- phone is much warmer, compared running under maemo OS
- "up arrow" doesn't work

Is it possible to somehow fix this "up arrow" bug?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by nielsvg (Post 748031)

but i chose 4 in the bootmenu but i cant connect to my wifi. i entered my wep key but it keeps downloading the ip-adress and then it goes back to scanning.

it keeps going in a loop

Ok, i had that kind of problem after i did the new update...

Then try this:
Just do this again in xterm:
mkdir /and (if error comes, just proceed)
mount -o noatime,rw /dev/mmcblk1p2 /and
cd /and
rm -rf *
bzcat /home/user/MyDocs/NITDroid-N900-0.0.5-3-BIG.tbz2 | tar xvf -
cd /and/system/bin
nano load_modules.sh (here you type your bluetooth number: BDADDR="0cddef0a0e6d")
cd /
umount /and

That fixed it for me... seemed like the old NITdroid build didn't get fully ereased the first time :)

Re: [Android] NITDroid V2 Development Topic

but i have the new build and did this already

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by Reffyyyy (Post 748018)

Get a file manager from Android Market, navigate to root>extras and open it from there.

That did work thanks ;)

One thing though the trailer on gametralirs.com did the buffering and just when it seemed to start the web crashed?

Anybody know of any sites that uses flashplayer 10.1 so i can test the flashplayer further to see if it crashes there to :)

e: Before gametrailers switched to 10.1 i wasn't able to watch trailers either from maemo microb, it allways hanged on the buffering, maybe it's just a to heavy site to cope for the N900's hardware?

Re: [Android] NITDroid V2 Development Topic

its possible its too heavy to handle on the ntidroid build as is (ie with no hardware assistance to gfx)
edit: the toystory3.com is one i use to test flash worked

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by dj_steve (Post 748059)

its possible its too heavy to handle on the ntidroid build as is (ie with no hardware assistance to gfx)
edit: the toystory3.com is one i use to test flash worked

steve,

i'm having a problem with wifi in the latest build.

i can enter my wep key and then it wants to get my ip-adress and then it disconnects, then scanning and then trying to get the ip-adress again.

and then it starts over and over.
in the install i changed the mac id to my one id

but it doenst work

Re: [Android] NITDroid V2 Development Topic

have you got any form of mac security on your AP ?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by dj_steve (Post 748065)

have you got any form of mac security on your AP ?

no nothing. in the first build when you helped my with logging in on my pc the wifi worked. and nothing changed in my wireless connection.

so i dont get it

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by maxximuscool (Post 747971)

install Flasher 3.5 (windows 32bits)
go to flasher folder by use Windows Key+R (run) type CMD - Enter
in CMD: cd c:\program (press tab)\ maemo\flasher (press tab)
you should get this line:

cd "C:\Program Files\maemo\flasher-3.5"

Take the battery out of the phone for 10seconds, put it back in and press hold "U" button then plug in the microUSB.

in CMD: type this (assuming that you've downloaded those files already and put them in flasher folder in C-drive.)

(command below will format your eMMC, be sure to back up everything before doing so).

flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R

Take battery out and press U and plug microUSB and run the next command. (this will reinstal firmware)

flasher-3.5.exe -F RX-51_2009SE_10.2010.19-1.002_PR_COMBINED_002_ARM.bin -f -R

You should get something like this: I reflashed mine just now lol. Because of i want my device to be cleaned again.
----------------------------------------------
----------------------------------------------

C:\Users\sopheak>cd "c:\Program Files\maemo\flasher-3.5"

c:\Program Files\maemo\flasher-3.5>cd "c:\Program Files\maemo\flasher-3.5"

c:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.
VANILLA_PR_EMMC_MR0_ARM.bin -f -R
flasher v2.5.2 (Sep 24 2009)

Image 'mmc', size 255947 kB
Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': <no version>
Booting device into flash mode.
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
1c8.
Raw data transfer EP found at EP2.
Image(s) flashed successfully in 34.958 s (7321 kB/s)!

c:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.19-1.
002_PR_COMBINED_002_ARM.bin -f -R
flasher v2.5.2 (Sep 24 2009)

SW version in image: RX-51_2009SE_10.2010.19-1.002_PR_002
Image 'kernel', size 1705 kB
Version 2.6.28-20101501+0m5
Image 'rootfs', size 173696 kB
Version RX-51_2009SE_10.2010.19-1.002_PR_002
Image 'cmt-2nd', size 81408 bytes
Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.8+0m5
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': <no version>
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 3625 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 15267 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 13250 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 14930 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 25555 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 23042 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (173696 kB)...
100% (173696 of 173696 kB, avg. 13175 kB/s)
Finishing flashing... done
CMT flashed successfully

c:\Program Files\maemo\flasher-3.5>

thanks for the reply. I'll give this ago just now.
Do you know where I can get the flasher for windows and the other files you mention?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by nielsvg (Post 748064)

i can enter my wep key

If you are really using WEP try it without encryption. It makes no difference for a hacker (even a N900 can hack WEP networks easily) and is easier to set up. (It would still be better to change to WPA2).

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by nielsvg (Post 748064)

He replied on my post about flashplayer 10.1 ;)

@Steve it worked flawlessly on the disney toy story 3 trailer/site, but crashed again on gametrailers.com :) So just that site thats a problem for now, i hope :)

Re: [Android] NITDroid V2 Development Topic

should I not be using this file RX-51_2009SE_10.2010.19-1.203.1_PR_COMBINED_203_ARM.bin because I got my phone in the uk or does it not matter ?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by ~phoenix~ (Post 747996)

thx for your work....

i'm still hoping for faster startup, and phone 3G support....

can i donate anywhere to support this projekt??

sry 4 my english....

Painful, but finally find it.
https://www.paypal.com/uk/cgi-bin/we...502e138eefdd27

dj_steve can you confirm so that is correct donadion adress?

Re: [Android] NITDroid V2 Development Topic

Am I right in thinking that with this new "no flashing required" version of NITDroid, that I can flash back to the stock kernel and it'll still work?

Re: [Android] NITDroid V2 Development Topic

Yup, but u need to install the new boot menu that flashes a diff kernel each time u select an option :)

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by thundead (Post 748128)

Yup, but u need to install the new boot menu that flashes a diff kernel each time u select an option :)

i think Rootfs;)

Re: [Android] NITDroid V2 Development Topic

Someone should provide some benchmark figures.

Such as:
Quadrant test
Linpack test
NenaMark1
Neocore
etc

Just to contrast to other devices running Android

Biblio-graphy

Re: [Android] NITDroid V2 Development Topic

@weißelstone: wpa2 does not work for me ...

Blues

Re: [Android] NITDroid V2 Development Topic

donate urls are :: GBP Donate(£)/USD($) Donate

Re: [Android] NITDroid V2 Development Topic

Thanks for the links and your great work, Steve....

Just made a donation to you....

Keep it coming...

:)

Mark

PS. Hopefully, others will show their appreciation too....

Also, two suggestions/reminders:

A. Help questions should go in the other Help/Tutorial Topic thread and

B. Please don't quote and reply to a post if all you want to do is ask a simple question or make a comment...

It's getting harder to get through this lengthy thread and I see many posts that could have been very short in length if they hadn't quoted a post for no apparent reason.

Anyway, just my 2¢, as we say....

;)

Re: [Android] NITDroid V2 Development Topic

Can you please fix the FM support in Maemo with the next build?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by stobbsc (Post 748096)

should I not be using this file RX-51_2009SE_10.2010.19-1.203.1_PR_COMBINED_203_ARM.bin because I got my phone in the uk or does it not matter ?

use the global version.

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by weißelstone (Post 748094)

i cannot disable the encryption. my service provider delivers the wireless router you should have and they secure it so nobody but them can mess with it.

but i got wifi to work on a pervious build but not in the new one

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by nielsvg (Post 748194)

FWIW, I got wifi working OK on my home network using WPA2....using latest build...

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by DaSilva (Post 748174)

Can you please fix the FM support in Maemo with the next build?

This is the Android thread not Maemo

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by DaSilva (Post 748174)

Can you please fix the FM support in Maemo with the next build?

Quote:

Originally Posted by *Sonic* (Post 748204)

This is the Android thread not Maemo

There where a bug when running the nitdroid kernel in Maemo like we did before that ruined FM radio support, so this is actually a valid question :P

To answer the question, it is fixed in this release! But your still running the Nitdroid kernel in maemo, flash back to the regular kernel in maemo to fix this issue.

Re: [Android] NITDroid V2 Development Topic

Ah right apologies, it just seemed a strange question to ask if FM had been fixed in Maemo and not Android LOL

Re: [Android] NITDroid V2 Development Topic

Tired of status/progress/woz-new questions a bit.
For everyone who interested in - RSS url:
http://gitorious.org/android-n900.atom

Just subscribe and watch for it.

Re: [Android] NITDroid V2 Development Topic

can someone help me with my wifi problem? i have the latest build but cannot connect to wifi

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by e-yes (Post 748239)

Tired of status/progress/woz-new questions a bit.
For everyone who interested in - RSS url:
http://gitorious.org/android-n900.atom

Just subscribe and watch for it.

Yea, would be nice if this thread was just updates and we had a thread for everything else, saves 200 odd pages of scrolling to get to what you want

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by kylepsp (Post 748256)

Yea, would be nice if this thread was just updates and we had a thread for everything else, saves 200 odd pages of scrolling to get to what you want

Then, please, delete your own post.
Thanks.

Re: [Android] NITDroid V2 Development Topic

Yea cause deleting my own post would get rid of all the other posts that aren't updates, genius.

Re: [Android] NITDroid V2 Development Topic

Anyway, smart players use the IRC, HA.

I'm asking this again. Can Jay-C release a PACKAGE of his bootmenu? It WILL help other projects. Also it will self-update itself, etc...

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by Siggen (Post 748208)

To answer the question, it is fixed in this release! But your still running the Nitdroid kernel in maemo, flash back to the regular kernel in maemo to fix this issue.

Hi Siggen, I am a bit confused. I used the new install method (without having nitdroid installed before) so I never manually flashed the kernel. But the FM radio does not work in Maemo. So what has the new install done with the maemo kernel and how do I revert it?

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by CormacB (Post 748287)

Find the option that says "Maemo 5 (blahblah-power)" on bootmenu and select it. It will flash the power kernel. If you didn't have the power-kernel, it will show "Maemo 5 (2.6.28-omap1)" or something like that.

Re: [Android] NITDroid V2 Development Topic

cant anyone help me fix my wifi problem???

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by giannoug (Post 748288)

Aha, that did the job. Just curious, why is that not the default? I assumed the default was the standard maemo kernel.

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by nielsvg (Post 748293)

cant anyone help me fix my wifi problem???

i had the same problem too (since i already had it installed)
you have to install Jay-C's multiboot-0.1.1

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by CormacB (Post 748319)

Aha, that did the job. Just curious, why is that not the default? I assumed the default was the standard maemo kernel.

No idea. I also had a similar problem and found out the solution myself. The first option (the default one) doesn't flash the default kernel, it leaves the old one flashed.

Re: [Android] NITDroid V2 Development Topic

Quote:

Originally Posted by humble (Post 748321)

i had the same problem too (since i already had it installed)
you have to install Jay-C's multiboot-0.1.1

i installed multiboot. I did everything like on this website:

http://wiki.nitdroid.com/index.php?title=N900-install

i followed it to the letter but nothing.