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?
Related
Can we make this a sticky post where the end status of the Kaiser Video driver development stands?
Where does it stand? Has anyone started work on it? How do we get ahold of the information required for developing the driver? Can we determine if the development for this driver is even possible? (Is the hardware completely set up to handle it? Maybe there are hardware design hurdles which makes it impossible to be done - that HTC knows about but cannot or will not currently tell us? Even if the chipset is up to it, maybe there is some other piece of hardware missing like an additional circuit left out? How can we determine this for sure and get the work on this started?
Let's make this a sticky post and only those with specific information should post here...
What pieces of hardware are required for a developer to work on this driver development issue? I am willing to part with my older units (for a price, I was going to sell them) if that would help the effort: (O2 XDA/O2 XDA II/Cingular 8525) - what specific models support this chipset so we know what hardware can be used for the development effort?
There are three sticky posts on the subject of video drivers already - are these needs not met by the Video driver project thread - http://forum.xda-developers.com/showthread.php?t=355345 ?
But not the current status
But not the current status in one place that is easy to find. Maybe there should be a sticky post with only one postingvand only updated - not added to - from time to time - only by the forum admin...
Developing new drivers from the ground up won't happen anytime soon. It's a massive undertaking and I bet much too much even for the fine people here.
Even "stealing" drivers from similair hardware has proven very difficult, though it's most probably possible.
I think our best chance would be if HTC releases a device with MSM 7200/7500 and they deliver it with drivers, then it would probably be a fairly easy task.
As for the hardware the only two things that come to mind would be if HTC bought cost reduced chipsets with non-functional Imageon hardware (if for an example there's a problem with yields and Qualcomm has a stock of partially broken chipsets) or if Qualcomm has different SKUs of the same chipset which they artificially handicap by disbling certain hardware (and thus ell them cheaper).
None of the two theories above are that far fetched actually.
Hardware manufacturers often artificially create multiple SKUs by disabling features in a high end product. (Perfect sample would be CD/DVD burners that are firmware capped to a lower speed that the hardware can actually manage.)
Sma ething happens with videocards. When Radeon 9500 was launched the chip on those boards were actually 9700 chips but with non-functional hardware units (and when ATi were out of those they actually started capping 9700 chips that were 100 % operational).
As for the exact current status I believe the only person who really gave this a try was Chainfire who tried to make the LG KS20 drivers work on a Kaiser without any luck. SO I guess the status is still att 0 % so to speak.
KruseLudsMobile said:
But not the current status in one place that is easy to find. Maybe there should be a sticky post with only one postingvand only updated - not added to - from time to time - only by the forum admin...
Click to expand...
Click to collapse
yes, thats a good idea.
Really there are way too many threads dealing with these issues. Two or three new ones at least pop up every day. As far as I know, there is currently nobody actually working on the drivers. I was, but after putting about a 100 hours in porting the LG KS20 drivers, ultimately without success, I focussed my efforts towards the website. Porting these drivers is most likely not impossible, but it's not an easy task and I personally only know of one person here on XDA who may possibly pull it off and this person does not have one of the affected devices, and even if she did, it might still take a long time to do.
In the meantime, progress is being made with the website, news coverage everywhere, and a lot going on behind the scenes that we honestly cannot say 'out loud'.
Let's first see what the update HTC keeps telling us about brings. And if you need to get rid of bounty money, I would say giving a fair part of it to those of us who have put all this effort and time into making it happen would not be unfair
Chainfire said:
Really there are way too many threads dealing with these issues. Two or three new ones at least pop up every day. As far as I know, there is currently nobody actually working on the drivers. I was, but after putting about a 100 hours in porting the LG KS20 drivers, ultimately without success, I focussed my efforts towards the website. Porting these drivers is most likely not impossible, but it's not an easy task and I personally only know of one person here on XDA who may possibly pull it off and this person does not have one of the affected devices, and even if she did, it might still take a long time to do.
In the meantime, progress is being made with the website, news coverage everywhere, and a lot going on behind the scenes that we honestly cannot say 'out loud'.
Let's first see what the update HTC keeps telling us about brings. And if you need to get rid of bounty money, I would say giving a fair part of it to those of us who have put all this effort and time into making it happen would not be unfair
Click to expand...
Click to collapse
not enough threads IMO
Guys, I can make this thread sticky too if you promise it'll be a catch-all thread, eferring to all the other, referred threads.
Is the g1 capable?
Lol how on earth would a g1 do that lol pointless post in the development section yet again ... look just go here http://www.aircrack-ng.org/
and post away as much as u like but Not In Here
nexx892 said:
Is the g1 capable?
Click to expand...
Click to collapse
would be sweet if someone can make it work..
i imagine it will be a battery killer
You would have to have the Debian OS installed on the side, which has been discussed on the forum many times. And then you'd have to run it on Debian. After hooking up the phones WiFi to Debian, which as far as I know, there aren't any Drivers made yet.
So, the G1 is capable, but it takes a great deal of work.
Not even mentioning the fact that it is illegal to crack the WiFi codes in some places...
Also, this is not a development question, it should be in Dream Q&A.
http://forum.xda-developers.com/showthread.php?t=508871
Aircrack for Android
Hi
Look just go here:
javapassionblog.blogspot.com/2011/06/aircrack-ng-su-android.html
As much as I would love it, no. I've been hunting this for a while myself. The G1 doesn't have Android drivers capable of monitor mode.
There is hope though. SHR Linux is a distro designed for phones. It started as an OS for the Openmoko Neo Freerunner and was planned to spread to more but it sucks on everything but the Freerunner and the G1.
http://www.shr-project.org/trac/wiki/Devices/HTCDream/InstallGuide
Anyway, SHR Linux uses the wl12xx driver, a mac80211-based driver for the wl1251 (the G1's wifi chip). Driver stability is sketchy but if we're lucky it'll go into monitor mode without crashing. The procedure to use the driver is written here: http://www.htc-linux.org/wiki/index.php?title=Dream#Core_Status
I haven't tried SHR Linux yet, it's on my list of stuff to do. I think I'll give a go today.
Before someone says "the chip doesn't support monitor mode", yes it does. Some guy made monitor+injection drivers for the N900 which uses the same wifi chip as the G1. Google "N900 bleeding edge wifi" if you want to see it, it's on his blog. 'Why can't we use this working driver for SHR/Debian/Android' you ask? Because that driver was designed for the Power Kernel mod of Maemo, but the driver would definitely help devs if they sought to get monitor mode from Android.
Slack
Don't forget about Backtrack's older versions as well (when we ran aircrack-ng through slackware)... BT had been using Slackware in some of the beginning releases of development and aircracl-ng ran beautifully.
Slackware has been around forever and has alson has a ARM based release of their distro for a little while now. I think it would be nice to see any of our devices running slackware and aircrack together, But who knows.
I liked BT better when it ran Slack anyways.
hellsdroid
http://forum.xda-developers.com/showthread.php?p=17750634 working aircrack-ng on g1
i have all this working with your fantastic tutorial and files provided and good links, but i have one problem, the resolution looks like it is set too high for the g1 480x320 res, and which buttons do you use to close airodump-ng to use aircrack-ng to crack the key??
Work in ZTE Racer in Android 2.1 yes or no
Hello Everybody!
I am using Galaxy S2 GT-I9100 and I can successfully run monitor mode on it with bcmon. I can run tools like reaver, aireplay-ng, aircrack-ng, airodump-ng and they all work perfectly, but I would really like to run airbase-ng, but when I try to run it, I got:
sh: airbase-ng: not found
Can anybody help me to get this tool working?
Thanks!
Hello
Title says it all.
Do you think it is possible to port Nokia's MaemoOS (www.maemo.org) from the new Nokia N900 to hTC devices?
Thanks for answers.
Sopis said:
Hello
Title says it all.
Do you think it is possible to port Nokia's MaemoOS (www.maemo.org) from the new Nokia N900 to hTC devices?
Thanks for answers.
Click to expand...
Click to collapse
Hi,
What are the difference with it and Winmo, Android,...?
that's hot!
im curious too about maemo...
i've taked a look on the web,but i found nothing....
It's Debian based running Hildon-Desktop on top...
With enough devs doesn't seem too hard to port, we already got Linux Kernel running on some PDA's it's mostly an Hildon-Desktop doing the rest.
Would be interesting indeed, I am currently waiting for Android to the HD, but Maemo would be nice too ! And I think I am not the only one.
Sopis said:
Hello
Title says it all.
Do you think it is possible to port Nokia's MaemoOS (www.maemo.org) from the new Nokia N900 to hTC devices?
Thanks for answers.
Click to expand...
Click to collapse
There is community driven edition of Maemo called Mer. It is fully open source and it should in theory be possible to run it on blackstones at the moment. But it is not that usable/fully polished as Maemo 5 on Nokia n900. HTC Touch Pro is already mentioned on http://wiki.maemo.org/Mer/Status.
PS. I'm following UPS delivery of my n900, will have it on monday
Don't forget that the N900 is a really powerfull device with alot more "oempf" then our HD's.
I think that as an linux distributable, android is allot more qaulified for our HD's then Meamo will ever be
Thank you all for very good replies
I did not think that this would make such an interest...hope more people will read this and maybe some DEVs too
probably yes, but given the time and effort required, it would be easier to just have people buy an n900. poeple choose a blackstone because they want winmo/tf3d or whatever
i like to think it like this - if someone found a way to attach a coffee machine to a blackstone, id be interested, but given the time and effort required to get it to work (not to mention practical) i wouldnt be too fussed. anyone who wanted coffee machine functionality might have bought the wrong device
id say lets android working first then maybe work on other linux OSs would be easier
A couple of things:
By default Mer uses LXDE as its desktop but you can switch to Hildon (the n900 UI) using update-alternatives (Google it).
However Hildon uses Clutter which uses GL, and it all runs on Xorg, so unless there's a hardware 3D driver for Xorg for your device you're going to be out of luck I think (unless you like horribly slow and jerky UIs). Afaik there isn't an accellerated 3D Xorg driver for Raphael. Not certain but pretty sure.
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.
I know that owners of the HTC HD2 are able to dual boot WP7 and Android on their phones--is it possible for this to be done on the Bionic?
IOS5?
I really just want to do this in order to show off my phone to all of my Apple fanboy friends. I also love the WP7 interface, and want to know if it's possible to get the real thing, not just Launcher7.
I've done some research and found a few projects dedicated to doing this, but no mention of phone compatibility, and nothing I would risk putting on my phone without some verification.
Part of the reason the HD2 was chosen for that was due to the large amount of hardware it shared with the EVO 4G. Also, HTC uses mostly stock Qualcomm parts in their phones. With the Bionic it would be more difficult, since Motorola doesn't make any WP7 phones, but since both are written to run on ARM CPUs it's theoretically possible. The hardest part would be drivers for the LTE modem, which is a proprietary Motorola part, and for the touchscreen. It would be a significant undertaking to say the least.
No. Windows Phone and iOS are closed source. There's no adapting them to the Bionic.
--
Sent from my Droid Bionic.