yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] ephumuris:
I have decompiled the framework-res.apk for beta 3 and edited arrays.xml. In here are the autobrightness levels and there were hardly any values. What i have done is taken the values from a stock Moto 2.1 rom and applied them to the beta 3 framework.

Please test only if you currently have issues with autobrightness. I have supplied the stock beta 3 framework should you wish to revert.
[Defy Android Development] ephumuris:
It's working for me. Read the thread!
[Defy Android Development] sunoldman:
For anyone who confused about the Chinese character in baseband swithcher.

Here is a translated version of it, mostly traslated to English

http://xdaforums.com/showpost.php?p=12604145&postcount=10
[Defy Android Development] peetr_:
Autobrightness works for me to, I only needed to change the levels in CyanogenMod settings - Display and now I don't even care about the brightness.
[Defy Android Development] AkkiandDefy:
I cant keep 1300posts in mind....

Sent from my CM-7 Defy with XDA Premium
[Defy Android Development] ephumuris:
Yes that works but my framework mod makes the levels the same as stock roms and you shouldn't need to manually edit levels. But whatever works for you :D
[Defy Android Development] Quarx:
Can you post stock values for Autobrightness?
[Defy Android Development] ephumuris:
Full brightness levels from Moto 2.1 rom. Some values probably not needed but take a look anyway.

<integer-array name="config_autoBrightnessLevels">
<item>1</item>
<item>3</item>
<item>30</item>
<item>100</item>
<item>249</item>
<item>651</item>
<item>1000</item>
<item>1500</item>
<item>2000</item>
<item>2997</item>
<item>4995</item>
<item>6992</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>21</item>
<item>21</item>
<item>84</item>
<item>84</item>
<item>84</item>
<item>149</item>
<item>149</item>
<item>149</item>
<item>204</item>
<item>204</item>
<item>204</item>
<item>255</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessButtonBacklightValues">
<item>20</item>
<item>20</item>
<item>100</item>
<item>100</item>
<item>100</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
</integer-array>
<integer-array name="config_autoBrightnessKeyboardBacklightValues">
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
</integer-array>

Let me know if they work for you. Seem to improve my experience.
[Defy Android Development] AkkiandDefy:
@Quarx

This will help fixing GPS Problems :)
[Defy Android Development] [] AL []:
...re. Oct30th nightly, yes responsive, got same video cam hang on stop and fc has w last nightly I've tried a few days ago.

Also have experienced a total freeze while just browsing though the settings menu; battery pull required.

Sorry for not supplying logcats, but camera bug should be easy to reproduced anyway (red).
[Defy Android Development] ccav2000:
This is not good :(
[Defy Android Development] gkai:
I think I had one too, just after the second reboot after installing the ram. No problem since though. I have a green lens (using LGcam app), and after a few shots and video, no force close. Even better, image seems much better especially for dark indoor shots.

Next days will tell, half a day is a bit short to judge stability, but for me this nightly looks like a keeper! :-)
[Defy Android Development] labsin:
It doesn't exist.

You can try toggle 3g/2g

http://xdaforums.com/showthread.php?t=739530

An app for these functions.

Sent from my MB525
[Defy Android Development] travis:
On some phones it is a tick box under:

phone settings/wireless&networks/mobile networks

"Use only 2G networks"

"Saves Battery"

If it's not there then you indeed do not have it.
[Defy Android Development] ktmbikerman:
Ah... now I know why I thought they were part of ms2ginger. You need to use the power widget in that rom as it doesn't have the notification power widgets.
[Defy Android Development] ccav2000:
Ok, the nightly I was waiting is online, so I will flash it soon. I must test the new patches, oh what we do in the name of progress! :D
[Defy Android Development] twa_priv:
Hi Epsilon,

Got the camcorder FC again (red lense). This time I had an

adb logcat > logcat.txt

command running while the phone was connected via usb.

Again, the video started recording but when stopping the recording the camera hung and finally FC'ed.

I attached a new log (logcat_camcorder_fc.txt). Maybe this log is more helpful and shows some indication as to why this error happened.

Also, after the FC the phone is totally unresponsive (even though not completely dead) with tons of "I/InputDispatcher( 2139): Dropped event because input dispatch is disabled." messages in the log. I've attached another logcat with the messages logged while the phone was unresponsive and needed to be rebooted. Needed to pull the battery because long-pressing the power button didn't bring up the usual reboot/shutdown menu.

