yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] RalphMalph:
Hope next release will have fixed:

- Nightlight

- Random FC's

- Screen wakeup delay/not waking up at all (even noop-mode)

- Bluetooth connect/disconnect (should be fixed with 7.1.2 according to Google)

Anyone (of the Mad-team) can confirm if these things are fixed or not?
[Miscellaneous Android Development] olus:
yes, please give feedback. because the random fcs are really annoying and i will flash stock or something else, when its not fixed in next update. cant wait another month with this bug..
[Miscellaneous Android Development] Xorianator:
Yes, very good idea. Instead of waiting until the fire is extinguished, you better burn down the whole forest.
[Miscellaneous Android Development] Hell.Kreak:
Does not matter if you aren't​ in the forest XD sorry but if the rom is not stable for him/her why shouldn't he move on? Everyone has other needs so let him ...
[Miscellaneous Android Development] moshe_lm:
bg image

Hi

I tried to change the Background image, after some minutes is was resetted to the default. why ?

What about the buttons in sleep mode?
[Miscellaneous Android Development] Xorianator:
What do you mean with buttons in sleep mode?

Which launcher are you using?
[Miscellaneous Android Development] moshe_lm:
I am using the BT (car) or Wired headset buttons when the device is in sleep ('power off'). When the device is on the BT/Headset buttons is works.

For example, I can't answer a call on driving from the wheel, but can do it when the device is with display on.

using the default one.
[Miscellaneous Android Development] Xorianator:
Ah okay. The button problem is known I think, but there is indeed a problem with the whole BT Connection & Deep Sleep, as far as i read in here. Think they are on it

Oh hmm k, i don't know why it's happening. Was there a FC (Force Close) for your launcher?
[Miscellaneous Android Development] moshe_lm:
You talk about BT, but I am talking about Wired also.

I did not see the FC, but I have an other problem in the lancher - the default BG image is showing again and again after I am changing it.

I can live with this bug, but just to note.
[Miscellaneous Android Development] Xorianator:
Oh okay I see, yes. If it's wired, I do have the same problem sometimes. I don't think this is a deep sleep problem, more a scheduler problem (so far I read this thread), bc this bug exists in Stock too.

You could try to change your default launcher (I am actually using Nova)
[Miscellaneous Android Development] moshe_lm:
I was changed the scheduler as I was see in this thread, the other problems (audio, wakeup ) solved, but not the wired buttons problem.

The problem is also with the lock screen. maybe changeable.

did you inspired when creating this rom from CyngoenOS Roms? I was moved from CM to mad and happy...
[Miscellaneous Android Development] mlara.particular:
[IMG="Battery"]https://xdaforums.com/picture.php?albumid=14113&pictureid=55424[/IMG]

just to get an idea of what DEEP SLEEPcould be, on my 2nd phone (Galaxy A5 "016, MM) after 11 hours of screen off with WiFi, GPS and Data Connection "ON" (got a few mails and Whatsapp during this period) the battery drains was 3% (11 hours!!!!). I would love to see this on our AL!!

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

---------- Post added at 11:30 AM ---------- Previous post was at 10:57 AM ----------

https://xdaforums.com/picture.php?albumid=14113&pictureid=55424
[Miscellaneous Android Development] RalphMalph:
Stick with the A5 and get out of here! Please
[Miscellaneous Android Development] Hell.Kreak:
you trying to be polite - I like :) #tryhardernexttime
[Miscellaneous Android Development] mlara.particular:
Ralph, honestly, I woud have expected a better answer from you, I am dissapointed, Hahahahah.

The A5 is a ****ty phone, just like your answer, but it shows where Deep Sleep could be with the APL.

So if you have any qualified answer to this, go ahead, otherwise, don't waste our time. Thx.
[Miscellaneous Android Development] RalphMalph:
Well, i think that we have to stop talking about Deep Sleep. Deep Sleep is working. Period!

Maybe it is not the best, but at least be happy it is working. And maybe/probably this is the best the VAL can do.

Also too many differences:

- Samsung is not Vernee

- 400 euro/dollar is not 175 euro/dollar

- MM is android 6.x, we have 7.1.1

- Snapdragon 615 is not X20
[Miscellaneous Android Development] trojanere:
Some people want the moon on a stick.. Sorry for the no contributory post but as Ralph says it's a cheap China phone and not a high priced mainstream flag/ex flag ship phone.

