yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] superdragonpt:
Well my comrade [MENTION=4761533]fire855[/MENTION] is always b# me about same battery drops, I didn't faced as bad issues as he has been having

The latest release is a full nougat and no longer based on stock mm "blobs" and mm "kernel" so lot has changed

Well the battery issue can only be related to one thing from what I understand with the fire855 feedback and yours

He can redo some stuff surely, he is a smart guy (usually) haha

There won't be more updates from me for VAL/VAX

I just can't stand this phone, [MENTION=4761533]fire855[/MENTION] can support it if he wants...

He is also the only one that haves VAL & VAX so... Good for him he can test on both..

Bb
[Miscellaneous Android Development] DVO-er:
Really???

I only bought VAX because it's support by MADos.

Please don't leave it......:crying:
[Miscellaneous Android Development] daitalos:
__ I hope you change your mind and do not stop your work (of course, real life is more important)

anyway, thanks for this amazing rom !

sry for english
[Miscellaneous Android Development] smilie108:
I am also only bought this because of mad OS would not be happy if superdragonpt would not support anymore because the other mados phones for me not so great what hardware belongs so please don't let us in the rain? Please [MENTION=5238428]superdragonpt[/MENTION]

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] Deepflex:
Hello M.A.D team [MENTION=5238428]superdragonpt[/MENTION] [MENTION=4761533]fire855[/MENTION] [MENTION=4196889]DerTeufel1980[/MENTION]

I really need your help / advice. I made LineageOS 14.1 based on the official MTK stock 7.1.1 for 6797, but, unfortunately, I can not fix the last bug with RIL. Don't have ideas for it, with MM based blobs for RIL and Modem Firmware no results. I hope for your help, I can provide the source code on request.
[Miscellaneous Android Development] superdragonpt:
i wont be supporting, doesn't mean the team won't, support will continue, the others can do builds for this device, for the moment im just tired of this device that's all

dont worry
[Miscellaneous Android Development] Xorianator:
Well, seemed to be a long journey without happy end. Thank all of you for your efforts to keep this ROM and phone great, I did really enjoy all of your and your teams work, it's been a great time having MAD OS on this phone. Good luck for your future for other phones!

Will there be any statement by fire855 and DerTeufel whether or not they continue developing for this phone? Would be good to know at least if we can expect any Oreo or not.
[Miscellaneous Android Development] RalphMalph:
I am almost sure that madOS will stay supporting this device until their device breaks down.

They are busy with Oreo so I am almost sure we will have that soon (no ETA).
[Miscellaneous Android Development] DerTeufel1980:
Probably in December ?[emoji23]

Sent from my uhans h5000, running Android 8.0.0
[Miscellaneous Android Development] fire855:
Development will continue. The most annoying issue is fixed soon ;)
[Miscellaneous Android Development] RalphMalph:
Hahahahaha

---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------

Oh wow.

Really? Great news. Soon we get O
[Miscellaneous Android Development] gycu:
I think it was about battery drain issue, not O. Right, guys?

Thanks MAD for not giving up on us yet :good:
[Miscellaneous Android Development] fire855:
Fix for charging / battery issues

Finally here is the fix for the charging / battery issues on our last madOS release.

Flash the boot_fixed_charging.img in recovery: Install -> Install Image -> select the file -> select boot partition -> Swipe -> Reboot -> Done!

Download: https://androidfilehost.com/?fid=962021903579489605
[Miscellaneous Android Development] RalphMalph:
Weeeeeeeeeeeeeeeeeee!

Great man. Great job, Mad-team
[Miscellaneous Android Development] lifescanner:
can anyone approve this fix ?
[Miscellaneous Android Development] smilie108:
Please take care you will loose all data !! I lose all data encryption password lose THX for the patch but now i loosed all photos and downloads apps an so now i habe to reinstall whole phone

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] zed-78:
Did you wipe and Not swipe?

Gesendet von meinem SM-G925F mit Tapatalk
[Miscellaneous Android Development] fire855:
This patch changes nothing on data encryption. There is no way you can loose data just by flashing this boot image.
[Miscellaneous Android Development] smilie108:
For me it was so only install your image after reboot I got message that data encryption is wrong and only way is factory reset sorry

Gesendet von meinem Apollo Lite mit Tapatalk

