yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] hexagon_sun:
Been lurking on here for a while but now I've run into an issue that just straight up boggles me, and I'm not sure what (if any) actions will fix it.

I just recently upgraded my phone from rooted/lagfixed JFD Stock Firmware to JI5, and then subsequently to JI6. Of course I had to de-root and lagfix before I did that. I was able to upgrade to JI5 and JI6 just fine. Everything works great.

Then I put One-Click Lag Fix on.

I can apply the root and all of the fixes. The phone boots back up, and in general works fine. I can also notice an increase in performance. But the drawback is, for some reason I now can no longer have vibrations of any kind. No Haptic Feedback, no vibrate for phone calls or notifications. No vibrations of any kind.

I'm stuck between a rock and a hard place here. I work in a company that would prefer I keep my phone on silent (vibrate) mode, so really I can't be missing that functionality. But I do want to benefit from the OCLF performance boost.

Has anyone else experienced this issue? Any one have ideas of how to fix this?

Here's as much detail as I can give you about the phone:

*Vibrant with 2.1 T959UVJI6 - downloaded from here: xdaforums.com/showthread.php?t=798125&highlight=JI6

*Applied RyanZA OCLF 2.1.2

*Rooted/EXT2 Tools/One-Click Lagfix 2.1+

Hopefully that's enough information. As I said, if I de-lagfix it, the vibration comes back, so there's no doubt that it is directly correlated to OCLF in some way. If there aren't any good options, then I'll probably just de-lagfix and keep it with JI6 stock. At least the GPS works. :P

One last thing, I also tried the oft mentioned Sound Manager workaround... to no avail.

Thanks to anyone who can help. Sorry for posting a book.
[Vibrant Q&A, Help & Troubleshooting] SamVib:
I would like to know also. I was on JI6, and applied the OCLF. I reverted back since I really really, missed vibrations.

I really don't know why that would trigger the vibration to go off. weird.
[Vibrant Q&A, Help & Troubleshooting] hexagon_sun:
Yeah, it doesn't make much sense to me either. I know when I did the older Lagfix on JFD my phone vibrated and everything worked fine. I've heard that JI2 is fine too, though I never tried it. I'm hesitant to go back down to JI2 though because from what I heard that requires a flash and re-partition, and I've already had to do that a couple times.
[Vibrant Q&A, Help & Troubleshooting] samoelito:
i have the same problem, but i didn't know this was caused by the OCLF.
[Vibrant Q&A, Help & Troubleshooting] hexagon_sun:
I had a couple of people mention to me that it was something dealing with a library change that OCLF makes. Not sure if that's true or not. I haven't gotten any answers about what I could do though, so if I don't hear anything soon, I'm just going to de-lagfix it.
[Vibrant Q&A, Help & Troubleshooting] kas21:
I am also having this issue. I went from stock JFD to JI5 and then back to stock JFD to JI6. Vibrate stopped working in JI5 and JI6 when OCLF v2 was applied. Version 1 of the lag fix seems to work fine and the only difference is supposed to be that v1 uses symlinks and v2 use bind mounts.

I have also noticed this in my logcat.

E/HardwareService( 2288): RuntimeException occured at doCancelVibrateLocked().
W/System.err( 2288): java.lang.RuntimeException: VIBE_E_NOT_INITIALIZED
W/System.err( 2288):	at com.immersion.android.ImmVibe.StopAllPlayingEffects(Native Method)
W/System.err( 2288):	at com.immersion.android.ImmVibe.stopAllPlayingEffects(ImmVibe.java:323)
W/System.err( 2288):	at com.android.server.HardwareService.doCancelVibrateLocked(HardwareService.java:516)
W/System.err( 2288):	at com.android.server.HardwareService.vibratePattern(HardwareService.java:350)
W/System.err( 2288):	at android.os.Vibrator.vibrate(Vibrator.java:69)
W/System.err( 2288):	at com.android.internal.widget.LockPatternView.detectAndAddHit(LockPatternView.java:471)
W/System.err( 2288):	at com.android.internal.widget.LockPatternView.onTouchEvent(LockPatternView.java:557)
W/System.err( 2288):	at android.view.View.dispatchTouchEvent(View.java:3765)
W/System.err( 2288):	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288):	at com.android.internal.widget.LinearLayoutWithDefaultTouchRecepient.dispatchTouchEvent(LinearLayoutWithDefaultTouchRecepient.java:54)
W/System.err( 2288):	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288):	at com.android.internal.widget.LinearLayoutWithDefaultTouchRecepient.dispatchTouchEvent(LinearLayoutWithDefaultTouchRecepient.java:57)
W/System.err( 2288):	at com.android.internal.policy.impl.UnlockScreen.dispatchTouchEvent(UnlockScreen.java:376)
W/System.err( 2288):	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288):	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:822)
W/System.err( 2288):	at android.view.ViewRoot.handleMessage(ViewRoot.java:1716)
W/System.err( 2288):	at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 2288):	at android.os.Looper.loop(Looper.java:123)
W/System.err( 2288):	at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:582)
[Vibrant Q&A, Help & Troubleshooting] funkyfungus:
I have this problem too. I just used Odin to go to the JI6 and I thought it was still laggy especially in Touchdown. Did root and OCLF 2.1 and no longer have vibration. Any news?

