Database Develop

aircrack -ng on android

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! 

Official Froyo devkit available for Download onTI website

Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.

Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!

Canadoc said:
Wow this could be just what we need!!!
Plus maybe the CM7 folk can port this over to gingerbread and deeperblue to honeycomb then we can have a true daily driver tablet as I believe these were the rate limiting steps!!!
Click to expand...
Click to collapse
Kind of neat how these things pop up...
Glad to be on board with the Nook!

Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post. I have been checking the TI developer site and noticed that they just posted an official android Froyo devkit available for download. the link is:
software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html
and the documentation is at:
/processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide
The source code is included and has new drivers for the SGX chip and a devkit for the WL1271 including bluetooth stack.
Also the kit include drivers for the DSP for video decoding and Flash acceleration in android.
I think this could be good to allow update to nookie froyo. I am in the process of testing the release on an OMAP 3530 dev board and will let you know.
Click to expand...
Click to collapse
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...

Thanks for posting. I'll take a look when I get home.

aludal said:
Lack of OMAP36xx as supported platform (read: NC) by this release is kinda disconcerting...
Click to expand...
Click to collapse
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.

Thanks for the info - looking at it, and i do see things like the OMAP3630 stuff in there, so this may every well be a useable Kernel for Froyo. Hot damn, maybe i will try my hand at compiling again (or if we are more lucky, dalingrin will find useful stuff, and really knock our socks off. )

Fifcic said:
The thing to understand is that all the OMAP 3 serires share the same software register interface. the part numbering is based on generation and intended market:
OMAP34xx: High Volume ODM 65nm
OMAP35xx: Embedded Low volume customers (same features as OMAP34xx)
OMAP36xx: High Volume ODM 45nm (Higher clock speed, SGX double clock speed)
AM37xx and DM 37xx: Embedded low volume customers (same features as OMAP36xx)
if you look at the release. this is intended for non ODM customers and enthousiasts access to the SDK they provide to their high volume customer. this is why the OMAP 34and 36 are not mentioned. TI provides them different SDK. the important part is that this provides a stable hardware accelerated kernel with drivers to the comunity.
the OMAP 3621 is an OMAP 3630 nutered. it has the same core but the pins to support pop memory and camera interface are not conected. It is still very powerfull as it still has the DSP and SGX core inside.
I hope this helps.
Click to expand...
Click to collapse
Updated drivers/dsp, updated linux kernel and bluetooth stack! This should really make for some interesting progress with nookie froyo, BT support, CM7 and possibly even the honeycomb builds

Assuming this kernel can be made to work, yes, it should really help. Some of the thing that i was looking for that are in the eclair kernel are missing (some of the OMAP stuff specific to our hardware), though, it may be a case of taking them and dropping them in. Either way, i hope this help, as i am dying to see our hardware put to better use.

Shouldn't this be in the development thread?

haganme said:
Shouldn't this be in the development thread?
Click to expand...
Click to collapse
Fifcic said:
Hello.
I am sorry I could not post on the development thread. this is my first post.
Click to expand...
Click to collapse
Yes, but new people to the forum can't post in Dev subforum until we have 10 posts.

Somebody had linked to this thread in the Dev forum, and for some reason, the mods closed it. OK, maybe we don't need two threads, but this really should be in the dev forum. It will get more attention there, and will hopefully be seen by those who need to see it..

I linked it as i thought more devs would see it there. Got a slightly rude post in reply that devs read both so.....

Indeed, i saw that, and it was uncalled for. Fact is, this is a dev thread, and should be there. Yes, a dev MAY read this forum, but truly, I don't expect them to, and things like this need to be as visible as possible - this is not the forum for that.

So.. any actual dev care to give feedback on the usefulness of this package, or are all the dev's handing out in just the dev forum still?

[KERNEL] Generic Android 3.0 kernel source

I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.

Ezekeel said:
I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.
Click to expand...
Click to collapse
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.

Lol Ezekeel, I've seen you praying Jean-Baptiste Queru for the Crespo-tree sources! I Think we have to wait one or two weeks...

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
Pretty much all the device-specific stuff is missing, but maybe we are lucky and no changes have to be made in the device-specific source for the Nexus S and we can simply keep these parts from our current code.

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?

Luxferro said:
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?
Click to expand...
Click to collapse
JBQ said that even if gpu is the same (omap4430) in galaxy nexus and in pandaboard he wasn't able to run the gnexus driver on the pandaboard and vice-versa because of some library-dependencies. So I think the drivers will not work out of the box...

awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.

Nice to know

simms22 said:
awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.
Click to expand...
Click to collapse
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App