---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------

Wipe dalvik and cache not right?

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] SounDWav3:
Proximity sensor

Hi guys! I have an issue with the proximity sensor. It's not working after I flashed this ROM. Any advice? Thanks.
[Miscellaneous Android Development] UNIX4ALL:
Thx !! I flashed it already on my wife's VAL, Tomorrow she will test it.
[Miscellaneous Android Development] BerniBoern:
why is every task manager app showing me that all cpu cores are stopped? I even installed a Linux container with Linux deploy and it said, that only 2 sometimes 3 cores are in use :0 (termux and htop said the same)
[Miscellaneous Android Development] joaopguima91:
After installing this fix, my adguard app cant set a proxy conection is this to be expectable? Thanks ;)

---------- Post added at 07:15 AM ---------- Previous post was at 07:05 AM ----------

I now noticed that i loose root privilegies after installing boot fix! Well if battery issues fixed i sure can live with that ! XD
[Miscellaneous Android Development] fire855:
Yes. You can install magisk or SuperSU afterwards again ;)

Gesendet von meinem Apollo X mit Tapatalk
[Miscellaneous Android Development] fire855:
Then you either has done something else in recovery or you modified the boot image somehow before. Having a rooted phone with magisk or SuperSU and then flashing my boot image doesn't break anything either. Only removes root. So you just need to flash magisk/SuperSU again.

But it can't break data encryption.

Gesendet von meinem Apollo X mit Tapatalk
[Miscellaneous Android Development] smilie108:
I only download install via install IMG and wipe cache and dalvik nothing else after reboot it show data encryption password wrong cannot decrypt data sorry

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] superdragonpt:
I don't trust him...

Haha joking, ye its fine...

That's virtually impossible

Its a kernel image, its flashed to its own partition (boot) doesn't touch on data ...

If all the cores where always working, then your device would work for like an hour or so with full battery charged...

That's how multi-cores work , it fires up more cores when more processing power is needed , this is a minimal explanation of course , google it, if you have some time ;)

Edit: likely cause it needs root privileges, just re-root again

That's normal, root is systemless, so every time boot has changed you need to re-flash root again (superSU or magisk)

Bb
[Miscellaneous Android Development] joaopguima91:
I have just one question. Will the re-root procedure alter or replace the boot fix previously installed?
[Miscellaneous Android Development] gycu:
I love you, man :victory:

It seems to work, I have half an hour without Idle Battery Drain, I cannot believe it, I'm happy :D

I flashed the image, reflashed supersu (the previous setting remained there), wipe dalvik/cache and good to go, everithing is smooth ;)
[Miscellaneous Android Development] Sax_93:
Hey, that fix Works?
[Miscellaneous Android Development] superdragonpt:
Not at all

Bb
[Miscellaneous Android Development] cedricboquiren:
Woooohoo! Back to Nougat again. My phone did not shut down/reboot by itself. I can verify that this really fixed the issue!

Waiting for the first Oreo build! ?

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

Perhaps you can still help [MENTION=4761533]fire855[/MENTION] develop this phone. ????
[Miscellaneous Android Development] RalphMalph:
Wow...battery-life was never better!

Really great job
[Miscellaneous Android Development] JohnnyWeiner:
And what about PumpExpress+ charging? Does it work fine after the fix?
[Miscellaneous Android Development] cedricboquiren:
One thing: charging is still slower compared to stock.
[Miscellaneous Android Development] JohnnyWeiner:
What does it mean? With PE+ it needs 1 hour 15 mins for me to charge from 10-15% to 100%.
[Miscellaneous Android Development] cedricboquiren:
It took me more 2hrs to charge it from 0-100, device was off.
[Miscellaneous Android Development] Sax_93:
Fixed :)
[Miscellaneous Android Development] daitalos:
first,(the easy way) you can try with an app from playstor , for example : https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset

__if this doesn't work, you can reflash mados (correctly,from the beginning - read first OP, post #2 & #3)
[Miscellaneous Android Development] RalphMalph:
Yes, it works like a charm

---------- Post added at 07:05 PM ---------- Previous post was at 07:04 PM ----------

