http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
mauricehall said:
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
CM9 will come with root access turned off (from the rom) by default. There is a new option so that you can turn root on be it for
Disabled,
Enabled for ADB only
Enabled for Apps only
Enabled for both.
That's all this really is.
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
CharlyDigital said:
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
You CAN enable ADB root using ADB which almost seems like a security flaw ADB root access is off by default as well.
But from what I have read ADB will not be required to set this. It just has to be changed by the user from the development options.
I have been wondering about this for a looooooong time. When we root our devices we are voluntarily opening up the biggest hole possible. I'm glad to see it addressed in such a practical manner.
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
....maybe it's just the devices you've owned?
Ask someone with an OG droid, or someone with an Evo, or a Hero, or a GSM Samsung Anything....Hell, CM7 is fantastic on my Nook Color....Cm9 is too, though--I don't remember--I think It's a kang....
The only issue I've had has been with CDMA Samsung handsets...
EDIT: I guess what I mean to say is, there is so much to support that unless you have one of the heavily supported (or easily supported) devices then the fact that it boots up and works at all should be impressive enough.....On all the above mentioned devices I had a nearly flawless experience far preferable to stock....and even with the CM7 kangs (though I haven't tried the CM9s yet). I'm not so sure we'll ever get official support at this rate, though I'm not convinced that's a death sentence. Bubby's Cm7 was working nearly flawlessly for me, aside from a scant few mildly irritating bugs....
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
I saw nightlies left and right on my OG Evo and though the E4GT may not get official CM7 support, We'll surely get offical CM9.
They couldn't get much done for a while because they were using older servers that couldn't keep up. Now they have nightlies going on the Galaxy Nexus, Nexus S, Xoom, Asus Transformer, Asus Transformer Prime, and the HP Touchpad.
I'm sure we'll get nightlies soon enough and you'll be seeing official functioning ROM's everywhere.
We already have functional CM9.
What is AOKP built on anyway?
Ophois said:
http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Click to expand...
Click to collapse
I think they're trying to go mainstream, maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
phatmanxxl said:
maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
Click to expand...
Click to collapse
Problem is the root is still easily accessible. You would see them providing rooting methods for their own software before you saw that. The carriers would also want nothing to do with it. The manufacturer still has the concern of warranty while the carriers have the concern of tethering etc. Carriers likely would never reject an entire manufacturers line, they will always have to cave to some things they do not like.
Though selling unlocked devices with CM much as PC manufacturers will sell hardware with alternative operating systems isn't outrageous. As for the concern of warranty and software caused damage. Routers for example have set a precedent in the support of custom firmware while maintaining warranty. There is plenty of unbricking support in routers. Though providing accessible jtag interfaces in devices that would be sold both retail and unlocked would probably be interesting. Thats just a need in a worst case scenario though not required.
They do seem to be moving in that direction for whatever intent or purpose.
Related
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 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.
We've seen lots of complaining in the last couple of days about what is and isn't working in these ports.
It seems GPS may or may not be working correctly, that it may or may not be due to the Leap Second.
WiFi, Bluetooth, volume... if you have these issues, they can mostly be remedied. If not, gratz.
The fact is, these Roms are ports of development previews on a phone slightly but importantly different than yours running an OS that hasn't been released yet.
I was deeply amazed and impressed that some developers had working ports to CDMA the very night it was announced for GSM.
I'd you are running one of these JB ports and you find that it works well enough as a daily driver, consider yourself fortunate and hit the thanks button on the OP, maybe even donate.
If you are trying it out, but find that it lacks the stability or functionality that you require, click the thanks button on the OP anyway because they spent the time to give you something now for free that which you would otherwise have to wait weeks for, or, considering VZW's track record, maybe never.
This is how I'm looking at it- I'm getting to preview the latest update for free before it officially comes available. Just like those lucky bastards at Google I/O, except how much did they pay per ticket?
Thanks, devs, for doing what you do.
Sent from my Galaxy Nexus using xda premium
Jubomime said:
This is how I'm looking at it- I'm getting to preview the latest update for free before it officially comes available. Just like those lucky bastards at Google I/O, except how much did they pay per ticket?
Thanks, devs, for doing what you do.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
They paid $900 per ticket. But they get $1200 or so free of stuff. So they actually received 300 for going to it if you look at it that way.
Nevertheless I'm very pleased with JB. Everything is working beautiful for me. I using daily driver now without any issues. Just the stock JB at that. I'm not much for all the features of Roms. More into kernel tweaks which I do miss from glados kernel. But Franco is doing fine for now.
M3drvr said:
They paid $900 per ticket. But they get $1200 or so free of stuff. So they actually received 300 for going to it if you look at it that way.
Click to expand...
Click to collapse
Thats why I put going to Google IO one year at least on my bucket list.
i think people are forgetting these roms are from nandroids! lol!
I most definitely appreciate the efforts. I ran the Vicious JB stock port on my VZW Gnex but in the end, I couldn't stick with it because the Verizon framework apps don't work on Jelly Bean yet. This means I couldn't use the My Verizon or NFL Mobile apps, and that's a deal breaker. I understand that you can blame Verizon for requiring the back end framework in order for their branded apps to work, and that's all fine and well, but at the end of the day, I couldn't run them.
Be that as it is, I still appreciate the efforts of those developers to have a working CDMA port the same night. Thanks to all who do what you do. I'm a software developer myself so I know how tedious this crap can be.
Half of the JB "hate" posts are not "my app doesn't work, JB sucks!" but rather "my app doesn't work, I'm posting it in case someone has stumbled upon a fix"
The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).
CMNein said:
The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).
Click to expand...
Click to collapse
Thanks for such an insightful comment. Any more bright ideas?
Sent from my Galaxy Nexus using xda app-developers app
chancy319 said:
Thanks for such an insightful comment. Any more bright ideas?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No, it succinctly indicates the issue at hand.
Sent from my Galaxy Nexus
oldblue910 said:
I most definitely appreciate the efforts. I ran the Vicious JB stock port on my VZW Gnex but in the end, I couldn't stick with it because the Verizon framework apps don't work on Jelly Bean yet. This means I couldn't use the My Verizon or NFL Mobile apps, and that's a deal breaker. I understand that you can blame Verizon for requiring the back end framework in order for their branded apps to work, and that's all fine and well, but at the end of the day, I couldn't run them.
Be that as it is, I still appreciate the efforts of those developers to have a working CDMA port the same night. Thanks to all who do what you do. I'm a software developer myself so I know how tedious this crap can be.
Click to expand...
Click to collapse
I used My Verizon on JB. You just need to install the VerizonSSO apk in order for it to work...I can upload the file if you need it.
well you know what the say "everything's amazing these days, nobody's happy"
[email protected] said:
I used My Verizon on JB. You just need to install the VerizonSSO apk in order for it to work...I can upload the file if you need it.
Click to expand...
Click to collapse
Would you mind? I can find download locations out there but I'm not sure what version's needed.
CMNein said:
The problem is 80% of the people who own a GN are:
a. Bronies (so they're inherently tools),
b. it's their first Android device (so they're inherently tools).
Click to expand...
Click to collapse
I hate you for making me google bronies.
jesusice said:
I hate you for making me google bronies.
Click to expand...
Click to collapse
Bring on the hate :cyclops:
These aren't "ports" of Jelly Bean roms. They are the real deal made specifically for this chipset and device. And, everything works.
I had to look up bronies as well.... I am sending along my hate alone with jesusice
akira02rex said:
These aren't "ports" of Jelly Bean roms. They are the real deal made specifically for this chipset and device. And, everything works.
Click to expand...
Click to collapse
That sort of depends. There are some changes that have to be made to a ROM for the GSM model to be 'ported' to the CDMA models. So, it's a 'port' for those phones, because only the GSM developer preview was 'released'.
They do realize other top phones are just getting ice cream sandwich, and we Nexii already have Jelly Beans sweet taste in our mouths?? Ridiculous!
Sent from my Nexus Prime
One of those lucky ones everything is working just fine, still couldn't see any issues, and I flashed my phone on the 28/06
Funny how ICS was the major update but jb is more of a complete experience.
butter and jelly please...
I meandered on to the development section and was quite surprised to see such recent ROMS and developers working on a cell phone that is turning 3 years old in 5 months. Many EVO buyers have had their contracts expire and are able to upgrade to a new phone. There are much faster phones out there, with better specs that are possibly more interesting to develop for, because you might reach a larger user base. My question to the Devs is why are you sticking to the original EVO? Don't get me wrong, I am a current original EVO owner myself so by all means, keep up the good work, just curious as to why you stuck to such an old device.
Simple answer is its fun! Its a great way to get practice and many devs have friends in the forum. So why walk away completely? If you still have it, you can test away on things you try to build.
Sent from my SPH-L710 using xda premium
Haha, so the EVO is just a scapegoat for developers that don't want to brick their actual device?
Boomchaos said:
Haha, so the EVO is just a scapegoat for developers that don't want to brick their actual device?
Click to expand...
Click to collapse
Accidental thanks :banghead: in some cases, no. But I actually have less a reason to not flash everything in sight, if you catch my drift..
Sent from my SPH-L710 using xda premium
Also the EVO is, and always has been a great Device. Why walk away from it when it still viable, and as stated hellua fun. The proof is in the pudding. Look at the support, and Rom Development available
TEAM MiK
MikROMs Since 3/13/11
If I could boil it down to a sentence it would be... The Evo is a great device to build for.
Sent from my PC36100 using xda app-developers app
4.2 on the OG is more functional than 4.2 on the Jewel. And I need the 4.2 Bluetooth stack. So . . . yeah . Thus the reason my OG is listed as Device 1 in my sig .
Hell, Devs are still working on the Samsung Moment
Sprint htc evo 4g
i bought a sprint htc evo 4g that i bought from amazon ... i cant use sprint in my country and i cant unlock a sprint phone since itc cdma right?... but can i just leave the phone like with sprint but root it and play wiith iit because the only reason i bought it was to learn everything about rooting and i needed a test device...??
There are jelly bean ROMS for the OG? Are all the radios working?
Captain_Throwback said:
4.2 on the OG is more functional than 4.2 on the Jewel. And I need the 4.2 Bluetooth stack. So . . . yeah . Thus the reason my OG is listed as Device 1 in my sig .
Click to expand...
Click to collapse
Wow, that was released in 2009...
HipKat said:
Hell, Devs are still working on the Samsung Moment
Click to expand...
Click to collapse
Sure. Since you don't have service on the phone, it's basically a really small tablet. All the basic functionality will work, and there is always WiFi.
galaxys3lover said:
i bought a sprint htc evo 4g that i bought from amazon ... i cant use sprint in my country and i cant unlock a sprint phone since itc cdma right?... but can i just leave the phone like with sprint but root it and play wiith iit because the only reason i bought it was to learn everything about rooting and i needed a test device...??
Click to expand...
Click to collapse
Boomchaos said:
There are jelly bean ROMS for the OG? Are all the radios working?
Click to expand...
Click to collapse
I'm not sure what you're asking. Please, be specific. The ROM is fully functional outside of the things that require new drivers for Android 4.x, i.e. front-facing camera, and WiMAX.
Boomchaos said:
Wow, that was released in 2009...
Click to expand...
Click to collapse
Yep and over on XDA-Developers, it's the most actively dev'd device still. It was the Evo of it's time
HipKat said:
Yep and over on XDA-Developers, it's the most actively dev'd device still. It was the Evo of it's time
Click to expand...
Click to collapse
It's actually SDX Developers...and yes the Moment was the "Evo" of it's time, sadly however, it's time has passed. I'm a new convert over to XDA from SDX, having to give last rites to my Moment a month ago. Really only one active ROM still being worked on (UberMoment 1.6 - props to TheTehk17 for hanging in there :good: ). They never got a GB Rom fully functional (CM7 was close), all dev was, and still is, Froyo. Major hardware limitations and lack of support will probably keep any further ROM upgrades forthcoming.
Inherited an OG to use for now - great to see all the work being done! Waiting for the arrival of the S4 or M7 for upgrade, until then enjoying the plethora of ROM's available!
Upon upgrade, I will be passing the OG on to any dev here who will continue to put it to good use!
tkacer said:
It's actually SDX Developers...and yes the Moment was the "Evo" of it's time, sadly however, it's time has passed. I'm a new convert over to XDA from SDX, having to give last rites to my Moment a month ago. Really only one active ROM still being worked on (UberMoment 1.6 - props to TheTehk17 for hanging in there :good: ). They never got a GB Rom fully functional (CM7 was close), all dev was, and still is, Froyo. Major hardware limitations and lack of support will probably keep any further ROM upgrades forthcoming.
Inherited an OG to use for now - great to see all the work being done! Waiting for the arrival of the S4 or M7 for upgrade, until then enjoying the plethora of ROM's available!
Upon upgrade, I will be passing the OG on to any dev here who will continue to put it to good use!
Click to expand...
Click to collapse
lol.. brain fart
Yeah, I never thought the Moment could successfully run Froyo, unless there was a hybrid Froyo/GB Rom. I dev'd a nice ROM for the Moment, but I think I took all the links down a few months ago.
HipKat said:
lol.. brain fart
Yeah, I never thought the Moment could successfully run Froyo, unless there was a hybrid Froyo/GB Rom. I dev'd a nice ROM for the Moment, but I think I took all the links down a few months ago.
Click to expand...
Click to collapse
The devs did a pretty good job porting over Froyo ROMs from the Intercept and Transform, and got those pretty functional. Otherwise, the phone would have been stuck on 2.1 Eclair! As mentioned, they have a somewhat working CM7 - buggy, but it does boot up.! The dev that ported that moved on leaving no one to work out the kinks.
So, for me, I'm like a kid in a candy store with not only GB Roms, but ICS, JB, AOSP.......and Sense too! Hell, I'm in hog heaven
lol. yeah, you can flash a different ROM every day for a year, going back to 2.1 if you wanted to
HipKat said:
lol. yeah, you can flash a different ROM every day for a year, going back to 2.1 if you wanted to
Click to expand...
Click to collapse
lol - I might have to hold out on that upgrade until I get this "flashing" urge under control..........
Will be interesting to see when the S4/M7 debuts, how long it takes to get dev going on each
i'm glad dev's have kept this phone up to date its alot of fun
So I'm due for an upgrade and I was wondering about this phone as it's the only one I really want. I currently have a motorola phone that was a flagship when it was first released(Atrix 4G) and while it was a decent phone, Motorola didn't really support it and stick to its release schedules with the phone. Normally this would not be a bad thing since there is the development community that one can fall back on, but this hindered the development community since developers needed to rely on Motorola for drivers and kernel along with Nvidia because the processor in the phone was a Tegra and I'm sure you guys already know how much Nvidia and open source don't go well together lol.
Anyways I was wondering if the SIII has(or will have) any sort of issues in the same area due to closed source or Samsung not releasing drivers,etc... to developers after major releases. I would wait for the SIV, but the phone is getting into screen size territory I'm not comfortable with and I don't want a Nexus 4 because the battery life doesn't seem to be as great as the SIII. Basically once I get my next phone, I want to be able to hold onto it for a few years without feeling the need to upgrade because of out of date software. The hardware in the SIII seems more than sufficient to be future proof.
Another side question: would there be any mods that retain some of the software features found in touchwiz or add any such as multitasking? Not a deal breaker, but just wondering.
octahedron said:
So I'm due for an upgrade and I was wondering about this phone as it's the only one I really want. I currently have a motorola phone that was a flagship when it was first released(Atrix 4G) and while it was a decent phone, Motorola didn't really support it and stick to its release schedules with the phone. Normally this would not be a bad thing since there is the development community that one can fall back on, but this hindered the development community since developers needed to rely on Motorola for drivers and kernel along with Nvidia because the processor in the phone was a Tegra and I'm sure you guys already know how much Nvidia and open source don't go well together lol.
Anyways I was wondering if the SIII has(or will have) any sort of issues in the same area due to closed source or Samsung not releasing drivers,etc... to developers after major releases. I would wait for the SIV, but the phone is getting into screen size territory I'm not comfortable with and I don't want a Nexus 4 because the battery life doesn't seem to be as great as the SIII. Basically once I get my next phone, I want to be able to hold onto it for a few years without feeling the need to upgrade because of out of date software. The hardware in the SIII seems more than sufficient to be future proof.
Another side question: would there be any mods that retain some of the software features found in touchwiz or add any such as multitasking? Not a deal breaker, but just wondering.
Click to expand...
Click to collapse
Seriously doubt Samsung will "prevent" users from being able to mod unofficially. This is one of their two flagship devices. However, it is the carriers that should worry you more. Remember that there are different hardware versions of the SIII as well. Most likely the international versions will be always ahead in getting new updates. On a carrier such as AT&T you are most likely to be the last to receive an update, if you get it at all. Ultimately, if you want guaranteed updates, Nexus 4 is the only sure way to go.
And seriously, read before you ask about mods. Yes and Yes to both questions. Read through and you will find a lot.
aybarrap1 said:
Seriously doubt Samsung will "prevent" users from being able to mod unofficially.
Click to expand...
Click to collapse
This is not completely true. Samsung has already angered alot of the top developers by not releasing the proper info on the exynos chip in some phones. Even after saying they would. Even some CM maintainers have sworn off Samsung until them come threw. But they still have some of the best tract records for android. Even though Sony is moving up fast.
@OP you will always find something about one company or another that wall cause issues with open source development. This is due to the phone OEM not owning all the software code for the devices. Take CDMA phones. They use a closed sourced phone to work on the network. Nothing Samsung can do about it as it is not theirs. We won't even start on the WiFi and BT chip.
In the end. Get a phone that does what you want and need. Development should never be a first choice. That is just a bonus.
aybarrap1 said:
Seriously doubt Samsung will "prevent" users from being able to mod unofficially. This is one of their two flagship devices. However, it is the carriers that should worry you more. Remember that there are different hardware versions of the SIII as well. Most likely the international versions will be always ahead in getting new updates. On a carrier such as AT&T you are most likely to be the last to receive an update, if you get it at all. Ultimately, if you want guaranteed updates, Nexus 4 is the only sure way to go.
And seriously, read before you ask about mods. Yes and Yes to both questions. Read through and you will find a lot.
Click to expand...
Click to collapse
I seriously doubted Motorola would have had issues with the Atrix seeing as how it was their flagship device as well. Seeing as how I've never had a Samsung smartphone, I'm not sure how they handle their updates and it has nothing to do with the carriers as much as it had to do with their Nvidia and Motorola because of Tegra and the fingerprint scanner/lapdock.
And "seriously" I've browsed through the developers forum before to see how active it was. All I wanted was a quick confirmation to my question instead of scanning each thread for a phone I may or may not get.
zelendel said:
This is not completely true. Samsung has already angered alot of the top developers by not releasing the proper info on the exynos chip in some phones. Even after saying they would. Even some CM maintainers have sworn off Samsung until them come threw. But they still have some of the best tract records for android. Even though Sony is moving up fast.
@OP you will always find something about one company or another that wall cause issues with open source development. This is due to the phone OEM not owning all the software code for the devices. Take CDMA phones. They use a closed sourced phone to work on the network. Nothing Samsung can do about it as it is not theirs. We won't even start on the WiFi and BT chip.
In the end. Get a phone that does what you want and need. Development should never be a first choice. That is just a bonus.
Click to expand...
Click to collapse
Gotcha and thank you.
Hello fellow Atrix owner! I'm a former Atrix owner myself. I can you tell right now, this place is hoppin' compared to the Atrix. You won't be disappointed with the choices with ROMs here! Got a couple of former devs from the Atrix over here as well making ROMs!
Sent from my SGH-I747 using xda app-developers app
I have 4.2.2 running almost flawlessly already. Even the nexus devices are just having this update rolled out. I think that goes to show the quality of the S3 development. There certainly isn't a lack of ROMs to choose from in this community.
Deggy said:
Hello fellow Atrix owner! I'm a former Atrix owner myself. I can you tell right now, this place is hoppin' compared to the Atrix. You won't be disappointed with the choices with ROMs here! Got a couple of former devs from the Atrix over here as well making ROMs!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
CamFlawless said:
I have 4.2.2 running almost flawlessly already. Even the nexus devices are just having this update rolled out. I think that goes to show the quality of the S3 development. There certainly isn't a lack of ROMs to choose from in this community.
Click to expand...
Click to collapse
Well this is good to know
I rooted and had neutrino running on my wife's atrix. Samsung phones are easy compared to that process. There are plenty of stock based and aosp roms available. I have flashed at least 20 different roms since October. I will be jumping on the S4 though when it arrives.
Sent from my SAMSUNG-SGH-I747 using xda premium
The samsung was easy to root and there seems to be plenty of rom choice comparatively to some other android phones i've owned.
y0yerrj0sh said:
The samsung was easy to root and there seems to be plenty of rom choice comparatively to some other android phones i've owned.
Click to expand...
Click to collapse
S3 is easy to hard brick too if you aren't paying attention to what you are doing. Just saying.....