Thanks for your help.

I'm on latest cm71-111031.1624-NIGHTLY-Defy.
[Defy Android Development] ccav2000:
@twa_priv where are the logs ?? Not seeing any.

I just flashed today's nightly, hoping for the best.
[Defy Android Development] twa_priv:
I attached the logs now - they were rejected at first because they exceeded the limit. Zipped them up instead.

Just out of curiosity I'm going to try now the latest official cm_jordan_full-45 nightly and see if I can reproduce the vidoe fc's there also....

EDIT: Same camcorder FC happened with official nightly #45.
[Defy Android Development] Otto.BR:
@ ccav2000

just a dumb idea, have you tried messing around the settings under sound in CyanogenMod settings? Like Notification Focus or Always play on Speaker?

I'm guessing that was one of the first things you tried, since you probably know your way around android better then I do... :D

Also. CyanogenMod settings FC's whennever I try to open ->Lockscreen -> Widget Options.
[Defy Android Development] ccav2000:
And like twa_priv above me, I only have bad news. The new patches had no effect, the MP3 decoder crashed again and notifications died.

At this point I'm forced to consider the builds here as unusable for me, falling back to the Cyanogen builds from the buildbots without H/W acceleration that do not exhibit this problem.

Sorry Epsylon3, but there is bug in that code, I cannot use it. And the only sounds played by my phone again was *only* "spacious", one of the default CM7 sounds for notifications. It's not a corrupted MP3 or anything from my SD.

---------- Post added at 12:18 AM ---------- Previous post was at 12:16 AM ----------

Obvously... NO. And I can clearly see in the logs the MP3 Decoder crash and burn with a full debug dump. The code has a bug, and it seems that only my setup triggers it.

---------- Post added at 12:45 AM ---------- Previous post was at 12:18 AM ----------

One final thought before I go to sleep.

The OMXMp3 decoder crashes *after* it has played the sound. The error is always the same:

E/OMXNodeInstance( 1954): FreeHandle FAILED with error 0x80001003.
F/OMXCodec( 1954): frameworks/base/media/libstagefright/OMXCodec.cpp:2829 err != OK

So whatever happens, happens when the decoder tries to free that handle, it fails, crashes, and then completely destroys all the notification related services, as I no longer get any notification sounds from that point until I reboot.

I have no idea why it can play the same sound a few times, then on some random occasion, playing the same sound again crashes it. (I always refer to my default notification sound, 'spacious').

This is my attempt to describe my observations as best as I can. Main source for notifications for me is the official Twitter client and the Google Talk client.
[Defy Android Development] Jefgenowitsch:
Just a reminder.Notification sounds also die on my phone.It appeared some nightlies before and on the latest nightly the problem still exist.

Is it possible that this problem is related to dsp? I remember that a had a few DSP error messages on my phone...just a thought.
[Defy Android Development] hailmary:
im been getting problems in notifications too...my text messages are numb & gtalk dont pop me up.

my resort is always 111015-1128-nightly its the cure;) the best.
[Defy Android Development] [] AL []:
Since we're in the bad news trend...

After trying Oct30 nightly for a short while and having the video cam problems,

I wiped cache and dalvik (maybe should have factory reset as well, but..) and restored my Oct15th nand. After that, I had a lot of problems getting wifi to connect: nit never connects or it might take 2 minutes just to see the wifi indicator and I also get the 'not in range' message. ....just as I wrote that I never experience wifi connection problems...

Forgetting that network, rebooting and even wiping cache and Dalvik and install the nightly again doesn't solve it either... Will try custom recovery factory reset and nand restore again but I might have no choice to go back once more to square one and flash sbf... dang!
[Defy Android Development] Epsylon3:
yep the wifi really need a fix...

else, today i found the way to change button backlight intensity

i heard some defy+ users who already have dead leds on the 2.3.x kernel

i will publish a new kernel module for that soon...
[Defy Android Development] nameite:
My DSP's been crashing ever since I came on CM7, but it never really affected me.