Thanks!

fF
[Vibrant Q&A, Help & Troubleshooting] T.Els:
I just wiped and installed up to JI6 and after installing oclf I am now without haptic feedback as well. Used the market app to apply the fiix.
[Vibrant Q&A, Help & Troubleshooting] ugonnax:
You can use the first version and you will have lag fix and also your vibration back.
[Vibrant Q&A, Help & Troubleshooting] mayhem1983:
What first ver are you refering too? Mine happen after I applied lag fix!
[Vibrant Q&A, Help & Troubleshooting] mishler77:
Thanks, I've been looking all over for this! Never thought about OCLF because vibration was fine before the update. Undoing V2 now...
[Vibrant Q&A, Help & Troubleshooting] lonejedi:
I am using JI6 with OCLF v2+ and the haptic feedback is working for me. It didn't work when I left the EXT Size option at the default, but I tried increasing it to about a Gig and it now works fine. I'm not sure if this is why it was fixed, though. Can anyone else try and confirm?
[EVO 4G Q&A, Help & Troubleshooting] freeza:
If the point of HAVS if to regulate voltage, etc. Wouldn't using SetCPU, well profiles in SetCPU, work with HAVS? Example:

I have a profile set to minimize frequencies from 128-245 mhz when screen is off. If HAVS worked with these frequencies to lower voltage, wouldn't keeping the frequency threshold between those two numbers keep HAVS maintaining a lower voltage?

I see a lot of people saying not to use SetCPU profiles with kernels that include HAVS, but never really explanation why.

Also, If one would decide to only use a profile while the phone was charging, that would have no effect on HAVS when the phone is unplugged, correct? I want to be able to switch the CPU governor to ondemand while the phone is charging so I can get the maximum performance, but when it's not charging to just go back to the kernel default, which is conservative. If using profiles negatively effects the performance of HAVS, can I just use a charging profile without negatively effecting HAVS?

Explanations people!
[EVO 4G Q&A, Help & Troubleshooting] drmacinyasha:
Snap 7.6 (which has nHAVS) works fine with SetCPU, and you're encouraged to use SetCPU. I don't know where you're seeing this "Don't use SetCPU!" stuff, but it's probably just people who are trying to prevent a deluge of complaints about their phones acting wonky.

Use SetCPU. The worst that can happen... Is your phone acts wonky/poor battery life. Make sure to NOT check the "Set at boot" options in SetCPU while you're testing!
[EVO 4G Q&A, Help & Troubleshooting] freeza:
Figured as much. Thanks!
[EVO 4G Q&A, Help & Troubleshooting] beatblaster:
Ya know, I never understood why people were saying not to use SetCPU with HAVS kernels either especially since, like, for example, Calkulin highly recommends SetCPU for use with his ROM and that comes packed with Kings #10 nowadays. I figure if Calk (or any other reputable ROM/kernel dev) says to do it he's probably saying it for your benefit. Now, on to find a real reason as to why or why not :)
[EVO 4G Q&A, Help & Troubleshooting] rugedraw:
I think that what is meant is that you don't have to use SetCPU because HAVS already reduces voltage to the processor when it isn't being used. Using SetCPU profiles won't mess anything up, but it is redundant to do so if the HAVS kernel is already controlling the amount of juice that goes into the processor at any given time.

Please note this is a hypothesis. I am not an expert by any means. If someone knows any better, please clarify, because I have been curious about this, too.
[EVO 4G Q&A, Help & Troubleshooting] freeza:
It makes sense, but isn't HAVS only a voltage regulator? Using SetCPU to lower frequencies should theoretically compliment HAVS especially with screen off profiles as to keep the voltage low with HAVS, and frequencies low with SetCPU. I know that Android/CPUs clock down when idle or when the screen is off, but their maximum frequencies aren't lowered as well are they? Using SetCPU to set a maximum frequency that's low should be even better. That's my take anyway.

