This software is desiged for you.
*****Basal Body Temperature V1.1*****
UPDATED AT JUN 21,2009
how does this work?
Record woman's basal temperature to your PDA/PHONE with this software. So, you can see the SAFE dates obviously.
I think he might have been asking what exactly the safe dates are and how to interpret the results. Perhaps checking to see if your work is sound. Maybe a 1 instead of an 0 somewhere in the code, may lead to a little Timmy, so perhaps a thorough explanation of how it works, and a disclaimer stating you are not responsible for any unfavourable outcomes as a result of using this software, and that the only true way to prevent unwanted pregancy is abstinence.
And then if you are still willing to accept the risk that you may be bringing a child into this world, using a second non-interfering form of birth control may be prudent. I say non interfering in the sense that double bagging is actually worse, but oral contraceptives in conjunction with a condom every time significantly lowers the risk of failure. Condoms have failure rates as high as 20% with not perfect use, and birth control has failure rates of up to 5% even when taken religiously, higher of course when there are missed pills. Want an even safer method? Use the pill, condoms, the withdrawal method, and basal temp measurement. Still nothing beats abstinence. Oh and one final thing, using just the pill doesn't protect against STIs, hence another tick in the WIN column for condom use even in the setting of oral contraceptives.
Hopefully the above info will be useful to at least one person in which case the time it took to write is worth it.
muchski said:
I think he might have been asking what exactly the safe dates are and how to interpret the results. Perhaps checking to see if your work is sound. Maybe a 1 instead of an 0 somewhere in the code, may lead to a little Timmy, so perhaps a thorough explanation of how it works, and a disclaimer stating you are not responsible for any unfavourable outcomes as a result of using this software, and that the only true way to prevent unwanted pregancy is abstinence.
And then if you are still willing to accept the risk that you may be bringing a child into this world, using a second non-interfering form of birth control may be prudent. I say non interfering in the sense that double bagging is actually worse, but oral contraceptives in conjunction with a condom every time significantly lowers the risk of failure. Condoms have failure rates as high as 20% with not perfect use, and birth control has failure rates of up to 5% even when taken religiously, higher of course when there are missed pills. Want an even safer method? Use the pill, condoms, the withdrawal method, and basal temp measurement. Still nothing beats abstinence. Oh and one final thing, using just the pill doesn't protect against STIs, hence another tick in the WIN column for condom use even in the setting of oral contraceptives.
Hopefully the above info will be useful to at least one person in which case the time it took to write is worth it.
Click to expand...
Click to collapse
Well put my friend....and Im in the STD prevention business.
muchski said:
I think he might have been asking what exactly the safe dates are and how to interpret the results. Perhaps checking to see if your work is sound. Maybe a 1 instead of an 0 somewhere in the code, may lead to a little Timmy, so perhaps a thorough explanation of how it works, and a disclaimer stating you are not responsible for any unfavourable outcomes as a result of using this software, and that the only true way to prevent unwanted pregancy is abstinence.
And then if you are still willing to accept the risk that you may be bringing a child into this world, using a second non-interfering form of birth control may be prudent. I say non interfering in the sense that double bagging is actually worse, but oral contraceptives in conjunction with a condom every time significantly lowers the risk of failure. Condoms have failure rates as high as 20% with not perfect use, and birth control has failure rates of up to 5% even when taken religiously, higher of course when there are missed pills. Want an even safer method? Use the pill, condoms, the withdrawal method, and basal temp measurement. Still nothing beats abstinence. Oh and one final thing, using just the pill doesn't protect against STIs, hence another tick in the WIN column for condom use even in the setting of oral contraceptives.
Hopefully the above info will be useful to at least one person in which case the time it took to write is worth it.
Click to expand...
Click to collapse
Thank you very much
This kind of application can be used by Medical field practitioners and professionals as well...
Good thing... and nice idea...
)
Ps. the Title of the thread is CATCHY! XDD
I thought I am in a medical forum
muchski said:
I think he might have been asking what exactly the safe dates are and how to interpret the results. Perhaps checking to see if your work is sound. Maybe a 1 instead of an 0 somewhere in the code, may lead to a little Timmy, so perhaps a thorough explanation of how it works, and a disclaimer stating you are not responsible for any unfavourable outcomes as a result of using this software, and that the only true way to prevent unwanted pregancy is abstinence.
And then if you are still willing to accept the risk that you may be bringing a child into this world, using a second non-interfering form of birth control may be prudent. I say non interfering in the sense that double bagging is actually worse, but oral contraceptives in conjunction with a condom every time significantly lowers the risk of failure. Condoms have failure rates as high as 20% with not perfect use, and birth control has failure rates of up to 5% even when taken religiously, higher of course when there are missed pills. Want an even safer method? Use the pill, condoms, the withdrawal method, and basal temp measurement. Still nothing beats abstinence. Oh and one final thing, using just the pill doesn't protect against STIs, hence another tick in the WIN column for condom use even in the setting of oral contraceptives.
Hopefully the above info will be useful to at least one person in which case the time it took to write is worth it.
Click to expand...
Click to collapse
...I'm lost.
Incidentally, if you're going to use basal body temperature as a guide, do it in an attempt to get pregnant, not in an attempt to determine when your "safe" days are. The basal body temperature is elevated by progesterone, which is released by the corpus luteum AFTER YOU OVULATE. Meaning it's fine to tell you when to have sex if you want a child, but a little too late after the fact if you are trying to avoid that, since by the time your temp goes up you've already released an egg.
Updated at Jun 21
N35 said:
Record woman's basal temperature to your PDA/PHONE with this software. So, you can see the SAFE dates obviously.
Click to expand...
Click to collapse
Hi how do i do that (Record woman's basal temperature)any guide or little guide would helpful.bcos very few men know it.
thankyou
ZzFDKzZ said:
...I'm lost.
Click to expand...
Click to collapse
And I thought I was the only one...
itsme_4ucz said:
Hi how do i do that (Record woman's basal temperature)any guide or little guide would helpful.bcos very few men know it.
thankyou
Click to expand...
Click to collapse
VERY few men know
so what does this help determine?
to know when to have sex with less of a chance of getting pregnant?
so wait, what is a basal temp?
make that three, im quite confused.
neoslan said:
so wait, what is a basal temp?
make that three, im quite confused.
Click to expand...
Click to collapse
There's a bit about it here: http://www.babycentre.co.uk/preconception/suspectingaproblem/chartingyourtemperature/
Taking temp won't help TODAY, but after tracking for a couple months the pattern for each woman will show up. Coupled with other indicators this method is extremely effective (12 yrs and no kids yet...).
Basically you know that she ovulates on say day 13 typically of her cycle. Count 7 days before that and start using a barrier method (or abstinence...right). 7 days is the max time for sperm to live. Count 2 days after ovulation, eggs live 24 hrs, extra day to be safe or if she's a double ovulator...
Don't take my brief overview as sufficient info, needless to say do more research!
Proposal for improvement
Not practical software, you need manual input of all data.
Would be better if the program could do a direct data aquisition (on phones with temperature sensor) and ...you simply stop the phone inside ...
Zeno2 said:
Not practical software, you need manual input of all data.
Would be better if the program could do a direct data aquisition (on phones with temperature sensor) and ...you simply stop the phone inside ...
Click to expand...
Click to collapse
And phone will enjoy all the fun ? :-D
Well I don't know... Letting my phone have my place in life. This is useful indeed. But as a suggestion, how about letting us know about more than one woman? It may be useful, to
- Preview the aproximate dates your mom, sisters, girls, will be on PMS. (so you go hide, or something)
- In case some of us are pimpin' an have more than one girl.
Related
Well I was just reading a thread about someone buying a Vibrant from someone who "found" it and this person was looking for a way to bypass WaveSecure.
We all know that with a little know how that it is possible with Recovery Mode.
The question I have is there a way to prevent even a Recovery Mode reflash? To absolutely stop someone from touching the ROM at all?
I know the Security Apps out right now can track you from GPS, wipe the phone remotely, etc... But can it stop someone from reflashing a ROM?
If there is a app out there like that please let me know, but if not, what would it take to create such a app.
What are YOUR thoughts??
What if this happens and then you brick for some reason need to reflash and it's locked. I would just bank on the fact that most people think that it's a "Droid" phone and don't know ****.
I was hoping for a question like that.
Either there is a security measure which at some point of using Recovery that it asks for a password or pin. Something that will allow you to access it securely and nobody else.
Yes, it is a droid, very true, but how many droids are out there now, are going to be out there, and with the new laws that allow you to unlock your device and pretty much do anything with it, more and more people are going to start playing around. Not only that, there is always somebody who knows someone, you know.
Personally myself, I would feel secure with having an implementation like this, everything else is pointless.
It's sort of like having a anti virus on your computer but not scanning for rootkits, only viruses.
The idea of that app sounds nice and all that but I seriously doubt that the average Android user would know about flashing ROMs and all that. But if it does get into the hands of somebody that does know how to do it then it can be a problem.
jzero88 said:
Yes, it is a droid, very true, but how many droids...
Click to expand...
Click to collapse
First of all these are android devices / android phones. I was mocking the people who call these phones "droid" phones.
Now on topic: All it takes to break this security is for one person to say, "I forgot my password on for the ==sUPERlOCKER== what do I do to get access?" Then all your worry is for nothing again.
What has been done can always be undone.
Sure, unlike me, I never forget my passwords. Especially for something this serious.
Second, of course something can be undo, but to what extent, after hearing your lack of concern makes me think you don't even have a lock on your phone
Again, would you rather have a password like "1234" that is easily guessed, or would you rather have something like "00LowJK54889$3%#". It's really a matter of personal security.
You sound like one of those people who would have Security Cameras, but never has the DVR on to record anything.
I'm saying your idea is bad. I have illustrated why. You have no counterpoint other than that I am 'relaxed' about my phone security.
How about this, keep your phone in your pocket or hand? 100% security.
This should be in general and not development
Sent from my Vibrant using xda app
This has been discussed a few times, you could compile your own recovery image and program in a password while at it, or you can accept that 90% of theives(or people who would find your phone) cannot get to recovery. If I found a phone then yeah I would go straight to recovery but I'm not your average user.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm saying your idea is bad. I have illustrated why. You have no counterpoint other than that I am 'relaxed' about my phone security.
How about this, keep your phone in your pocket or hand? 100% security.
Click to expand...
Click to collapse
First, my idea is not bad, give it time, you will see.
Second, I do not have a counterpoint because my main point is stated in the first post. Read again.
Third, I don't care if you are relaxed about your security or not. This post obviously is not for you, another negative person who stunts development if they do not see a logical use for themselves.
I wish you the best and hope that you do not need to ever use such a tool or measure. Take it easy.
This has been discussed a few times, you could compile your own recovery image and program in a password while at it, or you can accept that 90% of theives(or people who would find your phone) cannot get to recovery. If I found a phone then yeah I would go straight to recovery but I'm not your average user.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
On the Vibrant forums? Haven't seen anything yet.
Also, I am not betting on a thief or someone who found the phone to be able to get to recovery, I'm worried about who these people might know. It's surprising to see how many people out here think that they are the only person in a 20 mile radius who knows how to do such mods... Maybe it's just the people I know but I know quite a few people who can easily google and find a way, easily.
I can bet that 90% of people here do not know anything except following directions, no pun intended to those who do. I definitely do not know half of what I should know, but again, is it really that hard?
Your own logic defeats what you are saying here. Don't you understand OP?
If there is a security measure, there will be a work around it? So why have more than ONE thing for the uneducated masses and stop there?
If the person who steals your phone knows someone who could get around WaveSecure, or any other security application. Then that same person can get around ANY AND ALL other types and forms of theft deterrent. If not, they will know someone, ask on forums, etc. UNTIL they gain access.
zaduma
Then why have any security on anything at all?
You my friend make no sense, good day!
jzero88 said:
Then why have any security on anything at all?
Click to expand...
Click to collapse
Ok, I will lay it out as simply as I can man. I do not want to argue, but you are missing why this is impossible to accomplish.
The existing security layers can be compromised by lets say... 10% of the population, seeing as most people who are thieves do not talk about it, most people dislike thieves.
So effectively 90% of people will be stopped dead in their tracks by having WaveSecure, etc.
The 10% who are not stopped however, can not be stopped by any means. None. They are the people who read these forums, have technical ability, etc.
Therefore having one layer of security means 90% of people are stopped from using your device. But it has ridiculously diminishing returns. With two layers, say stopping access to recovery, 10% are now stopped. Just boot into download mode and flash with odin. Stop download mode? First of all how? Second of all, there has to be a workaround for people who forget their passwords and stuff. And guess what, those 10% will know about that as well.
So please, address these issues and resolve them somehow, and your idea has merit. Without doing so you are wasting your time.
Also, much to your liking I will assume, I will no longer be posting in this thread due to your constant elevation of flaming.
Any security pro will tell you, if you have physical access to a computer, you can make it usable for you. The only real security you can hope for its to prevent access to your data by the thief. That's what full disk encryption and such is about. For our phones, we could achieve this much with a custom kernel perhaps, but how would you enter the password? No keyboard at that level.
The cellular providers can prevent the stolen phone from getting on their networks, and some do, but that's about as far as it goes.
Its like having a lock on your front door.. Its only going to keep out the honest people... Thats what they are made for, honest people, because dishonest people will just kick the door in.. And the good thieves can pick a dead bolt...
Sent from my SGH-T959 using XDA App
I'm starting to think this request/question is for the wrong crowd, truly it is...
If you build it they will hack it... Hands down... Look at the droid x, the unhackable phone, it took 5 weeks..
Sent from my SGH-T959 using XDA App
I agree, never did I not. This thread wasn't to debate whether a security measure could be hacked or not, the thread was created to see what we could do to implement such a measure.
I am totally aware of that. I know that if there is a will there is a way.
PERSONALLY, that is something I wouldn't mind having. Though some of you disagree and have a right to your own opinion, that is beyond the point. I am trying to see if a) is it possible. and b) what it would take to do so, and possibly c) if anyone was interested in trying or helping out.
So feel free to express your opinion. Mine is that you can never have enough protection cuz I would never bring a knife to a gun fight. But that's just me...
BTW, those who hacked the unhackable phone I would consider being part of the .01%.
jzero88 said:
I'm starting to think this request/question is for the wrong crowd, truly it is...
Click to expand...
Click to collapse
If you mean people that know how things work, I suppose. It's the same problem as drm. When you understand why that's not possible, you will understand this. Read up on jtag as well, you can't protect against that. 90% is about as good as it gets.
So, if rooting the g tablet is the way to go, it surely must stand up to a few simple speed checks. Has anyone posted various root's numbers or have some to post?
Stuff like, time to boot? Time to load common apps? Time to open the same web page? Frames on games? Time to download? Max browser pages open? Other relevant numbers welcome...
As far as I can tell, without any objective numbers comparing root performance, a lot of this rooting fad raves could just be subjective reported elation about being able to be different.
Granted, originally, the Gtab OS had some flaws. That's old news, get over it. How do the current roots compare with OTA version 3588? I'm somewhat shocked not one of the pack of geeks that have rooted their G tab hasn't backed up their raves with real numbers...
Granted, being rooted to the latest vegan might get access to the full Android market, and perhaps even future updates in Android... However, if I'm finding most of what I want at Amazon Android, is rooting worth the trouble until the roots and android versions stabilize? Show us the NUMBERS...!
I've been there done that with this subjective stuff long enough not to be swayed without real numbers...
Also, do any of these roots do OTA auto updates or do root updates require a download & re-root? Just asking...
Jesus christ if you can't do a simple search for benchmark tests then I highly suggest getting the ipad2. I hear that the ipad 2 reads your mind so out don't have to do any search. We've only had a kazillion threads on this.
Edit
This is not to mention all the YouTube vids on this people have posted.
Edit again.
Actually, here are a few.
http://forum.xda-developers.com/showthread.php?t=1047098&highlight=benchmark+2011
http://forum.xda-developers.com/showpost.php?p=12984546&postcount=9
http://forum.xda-developers.com/showpost.php?p=12986416&postcount=10
http://forum.xda-developers.com/showpost.php?p=12986416&postcount=10
Edit again.
I'm serious, I highly suggest the ipad 2 to everyone I talk to. Speaking as someone who repairs computers as a side job, I'm fully aware that most people want to be spoon fed everything, which is why the ipad 2 is the ideal device for most people. If people want to complain about nothing, let apple deal with them.
Thanks for the links.
However, as best as I can tell, they seem to verify that the OTA updated Gtablet is about the same speed as Vegan in the benchmarks when the CPU speeds are similar.
However, do the benchmarks used translate into much of relevance to speed of actually using the tablet to open programs, boot the tablet, download & open web pages. Stuff that people actually do with the tablet... Unless that's what the benchmarks are testing... But that info isn't provided in the links. Again -- weak...
The numbers and detail provided in these links deserve barely more than a C grade, if that... And what they provide seems to be at equal speeds, the current OTA updated gtab OS works fine... As long as you don't need the full Adroid market...
You Tube links? As best as I can tell, not one of them is an objective comparison with the OTA 3588 update gtab. They are just videos of vegan working... As far as real world numbers and comparisons -- Grade D-...
Where are the Grade A numbers? It's not that I don't believe the ROMs are not an improvement, it's just where are the numbers to support these raves?
What exactly are you looking for? There are no hard numbers when it comes to real world use, just your user experience versus mine.
You're not telling us what you want. You said you wanted numbers so I gave you a bunch. Then you say you don't want those numbers. So, I ask again. What do you want?
I'll be brutally honest on this one. Vegan isn't that fast. From all my tests, Calkulin+Clemsyn combo is by far the fastest custom rom+kernel for the gtab.
After trying out everything, I'm back to Calkulin+Clemsyn combo.
Would you like me to make a video of myself openning various programs and post it for you? What do you want?
I'm thinking you should drop that 'r' from your handle.
You also have a misconception of what rooting is/does.
To become root in Linux/Android is to gain administrative privileges. In windows root would be called Administrator. Gaining root privileges gives you the ability to change system files and settings, NOTHING MORE. By itself it does nothing.
Now boys...
The fact is that if you need numbers, reports,testimonials or anything else to justify mucking around with the gtab thenyou probably should just get an iPad. Nothing to prove then -everyone "knows" its the best-no numbers needed! The gtab is for people that don't mind the hardware and software quirks as long as they have the freedom to mess around. Its not about the numbers -its about the experience.
[Q] Why should we ..?!
Droofus said:
I've been there done that with this subjective stuff long enough not to be swayed without real numbers...
Click to expand...
Click to collapse
Well, I am not sure anyone here is trying to sway you in one direction or the others.
Here is how things go in community forums like this one:
- People search for what they got in mind first.
- If they didn't find its either undoable or not that interesting for the community that no one bothered doing it.
- In both case those people are expected to either drop whatever they are wishing for or pursuit it on there own and then share their findings with the community.
In other words, why the heck am I supposed to go beyond whatever benchmarks readily available on the market to show YOU how good/bad are custom firmwares compared to stock ones when :
- custom firmwares are volatile and each couple of days there is a new rom or rom add on or a kernel released (am I supposed to maintain the stats for every single update released ? else how meaningful would be my outdated stats to you? when it represents a ROM that is no longer a candidate)
- the whole flash back and forth and in between roms is a 10~20 minutes process of YOUR time which would suffice to answer all your questions.
If you still need some usability tests (you can use your own stop watch to time through the videos) you might want to check here.
Best of luck,
Zaphod-Beeblebrox said:
I'm thinking you should drop that 'r' from your handle.
Click to expand...
Click to collapse
I think this was the best answer.
The information you are demanding is indicating your ignorance. As was already stated rooting does nothing for performance. If you want numbers you can install each rom and test with each kernel setting whatever your heart desires. Its not likely anyone else even cares as most people only care about stability and a lack of lag
Droofus said:
So, if rooting the g tablet is the way to go, it surely must stand up to a few simple speed checks. Has anyone posted various root's numbers or have some to post?
Click to expand...
Click to collapse
Rooting itself does nothing other than giving you root - the speed of your device before and after rooting is identical.
Now, if you want to talk about the speeds with or without an overclocked kernel, or with a custom Froyo vs custom Ginger vs stock rom, as others have said there are plenty of posts out there.
Mine lasted on the stock rom for exactly one boot after opening the box - so I could copy on the bits to begin the rooting/custom rom flashing goodness.
cu_ninja said:
What exactly are you looking for? There are no hard numbers when it comes to real world use, just your user experience versus mine.
Click to expand...
Click to collapse
What I'm looking for is defined, at least in part, in the first post. Copy and pasted here for your convenience.
Stuff like, time to boot? Time to load common apps? Time to open the same web page? Frames on games? Time to download? Max browser pages open? Other relevant numbers welcome...
If I go to a notebookcheck.net/Computer-Games-on-Laptop-Graphic-Cards, the various card performances in various games are reviewed. The reviews are very professionally and objectively done with detail. Clicking on any specific card opens a detailed review of that card. This allows users to make decisions based upon what sorts of (graphic game) uses they might actually have.
It seems a similar but much smaller objective set of benchmarks could be performed on the various g tablet roots using a set of common uses in part noted above. It doesn't need to be as elaborate or detailed as the video card review site noted above. Just objectively testing a few simple end user tasks would seem to be adequate to get beyond the subjective raves that one commonly sees about this or that OS change...
FYI, part of this is related to my background as a doctor (plus a computer background dating back beyond the Apple II to programming FORTRAN and COMPASS on mainframes in the 1960s). As doctors we are constantly bombarded with all sorts of anecdotal raves about this or that treatment all the time, only to find that they aren't supported by actual objective research -- some cause harm, not healing. Fortunately for those promoting software changes related to raves and fads don't have the potential to cause anyone significant harm... Excuse me if I'd like to see similar objective professional 'standards of care' when it comes to reviewing and analyzing software/hardware fads. I'm sure there are plenty of others in the audience who'd feel the same...
So is this a religious thread, I see Jesus was mentioned.
Actually sometimes you modders act like it.
I'll get the other times later. Here is the startup time.
Droofus said:
FYI, part of this is related to my background as a doctor (plus a computer background dating back beyond the Apple II to programming FORTRAN and COMPASS on mainframes in the 1960s). As doctors we are constantly bombarded with all sorts of anecdotal raves about this or that treatment all the time, only to find that they aren't supported by actual objective research -- some cause harm, not healing. Fortunately for those promoting software changes related to raves and fads don't have the potential to cause anyone significant harm... Excuse me if I'd like to see similar objective professional 'standards of care' when it comes to reviewing and analyzing software/hardware fads. I'm sure there are plenty of others in the audience who'd feel the same...
Click to expand...
Click to collapse
Well, while I can see your point, I also have to point out the other side of the argument. I am an engineer. Last year, we got a college graduate who, from the outlook, had all the numbers and credentials. He graduated with almost a perfect gpa. Sounds nice, right? He had all the numbers. The problem was as soon as he began working with us we figured out very quickly that we had a book smart-absolutely no common sense person with us. I swear, he pulled me aside one time and asked me why they were "watering the concrete slabs" in the lab. It got worse from there. I had to explain to him very basic engineering concepts and applications like stirrups, slippage, etc.
This guy actually went through college getting the grades and everything without actually understanding any of it. He graduated with a structural engineering degree without knowing the very simple practical processes of curing concrete or reinforcing footings.
The point is numbers can be deceiving if you ignore annecdotal (aka common sense) evidence. You need both objective numbers and common sense to work in reality. Sure, I've heard plenty of annecdotal nonsense like creationist BS, religious miracles, and homeopathic crap. I'll give you that. But you seem to be on the other extreme side, which is to ignore all personal evidence and place all your bets on pure numbers.
I'm telling you now. We got both the numbers and personal evidence. I'll try to get them for you.
Doofus
I like the list of missing benchmarks you listed. Why don't you measure them and report back?
Droofus said:
What I'm looking for is defined, at least in part, in the first post. Copy and pasted here for your convenience.
Stuff like, time to boot? Time to load common apps? Time to open the same web page? Frames on games? Time to download? Max browser pages open? Other relevant numbers welcome...
Click to expand...
Click to collapse
All those numbers are identical before and after rooting your device since nothing changes before and after root, other than you now have root access.
That was easy.
1
2
3
4
5
6
7
8
9
10
Theres some more random numbers
While watching everyone bash eachother here has its entertainment i have some advice.
Droofus
1 i would recomend not comming into a community forum and bashing people who put a lot of effort into making the product you own better. These people don't get paid for the hours of work they put in.
2 if you don't like how thing are done around here take the time to be a good example and do it better. You clearly have an idea in your head on how to make a professional stastical representation of the roms so do it.
3 what some people are trying to tell you is that it is not all about the numbers. Some people want gingerbread features. Right now all of the gingerbread roms suck for video performance due to driver issues so i don't use them. I like the gingerbread features but i watch videos a lot so i use a froyo rom. Others really care about performance so they give up some stability and overlock.
4 people around here get upset when the same question gets asked over and over again. If you have done some reasearch reference other articles to show that.
5 this is a dual core tablet, what are you doing that you care that much about preformance.
This thing is faster than my netbook.
6 dropping your title on us just makes you sound pretentious. There are a lot of very intellgent successful people here who are not impressed by doctors or your past experience. If you have useful skills to the community don't brag just use them and people will be grateful.
7 people were a little rude about it but they are right. I tell people that if they want something that is easy go buy an ipad or a xoom. If you want something for under 300 then buy a g tab and understand that with some effort it can be great.
Everyone
1 relax... starting flame wars with someone who doesn't know their way around isn't going to help anyone.
I forgot to mention that traditionally us geeks are known for our lack of formal documentation.
P.s. while many of us proudly wear the badge of geek calling us a pack of geeks is a little adversarial.
Hey all,
I've been a lurker for a while, been looking for a way to encourage the now Google-owned Motorola Mobility to unlock their bootloaders much like HTC has wisely done, but it's becoming more and more obvious to me that they don't care about the "minority" of us that actually feels as though we are entitled to full admin rights on our phones that we either paid a ton of cash for, or signed a lengthy contract to obtain. Verizon is the one blocking it? HTC found a way, and so can Motorola Mobility...that is cop-out.
My proposal is that there be an effort to unlocked the bootloader, I am not some expert programmer, and I am open to whatever will help the cause. I know there was a bounty on it, but to me this isn't about money, I'll donate time, money, information ripped from my phone if it, in some way, contributes to unlocked that bootloader. Even if you need my unused CPU cycles to calculate things, I don't care, just tell me what I can to do help, because I am sick of not being able to use my phone to it's fully potential.
Maybe I am being naive, but I believe if we all worked together we could accomplish this goal. If you agree, please, let's organize and figure this out!
-Joshua
I love optimism
I'm down with the movement...
This phone does have mad potential to be so limited compared to other phones.
I just can't believe that we are running an unofficial, incomplete version of CM7 and it runs smoother than stock Blur.
Is that telling you something about Motorola?
Do you guys think Google will make that decision for Motorola or will Moto stay the same?
Sent from my Android
Worth a try...
Re: Google changing Moto policy
I don't know so much about Google changing Motorola's stance on the locked bootloader, we've tried petitioning the company themselves, but have we tried petitioning Google? Or maybe it's too soon, maybe they are working on it right now? Hard to tell, and I don't want to put pressure on Google too soon especially if they are trying diligently right now to do the right thing.
But the above poster is right, cracking it ourselves is definitely worth a try. I have contacts (unfortunately know inside Motorola), I know people with lots of knowledge on encryption, I'll be honest one of my friends does have a knack for the impossible, but this would be too much for one lone person. I also have a few computers in the house, to donate computing power. None above 5 GB of RAM unfortunately, but my friend with all of that know-how does also have a synchronous 20/mbit up/down connection to the net, if that helps, and I have another friend that is the linux admin at a an unnamed private university in Durham that might could lend a hand in some way.
We have the resources, we just need to pool them.
Someone with the realistic technical know-how, just tell us where to begin, and the shortest path to getting to our goal and we'll do all we can to contribute!
Thanks for understanding and not just writing this off as a pipe-dream...because I know if we work together we can accomplish almost anything.
-Joshua
spyda256 said:
I don't know so much about Google changing Motorola's stance on the locked bootloader, we've tried petitioning the company themselves, but have we tried petitioning Google? Or maybe it's too soon, maybe they are working on it right now? Hard to tell, and I don't want to put pressure on Google too soon especially if they are trying diligently right now to do the right thing.
But the above poster is right, cracking it ourselves is definitely worth a try. I have contacts (unfortunately know inside Motorola), I know people with lots of knowledge on encryption, I'll be honest one of my friends does have a knack for the impossible, but this would be too much for one lone person. I also have a few computers in the house, to donate computing power. None above 5 GB of RAM unfortunately, but my friend with all of that know-how does also have a synchronous 20/mbit up/down connection to the net, if that helps, and I have another friend that is the linux admin at a an unnamed private university in Durham that might could lend a hand in some way.
We have the resources, we just need to pool them.
Someone with the realistic technical know-how, just tell us where to begin, and the shortest path to getting to our goal and we'll do all we can to contribute!
Thanks for understanding and not just writing this off as a pipe-dream...because I know if we work together we can accomplish almost anything.
-Joshua
Click to expand...
Click to collapse
i love your optimism i have some old pms that may help with the effort
SHA-1 brute force can be cracked for around $2 of Amazon cloud computing service.
http://www.geek.com/articles/news/r...for-2-10-with-amazons-cloud-service-20101122/
Isn't boot loader use SHA-1 encryption?
(of course, the key may be much longer, but it may not be impossible for cheap. I say try to pool together like $100 and try Amazon cloud computing a try?)
Re: Amazon
hpark21:
I like the way you're thinking, does anyone else think this might be a good call? I know there was a bounty of around ~$800 somewhere, so I doubt if all of us who rightfully were promised and unlocked bootloader wouldn't mind pooling a bit of money for the computing power, hell I myself would give $50 to the effort if we knew it was a viable solution.
Other thoughts?
Also, ztotherad, if you could send me those PMs maybe we can sift through those and see if there are some other avenues, nothing is off the table at this point.
thanks again for coming together on this, that is the true meaning of community.
spyda256 said:
hpark21:
I like the way you're thinking, does anyone else think this might be a good call? I know there was a bounty of around ~$800 somewhere, so I doubt if all of us who rightfully were promised and unlocked bootloader wouldn't mind pooling a bit of money for the computing power, hell I myself would give $50 to the effort if we knew it was a viable solution.
Other thoughts?
Also, ztotherad, if you could send me those PMs maybe we can sift through those and see if there are some other avenues, nothing is off the table at this point.
thanks again for coming together on this, that is the true meaning of community.
Click to expand...
Click to collapse
i can def send you them, idk how much help theyll be
Uh, I think it's already been established that brute forcing it is impossible.
Stuckinabox said:
Uh, I think it's already been established that brute forcing it is impossible.
Click to expand...
Click to collapse
In one of the many threads concerning bootloader unlocks, I believe the chances of us finding it were determined to be 1mill:1. It would take us over a decade to manually come up with the key. I don't want to kill confidence, but I'd like to keep things relatively rational.
Sent from my MB870 using xda premium
Stuckinabox said:
Uh, I think it's already been established that brute forcing it is impossible.
Click to expand...
Click to collapse
it's been established that brute forcing is nearly impossible, not completely impossible
it is something that would take an insane amount of resources to accomplish , and/or time ,
it would really come down to "how lucky are we?" really, as in::: how lucky are we that we stumble across or know a genius that can crack it, stumble across needed files, etc...
good luck to all who try, I wish I could do anything to get us there, but I don't know the first thing when it comes to this stuff, don't give up the dream!
Basically, what it comes down to is:
Find out what their hash key is. (encrypted password)
Then, try to go through all valid characters and see whether the input matches the output hash.
If one is lucky and they used short enough password, then it will be quick to find.
If unlucky and they used really long password, then the answer is that we won't be able to find it in REASONABLE time. (I would say 1-2 months to be reasonable - at $2/hr, it would cost $48/ day).
Only issue is when do we stop?
hpark21 said:
Basically, what it comes down to is:
Find out what their hash key is. (encrypted password)
Then, try to go through all valid characters and see whether the input matches the output hash.
If one is lucky and they used short enough password, then it will be quick to find.
If unlucky and they used really long password, then the answer is that we won't be able to find it in REASONABLE time. (I would say 1-2 months to be reasonable - at $2/hr, it would cost $48/ day).
Only issue is when do we stop?
Click to expand...
Click to collapse
There was some kind of crazy algorithm applied to each character to generate the correct item for each number of the key, correct? We would have to come up with that too?
Sent from my MB870 using xda premium
THANK YOU! Finally ... a revived movement. I pledged $100 on another thread and I'm good for putting it toward an unlocked bootloader again!
To learn from one of the most influential groups of our generation ... anonymous utilizes botnets to pool computing resources ... if we get a tool that could function similarly, could we not pool 1000s of computers together to crack it faster? It would make what is not feasible for a small set of computers to do... feasible. If all most users have to do is download a tool that gives us access to processing power and bandwidth ... users will download the hell out of it.
Count me in.
[ sent from _base2 ]
Hope
I understand doubters, and odds are likely against us, but that's ok, no one person can do it, and maybe not just one method, but somehow we WILL get to our goal. Whether Motorola capitulates or we find a method to crack it, we will not have this awesome hardware go to waste.
I am not generally a "black hat" kind of person, but in this case we are in the right so far as I am concerned (please don't quote DMCA BS to me, lol) because they made a promise to their customers, and it will be kept, whether they like it or not.
So, I am with the above poster that mention he didn't know quite where to start, or where we have already made progress, but if someone can help us out, explain the process, we figure out how to move forward. (Please forgive the run-on sentence).
I've minimal experience programming, only VB.net, C++, and a bit of Java from college, and I do tier 2 desktop support for a bank these days, but on my off time I'd love to spend it on something worthwhile, all of you deserve this, and we'll make it happen.
Maybe it's the troubleshooter in me that sees the problem and says "oh no, there's a way, we just need to find it". I have a colleague, the one I spoke of before, he has a knack for doing incredible things, so once we have a breakdown of what we need to do, perhaps he can be of help.
So my friends, where do we go from here?
spyda256 said:
I understand doubters, and odds are likely against us, but that's ok, no one person can do it, and maybe not just one method, but somehow we WILL get to our goal. Whether Motorola capitulates or we find a method to crack it, we will not have this awesome hardware go to waste.
I am not generally a "black hat" kind of person, but in this case we are in the right so far as I am concerned (please don't quote DMCA BS to me, lol) because they made a promise to their customers, and it will be kept, whether they like it or not.
So, I am with the above poster that mention he didn't know quite where to start, or where we have already made progress, but if someone can help us out, explain the process, we figure out how to move forward. (Please forgive the run-on sentence).
I've minimal experience programming, only VB.net, C++, and a bit of Java from college, and I do tier 2 desktop support for a bank these days, but on my off time I'd love to spend it on something worthwhile, all of you deserve this, and we'll make it happen.
Maybe it's the troubleshooter in me that sees the problem and says "oh no, there's a way, we just need to find it". I have a colleague, the one I spoke of before, he has a knack for doing incredible things, so once we have a breakdown of what we need to do, perhaps he can be of help.
So my friends, where do we go from here?
Click to expand...
Click to collapse
sir, did you get my pms?
Re: PMs
Nope, just saw them, thanks for that!
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Eckyx said:
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Simple answer is no not all devices are made the same. You see this with mass produced hardware. As for your PC ref. My brother and I have the same laptop while mine loves my set up, my brother has nothing but problems with it on his system. It comes alot down to personal set up and device. This has always been the case with mobile devices and custom roms. Stock roms are set to run on all devices the same. This is not so with custom roms.
Eckyx said:
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Zel pretty neatly answered this, but I will also add that modern consumer electronics interact with the immediate environment far more than our pcs do. Light sensors, 3g radios, barometers, etc. are far less deterministic than our classic closed-loop pcs. Part of this perception of flux is based on this real flux, for example one of the core features people will discuss is call/modem quality, but driver tweaking vs. actual signal strength is a pretty fuzzy battle for anyone but an electrical/firmware engineer. And just like in the pc world, when you're talking under volting and over clocking your mileage will vary.
If you are methodical and read all the materials, your phone will operate tip top. It seems to me a lot (not all) of the variances often do boil down to the users configuration.
Sent from my iPad using Forum Runner
I have fixed a lot of computers and have been flashing custom roms for a year and ill tell you, in my personal opinion, problems are 90% user error. If people would all install properly and wipe everything completely and follow everything they're told to do and read all possible material on what they're flashing they can, a huge portion of the problems would dissapear. But is that gonna happen? I hope so
Heck I make mistakes too. None of us are immune to screwing up right? Good luck all, happy flashing.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Eckyx said:
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Yes, they should and they do, absolutely with every ROM, stock or custom.
If they're purely, properly installed, they're all the same.
By "purely", I meant completely, virgin-like ROM without any add-on.
If you choose to install somethings else, to customize your needs or set it up the way you want, then it's a whole different ball game.
zelendel said:
Simple answer is no not all devices are made the same. You see this with mass produced hardware. As for your PC ref. My brother and I have the same laptop while mine loves my set up, my brother has nothing but problems with it on his system. It comes alot down to personal set up and device. This has always been the case with mobile devices and custom roms. Stock roms are set to run on all devices the same. This is not so with custom roms.
Click to expand...
Click to collapse
Just to chime in on the Windows thing - we buy a standard build HP computer at work for all developers. But if you put the same Windows disk in two of them and boot and install accepting all the defaults, there will always be slight variations in the way it configures itself between the two. It's probably the hardware detection that does it, but I swear you could get two of the same build lot and you'd STILL get something that didn't set up the same way. Sunspots? Power surge during the process? I dunno, but it does vary
You cant change the disk. Your network adapter has a MAC adress on it... windows will know something has changed. motherboard also has one.
A PC component are not the same at all.
You can buy a good I7 2600k or a bad I7 2600k. There are revisions of the very same model of CPU, memory, everything and its really hard to make 1 equal another.
Another thing is that one smartphone is a lot more delicate piece of hardware and the most important, has limited power to it components.
That makes harder to change anything on it. A small change could lead you to a failure.
just blame it on the ghosts in the machine and be done with it
votinh said:
Yes, they should and they do, absolutely with every ROM, stock or custom.
If they're purely, properly installed, they're all the same.
By "purely", I meant completely, virgin-like ROM without any add-on.
If you choose to install somethings else, to customize your needs or set it up the way you want, then it's a whole different ball game.
Click to expand...
Click to collapse
This is not the case. I have tested with two different EVO 4Gs and two different SGS IIs - of the same hardware revision, even.
I performed the same steps to root and ROM both of the sets of phones, and put the same ROM on them. There were no other apps installed, nor themes/addons. I then used each as my phone for a week, making sure that I installed identical apps and even synced app data.
Both performed differently. My i777 is the faster of the two, but my EVO 4G was the slower and more bug-prone.
Yes, this is anecdotal evidence, but I at least am convinced. Take it as you will.
Also the phones are made with lower quality checks than desktop. ie I can oc my sgs 1 up to 1.6GHz but uv of -25, the phone well restart. But other people can't go more than 1.2 and cab apply a uv of -150 on the same step.
This is a fact. Think if every phone it's done with high quality checks the price of the device will raise pretty high.
Once of the frustrating things is that the people responding on the forums, (ROM devs and regular users) often try to have it both ways.
If you're experiencing something they aren't, it's obviously your fault because it doesn't happen on their one phone so it can't possibly be anything but your own fault. Go wipe 50 times and do other things that will take 3+ hours each time and don't come back until you do.
Oh... you've done all that already and still having the issue? Oh well, all phones are different... tough luck, bro. I'm not going to spend any time on anything my one phone doesn't do.
(Never mind that a dozen other people have reported the exact same issue, and another several dozen are experiencing it but are too scared to post about it because they see how everyone else is being flamed, castrated or even banned for daring to suggest a bug.)
One way or another, it seems a convenient way to blow off users having legit issues.
While I suppose there might be slight deviations in components once in a blue moon, I think the "all phones are different" excuse is more often than not used as a way to easily dismiss people and issues without helping. It's been repeated over and over for so long now, the majority take it as "fact" without really putting much thought into how it could possibly be as widespread and dramatic as they're pretending it is.
I don't buy it.
Even just with modems... everyone's like, "Oh well all phones are different... some modems work better on some phones, or in different areas". What kind of BS is that? How on earth could any phone manufacturer then create a mass-market phone that worked across the country without hacking? I'm sorry, but you can't chastise and criticize the manufacturers for not producing the universal "uber-phone" that works great anywhere while at the same time admitting that "all phones are different" and therefore require hacking for your specific flavor or region. It's hypocritical.
I think it's very, very rare that actual hardware differences between the exact same model phone account for issues people experience, and is more often than not either user or dev (as much as they try to paint themselves as infallible gods) error that they don't want to bother with. "All phones are different" = "F-off, I don't want to deal with this"
sremick said:
Once of the frustrating things is that the people responding on the forums, (ROM devs and regular users) often try to have it both ways.
If you're experiencing something they aren't, it's obviously your fault because it doesn't happen on their one phone so it can't possibly be anything but your own fault. Go wipe 50 times and do other things that will take 3+ hours each time and don't come back until you do.
Oh... you've done all that already and still having the issue? Oh well, all phones are different... tough luck, bro. I'm not going to spend any time on anything my one phone doesn't do.
(Never mind that a dozen other people have reported the exact same issue, and another several dozen are experiencing it but are too scared to post about it because they see how everyone else is being flamed, castrated or even banned for daring to suggest a bug.)
One way or another, it seems a convenient way to blow off users having legit issues.
While I suppose there might be slight deviations in components once in a blue moon, I think the "all phones are different" excuse is more often than not used as a way to easily dismiss people and issues without helping. It's been repeated over and over for so long now, the majority take it as "fact" without really putting much thought into how it could possibly be as widespread and dramatic as they're pretending it is.
I don't buy it.
Even just with modems... everyone's like, "Oh well all phones are different... some modems work better on some phones, or in different areas". What kind of BS is that? How on earth could any phone manufacturer then create a mass-market phone that worked across the country without hacking? I'm sorry, but you can't chastise and criticize the manufacturers for not producing the universal "uber-phone" that works great anywhere while at the same time admitting that "all phones are different" and therefore require hacking for your specific flavor or region. It's hypocritical.
I think it's very, very rare that actual hardware differences between the exact same model phone account for issues people experience, and is more often than not either user or dev (as much as they try to paint themselves as infallible gods) error that they don't want to bother with. "All phones are different" = "F-off, I don't want to deal with this"
Click to expand...
Click to collapse
Great so what you're saying is everyone that says this (especially devs) are a bunch of dicks. Nice.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
Great so what you're saying is everyone that says this (especially devs) are a bunch of dicks. Nice.
Click to expand...
Click to collapse
That's actually not what I said at all, but I know it's a lot easier to summarize my post into one sentence that makes me look like an ass, than actually look at the points that I made.
sremick said:
That's actually not what I said at all, but I know it's a lot easier to summarize my post into one sentence that makes me look like an ass, than actually look at the points that I made.
Click to expand...
Click to collapse
I read the whole thing and that's exactly what it says.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
I read the whole thing and that's exactly what it says.
Click to expand...
Click to collapse
Nope. But let me simplify it for you:
1) There can't be the level of hardware variation that people claim. It's not seen in other electronics, and it's not been seen before the recent generation of smartphones. The assumption of its existence is a recent phenomenon however if it were real we'd see it everywhere, on other electronics other than phones.
2) If it were to really exist, people would lose the ability to legitimately blame the phone manufacturers for 90% of what they currently give them crap about, especially in regards to making a quality stock ROM. What are they expected to do, create thousands of variations of stock ROMs, one for ever county in the USA to compensate for this accepted "all phones are different" theology?
3) Due to it being repeated over and over and simply assumed to be true without any actual evidence to the fact, it's become a convenient way to dismiss user issues... even in the face of mounting evidence to the contrary on a specific issue. This unfortunate trend causes lots of friction between users and devs. Even if it were true, it's now become an over-used dismissal without allowing for the chance that the user might be right.
People can't have it both ways, but right now there's a lot of hypocrisy. If it's true, there's been no evidence actually shown... just anecdotal experiences that could be chalked up to any number of other things. And whether it's true or its not, either way a massive amount of thinking and behavior would then have to then change... but right now, people behave like it's true and not true at the same time, which is nonsensical and frustrating.
The simple answer is, there is no answer. Its the nature of the process.
I've had one click roms fail the 1st attempt only to succeed the 2nd without even closing the Odin just reconnect the phone.
Either you accept that and have fun with it. Or stick to stock and move on.
Sent from my SGH-I777 using xda premium
sremick said:
Nope. But let me simplify it for you:
1) There can't be the level of hardware variation that people claim. It's not seen in other electronics, and it's not been seen before the recent generation of smartphones. The assumption of its existence is a recent phenomenon however if it were real we'd see it everywhere, on other electronics other than phones.
2) If it were to really exist, people would lose the ability to legitimately blame the phone manufacturers for 90% of what they currently give them crap about, especially in regards to making a quality stock ROM. What are they expected to do, create thousands of variations of stock ROMs, one for ever county in the USA to compensate for this accepted "all phones are different" theology?
3) Due to it being repeated over and over and simply assumed to be true without any actual evidence to the fact, it's become a convenient way to dismiss user issues... even in the face of mounting evidence to the contrary on a specific issue. This unfortunate trend causes lots of friction between users and devs. Even if it were true, it's now become an over-used dismissal without allowing for the chance that the user might be right.
People can't have it both ways, but right now there's a lot of hypocrisy. If it's true, there's been no evidence actually shown... just anecdotal experiences that could be chalked up to any number of other things. And whether it's true or its not, either way a massive amount of thinking and behavior would then have to then change... but right now, people behave like it's true and not true at the same time, which is nonsensical and frustrating.
Click to expand...
Click to collapse
No you're actually wrong because sometimes things CAN go wrong with flashing stuff. And modems in fact do work better in some places than others even though they try to make them universal it is very difficult to do that. Also, if a dev doesn't see a problem, how is he supposed to fix it? Riddle me that one. Also, restoring should take at most an hour with something like titanium backup. So 3+ hours is bull.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
if a dev doesn't see a problem, how is he supposed to fix it?
Click to expand...
Click to collapse
He can start by not flaming the several people experiencing it (which scares away others also experiencing it, self-validating him and making him think the problem is less-common than it really is)
There's a difference between a problem being simply difficult for a dev to pin down and solve, and just attacking any user who dares bring up an issue that the dev himself isn't experiencing. Therein lies the hypocrisy, though: if "all phones are different", then a dev has to accept that a problem a user is experiencing might not be the result of stupidity on the user's part, and might actually be something in the ROM that simply didn't surface on the dev's phone, but is still something that needs to be addressed at the ROM level.
I totally accept that an issue the dev can't reproduce on his own phone is harder to resolve. But there are several devs who even make ROMs for phones they don't own anymore, and still manage to work with users to resolve issues. App devs do the same thing to resolve incompatibility bugs/issues with specific phone models the app dev don't own.
Also, restoring should take at most an hour with something like titanium backup. So 3+ hours is bull.
Click to expand...
Click to collapse
Not quite. Just the backup alone takes 45+ mins on my phone. The restore is the same amount, so you've got 1.5 hours right there without taking into account everything else that TB doesn't handle that needs to be reconfigured by hand, or the actual flashing, and tracking down other surprises. And because I apparently am one of the few people who care about their data, I also back up my internal SD... just in-case something goes wrong. I know the wipe shouldn't touch it... but "**** happens" and if something goes wrong during a flash and I didn't have a backup, it'd be my own fault and I'd be subsequently flamed for that. So I play it safe.
Once again, a case of users for whom its quick trying to tell everyone else they're full of BS. I accept that for some users, whether it's the # of apps, amount of data, or whatever, it goes fast for them. Lucky them. Why can't they accept the fact that it's not "10 mins" for everyone like they spread around and flame others for suggesting otherwise?
Ok Here is the thing. I have personally been flashing and making custom roms for phones as far back as the Motorola razor v3. I have multiple phone running the exact same firmware, set up the exact same way and the have run totally differently. If all phone were made equal then there would be no returns due to issues the phone had as they would have all run the same and acted the same as the units that the OEM quality control tested. Lets take the Black Jack 2 as an example. The BJII was a WM phone that would self corrupt the system/media folder. This prevented any ringtones from working and the OS had to be reflashed. All this running on Stock firmware. This didnt happen to all of them, but became a well known glitch to anyone that did cell phone troubleshooting and repair. Did you ever stop to think why OEM and carriers dont use the roms from places like XDA? This is because things here are always under development. There will always be bugs. In the end the developers are making things for their phones and are nice enough to share it for others to use. Some do keep making roms for phones they dont have as this is overly not hard to do. They do this just to be nice. Except for the hardware drivers most of the under lying OS is all the same.
If a dev cant reproduce it then there is no way for them to fix it with the way people tend to report bugs. (The wrong way without the proper info)
Now lets jump to the present. I have 4 phones sitting on my desk. 2 are the HTC Inspire and 2 are the Samsung Captivate. Both running the exact same rom and apps, but guess what. They run very differently. On 1 Inspire and 1 captivate, I can OC to almost double, while the other 2 cant handle more then 1.2 over clock.
One of them also doesnt like the AOSP based software while the others are fine.
As for your backing up and restoring. It can take a long time if you have a TON of apps. Flashing custom roms are not for everyone. If you dont have the time or the want to learn something then you are doing it for the wrong reasons.
sremick said:
He can start by not flaming the several people experiencing it (which scares away others also experiencing it, self-validating him and making him think the problem is less-common than it really is)
There's a difference between a problem being simply difficult for a dev to pin down and solve, and just attacking any user who dares bring up an issue that the dev himself isn't experiencing. Therein lies the hypocrisy, though: if "all phones are different", then a dev has to accept that a problem a user is experiencing might not be the result of stupidity on the user's part, and might actually be something in the ROM that simply didn't surface on the dev's phone, but is still something that needs to be addressed at the ROM level.
I totally accept that an issue the dev can't reproduce on his own phone is harder to resolve. But there are several devs who even make ROMs for phones they don't own anymore, and still manage to work with users to resolve issues. App devs do the same thing to resolve incompatibility bugs/issues with specific phone models the app dev don't own.
Not quite. Just the backup alone takes 45+ mins on my phone. The restore is the same amount, so you've got 1.5 hours right there without taking into account everything else that TB doesn't handle that needs to be reconfigured by hand, or the actual flashing, and tracking down other surprises. And because I apparently am one of the few people who care about their data, I also back up my internal SD... just in-case something goes wrong. I know the wipe shouldn't touch it... but "**** happens" and if something goes wrong during a flash and I didn't have a backup, it'd be my own fault and I'd be subsequently flamed for that. So I play it safe.
Once again, a case of users for whom its quick trying to tell everyone else they're full of BS. I accept that for some users, whether it's the # of apps, amount of data, or whatever, it goes fast for them. Lucky them. Why can't they accept the fact that it's not "10 mins" for everyone like they spread around and flame others for suggesting otherwise?
Click to expand...
Click to collapse
I agree with your point about the dev/user relationship. It can get pretty hostile sometimes which is completely unnecessary. Recently, I've been trying to emphasize the respect rule, regardless of who you are. Patience and cooperation can go a long way. And as zelendel said, sometimes people do report stuff the wrong way, but there's no need to be rude about it. Again, patience goes a long way.
Back to the main thing though, I'm not entirely sure how 2 fresh-out-of-the-box phones would work with the same settings and ROMs, but as others said, environmental and external factors can stress the phone and stuff just goes wrong. My phone, for example, would not operate the same as a fresh-out-of-the-box SGS2, even if you put the exact same stuff on it. Stuff just starts freaking out, and I'm pretty sure my phone is having hardware issues :[
Hello, I am currently a privacy novice trying to learn about different avenues of where I can get help to better protect myself. I see apple devices and I like the fact that they have a closed ecosystem per device, but I don’t like the fact that they are all interconnected with each other; it freaks me out that someone else with an Apple device could very easily connect to mine. That’s why CalyxOS stood out to me, because what it looks like from the outside-in is a decentralized form of android device, without all of the Google strings attached. I’d honestly rather use it than Graphene, because the people over on the graphene forums are kinda toxic to be honest. I have no knowledge of how to install operating systems, however, and I’m afraid that I could easily screw it up. Does Calyx sell any Pixel 6/Pixel 6 Pro models that I could buy to get started?
Welcome. I'm probably a terrible example but oh well. I had time to kill and been stuck on this topic myself since the early 90s.
If you're serious about privacy to the point that you are worried about other devices as you mentioned, I highly suggest (seriously, not trying to be a ****) you take some online courses on the fundamentals of telecommunications, and do some "light" reading on topics likeLinux Kernel, enterprise networking, Signals Intelligence, and Section 215 metadata collection. thats a decent starting point to the state of things. Though it's just a shinny coin on a string to distract while the real work continues. It must always continue. It will never stop.
I'm sorry to tell you.
It's too late. In any practical sense short of finding somewhere to go love in a cave until you starve or die from a infection a 99¢ tube of cream could have prevented.
You can have a privacy focused phone. It can keep certain things safe. Stop some people from doing things. Delay an outcome. You're gonna need to learn about installing an OS though. It gets pretty complex rather quickly.
Nothing is safe. Every lock can be picked or bypassed. There is no such thing as a door only you can use. The last place anything is truly a secret is in your head. When you are the only person in the entire world with the right permissions.
There was a window when we could have made meaningful and lasting choices in how protocols, standards, regulations, and laws were adopted. Back when it was all just a few hundred trunk lines, IXPs and NOC with good intentions, and tragically short sight. Lots of people screaming at the top of their lungs about the potential outcomes. Tinfoil hats were worn. Turns out we were right.
When you wrap your brain around what the "internet" really is...it's similar to getting a small sliver of understanding; grasping ever so lightly; the brain breaking inconceivable scale of the infinite universe and how infinitesimally small we are. The remnants of a dead stars clumped together pondering its own own existence. Connecting wires together and making things beyond our capabilities. The amount of data being exchanged right now ain't ****. It's bonkers, but it won't be next year, or next or the next.
The rate at which machine learning and the race to general AI is going, watch for the casualties along the way. one example is encryption as we know it. Gone. It'll be rendered trivial by 2040 MAYBE. Honestly that's a really high estimate. Likely before.
Post quantum encryption is just about as experimentally verifiable as string theory. Won't be long though before we get a chance to see if itll hold up. The Xbox is older than the time we have left. The Patriot Act as well.
Practice basic OPsec. Best Practices. Trust few, tell fewer. Read. Read some more. Then read the book. Every question you could ever think of likely has a 12 year old thread at a slackexchange site and no shortage of users ready to remind you how tired they are of duplicates. The community at grapheneOS is similar. On that though. Best to just go to the source. He tries to explain things without just speaking in jargon. Daniel Micay himself on the matter of android security.
https://www.reddit.com/r/GrapheneOS/comments/bddq5u
and
https://www.reddit.com/r/GrapheneOS/comments/du23la
There is no shortage of people currently who disagree with him even though they have little to no grasp on the complexity of what it is he actually intended. Ran into one of them myself, on this site, just the other day. Sure, It's hardneded, but what that means from user to user is drastically different.
It's more than some. It'll fit some use cases. But it's just a speck in a cloud. If you attract the attention of a human being with skills and motivation...good luck my dude. Godspeed.
The real thought experiment and one of my favorites to fall asleep to on nights I actually sleep is "what are they going to do with all the encrypted data they hoovered up and have been storing for the last 30-40 years? Once AI turns the encryption algorithms that humanity runs on into a half finished cheap dollar store sudoku." How long does any one reckon that'll be the case before us plebs hear about it. We got a good track record, as a collective species in doing the right thing, right? No way they will actually use what is functionally a rewind button on...well everything. Nah, it'll be fine.
Oh look, Lapsus$ group woke up, posted a new dump... Wonder how much Globant spend on securing their stuff. Probably more than me.
--just a jaded old man