Database Info

[Q] use tf to unlock and root phones

hey everyone,
so i finally got the dock for my TF a couple weeks ago.. i have several friends that are not as tech savvy as i am, but still like android, well i want to offer to root their devices for them. more out of curiosity then need i was wondering if it is possible to unlock and push the recovery from a TF? i know that the TF has ADB on it, but i havent really started any development on the TF its more for fun, i use my nexus 1 for development.. any light you can share on this would be appreciated.

Interesting...
Nice thread i hope some one comes up with further info about this idea i would like to do this too!!!! I have sold mi laptop TF can do everything... And soon W8 will be possible on it and STABLE Ubuntu!!!

I was contemplating this also since a girl I work with wanted me to root her Galaxy S1 but I only had my TF with me and we can't install drivers on the work computers.
I assume it should be possible, you just may need more of the Linux binaries, for example you may need to do it via a chroot install of Ubuntu or as a native (dual-boot) system. Look at the shell scripts and see what binary tools they require (cp, mv, cd etc...), you may be able to do it with Android's toolchain.

There's something in the market called "remote adb" which "might" be of use, but I kind of doubt it. It could also be one of those adbwireless versions of adb where you still do the heavy lifting from the PC.
My take would be to look at the results of google "+source +adb +android" and you'll get a couple of hits that point at adb repos in git format.
Then use a linux box to clone one and point it at some crossbuild tools (see for example the howto build kernel threads that are here and there) and built it for our architecture (arm{le}). I've done this for the bash shell and a few other things I liked in linux and it should be possible. One built, push it into /system/xbin, chmod 755 adb and see how things go.
I don't have the keyboard dock or the OTG dongle so no point in my doing it since I can't test.
Good luck -
edit: http://lackingrhoticity.blogspot.com/2010/02/how-to-build-adb-android-debugger.html seems like as good a place as any since it has source, instructions, etc. So probably all you have to do (if this nutty project will work at all) would be to modify the Makefile so that it's pointing to the toolchain for armv7le (or that's what uname -a shows on my eeepad).
edit: Another one that's already been built for android (I tested it), is sshd or dropbear and here is a link: http://jhulst.com/c/dropbear-ssh-android .
The main thing is being able to hit the device you want to setup using either ssh or scp, and functionally this'll do most if not all or more than adb will. What won't work are any scripts written that are already using adb commands.

thanks for the input originally i was thinking being able to use terminal inside honeycomb, but i suppose the easier (or perhaps better stated, the "road more traveled") route would be dual booting linux and just setting up the dev kit on there..

Latest version of ubuntu by little stevie is your best bet

[How-To][Linux]Hardware Acceleration on Linux Help

