yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] maniac103:
Right.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] juried:
Here is the result. I started the record well into the call, after I confirmed that the sensor did not respond each time. Most events did result in the screen turning on, but some of those events which took a bit longer, the screen either took several seconds to turn on, or did not turn on at all.

I noticed something more this test: The capacitive keys lit up each time I removed my finger from the sensor, but again, occasionally the screen did not get switched on.

I tried to note the times but it was rather hard... I hope this can be of value. Start from the latest event and work backwards- the last event or the 2nd last one was one of these dud ones.
[Defy Android Development] maniac103:
Thanks, the issue is evident in the log. The proximity event is processed in PowerManagerService, but turning on the screen is delayed to the point where the screen is turned on and off again at the same time.

I'll check out the code.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] popadic022:
now you know where is problwm with prox.sensor? can you fix it?:fingers-crossed:
[Defy Android Development] oSandmaNo:
Maniac

Can you please include dev tools and spare parts in your next build :)
[Defy Android Development] Nemado:
Hello. I tried CM10 two days ago but the custom brightness menu kept crashing. So I did a full wipe and installed the latest CM7.2 nightly and the custom brightness menu doesn't crash anymore. The brightness level, however, is bugged now. The default settings work but when I modify them, the screen brightness is blocked to the highest setting regardless of the light exposure. The buttons backlight settings still work as intended and change according to my settings and the light sensor inputs.
[Defy Android Development] adiq_ambro:
You can find both Developer Tools and Spare Parts in Google Play.
[Defy Android Development] Tha TechnoCrat:
Are Defy and defy XT the same phones?

Please reply ASAP
[Defy Android Development] TeeJay3800:
None of your questions are appropriate for a ROM development thread. They have nothing to do with this ROM and should be asked elsewhere. In fact, try searching before asking anymore extremely basic questions.
[Defy Android Development] ppero196:
No
[Defy Android Development] maniac103:
I've uploaded a new debug build here. Anyone with the proximity sensor problem, please do the following:

Install the build

Install the app CatLog

reproduce the problem one or two times

use CatLog to grab a log and post it or send it to me

Thanks.
[Defy Android Development] lolzas:
I get a battery drop from 34% to 19% with latest maniac defy+ build on my defy red lens

what should i do?
[Defy Android Development] TJKV:
You should search the forums for battery drop

Sent from my MB526
[Defy Android Development] popadic022:
do you have problem with prox.sensor?
[Defy Android Development] juried:
Here is the resultant catlog.

I noted it seemed to switch on most if not all times; however, I also noticed multiple times that if I covered the prox. sensor, it would momentarily darken and then switch on again, remaining on until I uncovered and then covered the sensor again.
[Defy Android Development] juried:
Here's another one, essentially the same conditions, but I disabled tasker, and instead of staying in the home screen, I went back to the call screen after starting the log recording. One of the very first results was that it switched the screen back on after first darkening it when the sensor was covered.
[Defy Android Development] maniac103:
The interesting thing is that in this log, the proximity sensor wasn't even enabled, because:

11-12 08:20:07.108 D/PhoneApp( 2531): updateProximitySensorMode: state = OFFHOOK
11-12 08:20:07.108 D/PhoneApp( 2531): screenOnImmediately false horizontal true beginning call false phone state OFFHOOK
11-12 08:20:07.108 D/PhoneApp( 2531): updateProximitySensorMode: lock already released.

... the phone app thought you're holding the phone horizontally. Was that the case? If yes, please provide another log where you're holding it vertically (or enable the 'always use proximity sensor' option). If no, I guess I should look towards the acceleration sensor instead of the proximity sensor ;) In that case, can you check whether the accelerometer data in the sensor testing app looks reasonable (d[1] around 9.8 and d[0]/d[2] around 0 when holding phone vertically, d[0] around 9.8 and d[1]/d[2] around 0 when holding phone horizontally)?
[Defy Android Development] juried:
Phone lying flat = X=Y=0 and Z=10, phone portrait vertical X=Z=0 and y=10, phone landscape vertical X=10 and Y=Z=0.

