[ROM] MIUI Port - Oppo Find 7 and 7a

[ROM] MIUI Port - Oppo Find 7 and 7a

This ROM is in no way suitable for daily use and is only shared so that other fellow developers can take a look and maybe provide fixes to one or multiple things on the "not working" list.
Take it as a very early proof of concept.
ROM DOWNLOAD: http://www.androidfilehost.com/?fid=23501681358554238
What I did to get this far...
1. I took the MI3W miui-germany ROM
2. I unpacked the MI3W's ROM
3. I unpacked the boot.img of the MI3W ROM (zImage, dt.img, ramdisk)
4. I patched the fstab.qcom and init*.rc files to match the Find 7a
5. I unpacked the latest OmniROM for Find7a
6. I unpacked the boot.img of OmniROM (zImage, dt.img, ramdisk)
7. I copied zImage and dt.img from OmniROM's extracted boot.img into MI3W's extracted boot.img
8. I repacked the MI3W boot.img
9. I bundled the MI3W system partition with the modified MI3W boot.img and uploaded it onto the internet for someone else to iron out the remaining bugs
What seems to work...
*) Basic Operation (MIUI apps, status bar, well what you would expect really)
*) Bluetooth
*) Wired Headset / Bluetooth Audio
*) RIL / Mobile Data
*) GPS
What doesn't work... yet...
*) WiFi (there seems to be some issues with wcnss / pronto / prima, this one is bad...)
*) Random Reboots / Blackscreen Glitches (from what kmsg tells me it seems to be related to wcnss, aka. WiFi drivers causing a critical error in kernel every once in a while, fix WiFi and this error will fix itself)
*) Speaker Audio
*) Rotation Sensor (and probably others)
*) Vibration
*) Skyline Notification Light
*) NFC
For pictures check the thread at the oppoforums: http://www.oppoforums.com/threads/rom-miui-port-for-find-7a.17409

Good things always have the obstacles.
You've done your part. And let other(s) help you.
I don't have knowledge about cooking a ROM.
But I think someone can help. @Entropy512, can you look at this one?

If you want mae some cool port, i thikn sense rom is good candidate...

Great work
hey there mrcoldbird,
great work so far...keep it up..will definately help support you on this when it is up and running..i am not a dev but if you need someone to just bug report i am there for you,will keep my eyes n ears peeled on the thread and as soon as it's near ready i will flash and help you anyway i can...thank you for all your hard work so far

Right now we need developers involved in this. We know the countless obvious bugs.
Just have to fix them.

Awesome work. Thanks bird. Any chance you want to try lewa os while you're at it. I personally think it is better. I imagine just how busy you are but just wanted to throw it out there

Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.

MrColdbird said:
Porting really should only be done when there is no source available for said ROM.
For unicorn a source rebuild might be better.
Click to expand...
Click to collapse
I updated my post. You should really check out lewa. It has find 5 official support

uppon2 said:
I updated my post. You should really check out lewa. It has find 5 official support
Click to expand...
Click to collapse
no news about this rom

I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.

MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
ok thanks for answer. i love miui rom. i think it can be the best rom for find 7a
good luck
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
if you need help for test rom tell me. i have a lot of time for this.
when i try to install your rom twrp failed. do you know why ?

jazzypit said:
no news about this rom
Click to expand...
Click to collapse
Lewa OS website
YouTube video

uppon2 said:
Lewa OS website
YouTube video
Click to expand...
Click to collapse
no rom for oppo find 7a
do you have a link for test ?

jazzypit said:
no rom for oppo find 7a
do you have a link for test ?
Click to expand...
Click to collapse
No. That is what I'm asking for; a build for lewa for the find 7.

uppon2 said:
No. That is what I'm asking for; a build for lewa for the find 7.
Click to expand...
Click to collapse
Which doesn't belong in this thread. Take it elsewhere.

justin654 said:
Which doesn't belong in this thread. Take it elsewhere.
Click to expand...
Click to collapse
Lewa OS is extremely similar to MIUI and that is why I even bothered to mention it. I know the developer is having some trouble with MIUI so I thought it would be useful and helpful to mention Lewa as it might be a project that will help the development of either or rom.
Please don't take a blunt tone with me (if that's what it was) as it only makes you look arrogant. Taking in to account our post and thanks scores it is quite clear who has contributed in a more positive way towards XDA. On that note; you might also want to thank MrColdbird in the OP for his contribution, which you have not done as of yet but you seem to be poking your nose in to the thread
That is all
Edit* I apologise MrColdbird if my suggestion was unwarranted.
MrColdbird said:
I was actually searching for people to help me with this but no one bit the bait yet.
I am continually working on MIUI, bit by bit... but due to reallife interference it goes... slowly.
Click to expand...
Click to collapse
I am setting up a build environment and will be looking in to it; starting with wifi. I think I might check out lewa as well.

