yashsingh1/xdaforums huggingface dataset:
[Oukitel (All phone models)] DerTeufel1980:
If the battery is too low, it needs to be plugged in for some time, to be able to get to the offline charging animation... Displaying the animation obviously also needs some juice... If my battery once goes this low, I'll check it

Sent from my Oukitel K6000 Plus running O-8.1
[Oukitel (All phone models)] Oxofrmbl:
Can this Mtk6750t be ported to mtk6750t? Or are there some incompatibilites?

I would like to try but i've got no experience in developing /porting.
[Oukitel (All phone models)] superdragonpt:
8.1.0 had some issues on this device initially...

finnaly all seems nice now, 8.1.0 r14 (february patch level) is currently under testing

cheers ( no ETA)
[Oukitel (All phone models)] LFRuisu:
I've installed the rom and the gapps but my google play services isn't working, every time I try to open a g-app it closes and shows the message "Google play services stopped"
[Oukitel (All phone models)] Matze0815:
Great OS, Roaming problem

Hi there,

first of all I want to say THANKS! The OS is great!

One little problem appears for me. I am located in Germany and my mobile internet connection only works when Roaming is enabled. Is there a way to fix this? I live close to the border so I do not want to have Roaming enabled all day long. Something in the Settings? Couldnt find anything.

Thanks in advance!

Matt
[Oukitel (All phone models)] DerTeufel1980:
Yeah... I am using eplus/o2 myself... We didn't add the needed change to detect this yet. Unfortunately there's nothing you can do for now

Sent from my K6000 Plus running madOS O-8.1.0
[Oukitel (All phone models)] Matze0815:
Thanks for the info.

I enabled roaming and select the network manually. Will I get international network when i leave germany? This would cause height cost.

One more thing:

I have trouble with wifi/bluetooth. Sometimes "bluetooth was stopped" appears. This was a main reason for me to leave oukitels android 7, but now it seems to be also a problem here? Is it because of oukitels drivers?

I have to restart the phone and everythings working fine again... (happens often when using fitbit app with fitbit charge 2)
[Oukitel (All phone models)] rolex0815:
I don't get the point, you're surrounded by countries of the European Union and Roaming shouldn't be that issue since June 2017? :confused:
[Oukitel (All phone models)] rolex0815:
He/She could grab the sources and add the corresponding xml files by him/herself.

That's what I am doing for years in Austria with national roaming. (I assumed that the problem is connected to national roaming.)
[Oukitel (All phone models)] Matze0815:
I'm not sure about Switzerland
[Oukitel (All phone models)] rolex0815:
Of course Switzerland is the exception.
[Oukitel (All phone models)] Matze0815:
Is there a description of how to do that?
[Oukitel (All phone models)] rolex0815:
Analogue to this thread https://xdaforums.com/google-nexus-5/general/mod-loose-roaming-r-mvno-home-network-t2969702

But I'm compiling it for myself and then it's just an easy addition of some xml files to the res folder.

If you can create a corresponding file with your provider and the net where it is roamed on, it works.

The method with de- and recompilation of the framework-res.apk isn't recommended for newer Android versions; newer than Lollipop respectively.
[Oukitel (All phone models)] Matze0815:
Phone calls not working properly

I just found out, that phone calls do not work as expected. I can hear the other person, but I can not stop the call, because the ui still shows me the dialer. Not the call view. Only way to stop the call is to turn the phone off.
[Oukitel (All phone models)] Zip4ever:
Browser crashes

Really love your Oreo ROM. One thing tough... When browsing the web with Chrome, the browser sometimes hangs and then the mad os logo is doing its little dance to restart some services...
[Oukitel (All phone models)] Sarvesh.huddedar:
Very nice.. waiting for this new one..

also not sure, what will it take to enable VoLTE in this new version.. i see some patches for enabling this but even after multiple tries, its not working for me..

Happy to test this new ROM once gets released..
[Oukitel (All phone models)] Matze0815:
Phone Call

Am I the only one who can not make phone calls properly?

This screen is missing:

https://www.tutorialspoint.com/android/images/call2.jpg

So I can not stop the call, and also can not type in numbers when a robot asks me something.
[Oukitel (All phone models)] Pyandroid:
Start 'Minimal adb and Fastboot' at Pc. In the command window, type: "adb reboot bootloader" and press Enter (this is restarting the smartphone into the bootloader)

This is where I am stuck. Phone just displays "=>Fastboot mode......" at the lower left hand corner and nothing happens afterwards.
[Oukitel (All phone models)] DerTeufel1980:
Not missing for me. Maybe you need to wipe... Was it missing from the beginning already?

