yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] :
Cannot install Magisk ...not foreseen?
[Miscellaneous Android Development] RalphMalph:
About 4K recording. It is working on not all devices. Some have it, some not. This is what was already found in test. That is probably the reason why Vernee never implemented it good. This is the same as on the Apollo X. If you don't have it, your phone hardware is the problem. I have also no 4K but my wife has. Ordered different dates.

---------- Post added at 10:03 PM ---------- Previous post was at 09:51 PM ----------

Real nice job MAD-guys. My first impressions is that it is really looking very good! Everything works great.
[Miscellaneous Android Development] honzyn25:
Magisk installs and works.
[Miscellaneous Android Development] Xorianator:
Agree, Magisk is working like a charm
[Miscellaneous Android Development] fire855:
We couldn't experience any performance problems that's why we enabled it by default. Enabled encryption still provides you more security than without. No one can just boot into TWRP and access your data. Someone would need way more experience and time for actually getting to your data (if someone finds a vulnerability in mediateks trustzone or can somehow access it).

If you really think it's useless, then you can flash Magisk for example and then force encryption gets disabled. I think formatting data in TWRP and rebooting should keep encryption disabled (I haven't tried this). Magisk removes the force encryption flag.
[Miscellaneous Android Development] fire855:
It shouldn't have an noticeable impact on the X20. The SoC is fast enough for handling this easily.

Yes, you can use TitaniumBackup for restoring your apps.
[Miscellaneous Android Development] fire855:
You can try to flash Magisk and format data in TWRP. Magisk should disable force encryption.
[Miscellaneous Android Development] RalphMalph:
Magisk works without a problem
[Miscellaneous Android Development] regnodulous:
If you have problems with the latest rom... Especially if sensors stop working

So I flashed the latest rom and had issues with my proximity sensor. So then I tried to wipe everything on the phone using TWRP and this seemed to cause my phone to get stuck on teh MAD screen when booting. I tried a backup and various other tricks but this is what worked to get me backup and running...

1. Restore your phone to the factory ROM using this guide and the ROM package downloaded from this website (and SP Flash Tool). getdroidtips com/install-official-stock-rom-on-vernee-apollo-lite (it won't let me post a URL here so you will need to add the . back in between the getdroidtips and the com)

This will restore you to android 6 and restore the stock recovery.

2. Factory reset your phone.

3. Reflash MAD rom using the SP Flash tool method. This will wipe everything again pretty much and restore TWRP for recovery.

4. Boot into recovery FIRST before booting into your new rom and install GAPS.

5. Boot into MAD rom

Everything now seems to be stable and working and my sensors are working again.

Cheers

Nat
[Miscellaneous Android Development] gbl08ma:
Thanks, this is what I figured, as all the Cortex cores in the X20 have cryptography extensions (extra instructions that accelerate common AES data paths). I'm still afraid not being able to mess with the data partitions as freely will later bite my hand, but I'll still try to leave encryption enabled for the sake of having a clean environment for bug reproduction, at least for the first days.

I can't wait to find out if my phone supports 4K. I suppose they changed sensors (or sensor revisions) at some point? Would explain why the camera on mine is mediocre in certain conditions, more than the reviews led me to believe. It's bad even when compared to the one on my other four year old phone
[Miscellaneous Android Development] RalphMalph:
MMS? Ehm you are still using that?

In The Netherlands i think all providers stopped using MMS from 1 July 2017.

I think i didn't use it the last 5-7 years
[Miscellaneous Android Development] gbl08ma:
[MENTION=5151414]Xorianator[/MENTION], just for the sake of completeness, you might want to add this to your guide: link :D

My phone just completed the first boot. It was quick, but the screen turned off as soon as it finished booting, before even showing the SIM PIN entry screen. Might want to improve that ;)

I did not lose the IMEIs.

For me, 4K option is available in the stock camera. And it really records in 4K H265. Proof (for me, VLC has some problems playing the file, but the Windows 10 movies player plays it right, as well as the phone. Also, Chrome appears to think that's a audio file. Download instead).

The proximity sensor is working for me (at least, I tried making a call and the screen turned on and off as it should).

Now on to connect to Wi-Fi, set up accounts, reinstall apps, root... ugh. I think it will all be worth it in the end :) Great job team M.A.D. :good:
[Miscellaneous Android Development] mlara.particular:
Hi, I keep getting this error when flashing magisk v. 13.3:

