Acer Iconia W700 i3 Processor

[Samer Al-bairouty]

Ya Hi there,,

please may i know why ur release is not compatible with ACER ICONIA W700 i3 processor?

 

i tried more & more of installing Android-x86 in different ways but I’ve got stack on Android Logo & that’s it,,

can u please have any solution of successfully installing ur android 4.4 RC2 on my Acer Tablet?

Note: i just wana tell u that i have installed ur version on many tablets & Laptops & all are installed succesfully except my tablet :(

Thank u,,

[Chih-Wei Huang]

Looks like the sensor hal crashed on your tablet.
Probably it's designed for w500, not for w700.
You can either debug and fix it,
or just disable it.
(edit /system/etc/init.sh and remove the w500 line)

[Samer Al-bairouty]

Hello Mr.  Chih-Wei Huang

Actually i was looking for u since very long time but thanks GOD that finally i got u :)

Thank u very much for being here to give as help, so can u with a big PLEASE to show me in brief how to
disable that line which u advised me to disable it?

plz i rally need to install Android_x86 on my tablet :(

Thank u very much & have a Wonderfull day,,

[Samer Al-bairouty]

Mr. Chih-Wei Huang

Hi again & sorry for being disturbing u my friend,, ill try to disable the line by installing the android then
ill boot from bootable flash like ( Ubuntu ) to edit that line to disable it,, is what im doing will fix?

Thank u,,

[Chih-Wei Huang]

That's just a text file (script).
You can modify it by any editor.
No need to use ubuntu.
(note the /system must be instaled as read-write mode,
you can't change it in livecd mode)

> --
> 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.



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

[Samer Al-bairouty]

Hi again,,

This's a final request my friend & i won't disturb u anymore, cz i feel u r always in harry :(
can u please do that script for me, cz i dont know how,,

Thank u & have a good day

On Sunday, May 25, 2014 2:02:42 AM UTC-8, Samer Al-bairouty wrote:

[Samer Al-bairouty]

i know that to apply the script it will be from the debug mode after i press Ctrl + Alt + F1
but i dont know what to write in the script,,

sorry again,,

On Sunday, May 25, 2014 2:02:42 AM UTC-8, Samer Al-bairouty wrote:

[Somebody]

Nobody can do it for you. It has to be done ON YOUR INSTALL.

[pstglia]

Hi,

Try this:

After booting android, press Ctrl + Alt + F1 to enter console. Then type these cmds:

cp /system/etc/init.sh /system/etc/init.sh.backup

grep -v w500 /system/etc/init.sh.backup > /system/etc/init.sh

After this, boot your Android.

Important: As Chih-Wei Huang said, You can only do this for a installed android-x86, not for live-cd. 

Also, make sure you selected Y for "would you like to make /system writable" during installer

[Samer Al-bairouty]

Mr. Pstglia

Thank u for reply, but im still facing a small problem, it gives me permission denied with knowing that i clicked
yes when asked me to make the /system writable during installation :(

so what to do now? plz give me a help

Thank u for being helping me ,,
Have a good day,,

On Sunday, May 25, 2014 2:02:42 AM UTC-8, Samer Al-bairouty wrote:

[Samer Al-bairouty]

By the way i have also tried this command ( mount -o remount,rw /system ) but it didnt work,
It gives me the same ( Permission denied ),,

On Sunday, May 25, 2014 2:02:42 AM UTC-8, Samer Al-bairouty wrote:

[Samer Al-bairouty]

On Sunday, May 25, 2014 2:02:42 AM UTC-8, Samer Al-bairouty wrote:

[pstglia]

Hi, are you sure you are booting from your hd/device where you installed. It's strange.

If you are really booting from hd, the only (remote) possibility I think is that detection script is geting Android img from other src than your hd.( Maybe the flashdrive you used to install Android).
If this is the case, you could boot your machine making sure the flashdrive is not connected to your hardware.
But, to be honest, I don't think this is the problem. You must be missing something :)

You can also try using busybox with your mount cmd:
busybox mount -o remount,rw /system

[Somebody]

Android-x86 mounts /system as RW by default. No need to remount it.

If it is not RW, then you didn't install /system AS RW, which means that it is stuck inside a squashfs container, and CANNOT be modified by ANY trivial means.

[Samer Al-bairouty]

You are absolutely right,, u r Genius :))

Actually I was trying to install android on external USB instead of internal HDD,,

maybe that’s why It was giving me some error, so after ur last mesg u let me have doubt as u said, so I reinstalled the Android again but this time into the internal tablet’s HDD & Viola ur command executed successfully,,

 

And also the android for the first time booted successfully :) its emazing man, im really happy :)

 

Very big thanks to you & to Chih-Wei Huang  for being  helping me,, I swear that I spent 4 months trying to figure out the way of how to ask for a help & I couldn’t  till I found this place,,

Thanks guys & I appreciate all of u my friends :)

 

Thank u & have a wonderful life ;)

[Chih-Wei Huang]

Could you show the content of /sys/class/dmi/id/uevent
Run 'cat /sys/class/dmi/id/uevent' in the console.

Besides, it's better to find the root cause of the crashing
and fix it. Please provide logcat of the crashing.

[Samer Al-bairouty]

Hi Chih-Wei Huang

You told me it's
( better to find the root cause of the crashing and fix it. Please provide logcat of the crashing )
What does that mean? cz i didnt understand,

Thank u,,

[pstglia]

He said we should investigate why w500 sensor hal  is crashing on your hardware. The cmds you executed removed it from init.sh, so it's just a workaround. 

logcat output will help to debug and solve it.

Cheers,

pstglia

[Samer Al-bairouty]

:) aha I see, actually I don't know how to investigate the problem, u figure out how :)