That's fine. "fastboot mode" is the bootloader

Sent from my K6000 Plus running madOS O-8.1.0
[Oukitel (All phone models)] Matze0815:
I think so. Never seen it.

Just tested answering a phone call. Also doesnt work..

Does wipe clear my apps/personal data?
[Oukitel (All phone models)] DerTeufel1980:
Yes, it does. Wipe is another word for factory reset.

Maybe try from recovery, wipe, and choose cache, instead of directly swiping to confirm.

Sent from my K6000 Plus running madOS O-8.1.0
[Oukitel (All phone models)] frankwangyun:
xposed supported！

https://xdaforums.com/showthread.php?t=3034811

It seems xposed Android Ore supported！ Thanks 。
[Oukitel (All phone models)] Matze0815:
Thanks for the answer.

I got it working now. Found out, that the default app for phone calls was not set in the settings. After doing that it worked.
[Oukitel (All phone models)] never4zip:
Issues with ROM

I have used this ROM for a couple of days now.

Beside of the issues with the car Bluetooth, there is something else which is quite strange.

After browsing the web, the madOs logo appears and the device does some kind of a mini reboot.

Yesterday however, I got a black screen telling "Starting android" and a progress bar. After 20 minutes nothin happened. I forced shut down the device.

After that I am unable to restart the device. The madOs logo appears, but the annimation stops en the phone just hangs there...

Switched to an other device temporary but going to try to re flash this Oukitel to the stock android...
[Oukitel (All phone models)] DerTeufel1980:
There's going to be a newer version soon.

However, for your current issue, you need to factory reset (wipe) the device from recovery

Sent from my K6000 Plus running madOS O-8.1.0
[Oukitel (All phone models)] fernseher:
Deleted
[Oukitel (All phone models)] mister_slowhand:
Well, I've been using this ROM from the very first day I had the K6000+ (early decembre). In fact, it's my wife's phone and she's no tech or so. I have no complaints at all, battery life seems good (she ends the day with 50% or more, using A LOT of the Facebook app...).

Recurring errors I see :

- sometimes "bluetooth has stopped" pops up but seems that it restarts itself and life goes on...

- WiFi is unstable. When connected, it's ok, but it often fails to connect at home. I have 2 Cisco AP, and it might be the cause as it looks like it has problems with roaming. For instance, if I shut an AP, it won't be able to connect to the other one. Needs reboot to connect, or it will finally connect after some times (hours...).

For a "under 100€ phone", it's an amazing device, of course thanks to this ROM because it looks like it's much more reliable than the official one !!
[Oukitel (All phone models)] Sarvesh.huddedar:
I am really waiting for next update on this ROM.
[Oukitel (All phone models)] ace794:
Everyone

Στάλθηκε από το K6000 Plus μου χρησιμοποιώντας Tapatalk
[Oukitel (All phone models)] Sarvesh.huddedar:
Thanks for correcting.. :)
[Oukitel (All phone models)] akaloith:
I am having serious problems while charging, sometimes it works, sometimes it doesnt.

and when my phone turns off then have huge problems charge it & turn it on

it the new version comming soon to see if it solves my problem or should i return to stock?

any guide to return to stock?
[Oukitel (All phone models)] RalphMalph:
What about try different cable?
[Oukitel (All phone models)] akaloith:
tried different charger, cable, wall, had my phone turned off for almost a day, and suddenly it went on just pluging unpluging!
[Oukitel (All phone models)] DerTeufel1980:
I switched to using this device for more than two weeks ago, and I did not face any issues with charging.

You're sure it's not a hardware problem?

Sent from my K6000 Plus running madOS O-8.1.0
[Oukitel (All phone models)] akaloith:
I try reinstalling the rom. when the new will come? is there a guide to return to stock?
[Oukitel (All phone models)] Pyandroid:
Me too..I am stuck with the original ROM....Can't wait.
[Oukitel (All phone models)] fernseher:
+1
[Oukitel (All phone models)] dylan54:
Very good and fast rom, i recommend.

Bug report from me for the future:

Change partition to f2fs => Rom no boot completely at the first time.

Change partition to f2fs => Google play stop any time

Kernel drain very fast the battery.

First boot stop at the pin code for phone sim. (remove sim and the first boot is ok)

No DRM google Widevine modular, required by many app

Speaker sound is very low.

Phone crash when charger is connected (+80% and black screen)

Very big thank for this rom
[Oukitel (All phone models)] LFRuisu:
Bugs