Maybe, but do you know that Vernee uses a dangerous high voltage in the stock rom!!!
[Miscellaneous Android Development] gycu:
Phone Idle drain is still there, I think I misunderstood what this update was all about. Probably it was only about the phone restarting at 15% and the false drain from the last update.
[Miscellaneous Android Development] RalphMalph:
Isnt that great?

Or do you want to blow up your device

---------- Post added at 07:06 PM ---------- Previous post was at 07:06 PM ----------

Which idle drain???

There is no
[Miscellaneous Android Development] qltsar:
Unfotunately, I have to confirm the same situation here.

Installed the new boot.img from TWRP --> bootloop -- > rebooted to recovery after 10 minutes, TWRP said, that my internal sd is enrcypted.

So I installed the whole ROM again, rebooted to TWRP, restored my backup then installed the new boot.img --> bootloop and my whole internal storage is encrypted / lost.

Now it's booted, there is a screen says: "Encryption unsuccessful" - all I can do is reset the phone - but the 'Reset' option on the screen is not working - nothing happens.

I will try if I can make it work without restoring my TWRP backup with the previous kernel, this is really strange, but I have to confirm it smile's situation is not fake at all!

Maybe the whole problem is not with the kernel just with the recovery itself.
[Miscellaneous Android Development] Skirmitt:
Can anyone tell me how I get into recovery again ? It's been a while and I forgot, sorry.
[Miscellaneous Android Development] smilie108:
That's exactly what I had but I had no backup

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] almajnoun:
install ok no problem TWRP -->install image-->boot-fixed-charging.img-->partition boot-->swipe-->rebot

Idle drain fixed for me
[Miscellaneous Android Development] Sax_93:
The smartphone go off when the battery was 15%. Now i make some battery calibration if it is my problem..
[Miscellaneous Android Development] fire855:
You have flashed our last release with SP Flash Tool? You flashed Magisk afterwards?
[Miscellaneous Android Development] McHappyMeal:
I found a fix to the battery problem

Download force doze from play store

As well as greenify

I used to get massive battery drain but not any more
[Miscellaneous Android Development] fire855:
That won't fix anything.

Here is the real fix: https://xdaforums.com/showpost.php?p=74384701&postcount=2638
[Miscellaneous Android Development] superdragonpt:
on top of the new kernel, you can also achieve even GREATER battery ...

... just never turn on, your device again

haah
[Miscellaneous Android Development] Sax_93:
Yes the charging is too slow. My phone from 0 to 77% about 2 h or more, with the fast charger.. .
[Miscellaneous Android Development] yeiyei0891:
Quick charge doesn't work with this ROM?
[Miscellaneous Android Development] cedricboquiren:
I think charging it slower will help reduce the stress the battery is handling. That would make our device live longer. I am just fine with that. Anyways, I also have Jiayu S3 which MAD also supports.
[Miscellaneous Android Development] smilie108:
Hi magisk I installed after reset not directly after installing IMG could this maybe the fault do I have to flash magisk directly after IMG without reboot between? Yes latest flash spf version

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] DerTeufel1980:
The more important question is, whether you are using the latest rom, which needs to be flashed by flashtool

Sent from my uhans h5000, running Android 8.0.0
[Miscellaneous Android Development] smilie108:
Yes I flashed it when you released it for me it's not that big problem the pics not so important that I would cry [emoji3] only Google authenticator is bad for me but nothing I could not handle

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] kucyk84:
battery drain solved for me also , i can handle with "slow" charging :)

cheers
[Miscellaneous Android Development] BerniBoern:
Okay thank you for the answer! So that means, that all 10 cores are able to work if its needed?

I was just curious why I can't see the usage of the cores. Just have a look at this screenshot:

This applies for all 10 cores.. that's somehow weird isn't it?
[Miscellaneous Android Development] qltsar:
Yes! Believe me, I have tried every possible scenario. So I ened up setuo my phone from start, but the strange thing is that when the phone boots itself, it's asking for a passcode during the M.A.D. OS bootlogo, I enter my passcode, and it shows again the bootlogo, then my phone starts.

The whole thing is really strange.

During the installation process, the recovery rebooted itself 2 times, once when I was copying the ROM files to my PC, secondly when I have flashed the gapps package.

I will still going to try something, because I really need my old backup from the OS, and I don't want to manually extract the files I need from the TWRP backup.

