What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Wireless Moot

Status
Not open for further replies.
The only thing I remember about that was some people who had froze or removed stuff had to first get back to stock before going to any leak...which I believe still holds true in order to get OTA.
But when the OTA is released it will be cross checked with the. 246 leak..and afaik that release is the final official OTA...so everyone who is running the leak will be on the path again.
I'm not sure what you were asking/saying so if my response isn't what you mean, ignore it :)

Sent from my. 246 ICS leaked BIONIC

In the case of the .905 update, the leak and the OTA had different file sizes, so everyone on the leak had to fxz back to 902 and then take the OTA .905 before they could install any of the ICS leaks. That much I do remember because I spent a lot of time going back to 902, taking the OTA update before moving on to the next leak (before HoB, of course). I had to look back through some older threads to refresh my memory on this.
 
In the case of the .905 update, the leak and the OTA had different file sizes, so everyone on the leak had to fxz back to 902 and then take the OTA .905 before they could install any of the ICS leaks. That much I do remember because I spent a lot of time going back to 902, taking the OTA update before moving on to the next leak (before HoB, of course). I had to look back through some older threads to refresh my memory on this.
I'm sorry, you are wrong. Like I said, I am the person who LEAKED .905, I do believe that I know what I am talking about. If someone had different file sizes between the leak and the OTA, they had a corrupt download.
 
Dave12308 said:
Let's wait to hear what he did (if he feels like sharing, that is).

I created a swap file in the android system to allow better ram access i also recreated my kernels values to run more efficient an then edited my I/0 scheduler for a 15mbs write speed an 25mbs read speed an i entered the wrong @##%#&#&&@%@%@%@ value somewhere
 
Last edited:
You are absolutely wrong. There WAS no difference, as a matter of fact, the .905 OTA never touched my phone until well AFTER I had installed my first leak (I am the originator of the .905 leak, actually). Most of the people having issues were using Safestrap. A build is a build. By definition, if something in .246 were changed, the entire thing would have to be rebuilt, and it would no longer be .246

Roger that Smaj.....
 
Dave12308 said:
I'm sorry, you are wrong. Like I said, I am the person who LEAKED .905, I do believe that I know what I am talking about. If someone had different file sizes between the leak and the OTA, they had a corrupt download.

Absolutey right. If you don't believe us parse it, you know what parsing is? A tool that is gonna splash your ego. The parse will show a null difference, means they are exactly the same. Windows guy aren't you? Dave and I both flashed over the leak. Dude. Google "software versioning".
 
Last edited:
sargentmajord said:
I created a swap file in the android system to allow better ram access i also recreated my kernels values to run more efficient an then edited my I/0 scheduler for a 15mbs write speed an 25mbs read speed an i entered the wrong @##%#&#&&@%@%@%@ value somewhere

Sarge! You know better than to play with the swap and heap size!
 
Status
Not open for further replies.
Back
Top