Here is a comparison someone did with SetCPU and various kernels and went so far as to say they've read several places that using SetCPU in conjunction with 'newer' kernels may be counterproductive, since the inclusion of HAVS. However, I haven't been able to find that many posts to backup this claim. That or I just suck at searching. lol

http://androidforums.com/evo-4g-all-things-root/179761-kernels-setcpu-battery-comparison.html
[EVO 4G Q&A, Help & Troubleshooting] jasonziter:
I'll run a test

Okay. Been running the Netarchy CFS HAVS 4.1.9.1 universal kernal in conjunction with set cpu and using Virus Anthrax v4.....battery life is bad so far. I don't know how it could be better on anyone else's phone either. I have set CPU set to minimal settings (profiles) and conservative. My up time (display)has been around an 45 min total. One call and a couple of MMS sent. My power manager settings keep the screen set to 80 on battery power. Total time 7 hours with 32 percent remaining.

Wifi, 4G, GPS, and push are TURNED OFF. Nothing that drains battery above normal system apps, is running.

This is not a good Kernal UNLESS........its because I just started using it this morning with my first run through of the battery being fully charged and the stats reset at the time of full charge.

So the question is:

How long should we run a kernal after:

1. Installing it

2. Starting with fresh 100% battery charge

3. Wiping battery stats.

Does it need one drain and one full charge before you throw the kernal to the dogs?

Should set CPU be disabled / uninstalled after HAVS kernals are flashed? I think I remember reading somewhere that you should not use set CPU with HAVS kernals. It doesnt make sense to me as set CPU sets the clock frequency and HAVS is for voltage scaling?

Im going to try and recharge the phone tonight after full run down and disable the set on boot setting for set CPU.

Anyone have any answer on this?

-JZ
[EVO 4G Q&A, Help & Troubleshooting] ms79723:
Well my understanding is that havs and setcpu do the same thing sorta, depending on how you set your profiles up. Because havs underclocks while the screen is off, which can be done with setcpu, and if you set setcpu to conservative then you might be getting the same affect you would get from havs. Having them both run is like overkill, your phone would be doing double the work for the same results.

Battery still gonna be a pain while the screen is on so it's not like both of these will drastically increase battery life while in use. It'll just manage the battery alot better while the phone is idle.
[EVO 4G Q&A, Help & Troubleshooting] freeza:
Hmm.. I should probably do some more reading on HAVS, because if it is responsible for regulating clock frequencies as well, then it would be counterproductive. HOWEVER, if HAVS does indeed regulate clock frequencies, the question would be what is the minimum/maximum frequency that our current HAVS kernel allows when the phone is asleep or idle? Because on my SetCPU profile, it is 128/245MHz for screen off.
[EVO 4G Q&A, Help & Troubleshooting] jasonziter:
I don't set my set cpu that low because, again......I read this somewhere....., set CPU with frequencies below 384 will disable the WIFI. Sounds wacky.....I know...if there is any truth to this let me know. I guess I could check to see if the WIFI enables after the screen off.....eg....its looking for the ip....

Great idea on a thread OP. Its obvious we need a place to gather some real information from reliable sourses on:

1. SET CPU and its use with newer Kernals / Kernals with HAVS in them

2. Are the newer kernals so evolved that set CPU is no longer needed. (I'd love that as Im a bit tired of setting my profiles every time I flash a ROM)
[EVO 4G Q&A, Help & Troubleshooting] freeza:
I have my WiFi turned on and connected to my home network all the time and have never noticed it shutting itself off or disconnecting with my frequencies that low :)

I don't think SetCPU will ever be obsolete unless devs compile a kernel that can automatically do the following:

-set max frequency to higher than default. (but probably wont for max compatibility reasons, since no evos are made equal and that said frequency is guaranteed to work with all evos.)

-set minimum frequency to the lowest possible without adverse reaction.

-dynamically change governor based on either charge state/load state/or remaining battery life.

-dynamically change max/min clock frequencies based on either charge state/or remaining battery life.

SetCPU will probably always be in my bag of must haves, BUT if there is proof that using profiles negatively effects HAVS, I will just remove the screen off profile. With netarchy's 4.1.9.1cfs kernel, conservative governor is the default, and SetCPU allows me to change governor to ondemand with a profile of charging/full. This is perfect. :)
[EVO 4G Q&A, Help & Troubleshooting] freeza:
Speaking of HAVS and SetCPU, a snippet from the common misconceptions thread:

