yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] rafroehlich2:
I would do a Google search to see if there are any old articles with a download link.

Sent from my PC36100
[EVO 4G Q&A, Help & Troubleshooting] twilk73:
There are several other functions you could do like set the home button to go to home page and if on home page drop down notification screen or to just drop down notification screen. You can also use the swype up or down function to access the notificaion screen. I have my home button set to drop it down but nine out of ten times i just drag the notification down and because i gott get my finger up there anyway lol I know its a stretch.
[EVO 4G Q&A, Help & Troubleshooting] nsolo1717:
i personally cannot find the option to add more home screens in ADW launcher version 1.1.3 . Don't know why it's gone. The option used to be there. Does anyone else know why i can't change it from 5 screens to whatever i want any more?
[EVO 4G Q&A, Help & Troubleshooting] jtc442:
Hit menu, then the edit button, then click on one of the green plus signs. That's what I did, and I have 7 screens now.
[EVO 4G Q&A, Help & Troubleshooting] nsolo1717:
thanks, just got confused because i remember the option being elsewhere, but not i see the light.
[Off-topic] htc fan89:
On august 27th at 12:30am eastern mars will be shining as the moon this is a rare chance to see mars with the naked eye. Mars will be 35m miles away from earth. Next one will happen In 2287 so no one now would be alive so watch it.
[Off-topic] [★]:
Thanks man! will this be visible from britain?:p
[Off-topic] b0dge:
Looks like this could be a hoax:

http://earthsky.org/astronomy-essentials/best-time-to-see-mars-in-2010

http://www.snopes.com/science/astronomy/brightmars.asp

I just did some googling to see if we could see it from the uk... :(
[Off-topic] htc fan89:
Ahh I was so excite anyway my uncle emailed me this so gotta tell him it could be a false.
[Off-topic] chopper the dog:
Original Android has a shot.

good day.
[Off-topic] jaszek:
My friend told me about that, and first thing I though was "BS". If it was so close it would be comparable to the size of a full moon, then that can't be safe. Mars is about twice the size of the moon, that means it would have to be twice as far from the earth as the moon (about 700,000 km) at perigee which is not far considering space, and mars is about 55 MILLION km from eart so then it would have to travel about 52 million km and be in the exact position to be compared to a full moon. Yes, you can call me a geek, and yes, I did these calculations in my head (but I think anyone can, it's not hard)
[Hero CDMA General] chromiumleaf:
Hey all,

Little late in the game, but I want to start doing my own theming. I searched around many places and found several really good guides on creating and dev'ing themes:

http://xdaforums.com/showthread.php?p=3175518

http://xdaforums.com/showthread.php?p=4438978

seem to be a couple of the really comprehensive ones.

Got them from the OP in one of our own Hero Themes and Apps sticky post: http://xdaforums.com/showthread.php?t=588351 which also has some great stuff in it.

My question is....both of those I linked above seem like older posts. Is there anything more current, and perhaps specifically for our Hero, that I should use or be aware of? Or are these still good guides that will work well even now?

Feel free to flame/bash me if I've missed anything obvious out there. Thanks for your input.
[Hero CDMA General] Papa Smurf151:
Check out my everything android thread in dev section. It has all the tools ull need plus links on how to use them
[Nexus One Android Development] 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.
[Nexus One Android Development] storm99999:
I personally think it won't be too hard.

