yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro ROM Development] cheapusenet:
im confused here, titchy linux runs just fine on the universal. why is it we dont harvest drivers from that?
[JASJAR, XDA Exec, MDA Pro ROM Development] laserdrome:
That's inadvisable. You couldn't properly test Android on the Universal, as all available versions lack many functions. And then again: The hardware of the Universal simply isn't powerful enough to have a very enjoyable Android-experience.

Better go to some o2/vodafone/t-mobile-shop and try some devices there.
[JASJAR, XDA Exec, MDA Pro ROM Development] 19noob66:
Yes, i also think so. I will test another Device with Android.

And then i will see what i buy, a HTC Touch HD or an Android Device?

Thanks for all of you for your help. Top Forum.
[JASJAR, XDA Exec, MDA Pro ROM Development] WaitingForTheSun:
I can't remember me reading a forum thread with so much enthusiasm. BUT! It is sooo bad to hear that the project is dying, or maybe already dead =( I really like android and I want my UNI to get a way to get out of the closet and be useful. When I found this thread I was hoping that it is a way that I thought about.

Notime, please, try to keep this project alive

. I would have even considered a donation for a nice and successful AndroidOS for Uni.
[JASJAR, XDA Exec, MDA Pro ROM Development] knabe-knuckles:
Hi,

I also got a Universal 64MB and want to try Android build from this thread.

But for the Donut release, the thing tells me a lot of pid tracked errors and reboots the device... any advice for me ?

I also get the "can't access tty job control turned off" error.

SD Card is partitioned into 100MB FAT and rest EXT3.

tia

Benny
[JASJAR, XDA Exec, MDA Pro ROM Development] bheam:
same problem here.. tried donut and froyo. i get to a shell prompt and it reboots aftter 3-4 seconds (at which point touch screen doesn't work in windows mobile, and i have to reboot again)

hlep
[JASJAR, XDA Exec, MDA Pro ROM Development] ALoGeNo:
Come on, Notime2d8, you are the last chance to our htc uni, i know that was happend with your laptop is a bull****, but we need you, im trying to do something using your online repo, but my skill with that is like my skill of english.., very low.

In any case, i hope that you can still help us, if you need some help to test, or so, you can find me on #htc-linux or #xda-devs on freenode.

Please help us, we need you.

Regards.
[JASJAR, XDA Exec, MDA Pro ROM Development] samjam:
Maybe some paypals which could pay for a new laptop would also raise the spirits enough to give it another go?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
No, that is quite alright. The insurance money I got is more than enough to buy a laptop and all new gadgets. As far as android is concerned I’ve managed to get the kernel back to where it was from memory plus added some new features. I’ve posted a link to the source code and updated the front page. I will no longer be working on it but will happy to assist anyone on how to get started.
[JASJAR, XDA Exec, MDA Pro ROM Development] ALoGeNo:
Okey, thank you in any case Notime2d8, i was download the common1 file, and i cant find the Makefile or config for 2.6.35 kernel, can you tell me where find that?

Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] WaitingForTheSun:
Man, thx for everything you've done, but why you are not going to work on it no more?
[JASJAR, XDA Exec, MDA Pro ROM Development] samjam:
thanks kindly for your efforts on our behalf
[JASJAR, XDA Exec, MDA Pro ROM Development] przemoc21111:
apps

maybe we make apps list run on android
[JASJAR, XDA Exec, MDA Pro ROM Development] daedric:
May i disagree?? Although it would have to push 4 times as many pixels, i trully belive it would be possible to have it, at least, as functional as msm7200 devices.

No one would belive we could have Android on a Kaise/Vogue... and yet we have :)

The only thing that doesn't work there, is the front camera, camcorder, and the battery driver. Everythin else works to some point.

Yet i agree, wan't to see android in its full glory? try a android device. desire or something... :)
[JASJAR, XDA Exec, MDA Pro ROM Development] kasputis:
Error.

I'm getting "Init not found " error. Can some help ?
[JASJAR, XDA Exec, MDA Pro ROM Development] komser:
it's possible to replace wm compelety with android ?

