yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] enatefox:
yea that link was what i was messing with. it was linked to on modaco as well. we'll get this to work but we're both strapped for free time. the good news is that meego is so young in development we're not missing a whole lot yet.

EDIT: lmao just saw that:

"Thanks to storm99999" on their wiki. nice. shouldn't they know how to do this?
[Nexus One Android Development] geney:
Wow... Would love to see this happen. But I know there's nothing much I can help except donating :o
[Nexus One Android Development] vgrade:
Updates to Nexus Meego port on the meego wiki page linked in an earlier post.

Sorry I can't link here as I'm am considered a potential spammer.
[Nexus One Android Development] storm99999:
Oh man, that's great news. Too bad the explanation for how they got it to work doesn't quite explain how we can get it to work.

I suspect we may just need to change a line or two on the .ks file, but it also could be a bigger change than that.
[Nexus One Android Development] vgrade:
Hi storm99999,

The 'they' is me :)

I took the daily from Saturday and added the mesa packages which provide software EGL and GLESv2.

Changed Xorg to load the fbdev driver. 'used Option Rotate CW'

Replaced the session line in uxlaunch to session=/usr/bin/duihome -software &

Hoe you had a drink with my donation :)

Next step is to build the aurora kernel and userspace drivers.

vgrade
[Nexus One Android Development] vgrade:
I've added some files to the wiki page with a kickstart, zImage and a couple of config files.
[Nexus One Android Development] storm99999:
Well, I have to congratulate you on your work, I don't know enough about meego/linux internals to have gotten that far.

A quick question, could you post your .ks file changes so that we can know the exact packages included? Edit: beat while I was typing. :P

Lastly, I think we don't have to worry about the kernel. The stock google kernel has the kgsl stuff in already. What needs to be done is to put the msm Xorg stuff in and add the OGL stuff for the adreno200. Looking at the wiki, we may need to splice two different versions of libc or add the ones from AOSP to a build setup and compile it.

Edit: How much is working?
[Nexus One Android Development] vgrade:
Thanks, just standing on the shoulders of giants.

There are many blockers for this port EGL,GLES,wifi,sound etc etc but I'm using it as a way of learning more about linux, meego, X, GL.

I was hoping that with the kgsl and msm Xorg we could get reasonable performance with just the mesa EGL and GLES.

I don't know enough (do we ever) about linux and the dynamic library system to make the adreno (bionic) libs coexist with the rest of the libc built meeGo.

vgrade
[Nexus One Android Development] vgrade:
Storm99999, can you post a link to the wiki as I still cannot.

Thanks

vgrade
[Nexus One Android Development] storm99999:
Well... EGL and GLES seems well covered in discussion.

Wifi... I think we just need the firmware blob in the right place (see the Debian threads for that) and all the right configuration boxes checked. A terminal would guarantee its operation, so once a system with adbd is configured, well, we're set for the most part.

Sound... That is tricky. I think the kernel has all the hardware specific stuff already coded but Android has a rather prominent position in controlling it. There's a reason why buggy roms suddenly open the media app when headphones are plugged in. I noted that pulseaudio was commented out in the .ks, does it cause system instability?

Libc... Well, I think if we just put the source for libc bionic into a build environment for MeeGo, it should build. I mean, it's libc, it should support all we need.

I'll try to get a system set up later this evening, because today I have a few hours to work with. Woo!

Oh, and linky: http://wiki.meego.com/ARM/MSMQSD

You'll be free to post links by 10 posts, I think
[Nexus One Android Development] vgrade:
I still don't understand how the two dynamic libs will coexist?

the adrene.so files are linked to libc.so (the boinic one)

the rest of meego to libc.so (the glibc one)

How will the dynamic linker know which one to load?
[Nexus One Android Development] vgrade:
Thats 10 posts.
[Nexus One Android Development] storm99999:
They won't coexist. We compile against the one that works with the adreno200.so 's. It might work.

That, or we compile the adreno200.so 's against glibc. We have the source for most of this stuff.

EditL: Oh wait, I'm not sure we have the adreno200.so sources, but we do have the linking GLES and EGL lib source.
[Nexus One Android Development] vgrade:
Do I have this right?

Option 1 - Compile whole of MeeGo against bionic libc

Option 2 - Compile adreno against glibs libc

1. I don't think the bionic libs are a FULL implementation of libc so will it have enough support for MeeGo. How would you know unless you tested every Meego app.

