--
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/-/0WR5j5dfH0YJ.
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.
as I wrote, this build contains all standard drivers. Did you try
adding a wireless network (doesn't need to exist) or switching it on
and off again?
Otherwise, Broadcom 54g is pretty generic, so you would at least need
to boot a recent linux (e.g. ubuntu) and check if the wifi works there
and what the name of the kernel module is.
Stefan
Ok, I see. I wasn't considering b43 as a useful driver, and it needs proprietary firmware, too. But I included it and will update the build sometime soon.
Thanks for reporting it!
Stefan
I think you need to contact Swype or ask in their forum for this issue. Maybe they send you a special version for testing.
Stefan
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/-/vjRvr_vY-IoJ.
Yes.
--
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/-/84aFKnS_nz8J.
Immediately after Android has started, open the Terminal Emulator, type
logwrapper dmesg
and press Enter and then type
logwrapper lspci
and press Enter. Then you open the "CatLog" application and in the menu there is an option to send the log (as attachment please) via Gmail or other options.
You can also try
modprobe wacom
in the Terminal and see if your touchscreen works then.
Stefan
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
On Mar 8, 2012 12:18 AM, "galu" <gal...@gmail.com> wrote:
>
> Radeon (RV100) on X32: it doesn't work (works the same as before - VESA framebuffer @800x600). All I know is that the card card is not supported by the "ATIRadeon" driver, only by "radeon" driver (ThinkWiki has some information on using this gpu under Linux).
I know, the RV100 is mentioned in the "radeon" mesa driver. But afaik there are some changes needed for Android. But I am not an expert in this area.
>
> Is there a way to force 1024x768 mode (framebuffer)?
I would have thought that "video=1024x768" on the kernel cmdline should do that, but apparently not.
Check the log (CatLog application) if you want to find out more (video is initialized at the very beginning).
Stefan
>
> Michael.
>
> On Wednesday, March 7, 2012 9:59:45 AM UTC+1, StefanS wrote:
>>
>> Hmm, I have enabled the radeon (rv100) mesa part, but I don't think it'll work. You can test it.
>
> --
> 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/-/6xdXKU6sL2wJ.
I would have thought that "video=1024x768" on the kernel cmdline should do that, but apparently not.
Check the log (CatLog application) if you want to find out more (video is initialized at the very beginning).
Stefan
Wifi on the x220 seems to work, although you may need to add a network
manually (doesn't have to exist) before it will show available
networks.
As for the torrent: you probably don't have a torrent client which
does trackerless torrents, so I would recommend you try Deluge or
µTorrent as they work well for me.
Stefan
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
Then, you need to check /sys/devices/platform/hdaps/position to see if
it outputs anything useful.
Stefan
Stefan
>> To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com.
Dear Stefan,I hope you are still engaged in the Universal images,I have a Lenovo X200 Tablet and already tested your builds, they run fine :) only problem is the Touchscreen/Wacom Pen.I already verified that the serial device works and outputs raw data for the panel on use. I also came across the wacom-input driver which "kinda" works.After enabling the touch screen traces, I can sometimes see that when I touch the screen with the Pen. but nothing really useful, only a single point is recognized, no lines.I know there are utilities for calibrating the touchscreen, but not included in the build and I don't know if its the solution so I didn't try to mix the images.If there is anything I can do, i'm glad to help (i'm familiar with c++ and linux ( compiling, gentoo etc )), but I hornestly don't know where to start ( also I hope the work can be avoided ).Best regards,Paul
Dear group,
I have created a new image not only for my beloved X41t, but i should also work on the X61t and maybe the x220t (WiFi doesn't seem to work on this).
It features the hdaps module from tp_smapi, so auto-rotation and tilt sensors games should work on the X61t now, too.
The image contains drivers for most components, so if your wifi/graphics/bluetooth/whatever doesn't work it's likely that it will not be so easy to get it to work.
Pinyin IME is also included, battery status is reported correctly always, etc. Full changelog will follow after some sleep :)
Magnet link: magnet:?xt=urn:btih:ab537845a97e9ddc0a24ab1093f4db6847764e9a
and the torrent file is attached as usual.
Looking forward for feedback :)
Stefan
Pen touch is sketchy. Works sometimes, others not.
Finger touch is not working (no pressure/resistive sensitivity)
Tablet's buttons are off
screen rotate goes to home screen
print activates the apps menu
escape is ok (I just lost my last edit :))
rocker button changes volume
Haven't tried the fingerprint scanner (no apps yet. hmm the Atrix has a fingerprint scanner
No orientation based screen rotate.
I was wondering however what approach was used for the wacom drivers?
From what I can tell so far there is no X on this droid and all documentation on linux wacom drivers indicates an x driver part. Also I don't see a udev anywhere (some other udev like system in place on android?). Could you share a little on what you did in this regard? And if you have any tips for fully configuring the tablet please let me know.