The attached logcat is with the phone held vertically, portrait position. I think the first event resulted in a screen staying off, not responding to anything. The interesting thing is, the capacitive keys light up when the prox sensor is uncovered, but the screen remains dark, and the capacitive keys are also unresponsive, so pressing 'Home' does nothing.
[Defy Android Development] juried:
There is another possibly related screen bug: Quite often when I press the power button to turn the screen off, it will turn on agan after a few seconds.
[Defy Android Development] maniac103:
Ok, that's fine.

The buttons are lit up a tad earlier than the screen is enabled. Obviously the point of the buttons being enabled is reached, but turning on the screen is delayed. It's still quite unclear to me why this delay (which lasts until the next proximity sensor event) happens. I assume it's related to either the phone entering deep sleep too early, or to some function call blocking. There's no more explanations for this.

I've uploaded a new build with even more debug. Could you please reproduce the log grabbing with that build?

I suppose this is related to some wake lock being grabbed. Please try to grab a log with that problem reproduced with the new build and hopefully we'll be able to see.
[Defy Android Development] juried:
OK, will be able to post something in a few hours from now.

Just a more basic question: The defy+ is supposed to be identical to a defy with red lens but with bigger battery. Sooooo, shouldn't the two builds use everything the same except battery files? Why further differences? Should we perhaps pursue the avenue of just using the defy red-lens firmware?
[Defy Android Development] [] AL []:
Typo...

@ maniac103:

I was doing some theming and after decompiling your last build's SystemUI.apk, I've found that:

\SystemUI.apk\res\drawable-hdpi\stat_sys_data_inadnout_e.png

is misspelled: [in

and

out]. I did not check the rest of the code to see if it links to it as it is [has the same bad spelling] or not though...

But still, I think that it should be corrected nevertheless..

That 'could' explain why I was seeing two different statusbar icons when playing around with mms last week...

That's it!

Cheers

/ A
[Defy Android Development] maniac103:
Some kernel interfaces are different between Froyo (Defy) and Gingerbread (Defy+) kernels. Proximity and light sensor is one example of those differences, RIL stack is another. Defy+ kernel can't be used on Defy (SOC camera won't work) and Defy kernel can't be used on Defy+ (due to higher bootloader version) - thus, the only way is to do two different builds.

Err, no ;) Other themes might (or probably will) already be using the misspelled version. Changing the file name will break things for those (existing) themes.
[Defy Android Development] [] AL []:
...or maybe eventually using a unified (containing all specifics for red/green/defy+) 2nd-boot custom kernel..?

