yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Good news Bad news

Good news is that the mainline kernel has drivers for both g3 and g4 flash devices and they are working in my kernel and you can read and write to them making it possible to flash a bootloader and have a full Linux/android device:

<6>docg3 docg3: Found a G3 DiskOnChip at addr ff000000, floor 0

<6>docg3 docg3: Found a G3 DiskOnChip at addr ff000000, floor 1

Bad news is that even though i have 3 universals i don't want to brick them testing with no jtag or way to recover :crying: D-two might pick up my slack here and help out but if not anyone who is able to and can build a kernel and is familiar with uboot or bootloaders i will help. This might change depending on if i can score some extra uni's off ebay.....
[JASJAR, XDA Exec, MDA Pro ROM Development] snowplow:
I've got a 64mb xda exec I'd sell you really cheap... PM me
[JASJAR, XDA Exec, MDA Pro ROM Development] rod555:
news on progress? Thx
[JASJAR, XDA Exec, MDA Pro ROM Development] SomeOneCares:
Hello,

I downloaded http://sourceforge.net/projects/htcuniversal/files/sdboot.zip/download as instructed and I extracted it to a 2GB SD card formatted as FAT32, I am using Universal 64M model, now after I execute haret-w it stops at "Jumping to kernel" is there something I am missing? I would really love to get my universal back to life with Android :)

thanks
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
You have a Uni with 64MB Ram right?

I have test the last kernel and the same problem and after look in the Source i have see that his kernel only support 128BM...

@notime

in the Universal init you set a register with comment //128 BM device or something else...

Please remove it for the Uni with 64BM...
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
Hey guys, 64 MB is just too little for Android. I managed to run some earlier version of this on a 64MB Uni and it was totally unusable. When I touched the display it took several minutes (!!!) before the system responded. If you don't have 128MB RAM don't even try it.

In my opinion Android is not suitable for Uni (or similar device with low memory and slow cpu) at all. The linux kernel is ok, but the applications are written in a java-like language which is interpreted in run-time by a Dalvik virtual machine and that is just too much memory and cpu hungry. I think that Firefox OS with HTML5 applications or even a mobile version of Ubuntu with native machine-code compiled applications may suite Uni better. Every application written in an interpreted language means a performance penalty compared to an application compiled to a native machine code. I still didn't get why an interpreted language was chosen for such underpowered devices with low operating memory like smartphones (ok, actual high-end smartphones have decent power and almost enough RAM). Probably it wasn't chosen for a technical reason but for a marketing reason - there were a lot of java programmers who could almost instantly start developing android apps and so the number od android apps could grow rapidly. But now we must carry (and pay for) disadvantages of this - hardware of android devices must be much more powerful than it would be needed for a native machine code apps, and also there are difficulties with multitasking because it doesn't work very well with Dalvik virtual machine so dualcore and quadcore cpus are a bit of wasted.

Sorry for the long post but I felt I needed to explain it.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I thought it wouldn't work!!!

I thought this wouldn't work for quite a few reasons...but my universal is taking everything i throw at it. Only console works at the moment and at full speed. I need to figure out how to get android to use or switch framebuffers. :good:
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
HA !

I've almost thrown my head off the window when I saw the picture!!! :) I would never believe a USB2VGA adapter would work with UNI... :good::good::good: Obviously the linux kernel inside the android has already required drivers. Or did you add them manually?

Are you using 128MB or 64MB RAM?

I'm still considering if it's worth the money to expand memory of my UNI to 128MB.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yes, I’m using the drivers that are in mainline kernel with a little change to get it to work with USB 1.1.

I’m using both.

The upgrade is probably not worth it to most people. I justified it by calling it a cheap hobby/development board to tinker away with and it has taken up hours/days of my time. But the main reason that I advise against it, is that you can get a nicely equipped android device that has 3x the specs of the universal even with HDMI.
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
Yes, that's right. I already have HTC Desire Z and also Samsung Omnia Pro (which I think is the best win-mobile phone) so I know what you mean. Actually I still use Uni because I haven't had enough free time to completely switch to a newer phone yet... :) But Uni's keyboard is just unbeatable... I'll miss it a lot. Both Desire Z and Omnia Pro have qwerty keyboard but they can't compare to Uni's.