I am using, flashin Android phones since 2010 but I have never ever seen anyithing like that.

The battery is better I can confirm that.
[Miscellaneous Android Development] honzyn25:
Do you think this?

https://youtu.be/g2WMN3qBOVQ
[Miscellaneous Android Development] fire855:
The passcode screen on boot is normal for android when the phone is encrypted. You can disable/enable that in the Security Settings.

Your phone wasn't encrypted before it seems. So either you didn't flash our last release with SPFT or you flashed Magisk and it disabled the encryption. What did you flash?

Also TWRP rebooted? That makes no sense
[Miscellaneous Android Development] qltsar:
I totally agree with the last sentence, it totally does not make any sense at all :D!

Yes, I flashed the latest ROM when it was out in late august, I was using the ROM since then, but not with Magisk. (SuperSU 2.8.2). Everything was working fine - belongs with the known issues.

'You can disable/enable that in the Security Settings.' - How can you do this, when you have a non-bootable phone :)? There was only a screen with the button with a non-starting ROM and with an encrypted /data partition.

Don't misunderstand me, I am really grateful for you guys what you developed for the phone!

I had a full backup from the internal storage, so it's only time consuming for me, no harm caused (hopefully :) ), but I wanted to address this issue anyway :).
[Miscellaneous Android Development] smilie108:
[MENTION=4761533]fire855[/MENTION] Prozess I did 1.download IMG Datei 2.reboot in recovery 3 go install install IMG select 4.select IMG file downloaded swipe bar down from left to right wait until it's ready. Then I go to wipe advanced wipe cache and dalvik then reboot to system / booting holded after mados logo was finished animation waited some time then make reset via the power button after restart it is asking about encryption password for data partition / I never had encrypted my phone

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] Sax_93:
Hey, why my phone say 32% battery of charge, and a few seconds later says 0% and go off; (Later i put on the smartphone it says another time 32% and later seconds says 0% ...)

I Used battery calibration later i discharged to 0 the smartphone...

It's a bug or other?
[Miscellaneous Android Development] joaopguima91:
I usually had a battery drain from 15% to 0% in a question of a couple minutes, but after the fix that is resolved!

I noticed too that the battery charges a bit slower but for me i like it like that, since the battery doesnt heat up as it usually did previous to the fix!

One thing it happens to me is : my mi hand 2 doesnt connect like at all with mi fit! Doesnt know why though!

And my GPS even with GPS status and toolbox doesnt work quite well even with high accuracy turned on! It takes a lot of time to get a signal and it loses it quite fast! Anyone has this problem or know any fix?

Thanks :)
[Miscellaneous Android Development] RalphMalph:
I think you all should stop complaining about charging slow after the new fix.

The problem of very rapidly charging (10 to 60% in about 10min) is gone. That was just fake. If the percentage is saying 100% it was not for real.

So nobody knows how much the charging to real 100% was.

The problem of instant drops from for instance 15 to 0 are gone too. Also that was because 15 was not really 15.

That it is maybe a bit slower than stockrom is because now there is a good voltage in charging. Vernee has in their stockroms a higher voltage, which was even so high that it was much out of the specs of the hardware. It is even dangerous and we should be all lucky that there was no explosion of a battery or phone during charging in stockrom.

Now we have a good stable phone, no strange battery behavior anymore, nice fast charging and most important maybe is safe for phone/battery and its owner.
[Miscellaneous Android Development] honzyn25:
I agree, cough on the complaints and hope that we will soon get Oreo and I do not mean biscuits.
[Miscellaneous Android Development] fire855:
I meant you can disable it when the phone booted ;)

It looks like your phone never was encrypted. But the last release enables force encryption. So something must have disabled the encryption. Do you have a TWRP backup before you flashed the boot.img? Can you upload your old boot.img from the backup?
[Miscellaneous Android Development] fire855:
The last release enables force encryption for higher security. Something disabled it on your phone. Did you flash the last release, booted in recovery and flashed magisk? or flashed anything else?
[Miscellaneous Android Development] smilie108:
I only know one spf version right? Magisk I flashed a few days later via twrp and dolby 6.3 after that I did nothing else where can I see if encryption is enabled or disable?

