Oreo - Mission impossible? [8.1.0_r46][6Oct2018] OmniROM-8.1

Status
Not open for further replies.
Search This thread

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,340
Hong Kong
Update

I planned to release another LOS-14.1 last weekend but something didn't seem right. I need to test longer. I'll clean build another one tonight.

For Oreo,
I managed to fix Video playback last week. :D
The only major issues left would be Video recording and Bluetooth.
There is not much update from the Lineage team so I'll take another look in video recording this weekend. See if anything pop up then.

Frankly, I seldom use Bluetooth and taking video but who can tell?
I'm on Oreo half the time now. I haven't experience what people said deep sleep issue. Anyway, its good enough for my personal use but yes, I miss a few features...

My problem is! I can't reliably post here. I can't update the Nougat thread. I have to retry a few times to post, edit or PM. :mad:
The most annoying is github. I normally can't push the source now. It might only work at late night.
If this persist, I can only push the source while visiting my mum in Hong Kong. That's my situation... :cyclops:

PS. For those who have the deep sleep issue, I think you can still get the log. You have to provide something for me to study.
 
Last edited:

Ashwinrg

Senior Member
Feb 23, 2015
735
193
27
Mumbai
I planned to release another LOS-14.1 last weekend but something didn't seem right. I need to test longer. I'll clean build another one tonight.

For Oreo,
I managed to fix Video playback last week. :D
The only major issues left would be Video recording and Bluetooth.
There is not much update from the Lineage team so I'll take another look in video recording this weekend. See if anything pop up then.

Frankly, I seldom use Bluetooth and taking video but who can tell?
I'm on Oreo half the time now. I haven't experience what people said deep sleep issue. Anyway, its good enough for my personal use but yes, I miss a few features...

My problem is! I can't reliably post here. I can't update the Nougat thread. I have to retried a few times to post, edit or PM. :mad:
The most annoying is github. I normally can't push the source now. It might only work at late night.
If this persist, I can only push the source while visiting my mum in Hong Kong. That's my situation... :cyclops:
I experienced deep sleep issue means after screen off it not responding to any keys or touch behaved like a dead phone until battery pull off and again starting after putting battery inside.

Anyway, thank you very much for working hard to give us oreo experience. Very much appreciate your work:)
 

Arjunism

Member
Oct 23, 2017
30
35
I planned to release another LOS-14.1 last weekend but something didn't seem right. I need to test longer. I'll clean build another one tonight.

For Oreo,
I managed to fix Video playback last week. :D
The only major issues left would be Video recording and Bluetooth.
There is not much update from the Lineage team so I'll take another look in video recording this weekend. See if anything pop up then.

Frankly, I seldom use Bluetooth and taking video but who can tell?
I'm on Oreo half the time now. I haven't experience what people said deep sleep issue. Anyway, its good enough for my personal use but yes, I miss a few features...

My problem is! I can't reliably post here. I can't update the Nougat thread. I have to retry a few times to post, edit or PM. :mad:
The most annoying is github. I normally can't push the source now. It might only work at late night.
If this persist, I can only push the source while visiting my mum in Hong Kong. That's my situation... :cyclops:

PS. For those who have the deep sleep issue, I think you can still get the log. You have to provide something for me to study.
Daniel, my guess for the deep sleep is that the display turned off completely and can't turn on again. I say this because the screen once turned off during a phone call but I can still speak through. To get the log is hard because everytime the issue occurs, I had to remove the battery. I can try to pull log from adb but that would be hard..I'm frankly inexperience but I sure can try. Or you can teach me on that.
 

greekfragma

Senior Member
Sep 25, 2007
330
154
Athens
I have the deep sleep bug also on latest Carbon especially during calls. My guess is with the proximity sensor communication with the radio driver or something in the middle of their usage.
 

divis1969

Member
Oct 3, 2012
12
2
I'm wondering how the RIL is working. Can I get more details?
It looks like both "vanilla" RIL and mtk ril daemons are working (or at least started, since there are probably two daemons defined in rild.rc and in init.modem.rc), is it correct?
 

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,340
Hong Kong
I have the deep sleep bug also on latest Carbon especially during calls. My guess is with the proximity sensor communication with the radio driver or something in the middle of their usage.

