yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Zorikage:
Seems LED when charging is always RED only green at the end, also notification on LED doesn't work anymore, no more blue notification when on whatsapp or kik they message me.. please fix

Edit: also when charging when the device is not turn on it just show the Vernee Logo and not the battery percentage!

When unlocking phone from the software key to power it, shows the LED red for a moment (only when charging) only when pressing the software key..

Edit2:

When the battery percentage is on 90% unlocking the phone pressing the power button doesn't show the red led again, just keep showing the green led (that's good)

Getting a message when the phone is charging and shows RED or GREEN LED, it's going to turn it off and when pressing hardware buttons its going to show the green or red LED again but for a few moments..

But the main problem is no message LED and no battery notification when device is off! :(

Is this a problem from the ROM??
[Miscellaneous Android Development] fards:
I'll build the kernel with some hotplug changes over the next few days. See if it makes any difference.
[Miscellaneous Android Development] gbl08ma:
I can confirm that the notification led appears to not be working, also when I'm adjusting the LED color settings, it isn't on when a notification appears saying it should be.

EDIT: I should mention I experienced another episode where the phone won't turn on either by fingerprint sensor or power button. It usually comes back after 10 or 15 seconds, and then takes a while to come up (screen all black for some seconds until the UI appears).

Regarding battery life, it doesn't seem worse than with Vernee OTA 2 but it's not stellar either. I'm noticing huge counts for wakelocks, even for my own app Clouttery, which supposedly only requests a wakelock once every 15 mins... Wakelock detector says it had 1007 wakeups in three hours. Gmail is at over 100K wakeups... is this normal for Nougat?
[Miscellaneous Android Development] fards:
There a couple of of bits of code in the kernel i noticed earlier when comparing it that might be causing that.
[Miscellaneous Android Development] gbl08ma:
I can't use Termux anymore, it's possible it's a problem of the app (incompatibility with Nougat), it worked fine on MM.
[Miscellaneous Android Development] Zorikage:
If you find out how to fix the LED problem it would be great

Maybe if battery percentage doesn't show when device is charging when is off (and also show just the Vernee Logo), is a kernel problem too?

Hope to know i'm not the only one
[Miscellaneous Android Development] nature boy:
Another small bug: can't change CPU governor in MAD settings
[Miscellaneous Android Development] gbl08ma:
Then I guess it doesn't turn on to ring alarms when off, either. That and on-off scheduling are (or were some years ago at least) kind of unique to MTK phones and are part of the MTK "framework" which M.A.D. throws away. Throwing away so much stuff has advantages and disadvantages...

It would be good if team M.A.D. could reimplement those features in a clean way. (The wishlist keeps growing...)
[Miscellaneous Android Development] Zorikage:
It's better let them fix the first bug we found like the LED and things we normally use on the phone, then after this amazing job developers did, they maybe will think to implement everything :D

Seems battery drain a little too fast when using a bit the phone (like watching notify)
[Miscellaneous Android Development] genesisalgor:
The thing of turning alarm when phone is off is a MTK feature, isn't present in AOSP source. You can blame Google.

Now should they focus in creating a way to implement this instead of focusing in the whole hardware bring up and OS polishment? They aren't throwing things away... and also have not obligation of adding things from MTK If they are upgrading to 7.1.1 they aren't Vernee. And they already added a lot of things from MTK, like Sim on/off and Band mode.

For MTK 7.0 ask/wait for Vernee.
[Miscellaneous Android Development] gbl08ma:
I wasn't suggesting they add things from MTK, in fact having a ROM with less MTK code, that's poorly understood and full of hacks, is one of the best parts of these close-to-AOSP builds. But since they already have their own extra options and even a extra settings menu, having reimplementations of MTK's best features doesn't seem too out of scope. Of course that's really low priority if you compare it with fixing these annoying things like the noise on the headphones or the not-so-functional notification led.
[Miscellaneous Android Development] Zorikage:
Agree, having some old feature in a Extra menu maybe in some more Stable version, gonna do a really big difference for those that love that kind of features avaiable only in Mediatek.. but probably M.A.D. had their reason aswel.
[Miscellaneous Android Development] Verevka:
not working adjusting the volume of the conversation, as well as in my CM, if you fix it tell me how. Although I doubt that you'll agree to help me :D
[Miscellaneous Android Development] DerTeufel1980:
You did not even release your kernel source code :/

We're indeed not going to release 'ready to go patches', but if we fix it, we can at least give you hints, how to do it
[Miscellaneous Android Development] Verevka:
All of my edits in the kernel was added only bugs :D now I use stock kernel sources
[Miscellaneous Android Development] DerTeufel1980:
What are you referring to?
[Miscellaneous Android Development] Dani551:
I don't mean to sound harsh or anything, but consider this:

The app is supposed to keep checking whether the system is in deep sleep or doze mode and when the system is indeed in deepsleep mode, the should be asleep too. But then some apps have wakeup paths which wake them up when in sleep mode. This action causes the system to exit the deep sleep mode and enter an active state. So now the other app is now running and causing CPU load while our app is still inactive. And even if this does not occur, it would take some genius algorithms and codes to determine when the app should ask the system to go into deep sleep state, if this is not defined by the android system. For a fully fledged android software developer, this might not be so hard to tackle, but for a relatively inexperienced programmer like me it would take some time to come up with something functional. Don't mistake what I am saying or implying here, your idea is brilliant but the way I see it, the work of building a good enough software for that might not be worth it, especially when Greenify offers the same functionality.

Cheers
[Miscellaneous Android Development] fLaSk1n:
Hi Primus.

I'm on o2 Germany and don't have that problem.

Maybe you should check, if you are using the right APN settings?

Gesendet von meinem Pixel mit Tapatalk
[Miscellaneous Android Development] Primus919:
I can only use The APN from eplus, thats this is right.
[Miscellaneous Android Development] fLaSk1n:
Eplus doesn't really exist anymore, it's all merged to o2 and they do use the same APN settings.

I would suggest you just try the settings for o2 - maybe then everything will work for you (again).

Same is / was for base customers.

Can google for that.

Gesendet von meinem Pixel mit Tapatalk
[Miscellaneous Android Development] Primus919:
Thanks for fast answer, i will test it

Gesendet von meinem Apollo_Lite mit Tapatalk
[Miscellaneous Android Development] Primus919:
It does not work

Gesendet von meinem Apollo_Lite mit Tapatalk
[Miscellaneous Android Development] RalphMalph:
Maybe you need to enable data usage
[Miscellaneous Android Development] Primus919:
Is enabled

Gesendet von meinem Apollo_Lite mit Tapatalk
[Miscellaneous Android Development] RalphMalph:
Just to be sure, Roaming is not the same as Data usage.

What about reset network settings?
[Miscellaneous Android Development] Primus919:
I know?

Gesendet von meinem Apollo_Lite mit Tapatalk
[Miscellaneous Android Development] 0312Penner:
I have sometimes the same problem. For me it helped to change from LTE to 3G for a few seconds and than switch back to LTE.
[Miscellaneous Android Development] Primus919:
Now I formated the phone, flashed original ROM, wiped with TWRP complete and installed this ROM now all works fine^^
[Miscellaneous Android Development] fLaSk1n:
Good when that helped :)

