i have asus R2E (umpc) which have pentium M processor and i915 gp.
and your iso is just ok, boots an run smoothly...
just wireless and touch screen not working?
how to add them to this build?
thanks any way.
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/yIbwxW2mGGcJ.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-x86...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
--
Hasan KÖSE
please tell us how can we do that job.
i have asus R2E (umpc) which have pentium M processor and i915 gp.
and your iso is just ok, boots an run smoothly...
just wireless and touch screen not working?
Hi,
> - audio (still waiting for the solution that Chi-Wei found)
Alsa is working, a few day's ago libaudio was pushed by Chih-Wei.
> - suspend/resume (still waiting for the solution that René found)
In ICS I am stuck :-(
resume will return to vt1, not the graphics screen
ctrl-alt-f7 also doesn't worrk
Are they related ???
very nice,I hardcoded 15 for the wetab.
i dont believe it. i just download and test your new build in asus r2e and yes,
as you say
* sound works,
* wifi works and
** touchscreen almost work
how almost: when i touch the CENTER of screen touch is OK,
but then when i move my hand from center to RIGHT, system understand is as DOWN,
when i move my hand left, system respond as UP etc...
Dear Stefan,
in your next build, it is posible to apply a patch
meintoined here:
http://groups.google.com/group/android-x86/browse_thread/thread/f2e5660a25496e84/2acb3a0496733d82?lnk=gst
i think this patch should address this issue and
then out asus r2E/H family umpc will get new life i think...
actually even it does not work, i think your build is enough to use in
asus r2e already.
thank you so much...
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/jRnFkIcRJSMJ.
wow, wow, wow!i dont believe it. i just download and test your new build in asus r2e and yes,
as you say
* sound works,
* wifi works and
** touchscreen almost work
how almost: when i touch the CENTER of screen touch is OK,
but then when i move my hand from center to RIGHT, system understand is as DOWN,
when i move my hand left, system respond as UP etc...
do you enabled touchscreen (swap xy etc)
we also need to map some onboard buttons to act as menu, escape/backspace etc...
how to learn scancode of those buttons...
after we learn scancodes...
setkeycodes SCANCODE KEYCODE
we can map these buttons for navigation buttons...
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
Stefan
Stefan
Stefan
When I go to keyboard settings or when I'm in an input field, in the
notification bar there is a keyboard symbol and there comes an option
switch "use physical keyboard". Probably for a "proper" device tree
for your tab there should be an option that the device doesn't have a
physical keyboard.
Stefan
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/xLpULESrGQEJ.
On Jan 29, 9:05 pm, StefanS <andr...@stefanseidel.info> wrote:
>
> I think it's just that the kernel shuts down the graphics, and when the
> device resumes it does so at VT1 (always I think). The console isn't
> working because it's disabled in init.rc (one line reads stop console).
> I just think the device goes to sleep again after wakeup that the graphics
> doesn't have a chance to come up - at least it's like that for me.
The device goes to sleep again because android doesn't know its
waken up.
This can be fixed by writing a POWER key on resume.
The real key is eaten by the ACPI.
I did a dirty fix in powerbtnd, to emulate a power key.
The device will wake, but still on vt1.
Rene
2012/2/2 aae_nsk <eisenb...@gmail.com>:
> Yes, maybe because low res 800x480, but there are sufficient space at
> screen bottom for onscreen controls, or at the top edge (where the
> status bar located and always on top)...
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Google determines ICS UI according to
resolution and dpi. That's not defined by us.
I think from the viewpoint of Google, 800x480
is a phone resolution.
> I saw dpi variable in:
> android-x86-ibm-thinkpad-x41t / system.prop
> # system.prop for x41t
> ro.sf.lcd_density=160
> Is it right place?
Yes, you can change it, or set DPI=120 in cmdline.
Stefan
the same functionality would be appreciated for the eeepc t101mt and
t91. This pages may be useful:
- https://help.ubuntu.com/community/T101MT
- http://www.maxerist.net/main/soft-for-win/tabletgohome
-- Duarte
2012/2/8 Marek Wojtaszek <woo...@gmail.com>:
> How to enable screen bezel buttons in x61t? Accelerometer does not
> work in my x61t so I would like change screen orientation with proper
> button.
>
> Accelerometer does not
> work in my x61t
You mean your hardware is broken? Or just you don't have the
libsensors in your build?
> so I would like change screen orientation with proper
> button.
Use the kdbsensor libsensors, it uses keyboard shortcuts for rotation.
Stefan
> How to enable screen bezel buttons in x61t?
See my init.thinkpad_x41t.rc for an example (setkeycode). The dmesg will print the keycode in plain txt if you press the button.
> Accelerometer does not work in my x61t
You mean your hardware is broken? Or just you don't have the libsensors in your build?
> so I would like change screen orientation with proper button.
Use the kdbsensor libsensors, it uses keyboard shortcuts for rotation.
You have two option:
a) find someone who is willing+able to do it
b) read and learn and do it yourself, and contribute it back ;)
Unfortunately, that's the way it works for "users". Either you live
with what you get, or you become a "developer" :) (It's not that
hard.)
Stefan
There's a more recent version available, try this.
Stefan
Stefan
As there is no grub in the Android image, does anyone know an easy way
to edit the missing /boot/grub/menu.lst?
Next problem: audio not working