yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9+ Questions & Answers] varcor:
Here's why it's shady. Before you pre-order, Samsung's website only provides general features about the device. After you pay, only then can you download or view a Users Manual on Samsung's website. There are many variants with Galaxy devices and you should have the right to know what the features and capabilities are BEFORE you pay for the device.
[Samsung Galaxy S9+ Questions & Answers] Superguy:
No, unlocked as in SIM unlocked.
[Samsung Galaxy S9+ Questions & Answers] Averix:
Not sure why you think this is shady. Typically, unless it specifically states Dual SIM, you should always assume it's a single one. The dual ones are not very common in the USA at all so why would the unlocked version be dual?
[Samsung Galaxy S9+ Questions & Answers] greycaptain:
I could have sworn when I first looked at the specs on the Samsung site before I did a pre-order it listed the device as being Dual SIM. Maybe they just had a generic spec list that included specs for International variants, but I was under the impression that it would be Dual SIM. That might be why the person above thought it would be as well.
[Samsung Galaxy S9+ Questions & Answers] BhamItGeek:
heh... not sure why you feel it's shady. Dual sim phones are 90% all the time international models. US models are single sim, unless otherwise specified.
[General Questions and Answers] gwolfu:
Hello there talented bootanimation creators,

Now am not sure how many of you know about the custom Android ROM named crDroid, yet so far we reached v4 based on Android Oreo.

With the advent in the Oreo realm, we wanted to ramp up a bit on the style of our bootanimation and also get the community a bit closer to our builds, so on behalf of our team, I would like to request a new bootanimation from the community.

Anyone can be part of this.

You can find our logo here https://androidfilehost.com/?fid=818070582850500135

So who's up for the challenge?
[Samsung Galaxy S9+ Questions & Answers] siulrei:
Someone have a solution to have a full picture on the call service? I hate the small circle I want a full hd picture on incoming calls sorry my bad english
[Samsung Galaxy S9+ Questions & Answers] tsiglas:
We will have to wait for someone to try and fix some "overlays" like the one's we had on NOTE 8 & S8+ that they have made the circle caller picture 100% bigger and maybe more.... But don't wait to have full 18:9 picture....

It was working in all devices with android 7 even on A3, A5, A7 2017 with Samsung experience UI
[Samsung Galaxy S9+ Questions & Answers] siulrei:
I see thanks for the reply :D
[Miscellaneous Android Development] DerTeufel1980:
​

This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:

Micromax Canvas 5 E481

Blu Life One X

Myphone 36

Qmobilez10

madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Working:

RIL (Calls /SMS, Data connection, etc)

Wifi

Bluetooth

FM Radio

All Sensors

Lights;

Both storages & MTP

HW de/encoding

Camera (photos and video)

GPS & aGPS

Audio

madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)

Not working:

XDA:DevDB Information

madOS_O_FEVER, ROM for all devices (see above for details)

Contributors

DerTeufel1980, fire855, superdragonpt

Source Code: https://github.com/MediatekAndroidDevelopers

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.x

ROM Firmware Required: unlocked bootloader, twrp

Based On: AOSP

Version Information

Status: Stable

Created 2018-03-13

Last Updated 2018-03-13
[Miscellaneous Android Development] O_G:
Duplicate thread, original here:

https://xdaforums.com/android/development/rom-official-mados-wiko-fever-clones-t3762800

[MENTION=4196889]DerTeufel1980[/MENTION], please only open one thread per subject matter. Cheers
[Windows Mobile Development and Hacking General] bluesky3012:
Hi, first of all sorry if i post in the wrong sub. i was really curious if we can change the language support for our t9 or xt9 on our windows mobile devices, i know there's a lot of phones/smartphones that has t9 support in their local language. any ideas guys? i'm trying to get indonesian language t9 support.

thanks in advance!

ps: i did search and found that the only similar thread is for wm smartphones ( non touch screen).
[Windows Mobile Development and Hacking General] bluesky3012:
no one?? at all?
[Miscellaneous Android Development] DerTeufel1980:
​

This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:

Micromax Canvas 5 E481

Blu Life One X

Myphone 36

Qmobilez10

madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Working:

RIL (Calls /SMS, Data connection, etc)

Wifi

Bluetooth

FM Radio

All Sensors

Lights;

Both storages & MTP

HW de/encoding

Camera (photos and video)

GPS & aGPS

Audio

madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)

Not working:

XDA:DevDB Information

madOS_O_FEVER, ROM for all devices (see above for details)

Contributors

DerTeufel1980, fire855, superdragonpt

Source Code: https://github.com/MediatekAndroidDevelopers

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.x

ROM Firmware Required: unlocked bootloader, twrp

Based On: AOSP

Version Information

Status: Stable

Stable Release Date: 2018-03-19