2. This option has more mileage but only if we have the FULL source to the adreno EGL, GLES files. As I understand it libEGL and libGLESc2 are just stubs (which we have the source for) which link to the adreno.so files. Do we have the FULL source for these libs.

vgrade
[Nexus One Android Development] vgrade:
OK so, nogo there then.

What about (and this is without a knowledge of how linux dynamic linking is done and the correct terms) replacing the linkage references to libc.so in the adreno.so files to point to a newly built (or just renamed from libc.so) bionic.so?

vgrade
[Nexus One Android Development] vgrade:
If we do go this way we need to consider if the resources used by the two libc implementation collide.
[Nexus One Android Development] storm99999:
I do not think we have the source, or at the very least, I didn't find any good news from my android-cm directory.

We may have no choice but to take the hardest path. Or at least a very difficult and tedious one.

Edit: Well, I just went through all of that just to have it crash on boot. 3 seconds in too. Must be doing something really wrong, probably something to do with dd screwing up with the file.

Anyways, is there anywhere where there is development discussion outside of here? IRC perhaps?
[Nexus One Android Development] vgrade:
IRC #meego-arm on freenode

query me and we can get a private message
[Nexus One Android Development] vgrade:
ah, you wrote the image straight to sdcard?
[Nexus One Android Development] vgrade:
http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Build_the_rootfs

We need to use the procedure here to write the rootfs to a sd card which has a single ext3 part on it.
[Nexus One Android Development] enatefox:
i <3 u all. also, the weego tab is coming that allegedly supports android apps. if that's that case, then their "nonrape" libc has bionic against it. what that means specifically i don't know but it's good news. i like where this is going =D

vgrade, i was asking punkkaos because i lack the finesse, to make a recovery that works like haret and can do image files. personally i'd rather a system.img on my SD than a partition.
[Nexus One Android Development] vgrade:
Not good news, really as its running android inside a vm see the follwing post to the meego tablet forum from the wetab team.

Good piece of marketing though. wetab supports windows, linux, android, osx apps. Don't tell them they are all running in a VM.

Hi all

Yes we do use MeeGo and it rocks! We use UI framework option and just put our UI on top. Actually it is MeeGo v1.0, but some components are even next to latest builds. So WeTab does support Multitouch, based on the MeeGo Touch Framework.

We support Qt 4.6 and will update to 4.7, once it is stable. Qt is the framework, which we prefer, but nevertheless we support GTK based apps as well as java, flash, air, android apps (last ones are running in a complete android 2.2 in virtualbox).

And by the way, since you have access to the root shell, so you could do what you like..

Cheers

WeTab Team
[Nexus One Android Development] storm99999:
Well, the procedure basically requires an SD card adaptor. Going through the phone invariably results in an ext partition with a destroyed superblock and an os that is confused as possible. I'm not sure why though, it should be avoidable.

Just a note for anyone who is trying the same thing and having it unable to boot.
[Nexus One Android Development] enatefox:
vgrade I'm clearly not as l33t as you are at getting this but I'm looking at the issues you're having and think I can at least point you in the right direction.

yes it can but I never got success with it when I was trying to get Gnash ported. The bro that is working on it got it to compile but I think he failed with something related to Gnash and not compiling glibc. His guide for building specific dependencies is here. I have too many questions to begin doing it myself but he pulled off at least compiling all the way though.

Hope that helps and the screen of Meego on your N1 is awesome work =D
[Nexus One Android Development] KnightMAREcrow:
4 day obligatory bump? Sorry, just checking on this thread daily as I'm very excited and interested in the possibility of dual booting Android and Meego.

Any update on progress devs and good luck
[Nexus One Android Development] storm99999:
Sorry, no news from me. I'm still waiting on getting the right hardware. I don't think we can do anything with just the phone. No matter what file transfers I make, if they're on ext3, the whole file system goes.

Maybe it's stupid configuration, but I can't do anything until I have a sd to micro sd converter. Not sure about everyone else, but I don't think there will be much progress until we start working entirely from source, which will be painful.

There are one or two things that are just configuration and file tweaks, like wifi possibly, but I can't tell from here.
[Nexus One Android Development] vgrade:
Updates here http://wiki.meego.com/ARM/MSMQSD
[Nexus One Android Development] vgrade:
storm99999

smoku on meego-arm today said that he has success in booting dell streak from p2 of a sdcard with a boot img flashed to the device.