Anyway it would be fine to have a let's say backup device with a modern OS. I have three Universals (sadly all only 64MB) so why not make some use of them. They are unsalable nowadays anyway. But android doesn't look very promising for a 64MB RAM device. Even the very first android device G1 had 192 MB RAM. Maybe Firefox OS would be a better choice but maybe not because it's designed for current devices which hardly have less then 512 MB RAM.

I have a contact to a guy who does the RAM chips exchange but he is charging 1300 CZK for it (including new RAM chips) which is around 65 USD / 51 EUR / 44 GBP. And that's quite some money for me. So although I'd love to have a 128MB Uni I'll probably stick with Tomal's v8.9 Win-mobile ROM.

Nevermind, it's still interesting to see the progress of your work. :good:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I’m being a little selfish and busy right now and just working on getting my 128 universal how I want it…but in a little bit I’ll show the 64mb universals some love since I know that it’s more of those out there. The idea is to use android 1.6 or 2.2 and back-ports from gingerbread…I just hate the thought of going backwards….then changing things to be more like I already have working in gingerbread. I started out with a 64mb universal and those versions worked well. I need someone who wants this and who knows how to build android and test it.
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
Is gingerbread (2.3?) that much more demanding than 2.2 that it cannot run on Uni? Or is there another reason why to stick only with 1.6 and 2.2?

I'd like to help, I have two more Unis so I can sacrifice one :) but I'm pretty new to android. I don't know how to build android or flash it to Uni.

Currently I'm slowly working on getting a 4.0/4.1/4.2 android on my Desire Z. But all I know now is that I will probably need to downgrade the firmware because there is no root for the current firmware version, then root it and then install whatever ROM I want. I'm just not familiar with android yet. But I'm IT guy so I can learn (hopefully) quickly :)
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
That is really cool :good:

I hope this will also work with android in the future...
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yes, there is a big difference. I think in general 2.3 use about 14-20mb+ more of ram. Those who have tried it says that it’s slow to boot and unusable but that’s coming from apps force closing and out of memory errors. Each version of android they add more things for gingerbread- new api's, wigets, nfc, misc. sensors, new keyboard, new launcher, and VoIP/SIP calling.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
So....it's not looking like it will work with android...The driver just starts and waits for the computer to request video settings and doesn't initialize any, so i'm either going to have to figure out how to request specific screen modes or try a different usb2vga device,
[JASJAR, XDA Exec, MDA Pro ROM Development] Coece:
i have version with 64mb...and please if someone could reupload Tomal v8.9 rom and explain me how to install it, that thread is dead so i posted it here..sorry about that

http://xdaforums.com/showthread.php?t=513907
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
Hi, all three versions can still be downloaded from my site, see the above mentioned thread on page 68 and my post with number 678. There are the download links.
[JASJAR, XDA Exec, MDA Pro ROM Development] Coece:
thanks a lot! :highfive:

can you say which I must install and is it hard to install? i dont know if i must install some kind of the recovery or something before flashing
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
First of all, please, post into the original thread. Not into this one. This thread is about Android on Universal.

In the begining of the original thread there are descriptions of all three versions, just read it. I haven't tried the "lite" or "zaxxmann" version and I don't have any screenshots anyway, but accoarding to the first post the only differences are in applications included. So "lite" has least applications and "zaxxmann" is somewhat specially equipped (lacks IE if I remember correctly). Zaxmann version is not described on the first page of the thread but a few pages later.

If you want to install it, backup all data from your phone because it will get completely erased (except SD card). If I remember correctly you should pull out both SIM card and SD card and the phone must be fully charged. Then connect it to your PC via USB cable and run the program. It will tell you what you should do. Anyway, there is a wiki page for Universal on the xda-developers site, where everything important is written.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Look what i got working!!!!

So i finally got video out working and shot another shaky/fuzzy/blury video. I wanted to show the total boot time but forgot to press record. My current setup runs a lot faster now with about 79mb free out of 120mb i'm still looking to lower this some more.

1. It's running through a USB hub which is causing some slow down.

2. No double buffer support

3. It's running at my screen's max reslution 1280x1024