You compile it with the right GCC, fix any possible errors, then add an android kernel (hoping the API doesn't change, which is a longshot and probably the biggest obstacle). After that is set up we move everything to their appropriate partition, fix the path, and it really aught to work then.
[Nexus One Android Development] chrisvuong:
i have no idea how to and how hard, but i think if people can port Android to iPhone , so this wont be something impossile :D
[Nexus One Android Development] dictionary:
I would absolutely LOVE for this to come true. I've been frustrated with my gma500 netbook, since I can't run Meego, or even Moblin. This seems like it would be fun to run on the n1.
[Nexus One Android Development] KnightMAREcrow:
Should we start a bounty, I would be willing to put money up for this, dual booting two open source systems would be great.
[Nexus One Android Development] maxisma:
Same here! $5 from me for the person who gets it to boot!
[Nexus One Android Development] Puenos:
Finally! I've waited for someone to take up this work!

Not that I could be of any help, but I appreciate your efforts and hope for your success!

Good look! :)
[Nexus One Android Development] enatefox:
Will be working on this. I don't think I want to flash it instead of Android and as a chroot it'll be more compatible (among ARM7 at least for now..) with other phones. Been barely successful with my old ATT Tilt w/1MB of RAM I gotta see what a Nexus can do =D
[Nexus One Android Development] jbbandos:
You know that the recently released Intel EMGD drivers work on Maemo? Since they are a binary blob even worse than the PSB drivers, they won't work on (k)ubuntu, only on Maemo and Fedora 11.
[Nexus One Android Development] enatefox:
i'm hazy on how we got fb support on kaiser/vogue but they're msm7k boards as well. i could be wrong but i believe team douche already has it built in. i did a lot of trial and error today to get a chrooted x-server to override android's display. i'm not sure how to get the hardware support because i fail at it and thought it would be easier to hybridize maemo over android at least for testing.

i'm all about getting this to work but irc is tedious so if anyone is actively working on it, i'm down for the cause.
[Nexus One Android Development] storm99999:
I plan on, when I get time, starting my attempts. It would be much easier if I could see the basic layout of the system, but I'm so inexperienced that I don't know where to start. I have a basic idea what to do with the source once I get it, but most of my assumptions rely in part on what I can find out.
[Nexus One Android Development] enatefox:
it's basically ARM Ubuntu w/a ton of customized UI but a basic Debian based distro nonetheless which is why I <3 it so much.
[Nexus One Android Development] storm99999:
Well, I guess it won't be too bad then, I personally was hoping for something that was update.zip capable, and a few simlinks might just do the trick.

The key questions I can think of so far are: how are the files are laid out, how does the window server interact with the kernel, what modules will be essential, how does the phone interface with the radio, minutiae like that.
[Nexus One Android Development] evilkorn:
The main road block I see is that we have still not yet been able to run anything outside of virtualization. I'm not sure how the boot process works outside of running an Android build, but a pure solution would be needed for best results.
[Nexus One Android Development] enatefox:
yes we can:

http://xdaforums.com/showthread.php?t=631389

who wanna help me
[Nexus One Android Development] storm99999:
I'm in. I found out something interesting yesterday, the Adreno 200 2D framebuffer is a standard kernel interface. So, if 3d acceleration isn't a priority, we shouldn't even have to port the windowserver. Heck, I'm pretty sure we won't have to port anything.

I guess I'm going to look at the source for debootstrap and see what hints I can gleam from it though.
[Nexus One Android Development] enatefox:
what do you need from debootstrap- it just pulls down the system image but we have meego's already.

here's what we have so far to play with, where to start?

custom dual/tri boot recovery image we'll need to avoid fastbooting the kernel:

http://xdaforums.com/showpost.php?p=5521417&postcount=5

i'd like to mix this into amon's or clockwork mod source with a text file on the SD card to configure kernel parameters

how to boot debian/ubuntu which we'd swap for meego's system:

http://xdaforums.com/showthread.php?t=631389

should handle enough to fully boot this thing

including his premade zImage you can mess with if you suck at compiling:

http://irregular-expression.com/tmp/zImage

meego's system as linked in the OP:

http://repo.meego.com/MeeGo/releases/1.0/core/images/meego-n900-open-armv7l/

no gsm, no audio, crappy fb based x11 w/o drivers.
[Nexus One Android Development] storm99999:
What system image are you using and how are you unpacking it? I'm not too worried about drivers, as with GSM I'm pretty sure that the API is either already set up as we need it or configurable. People on debian were getting texts to send at one point if memory serve
[Nexus One Android Development] enatefox:
meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw.bz2

should be the one. i believe it's an ext3 partition but haven't looked at it yet as i was looking into the debian thing. i mean gsm support for our boards which should be okay if we branch off of cyanogenmod's or similar. and if i'm right then "okay" means "complete support."

let me be more specific:

http://wiki.meego.com/ARM

and if you look at the MSM link it references a repost of the debian guide as well..

adapt these instructions for working with the image on your desktop:

http://wiki.meego.com/ARM/N900/Install/MMC