The trick is to get a correctly configure initrd when building the boot.img

He was going to post later.

This should allow you to progress without the sdcard adaptor.

I have also has two confirmations of the procedure at

http://wiki.meego.com/ARM/MSMQSD

vgrade
[Nexus One Android Development] vgrade:
Where did my last 5 posts go ?
[Nexus One Android Development] houmles:
Somewhere in black hole :)

http://www.xda-developers.com/announcements/xda-downtime/
[Nexus One Android Development] vgrade:
Thanks mate, I was thinking I'd dreamt all those new posts :)

Now what did I say !
[Nexus One Android Development] KnightMAREcrow:
vgrade, I asked you about the progress and you said that the drivers required were not yet open sourced. Also that it runs but at a very slow frame rate going on to say that it is due to hardware acceleration not yet being enabled

I think :) Anyways good luck
[Nexus One Android Development] kiwi89:
Just giving this thread a little bump.

Good to see the progress that has been made so far :)
[Nexus One Android Development] KnightMAREcrow:
Received the G2 yesterday, I'm hoping this development will find its way to the G2 dev thread. As usual good luck devs, waiting to donate :)
[Nexus One Android Development] HolloH:
Not a dev at all but this seems cool so all I can really do is bump
[Nexus One Android Development] zen kun:
just a little bump for this :D
[Nexus One Android Development] Fiddlestix:
Why we bumping a thread without a rom?
[Nexus One Android Development] sergioalvarezmac:
Hey guys, any news?

I hope I can see Meego on Nexus.

Good luck with it!
[Nexus One Android Development] bassaq:
meego 1.1 running...

anybody will try?

http://blog.mitsutaka.org/2010/11/meego-11-for-nexusone-status-and-how-to.html
[Nexus One Android Development] RinTinTigger:
NICE!

Will try!
[Nexus One Android Development] fidorulz:
We need this to be made into a flashable zip for easy flashing for all users. It may be hard but all the code is there

Would be great ROM
[Nexus One Android Development] gupta.keshav94:
Is it working for you? BTW will it run alongside android or we can have only either android or meego??
[Nexus One Android Development] fidorulz:
No haven't tried yet since im not too good in coding. That why I would love this to be available in easy to flash ZIP format
[Nexus One Android Development] sergioalvarezmac:
+1 on that. The only thing I can do with my knowledge (very limited) is flash a ROM :D

But this is cool. I hope someone could make it easy for us.

Thanks for the info.
[Nexus One Android Development] geney:
Wow!!! That's lots codes... ...:D
[Nexus One Android Development] gupta.keshav94:
Anybody tried it? :D
[Nexus One Android Development] enatefox:
I just need to know how to fastboot the rootfs in an image or tarball. I don't want to have to partition the SD card:

sudo ./fastboot -c 'root=/dev/mmcblk0p1 rw rootfs=ext3 init=/sbin/init rootwait noinitrd' boot zImage

that needs to say /dev/mmcblk0p1/meegorootfs.tgz but I'm not sure how.

If I can get that I can move on to putting what I have on git so we can collaborate the bugs. I have a kernel and the root compiled just need help getting the setup right to boot
[Nexus One Android Development] wind0zer:
excited

Will this have acceptable phone reception and battery for daily use, or is it simply a proof of concept kinda thing I wonder?

From the news about Nokia's transition into Meego I expected the Nokia N8 would've had Meego. Nokia also bought Swype; I like the direction in which they're moving. I Hope to use N1 meego instead of N8 and way before the N9 comes out ; )
[Nexus One Android Development] _Opiate_:
Hmm this would be interesting to try out but only in update.zip form. I'm not that into that OS to go through all that trouble.
[Nexus One Android Development] storm99999:
Alrighty guys, I may as well chime in.

Meego 1.1, if it's like 1.0 probably has no cell phone parts. There's a dialer, but I'm not sure it will be easy to get it to work. Interestingly enough, the Moblin x86 build has had the cell parts this whole time, probably because of the Intel partnership.

As for an Update.zip, well, it actually can be done. The root directory would have to be loaded with symlinks to /data/ or /system/ where the core of the Meego files go. Then it would work identically. The problem is that the N1 only has, what, 512 MB internal memory fractioned off in partitions? The last 1.0 build I installed was 430 MB. It could fit, barely, in a messy way, but multi sd-card partitioning and a dual boot bootloader will be a better, easier, undoable procedure.

