Related
Edit: its been reported that at&t is indeed blocking the unlock for their version of this device.
The release of the One X has us all very excited, and there is much reason to be excited. Yet, I feel like many people don't really understand some of the issues we may be up against. Let's take into account some recent HTC phones that came out. Let's look at the Vivid and Rezound. Both of these devices did not have the option to unlock the bootloader until months after. In fact, HTC was not even planning on talking about releasing the unlock until 6 months or later after initial release of the device. We started petitions, spammed the twitters and facebooks of AT&T/Verizon and HTC. It was amazing how each just blamed eachother for the locked bootloaders. Keep in mind this was AFTER the CEO of HTC promised no more locked bootloaders. Samsung does not ship locked bootloaders either. After a few months of begging and pleading, we eventually got official HTC dev unlock. But by that time, most the devs and community were gone.
We had a few teams working very hard on cracking the Vivid/Rezound but to no avail. Apparently HTC upped their game compared to past devices, and to this day we still don't even have unofficial bootloader unlock, s off, sim unlock, etc. On AT&T, the Vivid was one of the best spec'd devices, if not the best, out at the time. Yet, due to the actions of HTC/AT&T, the development was absolutely screwed. At this point in time we have only three or four devs with ROMs, no doubt we would have had tons more if not for the locked bootloader issues.
We need to talk with HTC before the release of this device to make sure the One X doesn't get screwed as bad as the Vivid did. You guys don't know how much it sucks to wait months and months to even put a custom ROM on your phone. We need to hold HTC to their promise. Sure, we can rely on unofficial methods, but then there's always that "what if" factor if nothing happens there.
EDIT: Willyami found this, I'm happy to hear temp-root is already achieved. Yet the article still states we need bootloader unlock or S OFF for perm root...
http://www.engadget.com/2012/03/08/htc-one-x-gets-rooted-before-retail-debut/
http://www.engadget.com/2012/03/08/htc-one-x-gets-rooted-before-retail-debut/
The One X is already rooted by Modaco. So I do believe this wont be such a problem to One X.
slapshot30 said:
The release of the One X has us all very excited, and there is much reason to be excited. Yet, I feel like many people don't really understand some of the issues we may be up against. Let's take into account some recent HTC phones that came out. Let's look at the Vivid and Rezound. Both of these devices did not have the option to unlock the bootloader until months after. In fact, HTC was not even planning on talking about releasing the unlock until 6 months or later after initial release of the device. We started petitions, spammed the twitters and facebooks of AT&T/Verizon and HTC. It was amazing how each just blamed eachother for the locked bootloaders. Keep in mind this was AFTER the CEO of HTC promised no more locked bootloaders. Samsung does not ship locked bootloaders either. After a few months of begging and pleading, we eventually got official HTC dev unlock. But by that time, most the devs and community were gone.
We had a few teams working very hard on cracking the Vivid/Rezound but to no avail. Apparently HTC upped their game compared to past devices, and to this day we still don't even have unofficial bootloader unlock, s off, sim unlock, etc. On AT&T, the Vivid was one of the best spec'd devices, if not the best, out at the time. Yet, due to the actions of HTC/AT&T, the development was absolutely screwed. At this point in time we have only three or four devs with ROMs, no doubt we would have had tons more if not for the locked bootloader issues.
We need to talk with HTC before the release of this device to make sure the One X doesn't get screwed as bad as the Vivid did. You guys don't know how much it sucks to wait months and months to even put a custom ROM on your phone. We need to hold HTC to their promise. Sure, we can rely on unofficial methods, but then there's always that "what if" factor if nothing happens there.
Click to expand...
Click to collapse
Absolutely agree with you dude. As a result of so few devs over there, I still haven't unlocked and rooted my Vivid.
Sent from my HTC Vivid using XDA app
i think people need to enjoy the phone a bit more, than thinking about custom roms and such. That's certainly not why im buying the phone, nor is it in the discussion. Maybe months or a year i would be open to it, but right now i can see myself enjoying it stock. Especially with ICS on board.
uranis said:
i think people need to enjoy the phone a bit more, than thinking about custom roms and such. That's certainly not why im buying the phone, nor is it in the discussion. Maybe months or a year i would be open to it, but right now i can see myself enjoying it stock. Especially with ICS on board.
Click to expand...
Click to collapse
Yeah, maybe for you. But this is a development site. we're here to develop and make the device as badass as possible. The phone will be enjoyed for sure. but enjoyed more with it rooted Running a CoreDroid Rom
uranis said:
i think people need to enjoy the phone a bit more, than thinking about custom roms and such. That's certainly not why im buying the phone, nor is it in the discussion. Maybe months or a year i would be open to it, but right now i can see myself enjoying it stock. Especially with ICS on board.
Click to expand...
Click to collapse
I think a majority of the people here would agree, the ability to customize your phone beyond what the manufacturer intended is your right as a consumer....you bought the phone...right.... also I might add, a majority of the people on this website are here for rooting information and custom roms.... it is after all, a development based forum. I think this thread should be closed though, because its been noted above that the one x has been rooted.
williamyi said:
http://www.engadget.com/2012/03/08/htc-one-x-gets-rooted-before-retail-debut/
The One X is already rooted by Modaco. So I do believe this wont be such a problem to One X.
Click to expand...
Click to collapse
Damn, nice find. I still wonder how HTC will do with the official unlock though. They are really laggy when it comes to releasing code too.
uranis said:
i think people need to enjoy the phone a bit more, than thinking about custom roms and such. That's certainly not why im buying the phone, nor is it in the discussion. Maybe months or a year i would be open to it, but right now i can see myself enjoying it stock. Especially with ICS on board.
Click to expand...
Click to collapse
lol easier to talk the talk than walk the walk. I had the same mindset you did, but two/three months of the same old thing and same old sense really sucked. Try it if you don't believe me.
420kushking said:
I think a majority of the people here would agree, the ability to customize your phone beyond what the manufacturer intended is your right as a consumer....you bought the phone...right.... also I might add, a majority of the people on this website are here for rooting information and custom roms.... it is after all, a development based forum. I think this thread should be closed though, because its been noted above that the one x has been rooted.
Click to expand...
Click to collapse
Yea it's your choice, but the phone isn't even out yet. I just don't understand buying a phone because of what rom you could possibly get on it. Just my opinion.
Unfortunately, that is only temp root. It is not a permanent root solution. This link is the exact method described in the article and its from this forums dev section.
http://forum.xda-developers.com/showthread.php?t=1562470
Sent from my HTC Vivid using XDA app
uranis said:
Yea it's your choice, but the phone isn't even out yet. I just don't understand buying a phone because of what rom you could possibly get on it. Just my opinion.
Click to expand...
Click to collapse
A HUGE factor that goes into what phone I buy is how big the potential is for development. I think that's a pretty common thing to look for for most XDA'ers.
420kushking said:
I think a majority of the people here would agree, the ability to customize your phone beyond what the manufacturer intended is your right as a consumer....you bought the phone...right.... also I might add, a majority of the people on this website are here for rooting information and custom roms.... it is after all, a development based forum. I think this thread should be closed though, because its been noted above that the one x has been rooted.
Click to expand...
Click to collapse
That's temp root, not perm root. The article states we still need S OFF or htcdev unlock for perm root.
slapshot30 said:
A HUGE factor that goes into what phone I buy is how big the potential is for development. I think that's a pretty common thing to look for for most XDA'ers.
Click to expand...
Click to collapse
Yeah that's what I look for. I was lucky for getting a captivate a while back, it was my first android device and I loved doing the customization. I'll be happy with this phone but I'm really looking forward to the development.
slapshot30 said:
Damn, nice find. I still wonder how HTC will do with the official unlock though. They are really laggy when it comes to releasing code too.
Click to expand...
Click to collapse
HTC have already released the source code to the Sensation ICS kernel, and it's not even properly rolled out yet. Doesn't seem laggy to me
Calm down dude!
HTC learned the hard lesson of Sensation/sgs2.
They losed 3 months of potential buyers (and that made the whole difference in sales volume) because they locked the bootloader.
sgs2 won because it was unlocked and rooted easily.
The HTC One X is already rooted thanks to Modaco, so no need to worry at all, also Mike did a custom rom already,there are many Sensation devs switching to One X...
Another pro argument might be that this will be a real flagship device. As we all know, htc released much too many phones in 2011 (close to 50 I heard in an xda-tv episode ) and they realized the problems that come with such an approach.
The vivid or the rezound might just have been skipped by most devs, some of the better are even still on the 2 year old HD2.
I really hope that this will be the next HD2, it's got all the potential to be the next best phone ever.
I believe that HTC are changing and learning. If you see the communications between them and XDA over the last year, if you see the HTCDev site, if you see the list of ICS updates, if you see the API's they are releasing, etc.
If you look at this http://www.youtube.com/watch?v=eCXgL7MDsIc Jeff clearly says it will be unlocked.
Also I agree with their reasoning for locking the boot loader, and as long as they release the unlock tool I think its a good process to ensure only those who know and accept the consequences will use it.
PS. Also the HTC One X is not tied to a partner so it should give HTC full control of what they do with it. Were as the HTC One XL is tied to AT&T so it may mean for that device its more complicated a process to get AT&T to agree to unlock the boot loader.
The "One" series must have been made for something, didn't they say they are trying to make their phones more recognisable too? In that case, it makes perfect sense to not release 50 phones a year (or one every week), as that really tarnishes the brand
i've never unlocked a phone on htcdev, but it has a generic unlock option.
you have to submit an identifier token you can query with fastboot, and you are getting a unlock binary sent by email which you can flash with fastboot to unlock the phone. if the hboot of the phone supports this.
seems very generic to me, and i guess you can already unlock a htc-one device using this method
Edit: Ops! I am wrong... please see later posts! Sorry blubbers!
vegetaleb said:
Calm down dude!
HTC learned the hard lesson of Sensation/sgs2.
They losed 3 months of potential buyers (and that made the whole difference in sales volume) because they locked the bootloader.
sgs2 won because it was unlocked and rooted easily.
The HTC One X is already rooted thanks to Modaco, so no need to worry at all, also Mike did a custom rom already,there are many Sensation devs switching to One X...
Click to expand...
Click to collapse
A custom rom means nothing. Did you even read the article or my post?? It says you still need s off or bootloader unlock for permanent root. Modaco only found temp root.
Sent from my HTC PH39100 using xda premium
Hi all.
Wondering if anyone is considering devving for CM on the HTC One X?
It looks as though the Asus Transformer Prime (Tegra 3) has nightlies http://download.cyanogenmod.com/?device=tf201&type=nightly
so there is some hope, in terms of CPU support.
I think HTC are a little less sluggish in releasing source too these days? Which bodes well.
Please use the poll to show support, would be interested to know how people feel about CM on the One X, personally I really hope it happens!
Well it looks as though people want a ROM, any devs care to volunteer?
I will be glad if that ROM will rise !
HOX without cm would be very disappointing....
Anyone have any news on the likelihood of a CM9 build for the HTC One X?
Think we just have to wait and see how popular the phone is first :-(
Sent from my HTC One X using xda premium
The phone will be popular, no question.
It's not a matter of if there is a CM9 build - just when.
M.
CM developers have one rule... one rule only... don't ask for ETA, you aren't asking that but they never seem to reply to us asking if a certain phone will be supported... Anyway seeing as the One X is a flagship device it will definitely be getting sometime... but for now i don't give a ****e about ROM's, i only care about the phone getting Revolutionary boot unlocker and root
I'd love CM on the phone. Came to it from an SGS II, and I really miss CM9.
I have test a long time CM7 on my SGS 2.
I was very surprise before that i don't know how look stock android.
CM is fast but have some problem with my carradio using my SGS 2 with USB.
Sense working good with it i hope a CM9 on Hox would not have the same problem.
Is anyone working on it?
Ive already started working on CM9 for the One S. However, HTC is slow with releasing the kernel source, making the job much much harder. If we are lucky, HTC will get around and help us out, if not, it might take a while before things are working.
Untouchab1e said:
Ive already started working on CM9 for the One S. However, HTC is slow with releasing the kernel source, making the job much much harder. If we are lucky, HTC will get around and help us out, if not, it might take a while before things are working.
Click to expand...
Click to collapse
Well, thank you very much. Now that I know I won't stuck with a stock rom, I might just take advantage of TMO's upgrade offer.
Again, we are dependant on the kernel source and even then the imageSense.chip drivers probably won't be released. There's some useful stuff on CodeAurora for it though so with time I'm sure we will figure it out
Sent from my HTC One S using Tapatalk 2
As long as WiFi, Pandora, and Firefox work, I'm good to go. I've probably taken about 40 pictures with my G2 that's two years old. I deal in data more than graphics. All I need are my tunes and slashdot fix ;-)
As soon as SWMBO signs off on the upgrade, I'll be ordering. I'll need to wait until after Mother's day, though. That's gonna take some cash
http://android.modaco.com/index.php...d-9-|-Boot,-Graphics,-Bluetooth,-Wifi-working
I posted on CM wondering the same thing. Hopefully it happens pretty soon; we do need a s-off exploit though before a CM rom.
we do need a s-off exploit though before a CM rom.
Click to expand...
Click to collapse
Correct S-off is gonna be needed.
Just give it some time it will come.
i used CM on my Droid 1 sometimes, but phone cams have been improved and customized a lot since then. is CM usually/always using a generic camera or do they include HTCs?
vallandil said:
Correct S-off is gonna be needed.
Just give it some time it will come.
Click to expand...
Click to collapse
Why? We can flash both custom kernels and roms with s-on (as long as it's unlocked through htcdev, ofc), right? Then why would we need s-off? Sure, it would be really nice to have, but it's not needed to get CM on our device.
Correct me if Im wrong.
Hi guys, I have been on this forums for quite a while even though I don't own a Nexus myself. I have been browsing through the development section every day and looking at all the ROMs etc..
I know that everything is open on the Nexus, all the sources, drivers, etc. I know that the advantages of having a Nexus is stock experience, with faster updates directly from Google. But what is the advantage of having an open phone as a user? I don't find much difference between the ROMs for Galaxy S II and the ROMs for the Galaxy Nexus. In fact the Siyah kernel, i think, has many many more features than the most popular kernel on this forums, the Franco kernel.
I am not trying to spark up anything over here. I just want to know what is the benefit of having such an open phone?
Difference between being in a wheelchair in a jail cell, even a jail cell with a window and open field sunny day with your legs running however fast you can. Its like that.
let it be.
@rbiter said:
Difference between being in a wheelchair in a jail cell, even a jail cell with a window and open field sunny day with your legs running however fast you can. Its like that.
let it be.
Click to expand...
Click to collapse
I would think that, but I can't see that translating to development. I mean, I must be blind to not be able to see the differences, but I really can't. I don't see any major improvements in the ROMs on the Galaxy Nexus
darkgoon3r96 said:
I know that the advantages of having a Nexus is stock experience, with faster updates directly from Google.
Click to expand...
Click to collapse
You answered your own question.
I already had 2 not Nexus Samsung phones and I will never make this mistake again. The lack of updates, the crappy skin that tries to look as the iPhone, etc.
In my experience, the builds from Google are much more stable, fast and reliable. And nothing in TouchWiz add anything that matters to me. To me Android is Nexus, I dont think I will build anything that is not Nexus again (but I really hope that HTC build the next one, I love the build quality of their phones).
martonikaj said:
You answered your own question.
Click to expand...
Click to collapse
Haha, that wasn't my question. I am not asking why the Nexus is a better device. I am asking how does opening up the sources and drivers improve on the development...
darkgoon3r96 said:
I would think that, but I can't see that translating to development. I mean, I must be blind to not be able to see the differences, but I really can't. I don't see any major improvements in the ROMs on the Galaxy Nexus
Click to expand...
Click to collapse
Sorry man, but in my opinion the stock ICS on the GNexus is miles ahead of any build from the SII.
martonikaj said:
You answered your own question.
Click to expand...
Click to collapse
The difference is some stuff on aosp
Roms still don't work on galaxy s2 but everything works on aosp roms on nexus because it's open and drivers and everything is available...
bottom line aokp cm9 etc will give u a better user experience on nexus fewer bugs
Sent from my Galaxy Nexus using Tapatalk 2
darkgoon3r96 said:
Haha, that wasn't my question. I am not asking why the Nexus is a better device. I am asking how does opening up the sources and drivers improve on the development...
Click to expand...
Click to collapse
Because your Galaxy Nexus comes with stock ICS out of the box. Sorry, but a custom ROM will never be as smooth and nice as the native out of the box OS.
juliano_q said:
Sorry man, but in my opinion the stock ICS on the GNexus is miles ahead of any build from the SII.
Click to expand...
Click to collapse
I still don't get why you guys think the Stock is so much better than AOKP? I mean, isn't that very similar to stock?
OK, let me see if I can answer it. I'm not a developer, so take it with a grain of salt.
The phone I had before this was the Samsung Captivate. I bought it August 2010. At the time, it was one of the more advanced phones on the market. However, within about an hour of using it, I realized that the AT&T bloatware was a problem. Though the device had a lot of memory available, the app drawer was harder to navigate because of 15 different AT&T apps on the phone, most of which charged a monthly fee to do what Google's equivalent apps did for free. So, I had to root it.
Things were fine for a couple weeks, but then I noticed that there were several apps that I couldn't download because everyone was on Froyo and I was stuck on Eclair. There was no word when either samsung or AT&T was going to provide me with an update, so I had to take matters into my own hands and get a ROM from someone else. I'm not saying the devs didn't do a good job, but they were hamstrung by both AT&T and Sammy who were not giving them the tools they needed to do the job right the first time.
I should also point out that a lot of these problems were caused by AT&T's insistence that they have their own version of the Galaxy S that was different from everyone else's. Thankfully, all the carriers learned from that mistake.
Over the course of a year and 8 months, I tried at least a dozen different ROMs on my phone to either try to keep up with the changes in the market, or just to keep it from freezing. Even stock Gingerbread had problems, likely because it was rushed out. I finally found a stable build in a ROM that used ICS (ironically, ported from the GNex). So that meant, if not for the great work of Team ICSSGS, my Captivate would NEVER have been a stable phone. All those commercials about being a smartphone beta tester seemed to be designed with the Captivate in mind.
The point of all this: When it came time for me to get a new phone, I was considering waiting for the GSIII, but then Google offered the GNex off contract for $400, a not unreasonable price for the hardware at all, but what I was really paying for was getting off the treadmill. Now granted, at this point I've only had the phone for about a week, but it performs every function I need it to, and AT&T has no say in it. Samsung only had a say in the hardware. And that's how it should be, and honestly why I think Apple had such a marketing edge for such a long time. Apple told AT&T exactly where they can shove their customizations, and now we have Google doing the same, but not publicizing it enough.
TL;DR: Google experience and faster updates. But those are more valuable than you think.
darkgoon3r96 said:
I still don't get why you guys think the Stock is so much better than AOKP? I mean, isn't that very similar to stock?
Click to expand...
Click to collapse
You just answered yourself... great roms/builds like aokp would not be possible without the Android Open Source Project. Even after saying that the quality on aosp devices running aokp like the gnex and ns are miles ahead of say the sensation or something along those lines due to the very face the the nexus phones have open source readily available.
Sent from my Maguro Yakju
The open let's you literally change ans re-code any part of the device you want. A touch wiz phone cannot do this cause the code is closed.
Custom roms on other devices are not the same though you may think they are. Most of the time something doesn't work cause it relies on a closed touch wiz framework function that has to be reverse engineered or hacked, or usually never works at all..
You need the kernel source code to really make any legit custom rom, and often have to wait months foe it to be released.
With an open device, you literally can implement anything your imagination can cone up with. No bugs or work a rounds.
In my opinion, there are two major differences:
1. On a Nexus device, you are guaranteed a large developer community. The SGSII may have a large developer community, but that's because it's pretty much of the most popular phones. If you buy something like the Samsung Galaxy Infuse (which several of my friends have) then you won't have nearly as big a developer community as the one for the Galaxy Nexus.
2. It's much much easier to root/customize/flash a Nexus device than any other device. All you need is "fastboot oem unlock" and the phone opens up for you. No need for bootloader downgrading/rooting exploits/HTCDev/manufacturer restrictions. This phone is designed to be a developer device. Also, when you screw up a Nexus, it is much easier to solve problems. Phone not booting? Use CWM. Recovery borked? Fastboot. Fastboot not working? ODIN flash. Lots of fail-safes.
Thanks a lot guys for taking the time just to help me out
I got my gnex last wednesday. No regrets at all, it's an amazing phone. My next phone will definitely be another nexus.
Advantage of having a Nexus?
It is like Burger King, you can have it your own way.
I'm going to get the G3 on late June or July,but I'd like to install CyanogenMod!
Anyone knows when I'll be able to do that?
Sure I predict July the 15 th 2055.... Come on they haven't even released to us .... And the bootloader may be locked so you may never have cyanogen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Sure I predict July the 15 th 2055.... Come on they haven't even released to us .... And the bootloader may be locked so you may never have cyanogen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Do you really think we won't be able to install Cyanogen? ¬¬''
you have to keep in mind the device still doesn't even have a custom recovery yet(neither has it been released worldwide) and lg put in some interesting things on the phone, other than the fact the bootloader is locked(just like the g2, g pro2, g flex, etc) there seems to be some more partitions in there(2 bootloaders, 2 root checking related partitions, etc) the g3 is going to be a tuff nut to crack and it will take some time for development to move the way people would like it to especially in the custom rom department, and we can expect that after the us/uk variants launch we will see some progress but if you want the device for aosp then get a nexus
This surely must be closer. Custom recovery is now available (if I am correct) ....
Any news?
TylerDurdenK said:
This surely must be closer. Custom recovery is now available (if I am correct) ....
Any news?
Click to expand...
Click to collapse
Custom recovery is not yet available. The T-Mobile variant bootloader came factory unlocked, so they will have TWRP shortly and custom AOSP/AOKP ROMs and kernels soon, but none of the other models yet. It could be next week, could be next month, could be next year for the rest of us.
I'm hopeful that it will be within the month, it seems like quite a few devs are attacking it. They're starting with universal root first though, so we'll just have to be patient.
Any news?
kamzata said:
Any news?
Click to expand...
Click to collapse
keep an eye on this forum
hello00 said:
keep an eye on this forum
Click to expand...
Click to collapse
Thank you. I keep the eye on it from lots of days but nothing seems to appear. I'm impatient because stock rom is very buggy and laggy. Thank you all guys work on it.
kamzata said:
Thank you. I keep the eye on it from lots of days but nothing seems to appear. I'm impatient because stock rom is very buggy and laggy. Thank you all guys work on it.
Click to expand...
Click to collapse
More than Cyanogen? Let's get real, except for the Nexus Cyanogen is usually pretty buggy even after multiple releases and I never thought it adds any particular value to my experience... Well, except for some weird looking icons and strange choice of color schemes. Sure, if you are into theming your phone there may be something there for you, but the first thing I do with any phone is install a plain black background, select white fonts and move on. If you feel the launcher is buggy there is Nova or apex.
TheBestEver said:
If you don't like CM why comment in a thread about them?
Click to expand...
Click to collapse
And where do you suggest I post my opinion about CM if not in a CM thread? You like it I don't. I stated my reasons, you stated yours. why do we have to agree?
TheBestEver said:
Well said
Click to expand...
Click to collapse
nobody need to agree. Just like to know, dev working a G3 intl version of cyanogen mod. END. haha..
Please reply or add your request to the CM forums.
Here is my request post:
http://forum.cyanogenmod.org/topic/99629-request-cm-for-lg-g3-lgls990/
and now with 'bump' will this work to bump CM for G3?
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