yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Llamatron:
In fact it's not big pictures, it's lottery: default behaviour is halfing the size until it fits, so if for example it is at 648x384 at some try (still bigger than 640x480), next try will be 324x192, and it's the resolution that will be used as it's now smaller than 640x480.

You probably picked the zip before I changed to the flashable, it just had directory structure. There's a meta-inf in the one currently attached but without signature, the script is different than yours too, I'll try to redo it with your tutorial when I'll have a bit of time.

You're very welcome, it's what these forums are for I think ;) and thanks to you for the infos about making flashable zips.

Also one last thing, 640x480 might seem a bit small for our smartphones, but some dumbphones who can receive MMS won't display anything bigger.
[Defy Android Development] maniac103:
Good job in trying this. I'll use the ICS scaling code in the next build.

So that proximity sensor problem only exists in landscape? LeopardSurd, can you confirm that?

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] LeopardSurd:
Not exactly, the bug appears no matter what situation (landscape, portrait, gravitational sensor). The option to force screen to open after the call ends is not a solution. Maybe I want to dictate a telephone number during a call but I cannot do it because I use the option „power button to end calls”.

I think this is the last annoying bug of CM7 and is pretty old.
[Defy Android Development] popadic022:
On my phone, when is in lanscape mode proximity sensor work (when cover sensor with hand-screen off, move hand-screen on), but in portrait mode i cant do that. But sometimes i must rotate phone few times to portrait-lanscape mode to power on screen. For me its only annoying bug of CM7.
[Defy Android Development] kapil_dheer:
EXT formats

I'm on Maniac103's latest nightly. I'm constantly following Quarx's 4.1.2 thread. Recently, ext file format support has been added to the ROM.

What i want to know is.....are the formats NTFS, ext2, ext3, ext4 compatible with CM7.2 we are using?

FAT32 & NTFS is compatible with windows..... any ways to make ext2,3,4 compatible with WINDOWS7?
[Defy Android Development] TJKV:
Regarding Windows 7, that's a question for google, not xda. About CM7, no because CM7 doesn't have custom kernel support (yet?)
[Defy Android Development] nolimitzz:
i can confirm that proximity sensor problem is there in portrait, to explain:

while in call, you take the phone away from your ear to end the call or do anything else, the screen stays off. it is an annoying bug i hope it gets solved.
[Defy Android Development] popadic022:
but only on cm7, not on cm9 and stock.
[Defy Android Development] LeopardSurd:
That's right. Now I use the stock GB rom and there is no such a problem.
[Defy Android Development] popadic022:
now i use cm9 and there is no problem. i would be nice if maniac103 or someone else can fix this problem. cm7 is better than cm9 for me, but dont use cm7 because that bug.
[Defy Android Development] maniac103:
What are your related settings under Settings -> Phone settings? I don't have the problem, so there must be something that triggers it.

I assume you've tested the proximity sensor (driver) under CM7 with one of the sensor tester apps from the market?

Also, do you see the proximity sensor being enabled (glimming red LED)?

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] popadic022:
my phone settings-phone settings is default, only check vibrate on start and end call (maybe that is problem). Red LED lamp glow only in landscape mode.
[Defy Android Development] maniac103:
I guess it works in landscape then?

But how do you get to landscape with default settings? IIRC the default settings allow portrait only.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] popadic022:
If you mean that the screen is rotate to landscape mode during call, answer is no (sceen is always in portrait mode during call). When phone is near ear it's in landscape mode (not screen), when rotate phone to landscape mode during call (red led lamp glow-screen off), but when i want to end call or to do other operation (go to menu,...) red led lamp not glow-screen is stiil off. so, i cant end call,go to phone menu....call is end when other side end call :(
[Defy Android Development] juried:
I have two defys, one defy and one defy+; both with this ROM. I checked today phoning between these two. The defy does not seem to have the sensor bug. My defy+ has it sometimes. I checked the sensor performance on the defy+ with an app from G play and it works as it should. It looks as if the phone app does not pick the sensor correctly on some occasions. I do not have landscape enabled in phone app.

I have never noticed a dimply glowing red led at the proximity...?
[Defy Android Development] popadic022:
i also have defy plus, maybe its problem with defy plus version?
[Defy Android Development] juried:
I have also found that if the screen stays dark after removing from ear, putting a finger on the proximity sensor for a moment will then switch the screen on.

