yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] dakoop:
Tried flashing twice and both times in terminal after typing commands it says vipermod not found
[Thunderbolt Android Development] SubliminalME:
Seems to be working fine for me too.used rom manager and it worked first time...2.0.5 and 2.5.4 at 1.4 with interactivex and .25 reduction so far
[Thunderbolt Android Development] bilbobrian:
Does anyone have text formatting issues in terminal using the latest build of CM7? I'm trying to figure out my issue.
[Thunderbolt Android Development] sincerity:
ediiiiiiiiiiiiiiiiiiiit
[Thunderbolt Android Development] -viperboy-:
Try redownloading from another browser. Your browser may have cached the bad file.

This was reported by one of my testers. I have no idea what would cause that, but I don't believe it's my script. It must have something to do with that Terminal. Is the one included with CM7 Android Terminal Emulator? That's what I use, but my tester said that using that didn't help but maybe it will for you?
[Thunderbolt Android Development] sincerity:
got it to work! can someone explain a little to a newb what I am supposed to do with this? thank you!

Like how do I tell how low my phone can go?

sorry for the lame n00b ?
[Thunderbolt Android Development] -viperboy-:
It's for modifying voltages on kernels that support the sysfs interface which basically allows the user to edit voltages on-the-fly instead of the values being hard-coded into the kernel when compiled.

So, what this will do for you is allow you to lower your voltages for better battery life or raise them if you are having issues running a custom kernel when the voltages may be too low for your phone. You can go as low as your phone will let you. What I mean by that is not all phones can handle the same voltages. My recommendation would be to lower the voltages by 25mv. Don't save anything, just run it like that for a little. If you're stable, go back in and save the voltages, then lower by 25mv. Repeat this until you find that your phone is unstable then raise voltages by 25mv, save, and run your phone there. It takes some time, but that's probably the easiest thing to do.

That's pretty much it in a nutshell :) there aren't alot of option for SVS kernels because they're pretty simple. But you will get better battery life with this mod for sure!
[Thunderbolt Android Development] sincerity:
perfect thank you!
[Thunderbolt Android Development] -viperboy-:
You're welcome :) thanks for using this! Please let me know if you guys find any bugs, have suggestions, want to see certain features or whatever. Also, I can't wait to hear how battery is for you guys!
[Thunderbolt Android Development] bilbobrian:
That was me...:)
[Thunderbolt Android Development] -viperboy-:
I didn't know if you wanted to be identified lol thanks for all your hard work!
[Thunderbolt Android Development] bilbobrian:
No problem. Hit me up if you need anything else tested.
[Thunderbolt Android Development] tct08:
I downloaded the file through both Dolphin and the stock browser and checked to make sure the file was I the zip but cannot get it to install through CWM. The zip flashes fine, but nothing. I'm BAMF gingerbread of that makes a difference.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] dakoop:
Is there a way to automate this? There was an oc app for the x that would keep lowering voltage until it errors and use most stable
[Thunderbolt Android Development] Jaxidian:
QuickClock Advanced Overclock is the app you're thinking of. Bought it but never found much use in it as I already knew what my dx supported (not much in terms of oc but lots in terms of uv).
[Thunderbolt Android Development] -viperboy-:
When you say "but nothing" you mean you can't run the script or you can run the script but things aren't changing? What kernel are you using?

Thanks for the info on that app. Unfortunately, that app doesn't seem to support Qualcomm processors (judging by the looks of supported devices). I don't currently know of a way to make the script find stable values, but I will certainly look into it :)
[Thunderbolt Android Development] tct08:
When I type SU --> vipermod it just says not found. I'm running Imoseyon's 2.5.4 test 4
[Thunderbolt Android Development] -viperboy-:
This seems like a Thunderbolt-only issue. I wonder if it doesn't like how it's being mounted in recovery? Try flashing twice in the same recovery session, one user said this worked for him. What recovery are you using?

Also, have you downloaded the .zip before? You may have downloaded the bad copy I accidentally posted. You may want to try downloading from another browser.

If it still doesn't work, you can manually extract the file to /system/bin then use Terminal and do:

chmod 0777 /system/bin/vipermod

su

vipermod