"Wrong" apn-settings was just an idea, because I had the problem after migrating from base to o2

Gesendet von meinem Pixel mit Tapatalk
[Miscellaneous Android Development] RalphMalph:
Good to hear
[Miscellaneous Android Development] Black Manta:
Does anyone know if it works to use the the rom with a F2FS filesystem even on /system? Like on the OnePlus 3T F2FS should give a better random-read performance and resulting faster application loading times.
[Miscellaneous Android Development] fLaSk1n:
I've formatted all partitions to f2fs before I applied the ROM through TWRP.

ROM reformatted the partitions while flashing.

Maybe I've missed something, but for me didn't work.
[Miscellaneous Android Development] DerTeufel1980:
There's no f2fs support
[Miscellaneous Android Development] RalphMalph:
Guess [MENTION=4196889]DerTeufel1980[/MENTION] is still here :victory:
[Miscellaneous Android Development] Black Manta:
Is it software based (system cannot work with it?) or only because the zip file format it? :)
[Miscellaneous Android Development] DJ_Casper:
Nope. It's not working for me
[Miscellaneous Android Development] Zorikage:
Dude he was ironic.. how did you not get that?

This ROM is only for Vernee Apollo lite..
[Miscellaneous Android Development] BlueFlame4:
If it was that simple, everyone would opt for F2FS ;) But no, it requires way more changes within the system than just this line.
[Miscellaneous Android Development] McHappyMeal:
Does Qualcomm 3.0 change work ?
[Miscellaneous Android Development] AxelMilb:
No Qualcomm Chipset no Quick Charge 3.0