matt2053 said:
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.

Maximilian Mary said:
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.
Click to expand...
Click to collapse
In one of the google groups replies JBQ said that they will always focus on the flagship phone.
Up until recently that was Nexus S.
Now the torch was passed and it's Galaxy Nexus first.
They will not dull the luster of their flagship phone by making libs and drivers for released phones available before the flagship phone has had time to shine.

I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
That will be a huge effort to fix, and it would probably cause more harm than good if you managed to fix the conflicts. I'm sure we'll have our sources in one/two weeks tops, so that's not worth the hassle in my opinion.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?

dvgrhl said:
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?
Click to expand...
Click to collapse
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.

Ezekeel said:
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.
Click to expand...
Click to collapse
First thanks for opening this thread, is a good idea.
At this moment I will wait some days to see if the crespo kernel 3.0 goes into public git, otherwise I will join the project to move the kenel since it will have multiple benefits.
Kalim

[Petition] For Nvidia to release tegra2 sources

http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers

xilw3r said:
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
Click to expand...
Click to collapse
Note from Nvidia about drivers
Hello Android Development Community
We appreciate all the interest and passion surrounding the NVIDIA Tegra Platform and we take our support for the development community seriously. NVIDIA has been working with Google and Motorola to provide the open source community with the required drivers and other binary code to build full Android OS images for the Tegra 2 powered "Motorola Xoom". We expect Google to make those components available as part of the Android Open Source Project soon.
In addition, NVIDIA is working on a full release of Ice Cream Sandwich (ICS) for our Tegra 2 Dual Core and Tegra 3 Quad Core reference devices to be made available early next year. This release package will comprise of binary code, drivers developed on our reference platforms and any patches necessary to ensure stability & performance with ICS. We hope the open source community can leverage this release for their work on all Tegra devices.
Andrew Edelsten
Source: http://forum.xda-developers.com/showthread.php?t=1309620
These petitions are of no use. The only option we have is to wait.

i know i know... online petitions dont accomplish anything.. but i guess im just a bit desperate.
ive seen that statement and what troubles me is that it mainly concerns xoom which is actually using a different kind of tegra2, ventenara or sth like that whereas 2x has harmony tegra 2, so if nvidia releases drivers for xoom, we wont have much use of them

[Port Request] OUYA

I would like to see Ubuntu running native on OUYA but my knowledge about porting Linux of any kind to other devices is simply not existant.
Is there anyone able and willing to do it? I think it should be relatively easy to do if you use ubuntu touch for asus transformer infinity (tf700t) to start because it also uses tegra 3 t33 as SoC. The touch enviroment obviously doesn't have to work so if you got time left you could do a preinstalled with KDE for good performance experience.
If tools like CWM or a cyanogenmod are helpfull you should go to the OUYA section of this wonderfull forum, they are avaliable right now.
Thanks for reading. Klindworth

Klindworth said:
I would like to see Ubuntu running native on OUYA but my knowledge about porting Linux of any kind to other devices is simply not existant.
Is there anyone able and willing to do it? I think it should be relatively easy to do if you use ubuntu touch for asus transformer infinity (tf700t) to start because it also uses tegra 3 t33 as SoC. The touch enviroment obviously doesn't have to work so if you got time left you could do a preinstalled with KDE for good performance experience.
If tools like CWM or a cyanogenmod are helpfull you should go to the OUYA section of this wonderfull forum, they are avaliable right now.
Thanks for reading. Klindworth
Click to expand...
Click to collapse
Ubuntu touch was designed for Mobile devices.. OUYA requires you to have a display like a TV or a monitor, if you know where I'm going with this then what you're asking to be done is the same as running Android on a desktop. Just get the normal Ubuntu that's designed for desktops and laptops. Ubuntu touch is only for small devices.

There is no "normal" preinstalled Desktop version of ubuntu with bootloader out there for the OUYA.
Ubuntu touch is still a real linux just with a different kernel like the ARM server editions and another GUI optimized for touch
or am i mistaken?
The benefit of ubuntu touch is the optimized kernel for ARM SOCs like Tegra3 not OMAP 3 or OMAP 4 or the TI ARM structures. With a lot of time and reading and searching i think i should be able to compile one or i could use the kernels already made by canicoal.
Uninstall the touch stuff an installing an alternative GUI and so on shouldn't be the problem.
My biggest Problem is to get it running without an proper boot.img.
Ouya has, like other Android devices, no real bios or efi and the only way i know to change the OS is via ADB in combination with CWM an fastboot to change the system data and the boot.img.
So if anyone knows how to port it i (and many other ouya owners) would be really greatfull if someone would take the time to port a version of ubuntu to the ouya and ubuntu touch seems to be the easiest option.
A tutorial to boot any linux natively on ouya(not chroot or something like that) and change the bootloader would also do it but it would be a lot of work to write one for retards like me

