Database Info

Why is pixel development lagging?

Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Sent from my Nexus 5X using Tapatalk

stackz07 said:
Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Click to expand...
Click to collapse
There are a few and the performance is good.

In terms of price, the pixel is pretty damn expensive compared to other android phones with similar specs. Add to that the fact that, in the USA, at least, it was nearly impossible to get one for the longest time and finally, the way the partitioning is set up is quite different that any previous android phones. All these make for some slow development.

It's expensive plus Google's security features are becoming more problematic. The newest bootloader is causing issues with root now.
The real dev device now is OnePlus not googles product anymore.

stackz07 said:
Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Was actually my thinking also...
I came to the conclusion, that nobody has this device, and also google is making it hard to develop for the pixel. Working against the dev community with each update.
I am not worried though, because I only need root for my ARISE sound mod ,and backup/restore via Titanium Backup. I'm running completely stock, because that is the fastest, smoothest, most battery friendly setup I could find. Now that (even with a lot of hacking and manual adjustments) both TWRP and root works somehow, I am enjoying my pixel as it is... All these new things, like slots, loosing the recovery partition etc. make this device terrible for flashing. I was used to flashing my phones without a PC for 6-7 years now. I didn't even had to hook them up to the PC, only once, at first recovery flashing.... This is not the case with the pixel..
Maybe if the new partition layout gets picked up by other manufacturers, the problems will be solved quickly. Or even google drops this nonsense with the new pixels, and then we are really doooooomed

mikeprius said:
It's expensive plus Google's security features are becoming more problematic. The newest bootloader is causing issues with root now.
The real dev device now is OnePlus not googles product anymore.
Click to expand...
Click to collapse
Lol...OnePlus are unavailable to release nougat for the OnePlus 2 (SD810+4Gb Ram)

I don't really agree. The development took some time because of all the new features.
We are not really missing any roms, root, twrp or anything I want to be able to do. I see PN, DU, Lineage, OctOS, PixelDust, RR. I mean what other ones you want?
I'll get an OP when they decide to support their devices at least 2 years. They burned enough people with OP2.

milan187 said:
I don't really agree. The development took some time because of all the new features.
We are not really missing any roms, root, twrp or anything I want to be able to do. I see PN, DU, Lineage, OctOS, PixelDust, RR. I mean what other ones you want?
I'll get an OP when they decide to support their devices at least 2 years. They burned enough people with OP2.
Click to expand...
Click to collapse
Twrp seems abandoned, and the mix and match instructions for getting things to boot and run with magisk etc just seem odd, that's all. I'm sure everything will be figured out with time, but was just honestly curious.

stackz07 said:
Twrp seems abandoned, and the mix and match instructions for getting things to boot and run with magisk etc just seem odd, that's all. I'm sure everything will be figured out with time, but was just honestly curious.
Click to expand...
Click to collapse
Well the developer works on it when he can. It works fine so we do have it. Will need a new one that can sign the boot image.
Magisk isn't officially support it since developer does not have the device.
New boot signing procedure had a fix in a day or two after Google release. That's not bad. Things are not perfect I agree. Multiple slots are making things the hardest I think.
Sent from my Pixel using Tapatalk

Probably security more than anything. Don't expect it to pick up anytime soon.

Custom Oreo roms?

Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.

revdirty said:
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
Click to expand...
Click to collapse
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.

Just from my point of view, finding the various aspects for my themes was a pain in the butt from N to O. Somethings that were once png are now vector images and that is just from a themers aspect,,,rom building is a whole other thing. I am sure there will be some soon.

I was thinking the exact same thing as OP. I hope this isn't the case for the Pixel 2 XL. My Nexus 6 is running a custom Oreo ROM and it's great so far. It's like a ghost town.

Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance

Oreo appears buggy...
I will wait for Pure Nexus Oreo

udahy.manna said:
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Click to expand...
Click to collapse
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.

cntryby429 said:
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Click to expand...
Click to collapse
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung

Why is custom ROM development on Pixel is very low?

hp13 said:
Why is custom ROM development on Pixel is very low?
Click to expand...
Click to collapse
Because it's an expensive device and it has this new crappy A/B partitions system

lorax70 said:
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
Click to expand...
Click to collapse
The new official flashable TWRP is out and compatible with pixel Oreo.

yeah, I would give "O" a little time. It appears that some are starting to have a few issues with phones being bricked. It's possible that one of the 3 is not related, but certainly my advice would be to wait folks. This could be related directly to branded phones, but not exactly sure and would only be speculation at this point. It's possible the DEV's are waiting on a few areas...
https://forum.xda-developers.com/pixel/help/pixel-bricked-overnight-t3681377
https://forum.xda-developers.com/pixel/help/google-pixel-bricked-oreo-twice-ideas-t3671302