Perhaps the event of prox. sensor is sometimes not detected due to other tasks having higher priority, and it drops off the end of the stack, or maybe the event stack is full or something...?
[Defy Android Development] jackajay:
i am also facing the same issue with my defy+ using maniac's cm7.2 rom.battery drains very badly :( if anyone has solution to this please let me know
[Defy Android Development] juried:
Read the "Battery drops explained" thread in general section.
[Defy Android Development] nolimitzz:
i have a red lense Defy and i have the problem.
[Defy Android Development] maniac103:
Ah, now that's starting to form a pattern. As I have a regular Defy, I don't have the problem if it's Defy+ only. Looking at the sensor HAL, I think I know what the problem is. I'll think about what the best fix for it is.

EDIT: Can you check whether the attached sensor HAL (unpack and copy to /system/lib/hw - Defy+ only!) works better?
[Defy Android Development] popadic022:
it would be nice if you can fix that. so, its only problem on defy plus :D?
[Defy Android Development] LeopardSurd:
thanks, I'll test it today on my Defy+.

L.E.: it doesn't work. The screen don't go off during a call.
[Defy Android Development] maniac103:
Ok. Does the attachment work better?
[Defy Android Development] LeopardSurd:
Now, it's working. I'll test it few days. Only this way can I tell you if the bug is gone.

:good:
[Defy Android Development] oSandmaNo:
Will try this on fuzzs build.

Edit:

Awesome people here! Works better than stock :D

Thank you maniac103!! :)

This was a really irritating bug.
[Defy Android Development] FINEEEEE:
What bug?...

Desde cualquier lugar de mi ciudad con el 4x4 de motorola
[Defy Android Development] [] AL []:
The one that will probably be fixed in maniac's next build...along with better mms pics attachment...

But if you're serious with your question, I'll still not answer it and say read back the last two pages or so...dev thread ;p

I guess I'll figure out if and when this fix comes out but still I wonder if this sensors.jordan.so will be only working for defy+ phones -> will it be necessary to replace for the old file for red lenses defy running plus builds?

I'll not going to claim a fix here, but -not to name him(/her?)- oSandmaNo just PM'd me and told me that an old battd file that I posted almost a year ago works better for him against battery drops on his Defy+. I've just updated an old zip to work on recent nightly here...might worth a try for you guys...

defy+ only
[Defy Android Development] LeopardSurd:
Just keep testing it. I test it on the last nightly from the official CM7 build. Until now it reacts better. Let's see if everithing is all right. :good:
[Defy Android Development] maniac103:
It's needed for every phone running the Defy+ build (actually, it's needed for every phone running the Defy+ = Gingerbread kernel).
[Defy Android Development] popadic022:
does new sensor fix work? no more prox.sensor "bug"? :D
[Defy Android Development] juried:
OK I put the file on my defy+, now I have not seen the bug again testing under the same conditions within minutes of each other. Before replacing the file, I would get the bug say once every 5th time removing from ear, now none.

So it looks like a goer! :good:

---------- Post added at 10:42 AM ---------- Previous post was at 09:42 AM ----------

I flashed this on my defy+ and there is one issue: Swiftkey does not recognise it as an SMS app - with the version that comes with this ROM, the smiley key is separate and easy to use; with this MMS.apk, the smiley is integrated with the enter key, so not so quick and easy to use.
[Defy Android Development] [] AL []:
OK, well thanks - I guess I've explained myself badly..

