Recent content by zeppelinrox

Multitasking mod would be the hardest part to update. There's alot of variations in smali code to consider. Coulda been a factor. But mostly time constraints and being swamped with more pressing issues. Big props to gu5t3r for his posts last few weeks. Funny that my absence prompted more...

I think xda's mailing system is buggy. I hadn't been notified regularly about replies to the thread. For example, I didnt get notified of Jar's reply. hisname is probably busy licking lollipops. lol yeah the Zeppelin has landed... ;) Well the pkill was a test to see if it would fix the...

Hey Primitive Screwheads... miss me? heh Been super busy IRL is all. Thanks to those that have helped the less fortunate and uhhh... logically challenged ;) oh nice. It would also be fine if all users of your caliber never found MY Supercharger. Because some people don't like free things or...

Work is killing me. I'm hoping somebody gets around to doing it lol Rebooting usually fixes that if there is no reason for that to happen. Well the patching is separate. Currently suffering from lack of time to update to the latest.

If only 3 blinks then its a dead battery. If it keeps on blinking and you cant get into flash mode, then its probably hard bricked. So if bricked, either fix it under warranty or open it up.

I used to take for granted that everybody would know what the "return" key was but it isnt so. Like Homer Simpson, some users would hit Andoid's escape/back key instead and wonder whats wrong with the script. The only thing you took for granted was a general level of competence but we also know...

1. Well you had adb push while you were still within adb shell ie. executing adb push from within the phone. 2. Its 1 line, not 3 lines. adb shell su -c "cp -f /sdcard/parted /system/xbin/" 3. SuperCharger runs fine but the patch hasnt been updated as of yet. Too busy lately to dive into it 100%

Ive stopped be concerned since I stopped thinking that there is an issue with the script.

Oh nice. You learned me something lol

Read the comments in the script. It even says what .1 means. Im pretty sure this is now a case of GUI.

In case you didnt know, the ran log will only show the latest flush. Evidence of the first 7 minute flush vanishes on the next flush since it is renewed. So if the interval is 1 minute, a new log is created every minute with no evidence of any prior flush. Just do what I asked. If you have a...

1. Answer my first question 2. Set the interval to 1 minute and wait 10 minutes until after boot. Then get the logs.

Nice idea! Whats the command to disable data?

Whats your idea? And yeah, even the flush script is rather complex lol

Ah ok. 1. V6 will actually tell you if FOM is in RAM. 2. If it isnt, open up 96superflush and turn on debugging. Just read its comments for the how to.