Any word on getting around the Sprint blocks (error 67) on a stock-derived ROM? WiFi tether works fine, but I'd rather use USB since it is faster, more secure, less of a PIA, and saves battery on my phone and laptop. I'm looking for a real solution where the phone relays the PC's packets, not some janky solution that involves an application running on my computer and/or the phone changing packet headers.
I'll probably switch to Cyanogen when a stable build is out, but until then...
So, no one knows how to USB tether? Damn.
You want rndis. This has been in the Linux kernel since 2.6 or so, but I haven't seen a prebuilt kernel that has it enabled.
(I'm a Linux guy, not an Android guy, so take the following with a grain of salt...)
I've been trying to get this working, which I thought would be a fairly trivial task (Set up a cross-compiler, download the Samsung kernel sources, turn on iptables and rndis, build kernel and modules, copy over, and go home happy.)
What I've found is:
1) Setting up the toolchain and building the cross-compiler is easier than expected because folks have automated most of it. (Look up crosstool-ng... sexy!)
2) Downloading the Samsung sources is easier than expected; Samsung has 'em right on their web site.
3) Stepping into Samsung's kernel source tree is like walking into a horror movie. You can almost see little sticky notes reading "OK GUYS I GOT THIS THING WORKING, DON'T KNOW HOW, NOBODY TOUCH IT" hanging off things. Maybe I'm just spoiled by being used to kernel source trees where changes are vetted by committee.
Part of the problem is that the stock kernel that comes on the phone is not compiled with CONFIG_IKCONFIG_PROC (which would let you check out the config at /proc/config.gz), and extract_ikconfig doesn't like it either. (This means that instead of starting with a known-good configuration and changing things slowly from there, as you would on a Linux box, you get to start with a "sounds-good-to-me" configuration and hope it works, which is extra-fun given that a lot of the things Samsung added are undocumented (and occasionally unlabeled).
Anyway, I'm working on it, but just building a kernel has turned out to be nontrivial. Once I get the stock Samsung kernel compiling, getting rndis and iptables going should be pretty easy, even if the code for them has to be merged in (this stuff has been in the linux kernel forever).
As an update, I got Garwynn's newest community kernel to build using a somewhat modified config extracted from the whompasaurus kernel (which is Perseus) (I did that because I didn't want to make sure I had drivers for all the twiddles and bobs in whompasaurus). The new kernel is running great!
It turns out that a little kernel hacking is going to be involved for those who want RNDIS and the android gadget driver; config makes them mutually exclusive. It will bear some looking into to see why that is (it might not need to be set up that way). One of the gadgets excluded is the Samsung Exynos Superspeed USB 3.0 device, which I do not think is an issue for the Note 2, but could well be a deal breaker for upcoming Exynos 5 phones. I'm too tired to dig through all the drivers and see what exactly is being broken, but that would need to be done before I declared this to be a good tradeoff.
For now, I'm just going to build it with RNDIS and without android gadget, and see how my phone likes it (and how USB tethering works).
Late breaking update: The RNDIS code in the kernel appears broken. Looks like a scope-of-function problem (conflicting functions named rndis_bind_config); will hack it into submission tomorrow.
I was about to look to see how you can enable USB tether till I realized my wifi tether is just as fast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any updates, really need usb tether for my car stereo
Sent from my PG86100 using xda app-developers app
I tried to build kernels with all three RNDIS kernel drivers. I did some hacking to try to get the samsung gadget that includes RNDIS to build, but have stopped work on this because:
1) I think getting this to work would take a significant investment of time
2) Samsung has announced that my phone will get Android 5; Android 5 is supposed to be Linux 3.9.x; so any work I do now will be obsolete in a couple months.
Note that I am not talking about getting Sprint's paid tethering app to work; I am talking about using the native rndis support in the linux kernel. (Frankly, that's probably all theirs is too, but they got the driver to compile.
I want this to work too, but I am done messing with it until Android 5.
Related
Before I begin, let me preface by saying how eternally grateful I am to the xda and wider development communities. You guys are awesome.
I'm new to the Epic, and for that matter new to Android, coming from a Windows Mobile device. Right out of the box, I knew I needed to hack this thing to allow for the kind of control I've grown accustomed to. Took me some time to mount it to my computer, a lot longer to root it permanently; then I realized that the most popular rom (at least on this board), Viper, needed me to be on the leaked stock, so I flashed to that, changed file system, and then flashed the VIPERrom 4.0.2c. I was pretty happy for a few minutes. Yay to getting rid of bloat ware! Yay to LauncherPro.
But then I realize, this thing doesn't have built-in wifi tethering. I thought that was THE big new feature back in Android 2.2, and the top ROM for my device doesn't have it? The only mention I see in the Viper thread is a suggestion that Barnacle worked for some people. Well that little program didn't work for me, and while I got a little further with Muller's "Wireless Tether", none of these apps are really doing it for me.
Is there no ROM for Samsung Epic that tethers out of the box? Am I the only one that considers connection sharing a really important feature for a 4G device? What's the deal here?
The app your looking for is Wireless tether for root users. Its the best of its kind. Not really sure how it works on viper but its fine on epic experience. And this is the development section.. something like this should go in general.
schnowdapowda said:
And this is the development section.. something like this should go in general.
Click to expand...
Click to collapse
You're right, I wasn't thinking about where this should go. Can I delete/move the thread?
Your going to have to go back to di18 firmware and search. [WIP]MobileAP epic. There is a link in that thread to the hacked sprint hot spot. This should get you were you want. As for a good di18 use aphis and Xtreme kernel. Good luck. make sure you search too. you will get flamed hard for posting in the wrong section..
Sent from my SPH-D700 using XDA App
wireless tethering is very buggy ATM on all Epic 2.2 builds, we don't have source for the kernel and to tether, theres changes that need to be made to the kernel. The best option for tethering and stability would be to stay with a 2.1 rom like Syndicate 1.0.2. It supports wired and wireless tether, both built in to the rom. You can use 2.1 roms with the DK28 modem or any of the others.
seroaddict said:
You're right, I wasn't thinking about where this should go. Can I delete/move the thread?
Click to expand...
Click to collapse
You cannot delete or move the thread on your own. I suggest you read the rules before posting anything else! At least one of the versions of wireless tether has always worked for me.
Sent from my SPH-D700 using XDA App
What is it your trying to tether off your epic?Wireless tether for root users should works for laptops if it is another android device like a tablet your trying to tether the tablet or other android device will need to be hacked to be able to allow it to see adhoc networks.If it is just a laptop though one of the versions wireless tether for root users should work though roms can be picky as to which version of wireless tether they will use.
Please post questions in Q&A section. Everyone please remember to click the "Report Post" button on the original post to have immediate action taken by the moderators. Also do not post in the thread itself telling the user that he made a mistake or broke a rule as it doesn't contribute to the thread and is unnecessary.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For everyone's information, the Report Post feature is the red triangle in the top-right corner of a post with the "!" inside of it.
I'm using Wireless Tether for Root Users on ViperROM 4.0.2c and it works like a charm. It was baked in for me...? However it wasn't working so I uninstalld and reinstalled from the market. It works very very well. Until we get mobileAP working on dk28, this is the best.
Sent from my SPH-D700 using XDA App
thesals said:
wireless tethering is very buggy ATM on all Epic 2.2 builds, we don't have source for the kernel and to tether, theres changes that need to be made to the kernel. The best option for tethering and stability would be to stay with a 2.1 rom like Syndicate 1.0.2. It supports wired and wireless tether, both built in to the rom. You can use 2.1 roms with the DK28 modem or any of the others.
Click to expand...
Click to collapse
All very interesting, and new to me. In reality, I think the Muller wireless tether app was working on Viper, but I wasn't getting past the local network. I've got it figured out now, but it's not quite what I had been hoping for. Regarding the source for the kernel, aren't they obligated to release that code based on the open source licensing? Is it just really laborious to merge the older Sprint kernel source with the relevant Froyo code?
In the meantime, I'll have to look into the 2.1 ROMs as you mention.
Hello anyone,
I just recieved a lovely FiiO E17 Alpen DAC & Headphone Amplifier which can act as a portable USB external soundcard for an android smartphone but only if the ROM supports USB host mode.
I have searched and found nothing. I would love to find a compatable rom for my desire HD.
Does anyone have any ideas or suggestions?
I will update this thread if I find anything.
Cheers
According to this it doesn't seem that any such rom exists. There were some attempts to make a working kernel but they seem to have failed. So there's no rom, i think.
Thanks for the reply Slavon-93.
Yes - it seems like USB Host implementation is close but no cigar.
When it does come along its going to be great - not just for music but for all the other USB devices that will be able to integrate with our smartphones
I would pay for that...
my tablet is ush host with dual boot Ubuntu and since our dhd are powerful enough to run linux it would be nice to have it!
Sent from my HTC Desire HD using xda premium
Agreed - I would pay also!
audio out
It works with Nook color and CM7 nightly.
http://www.head-fi.org/t/571944/ot-digital-out-on-android-phone/15
My Fiio E17 is arriving within the next days - I would be very happy if this will work. If not, it could be a reason to change the phone - or buy a Nook..
Just wait because somebody is making a kernel for OTG feature
Sent from my Desire HD using Tapatalk
Thanks tessut
That's great to hear. Is this the kernel you referred to?
http://forum.xda-developers.com/showthread.php?t=1518896
That kernel looks very promising. Apparently other issues have higher priority, so we probably need to be a bit patient about our issue
henrylar said:
It works with Nook color and CM7 nightly.
http://www.head-fi.org/t/571944/ot-digital-out-on-android-phone/15
My Fiio E17 is arriving within the next days - I would be very happy if this will work. If not, it could be a reason to change the phone - or buy a Nook..
Click to expand...
Click to collapse
Hi.
I'm very interested to see if this works for you. Not only the amp but also the dac. I'm planning on getting the Fiio E17 too and this would be a major boost if it worked.
I will, but it might take a bit of time. First of all we need a kernel that supports the function, which seems more promising now apparently. But I will report as soon as possible.
henrylar said:
I will, but it might take a bit of time. First of all we need a kernel that supports the function, which seems more promising now apparently. But I will report as soon as possible.
Click to expand...
Click to collapse
I've read that CM7 supported it. Or is that function not implemented for the DHD in CM7?
I thought the same, but it is a kernel issue, and if you follow the link in one of the first mails in this thread you can see how things were - until now where work is going on about a new kernel. OTG is not working yet, apparently, and it does not have first priority, but still, the foresight is much better than before..
Mayx I refresh that request?
Does anyone know of any rom/kernel? Preferrably 4.1....could someone with more knowledge shed some light on the issue why this seems to be such a problem? I'm sure there is a good reason I just like to understand it a bit better
It has been done with an old kernel so the device should be capable...and Android itself supports it, so the system should be capable as well.
I've mentioned this topic to certain developers but it seems no devs are particularity interested in getting this working on the DHD.
svhd rom support usb host mod with Mouse/Keyboard/Gamepad/Storage Device
[GUIDE]How To Use USB HOST
http://forum.xda-developers.com/show...4#post39500954
not only svhd host mode working... i tried on PACMAN rom and its working when kernel tuner is downloaded from play store.. it is working the same way like on svhd.. still i dont know how it works with hdd's
gerciolisz said:
not only svhd host mode working... i tried on PACMAN rom and its working when kernel tuner is downloaded from play store.. it is working the same way like on svhd.. still i dont know how it works with hdd's
Click to expand...
Click to collapse
PACMAN rom host mode work for you ??
i try to connect to host mode in svhd rom but i can't if you can help me so do it please !!!
this is my connectors picture :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep it worked but usb mass storage dont work on pc now XD i dwnloaded kernel tuner and did the same operation like on svhd..
It seems i have little bit other connection. I have OTG cable connected to usb hub with 4 inputs to first i've plugged mouse to second
Connected charger but i had to buy a usb cable which have 2 same male plugs, one goes to charger one to hub.
Ill post photo later
Interesting, hear about this a while back but never expected it to work so soon. The adapter makes sense, DHD can't deliver that power to a external device
Sorry if I'm misunderstanding how this works, but I don't understand what a kernel does. I recently installed the Franco kernal Milestone 2 onto my Android Revolution 3.0 ROM. I thought it would add new options to my device or something based on the description of the kernel, but I feel as if nothing changed...
Would anyone be kind enough to explain how these things work?
To put it as simply as I can, and the way I understand it (correct me if I am wrong anyone).. A kernel is the code between the ROM and the actual phone hardware itself, so in order for your firmware to communicate with your device hardware, it uses this middleman known as a kernel.
The easiest way to explain it is to say the kernel is like the brain for Android while the ROM is it's body. It's the core part of any operating system that is responsible for the most basic tasks such as turning on and off LEDs, charging the battery, distributing processor time to different apps/processes, etc.
You can find more about their differences @
ROM-VS-Kernel
xHausx said:
The easiest way to explain it is to say the kernel is like the brain for Android while the ROM is it's body. It's the core part of any operating system that is responsible for the most basic tasks such as turning on and off LEDs, charging the battery, distributing processor time to different apps/processes, etc.
You can find more about their differences @
ROM-VS-Kernel
Click to expand...
Click to collapse
A kernel is the ECU in a car.
The rest is the OS
I should be able to answer this myself since I just took a class that covered the basics of computing last semester, but despite the dozens of pages of notes, I can't. So... Wikipedia:
In computing, the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components)
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Kernel_(computing)
Which explains why you would flash a kernel that improves battery life (resource and power management) and/or increasing the processor's clock speed.
The Linux kernel handles the process sharing (multitasking), resource management and using device drivers abstracting the hardware from the applications.
A user program might address memory, but this is in a virtual address space. The kernel uses memory management to map this to physical memory (and maybe swap it out if other programs need to run).
(The kernel is in the middle (like the kernel of a nut). It is surrounded by the shell (like a nut!) )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ah, aha! Thank you! So basically I have to read the description of the kernel and what it does before I install it, because the things it changes aren't actually options? This makes more sense now. Thanks for the help everyone!
Luuthian said:
Ah, aha! Thank you! So basically I have to read the description of the kernel and what it does before I install it, because the things it changes aren't actually options? This makes more sense now. Thanks for the help everyone!
Click to expand...
Click to collapse
Franco lets you change options through his app...
https://play.google.com/store/apps/details?id=com.franco.kernel
Or if you're running a custom rom, many of these options are changeable in the "performance" section of the rom settings.
Does the Kernal have anything to do with the radio function? Reception?
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Ha ha ha ha ha!!!!!
keving75 said:
Does the Kernal have anything to do with the radio function? Reception?
Click to expand...
Click to collapse
My mistake.
Does the Kernel affect the radio function? What about GPS lock?
Luuthian said:
Sorry if I'm misunderstanding how this works, but I don't understand what a kernel does. I recently installed the Franco kernal Milestone 2 onto my Android Revolution 3.0 ROM. I thought it would add new options to my device or something based on the description of the kernel, but I feel as if nothing changed...
Would anyone be kind enough to explain how these things work?
Click to expand...
Click to collapse
Latest milestone its 3 and this speaks by itself :
Sent from my Galaxy Nexus using xda premium
I also would have accepted colonel sorcerer.
Hi
Guys i hear about kernel and can be flash into the device
What kernel can do?
if it helpful for the device can i have a new kernel for my device
Thanks guys
Search for kernel in Google. Kernel is the heart of our mobile. You can flash modified kernels.
Sent from my GT-I9082 using xda premium
IRAQIGHOST said:
Hi
Guys i hear about kernel and can be flash into the device
What kernel can do?
if it helpful for the device can i have a new kernel for my device
Thanks guys
Click to expand...
Click to collapse
Try google like maxxinn said for better info.
But basically, Kernel the the software between your firmware/ROM and our phone. Kernel is how your ROM governs your phone. So kernel has to be different for each phone model.
Stock kernels usually just have the essential things, just to run the phone like it should. Custom kernels have tweaks to make your phone better in several ways like faster, less lag, overclocking and better response and input options.
For our phone there is custom kernel but only for 4.1.2
k2wl is working on 4.2.2 kernel but it's not finished yet, but it's up for testing
What is KERNEL ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass.
Click to expand...
Click to collapse
j.posarekar70 said:
Click to expand...
Click to collapse
Nice 1 buddy
Special Thanks
Thanks guys for replay
I Will try to install a new one for my device
The Samsung Galaxy s4 has very impressive specs. It has a Quad-core processor. For any of you that are aware of WiFi encryption Penetration via Backtrack or other sources, could it be possible to hack WiFi on the new and powerful Galaxy s4? Of course, maybe Chrooting bt5? But then, you have your chipset to worry about.
Is there a method to hack WiFi via s4, or is the processor no match for WiFi penetration suites?
I don't think hacking Wi-fi networks is appropriate talk for XDA.
Exel said:
I don't think hacking Wi-fi networks is appropriate talk for XDA.
Click to expand...
Click to collapse
only if your talking about doing it to others. There are plenty of legit reasons to try and hack your own network.
as for the op, i read about a rom for a tablet that was specifically made for wifi penetration. So i guess it is possible, but for the question is it possible for our phone? well i have no clue
I havent followed it closely but the project linked above aims to write broadcom drivers for android wifi chips so that u can test ur network security. I believe the usual linux tools can be reused. These guys just need to develop drivers which support monitor mode and packet injection.
It was a pleasant surprise to see that they have a release now! It says they are working on the s4 too. It will be so nice since everyone has unix on their phones. I wonder how the hell they put it in an apk?? I thought it would be a kernel module
---------- Post added at 05:17 PM ---------- Previous post was at 04:50 PM ----------
I went and did some reading and it seems like their apk somehow hooks the wifi calls so they can accomplish monitor mode and packet injection without modifying the binary drivers. wtf..
faiyo said:
I havent followed it closely but the project linked above aims to write broadcom drivers for android wifi chips so that u can test ur network security. I believe the usual linux tools can be reused. These guys just need to develop drivers which support monitor mode and packet injection.
It was a pleasant surprise to see that they have a release now! It says they are working on the s4 too. It will be so nice since everyone has unix on their phones. I wonder how the hell they put it in an apk?? I thought it would be a kernel module
---------- Post added at 05:17 PM ---------- Previous post was at 04:50 PM ----------
I went and did some reading and it seems like their apk somehow hooks the wifi calls so they can accomplish monitor mode and packet injection without modifying the binary drivers. wtf..
Click to expand...
Click to collapse
So... Samsung Galaxy s4's "BroadCom" chipset will not cooperate in Backtrack Chroot? I haven't attempted a bt5.arm Chroot just yet, so I'm not sure if that chip set functions with Backtrack.
Is there a way to exploit chipsets to where they will work properly with BT? How do the backtrack and Aircrack people add more chipsets to the supported list, much less let it be used?
The only thing I have referenced to this is an apk I used with my S3. Was able to penetrate my home wifi. Just did it to see. Im not much into developing but I'm curious about things like that.
Sent from my SAMSUNG-SGH-M919 using Tapatalk
androidiphonehacker said:
So... Samsung Galaxy s4's "BroadCom" chipset will not cooperate in Backtrack Chroot? I haven't attempted a bt5.arm Chroot just yet, so I'm not sure if that chip set functions with Backtrack.
Is there a way to exploit chipsets to where they will work properly with BT? How do the backtrack and Aircrack people add more chipsets to the supported list, much less let it be used?
Click to expand...
Click to collapse
Theres no android device with a supported wifi chip, even the broadcom ones.
Im not too familiar with BT but afaik it is just a linux distribution with the tools and drivers bundled in; which they made none of it. The same tools are used on any unix env (mainly aircrack). But the wifi drivers must support the required features (monitor mode and injection). Most of the supported chipsets probably have drivers from the manufacturer with the required support. Probably all of the supported ones because no one cares so much about a specific pc chip to work on the drivers themselves. If they do work on it then im sure the drivers must have source code available. Otherwise it's just easier to use a different chip.
It's different with android chipsets because we're assed out unless someone does it at home. That's what these guys were doing. They started off trying to rewrite or patch drivers and release the unix binary to be loaded as a kernel module. Which is groundbreaking stuff because no one does that **** outside of the mega-corp engineering groups at the chipset manufacturers who have the source code. In the end they released a magical apk, again groundbreaking because i dont think anyone has ever developed an apk like this one (patching drivers...im so lost). As you can see, I'm really surprised they succeeded. It's real development they're doing and it was a big job. I just went thru their repo and it is out of date Theres no source for the apk
Whale.... I can't code in UNIX.. I can do a little bit of C++, but you can forget UNIX. Lol xD
Sent from my GT-I9505G using Tapatalk
So I did some more specific research on the S4's chipset.
Its a Broadcom 208.11ac adapter, but as you guys said.. The development team for creating a monitor Mode for Broadcom chipsets has no repo sources. Although. I'm pretty sure that you can Google it and find other Mirrors for the apk file.
___________UPDATE:_________________________________
I found this link, It looks pretty promising.
http://rootzwiki.com/topic/40428-backtrack-5v2-for-android-with-aircrack-reaver-s3-tested/#
Well, I would not be external wifi adapter (ex. Alfa awus036h )?
Yess
hi. I succeeded. i can use aircrack-ng with alfa awus036h on galaxy s4. Im using ubuntu. maybe you can too
http://forum.xda-developers.com/showthread.php?t=2338179
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi