yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
It should be no more then 8 seconds then you should see the kernel loading.

After the kernel loads it should error out and tell you if the partition is incorrect or it should start android.

If it's stuck at "jumping to kernel" try making sure that the phone is turned on and that wifi is off.

If this does not work i recommend trying a different rom as a few i have tried would not allow it to load.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
Latest cmfroyo is booting on my Uni, the vibrator keeps turned on...

How do I turn off the vibration before my device chokes?!?

It stopped. I wonder if it's because Android told it to, or if it's because the vibrator choke.

---

And now? How do I open the menu in order to change the settings to make it run close to full speed? Sometimes the screen goes all grey, but then it goes back to the home screen after some time - is the grey screen the menu? And the phone is getting hot - I hope it's just because bluetooth is still enabled.

---

OK, I managed to open the menu by pressing enter on the keyboard. But it's damn slow selecting items... I press "down" and it goes down after 15 seconds... or more.

---

Is there really any way to not turn on the vibration at startup? Does it turn on for debugging or do things really need to be this way if we want to have vibration from Android?

I already rebooted the device a lot of times because it seem hung and vibrating. I'd patiently wait for Android to startup if it weren't the fear of the constant vibration to damage something. Sometimes the vibration stops but then it goes back after some time, it looks like there's some process telling Android to turn on the vibrator but that process is hung and not responding. My device has 64MB of RAM... Is it because of that?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
One of the newer kernel's from the first page should have it turned off. On my universal with 128mb of ram i can just toggle the vibration or touch the lock screen and it stops and works normal after that, but it takes too long to do this with 64mb of ram and it running slowly. I haven't found the code yet in android to turn it off at startup but that should fix it....but until then it's just disabled for now.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
I was using an older kernel... I downloaded the latest zimage from the first post, replaced the files on the card and the first time I tried it got stuck on "Jumping to Kernel". I'm now waiting for the device to reboot to try second time. I'll keep this post updated.

EDIT: ...and I'm using original WM5, not WM6 custom ROM like madkat.

UPDATE: Hung... when Jumping to Kernel... what a hard jump! :D

It must be this latest kernel. The other one worked, although it vibrated like hell. Too bad, I overwrote all the old files and I have no backup of the older kernel.

EDIT2: Is the setcpu.txt file really needed? For what? It sets CPU speeds from haret before it jumps to kernel, I guess... is it possible that that's the problem?

UPDATE2: Nevermind. You don't tell people to, but in 64MB RAM devices you need to edit startup.txt and put 64MB for the memory instead of 128MB. Now it works. I'd be good if you updated your first post to concentrate all the information for newcomers in one place.

And, by the way, with the new kernel, the vibrator still vibrates. But Android seems faster to boot. Any ideas to stop vibration?

UPDATE3: It is asking me for the PIN code for the card. But the screen is always turning on and off (the whole screen, not just the backlight). And the vibration, as always, doesn't stop.

Why does the screen turn off? And now the vibrator stopped. But, the speakers are making strange noises.

If this weren't my device and your port, I'd laugh and call this the "Halloween Android Port - Special Edition Zombie" :)

FINAL UPDATE: The speakers didn't make more strange noises, the screen didn't come on again, so I reset the device and I won't be trying Android more today although I really wanted to. Thanks for your help.
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
notime2d8, thanks for chipping in! Isn't zImage the "kernel" in this context? It seems like it's zImage that has the problem, since haret-w can't JMP into it (or else the system is hanging at that point - I'm not getting any decompression messages, for example.) Is there any extra cmdline option I can add to get more verbose output, if it were to be called?

By ROM, do you mean root .tar.gz or do you mean an alternative zImage? Where would I find the latter?

Going to recheck my startup.txt for 128MB as per gbl08ma's post, and report back... seems obvious when you think about it!!

Thanks again

-- EDIT --

"Working" now I moved from 128MB to 64MB, but only up until it says "warning: `rild' uses 32-bit capabilities (legacy support in use)" - waits for quite some time, and then the screen blanks, and nothing happens after that.

-- EDIT --

