Related
Hello All,
Did ask this question in the main thread, however it might have been ignored, due to the heavy influx of posts. So I am using a custom ROM rootbox stable 4.0 on my SGS-II. Just wanted to ask that I maybe planning to buy the following type of bluetooth tags, once they become stable enough for main stream use.
1. http://www.sticknfind.com/
2. http://www.indiegogo.com/projects/button-trackr-find-lost-items/x/2060164?c=home
According to the information gathered these devices require "Bluetooth Low Energy" (BLE) enabled cellphones and the required software implementation profile to work on. Apparently in the Android domain only Samsung is providing it in S3, S4 and Note 2 only in stock ROM.
Just wanted to ask that does RootBox or any other leading custom ROMs supports this BLE profile, and if not at the moment, is there any plan to include it in the stable upcoming releases.
Thanks for the responses. Great work all the AOKP, Cyanogen, Paranoid, MIUI Developers.
HyperEscape said:
Hello All,
Did ask this question in the main thread, however it might have been ignored, due to the heavy influx of posts. So I am using a custom ROM rootbox stable 4.0 on my SGS-II. Just wanted to ask that I maybe planning to buy the following type of bluetooth tags, once they become stable enough for main stream use.
1. http://www.sticknfind.com/
2. http://www.indiegogo.com/projects/button-trackr-find-lost-items/x/2060164?c=home
According to the information gathered these devices require "Bluetooth Low Energy" (BLE) enabled cellphones and the required software implementation profile to work on. Apparently in the Android domain only Samsung is providing it in S3, S4 and Note 2 only in stock ROM.
Just wanted to ask that does RootBox or any other leading custom ROMs supports this BLE profile, and if not at the moment, is there any plan to include it in the stable upcoming releases.
Thanks for the responses. Great work all the AOKP, Cyanogen, Paranoid, MIUI Developers.
Click to expand...
Click to collapse
I am in the same boat as you. Need it to see my Casio GB-6900 Smart Watch which runs on LE. I have tried all nighly builds from haashcode and the rest of the soup. Not one has support for BLE. I hope they think of supporting this in their future release.
I am about to buy this phone because it is just so damn good for it's very low price tag, however one thing is bugging me about it. I came here to find that there are no Marshmallow ROMs for it yet and the main reason for me wanting to upgrade my phone in the first place is so that I will be able to run the latest Android ROM's without performance problems. I am currently on CyanogenMod 13 on my old Samsung Galaxy S3 and I like it, but it is slow. The Redmi Note 2 doesn't even have CyanogenMod support.
Is this because Xiaomi are going to release an official MIUI based on Marshmallow? I don't want to buy this phone if it means I am going to be stuck on MIUI or on an older version of Android. I am a bit perplexed because this phone sold a lot so why hasn't anyone made Marshmallow for it yet?
Do you think that development is going to pick up for this device or is this device a bad option if you want to run the latest Google Android (not MIUI)?
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
verbage said:
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
Click to expand...
Click to collapse
Thanks for the explanation. It seems really unfortunate that they haven't released the source. I guess I should either buy the more expensive Mi4 (which I believe the source is released for) or I can just wait it out and see if the source code get's released for the RN2. It seems strange to me that they wouldn't release Marshmallow-based MIUI for such a popular, fairly new phone. I think they will release it. If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
M will deffo be released for RN2. Main reason we still dont have it is:
a) first "official" device with M is supposed to be mi5
b) MTK prolly didnt polish 6.0 yet
Major companies that use X10 (eg Sony & HTC) didnt realse M for their devices either, at least as far as i know, however they are planned. So yeah M will arrive eventually, which is great, but that doesnt mean custom roms will get any better. And knowing xiaomi, and their kernel release policies, this is pretty much 100%. Pretty sure they still havent released any kernel source for their older MTK powered devices.
I think I'm going to buy the Mi4 rather because its kernel is open. I want to know that I'll be able to get android roms of any new releases. It's a real shame because the Redmi Note 2 is cheaper and a more superior device, but I have read that Mediatek are scumbags when it comes to releasing kernels because they want to force you to buy a new device when your OS becomes outdated which goes against the open source licence of Linux. Oh well, I guess that's business.
rimpy said:
If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
Click to expand...
Click to collapse
If they release MM-MIUI for the RN2, unless they release the source code, this will still mean that roms are cooked/repacked, or built from source, but probably imperfectly due to lack of source. Though MIUI is based on Android, I don't think there are free and open MIUI repositories where one could grab the necessary source code for the RN2.
At this point, like everyone said, it is very unlikely that Xiaomi will ever release the source code for the RN2. Without it, custom ROMs will never be proper, and it's the reason there are no MM builds yet.
However, even though MIUI is horrible and God knows that I hate it, it's quite usable. A version of the Xposed framework that works on the latest MIUI builds has been released a couple of days ago, and with it you can get most of the functionality a custom ROM provides. It's not perfect, and I'd prefer AOSP, but it is, IMO, the best this phone has to offer at the moment.
I only got mine about three months ago, and while there were many times I came to regret my purchase, every other phone in this price range and slightly above has inferior hardware. With that said, if you want a phone running AOSP or something very close to it, you'd be better off getting a Nexus or a device that is officially supported by CM.
Thanks all. I was just about to buy the RN2 but I am glad I posted here first. I've learnt a lot and I don't think I would be happy with a phone that has a closed source kernel. The Mi4 has a smaller screen, no SD slot, slower, and costs more, but its kernel source is released and it is supported by CM13. Still very good value for money so that's gonna be my next phone.
It actually isnt slower. Benchmarks only. If you run them side by side with either MIUI or CM youll see than Mi4 is actually much faster than RN2, so yeah, its a better option if you have the money
Just thought I'd make a thread about discussing the next version of Lineage OS. Lineage OS 15 is going to be out officially for our Axon 7 soon after the source code for Android 8.0 is released.
Haha how do you know that? I doubt that.
If past experience is any indication, I wouldn't expect it until about November.
Delete
OrdenKrieger said:
Haha how do you know that? I doubt that.
Click to expand...
Click to collapse
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
Doesn't mean that there is always some1 to maintain the device.
Edit: BTW I don't think that blogspot pages like http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/ being the best source.
Mod Edit: (non-English comment removed)
请仅用英文发表。谢谢。
Qǐng jǐn yòng yīngwén fābiǎo. Xièxiè.
Please post in English only. Thank you.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
OEM's are now required to provide support for two full yrs
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
It's not about AOSP , you can't build for non Google devices without CAF which hasn't been brought up yet.. It'll be a good month or so
kdp162 said:
OEM's are now required to provide support for two full yrs
Click to expand...
Click to collapse
No they are not, it's optional, there is no incentive for them to do so
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
You can compile AOSP for just about anything. It's getting ALL the hardware working correctly on a new release that's a problem. Sure, it might boot, but if you don't have audio or accelerated graphics, that's an issue. Once you have a working version from the vendor, then it's a lot simpler than just putting it together before that. And nothing happens if you don't have the drivers from the SoC vendors. That's why Project Treble is such a big deal, because if it works as intended, it will remove the need for those new drivers to get a new version of Android, because the HW abstraction layer will make the older drives work.
Waancho said:
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Click to expand...
Click to collapse
It could be that Motorola is releasing the drivers/SW updates. It really depends on the underlying hardware. If there is another device with the same hardware getting updated, those drivers can be pulled over and incorporated (the A7 has pulled a lot from the OP3). Or there are open source driver versions that could be pulled in.
Our biggest issue is that the audio chip we have isn't really on any/many other devices. So getting fully working drivers for that is a more limiting factor, than a Moto G 2013, which probably doesn't have anything outside of the standard QC SoC stuff.
And in the end, it comes down to the devs keeping stuff up to date. The Galaxy S2 is still running official LOS 14.1, because there are some crazy ass devs out there still getting stuff working on it. The more popular and easy to work a phone is, the more likely it will see longer 3rd party support. Sadly, the A7 is a little limited in both fronts combined with custom HW bits. The devs have done amazing work so far.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
therock11 said:
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
Click to expand...
Click to collapse
For gamers and daydream users that could be true.
When it comes to usability, privacy and customizations the LOS based ROMs are the first choice.
The audio issues are just minimal when you combine Dolby Atmos mod with custom rom.
So have you guys taken a look at Ordenkriger's post on the boot up of Lineage 15 with all the progress and what not?
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Cyberwolf2 said:
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
That's not an official source
bkores said:
That's not an official source
Click to expand...
Click to collapse
Ordenkrieger and Unjustified Dev think's otherwise..https://forum.xda-developers.com/axon-7/how-to/oh-lineageos-15-t3668956
Do you think this device will get custom rom support considering the price I reckon it will the only issue is the device is only available in india that being said oneplus only sells to a select group of countries
It will get custom roms, this phone will be available also in Europe and India.
I am planning to get this device. Earlier I was hell bent on getting Asus Zenfone 5Z which boasts of same configuration as OPO6, POCO F1. But then I saw how there is absolutely no development going on for the device! I am just hoping it doesn't happen with POCO F1.
Edit : https://www.xda-developers.com/xiaomi-poco-f1-developer-community/
Sounds promising. It's upto the developers now if they think this device deserves some Custom ROMs love ?
Easier bootloader unlocking, Kernel sources on Day 1 and Flagship specs at the cheapest available price... Surely it will get Custom ROMs once a few flash sales are over and the device ends up in a few experienced developers' hands... It surely will be the Best selling SD845 mobile in India for the coming months since other competing phones are a bit old and costly... Expect to have really healthy development considering Xiaomi phones generally have a very active community for Custom ROMs...
Dang. I just bought a mint condition Oneplus 5T for $320. Did I make the wrong decision? xD
This thing will get a lot of custom roms!
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
I think by the end of next month there will be lot of custom roms for Poco F1. Good gesture from Xiaomi. Supporting developer community.
No question about that, custom ROMs are coming, definitely. Just think about this - the max 2 has already been treble-ized and a custom ROM based on android 9 is in development.
Xiaomi will be releasing GSIs for this which will be very easily kangd into custom ROMs. No good reason why there won't be loads of development
thesoupthief said:
Xiaomi will be releasing GSIs for this which will be very easily kangd into custom ROMs. No good reason why there won't be loads of development
Click to expand...
Click to collapse
There is a difference in custom roms and development. They are not the same. Xiaomi always has roms. But none are developing on the device or working directly for that device.
Also the gsi don't do any good. Not for custom roms. Those will be still have to be built per device.
zelendel said:
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
Click to expand...
Click to collapse
Those in NA might import it, but the deciding factor will likely be availability of source, and 3G/LTE band support on global variant. Americans don't incur an "import" fee/tax like in other countries, so price shouldn't be an issue.
Kernel source is due for release on August 29th.
Reportedly compatible with the following US networks (covering most bases, I reckon):
T-Mobile 3G, T-Mobile 4G, AT&T 4G, Plateau Wireless 3G, Union Wireless 3G, Viaero Wireless 3G, West Central Wireless 3G, U.S. Cellular 4G, Verizon 4G, C Spire 4G, ClearTalk 4G, iWireless 4G, Limitless Mobile 4G, Mosaic Telecom 4G
This phone is treble enabled, so you can directly flash GSI on this and will work flawlessly (as far i think)
I will try android pie gsi as someone releases treble enabled twrp for it. It will be on xda as soon people started getting phones
zelendel said:
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
Click to expand...
Click to collapse
Unavailability in US has been the case for almost all Xiaomi phones but the thing is Xiaomi mobiles in XDA has one of the most active development... Many device has recieved unofficial Treble ports and already about 10 or more device has working Android Pie builds... Considering Poco F1's price and specs it shouldn't be a surprise if it ever has the most active development in XDA...
I think many Indian devs are good as any other devs outside. And even if the phone is launching in India only, many devs living outside would also try to get there hands on global version because of how much this phone offers for the price. Also Xiaomi releasing kernel source is a great move to motivate devs and upcoming devs to build custom roms.
bharathulaganathan said:
Unavailability in US has been the case for almost all Xiaomi phones but the thing is Xiaomi mobiles in XDA has one of the most active development... Many device has recieved unofficial Treble ports and already about 10 or more device has working Android Pie builds... Considering Poco F1's price and specs it shouldn't be a surprise if it ever has the most active development in XDA...
Click to expand...
Click to collapse
Getting ports is not development.
Price doesn't mean much in many places.
You are right. It has been and that is why none of the main developers of teams ever get the device.
I still have hope for this oem but we will see. They have a lot to make up for here with developers.
As for the most development. That sadly will belong to the pixel line. Which is what all the top developers get.
zelendel said:
Getting ports is not development.
Price doesn't mean much in many places.
You are right. It has been and that is why none of the main developers of teams ever get the device.
I still have hope for this oem but we will see. They have a lot to make up for here with developers.
As for the most development. That sadly will belong to the pixel line. Which is what all the top developers get.
Click to expand...
Click to collapse
In India, price means a lot... That is why most Apple has such a bad market in India and companies like Xiaomi with value for money products have such a huge market here... There are really skilled Indian Developers who opt to buy such cheap but Good devices...
They themselves stated about bootloader unlocking and custom ROM flashing in the launch event... Xiaomi is one of those very few companies who encourage rooting and stuffs without voiding the warranty...
In My personal experience, Xiaomi devices have very strong community support in XDA, I personally have Redmi 3S, Redmi Note 5 Pro and Redmi 5A... My Friends have a wide range of Redmi devices and They all have a Great custom ROM supply...
Its all from My knowledge and thoughts, just a healthy change of idea...
bharathulaganathan said:
In India, price means a lot... That is why most Apple has such a bad market in India and companies like Xiaomi with value for money products have such a huge market here... There are really skilled Indian Developers who opt to buy such cheap but Good devices...
They themselves stated about bootloader unlocking and custom ROM flashing in the launch event... Xiaomi is one of those very few companies who encourage rooting and stuffs without voiding the warranty...
In My personal experience, Xiaomi devices have very strong community support in XDA, I personally have Redmi 3S, Redmi Note 5 Pro and Redmi 5A... My Friends have a wide range of Redmi devices and They all have a Great custom ROM supply...
Its all from My knowledge and thoughts, just a healthy change of idea...
Click to expand...
Click to collapse
They are doing the same thing OEM have done before. Not to mention that they require to unlock the bootloader is bs.
To be honest, the only reason most devs even get the device is because xda buys it for them. That is why Franco supports the OEM.
I understand that is the way it is in India. That is why I said that it will most likely be developers from there that will need to focus on development. Not to mention that VOLTE is really needed in India and not anywhere else. Nor is it part of open source. So that will take an Indian dev to work on or there will be thousands of posts asking why VOLTE doesnt work. I talked to a few of the lead devs from different teams about the device and I got the same answer from all of them, they have zero interest in the device let alone the OEM. So one of their users will have to get the device and maintain it. Hell most wont even support this oem officially. But then you really cant blame the devs after what this company has done here.
I cant say about the device as I know zero people with the device and there is less then 1% chance that I even know anyone with the device form the OEM. But that could also be part of my job as they are banned along with ZTE and hauwei.
No 9.0 PIE ports for sd845?
I checked some sd845 phones like op6, mix2s, 5z, they dont have any custom roms based on 9.0. And they dont have too much custom roms like redmi note 5 pro or a1 etc. Can somebody guide me ??
I'm just wondering why there's so few official roms and also twrp for the Sofia series of phones? The G7 power has lots but the g8 or g power series has little to no official roms or recoveries.
Probably cause Motorola is releasing new versions all the time and developers can only keep up with so many branches so thats why we have unofficial builds, I guess in the end the phone isnt popular enough and falls behind the on the priority list.