[ROM][GEN2]CyanogenMod 7 (Android 2.3.7)

[Guest simonckenyon]

Personally I think those opposed to overclocking are as crazy for not wanting free performance as you think we are for overclocking. You guys realise it's not 10 years ago right? Modern computing hardware overclocks itself - it's that popular a practice. Intels latest CPU's do and my new graphics card as a tick box to overclock itself.

i am not opposed to overclocking at all

i am opposed to overclocking and reporting crashes

especially while we are trying to resolve some bugs

once these are sorted overclock away to your hearts content

TFT/N36/boot.img98d76/NOT OVERCLOCKING

[Guest chimas]

i am not opposed to overclocking at all

i am opposed to overclocking and reporting crashes

especially while we are trying to resolve some bugs

once these are sorted overclock away to your hearts content

TFT/N36/boot.img98d76/NOT OVERCLOCKING

I Believe this dude/dudette talks sense. Dont overclock and complain.

[Guest targetbsp]

i am not opposed to overclocking at all

i am opposed to overclocking and reporting crashes

especially while we are trying to resolve some bugs

once these are sorted overclock away to your hearts content

TFT/N36/boot.img98d76/NOT OVERCLOCKING

The crashes in N36 were caused by bugs in the overclocking feature itself! Not because people were overclocking unstably high. The developers fixed it in N37. That would have been tricky if none of us overclocked to have alerted them to the problem... :)

On another note... why do people keep being surprised the GPS crash isn't fixed? It sure would be nice if it was. I don't use the GPS but still in my view it's the most important outstanding issue. I just don't get why people expect it to be fixed every night when it's not been noted as such in either the bug tracker or Blade changelog? :S

Edited April 8, 2011 by targetbsp

[Guest jayhix]

The crashes in N36 were caused by bugs in the overclocking feature itself! Not because people were overclocking unstably high. The developers fixed it in N37. That would have been tricky if none of us overclocked to have alerted them to the problem... :)

On another note... why do people keep being surprised the GPS crash isn't fixed? It sure would be nice if it was. I don't use the GPS but still in my view it's the most important outstanding issue. I just don't get why people expect it to be fixed every night when it's not been noted as such in either the bug tracker or Blade changelog? :S

when did this gps crash bug first occur? im still running RC4 and today used navigation for a 4 hour drive with gps constantly on the whole time, and at no point has my phone rebooted

[Guest ThrashMan]

The crashes in N36 were caused by bugs in the overclocking feature itself! Not because people were overclocking unstably high. The developers fixed it in N37. That would have been tricky if none of us overclocked to have alerted them to the problem... :)

On another note... why do people keep being surprised the GPS crash isn't fixed? It sure would be nice if it was. I don't use the GPS but still in my view it's the most important outstanding issue. I just don't get why people expect it to be fixed every night when it's not been noted as such in either the bug tracker or Blade changelog? :S

Would be even easier if the option to overclock wasn't there. REALLY pointless on a phone.

[Guest xzyk]

when did this gps crash bug first occur? im still running RC4 and today used navigation for a 4 hour drive with gps constantly on the whole time, and at no point has my phone rebooted

Either reading this long thread (where various posts refer to this problem) or go to the CyanogenMod Issue Tracker and click on issue 3277 and you'll see it is indeed a problem. It seems mostly to affect TFT owners and possibly tied to bad battery temp sensor reporting and/or detection.

I have had this problem, and am able to reproduce it at will, with a full wipe, no google apps loaded, no sign-on to google and only GPtest app loaded (to be able to test it) AND no overclocking. I don't know how much more vanilla i can make the rom install than that and can confirm it is very much an annoying problem and renders the phone unable to use GPS, unless ofcourse you're willing to put up with the reboots.

Those of you who don't get the 'problem', great, but there are quite a few others who do have it.

BTW, if you read the problem carefully you'll see it doesn't manifest itself during the use of GPS, it happens after you've exited the use of the GPS app, and left the phone to go into sleep mode for an undetermined time, either it reboots by itself or reboots next time you try to use it.

Edited April 8, 2011 by xzyk

[Guest KelticDaz]

Either reading this long thread (where various posts refer to this problem) or go to the CyanogenMod Issue Tracker and click on issue 3277 and you'll see it is indeed a problem. It seems mostly to affect TFT owners and possibly tied to bad battery temp sensor reporting and/or detection.