I usually test it at night and leave it overnight. I haven't experience what you said. I did experience a few times in the early stage but not now. I'm on LOS-15 but Lineage haven't changed much for weeks, still 8.0.0_r3. I had patched a few things in kernel afterwards but seems not related.
Either way, I think someone can get a log with adb, until then... :confused:

I'm wondering how the RIL is working. Can I get more details?
It looks like both "vanilla" RIL and mtk ril daemons are working (or at least started, since there are probably two daemons defined in rild.rc and in init.modem.rc), is it correct?
I'm not sure what you asked. If any part of RIL doesn't work, we won't be able to use the phone.
I did replaced the MTK's RIL daemon with my own and wrap the .cpp library with my wrapper. It might eventually replace the one from MTK too. MTK has its own daemon for channels and mux but all .c libraries are proprietary. If you know how, you probably would study the init.xxx.rc for the services.
I had posted a few times with some details about the progress of RIL on my Nougat thread. You may read them if you are interested.

I don't know what you suggested. The file from LOS? How can it be helpful?
If you meant the definition change, it's surely been taken care weeks ago. Otherwise, how can we take pictures?
You have to be more specific. No more riddle please, I'm too busy to guess now... :cyclops:

For Oreo,
As mentioned earlier, Video playback is working (with Hardware decoders too) now.
I stated studying video recording yesterday. The workflow changed in Oreo. There are comments inside the source saying that metadata is now handled separately. Don't know what exactly it means. Sad news is I can't access http://source.android.com to read the latest info. now. :( The online-sac build with the 8.0 source is still 7.1 documentations so doesn't help...
It would be really helpful if anyone can download (or mirror) the whole http://source.android.com documentation for me.
The current status is,
I can play AV files in treble mode and there is no issues with the existing decoders. Therefore I want to try treble mode first. I have figured out a few things now and seems possible but still too early to tell.... :cyclops:
If that doesn't work, I would return to the old shared memory approach later... ;)
Cheers! :D
 
Last edited:

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,340
Hong Kong
@daniel_hk
anything from below links will help you?

https://github.com/GerritCodeReview/gerrit
https://www.gerritcodereview.com/
https://gerrit.googlesource.com/gerrit


I am a total noob for these but If you guide me how to provide you the resources I will upload it for you.
I know you want to help but sending me links are useless. Don't waste your time searching for the thing you don't know.
If you want to learn, go to the official AOSP site. Posts or threads here or the web are not necessarily correct. People just post what they think or understand. I can be wrong too. There are official and formal documentations you can always count on.

If you want to help, send me the log on the sleep issue you said. You can get the log via adb.

Is that wrapper's code published?
I think you're from academic field. Publish is a formal word which haven't heard for a while. :)
I already uploaded most of the source to github but not yet RIL and few others.
I've added a lot of logs, build flags and test codes inside. I need sometime to tidy up so that I can understand myself first. I don't have too much time lately and the local blocking of internet make things even worse. Anyway, it will be open source when ready.
If you have my device and know how, use my pre-built blobs first. It would not be difficult to make it work.

For Oreo,
8.0.0_r34 is out earlier and Lineage is still r3. But Carbon already merged to r33. I might build another Carbon in the coming weekend. Cheers! :D
 
Last edited:

sandwichk

Member
Dec 11, 2014
6
0
Bhopal
Thanks for the work.

Hey @daniel_hk Which of your ROM would you recommend me to install? I'm on K50a40_S427_160518_ROW. It has become very slow and hangs up all the time. I just want a bug less ROM with good performance and good battery life. I'll download this ROM after BT fix because I have MI Band 2. :angel:
 
G

GuestK00324

Guest
Hey @daniel_hk Which of your ROM would you recommend me to install? I'm on K50a40_S427_160518_ROW. It has become very slow and hangs up all the time. I just want a bug less ROM with good performance and good battery life. I'll download this ROM after BT fix because I have MI Band 2. :angel:
Carbon ROM
 

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,340
Hong Kong
daniel_hk
log deepsleep