Retried, found I could hit Enter at the term and get a prompt, so not related to the warning message. Waited for a long time and eventually got a bar at the top with time... and got the everlasting vibration problem :) I'm going to grab another root image and try that... and take a lesson in patience ;)

-- EDIT --

Seems fine, but very slow - with cmfroyo.tar.gz I had the vibration issue, with data.tar.gz I kept getting not-responding issues. With data.lite.tar.gz I can at least see icons, but haven't managed to get to settings yet!
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Have you cmfroyo.tar.gz or data.tar.gz? Data.tar.gz is newest port.

If it is slow you can run donut. It is faster and have free some ram:D.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
I have cmfroyo.tar.gz. I didn't notice data.tar.gz was newer. OK, so this invalidates all the problems I have had. I can't wait to try this new tar.gz on my device with the latest kernel (zimage).

Let's hope it works better than the other one!

I'm not willing to use Donut, because Donut is waaay outdated (circa Android 1.6) while there's already Android 3.1 (something that makes froyo builds still a bit outdated) out there. And if I were to use outdated software, I'd rather stick with Windows Mobile 5 (and even let my iPaq PDA with WM 2003 instead of a unmaintained Linux distro from 2006).

I'd much prefer to help working on Froyo until is it scaled down to 64MB RAM than use Donut.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
I think so. As you said, and done later, change 128MB to 64MB and it'll work.

You're using WM6 = you're using a custom ROM <-- All HTC Universals come with WM5 by default, so by custom ROM I meant you were using a WM6 cooked ROM. Nothing to do with Linux, much less Android.

UPDATE:

With data.tar.gz I only get this, after waiting for it to boot:

This repeats every 5 seconds or so. XX is a random that increases every time and YYY is another number, a bit higher (most of the times 5) than XXX.

It looks like it is indefinitely creating processes then killing them. It goes this way forever until I reboot the device.

Is this a corrupted download, did I do something wrong, or is data.tar.gz not meant to be used in a clean ext3 partition? I always format it before changing of Android build or Linux distro.
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
Thanks orzech2111, I'll give it a go.

gbl08ma, notime2d8: I tried cmfroyo, data and data.lite, data.lite was the closest I got to it working. Will give donut a try, doesn't matter to me if it's 1.6 - so long as Market works :)

Donut seems OK, so far, except touch screen is uncalibrated and I can't seem to get out of the search box!! - actually touchscreen seems to be off. Might restart Android and see if it's any better. Would be nice to use the cursor buttons on the flip when in portrait mode. Don't know about anyone else, but I usually launch Android with the phone in landscape mode...
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Lifting up Dev!

To all Devs working on this project,

I am going to write an article regarding this great work you have been doing so far.

I would like that someone could post or PM me the following in order for me to write the article:

- Names of Devs involved

- What is working so far

- What is not

- Limitations

- What can we expect in the future

- Any special help you may need in order to involve other Devs as a support

Hope you guys are interested and can help me on this, at the end this will be helpful for everyone waiting Android on the great Uni:cool:

Thanks in advance,

P.S, To all members not developing or helping with beta testing please help us to keep the thread as clean as possible!
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
madkat:

I don't think you can get official Market on a custom Android port.

For me the touchscreen on Donut works perfectly. I'd like Donut more if the phone (and SMS, etc.) worked to some extent. I've read that minimum requirements for Android include 128MB RAM (versus the 64MB some Universals have), and that Donut is better for low-mem targets as it consumes less memory. But, obviously, also provides less features.

At the end, if I wanted an Android device, I should have paid 120€ for one of the smaller Xperia phones that come with Android natively (and you have Market, windows and desktop effects, well, native Android 2.1 or 2.2), instead of 75€ for a new screen on a 2005 Uni.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
.

Thanks to notime2d8 for sending such nice PM

I´ll be writing an article soon with the intention of pulling more attention to this fantastic work it´s been happening here!

Any other info Devs think may be useful to include please PM or post here