I believe that Walter79 is currently working on one of those [and Quarx' cm10 custom kernel is also a unified one].

After a bit more investigation, I realized that both 'stat_sys_data_inadnout_e.png' and 'stat_sys_data_inandout_e.png' are included in the SystemUI.apk ...and that since beta 5 time for cm7-jordan [beta 4.1 didn't] :p

And I've also seen the same on some old cm7 roms for a ZTE phone.

I looked at a few themes I had decompiled earlier and none are referencing to that png name either.

But I'll play it safe and include redirections to both in my theme...

Thanks for the answer anyway :good:
[Defy Android Development] kapil_dheer:
Problem taking pictures....

Attached are some pics taken on maniac's 7 Nov nightly.....every second pic I take has some kind of colour wash offs....did nothing new.

Using defy plus builds on defy since last 6 months. Other camera apps like camera 360 produce even harder washoffs. Memory base same since I bought defy 1.5 years back. Tried to take pics in various modified ways but results almost the same.

Is the problem with my camera module or something gone bad in the recent updates. Please suggest.
[Defy Android Development] popadic022:
does earlier version cm7 than september have problem with prox.sensor? i see in quarx last version cm7, that file size is different than in lasta maniac103 or fuzz.
[Defy Android Development] juried:
Attached is the catlog. It did not seem to misbehave at all. Did you do something that would have fixed the bug?

The only thing I found, and that could be normal behaviour, is that when the phone is flat horizontal, it does not respond to the prox. sensor at all.
[Defy Android Development] maniac103:
No, I didn't. The logging might just change timing. Can you continue to try to reproduce the issue over the next few days?

The proximity sensor is only enabled if either the phone is held vertically, or the 'always use proximity sensor' option is enabled. If the phone lies flat somewhere, it's unpredictable whether this is recognized as portrait (proximity sensor enabled) or landscape (proximity sensor disabled).

Thus, I would say this behaviour is normal.
[Defy Android Development] juried:
I'm overseas for the next week, so hopefully someone else could try doing the logcat thing, at least until I am back.
[Defy Android Development] [] AL []:
+1 [although i don't own a defy+] - where's Leopardsurd?

NP/YW

You might want to try the new Phone.apk as I fixed a few issues with my first mod...

Get the fixed tweak zip on my original post here .

I gave more details on the issues there as well.

Talking of issues I had with compiling the Phone.apk...,

I don't know if it's specific with brut.all's apktool (and derived softwares from it: I had same problem with apkmanager and apk-multitool...), but there seems to be an issue with the "%" character in some of the Phone.apk's language strings xmls (9 language in fact: da, es, fi, it, lv, nb, ru, sv and zh-rTW).

I've found that mainly these three strings:

"throttle_status_subtext"
"throttle_data_usage_subtext"
"throttle_time_frame_subtext"
[all around line 200 of the respective \res\value-xx\strings.xml]

where there is either "%1$d%" or "(%2$d %)" --> the last"%" had to be changed for this one: "٪";

they then become: "%1$d٪" and "(%2$d٪)" respectively.

The chinese xml even has a third percentage character: "％" which also has to be changed for "٪" to avoid compilation errors.

So is this a known issue and/or maybe only an issue for hackers compiling on Windows?
[Defy Android Development] ktmbikerman:
Quick question... I'm currently on CM10 and have data on ext4 format. I would like to return to CM7 but I'm unsure if I have to reformat to ext3 before flashing CM7.

Anyone done this yet?

Thanks

EDIT: to answer my own question... I reformatted data and cache to ext3 before restoring nanroid backup of CM7 and all worked fine.
[Defy Android Development] ktmbikerman:
just installed the 7 line mms apk and the updated phone apk on my defy+, both are working well, Thanks AL
[Defy Android Development] tayte2003:
Does this rom include Sim unlock

Thank you very much for this rom. Does it include sim unlock. Or do I have to unlock it seperate. I'm new to this so if I'm asking a stupid question sorry in advance.

Thank You!
[Defy Android Development] DeeKay11:
Would exFAT support be added in the future, or is there a way to enable it now?

I have a 64GB SDXC card and

according to this

using FAT32 on it may shorten its lifespan and slow it down. While I care less about the lifespan, I can confirm it being slower.

Anyhow, super thanks for your (and folks around here) support.

I personally find this ROM much better suited for the Defy than CM10.
[Defy Android Development] popadic022:
is there any new news about prox. sensor? is it fixed?
[Defy Android Development] manoutch:
New euroskank CM7.2.0-20121117.1504-Defyplus work fine. :good:
[Defy Android Development] popadic022:
no "call end bug", sensor work ok during call, always?
[Defy Android Development] [] AL []:
It doesn't and a quick search would have resulted in this:

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

;)

Too quiet in here these daysl I even got time for some theming... :D
[Defy Android Development] ktmbikerman:
I switched to maniac's build from a week or so ago a couple of days back as I was going to be doing a 1500km road trip, and wanted the best connectivity possible. Unfortunately I suffered many data disconnects, fixed by a flight mode toggle.
[Defy Android Development] manoutch:
yes for me.
[Defy Android Development] popadic022:
works???:confused: now i install and its worst then earlier. do you have defy or defy+? sensors works ok on defy, but defy+ have problem.
[Defy Android Development] Nemado:
This custom backlight settings issue is driving me crazy. Everything worked fine a couple of weeks ago, then I decided for God knows what reason to install CM10 last week. After flashing CM10, custom backlight settings didn't work anymore. I tried reinstalling CM7, CM9, same issue, it didn't want to work anymore.

Then I decided to flash back to the official CEE froyo and do all the tedious installation process over again to have a clean CM7. So that's what I did. I've got a clean CM7 installation, nightly 16.11.

And custom backlight settings still don't work. And I'm losing it.

Could one of you try custom automatic backlight settings, and check that the brightness level change according to their custom settings? My phone just doesn't give a damn.
[Defy Android Development] manoutch:
defy+ see ma signature.

Try this method.

Work for me!
[Defy Android Development] Nemado:
I checked again the next day and everything was working fine. I did absolutely nothing in the meantime. now I wonder if the problem would fix itself as well on epsy's cm9. damn me.
[Defy Android Development] [] AL []:
Hey guys..and girls

No new nightly lately so I get some time to try new things out...

So if you are also seeking new things to try or just want to practice your modding skills, here's a link to the latest tweak that I've tried and the writeup I did on it.

If your are running on one of maniac's last 2 builds, there's even a flashable zip for you to try...

Enjoy

/AL
[Defy Android Development] antukubo:
i got problem with calendar notification on cm7.2 which is offset 8 hours (my GMT is 8+). When i set the alarm on 0000 hours, it will only notify on 0800 hours. I use the same Google account with my tablet and CM10 (on the same phone - 2nd boot) and it runs perfectly. Tried to clear data, re-install and even extract calendar.apk from Maniac's Nightlies but none is working. I didn't found any good solution on Google. Any idea guys?
[Defy Android Development] jayanth1255:
Which cm7 build is nice?? Jordan, Quarx or Epaylon?? I am thinking to come back to cm7 I don't know earlier which one I used..
[Defy Android Development] maniac103:
In case you're talking about reminders for all-day events: yes ;)

If you don't want to use nighlies, you need CalendarProvider.apk from a recent nightly. Then clear data of calendar storage (not the calendar itself!), let it re-sync and you should be good to go.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] antukubo:
I've been looking the solution for months but with your single answer, the problem is now officially gone. Wow... thank you very much! You saved my day...
[Defy Android Development] juan296:
We all use latest maniac's build :)

Arch Linux User ..
[Defy Android Development] Nemado:
By the way, I'm curious to know who's releasing the 'official' nighly builds on the official website and what are the actual differences between maniac's build and the official one. Could someone please indulge me?
[Defy Android Development] popadic022:
new release cm-7-20121125-UNOFFICIAL-jordan_plus-signed? prox.sensor fixed? anyone tried who use defy plus?
[Defy Android Development] Enricosteph:
Is it from here?

http://get.cm/?device=jordan_plus

Who is releasing this Builds?
[Defy Android Development] measel:
maniac
[Defy Android Development] popadic022:
yes from official site, and fuzz relese his CM7.2.0-20121126.2011-SKANKY-Defyplus.
[Defy Android Development] Enricosteph:
Okay thanks so the "cm-7-20121125-NIGHTLY-jordan_plus-signed.zip" is a Maniac Build?

Than i´ll give it a try...i´m currently on Maniac last "cm-7-20121107-UNOFFICIAL-jordan_plus-signed.zip".....his Build are great :good:
[Defy Android Development] measel:
no, i think he doesn't build it but commits the fixes and it's built by cyanogenmod. (not sure though)

ps: all the fixes are in maniacs latest unofficial build.
[Defy Android Development] maniac103:
Correct. The CM builds are done on a weekly basis, even if there are any no changes. I think this time there are changes: I submitted the LTO download to the official builds.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] cfanmaoli:
I had saw the EP3's last cm7 build had the 2ndboot kernel, would you made one?
[Defy Android Development] popadic022:
on last build from official site 25.11, prox sensor work ok, but still sometimes screen stay black after call or during call when move phone from ear, defy+.
[Defy Android Development] ofmb:
have you seen the build? where?

i think these are only commits
[Defy Android Development] cfanmaoli:
http://defy.wdscript.fr/ I am using now:)
[Defy Android Development] popadic022:
only defy, not defy +?
[Defy Android Development] cfanmaoli:
In 2nd-boot mod ,both 525/526 boot successed. (last EP3 cm

7 build )
[Defy Android Development] measel:
care to share some first impressions? any bugs?
[Defy Android Development] balllee:
wifi not work

others ok
[Defy Android Development] cfanmaoli:
How to say that.....just feel like the normal cm7 .:p
[Defy Android Development] Epsylon3:
Yes, there is still a kernel problem regarding the wifi module... But its the first bootable (and moddable so) kernel built from sources... for cm7

to be continued....
[Defy Android Development] XJeFX:
Hi, i need some help to go back to CM7...

I'm currently on CM10 latest build.

I have a Defy red lense with an defy+ sbf (DFPRC_U_4.5.3-109_DPP-6-7 BL5).

I tried almost everything to get CM7 working on my phone but it just bootloops or does nothing at all (stays on red M).

Things i tried:

1 Wipe system/data/cache -> installed cm7 from recovery.

2 Wipe factory reset -> installed cm7 from recovery.

3 flashed sbf again -> root -> recovery -> install cm7 from fresh recovery.

Note: 1 - I'm installing cm7 defy+ version of course, coz of my sbf.

2 - tried 2nd-init and 2nd-boot, still doesn't boot.

When i flash an CM10 2nd-boot rom, phone boots perfect.

This is really drivin me nuts so i just had to post it here.. hopefull someone can help me. Thanks! and sorry for the OT.
[Defy Android Development] balllee:
well my method is ,

1. go to moto(stock) official recovery do the two wipes (this will properly make.your data and cache be in ext3)

2.go to normal recovery(do not wipe in recovery of cm10 ,or.your data or cache will be in ext4 again)just flash cm7 and.kernel..

3.reboot go to lastest recovery(cm7 recovery ) .wipe if you want.reboot

this should work,atleast work for me.

if this method do not work.you may go back.to cm10 or flash a sbf
[Defy Android Development] juan296:
Omg! Cm7 with custom kernel? Excellent job ep3 ;) I LOVE U... lol, no homo :p