Now that you mentioned it, maybe thats why I miss some of my notifications.
[Defy Android Development] ccav2000:
Jefgenowitsch & Hailmary, thank you for finally confirming that I am not alone with this bug. The reason I am making such a big deal out of it is obviously because I use the notifications for interactive tasks that require a quick response usually, I cannot afford not to have notifications!

With respect to Epsylon 3 and the rest of the devs efforts, this bug is a show stopper for me.
[Defy Android Development] maniac103:
You don't make it a big deal, it IS a big deal. It's not only the muted notifications, but also a battery drain problem: As the notification service holds a wake lock during playback and won't release that was lock after the crash, the phone won't deep sleep anymore until a reboot.
[Defy Android Development] nameite:
That makes sense...so why does DSP manager crash?

Could we just remove it with RE?
[Defy Android Development] lukassek:
I can't use camera with flash... It's making black pictures... It doesn't work at least with last sixth nightlies in a row (the latest I tried is cm71-111101.0750-NIGHTLY-Defy)... Any suggestions...?
[Defy Android Development] Epsylon3:
Ok, new nightly 2011.11.01 with a new module to test (enabled) which allow to configure the buttons backlight brightness level (when on).

There are 64 levels for these leds, which could allow later to enable animations and dim on timeout...

echo 0-255 > /proc/ledsfix/brightness

default is 48, now we need to integrate that in android, to allow the automatic brightness adjustment of the buttons... :)
[Defy Android Development] maniac103:
I'll do that integration. I just would like to request a nicer module name first ;) How about "keypad-brightness"?

I think I may have found the bug. It seems related to the order of files played, perhaps it's triggered by multiple notification sounds being played at the same time.

I'll need some time to confirm that, though ;)
[Defy Android Development] henel321:
I can only second that. Currently on 20111031 and I experience the exact same behaviour. Everything looks dandy until notification crash and then wakelock and POOF there goes the battery...

20111031 has also started to spontaneously reboot and Launcher Pro has been crashing all morning which didn't happen on 20111030, but I haven't debugged that any further. :(

Installed official CM Nightly #45 now to see how that one behaves.
[Defy Android Development] ccav2000:
Well, if you require testing at any point, I'll do it. From the user side, it's all I can offer.

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

I'm also on the official No. 45, it's very stable.
[Defy Android Development] henel321:
Mine isn't..

Just froze solid (opening gmail?) and I had to pull the battery. Launcher Pro has been freezing for 5-10 s on a few occasions the last hour as well. Going to try to get some logcat information later on to see if there are some hints....
[Defy Android Development] ccav2000:
Damn. I will also know more latter in the day, I have not used the phone much as I'm working right now and don't have the time to fiddle much with it. If there is a problem, it should appear in mine too later.
[Defy Android Development] henel321:
Pin pointed the launcher pro problem.. Launcher Pro works great up until I press home when on the first home screen to display miniatures of all homescreens.

This simply locks LPP and produces the attached logs. Looks database related to me... Will try to revert to and older known working build to see if it works to see if it is purely LPP related or related to any framework/sqllite changes to CM7.
[Defy Android Development] ccav2000:
Interesting. I also use Launcher Pro, and have no such issue. Try uninstall/reinstall?
[Defy Android Development] henel321:
Doesn't work with #45 or 20111030, BUT it

works

with #37 so it is definitely CM7 related in SOME way. (Haven't done any changes to LPP, just changed roms wiping dalvik/cache each time)

LPP works if I reset to default settings with 3 homescreens on #45 or 20111101.... If i reload my saved settings it stops working again producing similiar logs as the one above.
[Defy Android Development] ccav2000:
I'm using 5 screens, but perhaps I have different settings in some way.
[Defy Android Development] duendetuc:
My phone doesn't enter in deep sleep with the default cpu configuration. Only when i desactivate the overclock ir bootmenu to get the motorola default configuration it enters ir deep sleep. What can I do?

Edit: false alarm. I did more testing. Now it reaches deep sleep at overclock config.

Enviado desde mi MB525 usando Tapatalk
[Defy Android Development] maniac103:
I have pushed the fix. Just try the next nightly and see what'll happen.
[Defy Android Development] ccav2000:
Noted, will definitely try it. News either tonight or tomorrow, depending when Epsylon3 builds one.
[Defy Android Development] LeopardSurd:
I'm using the same 45 official nightly and LauncherPro with 3 screens and I don't have any problem mentioned here. I think it is a LauncherPro related. My only special mention is that I use home button to enter in app drawer from LPP.
[Defy Android Development] everaldo.santos:
Force close in CyanogenMod Settings > Lockscreen > Widget Options. :(
[Defy Android Development] henel321:
It isn't. On official #37 it works, upgrading to 111030, #45 or #46 breaks it. Going back to #37 and it works again. (I haven't had the time to test exactly what build is the last one that works unfortunately.)

Possible to work around, yes, but hardly launcher pros fault.
[Defy Android Development] memz180:
Hey guys my phone locked up 2 times on the 31st nightly had to pull the battery and restart is this got anything to do with cpu power saver module that was added in history ? Hows the nov 1 nightly any better ? Cheers
[Defy Android Development] reaperzero:
on 111101.0750-NIGHTLY

force close when going to CM settings> Lockscreen> Widget Options
[Defy Android Development] memz180:
Its been like this for the past couple of nightlies
[Defy Android Development] UEman:
I don't get that force close with the same nightly.
[Defy Android Development] andyman_187:
notifications going silent for me as well (111030) battery drain until reboot too. Going for 111101.0750. can anyone confirm if the notification thing was fixed on this one? TIA!

---------- Post added at 09:28 AM ---------- Previous post was at 09:21 AM ----------

ok....i just confirmed this myself....notifications are ok now( so far) will continue to monitor throughout the day. I remember notifications were fine the first time i flashed 111030, then they just went silent the next day. Hope it it's not the same case with 111101.
[Defy Android Development] ccav2000:
Sorry mate but the 111101 is not fixed, I have already tried all recent nightlies. The next nightly will have a fix that maniac103 has included which will probably fix things, I'm waiting for it.
[Defy Android Development] andyman_187:
thanks, will be waiting for that one as well
[Defy Android Development] [] AL []:
So I'm curious: did your video cam still behave properly afterwards?

Because, that is what I'm mainly waiting for news on... Like I already mentioned, Idid give a chance to the runner and cleared cam's data, rebooted, took a few pics and tried the video cam again but it didn't work. Also noticed that the phone also got hot after the fc... But 2 fc and reboots plus a complete freeze up didn't make me want to continue the stability testing... ;)