4. I also had a usb mouse connected taking up bandwidth

If these are corrected it should run a little faster, also it works a little better than shown in the video..i was holding my phone while trying to use a micro mouse to navigate, so i was missing where to click a few times. I tried to show of some features added to the performance settings...but they're too blurry to see. I also tried to play a un-optimized video...it was only getting about 5 frames/sec :crying: so i stopped that. Enjoy!!!

[YOUTUBE]6NF0yfhau_w[/YOUTUBE]
[JASJAR, XDA Exec, MDA Pro ROM Development] kybergreg:
It shows that the video is private so I cannot watch it.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Sorry it defaults to that for some reason but it should work now.
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
Really cool... Awesome...

Have you a idea for speed up the framerate?

EDIT: if you have 79mb free will this work on 64mb devices?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Yes, I think I can speed it up by not using it with a USB hub and hooking it directly to my phone. And use my Bluetooth mouse as the USB one caused the video to slow down when I used it. Maybe add in double buffer to help with tearing and reducing the resolution from 1280x1024 down to 800x600.

I haven’t tested it but probably not... that’ll leave a 64mb phone with only 15mb which will be used up by settings or one app…and I only got that much by a few tweaks and removing SystemUI. Removing the phone and messaging functions should free up another 15-20mb and that should run ok on a 64mb device.
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
You think the main problem isn't the pxafb?

i don't know if this will help but it support the PXA3XX

I have a UNI with 64mb, too. i can test it for you...
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Just using the phone by itself, yes the pxafb is slowing us down. I did see a few articles about adding directfb to android...i'll look into it. But for the external monitor i had to disable the pxafb driver so that the external monitor gets mapped to /dev/fb0. So any slowness is coming from what i mentioned earlier and the usb port only being 1.1 = only 10mb/s transfer speed. If i could get mplayer to build i could have both enabled and just pick which frambuffer to send this video to. So i could have android on pxafb /fb0 and have a video playing on the monitor at /fb1.....i think this could work well before my uni burst into flames...

Cool, i'll post a stripped down version without extra apps, systemui, rild, mms, contacts, and phone...That should get us with minimum cpu/ram usage. :good:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
This looks possible... i have 81mb free so 17mb for 64mb universals...? Swap might stll be needed as i think it drops lower during bootup. And there could be more than 81mb free as i have jit enabled which uses about 3-5mb and settings usually takes up about 9-12mb... :confused: But it doesn't seem like android can run that light..? Zram might be helping more than i thought.

The files are posted here Link let me know how it goes [MENTION=1377734]d-two[/MENTION]
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
So did anybody try? I see 8+ downloads....
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
Sorry for the late reply...

The battery from UNI is DEAD :crying: i need a new one...

But i have test your filesystem with a other 64MB device ;)

[YOUTUBE]VstbFI7TIAs[/YOUTUBE]

It is working with 64MB :good:

EDIT: I have replace the boot animation with a qvga version...
[JASJAR, XDA Exec, MDA Pro ROM Development] Coece:
can someone guys pleas tell me how to put that rom on my 64mb mda pro please..i dont know the procedure..thanks a lot :)
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
That boot animation was pretty fast...how much ram was free.. 23 out of 54...? I did some touchscreen changes that might be messing up the touch? Was that a magician?
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
ok, this is my problem with the touchscrren :silly:

in the dmesg were my coords correct ;)

yes, it is the magician... and yes 23MB from 54MB free, i think the statusbar and phone were helpful...
[JASJAR, XDA Exec, MDA Pro ROM Development] Tessai:
Some instructions, please. I found this link, now what? :)

http://sourceforge.net/projects/htcuniversal/files/

(from here, of course: http://xdaforums.com/showthread.php?t=658664)

10x
[JASJAR, XDA Exec, MDA Pro ROM Development] miki100:
Guys, that's pretty awesome! (I wish I had more time and a "backup phone" to also "play" a bit again with BA)

[MENTION=557036]notime2d8[/MENTION] How much do you think would the ram usage rise if you left most important things like, systemui, rild, mms and phone?

Is it required that mms and phone must be running in the background all the time?

Too bad that I don't know android that much, but by looking at it's source code I can tell that it is not written for speed...

I wonder how fast that "slim" Android would work on BlueAngel or 128MB Universal :)
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
For me and the way i have mines setup... it flies and i think it runs as well as a g1 or magic but video playback, i only got to 20 f/s with rockplayer which the video and decoder weren't optimized.

