Android-x86 developments and issues
Re: Android-x86 developments and issues
I think what @L18L is highlighting is that -x86 is a root system to allow us to get some familiarity with Android as a platform using technology that's on your desk. Android, even rooted Android, is not like traditional OSes. Yes, it has a Linux base, but, it sharply departs to deliver UI responsiveness at fingertips/gestures in a very different way than used traditionally.
And, assuming development may be one's plan, 4.3 and kitkat most nearly match where Android is now going (very obvious in KitKat). It was not so obvious in prior releases.
Hope this helps
And, assuming development may be one's plan, 4.3 and kitkat most nearly match where Android is now going (very obvious in KitKat). It was not so obvious in prior releases.
Hope this helps
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: Android-x86 developments and issues
Exactly.gcmartin wrote:...system to allow us to get some familiarity with Android as a platform using technology that's on your desk.
... mouse and keyboard can be plugged in via USB on any recent tablet.
There is no need to use touch and gesture I think.
Another feature I have detected for me:
Speaking messages enabled in somewhere in preferences.
though there is no sound to hear but the text of the spoken words appear on red background at the bottom of the screen.
Really very useful.
Re: Android-x86 developments and issues
Also, working in reverse, it's easy to use remote desktop apps (Gmote, Splashtop, etc) on your tablet to run your PC using touch and gesture.L18L wrote: Exactly.
... mouse and keyboard can be plugged in via USB on any recent tablet.
There is no need to use touch and gesture I think.
Re: Android-x86 developments and issues
It's going where every other Google division is going:gcmartin wrote:And, assuming development may be one's plan, 4.3 and kitkat most nearly match where Android is now going (very obvious in KitKat). It was not so obvious in prior releases.
1. More insistent, intrusive involvement with your wallet and personal info
2. Compulsory integration with the widely spurned Google+
3. Simplifying the interface (at the expense of functionality) by adding layers of hidden control buttons on top of each other. Just keep piling on the bling until everything comes to a freezing halt. (That last pop-up doesn't close.)
4. Deprecating customizability in favor of standardization, indirectly creating another revenue stream to restore lost customizability.
5. Toolbars in ubiquity: Google coders love toolbars. Toolbars everywhere.
6. Carpal tunnel scrolling: Scroll into a void from which you never return (just close session and go someplace else)
http://arstechnica.com/gadgets/2013/11/ ... -reviewed/
I took a look at Dyle TV, and concluded that it only works with wireless on specific hardware, even when it promises a USB-enabled app in the near future. Does anyone know of an app to show broadcast TV on a wired-connected Android device?
https://play.google.com/store/apps/deta ... client.mcv
https://play.google.com/store/apps/deta ... client.mcv
Question
ARe you asking if there is a way to connect a DTV antenna-tuner to display content on an Android?
The offering you show is an app which will use one of these 2 receivers
But, if I understand the implementation, those are using a specifically tuned antenna to allow display of whatever the broadcasting location is licensed for. This is why you will only see a few of the local programming (TV stations) that the receivers get. The technology is seen in the 1st paragraph, here.
I did see another broadcast option about another US venture to broadcast to mobiles. In fact, as I remember, recently some broadcast content providers had tried to use the court system to shut them down.
Edited: added the Company which is sued for making broadcast content available
Which technology approach are you after?
ARe you asking if there is a way to connect a DTV antenna-tuner to display content on an Android?
The offering you show is an app which will use one of these 2 receivers
- Audiovox MobileTV Receiver
- Elgato EyeTV Mobile TV Tuner
But, if I understand the implementation, those are using a specifically tuned antenna to allow display of whatever the broadcasting location is licensed for. This is why you will only see a few of the local programming (TV stations) that the receivers get. The technology is seen in the 1st paragraph, here.
I did see another broadcast option about another US venture to broadcast to mobiles. In fact, as I remember, recently some broadcast content providers had tried to use the court system to shut them down.
Edited: added the Company which is sued for making broadcast content available
Which technology approach are you after?
The second option is more interesting to me, essentially, streaming broadcast TV on computers, tablets and smartphones. I can see how this technology would irk broadcasters and traditional television vendors.
https://www.aereo.com/
https://www.aereo.com/
Android-x86 4.4 review – first Release Candidate
http://www.linuxbsdos.com/2014/02/17/an ... candidate/
http://www.replicant.us/
Fairphone: "A seriously cool smartphone that puts social values first"
http://www.fairphone.com/
CyanogenMod: an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android-based firmwares of vendors.
http://www.cyanogenmod.org/
http://www.linuxbsdos.com/2014/02/17/an ... candidate/
Replicant (Android fork, a free software project)Known issues
- Suspend and resume may not work on some systems.
- The installer can't format ext3 filesystem.
http://www.replicant.us/
Fairphone: "A seriously cool smartphone that puts social values first"
http://www.fairphone.com/
CyanogenMod: an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android-based firmwares of vendors.
http://www.cyanogenmod.org/
Last edited by nubc on Tue 18 Feb 2014, 15:50, edited 1 time in total.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
A really worth to read articlenubc wrote:Android-x86 4.4 review – first Release Candidate
http://www.linuxbsdos.com/2014/02/17/an ... candidate/
Thank you, nubc
Development Release: Android-x86 4.4 RC2
http://www.android-x86.org/releases/releasenote-4-4-rc2
http://www.android-x86.org/releases/releasenote-4-4-rc2
Update on android devices/touchscreens, etc.
I'm doing programming with no problems right on an Samsung Galaxy Note 8 loaded with Eclipse. I have a case with a bluetooth keyboard that works as well as my laptop keyboard. Re: handwriting, the SPen works as well as pen and paper. Printing: I'm using a Samsung Laser printer that connects with wifi-direct. It doesn't require any wifi connection, and prints everything..handwritten notes, office docs, web pages, etc. Applications: rapid evolution of professional applications. There's an excellent ongoing android programming course for $2 a month that comes with eclipse software. There's a lynx text browser developed for Android with active development with SSL (for gmail), switches for javascript, etc. Formats everything correctly...very fast, no ads, etc.
Impressive <bye>
I'm doing programming with no problems right on an Samsung Galaxy Note 8 loaded with Eclipse. I have a case with a bluetooth keyboard that works as well as my laptop keyboard. Re: handwriting, the SPen works as well as pen and paper. Printing: I'm using a Samsung Laser printer that connects with wifi-direct. It doesn't require any wifi connection, and prints everything..handwritten notes, office docs, web pages, etc. Applications: rapid evolution of professional applications. There's an excellent ongoing android programming course for $2 a month that comes with eclipse software. There's a lynx text browser developed for Android with active development with SSL (for gmail), switches for javascript, etc. Formats everything correctly...very fast, no ads, etc.
Impressive <bye>
Android-x86 4.4-r1 (KitKat-x86) 8/08/2014
http://www.android-x86.org/releases/releasenote-4-4-r1
http://www.android-x86.org/releases/releasenote-4-4-r1
I find the versioning system to be confusing. In a recent post, the Android-x86 team announced release of Android-x86 4.4-RC2 (KitKat-x86) 5/20/2014, and now this announcement for Android-x86 4.4-rc1 (KitKat-x86) 8/08/2014. Notice the capitalization of RC in the previous release annoucement.The Android-x86.org is glad to announce the 4.4-r1 release to public. This is the first stable release Android-x86 4.4 (kitkat-x86). The 4.4-r1 release is based on the Android 4.4.2 (KitKat-MR1 release). We have fixed and added x86 specified code to let the system runs smoothly on x86 platforms, especially for tablets and netbooks. A live CD ISO [343 MB] is available for download.
I have an ASUS eeePC 4G, 900 MHz Celeron, 4GB SSD. 512MB DDR2. It is currently running Android-x86_4.0 Ice Cream Sandwich. Despite best efforts, both Chrome and Firefox for Android are spontaneously closing, and thus inoperable. What is the most recent version of Android-x86 that will work well on my eeePC? A primary consideration is the kernel version. I assume that the latest version of Android with kernel 3.0.x might lack retro drivers and be a poor choice of version. But I guess I'll give it a try anyway. The reason I chose to install an older version like Ice Cream Sandwich was that this was the last version of Android-x86 known to have su privileges.
The following OS installation attempts failed: Android-x86_4.4_r3, Android-x86_4.2, Android-x86_4.3, Wary 5.5, Slacko 5.5
And the winners are: Android-x86_4.0, Wary 5.1.1
I'm betting that some of the above failures are because of the placement of GRUB. While Android-x86_4.4_r3 did install successfully, I never saw the GRUB boot screen. Just got a white screen, some text, and then halted at command prompt. Any opinions or suggestions?
The following OS installation attempts failed: Android-x86_4.4_r3, Android-x86_4.2, Android-x86_4.3, Wary 5.5, Slacko 5.5
And the winners are: Android-x86_4.0, Wary 5.1.1
I'm betting that some of the above failures are because of the placement of GRUB. While Android-x86_4.4_r3 did install successfully, I never saw the GRUB boot screen. Just got a white screen, some text, and then halted at command prompt. Any opinions or suggestions?
Last edited by nubc on Sun 13 Sep 2015, 20:17, edited 1 time in total.
Problems booting the OS after GRUB instal
At the end of the installation of Android-x86_4.4, I was asked by the installer, Do I want it to install GRUB now. I clicked Yes. But the OS did not boot after restarting, despite its report that Android successfully installed, which is disappointing because this project was specifically intended for the eeePC. (It is noteworthy to mention that neither 4.4 nor 4.2 would run as live CD, but instead halt on inability to find files. BUT, Android did successfully install--just wouldn't boot.) Is there another way to install GRUB after Android-x86 finishes installing? Can I install GRUB from a Puppy live CD to accomplish this purpose?
I'm making some progress, if only to eliminate possibilities. After much thrashing about, here is GRUB Menu.lst
and here is the failed start of Android-x86_4.4_r3
Next step, I'll try to install Android-x86 4.2 Jelly Bean. Probably get the same result.
EDIT: What is this doing?
Code: Select all
# Linux bootable partition config begins
title Android-x86 4.4 r3 KitKat (on /dev/sda1)
root (hd0,0)
kernel /android-4.4-r3/kernel quiet root=/dev/ram0
androidboot.hardware=android_x86 SRC=/android-4.4-r3
initrd /android-4.4-r3/initrd.img
# Linux bootable partition config ends
Code: Select all
Starting up...
early console in decompress_kernel
Decompressing Linux... Parsing ELF... No relocation needed... done
Booting the kernel.
Detecting Android_x86...............................................................................................................
......................................................................................................................
.......................................................................................................................
EDIT: What is this doing?
Code: Select all
quiet root=/dev/ram0
Announcement: Android-86 Project has partnered with Remix OS
http://www.android-x86.org/changelog/partnership
http://www.jide.com/en/remixos-for-pc/announcement
I wonder if either of these projects have implemented hardwire or USB dongle ethernet connectivity.
http://www.android-x86.org/changelog/partnership
http://www.jide.com/en/remixos-for-pc/announcement
I wonder if either of these projects have implemented hardwire or USB dongle ethernet connectivity.
Last edited by nubc on Sat 05 Mar 2016, 09:34, edited 2 times in total.