[IMG="temp flash magisk"]https://xdaforums.com/picture.php?albumid=14113&pictureid=56064[/IMG]

https://xdaforums.com/picture.php?albumid=14113&pictureid=56064
[Miscellaneous Android Development] smilie108:
I have installed magisk 13.3 without trouble

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] skylineone044:
Hi!

Successfully flashed, with magisk, everything works!

But it would be nice to be able to initiate split-screen mode by holding down the square(multitasking) button too.

So far so good! :)

Nice work!
[Miscellaneous Android Development] RalphMalph:
I cannot see a picture attached to your message
[Miscellaneous Android Development] superdragonpt:
Well about the release:

This ain't " just another" normal update

This is a full new BASE ROM, built by us.

We had built Android Nougat in fully for this device,

( Unlike vernee that promised this .... )

this means there's no more old MM "blobs " or frameworks ,etc from MM.

Everything was upgraded...

About 4k:

Some may not have it, just like in stock ROM of Vernee. The cause?

The only thing I can think of, is hardware revisions, why?

Well some models use different nand part, as well as different PDAF of main camera.

Some devices use one main sensor, others use another.

About force encryption:

Our main concern is "security" , always been, ever since we started with old KitKat builds

( other devices) , not only on just kernel , but on the whole system.

Force encryption won't bring any less "performance" all the cores can handle this just fine...

This brings a new layer of security to your device and your precious data.

If one wishes to disabled it, just because... You can do it easily with Magisk

Cheers
[Miscellaneous Android Development] Black Manta:
If we want to change to another rom, do we have to flash the vernee stock rom with SDFT before because this release is specific for your rom?

I also think that because it's the first third-party-rom I have to flash with SPFT. :D
[Miscellaneous Android Development] superdragonpt:
You can always return to stock ROM at any moment

Just flash original vernee Marshmallow on SP FlashTools with upgrade mode

Bb
[Miscellaneous Android Development] Black Manta:
I mean if I want to change to for example LineageOS, do I have to flash stock rom before? Because I don't know what you have all changed in the partitions. :D

Nobody want's to go back to stock from your rom! :D
[Miscellaneous Android Development] superdragonpt:
No idea then... Never flashed those other ROMs, and I don't want to try that now hah

Probably... Probably.... You may need to flash stock MM Vernee first yes...

Bb ;)
[Miscellaneous Android Development] RalphMalph:
If you want to be sure, just flash stock before going to a different rom, but hey....

Nobody wants to go anywhere else than this rom :p
[Miscellaneous Android Development] mlara.particular:
Ralph, I deleted everything, new flash, magisk 3.13....worked...had some mix up of old data/rom with the new release, thx!
[Miscellaneous Android Development] gbl08ma:
Termux now works! Yay!

I think this alone was worth the chore of upgrading and having to setup my phone all over again :D

BTW: Magisk works fine for me too.

Also, a friendly reminder that you'll need to calibrate your battery by doing a full discharge. That's what I'm doing now. The battery is clearly not calibrated as it discharged 40% in about one hour, which clearly results in an abnormal SOT for the work I'm doing.

EDIT: Proof that screen casting now works. Casting to Windows 10 on my Surface Pro 3. Sound is casted too.
[Miscellaneous Android Development] almajnoun:
anybody have battery drain and percentage problem whit th last rom or just me in charg 47% up to 92% IN 2mn
[Miscellaneous Android Development] gbl08ma:
I experienced something like this, hence why I'm calibrating the battery... did you read what I wrote in the post above yours?
[Miscellaneous Android Development] Lorisson:
Anyone else experiencing this problem in the calibration menu or it's just me?

Inviato dal mio Apollo Lite utilizzando Tapatalk
[Miscellaneous Android Development] almajnoun:
no how to fixed pls ?

isearch and i find this method

1. Discharge your phone fully until it turns itself off.

2. Turn it on again and let it turn itself off.

