Related
According to Android Central, the real reason behind OP's merging of the OxygenOS and HydrogenOS that has been happening in the past weeks is due to a mass exodus of developers due to problems within the company. Problems such as long working hours and a lack of a common goal in the leadership. The merger was advertised to be in "a step in the right direction" but it looks like there's a lot issues at OnePlus that forced them to do this. There's also reports that the developers whose idea of a Nexus-like OS for the phones is no longer there and that more people will leave after the merger of OOS and HydrogenOS is complete.
This leaves me worried that we'll be left with old kernel and other sources to build fully working custom ROMs and that people who prefer stock will be left waiting for bug fixes and new updates for much longer.
The article is below.
http://www.androidcentral.com/onepl...l&utm_source=facebook.com&utm_campaign=buffer
My OP3 is on the way and now I'm worried too.
I'm definitely worried about the article. No human resources means no development... And to find very quick new talented people and to get them familiar with the architecture and structure of hard- and software, phew, is not easy.
Sounds like N for OP3 far far away
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
diegodm said:
My OP3 is on the way and now I'm worried too.
Click to expand...
Click to collapse
Don't be worried, i read somewhere both teams will keep UI close to Stock Android, or same as OOS, a separate launcher type stuff to keep H2OS along with it. So i think they know, Stock Android is one of the main reason why they sell phone, even now giving competition to Nexus phones.
Without stock, they will be at best like Haewei/Oppo or other Chinese brands.
But you raised an important question, there is not a single stable/bug free ROM, strangely/sadly or as good as OOS it self. Even the great official CM13 is in nightly stage. After so many months, people here are only installing to ROMS to be beta testers?
usmanxhmed said:
Don't be worried, i read somewhere both teams will keep UI close to Stock Android, or same as OOS, a separate launcher type stuff to keep H2OS along with it. So i think they know, Stock Android is one of the main reason why they sell phone, even now giving competition to Nexus phones.
Without stock, they will be at best like Haewei/Oppo or other Chinese brands.
But you raised an important question, there is not a single stable/bug free ROM, strangely/sadly or as good as OOS it self. Even the great official CM13 is in nightly stage. After so many months, people here are only installing to ROMS to be beta testers?
Click to expand...
Click to collapse
I really hope so... If I wanted Chinese interface I would have bought Mi5.
I just hope that the changes at Cyanogen don't affect CyanogenMod too much.
It's not all doom and gloom they could hire what's left of Cyanogenmod
Dear OnePlus 3t owners,
Is it sensible to buy a new OP3T after OP decided to kill updates post-O?
On this device, easy root, no updates but plenty of community support.
On others (S8, XZ Premium, other mainstream flagships), loss of features with root, somewhat more updates with less community support.
Please help me take my decision, and any and all help is greatly appreciated!
It depends if you want a phone to play around and mod or you want a phone to have longer updates although longer updates are not a guarantee in any brand even Google promises updates for 2 years only. 3t is still a pretty good device and I think we'll have good dev support for atleast a couple of years
Sent from my OnePlus3T using XDA Labs
No update ? Hmm, don't know where you see this, OpenBeta 13 has just been release today.
Personally, I bought the OnePlus 3T like one week ago for 350e on Ebay, very happy with with.
Before it, I bought a OnePlus 5 day one, and, well, if I'm here today, it's because I was very disappointed (*cough* Jelly Effect *cough* ), and I bought the OnePlus 3T because I need a new device right now: I prepare a trip in South Korea, and need a new device to replace the time bomb OnePlus 2 (sorry about my life topic).
I share the idea about the fact that the OnePlus 3T was the true Flagship Killer: low price for very good specs.
You can see that the device is still in top 3 devices on XDA (behind Samsung Galaxy S8/S8+ and LG G6), and for me, it's an indicator that the OnePlus 3T still has a bright future.
So yeah, OnePlus won't update the OnePlus 3T after Android O (but still security update tho), but he, we are on XDA, so plenty of custom ROMs available!
After all, I can't either ""force"" you to buy or not the OnePlus 3T. It depends on multiple points
-How many you want to put in your phone ?
-What is a good smartphone for you ?
-Do you care about officials updates of custom ROMs is ok for you ?
1. No updates: I actually meant "no major version updates".
2. So you have bought the 5 and saw that the 3T was better in comparison?
3. Are custom ROMs stable as stock on this device? (My 1st OP device, hope ROMs are as stable as stock to the contrary of Samsung)
4. Is the camera on custom ROMs any good (as in decent) without camera blobs from OnePlus?
Thanks for your advice! I'm actually biased towards buying the device but I have had my reservations
Well, I'm a tinkerer but I really prefer more updates as I do prefer longevity (3-4 years of college, not enough $$$ to spend on phones). Thank you a lot!
I don't think it'll matter. Android O will be a nice send off and I think said that they'll provide security updates also. The community will support this phone for many android revisions and groups/people like PA or Sultan got the same camera quality on their AOSP roms
Also, you said that you bought the 3T to replace your "time-bomb" OP2. How is the 2 a time bomb exactly? And could the 3T become one too?
I'm content with the device on O but as soon as P rolls out a problem arises. Community ROMs are not exactly stable (coming from Samsung, no idea w/ OP3T though) and I've read somewhere that PA and/or Sultan received the blobs from OP through bribery or something ... What do you think?
So you have bought the 5 and saw that the 3T was better in comparison?
Click to expand...
Click to collapse
Jelly Effect is a deal breaker for me. Search for it on internet, you will see.
Are custom ROMs stable as stock on this device?
Click to expand...
Click to collapse
For now, I don't know. I just flash a custom kernel on my device, but still under OxygenOS for now.
Is the camera on custom ROMs any good (as in decent) without camera blobs from OnePlus?
Click to expand...
Click to collapse
As I said, I don't know. But some recognized devs build ROMs which camera which seems to be as good as stock one (such as SultanXDA's ROM or ParanoidAndroid)
Also, you said that you bought the 3T to replace your "time-bomb" OP2. How is the 2 a time bomb exactly? And could the 3T become one too?
Click to expand...
Click to collapse
The OnePlus 2 was produced with the Snapdragon 810, which is, let's be honest, a sh*t. My user experience with it was pretty bad. Also, I don't know if you saw, but the Nexus 6P (which also has the Snapdragon 810) is victims of problems with this processor: actually, some users have a phone which can't even boot anymore. A user find a solution, but actually, the phone now uses 4 cores (the little cluster) instead of 8 (little + big cluster): I don't want the OnePlus 2 to ends like this, so I bought a new phone, just to be sure.
Aaaaand I f*cked up my answer. Of course, this posts contains answer to your questions @WaseemAlkurdi
Custom roms are far more stable on the 3t then on Samsung devices. Less hacking needed.
Updates are kinda over rated at this point. With the 3t you can just build it yourself. Though I would avoid Los based or PA based roms. Those tend to have the most issues with things like instability.
Think of it this way: would you buy this phone and use it as is, or would you out a custom ROM on it?
It might not get any updates from UP after O, but it's gonna get at least 3 more years of support from Lineage and others.
There are a plethora of "stable" custom built ROMs by several very talented developers.
To say that community ROMs are not stable is an EXTREMELY uninformed comment.
I've been running some form of a custom ROM for the past 7 years over a a multitude of phones following well known developers that in my opinion and experience put out better device software than the factory.
If you do choose the OP3T, you'll not be disappointed as it's a quality device with excellent community support.
Like could I build "OxygenOS P" myself?
And if LOS and PA ROMs aren't stable, is AOSP so? And that makes for a tradeoff for camera quality, as an earlier comment said that camera is the best on PA and Sultan (Sultan's being LOS based AFAIK)
@giant22000
Seems like it's going to be the OnePlus 3t after all, and what remains to be done is convincing my dad that an unknown China OEM (in local market's view - not our view) can make solid hardware.
"To say that community ROMs are not stable is an EXTREMELY uninformed comment."
This is relative. Coming from various Samsung devices, namely the Galaxy Grand 2 and the Galaxy Star (the crappiest device known to mankind) and servicing others including flagship models, it does happen that custom ROMs are, to say the best, variable in stability, ranging from crappiest (CM on the Galaxy S Duos and on the Star) to semi-stable (the stuff on high-end phones.
@ast00
I am a tinkerer by nature, no Android phone is mine unless the bootloader is unlocked, custom ROM, kernel, overclock, and later on, development.
I am only concerned about official updates as this may mean eventually being deserted by the community. Is this the case here?
@casual_kikoo
Thanks for your detailed answers!
Yes AOSP tend to be more stable then the other two. Just look at the thread and you will see issues with bootloops and other things. Yet AOSP based roms do not suffer from this.
The camera is good enough no matter the range. I tested both and to be honest it made little difference.
No you are not gonna build Oxygen OS as it is closed source but then again why would you want to?
Stability, mate. Heard that OOS is the most stable, then comes AOSP, then comes LOS.
And if it were possible to build OOS, the update issue would be fixed of course. But alas, it isn't possible, as you said.
No. Most ROMs run on the 3 and the 3T. I mean you flash the same zip for both phones.
This is good because our community is the size of 2 phone's communities. You will have plenty of support later on.
Take nexus 5 as example, its still getting regular rom updates such as PA or lineage, this device will be no different.. it will receive android updates from xda community for a long time
I only ask the above because we have one unofficial ROM and zero modified stock ROMs and nothing to flash in case of emergencies, it's off putting for me to modify anything as I've nothing on my memory to flash should I need it.
Not being needy, just concerned that this flagship isn't getting the treatment it deserves
Well there's reasons for that. Phone just came out not long ago, not released in the US, and in a strange move Huawei have said in two months bootloader unlocking won't officially be supported basically killing development for this phone unfortunately. I wouldn't expect any major developers moving their ROM's to us.
Giraff3 said:
Well there's reasons for that. Phone just came out not long ago, not released in the US, and in a strange move Huawei have said in two months bootloader unlocking won't officially be supported basically killing development for this phone unfortunately. I wouldn't expect any major developers moving their ROM's to us.
Click to expand...
Click to collapse
Still find it odd, firstly with every flagship I've had and as you can see from my signature ( if you're viewing this on a pc ) I've had quite a few.
I have never once seen, after over a months release only one non official ROM available for a phone, the Sony z1 and the note 4 being the worst amongst every device I've had, the OnePlus and the HTC sensation being the best with the most.
Secondly there is a huge chance that Huawei will overturn their decision to allow bootloader unlocking, not only that but id have imagined that with today's developers whether or not Huawei allows unlocking, we would still have a hack around it S-Off for HTC devices springs to mind.
The US not being involved is a loss but at the same time, some of the best developers I've had the chance to communicate with here on XDA have been from all over the world, not too many from the US iirc so I'm not buying that.
I'm not bashing here but just a little concerned that not a single ROM had been released, I think it's a terribly sign for such a device to have nothing.
I've even been looking into making my own ROM myself, will know over the next few weeks if I can make that a reality or not, but as it stands I don't even have a starting base and the difference between devices unless debranded is quite stark and would probably end up bricking devices.
Such a shame, I sincerely hope it changes but I'm holding less and less hope as time goes on.
PS: I'm not sure but wasn't treble meant to be able to be used on this device too??
There are plenty of treble based ROMs and most of them should work fine.: https://forum.xda-developers.com/project-treble
Just flash them via TWRP. Otherwise Huawei phones have traditionally never had much independent ROM development.
mrabcx said:
There are plenty of treble based ROMs and most of them should work fine.: https://forum.xda-developers.com/project-treble
Just flash them via TWRP. Otherwise Huawei phones have traditionally never had much independent ROM development.
Click to expand...
Click to collapse
Oh mate??? You might have just become my hero, I know literally nothing about project treble other than the fact that it may help with ROM flashing, but again have never done it..
Coming from the OnePlus 5 I never needed it.
Have you flashed any treble ROMs on this device ?
If you don't mind can I just ask.
If I flash something, how can I get back to my normal ROM if it becomes unbootable?
Update: @mrabcx
I tried to install a treble ROM, made a nand back up first and it failed to boot, restored nand and it's now back up and running.
I think we need a treble compatible twrp, does it even exist for the p20 pro??
I don't have P20 myself so can't answer that, but the phone is very similar to other Huawei phones such as Mate 10 and should in theory be able to boot Treble ROMs. I guess there could be some issues with clearing cache/wiping data etc. If you can post the details in the Treble ROM sections then I'm sure someone there will be able to help you out.
mrabcx said:
I don't have P20 myself so can't answer that, but the phone is very similar to other Huawei phones such as Mate 10 and should in theory be able to boot Treble ROMs. I guess there could be some issues with clearing cache/wiping data etc. If you can post the details in the Treble ROM sections then I'm sure someone there will be able to help you out.
Click to expand...
Click to collapse
Yep I was under that impression myself, then I tried every single ROM there is in the treble section, not a single one booted.
Not only that but everyone there is trying to get it working on their phones so no one really cares for anyone else.
Not good.
Tried via fastboot as our twrp doesn't work.
Tried via twrp and the sand issue.
Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
peanutpajamas said:
Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Click to expand...
Click to collapse
you can text if you send a screenshot or pic attached to it then the text goes through no matter what messaging app u use
bradhoschar said:
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
Click to expand...
Click to collapse
I thought that was just the links..
My thoughts are this sucks and op should be ashamed of themselves.they released a backport
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
superiscch said:
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
As the name suggests, this build of Android Q is best suited for developers and early adopters. As it is still in an early stage of development. That said, we do not recommend flashing this ROM if you have little to no experience in software development or flashing custom ROMs. Proceed at your own RISK!
Click to expand...
Click to collapse
superiscch said:
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
I think your right to a certain extent, but I also feel like lately OnePlus hasn't been doing what they have become known for, oneplus users want fast updates to try out the latest of Android.
this build while intended for development was made with very little thought, most other OEMs on the list actually made it useable, take essential for example, yes there are a few bugs but it can send a text and doesn't crash when you click on auto brightness. Even though it was for "devs".
OnePlus could have definitely done a better job at this, very dissatisfied.
SpasilliumNexus said:
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
Click to expand...
Click to collapse
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
fullofhell said:
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
Click to expand...
Click to collapse
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
If anyone want to see a video or a quick look than check this
https://youtu.be/Yhw6463pTPg
-snip-
PatrickLoewer said:
Has someone problems going back to custom roms?
I downgraded to the Pie Image linked in the OnePlus Android Q official post. This is working fine, i can boot and flash TWRP as well, but as soon as i install any room i go straight back to "Qualcom CrashDump Mode".
Tried the original fastboot partitions from "rom-stock-fastboot-roms-oneplus-6t" aswell, those are working fine for me as well. But soon as i flash any custom rom (tried 3 different ones) i go straight into the "Qualcom CrashDump Mode" (fastboot is no longer working after that so i have to use the MSM Tool to restore the phone).
Tried dirty flashing or a complete clean flash (wiping all partitions except Internal Storage) both result in the same Qualcom Crash screen.
Using the MSM Tool gets me a working Pie everytime, also using the original fastboot rooms works as well, it's only custom roms .... (tried with and without flashing magisk/opengapps)
Edit: International Version, no T-Mobile or McLaren Edition
Click to expand...
Click to collapse
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
fullofhell said:
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
Click to expand...
Click to collapse
Was not the problem, but the MSM Tool didn't worked with the version i had.
indian84 said:
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
Click to expand...
Click to collapse
Cute attempt at the assumption, but you're far from getting that one right. Try again.
SpasilliumNexus said:
Cute attempt at the assumption, but you're far from getting that one right. Try again.
Click to expand...
Click to collapse
Burnnnnn
fullofhell said:
--WoT--
Click to expand...
Click to collapse
No matter how buggy or broken they are, they are meant for developers to adapt software and hardware on them before final builds are out to the general public. Not for randoms to treat them as finals, as few here and a lot on the OP forums have done.
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Xpiatio said:
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Click to expand...
Click to collapse
Fairly sure you have to wipe and not choose "secure startup" (or similar) in the set up. That feature (encryption) is not working currently.
They could make a PRE-Alpha build, say DO NOT INSTALL THIS, and zillions of lDIOTS would download it because they want the latest update, no matter what, THEN, will get on here, OP's website and other places to complain about it.
It's like these clowns hanging out windows, rail cars and what not to get a selfie so they can get "likes"....lDIOTS
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.