Thanks all!
[JASJAR, XDA Exec, MDA Pro ROM Development] onurdndar:
But then you wouldn't get the excellent keyboard, pretty unique form factor or the ability to run WM applications. Linux runs OK with it too, way better than I thought it would with a window manager and 64MB ram. It's truly a device that deserves to be called a Pocket PC.

75£ is a bit much though. I bought my second hand Jasjar for slightly more than that.
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
Donut touchscreen worked fine after a reboot, but no GSM/GPRS/etc.

I guess no market is fine if you're happy with free apps (I am!!) and have another device with which to acquire them.

Tried putting data.tar.gz back on and got the same suspend_state and untracked PID problem, no idea why this should be - I cleaned everything off the ext3 partition and made sure to remove anything irrelevant from the FAT partition.

I have an xperia x10 mini. Could get a keyboard with the mini pro, but you still only get QVGA. And it's got a phone-centric interface rather than a productivity-centric interface. I'd just like to turn my old Exec (I got mine on contract when they were new, then O2 tried to screw me over so I took the device & screwed them back) into what would effectively be a very very small netbook, and if it could interface with a bluetooth GPS and run Skobbler then all the better - then I could have SpeedView on one screen and Skobbler on the other. Not keen on bigger devices as phones (I used to go in for the tiny Samsung flip phones like the A300 before I started developing for Windows Mobile for work) and not convinced I'd do much internetting on a mini pro just because of the keyboard.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
You actually can get market working and location based apps using a Bluetooth GPS I was planning on adding market but it always runs in the background and uses a good bit of ram but it works fine, following the guides from other ports and tablets that don’t have market.

Which kernel are you using that has working touchscreen in donut? Is the calibration off?

And donut could have the same functions working wifi, phone, sound, ect. But I won’t have time until after I get my kernel and drivers perfect. Then i plan on working back on froyo/donut builds and ubuntu or another linux distro. :cool:
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
I haven't changed zImage since I started. All I've got is zImage/HaRET on FAT32 (always the same in all cases) and whatever root tree (e.g. data.tar.gz) on ext3. Only changes made to startup.txt have been to remove the commented lines and change mem to 64MB.

Still scratching my head over the request_suspend_state issue - maybe something hardware state related? Perhaps there needs to be more aggressive hardware resetting during init? Yet to try cmfroyo again. Not had much time for the past couple of days :)
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
May Angstrom? A lot work, some you can improve, and we can have good OS. Repo is on the Angstrom page and I sew here some interesting apps e.g. VLC or Aircrack-ng :p You have good platform for porting. I know it isn't very popular system but you will have easier way to make good port.

PS: repo page http://www.angstrom-distribution.org/repo/ . We have ARMv5te.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
Someone has already ported angstrom, look at this website:

http://www.unilinux.4fan.cz/?page=opie

In fact this opie image is an Angstrom image (pretty old obviously) where nothing of special works: wifi, bluettoth, phone, all of these DON'T work - this is where notime's drivers would fit. But the touchscreen works and you can play around with the few existing apps, nothing more.

I doubt we'll be able to get froyo running at an usable speed on 64MB RAM, even Android official docs says it won't, so I'm surprised that it even shows us the icons and the menus (although pretty slowly, but it shows). It'd be pretty damn good if we could, but I don't think that's easy. We'd need to scale down froyo so much that it would become donut or even worse.

At the same time, as the time passes by, donut is getting unmaintained - it's old software.

