Database Info

Collabertive Effort Community Update Application

Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon

Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though

Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.

As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.

I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.

Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!

I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.

michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.

akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.

akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?

Ups wrong theread

not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease

I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.

The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.

willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.

Maybe something a little like this?

Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^

willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.

senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...

Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?

Why Doesn't Anyone use Google Code for AOSP rom development?

As long as a Rom doesn't include googlebits it should be fine on google code right? It would be nice to use for bug tracking and a quick downloading service.

Doubt it, since I imagine that a lot of bits are closed-source and harvested from existing ROM dumps and so forth.

I believe quietblongs was the only dev here that actually built his roms from source. With that said. I mean the entire thing except some libs. But I'm not sure if anyone else is doing this. I think most of the aosp roms we have are ports with maybe compiled frameworks from source. Again that's just a guess.
But speaking of quietblongs... I wish he'd come back and make us a bad ass 2.1 aosp build.(a hint to quiet to build us another bare bones build)

I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream, magic, and nexus only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.

5tr4t4 said:
I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream and magic only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.
Click to expand...
Click to collapse
Yeah u will always need proprietary files to build aosp. That's what vendor is for. I've started gathering and trying to setup a community vendor for cdma heros. But just been to busy to finish. Will try soon though an put it on github for all to use.
But as for camera drivers and stuff like that. Ur gonna find that making libcamera build isn't gonna happen as of yet in 2.x aosp. Because it is broken as of the moment and doesn't make. The only solution to gettin camera into an aosp build is to use the libcamera and other camera libs from mine and Flipz HTC Rom. But even then ur gonna need a compatible kernel camera driver to work with it. As of now we haven't got that working fully. But also even once we get the driver working ur gonna have issues in aosp builds with camera as the gsm hero devs have found. As it stands now the aosp camera doesn't fully support our camera. Leaving them left with a 3m camera and I believe no video. It seems that HTC did some extra work in their camera.apk to finish up and give full support for our camera. The problem with that and aosp is like most HTC apks work in and with a HTC modified frameworks. So it goes deep into the framework.jar and many other frameworks files. I won't say it can't be hacked in some how but I will say it won't be easy. But if u manage to pull it of please share because a lot of devs have tried and haven't managed to pull it off as of yet.

Maybe you can point me in the right direction. Attached is my "vendor overlay" attempt. In the first case it's just Lox's stuff for hero with "heroc" in all the right places. The "extract" script is mine, modified by me given Cyanogen's nexus overlay example.
If you can create a git of a proper overlay, that would be great. Even if, as you say, it doesn't get us all the way to a working AOSP ROM.
Lox's language in his extract script is like Cyanogen's in his git repo, ie "who the hell knows if this is right, just guessing". So in that spirit, here is my attempt: a little experience mixed with vendor hatred mixed with voodoo
Feel free to correct me as you can, I would be grateful for a leg up from someone who has been at this longer.
P.S. I can't believe I had to "zip" up a tar.gz tarball to get it to attach to a dev forum (Invalid file). Man, I'm getting old.
P.S.S The included "kernel" file is a zImage I built from your toastcgh 2.7 sources in git. The wlan.ko was built against that...I should double-check that fact...

Ah well, maybe when they redo the forums here they'll think about bug tracking etc but I doubt it.

I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.

darchstar said:
I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.
Click to expand...
Click to collapse
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs

darchstar said:
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs
Click to expand...
Click to collapse
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.

5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.

5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
It would minimize on duplicate bug reports at least.

jonnythan said:
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.
Click to expand...
Click to collapse
Understood, but the proprietary stuff can be pulled from the phone and/or from official releases for other HTC devices given the right script. That's why we need the vendor overlay.
I suppose the follow up question is, "why not just contribute to Android's AOSP core code in git, why create a forked AOSP repo?". That might be right, but we still need the overlay to pull the right files from the device. Perhaps taostcfh or quietblongs or darchstar already have this stuff ready and I'm just late to the game (probably ). Fine, I'd love to see that work so I can help out where possible.
<mini-rant>
This OEM/vendor crap really sucks...should I just repeat what has been said everywhere (and knocked down for very sound business reasons): Google should have released Android under GPL.
</mini-rant>