MTK Pump Express 5V 7V 9V

70 min 0-100%
[Miscellaneous Android Development] RalphMalph:
It should work I think. The technique is more or less the same. Also variable voltage during charging.
[Miscellaneous Android Development] No1VIPER:
Yes it does. I've been using one for a while. It charges just as fast as the original charger.
[Miscellaneous Android Development] Xorianator:
It definitely does work. I had a qualcomm charger and it was the onliest - beside the original ones - which charged fast.

Had, bc it had horrible noises....

But wrong thread guys, the general thread should be right for you purpose.
[Miscellaneous Android Development] RalphMalph:
It's so quiet here... Silence for the storm?
[Miscellaneous Android Development] FoxBob79:
I think the biggest problems are known by the developers and to tell them everyday the same would only steal their time to bugfix the problems. So we are patient, finger crossing and respectful waiting for a new build... :)
[Miscellaneous Android Development] RalphMalph:
true
[Miscellaneous Android Development] gazwalesuk:
Fast charge mode is a yellow light top left and when turned off its a thin blue battery icon with flashing inside only the original charger works with fast charging I've not yet found a alternative for pump express 3.0 or UK compatible.

Hope this helps :)

---------- Post added at 03:14 AM ---------- Previous post was at 03:10 AM ----------

Not in fast mode nope

---------- Post added at 03:15 AM ---------- Previous post was at 03:14 AM ----------

Nope it don't activate quick charge on mediatek
[Miscellaneous Android Development] No1VIPER:
Oh its the all knowing noob again.

So everyone else who has used Qualcomm 3.0 chargers and has them fast charging their Apollo Lites is wrong?
[Miscellaneous Android Development] AxelMilb:
Please use USB Multimeter

Gesendet von meinem Apollo_Lite mit Tapatalk
[Miscellaneous Android Development] RalphMalph:
Will it be a good day?

I am so curious to the new build :silly:

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

Why use a multimeter, just use normal clock. 0-100% in 1h15min...If it takes much longer then it is not working
[Miscellaneous Android Development] longnt2007:
Here is some pictures I'm using an Aukey QC3.0 with two devices, one is MTK Helio X20 and one is Snapdragon 820. Only multimeter can tell you that if you plug in QC3.0 compatiable devices to QC 3.0 charger, the charger will pump voltage up to 9V/12V, while MTK devices will stay at 5V/1.5A (standard BC 1.2), and make you thought that is quick charging lol.

In short: charger can recognize your device is compatiable with their quick charger protocol or not (by USB power coding on D+/D- voltage), you can read info at this link

http://lygte-info.dk/info/USBinfo UK.html

EDIT: I've brought this 2in1 charger and tested with multimeter, it can pump both MTK and Snapdragon devices to 9V. Another charger support both MTK Pump Express and QC3.0 is Sony UCH12 but it's expensive.

https://www.aliexpress.com/item/ROC...harger-2-in-1-5V2A-9V2A-12V1/32691437839.html
[Miscellaneous Android Development] marcolo76:
Hey guys.. this Charger and USB cable talking is way off topic!
[Miscellaneous Android Development] vcarbajo:
Is there any progress of battery drain bug when screen is off?

The smartphone consumes the same using it as not...

sorry for my english
[Miscellaneous Android Development] Sonic1SVK:
Known bug. Devs working on fix. Read cca 3 Pages back

Odoslané z Apollo Lite pomocou Tapatalku
[Miscellaneous Android Development] RalphMalph:
Hope for a good.... Ehm... Great weekend

;)
[Miscellaneous Android Development] Zorikage:
Mmh just to talk about different argument, is there any canche that developer can bring back some mediatek features that was very cool on the stock ROM?

I'm talking about the 'vibration' when someone accept your call.. or the alarm clock still works when the phone is off.. i'm just wondering..
[Miscellaneous Android Development] Richard0601:
Good evening I would like to know if the rom for apollo light are compatible with the apollo helioX25 Knowing that it is the same processors Waiting for your answers before flashing
[Miscellaneous Android Development] RalphMalph:
Not compatible
[Miscellaneous Android Development] Richard0601:
Thank you for the answer Then it is impossible to root it I found no twrp and rom for this model
[Miscellaneous Android Development] RalphMalph:
Correct, the device is simply enough too new
[Miscellaneous Android Development] Richard0601:
OK

Then wait