As for the rest, although it's been kind of a rough road in the past couple of weeks, there is some promising and interesting stuff coming: hardware acceleration, new kernel bits, maybe re-tweaked wifi... I really admire our devs' work.
[Defy Android Development] princess of hell:
+1

I Compiled a nightly with the same result Force Close.
[Defy Android Development] maniac103:
Please post a logcat.
[Defy Android Development] hailmary:
[QUOTE='[] AL [];

there is some promising and interesting stuff coming: hardware acceleration, new kernel bits, maybe re-tweaked wifi... I really admire our devs' work.[/QUOTE]

good to hear this one.i've been too busy-no time to check other sources/info;)

waiting...
[Defy Android Development] ccav2000:
Ok, Epsylon3 uploaded a new nightly, everyone who like me had any notification sound issues please try http://defy.tanguy.tk/jordan-nightly/cm71-111102.0510-NIGHTLY-Defy.zip

Other things are in this too, the backlight led module is also included, I can manipulate the led intensity of the 4 buttons below screen by using the custom levels for the screen brightness in settings -> cyanogenmod settings -> display -> automatic backlight -> edit other levels.
[Defy Android Development] walter79:
Could someone port led module to motorola defy+ roms?
[Defy Android Development] 57op:
Since i've got the same issue, i've posted a logcat.
[Defy Android Development] bpugliese:
ccav, is the notification problem finally solved for you?
[Defy Android Development] ccav2000:
Hmm, I cannot be sure until I use the phone more, but so far after about 3 hours it is operating properly, no errors.
[Defy Android Development] princess of hell:
ok, this is my logcat.
[Defy Android Development] labsin:
Button brightness working great. Only when on automatic brightness, they don't go back to full after they go dim and with a fixed brightness they don't dim. Also when you choose a screen brightness, the buttons go along... You probably already planned to do these think.

I'm happy with my bright buttons. Jet another cool new feature for our defy.

Sent from my MB525
[Defy Android Development] maniac103:
Thanks, it will be fixed in the next nightly.
[Defy Android Development] twa_priv:
Were the logs regarding the red-lense camcorder fc's I uploaded of any help?

Is there anything I can do to help debugging this issue further? I just re-installed cm7-111015-1128-NIGHTLY and was able to reproduce the FC's when stopping the vidoe. It took me a few tries to reproduce the issue, a little more than with more recent nightlies. But even recent nightlies don't always FC, sometimes it happens right away, sometimes it takes a few vidoes. I wasn't able to find a pattern yet- even though it seems (but I might be wrong) it happens more likely in darker environments.

Thanks
[Defy Android Development] andyman_187:
is there any way to disable to automatic brightness for the buttons? mine doesn't seem to be working properly....they go out after i unlock and to get them back on, i need to readjust my screen brightness...i was happy with them before, can you please provide an option to disable this? TIA!

BTW: notifications sounds seem ok...will do further testing (assuming there IS a way to disable the buttons brightness...if not, going back to nov 1 nightly which also seems to have OK notifications sounds at least for me anyway, but i didnt have too much time to test since I flashed the nov 2 nightly right when it came out)
[Defy Android Development] Epsylon3:
Yea, that will come... we are working on that... cm7 seems to be buggy also, on lcd switch on (a default value is set, then the one from autobrightness)

For defy+, i dunno but for the the 2.3.4 kernel on defy 1, i will do it soon...
[Defy Android Development] andyman_187:
Got it, thanks epsylon! I managed to work around this by setting a custom light level for the buttons at the lowest threshold (set to 20). They wont dim under bright conditions even with the rest of the levels set to 0, but at least they dont shut off completely when coming from the lockscreen.
[Defy Android Development] ccav2000:
Hm, why? Is there any plan to update to the 2.3.4 kernel eventually for the Defy 1? But that breaks the camera for everyone with the SOC camera module, no?
[Defy Android Development] Epsylon3:
Yea, but its for new defy+ users :p there is still lot of work to do about that

actually on my repo : light sensor, proximity sensor, battery and phone are not working... Quarx made some fixes, but we dont have an official branch
[Defy Android Development] ccav2000:
As for the notifications, so far so good, since I installed the 2nd November nightly at 17:00 GMT yesterday I had no problem. After this day is over I'll be 100% sure.
[Defy Android Development] ccav2000:
It's rather sad we cannot compile a new kernel, the hacks with modules fix some things but we cannot fix or update the core functionality. For example, I have noticed it has bugs with IPv6. Many times it thinks it's address is in use while it's not and disables IPv6.

Of course, such a bug is not likely to be noticed by the average user, as the average user doesn't even have native IPv6 connectivity, or cares about it. But take this as an example of things we cannot fix.
[Defy Android Development] flunk03:
a little help required over here , no matter what nightly am running on i still get accelerated battery drain inspite of callibrating the battery by wiping battery stats via recovery usually i get accelerated drain from 58% to 49% and then sometime 39% to 19% or 29% to 5% is anybody else experiencing these kind of spikes if so any workaround for this ?
[Defy Android Development] [] AL []:
Wiping batt stats in recovery doesn't mean that youve done a calibration; it simply erase the stats. You should only do that when then battery is full charged and that means way (1-2 hours) past the 100% mark.

As for the spikes, I always get the 56% to 49% one no matter what...

Someone as suggested that if you stop the charging before 95%, it illiminates it...but I don't find that convenient at all and I'd rather lose that 6% int the middle instead of not charging fully...

Restoring and nand also makes battery stats innaccurate and will create those 'accelerated drains' since the chances are that the battery is never exactly at the exact same level that it was when you've created the backup.

It's been said many times; the best practice is to fully charge before backing up, restoring or wiping stats.

And most of all, a real calibration involves letting your phone completely discharge then recharge it fully without interruption.

---------- Post added at 03:49 PM ---------- Previous post was at 03:40 PM ----------

+1 on this one because I don't think that I will test another nightly before I hear some development in this matter. I have yet to experience the problem on Oct15th nightly and hopefully, I won't now that I wrote it down...;)
[Defy Android Development] reaperzero:
thats weird :/ i did a wipe and its still the same though :/