maemo.org - Talk
Page 273 of 297 « First 263271272 273 274275283 Last »
Show 40 post(s) from this thread on one page

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)

kolos 2010-07-11 11:24
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?

Dousan 2010-07-11 11:27
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 :)

nielsvg 2010-07-11 11:30
Re: [Android] NITDroid V2 Development Topic
 
but i have the new build and did this already

Dousan 2010-07-11 11:43
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?

dj_steve 2010-07-11 11:53
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

nielsvg 2010-07-11 12:01
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

dj_steve 2010-07-11 12:01
Re: [Android] NITDroid V2 Development Topic
 
have you got any form of mac security on your AP ?

nielsvg 2010-07-11 12:03
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

stobbsc 2010-07-11 12:11
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?

weißelstone 2010-07-11 12:29
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).


All times are GMT. The time now is 08:50.
Page 273 of 297 « First 263271272 273 274275283 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8