Created 2018-03-13

Last Updated 2018-03-22
[Miscellaneous Android Development] DerTeufel1980:
Changelog 19th March 2018:

fixed offline charging

fixed proximity and light sensor

fixed applying smartwake settings after reboot

Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
[Miscellaneous Android Development] DerTeufel1980:
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used :)
[Miscellaneous Android Development] Rick02:
Thank u so much sir...we owe you?
[Miscellaneous Android Development] mrmazak:
Here is firmware folder(baseband) from Life One X with MM update.
[Miscellaneous Android Development] FERRARI81:
Opened an issue about some sensors

https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
[Miscellaneous Android Development] superdragonpt:
Great

This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc

For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc

About the alsps ( brightness ) what's the sensor used in blu?

We need to enabled it I suppose

Cheers
[Miscellaneous Android Development] mrmazak:
So the sensor.lib from Blu?

I will pull it and share.
[Miscellaneous Android Development] FERRARI81:
Ehm...I have not blue, I have original Wiko Fever

And...I'm noob :p ...in wich way I could check what's the sensor?
[Miscellaneous Android Development] mrmazak:
just because adaptive brightness is not working , does not mean it is the sensor.

If sensor was not working , there is another test (check) you can do.

make a call, then put phone to head and see if screen goes off.

I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.

I am away from my LOX now and for few days , so cant give direct test of light sensor.

attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.

I believe on oreo they go into /vendor/
[Miscellaneous Android Development] QUIZILLA:
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??

I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65. :)

Thanks
[Miscellaneous Android Development] FERRARI81:
It doesn't work in call too : the screen is always on.
[Miscellaneous Android Development] DerTeufel1980:
Please remove the quote of the whole FAQ. This is totally useless to ask your question...

You need to flash wiko mm rom first

I'll check it today
[Miscellaneous Android Development] Rikadoo:
Hello, I write from Padova, Italy,

I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.

Can I do this update procedure with this problem?

I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.

Riccardo

:pianto:
[Miscellaneous Android Development] DerTeufel1980:
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
[Miscellaneous Android Development] Rikadoo:
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.

If I copy the ROM on the SD card. Can I then install?
[Miscellaneous Android Development] mrmazak:
I am in process of installing new oreo twrp and MADOS.

During install of TWRP, I loose adb authorization. (adb session is "unathorized")

in "prop.default" it has

ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0

is this intentional?

additional question,

Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.

I think the adb auth problem is my pc, my other phone just started to do this too.

edit:

I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.

tried just adding blu files ontop of original rom files.

tried removing rom files and adding blu files

tried removing whole folder then adding blu folder

each time I get unknown baseband.

I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
[Miscellaneous Android Development] Rikadoo:
One and more questions,....

1. Our bootloader is blocked or already unlocked?

2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?

3 if isn't locked, how I install a custom recovery like twrp manager?

4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?

5 at the end, from twrp can I flash the ROM Oreo?

AHH , last question, can I flash this ROM from my phone with Android MM?
[Miscellaneous Android Development] DerTeufel1980:
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us
[Miscellaneous Android Development] DerTeufel1980:
Does it show the baseband in settings, about device?
[Miscellaneous Android Development] macadamlee:
The baseband is unknown and the sim cards doesn't works either
[Miscellaneous Android Development] DerTeufel1980:
Sim cards can't work without baseband.

Please try flashing wiko stock rom, with 'firmware upgrade' mode in sp flashtool.

Just replace the preloader of the wiko stock rom, with the preloader of your stock rom.

Then boot up and check if baseband and your imei number are fine. If they are, you can update to madOS again.
[Miscellaneous Android Development] Harishwarrior:
Bro...we need an update badly...

---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------

https://t.me/teammaxmtk
[Miscellaneous Android Development] _vvi_:
Hi, I just installed madOS on my wiko fever. There was a strange situation after first boot:

Inside settings with each chosen option (screen, info, sound etc) there was some noise from the speaker similar to sea waves. Also IMEI was not OK for both sim cards.

For me it was not a problem cause before loading madOS I backed up my whole original rom with nvram etc.

But when I entered to TWRP once more and reloaded to the system( without any additional actions / restoring the files) strange noise disappeared and proper imei was restored.

Is it possible to restore original functions of camera? lack of picture in picture and videos in fullhd will be a very painfull.

PS: I have problems with root - on superSU i receive boot image patcher ... decompressing ramdisk failure, aborting. What to do to fix this?
[Miscellaneous Android Development] mrmazak:
I can only respond to the superSU question.

The supersu installer is not compatibale with the compression used with this boot.img , so can use a modified boot.img (other compression) or use Magisk to root. And as noted in the OP. his suggestion is to use majisk anyway.
[Miscellaneous Android Development] yourrealking:
I finally succeeded in installing this on BLU Life One X. For others who wants to do the same thing, here is what I did: https://xdaforums.com/general/general/how-installed-mados-oreo-8-1-blu-life-t3802502