[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?

[APP][4.1+] Tuxoid v0.1.1 - A full Linux desktop environment on your Android

Code:
*** Disclaimer
As usual, I am not responsible for thermonuclear war or other apocalyptic futures.
TL;DR: If you break your device with this project, it's not my fault (although I will of course be willing to help you in your troubles!!).
Introduction
Have you ever wanted to use your Android device as a fully-fledged desktop Linux box? Now you can, with Tuxoid!
A year or two ago, I discovered the Linux-on-Android project. (http://forum.xda-developers.com/showthread.php?t=1585009) I was fascinated by the possibility of running Linux on top of Android and using a desktop environment. However, I was slightly disappointed by the lack of some features, as well as a lack of development over the time of the project's existence. Thus I embarked upon an epic quest (well maybe not quite that dramatic) to build my own version from the ground up, basing it upon the ideas explored by Linux-on-Android.
After some on and off hacking on my OnePlus One, I now have some very early working code.
Below is a video demonstration of the current state of Tuxoid, demonstrating a few of its features.
Here is a list of some of these features:
- The big one: fast and high quality display system
- Native keyboard and mouse support (automatically disables Android's built-in system)
- Audio support. Audio from the desktop environment is piped into Android's audio system, so you can use your device's speakers, headphones or bluetooth etc
UPDATE: First builds!
I've built the first publicly available versions of the project. Before you get excited, I should warn you that they are in an unstable state. You can grab the APKs in the Downloads section of this project, as well as on the Releases page of the project on GitHub. These builds are not for n00bs! If you're still determined to give them a try, here are the instructions:
Requirements
An Android device running 4.1 or newer (it will be availabe for older versions in the future, but for know only Lollipop is supported) Older versions now supported!
Root with SuperSU for managing permissions. I will not explain this here, as there are already hundreds of guides available. If you don't know how to root your device, this project (at least in these early stages) is not for you.
A reasonable amount of internal storage (at least 1-2 GB free)
A stable internet connection. Make sure you're using WiFi for best results.
A mouse and keyboard to control the desktop environment. You should be able to use wired ones (via an OTG adapter) or wireless via bluetooth. As long as Android recognizes it, you should be good to go.
This is not a requirement, but you won't be able to do much without it (for now): knowledge of the Linux command line and preferably how to use the pacman package manager for Arch Linux, as that is the distro upon which Tuxoid is based (more distros will be available down the line!)
Setup and installation
Once your device is rooted, open up the SuperSU app and go to the Settings tab. Find an option labelled "Mount namespace separation" and ensure it is UNchecked. (Make sure to reboot before continuing if you had to do this)
Download and install the APK for Tuxoid. Again, if you don't know how to do this, you shouldn't be attempting to install an early build Tuxoid...
Open the Tuxoid app and tap the gear in the actionbar to go to the settings menu. There are a few options you can tweak here, but the main one you should be interested in right now is 'Disk image size'. Select a size that suits the amount of space you have free on your internal storage. I would recommend 4GB (the default) to allow room for installation of your own packages later. If you have less space free on your internal storage than you select here, the setup process will fail.
Go back to the main screen of the app and ensure you have a stable internet connection. Now connect your keyboard and mouse (you must connect them before booting Tuxoid up every time). Then, press 'Start' to begin the setup process. This will probably take a while, so just leave your device down for a while and check up on it every once and a while.
Eventually, if all went well, you should see a screen with a grey background and an xterm window. Feel free to run some commands. To start, I'd recommend installing the Chromium browser (open source version Google Chrome). To do this, run 'sudo pacman -S chromium' (without quotes). The password is the same as your username. Once installed, run 'chromium' to start the browser. For those who are interested, the window manager installed by default is Openbox. If you want to install some more packages, the list of available ones in Arch Linux for ARM devices is available here: http://archlinuxarm.org/packages If you weren't able to get up and running (i.e. no screen with a cursor and no xterm), you can try some of the steps described in Troubleshooting & Tips.
When you're finished playing around, follow the steps below to ensure clean shutdown of Tuxoid. If you want to boot up again, you can just open up the app at any time and tap on the start button. Tuxoid will use your existing system image.
Shutdown procedure
When you're done, simply press the back key on your device to close the GUI and press the stop button to shutdown Tuxoid. After a few seconds, the log will show "SHUTDOWN!", meaning the shutdown procedure was completed successfully.
Troubleshooting & Tips
If Tuxoid failed to boot during the initial setup, you can retry by first removing files in the 'droidtop' folder on your internal storage (usually 'system.img' and 'arch.tar.gz') and then pressing 'Start' again in the app.
If your mouse and keyboard aren't working in Tuxoid, ensure that they were connected to your device BEFORE you pressed the start button and make sure they were detected by Android. If they weren't detected by Android itself the they definitely won't work with Tuxoid.
If you something goes wrong at any stage while using Tuxoid, please press the 'Send log' button in the app to send me a copy of the log shown on the main screen.
If the app crashes, a dialog will pop up asking you to send a report. Please do this as it makes it much easier for me to fix bugs!
If you have any feedback and suggestions, feel free to post them here in the forums! You can also submit issues on the GitHub project (although this is really more orientated towards developers)
If you are a developer and want to get involved in the project, you can post here in the forums and/or submit pull requests on GitHub.
Source code
I've published all of the source code for the app to GitHub (http://github.com/jackos2500/tuxoid) Feel free to fork and make changes, and, even better, submit pull requests to move the project forward!
Finally, I would like to say thanks to the guys over at Linux-on-Android for their great work, without which the idea for this project would never have existed!
XDA:DevDB Information
Tuxoid, App for all devices (see above for details)
Contributors
jackos2500
Version Information
Status: Testing
Created 2015-06-13
Last Updated 2015-06-14

Reserved
Changelog
v0.1.1
Adds compatibility for Android versions as far back as 4.1 (API level 16).
Bug fixes:
screen resolution could be detected incorrectly
'setenforce' could fail to execute due to its lack of existence on older platform versions
v0.1
Initial public release.

Reserved

Its really interesting to hear about linux on android

shahzu3 said:
Its really interesting to hear about linux on android
Click to expand...
Click to collapse
Yup! I think I'll put out a build later with some instructions so that people can try it for themselves.

Mm

shahzu3 said:
Mm
Click to expand...
Click to collapse
Well I've pushed out the first public build. Give it a try and tell me what you think!

Hi. Your project sounds great ??
Is really necessary to have so internal space or could it be possible one day to have the whole stuff on the external sd.??

That is just amazing, thanks for your work, a tablet running this would be really nice... I'm going to try it out.

Hello! This looks very promising but I can't find any download link. Is it missing?
Edit: My phone just didn't load the page fully, the download section is on the top.

DirkStorck said:
Hi. Your project sounds great
Is really necessary to have so internal space or could it be possible one day to have the whole stuff on the external sd.?
Click to expand...
Click to collapse
Good point! I'll see if I can do something about that sometime soon. Unfortunately if the chroot environment is not stored in a disk image the filesystem it is stored on must support Unix permissions, so no FAT32 formatted sdcards without disk images. FAT32 also limits file size to 4GB, so that would be the max size for a disk image there. I'll probably add a way of optionally adding an extra partition to your SD to get around this at some stage.
WideBRs said:
That is just amazing, thanks for your work, a tablet running this would be really nice... I'm going to try it out.
Click to expand...
Click to collapse
Cool, tell me what you think when you give it a go!

jackos2500 said:
Good point! I'll see if I can do something about that sometime soon. Unfortunately if the chroot environment is not stored in a disk image the filesystem it is stored on must support Unix permissions, so no FAT32 formatted sdcards without disk images. FAT32 also limits file size to 4GB, so that would be the max size for a disk image there. I'll probably add a way of optionally adding an extra partition to your SD to get around this at some stage.
Cool, tell me what you think when you give it a go!
Click to expand...
Click to collapse
I have been using Linux Deploy on my tablet and it worked quite well. They have the environment as an image on the internal or external sd card. I think 4GB is a enough for a Linux system. For those who want more would have to format the external as ext4.

DirkStorck said:
I have been using Linux Deploy on my tablet and it worked quite well. They have the environment as an image on the internal or external sd card. I think 4GB is a enough for a Linux system. For those who want more would have to format the external as ext4.
Click to expand...
Click to collapse
I've pushed a new release with support for devices running Android 4.1 and above. I think I'm going to start working on improving the user-friendliness of the project tomorrow. This will probably include improving the UI and setup process, as well as better error handling. Once that code is in place I won't have to refactor any new features I add to the new UI, so it makes sense to do it first. It will take a while, and whenever it's done, I'll probably start working on some of those new features.

Hi,
Could you tell me if:
a) my phones built-in keyboard will work?
b) if there's an option to use the touch screen to control the mouse?
Thanks

moodroid said:
Hi,
Could you tell me if:
a) my phones built-in keyboard will work?
b) if there's an option to use the touch screen to control the mouse?
Thanks
Click to expand...
Click to collapse
Right now, no. Both of these are definitely a high priority though.