http://xdaforums.com/showthread.php?t=790427
[EVO 4G Q&A, Help & Troubleshooting] wmdunn:
There's quite a bit of information in the Ultimate Kernel Review here ...

http://xdaforums.com/showthread.php?t=790559

In a recent post, the author (skydeaner), posts his own personal settings which include Kings #9 (havs) and SetCPU ...

http://xdaforums.com/showpost.php?p=8465730&postcount=104
[EVO 4G Q&A, Help & Troubleshooting] jasonziter:
Nice post man. Finally... some real info to use. I think I'm going to airborne virus with kk9.
[EVO 4G Q&A, Help & Troubleshooting] sgt. slaughter:
One King hasn't said to NOT use SetCPU, he said that setting profiles in it might interfere with his kernels sometimes and cause a slight conflict. You still have to use setcpu for overclocking your phone.

Also this snipit is from the other well known Dev in his Rom thread.
[EVO 4G Q&A, Help & Troubleshooting] freeza:
+1 on all of those points.
[EVO 4G Q&A, Help & Troubleshooting] Psichi:
I just got my Evo not too long ago, so I am still trying to figure out all of the SetCPU/HAVS/OC/UV nonsense to try and optimize my battery.

I am trying to translate all of the information this thread provides (plus all linked threads and relevant searches) in to stupid (the only language I understand)

HAVS and SetCPU can be used together (in theory) because

HAVS only effects voltage

SetCPU only effects processor speed

Anecdotally HAVS is a little wonkier than a non-HAVS kernel (from a benchmarking perspective)

Anecdotally HAVS and SetCPU have not returned the expected increase in battery life (possibly due to redundancy)

All should be taken with a grain of salt as each evo is a little different

In theory, Kings or Netarchy + SetCPU should equal great battery life when on standby (and depending on OC options should help when in use as well)

---

Is that an adequate translation to stupid?
[EVO 4G Q&A, Help & Troubleshooting] ms79723:
Well without the kernels, setcpu can help a lot when on standby. But Havs is now being focused on when the screen is on, and undervolting to help save battery while you are currently using your phone. Check out Netarchy's universal kernels, the more aggressive undervolting ones and then go to one of king's kernels and you'll see a huge difference between battery drain while the phone is on from the kernels. The more aggressive undervolting kernels hold on to that battery like there's no tomorrow.
[Vibrant Q&A, Help & Troubleshooting] Dugorf:
Right now I am running stock vibrant software with the kingklick oc kernel, oncl, and stock 2.1 unlock screen.

My question is when froyo comes out (hopefully soon) will I be ok to install the ota update. Our do I need to uninstall the lag fix and other mods.

Thanks in advance.
[Vibrant Q&A, Help & Troubleshooting] SamVib:
You would have to change your kernel, and it's best if you do a wipe when installing any new rom, especially a new firmware.
[Vibrant Q&A, Help & Troubleshooting] richan90:
Does a froyo update not replace the kernel?
[Vibrant Q&A, Help & Troubleshooting] Dammit2Hell:
I had a similar question. Stock, unrooted Vibrant.... I got the JI5 update last week over Kies. Then I read that T-Mo had said not to install it. Are the odds good that I will have to jump through hoops to get the OTA when it finally comes?
[Vibrant Q&A, Help & Troubleshooting] masterotaku:
The odds are you will need to Odin back to JFD to get the update via OTA.

However the odds are also that you will find it packaged here ready to Odin before you get it via OTA. OTA's are pushed out in batches, not to every single phone at once, so it can takes days or weeks for an OTA to complete for every device.

If you're already here (and it appears you are), you will know what to do when everyone else here does.
[Vibrant Q&A, Help & Troubleshooting] ShinyBuddha:
I'm in the same spot as you. I've got a vanilla Vibe and jumped on that Kies update =)

It's a great update and fixed the GPS issue but regarding the OTA, I'm sure we'll find out what's going on once the T-Mobile updates start rolling. Fear not, you're in the right spot.
[Vibrant Q&A, Help & Troubleshooting] Dammit2Hell:
Thanks for the info.

I've been around a while just lurking & learning. I've been dieing to root this phone (first android) but didn't want to do it and turn around after and return to stock for 2.2. It does look like we will have a rom before it comes OTA anyway.
[Vibrant Q&A, Help & Troubleshooting] quest4fire:
I'm sure someone will take the Froyo OTA and make a Clockwork Flashable Rom if you dont want to ODIN. So hang tight and check back because believe me that as soon as the OTA goes out, it will be on a download mirror for all us in less than 24 hours.
[Vibrant Q&A, Help & Troubleshooting] kizer:
Its a game.