I would expected it would be an alpha or beta quality (even that would be better than the outdated, spyware-ridden BLU stock rom), but it worked very well. It feels as if I bought a new device. Seeing how this hardware perfectly run Android 8.1 and apps, it is sad that many people are likely throwing this phone away because it never gets software updates from the manufacturer.

I hope there would be updates to the mad OS from time to time...

[IMG="Screenshot"]https://i.imgur.com/Te5yhra.png[/IMG]
[Miscellaneous Android Development] Harishwarrior:
Unknown baseband...
[Miscellaneous Android Development] _vvi_:
OK thanks. Magisk and root working.

after testing the rom

+ very fast

+ good cpu governor

+ battery...

- sometimes is loosing the internet connection.

- only battery thermal sensor can be checked

- lack of live mixing front and rear camera video/picture like in original Fever software

- only 720p video
[Miscellaneous Android Development] yourrealking:
Yeah, the baseband is "Unknown", and the phone does not recognise the SIM card. I have tried searching for a solution, but I could not find one. So, just to be sure, currently there is no way to get the SIM working on BLU Life One X with this ROM, is there?

It is not that I desperately need to get cellular working on this phone, but if there is an easy way to fix, why not, I would fix it. By the way, I have used this ROM for days, and it is very usable.
[Miscellaneous Android Development] Harishwarrior:
There is a solution I think...
[Miscellaneous Android Development] DerTeufel1980:
Please check the instructions on first page. There's a link for extra steps for blu
[Miscellaneous Android Development] Teblakuda4o4:
Guide on installing MadOS on Blu on Page 9 of this forum. There are also other revised guides for this floating around, look around a bit.
[Miscellaneous Android Development] Harishwarrior:
Bro...don't ignore me...

Just tell me whether wiko fever will get a update from your team or not...
[Miscellaneous Android Development] DerTeufel1980:
I am just not answering questions twice, especially not by private messages
[Miscellaneous Android Development] itsjustkarim:
Follow these instructions: https://xdaforums.com/android/development/rom-official-mados-wiko-fever-clones-t3762800
[Miscellaneous Android Development] yourrealking:
I tried from the start again, and I succeeded in making the baseband be recognised in the Fever Marshmallow V34, but there were lots of "not booting" issues after flashing the "modem fix" zip or flashing the madOS, so I overwrote some partitions like system or user data, etc (I do not exactly remember), and when I finally booted up to madOS, the baseband was unknown, again. Well, it took me hours and I got nothing.

I guess I will just use it as a Wi-Fi only device, until someone smarter than I posts here a foolproof flashable BLU Life One X baseband fixer for madOS.
[Miscellaneous Android Development] Teblakuda4o4:
Flashed a Modem Fix? U shouldnt be flashing any modem fixes.
[Miscellaneous Android Development] Deemo13:
Thanks for this write up! I have MadOS installed successfully on my Blu Life One X using the installed guide. I installed from stock MM up to this with little to no issues. Performance is better than on the stock rom for sure! Used Pico Gapps for lightweight install.

The only thing I cannot get to work that well is the Google Assistant. Any ideas?
[Miscellaneous Android Development] DerTeufel1980:
Google assistant needs the bigger gapps package. Pico is missing required libs
[Miscellaneous Android Development] Harishwarrior:
Google assistant works fine...

Install and update Google app

Then go to settings > App and notifications > Advanced > Default apps > Assist & voice input > change it to google

---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------

Keyboard swipe to type is working on Google keyboard...
[Miscellaneous Android Development] pakrett-bm:
Can we expect a new build ?
[Miscellaneous Android Development] DerTeufel1980:
You can always expect a new build, and we didn't stop developing, but I can't tell you a date
[Miscellaneous Android Development] Harishwarrior:
Live long MAD os?
[Miscellaneous Android Development] Deemo13:
This was definitely it. Thanks!
[Miscellaneous Android Development] Harishwarrior:
No bro...we have all the libs...

We just need to manually update Google app
[Miscellaneous Android Development] cgigate:
Flashed to the latest version madOS_8.1.0_fever_20180318 to to my BLU life one X 2016,

No mobile signal ....looks no baseband ...

I have to flash back to the stock to use my phone again, sigh !
[Miscellaneous Android Development] Teblakuda4o4:
You need to go through a specific installation method to get it working on Blu. Look through the pages here and you'll find it. Can't remember what page it is exactly.
[Miscellaneous Android Development] Harishwarrior:
Empty folders got created for every picture...
[Miscellaneous Android Development] Harishwarrior:
I am using stock MAD camera and Google camera- version 4.1.006.126161292
[Miscellaneous Android Development] asdkazmi:
This rom is for which device?
[Miscellaneous Android Development] g0didit:
Hi,