That should work for you. Please let me know if anyone else is still experiencing an issue with the mod not sticking after flashing.
[Thunderbolt Android Development] detox246:
Removed post
[Thunderbolt Android Development] Gunthermic:
Flashed in Recovery mode, vipermod not found error. Something is not right with the flashable maybe? I just downloaded it so I dont have any cached version of this mod.
[Thunderbolt Android Development] -viperboy-:
What recovery/ROM/kernel are you using? I am pretty sure it is Thunderbolt specific because I haven't heard anything about it for any of the other devices.
[Thunderbolt Android Development] dsvoda:
These are my settings running bamf remix and working great.
[Thunderbolt Android Development] -viperboy-:
Thanks for posting this! Did you have any issues flashing in recovery? What recovery are you using?
[Thunderbolt Android Development] Gunthermic:
I am using BAMF 1.1 Stripped ROM. And Ziggy's May 3, CFS Kernel.

I had to manually extract and move the file and chmod it, to get it to work. Using your flash.zip it doesn't put the file into bin. I did all this over phone so I haven't done a search as to if the file was put anywhere at all. I will also look at the zip tonight to see if I see anything as well.

I have already lowered mine by 50v so far and all is running well. Not seeing any lesss battery drain yet though. It's dropped by 5% in last 30 minutes with very little use. But I will contniue to monitor and adjust down.

Right now my low is 800 for 245Mhz and 1000 for 1036Mhz
[Thunderbolt Android Development] -viperboy-:
It wouldn't put it anywhere else other than /system/bin. If it didn't put it there and it's working on all the other phones I support, I assume recovery may not like the mount command. What recovery are you using?

For anyone else, could you please comment if flashing in recovery worked for you or not and what recovery you're using? Thanks in advance.
[Thunderbolt Android Development] Gunthermic:
clockwork recovery..

What is the lowest you recomend at this point. besides doign the 25 at a time, and creep it down. Maybe a better question is what is a good startign point and how long before creepign down?

**Edit: I think I may have found the lower limit. LOL tried to go lower than 800 and it froze then rebooted on me.
[Thunderbolt Android Development] johnclevenger:
Flashing in recovery CWM did not work for me. I had to manually move it (I put it in /xbin) and then change permissions.
[Thunderbolt Android Development] -viperboy-:
It's hard to say since I don't have the phone. It would be best to see what other users are doing to get a general idea of their voltages. As far as a good starting point, there are many ways to do it. The quickest (but possibly most annoying) would be to lower by 25mv and use the phone for about a minute, then reduce another 25mv. Repeat until the phone freezes/reboots. (I would recommend remembering your voltages and not saving, because if you save and the phone freezes, it may just bootloop) Then after the reboot, lower the 25mv above where the phone froze and save.

That's the way I would probably do it if I ran an SVS kernel :)
[Thunderbolt Android Development] dsvoda:
I didn't use recovery and glad to help. I like being a test dummy.
[Thunderbolt Android Development] -viperboy-:
Ugh, I'm not sure why it's not working for everyone. Sorry about this, I will look into it further and talk to some of the Thunderbolt Devs. For now, please utilize the workaround.
[Thunderbolt Android Development] Gunthermic:
Will also take a look at it when i get home tonight viper. Will PM you if I find anything within the flash myself.

800 seems to be the limit fo rmy Thunderbolt. 775 locks it and reboots.
[Thunderbolt Android Development] biggiephat:
mine flashed no problem.

...
[Thunderbolt Android Development] -viperboy-:
OP updated! Please see the changelog on my site for more information! The scripts should now flash better for you guys, please let me know!
[Thunderbolt Android Development] tct08:
I've tried the new zip (now back on Remix 1.6.3 Froyo) in CWM and now when I'm in the terminal, it recognizes that ViperMOD is there, but the screen flashes non-stop what looks like the ViperMOD logo and some other text (the lines keep moving and flashing so it's hard to read). From what I can make out, there is a warning that I'm on an unsupported device (Mecha) when I'm clearly running from a Thunderbolt.
[Thunderbolt Android Development] -viperboy-:
Oops! Good call. I changed my build.prop for ro.product.device to be "hi" and I saw what you were talking about. I fixed that problem, now I just need to know what ro.product.device says in a Thunderbolt build.prop. I was told it was "mecha", can someone please advise? I will put out an update once I have confirmation. It will probably take me longer to donwload a ROM than for one of you guys to answer this :p
[Thunderbolt Android Development] tct08:
I'm pretty sure it is Mecha
[Thunderbolt Android Development] -viperboy-:
Is the "mecha" or "Mecha". I need it exactly, please.
[Thunderbolt Android Development] -viperboy-:
Found that it is "mecha" so you shouldn't be getting a loop in the first place but I'm uploading RC2.01 now.
[Thunderbolt Android Development] tct08:
I checked and it actually says mecha exactly like that

edit: good timing =/ Well I'm not sure why it's saying unsupported device then.
[Thunderbolt Android Development] -viperboy-:
Neither am I. Try downloading RC2.01 off my website and see if it's working for you now please.

EDIT: What is odd is that I changed ro.product.device to mecha and the script worked for me without looping. That was before I posted RC2.01, so that's weird that it would do that to you. Just let me know what happens.
[Thunderbolt Android Development] tct08:
The screen is not looping anymore but it still says

mecha

Not an officially supported device
[Thunderbolt Android Development] -viperboy-:
Post your build.prop for me. I don't know how this is possible because if I change it to mecha on my phone, the script works just fine.

EDIT: I changed it to say "mecha " (with a space after it) I see the same error message you do. Maybe that's what's wrong.
[Thunderbolt Android Development] tct08:
http://dl.dropbox.com/u/18274663/build.prop

I looked in it and it says mecha...very odd
[Thunderbolt Android Development] -viperboy-:
Very odd, indeed. I have no idea to be honest. I can change my build.prop to say mecha and it works as it should but it's not working for you. Let me see if anyone else has this issue.
[Thunderbolt Android Development] -viperboy-:
Can anyone else give RC2.01 a shot and see if they have issues?
[Thunderbolt Android Development] biggiephat:
Does not work for me either. Says my mecha is an unsupported device. What did you change so much from rc1 to 2 that breaks it. It was working fine for me before
[Thunderbolt Android Development] -viperboy-:
The whole device detection, basically. It works perfectly for me on my EVO. Right now, I have no idea why the script is doing this to you guys since I have a pre-defined action for when it detects the Thunderbolt (and any phone, actually). This way, if you are running a HAVS kernel, it won't show you SVS options and things like that.

Basically, it looks like it's reading that it is a mecha but not following what I have it set to do which makes no sense if you look at how I coded it.
[Thunderbolt Android Development] biggiephat:
what is this coded in...im looking at it and im only good at c++ java.

syntax that just has a closed paren and not an opening one blows my mind.
[Thunderbolt Android Development] -viperboy-:
This is just basic shell scripting but it should still make sense to you if you look at it. You'll be looking toward the end of the file where you see "case $devicecheck in". You'll see that mecha is defined there. Check it out and let me know if you see anything wrong. Sometimes, it just takes a second set of eyes :)
[Thunderbolt Android Development] biggiephat:
yea i dont know shell scripting lol. probably should pick this up. Ill look at it. my SE degree needs to be put to use at some point lol
[Thunderbolt Android Development] JimSP:
I don't know why this works, but it did for me...

I looked at the shell script and couldn't figure out why it was failing it seems like it should work. So I edited my build.prop in root explorer and changed ro.product.device to inc. Ran the script again and this time it gave me the options for the Droid Incredible.

Manually switched my build.prop back to mecha (did not just rename my build.prop.bak) and ran the script again. Everything works now, I'm slowly dropping my voltages now to find out where it loops at.

[/IMG]

**Edit** Went back and rename my original build.prop and it still fails. Works fine as soon as I put the manually edited one back.
[Thunderbolt Android Development] gitku:
Same thing here .. unsupported device .. was using 1.2 before worked great
[Thunderbolt Android Development] -viperboy-:
Thanks for the info! So, it seems like there is something messed up in the build.prop. Atleast, that's what it seems like.

What is odd though is in your screenshot, it doesn't tell you what processor you have and it should. Hmm...
[Thunderbolt Android Development] JimSP:
Yeah I don't know what's up with the build prop I looked at them both side by side in a text editor and they look exactly the same. I don't have a box available to do a diff on right now.

The processor thing I forgot to mention. In your script it is grepping for msm7k in the build prop it is msm7x30. I'll change the script at lunch and report back.
[Thunderbolt Android Development] JimSP:
Ok I think I figured it out. In the original build.prop both the mecha and the msm7x30 in the ro.board.platform both have a space right after them. I erased the extra space on msm7x30 (and changed the original script to msm7x30) and now everything appears right.

