Many of you are going to know all this, and many know far better than I. Please, those that do, please step in and correct my information if I make any mistakes.
I see the word stable thrown around a lot - "Is this ROM stable", "stable release", etc.
I want to attempt to pin down a definition when in use for regular conversation, and I also want to address that there is one use of the word that is clearly defined and cannot be used lightly.
First, in the development/open source world, the vast majority of projects you will see are in beta or sometimes even alpha. This means that it's still in some sort of testing phase, and there are usually some bugs that need to be ironed out before it's termed a "finished product". By the very nature of software and developers' desire to be honest, it's quite common that there are some pieces of software that will never leave beta(and some even used in a corporate production environment. "beta" is not a death sentence and doesn't mean there's something fatally flawed). There is always more work to be done, a bug here, something to smooth out there, something that needs to be optimized, etc. A developer can not be satisfied to release a final version. That being said, it does happen. Once it reaches past beta, it often gets promoted to a "release candidate".
A release candidate, or RC, means that they are fairly satisfied that bugs are taken care of, and that they are PRETTY sure there's no major flaw lurking in the depths waiting for the perfect moment to rise and bring down death and destruction upon any innocent fool who crosses its path. This is the final step leading up to that coveted and rare specimen - the :victory:Stable Release.:victory:
Once the release candidate has gone through rigorous testing by developers, users, testers, etc, it can finally become a stable release. It's a big risk to label something as a stable release. This is the developer giving you their word and staking their reputation to say "there are no bugs in this piece of software. It is being released as a final version and will not cause you any trouble".
I beg you to correct me if I'm wrong, but I don't believe there are stable releases for any any ROM for the MT4GS. Once again, this is very common in the development world, and not just for phones. Just take a look at the number of projects on slashdot that are widely used by thousands of people with no trouble - much of them sitting in beta or even alpha.
Now is where we run into some ambiguity using the term. At a passing glance, and certainly to the uninformed, seeing that software isn't "stable" will naturally and intuitively lead one to believe it must be somehow unstable. Given the nature of open source and development, we know that this isn't necessarily the case. There may be something very minor that only comes up in certain situations, the developer may still feel that there hasn't been enough testing to rule out any bugs, or there may be no bugs at all but the developer is not yet satisfied with the completeness, speed, or number of features.
Now, I would like to address how the word is used in conversation or when asking questions about a ROM. Stability itself, is absolutely very important, with good reason, to a vast majority of people who own a mobile phone. This is often their only source of communication and is required for work, for emergencies, and for generally keeping in contact. If the phone fails to function in a manner that keeps the user reliably connected to their web resources as well as phone, email and messaging communication, there could very well be disastrous results. Therefore, asking if the rom is stable is very valid and relevant, but due to the fact that the word stable can have such an ambiguous definition, and is also a term for a particular stage in development, communication can break down pretty quickly between parties when the term starts getting tossed around.
The device I had previously was a Motorola Droid 1(OG Droid, Sholes, etc.). This phone had a huge and extremely active development community on many different websites. Many devs still hold the moto droid in a special place in their hearts for how hackable it was, the power it had for a device at the time of its release, and the massive userbase ranging from those with no technical ability at all to some of the best hackers ever to work on Android. This device truly represented the renaissance, if not the birth, of custom development for android devices.One thing that was extremely common across almost any ROM or kernel you could put on that phone, however, was a risk of "instability". In this case, this usually meant that the phone would randomly reboot, especially when doing something particularly tasking on the cpu(navigation was a particularly common culprit). In extreme cases, it would reboot and then go into soft bootloops once, twice, even five times. This happened more often with overclocked kernels, and most people had to look for multiple kernels and setcpu settings that would give them a balance between speed and stability. It took some trying and some tweaking. Most people would eventually get a setup that was solid. Even with a "rock solid" kernel and ROM setup, there were very few who NEVER experienced a random reboot when running a custom ROM/kernel. It was just something that happened. The other major issue people saw were force closes of apps. These were extremely common as well, but usually addressed more easily. Your setup was considered stable if you were confident that you could do all of your phone's functions without getting FC's and you weren't going to get a reboot 99% of the time. You could rely on it not to do anything unexpected.
I have, admittedly, not tested every ROM that exists for the MT4GS. I probably haven't tested half of them. I have however, tested most of the later releases with the exception of XMC's Jellybean. What I have found, however, is that out of all the ROMs I have tested for this device, each and every one one of them has met my personal definition of stable. I've never seen a random reboot on the MT4GS. If I see a FC, it's because I failed to clear data and cache before flashing something, forgot to flash or flashed the wrong version of gapps, or I'm trying to get something working that wasn't included in the ROM. It's for this reason that I really don't know how to respond accurately when someone asks something like "what's the most stable ROM for this phone?" or "I saw this particular ROM, can anyone tell me how stable it is?"
So I have two requests. The first is for anyone who cares to read all of this and answer. I'd like to ask you, if you are asking about how "stable" a rom is, what do you mean? Are you asking about whether it has bugs? They all have a bug list of what's working and what's not. Are you asking about whether it has a certain feature fully working? Once again, that's in the works/ doesn't work info usually including in the first post about the ROM.
Request 1:
Answer me this - What does "stable" mean to you?
Request 2:
When considering or just looking for info on a ROM and you have a question about this or that, be specific. If I've checked into a ROM, I very well might have an answer for you. If you just ask whether or not it's "stable", I don't know what you're asking
I can see where you're coming from.
Personally, stability for me is a rom that works well enough where the phone isn't bugged out entirely (has over 80% of the phone's default settings working such as calling or getting into e-mail, etc.).
In general, there are others who request too much and want utter perfection. No rom is ever going to be perfect, regardless of the stage of the rom (alpha, beta, release candidate).
Sent from my myTouch_4G_Slide using xda premium
To me a "stable" ROM is one where all of the phone's functions work as designed, meaning the camera, bluetooth, wifi, keyboard, etc. all function without having to do anything extraordinary. Also, the ROM itself doesn't require extraordinary measures to perform common functions and doesn't FC or random-boot. I can accept a few minor glitches, even stock ROMs from HTC have those. But, for my overall needs, I currently run only a stock-based ROM because I absolutely need the stability and all functions (especially the camera and stable wifi). This is my ONLY phone, I don't have another mobile nor a landline, so stability is #1 priority.
I've waited a long time for your post.
...and I agree with everything you've said thus far in principle.
The concept of stable is in and of itself a dynamic thing in a place like this under the many varied intentions of the people developing anything here.
Consider that in many cases things are made as examples, or proof of concept. Such things may be deemed stable by the creator on the particular proof, yet be unstable for other uses.
In many cases, such things are outlined by the developer and the bounds determining stability vary widely from project to project, and developer to developer.
In the retail world of say, phone sales, and the manufacturers guarantee against defects, the business world is held to a certain threshold of accountability for providing a working product.
For us here, there is no money involved - people aren't paying for a product, and so lose at most up time with the device while it gets sorted out. The total loss of the device itself, as in hard brick, due not to user error but to developer error is where I would say the minimum standard of stability lies.
That bears, in my eyes, the closest relation to the business world standard of a manufacturers guarantee against defects. Buggy software, and the clarification thereof being the topic to pick apart - i'd like to get a consensus of how many other people feel that simply not hard-bricking the device due to developer error is the complete polar opposite of:
karri0n said:
...
that coveted and rare specimen - the :victory:Stable Release.:victory:
...
Click to expand...
Click to collapse
...where the quote is in-context of being a final, finished product.
The minimum threshold being the easier end of the debate to reach agreement on and build our understanding from.
....
So how does a developer get to stable projects?
Drawing a parallel from the manufacturing industry, the answer is quality control.
If your business is running assembly lines of product, at the end of the line needs to be a certain amount of quality control before shipping. Else the product could vary widely in stated ability and function. A shop with little to no quality control could be one equivalent to an unstable release.
This points us in a direction in the determination of stability - the comparable equivalent from our point of view is testing. You have to test your product (project) before sharing, else you don't know if it will work right.
Unlike an assembly line where testing is done on a random small sampling of pieces, a developer must rigorously test and retest the project (product) to ensure stability and reliability of function.
Of course, this begs the question of the standards involved in testing.
Ever seen this movie? The Pentagon Wars
It's a riot - but also illustrates the importance of standards in testing.
To us one way, arguably the most important way, is developing a consistent method of testing to properly evaluate the desired results.
Consider my first project of involvement at XDA was in understanding the differences in MicroSD cards for running CM7 booted off the Sdcard and not the internal memory of a device. Some cards were downright buttery smooth and amazing, other cards were downright impossible to work with. They were directly found to be the culprit of force closes, if it could be run at all.
Once we determined that there was a specific brand that could be consistently counted on to perform to spec (through a massive posting of speed test results by ever so many members of the community!!! :highfive: ) - I set about trying to determine how accurate the posted information was.
This thread: A Closer Look At MicroSD and Reader Speed
...was primarily established to determine how much the type of card reader used skewed the testing results.
Granted, i'm biased based on having written the article, but I would consider that project to be an example of rigorous standards of testing for a particular piece of information.
I use this example to make the point of stability. In this case it directly equates to validity of results. By recording all of the data, publishing all of the data, people can point out where my math may be wrong if i've made a mistake based on calculations of the raw published data.
( just like people can offer suggestions on published open-source code )
...or incorporate the results into further testing of their own - based on the validity ( stability ) of the data.
Another example of what I would consider trying to achieve a "stable release" of an answer to a question through rigorous testing: My first real doubleshot contribution.
So I put forth those two projects of mine to illustrate what I consider stable releases of information. If not, explain why?
So a stable release not only is important from a user perspective, but also from an open-source developers perspective.
How solid is the code(knowledge, information, etc...) being built on, if a coding (or other...) project? Is the code you are nudging in a direction you think would be interesting buggy to start with?
Is your own new code buggy to start with?
Do you just throw it out there and keep working with it until it works? Do you take the time to ensure it works to the best of your ability before releasing?
Both are very valid approaches - some radical concepts are seen to reality much more quickly because the incomplete thought was tossed into cyberspace to grow to maturity.
The developers ability to relay the type of project it is, and the expectations of use can in fact create the business world equivalent of 'buyer beware' in the context of placing the onus of determining stability on the end user.
Because stability really depends on perspective.
Saying that something is a daily-driver, i'd use it everyday kind of thing is most akin to the:
karri0n said:
...
that coveted and rare specimen - the :victory:Stable Release.:victory:
...
Click to expand...
Click to collapse
...that we are trying to define as the upper end of finished.
There again though, this varies based on perspective.
Pretend a large enough user base decided they didn't care about not having any bluetooth ability. Along come some ROMs that don't include that function. They state such, and otherwise have bugs on a very individual user level basis, if at all.
To that user-base, those ROMs are stable. What about you? You lose your bluetooth headset and can't do without that. Being as bluetooth is a functional piece of equipment within the device, any ROM without it is technically unstable. Can we agree with this?
Stability can also be defined, at least in part, by a developers ability and attention to resolve issues "Immediately, if not sooner". This becomes a determination of stability based on the developers ability and timeliness in resolving issues.
Otherwise stable software can become corrupted through interaction with other code that doesn't agree with it. There are a lot of apps out there, and Android is an environment allowing for much more freedom then the app store.
Due to the increase of involvement of chaos theory throughout the Android environment, I'd put forth that the stability of any software is in part tied to the developers attention to unforeseen interactions due to the scope of Android at large.
Here again, is another example - by this definition:
"Bulletproof was more stable when I was actively working on it - before I had to take a leave of absence." During that leave time, the ROM is less stable then it was before, because any new problems aren't attended to.
But we can say that not only the level of attention, but the quality of that attention is important too.
A consistent voluntary lack of desire in chasing down new bugs and fixing them could be seen as the equivalent of that crappy customer service call. Maybe you just exceeded the developers interest in the project, and to that developer it was stable for it's intentions at the time, and has moved on.
From one perspective, the project was completely stable. From another, quite the opposite.
There again, you have developers moving on to other phones, or using projects as stepping stones to other goals. We would need to agree to be able to define something as "stable to a point" if the project was brought so far forwards before the developer left it behind for others to build on.
Sometimes while building bulletproof I threw out stability and claims/remarks thereof in order to challenge the community to define what it was to me.
In the end, stability to me correlates to the endless anal attention to detail - on all fronts. To write clean code, to properly wipe and prepare the device, and the burden of utilizing a stable product rests with both the producer and the user - even if the only user is the producer.
Given the many facets of 'Stability' in trying to define it - how accurately can we do so?
I look forward to the postings on this thought experiment.
How big is big?
I'd bet that the word "stable" means something slightly different to nearly everyone. As an active user that tinkers with their installation a lot "stable" means no more than a 1 problem that requires a reset every week or two. Different usage would mean different definitions. Another user on my account that primarily uses his smart phone for calls won't tolerate more than 1 problem a month and for him, even that is frustrating. For emergency personnel any problem that prevents phone usage would be way too many.
The word also has different meanings for different products. I wouldn't consider a router that has more than 1 or 2 problems a year stable. Commercial communications equipment I've worked with was deployed in environments where it was expected to run at least 2 years without a problem. It was so well designed that occasionally it would run 5 or more years and the end users would forget where it was located and sometimes even that it existed at all.
I guess language just sucks for this type of thing.
All I want is a sense-less ROM that doesn't have random reboots and I'll stick with this phone for another year. As it is now I can't freaking stand it. That's with a totally fresh wipe and install of Virtuous Inquisition. I just don't buy into the idea that these phones aren't meant to download all the apps and games we can fit off the play store (not that I do... I HAVE in the past but I've barely reinstalled anything since my most recent wipe). The idea that installing things is going to lead to issues that aren't the ROMs fault is crazy. The stock ROM doesn't have these issues with my apps being installed. I only rooted to get rid of that dumb genius button (and getting rid of sense was the icing on the cake although not totally necessary).
"Stable" should refer to a ROM that works completely fine except for 2-4 functions that are not essential to smartphone daily function.
"Stable" unfortunately refers to a ROM that boots around here.
Sent from my HTC MyTouch 4G Slide using xda premium
polarbearmc said:
All I want is a sense-less ROM that doesn't have random reboots and I'll stick with this phone for another year. As it is now I can't freaking stand it. That's with a totally fresh wipe and install of Virtuous Inquisition. I just don't buy into the idea that these phones aren't meant to download all the apps and games we can fit off the play store (not that I do... I HAVE in the past but I've barely reinstalled anything since my most recent wipe). The idea that installing things is going to lead to issues that aren't the ROMs fault is crazy. The stock ROM doesn't have these issues with my apps being installed. I only rooted to get rid of that dumb genius button (and getting rid of sense was the icing on the cake although not totally necessary).
Click to expand...
Click to collapse
I can't say I've seen any problems like you are describing. I only used Vinq for a very short time, before I realized that wifi calling didn't work on it. CM9 a5 does not have any random reboots and has more features than Vinq working. That being said, I haven't heard of anyone facng random reboots using Vinq. if I had to guess, I would say it's related to the way Vinq tries to patch some elements of Sense and some elements of AOSP together, and they just don't get along. If it were me, I would move to cm9. I don't like sense's remnants tainting up my device, especially if they're going to lead to problems. the ONLY exception to this is the stock DoubleShot camera I would enjoy having that, but not if it meant that I had to run sense libs and it started causing conflicts with other parts of my AOSP.
Related
I've been playing around with all the 6.5 ROMS available on this forum (plus have been lurking for a while so felt like doing some contribution could be appreciated ).
My company is very stringent about enforcing Exchange ActiveSync policies, especially PIN CODE, timeout to lock and remote wipe.
I noticed that on the 230XX series (I have tested up to 23053) posted here, there are two different behaviors, one serie works with my Exchange Active Sync, one does not.
Since the PIN request and lock timeout work fine with them, I have to assume the remote wipe feature has somehow be disabled by this ROM.
I have been able to identify that a ROM will give me this problem even without connecting with my Exchange Server.
in 100% of the case, if I try to import a root certificate on a "hacked" ROM, it will be installed without any warning, just a "Certificate successfully installed, press OK" dialog.
Now, on a ROM that is not "hacked", when you try to import a root certificate, you are warned that this may be an unsafe operation and have actually to confirm.
This is very concerning to me, because the warning being removed means that any bad guy can leverage these ROM to deploy a rogue root certificate to your device and your device can start trusting wrong sites.
I do not intend this to be an exhaustive list, but as of my testing only the following two ROMs work correctly:
- NATF
- RRE
All the others do not. The source of the non-working ones is either the same, or these people have purposedly altered the ROM to change the security settings. But the result is the same, security altered ROMS.
If anyone could confirm they are experiencing the same, I would not feel alone on the planet
UM
I'd just like to reiterate that this is a development community- most of the cooked ROMS you've tried are experimental works in progress. We tend to take our experimenting a bit far here- but as none of our 'products' are really production tested, it's fairly safe to say that all of them are just a bit unsafe.
A stock ROM has the benefit of being tested in a production environment- and while performance on these ROMs may not be optimal, they are composed of a set recipe of components established between the OEM and Microsoft.
Many of our ROMs are conglomerations of various different components- so it's not exactly safe to say that any of them can be held completely accountable for device security- there may be plenty of exploits present behind the scenes that never have been exposed or rectified.
We're small-scale individual developers. Most, if not all of us, do this for fun. Many of our packages deliberately alter the way in which devices handle certificates and signing- because it allows us to expand the boundaries we develop within.
If you're looking for guaranteed security, your best bet is to stick with a completely stock device. If you choose to use another ROM, any insecurity is not on the developer, but you.
Very well said! On top most, actually all of the 6.5 based ROMs have a microsoft beta as a base. Though it may be a save bet that the latest built # may be the closest to the final release at Oct. 9 it's a common practice to reduce/alter some "security" settings an policies for an "easier" way to success. None of these facts is to blame on any ROM chef or developer or however you want to name these creative heads here.
Their work is just incredible and I bet that ms or HTC would be proud to have such guys on board.
Note:
I bet that some individuals of both companies keep a close eye on what's going on here.
Guys,
Don't get me wrong, I know what I'm doing when installing a beta that has been leaked.
First, it's illegal, we are stealing non published source code, infringing intellectual property and probably making ourselves guilty of too many felony counts to be able to get out of jail without a long white beard.
But, joke aside, this was not the point of my post and I am sorry if I didn't explain myself clearly.
There are 23053 builds that work well are 23053 that do not, as was the case with any previous build number and, consistantly, I have had two out of the pack working exactly as expected from a security perspective, and all of the rest not working as expected.
So, since I do not believe MS is deliberately compiling one tree of the code with embedded security and another without, it means that someone in the middle is affecting it.
That was my point.
UM
Hummm...
Wrong approach fellow...
Wrong place, wrong time and wrong people.
Don't expect to be received with an open heart while commenting such things...
Imagine the following scenario:
A priest enters a strip bar and tells the owner of his concerns of moral ground, about the practices that take pace there... LOL
I may understand your point, definitely not your purpose.
If you are lucky enough not the get flamed, you will at least see some frown faces...
Leave it...
As someone suggested before, remember this is a development community...
If what you find doesn't suit your needs simply suggest changes or don't use it at all.
If you concluded, after experimenting, that the only functional ROMs are NATF and RRE ones, allow me the following suggestion:
Choose between 3 options:
1. Use a stock ROM so you don't «steal» form anyone and don't risk having to spend 5 days in a row shaving...
2. Use a NATF ROM
3. Use an RRE ROM
I believe i made my point as gently as I could...
If i may have hurt some feelings, i am deeply sorry for that.
Cheers
Well, 2 points in answer to your post where you obviously did not read mine:
1) Did you miss the sentence that starts with "Joke aside" ??
2) Don't care of being flamed, I provided evidence to people that want to make up their miind, they don't need you to tell them what is safe or not for them
Bottom line is:
- if you do not want to have a phone crashing on you, use a stock ROM (that's actually a good joke... Stock ROMs do not crash less than their beta counterpart).
- if you do not want your passwords, contacts or personal data to end up into some hackers site, be careful about what ROM you install
wearing my flame proof vest.
UM
unlockMe said:
Well, 2 points in answer to your post where you obviously did not read mine:
1) Did you miss the sentence that starts with "Joke aside" ??
2) Don't care of being flamed, I provided evidence to people that want to make up their miind, they don't need you to tell them what is safe or not for them
Bottom line is:
- if you do not want to have a phone crashing on you, use a stock ROM (that's actually a good joke... Stock ROMs do not crash less than their beta counterpart).
- if you do not want your passwords, contacts or personal data to end up into some hackers site, be careful about what ROM you install
wearing my flame proof vest.
UM
Click to expand...
Click to collapse
Dear UM,
I had a good laugh reading your last sentence LOL
I believe that wither you misunderstood me either I was not clear...
1. I am not accusing you of anything.
2. I read you whole message (points 1 and 2 included... They were there, weren't they...?)
3. I am not trying to demote you of you purposes... I was only trying to pass a message but given the fact the message wasn't delivered, I will try to rephrase...:
You are expressing both facts and opinions.
That is, indeed, you right given the fact we are in an open community and we, still, are in a free world (so to speak...).
I do not endorse or condemn none of your previous statements.
Knowing this community for quite some time and specially knowing it's member, active ones, passive ones, contributing ones, parasite ones, etc... I just know for sure that your comment in which you address people in such manner will have one of two possible outcomes:
1. Total ignorance
2. Flaming
Now, after this, do whatever you like Don't get me wrong and sorry if I made myself misunderstood
Nuff said.
Cheers.
This thread is not development related, moved to the appropriate section
First, let me say up front that I have the utmost respect for the developers in the Captivate forum. It's a handicapped device that has much more potential than I think we'll ever be able to tap, simply because there isn't much motivation for Samsung to fix its biggest issues. Let's face it: The things we like most about our favorite Android handsets are precisely the things that make them seem "too complex" to the non non-technical general public. I think that the Galaxy S line has been a huge dissapointment to enthusiasts, and a big "ooh, ahh" for the iPhone-types.
That being said, let me move on to my main gripe: Through my Droid Incredible, I fell in love with flashing ROMs. If it had a higher build number, I flashed it. And you know why? Because it was better a better build. Newer baseband versions fixed more problems than it caused. I could flash ROMs on a train versus needing to be at my desktop for an exhaustive multi-step shamble. And when ROMs were released from build to build, developers in general knew what to expect as far as results.
I simply can't say that that's true with the Captivate. I'm growing increasingly frustrated with this phone and it's idiocy. I hate having ROMs with "Beta 9.3.5" after their title. I hate that half of the releases are to take out some Samsung crap, replace it with some AOSP-like goodness, just to see what sticks.
Again, it's not a condemnation of the Devs. They have made this phone tolerable, which is no small task. I just think it's a sad state of affairs when an OS based on an open source foundation has been so brutally slapped together that it makes a phone with the looks and hardware specs of a Ferrari about as much fun to own and maintain as a Yugo.
Who's with me on this one?
EDIT:
I'm keeping my original post above, partly because there have been too many responses to make removing it reasonable, and partly because I'd like something to review the next time I decide to try and put my thoughts out there to the community.
I never imagined that I would draw so much criticism over this post. I honestly thought I did a pretty good job of making it apparent that I truly appreciate all of the developers' work. I'm a huge fan of the Android platform and of open source projects in general. Allow me to draw a poorly crafted and weak analogy, if I may:
I love my two-year old boy dearly. He's a fantastic kid and big bright spot in my life. He has asthma, and I really do hate providing his breathing treatments. It doesn't mean I'm not thankful for the technology that allows him to breathe, and I certainly wouldn't consider trading him in for a different model without such issues. I would, however, consider venting to other parents of an asthmatic child about how laborious the process of breathing treatments is, and how unfriendly it is towards children his age.
I'm not quite sure how I managed to come across as anti-open source, anti-developer, or at all unappreciative of our dedicated developers - but apparently that's exactly what I did, so for that I apologize. What is really awful is that with one well-intended post I feel that I have ostracized myself from a community that I thoroughly enjoy supporting.
So instead of being constructive... and building a ROM of your own or simply not using them, you're complaining? No one said you have to use them. No one said you have to update all the time.
Definitely not with you.
I think the fustration you're feeling is related to these only having being available to the masses for about 2 months. The modding community started with HTC phones, so they have the momentum. That being said the samsung community is making a lot of progress, and HTC/Samsung cross modding is in full swing. Be patient.
Sent from my SPH-D700 using XDA App
Thanks for your thoughts. I thought I had posted in "Captivate General", not "Captivate Troll." My mistake.
I have actually tried just about all the ROMs available. You may have noticed that I stated that this is not a Dev issue. I doubt many can do better than the talented developers we have here - I know I couldn't. Hell, even Samsung can't.
My point is that I think the Galaxy S line is a harbinger of things to come for Android. I hope I'm wrong, but as Android becomes increasingly mainstream, it also becomes increasingly less important to deliver function AND form.
The average consumer wants sexiness with phrases like "dual-core" listed in the specs, regardless of what the device can actually deliver.
Sent from my GT-I9000 using XDA App
crayak said:
I think the fustration you're feeling is related to these only having being available to the masses for about 2 months. The modding community started with HTC phones, so they have the momentum. That being said the samsung community is making a lot of progress, and HTC/Samsung cross modding is in full swing. Be patient.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You have a good point, and I have no problem waiting. I suppose I was just sharing my reflections.
Sent from my GT-I9000 using XDA App
I share you feelings somewhat. Thats why I picked a ROM (Cognition 2.1.6) and will stick with it until Froyo officially drops for the Captivate. I also hate having to restore a phone after a flash which is why I choose not to do it often.
vbhines said:
My point is that I think the Galaxy S line is a harbinger of things to come for Android. I hope I'm wrong, but as Android becomes increasingly mainstream, it also becomes increasingly less important to deliver function AND form.
The average consumer wants sexiness with phrases like "dual-core" listed in the specs, regardless of what the device can actually deliver.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I actually agree here. But this is sort of Google's thing in a lot of areas. Google Wave, Google Buzz etc. Google MASTERS searching. And everything else they throw stuff on a wall and some sticks and some don't. I worried about that with Android from the very beginning. They often times release half finished products and then allow the devs to finish (or not in some cases) the future of the product/service.
By going to 100 different carriers in 100 different iterations google may very well stop caring about the polished product and just allow the devs to do the rest.
When I had my HTC Hero I had a Flash addiction. Now I just have decided to stick with one build and update it when updates happen. There have been quite a few VERY recent improvements. SetIron's kernel is a fine example. Stuff is happening at a much faster pace than it was when I got my phone 2 months ago. There are twice as many ROMS if not more. Things are going blow wide open when Official Froyo and its source code drop. I think there was stagnent developing at first because we all knew Froyo was coming. If we're lucky Froyo and Gingerbread will share the same kernel so porting IT won't be a big deal either.
FWIW, The Captivate hasn't been out anywhere near as long as the Incredible. Give the Devs some time - it can only get better.
rfarrah said:
FWIW, The Captivate hasn't been out anywhere near as long as the Incredible. Give the Devs some time - it can only get better.
Click to expand...
Click to collapse
I think his frustration is more that we have this incredible piece of hardware and the less than stellar job that Samsung has done to finish it off on the software side. If it wasn't for the devs/cookers I probably would have sold my Captivate by now, and I have only had it for 1 month, coming from a Milestone.
Samsung, hire some of these devs to fix your mess you call a kernel and os. Without the lagfixes from the devs this phone responds worse than my Milestone.
bradasmith said:
I think his frustration is more that we have this incredible piece of hardware and the less than stellar job that Samsung has done to finish it off on the software side. If it wasn't for the devs/cookers I probably would have sold my Captivate by now, and I have only had it for 1 month, coming from a Milestone.
Samsung, hire some of these devs to fix your mess you call a kernel and os. Without the lagfixes from the devs this phone responds worse than my Milestone.
Click to expand...
Click to collapse
+1
Thank you for saying what I was trying to, but in far fewer words.
the galaxy s phones might be the last of the phones not locked by the manufacturer. and i like the samsung software package but dislike that it only works if x or y componant is still there. i dont get the appeal of aosp for an every day rom but i get that it is a transition for porting other things, once we know what we need to make the phone work with aosp we can make it work with anything. and i think that people arent giving samsung enough credit for support on the device. the stock rom was buggy and jf7 came out and made things better, now we are waiting on froyo and im sure it will be better yet, if the the leaked copies are an indication then froyo should be quite good.
i think the multi step proceedures is dev preferance for clearing data, there have been roms that you can flash over and keep everything. the other issue is lagfixes which aren't available(or needed) on other devices. the lagfix is part of those oh sh!t moments where you need odin, also having odin available is another avenue for the devs. if we could only flash from recovery you would see alot more cockwork flashable roms that are compatable with multiple lagfixes.
i messed with an evo and really got an apreciation for samsung, i felt the evo was of low build quality and that odin flashing a rooted rom is much more convenient than the rage against the cage meathod of adb pushing files and rooting and recovery flashing. rooting a galaxy s is rediculously easy, just an update.zip, or an one click app on the phone, or a one click app on a pc. or for froyo a 3click kernel flash in odin then an update.zip. or flashing a rooted rom with odin.
i have made many noob mistakes and taken risks and got it running every time. i dont know about the incredible but i think with some other devices i would have either bricked or pulled all my hair out fixing it.
i was in the airforce and one thing that people always said was that the two best bases are the one you last came from and the next one you are going to. people were always telling stories about "back in kirkland...." and "when i get to misawa..." but people were always complaining about there current base. i have a fealing that in year or two when we have new phones we will see many thing we hate about those as well. and if we had motorolas we'd hate those and if we had incredibles we see the galaxy s playing asphalt 5 from samsung apps and be like if only my phone could do 3d like that one.
I have one issue with my phone, the GPS. While I'm mad it doesn't really work it's something I NEVER use. Other than that I'm running the latest Cognition rom and couldn't be happier.
gunnyman said:
.....Things are going blow wide open when Official Froyo and its source code drop. I think there was stagnent developing at first because we all knew Froyo was coming.
Click to expand...
Click to collapse
I think this is 100% the reason. I fully expect that there will be some amazing things done and some great roms released.
I don't know if it was mentioned or not already but the reason why there are so many beta versions of roms and why newer versions open up issues is for the same reason as above, no source code available. So be patient and I promise you'll be kicking yourself for making this thread.
I am not a programmer, just a user with some technical expertise, but I love these open source OS's. I jumped on Linux as soon as MS Vista came out and the improvements and leaps forward by that community on the desktops has been amazing. When I opened a Win7 PC for the first time, I realized Microsoft is now copying Linux, not the other way around. Just last week I looked at the new MAC OS and I wanted to scream that they were ripping off the XFCE GUI in Linux. Linux is leading the way in Netbooks now and embedded devices are now a focus. If you have ever flashed a router with Tomato, or one of the other Linux router OS's, you know what amazing things routers are now capable of. And then we have smart phones and make no mistake, Android is just Linux in a smart phone. We don't have to deal with a proprietary systems from MS or Apple, where you only get what they hand out to you. This is Burger King baby, you get it your way. Google may be the name on this open source OS, but it belongs to us all. Google can not take this OS proprietary. Yet any time we, the people, wish we can spin off another branch of development with those things we want. OS's like Meego (and I'm sure there will be others) should be able to be ported over, if we wish, in the near future. We may be looking at an era where we can truly buy the smart phone of our choice, install our OS of choice and choose our carrier of choice with ease.
Bottomline here is you can help. If you are not a dev, or a programmer, you can still contribute to this by continuing to use these builds, and report bugs, and you can contribute money to any of the open source efforts, particularly in areas where you want to see more effort. You don't have to sit on the side lines anymore and just whine about how you are getting the short end of the stick by the big corporations. Open Source belongs to us all, take ownership.
i dont think apple is really copying xfce. ..macosx versions are terminal based and therefor unix like and very similar to linux. x11 window environments have been around for many year. xfce doesn't offer that much that i know of that isn't in others window managers. it is possible that the developers on all sides are taking ideas from each other, but i think since power user often have a lot of shortcuts setup to get through common tasks faster that they are implementing some of these things as presets. similarities can just as easily similar minds overcoming very common problems. granted many developers may be running alternate os's and may be inspired by the other. not that i dont believe in corperate espionage i certainly do but i think a lot of things are just obvious solutions.
the problem with phones is that the manufacturers can lock us out and the locks can be difficult to break. you are right that google doesnt own the os but the manufacturers have proprietary source along side the source that they must release because it was taken from google. at some point it makes development dificult. i think we need an emphasis on aosp to build roms from. not because i like the google software, i find it plain and ugly, but because once aosp is figured out there is more understanding of how it all fits together and ports become easier.
i just cant wait to see the day when we can custom order aosp compatible hardware and build phones based on what our priorities are and what we can afford. i know we cant actually solder the boards our selves with surface mount but it could be done on an assembly line with robots if a manufacturer decided to use them to there full potential.
vbhines said:
Thanks for your thoughts. I thought I had posted in "Captivate General", not "Captivate Troll." My mistake.
I have actually tried just about all the ROMs available. You may have noticed that I stated that this is not a Dev issue. I doubt many can do better than the talented developers we have here - I know I couldn't. Hell, even Samsung can't.
My point is that I think the Galaxy S line is a harbinger of things to come for Android. I hope I'm wrong, but as Android becomes increasingly mainstream, it also becomes increasingly less important to deliver function AND form.
The average consumer wants sexiness with phrases like "dual-core" listed in the specs, regardless of what the device can actually deliver.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I couldn't agree with your more about your criticism about Samsung - but I'm not sure how this applies for Android as a whole. The closest thing you can say is Android fails to exclude poorly performing companies - but that's not much of a statement, is it?
Sent from my SAMSUNG-SGH-I897 using XDA App
GreenWolf70 said:
I am not a programmer, just a user with some technical expertise, but I love these open source OS's. I jumped on Linux as soon as MS Vista came out and the improvements and leaps forward by that community on the desktops has been amazing. When I opened a Win7 PC for the first time, I realized Microsoft is now copying Linux, not the other way around. Just last week I looked at the new MAC OS and I wanted to scream that they were ripping off the XFCE GUI in Linux. Linux is leading the way in Netbooks now and embedded devices are now a focus. If you have ever flashed a router with Tomato, or one of the other Linux router OS's, you know what amazing things routers are now capable of. And then we have smart phones and make no mistake, Android is just Linux in a smart phone. We don't have to deal with a proprietary systems from MS or Apple, where you only get what they hand out to you. This is Burger King baby, you get it your way. Google may be the name on this open source OS, but it belongs to us all. Google can not take this OS proprietary. Yet any time we, the people, wish we can spin off another branch of development with those things we want. OS's like Meego (and I'm sure there will be others) should be able to be ported over, if we wish, in the near future. We may be looking at an era where we can truly buy the smart phone of our choice, install our OS of choice and choose our carrier of choice with ease.
Bottomline here is you can help. If you are not a dev, or a programmer, you can still contribute to this by continuing to use these builds, and report bugs, and you can contribute money to any of the open source efforts, particularly in areas where you want to see more effort. You don't have to sit on the side lines anymore and just whine about how you are getting the short end of the stick by the big corporations. Open Source belongs to us all, take ownership.
Click to expand...
Click to collapse
This is one of the best posts I have read on this forum. What a great insight into the evolution of the smartphone, it damn near brought a tear to my eye and sure as hell made me proud to be an owner and defender of the ideal of Open Source. Sure, my Captivate isn't perfect, but I continue to try new ROM's and use my technical proficiency to try and reason out any bugs so as to provide useful feedback. In turn, these ROM's continue to get better and everyone profits.
I love you guys... *group hug*
Dani897 said:
the galaxy s phones might be the last of the phones not locked by the manufacturer. and i like the samsung software package but dislike that it only works if x or y componant is still there. i dont get the appeal of aosp for an every day rom but i get that it is a transition for porting other things, once we know what we need to make the phone work with aosp we can make it work with anything. and i think that people arent giving samsung enough credit for support on the device. the stock rom was buggy and jf7 came out and made things better, now we are waiting on froyo and im sure it will be better yet, if the the leaked copies are an indication then froyo should be quite good.
i think the multi step proceedures is dev preferance for clearing data, there have been roms that you can flash over and keep everything. the other issue is lagfixes which aren't available(or needed) on other devices. the lagfix is part of those oh sh!t moments where you need odin, also having odin available is another avenue for the devs. if we could only flash from recovery you would see alot more cockwork flashable roms that are compatable with multiple lagfixes.
i messed with an evo and really got an apreciation for samsung, i felt the evo was of low build quality and that odin flashing a rooted rom is much more convenient than the rage against the cage meathod of adb pushing files and rooting and recovery flashing. rooting a galaxy s is rediculously easy, just an update.zip, or an one click app on the phone, or a one click app on a pc. or for froyo a 3click kernel flash in odin then an update.zip. or flashing a rooted rom with odin.
i have made many noob mistakes and taken risks and got it running every time. i dont know about the incredible but i think with some other devices i would have either bricked or pulled all my hair out fixing it.
i was in the airforce and one thing that people always said was that the two best bases are the one you last came from and the next one you are going to. people were always telling stories about "back in kirkland...." and "when i get to misawa..." but people were always complaining about there current base. i have a fealing that in year or two when we have new phones we will see many thing we hate about those as well. and if we had motorolas we'd hate those and if we had incredibles we see the galaxy s playing asphalt 5 from samsung apps and be like if only my phone could do 3d like that one.
Click to expand...
Click to collapse
GreenWolf70 said:
I am not a programmer, just a user with some technical expertise, but I love these open source OS's. I jumped on Linux as soon as MS Vista came out and the improvements and leaps forward by that community on the desktops has been amazing. When I opened a Win7 PC for the first time, I realized Microsoft is now copying Linux, not the other way around. Just last week I looked at the new MAC OS and I wanted to scream that they were ripping off the XFCE GUI in Linux. Linux is leading the way in Netbooks now and embedded devices are now a focus. If you have ever flashed a router with Tomato, or one of the other Linux router OS's, you know what amazing things routers are now capable of. And then we have smart phones and make no mistake, Android is just Linux in a smart phone. We don't have to deal with a proprietary systems from MS or Apple, where you only get what they hand out to you. This is Burger King baby, you get it your way. Google may be the name on this open source OS, but it belongs to us all. Google can not take this OS proprietary. Yet any time we, the people, wish we can spin off another branch of development with those things we want. OS's like Meego (and I'm sure there will be others) should be able to be ported over, if we wish, in the near future. We may be looking at an era where we can truly buy the smart phone of our choice, install our OS of choice and choose our carrier of choice with ease.
Bottomline here is you can help. If you are not a dev, or a programmer, you can still contribute to this by continuing to use these builds, and report bugs, and you can contribute money to any of the open source efforts, particularly in areas where you want to see more effort. You don't have to sit on the side lines anymore and just whine about how you are getting the short end of the stick by the big corporations. Open Source belongs to us all, take ownership.
Click to expand...
Click to collapse
EsotericPunk said:
This is one of the best posts I have read on this forum. What a great insight into the evolution of the smartphone, it damn near brought a tear to my eye and sure as hell made me proud to be an owner and defender of the ideal of Open Source. Sure, my Captivate isn't perfect, but I continue to try new ROM's and use my technical proficiency to try and reason out any bugs so as to provide useful feedback. In turn, these ROM's continue to get better and everyone profits.
I love you guys... *group hug*
Click to expand...
Click to collapse
Well said Androiders!
+10
Then go wait on the sidelines for a cyanogen port. We, galaxy s phone owners. Don't and won't need huge steps beyond what we have. Your expectations are limited to what your old phone needed to perform.
You are right its silly. And unnecessary. Find a new hobby if porting roms isn't doing it for you.
vbhines said:
First, let me say up front that I have the utmost respect for the developers in the Captivate forum. It's a handicapped device that has much more potential than I think we'll ever be able to tap, simply because there isn't much motivation for Samsung to fix its biggest issues. Let's face it: The things we like most about our favorite Android handsets are precisely the things that make them seem "too complex" to the non non-technical general public. I think that the Galaxy S line has been a huge dissapointment to enthusiasts, and a big "ooh, ahh" for the iPhone-types.
That being said, let me move on to my main gripe: Through my Droid Incredible, I fell in love with flashing ROMs. If it had a higher build number, I flashed it. And you know why? Because it was better a better build. Newer baseband versions fixed more problems than it caused. I could flash ROMs on a train versus needing to be at my desktop for an exhaustive multi-step shamble. And when ROMs were released from build to build, developers in general knew what to expect as far as results.
I simply can't say that that's true with the Captivate. I'm growing increasingly frustrated with this phone and it's idiocy. I hate having ROMs with "Beta 9.3.5" after their title. I hate that half of the releases are to take out some Samsung crap, replace it with some AOSP-like goodness, just to see what sticks.
Again, it's not a condemnation of the Devs. They have made this phone tolerable, which is no small task. I just think it's a sad state of affairs when an OS based on an open source foundation has been so brutally slapped together that it makes a phone with the looks and hardware specs of a Ferrari about as much fun to own and maintain as a Yugo.
Who's with me on this one?
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
In all honesty (and potential ignorance), I'm floored by the difference in commonly accepted time frames for testing desktop tweaks vs. mobile tweaks ("tweaks" used in the most general sense) and the influencing factors. Installing a new kernel on my Fassy feels like installing a new CPU in my desktop in terms of potential changes (good or bad) in stability, features, general performance, and tweaking potential, minus the thermal grease under my nails. In my PC OCing days though, people would commonly balk at anyone claiming a stable config without the 24h Prime95 runs, repeated SuperPi results, etc. as evidence; I really haven't seen anything like that in my limited smartphone experience, but I understand some of the reasons why, aside from being impractical for most users.
I find it easier to get spoiled on the mobile platform. It seems the majority of users (myself included) are less inclined to put a new kernel through its paces for more than a day or two before reaching a conclusion. With kernel and rom releases being far more frequent and accessible than, say, expensive user-upgradeable hardware, it makes perfect sense. Still, I often wonder if a given kernel or rom release has been deeply and broadly tested enough to truly provide the developers with reliable feedback. Dedicated beta testers are a godsend, but I'd venture a guess that such groups are frequently unavoidably too small to serve as a truly representative sample set. I'd be an idiot to overlook all of the amazing development progress many of us have grown used to (hence, "spoiled"), but I feel it would be shortsighted to assume that only a rare few serious devs out there have given up their free time on red herrings.
At last, there is an actual question here. I don't expect a concrete or "right" answer, though. To anyone reading, I ask: do you feel that developers and their projects (and thus the rest of us) would see any appreciable benefit from the widespread adoption of longer testing times? Obviously you don't need a week to figure out you're in a boot loop, but I feel like a lot of cumulative minor errors end up rearing their ugly heads despite a user thinking their configuration is "stable" after only a day or two.
NOTE: Despite the presence of a question, the overall intent of the post didn't seem to fit the Q&A section. I apologize if this was an incorrect assumption.
No. When something is released on xda it is immediately in "testing". For a developer to have user feedback, logs, and the discovery of potential app conflicts is what xda is all about. And you can see that type of "growth of an app" happen in android apps section. Many apps there started as v.01 alphas and are now full releases on the market (thanks to testings from courageous xda addicts). But for the non commercial side of things roms/kernels/themes. Being on the cutting edge comes with risks or if you're not sure of something, resist the urge and monitor the thread for a week or two and see if the modification suits your needs.
good day.
Chopper, I agree in principle but not completely in practice (though you have a lot more experience to speak from). As far as the "in testing" nature of projects posted here, I suppose my uncertainty goes back to the question of the quality and consistency of said testing. The kernel.org fiasco comes to my mind as a potentially interesting case study if significant time and resources could feasibly be allocated. I was intrigued to see a situation where such a large and varied (device-wise) group of users had to "settle" with the existing builds for so long. This allowed more time than usual for users to test and agree on the stability of a given build. Whether that was truly widespread or meaningful, I cannot say. To your closing point though, I was happy I decided to stick with 35 for a few days once the nightlies resumed.
Sent from my SCH-I500 using xda premium
This writer seems to think so.
http://www.theverge.com/2012/2/16/2801916/home-baked-roms-its-going-to-blow-up-sometime-soon
Actually he makes some valid points (and I use a Custom ROM myself).
Absolutely ZERO disrespect intended to the ROM developers here --- we should appreciate their very hard work and opening our devices up to so many other options and enhancing performance.
But after reading this article, what do people think about the safety of ROM flashing .... not in terms of bricking the device (we all know the risks), but in terms of:
A) Unintentionally opening the device up to exploits due to poor coding etc
B) A rogue developer intentionally exploiting to capture data for profit
Are you comfortable doing bank transactions on a rooted android device w/ custom ROM?
Interesting question
I have never even thought about what I do and don't do on my custom devices.
Forget the internet banking etc, there's also the entire gamit of email, social sites, work email etc etc
Just as well I trust you all!
This is definitely a concern......
Here in Korea though, the banking apps do not allow you to use them with a rooted device.....So each time, I have to unroot my device in order to do banking.
I do not know, however, if once I root again it would give the developer or hackers access to that data......
Something to think about as well though!
I realized: I never looked for an app that investigates security issues on a smart phone.
perhaps someone with knowledge in this field can give a few hints to usefull apps?
and yes, "I am with stupid too"
Motorola Defy+ with Quarx's CM9 nightlies and most of the time I still have no clue to what I am doing precisly.
But on the bright side: I do not use my phone for banking, there's nothing to "bank around"
Hmmm -- I had never considered that banks would block it -- have not tried yet. You make a good point about what remains on the device later -- at a minimum clearing browser history is a good idea -- but even that could be circumvented with a devious enough approach.
[email protected] said:
This is definitely a concern......
Here in Korea though, the banking apps do not allow you to use them with a rooted device.....So each time, I have to unroot my device in order to do banking.
I do not know, however, if once I root again it would give the developer or hackers access to that data......
Something to think about as well though!
Click to expand...
Click to collapse
I agree. From what I have seen most of the "advanced" posters here dismiss antivirus packages as a waste of time and money and they could well be right. Still I have not been able to find any real discussions on the risks the article I posted raised. It would be great if some of the more "expert" members here could offer their views.
I am loving my rooted G-Note with custom ROM ---- but I do not really have confidence in Android and its various hacks yet. Unfortunately the alternatives are rather poor.
gentle_giant said:
I realized: I never looked for an app that investigates security issues on a smart phone.
perhaps someone with knowledge in this field can give a few hints to usefull apps?
and yes, "I am with stupid too"
Motorola Defy+ with Quarx's CM9 nightlies and most of the time I still have no clue to what I am doing precisly.
But on the bright side: I do not use my phone for banking, there's nothing to "bank around"
Click to expand...
Click to collapse
I would say I agree and disagree with the article.
For me personally, when I decide to get all flash happy with my Android devices, I tend to not put any information regarding banking or credit cards. Logically, at least to me, the concerns sited in this article do occur to me. Then again, to be honest I do not put any of this information on my non jail broken company secured and encrypted I phone either. Call me paranoid.
Where I disagree with the article is in the insinuation that using a stock ROM with apps downloaded from let's say th he iTunes store is really much more secure. If a baked ROM can be pulling information behind your back, and somehow bypass security measures written into a banking app, why could not a fart app some momo downloads to be the life of the party do the same?
Flyer
I have been thinking about this ever since I've rooted my phone and flashed the first custom rom...
-and I still don't have a real answer.
Thats why I prefer stock ROM
finally its your (user) wish, weather to use custom rom or stock rom.
none of the developers are forcing to use their custom rom.
rom development is hobby,passion, and part-time for some of developers.
my few words.pls correct me if I'm wrong
Ever heard of pdroid? Droidwall?
reversegear said:
finally its your (user) wish, weather to use custom rom or stock rom.
none of the developers are forcing to use their custom rom.
rom development is hobby,passion, and part-time for some of developers.
my few words.pls correct me if I'm wrong
Click to expand...
Click to collapse
You are not wrong, but you are definitely off topic.
This is so one sided. You can say the same about any OpenSource program with small userbases. Take any little Linux Distri, any small OSS and you get to this problem quickly. Most of us can't review the source code properly so we have to rely on others. But at least you CAN rely on someone. You can't rely on anyone at closed source programs.
That's why you use Truecrypt for encrypting your hard drive and not Bitlocker, that's why you should use a Linux Distri and not Windows and that's why i use OpenSource ROMs and not the closed source StockRoms and even try to have as much OpenSource Apps on my Phone as possible.
Just my 2 cents.
He has the points and those are sorely his.
Calling other ROM flashers idiots is ridiculous and not very nice. In fact, based on what he typed, he seems to be an idiot himself.
Now to other Rom flashers, as long as then understand the risk of doing so, they entitle and fully responsible for their actions, no need to teach them.
Security issue? I drive a car to a bad area, get off, windows still lower, not even care to lock the car. That is my choice.
Now I'm going to the very nice, high educated area, I choose to lock the car, put the steering-wheel lock on. Again, it's my choice. Home wireless network, I choose to set the password or not, it's my decision. I understand the risk of not doing that. And if I choose not to do that, it doesn't make me an idiot.
Next, not all baked ROM are based on leaked official one. CyanogenMod team is well-known and they based on the Google source code, ASOP, not a leak one from vendors.
So, if ROM flashers realize what source they use, they're all set.
Writing a long article with just one-minded lopsided thinking like this is pretty lame.
an0nym0us_ said:
Ever heard of pdroid? Droidwall?
Click to expand...
Click to collapse
Pdroid: looks very promissing but you need to be a programmer and only for Gingerbread.
Droidwall: from what I understand from it it is a kind of fine-tuning of your data traffic. Pdroid goes much, much further and I would prefer it.
A real shame I'm not a developper/programmer and also very happy with my custom ICS ROM.....
On the bright side; I like tweaking but not social networking or any other more "dangerous stuff" Just like I'm used on my PC.
I've never bothered with a custom ROM, partly because I just realise that pretty much everything I could do with a custom ROM, I can do manually with a rooted phone. I don't like to install a package of software someone else thinks I should use, I prefer to pick and choose the stuff I want. Security concerns never really bothered me, I don't care too much about the security of my phone (I guess maybe some people would be annoyed at me if my contacts were stolen or something, but other than that there isn't really anything I care about on my phone). I never do online banking etc. on it, but that's just because that's something I do very rarely and only do when I'm at a computer anyway.
gentle_giant said:
Pdroid: looks very promissing but you need to be a programmer and only for Gingerbread.
Click to expand...
Click to collapse
You don't need to be a programmer. All you do is get your ROM zip, run the PDroid patcher on the ROM zip, it'll give you a patch zip, flash the patch zip in recovery, install PDroid from market. And I think there are unofficial ports to ICS possibly.
Doesn't stop me from flashing custom ROMs.
Oh well...?
Sent from the future.
I though the article itself was a bit sensationalistic but at the same time I think changing the ROM in a system (not to mention giving root permissions to apps) is a lot more potentially intrusive than downloading apps from Itunes or Gplay.
Anyway I like my custom ROM setup but I sort of feel like I am whistling in the dark at times. I think a lot depends on how sophisticated we are as users.
Case in point:
When I flashed my ROM for the first time, I freaked out seeing a bunch of Chinese names every time I made a call to certain numbers. The good thing about XDA is if you search you can find anything about ROM issues and in this case I learned that this was due to the developer using the contacts part from the leaked Chinese ICS and it had something to do with a "Phone locator service" that could be disabled. Ok so I disable and go back to whistling in the dark --- but I have not been able to learn what the phone locator service is in the first place or WHY i had Chinese names showing in my calls.
As a relative Noob I can follow instructions from most of the generally well written instructions on XDA and not get into trouble --- but (rhetorically) do I really understand the background issues and risks with some of these things?
What is this phone locator service anyway? Why the Chinese Names and Locations in the call indicators?
mcord11758 said:
Where I disagree with the article is in the insinuation that using a stock ROM with apps downloaded from let's say th he iTunes store is really much more secure. If a baked ROM can be pulling information behind your back, and somehow bypass security measures written into a banking app, why could not a fart app some momo downloads to be the life of the party do the same?
Flyer
Click to expand...
Click to collapse
Well you are right that we are all responsible for our own choices. I just think it is better for all that people can make as informed as choices as possible. That is why discussions like these can be good (even if the article was inflammatory).
To extend your analogy, maybe you think it is your choice to leave your car unprotected. But maybe your insurance company will disagree and try to teach you better? Maybe the police inform you to secure your car because you make more work for them when your car is stolen?
So as a car driver it is your choice, but many might argue that the community of car drivers needs to be educated on the risks of their behavior so that they can make more informed decisions. Then you benefit and the community benefits (keep insurance rates down, free up police resources etc.)
I hope I made sense
votinh said:
Now to other Rom flashers, as long as then understand the risk of doing so, they entitle and fully responsible for their actions, no need to teach them.
Security issue? I drive a car to a bad area, get off, windows still lower, not even care to lock the car. That is my choice.
Click to expand...
Click to collapse
I'd rather take the risk and enjoy life than sit on the sidelines. Considering that all smartphones have vulnerabilities, stock or no, I'll take my chances. I also have a bit of faith left in humanity in general and more so some in communities like XDA and Rootz where the general idea is clearly that these are places for everyone to contribute to everyone else, not to come in and scam.
Let's be real: if someone comes through here and drops something that ends up defrauding other for every person involved in coding the malicious item there are ten more capable devs who will have the motivation to take them to task in most unpleasant ways. I, for one, would not put my butt on the line by choosing a dev forum to release or market my malware.
So I've had my Infinity for some time now, and I love it. I was thinking about unlocking my device and I just wanted to see if it was worth it in time and such. I looked in the development section to see if there have been any issues with flashing new roms and stuff and it seems to be a lot easier and safer than when it first was being worked on.
I really only use my tablet for taking notes in class or playing the occasional game but if I was to go somewhere I would probably bring it instead of my computer as well. It works fine for what I'm using it for now but I just wanted to know if it would be worth unlocking it and stuff or should I just keep it the way it is.
Do the benefits outweigh the cons of the unlocking process is what I'm really getting after I guess? I would like to hear thoughts and opinions before going ahead and unlocking my device. I've looked the the general discussion and dev section reading things here and there but I want to hear what people have to say after unlocking or why they kept it stock as well.
Well, I'd say that -- generally speaking, obviously, for it heavily depends on your specific usage of the device -- unlocking and installing a good and mature custom ROM provides such bonuses in terms of fluidity, performance and tweakability that it's hard to even consider I would have stayed unlocked.
Especially the stock-based CleanROM is very fluid, and has all the base drivers from the stock edition. I haven't flashed any AOSP/AOKP/CM-based ROMs lately, but I imagine they will have come quite a bit further than they were when I kinda lost interest in them. The main issue for me is the fact that, as far as I know, on these ROMs the keyboard remains incompletely supported, and the touchpad cannot be switched off -- a deal breaker to me, since I tend to touch it lightly when typing, and thus interject words with random letters here and there, necessitating a complete copy edit before I can do anything with my typed text. Bummer.
The custom ROMs really have shown remarkable improvement, and provide tangible improvement over the stock ROM. The recommendation is easiest if you are (slightly) unhappy now: unlock it, and flash a custom ROM. Things get a bit more complex when you're actually happy with the device as is. Choice is then to a) stay locked and never know better, or b) take the "risk", unlock, flash a good custom ROM. I believe you will be slightly amazed in the latter scenario...
NOTE: I unlocked at the very first opportunity, and have flashed pretty much all the custom ROMs at one point or another in their existence and development up to now. I realize I might not be the most objective person to advice you in this case. Maybe someone who has stayed unlocked up till now will chime in and provide an opposite view. Take care!
Took me almost 3 months to unlock.
I'm a risk taker tho.
The principles of ORM could be applied here:
Accept risk when benefits outweigh the cost.
Accept no unnecessary risk.
Anticipate and manage risk by planning.
Make risk decisions at the right level.
Also remember the 3 levels of ORM lets take a look:
In Depth
In depth risk management is used before a project is implemented, when there is plenty of time to plan and prepare. Examples of in depth methods include training, drafting instructions and requirements, and acquiring personal protective equipment.
Deliberate
Deliberate risk management is used at routine periods through the implementation of a project or process. Examples include quality assurance, on-the-job training, safety briefs, performance reviews, and safety checks.
Time Critical
Time critical risk management is used during operational exercises or execution of tasks. It is defined as the effective use of all available resources by individuals, crews, and teams to safely and effectively accomplish the mission or task using risk management concepts when time and resources are limited. Example
*Straight from the US Dept of Defense!
Frostbiter said:
So I've had my Infinity for some time now, and I love it. I was thinking about unlocking my device and I just wanted to see if it was worth it in time and such. I looked in the development section to see if there have been any issues with flashing new roms and stuff and it seems to be a lot easier and safer than when it first was being worked on.
I really only use my tablet for taking notes in class or playing the occasional game but if I was to go somewhere I would probably bring it instead of my computer as well. It works fine for what I'm using it for now but I just wanted to know if it would be worth unlocking it and stuff or should I just keep it the way it is.
Do the benefits outweigh the cons of the unlocking process is what I'm really getting after I guess? I would like to hear thoughts and opinions before going ahead and unlocking my device. I've looked the the general discussion and dev section reading things here and there but I want to hear what people have to say after unlocking or why they kept it stock as well.
Click to expand...
Click to collapse
Without unlocking in order to run custom rom/kernel/mod, I probably throw my tablet in the trash. At the time I hated myself for purchased this piece of sh.... Once I unlocked, my tablet now is working so smooth and I love it. if you have been using your table for a while the chance for hardware defects is at the minimum. Unlock/root is no risk at all, pretty much straight forward, of course there always will be a .01% risk for anything.
Thats OK said:
*Straight from the US Dept of Defense![/COLOR]
Click to expand...
Click to collapse
I wanted to ask you where that came from, as it reminded me very, very strongly of the principles at the Royal Military Academy here in Holland. It's always the same everywhere in the military, I guess.
MartyHulskemper said:
I wanted to ask you where that came from, as it reminded me very, very strongly of the principles at the Royal Military Academy here in Holland. It's always the same everywhere in the military, I guess.
Click to expand...
Click to collapse
I used to hold training classes for new employees at an aircraft repair base in Utah.
A portion of the induction briefs included Operational Risk Management.
Those are from some of the instructional guidelines for the classes I had to teach.
Hadn't thought about that stuff since I retired.
Just popped into my head last nite for some reason.
Coming from the ground up
I unlocked and the only downer that I've found so far is the drm issue, you can get google play movies to work but it will NOT be in HD. Seems to be an Infinity issue.
I was using Cleanrom and it's definitely really nice, just installed paranoid android last night and LOVING it. Chrome actually works! Tweaked the settings so I get the Phone/hybrid ui in Chrome instead of the tablet ui and it's much better.
If the Movies drm thing is not an issue for you, I'd say you really have nothing to lose by unlocking.
Thanks guys for the opinions, I'll probably be unlocking my tablet when I have the time to sit down and make sure I do it right.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2