and as further motivation, remember when the N900 got x86 WINE via a statically compiled ARM QEMU binary within a x86 chroot? with an x-server we don't have the ****ty VNC fail we've currently had. we could truly run x86 chrooted software (or anything in a chroot like hot-swappable desktop distros) and connect to the host (maemo's) display. and the possibilities with xephyr nested x-servers.
[Nexus One Android Development] storm99999:
Well, great news on that front too, they use X.org by the looks of it. There's a 3d acceleration driver under development for it. I'm going to try first with a SD card install, as weaving around the wacky partition format is annoying. It'll be a few hours until I'm using an x86 system though to compile the kernel. By the looks of it, the kernel has to be custom in order to use an initramfs partition.
[Nexus One Android Development] enatefox:
and on that thread, people have modified cyanogenmod kernel to boot debian successfully. the kernel is fastbooted because of the whole recovery thing (for now). i'd recommend using his as a base and hopefully it can be merged later for l33tness
[Nexus One Android Development] storm99999:
Ahem... "I'm making a note here, huge success. It's hard to overstate my satisfaction!"

I did it. It doesn't boot to a gui yet, I still have yet to figure out how to do that, but I got x and xterm up. Yay! So, I'll do my best to get a gui (or hell, an onscreen keyboard or ssh would be nice) and put up instructions soon.

cjosey, on Flickr

Edit:

What works:

Framebuffer

Touchscreen

Rollerball

What doesn't:

Battery light doesn't turn on

No keyboard yet

No GUI

Does anyone have a mmc image like the one that was linked earlier for maemo 5? I know it exists, but Nokia is locking it off.
[Nexus One Android Development] KnightMAREcrow:
Storm for president!

Kidding aside great work, this is going to be a huge accomplishment.

Good luck to both of you

Edit: Would this help for your MMC image - http://wiki.meego.com/ARM/N900/Install/MMC
[Nexus One Android Development] storm99999:
No, I'm looking for the nonfree one, the one with a GUI. Nokia locks that file away all sorts of hardcore. I need to give them an IMEI and I only get 1 hour to download it.

I'm looking at a beagleboard guide that ended up with a gui. I'll try there first.

Edit: It appears their git repo has a gui. Hopefully... I don't feel like pirating an entire os.
[Nexus One Android Development] teamsilence:
Sorry to be off topic but I am glad to see maxisma and enatefox in n1 forum now... we are in good hands =) welcome
[Nexus One Android Development] storm99999:
So, yeah, for those who like ramming their heads against a wall, a guide!

This doesn't work. At all. But it's easy to have it not work, at least. So, only if you want to dev this, here's what you need:

Debian zImage, any and all pretty much work.

Meego MMC image.

Mount the SD card on your device.

Alright, in your happy linux install, back up your SD card in as many ways as possible.

sudo dd bs=4096 if=/dev/sdX of=imageback.img

Where X is the id of your phone's SD card.

Then, you want to put the meego image on your sdcard.

sudo dd bs=4096 if=<wherever it's downloaded>/meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw of=/dev/sdX

Then, once that's done,

adb reboot bootloader

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

Seriously, that's all. :)
[Nexus One Android Development] enatefox:
you don't need anything proprietary. the mmc guide is mainly because of nokia drivers. i can get the image together for you. you can build and download qemu images and the like freely i just forget where that was at the moment.

did you compile the kernel yourself or use the test one i linked to? i want to get a guide together for modifying the config off of cyanogenmod's kernel. best we stick to it and see about a merge/commit

as far as i know, adb should work immediately (assuming you pushed adbd to the image like i will). the main problem i saw was getting the framebuffer loaded which would only occur after userland loads-- assuming you get that far of course ;)

with adb comes ssh access so don't worry-- and they got usb host as well for keyboard/mouse support.

on to other good news, punkkaos is going to help with a custom recovery so we can use haret-like config files and have on-phone dual boot support for the kernel. of course, merging the kernel would be ideal but the system will either be in NAND or on the SD card. however.. he'll get us hooked up with that =D
[Nexus One Android Development] storm99999:
It has a framebuffer already. It loaded X. The problem is there was nothing else for X to load and I couldn't get my system to add adb to the image file until after I added that. There's no GUI past Xterm to use.