That was probably what is wrong with the script in the first place that extra space is causing it to fail. That is why it worked when i entered it manually, I didn't include the space.

I'm going to flash back to my original backup before I started messing with this today and edit the script and test once more I think everything should work right from the beginning.

[/IMG]
[Thunderbolt Android Development] -viperboy-:
Ah wonderful. Thanks so much for looking into this! Would you be able to hop in my IRC channel some time after 330?
[Thunderbolt Android Development] JimSP:
Yeah I'll PM you my gchat hit me up when you are ready and I'll jump on.
[Thunderbolt Android Development] bootny:
I appreciate all of the work you put in! When I set up v3 1.2 it wouldn't save..so I will try 2.1 and get back to you

midget tossing is habit...2010 midwest regional champion... hw 001
[Thunderbolt Android Development] -viperboy-:
Can I get a few people to test the next release in IRC right now?
[Thunderbolt Android Development] -viperboy-:
OP updated! I'm expecting there to be a few more bugs that need to be fixed so PLEASE post here and help me fix them!
[Thunderbolt Android Development] -viperboy-:
OP updated! Support for custom voltages for HAVS and SVS on Snapdragon processors!

Enjoy :D
[Thunderbolt Android Development] toebee76:
It flashed fine for me. But it wont allow me to enter voltages below 750. Not sure if this is a kernel or script issue. I am using bamf stripped 1.1 with Imoseyon's lean minimalistic kernel, v2.5.1. When I enter something lower than 750 it says its been changed but when I check the voltages it stays at 750.
[Thunderbolt Android Development] -viperboy-:
750 is the floor that is hard coded into the vdd interface. I need to set limits on these things so it alerts the user that you can't do it. But that's a limit of the kernel, not my mod :)
[Thunderbolt Android Development] -viperboy-:
OP updated!
[Thunderbolt Android Development] toebee76:
I tried flashing it to one of the alpha cm7 roms and it comes up as not found when I enter "vipermod".
[Thunderbolt Android Development] -viperboy-:
look in /system/bin - do you see it there?
[Thunderbolt Android Development] toebee76:
No I don't. That is if I am looking for a file called vipermod.
[Thunderbolt Android Development] -viperboy-:
Yeah you are. Please do the manual work around in the FAQ on my site.
[Thunderbolt Android Development] toebee76:
Ok I did it and its working. However I now can't change the voltages of each speed separately anymore. It say's that the option is coming soon. Is there a way I can make that work again?
[Thunderbolt Android Development] -viperboy-:
You must have downloaded an old version. Make sure when you fire up the script it says v3 beta 2.11 at the top.
[Thunderbolt Android Development] toebee76:
Sorry about that. I am not sure how I ended up with the old version. The new version flashed fine. One annoyance I have is when you raise voltages you do not have the choice for custom. You have to raise the voltage of all speeds. It makes fine tuning a pain.
[Thunderbolt Android Development] -viperboy-:
You actually can do it. custom voltages is under lower voltages but you can raise from there. I had plenty of feedback to move it out of that menu so I will in the next update.
[Thunderbolt Android Development] toebee76:
Oooh OK sweet. Thanks
[Thunderbolt Android Development] -viperboy-:
OP updated! I highly recommend that everyone update to this, all errors should be fixed now on all phones and ROMs!
[Thunderbolt Android Development] JimSP:
Good to see you back, I'll have to give it a try later.
[Thunderbolt Android Development] Camaros_Kill:
Im glad this got updated or i probably never would have seen it! Im running Imoseyens newest kernel on Thundersense 1.5 and i was able to set my voltages about 100mv lower on every clock 1.0ghz and lower! My battery life was already decent, but i cant wait to see what kind of improvements this mod will bring. Unfortunately, my Bolt must be a weak one because ive never been able to run it over 1.6ghz. Even with voltages cranked all the way to the 1475 max, it bootloops at 1.76ghz, the next step on this kernel after 1.6. Oh well, 1.6 is fast as hell anyway, and i dont really go over 1.2 for normal usage. Thanks for this mod!!
[Thunderbolt Android Development] YankInDaSouth:
This for GB, froyo or both? I'd love a GB kernel that solves the slow charge issue!
[Thunderbolt Android Development] -viperboy-:
Any kernel with the sysfs interface, I don't have a TBolt so I am not completely up to date with kernels and such, but on the left side of the FAQ page on my site there is some information about compatible kernels. You can also just give this a shot on whatever custom kernel you're running and see if it works :) I want to say it's only Froyo for now (just like the EVO) since I don't think there is kernel source yet.
[Thunderbolt Android Development] YankInDaSouth:
Awesome, thanks for the response. Currently running froyo so I may have to give it a try.
[Thunderbolt Android Development] n0thing2bdone:
what do you do if it bootloops? how do you undo changes? thanks
[Thunderbolt Android Development] -viperboy-:
Download the reset .zip on my site under the downloads page and flash it in recovery.
[Thunderbolt Android Development] pats4life100:
this is just a kernel right and can i use it on plainjanev3-froyo-1 rom
[Thunderbolt Android Development] -viperboy-:
No. It's a mod for a kernel. All the info is in the OP or on my site.
[Thunderbolt Android Development] bilbobrian:
Thanks viperboy.
[Thunderbolt Android Development] -viperboy-:
Anytime :)
[Thunderbolt Android Development] Camaros_Kill:
I tuned my voltages all morning long and i was actually able to get into setcpu and change max clock to a speed that was still stable before it bootlooped a second time. u just gotta go for it as soon as the launcher comes up. I did this maybe 12 times, probably more boots on my Thunderbolt this morning than all the rest of its past life combined.
[Thunderbolt Android Development] -viperboy-:
Just a quick update, here is what the app is looking like:

