Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
ncuxxx said:
Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
Click to expand...
Click to collapse
For now, no. Unless Huawei or 3rd party develop driver for it.
My E1550 now also collecting dust coz i'm using 101 most of the time rather than laptop.
If i understand, we need root access to add 3rd party driver? Or there uis no way to compile driver?
This would be quite interesting if it would work.
Would this also enable call/sms functionalities?
I have an AT&T Laptop Connect Dongle which does not work. I have been able to bluetooth tether using PAN. I would rather use adhoc, i haven't found a way yet.
I prefer Archos to improve the stabilities of his 2.2 firmware first before adding more "new" features.
3G dongles
Correct me if I'm wrong, but as far as I was able to digg around, it seems that USB host mode (wich is already in Archos), __usbserial.ko__, and adeqaute parts of devfs rules, are only three really necessary things that are needed on any linux, for USB 3G dongles to get properly recognized (at least Huawei ones).
rest of the things regarding "dial-up" a 3G connection, are done with commands from ppp package (should be in froyo), can be done from shell (busysbox __should__ be sufficient) for a start.
usb_modeswitch package is needed also, but only for the modems that are USB composites with virtual CD-ROM and/or MMC card reader (like mine E1552) in order to switch them to a serial mode (because their are detected as mass-storage initialy). For a start, this can be overcomed by sending adequate AT command's to dongle, that disable dongle's virtual CD-ROM and/or MMC card reader, from some windows machine prior to experimenting with dongle on linux/archos (setting is saved on dongle - you only need to do it once).
Since I still don't have my A101 (should receive it beggining of 2011), can someone tell me from kernel .config file is USB serial support compiled in archos kernel, and if not can we compile it as a additional module (like archos unionfs/ntfs modules is see in other thread) ?
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on have about the same power as old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Fallingwater said:
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on *have* about the same power of old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Click to expand...
Click to collapse
Try flashing it to another hard drive, insert both drives into the computer, and and at the grub menu press alt, and add "install=1 debug=" (without the quotes of course, and debug should have no character whatsoever afer the equals.
After installing from the second hard drive to the first, turn off the computer, remove the second hard drive, and boot up the conputer.
I hope this works for you.
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Flemischguy said:
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Click to expand...
Click to collapse
No need for windows, however it makes things easier for flashing it on the flash drive.
My recommendation, though, is to use the flash drive as an installer: according to what I had written above, install Remix OS to a hard drive from the flash drive.
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Fallingwater said:
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Click to expand...
Click to collapse
Not much, unfortunately.
However, perhaps a BIOS update will help.
It's already updated to the newest revision.
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Fallingwater said:
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Click to expand...
Click to collapse
Alright, I hope it'll work then.
I had Android 6 (Marshmallow) pre installed. With this version I was able to use external USB sticks and other devices (like a US Mause or a USB Keyboard). But after I flashed Eragon ROM the USB-C port no longer poweres external USB devices. Is there a hidden configuration I didndt notice? Or is this just my fault cause the cause is obvisios? Also Eragon Rom v3 is based on Android 6 so I through it would be passible.
Seems nobody knows why... Can somebody ask Skeleton1911 (I have ot enough posts to do so). Also What about additional driver installing for other USb devices (WLAN stick, Headset, )
Hi guys I am new here and new to this whole rooting, custom ROM thing. This all started from a need of an android device to run an app for a motorcycle efi tuner. It connects through a USB cable and allows me to change some tuning parameters in the module. I have never owned an android device, but I did own a Kindle Fire 2. After doing some research I stumbled across tutorials on how to install CM and make it an android device....and that where I am at now.
I have successfully rooted and installed CM 11-20160815-NIGHTLY-otter2, android 4.4.4, Kernal version 3.0.72+
Now the problem I am facing is the use of the usb cable to link the tablet and module. I have a USB OTG cable and after some research it looked like I needed a powered cable, so I made one of those too. I have installed Stickmount, USB OTG helper and USB OTG Checker. Running the checker I see that my device has the USB OTG API.
The interesting part now is when I connect the powered cable to the module and Kindle it will open the app automatically but it says not connected. The weird part is that it detects it enough to open up the app. Also I have not been able to mount through stickmount.
I am not a developer and not familiar with a lot of the lingo so at this point I am stuck. I don't know what else to try its over my head at this point. A google search turns up very little on this, although I have seen youtube movies of it working so I guess its possible.
Any help would be greatly appreciated!
Anybody have any ideas? I don't have enough post to put this in the kindle forums is it possible for someone to move it there?
back to the top
Hello
I've got my hand on a BEISTA K107, a low end Android tab with Android 10.0 on it.
I'm trying to setup a photobooth but the tablet do not detect my DSLR when I plug it in USB. The tablet is supposed to be OTG compatible but It seems that it's not usb host compatible
Any idea how to correct that ?
I've try rooting it without success
@zeph
Support for USB host and/or USB accessory modes are ultimately dependant on the device's hardware, regardless of Android platform level.