It's not really related to this thread nor Android, but I wonder if there is enough interested developers to pick up an existing ARM distro (e.g. Angstrom) and bring to it a modern UI (and new features) like Android? Both Opie and GPE are abandoned (or almost-almost-abandoned) projects, abandon highly visible since handhelds.org is "undergoing renovations" for almost an year. And neither Opie nor GPE are adequate to today's mobile phone concept (just compare GPE with Android, iOS or even Windows Mobile). So, developing something new keeping the low specs of the older devices like the Uni (but not only the Uni) would be useful and feasible as long as there are enough people willing to spend time coding it for free - something that I don't think that exists. End of offtopic :)
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I plan on working on Ubuntu and following the development of the Zipit Z2. It has 32mb of ram and runs versions of Ubuntu and Debian at normal speeds and seems functional. I’m continuing my work on froyo as it works perfectly with 128mb of ram and even if it is outdated it’s a good spot to be stuck at. Between updating froyo and working on the kernel and continuing to update it I’m hoping that I can free up an additional (hopeful) 10mb of ram giving 64mb users a total of 23mb free. That’s more than the amount I had free most of the time using my mytouch 3g. There are still memory tweaks and apps such as the phone and messaging that use a lot of ram that need to be replaced with lighter alternatives, the memory card read and write speeds can still be increased, people can move to class 10 SD cards, we're not using swap, and I’ve done none of the kernel tweaks for android so far like the other developers on this site. I still got a lot to do but in the end my universal is going to be more awesome then it already is….running android. :cool:
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
notime2d8, I really admire your enthusiasm :)

If I had the time and C++/lowlevel experience, I'd be right there with you, but these days I'm coding for the really big stuff instead of the really tiny stuff!

It's a shame Microsoft never realised their dream of making NT processor-agnostic. That was the idea in the first instance, and that's what HAL.DLL was for - the Hardware Abstraction Layer. With that said, it was quietly leaked that "Windows 8" is meant to be fairly processor-agnostic, I heard whispers of ARM...
[JASJAR, XDA Exec, MDA Pro ROM Development] phil.cooke:
Having a few issues.....

Well OK, One issue - I can't get past the "Jumping to Kernel..." stage.

Here's what I've tried so far:

1. Using Ubuntu and gparted, I've configured my SD card (tried 2 different ones so far - 1 x 1GB Dane-Elec and 1 x 2gb micro sd no brand) to have partition 1 as 40MB formatted as Fat32 labelled as "fat32", and partition 2 as the remainder of the disk formatted as ext4 and labelled as "ext4".

2. Downloaded the files from the first page (zimage.zip and froyo.tar.gz).

3. Extracted the 4 files from zimage.zip to the fat32 partition (there is no default.txt file though).

4. Using "sudo tar zxf froyo.tar.gz -C /media/ext4" I've put these files onto the ext4 partition.

5. Put the SD card into my Uni (I have 2 and have tried both - one is G3 and one is G4 - both 64mb) and with both the phone and BT switched on (wifi off) I have navigated to the fat32 partition and run HARET.

On both devices (with both cards) I then get the following (in very tiny letters):

HaRET boot

Shutting down hardware

