I have been searching all over internet for a simple answer to a simple question but I'm going insane. Is Wi-Fi Direct a dead functionality or it's just been removed from cyanogen roms? It seems that everyone has that functionality except AOSP-ROMs. Somebody give me an answer here.
Or is it forbidden to talk about it. Cause I don't see anybody asking this question?!!
lutanica said:
It seems that everyone has that functionality except AOSP-ROMs.
Click to expand...
Click to collapse
Stick to samsung roms if you want all the features, im sure it has something to do with proprietary drivers needed for it to work and the cm team simply can't get sources for them.
good ! very useful
Does anyone know the current status of ICS development for Amaze? Contemplating switching from Sensation, which is just at the doorstep of getting pure AOSP ICS, currently few minor bugs to be worked out. Just wondering how far development has gone, perhaps at other sites?
Xboarder is doing a ton of the work here and as far as I know he is the one working on it. I believe his latest thought was porting it from another device but so far all we have had is a functional touchscreen.
craigtut said:
Xboarder is doing a ton of the work here and as far as I know he is the one working on it. I believe his latest thought was porting it from another device but so far all we have had is a functional touchscreen.
Click to expand...
Click to collapse
Similar stuff going on @ sensation - Tripnraver is doing awesome work @ Modaco. I had tried his pure AOSP ICS rom and it's almost ready, save camera and bt, and I can't believe how amazingly fast and snappy it was. Not my daily driver yet, but mighty close.
I guess I should be expecting similar time frame from xboarder (i used one of his CM7 based roms on sensation).
I'll raise a toast to our first successful developer, and send them some beer change, too They all deserve much for their hard work.
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=1378294
The last post from him says he is working on something else currently.
I'm not too familiar with the reasons and the technical stuff. Why isn't there a reliable AOSP ROM for the Rezound? What is it exactly that makes it difficult to develop one?
The ril hasn't been completely worked out for any AOSP roms
It has to do with the way Google has implemented support for CDMA devices. Google doesn't officially support CDMA devices in the Android framework they provide, so its up to device manufacturers (HTC) to create the necessary support and add it in. Right now, the developers who make ROMs are probably tearing apart the recent HTC leaks looking for the bits and pieces they need to put an AOSP ROM together.
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
I tell you one thing. The first developer who provides a near perfect working of ICS AOSP is going to get $15 from me.
con247 said:
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
Click to expand...
Click to collapse
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
the non-Sense development has been disappointing so far, no AOSP and no MIUI....I think the people talking about the ril have it right, if it was LTE that was the problem we'd have AOSP roms out that don't have working LTE like some other phones do
I Am Marino said:
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
Click to expand...
Click to collapse
Not sure but it was easier for the bolt cause s-off.
So is it right to assume that if we get full s-off then comes AOSP?
What exactly is s-off?
Cares said:
So is it right to assume that if we get full s-off then comes AOSP?
Click to expand...
Click to collapse
it's possible but can't really be proven since we literally have full access with the exception to the actual radios when flashing. devs can already view radios to iron out the issues. it's just tricky to solve a scattered puzzle
S-OFF has NOTHING I repeat NOTHING to do with AOSP. The TBOLT had more people working on it and the RIL isn't probably as complicated. They still don't have AOSP ICS working either.
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Cares said:
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Click to expand...
Click to collapse
There is an active CM9 Alpha thread in the dev section with updates on where it is.
I can't thank the developers enough for their hard work on this, but I just got a question. I just installed JackpotClavin's 3-31.zip CM9 on SGP 5.0 US and it's whole lot better than before, but I'm still wondering if the dialer is intentionally removed there? Maybe I'm ignorant about how ICS handles the dialer, but I assume it should be there and I'd like that on SGP as well, to use it as a VoIP device. I'm still a noob not having access to the developer forum, so I'm wondering if someone forwards my request to the developer or hopefully he checks this forum as well. Thanks.
As title says...
This was the Android 4.2.2 sense 5 dump...
Curious if anyone is working on it.
I'd like to know this as well. I know a few developers have mentioned looking into it in their posts but I haven't heard anything about a port coming to the DNA.