5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
Exactly, thanks.

What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?

ffolkes said:
What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?
Click to expand...
Click to collapse
The fact that someone has to pay for it.

jonnythan said:
The fact that someone has to pay for it.
Click to expand...
Click to collapse
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...

ffolkes said:
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...
Click to expand...
Click to collapse
I have one too, but I would advocate for something more public, like git or sourceforge or Google Code, XDA, etc. You would want to make sure that you were gaining sharing capabilities and not just isolating yourself...either from upstream improvements or from other community stuff here and on other forums. A thousand people sharing is better than 10-20 people with a server, IMHO XDA has already proven that.
Plus, getting a development server going with all of the niceties of CVS et al is not easy...and there are ready-made solutions already available. None of this addresses jonnythan's point that some of this development is in legal limbo...what happens when someone , even by accident, pushes the google bits onto your public server?
...maybe you would get a cease and desist letter and become famous, LOL.

5tr4t4 said:
...maybe you would get a cease and desist letter and become famous, LOL.
Click to expand...
Click to collapse
Someone needs to combine the power of a forum with the legal protection of a public download site and the bug tracking of google code.
Apparently, I'm too lazy to code that all myself

[NLS] Beastmode's CM10 ROM 4.1.2 Full languages pack

Hi
NLS stands for National Language Support.
This package completes Beastmode's CM10 great ROM (coming in English) with all CM supported languages.
Instructions :
1. Flash CM10 V2 by Beastmode.
2. Flash cm10_nls_sgs4g.zip
3. Fix Permissions
4. Optionally flash 4.1.2 Gapps.
5. Reboot (go to System --> Display and turn off notification light).
6. In Settings - language and text - choose your language.
Enjoy!

mine

The build I am compiling will have rtl support in advanced settings!
But IDK if it will have languages in built.

airfluip1 said:
The build I am compiling will have rtl support in advanced settings!
But IDK if it will have languages in built.
Click to expand...
Click to collapse
Airflip, talk about it after you actually post a build. This whole "Look what I'm gonna do" is getting really old. I wish you the best in your quest to build ROMs but at some point you actually have to build something.

I have built roms. I have posted screenies, and I have posted some beta builds. Just because it isn't in the dev section doesn't mean that I haven't done anything with it. Right now AOKP seems to be having a lib issue, and I have exams, so I can't really build until then. Also, I don't see a problem with it since all the other devs do it. https://github.com/airfluip1/androi...mmit/cf07012b06b4ae3bcf2914fe698778a3c31b3cd4 is where you can see this change I made.
Also if you didn't catch it, http://d-h.st/Lke is a link to one of my builds

airfluip1 said:
Also, I don't see a problem with it since all the other devs do it.
Click to expand...
Click to collapse
None that I respect do it. It's one thing to say your going to do something. It's another thing entirely to come into other Devs threads and say "I'm gonna fix this" or "My ROM will have this". It comes across the wrong way. It would be like AOKP members coming into a CM thread and trying to one up them. It doesn't ever happen and that's because those guys have mutual respect for each other. I'm just letting you know how it comes across in print. It's up to you to figure out what to do with that info.

I apologize if it came across the wrong way though.

First of all - both of you are off thread topic !!!
Second, Airfluip has built things in the past and he has the capabilities.
I see no difference in posting "what I am doing" comparing to "who's ready for a flood" or "who wants some audioXX loving" which were all posted by our best and proven devs.
Third, RTL support is built in since ICS was out, there's no need to add anything.
I think the few contributors we still have here need a little more respect than given, that's all.
Even this simple resource adding required about 250 de/re-compiling and content copies, and it took some hours.
Now back on topic.

[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.