Hello everyone,
I own the NExus 7 and the missing adhoc capability bugs me.
Sadly there is no public available patch for the wpa_supplicant_8 (which is the v8 of this file).
In http://www.slatedroid.com/topic/31094-request-compile-ad-hoc-enabled-wpa-supplicant/ user alex mentioned he changed the code of the v6 patch from
http://dl.xda-developers.com/attachdl/1967d77f4caf72d003889b890e6a31dd/50471c4c/3/8/2/0/5/5/diff.txt
to v8, but he seems to not receiving thread updates.
Could anyone in this forum modify the v6 patch to work with v8? I then will compile my own wpa_supplicant and share it with whoever it needs!
thanks in advance!
bye
(PS: I am not allowed to post this devel threads as a new user, sorry)
Related
If you are interested in disabling exchange security and haven't yet found the solution, have a look at this thread in the N1 forums: http://forum.xda-developers.com/showthread.php?t=775007
I have applied it to my desire running MIUI and it works flawlessly.
anyone else using this Email.apk with MIUI? can you please check this post: http://forum.xda-developers.com/showpost.php?p=9716387&postcount=225
do you have anything similar on your Desire? especially with MIUI. btw, I'm running MIUI_Au 0.12.3
Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan
Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?
Please ask all questions in the Q&A section. Thread moved there.
Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...
You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?
Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.
Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??
Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.
If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box
Thnx. Already saw this actually
Hello everybody,
Before I jump into the compilation proces and uploading my build I want to ask everybody first if anybody is interested in a weekly build CM10.
I know that Ivendor is not changing his sources every week, but the base of CyanogenMod is under constant development, so changes in the CyanogenMod source will be up to date again.
Let me know if you're interested by replying to this thread.
Also if theres enough interest in a build with kernel 3.0 inside I'm also willing to upload this image as well.
Because already one person replied I'm willing to share my compiled image. After all it's already compiled.
This build is compiled against ivendors sources on his Github and the latest CyanogenMod sources which were available.
Of course this image is already tested on my phone and everything seems to work like it did on Ivendor's last build.
Because Ivendors sources haven't been changed, this build still has the same bugs as his build.
To be complete the following:
- Vsync doesn't work, because the current kernel doesn't support this yet.
- Panorama shots
- Also mobile internet has a little glitch, which only appears to happen if you have a Pin locked SIM.
Solutions to this are:
* Setting the phone into Airplane Mode and back to normal. This should load the needed module.
* A more clean solution is to use the patch provided at: d-h.st/BgH This patch can be applied through CWM.
- Also camera view is upside down, but this is not noticable in the final saved image. (Don't know if this is a new or already known bug I don't use camera that much).
You can download my build from: mediafire.com/?m765ok5mtly7l6h
You have to copy the links into you're adress bar, because I'm not yet allowed to post outside links.
If anyone has questions feel free to ask.
Greetings PsychoGame
a weekly build would be nice
i don´t use the 3.0 kernel because of the not working camera
i hope it changes soon
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
PsychoGame said:
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
Click to expand...
Click to collapse
Great idea. You can use 2 builds,one with 2.6 kernel, second with 3.x
it would be very great
Sent from my GT-I9001 using xda premium
I am posting here asking for help, assistance, coaching.
It seems to me that I have all the pieces to properly modify the Sero 7 Pro ROM to accept ad hoc Wi-Fi connections. I've spent several days trying to find a simple step-by-step guide for applying github patches to existing kernels and flashable ROM. I have come to believe that no such simple guide/aid exists because the process itself appears to be complex.
The Nexus 7 CyanogenMod has been successfully modified for ad hoc Wi-Fi. My research indicates that the Sero 7 and the Nexus 7 are similar enough that the same patches should be able to be applied to the Sero 7 ROM. The Nexus 7 and Sero 7 both:
Use Android Jelly Bean 4.2.X
Have the same processor, 1.3GHz NVIDIA Tegra 3
Use the same Wi-Fi Chip, Broadcom BCM4330
Kernels use the same Driver, Broadcom bcmdhd Version 5.90.195.104
What I have is the kernel source
http://hisense-usa.com/support/firmware/Sero%207%20Pro_kernel_opensource_us.tar.gz
The full Stock ROM, latest version
https://skydrive.live.com/redir?resid=F7DECBA5BB726100%21108
Patches applied to Nexus 7 CyanogenMod ROM with detailed discussion
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Briefly summarizing the discussion and code contained in the above Thinktube webpage:
The Kernel is patched making changes to the bcmdhd Wi-Fi driver
The ROM is patched making changes
to the wpa_supplicant
a few additions to the Android framework and
some changes to the Settings App
So in concept it seems pretty straightforward. Where I am struggling is the whole github process of applying the patch to the Kernel source. Then compiling the modified Kernel source. And applying the remaining patches to the ROM with the newly modified Kernel.
I need someone willing to work with me on the github piece. Or alternately coach me through that process.
So the resounding lack of response tells me either I've posted on the wrong forum or it is indeed as complex and cumbersome as I suspected.
But I may have figured out how to accomplish it myself. I have NOT figured out the github process. But I do know a little Linux and do run a virtual Ubuntu machine.
So I :
1. manually modified the Broadcom bcmdhd in the kernel source line by line.
2. swapped the wpa_supplicant file in the Sero7 stock ROM with the one from the Nexus 7 CyanogenMod ROM.
3. extracted the needed sero7_defconfig and initramfs.cpio.gz files
4. compiled the modified kernel source code and created a new boot.img
5. inserted the new boot.img to complete the modification of the Stock ROM
And if this all works, I’ll post my fix in a new thread, perhaps “Sero 7 Pro hoc Wi-Fi Fix”
wpa_supplicant
bardell3600 said:
So the resounding lack of response tells me either I've posted on the wrong forum or it is indeed as complex and cumbersome as I suspected.
But I may have figured out how to accomplish it myself. I have NOT figured out the github process. But I do know a little Linux and do run a virtual Ubuntu machine.
So I :
1. manually modified the Broadcom bcmdhd in the kernel source line by line.
2. swapped the wpa_supplicant file in the Sero7 stock ROM with the one from the Nexus 7 CyanogenMod ROM.
3. extracted the needed sero7_defconfig and initramfs.cpio.gz files
4. compiled the modified kernel source code and created a new boot.img
5. inserted the new boot.img to complete the modification of the Stock ROM
And if this all works, I’ll post my fix in a new thread, perhaps “Sero 7 Pro hoc Wi-Fi Fix”
Click to expand...
Click to collapse
Oh boy! I've been waiting to hear if someone got the ad-hoc going on the Sero 7 Pro. I've posted asking for help doing this too but never seemed to get a working answer. Did you get yours working and if so could you please post the wpa_supplicant file for the Sero? I would sure like to wifi tether to the Sero. It's the only device I have that doesn't see my phone's wifi.
Thanks a bunch!
Bob
Hi everyone,
You may have seen recent publication about WPA2 vulnerbilities (called KRACK): https://arstechnica.com/information...l-leaves-wi-fi-traffic-open-to-eavesdropping/
A wpa_supplicant patch is already released: https://w1.fi/cgit/hostap/commit/?id=a00e946c1c9a1f9cc65c72900d2a444ceb1f872e
Does anyone know whether it is already included in recent LineageOS builds?
Okay, patches are now included:
https://review.lineageos.org/#/q/st...wpa_supplicant_8+branch:cm-14.1+topic:krack-n
Manual patch of retired models?
Hi,
is there a way to patch a phone that is no longer supported by the vendor?
Let's say, root the phone, compile patched wpa_supplicant and replace it somehow. Is it possible?