i mean using android without haret, like at htc kaiser ?
[JASJAR, XDA Exec, MDA Pro ROM Development] orb3000:
Everything is possible, but I believe Android developing for Uni has stopped or slowed...

We should need Developers to jump on this and tell us what is possible and what is not...
[JASJAR, XDA Exec, MDA Pro ROM Development] 12omy:
tutorial porting

maybe someone can give us complete tutorial how to porting android kernel for htc universal...

i'am sorry for my bad english...
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I think I might have to do another update if android cooperates.

<4>universal_acx: universal_wlan_start: done

<4>universal_acx: universal_wlan_init: platform_device_register ...

<4>acx: found ACX100-based wireless network card

<4>initial debug setting is 0x000A

<4>acx: found an ACX100-based wireless network card, irq:260, membase:0x08000000, mem_size:33, iobase:0xc88b6000acx: the initial debug setting is 0x000A

<4>acx: using IRQ 260

<4>acx: request_irq 260 successful

<4>acx: ACX radio type 0x0d

<4>acx: requesting firmware image 'WLANGEN.BIN'

<4>acx: acx_write_fw (main): 0

<4>acx: acx_validate_fw (main): 0

<3>init: untracked pid 390 exited

<4>acx: requesting firmware image 'RADIO0d.BIN'

<3>init: untracked pid 391 exited

<4>acx: acx_write_fw (radio): 0

<4>acx: acx_validate_fw (radio): 0

<4>acx: initializing max packet templates

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx: TotalMemoryBlocks=79 (20224 bytes)

<4>acx: NVS_vendor_offs:0000 probe_delay:500 eof_memory:65536

<4>acx: CCAModes:04 Diversity:01 ShortPreOpt:01 PBCC:01 ChanAgil:00 PHY:05 Temp:01

<4>acx: AntennaID:01 Len:02 Data:1E 00

<4>acx: PowerLevelID:0A Len:00 Data:

<4>acx: DataRatesID:02 Len:05 Data:02 04 11 22 44

<4>acx: DomainID:03 Len:07 Data:30 20 30 31 32 40 41

<4>acx: ProductID:04 Len:09 Data:TI ACX100

<4>acx: ManufacturerID:05 Len:07 Data:TI Tes:

<4>acx: chipset TNETW1100B, radio type 0x0D (Maxim (MAX2820)), form factor 0x03 (Compact Flash), EEPROM version 0x05, uploaded firmware 'Rev 1.9.8.b'

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx: got antenna value 0x8D

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx: got Energy Detect (ED) threshold 112

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx: got Channel Clear Assessment (CCA) value 13

<4>acx copy_from_slavemem: warning! destination not word-aligned!

<4>acx: got regulatory domain 0x30

<4>acx: got sensitivity value 176

<4>acx: new ratevector: 82 84 0B 16 2C

<4>acx: phy0: changing radio power level to 18 dBm (23)

<4>acx: creating proc entry /proc/driver/acx_phy0/info

<4>acx: creating proc entry /proc/driver/acx_phy0/diag

<4>acx: creating proc entry /proc/driver/acx_phy0/eeprom

<4>acx: creating proc entry /proc/driver/acx_phy0/phy

<4>acx: creating proc entry /proc/driver/acx_phy0/debug

<4>acx: creating proc entry /proc/driver/acx_phy0/sensitivity

<4>acx: net device phy0, driver compiled against wireless extensions 22 and Linux 2.6.36+

<7>phy0: Selected rate control algorithm 'minstrel_ht'

<4>universal_acx: universal_wlan_init: platform_device_register: done

# e_fw (main): 0

:eek:
[JASJAR, XDA Exec, MDA Pro ROM Development] kitor:
So 'welcome back in development' ;)
[JASJAR, XDA Exec, MDA Pro ROM Development] blackSVK:
great news!
[JASJAR, XDA Exec, MDA Pro ROM Development] smartpal:
gud hear that android project is back on track. I was so dissapointed when i heared that the android project was dead. Really appreciate notime2d8's work and request him to keep his work on android going. pllllllllllzzzzzzzz dont stop ur work notime2d8. pppplllllllllzzzzzzzz
[JASJAR, XDA Exec, MDA Pro ROM Development] dutchschultz:
this is awesome! im pumped!@