3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.

4. Unplug your charger.

5. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.

6. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.

7. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.

8. Now, let your battery discharge all the way down to 0 percent and let your phone turn off again.

9. Fully charge the battery one more time without interruption and you should have reset the Android system's battery percentage.
[Miscellaneous Android Development] gbl08ma:
[MENTION=7966485]almajnoun[/MENTION], that method should work, yes. It's what I'm doing now.

BTW, I can confirm that automatic clean shutdown doesn't appear to work. Most phones I've used (and this one on previous ROMs) auto shut down at 5%, but currently mine says 3% and is yet to shut down.

Let's hope all this is due to bad battery calibration and not a bug in the ROM.

EDIT: I'm also happy to note that this ROM now reports battery tension properly (i.e. in mV and not V). This means my battery monitor now shows it correctly: link.

EDIT 2: feature idea: add an option to make long-pressing the volume up/down buttons skip tracks. This is/was an option in GravityBox, but I would rather not install Xposed just for this, especially when the Xposed on Nougat situation is... what it is. BTW, this is already supported when I long press the up/down buttons in my headphone remote. All I'm suggesting is for it to also be supported on the buttons on the phone itself.
[Miscellaneous Android Development] superdragonpt:
Yup

Battery & Thermal are different then you may experience before on stock ROM, Roms made out of "base MM" , madOS ,etc.

Then I also merged improvements:

Among the changes, you now have Pump Express working on Screen ON, something that Vernee never had ...

I would just let the device fully discharge , then full charge again for some times, then it'll be good

Cheers :)
[Miscellaneous Android Development] Rabanero:
I can confirm strange battery behaviour with this ROM version. Also, great battery drop at 15% and abnormal safe shutdown (it doesn't power off, but reboots constantly).

It charges without any issues when device is off, but if it's on, it begins with 47% and reaches 100% in less than 2 minutes.

I will try calibration method described above, but it seems it is a big ROM issue for daily use if it's still failing :(
[Miscellaneous Android Development] 007Gogi:
The display does not turn off during a call or a call.
[Miscellaneous Android Development] gbl08ma:
Follow the instructions for bringing back the proximity sensor that were posted a few pages ago on this thread.
[Miscellaneous Android Development] konsolenspieler:
Hm.. Seems like cifs support is still not implemented.

Also I thought about some other things that would be really nice to have:

1) I would like to only enable one of the features of the Magnification in the Accessibility settings and/or maybe I would like to change the activation rhythm/way because it really bugs me that Magnification gets turned on like every second when I use a macro script which clicks very fast..

2) I would like to display more things while the volume control bar is displayed after one of the volume gets buttons. E.g. the navigation bar (for guys who likes to hide their navbar normally), a custom menu with toggles (Magnification, Screenshot, etc.) or maybe even interactive or live content like Widgets, (FM/Internet) Radio, RSS or IRC..

3) Could you implement a internet browser, an ftp client and a file manager in your TWRP version?

And at last I found a bug: Sometimes when I switch Magnification on/off or if I just open it the ROM won't do any touch action. It shows were I touched (cause I enabled that in developers settings), but that's it. So I have to restart by pressig the power button for a long time..

Greetz
[Miscellaneous Android Development] Black Manta:
Yes, battery is strange. From 0-86% in one minute. ?
[Miscellaneous Android Development] gbl08ma:
I guess the changes to support fast charging with the screen on could be causing this. Perhaps, like 4K, it only works on some devices? :D
[Miscellaneous Android Development] BerniBoern:
Hello folks :)

First of all thank you for this awesome work!

Could someone explain me how to use this SP flash tool? I looked at serveral guides but its just so confusing.. I dont know which drivers etc I should use.

I previously just installed this rom via fastboot on linux and it was so super easy with just 3 commands basically (adb reboot bootloader, fastboot oem unlock, fastboot flash recovery) and then I installed the rom via recovery..

Compared to that simple process I am overwhelmed with this tool.. especially since I only have a windows PC at the moment which makes things even worse.. (drivers, adb, fastboot..)

If someone could explain me step by step what I should do I would be really happy.. thanks! :)
[Miscellaneous Android Development] DasGundi:
Hey there!