Gesendet von meinem Apollo Lite mit Tapatalk
[Miscellaneous Android Development] qltsar:
Yes, sure. I just restored the backup, it was not encrypted at all, if the new boot.img is forcing the encryption then we have the answer.

I just manually encrypted the phone (which means it formatted the SD partition again - I am not sure how...), root has been lost after the phone booted, then I flashed the boot.img and instead of SuperSU I flashed Magisk and it's working.

Can the Supersu change this behaviour when it flashed? Are you sure the encryption is active as default in the newest ROM?

Shall I dd the recovery or the TWRP format will be good?
[Miscellaneous Android Development] Sax_93:
I was using the charger with the quick charge and the charging was so slow 70% about 3 hours and later (1% every 10/15 minutes). Now i used a normal charger and i got 100% in a few minutes.

Then i used this app: "Battery HD - Battery" to get a calibration of the battery ecc.
[Miscellaneous Android Development] fire855:
Yes the last release has encryption active as default. The new boot image also worked fine for most persons.

Magisk / SuperSU can't change the encryption when the encryption was already done. It can only disable the encryption setting. If you want to remove the encryption after it was done already, you need to format data.

So the only reason why encryption would be missing is that you flashed SuperSU before you made the first boot after flashing it with SPFT. Or you formatted data afterwards.

TWRP format is also fine.
[Miscellaneous Android Development] fire855:
You can see it in the android security settings.
[Miscellaneous Android Development] smilie108:
Now it says encryptet what it was before i cant say. but now i try at the secound apolle i have and tell you later ther i have make a full backup and it says its encryptet i also have to enter the drawing at twrp to get data shown that i don´t have bevore becous my phone is not secured it for working ;)

Update

On the secound one witch has the same spf version like mine but have a plattern encryption there it was no problem to install without lose data or something else.

So it is maybe becouse i had no encryption enable with palttern or something else can this be ?

Mhm I would upload Screenshot but seems not allowed using 19.8.2017 build date
[Miscellaneous Android Development] tanish2k09:
Does anyone face gesture ghosting with smartwake?

What's gesture ghosting ?

Well gesture ghosting simply means detecting a wrong gesture when some other similar gesture is made.

:confused:

I mean anyone of you faced a "down" gesture trigger when you actually swiped up a couple times?

On my device I did and have commited the fixes to my git and it's working perfectly on my device now.:)

I just wanted to see if anyone else is facing the same and maybe I could contribute a tiny little bit by providing the minor (so to say) commits... :highfive: [MENTION=4761533]fire855[/MENTION] how can I commit? There are so many kernel sources...

PS : I'm not a user of Mad OS but I saw it uses the same smartwake that was added in my device so I thought of sharing. I'm not sure where this post would be relevant so I ended up posting here. Pls forgive if it's irrelevant here.

The author of the module as per listed within the code, is [MENTION=4196889]DerTeufel1980[/MENTION] and I hugely appreciate the amount of genius work done by him. :laugh::highfive:
[Miscellaneous Android Development] misterkiller:
It´s possible rename the boot_fixed_charging.img file to boot.img and replace the file on rom file and flash it on spft for clean & fresh installation all in one.

Sorry for the noob question.....

ps: google translation
[Miscellaneous Android Development] qltsar:
I checked it, just re-flashed the whole image, and booted with supersu 2.8.2. it's says it's encrypted, the problem is definately not there.

Now I restored my TWRP backup from the new system from yesterday with the new boot.img: Neither TWRP or the system when it boots up is asking for the encryption password - really wierd. It was asking for password before I re-flashed the system and restored my backup with TWRP, really-really strange!

[MENTION=4761533]fire855[/MENTION]: there is no way to change the encryption status in the ROM, you can't change it, even if you format, reflash the system, the only way to decrypt the partition is to reflash one of the old original system with SPFT.
[Miscellaneous Android Development] Irish_Dude:
This was the update I was waiting for

I flashed the latest battery fix file and my battery life is absolutely fantastic, the best it has been by far :)

Thank you M.A.D Team, much appreciated :)
[Miscellaneous Android Development] RalphMalph:
You dont need to rename. Just only flash this file (also with spft)
[Miscellaneous Android Development] cvegreen:
I will wait for be MAD again till O is out.

Sorry for my bad Englisch. I am from Belgium and speak Dutch :eek: