Related
Questions....
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Sent from my XT1254 using Tapatalk
Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM (Stock Based)
Unofficial CM 13
MoKee 6.0
Bliss 6.4
Nexus Experience (NX)
AICP (in the AOKP thread)
(I think that's all of them.) All are CM based except for my Brazilian ROM.
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)
Thanks!
Sent from my XT1254 using Tapatalk
iiWoodstocK said:
Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM
Unofficial CM 13
MoKee 6.0
Bliss 6.4
(I think that's all of them)
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)
Click to expand...
Click to collapse
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Quark Marshmallow ROMs at this point in time allow Verizon VoLTE.
ChazzMatt said:
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Marshmallow ROMs give Verizon VoLTE.
Click to expand...
Click to collapse
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)
iiWoodstocK said:
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)
Click to expand...
Click to collapse
Right. I left off AICP ROM because
1) it doesn't have Ambient Display (which makes it a non-starter for most), and
2) the ROM maintainer (who also has Bliss and AOKP) isn't really actively supporting it with a separate thread like the other two.
It may be an interesting "project" but without Ambient Display (or the Moto Display in your stock Marshmallow ROM) what unique feature does AICP ROM have the other 8 Marshmallow ROMs do not? (For instance the Quark Resurrection Remix and Bliss ROMs have the ability to use most Moto apps. Your own stock-based ROM can use all Moto apps by default. AICP does not have that functionality.) And if you don't like Ambient Display/Moto Display, you can just turn it off on any of those 8 ROMs; you don't need to install a ROM with that feature lacking.
arizonaomnia said:
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Click to expand...
Click to collapse
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
@iiWoodstocK Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks, since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware. (Verizon has not released the XT1254 Motorola Marshmallow ROM yet, and may never do so.)
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.
ChazzMatt said:
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
his Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware.
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.
Click to expand...
Click to collapse
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.
iiWoodstocK said:
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.
Click to expand...
Click to collapse
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
ChazzMatt said:
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
Click to expand...
Click to collapse
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.
koftheworld said:
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.
Click to expand...
Click to collapse
On various devices, I can't find any for Verizon with VoLTE that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.
ChazzMatt said:
On various devices, I can't find any that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.
Click to expand...
Click to collapse
Hopeful bb can find the right info from the logs that were provided. Would a huge win for those of us with Verizon as a network.
I *think* I've read Victara CM has Verizon VoLTE. Not 100% sure...
ChazzMatt said:
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
Click to expand...
Click to collapse
Wow, I used Dr DOS!!!!
You're a power user. Can the Sony Xperia X keep up? Rate this thread to express how "healthy" the development scene is for the Sony Xperia X. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
really bad comparing to other devices
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Gazatus said:
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Click to expand...
Click to collapse
lineageos? is there any?
coconutxyz said:
lineageos? is there any?
Click to expand...
Click to collapse
LINEAGE ?????
Where is?
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Dev community pretty bad as of right now... There's a lot of hope but still years behind dev community behind motorola/oneplus/etc
mase76 said:
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Click to expand...
Click to collapse
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Did you ever try SFOS? The usage is much cooler than
Android. And there will be an runtime env for Android apps.
I don't have a problem to pay for good things. But nobody
forces you to buy an Xperia X or pay for an alternative OS.
And you know, that an Android with Google services isn't
as free as you think?
Ok, it is getting offtopic.
If we'll could talk with Xiaomi Redmi Note 3 dev community, maybe we have other expectations with the development for this and Xperia X Compact device(s).
BTW, I been wanted show you that: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605
Regards.
Very bad compared to my 3 years old Asus Zenfone
This even getting Oreo
https://forum.xda-developers.com/zenfone-5/development/rom-aosp-oreo-tank0412-t3663733
Their Snapdragon 650 is a good SoC for Development, more, searching fix some errors that Sony let...
The problem is our own Dev here, is very low...
IDK why.
We'll should to port some things from Xiaomi's Phones (Xiaomi Redmi Note 3 Snapdragon and Xiaomi Mi Max), or, fuse our Dev with them Dev for making "bigger" to Snapdragon 650 SoC, at least.
SahilCrazy said:
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Click to expand...
Click to collapse
u know that jolla give you the option to compile sailfish x for yourself right? And you know that they need to make money because they paid sony for licenses etc. and have taxes and coworker etc.? It's not like that jolla is a one-man show in a cellar like some others here like to think or are by themself
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
cyanides13 said:
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
Click to expand...
Click to collapse
Now, is the "most seller" together to the Xiaomi A1.
With this, maybe we could see something for make to develop even more for this SoC.
Community development is bad, but not the worst. Unfortunately, "Bootloader unlock allowed" is "No" on my phone so I can't use anything community developed/maintained regardless.
IMO it's alright. We're still under cover of Sony's AOSP and various official projects (Omni and PA), and outside of that there are Unofficial LOS and Treble by Chippa_ahttps://forum.xda-developers.com/member.php?u=6994234 and Sjll respectively. Some of those ROMs are usable as daily driver.
Props to any and all developers who have been keeping this phone alive.
So this is a post for just making people realise some of the things going on in the Samsung Galaxy Tab A development forum (specifically the custom Rom development). So let's get right into the thing. I believe custom Rom should be focusing on bringing newness to old devices. Of course and some features are not available in New devices, and custom Rom and debloated roms help fill the gap ( we all know how heavily modded Samsung firmware is).
However recently there is a trend for DEVELOPERS to make custom roms for recently released devices ( SM-T580, SM-T280) . While the old 2015 models and others have no roms yet. I did hear that someone was making a unified Rom for some of these models months ago. I'm not saying that there shouldn't be any roms for new models . But there is an overcrowding in the market with custom roms for these devices and also with very little difference between these roms. Imagine this like there are a lot of products for one group of people and the rest get no products at all!
So this is my petition. Can just some of you show a bit love for these devices? If enough of you respond to this maybe there will be a positive change! That's all I want . I want everyone to pass this message around. Thanks for the help. And thank you Developers who make custom roms for any device because I know it's a hard job and you are doing this for free. :good:
Peace
P.S: This is my first post. I know I did some things wrong. So PLEASE don't be too critical about this.
Hint, Hint!! Devs make mods for devices they OWN. They aren't in it to support Samsung. They aren't in it to be charitable. They are in it because they enjoy doing what they do and want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have.
edit: There is also the fact that "custom" ROMs, like RR, Extremely and Ultra, are all just modifications of the STOCK ROM from Samsung. So, if Samsung hasn't produced a new ROM for an older device, then there is nothing to modify. The exception to that are the ROMs based on the LineageOS. But, again, these are based on adaptions from other devices that use the same SoC. So, if the LineageOS devs haven't produced one for the SoCs in older devices, you won't see one for your older Tab A.
Then why do they provide support for their releases. I get the thing you said about how roms a modified. But I dont think they make it just for themselves. If that were the case the would not be any "community" and XDA IS a well-knit community. Developers like @ashyx and @JazzPresso provide and support people with their mods and stuff. So the "want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have. " part I don't get.
Sent from my Samsung SM-T355 using XDA Labs
How are they supposed to debug problems when they no longer have a device to use for testing? What's not to get?
But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return
remarkablecow913 said:
But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return
Click to expand...
Click to collapse
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.
If only someone could port treble then the tablet would be sorted. But I doubt that's ever going to happen.
lewmur said:
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.
Click to expand...
Click to collapse
Anytime I tried twrp error was just because of device name or something of that sort. Is there a way of kinda forcing the flash? I've never tried it through other way. Thanks for advice
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Hello jcole20
That would be awesome if some devs started doing something with the RP2! If I had the knowledge, I would!! I've had the RP2 since June of this year. I had some issues with it at first but they have been worked out. I really like the phone and it would be cool to see some devs show the RP2 some love lol. Hopefully you can get something started! Take care!
Dennis
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
I am sure people would love to see some device specific development. I have read that since the release of project treble most people just flash the system image from other roms. I specifically would love to see a stockish rom so I don't loose chroma but still get updated security patches.
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Krazy_Calvin said:
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Click to expand...
Click to collapse
Most functionalities work on Pie GSIs out-of-box (you need to manually install ims.apk in order to receive SMS while on LTE, see relevant threads here, or look for it on some GSI threads such as Havoc 2.9). exFAT also works on supported GSI (with arter97's kernel), while it's not supported on stock. The only problems I have so far are bluetooth-related, and also the inability to set SELinux to permissive (not sure which might be the real cause as arter97 stated the SELinux could be permissive).
Bluetooth media audio doesn't work at all on GSI, partly due to the crippling overlays (which prevents aptX from working, and probably some other limitations). Phone calls work with a bluetooth headset, but for some reasons I couldn't properly route phone calls to my Huawei Watch 2 (which means I always have to take the call from my phone directly).
Given the mostly positive result with numerous GSIs (and that some users are happy with stock ROM, or stock-based ROM modifications), active ROM developments for the device itself doesn't seem to be at a high priority (as some might be able to contribute patches for this device to their favorite GSI instead)...
I'm currently working on my own build of LOS. I haven't seen to much active development either I'm new to rom building but looks like we could use all the help we can get!
I think the only active dev we have for this phone is Arter97's kernel and people tinkering with GSIs to get them working as they should. I wish there was more being done with the stock ROM because I like a lot of it's features, but am having a hard time dealing with it's overall instability. I'd be happy to help develop or test in whatever way I can, though.
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
Yeah, it’s definitely just total lack of interest from other devs. We even have a guy with a prototype Razer Phone 2 with an intact DRM partition and unlocked bootloader (Allowing Netflix HD and Vudu HDX) but we couldn’t even pay anyone to try to port it.
I think if we had a fully working AOSP tree that it would possibly bring other devs into the scene. Who knows though, it has never been a popular device despite how great it is.
LSS4181 said:
Most functionalities work on Pie GSIs out-of-box.
Click to expand...
Click to collapse
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
EMJI79 said:
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
Click to expand...
Click to collapse
A stock Android 10 (which means a stock vendor image for Android 10) is not necessarily required to have a usable Android 10 ROM (though it may speed up the development to some extent, if it does have one), but for GSI, having a stock Android 10 vendor image can be better (currently it's a hit-or-miss on existing Android 10 GSIs).
Another device that I have, Google Pixel C, never had stock Android 9 (so never had stock vendor images for Android 9, only for up to Android 8.1), but custom Android 9 ROMs are already available (thanks to followmsi's efforts) and are working well. For Android 9 ROMs, the build system builds new vendor images along with system image.
It's just whether we're going to see our device's trees being made possible, so we can start from there to develop our own custom ROMs. The existing materials might be a good starting point in making trees.
- Working with proprietary blobs (from Lineage)
- arter97's kernel (can be useful for making a kernel tree, though one can also consider using stock kernel source as a base)
- Razer factory images and kernel sources (for studying stock ROM/kernel details, and extracting necessary system and vendor blobs)
If you can port LineageOS to this device, great!
I don't understand why people aren't flocking to this device. I came from the LG G6 that probably will be stuck on Oreo forever that is way more popular. The RP2 is cheap, has killer specs + a micro SD card slot + a newer version of Android. Should be a developers dream, you would think. *shrug*
Not sure if anyone's active on this device at present. With RP2's 9.0 MR2 available on the official factory images page the latest proprietary blobs (as well as stock kernel source) are now publicly accessible.
Actually arter97 once mentioned that his RP2 kernel is almost inline with his OP6 kernel (which is also sdm845 and shares some similarities), so it's possible that OP6 (enchilada) trees may be a good starting point, but I'm not sure if any configurations are needed to keep 120Hz working as high refresh rate is relatively uncommon.
My time is very limited so I won't be able to dedicate too much time to experiment on this. At present most functionalities work fine with GSI (including Bluetooth, although tricky and aptX still not working).
IDK how relevant this is anymore but as a new razor phone 2 user to be soon I have been keeping up and it seems that @f(x)THaxxorX could be a possible candidate of what you're looking for I've been keeping up with development on the phone seems like he is doing pretty well even if we get patched gsi which properly work is better than nothing.
i did find another AOSP rom the other day looking to see if i could compile a 5.10 kernel for my phone and came across this rom
CalyxOS
calyxos.org
it is focused on security and keeping google spying off your phone.
why these developers like google pixel experience, calyxos and other AOSP roms don't advertise there roms here on xda i will never know. you would think they want more people to appreciate their work. than be hidden on some website that no one will ever find.
rchris494 said:
i did find another AOSP rom the other day looking to see if i could compile a 5.10 kernel for my phone and came across this rom
CalyxOS
calyxos.org
it is focused on security and keeping google spying off your phone.
why these developers like google pixel experience, calyxos and other AOSP roms don't advertise there roms here on xda i will never know. you would think they want more people to appreciate their work. than be hidden on some website that no one will ever find.
Click to expand...
Click to collapse
To either save someone a headache or possibly give them one if they want to help confirm my experience...I remember hearing when they dropped their A12 beta a month or so ago but forgot about it (personally it seems easier to take an everyday ROM and make it more secure, rather than take a niche security one and make it more enjoyable). Between waiting on LOS19 to finally drop & A12QPR3 giving me a pre-WiFi phone experience, I was gonna give it an honest few week review because I liked their A11/what they stand for.
A very long story kinda short, boot fails every single time after flashing(in recovery) nijel8's TWRP. Any one else? Certain per ROM reasons maybe I caused(kept bootloader unlocked, rooted, basically everything their site said don't do for privacy/security concerns, etc.)??