Notices

Originally Posted by M A S T E R

I also had this problem only after i updated for some reason. I havent fixed it yet because didn't see this thread until now! You guys are awesome, However before i go about doing this All i have to do is go to terminal, be in root and type what was posted earlier?

If so does it matter if i already have Titans Ideal/LV on? would that be a bad thing to do? should i go back to stock Speed before i do this transition? And/Or is it any different for anyone for any specific reason? Im ready to get my Joikuspot fixed. I thought i lost my moneys worth, so any help would be greatly appreciated by you guys.

Thanks in advanced.

-MASTER

Originally Posted by tzsm98

I am usually overclocked to 805MHz, I did not 'declock' before I entered the first line and everything worked when I ran JoikuSpot. I've had no instability (on the N900, my personal life is another story!) Failure to enter the second line one time did not seem to cause any issues. I believe this is a worry free sort of thing that will not interfer with other functions. That has been my experience.

I also tried to enter the lines of code using QueenBee widgets but that didn't have the desired result. Too bad, that would save a lot of code entering over the long haul.

Originally Posted by RockCreek1

Hi
I have a similar problem. Joikuspot worked fine prior to the recent n900 update. It also seemed to work fine, though took a few tries to connect, during the interlude between my downloading the recent N900 update and the most recent Joiku update. I am just a regular N900 user and I do not want to mess around with root, etc. Nor do I think I should be required to do so for something I paid for. So I wonder if there is another way to deal with this problem. My compter indicates that I am connected to Joiku with an excellent signal. Thanks in advance for your help.

Originally Posted by tzsm98

I've suggested to JoikuShop that they add a subroutine that detects which kernel is active and to have the code lines as part of the startup-shut down routines of the application. I also tried using QueenBee to handle the code but that didn't work.

Until JoikuShop takes my advice messing around in root to the extent this fix requires means having to be extra careful about typing and reviewing what you've typed before hitting the 'enter' key. You:

• open xterm
• type sudo gainroot 'enter'
• type modprobe JoikuSpot_Bouncer 'enter'
• close x-term

Case sensitive so be sure to watch for the capital letters. After you are done with JS:

• open xterm
• type sudo gainroot 'enter'
• type modprobe -r JoikuSpot_Bouncer 'enter'
• close x-term

Practice typing it in a note program or Conboy to build your confidence. I wish I could cut and paste from my note program to x-term but that doesn't seem to be possible. I'm kinda, sorta fearless when it comes to entering short pieces of code. The longer scripts are what scare me off. I'm too awful of a typist.

Originally Posted by M A S T E R

Wait a sec then. You are telling me that everytime i am OC'd i have to type the first batch of lines to use JSpot and then after i am done i have to essentially put it back? is that what the code is pretty much doing? If so what happens if i do not put it back? will something happen if i turn of my N900? or if i go back to stock kernel?

Is this mainly for the kernel then Because if i always use the same kernel will have to put Jspot modprobe back? I am clueless in this area BTW >.<

-MASTER

Originally Posted by Gusse

If you follow workaround guide from post #8 then you don't need to do any additional steps before or after using JoikuSpot. Working with latest Titan kernel (2.6.28.10power37).