[K3 Note Original Android Development] daniel_hk:
Some info about O-preview:

EAS is a kernel feature, not ROM feature. As far as I know, only QCOM CPU/HAL set support it.

Some info about O-preview:

I downloaded the o-preview2 source months ago. Not much effort to build it out and make it boot. There were many issues and I put aside until early last month. I synced to o-preview3 but it just couldn't be built without quite some modifications. I was hoping source of o-preview4 would follow soon after it's release. However, up to this moment (over half a month...) the source hasn't updated yet.

Anyway, I have tried for a few weekends. Finally figure out the concept of it's porting. It's quite different from the earlier versions. The hardware interface take over all the HAL processes. HAL connect to platform via services now. The sources are generated during compiling and its quite difficult to trace. The objective is leaving the platform untouched for new hardware. But manual and guide is not available. I don't even have a device which can run official OPP4 image. It's time consuming by trial and error with wild guesses. There are lots of work ahead and IMHO only few of the existing MTK developers might figure out.

Anyway, the following are my current status.

1. Hardware are using hwbinder to register the interface and connect via services. Backport of the kernel is straight forward and comparatively easy.

2. I started with Wifi. It helped learning how the new approach work. It is 90% working now. 5G, hotspot and p2p are all OK but hidden ssid is not working.

3. All sensors are working with minor modifications.

4. GPS is working with minor patches.

5. Graphic and Codec appeared to work without problem

6. There is a minor but lethal bug in Bluetooth. A simple and trivial open() and read() just doesn't work now... Might be CLANG related....

7. Finally, the most serious issue now is RIL. The existing blobs are definitely not working with the new interface/service approach. :(

Old blobs have a full proprietary set of daemon, libril and vendor ril. Each blob has a proprietary static module which is chip dependent. It just can't be rebuild directly unless we have the source for that static module. The reality is even phone manufacturers won't have it... :(

I have rewritten a new daemon and it might work. I also wrote a wrapper for the libril but wrapping the vendor lib is not possible. After a series of different approaches, I can connect the interface and the service. Baseband can be seen in About now. That means the daemon and service are working partially. But, there are many unknown issues. Even if I can issue AT commands to the modem, there are some misbehaviours in responds. Seem the vendor ril will issued its own requests with the old parcels but the sockets are not there any more. If that's the source of problem, we just can't do anything and probably dead end. Altogether, I would say its 50/50 to make RIL (hoping 70%, voice, sms, data, etc.) work and there might be other unseen issues... :cyclops:

Everything is there. Even if there will be new sources from MTK, there won't be new RIL blobs for our chip 6752... How can a phone live without RIL... :eek:

I haven't tried Camera and FM yet. If RIL doesn't work, there is no point to waste time on other parts.

That's the situation for O now... not promising :(