jackos2500 said:
Right now, no. Both of these are definitely a high priority though.
Click to expand...
Click to collapse
Excellent, thanks. I'll keep an eye on this...

Can i decompile and compile apk with this Linux for Android? I havent pc

this is really amazing, as it is very useful for tablets, at least for my tab s 10.5 inch, keep it up!
Currently using Xserver Xsdl, with the pain of slow refresh rate and input interrupt.
Thank you for this effort!

Hello,
So far, I had these issues before it worked, otherwise its awesome, the only way to render x server on android smoothly and no input latency without using direct (kernel) framebuffer:
1)Latest arch armv7hf use xorg-server and xf86-input-evdev compiled for/by version 1.18.x , had to recompile 1.17 from source since your module (the source code isnt released in your github :/, guess you forgot) is compiled for ABI module 20, currently 23.
2) High cpu usage, probably implement refresh rate limitation on the app side for displaying the shared memory framebuffer, though having the source code for the module would really help, guess its a modified dummy.so (?) to copy framebuffer to shm? Anyways ill try to workaround the issue using a compositor.
Thats all! working perfectly... If anyone need the compiled 1.17 versions of xorg-server and evdev, just use ABS or pm me.
Thanks!
EDIT: I think it would be better to turn this into X server framebuffer viewer app, and combine it with Linux deploy (+ 'custom scripts' option is already implemented in Linux Deploy, useful for evdev and xorg config) for more linux flavours

apparently, it seems that you have copied droidtop project without mentioning it (license: MIT) : https://code.google.com/p/droidtop/
which has been archived now with no public access