Can I flash this image on Ulefone Paris? (I think phones are identic according to specs)

Do I need some extra steps?

Thanx.
[Miscellaneous Android Development] Harishwarrior:
Nope it won't work...

If you flash it you might brick your device...
[Miscellaneous Android Development] g0didit:
Why there in no rom's for Paris?

Last rom I use is MIUI rom, but I need more AOSP rom. Anyone can make rom for Paris or provide how to change this rom to fit Paris?

I found also rom for Ulefone Metal but it wont work on Paris....
[Miscellaneous Android Development] DerTeufel1980:
Huh. This is weird... No one reported this ever before on any device/version...
[Miscellaneous Android Development] Harishwarrior:
Ah..man? I am the only one who takes time to report bugs...
[Miscellaneous Android Development] Harishwarrior:
When you edit any picture via default gallery app and while saving your pic ...you can see some developer error toast messages...

---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------

Donate a ' Paris ' for team MAD then you will get roms for your 'Paris'

---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------

Nokia 3310
[Miscellaneous Android Development] Harishwarrior:
Here is the error...
[Miscellaneous Android Development] superdragonpt:
...

iPhone 10

...
[Miscellaneous Android Development] superdragonpt:
sure .. That's what the title says...
[Miscellaneous Android Development] DerTeufel1980:
This also doesn't happen to me. There's no single empty folder

Yeah... We need to check this
[Miscellaneous Android Development] Harishwarrior:
you guys can replace the wiko baseband with the Blu baseband and zip the ROM....that will work... cause the baseband file won't change during compile...because we don't have source for that...
[Miscellaneous Android Development] zseoer:
Hope they will solve it soon...hhad
[Miscellaneous Android Development] Harishwarrior:
To the Dev of MAD OS:

I am trying to mod the mad os by changing the baseband file to fix the Blu baseband issue...

But I can't find the baseband file in the zip...

And which tool should I use to unpack the brotli zip

Where is the baseband file located..?

Help me guys...

Thanks in advance?

Update:

I found the baseband file in vendor/baseband

But there is a lot of files changed than Wiko fever...

And the clones doesn't have that much file..will it work when I replace ...and we have no other choice than that cause we don't have sources for baseband...
[Miscellaneous Android Development] ILoveTech!!!:
Hey there, first of all, thank you for your work. I'm using Casper VIA M1 (Wiko Fever clone) 32GB ROM/3GB RAM.

I flashed this rom and everything is working, expect the microphone. When i record my voice, there is too sizzles. I almost can't hear my voice. But if i raise up volume to latest, there is too sizzles, but i can hear my voice barely. When i make a call, my voice can't go to other side,but i can hear him who is on other side. I also tried port audio.primary.mt6753.so from my stock MM firmware,but this time i lose audio completely. What can i do?
[Miscellaneous Android Development] Harishwarrior:
To the devs:

Add Casper via M1 (mt6753)

One of our device clone..
[Miscellaneous Android Development] Longhorn87:
Hello, can i install this rom on a Wiko Fever Special Edition 3/32 GB?
[Miscellaneous Android Development] Harishwarrior:
yes you can..

just follow the guide for wiko fever properly
[Miscellaneous Android Development] ILoveTech!!!:
There's ways to tried work microphone on madOS:

-Change audio.primary.mt6753.so and audio.primary.default.so from my VIA M1 MM firmware (completely lose audio).

-Change all audio files from my VIA M1 MM firmware (phone stuck at last boot anim)

-Change kernel (stuck at bootloop)

But i think maybe it's caused from NVRAM, because when im on stock VIA M1 MM firmware microphone works perfectly but when i switched to Wiko Fever 4G V34 MM ROM there's exact issues on madOS. I compared NVRAM from Fever and VIA M1 and i see at media folder there is plus 2 files on VIA M1's NVRAM and this files about mic and media.
[Miscellaneous Android Development] Harishwarrior:
Try to find your audio device driver...if it has one..
[Miscellaneous Android Development] Deemo13:
Just in case anyone comes across it in the future, I was able to successfully flash the Low-RAM Property Patcher for Android and noticed a significant speed improvement.

What do you guys think? Using the Blu Life One X.
[Miscellaneous Android Development] Harishwarrior:
Well we have plenty of RAM and why did you patched that...it may improve speed ...due to other tweaks included in it...
[Miscellaneous Android Development] Harishwarrior:
Wait a minute...why you guys didn't released the update you made in this built (the update with mtk volume controls and some sensors fixed)...please release it...if you can..

I have that built as user-debug

But I want you guys to release it as normal built...cause I need to wipe data in user-debug built