Quote:
Originally Posted by Hugo381
Well like I said, I even removed the whole overclock command in the StartUp.txt so I should be running at stock speeds and I get the same problem whether its overclocked or not.
Should I leave the overclock command and just assign it the stock clock value instead of removing the whole command? It doesnt memorize the previous clock speeds when you reset the phone right? Its gotta be defined by the StartUp.txt at boot in order to apply the overclock?
At the moment I am reformatting the Storage Card in Fat32 and doing a clean install from the .rar file and see if I see any difference. I already went through this process 2 days ago but it didnt fix it when using .cab file again.
|
Yeah, so that's what I get for trying to read and post on my phone. Pulled out the laptop because I couldn't change my post :P
About the startup.txt, as far as I understand, most linux distro's save information about the last startup; however, it is for diagnostic purposes, not for restoring settings. Unfortunately, I have not found whether Android does this or not, or if loading the linux kernel using Haret makes a difference. You could always try forcing the default frequency in the startup.txt so Haret loads it properly.
For formatting the card really shouldn't matter, and I'm not sure this is helping fix people's issues. I know a fragmented card could lead to poor performance, and I guess you could have bad data next to good data. But it doesn't make a lot of sense.