My phone users on average 100 mAh per hour doing nothing much and not much more when i use it for none intensive apps and games. That's 31 hours for a full charge and I charge every night so it's not going to die on me anyway.
[Miscellaneous Android Development] Andr0iDUser:
LOL! Dude, you are really talking bull****!

You are right, "Deep Sleep" is working but it would be nice if the device "wake up", too! I have some serious probs with "Deep sleep". When receiving a call, the device does not wake up. I am not able to answer the call.

If you fine with what you got, why did you switch from Vernee ROM to M.A.D.? I guess, you were not happy what you received with the "best value" you had...

And its nonsense to compare two companies only about their value on stock market! I have worked with Samsung to deliver embedds when they started with their first Galaxy Device i9000 and trust me, every yearly hardware update of a "Galaxy" became worse and worse...

Vernee is not perfect and M.A.D. team is doing an excellent job. But it is far away from "best what we can get". But we all have to keep in mind that we do not get charged for this CFW and have to accept, too that probs get not fixed within a short time frame.
[Miscellaneous Android Development] RalphMalph:
yes, the waking up is sometimes a problem, but i never saw a msg from you that you were complaining. Maybe when you (and others) are telling MAD then they will give more priority. So please don't tell me anything.

Apart from that. I think you can only complain here, never said anything positive.

Please change rom to something else than MAD if you are so unhappy
[Miscellaneous Android Development] Xorianator:
Noone is paying them, they are distributing there time they could have with family, friends, hobbies, ... so we should be thankful.

Sure: That's no reason to don't criticize, but to be rude by saying stuff like "mimimi I paid literally nothing for my phone mimimi and using a free service mimimi and you don't spend all your time for getting nothing so that I get satisfied" is kind of bull****, literally.

So: If you want to complain instead of criticize, just pay them!
[Miscellaneous Android Development] Andr0iDUser:
You poor little boy... you are unable to read... Who are you? Are you one of the M.A.D. team? Or just one who is happy to use their work? Kind of fan boy?

I do not complain! The opposite: i appreciate their work! But I can mention things which are not working properly, too. And this, my friend, is not complaining.
[Miscellaneous Android Development] Xorianator:
Pls move further to another thread, you are just an disgusting person and this isn't about fighting each other. Wish that MAD would deliver their ROM to everyone except you, because u don't deserve stuff like this.

Btw to the deep sleep: I lost 10% in ~9 hrs and the display was on like 10 minutes of the time (for taking photos), Phone was in airplane mode. Pretty good result I think
[Miscellaneous Android Development] Andr0iDUser:
Lol. Are you retard? No more to comment from my side.

Your answer is very helpful. NOT!

The problem is no battery drain. That issue has been fixed! The problem is, that the device does not wake up.

There are several "tricks" to reduce battery usage like to disable WiFi Search, which is hidden at "Location". I bet you already knew this ;)
[Miscellaneous Android Development] lambie413:
Hi guys,

Hoping I can get a bit of help!

I have installed TWRP but am having issues installing. Here's what happens:

1. Moved madOS_7.1.1_apollo_lite_20170318.zip to SD card which is installed as portable storage

2. Reboot to recovery

3. Wipe data

4. Install from SD card and pick madOS_7.1.1_apollo_lite_20170318.zip

5. Get the message "Opening update package..." followed by "Installation aborted"

6. Original TWRP screes shows

Any ideas what I am doing wrong??

Cheers!!

Edit: Worked it out myself! Was using an old version of TWRP!
[Miscellaneous Android Development] lambie413:
Ok I've run into another problem.....

In an attempt to get the google restore screen at first boot I went to system, factory reset when i got into android 7.1.1

Problem now is the phone will only reboot to TWRP.

I have tried wiping data and reinstalling madOS_7.1.1_apollo_lite_20170318.zip but only get TWRP when I reboot

Any ideas??

Cheers!
[Miscellaneous Android Development] fards:
Please take time to read the rules of xda.

You as a junior member, are expected to comply with them.

Saying omg after repeating a complaint.

Not a bug report,

bug reports contain useful information such as logs showing the section where the problem occurs

But saying omg after complaining again

Suggests you have a somewhat immature attitude to this.

If you wish to participate constructively then please do so, constructively.