NetHunter 3.15.3 - S7 Edge (SM-N930F - Exynos - MM) - My set up, might be helpful.

The intention of this post is to possibly help some one out since I struggled to get this working. Non of this software belongs to me, its only a guide of the steps that got me up and running on my phone. Hopefully its useful for some one else.
I am currently learning Cybersecurity, I love nethunter for my lazy study sessions on the couch whilst trying to exploit virtual-machines running on my home server. However the tried and true Oneplus one is getting a bit dated and I really wanted to figure out how to get this running on my S7 edge. I spent days trying other tutorials for getting NH to run, some builds would only run on 6 cores which made the phone so laggy it would barely boot, while others would run smooth however HID and wireless attacks wouldn't work...
So what I am running now which is 100% working:
My phone - S7 Edge SM-N930F
Rom - Renovate Note 2.0 Note 7 port (Download from this site, You'll have to confirm your phone is compatible)
Kernel - kernel-nethunter-hero2lte-marshmallow-3.15.4-20170629-1630 (Downloaded from build.nethunter.com)
Kalifs - nethunter-generic-arm64-kalifs-full-rolling-3.15.3-20161129-1413 (Downloaded from build.nethunter.com)
Flash the rom, set up as you normally would.
Reboot to twrp - flash kalifs package, then flash kernel.
Reboot device.
Now when you start the Nethunter app for the first time, you'll have to give it permissions, and install chroot from the sdcard in kali chroot manager. However the package name will be kalifs-armhf-full.tar.xz, rename it kalifs-full.tar.xz otherwise it will not find it . Let it finish set up, usually takes 5-10minutes. Also, make a copy of kalifs-full.tar.xz on your computer somewhere (just incase the next thing happens).
-Note- You can try to use the download/install chroot option however its not that reliable imo. I find its much easier to do it manually installing from the sdcard!
Open the Nethunter Terminal app, give it permissions and click kali. Did it crash? Sometimes the terminal app can be flaky and what you need to do is uninstall androidVNC, Nethunter terminal, and the Nethunter app.
Download the apks individually, you can find them on GitHub. Reinstall Nethunter terminal, androidVNC and the Nethunter app ->in that order<- Don't ask me why it works, it just does.
Re-Open NH app, give it permissions, put that copy of kalifs-full.tar.xz back on your internal sdcard and install it again. Everything should work properly from now on.
Check to make sure your repositories are correct - [email protected]:~#nano /etc/apt/sources.list
Is it the same as what kali lists on their site? (see below):
deb http://http.kali.org/kali kali-rolling main contrib non-free
# For source package access, uncomment the following line
# deb-src http://http.kali.org/kali kali-rolling main contrib non-free
Yeah? good.
Then I have always needed to update the signature keys otherwise update, upgrade, dist-upgrade never works.
So in terminal again input [email protected]:~#wget -q -O - https://archive.kali.org/archive-key.asc | apt-key add
Now you can update [email protected]:~#apt-get update && apt-get upgrade && apt-get dist-upgrade
This will take a while.
Some minor glitches I have noticed in terminal:
- The Samsung keyboard enter key will switch between the return key, find key and go key randomly. Its annoying, but just use the hackers keyboard instead, or use the return key at the top of the terminal shortcut keys.
- Sometimes the space bar is missing in terminal the first time you run it after a reboot. Just restart the terminal, or use hackers keyboard.
Phone performance:
- Runs smooth as butter! Radios maintain good connection. No random reboots or freezes. However the battery life is not the greatest. I'll average 16 hours with 3hrs sot. Not quite like the two days + 7hrs sot I'll get out of my galaxyproject rom set up.
- Camera can be slow in low light. And in text messages the back facing camera doesn't seem to work when you try to take a photo as an attachment.
- Power saving and Ultra power saving can severely mess with the screen resolution. Screen image appears to be at 60% of the actual size, however touch locations of apps remain in the same location. So if you turn on power saving. It gets fun trying to predict where you need to touch the screen to turn it off.
Every tool in the nethunter app works for me. In terminal all my usual tools work fine like metasploit, nmap, enum4linux, dirb, nikto, cewl, sqlmap, wpscan, the aircrack suite etc. I even got openvas installed and working.
I don't come around often, but like I said due to my struggles I just wanted to write something up that might help others. I meant to do this months ago so everything is to the best of my knowledge. If you have any questions, I'll try to answer them when I swing by again.

Chuwi Hi10 Air Linux Installation Guide

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