Im busted LOL ..nah I just dont come on here alot but found interest again since theres a lot more people then there used to be.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
pod2g update via his blog
- Thread starter rick snagwell
- Start date
- Sort by reaction score
Im busted LOL ..nah I just dont come on here alot but found interest again since theres a lot more people then there used to be.
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)
The hacks section has been really pumping here lately. Since we have been waiting on the A5 JB.
This really isnt great news for the future of jailbreaking. Reading @planetbeing's post was a great read, a promising Read, all while being a depressing read.
I think in future versions of iOS apple should allow developers to have a little lee-way in apps so that we might be able to customize the OS a little bit. I'm not asking for much, just a little. Moving on, let's all get a semi over this JB!!!
The hacks section has been really pumping here lately. Since we have been waiting on the A5 JB.
This really isnt great news for the future of jailbreaking. Reading @planetbeing's post was a great read, a promising Read, all while being a depressing read.
I think in future versions of iOS apple should allow developers to have a little lee-way in apps so that we might be able to customize the OS a little bit. I'm not asking for much, just a little. Moving on, let's all get a semi over this JB!!!
Very nice read posted by planetbeing:
Why we can never give ETAs for jailbreaks. (self.jailbreak)
submitted 3 hours ago by planetbeing
The problem with giving any definite ETAs is that there can always be problems that crop up that blindside us that will take an unknown amount of time to solve (if they are even solvable). Let me give you a little timeline about this sandbox issue, for example (though I have to avoid giving currently classified technical details).
Generally, constructing jailbreaks takes a lot of time researching issues: how, conceptually, are we going to break Apple's protections and mitigations against it. Then, to figure out what precise techniques will we use to implement our ideas. Those take an unknown amount time and may actually be impossible. It is theoretically possible for Apple, if they don't make any mistakes, to create a system that prevents jailbreaking. Then, after those are figured out, time can be spent coding the jailbreak, which takes a more predictable amount of engineering time. Unfortunately, sometimes while coding, you happen to discover the method you thought would theoretically work, even a method you tested before, might have unforeseen difficulties because you made some incorrect assumptions.
When we're at the research stage, we can't give an ETA because we don't even know if it's going to be possible. When we're at the engineering stage, we can't give an ETA because heaven forbid we find that we've made a mistaken assumption and need to go back to the research stage.
I started to actively participate on January 6th, and I thought I could contribute by helping to figure out the sandbox issues since that's the one thing that needed to be researched at that point. The following five days has been one of the more irritating weeks of my life. On day 1, pod2g and I both independently came up with a way to circumvent the sandbox that would've been nice and simple. Unfortunately, later that day we discovered we misread the sandbox profile and it would not be possible. The next day was spent trying to see if any clever variation of the first idea could get around the sandbox: no. Then we were messing around and found a small vulnerability in the sandbox, a one millimeter hole in a huge wall if you will, and it seemed like it could be weaponized to get around the sandbox so we can break out. Eventually, I came up with the plan that formed the basis of what we have right now, but it needed three different pieces to make work. I managed to furnish the first piece myself pretty quickly, but the other two were not forthcoming. The next few days were filled with brilliant ideas by brilliant people that would work if only such-and-such were true. Every day, it was two steps forward and one step back. Then pod2g made a suggestion on how the second piece could be obtained and saurik managed to find it fairly quickly going off his suggestion. The day before, we thought we had finally gotten it: The idea had gotten past basic testing, so we made a few tweets on progress. Then later we found out, crushingly, that there was a weird behavior that prevented our method from working in practice. The next day was us scrambling to figure out a variation of the idea that would work, which required finding other candidates for the idea's prerequisites. saurik managed to figure some stuff out that gave us a little more invaluable wiggle room in finding the prerequisites and I managed to find something that would work. I created a proof of concept and it worked!
The result is basically building a program that aims a tiny bullet to shoot out of the one millimeter hole in our sandbox, having it bounce off of a few different surfaces (that we were lucky to find) to adjust our aim and have it go down the exhaust port of the Death Star, and instead of blowing it up, bounce off a few more surfaces inside the Death Star to get to the control room, and have the bullet bounce off buttons and levers to aim the Death Star at the sandbox wall to blow it up.
We don't think there's any more issues and we are starting to engineer it, but we don't really want to say we don't think there's any more issues because one or more might crop up. So basically, we've had really significant progress, but we can't give an ETA.
Amazing stuff!
Agreed. Jbing will be harder on the iOS devices going out from now on.
I may have to consider an Android device if no JB is introduced from now on.
Makes me sad.
Yup.
I know Apple probably hates jail breaking, but they hate Android too. I wonder which of the lesser two evils they'll choose!
I understand the sadness with the fact that planetbeing had to write that up, but it was a great read.
There will always be exploits. The question is, can they be found. As long as there are dedicated people to hack the code, we should be fine.
And Android isn't the problem. Google and the manufacturers are. Google can't get Android out of the beta phase and the manufacturers always have to screw up the ui and then not update the OS in a timely manner!
I wonder why Apple dislikes jailbreaking/customization so much. I already believe the iPhone is a better phone than Android phones as it is, but an iPhone jailbroken just blows the top off.
Needless to say, I am anxiously waiting to jailbreak my 4s.
Very nice read posted by planetbeing:
Why we can never give ETAs for jailbreaks. (self.jailbreak)
submitted 3 hours ago by planetbeing
The problem with giving any definite ETAs is that there can always be problems that crop up that blindside us that will take an unknown amount of time to solve (if they are even solvable). Let me give you a little timeline about this sandbox issue, for example (though I have to avoid giving currently classified technical details
Generally, constructing jailbreaks takes a lot of time researching issues: how, conceptually, are we going to break Apple's protections and mitigations against it. Then, to figure out what precise techniques will we use to implement our ideas. Those take an unknown amount time and may actually be impossible. It is theoretically possible for Apple, if they don't make any mistakes, to create a system that prevents jailbreaking. Then, after those are figured out, time can be spent coding the jailbreak, which takes a more predictable amount of engineering time. Unfortunately, sometimes while coding, you happen to discover the method you thought would theoretically work, even a method you tested before, might have unforeseen difficulties because you made some incorrect assumptions.
When we're at the research stage, we can't give an ETA because we don't even know if it's going to be possible. When we're at the engineering stage, we can't give an ETA because heaven forbid we find that we've made a mistaken assumption and need to go back to the research stage.
I started to actively participate on January 6th, and I thought I could contribute by helping to figure out the sandbox issues since that's the one thing that needed to be researched at that point. The following five days has been one of the more irritating weeks of my life. On day 1, pod2g and I both independently came up with a way to circumvent the sandbox that would've been nice and simple. Unfortunately, later that day we discovered we misread the sandbox profile and it would not be possible. The next day was spent trying to see if any clever variation of the first idea could get around the sandbox: no. Then we were messing around and found a small vulnerability in the sandbox, a one millimeter hole in a huge wall if you will, and it seemed like it could be weaponized to get around the sandbox so we can break out. Eventually, I came up with the plan that formed the basis of what we have right now, but it needed three different pieces to make work. I managed to furnish the first piece myself pretty quickly, but the other two were not forthcoming. The next few days were filled with brilliant ideas by brilliant people that would work if only such-and-such were true. Every day, it was two steps forward and one step back. Then pod2g made a suggestion on how the second piece could be obtained and saurik managed to find it fairly quickly going off his suggestion. The day before, we thought we had finally gotten it: The idea had gotten past basic testing, so we made a few tweets on progress. Then later we found out, crushingly, that there was a weird behavior that prevented our method from working in practice. The next day was us scrambling to figure out a variation of the idea that would work, which required finding other candidates for the idea's prerequisites. saurik managed to figure some stuff out that gave us a little more invaluable wiggle room in finding the prerequisites and I managed to find something that would work. I created a proof of concept and it worked!
The result is basically building a program that aims a tiny bullet to shoot out of the one millimeter hole in our sandbox, having it bounce off of a few different surfaces (that we were lucky to find) to adjust our aim and have it go down the exhaust port of the Death Star, and instead of blowing it up, bounce off a few more surfaces inside the Death Star to get to the control room, and have the bullet bounce off buttons and levers to aim the Death Star at the sandbox wall to blow it up.
We don't think there's any more issues and we are starting to engineer it, but we don't really want to say we don't think there's any more issues because one or more might crop up. So basically, we've had really significant progress, but we can't give an ETA.
I knew you had something to do with it.
I kind of of wish they would do what Microsoft did with Windows Phone 7 and the Chevron unlock. I true dream is that apple will allow you to pay a certain fair amount to allow "jailbreak" tweaks and customizations for devs. Just like windows phone 7 not every one is going to want to do it, just the ones that want to jailbreak!
Me too. I have grown to love Apple and the ease of use of its devices, but I also love having an "open" Apple device. ICloud and iTunes Match are a dream come true for me with all of my Apple devices, but I just may take the Android plunge in two years depending on the jb situation at the time. I like having phone freedom and maybe google and the manufacturers will get their act together by then.
Personally there is less and less of a reason for me to JB. As it stands I only want two JB apps, Lockinfo and BiteSMS.
I love bitesms.. its an amazing app just for the quick reply feature alone. TBH thats something Apple should have included in iOS.
I agree. That feature alone is worth the money. Its very convenient and a no brainier feature. Another good feature is when you get a MMS in the quickreply window, tapping on it front here brings it up to the forefront. then tapping swings it back. Very smooth and great feature. Its a small thing but great thing.
i like passwordpilot. very anoying to have to type my itunes pw every time i download or update apps in the appstore.
i also playawake where i can select any song in my ipod as alarm.
I hadn't heard of those. they sounds pretty useful though. MyWi was useful for awhile but since they started to crack down on tethering, I've decided keeping my unlimited plan is more important then streaming to my Air or iPad. I wouldnt last 2 weeks with the 2gb plan.
iScheduler was invaluable to me. Having the ability to activate any application on a timer was awesome (SiriusXM app in the morning as my alarm.) Also helped scheduling text messages that I didn't want to forget to send later on in the day.
yes, i think jailbreaking may or may not mean you have something useful for it, but at least having the potential is nice. after all, i bought my phone. shouldn't i get to control how i use it?
Two of my very favorites too! I thought playawake doesn't work with the new 5.0.1 jailbreak though?
FYI - my other "hall of fame" packages are icon renamer, mail more photos, open notifier, voicemail forwarder. All these should be standard functionality!
grouptones is also awesome, but sadly doesn't work on 5.0.1. either.
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)
What does it taste like? I'm getting rather hungry myself and would LOVE to have a little jailbroken apple pie today.... Seriously, the things that I like the most about JB are the simple ones mentioned, such as the quick reply window. This is something that when apple tool the idea from mobile notifier, they should have added without question. That, sbsettings, lockinfo, and maybe MyWi again. As far as the carriers cracking down I've never seen a problem on my wife's 4 that we still use for tethering today, I only upgraded it to ios 5 when the JB was available so we continuously used tethering for sometime now.
swiftbmx said:
What does it taste like? I'm getting rather hungry myself and would LOVE to have a little jailbroken apple pie today.... Seriously, the things that I like the most about JB are the simple ones mentioned, such as the quick reply window. This is something that when apple tool the idea from mobile notifier, they should have added without question. That, sbsettings, lockinfo, and maybe MyWi again. As far as the carriers cracking down I've never seen a problem on my wife's 4 that we still use for tethering today, I only upgraded it to ios 5 when the JB was available so we continuously used tethering for sometime now.
That's the amazing yet annoying part. "It's the little things". And we can't have them by default.
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)
When people threaten to switch from ios to android I laugh, because I've owned most every Verizon android since droid 1. I had the G1 the day it came out on T-Mo prepaid. Sure the new androids are nice with the big screens and even the new 720p screens. TBH the clarity on the GNex sometimes doesn't seem as sharp as the retina on my 4S. Sure I can tell on somethings but the difference is small. Sure some of the features Are things you think you will use. Such as NFC. While I'm sure the next iPhone will likely have it, it doesn't seem to be picking up any steam.
What we just talked about "the small things" is one reason I will always have an iOS device one way or another. Scrolling in the browser for example, I don't care what anyone says. If you think scrolling on android even compares, you are just trying to justify your purchase. Period. I've got a GNex(that will end up for sale likely), A bionic, and have used a Razr. They are all very nice and fairly smooth phones. But do simple things like scrolling in the browser or paging thru home screens. None of them compare to the smooth, not to fast/or slow(FWIW), fluid movement in navigating the UI the iPhone provides. These may not seem like big points but they are. My bionic for example(at least more often than GNex but this happens on both) sometimes when I press a app on the home screen it just kinda sits there for a few seconds. It's not opening the app and then trying to load- it just hangs. Once the app is open sure it's fast. They are great phones with tons of features but are lacking in areas that a basic user cares about the most.
The average user doesn't run benchmarks, nor care. It's not about actually being fast; but feeling fast. That's what you get, even with the iPhone 3Gs inferior hardware(by today's standards) feels much faster than many 1ghz androids, while it may not be. What's funny tho, even for those who want to compare benchmarks is this: the iPhone UNDERCLOCKED to 800mhz is faster than 98%(I don't have proof just google iPhone 4S bench and compare) of androids with have the RAM and sometimes even half the clock speed. I've compared it(4S) to the 1.5GHZ Rezound and it's like the difference between using a Droid 1 and GNex. It's partly got to do with the fact the Apple doesn't use crap SoC's like Qualcomm with crappy GPU's, but a lot to do with just having a well coded and well thought out OS.
I'm going to end rant bc I could go on, and on, and then on, but I didn't mean to offend anyone looking at androids but sometimes it seems like the grass is greener on the other side. It is in some aspects and isn't on others. I'm not posting this as a "iSheep" but as a person who has used almost every android in VZw lineup. When and if you make the transition you will miss things that work flawlessly(IMO) on iOS that can and do work(sometimes) great on android.
Lastly, even with the 4S hit or miss battery life, under heavy usage it blows every android out there. The iPhone IMHO is without question the best overall option out there for those looking at a smartphone.
When people threaten to switch from ios to android I laugh, because I've owned most every Verizon android since droid 1. I had the G1 the day it came out on T-Mo prepaid. Sure the new androids are nice with the big screens and even the new 720p screens. TBH the clarity on the GNex sometimes doesn't seem as sharp as the retina on my 4S. Sure I can tell on somethings but the difference is small. Sure some of the features Are things you think you will use. Such as NFC. While I'm sure the next iPhone will likely have it, it doesn't seem to be picking up any steam.
What we just talked about "the small things" is one reason I will always have an iOS device one way or another. Scrolling in the browser for example, I don't care what anyone says. If you think scrolling on android even compares, you are just trying to justify your purchase. Period. I've got a GNex(that will end up for sale likely), A bionic, and have used a Razr. They are all very nice and fairly smooth phones. But do simple things like scrolling in the browser or paging thru home screens. None of them compare to the smooth, not to fast/or slow(FWIW), fluid movement in navigating the UI the iPhone provides. These may not seem like big points but they are. My bionic for example(at least more often than GNex but this happens on both) sometimes when I press a app on the home screen it just kinda sits there for a few seconds. It's not opening the app and then trying to load- it just hangs. Once the app is open sure it's fast. They are great phones with tons of features but are lacking in areas that a basic user cares about the most.
The average user doesn't run benchmarks, nor care. It's not about actually being fast; but feeling fast. That's what you get, even with the iPhone 3Gs inferior hardware(by today's standards) feels much faster than many 1ghz androids, while it may not be. What's funny tho, even for those who want to compare benchmarks is this: the iPhone UNDERCLOCKED to 800mhz is faster than 98%(I don't have proof just google iPhone 4S bench and compare) of androids with have the RAM and sometimes even half the clock speed. I've compared it(4S) to the 1.5GHZ Rezound and it's like the difference between using a Droid 1 and GNex. It's partly got to do with the fact the Apple doesn't use crap SoC's like Qualcomm with crappy GPU's, but a lot to do with just having a well coded and well thought out OS.
I'm going to end rant bc I could go on, and on, and then on, but I didn't mean to offend anyone looking at androids but sometimes it seems like the grass is greener on the other side. It is in some aspects and isn't on others. I'm not posting this as a "iSheep" but as a person who has used almost every android in VZw lineup. When and if you make the transition you will miss things that work flawlessly(IMO) on iOS that can and do work(sometimes) great on android.
Lastly, even with the 4S hit or miss battery life, under heavy usage it blows every android out there. The iPhone IMHO is without question the best overall option out there for those looking at a smartphone.