this'll be awesome if we can get android on the uni!

awesome work mang!
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
phone is working in the current version of android?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Almost :eek:
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
what about home/back?

I have found these instructions:

--------------------------------------

Go into the menu, then spare parts, and select “end button behavior” and change it to either “go to home” or “home then sleep”,

then the right soft key will be the home/back button.

--------------------------------------

But does not works for me...

Anyway I don't understand the idea:

The home button is already right soft key and using the above instructions you are changing the behaviour??
[JASJAR, XDA Exec, MDA Pro ROM Development] brewhoxs:
Wow, it's really amazing cause Universal has walking in Android! ;)
[JASJAR, XDA Exec, MDA Pro ROM Development] z180:
It has only 64 MB RAM,most Android phones have more,like 192 on the Dream.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Mine has 128MB of ram, and most phones that have android are using a qualcomm msm soc that shares their ram with the modem and gpu leaving about 96mb free. So i should be ok, and maybe a barebones build with swap for 64mb users. :rolleyes:
[JASJAR, XDA Exec, MDA Pro ROM Development] z180:
The Universal contains a PXA 270 + a Qualcomm MSM6250 chipset for UMTS,

called QCT Platinum in the service manual.

The CPU docs state it can overclock safely to 624Mhz because

Intel/Marvell sold these chips clocked to 312,416,520 and 624 Mhz,it supports 3.0 MP cameras like on Athena that uses the same CPU and LCD sizes up to 800x600.

You can also run a modified version of the Sharp Zaurus zUbuntu and would be not much work patching OpenBSD and NetBSD zaurus ports.
[JASJAR, XDA Exec, MDA Pro ROM Development] abuabdillahaljawi:
Wow.. gonna try it out..

Keep Going man..

question: why is the link in fs64 and fs 128 is not there?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Haven't posted it yet i still have a few things to fix before i do. I should have it up later today or tomorrow.
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
to notime2d8:

Could you please post more info about running USB Host? Which cable will I need and how to set it up?

Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
For host you need a cable like this link and a powered USB hub like this link these are the ones I'm using and you'll need a kernel with host support enabled plus any drivers for the usb devices. I can do the kernel and drivers if you let me know which usb devices you are wanting to use.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Sound!!!!

I just got sound working in android!!!!!! Only stereo through the headphones and the phone mic right now. But I'm super excited I've been trying to get it to work for the longest. :rolleyes: I've been listening to these android ringtones nonstop lol!!
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
Congratulation to audio working.

I would like to use USB Host for keyboard, maybe mouse too and also USB Flash Disk or USB HDD.

Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
download kernel.zip. it contain startup, haret and zImage
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
hello notime,

first I have to tell that I am not UNIX expert but until now I was able to install every android release for android.

I've just download the last tar and there are things that I don't understand:

- the tar gzip contain only one directory called common - it does not look like a normal unix root fs

- the size of unzipped data exceed 400 MB and the recommandation for 150 MB from the first post

can you help me with these?

should I wait for the next release?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yes, i should be posting my next release later on today as soon as i figure out how to fix the phone support back to were i had it with working sms. What you downloaded was actually a backup of my kernel. After i get something working i try to back it up on my site to avoid it getting lost again.
[JASJAR, XDA Exec, MDA Pro ROM Development] dutchschultz:
This is so cool!
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Just posted the latest builds.

Just posted the latest builds on first page with sound on speakers and headphones that switches between the two. Also wifi and some phone functions, receiving calls stopped working when i got the sound working. And 100% working touchscreen. ;)

I also need some help with the asound.conf file in system/etc it controls the switching of sound states for different situations as well as which microphone and speakers to use. Right now the mic is always on and there's a lot of sonud controls and routing that i don't know what they do. If somebody can adjust the values and let me know what they do or if you can receive calls again. The asound.state file with all the controls and values is posted below.

Also let me know what wifi security settings work besides wep.

The browser and home screen tend to crash due to a error that i have to fix later. A different browser might be needed for web browsing.