However, we could jury rig a script to automate an install. Then it will be easy for many.
[Nexus One Android Development] dictionary:
It'd be so boooosssssss if you guys could get it fully running, and it was actually quick enough to daily
[Nexus One Android Development] enatefox:
storm can you tell me how to fastboot the tarball/ext3 img? I don't want to partition my SD card and can't find how to pass it (with the -c flag?). we can worry about fitting to NAND later
[Nexus One Android Development] storm99999:
I'm reading it as if you just uncompress it to a mounted ext3 mmcblk02 or rsync it through the old method. I haven't tried it yet, so don't hold me to it.
[Nexus One Android Development] KnightMAREcrow:
Glad to see a familiar name, welcome back to this thread storm. Still hoping we might see a dual boot for meego and android :)
[Nexus One Android Development] storm99999:
Yeah, good news on that front, this next week, though it does include school, is functionally break. Minimal homework, only one test, slight chance of rain, the usual.

I plan on this week getting DL links up for the kernel and the root FS as detailed a bit prior, just so people who are good userland devs don't have to set up a dedicated build environment. Now, it appears that since we have wifi, we have a gui, there are two targets of things that need work. One is the GPU driver. From my experience in the GPU threads around here and earlier results, the main target would be to cross compile the header object files. I honestly think that everything else is already in place except for those.

