hannah/rhannah/ahannah I NEED TESTERS PAY ATTENTION [mainly from rhannah] - Moto E5 Guides, News, & Discussion

To get more android ROMs 11 and 12 I need the support of the community and the way to give it is by testing my builds
I am currently unofficially maintaining moto e5+ havocOS and working on the creation of the 4.9 kernel which will be a huge improvement on the existing roms with new additions like EAS and more which will allow better performance, battery life and why not a small or medium overclock when I figure out how to do it right.
This also opens the way to stable android 12/L builds (remember that the current kernel 3.18 is not supported on android 12 and while the builds do start they are quite buggy.
for the work with 4.9 I am receiving a great help in the development from marcost22 but in addition to developing the kernel if it is not tested it is a waste of time, we are doing everything possible so that the device does not die and if you want that is yours time to help
there is currently no 4.9 support for hannah and ahannah so if you want to be a tester and you have that variant the builds will take time to arrive as I have to spend some time adding the dtb and first I prefer the kernel to be somewhat functional
in case you were wondering the builds with 4.9 already start but have some issues like audio, fp, gps, vibration and the camera can't record video, once that is fixed we will start working on adding support for the remaining variants and stuff like EAS and frequencies, after this I will build havoc with 4.9 and start working on android 12/L
I don't usually look at xda's private messages much, so it would be better if you send a message to @STKUser , if you don't know things like how to get logs don't worry because nobody is born knowing and everything can be learned.
With the help of the community great things can come, stay tuned.

Related

Custom ROM comparison database 2.0 (open to edit for public now!!!)

UPDATE: Database 3.0 can now be found here
Someone asked me to create a thread here for my custom ROM comparison database, so that's what I'm doing here now.
A few words from my side so you know what to expect of it and clear things up.
This is the original text I posted on my blog, so I'll just put it up here as well.
At the end of last week, I asked on G+ what to do next, an app comparison or a new custom ROM review. On of the first answers that got my attention was someone asking for a custom ROM comparison instead. I thought about it for a while how this could works since I can’t show them off side by side and it would be difficult no matter what. While thinking along I also remembered one post on YouTube where a viewer gave me the constructive criticism on the videos getting too long, especially the part where I listed all the features in the video review. I told him I am aware of that fact but I still haven’t found the right solution to make the videos shorter without missing any important specs. After some more thinking the idea of the comparison database was born.
The idea behind the database
Creating a database that contains all the available features clearly visible and quickly to access for everybody was actually the hopefully right solution. Using it I don’t need to waste anymore time on rattling down the whole list in my video… this saves me a whole lot of time but of course also you. And if someone wants to know if a specific feature is available in the reviewed ROM he can just quickly check the database and look for it, it’s as easy as that. Of course this method also allows me to focus more on the important aspects of the ROM itself.
Creating the database itself took quite some time for sure but in the end I think this is the cleaner and smarter solution for everyone. I hope this to get a helpful tool for everyone to easily find the right ROM for himself that suites him the most.
I did 2 videos, one quickly explaining the purpose of the database itself and an additional one explaining some of the more important custom ROM features so that people who are maybe new to custom ROM flashing know what to look for. If you see any feature in my database and wanna know what it is for or what it does, leave me a comment. I will then either quickly explain it if possible or collect some of the requests and make another “features explained” video.
Here is the link for the database (it will also be attached to every upcoming custom ROM video as well as the matching article), it will be updated with every upcoming custom ROM video review. I am no professional in text editing, so if someone is maybe bored or wants to help me out in making a better and more professional appearing database to improve it, please contact me, I’d really appreciate it.
Click to expand...
Click to collapse
Features of the database
--------------------------------------------------
- detailed list of all possible custom ROM feaures (~100 at the moment, constantly growing)
- containing 13 of the most popular ROMs + stock Android ROM + Xposed Framework to compare with each other (list is still growing)
- a lot of useful additional informations like links to downloads, ROM's websites, G+ communities and much more
- everything is sorted logically and color coded for fast and easy comparison
- all features have a quick explanation, expecially helpful for custom ROM beginners
- a lot of maintainers to keep it updated as good as possible (12 maintainers at the moment) - always looking for more, feel free to join
- constantly working on improving and enhancing the database
here is the link to the database 2.0 - thx to @parker09
some additional videos to explain the whole thing again...
Please feel free to leave any comments.
I'm a real Google docs noob so if someone maybe wants to help me clean it up and polish the style, just contact me.
And if this thread is posted in the wrong section, please just let me know.
UPDATE new host
Updates
Update
I read the posts here and on the portal and wanna set some things straight.
I do the database including the reviews in my free time, but besides that I´m also blogging,doing app/device reviews, how to´s and similar stuff so time for the database is therefore limited. That´s the reason I can´t progress with the database as fast as I would like to, also my way of testing takes up a lot of time.
I will of course try to do it as frequently as possible and of course ROMs like AOKP and Omni will follow in time.
That´s it for that.
Regarding mistakes and such, I know the database isn´t flawless but I´m not doing errors on purpose. About missing features of certain ROMs, it is possible some ROMs now have features that weren´t available at my time reviewing it but it´s almost impossible for me to keep track of all changes since I use different ROMs all the time and can´t always go back to already reviewed ones.
Update 2
Big change, after all what I read, I finally decided to make the database open to edit for public. Everyone can add ROMs and changes as he wishes to. I only ask users to be resposible and keep everything clean. Feel free to make new entries or correct errors if found. I think this is the best way for the database to grow.
The 2nd change is the move to another design made by @parker09 that is way nicer and better in my opinion.
The old one will still stay but won´t be updated anymore I think. So don´t forget to change your current link to the new one.
BIG THX to everyone in advance who decides to particate on working on the database, I hope the new way is a win for everyone.
Update 3
Sorry to say but the open to public idea wasn't the best it seems since the database somehow got messed up a bit. I want to prevent this from happening that's why I have some rules now to hopefully keep things clean and right this time.
Everyone is still welcome to participate in maintaining the database but has to do following now in order to get permissions to edit.
This reason for the rules is so I can better keep track of what gets changed by who and I know which parts are getting updated and which not.
How to get permission to edit?
Please contact me via PM on xda with the following title...
maintain custom ROM database "your email adress" "your google name" (the name that will appear when editing the document)
- Please also write down your name and email again within the pm just to be sure
- Please tell me which ROM(s) you would like to maintain or what you plan to edit.
- Please tell me if it is ok to add you to hangouts, this would make the teamwork faster and easier
Rules for maintainers
can now be found directly in the database
I want this so I have a list of all the maintainer and know who does what, so things don't get mixed up like 2 people editing one rom at the same time getting each other between in their way. This gives me a better overview so I can track the changes.
THANKS TO
-----------------------------------------------
n3ocort3x - AICP Team member
owain94 - PACman Team member
vedantgp - CyanFox Team member - Special thanks for a lot of groundwork&more
josegalre - Special thanks for a lot of groundwork&more
jrudyk
msn.debord
louisjms
lordbalmon
septigation
l3v14n
Thank your for publishing it here as well. This will be helpful for all of us. :good:
SlimBean has Breathing SMS. I should know I ported it (its in MMS settings)
cordell12 said:
SlimBean has Breathing SMS. I should know I ported it (its in MMS settings)
Click to expand...
Click to collapse
Maybe it didn't have it back when I reviewed it or I missed it. Will change it later. Thanks for the heads up
Can you add what you can do with stock+GravityBox? Then people can see which benefits they can get without flashing roms.
Hi nimrodity,
please make it available as a online tool for all ROM makers, so that they can update it as and when possible. and then there's no need you to update it.
Nice I did a column for Paranoid Android (as best I can - some features I don't know what they do) but did as best I could so if you want to copy & paste it.
https://docs.google.com/spreadsheet...VoZ1l0bWxoYnVzek9oNnhlWXc&usp=drive_web#gid=1
On the second sheet I started one ages ago and that's the style I went with, and you hover over for what their options are.
Interesting, but what I would really love to see is developers from cross-ROM platforms joining hands
Lastest Carbon have got Paranoid PIE.
Small adjustments
You had a really great idea by doing this. I once search for something similar to this spredsheet and didn't find anything useful...till now!!
You did a wonderful job!
I just noticed 1 small thing and my other point is a suggestion:
1. In CM10.2 you have an option for the vibration intensity only, so maybe you could add to the "vibration" section: yes, but limited.
2. My suggestion would be to add another "spec" for the ROM. It would be "screen color/gamma calibration". It's a very interesting feature and CM10.2 (latest nightly) has it.
What do you think?
Thanks
Keep up the good work!:good:
maxver0 said:
Lastest Carbon have got Paranoid PIE.
Click to expand...
Click to collapse
I know but it didn't back then when I reviewed it. I can't always update the database especially with the old review build date. It would be too hard to keep track of all.
Thanks for Your work... Hope You will add more ROMs to this database and I hope other members will help You to get the info You need for awesome ROMs like:
Purity...
crdroid
XenonHD
Liquid Smooth
Vanir
Carbon
Illusion
beanstalk
Jellybam
... and more AOSPs
... ... ... ... OMNI
Purity, Vanir, Jellybam and XenonHD should be simple to track because devs keep the same MODs&features... little changes on every new build
More difficult to track other ROMs that add&remove features very often
I can't help You because I'm a Stockish man and I won't try AOSPs for now
Thanks for useful database, It will sure help me when I will going to flash new rom
felix1234 said:
Can you add what you can do with stock+GravityBox? Then people can see which benefits they can get without flashing roms.
Click to expand...
Click to collapse
Doesn't really make sense since it's all about custom Roms but I already thought about doing a separate review for the blog.
Not sure about your idea, will think about it though
itechengine said:
Hi nimrodity,
please make it available as a online tool for all ROM makers, so that they can update it as and when possible. and then there's no need you to update it.
Click to expand...
Click to collapse
As you can see by my simple list I don't know much higher about docs and I have no clue how to do such a tool. The idea sounds really cool if someone knows how to do that and wants to help out just contact me
parker09 said:
Nice I did a column for Paranoid Android (as best I can - some features I don't know what they do) but did as best I could so if you want to copy & paste it.
https://docs.google.com/spreadsheet...VoZ1l0bWxoYnVzek9oNnhlWXc&usp=drive_web#gid=1
On the second sheet I started one ages ago and that's the style I went with, and you hover over for what their options are.
Click to expand...
Click to collapse
Will check it later. If you see my YouTube channel you see my PA rant. I don't really have that much interest updating the database with PA since I'm not really a big fan of the to work. Nothing personal but I just can't get warm with their Rom
@nimrodity
Great work. Important factors when choosing rom could besides features be "RAM usage on clean install and no tweaks/installed apps" and benchmarks based on the same conditions.
But anyways, awesome work :thumbup:
pemell said:
@nimrodity
Great work. Important factors when choosing rom could besides features be "RAM usage on clean install and no tweaks/installed apps" and benchmarks based on the same conditions.
But anyways, awesome work :thumbup:
Click to expand...
Click to collapse
Sorry I won't including benchmarks since they have nothing to say about performance in daily use. They are no important factor for me. Same for the rest, also I mention performance and such in my video reviews, don't plan on adding that stuff directly into the database though
On Cyanogenmod it says :
Volume Music Controls : music controls visible only but not with volume buttons.
You can control the music with the Volume buttons whilst being locked.
And if Poweroptions refer to the "menu" that shows when pressing the power button, you can en/disable airplane mode and select "Screenshot". And you can switch between Silent/Vibrate/Sound Profile.
Why no MIUI?
Great work! Just one little nag - why no mention of MIUI? It's distinct feature set should surely warrant a review, but that's just my opinion.
jwchips said:
Great work! Just one little nag - why no mention of MIUI? It's distinct feature set should surely warrant a review, but that's just my opinion.
Click to expand...
Click to collapse
My database is far from being complete, I just started . I chose my Roms randomly until now. Miui is still possible to come

[ROM] CyanogenMod CM-13.0 jgcaap's builds [EXT4/F2FS Compability]

Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So now I come to bullhead! After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.11.0.0
Optimized SQL code for faster Read/Write
CM Super User (for now is the most stable one)
Kernel with F2FS support
Improved Code of frameworks
Optimized Build with custom toolchain on ROM and Kernel
Optimizations for our chip
Improved sound with speex resampler
Improved bionic with many optimized libraries (faster rom)
Improved Art with upstream patches
Optimized native frameworks for our device
LZMA updated to the latest
Proguard 5.2.1
Google Webview
F2FS ready for data and cache
Immersive mode
Expanded Notifications
CAF Task Manager
Snapdragon Camera
Network Monitor
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
​
As you might know, all credits go to CyanogenMod Team.
Source Code
If you like my work, please consider a donation.
reserve
Frequently Asked Questions:
Q: What changes have you made between versions?
A: All changes made are the same as CyanogenMod ROM which can be found here: http://www.cmxlog.com/13/bacon/ and all manual changes will be also stated on 2nd post.
You can also check on Settings --> About where is all the changes .
Q: What is LZ4?
A: Read here about the project: https://github.com/Cyan4973/lz4
Q: Was latest build used LZ4?
A: This is still under testing and I'm working on it. It'll be on the test folder.
Q: What is the test folder?
A: Unstable, and test builds where I seek to study a new configuration to enhance user experience.
Q: Why don't you always share change logs?
A: Limited time. Sorry about it.
Q: Why do you many times ask for donations?
A: Well... This work is free, and as you know if you like it and on your own free will you think I deserve and currently wish to help me out as I am currently going to become unemployed and as also I study for my Masters in Finance , I believe is only fair. While you use, I'm testing and investing my time on it. Should be rewarded because of that right? Is only fair.
Q: Do you receive alot of donations?
A: Since last year until today I've received around 300 euro. But I've invested 1000 hours on these android builds. That gives a ratio of 30 cents an hour.
Q: Why do you still invest on android since it doesn't provide you any feasible income? I would have already quited!
A: Basically this forum makes me relax.
Q: Will you leave cm builds when exodus is released ?
A: I didn't plan on giving my cm builds, but if exodus prove to be superior why should i have double work right? Only time and users will tell.
Q: I'm confused. I have no clue which build is the latest!
A: You can always download again!
Q: Your site have ads why?
A: Need help on extra wealth to survive. Leave some clicks while you visit is only nice.
Q: I want more from the rom!
A: Me too!
Q: Why you sometimes ignore users?
A: I never ignore, just don't have time to answer all. Please help one another and also use search button. I think you prefer me learning to bring something nice than post all the time right? hehe
Q: I have so many questions to ask you!
A: I can provide many answers! Just ask!
Q: Can I PM you?
A: Only when is urgent!
Q: How to report bugs?
A: Our bugs are CM bugs. Report on JIRA: https://jira.cyanogenmod.org
Q: Are you CyanogenMod maitainer?
A: No, just an user which wants to have better builds possible. But would be nice to see CM adding me to the contributions list.
Q: Why Slim gaaps? Open Gaaps are so much cool!
A: Open Gaaps has provided many unstable issues which makes the phone unusable until a clean format. Slim gaaps have shown to be better on that.
Q: Why some buttons of UKM don't work?
A: Need time to improve that..
Q: I want an update app to auto update roms. To lazy to check the thread!
A: I understand, for now is not feasible to do it as I need time to analyse and understand best solution as I update tool-chains regularly and also is not my priority. Remember time is limited for me.
After positivive feedback i've opened this thread. New build in 2 hours Please wait and download.
#vızzz
thank you so very much
Cool can't wait.
Is up. let me know.
jgcaap said:
Is up. let me know.
Click to expand...
Click to collapse
Hey dude, ran some of your CM builds on OPO.. always smooth... good to see you here! Downloading now.
Very excited for this! Thank you!
Btw only kernel I didn't add yet f2fs. Will add next week with time.
This is the Rom I'm waiting for
Hopefully you will keep updating it since most of the roms stop updating after 18 months.
Apart from f2fs fstab, which you may already know about, everything seems to be working fine. Great job as always. Big thanks!
Will test some more.
Sent from my Nexus 5X using Tapatalk
ashatter said:
This is the Rom I'm waiting for
Hopefully you will keep updating it since most of the roms stop updating after 18 months.
Click to expand...
Click to collapse
Since the chip type is the same I'll merge some optimizations to the kernel from bacon. I should have at least one more year of my time to this stuff
On the 02.02 build i had issues with camera, but I think it was something wrong with my setup. On the latest build everything is OK. I'm eager to see what base you'll choose to work with in the future. Since you're using ubertc as a toolchain you can certainly try Ubermallow which I think it's the most up to date Aosp build.
Please give feedback Thanks.
jgcaap said:
Please give feedback Thanks.
Click to expand...
Click to collapse
What's the deal with 0.92x for animation? Is this something you choose arbitrary or just because?
marioemp2k7 said:
What's the deal with 0.92x for animation? Is this something you choose arbitrary or just because?
Click to expand...
Click to collapse
I choose.
Chronzy said:
Hey dude, ran some of your CM builds on OPO.. always smooth... good to see you here! Downloading now.
Click to expand...
Click to collapse
Things improved alot... Secrets are beeing found each day
joemanbui said:
Very excited for this! Thank you!
Click to expand...
Click to collapse
Thanks! Let me know how it goes.
Outstanding. No issues at all. Battery is amazing.

Bugless ROM(s)

I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch off/on - you switching off one sim and then can't bring it alive even after reboot.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
ViperOS lacks updates. Otherwise, it's a great rom really
Egyptiandroid said:
ViperOS lacks updates. Otherwise, it's a great rom really
Click to expand...
Click to collapse
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
comunity said:
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
Click to expand...
Click to collapse
Then, can you suggest a ROM that has the fewest bugs, besides great battery backup?
Egyptiandroid said:
can you suggest a ROM that has the fewest bugs
Click to expand...
Click to collapse
it was done in my previous message - DotOS. One more choice - LOS from HigwayStar. As I found these twos are both without "sim switch off/on" bug. But they have some other bugs (f.e. dark video).
Now I switched from DotOS to HigwayStar because HWS still working on it, and DotOS is freezed.
comunity said:
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch of/on - you switching of one sim and that can't bring it alive.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
Click to expand...
Click to collapse
It amazes me how anyone can post anything on this forum...
Can't you just dislike this post?
It amazes me how anyone can post anything on this forum.
Click to expand...
Click to collapse
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
comunity said:
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
Click to expand...
Click to collapse
If you're so dissatisfied, don't change ROM's then.
Hey. There's a good bugless(ughh) ROM it's called stock ROM. If you're not satisfied You can actually tell anything to them cuz you have paid for it. Have you tried that?
If you're so dissatisfied, don't...
Click to expand...
Click to collapse
my question was not about my satisfaction. it was about statistics - how many bugs from my list and which ones have every ROM published here.
I don't required recommendations or suggestions. I will be glad to see simple answers about each of 12 item - bugs exist or not. from anyone who had test them by himself )
Let me show answer example that I'm expected on:
LOS 14 from HigwayStar
fast charge - working but haven't indicator in status bar.
root - Magisk 16 built in ROM installation script
NFC & safetynet test - working, my payments were accepted lot of times. installing xposed module broke safetynet test (
VOLTE - supported, but I can't test bcz of absence 4G
sim switch of/on - working.
flight mode - after switching it off you can make new calls without any bodymovements.
led indicator - working out of the box. you can setup 16 mln colors, blinking speed and delays.
double tap to wake up - working from the box.
one key (energy saving switcher on left side) - may work, but ROM author decided to switch it off in latest release
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo especially for dark scenes.
finger print actions - work after reswitching navigation buttons, even without registering FP.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use. simply calculation issue, bcz battery isn't really draining by sleeping BT.
it's not an example. it's my real report about ROM that I'm currently using.
this report may be also about my DotOS usage, but i switched from DotOS to HWS because DotOS - frezed, and HWS - still under development.
Do you know what all bugs(super annoying) the stock ROM have? Did you bust into Lenovo forum and post things like this?
If yes then wait for their update (rip in advance)
If no then go try that and tell me if somebody gives a #@!*
This ROM development is nothing you own. It's developer's hobby which they do in their free time. So creating a thread like this with such a demanding attitude is crossing the line.
You said about the long post on every ROM like intro and blah. Blah. You should read them.
* We are not responsible for bricked devices, dead SD cards,
* Third World War, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
If you think you can make something better do it by contributing towards ROM development.
Wow! So much angriness for one simple question! )))
Dear Senior Member Siva Mk, let me ask you why you are wasting your time and writing to me one more "long post",
You said about the long post on every ROM like intro and blah. Blah. You should read them.....
Click to expand...
Click to collapse
instead of provide us answers for my question, if you have any one?
You are right - no one owes nothing to nobody! at this and all other forums.
I DON'T REQUIRE from somebody, and from ROM developers especially - any warranties and immediately fixing all existing and not existing bugs. Please reread my very first sentence in first post.
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning.
Click to expand...
Click to collapse
I simply want to get help from other users (or ROMs' authors) and collect in one place info about ROMs critical bugs, which maybe helpful for all of us here, to choose ROM, most appropriate for himself.
I have a question - I had asked it. On my previous post I gave an example of answer that I expected. If you haven't such answer - please don't grow Universe entropy and simply ignore my posts and topics. Let we all stop this flooding, and will concentrate on help one to another
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
medwatt said:
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
Click to expand...
Click to collapse
He's just another one who wants attention
medwatt said:
And who are you
Click to expand...
Click to collapse
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Nice thread, Sorry there is no bug-less rom available for P2 right now ?
For me the only rom that has no bugs is stock mm 6 even stock nougat for me has a bug that Lenovo can't solve till now linegue os by HWS is the best with minor bugs that does not affect daily drive
comunity said:
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Click to expand...
Click to collapse
Dude seriously if all people have a attitude like yours developers will just stop building roms altogether.

Native Biometric API support in coming android versions(from Pie onwards)

I was doing research on android's Biometric authentication .As we know back in android Marshmallow(6.x.x) we got native support for fingerprint recognition/fingerprint authentication.Not too long samsung started giving new way to unlock devices iris scanner in s8/s8+ last year,so it's there own implementation in S/W and so main problem is you cant use their implementation in any custom rom because AOSP upstream does not supports it.Now from Android Pie onwards they deprecated FingerprintManager API and bring us new BiometricPrompt API,means we can use other methods like iris,face recognition and other methods for unlock/authentication.Probably iris or face recognition might come in coming pixel.
So my main point of making this post is to discuss about the existing device with proprietary sensors like in galaxy s8/s8+/s9/9+,note8/9,mi8,poco f1 etc etc! .
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
one thing i want mention:-i remember galaxy s5 released with android 4.4.x,which clearly dont have FingerPrintManager Api,but some smart dev xda managed to get that sensor working on android M based custom ROM .Sooooo maybe we will able to get our,s face IR working in next iteration of android pie.
I am learning about the android"s arch(also learning how to develop custom roms from scratch)
So devs on xda who have knowledge ,must share .i am always ready to learn
topics i refer for case study:-
https://source.android.com/security/biometric/
https://www.xda-developers.com/iris-scanners-native-support-android-p/
https://www.xda-developers.com/android-p-new-biometrics-api/
Help me out! I can only REPLY to threads, I can not POST such one!
thetripleS said:
Help me out! I can only REPLY to threads, I can not POST such one!
Click to expand...
Click to collapse
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Jaskirat singh said:
Bro you are new member, so don't have permission to post, go read xda's rules and terms of XDA. And secondly do a Google search for your problems and stop spamming irrelevant replies
Please!
Click to expand...
Click to collapse
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
thetripleS said:
Sorry for inconvinience, I digged google, i couldnt find anything! Please tell me when can i start posting questions?? Its true that i am a new member and i started XDA today itself.
Click to expand...
Click to collapse
Go here you get an idea which sub-forum you need to post
https://forum.xda-developers.com/poco-f1
.
RUPESHBW said:
Who are you to tell him what to do xda is about sharing tech knowledge there is nothing wrong in posting by new member. He giving his knowledge i had question with his argument above i got my answer. If you cant let other not demotivate.
Click to expand...
Click to collapse
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Jaskirat singh said:
If have you anything related to my topic then most welcome.
And who "ARE" you to correct me.
I didn't say anything offensive to him and secondly i told him to read to rules and terms.
And yea i was not demotivating him, its you who judging here.now stop arguing.
Please :- "STICK WITH THE TOPIC!"
Click to expand...
Click to collapse
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
RUPESHBW said:
Oh its you posted this thread i forgot sorry didnt see i thought somebody just delete this arguments :laugh:
Click to expand...
Click to collapse
Its ok :/
Jaskirat singh said:
Will we able to get those existing sensors work on custom roms?as far source code is concerned ,we got whole device code of POCO f1(i am not sure about IR face reco).
Click to expand...
Click to collapse
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it. But it's impossible to know for sure until actual official Pie comes.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
i was wandering around and testing some things with this device.
Yes! That ir receiver(sensor) IS behaving as camera (which is not a color sensor only takes IR as input)
For testing i used miui hidden settings app
Go to hardware test(CIT)>52.ir camera.
And voila! You can see output on screen what this sensor sees
NOTE:- you can open this CIT settings if you tap kernel version number times, but you won't get that "ir camera" option, soooo you have to install that app
Btw anyone working or creating device tree for this device?
Well yea xiaomi is notorious for not giving up whole source, that's kinda bytuh thing
CosmicDan said:
Correction: we do not have whole device code. Nobody ever gets whole device code.
We have kernel source, but it is missing something. Mostly audio and wifi stacks. Wifi is easy to fix thanks to CAF, but audio is more difficult.
Making custom ROM's takes time because it is one big experimental process to get AOSP to work with existing blobs (pre-built binaries from vendor for hardware access) because we don't have the source code.
For IR Face recognition, there would have to be a driver in kernel for the camera, definitely. But that doesn't make it a given that custom ROMs can use it. It may also be missing in kernel sources, like wifi and audio is missing.
Ideally, when Poco gets Pie official update, yes - it will use the biometrics API, meaning that custom ROM's should be able to interface with stock blobs to also support it - this is achieved in much the same way as experimenting to get all the other hardware working. But it's impossible to know for sure until actual official Pie comes.
Most of this stuff relies on CAF, probably. If the kernel driver for the IR camera is found, or included in kernel source (don't know if it is but my guess is no), then they will have something to work on.
I think it's a bit early to speculate on such things now, since there is no public announcement from the community of any AOSP release based on Oreo yet, even.
Click to expand...
Click to collapse
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
frietketeltje said:
Did you perhaps had some time to look in to this ?
If they used this api in the latest pie beta ?
i read something om miui forums that they used the biometrics API in miui 10 pie versions from other phones.
i'm lacking the knowledge to look in to this myself :/
Click to expand...
Click to collapse
I'm not sure where to look, to be honest. This seems more like a back-end thing that makes development easier, rather than adding new features? At least that's what I remember.
Also note that I have no interest in custom ROM's personally; I'm modding stock MIUI instead.

What ROM for everyday on Android 9.0 ?

:angel:
Hello,
I am looking for a rom usable everyday (stable and good battery management) for Android 9.0.
I hesitate between Arrow OS, POSP and Bootlegger.
What do you advise me objectively (with your comparisons if there is)?
I have more attraction for the Arrow OS because it was more advisable (but the POSP with agent_fabulos attracts me too)
Thanks in advance.
Hi,
at the moment I use the unofficial LinaAge 16 build:
https://forum.xda-developers.com/oneplus-one/development/rom-lineage-16-0-bacon-t3894699/page1
Therefore I used Tugapower, which is LineAge based. In both roms there was no single reboot or force close of any app. Wifi, GPS and all I use works perfect. I also like the LineAge camera and gallery. It's also nice, that if you're using the dark theme, the notifications are still in a light theme. At other, mostly AOSP based, roms I had problems with camera, torch and some theme issues.
What I'm really missing is that button remapping isn't implemented as good as in AOSP-based roms.
I don't use Gapps, Bluetooth or NFC. So I can't say something about that.
An other point of interest (at least for me): I think, that the support for LineAge is more guaranteed in future, since this is a big team with a lots of developers, which are active. I tested a lot of roms in the last months and many of them are discontinued now. If you're flashoholic this is no problem. But if you want a rim for the next months ...
There's also a "Flashoholic" thread (I think in the "General" section). And also a "Flashoholic" Telegram group, of you're interested in flashing a new rom every week ...
A, I forgot: battery is also good on LineAge (I'm using build in "battery saving" mode. - Also a unique LineAge feature, AFAIK.).
Gaukler_Faun said:
Hi,
at the moment I use the unofficial LinaAge 16 build:
https://forum.xda-developers.com/oneplus-one/development/rom-lineage-16-0-bacon-t3894699/page1
Therefore I used Tugapower, which is LineAge based. In both roms there was no single reboot or force close of any app. Wifi, GPS and all I use works perfect. I also like the LineAge camera and gallery. It's also nice, that if you're using the dark theme, the notifications are still in a light theme. At other, mostly AOSP based, roms I had problems with camera, torch and some theme issues.
What I'm really missing is that button remapping isn't implemented as good as in AOSP-based roms.
I don't use Gapps, Bluetooth or NFC. So I can't say something about that.
An other point of interest (at least for me): I think, that the support for LineAge is more guaranteed in future, since this is a big team with a lots of developers, which are active. I tested a lot of roms in the last months and many of them are discontinued now. If you're flashoholic this is no problem. But if you want a rim for the next months ...
There's also a "Flashoholic" thread (I think in the "General" section). And also a "Flashoholic" Telegram group, of you're interested in flashing a new rom every week ...
A, I forgot: battery is also good on LineAge (I'm using build in "battery saving" mode. - Also a unique LineAge feature, AFAIK.).
Click to expand...
Click to collapse
Sincerely, thank you for taking the time for your advice.
Have you tried POSP rom or Arrow OS?
Of course I can install them to test but having feedback is always constructive.
Do not hesitate if other people want to share.
Spy20 said:
Sincerely, thank you for taking the time for your advice.
Have you tried POSP rom or Arrow OS?
Of course I can install them to test but having feedback is always constructive.
Do not hesitate if other people want to share.
Click to expand...
Click to collapse
Yeah. Today I tested ArrowOS: still problems with the build in torch. Yesterday I tested the new POSP build: still bootloop when trying to flash latest Magisk... Now I'm back on... LineAge

Categories

Resources