Do not repeat the same thing, it just gets peoples backs up. Especially when they are trying to fix your bug, and get email notifications of this thread!
[Miscellaneous Android Development] No1VIPER:
Don't forget that developers on here do all this for free. So just be patient and thankful, that they do it at all.
[Miscellaneous Android Development] gbl08ma:
I don't understand [MENTION=7844001]Zorikage[/MENTION], on post #123 you say the led is working (and is red) presumably after disabling ambient display.

http://xdaforums.com/showpost.php?p=70260906&postcount=123

But then on post #139 you say that messing with the ambient display setting "doesn't fix anything"...

It appears there are three different types of cases WRT the led situation:

- the notification led doesn't work at all, no matter what the ambient display setting is [MENTION=7844001]Zorikage[/MENTION] situation, assuming the truth lies closer to post #139 than #123...)

- the notification led only works (in blinking red only) only when ambient display is off (this is my case)

- the notification led always works (red only) even with ambient display on (@RalphMalph case)

Here's what I see (for me, XDA attachments only work in Firefox and I'm using Chrome now): http://s.lowendshare.com/11/1482775348.590.Screenshot_20161226-180100.png

It doesn't seem to have any updates installed.
[Miscellaneous Android Development] Zorikage:
The only Immature attitude is the "grow up" you've said before, you're even saying to me "read rules" when you don't even know if i did! Also that was a Question to get a quickfix if that was possible, also reporting my problem as developer ask me what the problem was with LED, so you're the one who need to read before reply ;)

Also saying LED is not working still after that things other user said IT'S SUCH A GOOD INFORMATION ITSELF.

Like i said before, i've donated too because the developers are doing a great job, i'm here to saying my REPORT about this ROM and trying to get a answer from developers that they already ask what LED problem i had! I've answer and then that guy come out with "grow up xdxd dont type omg xdxd". LOL

[MENTION=2150610]gbl08ma[/MENTION]

Edit: I tried that but doesn't work, i type "it work" because i was sure that if someone did that and it works that probably should work to me too, but no.

Also thank you for clear reply, you're a cool guy.
[Miscellaneous Android Development] fards:
"That Guy"

Is trying to fix your bloody problem!

But instead you have proven exactly the point i was making.
[Miscellaneous Android Development] gbl08ma:
Anyway, and in an attempt to find some "quick fix" and maybe help the devs, I have been experimenting.

If, as root, I write directly to /sys/class/leds/... all the leds work as expected. They even stay on during standby. Independently of "Ambient Light" being on or off. So everything appears to be fine when it comes to kernel control of the leds. The problem needs to be solved on the Android side of things, I think.

If you have rooted the phone you can try it yourself, using a terminal emulator:

$ su
# echo 255 > /sys/class/leds/green/brightness

(the led should go on. try pressing the power button, it should stay on)

# echo 0 > /sys/class/leds/green brightness

(the led should go off)

(repeat for the red and blue leds if you want)
[Miscellaneous Android Development] Zorikage:
You're such amazing man, i didn't tried it yet but i'll take a look about it, great work.
[Miscellaneous Android Development] fards:
Does it without root? If by might be something as simple as permissions, as i was looking at sepolicy.
[Miscellaneous Android Development] gbl08ma:
Note that when I said they all "work as expected", I meant they light up when you tell them to. It's not going to fix the notification problems, only make sure the kernel can turn the leds on and off (and that the leds have not gone bad on your phone for some reason). Just making sure to stay clear of any misunderstandings...

No, I began by trying without root and it gave a permissions error... now that I think about it, yeah, that could be the problem. But I can't mess with the leds like that as non-root on my MTK6589 phone either, and there the notification led works fine. So that's not necessarily the problem (note however that said phone is running Android 4.4 and that was many decades ago... oh wait :laugh:).
[Miscellaneous Android Development] fards:
I'm wondering if it's a naming convention. they are set up as devices/platform/leds-mt65xx

Something to pursue
[Miscellaneous Android Development] Zorikage:
And thanks again for another clear reply, it won't fix the problem but it's already something useful about it. (;
[Miscellaneous Android Development] w0nder:
my navigation buttons at the bottom of the screen stops working after 1 day with this rom. so this is what i tried to get rid of it:

- wipe cache/ dalvik cache - restart- still same problem

- so unroot and install stock recovery

- factory resett/ full wipe

- install stock rom with latest update, wipe cache again and boot

and these piece of .... navigation buttons still dont work

i mean wtf these phone has so many issues and now its complete useless for me. i hope efox-shop will take it back. -.-
[Miscellaneous Android Development] Verevka:
AOSP is very good, thank you very much for this, but I want CM14.1 :) will you publish the device tree for your other devices? Or not worth it to wait and try to gather from what is?
[Miscellaneous Android Development] superdragonpt:
CM is dead.