dantexaiver said:
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Click to expand...
Click to collapse
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.

I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol

Golf c said:
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Click to expand...
Click to collapse
Flash back to a nougat custom rom. Problem solved.

mitchdickson said:
Flash back to a nougat custom rom. Problem solved.
Click to expand...
Click to collapse
Haha, not quite.

Recently got a pixel after years of sony phones and am awaiting some Oreo custom roms. It's great I'm getting the latest OS updates straight away but the downside I guess is the newness means custom roms take longer. Now there's a working TWRP I'm hopeful we'll start to see custom Oreo roms appearing.

zelendel said:
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
Click to expand...
Click to collapse
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.

nine7nine said:
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
Click to expand...
Click to collapse
It is the standard for Google device. Notice how only Google devices use it?
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
A/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.

zelendel said:
It is the standard for Google device. Notice how only Google devices use it?
Click to expand...
Click to collapse
Motorola has been testing it, including a device that utilizes it now. Same goes with Xaoimi... Furthermore, a/b partition is a part of AOSP... Oreo devices going forward will be making use of Project Treble and I suspect in the next year, you are going to see more vendors adopting the new partition scheme.
On top of that, all new mediatek and Qualcomm SOCs will support A/b partition schemes.
https://www.xda-developers.com/xiaomi-mi-a1-android-ab-partition/
https://www.xda-developers.com/moto-z2-force-ab-seamless-updates/
https://review.lineageos.org/#/c/156378/
https://source.android.com/devices/tech/ota/ab_updates
zelendel said:
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
Click to expand...
Click to collapse
Um, no. it's perfectly reasonable for an end use running a custom ROM to want/expect OTA upgrades that uses seamless updating, where supported.... I've been involved in ROM development, in the past. thanks.... for someone developing a ROM; ya, you will be flashing your custom builds, but for an end user not building from AOSP, lineageOS repositories; OTA is far bore reasonable...
zelendel said:
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
Click to expand...
Click to collapse
lol. that comment makes zero sense, given the context... It's always been the case (for stock vs. custom roms) that you will be getting updates from one or the other, not both...
zelendel said:
IA/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
Click to expand...
Click to collapse
We will see, but given that Qualcomm and mediatek will be supporting it going forward and the revelations and direction of Project treble && VTS; I suspect that a/b partitions will become the norm...
the only question is what will Samsung do for future devices, since they unlike most vendors produce their own SOCs/Exynos boards.... I guess we will see when the next galaxy line is released.

looking for interested devs

Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.

so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.

godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk

Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source

godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk

Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.

godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk

Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice

godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk

Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform

godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk

Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.

Looks like Dirty unicorns incoming...

I was just checking out various customs threads & twitters and saw that DU had added Bonito to its official page as well as a screenshot on Twitter.
https://twitter.com/_DirtyUnicorns_/status/1129623484567621633?s=20
Im really hoping the dev community takes off for these devices like the old nexus days.

Wickidmasshole said:
I was just checking out various customs threads & twitters and saw that DU had added Bonito to its official page as well as a screenshot on Twitter.
https://twitter.com/_DirtyUnicorns_/status/1129623484567621633?s=20
Im really hoping the dev community takes off for these devices like the old nexus days.
Click to expand...
Click to collapse
I have mixed feelings. I rooted all 45 different Android phones I owned prior to my last 3 (essential, OnePlus 6, and more pixel 3A). I feel like these days there are way fewer reasons to use custom roms. Base Android has gotten really good, stock roms (for companies like OnePlus and essential) are stable and add lots of useful features, and the good manufacturers are doing updates multiple times a month anyways. We don't see crazy innovation like we did back in old paranoid Android days with projects like Halo and pie controls. And a lot of the real kernel developers like sultanxda moved on to other non-Android projects. It's a shame, but it helped push Google and it's partners into making better software. God knows how many features Google copied from custom roms. Kind of makes you wonder where we'll go from here now that roms are less of a necessity.

Yeah, I was on Android from day one and had been flashing the old windows phone before that. I've stopped installing roms on the last few phones however because I perceive them as worse than the stock software. I came here from a 6T which had a fair few ROMs but none that had the fingerprint sensor working correctly. I want that fingerprint sensor. There are other things but that's the idea, I used to see roms as a proposition where I gave up a few things but gained more than I lost. Now I don't see myself gaining much of anything that I'm not getting with a quick trip into Magisk with everything still working, but I do see things like that lost fingerprint sensor. It's kind of sad to me in a way because it was a bit like a hobby.

