Reply
Thread Tools
Posts: 62 | Thanked: 35 times | Joined on Mar 2008 @ Fort Gratiot, Michigan
#31
So, I've read the website-- Can someone give me a quick startup guide?

I know how to flash an image (I did the V2 Android already)-- but the ext3 filesystem thing confuses me.

--Jake
 
solca's Avatar
Posts: 109 | Thanked: 196 times | Joined on Sep 2008 @ Guatemala
#32
Originally Posted by mrp View Post
any way this could work on 770?
If you are willing to help yes, firstly I would generate a debugging kernel for N770 with console output to screen so you can tell me where it ends. plz tell me when you are ready?
 

The Following User Says Thank You to solca For This Useful Post:
b-man's Avatar
Posts: 549 | Thanked: 502 times | Joined on Feb 2008 @ Bowling Green Ohio (united states)
#33
Originally Posted by jakemaheu View Post
So, I've read the website-- Can someone give me a quick startup guide?

I know how to flash an image (I did the V2 Android already)-- but the ext3 filesystem thing confuses me.

--Jake
Here's how you can easily partition/format your memory card on your device.

First, make shure you have e2fsprogs installed and do the following as root:

Code:
fsdisk -uM /dev/mmcblk0
Assuming you want a 356MB partition for user-space, and the rest of your memory card for Android, enter the following in the displayed order

Code:
356,C
,,
,,L
,,
Then reboot, this will make a fat32 filesystem on the first partition for some user-space (mmcblk0p1), a empty partition on mmcblk0p2, a linux83 filesystem on the third partition (mmcblk0p3), and a empty partition on mmcblk0p4.

After you reboot, make shure that your internal memory card is not mounted and do the following to format your memory card so Android has a proper filesystem to run on.

Code:
umount /dev/mmcblk0
mkdosfs /dev/mmcblk0p1
mkfs.ext3 /dev/mmcblk0p3
Then mount your /dev/mmcblk0p3 device to /opt, untar your Android OS to /opt, umount /opt, and flash your kernel, enjoy!
__________________
I'm an advanced user and a bit of a modder.
----------------------------------------------
I am involved with Mer, Deblet, and NITdroid.
My ports/creations/hacks: GNOME (for Deblet), Cdeb2», Ubuntu, playable flash games in the "Get Started" app, DBS, ect...


enhanced fedora port has been canceled in favor of NITDebian (TBA)
 

The Following 3 Users Say Thank You to b-man For This Useful Post:
Posts: 1,213 | Thanked: 356 times | Joined on Jan 2008 @ California and Virginia
#34
Hey, just wanted to say that it works on my N810. Hopefully the tearing problem will be solved.

Apps work for the most part, lots of random crashes, but system seems beta quality stable. Even the OpenGL apps work, which is kinda amazing.

For the most part, it is much smoother than Meamo, although a bit more annoying (No full screen button, no close button, etc).

Two questions:

How does WiFi work? I can't add a network without a crash

If I flash a Maemo kernel, such as the rotation one, will I get everything back, or will I have to reflash?

I can't wait for a 100% release!
__________________
----------------------------------------------------

www.ezschool.com - The best online educational experience.

Last edited by Thesandlord; 2008-12-09 at 02:07.
 
b-man's Avatar
Posts: 549 | Thanked: 502 times | Joined on Feb 2008 @ Bowling Green Ohio (united states)
#35
Wow, OpenGL works!?!?, that is amazing!

Wifi drivers work, but some people are reporting that for some odd reason, Android has a hard time "bringing up" network services at boot time.

Also about your kernel question, if you use a linux desktop, you shuld be able to flash the kernel without effecting maemo. However, if you use Windows, you might need to reflash.
__________________
I'm an advanced user and a bit of a modder.
----------------------------------------------
I am involved with Mer, Deblet, and NITdroid.
My ports/creations/hacks: GNOME (for Deblet), Cdeb2», Ubuntu, playable flash games in the "Get Started" app, DBS, ect...


enhanced fedora port has been canceled in favor of NITDebian (TBA)
 

The Following User Says Thank You to b-man For This Useful Post:
solca's Avatar
Posts: 109 | Thanked: 196 times | Joined on Sep 2008 @ Guatemala
#36
Originally Posted by qole View Post
So, is the new Maemo 5.0 kernel of any use to you Android porters? It is only 2.6.27, but it should have the WiFi stuff integrated into it.
qole, looking into this, Maemo 5 kernel does have impressive support for RX-51 hardware, including Free/Open Source wireless drivers (wl12xx) which is neat! but it doesn't have much of value for N8x0 that is not already in the OMAP tree.

It failed to compile for a N810 target too, hopefully Nokia will fix this.
 

The Following User Says Thank You to solca For This Useful Post:
Posts: 1,213 | Thanked: 356 times | Joined on Jan 2008 @ California and Virginia
#37
Ok, after playing around for a while, I have found a few "problems." Hopefully this will help some people.

Kernel Version: 2.6.28-rc7-omap1
Build number: nit-eng 1.0 TC3 eng.solca.20081208.021935 test-keys

The time does not work, it just stays stuck at what it was at boot.
Crashes after about 5 minutes, no matter what.
Calculator and Notepad don't work, while pictures, music, API demo, settings, browser, contacts, dialer do work. Not sure about the other apps.
__________________
----------------------------------------------------

www.ezschool.com - The best online educational experience.
 

The Following 2 Users Say Thank You to Thesandlord For This Useful Post:
solca's Avatar
Posts: 109 | Thanked: 196 times | Joined on Sep 2008 @ Guatemala
#38
It seems after serious debugging I find the WiFi problem, it seems the stlc45xx driver is returning bogus signal levels for some APs to the Android WiFi service which crashes and restarts the whole environment.

I have reported this to the stlc45xx mailing list so it gets fixed there and in the meantime I'll code a fix for this bug in Android too.
 

The Following 5 Users Say Thank You to solca For This Useful Post:
tmlind's Avatar
Posts: 10 | Thanked: 43 times | Joined on Dec 2007
#39
Originally Posted by qole View Post
LEGACY? <gets all red in the face and roars,> LEGACY?!?

Maybe there's a mistake here? Are you sure these are required N800 drivers? The tsc2301-core is staying; perhaps they're doing the audio mixing differently now?

How dare they declare my beloved N800s LEGACY!? They're only two years old! OK, the N800 has been discontinued, and two years is a long time in this market, but come on, guys!
Heh Well we're trying to move all the driver development to the
proper driver mailing lists instead of carrying them in the
linux-omap tree. If the drivers just sit in the linux-omap tree,
they won't go anywhere and won't get properly reviewed either.
That's why they're called "legacy", not because they are too old.

The goal is to make things usable with the mainline kernel. For
audio, there's a way better framework already called ASoC.

Somebody just needs to write the N800 driver for it. N810 already
works with ASoC! See sound/soc/omap in your kernel tree.

Regards,

Tony
 

The Following 2 Users Say Thank You to tmlind For This Useful Post:
Posts: 57 | Thanked: 4 times | Joined on May 2007
#40
hi, just curious to know which miniSD is /dev/mmcblk0p3?
It seems that I only copied the root file system to the external SD card, and it works now. So it seems that /dev/mmcblk0 be the external minisd? Or does the kernel has the capability to try different miniSDs?

NITdroid is far better in functionality and usability! the clock is working, the gui is pretty fast! The stability is the only thing needs to be improved. Every time i tried to enable the wifi, it restarts the GUI. And I observed frequent reboot after some time idle.
 
Reply

Tags
android, nitdroid

Thread Tools

 
Forum Jump


All times are GMT. The time now is 03:57.