Did anyone continue or further develop Host mode for the Nexus? After seeing this:
http://www.androidpolice.com/2011/0...-canon-eos-from-your-android-phone-or-tablet/
I want it, incredibly bad. I haven't been able to find anything past that one guy that did it with 2.2 over a year ago, why does it seem that development on this completely ceased? I guess there really was only a specialized group that would really ever use it, but that's one super innovative use that has me extremely interested.
I'm currently on CM7 (and love it), but this is so freaking cool to me I'm actually semi-considering downgrading... please don't make me downgrade, and instead tell me that USB Host mode development on the Nexus one has made it to gingerbread...
I was about to post the same question! I'll be following this thread with interest.
Can someone please explain the limitation that prevents the N1 working as-is with USB host anyway? My (admittedly very vague) understanding is that the N1 hardware isn't able to supply the necessary power to the external device, hence USB Host support is disabled in the kernel for the N1 at compile time. Am I close?
Well now that it's been moved out of the development sub-forum I'm not sure if i'll get any developers to chime in... but for the first time in almost a year and a half that I've had my Nexus One, I actually want a new phone I wonder if it'll work with tablets seeing as how some of them have host mode enabled in honeycomb...
AFAIK, you'll be getting OTG capabilities in Ice Cream Sandwich.
Related
So the blogger over at 'Android and me' has speculated that older devices will not receive the 2.0 update.
This guy has done this before, he also said 1.6 was too big for the G1 OS partition and of course we all know this was wrong.
I want to know what the dev's think, once all the bull**** is striped and the 2.0 source code is at stock for the G1. How large will it be? And how much room will be left over for downloading apps?
Thank you for your time.
And how much room will be left over for downloading apps?
Click to expand...
Click to collapse
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.
vixsandlee said:
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.
Click to expand...
Click to collapse
I know, I know... I had 2.0 running for a time and it was great. I used apsd and linux-swap. What i want to know is conclusive evidence that the guy over at Android and me is full of ****.
He always speculates that the G1 will not get updates and is usually wrong. What i am wondering is how large the stock 2.0 for the G1 will be. The Dev's may have an idea.
the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.
Both htc and t-mobile have officially stated that the dream is still getting the 2.0 upgrade. As somebody else said, the point is moot for rooted users because we can always port the newer code to our aging phones, but there's a hitch: the moment htc stops supporting the device, we're on our own.
I've yet to see somebody build the android code for the dream without help from the pre-configurations found in the aosp for dream, and now that the sapphire is officially the adp2, i smell the demise of the dream near.
The biggest enabler of the custom firmware movement was the fact that the dream was also the adp1, so there was a lot of interest on making building the platform easy. We just piggybacked on that.
Take one look at has been accomplished with the hero so far. I still remember the whole "let's make htc give us our hero kernel code" because all thought it would open the door for custom hero firmware. they couldnt have been more wrong. without htc's support, all they got was a fancy linux kernel that they had no idea what to do with, and also discovered how little the kernel had to do with android.
There's now a grand total of two aosp roms for the hero, and they're both so broken that they're really just novelties.
What I'm going at is that once htc drops the dream, people are going to realize knowing linux will only take you so far and you'll have to know android if you plan to get at least a botched android build working on the device.
So eventually, even being rooted will not be enough to ensure continued ability to run the best and latest, unless, ofcourse, we get real devs (again, I'm not claiming to be one myself) in here.
Oh, and.... a bigger android install wont mean less app space... learn to android...
The android system belongs in the 70 mb system partition and, on a factory, official build, doesnt spill into the /data partition where you install your apps. And if you do have root and a2sd, what do you care how big the system is, you can always make your ext bigger, so it should't be a worry for a rooted user.
Really... learn 2 android...
s15274n said:
the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.
Click to expand...
Click to collapse
You know that the guy at Android and Me has been wrong on this exact issue before right?
When 1.6 was still in the pipes he had a pie chart and everything explaining why it was physically impossible for 1.6 to fit on a G1 (non-rooted). Then 1.6 was pushed to everyone....
http://androidandme.com/2009/08/news/t-mobile-g1-owners-dont-expect-any-future-android-updates/
^^
He was using his best guess at the time after speaking with t-mo, htc and the lead developer from google. He also assumed we would get a VERSION of OS 1.6. Everything he stated then seemed logical... don't fault the guy for not predicting the future man.
What it all boils down to is this;
Whether a device will get an update or not has virtually NOTHING to do with the device specifications and/or storage space. There is LOTS of space available on the device, despite what some chicken little's speculate based on a moronic look at the "free space in /system" (which has VERY little meaning). What determines whether a device will get a particular update or not has everything to do with what the MANUFACTURER WANTS TO DO.
In other words, this is *all* in the hands of HTC. Even tmobile has hardly anything to do with this since tmobile themselves don't have the source for the proprietary binaries (which happens to be the stumbling block) -- although tmobile can say "not for ours" if they want, HTC can still build the binaries and/or system image for DREAM/ADP1. Fully in their hands and nobody else's.
Which leads to a couple of options for updates;
1) modify the current state of AOSP to remain compatible with existing HTC binaries,
2) reverse engineer HTC proprietary binaries so they're no longer needed.
I vote for #2. The replicant project seems to have this aim, but I don't know if they are still alive or if they died along with the open android alliance... http://trac.osuosl.org/trac/replicant/wiki
How they getting this port before Nexus One? What's up with that?
http://androidcommunity.com/unofficial-gingerbread-port-for-droid-x-available-now-20101212/
"Unofficial" - means, compiled from SDK, using hacks for HW support.
I guess nobody wants to do the same hacks for Nexus, given that it's the first in line to receive the proper official update.
Like Jack_R1 said, it's pretty pointless since we get the proper update pretty soon after while it will probably take months for the other phones. Also, the hacked SDK-image is basically so limited and slow that it's unusable for more than playing around a few minutes.
Has anyone successfully attached and used a wired Usb keyboard. I've searched thoroughly but haven't seen it specifically answered.
The only references seem to be regarding the potential blue-tooth capabilities, news that we all anxiously await. But I'm interested only in a wired...or possibly a wifi solution. at this time. I know that it has been done on an HTC android, and they speculated that it should be possible on most android phones but I haven't seen this confirmed for the nook color. I only ask because I would have to buy (arrggg.....spend money, deep breaths, deep breaths) and would like to be sure before making any purchases, thanks.
Seeing that the Evo will most likely never get stable USB host support I have abandon future projects on the Evo and am looking at expanding the Atrix/Photon feature set. I'm looking to work with a dev on external touchscreen support for the Atrix/Photon platform as well as other possible USB devices.
Granted, I have a the "CDMA Atrix" a.k.a. Photon but drivers should be easy to port and would benefit both devices. If I can get some devs on board we can nail down hardware specifics and other details later. I won't go into detail here as to what the end results will be but devs feel free to PM me with any questions. Hopefully there will be more dev involvement than the Evo Desktop had.
I am seeking a similar solution, i would like to run my Atrix as a car-pc with a 7 inch touch screen in dash. Please keep us updated!
Lokifish Marz said:
Seeing that the Evo will most likely never get stable USB host support I have abandon future projects on the Evo and am looking at expanding the Atrix/Photon feature set. I'm looking to work with a dev on external touchscreen support for the Atrix/Photon platform as well as other possible USB devices.
Granted, I have a the "CDMA Atrix" a.k.a. Photon but drivers should be easy to port and would benefit both devices. If I can get some devs on board we can nail down hardware specifics and other details later. I won't go into detail here as to what the end results will be but devs feel free to PM me with any questions. Hopefully there will be more dev involvement than the Evo Desktop had.
Click to expand...
Click to collapse
Basically there should be no porting needed. Atrix and Photon kernels are 99.99% the same and just differ in build configuration.
I thought to do this exact same thing as it makes tremendous sense. Everything already on the phone. Could be implemented very easily with the multimedia dock or even the car dock that enters the Photon into navigation mode automagically.
Have you tried the touch screen USB support yet?
Hi, so the other day my USB contact broke on my 920 which forced me to switch to a SGS4 while waiting for to get fixed, which made me think about the possibility to port WP to new hardware, in this case specifically the SGS4.
So I was just wondering what we would have to do for Windows Phone to boot on the S4? I know C, C++, C# (plus some more languages which aren't relevant to this idea).
I mean they got WP7 to boot on the HD2 so its not *impossible* right?
filfat said:
Hi, so the other day my USB contact broke on my 920 which forced me to switch to a SGS4 while waiting for to get fixed, which made me think about the possibility to port WP to new hardware, in this case specifically the SGS4.
So I was just wondering what we would have to do for Windows Phone to boot on the S4? I know C, C++, C# (plus some more languages which aren't relevant to this idea).
I mean they got WP7 to boot on the HD2 so its not *impossible* right?
Click to expand...
Click to collapse
1) However it's VERY HARD.
2) If your S4 has Exynos you can forget about WP.
3) HD2 is almost a SINGLE positive example.
Porting such close-source OS to other device is a LEGENDARY task. Too much work.
-W_O_L_F- said:
1) However it's VERY HARD.
2) If your S4 has Exynos you can forget about WP.
3) HD2 is almost a SINGLE positive example.
Porting such close-source OS to other device is a LEGENDARY task. Too much work.
Click to expand...
Click to collapse
Yes I understand that porting WPA would be above "a hard task" however, I'm still interested in seeing where we are stuck. I don't expect to be able to do anything but getting a better understanding of the scene will help drastically in understanding what I need to learn to be able to accept such a task
Also, I mean WPA in general so 7 would work to learn more about
filfat said:
Yes I understand that porting WPA would be above "a hard task" however, I'm still interested in seeing where we are stuck. I don't expect to be able to do anything but getting a better understanding of the scene will help drastically in understanding what I need to learn to be able to accept such a task
Also, I mean WPA in general so 7 would work to learn more about
Click to expand...
Click to collapse
You need to write bootloader and all drivers for HW. And you don't have SDK for it.
filfat said:
Hi, so the other day my USB contact broke on my 920 which forced me to switch to a SGS4 while waiting for to get fixed, which made me think about the possibility to port WP to new hardware, in this case specifically the SGS4.
So I was just wondering what we would have to do for Windows Phone to boot on the S4? I know C, C++, C# (plus some more languages which aren't relevant to this idea).
I mean they got WP7 to boot on the HD2 so its not *impossible* right?
Click to expand...
Click to collapse
Please search before posting (rule #1). This is one of the many, "Hey can we port Android to WP because of similar hardware?". These questions have been asked numerous times and many threads have been opened with the same subject... The explanation of the difficulty has been given multiple times.
With that said, I'll be closing this thread.