Turning off MMU... (I can't quite make out the 3 capital letters so may be different)

In Preloader

PSR=600000df (I think)

Tags relocated (I think it's tags)

Kernel relocated

Initrd (I think) relocated

Jumping to Kernel...

at which point it just hands there doing nothing. Any ideas please?
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Change you word 128mb to 64mb in startup.txt?
[JASJAR, XDA Exec, MDA Pro ROM Development] phil.cooke:
Thanks - just spotted that as I re-read the entire thread! At least I'm further than before.

now hanging at the adb_open line....wait - it's got past that bit and is now a blank screen. More waiting I think!
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Froyo is Froyo... It's slow.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
After that, phil.cooke, I can tell you: it will start vibrating like hell and slowly the Android interface will appear. If you're lucky enough, you might manage to open the applications drawer, but don't even think about starting an app. You'll also discover that if you press the reject call key (red) on the qwerty keyboard (when the phone is in "laptop" position), it will switch to a blank screen, and when you press that key again, you'll be back to the Android interface. Ultimately, it might stop vibrating for a while but then it will start vibrating again - unless vibration is disabled at all in the kernel.

About my device, I decided to drop the fear and flash a WM 6.1 ROM on it (Tomal's 8.9 regular I think). I also flashed WM 6.5 but found it slow and came back to 6.1 which is what I'm using happily. I haven't tried to boot Android from it as all my SD cards are being needed, but IIRC notime said Android wouldn't boot from some custom ROMs he tried - and, I must admit, I prefer using WM 6.1 to having the possibility to boot Android.
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Have you this

http://sourceforge.net/projects/htcuniversal/files/zimage.zip/download zimage? I'm try and I'm haven't vibration.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Article is up on the Portal!

http://www.xda-developers.com/android/porting-android-to-the-good-ol-htc-universal/
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Thank you

Thank you.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Glad to help guys, if I you need anything else please let me know :)
[JASJAR, XDA Exec, MDA Pro ROM Development] v0vik:
to orb3000

you wrote

Limitations:

- Devices with only 64mb of ram

but i have Univesal with 128Mb RAM,

and this Android work for me
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
But most devices have 64mb. You have 128mb like notime, so it must work on 128mb too.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
I was referring to that 64MB of RAM will have limitations regarding Android, of course it can work on 64 and 128MB Uni´s
[JASJAR, XDA Exec, MDA Pro ROM Development] Downlord95:
is it possible to partition the sd card under windows and put the tar.gz on the ext4 partition under windows????:confused:
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
No, but you can use Live-CD or Live-usb.
[JASJAR, XDA Exec, MDA Pro ROM Development] madkat:
You can also boot a very slender Linux from a FAT32 partition into RAM on the Universal then shell into it from the PC, add an ext4 partition and unpack the .tar.gz from the FAT32 partition into it. Works better if you can follow instructions without inventing your own spaces & dashes in commands.
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
You write about Angstrom? I'm try it, but if whose have 256mb or less it is impossible.
[JASJAR, XDA Exec, MDA Pro ROM Development] tayfelix:
Steps

Does Anyone Can Write Out The Steps?
[JASJAR, XDA Exec, MDA Pro ROM Development] hitpopmcjason:
anyone succeeded?

ah, anyone else?
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
On first page first post.

PS: I wait for any suggestion. I can only change graphics or add apps, because drivers not working:mad:
[JASJAR, XDA Exec, MDA Pro ROM Development] tayfelix:
Help

Finally Can Put It In My Device, But There's A Problem, it kept saying

ds1wm dslwm: reset failed

ds1wm dslwm: reset failed

ds1wm dslwm: reset failed

ds1wm dslwm: reset failed

ds1wm dslwm: reset failed

ds1wm dslwm: reset failed

And Continue... Need Urgent Help!
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Which version you use? 1.6 or 2.2? Change you 128mb to 64mb in startup.txt?
[JASJAR, XDA Exec, MDA Pro ROM Development] tayfelix:
Noe Wat Problem, Forget To No Bluetooth
[JASJAR, XDA Exec, MDA Pro ROM Development] tayfelix:
Why Is Ecliar tar.gz? and what is common.tar.gz
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Common.tar.gz is for devs. For users is (actually) data.tar.gz.
[JASJAR, XDA Exec, MDA Pro ROM Development] tayfelix:
Ok, Den Where is The Eclair.tar.gz?
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
New version

New version. I have hope notime2d8 talk more about. Now I can talk only that it is some files and you must copy it on SD.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Answer:

The titchy linux was running on 2.6.21 kernel, i'm using a 2.6.32 kernel where the driver structure and code has been changed since around 2.6.23 so non of the drivers can be moved over and or I’m not skilled enough to convert/port them for android. :(
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Touchscreen Support!!!!

Slowly knocking the list down. I surprised myself on this one. :rolleyes: Didn't think i was ever going to get this working. Updated kernel posted on first page.
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Thanks notime!

keep up the good work!
[JASJAR, XDA Exec, MDA Pro ROM Development] Simon_WM:
Guys, sorry to be a pain,

but could some1 write me a tut on the partion on the SD card... as in the case i am a noob =]
[JASJAR, XDA Exec, MDA Pro ROM Development] hackbob:
Thx a lot for the touch.

I'll be testing it later, but i'm so appy about the news.
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
Hi there! I want to test android on my Uni, but there is not any default.txt or haret in rar you posted. Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I updated the zip file with them.
[JASJAR, XDA Exec, MDA Pro ROM Development] hackbob:
Hi all,

tested the new version; the touch sometimes seems to not work.

But i've a question... when I run a program (ex. the message) where i need to click to exit?

I've tried clicking on the whole screen but I wasn't able to find out.

Regards,