There is a well known issue with wpa_supplicant on 4.2.2 JB being broken for LEAP (802.11X Enterprise) authentication.
There is a development version of wpa_supplicant available (https://android.googlesource.com/platform/external/wpa_supplicant_8/) that solves the issue however recent patches from there didn't yet go into Google's release.
AOSP build from CM doesn't seam to be usable on non-AOSP ROMs and moreover I'm not sure it solves the issue (if it takes official Google release code then it doesn't).
If anyone could compile the code (https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master) for non-AOSP builds (preferably ARHD ROM), it would be greatly appreciated.
Related
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
I read in the cyanogenmod forums that that the ROM (the public alpha-1 version) made by arco68 is "unofficial" CM9 ROM. What can be the reason for this custom ROM being "unofficial?"
im sure your not a good of a reader arent you ?
well 1st of all its unofficial because samsung WILL not realease ICS on SGW
and what arco has made is still incomplete ... there is still known bug and unknown bug that hasnt been fix yet ...
and the the ics camera on cm9 for sgw still is not working that's why its not official
chocolemon said:
im sure your not a good of a reader arent you ?
well 1st of all its unofficial because samsung WILL not realease ICS on SGW
and what arco has made is still incomplete ... there is still known bug and unknown bug that hasnt been fix yet ...
and the the ics camera on cm9 for sgw still is not working that's why its not official
Click to expand...
Click to collapse
I see .
Before my next question, I wanted to clarify first that by "unofficial," I meant the "unofficial CM9" built by arco68. (I am also aware that Samsung will not release "official" stock ROM)
Now, if that's the case, then what is the difference between the nightly builds (which, I assume are the alpha builds, please correct me if wrong) in the cyanogenmod's device page and the build (Alpha-1) version of arco68's ROM?
it's considered unofficial because it's not being released by the core team from cyanogenmod. They don't and can't work on every single device.
Still, cyanogenmod announced recently that they will support and assist whenever possible independent developers (like arco) and make their ports official at some point and, of course, under certain criteria (QC probably).
AFAIK CM9 for the SGW will become an official CM9 release as soon as it gets finished.
If I'm not mistaken all releases of CM9 are still in alpha stage.
On 2012.05.28 ipaq3870 uploaded his last version of i8000 android kenrel. a kernel that is based on M910 (s3c6410) phone, modified for our device.
Two years later and after saw gingerbread running on our phone, even with some problems and lacks i decided to contribute, work and continue this project.
i want to modernize this kernel in order to make our froyo ROM faster and make gingerbread ROM with more features to work.
there are many sources over the internet. we only need some volunteers. no need for advanced linux/programming knowledge. some free time and will to study a little is necessary of course.
volunteers can contribute here
https://github.com/argentinos/o2droid (fork from ipaq's job)
sources can be found here
https://github.com/a.../kernel-s5pc100
https://github.com/a..._samsung_omnia2
https://www.kernel.org/
http://opensource.sa...earchValue=m910
http://opensource.sa...earchValue=5800
https://github.com/a..._samsung_omnia2
http://omnia2droid.g....com/svn/trunk/
my last goal is to see latest version of 2.6 kernel on our phone. i do not think our old phone can ever execute 3.X kernel or run properly android ICS, JB etc
for those dreaming about it can conrtibute on erikcas 3.0 kernel for i8000 here
https://github.com/erikcas/spica-3.0
Hi,
I know, that sooner or later there will be a CM ROM based on Android 5.0 for our n7100. But it will be really nice to see pure AOSP ROM, compiled from sources of 5.0. I don't know, if is it possible, so I'm posting a question about it.
I remember I had i9000 long time ago, and somebody created AOSP 4.0 ROM for it - that was the best, most stable and fastest ROM I've ever used on i9000. Compiled from Google sources, without any add-ons. Hope to see Android 5.0 AOSP for n7100 sometime...
Now that lollipop has officially been released to AOSP, do we still need to wait till LG releases their source code merged with Android 5.0 ? Or can devs simply grab it and compile from googles source code ?
Probably won't be able to get much functionality (i.e., it won't work!) until LG updates the hardware drivers.
Yeah.... I just mentioned this in another thread.... Any custom LP ROM that gets shared will be a hybrid.... Android LP built on top of LG's KK stuff (kernel, modems and drivers).
Not saying that it can't be done, but I would expect some issues... My only seat time with a ROM like that was running Kitkat builds for my Galaxy S3 back when KK was first released. If I went a day with only a couple of reboots, I was lucky (every time it switched from WiFi to mobile it would panic boot, for instance). And that was just a 'minor' upgrade (4.3 to 4.4).....
The unofficial CM rom is working really well for me and it is still in alpha. I think by December we should have some pretty stable 5.0 AOSP roms.
The Pac 5.0 rom is very stable, the only thing I found wrong with it was the IR Blaster