good luck

I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.

FareedYusoff said:
I've pm one of the Miui dev from note 1 community, and hope that he willing to lend his hand for you @MrColdbird.
Mr @Gerrett, can you help him? If you got some free time. I know you so busy. But at least, just a little guide for him.
Click to expand...
Click to collapse
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).

MrColdbird said:
Actually I've got 99% of the issues resolved already by using a different port-rom in conjunction with a few OmniROM injects.
At the moment only the proximity sensor (screen off on holding the phone to your ear) and nfc are broken, lte works, but needs to be reselected every time the phone reboots via the service menu (dialer code).
Sadly, I'm not allowed to share that (quite nicely working) ROM just yet as I switched port-bases to a unreleased chinese one in favor of the MI3W port-base.
Until that chinese author releases his first public port base-rom I'm kinda bound by the promise I gave not to unveil things early.
Just hang in there, it shouldn't be long until you guys have MIUI on Find7a... all I can tell you is that it works nicely and without any critical flaws I can see except those mentioned above (which we will get fixed too eventually).
Click to expand...
Click to collapse
Quite fast actually. By the way, I just can wait and see your nice work.
I'm trying to help, but that's all I can do right now. All the best on your effort.
I appriciate your hardwork. :highfive:

Related

DONT BOTHER WITH THIS SEE Herosso

This is now obsolete, Erasmux has ported the hardware (some of it) which i am havign trouble doing.I dont intend to steal his work so please use his!
http://forum.xda-developers.com/showthread.php?t=1026699
To revert MTD and flash back please see HERE

Issues and Changelog
Changelog..
First version..
Issues..
WIFI
MICROPHONE
CAMERA
NETWORK DATA - A little fishy
ROTATE - Think ive fixed in next version
MARKET - Loops Crashing?
BROWSER - Loops Crashing?

Well no bug or something, but I've added the rom on my mirror . here

Good luck with this. It's great to see that there are still some people who believe in a 2.2 sense rom for the hero
when the rom is tested a bit i will add it to my rom database

dude, you built a rom! congrats on being so bleeding edge bonesy!
I'm impressed with your guts
um, don't take this the wrong way, but I'm not about to try it just yet... ;-) It's just because I need my phone and it's camera etc for daily use. I have faith in you - you've been messing with this stuff longer than I have probably dude and your flashing instructions are VERY clear which is comforting.
I'm really impressed that you persevered like this though man!
cheers
Don

Like I said gonna give it a try when at work. Great work man. And ill report back in here all my findings.
Like don said. Great to see this still happening to the hero.
Sent from my HTC Hero using Tapatalk

What is working? What not?

krygo said:
What is working? What not?
Click to expand...
Click to collapse
see 2nd post,Lots working but lots not,was up untill 4am trying to fix some,as soon as i get mic and / or wifi going ill release 0.2

hi there!
I'm a bit puzzled how to revert to pre-MTD changes state.
I am willing to test this rom, but I would like to have an option to nandroid back without much of a problem. I read through the topic bonesy linked, but haven't found a simple answer/solution.
I hope I could help some more, at least confirm bugs or something.
Cheers!
brat.haneq
EDIT:
Is it as simple, as flashing "remove" zip?

Nearly, you will need to re-flash recovery too, Through fastboot..
Im struggling at the moment as i have 2 different builds on 2 different computers.As soon as i can get to my work computer i can carry on with it all

Call me stupid but is CustomMTD really necessary ? This rom can't work as all roms do? I've flashed it without MTD method and I am stuck on first splash-screen (mine says HERO on black background).
BTW ty for working on a Froyo Sense port for Hero GSM

omg Ninpo is involved, <3 him (nogay)
I will try when it's a little bit better ^^ and can be used for 1 day at school
good work man!

Wupper said:
Well no bug or something, but I've added the rom on my mirror . here
Click to expand...
Click to collapse
offtopic:
omg you again XD hahahaha

I will not flash this yet but still I want to say thanks to all devs for working on froyo sense

@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey

f_padia said:
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
Click to expand...
Click to collapse
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Is custom MTD really necessary?
Click to expand...
Click to collapse
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it

bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Click to expand...
Click to collapse
I couldnt agree more! well if you do find anything useful I will help anyway I can

bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
Click to expand...
Click to collapse
Well took a quick look at this. Will try to devout some more time over the next few days and see if it'll get me anywhere.
What I got for now is:
a) There is quite a lot of "junk" on the system partition here, after a short cleanup it fits very nicely without the MTD patch .
b) libwebcore.so fixes the browser crashes and most likely the markets too.
If I have time tomorrow I'll try to give the microphone a shot, cause this is the most critical problem at this point - whats the point of having a telephone you even talk to...
Hopefully I'll also release something for testing tomorrow...

Thanks Erasmux, i would have gtalked you today but been at work and the boss was in...so no devvin on the work pc lol.Got market and browser fixed as you say and also rotate and i think light sensor.I removed nabservice.apk as it only FC'd.Would be great if we can arrange a time over the W/end to talk

Opened a new thread for "my" version of this port:
http://forum.xda-developers.com/showthread.php?t=1026699
Please note, that the amount of effort I will be able on such a (closed source) ROM is limited. I mainly what to see how far I can get this, especially in terms of hardware support, with my past experience.
So its up to you if you want to continue to keep your version going in parallel. If you do (or anyone else), please feel free to reuse anything from "my" ROM....

Ecoo Aurora Plus 3GB, MTK6753 (different processor)