If anybody knows how to edit or create intrid files let me know so we can work on a better startup and get closer to the way that the Kaiser loads android from sd maybe even using Gen y Dualboot
[JASJAR, XDA Exec, MDA Pro ROM Development] dutchschultz:
Awesome man. I'm going to try this out
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
hello notime,

I've tried but unfortunately unsuccessful:

freezed in initial screen with small fonts; the last message "jumping to kernel"

then tried to modify startup.txt replacing mem=128M with mem=64M:

"Failed to execute init. Attempting defaults...

Kernel panic - not syncing: No init found. Tru passing init to kernel.

.....

Rebooting in 120 sec

Any idea?

My device has only 64MB...

I have changed the zimage and rootfs.
[JASJAR, XDA Exec, MDA Pro ROM Development] fullo:
same issue of cer7400 , on uni 64 mb, i deleted mem=128 from startup.txt

...Kernel panic ... No init found....
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Do you see where the memory card is detected? And are you using a ext3 or ext4 partition?

Has anybody gotten it to load? I will have to check the rootfs later when i get off work then to see what the problem is.
[JASJAR, XDA Exec, MDA Pro ROM Development] spanner3003:
cannot execute "" permission denied

hi notime2d8 i an getting init: cannot execve (''): permission denied right where it should be starting android from. they are /system/bin/mediaserver,keystoke and dbus-daemon over and over.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Ok, thanks, thats what i needed to know. I will post a new build and actually test it in a few hours.
[JASJAR, XDA Exec, MDA Pro ROM Development] spanner3003:
got it working :) I think!

Hi notime I got it working. :) it's vibrating now, how do i stop it?

I had to format the ext4 partion without taking owership and sudo into the ubuntu file system and move the files out of the cmfroyo folder into the root of the parttion.

IT WORKED IT HAS STARTED :D
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
That would make since i must have compressed my cmfroyo folder instead of just the files. so when everyone extracts it on their memory cards instead of the files they have a foler cmfroyo with the files in it. I will fix it in little bit. let me know how everything works if you're using a 64mb universal and you just have to touch a button on the lockscreen or do something to toggle it like turning to volume off with the slider.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I just posted the fixed build.

I think I'm going to switch to a standard froyo build instead of trying to use a Cyanogenmod build. It doesn't seem worth the issues that it causes with compatibility, crashes, and the browser for the extra features that it adds. :(
[JASJAR, XDA Exec, MDA Pro ROM Development] onurdndar:
Yay, I finally managed to bring my 64M Jasjar to the point that it started vibrating.

Now I'm afraid it'll run out of power before it finishes booting :D

Edit : Home activity crashed, restarted, crashed again. I couldn't stop the vibration or do anything, really. I rebooted before the phone tore itself apart or burst into flames because of the vibration :)
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yeah it takes a while to turn off at the first boot. I will try to fix it for the next release or just remove it. It works fine after you toggle it that first time to stop it.
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
Hello,

I succeeded with start start. vibrating stopped.

Right now I am in cycle:

Home activity crashed, restarted, crashed again,

and again
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
That might be to low memory or due to the libskia.so errors that affect cm6 roms but it shouldn't loop like that.

I have a asop 2.2.2 froyo building right now that should give us a little more free ram and stop the force closes from errors. I'll get it posted as soon as i finish porting my changes over and fix or remove the vibrator.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
Thanks a lot for all your work, mainly for notime's work but also for all the others that have worked in this before :)

I'll try this new build when you fix the vibration and free RAM thing. Before you started working on this again, I was almost going to ask here to compile Android for the Uni from what has been already done, but three days ago I came back here and saw this is moving forward again. Great!

With the previous 2.0 build, I just got stuck with a black screen (which is normal) for a half of hour (yes, 30 minutes, which doesn't seem so normal), until I gave up and reseted to go back to WM. I did this three times and even did the procedure (formatting SD, extracting everything, etc.) again one more time just to be sure...

I just hope that with 2.2 this is fixed or else I'll start to think my Uni has something so special that doesn't let Android boot... :)

It seems that now the non-working things list is reduced to two items... cameras and power management. But I have a question: in the kernel status, when you say "Audio", does it mean both headphone plug and internal speakers (when headphones disconnected)? Or only one of the two work?

Also, can someone please tell me if, on Android on a Universal, it's possible to have sound coming from both in-device speakers and the headphone plug, or is it an hardware limitation (and not a WM drivers one) that makes it impossible to do such thing?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yes both the headphones and the main speakers work. The main speakers switch off when headphones are inserted and vice versa. And i had it like that at first where both were on and playing sound on the headphones and speakers before i fixed the switching from inserting headphones. So it's not a hardware limitation, and can be made that way by removing the switch from the code or maybe editing the asound.conf.
[JASJAR, XDA Exec, MDA Pro ROM Development] rmof:
I want to say thanks for a great job;)

