Enable touchscreen for external monitors or built-in touchscreen devices (for example, laptops)

[Rusu Mihai Cristian]

Hello. I own a HP Pavillion x360 11-n010sn that has a built-in touchscreen with 10 points. I tried to boot android x86 in live cd mode... successfully, but I am not going to dual boot it if the touchscreen for this system is deactivated, as for windows 8.1 (my system) is working perfectly.
I suggest to add for some devices support for the touchscreen, as I cannot, in any way, run android without touchscreen. The mouse is working perfectly, but I still want that feature implemented, and if you cannot do it, at least make some images for this device to be booted and the touchscreen to work like a tablet... Please do something!

[Edgardo Gho]

How is your touchscreen connected? USB?

If it is, then run a linux live cd, and if it works there, run: lsusb and lsmod

Paste the output here so we know which driver is handling your touchscreen.

[Rusu Mihai Cristian]

The touchscreen is built in the laptop.

Did you look at the specs of the device?

I tried to boot it up, worked perfectly, but no working touchscreen

And, I am a bit of a noob with these linux instructions... :(

[Edgardo Gho]

Even if it is built in with the laptop it needs to somehow connect to the motherboard. Most of the touchscreen I know (resistive, capacitive, optical) are USB. If you run a linux live cd (I would use the latest ubuntu) just open a terminal and type:

lsusb > ~/Desktop/lsusb.txt

That will list the usb devices and create a file on your desktop with them

Then type:

dmesg > ~/Desktop/dmesg.txt

That will list all the devices the computer picks up during boot.

If the touchscreen works on linux, make sure you also run:

lsmod > ~/Desktop/lsmod.txt

That will probably show which driver is handling it (although that can be extracted from dmesg too).

[Rinaldo Jonathan]

There is no such thing as n00b.

About the linux live cd, you can just download ubuntu (http://ubuntu.com), boot it, wait until the desktop appears, right click the desktop, open new terminal window, type the command he said.
Put here all the results. It will be shown in your live desktop, as a txt file.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Rusu Mihai Cristian]

If I download it, Shall I just put it to an USB stick and just boot it? or how? My laptop DOES NOT support CD/DVD, AND I AM NOT GOING TO BUY AN EXTERNAL DVD DRIVE.

That is all i need. I will attach later on the logs.

Shall I open them before to see if I can figure it out?

Shall I install it to an drive like: Make out of C:\ with 400GB into 350 GB and one with 50GB and install it there, or just use an iso live boot from the usb drive of 2 GB that I have?

That's all...

[Melvin Sowah]

To run Ubuntu off a USB, Google Unetbootin, download it, run it, then select Ubuntu from the distribution list. Plug in your USB and select that from the list below. It will download Ubuntu for you and make your USB bootable. All you need to do then is restart and boot into your USB

[Rusu Mihai Cristian]

And is it alright if I downloaded the ubuntu 15 latest iso and used the unetbootin with that iso?

[Melvin Sowah]

Yeah, that should be fine

On 18 May 2015 08:17, "Rusu Mihai Cristian" <951m...@gmail.com> wrote:

And is it alright if I downloaded the ubuntu 15 latest iso and used the unetbootin with that iso?

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/PUTDWBx6gOs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.

[Rusu Mihai Cristian]

Finished download and unetbootin on apacer 2GB usb drive. Booted it, pressed try without installing, on the keyboard. Screen turns off, turns on with some console-like screen, with an cache error and idk what else, screen turns off, ubuntu screen with 5 dots turns on, dots turn orange, white, and ths is the problem. Tried 3 reboots, but gets stuck at the second turn orange dots at first 1 or 2 dots, and the usb drive turns off (the led is not flashing anymore).

Waited 20 minutes, still nothing. 

Do I have to dualboot this thing in order to get a driver info to get android here? or I can tri-boot windows, ubuntu and android?

I am really stuck :(

[Edgardo Gho]

Try a different linux distro. I would use sysresccd:

http://www.sysresccd.org/SystemRescueCd_Homepage

You can burn it to a flashdrive like ubuntu using unetbooting.

Once it starts, it will leave you on a terminal, just type: startx

that will start the GUI. Check if the touchscreen works there. Then run the commands to get lsusb, lsmod, dmesg into files and post the files here. You can probably connect your computer to the web using ethernet or wifi using sysresccd.

[Edgardo Gho]

if your touchscreen is USB, you might get the vendor id and product id using windows:

http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9

I've seen weird touchscreen that use I2C and require a few modules to be enabled in order to work on linux.

[Rusu Mihai Cristian]

I saw that the usb stick was formated in FAT mode, not FAT32. Will try again. If it will not work, then I will try sysresccd on it.

If still not working, then my USB stick and my PC are 2 damn little *******

[midi jari]

ok

1) Downlaod Linux Mint (Google that) and you'll find downloadable ISO.

2) Use Unetbootin to write the image on the USB (make sure it's already formatted as FAT32)

3) Boot from the USB 