I have had this problem, and am able to reproduce it at will, with a full wipe, no google apps loaded, no sign-on to google and only GPtest app loaded (to be able to test it) AND no overclocking. I don't know how much more vanilla i can make the rom install than that and can confirm it is very much an annoying problem and renders the phone unable to use GPS, unless ofcourse you're willing to put up with the reboots.

Those of you who don't get the 'problem', great, but there are quite a few others who do have it.

BTW, if you read the problem carefully you'll see it doesn't manifest itself during the use of GPS, it happens after you've exited the use of the GPS app, and left the phone to go into sleep mode for an undetermined time, either it reboots by itself or reboots next time you try to use it.

Absolutely spot on. Mine's a tft screen for the record.

[Guest Ron=)]

thank you very much! :), but i am new to this so? go into clock work? and press install zip from sd card. then install the one you just gave me? and then complete the process that should have worked originaly yes?

That's exactly right!

Don't forget to make a Clockwork Backup before you flash anything though!

Edited April 9, 2011 by Ron=)

[Guest wbaw]

The crashes in N36 were caused by bugs in the overclocking feature itself! Not because people were overclocking unstably high. The developers fixed it in N37. That would have been tricky if none of us overclocked to have alerted them to the problem... :)

On another note... why do people keep being surprised the GPS crash isn't fixed? It sure would be nice if it was. I don't use the GPS but still in my view it's the most important outstanding issue. I just don't get why people expect it to be fixed every night when it's not been noted as such in either the bug tracker or Blade changelog? :S

The gps shutdown issue seems to be fixed now, Tom G has produced a kernel which fixes it. It was caused by false high battery temperature readings during sleep causing the phone to shut down, this new experimental kernel ignores the false high readings for a while until they've settled down to something more reasonable.

http://code.google.com/p/cyanogenmod/issue...ail?id=3277#c81

If anybody who was having the issue can try the new kernel out & post logs, then it should be included in cm7.

[Guest Michealtbh]

Would be even easier if the option to overclock wasn't there. REALLY pointless on a phone.

Its not pointless. It makes a noticeable difference in speed and performance. If its possible without compromising stability then I dont see the problem

[Guest ambak]

The gps shutdown issue seems to be fixed now, Tom G has produced a kernel which fixes it. It was caused by false high battery temperature readings during sleep causing the phone to shut down, this new experimental kernel ignores the false high readings for a while until they've settled down to something more reasonable.

http://code.google.com/p/cyanogenmod/issue...ail?id=3277#c81

If anybody who was having the issue can try the new kernel out & post logs, then it should be included in cm7.

+1 .......thanks again guys, good work

[Guest samjam]

The gps shutdown issue seems to be fixed now, Tom G has produced a kernel which fixes it. It was caused by false high battery temperature readings during sleep causing the phone to shut down, this new experimental kernel ignores the false high readings for a while until they've settled down to something more reasonable.

http://code.google.com/p/cyanogenmod/issue...ail?id=3277#c81

If anybody who was having the issue can try the new kernel out & post logs, then it should be included in cm7.

I downloaded http://205.185.123.36/boot.img-slarti

Does anyone know what I should do with it?

Sam

[Guest The Soup Thief]

i can haz fm radioz ? ! ? :) :) :)

btw, targetbsp,

The developers fixed it in N37. That would have been tricky if none of us overclocked to have alerted them to the problem...

the guys (including Jacob and TomG) on irc were aware days ago that overclocking was broken on n36 - people posting and reposting here about their phones crashing (with or without mentioning whether they were overclocking) wasn't helping define the problem, it was just causing themselves hassle and putting others off a ROM which actually still needed other features tested. Y'know the "Here be dragons..." warning after CM Settings>Performance? It explicitly states that you should approach with caution and certainly post bug reports etc re experimental builds after changing the performance settings

Anyway, we're not going to agree on this one, i think, so maybe best just be thankful that it's been resolved in n37

[Guest Michealtbh]

Has anyone seen this? I might try it later when I have time, hopefully it makes our feeble cameras a little bit better

[Guest JimJam707]

Has anyone seen this? I might try it later when I have time, hopefully it makes our feeble cameras a little bit better

Nah, that's for the Nexus One only.

[Guest Michealtbh]

Should work with any phone running cm7, I dont see why it wouldnt

*Edit works on HTC Wildfire too. They both have 5mp cameras though. I'll try later anyway.