Hi there,
This thread is to collect the thoughts for this particular device. It is an Ecoo Aurora Plus (3GB) model but is also the variant which has a different processor (MTK6753).
Sadly there aren't many roms for this device yet. I was able to use the following roms with success:
(I cannot yet post links, so here are the breadcrumbs to the exact pages on "needrom" dot com.
TWRP
Home » - OTHER » E-F-G-H » ECOO » E04 Lite MT6753 TWRP
Android 5.1
Home » - OTHER » E-F-G-H » ECOO » ECOO E04 3GB+ MT6753
All of the important stuff works (from my perspective). I prefer something leaner, so I am waiting for a different rom to be available, but so far this one is pretty good. It was especially handy since you can't find the stock rom anywhere, and also when I bricked my phone and just needed something that worked.
Do you have this device? What rom/apps are you running on it?
Note: There were annoying ads appearing, which I was able to remove by using a different Launcher. The Ecoo Launcher seemed to be the source of the ads.

Hi I'm waiting for it, it's at the custom office now and I should get it soon in about a week I hope.
I've heard on an Italian forum of another guy who got a bug, usual on mtk 6753, with whatsapp crashing the camera when used from within whatsapp. Did you find the same issue with that rom?
Let's keep this thread alive if any updated rom will hopefully come.

bugs bugs bugs
I got mine a couple of days ago, with the latest 5.1 update. I got some bugs that are really annoying. The screen locks by itself randomly, the dropdown settings tab 50% of the time doesnt dropdown and the 3d performance is poor. Antutu full score on mine is a little over 36000, but as i said 3d is terrible (7fps at marooned scene and 4fps at garden scene). Also battery life is terrible.....
I dont know if i just got a bad piece or if they are all rom related, but i am willing to try a few roms before i decide to send it on a 3 month warranty trip back to china...
If i didnt have these bugs, i would say that this is a truly great phone and not just for its price range.
All help would be appreciated guys.
---------- Post added at 09:23 AM ---------- Previous post was at 09:19 AM ----------
forgot to mention that i just reflashed the latest rom that mcsilvio mentioned (ECOO E04 3GB+ MT6753) and bugs still insist...

lzwfkv said:
Hi I'm waiting for it, it's at the custom office now and I should get it soon in about a week I hope.
I've heard on an Italian forum of another guy who got a bug, usual on mtk 6753, with whatsapp crashing the camera when used from within whatsapp. Did you find the same issue with that rom?
Let's keep this thread alive if any updated rom will hopefully come.
Click to expand...
Click to collapse
Crashing Camera apps - YES. I have tried many camera apps from the app store. They ALL crash the camera when taking a photo. The preview/viewfinder works, but when i try to take the picture, the camera freezes. Now I am using the ROM mentioned in the original post, and the camera app that comes installed with that ROM works.
Man I REALLY hate the pictures this phone takes.

mpolyzois said:
I got mine a couple of days ago, with the latest 5.1 update. I got some bugs that are really annoying. The screen locks by itself randomly, the dropdown settings tab 50% of the time doesnt dropdown and the 3d performance is poor. Antutu full score on mine is a little over 36000, but as i said 3d is terrible (7fps at marooned scene and 4fps at garden scene). Also battery life is terrible.....
I dont know if i just got a bad piece or if they are all rom related, but i am willing to try a few roms before i decide to send it on a 3 month warranty trip back to china...
If i didnt have these bugs, i would say that this is a truly great phone and not just for its price range.
All help would be appreciated guys.
---------- Post added at 09:23 AM ---------- Previous post was at 09:19 AM ----------
forgot to mention that i just reflashed the latest rom that mcsilvio mentioned (ECOO E04 3GB+ MT6753) and bugs still insist...
Click to expand...
Click to collapse
Hmm. I have bugs, certainly, but I don't have those bugs you mentioned. I BELIEVE I did have the random locking screen bug when the phone was brand new, but I have not had that since I switched ROM. I haven't tried a 3d game yet.
Did you switch Launcher? I highly recommend it. It may even clear up some bugs. Keep us posted.
Yes it is still a great phone. We will get a great ROM one day.

mcsilvio said:
Hmm. I have bugs, certainly, but I don't have those bugs you mentioned. I BELIEVE I did have the random locking screen bug when the phone was brand new, but I have not had that since I switched ROM. I haven't tried a 3d game yet.
Did you switch Launcher? I highly recommend it. It may even clear up some bugs. Keep us posted.
Yes it is still a great phone. We will get a great ROM one day.
Click to expand...
Click to collapse
I tried the Miui Home launcher with no luck concerning the bugs. Beautiful launcher though, but didnt keep it because for some reason it didnt show my google contacts although it was synced..???
So back to stock, and waiting for a solution, if it ever comes along..

mpolyzois said:
I tried the Miui Home launcher with no luck concerning the bugs. Beautiful launcher though, but didnt keep it because for some reason it didnt show my google contacts although it was synced..???
So back to stock, and waiting for a solution, if it ever comes along..
Click to expand...
Click to collapse
Where do you get the stock rom? did you do a backup?
About the launcher, I had to remove the "Ecoo Launcher" because of ads (not really bugs). I did this with "Titanium backup" after I rooted my phone. Maybe give Nova launcher a try? Not really for bugs, just for a smooth experience.

mcsilvio said:
Where do you get the stock rom? did you do a backup?
About the launcher, I had to remove the "Ecoo Launcher" because of ads (not really bugs). I did this with "Titanium backup" after I rooted my phone. Maybe give Nova launcher a try? Not really for bugs, just for a smooth experience.
Click to expand...
Click to collapse
No didnt do a backup.
Got it from the same page you mentioned at needrom, e04 3gb+ mtk6753

Still in desperate need for a decent rom for it....sbd help

mpolyzois said:
Still in desperate need for a decent rom for it....sbd help
Click to expand...
Click to collapse
Yeah, me too. Being a developer, I was hoping to visit the subject of making an AOSP one myself. Haven't had the time. I read that for MTK processors it's not so easy as MediaTek did not release the chip's "source code" (or something like that). But I'm curious about how other MTK ROMs exist.
I was thinking maybe its worth PORTING a ROM from a different phone with the same proc? Say and Elephone P8000 (MTK6753).

Hi, nothing happening yet with this phone? It just arrived to me and I will be testing it after a full charge soon. In meanwhile as for the camera bug used from whatsapp, a workaround has been found by Enabling the flash led after you open it from wa; it should work.

Still no love on needrom com. I tried your flash workaround and it works! I tried it with what's app and open camera. Good job!

Got some love on needrom. A little. A user who has made some roms for the MTK6752 version asked someone for some information about his device. I stepped in and offered to help. He asked me to take screencaps of my device info using MobileUncle. I have done this and sent it to him, but that was in a PM. For everyone's sake, here is a link to the compiled screencap of the Ecoo E04 3gb MTK6753 Device Info.
http://postimg.org/image/qg0vczvpp/7414e7c3/
Thanks,
Marco.

Try to make "something" for Ecoo e04 mt6753
Hi to all
Lately I am trying to help the owners of the Ecoo e04 mt6753. Today I have built a twrp 3.0.0.0 for your device ... if everything will works well ... then I will try to build a rom for your device. I need someone to help me to do some test about twrp ... it is because I am a owner of an Ecoo e04 mt6752 ... so I can't test the twrp on my device. I am not sure that twrp will works well ... BUT ... if everything will be all right ... then I will start to work on the rom project. In case anyone's interested ... please give me a feedback ... so I will send you the link of my twrp test by private message.
Regards

Yes please, count me in for the twrp

mpolyzois said:
Yes please, count me in for the twrp
Click to expand...
Click to collapse
Probably my first twrp test will doesn't works ... but day after day (and test after test) we will achieve the goal.
I have sent you my twrp 3.0.0.0 test by private message ... please give me a feedback when you have tested it.
Thank you for making yourself available

Cleopatra Bianchi said:
Probably my first twrp test will doesn't works ... but day after day (and test after test) we will achieve the goal.
I have sent you my twrp 3.0.0.0 test by private message ... please give me a feedback when you have tested it.
Thank you for making yourself available
Click to expand...
Click to collapse
Good day, Cleo.
I have this phone and i can help you to test your TWRP. Give me a link and tomorrow i give you all information about this.

Cleopatra Bianchi said:
Probably my first twrp test will doesn't works ... but day after day (and test after test) we will achieve the goal.
I have sent you my twrp 3.0.0.0 test by private message ... please give me a feedback when you have tested it.
Thank you for making yourself available
Click to expand...
Click to collapse
All works fine. Tested on my MTK6753. Maded backup. Mounted all partitions. Tnx a lot for your work Cleo. Will be waiting for firmware from you.

Maddy_kz said:
All works fine. Tested on my MTK6753. Maded backup. Mounted all partitions. Tnx a lot for your work Cleo. Will be waiting for firmware from you.
Click to expand...
Click to collapse
EUREKA
I have one last favor I would ask to you : please reboot your device into TWRP 3.0.0.2 recovery and make a screenshot of the main menu. Then please send me that screenshot to me by private message. I need that screenshot to publish the twrp on Needrom.
Thanks in advance.
Kindest Regards

Maddy_kz said:
All works fine. Tested on my MTK6753. Maded backup. Mounted all partitions. Tnx a lot for your work Cleo. Will be waiting for firmware from you.
Click to expand...
Click to collapse
Hello Friend. Are you sure that you have a working recovery? I tested the recovery on your Ecoo E04 3GB + tried different ways of installation . No one returned no results .

AOKP-Jan 2017-H30-U10-Syed Hassan

AOKP-Jan 2017-H30-U10-Syed Hassan
Rom Download Link:
https://www.youtube.com/watch?v=3_3e5o8xnvY
Link Is In Video Description
Click to expand...
Click to collapse
Mirror Download Link Added For Those who are having prob in downloading through mega
Click to expand...
Click to collapse
Gappd Included,,
No Need to Flash Gapps Separately
Installation Instructions:
> Before any modifications please take a nandroid backup of your phone so you can revert it in case anything goes wrong
> Go to recovery and wipe all partitions except SD card
> Flash the Rom zip
#No need to Flash Boot.img(Separately)
In case of no signals issue, flash an appropriate modemfix from codelover's thread http://forum.xda-developers.com/android/development/guide-huawei-honor-3c-h30-u10-t2837773
Features:
HTML:
*Vibration Patterns
*Led Control
*Clock Settings
*Recent Settings
*Recent Search Bar
*Recents in Fullscreen
*Clear Button
*Lock Screen
*Set lock Screen Wallpaper
*Efect Blur
*Media Convert
*DT2S on Lock Screen
*Status Bar
*Carrier Label
*Custom Carrier Label
*Carrier Label Color
*AOPK Logo
*Bringhtness Control
*Show Notification Count
*Double Tap To Sleep
*Notifications Drawer
*Quick PullDown
*Smart PullDown
*Number of QS tiles per row
*Show weather
*Time contextual Header
*Task Manager
*Clear all icon
*Hardware keys
*Backlight
*Endcall
*Wake up device
*Answer Call
*Long press action
*Double tap action
*Wake up device
*Short press action
*Power menu
*Reboot
*ScreenRecoder
*Navigation Bar
*Pa Pie Control
*Sound
*User Interface
*App Launcher
Bugs: VPN Partially Working
[Changelog Build 7 Juanary 2017]
*Navigation Bar Delete Button Added
*Rild more Stable
*Theme Chosser New
Upload On Social Media Fixed
*Added Text in Lock Screen[/QUOTE][/CENTER]
BUGS:
Vpn:
open vpn root which is included in rom and with that you can connect with private server or public with have user and pass and host ip or address in pptp and l2tp
To use with shadow shock connect with natMOD enabled
2g/3g switch(Change 2g/3g in settings/system profile)
Please Hit Thanks button if you like and support my work
Click to expand...
Click to collapse
Credits:
Code:
Team AOKP Project
Team AOKP Project
Hassanjavaid8181(ME)
Ivan Velazquez
XDA:DevDB Information
AOKP-Jan 2017-H30-U10-Syed Hassan, ROM for the Honor 3C
Contributors
hassanjavaid8181, hassanjavaid8181
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: cyanogenMod
Version Information
Status: Stable
Current Stable Version: v1
Created 2017-01-24
Last Updated 2017-01-24
Click to expand...
Click to collapse

well done, big effort bro.
I saw the video on YouTube, please can you provide us with theme details and icon pack used by your Rom ?

What about Xposed?

AhmadSant said:
well done, big effort bro.
I saw the video on YouTube, please can you provide us with theme details and icon pack used by your Rom ?
Click to expand...
Click to collapse
bartxsporx1 said:
What about Xposed?
Click to expand...
Click to collapse
thanks,,itheme dark theme with minimale icon pack:good:
xposed already active in this rom,,

Links in description don't work :/
EDIT.
Ok, I opened it in MEGA app and it works, let's check it out

Bro ur all roms are amazing but I have a suggetion for u its most better is u need to work on bugs after fixing the bugs u make new roms. Thanx for Roms

gps fix patch
https://www.androidfilehost.com/?fid=817550096634744630

hi
tanks a lot!
this link isn't work!
ww.youtube.com/watch?v=3_3e5o8xnvY
is there any other download link?

Davidzzzzzzz said:
hi
tanks a lot!
this link isn't work!
ww.youtube.com/watch?v=3_3e5o8xnvY
is there any other download link?
Click to expand...
Click to collapse
Because you put ww instead of www.
Sent from my Honor 8 using XDA Labs

tnx
that was Typographical mistake!
when i go to the link, the YouTube says :
This video is no longer available because the YouTube account associated with this video has been terminated.
*****
!!!

Davidzzzzzzz said:
tnx
that was Typographical mistake!
when i go to the link, the YouTube says :
This video is no longer available because the YouTube account associated with this video has been terminated.
*****
!!!
Click to expand...
Click to collapse
Oh. Then we have to wait for OP to provide a new download link.0

adriansticoid said:
Oh. Then we have to wait for OP to provide a new download link.0
Click to expand...
Click to collapse
Yes, we always have to wait, wait waaaaaaaaaaaaaaaaaaaaiiit.
Let me put it this way: It is unfortunate that this smartphone only enjoys a last "Unicorn", i.e. the last devloper who seems to be invovled in many things and seems to be, at least at the moment, not very responsive ....
Cheers, dfahren

dfahren said:
Yes, we always have to wait, wait waaaaaaaaaaaaaaaaaaaaiiit.
Let me put it this way: It is unfortunate that this smartphone only enjoys a last "Unicorn", i.e. the last devloper who seems to be invovled in many things and seems to be, at least at the moment, not very responsive ....
Cheers, dfahren
Click to expand...
Click to collapse
He has a life to you know. So without any word from him that he is stopping the development for 3C, we are to assume that he is working on something.
Sent from my Honor 8 using XDA Labs

adriansticoid said:
He has a life to you know. So without any word from him that he is stopping the development for 3C, we are to assume that he is working on something.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Adrian,
who of us has not a private life? We all do and we all deserve one. No doubt about it. However, what I did when I edited the kernel of the Huawei Mediapad or when I wrote my USB-to-Ethernet-Helper even if I ceased developing (because of too little time and other commitments) I always checked the forum at least every two days and provided explanation or at least a helping word as far as I could. I don't want people hanging around waiting for something that is never going to happen. Let's be fair to one another and not waste precious time!
Rom cooking is something that's very laborious and veeeeery time consuming that's why I never went into this business and rest assured I admire those folks who devote their time and tremendous effort to make a new Rom happen. Quite terrific. But it is also true that Rom port users want to enjoy a Rom where the features they want to use are in fact usable. If they need facebook messenger badly and it doesn't work, well they skip the Rom and revert to stock. What else are they supposed to do? But what's the purpose of this Rom then?
Personally, I don't need zillions of Rom ports, I need a working one with a recent kernel with as little bugs as goes. Yes, sure, cooking several Roms with the same kernel and they all suffer from the same bugs because these bugs are hard to squash since they need to be fixed somewhere in the depths of the Android system or even somewhere in the kernel video driver (for instance) is easier than getting right at the culprit. Yes, sometimes knowledge is missing or time or resources, you name it. If there is at least another developer, you can buddy up and support each other. If you are left alone, well, developer support of this type of device is more often than not running out in the near future.
The sad truth here on XDA forums is, we suffer from many, tooo many devices and too few developers for all these devices. Also it is forbidden to charge money for one's development efforts. Donation is ok, but who can live from donations??? Rom cooking takes soooo much time and if you want to do it so that 95% of the people are satisfied with your Roms you need so much knowledge, too. No wonder developers withdraw their favor from old smartphones and turn to newer, more exiting ones, where manufacturer support is better.
Cheers,
dfahren

dfahren said:
Adrian,
who of us has not a private life? We all do and we all deserve one. No doubt about it. However, what I did when I edited the kernel of the Huawei Mediapad or when I wrote my USB-to-Ethernet-Helper even if I ceased developing (because of too little time and other commitments) I always checked the forum at least every two days and provided explanation or at least a helping word as far as I could. I don't want people hanging around waiting for something that is never going to happen. Let's be fair to one another and not waste precious time!
Rom cooking is something that's very laborious and veeeeery time consuming that's why I never went into this business and rest assured I admire those folks who devote their time and tremendous effort to make a new Rom happen. Quite terrific. But it is also true that Rom port users want to enjoy a Rom where the features they want to use are in fact usable. If they need facebook messenger badly and it doesn't work, well they skip the Rom and revert to stock. What else are they supposed to do? But what's the purpose of this Rom then?
Personally, I don't need zillions of Rom ports, I need a working one with a recent kernel with as little bugs as goes. Yes, sure, cooking several Roms with the same kernel and they all suffer from the same bugs because these bugs are hard to squash since they need to be fixed somewhere in the depths of the Android system or even somewhere in the kernel video driver (for instance) is easier than getting right at the culprit. Yes, sometimes knowledge is missing or time or resources, you name it. If there is at least another developer, you can buddy up and support each other. If you are left alone, well, developer support of this type of device is more often than not running out in the near future.
The sad truth here on XDA forums is, we suffer from many, tooo many devices and too few developers for all these devices. Also it is forbidden to charge money for one's development efforts. Donation is ok, but who can live from donations??? Rom cooking takes soooo much time and if you want to do it so that 95% of the people are satisfied with your Roms you need so much knowledge, too. No wonder developers withdraw their favor from old smartphones and turn to newer, more exiting ones, where manufacturer support is better.
Cheers,
dfahren
Click to expand...
Click to collapse
I understand it man. I feel it. This was they before for me in Galaxy Ace NXT. Development was pretty dead. Until two people came and did some very heavylifting for us who waited a long time for a stable ROM. I was very happy that time. I hope this will change in the near future. Every phone deserve some development. Thanks for your time man. Have a nice day. :highfive:

dfahren said:
Adrian,
who of us has not a private life? We all do and we all deserve one. No doubt about it. However, what I did when I edited the kernel of the Huawei Mediapad or when I wrote my USB-to-Ethernet-Helper even if I ceased developing (because of too little time and other commitments) I always checked the forum at least every two days and provided explanation or at least a helping word as far as I could. I don't want people hanging around waiting for something that is never going to happen. Let's be fair to one another and not waste precious time!
Rom cooking is something that's very laborious and veeeeery time consuming that's why I never went into this business and rest assured I admire those folks who devote their time and tremendous effort to make a new Rom happen. Quite terrific. But it is also true that Rom port users want to enjoy a Rom where the features they want to use are in fact usable. If they need facebook messenger badly and it doesn't work, well they skip the Rom and revert to stock. What else are they supposed to do? But what's the purpose of this Rom then?
Personally, I don't need zillions of Rom ports, I need a working one with a recent kernel with as little bugs as goes. Yes, sure, cooking several Roms with the same kernel and they all suffer from the same bugs because these bugs are hard to squash since they need to be fixed somewhere in the depths of the Android system or even somewhere in the kernel video driver (for instance) is easier than getting right at the culprit. Yes, sometimes knowledge is missing or time or resources, you name it. If there is at least another developer, you can buddy up and support each other. If you are left alone, well, developer support of this type of device is more often than not running out in the near future.
The sad truth here on XDA forums is, we suffer from many, tooo many devices and too few developers for all these devices. Also it is forbidden to charge money for one's development efforts. Donation is ok, but who can live from donations??? Rom cooking takes soooo much time and if you want to do it so that 95% of the people are satisfied with your Roms you need so much knowledge, too. No wonder developers withdraw their favor from old smartphones and turn to newer, more exiting ones, where manufacturer support is better.
Cheers,
dfahren
Click to expand...
Click to collapse
Well!! You dont need to write a whole essay on that LOL
I was busy....it's eid season here
Here is the link
https://mega.nz/#!4NoSSAjY!MfMDojGE9jt2OMNFikqzE62HXGExK7gkGYcrzo2y3Yw

hassanjavaid8181 said:
Well!! You dont need to write a whole essay on that LOL
I was busy....it's eid season here
Here is the link
https://mega.nz/#!4NoSSAjY!MfMDojGE9jt2OMNFikqzE62HXGExK7gkGYcrzo2y3Yw
Click to expand...
Click to collapse
Sorry Hassan, I did not intend to put you or your work down. Absolutely not. But I thought to myself "He (you) would not let this uncommented ...." which you did ... :laugh:
EID season? Ramadan? Sorry, again I have no clue.
Ok and this link, nice, but what did you do?
When I'm writing "novels" you are composing "poems"!

Multirom? Dual-Boot patcher?

Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/

Oh hell yes! I'd like to see this!

Desperately waiting for it!

Sounds cool, I can have Omni and XOSP at the same time ;P

https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom

Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well

AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...

Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.

AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...

Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:

Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step

A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.

valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.

valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever

AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.

valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs

delete

I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.

AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.

It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.

Promised Land of speed / battery tweaks, FINALLY after 15? years!? on this site

Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!

not sure how increasing the refresh rate helps battery?

ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Im getting bootloop when i tried itt on P

Don't try it on Android 10, it should work only on Pie

So does he mean that we can also get 84hz screen on pixel phone...?

DvLAx3l said:
Don't try it on Android 10, it should work only on Pie
Click to expand...
Click to collapse
I can't even get it to work on pie tho lol

Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.

melodystyle2003 said:
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
Click to expand...
Click to collapse
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out ?

eminem5055 said:
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out
Click to expand...
Click to collapse
That would be awesome

OK, I ll try to get some permissions before building / posting the revisions.

melodystyle2003 said:
OK, I ll try to get some permissions before building / posting the revisions.
Click to expand...
Click to collapse
Sounds good man! ?

eminem5055 said:
Which dtbo.img did you use as well?
Click to expand...
Click to collapse
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.

ha7msterx said:
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
Click to expand...
Click to collapse
ALSO, if the screen refresh part is a placebo, requiring a kernel modification to actually change, then ok.
Embarrassing to state, but I didn't actually test the resultant screen refresh rate, or really anything other than the subjective snappiness of my device.
So now I feel like I rushed to post, but I won't kill the thread because apparently melodystyle2003 is compiling a kernel. Thanks for that.

A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.

melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Really looking forward to this

melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35

Freak07 said:
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Click to expand...
Click to collapse
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards

melodystyle2003 said:
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
Click to expand...
Click to collapse
It´s not possible to overclock the displays of the pixel 3 or the pixel 3 xl that way. I don´t need to compile a test kernel to be able to tell you.
Displays running in command mode can´t be overclocked that way, unless you have access to internal files or you are able to flash display firmware to your device.
Both panels from Pixel 3 or Pixel 3 XL run in command mode:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L20
https://github.com/freak07/Kirisaku...google/dsi-panel-sw43408-dsc-fhd-cmd.dtsi#L20
Whereas the pocophone runs (as it seems more than one type of display across different units) all used panels in video mode.
https://github.com/d1stru3t0r/testz...qcom/dsi-panel-ebbg-fhd-ft8719-video.dtsi#L24
https://github.com/d1stru3t0r/testz.../dsi-panel-tianma-fhd-nt36672a-video.dtsi#L24
Panels in video mode can be overclocked this way, if it´s desirable is another question.
Sorry to be the bearer of bad news, but it´s simply not possible on Pixel 3 devices.
You can even unpack the dtbo.img, change the line you intend to change and any fps app might show you more than 60fps, but you just fooled the app into thinking our displays refresh at a higher rate than 60fps.

Develop Bugs

welcome