The log you sent seemed doze related. It might be the ambient display not properly handled in CR-6.0 yet. I have tested in LOS-15 for quite long and it didn't happen to me. I only install a handful of apps and no Gapps (not working here) and I rooted it. Anyway, I'll build a LOS later for you guys to test.

Hey @daniel_hk Which of your ROM would you recommend me to install? I'm on K50a40_S427_160518_ROW. It has become very slow and hangs up all the time. I just want a bug less ROM with good performance and good battery life. I'll download this ROM after BT fix because I have MI Band 2. :angel:

Everyone's usage and habit is different. One man's meat is another man's poison. The best and only way is to test it yourself.

Any update on oreo status @daniel_hk? Internet issue in your area solved?

CR-6.0 is not ready yet but LOS is also updated to 8.0.0_r30 earlier. I only have an hour or two spare time each day so not much progress... The internet situation can only be worse so I have to live with it.

I have been studying video recording for some time. I managed to stop the crash but the out file only show green screens. Audio in the file is recorded correctly. I remember same thing happened in Nougat before so seems close now. Anyway, I'll build another LOS-15.0 before sleep, hoping nothing went wrong... ;)
 

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,340
Hong Kong
20171120 LineageOS 15.0 beta test build

There are a lot of logv added so I made a cleaner build late last night. It was out this morning and I just tested briefly.

The current status is:
1. As mentioned earlier. Video playback (with HW decoders) is working now.
2. I have removed some Lenovo features from the kernel. eg. Power off charging UI and gesture are obsolete now.
3. Video recording crash fixed. In the out file, video is mess up but audio is normal. Video and audio use different threads (same codes but different codec) so I think the encoding workflow is OK. It might be the offset/range or handle send to MTK's encoder not handled properly. I might need to dump and study the raw video before passing to the MTK codec and the MPEG4 writer.
I'm not familiar with camera and image processing. No idea what's the streaming and frame format yet. Need some time to study first. Any suggestion is welcome.
4. Beside that, the only major issue left is Bluetooth now. Detail can be found in the OP. ;)

