Hello,
Can someone create a ROM with android 9 for The Sony Xperia Z5P (E6853)?
ker_99 said:
Hello,
Can someone create a ROM with android 9 for The Sony Xperia Z5P (E6853)?
Click to expand...
Click to collapse
You can try. @Berni-0815 he works for z5 compact but he has a big problem. Maybe you can help him.
No way!
You could try to build AOSP 9
Android 9 is a no go for now. I plan to build LineageOS 15.1 for Z5 Premium. Expect to see more news in the few weeks/days. Don't expect it to be a full on stable release, that's probably going to take months. Sadly it seems no one cares enough these days so I won't be all that motivated.
Joel16 said:
Android 9 is a no go for now. I plan to build LineageOS 15.1 for Z5 Premium. Expect to see more news in the few weeks/days. Don't expect it to be a full on stable release, that's probably going to take months. Sadly it seems no one cares enough these days so I won't be all that motivated.
Click to expand...
Click to collapse
Thank you so much in advance. I'm sure there's many of us who will appreciate this.
Mike3009 said:
Thank you so much in advance. I'm sure there's many of us who will appreciate this.
Click to expand...
Click to collapse
I'm still learning my way around Android so as I said before don't expect it to be stable out the box. I can't guarantee anything for now, but I can promise that I'll get some sort of functional build of Oreo in the end. The only thing I'm worried about right now are the proprietary (closed source) drivers that may hinder certain functions from working.
Joel16 said:
I'm still learning my way around Android so as I said before don't expect it to be stable out the box. I can't guarantee anything for now, but I can promise that I'll get some sort of functional build of Oreo in the end. The only thing I'm worried about right now are the proprietary (closed source) drivers that may hinder certain functions from working.
Click to expand...
Click to collapse
Sure man, really any effort you could offer would be greatly appreciated and not just by me, I'm sure there's others following as well. There was a developer on this forum who attempted to port oreo to the z5 premium but he ran into issues and gave up. One thing that I can remember without checking the thread was that the camera completely didn't work. Do you by any chance have access to a z5 premium to test it on?
Mike3009 said:
Sure man, really any effort you could offer would be greatly appreciated and not just by me, I'm sure there's others following as well. There was a developer on this forum who attempted to port oreo to the z5 premium but he ran into issues and gave up. One thing that I can remember without checking the thread was that the camera completely didn't work. Do you by any chance have access to a z5 premium to test it on?
Click to expand...
Click to collapse
That is what I read as well, and yes I do own a Z5 Premium (single sim) which I will be doing my testing on. I haven't seen anything about Oreo for our device but I have seen attempts on other devices such as the Z5 and Z5C. They seem to have issues with certain functionalities like the camera as you mentioned. This is due to the proprietary blobs not being updated to support Oreo if I'm understanding this correctly, which is also my biggest worry. I'll be working on 7.1 for now just to make sure I'm going on the right path before shifting to Oreo. One of the things I want to bring to this device is Omnirom. I remember using it on an older device with kit kat years ago, and it was my go to back then.
Joel16 said:
That is what I read as well, and yes I do own a Z5 Premium (single sim) which I will be doing my testing on. I haven't seen anything about Oreo for our device but I have seen attempts on other devices such as the Z5 and Z5C. They seem to have issues with certain functionalities like the camera as you mentioned. This is due to the proprietary blobs not being updated to support Oreo if I'm understanding this correctly, which is also my biggest worry. I'll be working on 7.1 for now just to make sure I'm going on the right path before shifting to Oreo. One of the things I want to bring to this device is Omnirom. I remember using it on an older device with kit kat years ago, and it was my go to back then.
Click to expand...
Click to collapse
Awesome, I'm on a e6853. I'd be happy to help test anything.
I'm also happy to help you test.
Joel16 said:
That is what I read as well, and yes I do own a Z5 Premium (single sim) which I will be doing my testing on. I haven't seen anything about Oreo for our device but I have seen attempts on other devices such as the Z5 and Z5C. They seem to have issues with certain functionalities like the camera as you mentioned. This is due to the proprietary blobs not being updated to support Oreo if I'm understanding this correctly, which is also my biggest worry. I'll be working on 7.1 for now just to make sure I'm going on the right path before shifting to Oreo. One of the things I want to bring to this device is Omnirom. I remember using it on an older device with kit kat years ago, and it was my go to back then.
Click to expand...
Click to collapse
Cool! My daily driver is my E6883 dual sim. I'm also happy to test, as I have several other Xperia models to fall back on.
Joel16 said:
I'm still learning my way around Android so as I said before don't expect it to be stable out the box. I can't guarantee anything for now, but I can promise that I'll get some sort of functional build of Oreo in the end. The only thing I'm worried about right now are the proprietary (closed source) drivers that may hinder certain functions from working.
Click to expand...
Click to collapse
I'm also ready to test it with my E6853 (Z5P).
TWRP is installed
@ker_99 and @wicozani then please try this rom and provide logs, thank you.
https://forum.xda-developers.com/showpost.php?p=81328929&postcount=10
Related
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
In my experience unless you are using a nexus device aosp roms are never 100% at least not until the phone is at the year/year and a half mark. Now if your talking about camera not working and stuff like that yeah its going to take time especially since only a hand full of devs are working on it in there spare time. On the plus side they will probably have most of the kinks hammered out before L releases and most of the changes and fixes will translate over.
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Jess813 said:
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Click to expand...
Click to collapse
We do have aosp roms.....
ThePagel said:
We do have aosp roms.....
Click to expand...
Click to collapse
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Jess813 said:
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Click to expand...
Click to collapse
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
ThePagel said:
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
Click to expand...
Click to collapse
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Jess813 said:
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Click to expand...
Click to collapse
Somebody will send a request to have a rom reviewed to be added to the official git. It will just take the one person and a little time. If you feel strongly about it you could ask one of the devs working on it to send it to the cm team for review but I bet one of them will after the camera is fixed. whoever does will have there name next to 99% of the commits in the official github so that person will have bragging rights.
Tom Marshall was working on it then intervigilium, who yesterday had some activity on his github and finally invisiblek as well, all with cyanogenmod. Not to mention the actual phone 2 of them are using belongs to...think it was Roman from AOKP. You also have the guys here working on it when they have time. My bet would be a few more weeks and it will be up and running properly.
Good to know, I love this phone however but I'm sure with an AOSP ROM it'll fly!!!
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
coding a new rom takes time and devs work on their own dime as so few here actually donate anything to them. Phones and their hardware are becoming way more sophisticated each year and porting any flavor of rom is no longer something easily done. If people are impatient perhaps they need to open their wallets and give the devs some inspiration.............
Isnt ATT usually the first to get it? Why are we last all sudden?
No maintainer so it won't get approved for nightlies. CM requires someone with development knowledge and who owns the device to keep it properly updated before it will accept them into nightlies
Sent from my LG-D852 using Tapatalk
That said there are builds out there. I've been running the following build for a week or so and it's absolutely wonderful. Better than any LP ROM I've even tried.
http://forum.xda-developers.com/lg-g3/general/cm13-lg-g3-test-builds-t3245744
Here are 2 location to get CM13 unofficially for the D850:
https://ci.galliumos.org/job/cm13/device=d850,jdk=OpenJDK7,label=android/
https://www.androidfilehost.com/?w=files&flid=44671
It's been running well on mine. The biggest issue has been no functioning GPS.
kimocal said:
Here are 2 location to get CM13 unofficially for the D850:
https://ci.galliumos.org/job/cm13/device=d850,jdk=OpenJDK7,label=android/
https://www.androidfilehost.com/?w=files&flid=44671
It's been running well on mine. The biggest issue has been no functioning GPS.
Click to expand...
Click to collapse
I'm running the second build and it is good so far, except for the odd random reboot or I'll have to pull the battery.
Wow no GPS = no ingress or maps. Pulling the battery might as well be cm12.1
Cuzz1369 said:
No maintainer so it won't get approved for nightlies. CM requires someone with development knowledge and who owns the device to keep it properly updated before it will accept them into nightlies
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
OK so why are there 12.1 nightlies? Where did those devs go? Why do att users always get screwed over?
lolwatpear said:
OK so why are there 12.1 nightlies? Where did those devs go? Why do att users always get screwed over?
Click to expand...
Click to collapse
You know some people get new phones, some people get a life. Some people get sick of hearing crap like this.
Cuzz1369 said:
You know some people get new phones, some people get a life. Some people get sick of hearing crap like this.
Click to expand...
Click to collapse
AMEN! "Users getting screwed over by devs not doing stuff for free any more". Sigh.
roirraW "edor" ehT said:
AMEN! "Users getting screwed over by devs not doing stuff for free any more". Sigh.
Click to expand...
Click to collapse
I didn't say it, so I can't comment on the intention of the comment, but I would have taken it as meaning that we constantly get screwed over by AT&T and device manufacturers like LG, both of which are true. We (I anyway) are very thankful for the devs who give us awesome things like CM and other assorted roms and kernels and whatnot - we love you guys. I've had other LG flagships for which AT&T and LG dropped support way earlier than expected, and earlier than other carriers' variants. In some cases they have even promised a certain level of future support then decided later to end development early without comment.
It gets old - we like our LG phones for a lot of reasons, but AT&T and T-Mobile users often get screwed so we have to depend on independent devs. Either we move on to another phone, stick with an old OS or base, or someone creates something awesome. We love the dev community and hope they stay interested, but if they lose interest what are we supposed to do, pay them full-time salaries to port CM 13? That just isn't possible without a lot of organization and large scale funding. If you don't want to develop, don't. You certainly have a right to get frustrated, as do we. So again, I don't know the intent of the original comment, but try not to take it personally, and please don't assume that most users and consumers have any animosity for devs, because we don't - we are amazed by what you all do. If it is glory and being showered with money and praise you seek, you're probably in the wrong field, but thanks for your contributions anyway.
emepher said:
I didn't say it, so I can't comment on the intention of the comment, but I would have taken it as meaning that we constantly get screwed over by AT&T and device manufacturers like LG, both of which are true. We (I anyway) are very thankful for the devs who give us awesome things like CM and other assorted roms and kernels and whatnot - we love you guys. I've had other LG flagships for which AT&T and LG dropped support way earlier than expected, and earlier than other carriers' variants. In some cases they have even promised a certain level of future support then decided later to end development early without comment.
It gets old - we like our LG phones for a lot of reasons, but AT&T and T-Mobile users often get screwed so we have to depend on independent devs. Either we move on to another phone, stick with an old OS or base, or someone creates something awesome. We love the dev community and hope they stay interested, but if they lose interest what are we supposed to do, pay them full-time salaries to port CM 13? That just isn't possible without a lot of organization and large scale funding. If you don't want to develop, don't. You certainly have a right to get frustrated, as do we. So again, I don't know the intent of the original comment, but try not to take it personally, and please don't assume that most users and consumers have any animosity for devs, because we don't - we are amazed by what you all do. If it is glory and being showered with money and praise you seek, you're probably in the wrong field, but thanks for your contributions anyway.
Click to expand...
Click to collapse
Thanks. Yes, that's what I meant. ATT is the reason why devs don't have ATT phones, even ones that are very open to development. They must not see a point in developing for a device with less already-established devs and less users.
As for my previous questions, I legitimately wanted to know where the devs who had just worked on 12.1 cm went. I just didn't know how the nightlies worked.
Updates for CM13.0 d850 here
Some UNOFFICIAL CyanogenMod CM 13.0 (AOSP Marshmallow 6.0.1) ROM images for d850 are here. I've been building them for about a month and posting an update every couple of days. I hope to continue posting semi-daily updates until somebody at CyanogenMod starts maintaining a d850 nightly.
wseverin said:
Some UNOFFICIAL CyanogenMod CM 13.0 (AOSP Marshmallow 6.0.1) ROM images for d850 are here. I've been building them for about a month and posting an update every couple of days. I hope to continue posting semi-daily updates until somebody at CyanogenMod starts maintaining a d850 nightly.
Click to expand...
Click to collapse
I've been running your 20160305 for the past couple days and it's been very stable. Thanks for sharing your nightlies.
does GPS works with the latest cm13 nightly?
Has anyone tried running the official cm13 build from T-mobile G3? The only difference I'm aware of is WiFi calling.
appsmarsterx said:
does GPS works with the latest cm13 nightly?
Click to expand...
Click to collapse
everything should be working.
I used gps google maps to nav on a car drive recently, just fine, no issue
there is already CM13 for D850
http://subefotos.com/ver/?034b03d64343e75988549fff7cd5a5f2o.jpg
undivide said:
everything should be working.
I used gps google maps to nav on a car drive recently, just fine, no issue
Click to expand...
Click to collapse
What made you go back to stock? (I'm assuming your signature is up-to-date)
deathbytalkshow said:
What made you go back to stock? (I'm assuming your signature is up-to-date)
Click to expand...
Click to collapse
yeah, I went back to stock because it was getting harder to find a good working build of cm and I was getting tired of flashing daily so I went to weekly flash and I got tired of that so I did a revert and took all the updates OTA thru at&t to get up to 6.0
I wanted to be able to use android pay whenever I need to.
For a stock base, LG really has everything I need but I still overlay nova prime launcher to clean things up a bit. Its little things like not having to worry about whether or not an app is going to load or crash the entire system. Also not having to worry if a reboot or shut down is going to lock my phone and require a battery pull, which I have not had to do once since going to stock.
In the event that I do go to sell the phone off it generally is more desirable to have stock OS.
Oh also, my wife got a new galaxy s7 so we can do VoLTE calling now =-)
This might be my imagination but the cell tower service seems more consistent with at&t stock os.
Have no need for root and no need for kernels or any of cm's little oddities.
Sometimes I think the maintainers change things in the rom just for the sake of changing something, whether its necessary or not and without regard for whether it might wreck havoc on the entire system stability
undivide said:
yeah, I went back to stock because it was getting harder to find a good working build of cm and I was getting tired of flashing daily so I went to weekly flash and I got tired of that so I did a revert and took all the updates OTA thru at&t to get up to 6.0
Click to expand...
Click to collapse
I'm on Cricket so it won't let me OTA to 6.0 unless I have an active AT&T SIM. I'm hoping someone at a Cricket store has one lying around that I can borrow. But I get what you mean. Whenever there was a nightly I liked that gave me no problems, I stuck to it like glue I actually gave CM13 a try for a while, today, and it was like butter. But the one thing that don't like losing from LG stock is the "content lock" in the gallery. I haven't seen a 3rd party app that encrypts and locks them down like LG; others just hide it with .nomedia or their app is bulky or they convert it but can't recover images anymore.
Thanks for replying
Can any one have any news for oreo rom for op3 like linage 15 or RR rim or any other rom..... If any news plz plz give a comment
Waiting...........................
My bet is December like last year.
Still checking everyday on xda ???
Playa82 said:
My bet is December like last year.
Click to expand...
Click to collapse
I'm pretty sure that he's talking about custom ROMs.
deepak3048 said:
Can any one have any news for oreo rom for op3 like linage 15 or RR rim or any other rom..... If any news plz plz give a comment
Click to expand...
Click to collapse
Check this out..
https://plus.google.com/+varund7726/posts/BeSViUDtVpH
Summary for RR
Final N build will come out when sept security patches are out
No work has started by us for O yet
When we start the work on O , main branches will be kept private till we carry out our tests
O builds will not come out for a month or maybe more
Though it does not mean individual RR developers are not working because then you also have this
https://plus.google.com/+AkhilNarang/posts/Hup1zPxKNyW
Devs are working hard to bring up O for OP3 they are working in the background. Expect some alpha builds to drop next month for sure
Because of project treble being introduced into oreo, I'm not sure how it will effect custom roms. Pure nexus roms will be easy, Will insanely feature filled roms like rr could very well be alpha or beta till december or january.
Asking for ETA's on XDA... Someone has not read the rules...
Dlind said:
Because of project treble being introduced into oreo, I'm not sure how it will effect custom roms. Pure nexus roms will be easy, Will insanely feature filled roms like rr could very well be alpha or beta till december or january.
Click to expand...
Click to collapse
It wont be that hard really as it will have to be removed and disabled. Just like the dual partition setup. Or any other system mechanic really.
All xiaomi phones get oreo custom roms.
Keyvannn said:
All xiaomi phones get oreo custom roms.
Click to expand...
Click to collapse
I wouldnt be too worried about those. Almost nothing works. No dev with any self respect is gonna put out a rom that has the majority of things broken.
lineage 15 is here
https://forum.xda-developers.com/on...evelopment/rom-kernel-lineageos-15-0-t3668952
Dupleshwar said:
lineage 15 is here
https://forum.xda-developers.com/on...evelopment/rom-kernel-lineageos-15-0-t3668952
Click to expand...
Click to collapse
That should have been expected with all the other ports around. Not surprised most things still don't work. But they got progress. I'll wait for an aosp rom before updating. To be honest the more I see the less I am thinking about updating.
zelendel said:
That should have been expected with all the other ports around. Not surprised most things still don't work. But they got progress. I'll wait for an aosp rom before updating. To be honest the more I see the less I am thinking about updating.
Click to expand...
Click to collapse
After using Oreo on Pixel XL I went back to N so many issues
liam_davenport said:
After using Oreo on Pixel XL I went back to N so many issues
Click to expand...
Click to collapse
Yeah many are reverting back to android N due to the typical Google update. Full of bugs and not tested. It is gonna take the rom devs months to fix everything google broke. But that is normal
zelendel said:
It wont be that hard really as it will have to be removed and disabled. Just like the dual partition setup. Or any other system mechanic really.
Click to expand...
Click to collapse
I see. I didn't think treble could be removed. But now that that isn't a problem.
Dlind said:
I see. I didn't think treble could be removed. But now that that isn't a problem.
Click to expand...
Click to collapse
Treble won't ever see this device and to be honest I'm betting the oem disable it in the majority of devices. Googles hope with treble is not something that will be useful for about 5 years or so.
zelendel said:
That should have been expected with all the other ports around. Not surprised most things still don't work. But they got progress. I'll wait for an aosp rom before updating. To be honest the more I see the less I am thinking about updating.
Click to expand...
Click to collapse
Agreed
Closed beta 8.0 was just released. Public beta expect by the end of this month. http://www.androidpolice.com/2017/0...coming-soon-public-beta-slated-end-september/
Now I'm on stock Android 9 (very first build) + Magisk.
Everything is fine. I've never want to flash android 10 (or LOS 17.1). Because not much differences between 9 and 10.
But now, when Android 11 is released, I really want it.
Any ideas, guys?
I cannot find any plans about possibility of development adroid 11 on Pixel XL.
Thanks in advance.
There has been indeed a question about Android 11 in "PixelDust Android 10" thread, to which the ROM creator replied: "I will give it a try". So we'll have to be patient for now.
Darkboom said:
There has been indeed a question about Android 11 in "PixelDust Android 10" thread, to which the ROM creator replied: "I will give it a try". So we'll have to be patient for now.
Click to expand...
Click to collapse
Over on RR I believe, someone said their friend got AOSP 11 booted and built for it, but is having RIL issues; that's hopeful at least.
Voltz100999 said:
Over on RR I believe, someone said their friend got AOSP 11 booted and built for it, but is having RIL issues; that's hopeful at least.
Click to expand...
Click to collapse
Yeah it is! Seems like we'll get Android 11 in the future, good to know.
Darkboom said:
Yeah it is! Seems like we'll get Android 11 in the future, good to know.
Click to expand...
Click to collapse
They have a tree assembled already apparently, it's just that RIL is broken. I asked how broken but it may take a few days for him to see it.
Voltz100999 said:
They have a tree assembled already apparently, it's just that RIL is broken. I asked how broken but it may take a few days for him to see it.
Click to expand...
Click to collapse
There is no rush tbh. It's a surprise we'll get the new android at all, let alone so soon.
Darkboom said:
There is no rush tbh. It's a surprise we'll get the new android at all, let alone so soon.
Click to expand...
Click to collapse
Apparently RIL is very, VERY broken, as is the camera; it thinks it's always on.
Voltz100999 said:
Apparently RIL is very, VERY broken, as is the camera; it thinks it's always on.
Click to expand...
Click to collapse
Well that's unfortunate, hope it will be fixed soon!
Darkboom said:
Well that's unfortunate, hope it will be fixed soon!
Click to expand...
Click to collapse
I do believe they can
Yeah, so the dev that's currently working on porting 11 to the Pixel is going to be busy for the next few days, so porting is on hold. Although the bugs have been resolved, the reason it's being held back is because he's trying to get GApps to fit on the phone, and is also doing an 11 bringup for the S6.
yagyaxt1068 said:
Yeah, so the dev that's currently working on porting 11 to the Pixel is going to be busy for the next few days, so porting is on hold. Although the bugs have been resolved, the reason it's being held back is because he's trying to get GApps to fit on the phone, and is also doing an 11 bringup for the S6.
Click to expand...
Click to collapse
I hope he can get it, he's a smart man. Much more than I with my basic knowledge on building and assembling trees.
As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Your fone working on a custom rom will still work, since you'd think it was the custom rom updated...
If they do stop the fone calling, there's plenty other apks for 'near field' communication
Free wifi calling hint hint..
Pachacouti said:
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Click to expand...
Click to collapse
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
David B. said:
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
Click to expand...
Click to collapse
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Pachacouti said:
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Click to expand...
Click to collapse
Well, LineageOS certainly does that, but at the same time, it also takes them about 6 months to move to a new major release of Android. I was hoping that someone would know of a release that does it just as well, but is a little more flexible with migrating. I haven't found any myself.
I've yet to convince myself which version is for my fone lol
David B. said:
As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Click to expand...
Click to collapse
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Not at all, they all sound excellent, however, my fone cant write to the actuall system, can mount, but no joy yet doing anything else, and no overlay works so far, the only custom os I could install was a chrooted nethunter, which was pretty lame and useless being my system as root is a pain... so I'm looking..
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
My plan, at least for now, is to ride on stock until the last update is pushed, and then once LOS gets updated to 12, I will migrate. The only problem with this, though, is that it would leave me without security updates from the end of December until either March or April, and I am not sure how I feel about that.
My experience might help...Last year I was using a Motorola 5Plus with Pixel Experience Rom and loved it. My phone was fast, stable and highly compatible to the "Pixel Experience". I had a hardware issue and decided I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
I'm hoping someone picks up PE and ports it to the 3XL and I'll use that....otherwise, any alternative suggestions for closest to "stock" Pixel would be appreciated...
S
spschneer said:
I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
Click to expand...
Click to collapse
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
David B. said:
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
Click to expand...
Click to collapse
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
spschneer said:
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
Click to expand...
Click to collapse
Great! I guess it's time for me to start researching building my own image.
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
spschneer said:
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
Click to expand...
Click to collapse
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
David B. said:
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
Click to expand...
Click to collapse
Sounds like a plan...will keep an eye on development threads for it once it goes out of support.
Even though the last update will be in Dec I'll probably keep using the 3XL until the 7 comes out (or 6a maybe). I just had the battery replaced a couple months ago, and there is nothing wrong with the phone. I usually use devices until EOL hits, and then upgrade when the next OS/phone comes out, so whatever device I'm using at any given time is on the current OS release (IE: 3XL on Android 12 until Android 13 drops, and then upgrade phone to get Android 13).
I would like to use that method, but I think it's too expensive, so I try to settle for "my phone's basically dead."
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
Does the unlimited Google Photos upload work on LineageOS?
quera said:
Does the unlimited Google Photos upload work on LineageOS?
Click to expand...
Click to collapse
I don't know how to tell if it is still in effect. I see photos counted against my storage allotment, but don't know if that is just for my previous phones, or if it includes the Pixel photos.
My guess is you would have to use the Google Camera and Photo apps to keep unlimited upload, if it can be kept with LineageOS.