[Dev] Android on the Universal

[d-two]

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?

No, i have only replace the Kernel from yours to mine...

AND HERE:

I have create my own small android and in this is the touchscreen work! You must have something in your android !!!

 

[notime2d8]

No, i have only replace the Kernel from yours to mine...

AND HERE:

I have create my own small android and in this is the touchscreen work! You must have something in your android !!!

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?

 

[d-two]

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?

Here is the compete source:

/* Physical address space information */

static unsigned long universal_pin_config[] __initdata = {
....
	/* SSP 1 */
	GPIO23_SSP1_SCLK,
	GPIO24_GPIO | MFP_LPM_DRIVE_HIGH,
	GPIO25_SSP1_TXD,
	GPIO26_SSP1_RXD,
...

};

/*************************************************************************
* Touchscreen - TSC2046
**************************************************************************/
/* fixed regulator for ads7846 */
static struct regulator_consumer_supply ads7846_supply =
       REGULATOR_SUPPLY("vcc", "spi1.0");

static struct regulator_init_data vads7846_regulator = {
       .constraints = {
               .valid_ops_mask         = REGULATOR_CHANGE_STATUS,
       },
       .num_consumer_supplies  = 1,
       .consumer_supplies      = &ads7846_supply,
};

static struct fixed_voltage_config vads7846 = {
       .supply_name            = "vads7846",
       .microvolts             = 3300000, /* 3.3V */
       .gpio                   = -EINVAL,
       .startup_delay          = 0,
       .init_data              = &vads7846_regulator,
};

static struct platform_device vads7846_device = {
       .name           = "reg-fixed-voltage",
       .id             = 1,
       .dev = {
               .platform_data = &vads7846,
       },
};

static const struct ads7846_platform_data tsc2046_info = {
	.model            = 7845,
	.vref_delay_usecs = 100,
	.pressure_max     = 512,
	.debounce_max     = 20,
	.debounce_tol     = 10,
	.debounce_rep     = 1,
	.gpio_pendown     = GPIOA12_TOUCHSCREEN_N,
	.x_max			  = 480,
	.y_max			  = 640,
	.calib_data		  = {9078, 26, -3438768, 36, -11665, 45389832},
};

static struct pxa2xx_spi_chip tsc2046_chip = {
	.tx_threshold = 1,
	.rx_threshold = 2,
	.timeout      = 64,
	.gpio_cs      = GPIO24_TSC2046_CS,
};


static struct spi_board_info tsc2046_board_info[] __initdata = {
	{
		.modalias        = "ads7846",
		.bus_num         = 1,
		.max_speed_hz    = 2600000, /* 100 kHz sample rate */
		.irq             = PXA_GPIO_TO_IRQ(GPIOA12_TOUCHSCREEN_N),
		.platform_data   = &tsc2046_info,
		.controller_data = &tsc2046_chip,
	},
};

static struct pxa2xx_spi_master pxa_ssp_master_info = {
	.num_chipselect = 1,
	.clock_enable   = CKEN_SSP1,
	.enable_dma     = 1,
};


static void __init universal_init(void)
{
...
	spi_register_board_info(tsc2046_board_info, 1);
	pxa2xx_set_spi_info(1, &pxa_ssp_master_info);
	platform_device_register(&vads7846_device);
...
}

Do you have an idea why the SDCard is not right detected?

 

[notime2d8]

Do you have an idea why the SDCard is not right detected?

No, as the kernel is booting from the sdcard so thats working....the only thing after that is android mounting the mmcblk0p1 as sdcard either manually by the init.rc or automatically by vold.fstab...

can you try adding this to your init.rc: mount vfat /dev/block/mmcblk0p1 /sdcard

 

[d-two]

No, as the kernel is booting from the sdcard so thats working....the only thing after that is android mounting the mmcblk0p1 as sdcard either manually by the init.rc or automatically by vold.fstab...

can you try adding this to your init.rc: mount vfat /dev/block/mmcblk0p1 /sdcard

I have use your init.rc and with your kernel is it working... also it has something todo with the kernel...

EDIT: The SDCard is mount...
EDIT: Or can you give me your kernel an i will look what is the difference...

 

[notime2d8]

I have use your init.rc and with your kernel is it working... also it has something todo with the kernel...

EDIT: The SDCard is mount...
EDIT: Or can you give me your kernel an i will look what is the difference...

I'm just using the kernel/common/android-3.8 from the android git... You should just go ahead and jump kernels...so you can figure out why my touch isn't working....can you post your zImage so I can test?...I reverted all my changes in frameworks/base and deleted my .idc file but still....its not working...

Sent from my SGH-T959 using xda app-developers app

 

[d-two]

I'm just using the kernel/common/android-3.8 from the android git... You should just go ahead and jump kernels...so you can figure out why my touch isn't working....can you post your zImage so I can test?...I reverted all my changes in frameworks/base and deleted my .idc file but still....its not working...

Sent from my SGH-T959 using xda app-developers app

OK, i don't know why... but after loding your config and setup a little bit more it's working

Here is my zImage...

 

[d-two]

Have you test my kernel?

 

[notime2d8]

Have you test my kernel?

Yes...it booted but after the dmesg it stayed blank and never went to the home screen.

Sent from my SGH-T959 using xda app-developers app

 

[d-two]

Yes...it booted but after the dmesg it stayed blank and never went to the home screen.