Uploading now, check OP for the download link. cheers! :D
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    Oreo - Mission impossible?
    I started studying "O" in early August. All I got were the O-preview3 factory images for qcom and tegra devices which I don't have. Built it out and made it boot wouldn't be too hard but everything seemed different. It took me some time to figure out the flow of the new frameworks. At that time, only the RIL and Graphics sources were really "O". The most devastated situation would be the RIL. Seemed dead end at that time. That was the first time I feel impossible. The source from MTK's RIL made things even worse. All the .c functions are buried inside prebuilt static libraries. Frankly, up to this moment, I'm still not fully understand the workflow of MTK's RIL... :eek:
    While I was struggling with the RIL, "O" - Oreo was launched. The most helpful info. were also released in source.android.com. Sadly, I can't access this website no more... Never take it for granted for anything. You can loose anything/anyone for no reason. :( The sources were then completed and took me some times to made it boot "again".
    Eventually, I can make the RIL almost fully working recently. Yes!:victory: All I can say is, we are lucky. Our RIL blobs only experience a few crashes which I can managed. I had tried five or six sets of blobs for different MTK chips. Each had different crashes so there is no guarantee that all MTK devices might work...
    Last week, I finally figure out how to made the camera work. Seems not "impossible" now so I start this new thread.
    I can't start a DevDB now. The response from XDA official is "They can't think of obvious reason". Anyway, I pay for ad-free and still the status shows connection to axx.amazon-adsystem.com. It just hang there for minutes (until timeout I suppose). However, I can start a normal thread (after minutes of delay) and that's not a problem to me. I already learnt to live with so many obstructions now. :cyclops:

    There were just too many distractions and ridiculous people out there. I don't want to waste time arguing so I would make it short this time. I rather spend time on something I'm good at. ;)

    For those who want help, no matter its ROM related or about development, please don't use PM. There are many limitations with PM. Do it formally. Start a thread in Q/A or post with all the details you can get (log, kmsg, screenshot, etc.). It's no harm for more opinions. Hiding in the dark doesn't help.

    Current Status :confused:
    KERNEL
    Patch: Binder and sdcardfs update are required and essential for Oreo.
    See commits in my github for detail

    AUDIO
    Recording: Working
    Playback: Working
    Patch: Load a copy of the struct instead of the pointer to address.

    BLUETOOTH
    Working
    Issue: Workflow issue in BTIF driver.
    Patch: New driver and HAL build from source.

    CAMERA
    Flash/Torch: Working
    Capture: Working
    Issue: User handle is required in GetMemory. MTK blobs return null.
    Patch: Save a copy of the user handle. Don't know if other devices might work or not. It's better to rebuild a few blobs but I don't have the source for my device...
    Issue: Oreo use a ring buffer of native_handles and no more ANativeWindowBuffer.
    Patch: A wrapper is required for the libcam.client. (The better way would be rebuild it but again no source...)
    HDR: Working with Snap in LOS-15.1
    Video recording: Working
    Issue: Oreo doesn't support GRALLOC (or I don't know how). The old HAL1 implementation doesn't work too.
    In short, need to find a way for the metadata that our old blobs can handled.
    Patch:
    1. Add libcamera_parameters_mtk for the MTK extra parameters
    2. Add another mode to handle Gralloc in stragefright.
    3. Patch the OMXNode to handle Gralloc mode.
    4. patch the OMXClient to use mediaserver
    5. Patch the hardware interface to handle Gralloc Metadata and work with the new OMX interface.

    DISPLAY/TOUCH SCREEN
    DT2W: Working

    FM RADIO
    Working

    GPS
    AGPS: Working
    GPS & BEIDOU: Working
    GLONASS: Enabled by default

    GRAPHIS
    HWC: Working
    Issue: Android platform changed
    Patch: A simple patch in libgui_ext (might use shim if timestamp proved no use)
    OpenGL: Working

    LED
    Notifications: Working
    Charging: Working
    Low power: Not Working
    See Post #806 for detail. Haven't study why --pending

    MEDIA
    Video Playback: Working
    Hardware decoder: Working
    Issue: crashed
    Patch: A small patch in minijail use Asan.

    POWER
    Power off charging: Working

    RIL
    Phone calls: Working
    Mobile Data: Working
    SMS: Working
    Dual SIM: Working
    Issue: Completely new approach in Oreo with interface/services. No more sockets. AND all .c libraries are proprietaries.
    Patches:
    1. Replace the MTK RIL daemon with AOSP patching for MTK
    2. Wrap (eventually replaced) the libril from MTK with AOSP patching for MTK
    3. Patch the RIL interface/service to work with the MTK vendor library.
    Some more detail can be found in post #65 and post #806

    SENSORS
    All sensors are Working
    Patch: Lower the requirement from 1.3 to 1.0

    WIFI
    ap,p2p: Working
    Miracast: Working
    Noted: only work on 2.4G as before
    Hotspot: Working
    Hidden SSID: Not support
    No idea why yet. --pending

    Sources :cowboy:
    Github

    Download :highfive:
    Experimental: AndroidFileHost
    OmniROM: AndroidFileHost, 百度网盘
    LineageOS-15.1: AndroidFileHost, 百度网盘

    Install :fingers-crossed:
    Flash with the latest TWRP
    1. Factory reset
    2. Flash ROM
    3. Flash SuperSU (tested ver.2.82)
    4. Reboot and setup wifi
    5. Flash Gapps (tested opengapps 8.1)

    Change Log :)
    Code:
    [B][COLOR="Blue"]2018/10/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r46 (OPM4.171019.030.K1)
    - New build enviornment
    - Security patch Sep. 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/8/11[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r42 (OPM4.171019.021.Y1)
    - OmniLib is updated
    - Security patch Aug. 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/7/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r36 (OPM2.171026.006.H1)
    - SELinux Enforcing
    - Security patch July 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/6/26[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r30 (OPM2.171026.006.C1)
    - SELinux Enforcing
    - Add/Fix SEPolicy rules for GPS, camera, Video, etc.
    - Security patch June 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/6/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r32 (OPM4.171019.021.E1)
    - OmniLib is updated
    - A few bug fix in Omni Apps
    - Security patch June 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/5/18[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r28 (OPM4.171019.029.B1)
    - Security patch May 5, 2018
    - chromium-webview update[/INDENT]
    [B][COLOR="Blue"]2018/5/11[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r26 (OPM2.171019.029.B1)
    - Security patch May 5, 2018[/INDENT]
    [B][COLOR="Blue"]2018/4/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
    - fix vendor image mismatch warning
    - fix a few security issues in reading NVRam
    - chromium-webview update[/INDENT]
    [B][COLOR="Blue"]2018/4/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
    - Security patch Apr. 5, 2018
    - adjust some memory defaults
    - handle the build flags for MTK devices (to live with other devices in the same source)[/INDENT]
    [B][COLOR="Blue"]2018/4/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r20 (OPM2.171019.029)
    - Security patch Apr. 5, 2018
    - HDR broken in this build. Check [URL="https://forum.xda-developers.com/showpost.php?p=76174760&postcount=612"]post #612[/URL] for the fix patch[/INDENT]
    [B][COLOR="Blue"]2018/3/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r15 (OPM1.171019.021)
    - Add Device Features support in OmniGears
    - Device Features: Display Color Adjustment is added[/INDENT]
    [B][COLOR="Blue"]2018/3/9[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r15 (OPM1.171019.021)
    - Workaround for Proximity sensor in InCall screen
    - Settings: LiveDisplay is supported now[/INDENT]
    [B][COLOR="Blue"]2018/3/2[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
    - The patch for codec and power off charging animation included
    - Workaround for Proximity sensor in InCall screen
    - HDR support with Snap porting to OmniROM[/INDENT]
    [B][COLOR="Blue"]2018/2/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
    [INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r11 (OPM1.171019.018)
    - All previous fixes in Omni-8.1
    - HDR support with Snap port 
    - Patch for MTK soft codec[/INDENT]
    [B][COLOR="Blue"]2018/2/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
    - Fix Lockscreen settings
    - Minor patch in video recording to make it more stable
    - update codec conifg
    - check [URL="https://forum.xda-developers.com/showpost.php?p=75609953&postcount=338"]post 338[/URL] for the codec and power off charging animation patch[/INDENT]
    [B][COLOR="Blue"]2018/2/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
    - Source is sync to the latest Omni-8.1
    - userdebug build.
    - Native Video recording is fixed. [COLOR="Red"][B]Edit[/B][/COLOR]: check [URL="https://forum.xda-developers.com/showpost.php?p=75488295&postcount=273"]post #273[/URL] for the camera patch
    - Phonograph and equalizer are also fixed.
    - MP3 and FLAC can be played now.
    - GPS: Enable GLONASS by default [/INDENT]
    [B][COLOR="Blue"]2018/1/21[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
    - Security patch Jan. 5, 2018
    - Add Messaging apk
    - Add FM radio apk
    - Add the forgotten vibration support 
    - RIL: Fix a bug in carrier info. 
    - Clean up the internal log I added. [/INDENT]
    [B][COLOR="Blue"]2018/1/7[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
    [INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
    - Initial release 
    - Security patch Jan. 5, 2018
    - New Bluetooth driver and HAL.
    - Kerenl: a few minor patches[/INDENT]
    [B][COLOR="Blue"]2017/12/30[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.1[/B]
    [INDENT]- The latest Carbon CR-6.1 source, Android-8.1.0_r1 (OPM1.171019.011)
    - Cumulated patches from LOS-15.0
    - Security patch Dec. 5, 2017[/INDENT]
    [B][COLOR="Blue"]2017/12/22[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
    [INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
    - libsuspend: add earlysuspend support
    - Kernel: tidy up lenovo features source
    - DT2W: working now[/INDENT]
    [B][COLOR="Blue"]2017/11/20[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
    [INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
    - Kernel: remove obsolete Lenovo features
    - Mediaplayer: fix video playback
    - Camera: Add mode to handle MetaDataGralloc in video recording. (only audio working now...) WIP[/INDENT]
    [B][COLOR="Blue"]2017/10/23[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.0[/B]
    [INDENT]- The latest Carbon CR-6.0 source, Android-8.0.0_r15 (OPR3.170623.008)
    - Alpha test build[/INDENT]
    Known Issues :(
    - May be a few...​

    Donations :angel:


    show.htm
    27
    20180811 OmniROM-8.1

    As Pie is out, this would probably be the last OmniROM-8.1 update. :)
    - The latest OmniROM 8.1 source, Android-8.1.0_r42 (OPM4.171019.021.Y1)
    - OmniLib is updated
    - Security patch Aug. 5, 2018
    20
    20171222 LineageOS 15.0 beta test build

    Last week, I started another round on the kernel. There were some progress and I just built another LOS-15.0 test build.

    In this build,
    1. The latest Lineage have a few features included (eg. double tap status bar to lock)
    2. SOD is fixed.
    3. DT2W is working now
    4. Charging and power management are enhanced.
    While other issues are still there... :(

    This would be the last 8.0.0 test build and It's about time moving to 8.1. :)

    About RIL:
    Since there are many queries, I summarize my findings here. I only study the official source briefly so correct me if I'm wrong. ;)
    The official document from AOSP mentioned that the old socket approach would parcelled 3 times. That means same set of data are copied 3 times per request/response. Oreo's new approach is to avoid that. A request/response would only parcelled once between the service and Framework.

    Official MTK RIL in O-preview
    1. They keep using sockets to communicate so there would be minimal changes in librilmtk and vendor RIL.
    2. Work around is to introduce the proxy daemon and library to work with Oreo. I would imagine its still copied (at least?) 3 times.
    3. Framework patches are required in java level and so as the services. Some of those might be ignored as before. This seems against the spirit of project treble.
    Frankly, if all my trials failed, this would be the last method I can think of.
    IMHO Mediatek engineers are a bit lazy.

    We don't have the full sources for vendor RIL library (mtkril), libril (librilmtk) and the ccci daemon. Therefore the workflow from kernel to HAL can only be the same as before.
    My approach is to replace mtkrild and librilmtk. Replacing mtkrild is rather straight forward. There are a few functions inside librilmtk which are required by the vendor RIL. Therefore my libril it's still a wrapper (for librilmtk) now.
    I used the AOSP libril as start. I was trying to create the IRadio service for MTK so that framework can be untouched. Everything can hopefully be done inside the libril. During the course, there were a few crashes in the vendor RIL. I had to wrap or replace the crashed functions. To do so, I had to binary edit the blobs to redirect the calls. The workflow of librilmtk is quite tricky and frankly I'm still not fully understand. I just emulated the workflow of librilmtk by supplying the same set of data to vendor RIL and daemons. The rest was patching each request and response so that the correct data would be parcelled to/from Framework.
    I don't know how to explain but the source is there. For those interested, you may compare it with the source from AOSP and MTK. It shouldn't be too hard to understand what I was doing.

    There would be some spare time in the upcoming holiday. Hoping something might pop up... :D
    20
    20180206 OmniROM 8.1

    @santoimam, Frankly, MTK just has too much to hide. It doesn't help much but having the source would definitely be better.

    I just make a clean build before dinner. It's out now.
    This is the latest Omni-8.1 Android-8.1.0_r7 (OPM3.171019.013).
    The previous test builds are eng builds which were better for debug but has minimum security. From now on, it would return to userdebug.
    In this build:
    1. Source is sync to the latest Omni-8.1
    2. Video recording is fixed.
    3. Phonograph and equalizer are also fixed.
    4. When studying the video codec, I found out how to enable FLAC. MP3 and FLAC can be played now.
    APE and ALAC require some platform changes so I don't want to waste time. I think FLAC would be good enough already.

    All the major issues are more or less fixed. I'll tidy up the loose ends and hoping it can be my daily driver soon. Cheers! :D
    Edit: check post #273 for the camera patch for video recording. ;)

    P.S. As I mentioned many many times, dropping a few words or a link won't help anyone. It's just annoying and I have no choice but ignore it.
    If you don't want to provide detail and/or logs, etc. Please don't post on my threads. ;)
    20
    20181006 OmniROM-8.1

    Just update to Ubuntu 18.04 and the want to test the new setup. Omni has another update earlier so I build this one.
    - The latest OmniROM 8.1 source, Android-8.1.0_r46 (OPM4.171019.030.K1)
    - Security patch Sep. 5, 2018
    Cheers! ;)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone