[ROM] CM6-clean for development / testing

[Guest dr.flo]

This rom seems to have the same problems Tom's did back in the beginning, not responding to hardware buttons when the screen is off.

Could you describe this a bit more? What hardware buttons (red/green/menu/back or vol+/-) and how long should the screen be off to triggger the problem? What behavior is expected and what behavior is seen?

I just ask because I've used the 20120202 version for same days now and I didn't notice anything. But I never tried e.g. vol +/- when screen is off. One of red/green/etc turns screen on and shows the lock screen for me.

(-> maybe you can take "newer" keymap from there instead of toms rom)

Would it be OK if I include the link to your new gapps (or maybe a mod of it) in the 1st post instead of the market-only-gapps?

Edited February 8, 2012 by dr.flo

[Guest hzf]

This fixes the GMail problem for me on rom version 20120206 (20120202 untested, might also work there)

Replace libwebcore.so with this one (origin: update-cm-6.1.0-DS-signed.zip, official CM6.1 release for HTC dream). This effectively reverts just libwebcore to the official CM6.1 release version.

libwebcore from TomG's rom cannot be used on cm6-clean because lib dependencies differ (due to eclair camera hack in TomG's version).

version 20120202(using this for a week now) tested, gmail working fine

thanks for figuring this out!

hw buttons also working for me,

Edited February 8, 2012 by hzf

[Guest dr.flo]

version 20120202(using this for a week now) tested, gmail working fine

thanks for figuring this out!

hw buttons also working for me,

very useful feedback, thanks!

I've just looked at qwerty.kl - it is identical in both cm6-clean versions. So I don't understand why hw buttons would work for you but not for twrock.

@twrock please explain a bit more what the problem is about. I found this on the net regarding keymap

• WAKE: When this key is pressed while the device is asleep, the device will wake up and the ky event gets sent to the app.
• WAKE_DROPPED: When this key is pressed while the device is asleep, the device will wake up and the key event does not get sent to the app.

All that differs in your version of keymap is that some buttons have WAKE_DROPPED removed. These keys should wake the device but the event should be ignored, when WAKE_DROPPED is set. What do you mean exactly by "not responding to hardware buttons"? Device acts like it is dead, or device wakes but ignores key? The latter would be intended behavior.

[Guest dr.flo]

camera button not taking pictures in original camera app may be related to autofocus settings... (try another focus option then camera button will work).

This may in turn may be related to keymap - I remember some camera focus fix that simply replaced keymap, so maybe keymap holds some options for the camera button that need to be adjusted..

edit:

key 249 FOCUS

I will prepare updated rom downloads that incorporate all previous fixes and post them on the main page later today...

Edited February 8, 2012 by dr.flo

[Guest hzf]

strange thing happened:

just took a picture(pudding camera), plug in usb, opening picture on computer, unmount from computer - usb storage turn off, and wanted to take another picture and camera FC ( stock app too).

update after reboot

EDIT:

it was caused by starting camera before SD fully mounted - reboot solves

it seems that i need an 'idiot proof' ROM :)

Edited February 8, 2012 by hzf

[Guest D-D-]

very useful feedback, thanks!

I've just looked at qwerty.kl - it is identical in both cm6-clean versions. So I don't understand why hw buttons would work for you but not for twrock.

@twrock please explain a bit more what the problem is about. I found this on the net regarding keymap

• WAKE: When this key is pressed while the device is asleep, the device will wake up and the ky event gets sent to the app.
• WAKE_DROPPED: When this key is pressed while the device is asleep, the device will wake up and the key event does not get sent to the app.

All that differs in your version of keymap is that some buttons have WAKE_DROPPED removed. These keys should wake the device but the event should be ignored, when WAKE_DROPPED is set. What do you mean exactly by "not responding to hardware buttons"? Device acts like it is dead, or device wakes but ignores key? The latter would be intended behavior.

It happened to me on different roms. Sometimes the phone hangs and even if somebody is calling you, the screen just won't turn on.

I think that's the problem he is experiencing.

[Guest twrock]

Sorry, I wasn't clear. There is no "bug" with the hardware buttons. There are settings for a few of the butttons that are different in the qwerty.kl file I uploaded. There is one addition as well: key 249 FOCUS (And I can't remember what that does, but my camera button take pictures.)