How many Points do you get with Antutu in the latest build? I'm about to change from RessurectionRemix to madOS ^^
[Miscellaneous Android Development] gbl08ma:
There really appears to be a problem with automatic shutdown. My battery is now at 3.621 V which is below the nominal voltage for lithium-ion batteries, yet the phone doesn't turn off, abruptly or cleanly.

And yes, the battery was seriously miscalibrated. It took five hours to go from 3% to 1%. This with music always playing on the loudspeaker, and occasional screen-on usage. I think I'm going to power off now and charge the battery, I don't want to damage it.

EDIT 17:08 UTC: it finally abruptly turned off, but started rebooting immediately like someone described here earlier. It's now charging...
[Miscellaneous Android Development] honzyn25:
82000
[Miscellaneous Android Development] smilie108:
[MENTION=5238428]superdragonpt[/MENTION] the voltage show on look screen does not fit with measurement on usb

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] Black Manta:
Antutu... *cough*

PS: ondemang governor and deadline IO-scheduler :)
[Miscellaneous Android Development] FoxBob79:
AMAZING how fast madOS works!! :) BIG THANKS to the whole Team...

But one question: Is there a chance to change the launcher?? I would like to install the lineageOS-launcher, but till now I have no luck to install it. Maybe an similar launcher to the lineageOS-launcher??
[Miscellaneous Android Development] DasGundi:
Thank you!
[Miscellaneous Android Development] gbl08ma:
First discharging and charging curve for my Apollo Lite after installing the latest version of this ROM (fast charging with original charger and cable):

(green = charge %, uses the left scale; yellow = tension, uses the right scale; blue = temperature in Celsius, uses the left scale)

Look at the amount of time it took to go from 3% to 1%. That is clearly wrong. This is why battery calibration is so important.

The battery temperature went up to 50 degrees Celsius at one point during charging, making the phone quite uncomfortable to handle. I believe this is why on the stock ROM, fast charging is disabled when the screen is on.

That jump from 89% to 100% at the end, means my phone, bought in November, already lost about 10% of the battery capacity. This is after about 142 charge cycles (using the same calculation method Apple uses). My older phone jumps from 70% to 100% at the end of a full charge cycle like this, but that was after three years of use...

Now on to test standby battery life. Let's find out if the deep sleep problems are really fixed :fingers-crossed:
[Miscellaneous Android Development] RalphMalph:
Yes, battery is sometimes really strange.

No idea yet why and how.

Quick charge is in couple of minutes to 50-60% but when you unplug then... The phone is empty very quicly also. It looks 50-60% charged, but it isn't i think
[Miscellaneous Android Development] Marcyvee:
First of all, thank you! You resurrected my girlfriend phone.

So, can someone link me the last firmware we need to install?

And explain the way to install it, please?

Everytime I used flash tools I get a brick or a boot loop :(

Sorry, I misunderstood! We have to flash the last zip with SP flash tools, as firmware upgrade.... Clear! XD

Thanks again
[Miscellaneous Android Development] Xorianator:
I wrote a small Installation guide which covers almost everything you need to know: Installation Instructions

As far as I understood you have to come from the 2nd latest MAD Build before flashing the new one, but netter ask about this one of the developers.
[Miscellaneous Android Development] Black Manta:
Nope, you don't. I'm coming from LineageOS without problems. :)
[Miscellaneous Android Development] gbl08ma:
So I left the phone to slowly discharge with no open apps in the foreground or the background. The screen was mostly off except for when I turned it on to disable the fingerprint reader.

My conclusion is that there is still a battery drain when the screen is off, more than what would be ideal.

Part of it is due to the fingerprint reader: from 100% to 80% (which took less than three hours), I left the fingerprint reader enabled. The phone stayed a bit warm and the few times I turned it on to peek at the lock screen, there was always a message like "Partial fingerprint detected" or other fingerprint error message. This was with the phone laying flat on a clean table. At this point, I decided to disable fingerprint unlock to see if it decreased the battery drain, and it did. The phone also stopped feeling warm to touch. So if you want good standby battery life, disable fingerprint unlock.

