[Android Apps and Games] csagan5:
1. because I am developing it. If you care to know the reasons, it is because I adopted versioning numbers which allow to install updates rather than reinstall. there is another change that I will have to do sooner or later, that is regarding the package name, but it can wait. Over time there will be less and less breaking changes of course; please bear in mind that I am not paid to develop this (it's in my free time), and surely not paid by you

2. Importing bookmarks from Chrome to Bromite is not something I committed to support.

Please be aware that I do not break any functionality on purpose, and all the versions released are always available on the github project. Bromite is provided "as is", it is what I use to browse internet and I am sharing it with everyone else. Nothing more, nothing less.

[MENTION=7750130]firmaniac[/MENTION] you can submit them to Github issues here: https://github.com/bromite/bromite/issues/ however no promises, if they are easy I might develop them but one has to see if they are 100% good features for all users. With (2) and (3) I agree they would be in line with Bromite.

[MENTION=4867978]m0ndul[/MENTION] thanks for checking this, I was not aware. It is not an intentional change and I wonder where it comes from...probably something changed in Chromium.

Edit: I went to check, this is not the reason of the install problem.

From the previous release, .144:

In the .150 release:

There was no application name change. I created a full diff of the AndroidManifest.xml metadata here: https://gist.github.com/csagan5/7036d68269e586e27d655f9d4a738c19

I still think that the install problem was due to the fact I started using Google Play's version code scheme for updates, so if that's the case the breakage will not repeat for next version. I had picked a higher version code number to prevent any issue, but apparently did not work.

I am not sure I can fix it, fixing it now will make it problematic for people that have already installed it with the new app name. However, if it causes problems (because the app name is the same as Chrome's) then we have to fix it and it's not a choice.

See above.

They have been submitted as feature requests already; I spent some time going through the CAF commits, however nothing was easy to import in latest Chromium trees and would require major work or a rewrite.

This could be due to the H264 improvements I enabled; please test with next release, and if still there I can make a build for you to test with with H264 optimizations disabled.

Data saver is a service by Google, they do not allow us to use it outside Chrome.

I am not sure you understand how data saver works. It uses Google's servers, so basically you think somebody would pay servers for you to have this feature and reverse-engineer Google's data saver APIs for free? Not going to happen. It would take a single person about 2 months of development, without considering the cost of the servers per month after the feature is released. Also, it is never going to be part of Bromite because the privacy goes out of the window if you allow Google servers (or anybody's else) to cache all your downloads.