[This thread is for support on getting hardware acceleration working on your brand new Linux installation on your Transformer. While not directly related to development, most of the "Linux on TF101" threads are in the TF101 development forum, so it makes sense that a help thread is here. If it should be in another forum, please move it.]
Update 2014-03-29!
-----------------------------------------------------------------------
Nvidia has updated the Ventana driver to 16.4 with some important fixes for us! Here's what I've noticed thus far:
You can now boot Linux on your Transformer without having to undock the keyboard! No more errors spamming the console, preventing normal boot. Woohoo!
Despite @jrohwer's claims of getting 300+ fps with es2gears, I was never able to get over about 61 with the Nvidia driver (with mesa, I would get about 30 fps). This new driver fixes that, and es2gears can now achieve these great rates out of es2gears.
kwin_gles is much more stable
I've updated this thread for the new driver and also included updates/fixes based on @jrohwer's comments and my own experiences since I posted the original thread.
----------------------------------------------------------------------
You're tired of Android on your TF101 and you decide you want a real OS. This thread is for support on getting hardware acceleration working with your favorite Linux distro.
I don't have all the answers but I do have video playback working on Debian unstable using the nvgstplayer app.
This post will be updated with better, more specific instructions as the process is honed.
Here's how (I think) I did it and what's required. Obviously, you need an already working Linux installation on your TF101, with a graphical interface of some sort working (LXDE, XFCE, Gnome, KDE, Enlightenment, whatever). If you've used one of the already existing images around, you may already have hardware acceleration.
Install the appropriate mesa packages.
libegl1-mesa
libegl1-mesa-drivers
libgl1-mesa-dri
libgl1-mesa-swx11
libglapi-mesa
libgles2-mesa
libosmesa6
mesa-utils-extra
Reboot (just to be sure you didn't break anything)
Download the latest Ventana driver package from here: https://developer.nvidia.com/linux-tegra-rel-16. You can find the download link under the "Additional Information" section.
Make a backup copy of your xorg.conf, as the installer will overwrite it:
Code:
cp /etc/X11/xorg.conf ~
Extract the package.
Code:
tar -xjf Tegra20_Linux_R16.4.0_armhf.tbz2
Figure out what ABI release you are using. On Debian, you can check like this (you are looking for xorg-video-abi-##) For current Debian stable, the ABI is 12. Note Debian testing/unstable are using ABI 15, which is not supported by the Nvidia driver.:
Code:
aptitude show xserver-xorg-core | grep abi
cd to the Tegra for Linux directory and run the install script:
Code:
cd Linux_for_Tegra
sudo ./apply_binaries.sh --root / --xabi ##
Patch the /etc/X11/xorg.conf with anything extra that's needed (check your backup)
Download the latest Ventana Codec Package from the same spot as the driver and get it installed:
Code:
tar -xjf Tegra20_Linux-codecs_R16.4.0_armhf.tbz2
tar -xjf restricted_codecs.tbz2
sudo cp lib/firmware/* /lib/firmware/
Ensure the linker reads the new Nvidia modules before the default mesa ones. You can follow @jrohwer's instructions in post #4 below. Alternatively, create a file in /etc/ld.so.conf.d/ called 000-nvidia.conf and put this in it:
Code:
/usr/lib
Reboot (so the linker picks up the new path...alternatively run ldconfig and restart X)
The mesa-utils-extra package has some utilities to test EGL. Try running the es2_info. You should see NVIDIA Tegra as the GL_RENDERER:
Code:
EGL_VERSION: 1.4
EGL_VENDOR: NVIDIA
EGL_EXTENSIONS:
, EGL_NV_system_time, EGL_KHR_config_attribs,
EGL_KHR_surfaceless_context, EGL_KHR_image, EGL_KHR_image_base,
EGL_KHR_image_pixmap, EGL_KHR_gl_texture_2D_image,
EGL_KHR_gl_texture_cubemap_image, EGL_KHR_gl_renderbuffer_image,
EGL_ANDROID_blob_cache, EGL_KHR_vg_parent_image, EGL_NV_perfmon,
EGL_KHR_lock_surface, EGL_KHR_fence_sync, EGL_NV_sync,
EGL_NV_depth_nonlinear, EGL_NV_post_sub_buffer,
EGL_NV_post_convert_rounding, EGL_NV_native_query, EGL_KHR_stream,
EGL_KHR_stream_fifo, EGL_KHR_stream_producer_eglsurface,
EGL_KHR_stream_consumer_gltexture, EGL_KHR_stream_cross_process_fd,
EGL_EXT_create_context_robustness, EGL_IMG_context_priority,
EGL_NV_3dvision_surface, EGL_KHR_reusable_sync, EGL_NV_stream_sync,
EGL_NV_coverage_sample, EGL_NV_coverage_sample_resolve
EGL_CLIENT_APIS: OpenGL_ES2 OpenGL_ES OpenGL OpenVG
GL_VERSION: OpenGL ES 2.0 14.01002
GL_RENDERER: NVIDIA Tegra
GL_EXTENSIONS:
GL_OES_rgb8_rgba8, GL_OES_EGL_sync, GL_OES_surfaceless_context,
GL_OES_fbo_render_mipmap, GL_NV_depth_nonlinear, GL_NV_draw_path,
GL_NV_texture_npot_2D_mipmap, GL_OES_EGL_image, GL_OES_EGL_image_external,
GL_OES_vertex_half_float, GL_OES_mapbuffer, GL_NV_draw_buffers,
GL_NV_multiview_draw_buffers, GL_EXT_Cg_shader, GL_EXT_packed_float,
GL_OES_texture_half_float, GL_EXT_texture_array,
GL_OES_compressed_ETC1_RGB8_texture, GL_EXT_texture_compression_latc,
GL_NV_texture_compression_latc, GL_EXT_texture_compression_dxt1,
GL_EXT_texture_compression_s3tc, GL_NV_texture_compression_s3tc,
GL_EXT_texture_filter_anisotropic, GL_NV_get_tex_image, GL_NV_read_buffer,
GL_NV_shader_framebuffer_fetch, GL_NV_copy_image,
GL_NV_fbo_color_attachments, GL_EXT_bgra, GL_EXT_texture_format_BGRA8888,
GL_EXT_unpack_subimage, GL_NV_pack_subimage,
GL_NV_texture_compression_s3tc_update, GL_NV_read_depth,
GL_NV_read_stencil, GL_NV_uniform_buffer_object, GL_NV_map_buffer_range,
GL_EXT_robustness, GL_OES_standard_derivatives,
GL_NV_EGL_stream_consumer_external, GL_EXT_separate_shader_objects,
GL_NV_copy_buffer, GL_NV_3dvision_settings, GL_EXT_debug_marker,
GL_EXT_debug_label, GL_EXT_texture_storage, GL_NV_pixel_buffer_object,
GL_NV_framebuffer_blit, GL_NV_explicit_attrib_location,
GL_NV_coverage_sample
Run es2gears. For me, it starts out at over 600+fps and drops as it runs a fair bit. But, as long as you're not getting like 30fps, you're good!
Give the Nvidia video player a try. It was installed by the installer you ran above:
Code:
nvgstplayer --uri <path to video file>
Try the Simpsons trailer 720p mp4 here (http://www.dvdloc8.com/clip.php?movieid=12167&clipid=1) and see how it works.
Questions and Answers (mostly questions right now!)
As mentioned above, I don't have all the answers. In fact, I have more questions than I do answers:
How can I get accelerated video playback working with other video players (totem, vlc, etc.)?
How to get 3d working? More specifically, fancy animations in Gnome Shell or KDE, etc.?
kwin_gles seems to work ok now.
According to a message from steveeJ in another thread (http://forum.xda-developers.com/showpost.php?p=44952355&postcount=117):
right now, the support for egl accelerated desktop environment is being in development by gnome using clutter with egl acceleration, and kde with egl acceleration in kwin. but nothing seems to be ready for production use.
Click to expand...
Click to collapse
In Debian, there is a clutter-1.0-tests package. Whenever I try to any of the tests, they just all segfault on me.
As well, with new Debian releases (current testing and stable), the X ABI is too new and not supported by the Nvidia driver, so you can't get newer releases of Gnome going.
es2_info says "GL_RENDERER: Software Rasterizer". Doesn't say anything about hardware acceleration, but I assume that's fine in this scenario? If your GL_RENDERER says Software Rasterizer, you don't have hardware acceleration.
Comments/questions/answers/suggestions/etc. welcome! Let's make hardware acceleration on Linux great!
Is there any way to have a linux installation with a bluetooth keyboard...and maybe a simple step-by-step guide for the installation process. Thank you.
klau7 said:
Is there any way to have a linux installation with a bluetooth keyboard...and maybe a simple step-by-step guide for the installation process. Thank you.
Click to expand...
Click to collapse
Hey klau7.
I don't use any bluetooth devices so can't really help with that request, unfortunately.
Sent from my Nexus 4 using xda app-developers app
TravellingGuy said:
[*]The mesa-utils-extra package has some utilities to test EGL. Try running the es2_info and see what you get. I think you should get some indication that EGL is there. Here is what I currently see:
Code:
EGL_VERSION: 1.4 (DRI2)
EGL_VENDOR: Mesa Project
EGL_EXTENSIONS:
EGL_KHR_surfaceless_context
EGL_CLIENT_APIS: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3
GL_VERSION: OpenGL ES 2.0 Mesa 9.1.6
GL_RENDERER: Software Rasterizer
GL_EXTENSIONS:
GL_EXT_blend_minmax, GL_EXT_multi_draw_arrays,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_format_BGRA8888,
GL_OES_depth24, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,
GL_OES_mapbuffer, GL_OES_rgb8_rgba8, GL_OES_standard_derivatives,
GL_OES_stencil8, GL_OES_texture_3D, GL_OES_texture_npot,
GL_OES_depth_texture, GL_OES_packed_depth_stencil,
GL_EXT_texture_type_2_10_10_10_REV, GL_OES_get_program_binary,
GL_APPLE_texture_max_level, GL_EXT_read_format_bgra,
GL_NV_fbo_color_attachments, GL_OES_vertex_array_object,
GL_EXT_texture_rg, GL_EXT_unpack_subimage, GL_NV_draw_buffers,
GL_NV_read_buffer, GL_EXT_map_buffer_range
Click to expand...
Click to collapse
Looking by the above, you definitely do not have hw acceleration working, but software rasterisation by mesa (see the line GL_RENDERER above. When I run es2_info, I get:
Code:
EGL_VERSION = 1.4
EGL_VENDOR = NVIDIA
EGL_EXTENSIONS = EGL_NV_system_time EGL_KHR_config_attribs EGL_KHR_surfaceless_context EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_ANDROID_blob_cache EGL_KHR_vg_parent_image EGL_NV_perfmon EGL_KHR_lock_surface EGL_KHR_fence_sync EGL_NV_sync EGL_NV_depth_nonlinear EGL_NV_post_sub_buffer EGL_NV_post_convert_rounding EGL_NV_native_query EGL_KHR_stream EGL_KHR_stream_fifo EGL_KHR_stream_producer_eglsurface EGL_KHR_stream_consumer_gltexture EGL_KHR_stream_cross_process_fd EGL_EXT_create_context_robustness EGL_IMG_context_priority EGL_NV_3dvision_surface EGL_KHR_reusable_sync EGL_NV_stream_sync EGL_NV_coverage_sample EGL_NV_coverage_sample_resolve
EGL_CLIENT_APIS = OpenGL_ES2 OpenGL_ES OpenGL OpenVG
GL_VERSION: OpenGL ES 2.0 14.01002
GL_RENDERER: NVIDIA Tegra
GL_EXTENSIONS:
GL_OES_rgb8_rgba8, GL_OES_EGL_sync, GL_OES_surfaceless_context,
GL_OES_fbo_render_mipmap, GL_NV_depth_nonlinear, GL_NV_draw_path,
GL_NV_texture_npot_2D_mipmap, GL_OES_EGL_image, GL_OES_EGL_image_external,
GL_OES_vertex_half_float, GL_OES_mapbuffer, GL_NV_draw_buffers,
GL_NV_multiview_draw_buffers, GL_EXT_Cg_shader, GL_EXT_packed_float,
GL_OES_texture_half_float, GL_EXT_texture_array,
GL_OES_compressed_ETC1_RGB8_texture, GL_EXT_texture_compression_latc,
GL_NV_texture_compression_latc, GL_EXT_texture_compression_dxt1,
GL_EXT_texture_compression_s3tc, GL_NV_texture_compression_s3tc,
GL_EXT_texture_filter_anisotropic, GL_NV_get_tex_image, GL_NV_read_buffer,
GL_NV_shader_framebuffer_fetch, GL_NV_copy_image,
GL_NV_fbo_color_attachments, GL_EXT_bgra, GL_EXT_texture_format_BGRA8888,
GL_EXT_unpack_subimage, GL_NV_pack_subimage,
GL_NV_texture_compression_s3tc_update, GL_NV_read_depth,
GL_NV_read_stencil, GL_NV_uniform_buffer_object, GL_NV_map_buffer_range,
GL_EXT_robustness, GL_OES_standard_derivatives,
GL_NV_EGL_stream_consumer_external, GL_EXT_separate_shader_objects,
GL_NV_copy_buffer, GL_NV_3dvision_settings, GL_EXT_debug_marker,
GL_EXT_debug_label, GL_EXT_texture_storage, GL_NV_pixel_buffer_object,
GL_NV_framebuffer_blit, GL_NV_explicit_attrib_location,
GL_NV_coverage_sample
Note amongs others that GL_RENDERER is NVIDIA Tegra.
The issue is that both mesa and the NVIDIA Tegra drivers provide the libs libEGL.so, libGLESv1_CM.so, and libGLESv2.so. If you install both the mesa drivers and the Nvidia ones, then only one of these gets found, this depens on the how ld-config is set up.So in your case obviously the mesa lib gets found first and not the Nvidia ones.
Possible fixes (try individually or all)
Remove the mesa egl and gles drivers.
In /usr/lib, do (as root)
Code:
ln -s libEGL.so.1 libEGL.so
ln -s libGLESv1_CM.so.1 libGLESv1_CM.so
ln -s libGLESv2.so.1 libGLESv2.so
cd arm-linux-gnueabihf
ln -s ../libEGL.so
ln -s ../libGLESv1_CM.so
ln -s ../libGLESv2.so
ldconfig
Restart X.
Run es2_info again to confirm. (The fact that xorg.log shows the nvidia tegra driver loaded does not mean that the nvidia GLES libs are actually called).
You can test the performance with es2gears (also part of mesa-utils-extra). With the mesa driver, I get about 55 FPS, with the nvidia driver I get around 320 FPS
BTW Ubuntu has packaged the Nvidia drivers as nvidia-tegra (in Ubuntu raring this is only the tegra 16.2 driver but it works fine nevertheless. I use it as it sets up everything correctly, and figures out the gles and egl libs with update-alternatives, so the right libs get called. Dunno if Debian packages nvidia-tegra as well.
Questions and Answers (mostly questions right now!)
As mentioned above, I don't have all the answers. In fact, I have more questions than I do answers:
How can I get accelerated video playback working with other video players (totem, vlc, etc.)?
How to get 3d working? More specifically, fancy animations in Gnome Shell or KDE, etc.?
According to a message from steveeJ in another thread (http://forum.xda-developers.com/showpost.php?p=44952355&postcount=117):
In Debian, there is a clutter-1.0-tests package. Whenever I try to any of the tests, they just all segfault on me.
es2_info says "GL_RENDERER: Software Rasterizer". Doesn't say anything about hardware acceleration, but I assume that's fine in this scenario?
Click to expand...
Click to collapse
The segfault may well be due to the fact that you are calling the mesa libs, not the nvidia ones. For KDE, you can run kwin_gles as I explained in my reply on the rootbind thread.
Let us know your progress
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
klau7 said:
Is there any way to have a linux installation with a bluetooth keyboard...and maybe a simple step-by-step guide for the installation process. Thank you.
Click to expand...
Click to collapse
I haven't tried but I use a bluetooth mouse without problems on my linux installation (Ubuntu raring). I see no reason why the bt keyboard should not work.
jrohwer said:
Looking by the above, you definitely do not have hw acceleration working, but software rasterisation by mesa (see the line GL_RENDERER above. When I run es2_info, I get:
Code:
<snip>
GL_RENDERER: NVIDIA Tegra
<snip>
Note amongs others that GL_RENDERER is NVIDIA Tegra.
The issue is that both mesa and the NVIDIA Tegra drivers provide the libs libEGL.so, libGLESv1_CM.so, and libGLESv2.so. If you install both the mesa drivers and the Nvidia ones, then only one of these gets found, this depens on the how ld-config is set up.So in your case obviously the mesa lib gets found first and not the Nvidia ones.
Possible fixes (try individually or all)
Remove the mesa egl and gles drivers.
In /usr/lib, do (as root)
Code:
ln -s libEGL.so.1 libEGL.so
ln -s libGLESv1_CM.so.1 libGLESv1_CM.so
ln -s libGLESv2.so.1 libGLESv2.so
cd arm-linux-gnueabihf
ln -s ../libEGL.so
ln -s ../libGLESv1_CM.so
ln -s ../libGLESv2.so
ldconfig
Restart X.
Run es2_info again to confirm. (The fact that xorg.log shows the nvidia tegra driver loaded does not mean that the nvidia GLES libs are actually called).
You can test the performance with es2gears (also part of mesa-utils-extra). With the mesa driver, I get about 55 FPS, with the nvidia driver I get around 320 FPS
BTW Ubuntu has packaged the Nvidia drivers as nvidia-tegra (in Ubuntu raring this is only the tegra 16.2 driver but it works fine nevertheless. I use it as it sets up everything correctly, and figures out the gles and egl libs with update-alternatives, so the right libs get called. Dunno if Debian packages nvidia-tegra as well.
The segfault may well be due to the fact that you are calling the mesa libs, not the nvidia ones. For KDE, you can run kwin_gles as I explained in my reply on the rootbind thread.
Let us know your progress
Click to expand...
Click to collapse
Getting closer! As soon as you mentioned the libraries being provided by mesa and the NVidia package, I had a doh! moment. es2_info is now showing the same as you, along with GL_RENDERER showing NVIDIA Tegra.
However, I'm now suffering this error when running es2_gears over and over again to stderr and only getting around 40-60fps
Code:
Couldn't open /sys/bus/nvhost/devices/host1x/syncpt/22/max
Sounds like I'm not the only one with this problem. http://forum.xda-developers.com/showthread.php?p=35545164#post35545164
The clutter test applications no longer segfault either, but do also throw the above error.
Unfortunately, Debian does not have packaged Tegra drivers (although I did see a request to package them a couple of years ago). I tried the Ubuntu package, but seems Ubuntu is at a higher ABI than Debian Sid at the moment, so it didn't "just work".
I'm going to try using some previous releases of the Tegra drivers or maybe unpack the Ubuntu package and manually put the files in place and see what happens, unless you have extra words of wisdom, jrohwer.
Thanks for your help, I'm hoping my trials and tribulations will also help out others.
TravellingGuy said:
Getting closer! As soon as you mentioned the libraries being provided by mesa and the NVidia package, I had a doh! moment. es2_info is now showing the same as you, along with GL_RENDERER showing NVIDIA Tegra.
However, I'm now suffering this error when running es2_gears over and over again to stderr and only getting around 40-60fps
Code:
Couldn't open /sys/bus/nvhost/devices/host1x/syncpt/22/max
Sounds like I'm not the only one with this problem. http://forum.xda-developers.com/showthread.php?p=35545164#post35545164
The clutter test applications no longer segfault either, but do also throw the above error.
Unfortunately, Debian does not have packaged Tegra drivers (although I did see a request to package them a couple of years ago). I tried the Ubuntu package, but seems Ubuntu is at a higher ABI than Debian Sid at the moment, so it didn't "just work".
I'm going to try using some previous releases of the Tegra drivers or maybe unpack the Ubuntu package and manually put the files in place and see what happens, unless you have extra words of wisdom, jrohwer.
Thanks for your help, I'm hoping my trials and tribulations will also help out others.
Click to expand...
Click to collapse
Yes, I'm getting the same /sys/bus/... error as you and others, seems to be a problem with Jhinta's kernel. Unfortunately I don't have any C programming skills so can't investigate this further. However, when you pipe stderr to /dev/null (es2gears 2>/dev/null) you will get around 300 FPS. So it seems to "work" even though you get this error. kwin_gles also "works". This is also the state I'm at so have no additional suggestions.
Incidentially the kernel posted by sni on the Jhinta kernel thread:
http://forum.xda-developers.com/showpost.php?p=43203818&postcount=569
actually works and has this fixed. The only issue I have with that kernel is that it is not overclocked so it is slow. But all the other things (USB, framebuffer, nvidia hw accell) are fixed! I tried to patch the overclock code into Sni's sources and while the kernel compiles without error, it won't boot. As mentioned I don't know C so can't really debug this. So for me it's the choice of having a half working but fast kernel (my own) versus a fully working slow one, and I chose the earlier option since I use my tab as my main computer when travelling and need it to be fast. I can live with the half working stuff as it is not a show stopper for me. Ultimately however, it would be really cool to have the overclocking code working in Sni's kernel, then we would have a really "perfect" solution for Ubuntu on the tf101....
jrohwer said:
Yes, I'm getting the same /sys/bus/... error as you and others, seems to be a problem with Jhinta's kernel. Unfortunately I don't have any C programming skills so can't investigate this further. However, when you pipe stderr to /dev/null (es2gears 2>/dev/null) you will get around 300 FPS. So it seems to "work" even though you get this error. kwin_gles also "works". This is also the state I'm at so have no additional suggestions.
Click to expand...
Click to collapse
Interesting, as I did redirect stderr to /dev/null as well, but I still only get around 60fps, not the 300 that you and the the other thread mention.
Makes me think that I still don't have hardware acceleration, despite es2info suggestion otherwise.
jrohwer said:
Incidentially the kernel posted by sni on the Jhinta kernel thread:
http://forum.xda-developers.com/showpost.php?p=43203818&postcount=569
actually works and has this fixed. The only issue I have with that kernel is that it is not overclocked so it is slow. But all the other things (USB, framebuffer, nvidia hw accell) are fixed! I tried to patch the overclock code into Sni's sources and while the kernel compiles without error, it won't boot. As mentioned I don't know C so can't really debug this. So for me it's the choice of having a half working but fast kernel (my own) versus a fully working slow one, and I chose the earlier option since I use my tab as my main computer when travelling and need it to be fast. I can live with the half working stuff as it is not a show stopper for me. Ultimately however, it would be really cool to have the overclocking code working in Sni's kernel, then we would have a really "perfect" solution for Ubuntu on the tf101....
Click to expand...
Click to collapse
Good luck! Love to see an updated kernel with everything fixed up.
I'm heading trip soon, so probably won't be around the forum until mid-September.
Do you his think it is possible to get the "special effects" in kwin working? I installed the tegra drivers and switched from xfwm4 to kwin_gles but for now the effects like wobbly windows don't work
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
Do you his think it is possible to get the "special effects" in kwin working? I installed the tegra drivers and switched from xfwm4 to kwin_gles but for now the effects like wobbly windows don't work
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yes I have them working. I don't know about wobbly windows, don't like them But the desktop cube for switching desktops works for sure for me, and other window effects as well.
Are you sure the tegra drivers are loaded (what does es2_info show, NVIDIA Tegra or mesa? it must be the former).
In KDE systemsettings, Desktop Effects, click "enable desktop effects at startup". In the advanced type change compositing type to OpenGL, and rendering to "native" (something like that, writing from memory here).
I cant get nvidia opengl working in Lubunutu raring :\
jrohwer said:
Yes I have them working. I don't know about wobbly windows, don't like them But the desktop cube for switching desktops works for sure for me, and other window effects as well.
Are you sure the tegra drivers are loaded (what does es2_info show, NVIDIA Tegra or mesa? it must be the former).
In KDE systemsettings, Desktop Effects, click "enable desktop effects at startup". In the advanced type change compositing type to OpenGL, and rendering to "native" (something like that, writing from memory here).
Click to expand...
Click to collapse
You use xfce right, how do you start kwin on boot
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
You use xfce right, how do you start kwin on boot
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
No I don't run xfce, I run KDE! I have installed kubuntu-desktop and kubuntu-low-fat-settings (to disable the semantic desktop and akonadi stuff). The speed is quite acceptable. I am not sure whether kwin (window manager) will work with xfce (desktop environment) - have never tried.
I have installed kdm and this starts on boot, and then boots the KDE session. But I suppose lightdm could work as well, just I prefer KDM.
jrohwer said:
No I don't run xfce, I run KDE! I have installed kubuntu-desktop and kubuntu-low-fat-settings (to disable the semantic desktop and akonadi stuff). The speed is quite acceptable. I am not sure whether kwin (window manager) will work with xfce (desktop environment) - have never tried.
I have installed kdm and this starts on boot, and then boots the KDE session. But I suppose lightdm could work as well, just I prefer KDM.
Click to expand...
Click to collapse
I know kwin works with xfce because I looked it up on YouTube but I don't know how to start kwin on boot. I can start kwin by doing a "kwin --replace" but it seems like I don't have HW composing because effects aren't working and when I tried on full KDE they didn't either ( I only install the nvidia-tegra package )
Sent from my SCH-I535 using Tapatalk 4
jrohwer said:
Yes I have them working. I don't know about wobbly windows, don't like them But the desktop cube for switching desktops works for sure for me, and other window effects as well.
Are you sure the tegra drivers are loaded (what does es2_info show, NVIDIA Tegra or mesa? it must be the former).
In KDE systemsettings, Desktop Effects, click "enable desktop effects at startup". In the advanced type change compositing type to OpenGL, and rendering to "native" (something like that, writing from memory here).
Click to expand...
Click to collapse
Is there a way for you to give me your settings, I have the nvidia installed up and running but opengl settings in kde wont work even if I switch to kwin_gles ( yes I switched to kde)
Can some one help me get nvidia opengl up and running in Lubunut raring?
I already installed nvida drivers provided by OP, but doesnt seems to get booted. Also i change ldconfig.
So im kinda lost.
vietchinh said:
Can some one help me get nvidia opengl up and running in Lubunut raring?
I already installed nvida drivers provided by OP, but doesnt seems to get booted. Also i change ldconfig.
So im kinda lost.
Click to expand...
Click to collapse
Does es2_info show that you are actually using the nvidia drivers? Refer to this post:
http://forum.xda-developers.com/showpost.php?p=45011655&postcount=4
jrohwer said:
Does es2_info show that you are actually using the nvidia drivers? Refer to this post:
http://forum.xda-developers.com/showpost.php?p=45011655&postcount=4
Click to expand...
Click to collapse
Uhm no:
libEGL warning: GLX/DRI2 is not supported
libEGL warning: DRI2: failed to authenticate
EGL_VERSION = 1.4 (DRI2)
EGL_VENDOR = Mesa Project
EGL_EXTENSIONS = EGL_KHR_surfaceless_context
EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3
GL_VERSION: OpenGL ES 2.0 Mesa 9.1.3
GL_RENDERER: Software Rasterizer
GL_EXTENSIONS:
GL_EXT_blend_minmax, GL_EXT_multi_draw_arrays,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_compression_dxt1,
GL_EXT_texture_format_BGRA8888, GL_OES_depth24, GL_OES_element_index_uint,
GL_OES_fbo_render_mipmap, GL_OES_mapbuffer, GL_OES_rgb8_rgba8,
GL_OES_standard_derivatives, GL_OES_stencil8, GL_OES_texture_3D,
GL_OES_texture_npot, GL_OES_depth_texture, GL_OES_packed_depth_stencil,
GL_EXT_texture_type_2_10_10_10_REV, GL_OES_get_program_binary,
GL_APPLE_texture_max_level, GL_EXT_read_format_bgra,
GL_NV_fbo_color_attachments, GL_OES_vertex_array_object,
GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5,
GL_EXT_texture_rg, GL_EXT_unpack_subimage, GL_NV_draw_buffers,
GL_NV_read_buffer, GL_EXT_map_buffer_range
I tried method (2.), but i dont know how to execute method 1. ,because im a huge noob in linux. Only scratching the surface.
After using apt-get install nvidia-tegra. I get:
[email protected]:~$ es2_info
****nvrm_init failed****
Error: Can't open /dev/nvhost-ctrl
Opening channel failed 7
Error: eglGetDisplay() failed
zachf714 said:
Is there a way for you to give me your settings, I have the nvidia installed up and running but opengl settings in kde wont work even if I switch to kwin_gles ( yes I switched to kde)
Click to expand...
Click to collapse
See attached screenshots from systemsettings. If it at first gives an error message when clicking "Enable desktop effects at startup", make sure the option is clicked, apply, exit system settings, log outof X, restart X-server (alt-X in KDM) and log in again, and it should work (at least it does for me).
jrohwer said:
See attached screenshots from systemsettings. If it at first gives an error message when clicking "Enable desktop effects at startup", make sure the option is clicked, apply, exit system settings, log outof X, restart X-server (alt-X in KDM) and log in again, and it should work (at least it does for me).
Click to expand...
Click to collapse
My desktop effects just don't work, I can enable but they don't work
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
My desktop effects just don't work, I can enable but they don't work
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
That's weird And es2_info shows that NVIDIA tegra is used for rendering? Have you tried running
Code:
ps -ef |grep kwin
in a terminal to actually verify that kwin_gles is running?
Related
Hi,
I followed this thread Chroot Ubuntu and installed ubuntu
As other guys, some application won't launch or crash under gnome
On the OP, people talk about memory limit of 32M per app on android, but for example the system monitor is a small app that consumes less than 4M and it won't launch...
Unfortunately, i cannot post on the OP (too few posts for me, cannot post on dev section), so i give what i found here (maybe a gentle admin will move the thread )
So
I installed lxde from terminal, and switched to lxde :
# apt-get install lxde
# update-alternatives --config x-session-manager
(i chose "start lxde")
Click to expand...
Click to collapse
reboot the TF, restart chroot ubuntu, vncserver, then connect, i got the lxde x env, and guess what ?
system monitor works, update manager, synaptic package manager, etc...
Don't know if it's because it's a lighter interface, but it does the trick !
@+
Some things still don't seem to load properly even on lxde , such as chromium, but it seems to be an improvement.
Probably should check for issues involving shared memory and X extensions. Remember, it is not quite the current X.Org you're running.
Sent from my Transformer TF101 using Tapatalk
Thanks for that trick!, but I can run more than 4-5 apps in chroot Ubuntu (not at the same time). I open Firefox, close it, open OpenOffice Writer, close it, open Gedit, close it, open LXTerminal and closeit. After doing this, I'm unable to start other app
tisi1988 said:
Thanks for that trick!, but I can run more than 4-5 apps in chroot Ubuntu (not at the same time). I open Firefox, close it, open OpenOffice Writer, close it, open Gedit, close it, open LXTerminal and closeit. After doing this, I'm unable to start other app
Click to expand...
Click to collapse
That's pretty strange, i made a few tests on mine
I can run at the same time Firefox, LXterminal, Gedit, Synaptic package manager, system monitor, movie player...
Close them, reopen Firefox etc
But Zoho web applis don't start at all for example.
Spidey01 said:
Probably should check for issues involving shared memory and X extensions. Remember, it is not quite the current X.Org you're running.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info
I wonder if we can run another distro, ubuntu 11.10 for example, via chroot ?
I noticed that the swap is disabled in the kernel used in the root.fs image, which could maybe help the memory management
Depending on how much work you want to do you can run any distro that supports the processor architecture. I use Debian stable because it seems to have a lot more debs available than Ubuntu, when you have ARM instead of x86 crud .
From talk I believe Ubuntu will eventually be a great choice, perhaps even as a total replacement or dual boot, but the TF101 may look like a G1 or original Droid by then.
Sent from my Transformer TF101 using Tapatalk
ID6548437 said:
That's pretty strange, i made a few tests on mine
I can run at the same time Firefox, LXterminal, Gedit, Synaptic package manager, system monitor, movie player...
Close them, reopen Firefox etc
But Zoho web applis don't start at all for example.
Click to expand...
Click to collapse
I was not so lucky. I can only run one app at a time as well. Maybe there's a difference in how we're set up?
Spidey01 said:
Depending on how much work you want to do you can run any distro that supports the processor architecture. I use Debian stable because it seems to have a lot more debs available than Ubuntu, when you have ARM instead of x86 crud .
From talk I believe Ubuntu will eventually be a great choice, perhaps even as a total replacement or dual boot, but the TF101 may look like a G1 or original Droid by then.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I just want to run p2p client to download tv series
Not a lot of stuff
I will take a look at Debian
Thanks
livinsacrfice said:
I was not so lucky. I can only run one app at a time as well. Maybe there's a difference in how we're set up?
Click to expand...
Click to collapse
I made very minor changes to the initial config, i just removed a few app from the menu "Preferences > Desktop session settings"
I just left :
Wicd network manager tray
SSH key agent
Certificate and key storage
Secret storage device
I unchecked all others
And that's all i did, i believe
But i run UltraVNC client from my win xp, what about you ?
oh, I was using the VNC client on the TF101. When I connected from a different machine, I was able to load multiple apps at a time.
Nvidia is pretty good about releasing drivers for their x86 graphics hardware. Have they not released drivers for the transformer geforce that we still have to use vnc servers instead of x.org?
Is there really no way to run x.org on the transformer? That would totally take away the need to use nvflash and deal with partitioning etc....
If we could just chroot and startx right from there and at the same time kill the apk stuff
INFORMATION
DEVICE
Craig CLP281 Android Netbook
Via Wondermedia 8650 based chipset / 800 mhz / wifi / 3 standard usb / ethernet!
PROS
Original firmware available
Original firmware unlocked
Unique form factor
Inexpensive
CONS
No obvious upgrade path
No sources posted
No officially supported flash player
Lower end hardware
HOWTO
unzip to sdcard
start device with sdcard plugged in
wait for everything to be wiped out
ROM
OVERVIEW
This is a modified version of the official firmware. The focus is on removal of bloatware and unneeded proprietary software.
INTEGRATED SOFTWARE
su
Superuser
Terminal Emulator
ConnectBot
Total Commander with ftp and lan plugins
Gapps
Zirco Browser
Yaxim Jabber Client
Jota Text Editor
DO IT YOURSELF
See the README to deduce how to modify the ROM yourself. The changes are documented thoroughly so that many people can use this release as a kitchen of sorts.
LINKS
R1
ROM: http://www.mediafire.com/?dsf11zm7jik9f63
SOURCE: http://www.mediafire.com/?8juzj5qb5jme1ud
ROM: http://dev-host.org/xcz68h384fe8/clp281_firmware2.2_HACK9_R1.zip
SOURCE: http://dev-host.org/ekni2eg4td3i/SOURCES_1.zip
R2
ROM: http://dev-host.org/gm3c1mrdeai3/clp281_firmware2.2_HACK10_R2.zip
ROM: http://www.mediafire.com/?4tpli2998g10to4
R3
ROM: http://dev-host.org/qyo428ewrgvl/clp281_firmware2.2_HACK11_R3.zip
SOURCE: http://dev-host.org/w8p6gotfisnb/SOURCES_2.zip
ROM: http://www.multiupload.com/V5MKGW7X5V
SOURCE: http://www.multiupload.com/KG7KJJKT8U
R4 (Latest)
ROM: http://dev-host.org/b1ufq9iixe9k/clp281_firmware2.2_HACK12_R4.zip
ROM: http://www.multiupload.com/IJWDECP8WF
chroot Repository
References:
http://forum.xda-developers.com/showthread.php?t=486247
http://forum.xda-developers.com/showthread.php?t=1172504
Please choose one of the following 2 methods!
USB Control Script (1st method):
DEBIAN_CONTROL - see bottom of post for script
MicroSD Control Script (2nd method):
DEBIAN_CONTROL_SD - see bottom of post for script
You will need this image unless you plan to put your own together.
Debian Squeeze Image:
http://www.multiupload.com/C9RDP4ODZX
The image can be flashed to your usb drive or sd/microsd card with dd on your fullsize computer. Please be aware that I have not tested running from a fullsize SD card.
dd if=~/nameofimage.img of=/dev/nameofdevice
Operation
1.Run the control script to start the chroot. You can run console commands here. The screen command is useful here also.
2.Run ./vnc to start the vnc server which itself starts xorg and the window manager. The script is not totally failure proof.
3.Login with your vnc client. I use Android vnc viewer. Password is testing.
http://code.google.com/p/android-vnc-viewer/
Window Managers
lxde
icewm
xfce
check /.vnc/ for the xstartup scripts. just rename the one for the window manager you want to xstartup and reboot your chroot.
BUG:
chroot will not cleanly unmount
SOLUTION:
keep chroot running in the background - it should only take up memory not cpu
Stock ROM Repository
Images contain stock system, stock boot, and CWM recovery.
vm670 recovery image is for the new screen version so it should work for all vm670.
LG vm670:
http://www.multiupload.com/LG1JCZ5CMD
Samsung i9023:
http://www.multiupload.com/KX1LIAASH3
Craig clp281:
http://www.multiupload.com/9XUQA7SEF1
Asus tf101:
http://www.multiupload.com/XMRO9AI4KC
Samsung p6210:
http://www.multiupload.com/L702W2MA7J
Can you add in support for the official android market, i would love to have this on here.
FAQ POST:
Does Flash work?
I am not holding out much hope for flash on ARMv6. It seems like a long complicating debugging process for what is in the end slow and buggy results.
The browser is slow?
Right now, it seems that javascript performance on the stock browser is much worse than I expected. For now, try turning off javascript and images if you use the stock browser.
Stock ROM?
The link for the device on Craig's website is:
http://www.craigelectronics.com/site/pdetails.php?id=314
You can download the completely stock ROM from here.
ADB?
I tried ADB with a male to male USB that I had laying around with no success with a GNU/Linux PC and a different Windows PC. All 3 USB ports were tested. But you can connect with adb connect ipofdevice over your LAN if you see what address your router is giving the device. Or of course you could set a static IP.
Minimize application?
You can return to the home screen at any time by pushing fn+home.
Sources for the binaries you have added?
Try the sources link on the first post. The zirco apk is unchanged and their website is here: http://code.google.com/p/zirco-browser/ . The Gapps are straight from my VM LG Optimus V.
Mount an ext2/3 formatted USB drive?
mount -t ext3 /dev/block/sda1 /mountpointofyourchoice
Enter key not working in some terminal applications?
Use Ctrl-m instead.
References:
https://github.com/jackpal/Android-Terminal-Emulator/issues/21
http://code.google.com/p/terminal-ide/issues/detail?id=6
Just wanted to thank you for taking this project on. This device could be much more and for the price you just can't go wrong. Good luck and I'm off to root.
Is it possible to boot or load a stripped version of windows xp from a thumb drive? and did you try all the usb ports with that cable?
wgallt:
The root situation on the ROM and my current devices in general is a little complicated. For this device in general, it comes ADB rooted out of the box. I have added another su to the rom that will allow console root. Unfortunately, because it is an older version of su, it does not seem to work with Superuser.apk. I am waiting on a response in the Q/A forum on errors I am getting compiling the current version of su. I have been able to compile Superuser.apk successfully but it is not much use without the current version of su. I am of course preferring to include source and source-compiled binaries wherever possible in the ROM.
celltimemb:
Market added.
See above for ADB info.
Regular Windows XP does not run natively on ARM CPUs. From Craig's website it appears that they have an identical model running Windows CE. You should look into any running a lightweight GNU/Linux chroot with QEMU or VMWare and then booting something like Windows 98. I would be amazed to see it, especially with the limited RAM we have available.
I am releasing a new ROM with integrated Google Apps and a open source browser named Zirco which seems to run very well. Compare the stock browser with stock settings to Zirco on forum.xda-developers.com to know what I mean. Be sure to read the README.
This ROM may end up becoming a different series entirely. One with the market and one without.
I have updated the first post with the links and README.
can u add live wallpaper support in a future rom?
If I get around to compiling AOSP that should come with live wallpaper.
I tried copying the live wallpaper apk and what I thought to be their dependencies from my Optimus V. Unfortunately, the switcher crashed and the logcat just said the wallpaper switcher would not start.
lot of apps run real slow and lag i tried some games like that bird game where you flick it to the target, i get like 1 frame every 2-3 seconds for the animation, soo slow, they claim 800 MHZ processor but damn this thing is soooo slow. even the fake chinese android phones the star A5000 runs and performs better than this.
2d games lag real bad so I dont see any 3d gaming at all on this machine. unless some elite hacker and coder can make a fully optimized rom for this thing.
Thanks for reporting your results. I have had mixed successes with games. The drag racing game works decent and another rice-can type racing game worked ok too. But many games instantly crash also. The live wallpaper would probably run slow anyway.
Web browsing
Remote administration
Network administration
Note taking
Light media playback
VOIP
Chat
These are all the uses I can think of it for the moment. It gives me an idea to include a note taking application at some point.
the new browser force closes on me, and does this thing have flash support, I have a gut feeling this is an x86 formfactor which is why it runs so slow.
Please read the README and in general read the previous posts carefully.
This is definitely not an x86. It if were, it would actually be faster.
One of these pages is the page for the CPU:
http://www.wondermedia.com.tw/en/products/platform/soc/wm8650/index.jsp
http://www.wondermedia.com.tw/en/products/platform/soc/wm8750/index.jsp
Lol on the craig website product page they show windows on it instead of android.
http://www.craigelectronics.com/site/pdetails.php?id=314
This thing can supposedly handle 3d gaming so i cant undertsand why most games including 2d games run so slow.
---------- Post added at 09:29 PM ---------- Previous post was at 08:57 PM ----------
Is it possible to put Windows CE 6 on this from the craig CLP280 model?
Merry Christmas!
After a productive night the R3 ROM is out.
The changelog and sofware list highlights:
removed zirco integration
init.rc changes to support zirco
holiday wallpaper
added OPTIONAL on localdisk with:
yaxim jabber client - open source
zirco browser - open source
jota text editor - open source
su - compiled from source
superuser - compiled from source
For security reasons, you should probably choose allow once instead of always for su.
As usual be sure to read the README.
Just got a Craig Netbook. I hate the Android stock install. I found this thread and it seems like the answer I'm looking for. If I understand you correctly, the description you give for the Rom"
"OVERVIEW
This is a modified version of the official firmware. The focus is on removal of bloatware and unneeded proprietary software."
is the first hack? (clp281_firmware2.2_HACK9_R1)
Also, if I do this and screw it up, can I reinstall the original Android from the Craig website?
Thanks.
Yes that is the first release. I would recommend trying the third as it is the latest version as of this post.
Yes you can reinstall the original firmware.
Thanks Jason.
Hey Jason. I just installed it. Had to download a new adobe flash player to watch a youtube video.
When it comes to this operating system I am a total newbie. So, in order to do a "do it yourself" install (since I still can't install some pre installed apps like "Dialer" and other things) are there simple instructions to do a "do it yourself" or do you have to be a techy to do it? I know Windows OS well but Android is so foreign to me. Just had this thing for a few days and I am ready to throw the netbook against the wall and then stomp on it. Your root was my last hope.
Well first off, were you able to actually play flash in the browser? That would be a nice new development. Alternatively, you could try the included Youtube player.
I would be glad to help in any way I can. For a do it yourself ROM, you would just take the factory firmware RAR file and edit it yourself. You would start by unRARing the file with something like WinRAR on Windows. But I would recommend trying GNU/Linux instead if you are at all interested in development. You can use the README file and this thread as a reference along the way.
Why are you interested in installing the dialer anyway? I noticed some phone components are installed but there seems to be no way to access them.
You're a doll Jason. Thanks for your willingness to help.
I didn't know about the Youtube player. Thanks for the tip. On the original install I was able to play flash in "Browser" (at Youtube at least) but not with "Browser" in this install. Although, maybe "Browser" opened "My Browser" in the original install and that's the one that had flash support. (I'm still learning). So since I didn't get around to installing your included browser maybe that's why it wouldn't play. Anyhow, I couldn't install the flash update via the link Youtube provided. The little download arrow on the top left hand of the screen just never went away. I had the unit on for about 3 hours and the arrow remained with no confirmation that the download was complete. I searched the system and the SD card for the download but couldn't find it. This is not the first time I had this problem with downloads so maybe it's something with my particular device. This is actually my third. Last two were defects.
About the Dialer... it was a typo. I meant to say I want to UNINSTALL it from the unit, but Android won't let me. It just seems useless to have this app since I have a netbook and not a phone. Plus, I think it may be eating up my battery usage as it could be the app responsible for the cell standby thing I have in Battery Usage which is using up 80% of my battery. Like I said, I am a newbie to this OS so, I'm looking at things like Dialer, Telophony etc. I may be wrong about this though. It may be some other application seeking Cell Radio signal as reported in Battery Usage.
I just did a side by side comparison of the unzipped install I got from Craigs website (by the way, thanks for that link) and your version to see if I could learn and do my own hack. I did notice a few differences.
Ok first I saw the Optional folder with some apps and Browser fix as you mentioned in the Read me
Then there was the app folder where you removed some apps from the original install and added others. Is it as simple as that? To just delete the apps you don't want from this folder of the original install? Unfortunately I don't see Dialer in that folder. I'd like to get rid of that too. I guess you can't get rid of every app.
Another difference was that I saw "su" in "bin". and I noticed SuperUser.apk in your app folder. Does that app make you the administrator of the device giving you access to system files to delete them if you want to? (I looked it up on WIKI) Cause maybe I can include that in my hack.
Also I see another difference in this folder:
\FirmwareInstall\packages\fs_patch\root_patch\system\lib
In your readme you said these are shared libraries but I don't have a clue what that means. Do I need these files?
Thanks again for taking the time with this. I would love to do my own hack. It would give me great satisfaction after the countless hours of stress trying to do stuff they won't let me do.
All the best,
Angie
*YO! New version can connect to a TV via HDMI. If you have a USB-host, you can also connect a keyboard and a mouse!*
Hi. I want to introduce you Wishnu. The essence of our project is the launch of computer OS Linux Debian inside an Android mobile device. Then this device connects to a computer by means of the USB-cable. Actually that allows transforming any Android device into a real computer. You can connect the phone to different computers at home, at work and on a visit and use the phone’s own screen and input equipment on the journey.
We have taken "running chrooted debian/ubuntu on android" idea as the base and created something interesting with it.
First, we have created Android application which starts Debian on android mobile device with one click (no need to type any commands in the terminal etc).
Second, we have written desktop client application which shows Debian desktop running on mobile phone on the PC or laptop with wide screen, mouse and keyboard, so this actually turns the solution to the docking station like Motorola Lapdock or devices such as Pocket Desktop, but much better, cause you don't need to buy additional docking station device and you will immediately receive tons of common desktop applications available from Debian MIPS/ARM repositories (even pdf document viewers, image editors, office with spreadsheets and presentations editors etc).
Also device SD card available inside chrooted system in /media/sharedSD dir.
Watch the video in action
And this one (sorry for the quality, I used my matreshka as a camera).
Screenshots
Currently Wishnu uses Debian 5.0 ARM image taken from this thread. We are planning to add more customized and fresh Debian and Ubuntu OS images.
System requirements
PC client
- OS Windows XP, Vista, 7 (x86) or Linux (x86, x64)
- Java Runtime Environment must be pre-installed.
- Device ADB driver on Windows (on linux no adb driver needed, but adb server should be started as root in most cases)
Android device
- MIPS or ARM
- Mobile processor 500 MHz, 256 mb RAM (Recommended: processor 1 GHz and >512 mb RAM)
- Android OS 1.5 or higher.
- The device must be rooted.
Download and install instructions
Or download on Android Market
This one is much easier to start with than existing LinuxInstaller - no need to type any commands in terminal or adb shell - just download image file and press start. Also desktop client is great idea.
Needs more options for system control though and also Ubuntu image for desktop instead of old debian.
yo, we need some response, please download our awesome application! or at least tell us why you won't do it (maybe Wishnu is useless or smb is better). Thank you!
How does it do with running heavier weight applications such as thunderbird?
agoodm said:
How does it do with running heavier weight applications such as thunderbird?
Click to expand...
Click to collapse
Actually it depends on your phone's performance. We use Sony Ericsson Xperia arc for testing and have no problems running such applications. You better try it and inform us about results)
Are you using the armel or armhf Debian distribution?
nicktastique said:
Are you using the armel or armhf Debian distribution?
Click to expand...
Click to collapse
Currently we have images of debian squeezy for armel and mipsel.
A bit busy with the holidays and all, but I will give it a look. I definitely recommend checking out armhf. I've been testing it on my Droid 3 and cursory benchmarks show it to be something like 850% faster than armel. armel is basically useless in comparison.
Debian's armhf Icweasel 9.0 was actually faster than the native Firefox Mobile 9.0 app on the SunSpider benchmark (by 80ms, but still).
Thanks for your work, looking forward to checking it out.
lokosokol said:
Currently we have images of debian squeezy for armel and mipsel.
Click to expand...
Click to collapse
Very interesting idea, and I'd love to give it a go. Unfortunately, it doesn't work for me. I get an error, "Can't connect to OS image".
The checks run okay, so everything appears to be okay.
I'm using a Samsung GS2, on 2.3.5 (stock ROM), so hardware and OS are more than adequate.
Edit: Okay, so it was the stock ROM that was the problem. I assume it doesn't support loop devices (whatever that actually means!) I've got a custom ROM on there now and it gets a lot further, but I still have an issue.
It gets to the "Starting System" stage and I get the error message "OS start failed (bad program identificator)".
So, any advice?
Thank you for your advice, guys!
nicktastique said:
A bit busy with the holidays and all, but I will give it a look. I definitely recommend checking out armhf. I've been testing it on my Droid 3 and cursory benchmarks show it to be something like 850% faster than armel. armel is basically useless in comparison.
Debian's armhf Icweasel 9.0 was actually faster than the native Firefox Mobile 9.0 app on the SunSpider benchmark (by 80ms, but still).
Thanks for your work, looking forward to checking it out.
Click to expand...
Click to collapse
Thank you very much for this hint — we are working on preparing better system images and will definitely give this option a try.
Archer said:
Very interesting idea, and I'd love to give it a go. Unfortunately, it doesn't work for me. I get an error, "Can't connect to OS image".
The checks run okay, so everything appears to be okay.
I'm using a Samsung GS2, on 2.3.5 (stock ROM), so hardware and OS are more than adequate.
Edit: Okay, so it was the stock ROM that was the problem. I assume it doesn't support loop devices (whatever that actually means!) I've got a custom ROM on there now and it gets a lot further, but I still have an issue.
It gets to the "Starting System" stage and I get the error message "OS start failed (bad program identificator)".
So, any advice?
Click to expand...
Click to collapse
Could you give us a log file of that failed launch? It should be in "/path_to_application_data/log" folder.
I tried it out and I get "Error:OS start failed (timeout expired)
Here is the log:
Code:
############Preparing Base System############
############Preparing Base System Check############
***Checking Ext2 exists/not exists***
true
***Checking system loop device file '/dev/block/wishnuloop' exists***
true
############Preparing Base System Check Finishes############
############Preparing Base System Ends############
############Mounting System Image############
############Mounting System Check############
**Checking /dev/block/wishnuloop mounted/not mounted**
#busybox losetup /dev/block/wishnuloop
/dev/block/wishnuloop: 0 /mnt/sdcard/wishnu/system.img
Return code: 0
**Check /data/data/edu.phystech.wishnu/system mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system
Return code: 0
############All Correct############
############Mounting System Image Ends############
############Preparing System############
############Preparing System Check############
**Check /data/data/edu.phystech.wishnu/system/dev/pts mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/dev/pts
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/proc mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/proc
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/sys mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/sys
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/media/sharedSD mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/media/sharedSD
Return code: 0
############All Correct############
############Preparing System Ends############
############Starting System############
############Starting System Check############
############start from ip_forward############
#busybox sysctl -w net.ipv4.ip_forward=1
net.ipv4.ip_forward = 1
Return code: 0
#busybox chroot /data/data/edu.phystech.wishnu/system /bin/bash -l
su: applet not found
#busybox fuser -k /data/data/edu.phystech.wishnu/system
Return code: 1
#rm /data/data/edu.phystech.wishnu/system/root/.vnc/localhost:1.pid
rm failed for /data/data/edu.phystech.wishnu/system/root/.vnc/localhost:1.pid, No such file or directory
Return code: 255
############Start Failed############
According to the log your busybox is a bit "incomplete" - it doesn't include a chroot applet (which is really strange). I think reinstalling it should solve the problem (in this case busybox installer or BusyBox from android market should help).
I have tried several versions of busybox (1.19.3, 1.18.4, etc) and they all give the same error. It seems that it tries to run "busybox su" when it does not exist..
Ok, this means that we also have some problems with log printing.
Using "busybox su" seemed to be a bit safe command (it worked on all devices we have for testing). Now it turned out that it doesn't work on every device.
By the way I think I should introduce myself - I'm one of the Wishnu developers, so with any problems you can write to me.
The website claims the app on android can run by itself without using a computer. Does this mean the Debian environment is self-contained and can be run as such? The app seems to start linux, but a computer is then required to view the desktop, correct? How does one view the linux desktop from the phone itself?
The app runs fine on my phone. The image file needs to be place on the internal memory, rather than the SD card itself for it to run properly.
Droid 3 running Steel Droid 3 with root.
GoTeamScotch said:
The app seems to start linux, but a computer is then required to view the desktop, correct? How does one view the linux desktop from the phone itself?
Click to expand...
Click to collapse
You can use any VNC client from the android market to get the picture from the linux desktop on your phone.
There connection address is "localhost", port 5901 and password is "android".
You can check gallery on our site to see how it works (photo with phone connected to the TV).
e334 said:
It seems that it tries to run "busybox su" when it does not exist..
Click to expand...
Click to collapse
Checked the source code of the app - version that should be on the android market and the site shouldn't run any "busybox su" command (however it is always possible that we made a mistake).
So first of all I want to make sure that your busybox has chroot applet.
Please, could you perform "busybox chroot " command from the adb shell (or in the terminal emulator in your phone) and post here a result of this command?
If it works I'll attach the launching script (nearly the same we have in the app) and I hope we will find out what's wrong with the launching procedure.
Awesome, thank you very much for the tip! I downloaded a free VNC viewer app from the market and entered the info you gave and it worked! The desktop is a little sluggish but that's sort of to be expected, even with a dual-core phone.
This is very cool software! I didn't realize running Linux on a Droid 3 was possible as of yet because of loopback support. I've been looking into ways of installing Linux since I got the phone, but couldn't find a way around my kernel's lack of loopback. How does your software overcome this obstacle? Are there any plans of improving speed in future releases?
By the way, if your group would like a graphics designer for UI elements or website images I am available! I work for a company in Olympia, Washington making graphics (in-store signs, exterior posters, skins, icons, etc...). This seems like a cool project and I'd be willing to help out for a cup of coffee or something.
Great project.
Do you have more info on building Debian for Android? Also, how much of the "native" Debian UI apps are transferable (and usable) from the phone?
Stuff that doesn't work: 3G/LTE, accelerometer, GPS, camera, and maybe some other stuff that I'm not remembering
Stuff that does work: GPU (full OpenGL 4.5 and Vulkan), sound, USB device and host, WiFi, Bluetooth, touchscreen (including stylus), SD/USB install
Downloads:
Linux4Tegra R24.1 beta (mirror) (updated on February 18th 2016)
Linux4Tegra R23.1 (mirror) (updated on November 21st 2015)
Linux4Tegra R21.4 (mirror) (updated on July 21st 2015)
Linux4Tegra R21.3 (mirror) (updated on March 9th 2015)
Installation instructions:
Install MultiROM (+ TWRP + touch support + patched kernel)
Download Linux4Tegra and install it through TWRP (Advanced -> MultiROM -> Add ROM)
Tips/notes:
To enable the on-screen keyboard during setup or login, press the blue icon in the corner and select on-screen keyboard from the menu that appears.
To enable the on-screen keyboard on desktop, run Onboard.
If your touch input becomes misaligned, install and run xinput-calibrator.
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Gnurou said:
I am *very* interested in knowing which kernel you have used for this. Upstream, L4T, Android? This looks very promising in any case.
Click to expand...
Click to collapse
I've tried L4T 21.2, 19.3 and Lollipop. All of them need a small kernel patch (which might break HDMI, I have no idea) for the graphics to work, but apart from that they should all work fine for the most part.
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Edit: this actually isn't needed, I was just using the wrong cmdline
Getting Started
THESE INSTRUCTIONS ARE OUTDATED. CONSIDER USING THE PREBUILT INSTALLER FROM THE MAIN POST INSTEAD!
You need a computer with Linux installed and some free space (I don't have the exact numbers, but 5GB would probably be enough). On the tablet, you need 2-3GB of free space (on the internal memory), an unlocked bootloader , root and you need Busybox installed too.
On the computer, you'll need to compile your kernel first (this guide includes the compiler, and there's a prebuilt boot.img in the attachments if you want to skip this part). I recommend using https://github.com/Bogdacutu/STLinux-Kernel, with st8_linux_defconfig.
The initramfs is pretty simple, it just mounts the relevant system partitions and loads Linux from them: https://github.com/Bogdacutu/STLinux-Initramfs. You'll need to edit KERNEL_PATH in build.sh and make the kernel beforehand, then running build.sh will result in a boot.img which you can boot with fastboot:
Code:
fastboot boot new_boot.img -c "console=tty1 fbcon=map:10 fbcon=rotate:2 fbfix"
For the rootfs, Linux4Tegra is the easiest place to start from. All the Tegra K1 versions should work fine. For example, with R21.2: (the sudo is necessary there)
Code:
$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra124_Linux_R21.2.0_armhf.tbz2
$ tar xfvj Tegra124_Linux_R21.2.0_armhf.tbz2
$ cd Linux_for_Tegra
/Linux_for_Tegra$ wget http://developer.download.nvidia.com/mobile/tegra/l4t/r21.2.0/pm375_release_armhf/Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar xfvj ../Tegra_Linux_Sample-Root-Filesystem_R21.2.0_armhf.tbz2
/Linux_for_Tegra/rootfs$ cd ..
/Linux_for_Tegra$ sudo ./apply_binaries.sh
/Linux_for_Tegra$ cd rootfs
/Linux_for_Tegra/rootfs$ sudo tar cfvj ../rootfs.tar.bz2 .
The resulting rootfs.tar.bz2 you'll need to somehow get on the device. For the next part, I'll assume it's in /sdcard/rootfs.tar.bz2. You'll need to do this on the device (through ADB or through Terminal Emulator)
Code:
$ su
# cd data
/data# mkdir linux
/data# cd linux
/data/linux# tar xfvj ../media/0/rootfs.tar.bz2
Enabling Bluetooth with brcm_patchram_plus:
Code:
$ sudo brcm_patchram_plus -d --patchram /system/etc/firmware/bcm43241.hcd --baudrate 3000000 --enable_lpm --enable_hci --use_baudrate_for_download --no2bytes --tosleep 1000 /dev/ttyTHS2
Prebuilt boot images:
new_boot(80).img - working WiFi and sound
new_boot(90).img - added pointer emulation to touchscreen driver
new_boot(94).img - fixed Bluetooth stability
new_boot(114).img - fixed HDMI, added support for non-LTE partition table, my tegra driver patch is now optional (without it fbcon doesn't work properly, enable by adding fbfix to cmdline)
new_boot(123).img (newest at the moment) - fbfix isn't needed anymore, added support for tmpfs ACLs, enabled XZ compression (because after reaching a certain size, the kernel wouldn't find the initramfs anymore), enabled KVM
Bogdacutu said:
Code:
In drivers/video/tegra/dc/dc.c, in tegra_dc_probe, after "int i;" add:
static int num_probed = 0;
if (++num_probed > 1) return -ENOENT;
Click to expand...
Click to collapse
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
_TB_TB_ said:
Won't this code always return - ENOENT?
Sent from my Xperia Z1 Compact using Tapatalk
Click to expand...
Click to collapse
It will always return -ENOENT except for the first time the function gets called (which is enough for the screen to get initialized).
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
joshtheitguy said:
Unless you are looking to completely break the Ubuntu install, do not perform a release upgrade to 14.10.
Everyone here probably already knows this but I wanted to see what would happen, which was rendering the x-server unusable. These results did not surprise me but hopefully this will save someone else who has the same idea as I did some time.
Click to expand...
Click to collapse
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Bogdacutu said:
Try doing
Code:
sudo apt-mark hold xserver-xorg-core
before doing the upgrade, to prevent the driver from being overwritten.
Click to expand...
Click to collapse
Thanks, that was the command I couldn't remember. Let me do a backup of it first then I will try again to see if the outcome is any different, I'll let you know how it goes once I have a chance.
Great i need a dual boot Android/Linux
Bogdacutu said:
What works:
Audio
WiFi
Click to expand...
Click to collapse
Bogdacutu said:
Got it working thanks to /u/GenuineAster, will post a full guide in a day or two.
Click to expand...
Click to collapse
Bogdacutu said:
Photos:
https://s3.amazonaws.com/pushbullet...OAfew/Screenshot from 2014-12-28 12:51:51.png
Click to expand...
Click to collapse
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
etienne51 said:
I got my tablet 2 days ago, and I'm already trying to mess up with it... I decided to try to install Ubuntu on my Shield Tablet (WiFi only, EU model).
So basically, I managed to boot it up thanks to you tutorial. It seems to be working well, but there are some things that does not work, and I see you apparently solved those issues already...
The issues I have are the following, ordered by priority:
- No WiFi (I see that you apparently solved this issue, can you please explain how you managed to do that?)
- While I was writing this message, I went to keyboard layout options, and the OS crashed, it went back to login screen twice (I was on the same window each time, it showed nvidia black screen, then the login screen)
- No audio (I only have a device named "Dummy audio input/output", you seem to have audio, can you confirm that?)
- Graphics flickering on some textures, for example, on the main sidebar menu, when my mouse pointer is over an icon, there is a background on that icon, but the background is flickering, that's weird...
- No touchscreen (But you don't neither)
For the moment, I think the most important thing is WiFi, since I can't do anything without network connexion. Can you help me with that? Thank you!
Click to expand...
Click to collapse
I just updated the boot.img from post #4, WiFi and sound work now, Bluetooth works if you load firmware but it's pretty unstable at the moment.
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
etienne51 said:
Ok, I just tested it, and I confirm it works! I haven't tried bluetooth for the moment, but I have WiFi and audio now with v80. Thank you for the update!
I have another question, I saw your previous screenshot showing glxgears running at around 900-1000fps. Since I have some small lags sometimes, I decided to try glxgears and I'm running at around 450fps, that's less that half the framerate you have on your Shield Tablet. Did you do something special with the drivers after the tutorial you wrote?
Click to expand...
Click to collapse
Not really, you can try messing with the governors and max frequency, iirc there's a script in the driver package that automatically sets the CPU frequency lower on boot.
Update: I got the touchscreen to work with the Android drivers! I will upload the changes to my kernel repo soon (as soon as I figure out which of all the changes I did are actually required).
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
No idea if HDMI works, I don't have a cable (my patch might break it though, in which case we'll probably need to change it). And it works on LTE tablets, but mobile data doesn't work (at least for now).
adampdx said:
How is HDMI out? I find it mildly function on Android, can I expect the same from Ubuntu? Also, I didn't see if LTE is supported.
Click to expand...
Click to collapse
I just ordered a Mini HDMI to HDMI cable, it will arrive in less than a week. As soon as I get it, I'll tell you guys how it works!
/u/GenuineAster confirmed that HDMI isn't working. I'm going to get an Ethernet adapter for netconsole soon, so that I can find out why it doesn't work with my patch to the tegra driver (which I'm sure is the reason HDMI isn't working). I'm also working on a way to get libGL.so to work in an i386 chroot (so that we can try to play desktop games that aren't compiled for ARM yet).
I'm impressed that this actually works so well. Makes what I have on my Shield Portable look pitiful. No sound, no video acceleration, etc. Now the question is, what changes have to be made to a mainline kernel to get similar results? Well, minus the video acceleration that's likely hard-coded to a specific kernel version. Bogdacutu, do you have a patch of your changes? Your github repo isn't a forked copy of the kernel, so it's hard to see the initial changes. I'd like to get a copy of Fedora running. Also looking forward to your touchscreen fix. My usb-otg cable is flakey to the point it causes Ubuntu to reboot if I bump it too much...
Question to the larger community: Anyone know how to get the wireless controller to work with this? I poked at wpa_cli and a couple of the p2p_ commands, but so far haven't picked up anything from the controller when it's searching.
Edit: Seems the otg charging thing doesn't work either. Makes long-term use impracticle when an input device has to be plugged in. Any of the kernel hackers know the bits that changed in nvidia's lollipop kernel to allow this?
Disclaimer: I got this device from the Manufacturer to test Linux on it. The below findings are my own and express my own opinion.
Specs and short review:
Intel Atom x5-Z8350 CPU (4x1,92 GHz)
Intel Integrated GPU
1920x1200 10.1" IPS Screen
4GB RAM
64GB Internal Storage
1 x USB C
1 x USB Micro B
1 x Mini HDMI
Bluetooth 4.2
2.4GHz WiFi
Rotation Sensor
Front and Back Camera
Mico SD Card slot up to 400GB (Website claims 64GB but I sucessfully tested it with an 128GB Card that uses the SDXC Standard)
Headphone Jack
Stereo Speakers
Keyboard Dock Support
Touchpen support
The Chuwi Hi10 Air is a compact 10.1" Tablet running a Windows 10. It has a sturdy Aluminium Body and the overall build quality is astonishing.
The speakers are surprisingly good for a tablet in that price segment. Paired with Bluetooth, a headphone jack and the 1920x1200 WUXGA display it's perfect for all kind of Media Playback. The battery is powerful enough to easily survive a few Movies. The optional detachable keyboard is a welcome addition for when you need to write some text.
The keyboard is nice to type on, but I had cases where it would send keys out of nowhere. I can't guarantee that's not caused by the few drops of water I accidentally spilled on the connection to the tablet at some point. I'm not a big fan of the trackpad, mainly because it's way to small to be usable for me but that might be because I am used to the trackpad on my 15" MacBook Pro.
The Touchpen is very accurate thanks to the digitizer, however the touchscreen does not send different signals for Pen and Finger to the System. That means trying to take notes while resting your hand on the screen doesn't really work.
Sadly, the full Windows 10 install user experience is really impacted by the entry level Intel Atom Z8350. It's just not powerful enough to accomplish any advanced tasks.
However, Chuwi sent me the device to bring linux to it, so that's what I did. This allows us to use lighter Window Managers and therefore more resources for actual tasks, resulting in a better performance.
Install Linux
First of all you need to install Linux on the tablet. That means you will erase your internal Windows installation, so make sure to either do a backup of it, or at least make yourself familiar with how to reinstall Windows in case it's needed.
Please note that you can NOT install Linux on an SDCard because the BIOS can not boot from the SDCard.
Backup
You can find the Hi10 Air Windows drivers here:
https://forum.chuwi.com/forum.php?mod=viewthread&tid=6861
And a guide here (applies for the Hi10 Air too):
https://forum.chuwi.com/forum.php?mod=viewthread&tid=15&page=7#pid29091
https://forum.chuwi.com/thread-15-1-1.html
Install
Next up, it's time to choose your Linux distro.
I recommend anything that is based on Arch Linux and that uses either LightDM or lxdm, because that is what my guide will be using to setup certain features. Of cause you're free to choosewhatever you want.
That means you could for example use Antergos, an ArchLinux based distro that includes Desktop managers (for Antergos I recommend XFCE), or go the hard way and install ArchLinux from scratch and use lxdm with LXQt. LXQt proved to me to be the best lightweight and yet High-DPI friendly Desktop Environment, so that's what I used.
I trust you will be able to find the guides on how to install either with a quick Google search, so I will not go much further into detail here.
To get into the boot menu, you need to press F7.
After your installation is done most things are already working.
Fixing Remaining Issues
Out of the box, there are a few issues and things that do not work because they are missing drivers or similar.
Automatic Rotation
We're getting started with the most important which is rotation.
As you'll need to enter a couple commands to get automatic rotation working, start off with manually rotating the screen by opening a terminal and run the command
Code:
xrandr -o left
Note: xrandr is part of xorg-xrandr, and you will need that package for autoration to work.
There are a couple solution on how to rotate the screen out there, however I decided to go for the one with least overhead that looked the cleanest to me.
First of all, compile the 2in1screen binary. The sourcecode can be found on my GitHub. Download, compile it and push it to /usr/local/bin.
Note: Make sure to install xorg-xrandr and xorg-xinput for this tool to work.
Code:
wget https://raw.githubusercontent.com/Myself5/Chuwi_Hi10_Air_Linux/master/2in1screen.c
gcc -O2 -o 2in1screen 2in1screen.c
sudo mv 2in1screen /usr/local/bin/
sudo chmod +x /usr/local/bin/2in1screen
Now configure the Desktop Manager to start it after login.
LXDE: add
Code:
/usr/local/bin/2in1screen &
to
Code:
/etc/lxdm/PostLogin
LightDM: Place the screenrotate.sh in /etc/lightdm/screenrotate.sh and set
Code:
display-setup-script
in
Code:
/etc/lightdm/lightdm.conf
to
Code:
display-setup-script /etc/lightdm/screenrotate.sh
screenrotate.sh
Code:
#!/bin/bash
pkill -9 2in1screen
/usr/bin/2in1screen &
Reboot and make sure everything works as desired.
Touchscreen
The Hi10 Airs Silead touchscreen requires drivers that are not bundled with a Linux install. You can download them here: https://github.com/onitake/gsl-firmware/tree/master/firmware/linux
See the Readme on how to install them.
These drivers get loaded by the Linux kernel. I submitted a commit to add support for the Hi10 Air to the Linux Kernel and it has been approved. The commit is merged in the 5.1 (and newer) Kernel. That means you need to update your kernel for a proper touch support.
If you previously used my Kernel you can go back to the official kernel by running:
Code:
sudo pacman -R linux-chewbacca linux-chewbacca-headers
sudo pacman -Syu linux linux-headers
sudo grub-mkconfig -o /boot/grub/grub.cfg
Now reboot and enjoy your touchscreen.
Audio
If your Audio isn't working, make sure to update the alsa-lib to Version 1.1.7 or above. On Arch that package is in the stable repos so a
Code:
sudo pacman -Syu
will be enough.
Bluetooth
Install blueman and follow the firmware instructions mentioned here:
https://github.com/lwfinger/rtl8723bs_bt/issues/28#issuecomment-432806835
Which means you need to clone https://github.com/lwfinger/rtl8723bs_bt
and run
Code:
sudo cp rtlbt_fw /usr/lib/firmware/rtl_bt/rtl8723bs_fw.bin
sudo cp rtlbt_config /usr/lib/firmware/rtl_bt/rtl8723bs_config.bin
cd /usr/lib/firmware/rtl_bt
sudo ln -s rtl8723bs_config.bin rtl8723bs_config-OBDA8723.bin
General UI
Now, you probably already noticed, everything is a bit small to use your Fingers.
As a browser I recommend Google Chrome as that has a great touchscreen UI already.
For File browsing and reading I suggest using nautilus and evince because of their touch friendlyness.
System DPI
For the whole system, there is a few things you can improve:
First of all, increase the general DPI.
You can do so by adding
Code:
Xft.dpi: 150
to
Code:
~/.Xresources
. If the file doesn't exist, create it.
LXQt Tweaks
Next up a few additional tweaks for LXQt:
First of all increase the Panel bar
Rightclick on the Panel and Press "Configure Panel". Then set the Size to 50px and the Icon Size to 30px.
Next up, Go to the Menu -> Preferences -> LXQt settings -> Appearance -> Font and set the DPI to 96
and finally go to Menu -> Preferences -> LXQt settings -> OpenBox Settings -> Font and increase the individual fonts to get a window title bar to drag/drop as well as hit the navigation with the finger. I set mine to Cantarell 16 and Cantarell 14.
Install OnBoard
Another Handy feature I found myself in need of was an onscreen keyboard. For that I installed OnBoard, and found a very neat feature here: https://bugs.launchpad.net/onboard/+bug/1232107
You can map a button to open/close the keyboard.
I set mine to Super L, which equals the left Windows button and the touch button on the tablet itself.
In the LXQt Settings Menu you can configure Shortcut Keys.
Create or edit the existing shortcut and either map the following DBus Call.
DBus Call:
Service:
Code:
org.onboard.Onboard
Path:
Code:
/org/onboard/Onboard/Keyboard
Interface:
Code:
org.onboard.Onboard.Keyboard
Method:
Code:
ToggleVisible
If your Desktop environment doesn't support DBus calls, use the following command:
Code:
dbus-send --type=method_call --dest=org.onboard.Onboard /org/onboard/Onboard/Keyboard org.onboard.Onboard.Keyboard.ToggleVisible
I got a Chinese manufactured pad-like device which is supported by the Linux mainline kernel and works pretty well except for the ****ty wifi chipset from Broadcom. That device has z8300 Soc and runs pretty well. I really like the On-The-Go device design as it is easy to carry around. Thanks for sharing!
Does this do a total partition wipe? Can you install to the Android partition and keep windows?
Droid_Nut said:
Does this do a total partition wipe? Can you install to the Android partition and keep windows?
Click to expand...
Click to collapse
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.
I would love to get one of these units for review
Myself5 said:
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.
Click to expand...
Click to collapse
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
Droid_Nut said:
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
Click to expand...
Click to collapse
That sounds like a good plan. Clonezilla backup is what I went for too.
silv3rfox said:
@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
Click to expand...
Click to collapse
Battery life is great, i'd say better than Windows. Can't give you any numbers though because I didn't really pay attention to it yet.
Android-x86 is technically possible and with the Linux drivers even easier but I havn't looked into that yet.
Hey guys happy to see there is interest in this tablet. I do got the dualboot version too.
To install Android i found this:
jonathansblog. co.uk/ factory- restore- android- on- chuwi- hi10
After i personally Installed remix OS
konstakang.com /devices /chuwi_vi10plus /RemixOS/
When I installed Ubuntu, just Ubuntu Started, Android stuck, i found a solution here:
github.com /floe /tuxblet
I Just cant figure out this one:
Unfortunately, this still causes the Android install to hang on boot after Linux has been installed. I was assuming, for a very long time, that this is also an EFI-related problem. However, after multiple factory resets (see https://forum.chuwi.com/thread-2341-1-1.html and https://01.org/node/2463 for instructions), I finally found out that the problem is related to the very eager Ubuntu automounter, which grabs any ext4 filesystem it can find and mounts it read-write.
Of course, this shouldn't be a problem in theory, but this also happens for the Android system/data/etc. partitions, and whatever Ubuntu does to the ext4 FS when it's mounted, causes Android to croak. This means that even just booting a Ubuntu Live System from USB one single time will likely render the Android installation unbootable.
I've finally managed to fix this by setting the respective UUIDs to noauto in /etc/fstab as follows:
# do _not_ automount the Android partitions
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 /none ext4 ro,noauto 0 0
If you look closely, you will notice that entries 2-4 are not actually proper UUIDs, they have an additional digit from 1-3 at the very end. The reason for this is that all the Android partitions (system, cache, data, config) have the same UUID and show up with the extra digit when the automounter grabs them. I'm not sure if this UUID duplication might actually be the root cause...
Unfortunately he does not explain how to no auto mount this partitions without a live CD and / or it is going to work even if Ubuntu installed is.
Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
nikmag said:
Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
Click to expand...
Click to collapse
5.1 includes the touchscreen fix on it's own so you don't need to use the kernel I provided anymore.
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
nikmag said:
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
Click to expand...
Click to collapse
So it does work with my 5.09 kernel though, right? Otherwise you'd have forgotten to install the touch drivers (see the OP on how to do that).
Bluetooth works flawless for me on Arch. Maybe Mint has some other packages that don't fully work with the chip yet?
As for Grub: there's nothing we can do about that. As it currently stands grub has no support for touchscreens or screen rotation. You could try different UEFIs (rEFInd comes to mind here) but other than that it's not possible. I thought about possibly mapping the volume buttons to up/down for selection, but that would still leave us without an enter key.
Although, now that I think about it again: it might be possible to register the windows touchkey as "enter". I guess I'll take a look into that
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
nikmag said:
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
Click to expand...
Click to collapse
According to a quick Google search custom keymapping for grub seems to be harder than expected. rEFInd seems to have touch support for some tablets though. I might look into that instead.
The "active Pen" on Windows is useless because it's not "active". It does get prefered over your hand, but the Hi10 Air doesn't have proper pen support. So the 256 pressure level touchpen they sell you is effectively as good as your finger. There is no pressure sensitivity support. On Linux this get's even worse because the pen is apparently using a different kind of calibration, so if you use it it's horribly offset. I was looking to use it for Notes during lectures, which is impossible to do. Even on Windows it's just not working. I've been in contact with my contact at Chuwi (who also sent me the device) and he just kept on talking around the topic. He never officially claimed the Pen would be supported but also never denied it. All he did was keep on sending me different touch drivers to "make the pen work" (although the definition of the term "work" can mean everything here).
TL;DR: Not pleased AT ALL.
P.S: I just updated the OP. the 5.1 kernel is released and works flawless on my Hi10 Air.
Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc
heenry20 said:
Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc
Click to expand...
Click to collapse
So which tablet do you have? A normal Hi10 Air?
Myself5 said:
So which tablet do you have? A normal Hi10 Air?
Click to expand...
Click to collapse
Yes, running kde neon.
M5 you are right, the finger is much better than 'active' pen! I bought also nebo app for recognition but the pen is totally invisible. Probably you checked drivers from you know https://forum.chuwi.com/thread-6861-1-1.html. It will be a big help if you manage to do something with rEFInd . Thanks