Originally Posted by martie1 (Post 596629)

can someone explain me how to flash my device with 900 mhz? i already have downloaded the kernel voor 900 mhz, but how to install it??

thnx

Originally Posted by javispedro (Post 596628)

The crew who designed the hardware, yes...

Originally Posted by javispedro (Post 596628)

How many times do I have to tell you that this is not the case?

Originally Posted by LondonBenji (Post 596648)

If I am not on charge then doing a "cat /proc/cpuinfo | grep MIPS" repeatedly, shows the CPU scaling constantly between 250/125 and 600/700/800/900 depending on the kernal image used.

Whilst on charge the value stays locked at 600/700/800/900 depending on the kernal image used.

My assumptions then are that the BogoMIPS are a roughly direct representation of MHz and that what this value represents is in fact the current state of the proc.

Please correct me where I am wrong.

Originally Posted by hollow (Post 596649)

why will the life time of the processor be halved . as long as its stable @900mhz its not like its running at 100% all day long

Originally Posted by LondonBenji (Post 596648)

You mean the hardware around the TI chip... they didn't design the TI chip, they just implemented it.

Originally Posted by LondonBenji (Post 596648)

If I am not on charge then doing a "cat /proc/cpuinfo | grep MIPS" repeatedly, shows the CPU scaling constantly between 250/125 and 600/700/800/900 depending on the kernal image used

Originally Posted by filologen (Post 596431)

It seems that most people after flashing one of the overclocked kernels onto the device gets "Version: Unknown" listed in "About the product". This is however not the case for me (I use the 900ghz image), and I wonder if this could be due to me using fiasco-flasher on the device instead of the Flasher-3.5.

Not important, but just a little bit interesting.

Originally Posted by shady (Post 596691)

i bricked my device trynna figure this out.

Originally Posted by javispedro (Post 596676)

I was talking about the N900. And the people who wrote the datasheet did design and implement it.

Originally Posted by javispedro (Post 596676)

MIPS is a lie. Also, when you tap the touchscreen or the keyboard the device bumps the cpu frequency to the maximum temporarily. This explains why what you're doing is hardly a test.

Use the above or even watch cat /sys/devices/system/cpu/cpu0/cpufreq/stats/scaling_cur_freq .

Originally Posted by thearcane (Post 596689)

I ran Conky on my stock N900, watched it idle at 250MHz, plugged in the cable, and after it jumped up to 600MHz until I dismissed the connection choice menu it settled on 500MHz. After I disconnected the cable it dropped right back down to 250MHz.

This seems like it could be troublesome with OC, since I usually tend to charge my phone overnight, probably for longer than it needs.

Originally Posted by tangs (Post 596708)

Someone tried Enna after flashing to 900mhz ? should be interesting to know if this app is really running faster.

What should be the "fastest" 900mhz with stock DSP or 900mhz with 500DSP ?

Originally Posted by jimmyb5374 (Post 596742)

I am running the 800mhz flash , and using enna a little just to try it out, apart from 1 sec of "greenscreen" when loading a video file its running smooth for me so far

hope that helps a bit

James

Originally Posted by Dirkjl (Post 596675)

Suitable USB Device not found, waiting
help:)
im using this command:
flasher-3.5.exe -k zImage-900mhz -f -R

Originally Posted by Dirkjl (Post 596675)

Anyone have an idea why flasher is saying this to me when i want to flash the kernel:

Suitable USB Device not found, waiting

help:)

im using this command:

flasher-3.5.exe -k zImage-900mhz -f -R

Originally Posted by evilJazz (Post 596776)

Alright, I overclocked my N900 to 1700 MHz.
Running stable for almost 21 hours now.
http://www.flickr.com/photos/1018569...88129/sizes/l/

Sure, it is bulky with the huge heat sink on the backside and you might need a nuclear reactor to power this thing on a longer trip, but at least you are on the cutting edge, right?

Oh, well, never mind. ;)

Originally Posted by evilJazz (Post 596776)

Alright, I overclocked my N900 to 1700 MHz.
Running stable for almost 21 hours now.
http://www.flickr.com/photos/1018569...88129/sizes/l/

Sure, it is bulky with the huge heat sink on the backside and you might need a nuclear reactor to power this thing on a longer trip, but at least you are on the cutting edge, right?

Oh, well, never mind. ;)

Originally Posted by evilJazz (Post 596776)

Alright, I overclocked my N900 to 1700 MHz.
Running stable for almost 21 hours now.
http://www.flickr.com/photos/1018569...88129/sizes/l/

Sure, it is bulky with the huge heat sink on the backside and you might need a nuclear reactor to power this thing on a longer trip, but at least you are on the cutting edge, right?

Oh, well, never mind. ;)

Originally Posted by Ronaldo (Post 596773)

use this command (no .exe)

flasher-3.5 -k zImage-900mhz -f -R

Originally Posted by DarkPand0r (Post 596785)

Hey Guys,

Currently running the 900mhz kernel with the stock DSP.
Sat listening to music with FM transmitter for around 1.5 hours with absolutely no effect, ran really well.

One question I have is, Would their be a big difference between the 900mhz/stock and 900mhz/500 for example?