Adding back in those things will drop ram down to about 64mbs...so about 16mb+/- . and yes they are required to be running in the background or you will not receive calls or texts.

It'll be nice if we can just remove a lot of the unneeded features for our phones, like proximity sensor support, nfc, wimax, replace animations, simplify the launcher, and optimize bionic,skia,surfaceflinger,dalvik, and opengl with some more armv5te asm and maybe iwmmxt for the universal. <- i think [MENTION=1377734]d-two[/MENTION] can do all of this, joke. It should be able to fully replace windows mobile even on 64mb devices... .then we might just need to start building our own apps and emulators...:confused: #noangrybirds.
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
Yes, the modifying of Android is on my future plan :D

Here a short video how good the touchscreen can work ;)

I have patch the ads7846 driver again :silly:

[MENTION=557036]notime2d8[/MENTION]: I think this can help for the Uni too... if i have a new bettery i will test it again with uni :)

[YOUTUBE]rvla_-9E8gg[/YOUTUBE]
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
Hmm... wouldn't be easier to just replace launcher? If I am right ADW Launcher from CM isn't so efficient (on LG P500 and Xperia U I had micro-lags). I think for Universal you can use Nemus Launcher (it used to use around 5mb of ram, but I am not sure about now) or Lightning Launcher (customizable and (if I good remember) can turn off animations).

Sorry for my English :)
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
The Lightning Launcher looks good... but very important is that the launcher less memory need!!
[JASJAR, XDA Exec, MDA Pro ROM Development] orzech2111:
I know that, I had Uni and I remember my "fight" for free ram :) I am not sure how much ram Lightning Launcher need, but on ICS it's around 18mb. It looks riddicoulous for me, but same with Nemus Launcher. Smart Launcher usage is around 11mb. I am not sure, but I think on Uni they should use less ram.
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Where does this patch happen to be posted...? :) I will test it for you as my touchscreen has not work since I switched drivers and tried two different ways to calibrate it from android... The video is nice...I don't see the jumping from polling
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
Ok, wait a little bit i will clean up the stuff ;)
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
[MENTION=557036]notime2d8[/MENTION]

Example configure:

static const struct ads7846_platform_data tsc2046_info = {
.model = 7845,
.vref_delay_usecs = 100,
.pressure_max = 512,
.debounce_max = 20,
.debounce_tol = 0xffff,
.debounce_rep = 1,
.gpio_pendown = GPIO115_MAGICIAN_nPEN_IRQ,
.x_max	= 240,
.y_max	= 320,
.calib_data	= {4440, -25, -1556132, -17, 5815, -1802912},
};

EDIT: can you please remove your modification from android for the touchscreen and build it again :fingers-crossed:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
So you're putting the tslib values directly into the driver? There was a patch I was using with the other driver that allows doing this from your startup.txt boot command line....

The only problem that I see is that the values change between touchscreens.

I wonder if I can make a tslib app that adds the values to a sysfs line or to your startup.txt ....?

Edit: I will try it first it may work OK.

Edit2: yes, it will be 3hrs to post the new build....still at work
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
i use the same method for blueangel and this work fr every version...

the different between the different touchscreen is very small (from blueangel i have 4) !!!
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
[MENTION=557036]notime2d8[/MENTION]

I have a new Battery :D

Here is the result

[YOUTUBE]LQtwCUCTWXw[/YOUTUBE]

but in my kernel the PXA Framebuffer is buggy?! have you patch it?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
That is so great... yes i have a patch after it is applied my info is this:

static struct pxafb_mode_info htcuniversal_lcd_modes [] = {

{

.pixclock	= 38400,

.xres	= 480,

.yres	= 640,

.bpp	= 16,

.hsync_len	= 4,

.vsync_len	= 1,

.left_margin	= 20,

.right_margin	= 8,

.upper_margin	= 7,

.lower_margin	= 8,

.sync	= FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,

},

};

