Hello.
I managed to install RemixOS in my Asus Transformer Book T100TAM, and so far I'm loving it.
But I can't get the touchscreen to work, any hints?
Also, I'd like to turn off the option to tap-to-click, because I keep clicking accidentaly. Is it possible?
Thanks in advance.
It seems that the touchscreen driver doesn't work or is not there. Android-x86 build works fine with touch as far as I remember.
I have one question for you:
Do internal speakers disable automatically when you connect the headphones into the audio input?
The internal speaker doesn't disable when I plug headphones.
If you need anything tested for this particular model, please ask me.
An update on my issue: I reinstalled Remix OS, and at first boot the touchscreen works OK. After a reboot, it never works again.
Don't know if it's relevant, but I used this tool to install Remix OS:
http://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
Had to use the tool because this PC doesn't have Legacy Boot, and it has 32 bit only UEFI.
Another thing: the camera LED notification light (a dot that only lights up when the camera is in use) is always on.
Related
I don't know if anybody can help me with this problem but I'd appreciate if anybody could, as I have 2 Asus HD7 Memopad (ME173x) tablets running identical to each other, same settings, same software, etc. I have a powered hub in an OTG cable connected to one of my tablets. When I hookup my Canon point and shoot digital camera to the hub, one of the tablets sees it acknowledges it pops up a window saying what program should I use for this USB device either Asus Gallery or the Asus studio or the Google camera importer, and everything works fine.
I unplugged the OTG cable from that tablet and plug it into my other tablet and I get nothing what so ever, nothing pops up. but I know its not a problem with the USB port on that second tablet because when I plug in a flash drive into it and load up the OTG helper I can see the flash drive with no problem using ES file manager. I just can't seem to get the camera to read on that tablet.
so I plug the OTG cable back into the other tablet and boom it pops up the pop up again and it works. I compared settings on both tablets and they're all the same settings identical. I don't remember what I did if I did anything to the first tablet to make it work.I think I just plugged it in and it worked.
I appreciate any help somebody can give me to figure out why the second tablet is doing this? If I have a setting that I need to do I like to know what it is or maybe I forgot a step that I did on the first one I can't remember thank you for your help I appreciate it.
Dog
Dog Rox said:
I don't know if anybody can help me with this problem but I'd appreciate if anybody could, as I have 2 Asus HD7 Memopad (ME173x) tablets running identical to each other, same settings, same software, etc. I have a powered hub in an OTG cable connected to one of my tablets. When I hookup my Canon point and shoot digital camera to the hub, one of the tablets sees it acknowledges it pops up a window saying what program should I use for this USB device either Asus Gallery or the Asus studio or the Google camera importer, and everything works fine.
I unplugged the OTG cable from that tablet and plug it into my other tablet and I get nothing what so ever, nothing pops up. but I know its not a problem with the USB port on that second tablet because when I plug in a flash drive into it and load up the OTG helper I can see the flash drive with no problem using ES file manager. I just can't seem to get the camera to read on that tablet.
so I plug the OTG cable back into the other tablet and boom it pops up the pop up again and it works. I compared settings on both tablets and they're all the same settings identical. I don't remember what I did if I did anything to the first tablet to make it work.I think I just plugged it in and it worked.
I appreciate any help somebody can give me to figure out why the second tablet is doing this? If I have a setting that I need to do I like to know what it is or maybe I forgot a step that I did on the first one I can't remember thank you for your help I appreciate it.
Dog
Click to expand...
Click to collapse
Problem solved, problem solved! I solved the problem, problem solved! haha
I ran the app called USB host diagnostics on the the second tablet that was giving me the problem. It fixed the problem I then looked at the first tablet as I seen the program looked familiar. It was already installed on the first tablet and I remember running it before and well as you know both tablets are working.
Hey guys,
My Nexus 4 screen+digitiser are dead (I replaced the whole phone with a Moto G because it was nearly the same price as repair). I changed recovery from TWRP to CWM, installed a stock ROM but now I'm stuck. I can't set up the phone without being able to touch the screen, can't add a bluetooth keyboard without touching, can't remotely control with ADB without touching (to confirm the request), and I can't remotely install anything because I haven't added my Google account yet (clean flash of stock ROM).
I've tried to Google this but have had no luck, do any of you guys know if there exists a flashable VNC or other remote software which I can just stick on the phone, and then be able to VNC straight in (without confirmation) to control the phone and get it set up?
I wanted to set up the phone as a desktop computer for the kids (MHL-HDMI for the monitor, bluetooth keyboard and mouse for control, speakers in the headphone jack for sound).
Thanks for reading my question guys and any ideas you may have!
ı need flashable VNC. Did he find anything in 7 years? .S
I was using my wireless Logitech desktop set but I noticed some lag after not using it for some seconds. When I keep using the mouse or keyboard there is no problem and everything works fine. But when I stop typing or stop mousing for longer than three seconds, the tablet doesn't recognize any input anymore. When I move the mouse or use the keyboard, nothing happens, but after two seconds any input is recognized again.
So I have to keep typing or else I have to wait some seconds to let the tablet recognize any input. This is unworkable.
I tested it with two desktop sets with two different Unifying receivers. When I use a corded mouse or keyboard, everything's fine. It seems to me that there is some sort of logitech standby mode which the tablet can't handle or something.
What can I do abaout this?
Added logcat of connecting usb, a freeze moment, and the disconnection. But I see nothing wrong there...
http://pastebin.com/fisK3hQ0
I bought an other Logitech Wireless mouse (standard receiver, no Unify) and that one works perfectly. So it looks like it has something to do with Unify, not wireless in particular.
Anyone?!
The Shield tablet has the same issue:
https://forums.geforce.com/default/...quot-delayed-input-after-inactivity/?offset=2
Maybe it has something to do with the Tegra K1?
farris said:
The Shield tablet has the same issue:
https://forums.geforce.com/default/...quot-delayed-input-after-inactivity/?offset=2
Maybe it has something to do with the Tegra K1?
Click to expand...
Click to collapse
It is really annoying. My Shield Tablet is fantastic, except for this issue with the keyboard/mouse. Sad panda.
scotte9999 said:
It is really annoying. My Shield Tablet is fantastic, except for this issue with the keyboard/mouse. Sad panda.
Click to expand...
Click to collapse
And no solutions yet. Maybe a different kernel will work, but I like to keep my N9 stock (the first months hehehe)
Any solution?
Has there been any solution to this issue yet? I too am having the same problem.
Work Around
I have a work around that seems to fix this issue. For this to work you will need to be root. Also note that this solution will cause all USB devices to remain on at all times and will not survive a reboot. My experience is mostly with linux and very little with android. I expect someone should be able to modify the following script fairly easily for a more permanent solution.
Open your favorite terminal emulator and type the following four commands pressing enter after each:
su
for i in /sys/bus/usb/devices/*/power/control;
do echo on > $i;
done
This script toggles the power control setting for all usb devices from the auto state to always on. Hope this helps!
I have a slight lag with my logitech controller through USB OTG. It's just a split second lag, but it's there right from when you plug it in. Makes it unusable for gaming. No issues whatsoever with my Logitech bluetooth keyboard however.
Hi there.. no sound for me in my dell xps 12 9250 even with latest update I heard that the stock android-x86 rc2 supported my sound card so maybe jade didn't update there kernel?
My sound card: realtek high definition audio (sst)
@katana444 don't just say u heard Android-x86 supports your sound card - be sure - check it out by installing it.
On my device sound works from the beginning, but it works either badly or fails few minutes after booting the system.
I have the same audio card on my Lenovo miix 700, and it's not working on the latest RemixOS release, while it is working on Android x86 RC2.
According to Jade developers, they are aware of the issue, not all changes in RC2 have been incorporated yet, hopefully in the next release we will also have audio working.
I want to emphasize to you all that realtek high definition audio (sst) is just a "userfriendly" sound device name. There are dozens if not hundreds of audio chips that carry this one same name, but many require different drivers - because of that, providing just this name can be insufficient. I for instance, I found out online what my audio chip model was. There are many methods to get the proper HW info, but Remix needs a good, neat guide for that.
About differences between Remix and Android-x86 - I agree, these are weird. Logically, I'd thought that Remix has all what Android-x86 + it's own features, but apparently there are differences, the sad fact is that sometimes it's backwards. Developing such project is a big challenge and we should have that in mind - there will be lots of problems and that will persist for some time (probably long) before we reach a stable state.
Ventricle said:
@katana444 don't just say u heard Android-x86 supports your sound card - be sure - check it out by installing it.
On my device sound works from the beginning, but it works either badly or fails few minutes after booting the system.
Click to expand...
Click to collapse
Thanks for reply already installed android-86 rc2 before i saw your message actually the sound working perfectly and that's really weird i really hope jide update the kernel
KamaL said:
I have the same audio card on my Lenovo miix 700, and it's not working on the latest RemixOS release, while it is working on Android x86 RC2.
According to Jade developers, they are aware of the issue, not all changes in RC2 have been incorporated yet, hopefully in the next release we will also have audio working.
Click to expand...
Click to collapse
I saw your reply in another thread about that you have really good tabletPC it's was my second choice before I bought Dell XPS 12 9250 as you say the sound working with stock android-x86 but unfortunately not working in remix OS
another thing that confused me how do you lock your screen for me the power button not functional and if i used a third party app to lockscreen the remix os is just turn off
Vioner said:
I want to emphasize to you all that realtek high definition audio (sst) is just a "userfriendly" sound device name. There are dozens if not hundreds of audio chips that carry this one same name, but many require different drivers - because of that, providing just this name can be insufficient. I for instance, I found out online what my audio chip model was. There are many methods to get the proper HW info, but Remix needs a good, neat guide for that.
About differences between Remix and Android-x86 - I agree, these are weird. Logically, I'd thought that Remix has all what Android-x86 + it's own features, but apparently there are differences, the sad fact is that sometimes it's backwards. Developing such project is a big challenge and we should have that in mind - there will be lots of problems and that will persist for some time (probably long) before we reach a stable state.
Click to expand...
Click to collapse
Sorry for this naive question:
how could i found the chip model (number) used in the sound card of the laptop?
thank you !
Losl
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
I installed 104 on virtual box and USB flash drive. In VB the audio setting is:
Host Audio Driver: Windows DirectSound;
Audio Controller: ICH AC97
The sound card works perfectly.
But NO sound when running 104 from the USB flash drive. Any suggestion.
THX!
losl
So I finally have Android Apps working on the Chromebook Pixel 2013. It was an easy matter installing the R11 firmware. The issues I am facing have to do with the sound. It plays sound, although the volume does not seem to work as it should. It only really changes when I set it to either mute or on at full volume.
Also, there seems to be an issue with the headphones. I need to go into the Alsamixer and unmute the channels. The issue is I can not save this setting (tried the normal Linux way with no success) so when ever the comp is restart have to go back into the Alsa mixer. It is not a major issue, but it is one thing keeping it from being flawless.
The only other thing is the mouse pointer in android apps is very small. I am thinking this has to do with the way Android is rendered on Chrome OS and the resolution of the screen, so not sure if there is any way of fixing it, but thought it I would bring it up. Beyond that, if anyone has a Chromebook Pixel and wants Android apps, the process is easy. If anyone needs me to outline the full process, just let me know! The Chromebook Pixel 2013 is far from dead, and still one of the most stunning laptops you can buy!
I'll probably be doing this myself shortly. I'll investigate the audio issues and alsamixer. I assume this is you? https://www.reddit.com/r/chromeos/c...pixel_2013_but_now/?ref=share&ref_source=link
Thanks,
Michael
Did you ever get this working? I've tried and after installing the R11 firmware it won't boot.
How do you install the firmware?