CM N lacks some things

Not updated to latest buildID

Etc

Device/ vendor:

I'm still thinking if I will release those

People use and abuse of our devices/ vendors /kernels

.. And never use it on the right way --> cherry pick / credits ..

Its something I need to think about ...

GPL part its done, kernel is public so we are in compliance .

As a note:

The issue you previously reported Is now fixed.

Should come on next build

Thanks reporting that issue.

EDIT: in my personal opinion,the best route right now is going the AOSP way + adding custom features/ personalizations, that's something we've been doing , and this ROM already haves a fair amount of those.

The route is to add more features, but, that don't " collide " with AOSP.

BB
[Miscellaneous Android Development] Huncriter:
lets wait linageOS
[Miscellaneous Android Development] Verevka:
I've tried, wishing to join - https://github.com/Verevka/android_device_vernee_k15tb_a

Again, thank you M. A. D team!!!
[Miscellaneous Android Development] Black Manta:
LineageOS sources are there! Btw. cm sources under another name. :D
[Miscellaneous Android Development] gbl08ma:
There are other custom ROMs besides CM/LineageOS. Even if these other ROMs have not made a Nougat release yet, they'll certainly get there some day. Having device/vendor trees that are not polluted with MTK's crap would greatly speed up the process of getting other ROMs to work on this phone, not to mention increase the probability that it will be maintained into Android O, P, ...

With the amount of RAM this phone has, except for hardware failure, specs-wise I don't see why it won't last as a mid-range for a long time.

While I like AOSP very much, on other phones I have tried other ROMs, and seen and used features that will likely take Team M.A.D. months or years of work to replicate without bugs - time that would probably be better spent freeing other MTK-powered phones from their "misery". Who doesn't like choice?

However, I agree that ensuring proper licencing and attribution to those who did the hard work is a problem that is very hard to solve. In fact, with this phone alone, the track record is already not so good, since I've read there are some ROMs floating around with custom kernels for which the source is missing, in violation of the GNU GPL. I have also read that Team M.A.D. has been burned bad in the past, with people stealing their work.

Sometimes I try to think of a technical measure that would ensure proper attribution, but history has told us that technical solutions rarely fix political problems. The only "winning" technical solution here is to not release the source, but I hope you recognize that this way of thinking is exactly why many phones today don't have their sources released. In fact, it was this way of thinking that resulted in me having three devices stuck in Android 4.0, 4.2 and 4.4 in my desk, when two of them have specs sufficiently good to run Android 6+.

I see that your position lies more on the side of "if anyone wants more custom ROMs, they are free to repeat the work we did for their own builds": a view I can completely understand, although obviously not the one I support most. I'm very grateful that you decided to begin working on this phone and brought us 7.1.1 in record time, independently of source availability. It's not like most MTK-powered phones have sources available (at least, up-to-date ones) and even the source release for the Apollo Lite officially never happened, and yet people still buy them and use them.
[Miscellaneous Android Development] RalphMalph:
Adding to my review.

Nightlight is not working good. It stays on. Eventhought i have set end time
[Miscellaneous Android Development] lymbra:
confirmed - same here
[Miscellaneous Android Development] skylineone044:
I think you've got a recovery bootloop...

Maybe you can look at this theard:

https://xdaforums.com/showthread.php?t=2426426&page=38

:)
[Miscellaneous Android Development] iRed4321:
Hi everybody !

1: sorry for my English

2: thank you so much for your work, it's awesome.

In France, we have a application call molotov.tv to watch live TV free, but since I flash the rom, I got this error message when starting to watch the TV : This device does not support the required DRM scheme.

Any ideas ?
[Miscellaneous Android Development] Black Manta:
DRM = Digital rights management.

It's a method to control media usage.

