Archive

Posts Tagged ‘Software development kit’

Apple Seeds iPhone OS 3.1

Apple has seeded iPhone OS 3.1 to developers along with a new version of the iPhone SDK.

Few details have been provided; however, its likely that Apple has closed the exploit used by ultrasn0w to unlock the iPhone.

Remember not to update when the new firmware goes public.

(via iClarified.com)




Update:
Word from the Dev Team on iPhone OS 3.1:

You’ve seen us give this warning before, and there are only so many ways to say it or come up with a clever title Smile But here it is: ultrasn0w users must stay away from any firmware updates past 3.0 (including today’s 3.1 beta) until we release the tools that let you update the firmware without updating the baseband. For most phones out there, baseband updates are irreversible and you’ll lose ultrasn0w. 

The 3.0 jailbreak was one of those (rare) times where both the jailbreak and the unlock coincided (the only other time was 2.2). It’s important that people realize that *most* firmware releases aren’t like that, and you need to take steps (via the tools) to separate the firmware update from its included baseband update. 

This warning does not apply to the iPhone 2G, which uses BootNeuter for the unlock, not ultrasn0w.

 Retweet This Post

3G iPhone, Apple News, Featured, Jailbreak/Activate, Software Unlock - YES!, What's New, iPhone, iPhone 3G S, iPod Touch News , , , , , ,

So what’s the big deal with iPhone firmware 3.0 anyway?

“So whats the big deal with firmware 3.0?” - A friend asked me with a look of confusion on his face… “Can’t all phones copy and paste stuff, forward sms messages, send annoying mms messages and all that crap?” … I stared at him and mumbled “uhh yeah, but they are all crappy phones.”

So what IS the big deal about iPhone Firmware 3.0 anyway?

Well, it’s one step closer to satisfying allot of iPhone and Touch users out there, myself included. It’s nearly everything we have been asking for from the beginning with firmware 1.0, and we all know that Apple is still holding out on us.

Do the new features of 3.0, (Tethering, MMS, A2DP Stereo Bluetooth, Landscape Keyboards and of course Copy, Cut and Paste among others) make up for the user customizing and limitlessness boundreis of jailbreaking and Cydia?

Well I am sure that 3.0+ will stop allot of people turning to jailbreak only apps like PDANet to tether their iPhone 3G to their Notebook, or Clippy to copy and paste stuff. Unless Apple addresses Video Recording, Springboard Wallpapers and Custom Icons, I think people are going to continue to jailbreak and customize their devices no matter what.

That said, I would bet that Video recording is coming with the new faster iPhone hardware in June and I wouldn’t doubt if Apple threw in some sort of springboard skinning app to try and sway allot of the jailbreakers from opening up the OS. But there is also one major reason to jailbreak the iPhone, and that’s to unlock the device to work with other carriers. As long as there is an iPhone Dev Team and the challenge and demand for an iPhone unlock, the hard working .org will be there to help.

Over the next few months the next 3.0 Beta’s will be rolling out and they are going to be chock full of all sorts of new API’s and hidden features. But what about the current 3.0 Beta? Is it worth installing on your iPhone (or Touch), more so is it worth forking out $99 US to join the Apple Dev Program just for the 3.0+ Betas? Let’s see..

iPhone 3G and 3.0 Beta

If you have an Unlocked iPhone 3G (using Yellowsn0w) - don’t do it. Just stop reading now, go and check out something else. Updating to 3.0 with an unlocked iPhone 3G will result in the iPhone 3G’s baseband modem (what connects it to the cell network) will be updated and the Yelllowsn0w unlock will be gone and who knows when or IF it will be able to be unlocked again.

If you either have a Officially Unlocked iPhone from an authorized carrier that can use any sim card, or you are locked to a carrier and have no plans on using the device with other sim cards, then you can try it out, but be warned, this is a Beta version of 3.0, so expect reboots and slowwwwww operating.

Some 3rd party apps (like Facebook), are not working entirely or properly. Downgrading your iPhone 3G on 3.0 back to 2.2.1 is possible but your modem firmware will still be updated, so if your having signal problems with 3.0 beta, then you may be having them still after forcing a downgrade to 2.2.1. Again, this is beta, you may want to wait for it to become more stable.

iPhone 2G and 3.0 Beta

If you have an iPhone Unlocked 2G, well the world is your oyster. I have updated my 2G iPhone back and forth. From 2.2.1 Unlocked, updated to 3.0 and remained unlocked (activated but no Jailbreak/Cydia), back down to 2.2.1 and was still unlocked (unactivated) and then QuickPwned to activate 2.2.1, got back Cydia etc, updated again to 3.0 via iTunes and was activated and unlocked (no Cydia yet on 3.0 obviously). So your iPhone 2G can make the trip up and down the Yellowbrick Rd as many times as you wish an remain unlocked.

Same as above though, some third party apps are not working correctly and on the 2G iPhone 3.0, Stereo Bluetooth, MMS and some other functions are either not turned on or are not going to work on the old hardware (like future Turn by Turn GPS apps).

How To Update to 3.0