When I try to upload a video to instagram it is uploaded with bugs in image, and I can't post videos on my stories, I've already tried to reinstall instagram but it still don't working
[Oukitel (All phone models)] jmaciel_:
Bugs process video

please check in this new version 8.1 if the error persists in whatsapp when processing videos and gifs. in instagram it has the same error but the image gets broken messed up. in version 8 this is unbearable just ask you to check before posting thank you right away
[Oukitel (All phone models)] DerTeufel1980:
Seems fine
[Oukitel (All phone models)] Eselter:
What about android auto ;) ?
[Oukitel (All phone models)] DerTeufel1980:
What about it?

I can't test this though... My car doesn't support it
[Oukitel (All phone models)] Eselter:
You can try it with emulator.
[Oukitel (All phone models)] ace794:
Hi everyone.do you know if the release of new update coming soon?

Στάλθηκε από το K6000 Plus μου χρησιμοποιώντας Tapatalk
[Oukitel (All phone models)] DerTeufel1980:
Yes... But my time is very limited currently
[Oukitel (All phone models)] ace794:
Thank you.take your time.i'll be pleasantly waiting

Στάλθηκε από το K6000 Plus μου χρησιμοποιώντας Tapatalk
[Oukitel (All phone models)] FPS_drop:
Ouketl u22?

Hi! I was wondering if you could make a rom for the oukitel u22? I can't find any custom roms for it. :(
[Oukitel (All phone models)] tonymarkoc:
Is this worth updating? Or should i just wait for the new version? thx
[Oukitel (All phone models)] voshchronos:
What screen on times are you guys getting with this rom?
[Oukitel (All phone models)] neovaughn:
where is MAD OS with android 8.1 from Oukitel K6000 PLUS??????????

WE NEEDDD!!!!
[Oukitel (All phone models)] vaggos_vankel:
+1:fingers-crossed:
[Oukitel (All phone models)] DerTeufel1980:
I need to check/fix some performance issues on 8.1 first
[Oukitel (All phone models)] neferkar:
Thank you very much.

we all really need this rom

we wait
[Oukitel (All phone models)] :
We are waiting this rom! Thank you very much
[Oukitel (All phone models)] CraschTD:
Twrp oreo fails to start

I have the same problem. Flashing twrp oreo, when starting the phone flashes five times and then remains gray.

With Jemini TWRP 3.1.1 it start in recovery correctly, but when I try to install Oreo ROM I got "Updater process ended with ERROR: 7"

Tried to redownload zip files and reinstall, but I've got same behaviour.
[Oukitel (All phone models)] DerTeufel1980:
If the oreo trwp does not work, chances are almost 100% the rom would not work as well.

Are you familiar with adb shell?
[Oukitel (All phone models)] CraschTD:
Yes, i'm familiar with adb...

I found a workaround...

I modified updater-script removing the first two lines when it checks for version and model... (I know it's dangerous :p)

Anyway rom installs ok, now I'm installing gapps... finger crossed...

edit: Oreo installed and everything seems working fine!!! So far so good.

Waiting for 8.1... great job!!

edit 1: screen turned off and didn't came back... Phone still alive. Tried to reboot it but after the oreo logo it went black and restarts itself.

Tried reinstalling ROM but till now same behaviour :(

Edit 2: restarting phone in safety mode (press Vol- on restart) I got to the rom. So it's something loaded on startup. How can I troubleshoot that?

Edit 3: attached adb bugreport done with phone working but with black screen

Edit 4: installing gapps solved the problem! But now lots of FC on gapps! Retrying with pico version.

Edit 5: formatting f2fs cache partition with TWRP Jemmini screws up things

Edit 6: attached logcat of google play services fc

Edit 7: repeated everything from the beginning and now no more FC, when screen turns off it didn't come back (phone is working fine except this)

It seems that to solve this problem we have to know why Oreo TWRP is not working (blank screen) and Jemmini 3.1.1 does.

put phone in fastboot mode

Attach to pc

start with TWRP Jemmini with

fastboot boot recovery.img

In TWRP full wipe and install MadOs, gapps

After starting MadOs enable debug mode (to ease restarting from adb)

attached logcat of display not showing (screenblack.txt)
[Oukitel (All phone models)] CraschTD:
I know that I shouldn't ask for ETA, but...

I have to decide if it's better to wait for 8.1 (hoping my problem will be fixed) or returning to 7.

Thanks
[Oukitel (All phone models)] :
News on update?
[Oukitel (All phone models)] DerTeufel1980:
We're working on it
[Oukitel (All phone models)] jmaciel_:
I wanted to know with return version nougat android 7. factory version. wanted to know procedure
[Oukitel (All phone models)] Breathewave:
You need Oukitel's Stockrom from the website and a recent version of the SPFlashTool (I'm using it on Arch Linux -> AUR package). The scatter file you need is part of Oukitel's Stockrom archive.

-> Backup you stuff first, especially the internal storage! Your SD card won't change at all.

-> Turn off your phone, start SPFlashTool, select the driver and scatter file.

-> Use "Download only" from the drop down menu below and hit the "Download" button above.

-> Remember: the entire internal space will be overwritten!

-> Hold Volume + and plug in your USB cable. If you get an error message, use another driver for flashing your phone.

Good Luck :)
[Oukitel (All phone models)] bakker_be:
Orange State, any fix?