I realize that it is needed for both phone types. I was just wondering that since that it seems to be a bug only on Defy+ phones, if your new file with the fix would not risk of breaking something with the old Defy (which in turn would need to use the old (last build's) sensors.jordan.so). But nevermind; I know the fix if it will and really, I should have just tried the file you've just posted... silly me [it was late last night] :cyclops:

Well, I don't use Swiftkey so I wouldn't really know -thanks for mentioning this anyway.

Although, the issue I see here is that people flash things without reading ... ;)

You see that link in the middle of your quoted text: and posted here 2 weeks ago ? well, there I clearly wrote: "I did a few changes already and I must also add that I've tweaked it to get the "enter" key [allows writing sms on multiple lines] instead of the smileys key."... :highfive:

[if you really want to try the original -with the smiley button- let me know and I'll try to find or tweak it back for you][in case you don't know; if you want to get the cm7 stock one; extract it from the nightly zip and push it in /system/app + set permissions or just re-install the nightly without wiping data]
[Defy Android Development] juried:
Hmm, I see... I like the bubble text version, that's the main reason I chose it... the scaled MMS pics is of no importance to me. I don't use the themed icons either... so should I just flash the bubble version in the earlier post?
[Defy Android Development] [] AL []:
read again! Now I don't feel like looking for the smiley one... And you can just use the menu button and get a much more convenient than stock popup window for them...

Edit:

In blue text just above: I think it was pretty clear.. So that's why I don't get why you asked that last question and why my mood wasn't so good. The attachment there is even called -sorry for the typo-: :"Mms-Sony_mod_no_simley.apk"... So I just get tired of spoon feeding sometimes...

Anyway, here's the original, untouched, WITH smiley button and without llamatron's tweak for mms pics Mms.apk from a Sony forum [sorry lost the link of it..]. And you'll then see that I themed more than the app icon... You'll have to change the name and push it manually - no flashable zip this time...I got two babies of my own here two take care of so I hope you understand..
[Defy Android Development] juried:
I suspect we are talking past each other. But since I have read and re-read your reference and not gotten much further at all, and you don't feel to be in a very helpful mood either, just forget it.
[Defy Android Development] Llamatron:
New maniac build is up

and I'm realising I might not be using the right sources, isn't the code below supposed to sync me with maniac's gingerbread sources?

repo init -u https://github.com/maniac103/android.git -b gingerbread
repo sync -c
[Defy Android Development] maniac103:
Yes, that should be correct. I've also forked the MMS app now, so you should get the changed resizing code with that command as well.

BTW, the new nightly contains said new resizing code and the Defy+ proximity sensor fix.
[Defy Android Development] Llamatron:
Guess it's because I have a different Mms code, right after you uploaded the new builds zips I did a sync that didn't change the mms_config.xml according to your "Use stock user agent" commit, nor my modified files. Now I can't sync anything I got error: .repo/manifests/: contains uncommitted changes.

Did you find out why the images are scaled by 0.75 increments?
[Defy Android Development] popadic022:
just install new maniac103 build and again great built (speed, stability,...) and old sensor "bug" mb526 :( it's not like in previous version's it's worked better, but it's still there, every 6-8th time for me (when move phone from ear). does anyone else have the same issue with fixed sensor with new release or just me (defy+ mb526)?
[Defy Android Development] LeopardSurd:
I'm still on tthe last official CM7 nightly for Defy+ and I use the sensors from maniac attached here in forum. I confirm that the bug you said is not dead after almost 2 days of testing.
[Defy Android Development] popadic022:
here is a video which i made how proximity sensor work on my defy plus: http://www.youtube.com/watch?v=LdegcyhnEKQ&feature=youtu.be sometimes work, sometimes won't :(
[Defy Android Development] xabierd:
I use orange baseband in spain and it works OK. My cm7(beta3) is installed over nordic fixed sbf. But i had a few issues with 2g(not 3,5g) so i switched to orange and it works OK
[Defy Android Development] psicodelico:
When the data icon is not Green that mean Google's push service is not connected, so you can't for example download a file from market but you can access you favorite webpage :)
[Defy Android Development] Quarx:
Please try this update.zip for GPS.:)
[Defy Android Development] AkkiandDefy:
Thanks for the zip
[Defy Android Development] gunichou:
Well since i've installed this rom i'm so happy :)

I just have one problem: On my Win7 64 bit, Usb mtp drivers are bad and i can't use the portal mode.

I've uninstalled all drivers and motorola programs on PC. That's allways wrong.

Sommeone have an idea ?
[Defy Android Development] Quarx:
GPS -> Post # 1716 (too proprietary code of libgps )

Fm radio - Many problems with closed modules (libaudio etc) - w8

Difficult to work with closed modules.

Portal mode don't work.
[Defy Android Development] AkkiandDefy:
I saw the post to late sorry

EDIT: I tested the zip and must say my GPS is slower as before.

It installs the north america pool config

Sent from my CM-7 Defy with XDA Premium
[Defy Android Development] Quarx:
Motorola(Broadcom) GPS don't use gps.conf.

gps.conf need only for Qualcomm gps (libloc)