It’s easy really, just find the 3.0 ipsw restore files for your device and make sure to hold option/alt and click Update, and NOT Restore with the 3.0 firmware, or you’ll be un activated and having to downgrade and start all over. Don’t ask me for the firmware or where to get it, google is a great place to start looking, there are all over the torrent sites OR you can join the Apple Development Connection, fork out the $99 USD and get the SDK and Beta firmware and instructions on how to install 3.0 on your device. Hell you may even develop and app and make a buck or two million.

Is 3.0 worth it to update?

Yes and No. 3.0 is not very reliable, As I have my iPhone 3G to fall back on if ever needed, I have no issues with updating my 2G and having a laggy OS or no caller ID, I can enjoy the 2G and 3.0 for a couple hours and when I am going out, swap my sim into the 3G and be on my way worry free. BUT - dam the new 3.0 features are great. I already miss them when using my 3G on 2.2.1.

Verdict

Wait. 3.0 is everything everyone is making it out to be. It’s full of new features and unfound suprises. It’s got the potential to be the BEST mobile OS out there, period. But at present, it’s buggy and laggy. It’s in beta. Getting it and installing it is not easy nor supported unless you are a Developer. I would wait until the official version of 3.0 comes out, unless you feel for a trip down the Yellowbrick Rd.


Reblog this post [with Zemanta]

 Retweet This Post

3G iPhone, Apple News, Featured, iPhone, iPhone Unlock Updates , , , , , , ,

Do It Yourself: Doom for the iPhone with TV-Out

Why he chose to use an Apple II monitor rather than a high-end HDTV? He says, "this is what passes for 'fun' around me."

We recently posted an article showcasing an undocumented feature in Apple’s iPhone Software Developers Kit (featured on many websites), where one iPhone developer was able to turn its game into a version suited for playback on big-screen TVs and using the iPhone as the game controller.

Well Steven Troughton-Smith, who ported Doom for the iPhone/Touch took it upon himself to try this out and has provided instructions for those that wish to try this our for themselves with Doom, their iPhone, and Apple TV-Out cable and of course a compatible TV/Monitor.

[Thanks to Steven Troughton-Smith and Erica over at ArsTechnica]

Try it yourself

If you’ve gotten excited about this iPhone/TV-out stuff, you can give it a try. Troughton-Smith has released the Doom source as an open source Google Code repository. Here’s what you need to do to put Doom on your iPhone, assuming you’re a registered (and pay $99/year) iPhone developer and have Apple’s iPhone SDK:

  1. Check out the latest svn repository from Google Code: svn checkout http://iphonedoom.googlecode.com/svn/trunk/ iphonedoom-read-only
  2. Locate the Xcode MobileDoom.xcodeproj in the iphonedoom-read-only folder.
    Right-click (control-click it) and choose Show Package Contents.
  3. Copy the steven.pbxuser file and rename it as your normal Xcode user name.
    In my case, that’s ericasadun.pbxuser. Your name will obviously vary.
  4. Download a copy of the Doom levels file, doom1.wad. I found a copy at MIT. I am not sure what the copyright/intellectual property of this material is, so use your best judgment.
  5. Add the .wad file to the project folder.
  6. Launch Xcode and open the MobileDoom.xcodeproj file.
  7. Open DoomAppDelegate.m and add a one-line definition to the top of the file to enable TV-out.

    #define ENABLE_TV_OUT 1


  8. In the Project Window, locate Groups & Files > Targets > MobileDoom and double click it. This opens up the Target Info window.
  9. In the Target Info window, click the Properties tab and update the Identfier to match your Apple signing identity. In my case, that was com.sadun.${PRODUCT_NAME}.
  10. Open the Build tab and update your Code Signing Identity, typically iPhone Developer: Your Name.
  11. In the Build tab, find Other C Flags. Set them to -DNORMALUNIX -DUSE_SOUND.
  12. Clean any previous builds, compile and deploy to your device.

Make sure you have connected your iPhone to a television using an Apple-branded cable. Then run the program and enjoy playing Doom.

[Via ArsTechnica]

Reblog this post [with Zemanta]

 Retweet This Post

Join the forum discussion on this post - (1) Posts

3G iPhone, Featured, Jailbreak/Activate, iPhone , , ,

Google admits breaking AppStore rules with iPhone Google Voice Search

Google acknowledged breaking the rules of Apple’s iPhone SDK when it created the latest version of the

Google Mobile application for the iPhone, where the app uses undocumented and unauthorized API’s to access the iPhone’s proximity sensor to initiate and terminate it’s new Voice Search service.

A Google spokesman confirmed Tuesday that Google Mobile uses undocumented APIs (application programming interfaces) in order to use the iPhone’s proximity sensor to prompt the verbal search. iPhone developers were only supposed to use the APIs that Apple published in the SDK when they create their applications under the
terms of that agreement.

Google has denied, however, a more serious charge that it was linking to private or dynamic frameworks in the Google Mobile application. That’s considered a big no-no in the development community.

The problem with using undocumented APIs is that your application code could break in the future as Apple updates its software, but a lot of developers appear to have taken that risk in order to deliver a cool feature, such as Google’s verbal search prompt.


[via Cnet]

Reblog this post [with Zemanta]

 Retweet This Post

Join the forum discussion on this post - (1) Posts

3G iPhone, AppStore News & Reviews, iPhone , , , ,