As for the rest of the buttons, when the screen is off, certain button presses are either supposed to be or not supposed to be passed through to the OS. IIRC, the main buttons that this uploaded qwerty.kl changes from what was happening are:

volume up (short press raises volume; long press skips to next track)

volume down (short press lowers volume; long press skips to previous track)

green call (will not wake the device; this keeps the device from turning on every time you bump that button while it is in your pocket)

trackball press (will not wake the device; but this can be toggled back on in CM settings; this keeps the device from turning on every time you bump that button while it is in your pocket)

red endcall (will not wake device; this keeps the device from turning on every time you bump that button while it is in your pocket)

Having the screen turning on every time you accidentally press those three raised buttons can be a real battery killer, because you usually don't know it is happening. The volume up and down buttons are supposed to work while the screen is off, but are not supposed to turn the screen on. This qwerty.kl solves all of those issues. It was something that we all worked out together "back in the day" when we first started fixing Tom's rom. It needs to be fixed in this rom as well. (But I can't be sure about key 249, because I can't remember why we added that one.)

Hope that helps.

Edited February 8, 2012 by twrock

[Guest dr.flo]

Sorry, I wasn't clear. There is no "bug" with the hardware buttons. There are settings for a few of the butttons that are different in the qwerty.kl file I uploaded. There is one addition as well: key 249 FOCUS (And I can't remember what that does, but my camera button take pictures.)

...

OK, now I understand! This is indeed better than the default config. I just didn't get the idea before.

Btw, the FOCUS key is what makes your camera button take pictures.

I will include the updated keymap in the next rom upload.

[Guest dr.flo]

I will include the updated keymap in the next rom upload.

Updated 1st post with bugfixed version of both cm6 builds. Those that already applied fixes as posted in this thread do not need to update. The freshly uploaded roms just have the fixes included, nothing else changed.

[Guest twrock]

Updated 1st post with bugfixed version of both cm6 builds. Those that already applied fixes as posted in this thread do not need to update. The freshly uploaded roms just have the fixes included, nothing else changed.

Thanks. And, yes, you definitely can link to anything I upload in any way you find useful. I hope that gapps works well for others. I haven't tested it for a very long period of time, but so far so good.

[Guest pier11]

the file in cm6 & cm7 is basically what was in stock eclair rom for pulse.

likely cm7 build also need at least focus button as I've already heard complains that hardware camera button does not take pictures (though it does start camera app fine).

[Guest dr.flo]

the file in cm6 & cm7 is basically what was in stock eclair rom for pulse.

likely cm7 build also need at least focus button as I've already heard complains that hardware camera button does not take pictures (though it does start camera app fine).

Then we would just need to add the "FOCUS" line to the keymap.

The camera button seems to be tri state (unpressed, half pressed == focus, and pressed == camera button). This explains that depending on autofocus mode, camera button is ignored by camera app. Thats because in certain modes, the app wants 1st to get FOCUS then to get CAMERA. Therefore FOCUS must be contained in keymap.

[Guest desalesouche]

the file in cm6 & cm7 is basically what was in stock eclair rom for pulse.

likely cm7 build also need at least focus button as I've already heard complains that hardware camera button does not take pictures (though it does start camera app fine).

i changed the key map as suggered in cm72...it is working...

[Guest twrock]

24 hour report.

After replacing the keymap, updating or replacing a few system apps, and reinstalling with DT Apps2SD and gapps, I have had an extremely stable phone for the past 24 hours. No FC's even with heavy use. 3G, Bluetooth (including BT keyboard), Wifi, camera, gapps and everything else I used have all worked without any problems. I have not done anything with GPS, but dr.flo has already said that bug is still in the rom. Wow, this is feeling like a very nice rom! Thanks for making it available.

No report on battery life yet. I haven't been following my usual usage pattern, so it isn't fair to comment on that yet.

Incidentally, I modfied the build.prop slightly to turn off compcache and set vmsize to 24 (jit was already off). I also am running cachesd, swappy30, and lowmem-moderate, all of which are the usual way I run things on my phone.

dr.flo, I am curious why you chose to remove your GPS patch. Was it really that bad, or just less than perfect? Have you got other ideas for how to fix that?

[Guest hzf]

I've checked the forum with Browser and the timestamps are in GMT but I am GMT+1, strange.

And I absolutely agree with twrock this is a really nice rom, no problems with it - except the ones I caused :)

[Guest dr.flo]