Klindworth said:
There is no "normal" preinstalled Desktop version of ubuntu with bootloader out there for the OUYA.
Ubuntu touch is still a real linux just with a different kernel like the ARM server editions and another GUI optimized for touch
or am i mistaken?
The benefit of ubuntu touch is the optimized kernel for ARM SOCs like Tegra3 not OMAP 3 or OMAP 4 or the TI ARM structures. With a lot of time and reading and searching i think i should be able to compile one or i could use the kernels already made by canicoal.
Uninstall the touch stuff an installing an alternative GUI and so on shouldn't be the problem.
My biggest Problem is to get it running without an proper boot.img.
Ouya has, like other Android devices, no real bios or efi and the only way i know to change the OS is via ADB in combination with CWM an fastboot to change the system data and the boot.img.
So if anyone knows how to port it i (and many other ouya owners) would be really greatfull if someone would take the time to port a version of ubuntu to the ouya and ubuntu touch seems to be the easiest option.
A tutorial to boot any linux natively on ouya(not chroot or something like that) and change the bootloader would also do it but it would be a lot of work to write one for retards like me
Click to expand...
Click to collapse
Why would anyone want a mobile operating system on a device like that... Yes, Ubuntu Touch is still real Linux but if you wanna get an OS on OUYA that was designed for small screens and touch then be my guest.. And there already is Ubuntu desktop versions for ARM. You're better off getting the ARM version, stripping it down and putting a simple GUI.

Didn't find a Tegra3 optimized arm version yet and don't know which arm kernel version would be completely compatible. is a kernel optimized for cortex A9 enough? Link??
also the problem of no working bootloader still isn't solved.
would be fine with me if someone would port that. all i want is a working linux port for ouya

darkforester67 said:
Why would anyone want a mobile operating system on a device like that... Yes, Ubuntu Touch is still real Linux but if you wanna get an OS on OUYA that was designed for small screens and touch then be my guest.. And there already is Ubuntu desktop versions for ARM. You're better off getting the ARM version, stripping it down and putting a simple GUI.
Click to expand...
Click to collapse
I would like to point out he is saying to change the desktop environment to run something more desktop friendly
Although the only environment I know of is a buggy version of unity from the Ubuntu ARM days...there might be gnome as well, if you look through the Backtrack and Kali sources
Sent from my Barnes & Noble Nook Tablet using xda app-developers app

Klindworth said:
Didn't find a Tegra3 optimized arm version yet and don't know which arm kernel version would be completely compatible. is a kernel optimized for cortex A9 enough? Link??
also the problem of no working bootloader still isn't solved.
would be fine with me if someone would port that. all i want is a working linux port for ouya
Click to expand...
Click to collapse
You're not going to find a version optimized for Tegra 3 on their site because Ubuntu already recognizes the chip..
I don't wanna sound like an a-hole but the idea is a bit far fetched.. the OS isn't even 100% stable, most core functions are working such as calling, wifi and other stuff.. but okay you get it to work right?, then what?, even if you use a GUI like GNOME which I doubt anybody is gonna want to port (since GNOME is made for desktops and laptops) you're still gonna be very limited. Plus does Ubuntu touch even support HDMI output yet?. There's just too much work for this..

You're not going to find a version optimized for Tegra 3 on their site because Ubuntu already recognizes the chip..
Click to expand...
Click to collapse
maybe im dumb but i only find preinstalled ARM edition for servers with omap 3&4 architecture. would you please link the version you think is running? and do i need a boot.img modified for the ouya? if i need one, can you provide one or know somebody who can do it?

Someone is getting close to bring fully functional native Debian to the OUYA. Can't wait until all mayor issues are fixed :victory:
http://tuomas.kulve.fi/blog/2013/08/11/debian-on-ouya/

Isn't it as easy as taking an iso and turning it into a cwm bootanle zop and adding controller support?
~~~~~~~~~~~~~~~~~~~~~~~~~
I am here to help and provide knowledge to help others with there problems/issues. If you do have a question don't be afraid to shoot me a PM and I will help you and put you in the right direction to the best of my ability and will get your problem and/or issue solved.
~~~~~~~~~~~~~~~~~~~~~~~~~

If you know how to do it try it and post the results. I think there should be some issues otherwise Linux distros for OUYA would be accessable and widely spread.
But knowing the issues could help someone else to figure out how to do it right. So, as I said, please try and post the results.