From my side the system is working very well, I have a small bug when screen goes off I notice its becoming light black screen not dark black, it means the screen is still on, so will drain the battery ;)

Anyway thank u very much my friends for all what u did here,,

Have a good day :))

[Nabil Hassani]

I use a W700 i3, and managed to run your compiled Android x86 4.4.2 RC2.

As you advised removing the section with W500 removed the crash.

Is there any progress on this front?

because without the sensor section, the W700 auto-rotate does not work, and it is stuck in landscape mode.

Otherwise, everything seems to work fine.

Thanks for the work. 

[pstglia]

A logcat /dmesg output is necessary to investigate what is wrong.

Can you provide it? You can use this procedure to save these outputs on a flashdrive:

You must plug a second flash drive with a fat32/ext2 or ext3 partition. Then do the following:

cd /data

mkdir x

# Note: sdc1 was the device/partition associated in my system. Yours may be different. dmesg shows you the device created

busybox mount /dev/block/sdc1 x

cd x

logcat > logcat_output_DEVINFO_YYYYMMDD.txt 

# Wait about 10 seconds to collect enough info. Then press CTRL+C to stop writing

dmesg > dmesg_output_DEVINFO_YYYYMMDD.txt

cd ..

busybox umount x

# after unmounting, you can unplug the flashdrive

Thanks

[Nabil Hassani]

I will provide it soon, as soon as I acan boot with Android, currently not.

Thanks

[Nabil Hassani]

I got the two text files, logcat and dmesg.

I am attaching them as zip.

Hope it helps you to fix this issue.

Cheers

Nabil

On Friday, 20 June 2014 02:05:33 UTC+2, pstglia wrote:

[pstglia]

Just to confirm, you got this info with original init.sh right? ( trying to load w500 module)

Thanks!

[Nabil Hassani]

This was after removing the offending W500 section.

I cannot get into Android without moding init.sh in this way.

So I guess it is needed that I put back the offending section, then remove it,

then immediately after the first successful boot collect logcat / dmesg fresh?

please confirm.

[pstglia]

Hi, 

Can't you access console/terminal screen when the module is loaded (alt+f1)? Your device keeps stucked?

Have you tried debug mode?

If you remove the module and reboot device, we'll lose the log info generated. The ideal was:

 - Boot your device, loading the w500 module;

 - Enter console (alt+f1 or alt+f2 if under debug mode) and collect logcat/dmesg info

Regards,

pstglia

[Christopher Price]

Just a heads up, I know the Android-IA team used the W700 as one of their development systems in the past. You may want to try Android-IA IvyBridge and that could work.

I don't mean to go off-topic on Android-x86.org, it would be nice if we could get both working - just wanted to point out Android-IA should work today.

The only subtext there is you may need to replace the Wi-Fi card with a newer one, as Android-IA supports only the Intel 3160 & 7260 families today. Be sure to switch back over to UEFI booting if you disabled it on Android-x86.

Christopher Price

ConsoleOS.com

[Nabil Hassani]

The Android-IA effort keep on claiming that their releases are pre-alpha, how can I trust or want such releases.

Besides, on W700, I am using usb legacy, and it is working very well with 4.4.2 RC2 here.

Only plodding along about the auto-rotate that is not working.

W500 is mint in fact (I have that too).

[Christopher Price]

I won't speak for the Android-IA team, but clearly when any large company releases an OS kernel, they're going to have to be at a much higher standard than what anyone in the community holds to.

By referring to the kernel as a prototype/pre-alpha, people are much less likely to depend on it in the general public. Android-IA has to be updated via flash drive or fastboot today - to the general public, that's pretty "pre-alpha" - even if it does indeed work very well.

All I am saying is, try it out and see for yourself. It's free software and can easily be removed. W700 was a device that 01.org has used to engineer Android-IA, you're just more likely to get a bootable device with it as a result, that's all.

Christopher Price

ConsoleOS.com

--
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/2qgRMORq-70/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.

[Nabil Hassani]

But I am getting a pretty good result with the RC2 from this google team, I am not complaining, and for Acer W500 it works perfect.
I will try it maybe sometime when I get a bigger hard drive on the W700.

For now, just trying this RC2 from usb.

[Nabil Hassani]

With the debug mode option, I get to a command prompt twice in booting, and when I exit the second time, it again stays stuck at the Android logo.

trying to mount sdc1 is not possible, it says not directory found.

after the first exit, and doing ctrl+alt+F2, there is no /data folder, so I cannot mount to x.

also if I try to mount the usb intoan x in the /tmp folder, again I get the error there is no directory, so the mount command does not seem to work.

As a result, I cannot get you dmesg or logcat in debug mode.

There must be another way?

[pstglia]

In this case, you can try to use adb from another machine. Something like this:

adb connect ip_of_the_device 
adb logcat -v threadtime 

Regards,

pstglia

[Nabil Hassani]

Maybe, though I used usb serial connection not LAN.

But I think I will try to collect dmesg / logcat by using the /data folder without ctrl+alt+F2, and x as a permanent folder, and collect the text files from the usb within windows.

[Christopher Price]

Despite their model numbers being similar, W500 and W700 are completely different tablets. The W500 is an AMD C-50 whereas the W700 is an Intel 3rd Gen Core processor tablet. That's why the two distributions will perform very differently on each, Android-IA won't even run on the W500 whereas on the W700 it will probably run better (aside from Wi-Fi, again you may have to upgrade the mini-PCIe card for Android-IA to work fully).

Android-IA can run live from the USB too, just make sure to disable UEFI Secure Boot if your machine has it enabled.

The W500's C-50 GPU is probably old enough that it ducks the RadeonSI issue, so you actually have the "sweet spot" in terms of Android-x86.org AMD systems in the W500.

Christopher Price

ConsoleOS.com