Thanks for sharing

Arch Linux User ..
[Defy Android Development] cfanmaoli:
BUG:The cpu overlock settings in bootmenu didn't work.
[Defy Android Development] [] AL []:
Nice! Excellent news.

I knew it was just a question of time before we see some custom kernel around - just didn't expect the first would come from Epsylon3 though.

I thought that between the Swiss Alps, cm9 and the SII developement, we would never see you back here...

Welcome back!! :good:

- - -

OK since I'm here...

It's nothing new and like I did before for ICS, if anyone wants to try out Jelly Bean new animations on cm7,

I made a flashable zip for it but READ ON.

--

Edit: I have no clue if those are from 4.1 or 4.2; I found the files in this thread.

-

-

Pre-requisite

:

using on maniac103's Nov07 build

If you use another build, the framework-res.apk might be different and you will break things or not even be able to boot up if you install this zip.

YOU'VE BEEN WARNED !!

So AGAIN: try this on maniac's

2012 November 7 ONLY

.

But otherwise, it only takes 5 minutes to do the tweak, in just a few simple steps:

- Pull the framework-res.apk from your rom [in: \system\framework];

- decompile it;

- go in you relevant project folder and make sure that these integers have the

following values [in \framework-res\res\values\integers.xml]:

<integer name="config_shortAnimTime">200</integer>
<integer name="config_mediumAnimTime">400</integer>
<integer name="config_longAnimTime">500</integer>
<integer name="config_activityShortDur">150</integer>
<integer name="config_activityDefaultDur">220</integer>

