Related
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
In my experience unless you are using a nexus device aosp roms are never 100% at least not until the phone is at the year/year and a half mark. Now if your talking about camera not working and stuff like that yeah its going to take time especially since only a hand full of devs are working on it in there spare time. On the plus side they will probably have most of the kinks hammered out before L releases and most of the changes and fixes will translate over.
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Jess813 said:
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Click to expand...
Click to collapse
We do have aosp roms.....
ThePagel said:
We do have aosp roms.....
Click to expand...
Click to collapse
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Jess813 said:
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Click to expand...
Click to collapse
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
ThePagel said:
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
Click to expand...
Click to collapse
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Jess813 said:
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Click to expand...
Click to collapse
Somebody will send a request to have a rom reviewed to be added to the official git. It will just take the one person and a little time. If you feel strongly about it you could ask one of the devs working on it to send it to the cm team for review but I bet one of them will after the camera is fixed. whoever does will have there name next to 99% of the commits in the official github so that person will have bragging rights.
Tom Marshall was working on it then intervigilium, who yesterday had some activity on his github and finally invisiblek as well, all with cyanogenmod. Not to mention the actual phone 2 of them are using belongs to...think it was Roman from AOKP. You also have the guys here working on it when they have time. My bet would be a few more weeks and it will be up and running properly.
Good to know, I love this phone however but I'm sure with an AOSP ROM it'll fly!!!
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
coding a new rom takes time and devs work on their own dime as so few here actually donate anything to them. Phones and their hardware are becoming way more sophisticated each year and porting any flavor of rom is no longer something easily done. If people are impatient perhaps they need to open their wallets and give the devs some inspiration.............
Hello all,
Given that Amazon has just slashed the price on what is in reality a powerful phone, what is the likelihood that we could see an unlocked bootloader (from the community) in the near future. CM would really make this phone fly.
I got the Fire Phone, as it was a $100 for me (i consider the 99$ amazon prime that comes with it, like renewing my existing one that expires on Jan 1st anyway).
As an excited developer, I actually am planning to devote time to trying to flash Custom Recoveries (or at least boot them), and getting Android Lollipop on it. Those are my 2 goals. I have no clue if I will achieve them, as this is my first strong attempt at making something custom, but I will try. I have android 5.0 and fireos sources downloaded. I will try to pull all the system level stuff on my phone from it (incase I need drivers or something), and take a stab. If I can get Lollipop stock working, I will then move to CM 12 and do that.
My goal is for 5.x support. If I can pull it off, I don't want to foray into anything less than Android 5.0.
Wish me luck.
As for bootloader unlock, I haven't checked, but it might be as simple as fastboot oem unlock. Here's to hoping.
Great to hear! Thank you for dedicating your time, I am hopping after end of this semester I will be able to join in this endeavor.
Best of luck!
funkybassplayer said:
Great to hear! Thank you for dedicating your time, I am hopping after end of this semester I will be able to join in this endeavor.
Best of luck!
Click to expand...
Click to collapse
Just a heads up, the bootloader is locked down pretty tight. Unlocking it will require finding and using an exploit. there is a guy on the HDX forum that found an exploit for that Tablet that would work for the Fire Phone, but he decided for legal reasons to not release it anywhere, so both devices are in limbo. Wish i knew even at which exploit to look into and I would do the rest myself.
if it is locked so tight, what is the point of giving away as open source
Daegalus said:
As for bootloader unlock, I haven't checked, but it might be as simple as fastboot oem unlock. Here's to hoping.
Click to expand...
Click to collapse
lol, you must be joking.
dimex said:
lol, you must be joking.
Click to expand...
Click to collapse
Umm, no, not at the time of that post. If you read the post i made after that, you would have seen that I actually checked and found out it wasn't the case. Way to jump the gun.
Daegalus said:
Umm, no, not at the time of that post. If you read the post i made after that, you would have seen that I actually checked and found out it wasn't the case. Way to jump the gun.
Click to expand...
Click to collapse
If it was as simple as a 'fastboot oem unlock' we wouldn't be here half a year later discussing this to begin with. All I'm saying, of course that wasn't going to work.
Glad you're attempting this. If I can help, please let me know. Unless people smarter than me can unlock the bootloader, you might be creating one great virtual machine that won't make it to this nice piece of hardware.
I bought this phone to learn more about the same things you plan to do. I dislike the fireos (and the glitches in the use of the side-loaded gapps) enough to return the phone, but the cheap price, dreaming of a decent OTA update in January, and folks like you working on it makes me think I'll hang on to it as a backup.
I just got a fire phone as well. Hope this forum will get more traction as Amazon release its FireOS source...
"My name is 4.1chan, I will hack this device because I am great developer. Trust me, I took a Jawa class in Kindergarten and passed."
Seriously though, can't see this happening any time soon. You need experienced people, not someone who says they can do it even though they don't even know the boot loader is locked like Ford Knox. Big talk has always led to big disappointment in my experience on xda-developers. Don't get your hopes up, the phone is basically rubbish as it is (even more with simlock), so don't just buy because it is cheap.
Agreed, I am not expecting much on the unlocking front. If it happens great, if not oh well. But I would not call this phone rubbish, it's fast cheap and runs everything I need perfectly. Sure it doesn't have that perfect Android feel, but who cares. Plus the auto scroll feature is pretty handy.
The phone's spec is great for the $200 unlocked price but NO ROM, NO BUY MAN.
funkybassplayer said:
Agreed, I am not expecting much on the unlocking front. If it happens great, if not oh well. But I would not call this phone rubbish, it's fast cheap and runs everything I need perfectly. Sure it doesn't have that perfect Android feel, but who cares. Plus the auto scroll feature is pretty handy.
Click to expand...
Click to collapse
Agreed! An excellent phone for $100! Can't beat that price. Runs what I need as well once you install Google framework, services and play store.
Sent from my Nexus 6 using XDA Free mobile app
*sigh* nevermind, I just leave this here, since THIS is a thread about the bootloader (thanks for trying, Mod. ^^)
Viperise152 said:
http://www.xda-developers.com/kindle-fire-hd-6-and-7-receive-bootloader-unlock-and-twrp/
Will this help us Fire Phone users?
Click to expand...
Click to collapse
Eiermann78 said:
I already tried this and CuberHDX.py, too but it fails with Unlock Code is NOT correct
Maybe the Steps would be right, but i don´t know how to figure out the correct code for the fire phone.
Tested at Fire OS 3.5 and 4.6.1
Click to expand...
Click to collapse
@ Viperise152 & Eggmän78 Sadly: No, it won't help. The unlock for the 6" and 7" is based on the HDX bootloader unlock method. This vuln. was already fixed for the FirePhone by Amazon.
https://android-review.googlesource.com/#/c/117742/
There's no exploit example, but maybe there's a new hope for getting root on the Fire TV Stick and newer Fire TVs. Can anyone confirm the Fire TV has the vulnerable code?
This is very exciting! Crossing my fingers!
Oh boy. This one is BIG. If the Fire TV uses this library, it's just a matter of time.
http://www.cvedetails.com/cve/CVE-2015-1474/
Exciting news!!!
Sizzlechest said:
Oh boy. This one is BIG. If the Fire TV uses this library, it's just a matter of time.
http://www.cvedetails.com/cve/CVE-2015-1474/
Click to expand...
Click to collapse
But if I read this right this affects only 5.0 devices. And AFTV is not 5.0 AFAIK.
Ultraschorsch said:
But if I read this right this affects only 5.0 devices. And AFTV is not 5.0 AFAIK.
Click to expand...
Click to collapse
You didn't read it right. It affects 5.0 and below.
Sizzlechest said:
You didn't read it right. It affects 5.0 and below.
Click to expand...
Click to collapse
Yes, I read through the Android 4.4 sourcecode. The bug is already there. Unfortunately I am no CXX and security expert, so I hope someone else writes an exploit. Should not be too hard.
Not to discount any other dev, but rbox seems to be the guy that would know if its poossible. He seems to be the man when it comes to the Fire TV. Why not just ask rbox? He can probably give you a straight foward answer and you wouldn't have to speculate anymore. Just ask rbox, cause I am pretty sure he would know if it would work.
porkenhimer said:
Not to discount any other dev, but rbox seems to be the guy that would know if its poossible. He seems to be the man when it comes to the Fire TV. Why not just ask rbox? He can probably give you a straight foward answer and you wouldn't have to speculate anymore. Just ask rbox, cause I am pretty sure he would know if it would work.
Click to expand...
Click to collapse
You mention @rbox so many times, but you don't really mention him at the same time. Want his attention? Mention @rbox
its still not going to fix the efuse. amazon really lost my support when that happened.. fireTV is a bedroom box now and i've moved to the 100$ M8 amlogic box running openelec.. if you want something for pure XBMC this is a much better option and fully supports different refresh rates.
Right it won't fix the efuse but I'm pretty sure that I'm not the only one still using the old firmware without efuse and hoping for software root...
gamer765 said:
You mention @rbox so many times, but you don't really mention him at the same time. Want his attention? Mention @rbox
Click to expand...
Click to collapse
I do not want his attention at all. I was simply informing people that if they wanna a quick reliable answer that rbox would probably be the one to ask. I have said several times that I could care less about rooting my Fire TV. I just know how these threads pan out, they usually end up in arguements over wheather or not its possible, so I was trying to give them a quick solution to their question. If they wanna now if its possible they could probably get an answer from rbox and there would be no more speculation and nobody would have to eventually get mad when someone says it won't work. He is a reliable source so why wouldn't they wanna ask him? If I mention him it means I mentioned him period. Yes I mentiond him, cause without a doubt he is probably considered the top dev for the Fire TV. No harm in mentioning him or trying to point people in the right direction to ge an answer. If they ask him today and he responds with a definative answer today, they have their answer and there will be no more wondering.
From what I read, this alone isn't enough to gain root. You need to combine this with other exploit(s) to get it. I've read that there is a forthcoming proof of concept that uses it. So we just have to wait and see. But... hope is not lost totally for people with the fire tv with the fuse blown. Before I had the unlock working, I was working on safestrap for the fire tv. Safestrap allows you to boot to recovery with a locked bootloader. So if this results in root for the newer firetvs with the blown fuse, making a safestrap package is a possibility. No promises on when or if it would actually happen. As for that happening with the stick... highly unlikely (from me) because it's a completely different architecture from the Fire TV.
rbox said:
From what I read, this alone isn't enough to gain root. You need to combine this with other exploit(s) to get it. I've read that there is a forthcoming proof of concept that uses it. So we just have to wait and see. But... hope is not lost totally for people with the fire tv with the fuse blown. Before I had the unlock working, I was working on safestrap for the fire tv. Safestrap allows you to boot to recovery with a locked bootloader. So if this results in root for the newer firetvs with the blown fuse, making a safestrap package is a possibility. No promises on when or if it would actually happen. As for that happening with the stick... highly unlikely (from me) because it's a completely different architecture from the Fire TV.
Click to expand...
Click to collapse
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
E--Man said:
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
Click to expand...
Click to collapse
I had googled the CVE number and found a thread on one of the samsung forums here that they were discussing it.
E--Man said:
RBox, thanks for chiming in. Many of us are hoping for a FireTV Stick root. I guess we'll have to wait and see like you said. Hopefully we'll hear something soon! Any particular forum we can keep an eye on besides this one?
Click to expand...
Click to collapse
This thread is full of Samsung Note 4 users salivating for a new root exploit: http://forum.xda-developers.com/note-4-att/general/galaxy-note-4-root-progress-t2961974/page111
Sizzlechest said:
This thread is full of Samsung Note 4 users salivating for a new root exploit: http://forum.xda-developers.com/note-4-att/general/galaxy-note-4-root-progress-t2961974/page111
Click to expand...
Click to collapse
Ahh yes, because the AT&T ones come with a locked Bootloader I heard about that... They (we) all deserve it too because we paid for the device!
If the method to root is similar *and* it is possible, then its just a matter of time...
Watch defy. Closed bootloader is sad.
But no Problem at all.
2nd init is long time happened
We need the right dev.
Quarks is the superman
Sent from my Nexus 4 using XDA Free mobile app
E--Man said:
Ahh yes, because the AT&T ones come with a locked Bootloader I heard about that... They (we) all deserve it too because we paid for the device!
If the method to root is similar *and* it is possible, then its just a matter of time...
Click to expand...
Click to collapse
Just because you buy a device does not mean that you deserve to be able to do something that the makers of it never intended it to do. Its like someone goin out and buying an RX7 and saying it deserves to go faster than a Lambo. Any mildly intelligent person would have never bought the Mazda if they wanted it to outrun a Lambo, cause they would know ahead of time its not made to outrun a Lambo. I can understand why people wanna root. I even have rooted devices, but to get mad because you cannot root a device makes zero sense. You knew Amazon did not want you to root it before you bought it, so why complain now? You deserve many things in life simply by being human, but a rooted Fire TV is not on the list of things that anyone deserves. Look at it like this, if root never comes too the newer firmwares, you will forget about when you buy your next device. I must admit I was kinda irked when I read that some Fire TVs cannot be rooted, but i took my chances and bought it anyway, and now I have a nonrootable device, and its absoluely not a big deal. I knew ahead of time what I was getting into and if I get root one day that will be fine, but if I don't I am still fine wiith that too. My Fire TV does everything I need it to do without root so its really not a big deal. I have noticed after I got a little older that the alure of cool apps and cool mods have worn away. I no longer care how cool my Android devices look or what cool tweaks I can use, I simply just want a device that does what its supposed to do. I have done so much "cool stuff" on Android devices that I am actually burnt out. I don't even carry my cell anymore. I have a Galaxy Note that has never been outside except for when UPS dropped it off. Trust me, not having root for your Android device is not gonna have any negative effects on your life if it does not happen.
porkenhimer said:
Just because you buy a device does not mean that you deserve to be able to do something that the makers of it never intended it to do. Its like someone goin out and buying an RX7 and saying it deserves to go faster than a Lambo. Any mildly intelligent person would have never bought the Mazda if they wanted it to outrun a Lambo, cause they would know ahead of time its not made to outrun a Lambo.
Click to expand...
Click to collapse
That is a terrible example. Since we buy the devices we should be able to do what we want with them, similar with cars. We buy cars and since we bought them, we can customize them as we wish. Last I checked, there was nothing in place from stopping me from popping the hood open and doing what I wish with the engine or interior.
Your poor example is akin to saying I bought a cheap outdated phone like an Alcatel and saying it deserves to be faster than an HTC One M8. Learn to troll better.
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