Near the window, I found six satellites and fixed by 1-1.5min with 3 satellites.

Accuracy 15.1m
[Defy Android Development] adi4motion:
i stayed near the window aprox 5 min, no fix

1 satelite found (on froyo 9-10)

with wi-fi on 3 sats found but still no fix --- i take this back, i don't think it has to do with the wifi

however, on froyo, if the compass wasn't well calibrated i was having troubles getting a fix, now the compass seems slow and buggy, maybe it's related?!

edit: oh, and auto-brightness seems to be working but it takes awfull lot of time to make the changes

edit 2:

@Quarx

milestone's gps is different? can't you use milestone's CM 7 sources ?
[Defy Android Development] Rhyr:
What about the upgrade to CM 7.0.2? :-)
[Defy Android Development] tnicko:
Yup, of course I checked that ;)
[Defy Android Development] Quarx:
In Beta3 gps from milestone.

in latest update.zip, gps from defy.

libgps.so is proprietary module and do not have sources.
[Defy Android Development] gkrananth:
Hi Quarx

I am getting this error when i do this command. what causing the problem

Anantharaj-Govindarajs-MacBook-Pro:WORKING_DIRECTORY ananth$ repo init -u git://github.com/Quarx2k/android.git -b gingerbread

Traceback (most recent call last):

File "/Users/ananth/bin/repo", line 603, in <module>

main(sys.argv[1:])

File "/Users/ananth/bin/repo", line 570, in main

_Init(args)

File "/Users/ananth/bin/repo", line 184, in _Init

_CheckGitVersion()

File "/Users/ananth/bin/repo", line 213, in _CheckGitVersion

proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)

File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/subprocess.py", line 595, in __init__

File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/subprocess.py", line 1106, in _execute_child

OSError: [Errno 2] No such file or directory
[Defy Android Development] tgzw:
gps ，2 minutes belongs to the normal，The key is to agps
[Defy Android Development] danielck78:
Hi Quarx,

I am having problem with my screen during and after call. Unable to bring back the screen. It was just blank. I cannot press any button or do anything. It can only reboot it by taking out the battery. Can you tell me what's wrong?
[Defy Android Development] rrhg:
Hi

Anyone can post the link for gps fix with region (asia, europe africa etc)? I don' t remember where i find it :)

Thks
[Defy Android Development] AkkiandDefy:
FasterFix in the Market i posted it on page 123

Sent from my CM-7 Defy with XDA Premium
[Defy Android Development] ketonkss4:
Sorry if this has already been adressed but.. can you make backup nandroids of this rom like a regular rom?
[Defy Android Development] noxunas:
Is there any success for :

- aGps ?

- FM Radio ?

- autocontrast ?
[Defy Android Development] pl4cid:
Yes, look in the first post and be patient ;)
[Defy Android Development] maniac103:
And when testing the proximity sensor using a tester app, e. g. MySensors, it works 100% reliable? I just can't imagine there's a proximity sensor usage problem in the phone app, as it works absolutely fine for the normal Defy.

Edit: And was the video made with the old or the new HAL?

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] popadic022:
New, download your last release and install then make video. Maybe on normal defy work's ok, but on defy + wont :(
[Defy Android Development] juried:
I tested some more...

the bug seems to work both ways. Sometimes it won't switch the screen off either. Sometimes it becomes unresponsive; then when I turn the phone to landscape (but I had portrait mode fixed in these tests) then immediately the sensor becomes responsive again.