Definitely making some great progress. Before this is released, you will see a -25mv and +25mv button for easy changing of all voltages and I would love to make the volume buttons do that too :D There will also be an "Apply" button and a "Set on Boot" button with a confirmation message.

Also, I could use a logo for viperMOD if you guys would like to help me out! Please, something professional - nothing done in paint :D 512x512px and a second promo logo (what you see in the Market when you click on the app) that is 180x120px. Please send all submissions to viperboy@tiamat-aosp.com and I will pick the best one and I will give that person a free copy of viperMOD [Pro, +, whatever I choose to call the paid version]!

Just like to keep everyone up to date :)
[Thunderbolt Android Development] -viperboy-:
After multiple requests, I have decided to put a Donate button in my sig. Please read the link underneath it, I think it's imporant.

Also, please don't feel obligated to donate. I hope you don't see this as me "whoring myself" to you guys. I've been asked numerous times in the past to put up a donate link and I finally decided to. I do what I do because I love Android and I really want to continue getting my hands into everything Android. You guys give me something to work for and I really enjoy making a user happy, even if it's only with my lowly shell script.

If you would like to donate, I would really appreciate it no matter the donation amount. You guys are awesome and I can't thank you enough fore giving me a great place to dev and provide to such a great community.

Sincerely,

Derek
[Thunderbolt Android Development] Gunthermic:
Thank you for your hard work.
[Thunderbolt Android Development] -viperboy-:
OP updated with the new website. HUGE thanks to Cayniarb with Tiamat Kernels for the hosing and website. Definitely the best kernels out there, you really should check them out if there is one for your device! Thank you very much, Cayniarb!
[Thunderbolt Android Development] nerogold:
Thanx viper, have been trying the older mod on new kernels but never worked. Again thanx for update.
[Thunderbolt Android Development] -viperboy-:
Sorry, what isn't working?
[Thunderbolt Android Development] arasky:
im on tiamat 1.0.4 and i dropped 100mV which is stable for me at 1GHz (1075mV stock), but when my phone screen goes off and drops to 268MHz (825mV stock) is when it causes problems. my question is, should i lower the voltage to the lowest value that will take, say 50mV, and keep it stable at 245-1000MHz or increase the minimum frequency to 345MHz with the same drop in voltage?

thanks
[Thunderbolt Android Development] shelooga:
ill have to try this out. i loved quickclock for my dx, and obviously i want to squeeze every second of battery life i can out of this phone. im going to try it out once i finish a few things im working on (my first gb rom).

in the meantime, i have a rough idea for a logo, although i have no experience in creating logos, especially without the use of paint lol, but if youre familar with the Dodge Viper (and if you arent, well, go to hell) i think you should alter that logo a bit and use that. its a pretty sharp badge