This is a great phone
[Miscellaneous Android Development] James.Miller:
So yours does work? Interesting, because everything I've seen would suggest it would never work, such as QC QuickCharge using usb2 when MTK pump express works over usb 3.

Have you confirmed that your phone charges at 16w or is it an assumption? I have a full fat Apollo so not exactly apples to apples however my aukey QC3.0 charger charges my Apollo no quicker than a normal usb charger does; I measured it at the wall and it never exceeded 10w draw (so i assume it's sitting at 5v/2a). The bundled vernee adaptor however, very fast. But as per pump express the phone needs to be off for it to charge at 16w , otherwise it falls back to 10w when the phone is on.

Are you saying you see 16w charge with a QC 3.0 charger?

Anyway, 'jealous of you guys with custom roms on your lites. We're still stuck with stock roms.
[Miscellaneous Android Development] Xorianator:
People, please, this is the wrong thread.

This thread is about the MAD Rom, not the apollo lite in general...

So please move on to the general thread, this way: https://xdaforums.com/general/devic...nee-apollo-lite-helio-x20-4gb-ram-hd-t3362898
[Miscellaneous Android Development] James.Miller:
Hey, i'm assuming this is purely a hardware thing and No1VIPER is wrong but there could be something in the ROM overriding it...maybe. At least that point needs confirming before you tell me im posting in the wrong thread?
[Miscellaneous Android Development] Xorianator:
Yeah but you are not discussing about if this ROM supports it, you are discussing about in general.

So it would be ok to ask the devs, but instead of doing you are posting permanently something which is not close to be about this ROM...
[Miscellaneous Android Development] James.Miller:
one post is not permanently. The rest of them were spent pointlessly replying to you.:rolleyes:

Now instead of continuing to drag this discussion on, why don't you leave it alone and let No1VIPER reply, here or in the other thread, and then we'll all know? :)

Or you could keep dragging this pointless argument on if you like. I won't be joining in though.
[Miscellaneous Android Development] Xorianator:
Without being inpolite, but is there any progress in catching the root of the battery drain problem?
[Miscellaneous Android Development] Black Manta:
This is from superdragonpt a few sides before:
[Miscellaneous Android Development] RalphMalph:
I hope not, but have the feeling that development of the Vernee-devices (Apollo lite and Thor) is a bit on low priority.

Hope soon someone can tell the status.
[Miscellaneous Android Development] Zorikage:
Guys is there any way to get Vulkan API support working on the apollo lite?