After that, I still had noticeable battery drain, but since some of the apps I have installed could be at fault, I'm not going to comment further.

EDIT: in case anyone's interested, here's a screenshot of wakelock detector

(deep sleep only 1h). I'm using the Gapps Nano package from August 20, SHA1 49450052f4a97db68f5b65744df7fa926b6450b9. I'm now going to greenify some more programs, but I don't think that's really the problem. Perhaps I'm better just accepting the Helios X20 is terrible at sleeping? :D
[Miscellaneous Android Development] Sasra:
i have the same problem
[Miscellaneous Android Development] comand11:
Hi, i have no Problems with the Battery, but the wlan connection isnt stable. Often sites or videos doesnt load or doesnt load completly.
[Miscellaneous Android Development] Conqinner:
Hi,

first, I want to thank you for the rom. I also have the battery problems, today I was literally 2 hours watching video on 3% of battery. Earlier in work, I tried to do some calibrating, but so far it is working oddly.

I like that the night light is working fine now since I read quite a lot. The thing that still bothers me is that I can’t see lte frequencies in band mode settings. Therefore lte is not working for me…
[Miscellaneous Android Development] qltsar:
I can confirm the strange battery behavior as well. My phone is charging at the moment and I noticed something, is that possible that the fast charging is only working until the battery reaches 80%? It has charged like normally - with fast charge - until it reached 80%.
[Miscellaneous Android Development] Black Manta:
After a complete discharge and charging from 0% to 100% with powered-off phone battery is normal.
[Miscellaneous Android Development] gbl08ma:
I have great news... this is the discharge curve since I disconnected the charger yesterday:

Since yesterday's chart, I did two notable things:

- I greenified Twidere (which was the champion of wakeups in yesterday's wakelock detector report)

- I changed the location mode from "Device only" (GPS) to "Battery saving"

The phone was in deep sleep for a whooping total of 9 h 22 m, or 59% of the time. And in the morning I had lots of notifications, from text messages to GCM notifications and even notifications from apps that don't use GCM but use periodic server polling instead - which means it wasn't so "lost" in its deep sleep that it became unware of what was going around. Just like it should :good:

Wakelock Detector screenshot

As you can see, the battery drain is now about 2 to 3% per hour. This is more in line with other phones with the same set of apps and settings. :good: It's likely you'll be able to get even better results with proper tuning and careful app selection. For example, I have two apps running which wake up the device relatively constantly: one scans for Wi-Fi networks every minute, and the other is the battery monitor that wakes up the device about every 15 minutes (and this one did wake up the device for sure, because as you can see the chart indeed contains an entry about every 15 minutes).

And to everyone still complaining about strange battery charging behavior, make sure you discharge the battery first all the way to the point where the phone abruptly turns itself off, then charge it all the way up in one go.
[Miscellaneous Android Development] rattleb0x:
Hi,

Everytime I flash the madOS ROM I lose my IMEIs. I need to go back to stock ROM and use the code *#6813# to reenter them.

This doesn't work on madOS. I've tried flashing the IMEIs with MAUImeta (won't connect to the phone on madOS though it works with stock) and Chamelephon ( this one actually f***s it up a bit more, to the point the sims no longer work )

Anyone here has got any ideas?

Thanks in advance
[Miscellaneous Android Development] superdragonpt:
This happens only if you had used "format all" ..

Using stock code to enter IMEIs is just an temp solution until data is wiped...MAUI sucks... Use SN writer

Works great

Bb
[Miscellaneous Android Development] hainbloed:
You can simply restore the NVRAM partition, e.g. with TWRP recovery or Flashtool.
[Miscellaneous Android Development] The21Calvo:
I tried to calibrate but still this problem :/
[Miscellaneous Android Development] Domnea:
I have same problem with battery, I was playing and got warned low battery 15% after few minutes I got warned again low battery 5%. I grabbed my battery bank and after 3 minutes it charged to 60%.this is not possible. Something is wrong . But overall this Rom is far better than old one.good job MadTeam.
[Miscellaneous Android Development] Tschumi:
I have the same problem with the battery, even after three callibrations. It falls abruptly from 40% to 3% and then shuts off. Otherwise is an excellent rom.