(you 'might' have to add the last two lines above)

- extract the anim folder from my attachment and drag and drop all the xml files over the ones in \framework-res\res\anim\

[answer yes if asked about replacing existing files with same file names];

- recompile and repackage the new apk [preserving the stock 'META-INF' folder, AndroidManifest.xml, classes.dex and the 'assets' folder]

- place it (replace mine) in the zip I gave and flash it;

- also place an untouched framework-res.apk in my undo zip as a safety..

- in the phone's Settings/Display/Animation: select "All animations"

Done and enjoy!
[Defy Android Development] XJeFX:
Wich kernel should i flash?

i have a red lens defy with a defy+ sbf.

Thanks
[Defy Android Development] bhupatib:
I'll try out, thanks :) BTW is this from 4.2 coz I have also added JB transition animation in my JB MakeOver mods but that's from 4.1
[Defy Android Development] bobbyphoenix:
Screen turns on and phone beeps a couple times while charging.

I installed this ROM successfully, and so far I love it. One thing that keeps happening is every time I have it plugged in to charge every couple minutes the screen comes on, and it beeps several times. I tried searching for an answer, but didn't find anything on it. Am I the only one this is happening to? I don't think it's an app because as soon as it booted from install I plugged it in, and within a couple seconds it started beeping. It does about four beeps in a row. I even tried turning off all sounds I could think of, but nothing works. I can mute the phone, and that works, but the screen still comes on. Any help is greatly appreciated.