Edited April 9, 2011 by Michealtbh

[Guest The Soup Thief]

I downloaded http://205.185.123.36/boot.img-slarti

Does anyone know what I should do with it?

Sam

If I remember right from the last time I flashed a new boot image, this should work

1. rename boot.img-slarti to boot.img
   
2. within the n37 zip, swap this boot.img for the boot.img that's already in there
   
3. flash the whole (now modded) n37 again
   

Alternatively I think you can slap it into an existing install, but this is how I did it - might be an idea to nandroid first, of course Edited April 9, 2011 by The Soup Thief

[Guest Michealtbh]

Just noticed the Tablet Tweaks in Nightly 37, we can now have the status bar at the bottom, pretty cool :)

[Guest Len Ash]

Just noticed the Tablet Tweaks in Nightly 37, we can now have the status bar at the bottom, pretty cool :)

The alternative boot.ing appears to work OK (within the realms of development anyway)

Still no effing WiFi reconnect though... some really odd/old driver stuff in there.

Beginning to resemble a collection of fudges now

[Guest Roku]

Updated to N37 and now phone can sleep? Battery didn't drop a single% at night.

[Guest The Soup Thief]

Just noticed the Tablet Tweaks in Nightly 37, we can now have the status bar at the bottom, pretty cool :)

neat!

btw - didn't have the gps problem, but I've put the new boot.img on to see if it melts my phone

Hasn't yet

Edited April 9, 2011 by The Soup Thief

[Guest pellonet]

If I remember right from the last time I flashed a new boot image, this should work

1. rename boot.img-slarti to boot.img
   
2. within the n37 zip, swap this boot.img for the boot.img that's already in there
   
3. flash the whole (now modded) n37 again
   

Alternatively I think you can slap it into an existing install, but this is how I did it - might be an idea to nandroid first, of course

Comment 55 by project member [email protected]

Yes, flash with fastboot, but to the boot partition.

fastboot flash boot <imgfile>

http://205.185.123.36/boot.img-slarti

Edited April 9, 2011 by pellonet

[Guest k0nrad]

Something's weird either with my phone or with the N37.

I updated RC4 to N37 straight (cache wipe only) to find two apps missing (Transportoid and TweetDeck) and impossible to reinstall (either from Market or backup), saying something about 'unavailable libraries' (rough translation, didn't switch the locale to check).

So I thought fixing permissions via ROM Manager may help - only to find SU privileges buggered up - no go for ROM Manager for some reason, although it was properly ticked in ChainDD's SuperUser.

At that point I went to restore my RC4 from CWM. Unfortunately the backup was buggered up as well (too little space on the SD I suppose).

So I wiped everything and did a clean install of N37 + gapps. Guess what - no gapps. After numerous reflashing, wiping, redownloading gapps from different mirrors, etc - nothing. No way to access Market or anything.

I did a clean RC4 install and gapps flashed OK - it's performing Restore from my google account now (taking painfully long on WiFi though, and not showing any progress on the bar :/).

I guess I'll stay with RC4 till the soon-to-arrive Stable release, as it was reliable enough for my taste so far.

[Guest Roku]

I came from N31. Pulled titanium backup apk to SD-card. Installed N37 from ROM Manager, Wiped data and cache. Installed titanium backup apk from SD-card and restored apps and accounts. So far so good. Even Angry Birds are working from backup what they didn't do in N31. Don't know why.

[Guest dibbles]

I have flashed that boot.img which Tom supplied by having to edit the latest nightly, n37. For some reason I wasn't able to use the fastboot flash process as it kept producing error..?

I have noted that Tom has asked for "dmesg logs".

Is it possible to record those to the data folder whilst testing out the GPS and if so how...?

Could I use the terminal emulator as SU and then type...

dmesg > /data/dmseg.log

would that work...?

Different from the above...

Has anyone else found that build n37 is still very sensitive to overclocking...?

Whilst I would not overclock whilst testing the GPS function I have found that any changes to the overclocking speed will cause the phone to shut down. My phone has always been very very stable at 710mhz and so I ran it at 691. Trying at 652 it will cause it to switch off with n37.

Using SS RLS4b and there is no issue with running at a higher speed nor is there with n35.

Or could the above overclocking issues be due to the test img from Tom not containing the latest fixes in n37...?

Edited April 9, 2011 by dibbles