wet ipod touch, help! :(
hi, yesterday i was out in the street and it started raining… my 2nd gen ipod touch got all wet!!
the problem is… it was on all the time! i was listening to music and had the ipod in my pocket but still got wet, tried to turn it off but couldn’t because slider didn’t work… the whole touch screen doesn’t work correctly (volume goes up and down randomly, random keys are pressed when on the keyboard, etc… i could BARELY turn it off after trying several times)
what can I do? 
Slow/Laggy response time..
Hey,
I have a REALLY simple openGL app derived from the template… The animation timer interval is 1/60, and it calls my selector drawView().
The app has 6 total sprites on the screen: 1 background image, and 5 sprites that move around the screen. For some reason, I am getting EXTREMELY slow/laggy response times from moving these sprites around. I’m wondering if its possibly because I am doing all of the updates for these sprites within the drawView() before I do the rendering.
Do I maybe want to create a separate timer for updating these sprites, and keep the drawing on a separate timer? It’s really odd behavior, sometimes its smooth and doesn’t seem to get bogged down, and others, it seems to be really slow and laggy.
It seems odd that such a simple app with very little happening would have such slow, sluggish behavior.
Any help or possible theories would be greatly appreciated here.
Skype’s latest update breaks it on JB touch!
Just to let you know, last night I updated Skype and upon opening it after the update, you get a nice note saying the application won’t work on modified 2.2.1 or 3.0 devices. So beware if you want to use this app, update and say bye bye to it or un-jb to use it again. Is this a new trend by Apple to start making apps not work on JBed devices?
Need help with editing icons
hey,
I am very amateur with GIMP. I only just learnt how to resize and round the corners of an icon, lol.
I downloaded the Revolution theme, and well some of the icons aren’t included. So I decided to resize my own icons.
So I did so, but where I rounded the corners, a white background is left. How do I get rid of those, using GIMP?
This is what is looks like (Hotmail icon circled in red) :
No 3GS Jailbreak until OS 3.0.1 Released
The Dev-Team have stated that they will wait for the 3.0.1. firmware before releasing a 3Gs jailbreak. This gives them time to assess any patches Apple make in the new OS and to work on current issues with the 3.0 OS jailbreak they recently released for non-3GS devices.
However, the message is clear: 3GS owners who want to jailbreak should make a full USB dump or capture img3’s signed with their ECID to ensure that you will always be able to jailbreak going forward.
Quote:
|
Originally Posted by Dev-Team Blog
The needs of the many…
Spock said it best: “The needs of the many outweigh the needs of the few…”  Summary: We can jailbreak the 3GS right now. But making our jailbreak public at this point in time would benefit relatively few people. It would in fact be detrimental to many more people than it would help. So we feel it’s best to keep our version of the jailbreak out of Apple’s sights for the time being. Details: If you already have a 3GS phone and have already done a full USB dump or captured your img3’s signed with your ECID, then you’re in great shape. You will always be able to jailbreak. But many people who plan on getting a 3GS do not yet have one. For instance, many people are waiting for their existing contracts to mature to the point where they get a price break on the 3GS. Many people are trying to sell their 3G before they can buy the 3GS. There are parts of the globe where you can’t even buy a 3GS yet! The reasons are varied, but they are many. The nature of the 3GS hardware allows Apple to stop IPSWs from being usable unless you’ve already gotten the signed chunks they send to you based on your ECID (a unique chip ID). You cannot get these signed chunks without knowing your ECID, and you don’t know your ECID until you’ve bought your 3GS. The jailbreak requires at least one signed iBoot-family img3 for your device. And that iBoot needs to have an exploitable bug. It’s an all-or-nothing deal…you either have your signed exploitable iBoot ready to use, for now and forever — always jailbreakable — or you have nothing. Here’s the critical point, the reason why we’re delaying our version of the jailbreak: Once the jailbreak is out, Apple will fix the iBoot-family bug we use to accomplish it. They will simply stop signing the old iBoots and only sign the fixed ones. If you bought your phone after Apple has done this, there’s nothing you can do…the jailbreak isn’t going to work for you. It is possible that Apple will find the bug we use without our handing it to them on a silver platter (via a public jailbreak). In that case, we will have delayed our jailbreak for “nothing”. But we’d rather be safe than sorry! Apple is surely coming out with a 3.0.1 firmware release shortly. They need to fix ultrasn0w. They need to fix some UI issues. 3.0 is buggy and 3.0.1 is coming. We’re going to wait and see what 3.0.1 brings before figuring out the release date for our version of the jailbreak. In the meantime, we have some remaining 3.0 jailbreak issues to investigate, including push notification. Thanks for being patient with us while we took a 3GS “timeout”! |
Winners of the June Write & Win Competition
WRITE and WIN | June Winners
This month’s competition was to win a CoreCase Aluminium Slider case.
The winners of the June Write & Win Review competition are:
Member review prize:
Sargeant Pepper for the detailed and informative BeejiveIM review
MR Team Prize:
Radish for the excellent Knights On Rush review,
which was recently revisited to consider the 1.1 update of the game.
The July Write & Win competition will be opened tomorrow.
Keep and eye on the iTunes App Store Review forum for details.