They come out with something

The Devs make it flashable

They leak something

The Devs make it flashable

.

.

.

.

.

.

They leak something

The Devs make it flashable. ;)
[Legend General] liltbrockie:
...what feature are you looking forward to the most?
[Legend General] TheGrammarFreak:
If anyone says Flash I'll hurt them :P

All the required drivers for 2.2, so that we can use 'em in CM
[Legend General] rajasyaitan:
Fla... Cancel that. JIT.
[Legend General] TheGrammarFreak:
You die. Lol. We have JIT in CM...

Swyped from my HTC Legend
[Legend General] PandaVoyageur:
270 degrees rotation (yes I'm left-handed) and app2sd (legend internal memory...)
[Legend General] kapu007:
Restoration of the SMS view as it was when I bought this phone. Makes me mad to browse to the bottom of the messages, when I receive SMS from someone I text a lot.
[Legend General] rajasyaitan:
Yea but somehow I feel that it is not working 100%. But seriously, flash. Its a neat feature that we're missing. Too bad eh?
[Legend General] TyCam:
Well, as I'm already using the Azure rom, I already have the 2 features I wanted most... putting apps on the sd card and the rotation, as already said. Except the rom allows a full 360 degree.

But the apps 2 sd was a big one since the Legend ran out of space after only a few app installs.
[Legend General] steelflame:
maybe a HD vid recording? possible?
[Legend General] TheGrammarFreak:
Ali Ba thinks so, but only with a bit of work. I'm sure HTC would do it if they could.

Swyped from my HTC Legend
[Legend General] kazzaz:
animated wallpapers
[Legend General] Lord-Vader:
JIT with Sense! my 2g ipod is smoother than 2.1
[Legend General] RayGarden:
Writing App installs to SD-card + New Sense utility
[Legend General] gallery:
Live wallpaper, application sharing, torch light, fmradio widget, and app2sd
[Legend General] randy_khoo:
erm... for someone to hack it so that it runs faster... and post the ROM here. LOL
[Legend General] janarp:
Good one...=)
[Legend General] virani_joush:
App2sd is a must feature and live wallpapers, faster processing, wifi hot spot capability, full flash support, lesser battery consumption.
[Legend General] janarp:
Anyway what's the point of this thread. It does not bring FROYO closer to us.
[Legend General] the_canuck:
so sorry, your highness. next time we'll ask you before we start talking about something. :rolleyes:
[Legend General] TheGrammarFreak:
Lol.

Swyped from my HTC Legend
[Legend General] liltbrockie:
lol... do you only do things that bring Froyo closer?
[Legend General] janarp:
=)=) im just asked... im waiting too froyo... really want it like u guys...

and im not who says what to talk...=)

and i cant do anything to bring closer... if i can then we allready have froyo...=)=)
[Touch Pro2, Tilt 2 Windows Mobile General] potpotskii:
Hi! Can anybody tell me how to adjust the size of the task bar and menu bar on my TP2 (WM 6.5 stock rom from Sprint)? I want to maximize the Rhodium's big screen when I use Word Mobile. The task bar and bottom bar makes the screen look cramped when I write emails in landscape mode. I've been looking for a registry tweak or an application which could do this, but I have'nt succeeded yet. I have tried Advance Configuration Tool but it did not work. It would be nice if there's a taskbar and menubar that would not occupy that much space, probably just an icon on four corners for some functions like the Menu, Exit, etc. Or a minimizable taskbar.. I'll appreciate it if someone could give me links.. Thanks for reading this!
[Touch Pro2, Tilt 2 Windows Mobile General] potpotskii:
Ah, so this can't be done? Too bad.. Is there any option? Ive tried transparent taskbars but it's only transparent on the theme. Thanks for the quick (and concise answer)!
[Wildfire Android Development] Akerhage:
Ok after many many hours of frustration I finally got the phoone rooted, have the superuserapp so it must have been done right!?

Had Windows 7 64bit version, so this is how I did for all others trying.

The ADB changes to HTC something, dont know if it supposed to be like that? Havent really checked if the ADB is working. Is that neccessary if I want to install WildPuzzleRom? Or is Busybox an alternative then?

OKAY after explaining how I did, my question then:

* Is it okay now to try installing WildPuzzleRom

* Do I have to do a nandroid backup BEFORE that?

* Do I need to make an goldcard for this?

* Do I need a USB card-reader-adapter for this? (If I must connect the SD to the computer for putting files on to it o format it or something?)

* Is 2gb enough for that? Considering that I want have mp3s, movies etc on the card, just for flashing roms and downloading fun apps.