Related
Update
Moto hasn't enabled treble in Indian Moto X4 (XT1900-2)
Many OEM like Nokia, OnePlus etc are disabling Project Treble on their devices in Oreo updating stating that Treble requires re-partitioning of internal storage which if done via OTA has a high probability of bricking the phone.
https://m.gsmarena.com/current_nokia_phones_will_not_support_project_treble-news-28590.php
https://www.gsmarena.com/oneplus_ex...ject_treble_on_current_devices-news-28616.php
So will Moto X4 get Treble in Oreo Update? I'm afraid it might not get it.
Is Project Treble linked with the A/B Partitions ? If yes, we have already these partitions on our Moto X4 (non Android One Version) so I hope it will be compatible...
Taolefeng said:
Is Project Treble linked with the A/B Partitions ? If yes, we have already these partitions on our Moto X4 (non Android One Version) so I hope it will be compatible...
Click to expand...
Click to collapse
Nobody knows for sure yet. We'll have to wait and see when Oreo drops.
x4 was launched quite a bit after oreo was already officially released, and it's a mid-end phone by Motorola (they even give moto g4 oreo update, even though it's because they feel pressured due to previous mistaken promise, they still said they 'll go through with it...) .
It could definitely increase sales of the moto x4 and make it more able to compete with devices that will be released on Oreo in the next months coming. It would mean that customers will get updates as frequently as other devices released on Oreo,
Moto x4 retail version is released with A/B partitions just like Pixel 2XL. Seems like A/B partitioning is essential for Treble, which devices like 1+5 lack indeed.
So these are 5 factors which could contribute to treble being activated when Oreo comes to the x4 but treble could just as likely not be on it...
There are phones that got released way before the x4 that did pull it off, so it's possible.
hpgramani said:
Many OEM like Nokia, OnePlus etc are disabling Project Treble on their devices in Oreo updating stating that Treble requires re-partitioning of internal storage which if done via OTA has a high probability of bricking the phone.
https://m.gsmarena.com/current_nokia_phones_will_not_support_project_treble-news-28590.php
https://www.gsmarena.com/oneplus_ex...ject_treble_on_current_devices-news-28616.php
So will Moto X4 get Treble in Oreo Update? I'm afraid it might not get it.
Click to expand...
Click to collapse
I think motoX4 will get Treble update as having somewhat above average knowledge in smartphones, I noticed that i'm getting 44gb of space left in my 64gb variant. and moto having almost stock android without tones of blootwares. I think i should get somewhat 50-52 gb of onboard storage. And as Project Treble needs another partition may be that's where the extra space went.
Its all just my way of connecting dots and looking at the big picture. I hope i'm not wrong and u guys will agree:angel::angel:
Off topic but has anyone seen any news about the oreo update for Moto devices? I'm seeing on the tech blogs that other devices receiving betas. Helk,the HTC u life on T-Mobile is actually receiving oreo right now. I saw somewhere that Moto said promised oreo by the end of the year and no word.
Sent from my [device_name] using XDA-Developers Legacy app
aakarshmodi said:
I think motoX4 will get Treble update as having somewhat above average knowledge in smartphones, I noticed that i'm getting 44gb of space left in my 64gb variant. and moto having almost stock android without tones of blootwares. I think i should get somewhat 50-52 gb of onboard storage. And as Project Treble needs another partition may be that's where the extra space went.
Its all just my way of connecting dots and looking at the big picture. I hope i'm not wrong and u guys will agree:angel::angel:
Click to expand...
Click to collapse
our nougat has A/B partitions already, they have nothing to do with treble... that's where all the space went. z2 is not getting it, and we probably are neither..... as someone with above average knowledge, yours is pretty lacking
bombaglad said:
our nougat has A/B partitions already, they have nothing to do with treble... that's where all the space went. z2 is not getting it, and we probably are neither..... as someone with above average knowledge, yours is pretty lacking
Click to expand...
Click to collapse
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best
aakarshmodi said:
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best
Click to expand...
Click to collapse
That's not true at all. The reason for A/B partitions is to allow for seamless background updates, nothing to do with Treble. They were implemented on Pixel 1s before Oreo and Treble even existed.
Moto is under zero obligation to implement Treble on the X4... Unless Google really asks them to as part of the Android One program. Which is possible. I'd say it's 50/50 if we get it.
FanDroid09 said:
That's not true at all. The reason for A/B partitions is to allow for seamless background updates, nothing to do with Treble. They were implemented on Pixel 1s before Oreo and Treble even existed.
Moto is under zero obligation to implement Treble on the X4... Unless Google really asks them to as part of the Android One program. Which is possible. I'd say it's 50/50 if we get it.
Click to expand...
Click to collapse
the question is, whether google will treat a1 devices like pixels in this regard
funkymonkey_01 said:
Off topic but has anyone seen any news about the oreo update for Moto devices? I'm seeing on the tech blogs that other devices receiving betas. Helk,the HTC u life on T-Mobile is actually receiving oreo right now. I saw somewhere that Moto said promised oreo by the end of the year and no word.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The Android one edition starts recieving Oreo.
https://www.phonearena.com/news/Mot...arts-getting-Android-8.0-Oreo-update_id101000
So those who have Android one edition can check whether project treble is enabled or not
any updates regardes treble?
https://forum.xda-developers.com/showpost.php?p=74940357&postcount=17
Looks like it's not enabled.
LIONS1 said:
any updates regardes treble?
Click to expand...
Click to collapse
no treble support for mx4 even after oreo update
Sagar_1401 said:
no treble support for mx4 even after oreo update
Click to expand...
Click to collapse
same here for MI A1 thats disappointment only HTC U11 Life has it
aakarshmodi said:
We will get treble feature .... Apart from that there is no reason to give a/b partition. As it was also rumored in early 2017 for motox4. Anyways let's wait n hope for the best
Click to expand...
Click to collapse
we're not getting it, told you so
Anyone grab OTA zip yet? Would love to take a peek.
As for treble...wonder if proprietary vendor/HALs will ever pop up anywhere (assuming they were ever created). Seems that is all that is needed to implement it on an otherwise capable device.
bombaglad said:
we're not getting it, told you so
Click to expand...
Click to collapse
Not having it enabled yet isn't necessarily a sign that it isn't coming. The question is still is it partitioned TO support it, even if not using it yet. it was the repartitioning that other vendors claimed made it nearly impossible to support older devices, so if they have prepared and partitioned it cleanly, then there is still hope. It isn't a good sign though.
ebrandsberg said:
Not having it enabled yet isn't necessarily a sign that it isn't coming. The question is still is it partitioned TO support it, even if not using it yet. it was the repartitioning that other vendors claimed made it nearly impossible to support older devices, so if they have prepared and partitioned it cleanly, then there is still hope. It isn't a good sign though.
Click to expand...
Click to collapse
yes it is, stop waking false hopes in people.. the current A/B partitioning scheme has nothing to do with treble, all would still have to be repartitioned again for treble to be implemented... if they wanted to implement it, they would've done it already.... why would they even make two separate oreo builds, one without treble and later one with it?
also, i hate how everyone talks about "enabling" and "not enabling" treble... it's not a flag in build.prop or whatever that you can just enable, which makes treble magically work! it's a huge structural change on a pretty damn deep level. so please, let's talk about implementing, rather than enabling treble
bombaglad said:
yes it is, stop waking false hopes in people.. the current A/B partitioning scheme has nothing to do with treble, all would still have to be repartitioned again for treble to be implemented... if they wanted to implement it, they would've done it already.... why would they even make two separate oreo builds, one without treble and later one with it?
also, i hate how everyone talks about "enabling" and "not enabling" treble... it's not a flag in build.prop or whatever that you can just enable, which makes treble magically work! it's a huge structural change on a pretty damn deep level. so please, let's talk about implementing, rather than enabling treble
Click to expand...
Click to collapse
It is about being able to load the proper vendor modules into the proper places. The key questions are a) are the places ready to receive the vendor modules when ready and b) when will the vendor modules be ready. You can easily have a Treble partition structure without the code to put in it. Why else would there be so many partitions vs. other phones on the X4? I'm not saying treble WILL ever be enabled, but there can be very good reasons (like lack of Qualcomm Treble modules for the hardware) why the phone hasn't had a treble enabled build yet.
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.
Hello,
Anyone try a gsi rom on the OP10 Pro ?
Jordanrnd said:
Hello,
Anyone try a gsi rom on the OP10 Pro ?
Click to expand...
Click to collapse
where did you find it?
Hkifuos said:
where did you find it?
Click to expand...
Click to collapse
I check with treble app and choose all rom available on gsi github
I have yet to try it but the phh gsi aosp one has fixes for booting snapdragon 8 gen 1.
Search the A/B ROMs on xda... There's a pixel experience one that looks promising
Way back...
GSIs on OP10Pro
With an unlocked BL, flash an ARM64 AB GSI within fastbootd, format userdata from recovery, reboot, profit. vbmeta should only be needed if you do Magisk. Google GSIs simply boot; PHH-based ones (which are ones people will actually want to use)...
forum.xda-developers.com
Not a good experience though, I can't quite get the overlay and 2K resolution to work consistently, let alone common bugs like VoLTE and FP.
AndyYan said:
Way back...
GSIs on OP10Pro
With an unlocked BL, flash an ARM64 AB GSI within fastbootd, format userdata from recovery, reboot, profit. vbmeta should only be needed if you do Magisk. Google GSIs simply boot; PHH-based ones (which are ones people will actually want to use)...
forum.xda-developers.com
Not a good experience though, I can't quite get the overlay and 2K resolution to work consistently, let alone common bugs like VoLTE and FP.
Click to expand...
Click to collapse
Yea I think this is the problem with treble, the concept was nice but each device needs it's own support, having one image for every device is a problem in itself
dladz said:
Yea I think this is the problem with treble, the concept was nice but each device needs it's own support, having one image for every device is a problem in itself
Click to expand...
Click to collapse
This being a OnePlus "x Pro" flagship, I'm sure it'll get device-specific ROMs shortly. Me working with PHH to boot on it is more to clear the way for other more obscure SM8450 devices.
AndyYan said:
This being a OnePlus "x Pro" flagship, I'm sure it'll get device-specific ROMs shortly. Me working with PHH to boot on it is more to clear the way for other more obscure SM8450 devices.
Click to expand...
Click to collapse
If he'll work with you on the specifics then great.... Problem for me with treble is what I've said above.. If you ask a question in that forum it's swallowed almost immediately, so for an end user it's not exactly intuitive or even helpful in a traditional ROM owner/flasher sense of the word..
Information for specific devices simply doesn't exist. So it becomes a minefield for the end user.
Could be done a lot better, that's why so many people just don't bother with them.
dladz said:
If he'll work with you on the specifics then great.... Problem for me with treble is what I've said above.. If you ask a question in that forum it's swallowed almost immediately, so for an end user it's not exactly intuitive or even helpful in a traditional ROM owner/flasher sense of the word..
Information for specific devices simply doesn't exist. So it becomes a minefield for the end user.
Could be done a lot better, that's why so many people just don't bother with them.
Click to expand...
Click to collapse
I myself am also the type who doesn't care about all the specifics - even on my daily driver with GSI, I leave VoLTE and some other problems unfixed. Also, I don't actually own that OP10Pro, I just had it briefly.
An actual owner/user here might care, but before he figures out (or finds out he can't fix everything), I bet a device-specific ROM would've already come out. A rare case/device where running a GSI isn't worth the trouble, if you ask me.
AndyYan said:
I myself am also the type who doesn't care about all the specifics - even on my daily driver with GSI, I leave VoLTE and some other problems unfixed. Also, I don't actually own that OP10Pro, I just had it briefly.
An actual owner/user here might care, but before he figures out (or finds out he can't fix everything), I bet a device-specific ROM would've already come out. A rare case/device where running a GSI isn't worth the trouble, if you ask me.
Click to expand...
Click to collapse
Yea i agree, it's just a shame as the content is actually there, I could live without certain things myself. Volte I'm not overly fond of tbh..
I just find the whole thing more troublesome to just get info on treble ROMs.
I had a P20 Pro prior to the 8 pro and GSI ROMs would have been a god send so I'm sure there are a tonne of people out there who could use them..
I'd hope that it would be clearer but it's been so long now that I doubt that'll ever happen..
It's good you're working with pph. I hope that info you gather will be useful to others
I've tried to flash the latest phhusson
AOSP 12.1 v413 It's booting up, but you can't call someone (connection is dead). IMS Network is not supported. And no fingerprint and no auto brighness. Not usable right now
bhammler said:
I've tried to flash the latest phhusson
AOSP 12.1 v413It's booting up, but you can't call someone (connection is dead). IMS Network is not supported. And no fingerprint and no auto brighness. Not usable right now
Click to expand...
Click to collapse
I can't comment mate. I think you're very brave. You should make a thread based on your experience..
Document the crap out of it.
Share the hell of it.
This is needed for every OnePlus 10 pro owner, do it
it's very easy: don't use GSI right now ;-)
Aww dang. I really want some customization here. Having to restart everyday cause slow downs suck
Hello,
I've been missing for quite a long time from XDA, but I'm about to get a new phone soon (maybe another OnePlus?) and I came here to check for new custom ROMs updates.
But it seems I cannot find any custom ROM for the OnePlus 10 Pro (yet?), why is that?
Thanks for the info.
No msm unbrick tool, no sources and so on.
Oneplus sucks every phone a little bit more! 10 pro is definitely my last OP phone
You can try GSI roms, but they're buggy (e.g. fingerprint sensor is not working)
Also you cannot unbrick your phone unless you send it to 1+ which makes development hard
Source tree is different default compilable sources.i hope someone could port it.
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
galaxys said:
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
Click to expand...
Click to collapse
What mods are you using mate?
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
See a my reply to other post on oneplus 10 pro
ectoplasma22 said:
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
Click to expand...
Click to collapse
İ can't found it .could u share for me .it has same tree our devices i could work it.
metrixx02 said:
İ can't found it .could u share for me .it has same tree our devices i could work it.
Click to expand...
Click to collapse
There's a telegram group, check the pinned posts
Xiaomi 12 | OFFICIAL
Xiaomi 12 Official Group • English only chat • Read Rules ( /rules ) • Channel : @Xiaomi12GlobalUpdates • Photography group : @Xiaomi12GlobalPhotography • Off-Topic Group : @PocoOffTopic • Customization Group : @PocophoneCustomization
t.me
I've found this: https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450
And this: https://github.com/OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8450
But, sadly, I've also read this post: https://forum.xda-developers.com/t/how-not-to-guide.4458091/post-87108519
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
dladz said:
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
Click to expand...
Click to collapse
Yeah, I remember the old times here on XDA, there was so many threads proposing many different flavors.
I used to flash and try new ROMs almost everyday...
Now I have to get a new phone, I came here to check and I've realized it all changed.
It's even hard to find ROMs for Google Pixels and OnePlus phones, I don't know what happened but it's kinda frustrating...
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Honestly mate, I've had enough phones to know that it should have happened by now.
I'm very patient, no problem in waiting, but every single OnePlus device has had several ROMs by this point bar none
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Why do you need google roms? are they better?
Otherwise it finds 2-3 threads about to change to global or EU version.
But that is not you want?
lorenx said:
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Click to expand...
Click to collapse
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
EtherealRemnant said:
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
Click to expand...
Click to collapse
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
toolhas4degrees said:
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
Click to expand...
Click to collapse
There's also the fact that A/B partitions lead to plenty of bricks and the devs get blamed for it plus the issues that come with AVB 2.0, manufacturers not releasing full kernel sources... It's all a circus.