Related
http://device.sprintpcs.com/Samsung/SPH-D710/FB24.rdf
Let the fun begin?
Caulk!!!
And here...we...go!
whaaaat lol keep em coming!!!!!
I'm really at the point where I think (personal opinion) unless it's got some major changes/fixes screw it not worth it.
cidica said:
I'm really at the point where I think (personal opinion) unless it's got some major changes/fixes screw it not worth it.
Click to expand...
Click to collapse
No way! This is just like flashing CM7 nightlies a year ago on my OG EVO, I love it! Keep the leaks coming guys! I want to watch this baby develop into a full grown ice cream sandwich!
cidica said:
I'm really at the point where I think (personal opinion) unless it's got some major changes/fixes screw it not worth it.
Click to expand...
Click to collapse
well good.. more bandwidth for me. lol
cidica said:
I'm really at the point where I think (personal opinion) unless it's got some major changes/fixes screw it not worth it.
Click to expand...
Click to collapse
It's good for the flashaholics, though. I'm just happy that we have proof positive that Samsung is working hard on getting ICS up and running on our phone.
cidica said:
I'm really at the point where I think (personal opinion) unless it's got some major changes/fixes screw it not worth it.
Click to expand...
Click to collapse
Seriously. I'm still on EL29, and will remain there until all the drama of the FB** releases are sorted out. I've seen far too many people bricking their phone, and without CWM built in yet, it's just too much hassle going back and forth. That said, it's still nice to see some actual Sprint/Samsung dev going on with regards to our phones. It's about time.
schlonky said:
It's good for the flashaholics, though. I'm just happy that we have proof positive that Samsung is working hard on getting ICS up and running on our phone.
Click to expand...
Click to collapse
I am a flashaholic as well. I've wanted ICS for a long time but I kept patient which a lot of people did not. I also need stability as well at times don't get me wrong I'm glad they are working on things but 2 days difference at times does not show much also. that being said I still flashed FB21 lol.
Who cares if the RDF is up, they seem to put one up every 3 days or so.. it doesnt even get released for about 4-5 days after the RDF goes up.
Man, is it ever going to stop!!!
Ugh I hate this
It's good they're working on ICS and all but do we really need to leak every build.
iSaint said:
Ugh I hate this
It's good they're working on ICS and all but do we really need to leak every build.
Click to expand...
Click to collapse
Cmon Saint you already know the answer to that
jasone4gt said:
Man, is it ever going to stop!!!
Click to expand...
Click to collapse
it'll never stop ... unless they stop support for our device pretty sure you wouldnt want that.
dev_man77 said:
Who cares if the RDF is up, they seem to put one up every 3 days or so.. it doesnt even get released for about 4-5 days after the RDF goes up.
Click to expand...
Click to collapse
Not true, FB 21 got leaked and released yesterday, just 2 days after the rdf posted....
iSaint said:
Ugh I hate this
It's good they're working on ICS and all but do we really need to leak every build.
Click to expand...
Click to collapse
Well this isn't a leak .... yet.
I knew it would be like this once it got rolling. Which is why I'm not theming my ICS ROM or putting any real time into setting it up. In fact I've only re-installed/restored a fraction of my daily driver Apps. I've got all that tucked away in my nice little EL29 backup, which I'm 5 minutes away from if I need my phone to be 100% functional. It also makes flashing new leaks once a week easier and more fun.
Those that are bricking their phones, while I definitely feel for them, must be doing something whacky. If one follows tried, true and simple Odin and CWM methods, it's like flashing any other ROM and carries the same minimal risks. Any time I flash, I check the md5s and have a plan on where I want to be and the steps I need to take to get there. Every damn time. A bit of thought and patience can be the difference between a lot of fun and a brick.
Meh I'm fckin rambling. Probably a side effect of my 2yr old getting the flu and puking all night long. I'm tired.
Dchibro said:
Well this isn't a leak .... yet.
I knew it would be like this once it got rolling. Which is why I'm not theming my ICS ROM or putting any real time into setting it up. In fact I've only re-installed/restored a fraction of my daily driver Apps. I've got all that tucked away in my nice little EL29 backup, which I'm 5 minutes away from if I need my phone to be 100% functional. It also makes flashing new leaks once a week easier and more fun.
Those that are bricking their phones, while I definitely feel for them, must be doing something whacky. If one follows tried, true and simple Odin and CWM methods, it's like flashing any other ROM and carries the same minimal risks. Any time I flash, I check the md5s and have a plan on where I want to be and the steps I need to take to get there. Every damn time. A bit of thought and patience can be the difference between a lot of fun and a brick.
Meh I'm fckin rambling. Probably a side effect of my 2yr old getting the flu and puking all night long. I'm tired.
Click to expand...
Click to collapse
totally agree with the Flashing stuff. This is one way I've stayed golden with every build without ever having an issue flashing things.
im going to hang on til there is a stable release but thanks for posting!
schlonky said:
It's good for the flashaholics, though. I'm just happy that we have proof positive that Samsung is working hard on getting ICS up and running on our phone.
Click to expand...
Click to collapse
+1
Some people are flashing junkies, and will love to test it out
I love that they are working on this but what I really hope Is that the leaks help the cm9 dev get things sorted out because I'm. Not moving from gingerbread until things are stable. I also really want to see what ICS Touchwiz will look like after they are DONE.
But for now I'm Perfectly happy on my very stable and fast dark ics themed blend rom!
Sent from my SPH-D710 using xda premium
It's getting a little sad that there is still no credible rumors on an official update for Verizon Nexus Owners. The 4.04 update to GSM owners may have caused some issues for them and Google jumped on it and fixed in a few weeks. Would love for Verizon/Google to show us a little love too.
Nope I already have 4.0.4, and have a ton of customization options that I wouldn't have with stock.
I've been here since December waiting for some bug fixes. Makes me sad really.
Its not on Google, this falls on Samsung/Verizon and their proprietary blobs or whatever the heck you call them, lol
Sent from my Galaxy Nexus using Tapatalk
Nope. I come for the comedy of threads like this.
good day.
Verizon is the holdup, not Google. The only upside is that the firmware for the VZW version will probably not be prone to some of the same problems the GSM version has had due to the extra testing.
It's equally frustrating for VZW Xoom owners. The WiFi-only Xoom got ICS in January. The VZW Xoom is still on Honeycomb. Apparently Google finished the ICS build for it a while ago but Verizon hasn't finished testing because it isn't a priority device for them.
Sent from my Galaxy Nexus using Tapatalk 2
Yes, I visit this forum and a few others to try to get info on the Verizon update. My phone suffers from the audio reboot/one-way audio issue and it's extremely frustrating. I know I can root and flash but I choose to leave my device stock. It's a toss-up as I'd rather wait to have the update properly tested, but the phone part of my phone is almost useless.
Nope. I've been running IMM76D since day one of release. I will be running IMM76I in the next day or so as well, if I get off my butt.
Lucky Armpit said:
Yes, I visit this forum and a few others to try to get info on the Verizon update. My phone suffers from the audio reboot/one-way audio issue and it's extremely frustrating. I know I can root and flash but I choose to leave my device stock. It's a toss-up as I'd rather wait to have the update properly tested, but the phone part of my phone is almost useless.
Click to expand...
Click to collapse
I've always taken a proactive approach to Android phones. I don't look at it as how bug free it is stock, but rather what I need to do to fix it and be happy.
And I am a happy owner.
cordell12 said:
Its not on Google, this falls on Samsung/Verizon and their proprietary blobs or whatever the heck you call them, lol
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Wrong. Google updates the Verizon Galaxy Nexus...it's just that updates have to be approved by Verizon first. Simple as that.
what are you guys doing? waiting around for stock images and ota's? flash cyanogen and be done with it, you'll be up to date and have more customizations than stock anyway ...
blowtorch said:
what are you guys doing? waiting around for stock images and ota's? flash cyanogen and be done with it, you'll be up to date and have more customizations than stock anyway ...
Click to expand...
Click to collapse
I prefer stock myself because I don't like the "everything AND the kitchen sink" mentality of custom ROMs. I like the "less is more" mentality. Plus, stock ROMs may not have quite the performance of a custom, but stock ROMs generally work better as daily drivers because they're more stable. In addition, kernels are a touchy subject for me as well. I sort-of have trust issues with developers writing kernel tweaks for hardware of which they have no documentation. Only OEMs truly know what a device's hardware is capable of and what its limitations are.
I also keep my stock ROM unrooted because root access doesn't really give me any functionality that I'm interested in. I'd basically root because I can, and that's not really very appealing. *shrug*
Different strokes for different folks.
blowtorch said:
what are you guys doing? waiting around for stock images and ota's? flash cyanogen and be done with it, you'll be up to date and have more customizations than stock anyway ...
Click to expand...
Click to collapse
I'm waiting for a rom AND radio update the truly fixes some of the big items. I've been reading on the radios and as far as I've read there isn't a true fix on the radio (voice and data) yet for Verizon CDMA phones.
boe said:
I'm waiting for a rom AND radio update the truly fixes some of the big items. I've been reading on the radios and as far as I've read there isn't a true fix on the radio (voice and data) yet for Verizon CDMA phones.
Click to expand...
Click to collapse
The I515.LA02 radio that comes with the 4.0.4/IMM30B OTA is excellent. Improved my radio noticeably.
boe said:
It's getting a little sad that there is still no credible rumors on an official update for Verizon Nexus Owners. The 4.04 update to GSM owners may have caused some issues for them and Google jumped on it and fixed in a few weeks. Would love for Verizon/Google to show us a little love too.
Click to expand...
Click to collapse
Yes, I prefer stock myself to, however... one of the main reasons I got the Nexus was for "timely" updates.
4 months is not timely when the rest of the world has an android version newer than my "flagship" device!!! I finally got fed up with Verizon's phone support/approval process so I unlocked/rooted/flashed AOKP and franco kernel.
I've never looked back.
oldblue910 said:
I prefer stock myself because I don't like the "everything AND the kitchen sink" mentality of custom ROMs. I like the "less is more" mentality. Plus, stock ROMs may not have quite the performance of a custom, but stock ROMs generally work better as daily drivers because they're more stable. In addition, kernels are a touchy subject for me as well. I sort-of have trust issues with developers writing kernel tweaks for hardware of which they have no documentation. Only OEMs truly know what a device's hardware is capable of and what its limitations are.
I also keep my stock ROM unrooted because root access doesn't really give me any functionality that I'm interested in. I'd basically root because I can, and that's not really very appealing. *shrug*
Different strokes for different folks.
Click to expand...
Click to collapse
Why don't you try a custom ROM first? There are many that are awesome
"daily drivers." I am running Gummy 1.0.1 and it is freaking incredible! The stability is better than stock and you can't tell a difference from stock if you don't change anything in the Gummy settings. Instead of having trust issues with developers, give them a shot and try some of the stuff out.
oldblue910 said:
I prefer stock myself because I don't like the "everything AND the kitchen sink" mentality of custom ROMs. I like the "less is more" mentality. Plus, stock ROMs may not have quite the performance of a custom, but stock ROMs generally work better as daily drivers because they're more stable. In addition, kernels are a touchy subject for me as well. I sort-of have trust issues with developers writing kernel tweaks for hardware of which they have no documentation. Only OEMs truly know what a device's hardware is capable of and what its limitations are.
I also keep my stock ROM unrooted because root access doesn't really give me any functionality that I'm interested in. I'd basically root because I can, and that's not really very appealing. *shrug*
Different strokes for different folks.
Click to expand...
Click to collapse
Cyanogenmod 9 has been stable for months now as they have been focusing on it as a main priority. Not to mention obvious extra features that they have been adding once they have been deemed stable. I use GLaDOS kernel and easily get 3x the battery life and way faster than any stock rom's kernel. Custom kernels like GLaDOS and Lean Kernel never had the "signal drop" issue with 4.0.4 because they patched it in their kernels a along time ago.
Root doesn't add any functionality that you are interested in? Have you heard of LBE Privacy Guard? https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5sYmUuc2VjdXJpdHkubGl0ZSJd
Dev's only improve on stock as far as i am concerned. I donate and support devs because of the enhancements that they make in making this phone better. You are not getting all you can out of your phone if you're on stock ...
like you said to each his own ...
The tools are available for the latest update. If you don't want to take it into your own hands then you really can't complain about it if you're unwilling to fix it yourself.
Sent from my Galaxy Nexus using xda premium
blowtorch said:
what are you guys doing? waiting around for stock images and ota's? flash cyanogen and be done with it, you'll be up to date and have more customizations than stock anyway ...
Click to expand...
Click to collapse
Yes, I am waiting for OTAs. Modifying my primary means of communication scares the crap out me, espeically with the chance of making it a $300 paperweight. I understand that tens of thousands of people modify their Android devices every day without issue, and the risk of bricking is extremely low. However, there is still a risk and due to that, I choose to wait. The reward does not outweigh the risk for me.
I just gotta say this. THERE IS NO REASON NOT TO INSTALL A CUSTOM ROM. NONE. ZERO.
Why do you think android is open source? The arguments against rooting/unlocking and installing a custom rom are laughable. If you run stock, and complain about not being on the cutting edge, you have to realize that this is YOUR choice.
AOKP M5 will be JUST AS STABLE as stock, but with better performance, battery life, customization, etc.
If you are still on 4.0.2/4.0.3 you have nobody to blame buy yourself.
---------- Post added at 05:43 PM ---------- Previous post was at 05:37 PM ----------
Lucky Armpit said:
Yes, I am waiting for OTAs. Modifying my primary means of communication scares the crap out me, espeically with the chance of making it a $300 paperweight. I understand that tens of thousands of people modify their Android devices every day without issue, and the risk of bricking is extremely low. However, there is still a risk and due to that, I choose to wait. The reward does not outweigh the risk for me.
Click to expand...
Click to collapse
If you use the toolkits to root/unlock, and flash custom roms, the risk of bricking your phone is 0%. This is assuming that your phone is not a lemon.
There is NO risk to rooting/flashing custom roms, ZERO. Even if you did something stupid like pull your battery while flashing something, you can ALWAYS restore.
Hi,
I'm from http://forum.xda-developers.com/nex...3-10-zen1-dollar-drink-night-bfs-msm-t3062814 and also on the nexus 9
It's cool to see somebody has noticed -zen kernel in a far off community such as the find 7.
Somebody noticed I mentioned I'd support -zen on a few flagships in addition to the nexus devices.
I explained the hurdle of having 3rd party testing for such a daunting task. My BFS work on android/3.10 has yielded nothing but positive feedback on the N6 and the 64-bit N9.
However, somebody here reached out to me and said "hey support us, we are active but we don't have enough developers here"
I would happily do this but I have observed the find 7 is using a 3.4 kernel. In order to do the work with BFS I will likely have to reboot and flash to it dozens of times per hour, pull logs constantly, test all situations for kernel errors, etc.
Before you say "oh he just wants us to buy him a new phone sick son of a b*&$&$&$"
No not at all, what I need to bring Zen to the find7 (and likely other devices like the N5 and N7 - who I have maintainers for a future BFS patch already in place, they just need the patches) is anybody who is willing to volunteer any 3.4 Linux kernel running android device, with an unlocked bootloader
It can be broken, damaged, hold no charge as long as the screen is mostly legible and runs 3.4, unlocked bootloader, etc. I will probably need no more than 1-2 weeks with it, so if anybody volunteered I will happily send it back to them as soon as I'm done with it.
Somebody here asked me, I told them I can't possibly do it on 2nd hand testing (not that itnisnt greatly appreciated) but for a task like this it isn't ideal. if I get 1 hour to work it's much faster to just do itnall myself and flash maybe dozens of times versus sending test builds and waiting for reply and secondary logs, etc.
Thanks,
B
My endeavor to bring it to the nexus 9, which I do not own was successful but finding testers for that thing was basically impossible. Little interest and little users overall (I almost backed out but since I finished the patch for tegra I released it blindly and it works well)
Someone give this man some help! I want a custom kernel for my Find 7a.
Have you tried the oppo forums? I'd let you use mine if you're in the Chicago/north west Indiana area
wergrun said:
Have you tried the oppo forums? I'd let you use mine if you're in the Chicago/north west Indiana area
Click to expand...
Click to collapse
If he is not living there, would you send it if I would pay for the parcel (both ways)?
Just want to make this happen so badly but this is all I can do as I dont have a device on me I could send ):
znarf2369 said:
If he is not living there, would you send it if I would pay for the parcel (both ways)?
Just want to make this happen so badly but this is all I can do as I dont have a device on me I could send ):
Click to expand...
Click to collapse
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
wergrun said:
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
Click to expand...
Click to collapse
alright just let me know (;
Just to ask quickly, which ROMs would u support with ur kernel? I have tried CM12 and I am now on NamelessROM which I am loving.
I know some kernel DEVs only like to work for one ROM, or only for the stock OS of the device.
Thank u for wanting to work on our device, it seems like all the DEVs went for the OnePlus One, and everyone forgot about the blatantly better Oppo (lolz)
wergrun said:
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
Click to expand...
Click to collapse
found anything so far?
the problem is I really would like to help but my device I could send is in germany (relatively high costs for shipping to usa and back to germany, about 130 $) and I am located in New Zealand right now so even if I would I cant because I dont have any access to the phone..
i would love to test it for you!
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
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.