Originally Posted by val580 (Post 596820)

found this about droid :


Fried GPS chip from overclocking?
Hi all,

I'm having trouble with my GPS getting a lock. Sorry for the long post, but I wanted to be thorough in my description and "help you help me"

Background
About a month ago, I rooted my Droid, threw the 0.8ghz kernal on it from "Root Your Droid" website, and overclocked it to 0.8ghz using SetCPU. It worked great for a few days, but the back side near the camera would always get warm to the touch if I did anything processor-intensive on the phone.

One day, I docked the phone to the Motorola car dock and used the GPS navigation for a road trip. The car dock was suctioned on the driver's side of the windshield, and since it was a sunny day that day, it had full exposure to sunlight. I also had a car charger hooked up to keep it juiced up.

30 minutes into the drive, the navigation went all crazy. It lost GPS signal, then a few seconds later, it tried to hone in my position to some random location, drifting southeast every second, even if the car wasn't moving. I tried to zoom out, but it kept scrolling the map screen to my "new position". I quitted the Navigation and checked on Google Maps: same thing.

I also noticed my phone was really, really hot. Not painful just yet, but getting there. I shut the phone down, pulled the battery, and let it cool down for 30 minutes or so. When I turned it back on, the GPS was working again, and so was navigation. That whole ordeal freaked me out, so I used my TomTom for the rest of the trip instead.

My GPS continued to function ok for a few days, but I didn't use it too much after that incident. Several days later though, my GPS failed to lock onto my location in Google maps again, and it did that messed up scrolling/false locking thing. At the time, I ignored it, and several days later, it was working fine again. This repeated itself continuously, although nowadays it wouldn't do the scrolling/false locking as much; it just wouldn't acquire a lock.

The Problem and Current State
I have Pete's BB v0.9 ESE53 Android 2.1 overclocked to 800 mhz max, 400 mhz min. Everything on the phone is working fine EXCEPT for the GPS. The GPS fails to lock onto my position, although the cell tower AGPS always gives me a good regional approximation of my location in Google maps and in any apps that uses general geolocation.

The real kicker is that GPS fails like 80% of the time, regardless if the phone is warm to the touch or not. In other words, there's a small chance that for any given day, the GPS would work for some time for that day. When it works, it works great. When it doesn't, it won't lock onto my position and occasionally gives me false positionings that persistently update in one direction or another (as if I'm always movving, even though I'm not).

I'm afraid my overclocking may have overheated the GPS chip and fried it, even though it was at a speed that's informally accepted as (relatively) "safe". Maybe it was a combination of overclocking, being in the sun, and hot battery from being plugged into the car charger that fried it?

Attempted Remedies
Whenever my GPS didn't lock, I did one or more of the following (not necessarily in this order) to no avail:

1. Factory wiped and restored to virgin Droid ROM, Android 2.0.1
2. Killed all GPS/geolocation-using apps
3. Disabled/enabled GPS/geolocation/wireless networks lock settings
4. Shutdown, pulled battery, left off for 30+ minutes, turned back on
5. Left Google maps or Navigation app on for 60+ minutes to try to acquire position
6. Downloaded GPS Status and GPS Test apps. Both would show 2 to 6 satellites, but for the majority would not acquire signal. For when they DO acquire signal, 1 of 2 things occur:
* It's a good acquisition and it's one of the rare times the GPS works as intended.
* It's a false position (as described above), and I'm moving 20 to 40 MPH in some odd direction at an altitude of -5km
7. Dialed *228 and hit "1" to reprogram my phone, followed by a reboot.
8. Spun it several times on all 3 of its axes.
9. Consulted the stars, sacrificed a lamb, and ritualistically danced around the Droid.



Any help would be greatly appreciated! I've scoured the interwebs and found nothing similar to my case (especially with the perpetual false positioning/movement).


http://forum.androidcentral.com/moto...rclocking.html

Originally Posted by Stonik (Post 596614)

So what happens if after a few months some of the overclocked devices just die? We all know how hungry the gizmo sites are for big headlines (and clicks), even if there were just a dozen bricked N900s running @1050 MHz. So would it go like:
1) Intel and AMD and the mainboard manufacturers, where the blue smoke is always the user's fault - not hurting the manufacturer's brand.
2) Shocking news of burning Nokia smartphones, which is way too easy to overclock. Most people would probably read just the headlines, and that wouldn't be good for N900.

In my personal opinion, Nokia should actually be there first before anything happens, and put up an overclocking party. They should invite a few famous overclocking teams around the globe with 100 N900s to grill. That's when they could also tell the public audience not to overclock their devices, as it would possibly damage their smartphones. This would - however - promote N900 as the ultimate powertoy with no limits. It certainly would be something that no other phone manufacturer has ever done.

Originally Posted by egoshin (Post 596819)

Download to N900 and use this command on it:

flasher -k zImage-900mhz -f -R

No PC is required.

Originally Posted by DarkPand0r (Post 596785)

Hey Guys,

Currently running the 900mhz kernel with the stock DSP.
Sat listening to music with FM transmitter for around 1.5 hours with absolutely no effect, ran really well.

One question I have is, Would their be a big difference between the 900mhz/stock and 900mhz/500 for example?