Simple question: does anyone really review the code????
ogntng said:
Simple question: does anyone really review the code????
Click to expand...
Click to collapse
Yes. You'll see a lot of 'contributors' on any ROM's GitHub page and as they add/tweak features, fix bugs and clean things up, the code is being checked constantly. These can be dozens of even thousands of people checking each other's work. This doesn't even consider the people that just look at the code, which everyone is free to do.
Here's the people working on a crDroid ROM for the OnePlus 7T:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's almost 10k people involved on a kernel:
On our side – the moderator team – we do a lot of version checking to see if the published versions of components actually match the ones in the source code. Of course, as there is a tremendous amount of code in a ROM, not everything is meticulously being reviewed line by line but anything remotely malicious tends to stand out and when there's the slightest bit of doubt a deeper analysis will occur by multiple parties. Next to all that there are also automated reviewing processes and built in safeguards.
Related
Here's a comparison chart I just created of warranty and insurance coverage for smart phones.
Comparison is between SquareTrade, Worth Ave Group, ToughCell, and Sprint TEP. I did not include others as I am not really familiar with them or haven't heard of them. I have Sprint, worked with SquareTrade, and will probably be going with Worth Ave Group in the near future. I did my best to be as accurate as possible but things may be different! Feel free to suggest corrections and/or additions. I'll update/fix it and repost whenever I get the chance.
**This information may not be 100% percent accurate so ask questions to whichever party you choose before signing up for anything, anywhere! Things change, and information found on their websites may change or may be incorrect! All information in this chart is collected from their respectful websites and recent experience**
*Coverage compared is for SMARTPHONES only, NOT iPhones or anything else* No, I'm not saying iPhones aren't smartphones, they have their own category on most of the websites of these providers.
Green is a little shout out to Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To download ROMs from http://tamsuicm11.github.io, be sure your browser works correctly.
After scratching my head for a number of months, asking myself what this site might be good for, I realized that my browser (Firefox in this case), doesn't handle the javascript properly. Thus it displays the menu bar, but never any content.
I suppose this is the main reason people are asking so often for the TamsuiCM11 releases at http://forum.xda-developers.com/xperia-j-e/orig-development/tapioca-cm11-kernel-3-4-t2581726 . They just don't see the website content and thus think the only way getting this ROM is building it by themselves.
Hope this helps.
Link Not Found
typ0rary said:
To download ROMs from http://tamsuicm11.github.io, be sure your browser works correctly.
After scratching my head for a number of months, asking myself what this site might be good for, I realized that my browser (Firefox in this case), doesn't handle the javascript properly. Thus it displays the menu bar, but never any content.
I suppose this is the main reason people are asking so often for the TamsuiCM11 releases at http://forum.xda-developers.com/xperia-j-e/orig-development/tapioca-cm11-kernel-3-4-t2581726 . They just don't see the website content and thus think the only way getting this ROM is building it by themselves.
Hope this helps.
Click to expand...
Click to collapse
mega.co.nz is now not available
& what about CM11 for xperia e dual
I use Firefox and it works correctly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but thanks for informing, I will change something
Here's a daydream that old school hackers out there might recognize if you've ever used CDE on Unix or VMS. This is an Android port of Jeff Butterworth's xswarm. This was mostly done as a learning project and I still have a few questions resulting from it. Though for now it's done, working, and I think I've added enough options. I'll take bug reports and pull requests but don't expect too much in the way of additional features.
Anyway, here's some shots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--- Non-devs can skip the following questions. ---
Is there a color picker library that uses fragments and also allows hex entry? lomza/android-color-picker looks like one of the better ones, though I'd really prefer something with text input for exact values as well.
I'm also trying to come up with a way to programmatically pull in resources so I don't have to do ugly enumeration such as this (see TODO sections). The EditTextPreference dialogs do bounds checking before updating the summary field, but one thing that throws a wrench (or IllegalStateException) into things is that EditTextCheckBounds isn't attached to the Activity so you can't call getResources() within that function without jumping through a lot of hoops.
Source: https://github.com/coax75ohm/droidSwarm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Is It and What Does It Do?
Hey guys, this is just something I was working on, to dabble in the new material design introduced with Android 5.0 Lollipop. Wanted to play around with some of the new stuff, while also making something somewhat useful at the same time. It's a really simple app that allows you to perform USSD tasks with buttons instead of having to type it out.
This specific one is for AT&T Users, but I have plans to do it for other networks.
If you do know more codes that can be added or any of the existing ones that needs to be corrected let me know!
Plans for Upgrades
In the really near future, I'm hoping to add much more codes as well as addtional functions. However, I don't use AT&T, so if anyone can suggest additional codes/features, it would be helpful.
Download
Click here
Contact for Additions or Corrections
Twitter: @T3smash
first. thank you for this. very useful. :thumbup:
err on the side of kindness
mrrocketdog said:
first. thank you for this. very useful. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Thanks!
What the hell is this system component?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not malicious if that's what you're wondering.
Internally there are *dogfood* and *fishfood* versions of some apps, so you can *dogfood* (verb) and *fishfood* them respectively.
Dogfooding is using an app or feature shortly before it's publically released. The term *dogfood* comes from the expression ["eating your own dogfood"](https://en.wikipedia.org/wiki/Eating_your_own_dog_food).
Fishfooding is using an app or feature really early in its development before it's even really finished.
The term *fishfood* actually comes from the Google+ team inside of Google. Google+ was internally codenamed Emerald Sea. During its early development, it wasn't finished enough to be considered dogfoodable, so they called it fishfood. Because Emerald *Sea*.
Click to expand...
Click to collapse
Reddit
So google sees people using very early unreleased apps as fish, and people using "beta" apps as dogs, interesting.
So people using the actual releases must be apes. Good to know. Google is absolutely correct, most modern humans are lab rats following their one and only true purpose, being a lab rat.
Thanks anyway.