I made this about... 2 years ago. I never shared it with anyone. As I recall, it runs Gnome with X11 or with Wayland utilizing android graphic drivers. If you run Wayland and want to use X11 it then uses XWayland. XWayland works, except for it only works with the first mouse click. I basically took as much sailfish stuff as I could and made it run on ArchLinux, this was with pulseaudio, and bluetooth I think, except I never did get hardware accelerated codecs to work (GST Droid). I also played with Hawaii.. http://hawaiios.org/download/distros/ Which is included, although it never ran that well. And weston is also an option to use with this, you can see this with the LightDM login screen. Remember this is 2 years old. If you upgrade pulse audio or anything else it might break everything because of the kernel and systemd and god knows what else.
Also, I don't currently have a touchpad to play with. If I recall this zip file has a kernel and a rootfs.tar.gz inside, and.. I am not sure what partition you stick it in, probably /dev/store/ubuntu... So.... Maybe when I get a touchpad, I can figure it out, or play with this again.
https://drive.google.com/open?id=0B0ERXWZfh_RJNlR3VHhiUmNra1E
Related
Know I know this seems far fetched and has nothing to do with android, but could I download a firmware update for my TV (which is installed via a USB flash drive) and extract it and replace the image files.
Most TVs seem to run on the same software so if they get it working for one, it should work for all.
I just think the ui is really ugly so I was just curious if anyone has ever tried such a thing.
McMichael96 said:
Know I know this seems far fetched and has nothing to do with android, but could I download a firmware update for my TV (which is installed via a USB flash drive) and extract it and replace the image files.
Most TVs seem to run on the same software so if they get it working for one, it should work for all.
I just think the ui is really ugly so I was just curious if anyone has ever tried such a thing.
Click to expand...
Click to collapse
Well, the reason you can mess around with Android is cause its open source. This TV software is very likely closed source. Not impossible, but much more difficult to modify. Ive never heard of it personally
You could buy something like an Odroid or those Chinese flash drives which have android pre-installed with them. Also you could try a raspberry pie with Android.
First off your TV's insides are almost certainly not standardized enough for such a thing. Second there just isn't really a demand for such a thing in the first place. Smart TVs already exist, as do USB smart TV dongles.
Wish we could flash a new TV into our watching room...
Frigging Samsung plasmas suck! fixed once under warranty same problem almost exactly a year later.
Bizz! You could just connect your android phone through HDMI too! Becomes a poor man's smart tv
Sent from my Nexus 4 using Tapatalk 2
Hey there. I have the Nook HD+ and was using Cyanogenmod 10.1 for a while. I very much enjoyed using it, but eventually ran into an issue I hope to get resolved someway. One of the main things I'd like to do with my tablet is use it for emulators and for that I'd like to use a wii remote. Now, the issue with that is, as some of you may know,wii remotes no longer connect to android as of 4.2 due to some bluetooth change. What I've found out is that the remote will sync to the standard Nook OS, due to it being 4.1 or whatever.
So I guess my question would be this. Is there a way to use cyanogenmod and still get the wiimote functionality in some form? Is it possible to dual boot or something along those lines? As in use the stock Nook OS for emulation and cyanogen for other uses. I'm not very experienced when it comes to working with phone ROMs and such. And when I did search for things about dual booting it was paired with heavy use of jargon and I couldn't make heads or tails of it. I'm really looking for options for things I could go about doing here.
Thanks for your time
hyperbolictowel said:
Hey there. I have the Nook HD+ and was using Cyanogenmod 10.1 for a while. I very much enjoyed using it, but eventually ran into an issue I hope to get resolved someway. One of the main things I'd like to do with my tablet is use it for emulators and for that I'd like to use a wii remote. Now, the issue with that is, as some of you may know,wii remotes no longer connect to android as of 4.2 due to some bluetooth change. What I've found out is that the remote will sync to the standard Nook OS, due to it being 4.1 or whatever.
So I guess my question would be this. Is there a way to use cyanogenmod and still get the wiimote functionality in some form? Is it possible to dual boot or something along those lines? As in use the stock Nook OS for emulation and cyanogen for other uses. I'm not very experienced when it comes to working with phone ROMs and such. And when I did search for things about dual booting it was paired with heavy use of jargon and I couldn't make heads or tails of it. I'm really looking for options for things I could go about doing here.
Thanks for your time
Click to expand...
Click to collapse
If CM10.1 (android 4.1) works with the wii remote, could you not go back to using that? What was the issue you mention running into?
In the development forum there are builds of CM10.1 and the latest stock OS that can run off an sd card rather than installing to the device, so you can have a kind of dual boot situation where you just pop the sd card in when you want to use that operating system. That might work for your situation.
hyperbolictowel said:
Hey there. I have the Nook HD+ and was using Cyanogenmod 10.1 for a while. I very much enjoyed using it, but eventually ran into an issue I hope to get resolved someway. One of the main things I'd like to do with my tablet is use it for emulators and for that I'd like to use a wii remote. Now, the issue with that is, as some of you may know,wii remotes no longer connect to android as of 4.2 due to some bluetooth change. What I've found out is that the remote will sync to the standard Nook OS, due to it being 4.1 or whatever.
So I guess my question would be this. Is there a way to use cyanogenmod and still get the wiimote functionality in some form? Is it possible to dual boot or something along those lines? As in use the stock Nook OS for emulation and cyanogen for other uses. I'm not very experienced when it comes to working with phone ROMs and such. And when I did search for things about dual booting it was paired with heavy use of jargon and I couldn't make heads or tails of it. I'm really looking for options for things I could go about doing here.
Thanks for your time
Click to expand...
Click to collapse
With the latest update ( 2.1.1 ), the stock Nook HD+ is ICS 4.0.4. Google broke Android's bluetooth support with Jellybean 4.2+, and CM and others are trying to fix it but with limited success. You can dual boot by running an alternate OS off of the SD Card. I run stock 2.1.1 from SD Card as per:
http://forum.xda-developers.com/showthread.php?t=2330083
With a supported 16/32GB SD Card you can have plenty of room for all kinds of roms for emulators.
However, I would rather not use the WiiMote for emulators. Rather, GameStop has a $9.99 bluetooth wireless controller for Android Tablets that purportedly still works with CM 10.1/2 and has analog sticks and all. I plan to get one of those, but they are sold out online and I just haven't made the trek to a GameStop that has them....
Gamestop no longer has those blu tooth controllers, but the gamestop red samurai
works very well...I just got one a few weeks ago. $ 19.99
Hi,
I want to install XBMC on my Raspberry Pi B model. I have done that sometime in the past, but at that time XBMC was very unstable and it was crashing a lot. So, has anyone recently installed XBMC? If so, does it have any stability issues? Is it running smoothly (performance-wise)?
If you faced anything strange please let me know...
Do some research on Raspbmc, xbian and openelec. I run Openelec hard wired to a NAS without any issues. From rrading the foruns most issues come about because of special requirements and customisations (where the user lacks the skills/knowledge) run stock and its a pretty sweet media centre for the price tag.
Raspbmc
I've used Raspbmc with great success. It's optimised for running xbmc on the Pi and I've found it fast considering the hardware it's running on.
It's very easy to set up and playback is very smooth over wired ethernet.
A couple of my non-techie mates use it daily without problem.
I can't comment on other solutions as I've not tried them.
I'm in a similar boat - about to set up a new B+ for both my kids to use in their education and also as a "secondary" (although I can see it being the default day to day) configuration as a media player for my dumb TV.
From the research I've done so far, currently (overclocked) OpenElec seems to be slightly recommended against XBian, with RaspBMC a bit behind that. But all the reviews and websites seem to indicate that all three will do the job fine, with the recommendations being from ease of set-up and how "cutting edge" they are in terms of maintenance and improvement. And also that each tend to get boosted at their updates so the lead changes quite regularly.
In my case I think I'm going to set up one SD card for the kids with Raspian and stuff like Scratch and maybe Python etc, with a second card dedicated to media use and swap them out when the usage changes over. That way I can nuke from orbit and play around on the media side without affecting their set-ups at all.
One of the better comparisons sites I saw was the links below (and the pages linked from them):
http://www.htpcbeginner.com/overclocked-openelec-vs-xbian-raspberry-pi/
http://www.htpcbeginner.com/raspbmc-vs-openelec-comparison-2014/
http://www.htpcbeginner.com/raspbmc-vs-openelec-comparison-2014/
I prefer openELEC. I set it up so that the USB drive was the root device so I had more storage and so I can safely overclock without corrupting my SD card
Hey Guys
First of all: I realize that this is a rather long text, so I appreciate the effort of everyone who is going to read it!
Also, I asked a questions about 2 weeks ago, which was related to this topic, but was very specific about android wear (which I gave up on since then!).
So, actual post:
I want to build, or already am building an informational system for my motorcycle.
As the result of my work, I imagine a display (about 7 inches) in the dash of my motorcycle. It shall display information from my Smartphone (for example notifications about incoming calls etc.) as well as giving me the possibility to control the music on the smartphone (Android 5.1).
Also, I want to display further information, like speed, average speed, altitude etc. (hope you got the idea, basically just an advanced trip computer).
I started developing something, but ran into issues. I will explain my two concepts or ideas I had so far and explain, what the issues were I ran into. I then hope, that somebody here has a solution for my problem (which includes recommending hard- and software).
Firstly about my skills: I am experienced in programming "low level hardware", like Atmel's AVR Series (in plain old C) and developing the associated hardware for it. Also making custom pcb's at home isn't a problem for me, as long it doesn't come to some fancy BGA or SMD packages
On the programming side I am experienced the most in Java (and Android, which is basically Java of course). I know also C# and the .NET framework.
But I am willing to learn something new
The two ideas I had so far differed on the way how I wanted to let the raspberry pi (which I wanted to place in the cockpit) communicate with the smartphone.
In both concepts, I planned to have a raspberry pi with attached display in the cockpit on which I wanted to run a JavaFX application (already started programing). This application would then communicate with the smartphone over:
Idea 1: Java serialization:
I wanted to communicate over command objects. So for example I'd have an object for asking the altitude from the smartphone.
I'd then serialize this command object on the pi's side and deserialize on the smartphone. This isn't a problem, because there's java on either side (already got that piece working).
The smartphone would, after receiving and deserializing the object, get the actual altitude from the GPS sensor, pack the result in an answer-object, serialize it and send it back to the pi.
The issues I ran into were the following:
-Java Bluetooth library: I wasn't able to find a good, up-to-date, java library for communicate over Bluetooth in java. I then stuck to RXTX Library which did the job, but I always had the feeling of doing something "not so good". In particular I didn't want to just write on a COM-Port (which is emulated from the Bluetooth-module), because I had the feeling that COM-Ports may change after reboots if the OS feels like it, and I didn't want to build something which needed constant "tinkering". Also, writing to COM-Ports in 2015 just feels wrong, but this may be my personal problem
Idea 2: HTTP and Web Sockets
The basic idea was to have a webserver running on the smartphone and offering a REST-like API which I could access from the pi.
I also got this concept working, like so:
By using the NanoHTTPD library (from github) I was able to start a webserver on the android device. When then someone issued a POST-request on, for example, <IP>:<port>/api/music/next, the WebServer would receive this request and switch to the next song.
Actualizing data on the pi which changes often, for example the altitude, would have been achieved by using a WebSocket connection between the Java-App on the pi and the android webserver (which I also got to work).
I figured out that it would be a power consumption problem to let the smartphone offer a wifi hotspot (I don't want to have to connect the smartphone to cables on the motorcycle), so I decided to let the pi start a wifi access point (which isn't a power problem, because the pi is connected to on-board-power of the motorcycle).
However I then realized that the smartphone won't connect to an access point which doesn't offer internet access but only LAN-access.
And even if there was a way to force the smartphone to let it connect anyways, it isn't guaranteed that this will work too on future devices. And: The whole notification-stuff would have been needless, because as long as the smartphone is connected to a "dead-end wifi", it wouldn't receive emails or whatsapp-messages.
Idea 3: Using Bluetooth low energy:
It seems like the new, modern way, to let devices communicate over Bluetooth is to use Bluetooth low energy (BLE). (But I never worked with it before!).
However, there seems to be little to no support on raspberry pi for it, and it seems to be impossible to find a library for java which helps in using BLE. (If anyone knows one, please let me know).
I then thought about replacing the raspberry pi with an android board, because android has support for BLE. But I wasn't able to find a board which is supported from android 5.1+ and offers support for BLE. Even the Odroid-boards don't seem to support android >4.4 and BLE.
Summary:
In general I liked the second and third option much better. It seemed to be the the more versatile, modern way. The first way felt a bit like a hack.
However I found those problems I presented above, and until now, I couldn't think of a way around it.
If anyone here:
1) Solved this problem already
2) Knows a really good, NON-HACKY, community supported, Java (BLE) Bluetooth library
3) Knows a language or framework which would be well suited to solve the problem
4) Has another good idea how to solve it
Please let me know!
I just want to build something sophisticated, (which I could maybe make an open source project out of it) which isn't hacky.
I mean, the problem has to be solvable, look at the Pebble smartwatch. They also solved it without android wear.
I really want to emphasise that this is an open question. I am not limited / fixed on Java, Raspberry pi or anything.
I those have two requirements.
1) I don't want to connect the smartphone to a cable, either for data or for power
2) The solution needs to be something power saving, so no hotspot on the android device
3) Non-hacky, sophisticated solution
Best regards
Me =)
PS: As English isn't my native language, I maybe put some sentences wrong or wasn't able to express something clearly and unambiguous.
Please feel free to ask, I'd be pleased to clear any questions!
Any updates?
Hi!
I know this is an old thread, but I'm struggling with a similar issue - except I want to use it for roadcycling. Did you have any luck with your project?
All the best
Marius
Hello all!
So I've been using Mac for the last years and really enjoying it, but now wanted to use Linux (more specifically Fedora) as my main OS, rather than MacOS.
The machine for doing so it's a late 2013 15" MacbookPro with NVIDIA graphics.
For getting everything setup it took a while as a lot of drivers are proprietary, but manage to get most things working (expect for sleep, that for an unknown reason is broken and the Mac takes more than 5 min to wake from sleep, and FaceTime camera not working).
The problem however is that the machine is using the NVIDIA GPU, which causes it to get very toasty and drain battery faster.
I would like to enable the iGPU, but keep the NVIDIA GPU available as sometimes I connect an external monitor using the HDMI port.
I am newbie to Linux and have little knowledge but want to try everything possible to make Fedora work as best as possible on my computer. The procedures I tried were:
-Install rEFIND and try to use an set_apple.efi thing but probably did it wrong and did not work,
-Try to modify NVRAM variables to make the mac use the iGPU by default, but when booting to Fedora still only show up the NVIDIA GPU
Any help is welcome, bur please don't say for me to stay on MacOS or that is impossible as I read from people who manage to succored.
Thanks in advance!