xxBrun0xx said:
I have mixed feelings. I rooted all 45 different Android phones I owned prior to my last 3 (essential, OnePlus 6, and more pixel 3A). I feel like these days there are way fewer reasons to use custom roms. Base Android has gotten really good, stock roms (for companies like OnePlus and essential) are stable and add lots of useful features, and the good manufacturers are doing updates multiple times a month anyways. We don't see crazy innovation like we did back in old paranoid Android days with projects like Halo and pie controls. And a lot of the real kernel developers like sultanxda moved on to other non-Android projects. It's a shame, but it helped push Google and it's partners into making better software. God knows how many features Google copied from custom roms. Kind of makes you wonder where we'll go from here now that roms are less of a necessity.
Click to expand...
Click to collapse
I agree with you. I haven't rooted my past 4 (6, 6p, pixel xl, pixel 2 xl) probably bc they all ran "pure Google."
I do also have a note 9 att variant and I wanted to root and install custom on that device the 2nd day in.
But to have options is always a good thing. Keep it up devs!!!
Sent from my Pixel 3a XL using

I can't get excited because I tried to figure out what features this rom has that would entice me to get into unlocking/etc and I can't find any sort of place where they actually tell you why you should install their mod. Their website still lists g+, to give an idea of how good their user communication is.

Is there any way I can get hotspot to work without having to use a custom rom

With magisk and Xposed, ROMs just aren't as necessary to me as they used to be, especially now that Google has made a good bit of functionality Pixel-only that isn't always replicated as well in ROMs.
There are still plenty of folks looking forward to them though, so this is definitely good news!

I stopped using custom roms when Marshmallow came out.
But I still use EX for the kernel..
Sent from my Pixel 3a XL using Tapatalk

jmcandrews83 said:
Is there any way I can get hotspot to work without having to use a custom rom
Click to expand...
Click to collapse
Yes, there's a build prop mod that pretty well known and works on any phone. Unfortunately you need an unlocked bootloader and root so no OTAs and you'll have to keep magisk updated to keep safety net working (it gets updated pretty often)

Heck I dont know why anyone would not want a custom rom. More options and features. Yeah stock has gone far these days but I will always welcome more development.

I can totally understand why people feel there isn't a need for root access or custom ROMs anymore. Stock has certainly improved a lot. I find it useful for a few things, though:
Limiting battery charge to 80% so it prolongs the life of my battery. It's important in a world where you can no longer change batteries with ease.
Swapping my back button on the nav bar to the right side
De-Googling my phone, i.e. installing LineageOS without GApps.

Hold on just a sec, for my part I didn't say anything about root, that's a must have for me. I also didn't say that I don't welcome the development, just that it probably wont be for me. Despite that I'm always glad to see it happen whether it is applicable to my use case or not. I certainly didn't mean to imply or say that ROM development is bad, I apologize if that was the connotation people got from my posts.

krabman said:
Hold on just a sec, for my part I didn't say anything about root, that's a must have for me. I also didn't say that I don't welcome the development, just that it probably wont be for me. Despite that I'm always glad to see it happen whether it is applicable to my use case or not. I certainly didn't mean to imply or say that ROM development is bad, I apologize if that was the connotation people got from my posts.
Click to expand...
Click to collapse
Hey, there! If you're replying to me, I'm sorry if I mislsed you. I didn't quote anyone because I was just referring to the general discussion from everyone.

Archangel said:
Heck I dont know why anyone would not want a custom rom. More options and features. Yeah stock has gone far these days but I will always welcome more development.
Click to expand...
Click to collapse
Same here bro ...i love more options and features cuz then it feels like i have 3 different phones in 1 lmao
Stock is getting better but still a little boring for me

I just hope this isnt another one of those Pixel XL things where all of the development goes to the XL and nothing comes to the regular Pixel 3a

Looks like they released a release candidate.
http://download.dirtyunicorns.com/?device=bonito

Wickidmasshole said:
I was just checking out various customs threads & twitters and saw that DU had added Bonito to its official page as well as a screenshot on Twitter.
https://twitter.com/_DirtyUnicorns_/status/1129623484567621633?s=20
Im really hoping the dev community takes off for these devices like the old nexus days.
Click to expand...
Click to collapse
I would think that would be the case - especially given the massive availability in North America alone. (I had a Galaxy Nexus and ran DU on it starting with Marshmallow and through Nougat - DU on a Pixel 3a XL would be - literally - Old Home Week and a good thing.) The ONLY reason I'm not running DU *now* is that I left the GNex for the Galaxy S7 Snapdragon - and not long after, the GNex croaked - it's now a paperweight.
If anything, the Pixel could be bigger than the Nexus line *ever* got to be - here is why:
1. First off, it can go to any carrier in North America - it's not restricted to Verizon Wireless.
2. Wide retail availablility - online my foot! I don't HATE online - I just prefer retail for things like phones (and that is despite being in the front yard of Amazon HQ2). And that is just the availability end.
3. Sane pricing - even, if not especially, in retail. ($479USD - as I stated before, that is the 3a XL - *half* the price of the S10e.) The S10e is pricier than the Note 9 - which is bad enough; to have the 3a XL undercut the same S10e by that much? Why would - or should- I buy an S10e? (And I don't hate the S10e - before the 3a and 3a XL came along, I was seriously considering the S10e, and I had actually seen it in retail and gotten some hands-on time with one - I haven't been able to do that with the 3a XL yet.)

Archangel said:
I just hope this isnt another one of those Pixel XL things where all of the development goes to the XL and nothing comes to the regular Pixel 3a
Click to expand...
Click to collapse
The XL has been Google's AOSP build target with all the Pixels including 3a.

lazycow said:
The XL has been Google's AOSP build target with all the Pixels including 3a.
Click to expand...
Click to collapse
So, I should return my 3a and get an XL for the dev support, you think?

jmtjr278 said:
So, I should return my 3a and get an XL for the dev support, you think?
Click to expand...
Click to collapse
I suspect the XL will get more support. But I don't know enough about either device to be sure how development will progress.

pixel 2 xl to pixel 4a???

So I went from the pixel 2xl to the 4a.
Mainly because development was coming to a halt.
But seems that there is nothing going on with the 4a.
Did I pick the wrong phone to upgrade to.
What I really like about pixels is being able to use fastboot, the camera and not using a program like let's say odin.
Should I have picked up a OnePlus phone instead.
Are google phone just going down hill now a days.
I just would like honest answer not just the normal well you development the **** then. That response is getting old. Xda forms are a great place to asked and get answers. But does anyone have any good suggestions. Thank you

I did the same thing. So far there's a couple 11 ROMs available, Superior os and Derpfest. Hopefully things pick up soon.
If not I'll be giving this to my wife and getting a 4a5g or a 5

Edmontonchef said:
I did the same thing. So far there's a couple 11 ROMs available, Superior os and Derpfest. Hopefully things pick up soon.
If not I'll be giving this to my wife and getting a 4a5g or a 5
Click to expand...
Click to collapse
4a 5g is way worse on development. They have proton kernel and that's it. We have some roms and some kernels. I think most custom roms just attempt to replicate vanilla android with useful features. I think that's why you have so few roms here. We already have vanilla. I think a ton of the features of customs from generations past have slowly made their way into vanilla and there aren't really a whole lot of features lacking. I realize some more customization in certain areas would be nice but we are on the right track. I don't even find root access to be 100% necessary out of the box anymore.
Sent from my Pixel 4a using Tapatalk

If custom ROMs you are after head over to the project trebble page and flash a gsi.

ttocs99 said:
If custom ROMs you are after head over to the project trebble page and flash a gsi.
Click to expand...
Click to collapse
Do they run well
A video I saw was saying that sometimes they don't work on all phones correctly
But I also don't know much about gsi roms
Sent from my Google Pixel 4a using XDA Labs

I am getting ready to compile the kali nethunter kernel for our device. Maybe ill start porting some stuff too.

SirFronts said:
Do they run well
A video I saw was saying that sometimes they don't work on all phones correctly
But I also don't know much about gsi roms
Sent from my Google Pixel 4a using XDA Labs
Click to expand...
Click to collapse
That's the point people! are using gsi on all kinds of devices but they should work fine on pixels. A lot of fixes has been implemented on most gsi. It's worth a shot and have nothing to loose as it's easy to fix a soft brick on pixel by fastboot flashing the 4a factory image.

ttocs99 said:
That's the point people! are using gsi on all kinds of devices but they should work fine on pixels. A lot of fixes has been implemented on most gsi. It's worth a shot and have nothing to loose as it's easy to fix a soft brick on pixel by fastboot flashing the 4a factory image.
Click to expand...
Click to collapse
You are right that's the one thing I love about pixels.
I haven't bricked one yet. Gotta love flash-all lol.
That's why I didn't mind using OnePlus 7pro
Sent from my Google Pixel 4a using XDA Labs

SirFronts said:
Are google phone just going down hill now a days.
Click to expand...
Click to collapse
No, the opposite. On previous phones stock Android sucked so you had to faff about with unlocking bootloaders, flashing roms, getting help from incels with social problems (as you mentioned - "fix it yourself" type responses).
The pixel 4a is now as good as the best non-standard Android phones, like the OS on Honor/Huawei phones, so there's no longer any need to waste time risking bricking your phone with rom flashing and the like; it's pretty much perfect out of the box...well, nothing Nova Launcher won't fix.

Yep back in the day...3g days lol...root and roms were developed to improve devices overall. With the pixel line they really don't improve anything really. Now if someone ports say MIUI or something drastically different I will just stay stock. That's just me though.