Sent from my SGH-T959 using xda app-developers app

No error message or something else...

Has Android started?

Sent from my NexusHD2 using xda app-developers app

 

[notime2d8]

No error message or something else...

Has Android started?

Sent from my NexusHD2 using xda app-developers app

Nope, I'll hook it up to adb later...but I think android did start and it never rebooted...

Sent from my SGH-T959 using xda app-developers app

 

[notime2d8]

I wish i had an sdio card to test....

I really would love to get sdio working/tested or someone else to.. @d-two :highfive: Because i really want to try and get one of these cards!!!

http://www.ebay.com/itm/Universal-S...070?pt=LH_DefaultDomain_0&hash=item2a2c7cc206

Wireless N, FM, and bluetooth...This one probably won't work cause it looks like some connections still need to be soldered.

I don't know where I'm going with this but everything works with USB host ... Some slowly... also the Wii and ps3 remotes work over Bluetooth...I might post another video of the USB video and Wii remote when I get double buffering and some USB cables done.

 

[notime2d8]

I don't know where I'm going with this but everything works with USB host ... Some slowly... also the Wii and ps3 remotes work over Bluetooth...I might post another video of the USB video and Wii remote when I get double buffering and some USB cables done.

Here's my next shaky video...with the resolution dropped down to 800x600 using a Wii remote...i didn't plan it out...it's a poorly done video...but yeah...usb mouse/video and Wii remote.

 

[NikolasV]

Hi!
Could someone write which exactly commands i must type in linux terminal to create partitions with needed size and copy all necessary files to them.
I using Debian live cd/

 

[orzech2111]

Hi!
Could someone write which exactly commands i must type in linux terminal to create partitions with needed size and copy all necessary files to them.
I using Debian live cd/

You have to partition SD card, e.g. by Gparted or any tool for Windows (partition for Android must be second and at least ~200mb I think). Next: write in linux terminal: mkfs.ext2 /dev/sdb2 (it should work, but I am not responding for any problems) or just (if you have graphical environment on Debian) run GParted and format it easier and safer way.

Next you should use this commands:
mount /dev/sda2 /mnt
tar -xvf /location/of/slim.tar.gz /mnt

It should work, but I am not sure it will work well. I hope I helped.

Sorry for my English. I tried to not make many errors(?) in this post.

 

[ALoGeNo]

Hi dudes, I have my htc universal modded with external wifi anntena connector SMA, I'm not using it is very sad to have that piece of hardware getting dust, maybe someone is interested on it, here I let you some pics, if you are not interested maybe can do this mod for him self hehe.

NOTE: I have also 4800mAh chinese battery pretty new with big cover, if some one needs better pictures just PM, this ones are old ones, now I have better camera

NOTE to SomeModerator: I dont Know if I'm breaking some rule, if I do just PM please/thanks.

Cheers.

Enviado desde mi GT-I9003

 

[paolo.oliveri]

Hi notime2d8 and All,
sorry for my basic questions, but I'm getting trouble while trying to boot android with My UNI G3 64mb Device.
With Minitool Partition Wizard I partitioned My 8gb SDHC Card in two: The first partition is FAT32, c.a. 7gb, the second one is EXT4, 1gb. Also I've tried with another 2gb SD Card, partitioned in the same manner (but obviously with other partition dimensions).
Then I transfered zImage, startup.txt and haret-w.exe to the first partition; I tried several options from sourceforge site: zImage 3.10, 3.8 and the "slim" version.
Then I mounted EXT4 partition with Paragon ExtFS, and I extracted the correct content of data tar to the root of that partiton (i.e. data.tar.gz or data.lite.tar.gz with zImage 3.10 or 3.8, slim.tar.gz with the correct zImage in "slim" section of the site).
Then I checked for startup.txt options, to remove "mem=128M" and add both nothing or "mem=64M" in the boot sequence, and add
another tweaks, such as Touch Calibration parameters and other stuff.
Then I finally inserted SDHC (or SD) to the phone, I checked that bluetooth and phone were powered on and not Wi-Fi stack (I've also tried with BT off with the same results), and finally I launched "haret-w.exe".
Application starts, begins to load drivers, but after a few seconds arrives at the message I added in attachments. As you can see, the device reboots itself without any success to let it work. What am I doing wrong?
Thank you all for the patience.

 

[dstyl]

Boot athena from USB or internal FlashDisk

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.

Sorry i know its a bit offtopic but im having problems to boot android.I have no minisd card so the only possibilitys to boot are over the cable and than from usbstick or the internal flash of the athena 400. I tried everything but i always get kernel screen , then android and then only a black screen stays or my phone just reboots into wm. I dontknow what im doing wrong , formated usb into 2 ext2 partitions and a swap and still cant boot. If anyone knows what im doing wrong ? I just posted it because the athena forums are dead

 

[OMOZ]

HTC Universal und Android

Hello to all, I have now spent 24 hours to finally see Android on my HTC Universal and fail again on reboot after reboot comes back WM 6.1, I think the SD card partitioned'm right at the end .... although I until now everything always hinbekommen, I read often use some commands as write in linux terminal: mkfs.ext2 / dev/sdb2, how do I do that? Create file? Sorry for the stupid questions, but hope dies last, maybe even one or the other but still a hint, because somehow I take the HTC Universal regulary! Did my comment / question from German to English with Google translator translated

Regards OMOZ

 

[kEviN.H]

D900 is good phone