The other thing I see is that we're using native ARM hardware and no one has yet built a gui for the N900 yet.

The kernel was the one you linked to.

At the moment, I'm making my own image to see if I can hybridize the N900 configuration and the Beagleboard one.

Edit: Yes, there is a rudimentary GUI already, but it's very much beta software so it's not in the semi-stable releases.
[Nexus One Android Development] enatefox:
no, i mean people were having that issue. you obviously didn't fail.

what do you mean no GUI?

http://meego.com/downloads/releases/1.0.80.8/meego-handset-day1-developer-preview

success should look like this:

http://meego.com/devices/handset/handset-screenshots

i could care less about meego to be honest (at this point) i care about the phone connectivity of it. it's a full fledged ubuntu distro and we have over 9000 apps for it as is-- the desktop is more than vetted. if we get this stable to run, we can work from there. you seen moblin (which was merged into meego) right?
[Nexus One Android Development] storm99999:
The N900 version of the same thing has support for that, but I can't download it. Clicking on N900 support prompts for an IMEI to download. I have to make due with the free code only.

Edit, anyone with an N900, can you download http://tablets-dev.nokia.com/meego-...armv7l-n900-nokia-closed-1.0.80.8.20100630.ks or anything later in that folder for me?
[Nexus One Android Development] enatefox:
i can't boot this yet (pls shr ur setup kthx) but what am i missing here?

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

"Day one codedrop available here: http://repo.meego.com/MeeGo/devel/n900/images/"

"The image with Nokia proprietary components can be loaded from here:"

^ this is the one that asks for the IMEI
[Nexus One Android Development] storm99999:
Yeah, those proprietary components include such things as a GUI, but currently, I'm building a new version that has fennec included and a basic GUI, so problem solved, sort of. Using the free-only will boot to Xterm and that's it, which is what I have shown in my success image.
[Nexus One Android Development] enatefox:
gotcha, their layout is literally a short bus. it doesn't matter at any rate honestly GUI or not. we can load any desktop we want, any software we want, etc. all that does matter is phone functionality but i think we're missing where that's at as i highly doubt the dialer is closed source.

specifically, i can download the x86 netbook image right now-- with full desktop. we need the handset equivalent.

like this: http://wiki.meego.com/Image_Creation
[Nexus One Android Development] storm99999:
I think the dialer isn't proprietary, but I won't know how to figure it out until the build is done.

Edit: I've found the proprietary URL, but to be honest, if I can get it to work without it, why bother? If this run doesn't work, I'll add it though.

Edit2: Neeeeed faster SD card. Class 2 with a 1.8GB transfer?! Oh well, got to plan ahead if I am going to deal with 600s transfers with any regularity.

Edit3: Yes, dialer is available by the looks of it, no I can't get my system to boot with my new build.

Edit4: Nor can I do much of anything. It just plain refuses to boot anything. ADB won't even come up and I added it.

Edit5: And I found out why, so I'll try again. Why do I do these long edit trees?

Edit6: No more SD card to work with anymore. dd refuses to work on it, though I suspect it might be the image I made.
[Nexus One Android Development] enatefox:
if you can fastboot the kernel, can you use remote (on PC) images or is that a pipe dream? i'll look more tomorrow
[Nexus One Android Development] storm99999:
Alright, so I think there's something very screwy going on.

If I build meego with /dev/mmcblk0p1 as its target, the kernel will just keep trying to boot. If I then change it to /dev/sda as its target, the system will die after 5 seconds of running. If, however, I say that the kernel should boot off of say /dev/myface, it'll act like I built the partition for /dev/mmcblk0p1. So, I think the system immediately crashes after boot and it must be configured as a /dev/sda device. I'm going to add adbd to my build here soon and have it so that it only loads X. This will give me a good indication of what's up.

Only running X still nukes it. I'm using the latest weekly, but the nightlies had a big jump in version #.
[Nexus One Android Development] KnightMAREcrow:
Is it feasible when Meego officially drops?
[Nexus One Android Development] storm99999:
Maybe, but that gives me an interesting idea. Due to some friendly help, I have access to the downloads of the official Maemo 5 eMMC release. I could try those, but I obviously couldn't help anyone else get them. It could be done as merely a proof of concept though.

