[ROM][OFFICIAL] dotOS 3.0 Pie [MARKW][9.0.0]

[kelelowo]

Quick Charge 2.0 os working?

how to set up auto call recording?

 

[adbazym]

Anyone got problem with gps? Too slow for gps to lock, sometimes not locked at all. Tq.

 

[Law_Ger]

Anyone got problem with gps? Too slow for gps to lock, sometimes not locked at all. Tq.

No problems at all. Use for Navigation with Android auto and Everything works fine.

 

[vefuh@nyrmusic.com]

TO DEVELOPER'S

I can't set black colour in accent colour (#bug)
After pair Bluetooth set to phone sometimes it get weird and disconnect connection
Please add widget like it was in MIUI to clear cache of RAM (kill all running apps)
Please add option to change fonts.
After turn off clock in status bar it ALWAYS show up again (bug#)
Equalizer seems to doesn't work well. Maybe Beats audio or something better then this

besides system is Okay. Simple and clean. Good job.

 

[davidnw]

Anyone got problem with gps? Too slow for gps to lock, sometimes not locked at all. Tq.

Try an app like GPS test , it will show you details of satellite picked up by the phone.

I have had no problems, sitting in my house now - 11 seconds for a GPS position fix shown by the app. Accurate to a meter or two.

I just noticed the phone seems to prefer Chinese and Russian satellites before the USA GPS although that could be just what is in the sky at the moment. Also possibly because they are more accurate?

 

[Defforest]

Try an app like GPS test , it will show you details of satellite picked up by the phone.

I have had no problems, sitting in my house now - 11 seconds for a GPS position fix shown by the app. Accurate to a meter or two.

I just noticed the phone seems to prefer Chinese and Russian satellites before the USA GPS although that could be just what is in the sky at the moment. Also possibly because they are more accurate?

Yes, its true and I can confirm this.
If your phone have root access you can try to use Top NTP from playstore, and build gps.conf to your own desired location.

 

[sdhan9879]

Yes, its true and I can confirm this.
If your phone have root access you can try to use Top NTP from playstore, and build gps.conf to your own desired location.

Bro can tell which recovery should I use, cause its working with mine one, please link a recovery.

 

[Trifyllara]

Many thanks to all the team for this rom.

Any update coming?

 

[An0n1mUs]

Guys, I'm having toruble installing this rom.
In recovery I get this error:
"E3004: This package is for device: markw; this device is .
Updater process ended with ERROR: 7"
I have tried with TWRP 3.0.2.0; 3.0.3.0; 3.1.1.2 always same error
However I have installed xiaomi.eu rom without trouble.

Also I get the same error with PixelExperience

 

[Trifyllara]

Guys, I'm having toruble installing this rom.
In recovery I get this error:
"E3004: This package is for device: markw; this device is .
Updater process ended with ERROR: 7"
I have tried with TWRP 3.0.2.0; 3.0.3.0; 3.1.1.2 always same error
However I have installed xiaomi.eu rom without trouble.

Also I get the same error with PixelExperience

It happened to me also during flashing.
I remember TWRP, while flashing, reporting "Not mounted disk" or something like that.
Did you performed this, prior flashing the rom : https://windowsreport.com/driver-signature-enforcement-windows-10/
Hope this helps...
Also pls try this:
Re-flash twrp with Adb and then dont get out of the command screen, but give the command "adb reboot bootloader".
Your device will boot in Twrp and hopefully you can proceed with clean install, as per instructions in page 1 of this thread...

 

[An0n1mUs]

It happened to me also during flashing.
I remember TWRP, while flashing, reporting "Not mounted disk" or something like that.
Did you performed this, prior flashing the rom : https://windowsreport.com/driver-signature-enforcement-windows-10/
Hope this helps...
Also pls try this:
Re-flash twrp with Adb and then dont get out of the command screen, but give the command "adb reboot bootloader".
Your device will boot in Twrp and hopefully you can proceed with clean install, as per instructions in page 1 of this thread...

I didn't have driver issues, every TWRP image is installed correctly.
Xiaomi.eu roms install correctly, but dotos and pixelexperience give this error.

 

[Trifyllara]

I didn't have driver issues, every TWRP image is installed correctly.
Xiaomi.eu roms install correctly, but dotos and pixelexperience give this error.

For your info i used TWRP 3.2.1.0-Treble....
I think that's the good one for android 9

 

[davidnw]

Guys, I'm having toruble installing this rom.
In recovery I get this error:
"E3004: This package is for device: markw; this device is .
Updater process ended with ERROR: 7"
I have tried with TWRP 3.0.2.0; 3.0.3.0; 3.1.1.2 always same error
However I have installed xiaomi.eu rom without trouble.

Also I got the same error with PixelExperience

I had this problem as well I think the problem is TWRP is not recognizing the device is actually markw hence the message "this device is . "
I followed this as advice to remove the device test from the install script - https://xdaforums.com/showthread.php?t=2302599 and installation worked.

I have since changed TWRP version but have not tested it yet.

 

[An0n1mUs]

For your info i used TWRP 3.2.1.0-Treble....
I think that's the good one for android 9

I think this is the issue, I dont have the Treble TWRP.
Could you send me the link to download the recovery that you used?

 

[Trifyllara]

I think this is the issue, I dont have the Treble TWRP.
Could you send me the link to download the recovery that you used?

Yep

Here it is: https://androidfilehost.com/?fid=890129502657599344

Hope this helps...

 

[An0n1mUs]

Yep

Here it is: https://androidfilehost.com/?fid=890129502657599344

Hope this helps...

It worked. Thank You.

 

[Trifyllara]

It worked. Thank You.

Nice !!!

 

[Law_Ger]

Just one quick quuestion: Is this Rom still in dev and when will aprox. the next update with may security patch come. I saw that other roms got update.

Thanks in advance for all your work.

 

[davidnw]

dot_markw-userdebug roomservice data missing in github

I am trying to build markw following the instructions on the page - https://github.com/DotOS/manifest
The option "20. dot_markw-userdebug" is listed on the lunch menu. However the markw roomservice data seems to be missing. I get the error message:

Exception: markw not found in dotOS-Devices Github, exiting roomservice
build/make/core/product_config.mk:244: error: Can not locate config makefile for product "dot_markw".

Any assistance would be appreciated.

 

[DarkAngelGR]

Since Granrage dropped dotOS, I decided to make a build of it, it's unofficial and I will probably not update any time soon

https://drive.google.com/file/d/1mP_QQLA3bi0QgbsrfW4lj7QijiKabJ9e/view?usp=drivesdk

Note: Led might be blinking even when there are no notifications, just reboot to solve the bug, also gcam not included so users can install the version they want (gcam 6.x has a green tint in selfies with HDR+ on)