The other is the radio. Now, the Meego 1.0 version had only a radio interface on Moblin builds. Hopefully this has changed, but it's doubtful. I'll know once I have my SD card converter. Anyways, we have the dialer, we should just need to hook up the right AT commands to the right /dev/*some serial port* or something like that. We have the android source for how it's done with our kernel already, so this shouldn't be too hard a task. Anyone feel like mapping it out?

Edit: Oh yeah, unrelated, hopefully I'll fix the Sith bug in my other thread too. I kinda left at a bad time, didn't I?

Edit2: Uh-oh, it's next to freaking impossible for me to make a current image. It's all sorts of broken on my build, failing by saying that I have no /bin/sh. Sorry I won't have anything up tonight.

Edit3: No longer uh-oh, just a PEBKAC. I was building it for x86 with an arm7l configuration.

Edit4: I got it to boot, but no real success. The screen will flash to black once and then flash black and stay that way for ~2 minutes that I tested it. Since the screen is off and there are no indicator lamps, I cannot tell if it is broken or no. The only information I can gleam is this:

To put the .tar.gz file on the device, run this command:

sudo tar -xvzf meego-handset-armv7l-nexusone-1.1-1.1.20101107.1852-rootfs.tar.gz -C <mounted mmcblk0p2 dir>

If it's not root, it won't work.
[Nexus One Android Development] ninjarock3002:
i read blog.mitsutaka.org.

i downloaded android-msm-2.6.32 ($ git clone git://android.git.kernel.org/kernel/msm.git -b android-msm-2.6.32 android-msm-2.6.32)

then i don't understand next instructions

I'm newbie...he/:D
[Nexus One Android Development] [-o']:
Yeah, I give my full support for this project!
[Nexus One Android Development] storm99999:
Hehe, I was the first one to get it up and running and I have a bit of trouble following the guide. Somewhere along the line, the file system I make just doesn't work... So, I can't help you there.
[Nexus One Android Development] ninjarock3002:
Thank U.

i don't undrestand this step :

Then, Preparing cross compiler. cross compiler uses prebuilt.git from Android git tree.

Can U explain????

he.thanks
[Nexus One Android Development] matiu:
Someone with the right skills could compile a simple installation .zip?
[Nexus One Android Development] SuperUserMovado:
android brothers from another mother

have any of you tried using kexec-tools instead of fastboot to boot meego

I am trying to boot meego on the Xperia X10 with kexec-tools since we cannot use fastboot at the moment.

I formated the sdcard to ext3 and copied meegos rfs onto it.

I placed the zImage into the root of internal memory.

(The memory card is not recognized when android boots.)

After android boots i use connect bot to launch the commands

kexec-tool -l zImage.img --command-line="init=/sbin/init rootwait root=/dev/mmcblk0p1 rw rootfs=ext3"

sync

kexec-tool -e

I don't have a nexus one so I don't know if this is an issue with my phone or the commads I am passing. Can someone give this a try with their phone. This will not brick your device, if it fails (which it has for me), your phone will simply reboot.
[Nexus One Android Development] sleepr:
has this project been abandoned?
[Nexus One Android Development] samuel2706:
I'm guessing so buddy
[Nexus One Android Development] swapniladsure:
i have nexus one ..tell me steps in details...

hey dude i have nexus one...tell me steps in details...also tell me which files to be downlaod..and where to type commands ( enter command ) ...

please tell me all details steps...
[Nexus One Android Development] MegadetH93:
hey

a couple of monthes ago i was trying it for meego and i got my meedo.ing from meego 's website,they have made an .img one specially for nexus one! check out their site.
[Nexus One Android Development] firechaos:
omg omg things getting interesting
[Nexus One Android Development] bazza_1988:
Do you have a link for the .img?
[Nexus One Android Development] narcisco.cruz:
Sounds like a bunch of bull why not post the semi URL or semi link
[Nexus One Android Development] linuxmanju:
May be this would help

http://wiki.meego.com/ARM/MSMQSD
[Nexus One Android Development] theGanymedes:
Well, I saw a question on that page, asking if Bionic and GlibC can coexist.. Well it does! I did it on Desire, but it has nothing special about Desire (maybe recovery scripts do need some editing, not sure).

If the developer of MeeGo is still around (or anyone interested in project), please contact me - I'm very keen on this stuff lately ;)

GlibC in Android post: http://xdaforums.com/showthread.php?t=1299962
[Nexus One Android Development] LuHe:
Thanks you! You've done a really incredible job!

I'm still interested in MeeGo - but in other ways: I tried to port the MeeGo successor "Mer" (the community project) to the device and use Plasma Active as UI. It's still a long way before it's running but your post will really help ;)
[Desire General] abc27:
http://repo.meego.com/MeeGo/releases/1.0/core/images/meego-n900-open-armv7l/

My idea is to use the current effort to run Ubuntu/Debian on the phone as a method to get MeeGo running on the phone as well (Maemo should be similar). What we'd need to achieve is to get an .img of MeeGo/Maemo as we do Debian/Ubuntu. Driver issues (If present) should be rectifiable by porting over some of the Debian/Ubuntu ARM drivers.
[Desire General] Mestr:
Great idea! I hope devs will start working on it!
[Desire General] BlackDragonBE:
Great! Tell us when you're finished!
[Desire General] Ireas:
Looks like they made some progress, as the N1 Version is already avaible

http://wiki.meego.com/ARM/MSMQSD
[Desire General] d3sm0nd:
Anyone working on this ?
[Desire General] mr.r9:
Even if someone is working on it, I don't think it'll be as simple as "Install Meego through update.zip in recovery". However I hope so:)
[Streak 5 General] AndrewKl:
Just got my Streak the other day and noticed that it's quite difficult for me to get the haptic response from the three side side buttons (return, menu, home), particularly the return menu. I usually can't get a response from a finger tip unless I touch it repeatedly, and I usually need to press down harder than I think I should and with at least a half inch diameter of my finger. Is that normal?
[Streak 5 General] squalllion1uk:
Sounds odd never had that problem I can just tap mine quickly and it picks it up. It could be possibly where your pressing maybe.
[Streak 5 General] AndrewKl:
Thanks for the reply. Is yours as sensitive as touching the touchscreen? Mine definitely isn't.
[Streak 5 General] Techneut:
This seems to depend on your fingers! (too dry or wet skin?)

Try to let somebody else do the same thing...

You will be surprised.
[Streak 5 General] Troute:
I did first think maybe your fingers were not conductive enough but as you say the screen is working ok then I reckon your buttons are not working as they should. Contact Dell or your provider?

For reference my screen and side buttons seem to be equally sensitive, in fact I could do with the side buttons being a little less sensitive..
[HD2 Android Q&A, Help & Troubleshooting and Genera] chenyufei.1992:
how do you guys manage to sync it with some syncing software, i mean i was trying to install some apk and games, i just can't use my apk installing software on pc, cuz the device is not found, the only thing i can do when i connect hd2 to pc is using it as a usb drive, and it's in the debugging mode. anybody has any ideas how can i make it sync with my apk installing software or can you give me a way to install some apk to my hd2, much appreciate it
[HD2 Android Q&A, Help & Troubleshooting and Genera] chenyufei.1992:
ok, i 've just tried astro, the problem with that is, i created a foder and put apk files in it. and i can't find them in astro at all, not only the files but also the whole folder, they all just disappear............somebody help me out