Hello, after a previous f***-up, resulting in a "Red state" bootloop, I seem to have succeeded in flashing this ROM. It still gives an "Orange State" warning though. Is that "as expected" or is there a fix for that?

EDIT: it seems that quickcharge doesn't work in this ROM ...
[Oukitel (All phone models)] Breathewave:
In order to remove the "Orange State" message, you need to lock the bootloader again with "fastboot oem lock" + Volume up.

The battery capacity is wrong within the ROM (4500 mAh vs. "real" 6080 mAh), so turn off the phone to make use of the quick charge feature used by the device's firmware. I noticed no severe additional time while charging it.
[Oukitel (All phone models)] bakker_be:
It seems that Bluetooth isn't working very well ... I have several bizarre symptoms, all when connected to my cars (VW Golf VII) infotainment system. I don't use Bluetooth anywhere else. None of these symptoms were present in the original ROM

-Streaming off-lined Spotify or Tidal content isn't always fluent. I get a lot of "stuttering", as if it's rebuffering

-I can't use it to make a phone-call. It just reverts to the handset

-It doesn't seem to really save the connection. Each time I get into my car I get a new pairing request. On the phone I only see the one device for my car, but in the car's paired devices list a new entry is added on each connection

-It doesn't keep a custom name after a reboot. I renamed it to "K6000" in stead of the default "Oukitel k6000_plus", and after a reboot it has reverted to the default
[Oukitel (All phone models)] bakker_be:
Hmmm, that gave me "red state" again :( Trying to solve it again, using this thread https://xdaforums.com/android/general/fix-orange-bootloop-oukitel-k6000-plus-t3747273 as before ...

EDIT: That didn't work. Thinking it was because of the locked bootloader, I unlocked it again, and now at least my phone starts up again ...
[Oukitel (All phone models)] DerTeufel1980:
You can't use a custom rom with locked bootloader
[Oukitel (All phone models)] :
How much time we need to wait for a perfect version offline Oreo 8.1? 1/2/3/6 month?
[Oukitel (All phone models)] cojo11:
When its ready!!

Its going not Faster when everbody ask
[Oukitel (All phone models)] b3stw4y:
Hi everybody,

my battery lifetime has decreased significantly since i flashed this rom, had the stock android 7.0 on it before

is it normal?

and also my touchscreen is not working sometimes, but this was also on the stock rom a problem, so i think it's a hardware failure.

someone got the same symptom?

greetz
[Oukitel (All phone models)] aiman36:
is this gonna work on sharp z2
[Shield Tablet Q&A, Help & Troubleshooting] tgregi:
hi, today I bough used (one year old, still in warranty) shield k1 and battery drain, even when not playing, is like 1% a minute. Also recharging is pretty slow. I have stock rom noughat version 5.2 and I did factory reset. I found some issues occuring after update to 7.0. But I can't find anything how to fix it. and also I'm not sure if battery can be dead after one year or if it's software related... Please see attached picture

Should I root and try some custom rom? I will stop my warranty:(
[Shield Tablet Q&A, Help & Troubleshooting] fpozar:
Rooting doesn't void warranty and you can always simply unroot and go to stock ROM, so I suggest you to flash latest stock ROM to get the newest firmware (the one for faster charging) and then you can flash which ever custom ROM you like the most.

Edit : so to answer your question, this is far from a good battery life, but I am 95% sure that with customisation you can make that better. When you do that we can evaluate the health of your battery.
[Shield Tablet Q&A, Help & Troubleshooting] mirrin:
My shield on tesla rom took 6 days to go from 100% to 20% idleing. It took my charger 2 hours to put it back to 100%
[Essential Phone Questions & Answers] lemonspeakers:
I did a full wipe of the Essential phone, and I realize that I only have 100GB of storage space as opposed to the 128GB. That's a full 28 GB of lost storage space! Where did it all go?

With the Oneplus 5 (128GB), I have 116GB after a full wipe.

Where is all that missing storage going towards?
[Essential Phone Questions & Answers] JoRocker:
System uses 21 GB, so....... 107.... Although mine says 21GB system after backup and videos/photos stored, and many apps installed. So about 110's sounds right.
[Essential Phone Questions & Answers] garywojdan81:
Doesn't this have the A & B system partitions going on? That's gotta account for some of it.
[Zooper Widget General] malhyp9:
Hi there I have a xiaomi mi mix with Zooper pro installed, I have created several buttons and find that they don't open the apps that I have linked them to all the time. Sometimes they work 60% of the time. After a reboot they don't work. After pressing several things all of a sudden okay. Any suggestions?
[Zooper Widget General] krianne:
I also have the same issue. I'm currently using a widget (Parrot / ZW23) and setting the buttons do not work. The only thing that works is the app drawer but that was already pre-set.
[Miscellaneous Android Development] RemusW:
I know that this source is not Lineage but I would think the basic principles for building for an supported device under Lineage would also be applicable to any other source repository.

All of the guides I have found only tell you how to build for a supported device and not any help for an unsupported one. I figured out how to sync a suitable device tree and kernel etc but since the rom source repository does not support my device I can't go any further. I can't get it to build from my sync'd local sources it keeps trying to pull stuff from the original source repository so builds fail at the start.

I have setup a local manifest for this project that sync's the device tree and a kernel and the proprietary blobs and this sync completes without error. next I ran - source build/envsetup.sh and then brunch hlte (not a supported device I know) but that throws up this error -

build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.

Device hlte not found. Attempting to retrieve device repository from GZOSP-Devices Github (http://github.com/GZOSP-Devices).

Repository for hlte not found in the GZOSP-Devices Github repository list.

If this is in error, you may need to manually add it to your .repo/local_manifests/gzosp_manifest.xml

build/core/product_config.mk:248: * Can not locate config makefile for product "gzosp_hlte". Stop.

So I think that the error basically means that github.com/GZOSP-Devices does not have the hlte device listed so can anyone tell me how to make the build point to my local repository after I have sync'd so that it at least starts to build ?

I am a newbie to rom building and have much to learn but I would really appreciate any help you guys could give.

Thanks in advance for any an all help offered.
[Pixel C General] peterk-1:
Keyboard maps for all supported languages https://android.googlesource.com/device/google/dragon/+/oreo-r6-release/DragonKeyboard/res/raw?autodive=0/
[Pixel C General] clot81:
I shall wield the power of grep and post just the ralt-mapped keys from the OP.

# US key character map for Google Pixel C Keyboard
key 1 {
ralt: replace ESCAPE
key 2 {
ralt: '`'
ralt+shift: '~'
key 9 {
ralt: '['
key 0 {
ralt: ']'
key O {
ralt: '['
ralt+shift: '{'
key P {
ralt: ']'
ralt+shift: '}'
key EQUALS {
ralt: '\\'
ralt+shift: '|'
[Pixel C General] clot81:
unfortunately i'm not getting these keys in either terminal apk i'm using.
[Pixel C General] locuturus:
I've found that in lineage os I no longer have several of the old key combinations working. I'm not sure what the underlying issue is or when it first occurred but I do recall that on stock Pixel C firmwares there was a system app for the keyboard and it managed firmware updates and also apparently overrode the system's key layout file because if you ever had a look at that file you might have noticed the keyboard was configured to support several combinations that actually never worked. A delete key for example.
[Honor 9  Themes, Apps, and Mods] wyko2k:
Hey guys,

any chance to configure the h9 like an p10? i mean with navigationbar activated?

thanks! :)

Oh sry, i thinked i post in Q&A section... pls move
[Honor 9  Themes, Apps, and Mods] Honor9Fan:
You can install a app from playstore that is adding a nav bar like that. There are some apps for this.

But why when you have real buttons on the honor9 ?
[Honor 9  Themes, Apps, and Mods] Anewkine:
:confused:

Hello,

What is the name of this application please?

Because for me it is impossible to show a navigation bar without having a rooted device and even less with a Rom Stock.

I am interested if you have the solution.

Thanks in advance.
[Honor 9  Themes, Apps, and Mods] Honor9Fan:
Search for "button remap" on google playstore. You will find some of these apps.