static struct pxafb_mach_info sony_acx526akm = {

.modes	= htcuniversal_lcd_modes,

.num_modes	= 1,

.pxafb_lcd_power	= universal_lcd_power,

.pxafb_backlight_power	= universal_backlight_power,

.lccr0	= LCCR0_Act | LCCR0_Sngl | LCCR0_Color,

.lccr3	= LCCR3_HorSnchH | LCCR3_VrtSnchH | LCCR3_PixRsEdg | LCCR3_OutEnH | LCCR3_Acb(0) | LCCR3_PixClkDiv(5),

.lccr4	= LCCR4_PCDDIV,

.width	= 54.72,

.height	= 72.96,

}
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
thank you, i will test it ...

i have test the magicain touchscreen again but in android only the left corner ist working? i have change the dpi to 120 in the buid.prob but in adb says the dpi from framebuffer is 160?
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Did you try setting both:

ro.sf.lcd_density=120

qemu.sf.lcd_density=120

also the patch didn't fix the touch in android for me :crying:
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
yes, i have change both values from 160 to 120...

01-01 00:02:30.320: I/gralloc(1103): using (fd=28)
01-01 00:02:30.320: I/gralloc(1103): id = PXA
01-01 00:02:30.320: I/gralloc(1103): xres = 240 px
01-01 00:02:30.320: I/gralloc(1103): yres = 320 px
01-01 00:02:30.320: I/gralloc(1103): xres_virtual = 240 px
01-01 00:02:30.320: I/gralloc(1103): yres_virtual = 324 px
01-01 00:02:30.320: I/gralloc(1103): bpp = 16
01-01 00:02:30.320: I/gralloc(1103): r = 11:5
01-01 00:02:30.320: I/gralloc(1103): g = 5:6
01-01 00:02:30.320: I/gralloc(1103): b = 0:5
01-01 00:02:30.320: I/gralloc(1103): width = 38 mm (160.421051 dpi) <---
01-01 00:02:30.320: I/gralloc(1103): height = 51 mm (159.372543 dpi) <---
01-01 00:02:30.320: I/gralloc(1103): refresh rate = 119.33 Hz
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
I thought that was telling what it should be based off of sceen size and resolution and that this :

W/SurfaceFlinger( 1001): ro.sf.lcd_density not defined, using 160 dpi by default.

Shoud be showing if it defaulted to 160 dpi?
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
can you give me your kernel config?

But in android the systemUi is 120 dpi? really strange...

Here a video from Uni with working touchscreen in the left corner...

[YOUTUBE]XIO14mfh31U[/YOUTUBE]
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Thats's with 64mb? it seems snappy.
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
What do you mean ? slow or smooth... :D
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Smooth...i also figured out how to get the kernel down from 6.3mb to 4.9mb uncompressed.

I added this:

config SND_SOC_AK4641_CODEC

tristate "Build AK4641 ASoC CODEC driver"

select SND_SOC_AK4641 if I2C

to: 3.8/sound/soc/codecs/Kconfig

It builds only the one codec instead of the 40+ :victory: ...this gave me an extra 1.4mb in android.
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
I know ... sorry, this was one of my first modification...

my kernel is 2,1 MB(size not ram usage :D) and i have insert the blueangel, magician, hx4700 and universal, don't know how much it is in android...

ok, so we have here 4:30 AM i need sleep...
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
why is the sd card not right detected in my kernel? :mad:
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Is it just the kernel that you are changing, it works ir you switch to mines? Did you change the vold.fstab or init.rc?
[JASJAR, XDA Exec, MDA Pro ROM Development] d-two:
No, i have only replace the Kernel from yours to mine...

AND HERE:

[YOUTUBE]suIBphGJ0dI[/YOUTUBE]

I have create my own small android and in this is the touchscreen work! You must have something in your android !!!
[JASJAR, XDA Exec, MDA Pro ROM Development] notime2d8:
Well..thats weird...i replaced the file in frameworks/base/ui with the ones from aosp...there shouldn't be anything else that was changed. Can you post you setup for the touchscreen? Did you change xmax and ymax to 640x480 and did you use the same tslib values?