Because your device is modded with a custom rom it won't work. :)
[Miscellaneous Android Development] iRed4321:
Ok and is it planed to add theses DRMs in a next realase ?
[Miscellaneous Android Development] Xorianator:
Think that's nothing the developers can do. Write an e-mail to the developer and tell him about your problem, hopefully you'll receive an answer with a bugfix :)
[Miscellaneous Android Development] iRed4321:
I have to write an email to the mad team or to the developer of my app ?
[Miscellaneous Android Development] Black Manta:
I have a bugfix. -> Stock Rom :P
[Miscellaneous Android Development] Xorianator:
lol wtf?

I mean't he should write an e-mail to the app devs
[Miscellaneous Android Development] Black Manta:
Okay, that wasn't very clear. :D

But why should the app developers change that? I mean DRM is used to control the media usage to prevent the abuse of the program as I understand.

And otherwise flashing Stock Rom could be an option too. :D
[Miscellaneous Android Development] Xorianator:
Flashing Stock ROM = Solution for everything, even peace on earth *topkek*

Idk why they should, but if he would say "Hey look, there's a problem on that app with this device on that ROM" they could say him how he can fix it / if it's possible to fix that :)
[Miscellaneous Android Development] Black Manta:
It was even more a joke than a real solution. :D I wouldn't change back too. Maybe he has an unlocked bootloader. I know from LG phones that DRM isn't working with LG devices which has an unlocked bootloader. Could be the problem here.
[Miscellaneous Android Development] oliveirag97:
Hi, I'd like to know what the best Rom for the apollo lite vernee, which has the longest battery life

Sorry for my english
[Miscellaneous Android Development] Black Manta:
There isn't really the best rom for our VAL. Allof the roms have their own king-features. But I think the longest battery life always have the stock rom from Vernee, but it isn't the newest Android version and don't have all these features from M.A.D...
[Miscellaneous Android Development] cedricboquiren:
New great features has been said to be in the next madOS for Jiayu S3. "Double-tap anywhere to lock" is one. More likely, those new features would also be present in our next update (if there would be any). So guys, you know what to do. Raise your hands and give power to the superdragon and his gang mates. Haha
[Miscellaneous Android Development] Xorianator:
Instagram & Snapchat Users hate this trick.
[Miscellaneous Android Development] Black Manta:
Haha yeah! :D I personally swear on LineageOS. First build is running. :D
[Miscellaneous Android Development] Xorianator:
The build from Verevka? How is it running?
[Miscellaneous Android Development] Black Manta:
PM :D

This thread should not go too off-topic.
[Miscellaneous Android Development] mujju85:
Can I flash this rom on Redmi note 4 both are having same hardware
[Miscellaneous Android Development] RalphMalph:
Just try
[Miscellaneous Android Development] Jalfrezi:
For some reason my middle section on the screen isn't as responsive as the rest, is that just my phone or anyone else had this ?
[Miscellaneous Android Development] cedricboquiren:
Of course you can. Vernee is like Xiaomi, plus they got almost identical hardware. [emoji1] [emoji1]
[Miscellaneous Android Development] Black Manta:
Redmi Note 4 != Vernee Apollo Lite

Yes, it's so simple.
[Miscellaneous Android Development] Pbakki:
Works for Apollo instead of Apollo Lite?

Hi,

Does this work for Apollo instead of Apollo Lite?
[Miscellaneous Android Development] Xorianator:
Yes, but u need to wipe the EFS partition to getting it working

No it doesn't, pls don't delete your EFS partition!
[Miscellaneous Android Development] Black Manta:
From all our comments in this thread, what do you think? :D

Little hint:

It won't work! Its's another device. Vernee Apollo Lite roms are only working on, what a surprise, a Vernee Apollo Lite. :P
[Miscellaneous Android Development] mujju85:
Got this error while installing
[Miscellaneous Android Development] reebomber:
Guess it doesn't work, then.
[Miscellaneous Android Development] fards:
Oh there's always a chance it'll work.

Sometimes it just needs a bit of assistance.

To be able to squeeze it in sometimes you have to use a 10kg sledge hammer.

Other times it involves throwing the phone at the rom , or alternatively dropping it on the rom from several stories up .

:p
[Miscellaneous Android Development] trojanere:
Use the MAD twrp download​.
[Miscellaneous Android Development] Black Manta:
1. The package does not support the Redmi Note 4 alias Nickel.

2. I don't know which storage version you have but there is a high chance that the Note 4 has a diffrent partition layout.
[Miscellaneous Android Development] RalphMalph:
Guess its not working
[Miscellaneous Android Development] nature boy:
What's with the epic trolling?