4) WAIT!

5) Once on the Desktop, Hit Ctrl+Alt+T, a Terminal Window will show up, here you type some commands

6) type this: 

lsusb > ~/Desktop/lsusb.txt && dmesg > ~/Desktop/dmesg.txt && lsmod > ~/Desktop/lsmod.txt

Either write it yourself or copy and paste the whole line above.

7) then once done, type this: nemo ~/Desktop, this will open a window, and you'll see 3 files: lsmod.txt and dmesg.txt and lsusb.txt

8) Copy them somewhere else (on another USB Disk/Drive, not your HDD, and not the USB you're working from) then upload them and share the link here.

[Rusu Mihai Cristian]

Ubuntu is a big fail... for now...

So, Is it alright if I upload those files from linux mint directly to the internet? Here?

[Rusu Mihai Cristian]

Got Sysresccd, ran startx, but:

Touchscreen still not working!!!!!!!!

Here are the files you all requested

Thanks a lot for the help

[Fajar A. Nugraha]

On Tue, May 12, 2015 at 12:48 PM, Rusu Mihai Cristian
<951m...@gmail.com> wrote:
> Hello. I own a HP Pavillion x360 11-n010sn that has a built-in touchscreen with 10 points. I tried to boot android x86 in live cd mode... successfully, but I am not going to dual boot it if the touchscreen for this system is deactivated

https://www.google.com/search?q=HP+Pavillion+x360+touchscreen+linux
links to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376509
, which says you need kernel >= 3.16. Sysrescuecd with kernel 3.14
won't work.

You didn't say which version of android-x86 you boot. I used T100
magic stick (http://forum.xda-developers.com/windows-8-rt/win-8-development/live-asus-t100-ta-magic-stick-t3091481)
that comes with kernel 4.0, works okay on asus t300 chi. Might work on
your device too.

If THAT works, you'd then need to do manual install (process not covered here).

> I still want that feature implemented, and if you cannot do it, at least make some images for this device to be booted and the touchscreen to work like a tablet... Please do something!

You do realize that developers and contributors doesn't get paid for
their work on android-x86? Saying "I want this, fix it, do something"
doesn't help.

If you want something that works with support, buy amiduos. It's an
emulator (not native), but very much usable when I tested it. If you
want to help android-x86 development, then be patient when testing
various things.

--
Fajar

[Edgardo Gho]

You've got a crappy I2C DesignWare controller. It needs to be enabled in the kernel for the hid-multitouch module to pickup the touchscreen.

[   35.920964] i2c_designware 80860F41:00: controller timed out
[   35.920995] i2c_designware 80860F41:00: Unknown Synopsys component type: 0x00000000
[   35.921026] i2c_hid i2c-ITE33D1:00: unable to fetch the size of HID descriptor (ret=-110)
[   35.950030] i2c_designware 80860F41:01: timeout in enabling adapter

You will need a kernel newer than 3.17 (3.18 or 4.0 will work). The Synopsys Designware modules have to be enabled:

CONFIG_I2C_DESIGNWARE_CORE=m
CONFIG_I2C_DESIGNWARE_PLATFORM=m
CONFIG_I2C_DESIGNWARE_PCI=m

This touchscreen won't work with ubuntu 14.X unless you change the kernel. But I'm positive that if you compile a kernel with those modules enabled touchscreen will work.

[Edgardo Gho]

By the way, the sysresccd has those modules built in:

i2c_designware_platform    12438  0 
i2c_designware_core    13304  1 i2c_designware_platform

But they don't work for that touchscreen on kernels older than 3.17. I have an asus laptop (crappy) with the same touchscreen and it took me a long time to figure out how to make it work under linux.

From what I see the android_x86 defconfig for kernel 4.0 has those modules enabled. Please try with a build that has that kernel.

[Rusu Mihai Cristian]

luni, 25 mai 2015, 10:53:26 UTC+3, Fajar A. Nugraha a scris:

On Tue, May 12, 2015 at 12:48 PM, Rusu Mihai Cristian
<951m...@gmail.com> wrote:
> Hello. I own a HP Pavillion x360 11-n010sn that has a built-in touchscreen with 10 points. I tried to boot android x86 in live cd mode... successfully, but I am not going to dual boot it if the touchscreen for this system is deactivated

https://www.google.com/search?q=HP+Pavillion+x360+touchscreen+linux
links to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376509
, which says you need kernel >= 3.16. Sysrescuecd with kernel 3.14
won't work.

So, Will you suggest me an iso file download link for use with any PC that has a linux kernel over 3.1X?

 

"You didn't say which version of android-x86 you boot. I used T100 
magic stick (http://forum.xda-developers.com/windows-8-rt/win-8-development/live-asus-t100-ta-magic-stick-t3091481) 
that comes with kernel 4.0, works okay on asus t300 chi. Might work on 
your device too."

I used at first an ISO Image from intel with AMD-64, using android version 4.4. I was hoping that it will be the same with android x86. So I came here to see if it is ok.

[Fajar A. Nugraha]

On Tue, May 26, 2015 at 1:26 AM, Rusu Mihai Cristian <951m...@gmail.com> wrote:
> So, Will you suggest me an iso file download link for use with any PC that
> has a linux kernel over 3.1X?
>

> magic stick
> (http://forum.xda-developers.com/windows-8-rt/win-8-development/live-asus-t100-ta-magic-stick-t3091481)

Did you open that link?

[Rusu Mihai Cristian]

I will try it. I can Try it, but I want those 3 systems tri-booted from my UEFI Hard-Disk.

Cheatman said in a post in that topic: The HP omni problem comes from the kernel, which I did not build and I do not maintain. Also, I don't have a HP omni, so I can't test it out.  

[rbg]

you can try the latest builds from git here:

      https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing

[Rusu Mihai Cristian]

I wanted just a guarantee that it will work WITH THE TOUCHSCREEN on this device that latest. The 4.4 latest before the 5.1.1 releases are with the kernel over 3.18?

[Fajar A. Nugraha]

On Tue, May 26, 2015 at 12:46 PM, Rusu Mihai Cristian
<951m...@gmail.com> wrote:
> I wanted just a guarantee that it will work

... and that, is your main problem.

With open source software in general, saying "I want a guarante" will
not get you anywhere. If anything, it will only discourage others from
even trying to help because you'll come up as being lazy. Again, if
you want support, including "does it guarantee to work on
configuration X" or "will I get a refund if it doesn't work", use one
of the commercial solutions.

If you want to keep on using android-x86, be prepared to do various
testings, and there's no guarantee that the end result would be like
what you want. If you see others using the same hardware as you do,
great, as it means you can learn from their experience. Don't count on
others to do the testing for you though.

> The 4.4 latest before the 5.1.1 releases are with the
> kernel over 3.18?

git builds should use kernel 4.0 (haven't check the official build).
Same thing with T100 magic stick. They might include different kernel
configs, libraries, or customization though, so some of the builds
might work on your system while others wont.

--
Fajar

[rbg]

you can play what if's all day...or you can try a build and find out...

[Rusu Mihai Cristian]

To be honest, I have school in the afternoon, as I don't have much time. And I don't want to get there without my homework done. So That's why I am that kind "I want a guarantee". I mean, I want to know if it was tested on devices like mine.

[Antony Stone]

On Tuesday 26 May 2015 at 17:37:46 (EU time), Rusu Mihai Cristian wrote:

> To be honest, I have school in the afternoon, as I don't have much time.
> And I don't want to get there without my homework done. So That's why I am
> that kind "I want a guarantee".

In that case it sounds very much like an open source project under active
current development is not the right solution for your needs.


Best regards,


Antony.

--
Anyone that's normal doesn't really achieve much.

- Mark Blair, Australian rocket engineer

Please reply to the list;
please *don't* CC me.

[Rusu Mihai Cristian]

I just tried the iso from your git build links. The 4.4 with 64 bit thing did not work: In boot options, it did not found my usb stick bootable.

Will try with 5.1.1

[rbg]

that is a Bay Trail-M SOC processor I think you'll find....

you should be using the T100 / Magic Stick / .img builds for that system most likely...

[Rusu Mihai Cristian]

I got the android 5.1.1 iso but it booted me to that A N D R O I D and then it took me to a terminal. No android boot animation, no UI, no nothing but the terminal. Can somebody help me?

[Rusu Mihai Cristian]

Please help me! I do not have a damn clue why is it stuck on the android terminal and not booting in the U.I.

Help

[Antony Stone]

On Monday 08 June 2015 at 20:38:52 (EU time), Rusu Mihai Cristian wrote:

> Please help me! I do not have a damn clue why is it stuck on the android
> terminal and not booting in the U.I.

Please remind us what CPU and graphics chipset (be as specific as you can be)
you are trying to use, and also let us know which Android-x86 version / image
you are running.


Thanks,


Antony.

--
+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++

[Rusu Mihai Cristian]

Mentioned above at the very first post. In other words, Intel pentium n3520 @ 2.16GHz

That is how I failed... 

[Rusu Mihai Cristian]

and the image is an android 5.1.1 image that boots into a terminal and not into the U.I.

[Rusu Mihai Cristian]

Erm, will someone help me install the android from a 1.5 GB USB Stick onto a 64 bit laptop with touchscreen (means linux kernel 3.18 or over to fix the touchscreen bug) or you will all sit here and do nothing?

[Rusu Mihai Cristian]

I want to be precise: I want an ISO file of an android image that is stable and has all its functions working, no matter if it's x86 or x64. That's all I need.

[Edgardo Gho]

The new sysrescd http://www.sysresccd.org/Changes-x86 has 3.18 as alternative kernel.

Make sure you choose the alternative kernel when booting (not just regular kernel which is 3.14).

run startx and X should start with touchscreen support.

If it works, then at least you know that your touchscreen is compatible with kernel 3.18.

I have a similar touchscreen on an ASUS laptop and have been using kernel 3.19 for it (although I remember using 3.18.2 and it did work).

I did have some problems running Android-x86 on that laptop. Video did not work. I can't run android-x86 on that laptop for the moment since I use it for something else.

I would advise you to clone the source and build it yourself. It takes a lot of hours to build it but If you don't erase the folder with the source then next builds are only a few minutes.

If you want something that works with no problem I would use genymotion or some other android emulated environment.

[Rusu Mihai Cristian]

First off, I have NO IDEA how to build anything in the IT terms.

Second, Emulation is laggy for both the Host OS (the one used now) and Guest OS (the emulated one)

I want to be a bit precise: If any apps work, google play, video and sound, wifi and ethernet cable then I am satisfied

[rbg]

IMO - your best bet is to just use this....

http://amiduos.com/lollipop

[Mexus]

Man, change you attitude or get the f out of here. I am sick and tired of your requests. Are you paying these guys or what? I want, i want, i want. Do you know what everything i want?

Do you know how many ISO's and builds did i try until i got half of the things working? Before i started with android i have no idea about compiling from source code. Nothing. But i WANTED to make it work. I did read thousands of topics, spend my free time and kept trying instead of saying i want and do something to the others...now i am compiling my own builds and still reading because there is still so much to learn. If you have no time to test things and don't even want to sacrifice your free time then better forget about Android. Because this is nothing for you. 

[Rusu Mihai Cristian]

I don't know how to build, alright? even if I learn, I don't have any free time.

[Darren Clark]

People here have actually spent more time reading you say you don't know how to build an ISO than it would've taken you to learn.

If you don't have any free time, what makes you think anyone else does to get you what you want?

[Rusu Mihai Cristian]

I have managed to make it work, finally

but, I cannot install it anywhere.

if I try to boot it in UEFI, whether option I choose it remains like a console and a large _ frozen there. Nothing changed, on the 1366x768 resolution

If I boot it from legacy mode, I can live CD it, but if I install it, I only get from USB stick, same to the choose drives and hard drive, only fatal errors, then it exits because I have no space. I have 400 GB of space free... WTH...

The image is 4.4 r2, the touchscreen works, but the keyboard not works, my wifi has WPS and I can download somehow a keyboard for the screen (hacker's keyboard) from an apk downloader very hard, but possible.

That is all, the biggest concern being not able to install it in legacy mode, and not working from the UEFI anything

I am sorry for all my imature behavior earlier...

[Rusu Mihai Cristian]

Error messages at creating a partition:

Trying to use win95 usb stick (the actual live cd usb drive) - Can install in all formats, but I am affraid that I will lose the Live CD and... yeah... I want it on hard drive

-FATAL ERROR: Bad Primary partition 0: Partition ends after end-of-disk. Press any key to exit cfdisk.

Trying to use the Hard disk in any way (New partition, unpartitioned disk space etc.)

-Warning!! Unsupported GPT (GUID Partition Table) detected. Use GNU Ported.

-After pressing any key, same as the USB one: FATAL ERROR: Bad Primary partition 0: Partition ends after end-of-disk. Press any key to exit cfdisk.

[Mikerx86]

Your partition is corrupted Google the Linux forums for how to fix this... If that doesn't work use a track sector imager to back up your data. And reformat..

Mike

Sent with AquaMail for Android
http://www.aqua-mail.com

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Rusu Mihai Cristian]

Can you give me the link to that post please?

I tried the following: Unpartitioned space, FAT32 format in one partition, UNetBootIn. Same errors.

[Mike R]

Google the Overlapping Partition Error...

On 7/16/2015 12:57 AM, Rusu Mihai Cristian wrote:

Can you give me the link to that post please?

I tried the following: Unpartitioned space, FAT32 format in one partition, UNetBootIn. Same errors.

[Edgardo Gho]

http://lmgtfy.com/?q=Overlapping+partition+error

[Rusu Mihai Cristian]

SourceForge is down... One thing I tried is to delete all my non used partitions that had all the free space.

I am not used to linux... sorry...

I could try to get some tool to make an ext3 partition... if that ain't buggy?

[Mike]

Ya I noticed you said cfdisk AFTER I hit send, Sry, Honestly I was In linux using Gparted when I got the error, so I just tried there, Not sure how to Fix in windows, and Honestly, I couldn't even fix mine, I had to reformat the entire drive, By Reformat I mean FORMAT C: NOT delete the Partition.... I wanted it to do the whole drive to make sure I wasn't starting to get a Hardware Failure... So best bet is google overlapping partition in windows and see what you can find...

Mike

Sent with AquaMail for Android
http://www.aqua-mail.com

--

[Rusu Mihai Cristian]

I want to add something, even if I did not add at the first posts... I want to dual boot it along with windows 8.1 (Warning! Windows 10 is coming!)..

My C:\ Drive is my windows partition

My D:\ Drive is my OEM recovery accessible from windows and I think there is another partition of recovery that is not accessible...

I do not accept the idea of formatting ANY of the partitions including Windows and recoveries. because if I do that, My laptop would turn into some useless metal... The games I wish to play (and I have on G.Play) are terraria mobile edition and minecraft. I might play them as PC versions, but I feel like the touch(screen) is PURELY useless... And I do not want to spend more money when they come out on windows store because I feel like I am throwing away money for no reason (I mean the same game just in windows version)...

So... yeah... any other ideas?

SourceForge is still down...

[Rusu Mihai Cristian]

Or to make it WAYYY more easier: Is there any way to save data inbetween live cd sessions of android x86? If there is, and it will work. then my problem is solved. (乃^o^)乃

[Mike R]

Nope, Only on Install, Live doesn't save any data....

Mike

On 7/17/2015 12:20 PM, Rusu Mihai Cristian wrote:

Or to make it WAYYY more easier: Is there any way to save data inbetween live cd sessions of android x86? If there is, and it will work. then my problem is solved. (乃^o^)乃

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email toNope android-x86...@googlegroups.com.

[Rusu Mihai Cristian]

not even if you add a data folder or shit? because I heard that might work.

[Miker R]

Last I heard from C.W. nope, Unless something has changed in the last couple months....

As for the Partition thing, I couldn't agree more, But your not going to be able to re-size/adjust partitions until you solve the error...And In my mind I just made the decision to format because I figured EVENTUALLY it was gonna crap out on me anyway so instead of it doing it when I wasn't ready for it, I took care of it on my terms.....

As I said, I'd go find a decent DOS Imaging program I believe I had OSF, not sure, Do a T/S image of What's Important, Reformat, and Re-write the Image....

Just My opinion....

AND Yes Getting My download on July 29th 8-)

Mike

[Rusu Mihai Cristian]

If the partitions are windows and the recovery and 100 GB of unallocated space, can I do something about the imaging? the thing is, I do not want to format my windows/recovery partitions. Can I create one with imaging partition programs?

[Miker R]

The Imaging program I used Booted Off of a Burnt Cd and it runs in DOS, So Ya, You can do the Image on Anything that's on the Storage Device, Hell, Then If you wanted, Do the format, use the windows installer to reinstall windows, So your Partitions are setup Right, Then Overwrite with the Image(s), Than Partition what you want and you should be good...

Mike

[Miker R]

http://www.osforensics.com/tools/create-disk-images.html

On Friday, July 17, 2015 at 12:52:38 PM UTC-5, Rusu Mihai Cristian wrote:

[Rusu Mihai Cristian]

The windows is Pre-Installed, laptop has no CD Rom, and I have no installation disk.

[Mike R]

LOL, fun, Well Back in the day you could copy the OEM to a DVD and use it to re-install.. But I'd test first.... I haven't had that problem in a long time...

On 7/17/2015 1:00 PM, Rusu Mihai Cristian wrote:

The windows is Pre-Installed, laptop has no CD Rom, and I have no installation disk.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

[Rusu Mihai Cristian]

I don't want to f*ck up my laptop. I just want to be able to dual boot android along with this OS

without f*cking it up of course

[Mike R]

Well why not just Buy a Cheap USB/SDCARD or some kinda of "Plug-In" media and use it...

On 7/17/2015 1:05 PM, Rusu Mihai Cristian wrote:

I don't want to f*ck up my laptop. I just want to be able to dual boot android along with this OS

without f*cking it up of course

[Rusu Mihai Cristian]

I have that 4.4 r2 image on a 2 GB usb stick... it won't let me install it. You know any better image so I can install it without it having touchscreen/wifi/sound problems or installation errors?

[Mike R]

Honestly I'm not sure on that, Did you get it off of Android-x86.org??  I believe that has the OLD Installer On it, You Can check here, or My Downloads (www.android-x86.net), For the Builds with the new installer, other then that I've heard some USB Sticks just don't work... Dunno Why.....

On 7/17/2015 1:09 PM, Rusu Mihai Cristian wrote:

I have that 4.4 r2 image on a 2 GB usb stick... it won't let me install it. You know any better image so I can install it without it having touchscreen/wifi/sound problems or installation errors?

[Rusu Mihai Cristian]

original website (I think .org), it can be installed on the stick (shows the partition as win95), it runs perfectly in live CD mode...I will check the .net one

[Rinaldo Jonathan]

You aren't at school 24/7 right?
You want my story? Okay. I just graduated from high school, and my school starts at 7.00 morning and ends at 17.00.
But I still have time to mess around with android-x86. How? time management, dude.

next time, if you want to have a device that fully (well, almost) supported, buy the device that most of us use, or cwhuang use. Everybody knows that cwhuang works at ASUS, so I bought ASUS Transformer Book T100. Even after that, there is still no guarantee. I bought my ASUS, broke the digitizer (the community even knows that and suggest me to buy the replacement at eBay!), leave it almost a year, sending it for fixing and that took me a month, and even after that, the android-x86 is still not usable.

But after countless testing, it finally worked.
Now go buy T100 (well, that was not the point actually.)

Stop asking if anybody have tried. They haven't, so they ask you to try. Even if you donate your device, there is no warranty that it will work.

Basicly, if you don't want to cook (or help someone cooking), don't eat.

Pada tanggal 26 Mei 2015 22.37, "Rusu Mihai Cristian" <951m...@gmail.com> menulis:

To be honest, I have school in the afternoon, as I don't have much time. And I don't want to get there without my homework done. So That's why I am that kind "I want a guarantee". I mean, I want to know if it was tested on devices like mine.

[Miker R]

Partition should be EXT3/4....Not sure why if it's formatted that way it's showing as Win95?!?!?  Ain't that FAT32??  And yes the OLD installer doesn't format EXT3, Could be the problem.... In Which case your gonna need a Linux Live CD to format EXT3/4 anywho...  (or the new installler...)

[Rusu Mihai Cristian]

I got now some holidays. I got the most problems fixed. Now it is a setup problem. I could handle it. I have time...

I will retest with those 2 iso images (32-64 bit, my device has 64 bit)

[Rusu Mihai Cristian]

from the .NET website

and before that, I will retest the same image... with some adjustments. Will post results.

[Miker R]

Ok Good Luck

[Rusu Mihai Cristian]

Yeah that was an old installer. Which one of the new ones should I try first? 32 bit or 64 bit (my pc is 64 bit)? And also, it may take some time, because my internet sucks :(

[Mike R]

Really no advantage to 64bit (right now), just basically for test to get to 64/64, I'd go with 32 For App Compatibility reasons....

On 7/17/2015 1:50 PM, Rusu Mihai Cristian wrote:

Yeah that was an old installer. Which one of the new ones should I try first? 32 bit or 64 bit (my pc is 64 bit)? And also, it may take some time, because my internet sucks :(

[Rusu Mihai Cristian]

I have a Huge @$$ problem. I downloaded from the .net android x86 and it is the same old installer - 4.4 r2

and same from .org site.

I trust the 4.x versions more than 5.x versions so I don't know where to go now... 4.4 r2 is so stable... same problems. I tried with latest unetbootin and rufus 2.2 with MBR on bios and uefi. uefi you choose anything but windows 8 and does nothing. in legacy mode, same installation problem. unsupported GPT and that fatal error...

Any other ideas?

[Chih-Wei Huang]

2015-07-18 1:49 GMT+08:00 Miker R <mike...@android-x86.net>:
> Last I heard from C.W. nope, Unless something has changed in the last couple
> months....

Wait... What did I tell you?
Probably you misunderstood something.

The only difference between "live" and "non-live" mode
is the "live" mode saves data to ramdisk,
while "non-live" mode saves data to
a persistent storage.

So you don't really need to do installation.
You just need to specify a persistent storage
to the cmdline of bootloader, then you can
"convert" the live mode to non-live mode.

You can do it by specifying DATA=xxx
in the cmdline.
xxx could be a linux ext3/ext4 partition,
or a loopback file with linux filesystem.
How to do that is too complex that
I'm lazy to say here.
I suggest you search the forum.
There are many discussions about that before.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Mike R]

Chih-Wei Huang

12/28/14

2014-12-28 16:33 GMT+08:00 John Williams <ojohnn...@gmail.com>: 
> I have a question with your ISO,  how do I get it to save.   Everytime I 
> boot into the USB.  I have to reconfigure Android.  Or is it something I am 
> doing wrong? 

The iso runs in live mode. 
That is, all data save in ram and will lose after poweroff or reboot. 
You have to install it to HDD (manually), 
or change boot option to save data to usb. 
(I've posted the detailed steps. Search it)

https://groups.google.com/forum/#!searchin/android-x86/save$20in$20live$20mode/android-x86/svh5JBm5i3U/rkM5tBEV_H8J

MY BAD!  Must not have read all the way through......

Mike

[Rusu Mihai Cristian]

The results are these:

In all ISO 4.4 versions, from BOTH the websites, none work to install and still have the old installer.

Do I have to use GParted on an unallocated space partition and see if that works or I'm done for?

[Rusu Mihai Cristian]

Anyone can help me from the point from my last post? I don't want this post to be a necro...

[Rusu Mihai Cristian]

please...

[Rusu Mihai Cristian]

Well, if ther is still no answer, then I want to make this post a necro.

[Rusu Mihai Cristian]

I want to know,is there anything else I can try?

[Rusu Mihai Cristian]

The device had its bios updates and all of its system updates. After that, I tried to install ubuntu. I made a partition where to install it. I booted in test mode in UEFI. The results: it booted correctly. I suppose that it will happen the same with the android-x86 images...

It is all coming to a close end, my friends...

[Rusu Mihai Cristian]

The thread has been resolved, but another problem has appeared: The UEFI support.

I will create another post about this.

Thanks for everyone who helped.