I'm glad to hear the rom works stable for you! It also does for me (I'm still using the first version).

dr.flo, I am curious why you chose to remove your GPS patch. Was it really that bad, or just less than perfect? Have you got other ideas for how to fix that?

I was not really happy with it. Although the GPS icon goes away, it only does because I send an extra notification from within the java framework. Normally the GPS driver itself should be fixed.

I thought that I would have time to look at the driver and fix the issue there. Thats why I decided to revert the patch in java component of location services.

As a temporary solution, I could add it again if there is demand.

I noticed the following - cited from TomGs original thread:

0.20 - 10th October 2010

Updated to latest source from git. Now based on Android 2.2.1 (FRG83)

GPS problem fixed.

...

0.10

Reboots if GPS is turned off then back on.

...

The version 0.10 GPS drivers are compiled from source in CM6. The GPS icon completely functions as expected there. But the device reboots as stated when toggeling GPS - this behavior can be reproduced on my roms when building the GPS driver from source.

The version 0.20 (and above, including TXG, and currently cm6-clean) GPS drivers were taken from eclair. They work, do not crash, but they do not interact correctly with the framework regarding GPS icon update.

It would be better to fix the reboot issues with GPS drivers included in CM6 - this would give fully working GPS without any hacks in java components of the framework.

Edited February 9, 2012 by dr.flo

[Guest pier11]

how gps is functioning(?) on cm7? May be worth to look there...

[Guest dr.flo]

how gps is functioning(?) on cm7? May be worth to look there...

from source and as far as I know without issues.

But api has changed a lot, many files differ completely :(

[Guest twrock]

My first "seriously" bad thing happened today with this rom.

I was unable to accept an incoming call, and I let it just quit ringing. 15 minutes later I tried to return the call. There was no sound on my end of the call, no ringing, and no voice from the other person after they picked up. I verified my phone's sound was on (it was). I hung up, called back again, and it happened the same. They could hear me (verified later), but I could not hear anything. I rebooted, and was able to place the call normally.

I suppose I should attempt to reproduce the problem, but maybe it was just one-off.

[Guest dr.flo]

My first "seriously" bad thing happened today with this rom.

Did something like that ever happen with original TomG port? Maybe some build.prop setting can fix it...?

[Guest jace7]

My first "seriously" bad thing happened today with this rom.

I was unable to accept an incoming call, and I let it just quit ringing. 15 minutes later I tried to return the call. There was no sound on my end of the call, no ringing, and no voice from the other person after they picked up. I verified my phone's sound was on (it was). I hung up, called back again, and it happened the same. They could hear me (verified later), but I could not hear anything. I rebooted, and was able to place the call normally.

I suppose I should attempt to reproduce the problem, but maybe it was just one-off.

Hi TWROCK , I have experienced the same problem a couple of times with your TXG06 rom , had to reboot to get the phone working again . Just updated to TXG07 , no probs yet . Thanks to all you guys for the great work

[Guest twrock]

Did something like that ever happen with original TomG port? Maybe some build.prop setting can fix it...?

I haven't, but Jace7 definitely did with TXG. So it looks like it isn't specific to this rom, but it has happened to at least two of us.

I will go back and delete any changes I made to the build.prop of this rom and try running it for a while again. Maybe I can test that particular sequence of events both before and after I modify the build.prop.

[Guest dr.flo]

I haven't, but Jace7 definitely did with TXG. So it looks like it isn't specific to this rom, but it has happened to at least two of us.

I will go back and delete any changes I made to the build.prop of this rom and try running it for a while again. Maybe I can test that particular sequence of events both before and after I modify the build.prop.

Might also be interesting to see if it happens on the newer froyo branch (instead of froyo-stable). Maybe the issue got fixed there...?

[Guest dr.flo]

You may want to try this libloc_api.so

It is a candidate for fixing gps icon bug within gps driver itself. Should work on TXG as well. Since this originates from the gps driver that previously caused reboots when switching gps off/on, we also should verify that we do not introduce this "old" bug again.

Edited February 13, 2012 by dr.flo

[Guest didije]

You may want to try this libloc_api.so

It is a candidate for fixing gps icon bug within gps driver itself. Should work on TXG as well. Since this originates from the gps driver that previously caused reboots when switching gps off/on, we also should verify that we do not introduce this "old" bug again.

verified. works great on TXG as well