I'd much rather get an open-sourced build to 100% though. That I could share with everybody.
[Nexus One Android Development] KnightMAREcrow:
theres an update to the look and feel of Meego, One unthemed and one themed. IMHO the green theme is hideous.

Anyways I wanted to ask you (storm) if you are aiming at trying to port over the untouched meego from the screen shot, that's what I would love to see dual booting with android
[Nexus One Android Development] storm99999:
I hope to get something working but until this stuff is stable, the target is moving quite fast. When MeeGo hits stable, we then know that, if it doesn't boot, it's because of an incompatibility, not an error, and we can make serious progress on it. The one that I photographed works 100% but without a keyboard, but nightlies don't, even with mcompositor disabled.

I'll upload my .ks file I got from the MeeGo proprietary server in a bit with the proprietary guts removed. We don't need them anyways, it's the N900 specific battery manager (our stuff's kernel level, so it doesn't matter) and the wifi firmware. I don't even need to frequently update it as the data is surprisingly human readable.
[Nexus One Android Development] enatefox:
down but not forgotten, im still working to get this going. looks like we'll have a dual-boot recovery very shortly as well =D. can you please upload what you do have so we can work off of it?
[Nexus One Android Development] storm99999:
Sorry about that, here's the .ks file without the proprietary stuff we don't need. It should be kept up to date, and yes, it is identical to the one on the proprietary server except this one is keyed to the daily build server and there isn't a proprietary repo.

http://meego.gitorious.org/meego-os...s/blobs/master/handset/handset-armv7l-n900.ks

Oh, if @BUILD_ID@ is not populated automatically, it should either be replaced with "daily", or one of the weeklies found here: http://repo.meego.com/MeeGo/builds/trunk/

(For example, right now, I'd use 1.0.90.1.20100907.1 for the ID as daily is out of date...)
[Nexus One Android Development] ermacwins:
Where did you read that?
[Nexus One Android Development] maxisma:
This is a tes.. uh no it's a bump.
[Nexus One Android Development] kiwi89:
bump.

Would love to see something like this happening.
[Nexus One Android Development] enatefox:
Punkkaos said he got dual boot recovery. I'll check with him on an ETA. Now I have to try to build this. Also shameless bump

About to boot my first attempt using a stock n900 image. If I win, I'll be as far as you storm99999-- X-server but no desktop. That I can deal with. Threads not dead!
[Nexus One Android Development] chrisram88:
u can do it cuz ur lady puts up with your devvin :)
[Nexus One Android Development] crpercodani:
this would be fantastic
[Nexus One Android Development] enatefox:
lulz. twitter has invaded the thrad. tonight was a fail. it's still on so i'll keep this thread going as my lady puts up with it and donations come in. hopefully others do the hard work for me so i can take credit. i've been craving giant red text about donations lately
[Nexus One Android Development] storm99999:
Let me know if there is any way I can help. I'm currently on a temporary programming break due to brain asplosion so that's why I've been out of the forums, but I can help out wherever I can.

Of great importance, is there any X based visual keyboard? This sure would go a lot faster if we had one, as then we can disable all that doesn't work and selectively enable it at boot.
[Nexus One Android Development] enatefox:
touch screen is working? i don't think you'd have luck unless a window manager was available. adb should be available if you follow the previous links to link adbd. they said it was available at boot or you should be able to ssh if nothing else.

i failed before because i'm trying to work around partitioning-- stupid user error.
[Nexus One Android Development] kiwi89:
Yea, I didn't think the touch screen would initially work. But yea, sshing to the phone shouldn't really be a problem if adb isn't working.

I'm going to have a bit of a play with this on my hero and see if I can figure anything out.

edit:

Just found these links that may be of use:

http://wiki.meego.com/ARM/MSMQSD - this guy seems to have gotten something booting on his nexus one.

http://forum.meego.com/showthread.php?t=1381&highlight=android

http://forum.meego.com/showthread.php?t=955&highlight=android
[Nexus One Android Development] storm99999:
Yeah, touchscreen is functional, but barely. It acts like a laptop touch pad, not mapped 1:1. the trackball is click, and it works to scroll too.