Some games and emulators use only two Cores and with OpenGL performance is not the best.
[Miscellaneous Android Development] rxbn:
Hey, just found another bug. I don't know if it's just for my case but WhatsApp and Snapchat cant reencode or compress (I don't know) a recorded video.
[Miscellaneous Android Development] Black Manta:
Yeah, I have that bug too. Don't know if it's a rom bug or whatsapp bug. :/
[Miscellaneous Android Development] konsolenspieler:
Is there cifs support?

I badly want to use cifsmanager to mount my network drive, but it seems like the stock rom hasn't cifs support, so I would even change the rom just for that.
[Miscellaneous Android Development] DerTeufel1980:
Battery stuff is really weird... Maybe some thing is not compatible with nougat at all...

We basically tried everything,

From removing every mtk related driver (just kept the minimum to get it boot), to adding more mtk stuff, using other ramdisk, built cm14... Everytime device does not sleep.

One could think it's the kernel then... But no. Our kernel sleeps on stock Android 6 rom more than stock kernel.

And stock kernel does not sleep on our rom.... But our rom works on every other device...

Conclusion, it has to be something device specific, but not the kernel... Which we already replaced everything...
[Miscellaneous Android Development] No1VIPER:
That's a real shame. Well thanks for all your efforts, and thanks to the while MAD Team.
[Miscellaneous Android Development] RalphMalph:
Thank you all for the effort, you did a real good job. Now we all know why there was no reporting of it. So difficult, so much work, no time to report.

Thanx MAD-team.

As I said before, luckily we have pump express, 0-100% in 74min.
[Miscellaneous Android Development] UNIX4ALL:
We must wait official nougat then... Maybe the new kernel fix this problems.
[Miscellaneous Android Development] No1VIPER:
I wouldn't count on it.
[Miscellaneous Android Development] RalphMalph:
Hopefully we can leave this for now behind us and concentrate on the next build with the battery-drain as a known error.

I am almost sure that we will have a new build soon.

Today a good day? :p
[Miscellaneous Android Development] kisger13:
I'm really sorry, maybe that's the reason why the stock rom delayed. Thank you for your effort and please don't give up, because your work is amazing and the rom is really good. Fingers crossed for you.
[Miscellaneous Android Development] superdragonpt:
It ain't a kernel issue... (99%sure)

With all the flavours we built, and like my team mate said...

We are still looking at other things

Bb
[Miscellaneous Android Development] DerTeufel1980:
Yeah...

Who knows... Personally, I doubt it's kernel... Maybe we are just too dumb to fix our error (if any)...

Unless vernee updates stock rom, or verveka has a cm-14.1 build with deep sleep working (he didn't say anything about it)... We need to live with it
[Miscellaneous Android Development] Jango Phat:
Thanks Team M.A.D. for all the effort and hard work!

[MENTION=5213876]Verevka[/MENTION] any news from your side since you're also working on the 7.1.1.?
[Miscellaneous Android Development] FoxBob79:
Could the beta release of 7.1.2 give some hope? Maybe the problem would be solved by the new version...

PS: Verevka changes something around the "pstate", maybe the problem is that the kernel gets no signal to sleep. A wrong or broken "pstate" could be a reason for that.

PPS: That is just an idea!! Dont hang me if i tell totally bullsh*t... :)
[Miscellaneous Android Development] Zorikage:
Can someone tell me if there's any way to get Vulkan API driver support in the future?
[Miscellaneous Android Development] Xorianator:
Thank you for your response...

If this error is not happening on Android 6, would you might build an Android 6 Version of your ROM? Would be great to fix those Battery Issues.
[Miscellaneous Android Development] reebomber:
First of all, I would like to thank everybody for the very hard work that has been put into this rom, and debugging this deep sleep issue.

We had all been waiting for today's (bad) news, and apparently there is not really an end in sight for this lack of deep sleep problem, causing the battery drain on this ROM.

I had this ROM installed for almost a month (almost since "stable 1" came out), and last weekend decided to try AICP11 from Verevka. Indeed, the battery last considerably longer (airplane mode and no use there is almost no drain from battery in one night), but I can still find the same biggest problem that was reported on this ROM, but were sort of forgotten because of the battery drain issue: Lag when pressing power (it takes normally 1 or 2 seconds to turn on, sometimes I have to reboot, because it just wont restart).

Since this is, by definition, related to deep sleep (coming out of), and since deep sleep is the problem, might this not be related? Might this be related to a "difficult" hardware? Also (and maybe related), I never got fingerprint to work properly (on either rom), mostly because it would apparently even make this problem worse. I have turned on and off all the gimmicks for lock screen (flash and camera on power button, fingerprint, etc), and the problem is still there.

Yes, a freshly installed ROM does not have these problems, but who uses a freshly installed rom as a daily driver? :)

So my point is: Can we expect maintenance of this rom, or a M.A.D. Marshmallow ROM, if the deep sleep problem seems to be contained under Android 6?
[Miscellaneous Android Development] RalphMalph:
I don't think we should go back to android 6 because of this battery drain.

Look at the great rom there is now. I really don't understand why everybody is so into this problem. Yes it is not good, but come on, in 1 hour the battery is back up.

I think the MAD team should focus first on other existing bugs and then release that. I mean, we are already running our devices 2 months with this battery drain. 1 or 2 more month does not hurt.

After that the team can try to fix the battery drain, maybe even with 7.1.2
[Miscellaneous Android Development] kisger13:
The only disadvantage is the lifetime of the battery. If you drain and charge it twice a day it will die in 6-8 months....

https://en.wikipedia.org/wiki/Lithium-ion_battery
[Miscellaneous Android Development] RalphMalph:
You are saying that when you are not charging it 2x a day, that the battery lives 1 year. Pffff. I dont think so.
[Miscellaneous Android Development] DerTeufel1980:
Sorry, but we're not going back in time.

Android 6 is old, and I'll never compile it again
[Miscellaneous Android Development] RalphMalph:
Hmmm can only thank 1 time :p
[Miscellaneous Android Development] Xorianator:
[MENTION=299231]RalphM[/MENTION]aph as [MENTION=6126582]kisger13[/MENTION] is saying, it will kill the battery faster. In general a LiIon Battery can hold 1000 Cycles without losing smth, so in 1 1/2 Year it will start losing it life.

Btw I am charging it 2 to 3 times a day...
[Miscellaneous Android Development] 0312Penner:
i found this after searching a bit:

https://github.com/Verevka/android_device_vernee_apollo