Related
Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
No, don't do that. Especially not the RUU since that does more than just installing a stock rom.
wrath0r said:
Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
Click to expand...
Click to collapse
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
xpirt said:
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
Click to expand...
Click to collapse
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
wrath0r said:
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
Click to expand...
Click to collapse
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
jmz said:
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
Click to expand...
Click to collapse
Correct. And....ohai!
The partition layout is completely different as are the kernel base and ramdisk offsets. If you flash that RUU...you may be heading back to the AT&T store immediately afterwards.
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Sent from my One using xda app-developers app
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
xpirt said:
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
Click to expand...
Click to collapse
Yes. And this is how I was able to port sense to the First so easily. HTC's "AOSP" roms are purely Sense roms with specific apks replaced with AOSP apks. In 4.2+ a lot of changes need to be made to kernel to boot AOSP. Those changes won't necessarily be compatible with sense
Sent from my HTC One using XDA Premium 4 mobile app
boy am I glad I saw this before trying to flash my mini !
GPE for the Mini
h8rift said:
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Click to expand...
Click to collapse
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
yourmate said:
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
Click to expand...
Click to collapse
Yeah buddy... Try this http://forum.xda-developers.com/htc-one-mini/orig-development/rom-t2825888
Cheers
I would not install any CM-based ROM (CM/Candy*/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will, eventually) get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
excellent, thanks
pure.by said:
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Excellent suggestion as I was looking for the GPE originally :good:
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
EH? There has NEVER been any reports of overheating or bricked devices on CandyRom! So I suggest for you to get your facts right before posting.!
AnGrY sCoTsMaN said:
There has NEVER been any reports of overheating or bricked devices on CandyRom!
Click to expand...
Click to collapse
I'm very sorry if that is the case, then I must be mistaken for another ROM; there were a bunch involved in this issue.
But no reports does not mean it has not happened. As far as I know CandyRom is CM-based *, and overheating issue affects all CM-based ROMs the same. Not sure what makes CandyRom different in that aspect. *
Once again, it may happen or it may not. You can either see it as a lottery or a ticking time bomb. Either way, I better go with the ROM that just does not have that possibility by design.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
yourmate said:
Excellent suggestion as I was looking for the GPE originally :good:
Click to expand...
Click to collapse
Glad I could help
If you could find some time in a week or two to report back about stability, performance and your overall experience, that info would be much appreciated!
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Yeah get your facts correct before you post Candy Roms isn't even Cyanogen based like the rest you stated and no bricks have been made by using this ROM either. For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
tr1gg3r84 said:
Candy Roms isn't even Cyanogen based
Click to expand...
Click to collapse
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me.
Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly right away.
pure.by said:
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me. Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly.
Click to expand...
Click to collapse
Yeah well I should know what I'm on about, after supporting this device for so long before anyone even cared about developing for it....(well there's a lot of so called (Devs) that like to spread rumors about other ROMs to increase their user base) pretty much sick to death of it tbh. Apology accept and cheers for that. CandyRoms is a great ROM supported by over 30 devices and glad to be apart of the team of working hard developers
tr1gg3r84 said:
For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
Click to expand...
Click to collapse
Good for you.
Thanks God, that bilal_liberty's thought it differently and shared it rather than just posting about it
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.
When I the I had nexus 5 there used to be loads of content in xda be it roms or mods. Now for the pixel 2 there is no custom rom to begin with. I understand the stock Google oreo is as good as ever but still the basic tweaks would add much more to it.
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
I was just looking for dual speaker ring, status bar tweaks.
I hope to see more soon as well. Now that Verizon phones are on board for rooting there will probably be more devs getting their hands dirty.
Not to mention there are still only a few phones running Oreo. Right now it's just basically pixel owners. So all the mods made for other phones haven't been ported or upgraded.
I'll have this phone for the next two years I'm hoping there will be more with time.
I haven't even been able to get debian, Ubuntu, or Kali to work along side this phone yet. Proot and chroot don't seem to be working as they should. I tried 3 methods. Linux deploy, termux ,and using the nethunter module. Guess I'll just keep at it until New methods are found.
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
One plus because of the price
Sent from my Google Pixel 2 XL using XDA Labs
Sman999 said:
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
Click to expand...
Click to collapse
The a/b bootloader partitions... No dedicated recovery.... Blah blah blah too much for me to understand but basically it's screwing with devs.
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
I guess oneplus or Samsung. The later cuz the design is awesome but software experience is poor so if the software is improved it ll be awesome Samsung. ?
I wondered the same thing but then it dawned on me, I only rooted/ROM'd devices to run something that's a vanilla build of Android. That's what this is. There's a few nitpicky things that I would love to have but for the most part, I'm happy with it.
main reason for me is the PRICE.. if it was just priced same as the nexus 5, . thats why oneplus devices are being so favored
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Surge1223 said:
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Click to expand...
Click to collapse
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
bmwh0r3 said:
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
Click to expand...
Click to collapse
Ironic you should ask..I helped him come back to the game today you could say lol
I apologize in advance if this is breaking rules begging for updates, I don't want to do that. I just want to know if my understanding of the situation is correct; I've never flashed a custom ROM before. At a high level, my current understanding is:
1. AOSP camera works in Custom ROMs but are not very good, because there is a lot of proprietary stuff in cameras that manufacturers put in. It is hard to get blobs working well on custom ROMs because source code is unlikely to be released.
2. Historically, XDA contributors, after a lot of work, were able to get OnePlus 3/3T camera blobs from OxygenOS working about as well on custom ROMs as on OxygenOS. I'm not sure if this is true for the 5/5T. I don't know if this tells us anything about the OnePlus 6 or not.
3. XDA contributors are currently looking at porting Google Cam to the OnePlus 6, which might be even better than stock, but might never work well. Work by developers here is ongoing. (Do historic GCam ports work on custom ROMs?)
https://forum.xda-developers.com/oneplus-6/themes/oneplus-6-google-camera-port-t3797544
My question is: Is this all the known relevant information, as of right now? Are there other camera projects I should be following?
Thank you!
BeakerBen said:
I apologize in advance if this is breaking rules begging for updates, I don't want to do that. I just want to know if my understanding of the situation is correct; I've never flashed a custom ROM before. At a high level, my current understanding is:
1. AOSP camera works in Custom ROMs but are not very good, because there is a lot of proprietary stuff in cameras that manufacturers put in. It is hard to get blobs working well on custom ROMs because source code is unlikely to be released.
2. Historically, XDA contributors, after a lot of work, were able to get OnePlus 3/3T camera blobs from OxygenOS working about as well on custom ROMs as on OxygenOS. I'm not sure if this is true for the 5/5T. I don't know if this tells us anything about the OnePlus 6 or not.
3. XDA contributors are currently looking at porting Google Cam to the OnePlus 6, which might be even better than stock, but might never work well. Work by developers here is ongoing. (Do historic GCam ports work on custom ROMs?)
https://forum.xda-developers.com/oneplus-6/themes/oneplus-6-google-camera-port-t3797544
My question is: Is this all the known relevant information, as of right now? Are there other camera projects I should be following?
Thank you!
Click to expand...
Click to collapse
It's all known. Google has made their camera software public for a while now. A very capable developer who has developed a working gcam for other devices will be receiving a op6 from op so development will continue for the gcam for the 6. It will take some more time for a stable version to be released.
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.