I looked at it with My Android Sensors also, also during a call when it was unresponsive but it was perfectly responsive in My Android Sensors. Then back to the phone call which was still ongoing, unresponsive again. Then turn it to landscape, instantly responsive again.
[Defy Android Development] oSandmaNo:
I flashed the cm7 from get.cm and used your proximity fix. The bug came back!! :(

But in zdevice test it works fine and quickly too.
[Defy Android Development] maniac103:
What do you mean by 'came back'? Was it not present in the unmodified get.cm build?

EDIT: I've uploaded a build with proximity sensor debug output here. If anyone of you Defy+ users knows how to use adb, it would be great if you could do the following:

install the build

run adb logcat on a connected PC

start call

try to reproduce the problem while adding markers to logcat describing what you did ('covered sensor', 'uncovered sensor' etc.)

send the logcat output including markers to me

That way, we'll hopefully get to the bottom of this.
[Defy Android Development] oSandmaNo:
'Came back' means it didn't get fixed :(

I don't know if unmodified was working. I applied the fix as soon as I flashed. In the fuzz build your fix worked nicely.
[Defy Android Development] [] AL []:
I quick comment about the new Mms resizing changes and 2 off-topic tweaks for whoever would be interested in trying.

So first the Mms:

[See pic1] The 20121107 build from maniac gives me smaller attachment and slightly lower visual quality than with Llamatron's tweak.

Just a primarily result as this is only tested with one [I have to pay for those mmses..!!] fairly large picture - more testing might be required.

Now the off topic part..:

Two tweaks that I've tried today:

1- I've made the contact picture bigger in the dialer. Made it 40% wider than stock so double in area size. Can't go any bigger without overlaping the hold button or getting the conversation timmer bumped away [pic2 and cwm zip attached]

2- I've asked the question before as to why the sms compose window is so small (only 3 lines max) in portrait mode when there is space above the keyboard.. So I found how to increase this and I've made it 7-line high max. I've also included the NO SMILEY BUTTON tweak which makes perfect perfect sense with that tweak... This is made using the Mms.apk from maniac's 20121107 build also.

Enjoy...or not - but please don't bite the hand that feeds you ;)

/ A

Edit (Nov 15th) - new Phone.apk zip:

FIXED: 1- I previously had to remove some language strings [deleted the whole da, es, fi, it, lv, nb, ru, sv and zh-rTW (9) languages in fact] in order to compile the Phone.apk properly; 2- had the wrong framework for compiling and the "Enable Blacklisting" option was gone; and 3- the contact picture is now lower and not hiding the text beside the hold button.
[Defy Android Development] juried:
I put another file on my defy+ and so far it is working 100%... please try this, place as before in /system/lib/hw.
[Defy Android Development] maniac103:
That's the stock one, right?
[Defy Android Development] popadic022:
i try from stock and cm9, doesnt work. same problem.
[Defy Android Development] juried:
I pulled it from Walter's MS2G4. I did the same sort of tests and so far so good. I just checked again, still good. It occasionally takes a second or two to respond but it always does, mostly immediately.
[Defy Android Development] maniac103:
But as we can't pull any actual fixes from it, this conclusion doesn't help much, though. From the text strings visible in the binary, it looks like it pretty much does what our sensor lib now does.

I would prefer if we could debug our sensor lib to get to the bottom of the problem (see a few posts above).
[Defy Android Development] kapil_dheer:
A small question out of context.....I heard people pulling a logcat while booting......I need to do the same......I read somewhere to activate adb in bootmenu , connect the cable , run adb logcat command on pc from the adb.exe folder and finally reboot.

During reboot, do not get any logs, the pc waits for the device... only after proper bootup, I immediately get logs. Is it normal?

Referred to various threads but this thing remains unclear. Please help me understand.
[Defy Android Development] ktmbikerman:
Thanks Al, I'll try this on my wife's defy.
[Defy Android Development] oSandmaNo:
Sorry about my previous post! The fix works fine during a call. Its when the call gets disconnected the sensor stops working(or the screen simply doesn't turn on)
[Defy Android Development] popadic022:
i think the problem isn't in sensor (if same sensor works ok in stock rom, cm9) then the problem is something other. i am not advanced to know why sensor sometimes work some times not, but someone probably know. maybe we can ask quarx or some other developer?
[Defy Android Development] maniac103:
It surely is a software problem. Only way to find out is to debug it (see my request a few posts above).
[Defy Android Development] juan296:
Why Quarx or other developer?

Maniac is a GREAT DEVELOPER, if he can't fix this failure, just wait.. he will be fixing in some moment!

Arch Linux User ..
[Defy Android Development] juried:
Unfortunately I won't be able to help in a hurry. I haven't used adb before so would have to do a bit of learning first, but I am going overseas for several weeks.

But I don't see what the problem is with the file I posted - if it works then why can't it be included in the next release...? Or am I missing something? I have tested it 3 times and zero problems.
[Defy Android Development] maniac103:
I won't replace 99% working source code by some random binary.

You can also grab a log with the CatLog app. If you can tell me the timestamps of your actions (just check your watch ;) ), that'd be good.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] juried:
OK I will do the catlog thing in a few hours from now. Will first install your debug version right?