I am having a problem that is: "init not found"and after few seconds appears rebooting 160 sec ...

Universal restarts and returns to windows mobile .. : S: S

Any suggestions .. I think everything is all right ..
[JASJAR, XDA Exec, MDA Pro ROM Development] rmof:
I managed to pass the previous step .. now blocks in permission denied? and not leave here .. Any Suggestion?
[JASJAR, XDA Exec, MDA Pro ROM Development] cer7400:
could be a problem with mounting ext fs from the card or ext fs itself

try to read/verify the linux fs from the card
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
to notime2d8:

Please, is there an USB Host support in your newest kernel posted in the first post?

If you have time, please could you build also Donut (1.6) rootfs with Wifi, audio, USB Host and other things, because CM build of 2.2 is so slow on 64MB Uni.

Thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Just an update on the new asop 2.2.2 build it works better. All of my changes are ported over with the vibrator removed. I have no force closes on the browser and home screen but wifi is broken :mad:. But I should be uploading it as soon as I get that fixed. On my universal I have 76mb free using launcherpro for home and no other processes running. That should be about 12mb free for 64mb users?

Pandora works and I found a nes emulator that runs full speed with sound and multiple button presses. :D

Not yet but i am working on that. I figured that most people don't use adb except me so going forward i will add host support for the usb port to my kernels and will try to get that out asap or with the next release just need to figure out how it affects the modem.

Donut did run better when i had a 64mb uni....maybe a CM build of donut? ;)

But that will be a little until this happens due to me having to change the touchscreen driver, and backporting wifi. But sound and some phone functions should be easy to do. But that's a great idea going forward to have two builds one for 64mb universals with Donut and one for 128mb unis with Froyo.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
I agree a Donut build should be made for users who want it but... don't forget there is at least one 64MB Uni owner (me) that would like to see 2.2/Froyo working on it, as 1.6 is old software... and for old software, I already have WM5 :)
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
I have got a problem with lastest kernel. It always stuck at Jumping to Kernel. I have already tried to copy it 5 times but nothing helped.
[JASJAR, XDA Exec, MDA Pro ROM Development] gbl08ma:
Did you turn the phone on, on Windows Mobile (NO flight mode)? If I recall correctly, I was having that problem, and after I read the first post further I noticed it was needed to turn on the phone... unless I'm confusing with another thread/site.

Now as I can't see these instructions... is it still needed (assuming it ever was)?
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
I have phone turned on. But it still stuck on the Jumping to Kernel.
[JASJAR, XDA Exec, MDA Pro ROM Development] WaitingForTheSun:
When I change "mem" parameter in startup.txt to 64M it seems to boot, then it writes "Kernel panic - not syncing: Fatal exception" "rebooting in 160secs". I did this with my gsm on and no sim.

With gsm off it "jumps to kernel" infinitely

I have a 64mb RAM G4 uni.

P.S. notime2d8, glad that you're back!
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
So i have solved my problem. The problem was in startup.txt I used startup.txt from your older kernel and it boot without any problem.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Do you know what was different between the two?
[JASJAR, XDA Exec, MDA Pro ROM Development] ---UFO---:
There weren't these 3 commands in older startup.txt : no_console_suspend=1 console=ttyS0,115200n8 mem=128M

By the way, your lastest cyanogen Froyo mod from 15. feb. is much more faster and i have 22MB free RAM on 64MB Universal. But i can't find there market application.

Thanks for your great work.

Please, could you also build to your kernel USB Host drivers for mouse, keyboard, Flash drive and external Hard drive? Thanks