yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] fefopumper:
OMG!!!

Waiting.... Waiting... Waiting.... Waiting...

You're the man...

Thanks for your job since now
[Defy Android Development] AkkiandDefy:
Sorry for asking, but could you add which languages are in it, just if you have time....
[Defy Android Development] hirano:
Why so butthurt? This is a forum and we are supposed to ask questions. This is not a blog or twitter eske one sided posts.

By the way, I figured out my answers:

1) 3g radio = RIL and its not working

2) sound is working on alpha 2, not released yet.
[Defy Android Development] Passa91:
Chill-out brother! The only person not displaying civility is you.
[Defy Android Development] iaio72:
peace and love brothers!
[Defy Android Development] djkail:
Very good news!!! Good work man... Keep us updated :)
[Defy Android Development] marhensa:
agree..

c'mon guys..

no need to be angry and mad here :)

we all are defy brothers.
[Defy Android Development] jereaa:
YEAAH YOU ARE THE MAN! I WAS EXPECTING THIS!!! I hope this progresses smoothly and hope we'll have a stable CM7 running on defy soon :D
[Defy Android Development] urdestny:
This is a note from the Korean 2nd Init developer.

You may choose to upgrade your 2nd-init boot recovery program to v.0.45. In this version, you do not need to manually boot all the time. Once choosing the desired boot option, it will automatically boot CM7 when you turn on the device next time.
[Defy Android Development] iaio72:
quarx please, can you reupped the last version of rom?

thx!
[Defy Android Development] :
Not to quench your highs, but without a custom kernel I very much doubt the usefulness of this port, as the kernel is 50% of what CyanogenMod about.

For instance, and IIRC, guys were able to used kexec to load another kernel for another Moto phone, but they eventually gave up because they just couldn't get the radio work.

As this stage, I couldn't see any difference between this and that effort. And without a working radio, this is pretty much useless.

That being said, I would be happy to be proved wrong.

Good luck.
[Defy Android Development] marhensa:
maybe this, mate :)

http://xdaforums.com/showpost.php?p=12875067&postcount=75

or

http://xdaforums.com/showpost.php?p=12876221&postcount=78
[Defy Android Development] Rhyr:
So is it possible ti have a dual boot with motorola rom and CM7 rom without flashing every time? :-)
[Defy Android Development] iHedG:
It's baseband switcher for T-Mobile/Vodafon users and Chinese =)

(Who have problem with 2g/3g)
[Defy Android Development] Rhyr:
Really nice idea :-)
[Defy Android Development] Raccroc:
So far so good...everything working (except known, listed issues) since Beta 2. Thx!

Quick CM7 specific question...

Settings > Applications > Double Tap Home Launch

Doesn't appear to be an option in this build. As I have gotten extremely used to launching my browser that way, could anyone point me in the direction of customizing Double Tap Home in CM7?
[Defy Android Development] edition-:
Just updated to beta3, gps is ****ed up

For me it seams to get the signal faster, but it says i'm like 1km from where i am :X

Anyone with the same problem?
[Defy Android Development] AkkiandDefy:
That thing I was surching, too, because I open the Browser with it, too.
[Defy Android Development] carlonchete:
try this facebok app http://www.multiupload.com/1DXTR2Q4N7
[Defy Android Development] Rhyr:
Work great!

Thanks man, you have saved my Social life :D
[Defy Android Development] xift:
after having no problems with the camera at all in beta one, now the preview window is now just black :(

So it seams to be the rom you were coming from that decides if it works or not. I came from orange froyo before updating to beta1 and then beta3 ****ed it up...

But still great work quarks :) If you get the radio done you are my personal hero!

regards,

xift
[Defy Android Development] mussio:
my gps dosnt work i'm using gps test and i only get 2 sat in view and 0 in use.
[Defy Android Development] edition-:
My GPS gets the signal but it says i'm in another road, like 1km from my position.

The gps.conf in /etc/ folder is using NorthAmerica NTP, i changed it to Portugal but i still have the same problem :|

Any help?
[Defy Android Development] Quarx:
Try to edit gpsconfig.xml and location.cfg

gps.conf not use and will be removed

And try this libgps.so (copy to system/lib and reboot)

http://ge.tt/3VARJSQ?c
[Defy Android Development] xift:
reboot solved it :)
[Defy Android Development] viper.:
I hade the same prbolem.. you have to delete the data from camera app /lgcamera in settings/applications/manage applications the selecet camera and press clear data and reboot

GPS takes at least 4 minutes to lock on and it shows wrong position..

@quarx where can we find gpsconfig.xml - location.cfg ?
[Defy Android Development] Quarx:
in system/etc
[Defy Android Development] Dude-01:
Good evening guys. I'm the only one who has got problems with *.wma soundfiles? *.mp3 files are working without any problems but I'm not able to start any *.wma file? Someone else with the same problem?
[Defy Android Development] edition-:
Deleted gps.conf and changed the libgps

Now the gps really stopped working, it doesn't turn on :|, the applications say that is off
[Defy Android Development] mussio:
i didnt delete gps.conf i just replaced the libgps but still having the same symptoms i have about 2-3 sats in view but none in use
[Defy Android Development] edition-:
Can you get me the gps.conf? I forgot to save it xD

Edit: Nevermind got it, lets see if it works

Edit2: Tried with gps.conf again with new libgps, same problem, GPS Test FC and iGO says is turned off :\
[Defy Android Development] mussio:
finally got a lock took about 5 mins and i only have 6 in view and 4 in use seems unstable but it works
[Defy Android Development] edition-:
Strange why mine stopped working after the new lib :\

Edit: Just tried to copy again, GPS really stopped working for me :\

Can you send me your lib mussio?
[Defy Android Development] gkai:
Did u activate the CPU settings overclock/undervolt? What about power usage when sleeping (screen of, data off, phone in deepsleep or min freq (if it does not go into deepsleep, but in your case it seems this issue has been solved).

On my side, best I have been able to do is about 4%/8h, de-activating CPU settings (thats with the wifitest3 kernel) with the kernel not going to deepsleep (only to go to deepsleep with this kernel and radio modules is to set airplane mode). Strangely, it seems that using setvsel does not increase battery use like the bootmenu cpu settings do...With SetVsel 20@300, 33@600, 44@900 I am using roughly the same power when phone is "sleeping" than without any overclock/undervolt. Should be lower because I lowered Vsel at 300 MHz compared to stock, but not really sure.

It is not easy to measure (I have only one phone so I can not let it off longer than 1 night) and the diagnostic tools are not reliable (power tutor uses powr and report incorrectly the screen power draw, CPU spy do not see the new cpu freqs set by SetVSel, stock battery power reports seems accurate for total power use but power by app/process looks suspicious,...)

I am tempted to try the same strategy as you did: go back to boot179-4 or previous kernel and check it with a recent nightly (I like 110918, more recent ones looks a little bit less responsive)

---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------

I tried 110923 and went back to 110918 too. This may be subjective, but indeed 110923 scrolling (horizontal between home screens, vertical in long list like in K9mail or sms view) feeled more choppy indeed. Overall, 110918 feels more responsive in my case too (base kernel was testwifi3 for both nightlies....)
[Defy Android Development] memz180:
I tried 110923 and went back to 110918 too. This may be subjective, but indeed 110923 scrolling (horizontal between home screens, vertical in long list like in K9mail or sms view) feeled more choppy indeed. Overall, 110918 feels more responsive in my case too (base kernel was testwifi3 for both nightlies....)[/QUOTE]

Finally

I thought i was one of the few with this problem i wonder what seems to be degrading the performance all i know is that the 110918 running just perfect with mine just have to wait till this problem is fixed or stick with the one i have. thanks for the response mate.
[Defy Android Development] sp8y:
Yes I tried with the overclock settings disabled so running on stock Moto clocks & when the suspend returned I then enabled the CPU settings in the boot menu to my usual smartass governor running 300/22, 600/32, 900/48.

Haven't noticed any difference with power consumption in either configuration & I normally get 3-4% battery loss during an 8 hourly over night sleep unless suspend kicks in.

I've tried going back to different kernels but the issue still remained & the only thing that has "up to now" sorted it was using the old 177 wifi driver.

So any changes I made that didn't stop the suspend returning were then changed back.

Phone is now on charge so I'll reboot it later & then see how the next 24hours goes.
[Defy Android Development] Johanpro:
LOVE IT :p

I use nightly build 110923

modified CPU to 1200/68

It's perfect for me.

Much more battery life with this then standard Defy with setvsel 1300/68

A big difference was bluetooth battery consumtion

And it all feel much quicker

Thanks

/J
[Defy Android Development] onesss:
It is almost perect,many thanks to all those involved !!!
[Defy Android Development] m-one:
Helpful or not:

My phone is now running for 47hrs and has 28% battery left. CPU Spy shows:

1000 (vsel 54) Mhz ~1 hr

600 (vsel 40) Mhz ~ 10 min

300 (vsel 20) Mhz ~ 3 hrs

Deep Sleep ~ 43 hrs

Using 179-2 CEE with 110921 nightly. Enabled overclocking in bootmenu (should I leave it as is or change to disabled - i have setvsel installed?).
[Defy Android Development] zakoo2:
the lens is capable, the bottleneck is the SOC module, which is not fast enough to handle 1080p or even 720p.
[Defy Android Development] Sigma47:
Lookin good!!!

I did a complete wipe and reinstall of RC 1.5 and then the 9/23/2011 nightly... gotta say this is looking promising! Thanks for the sol'ns devs!
[Defy Android Development] ccav2000:
New nightly cm7-110925-1407-NIGHTLY, camera is not working (green lens), wiping camera app data has no effect either. The preview is totally black.

Avoid this nightly if you care about Camera.

---------- Post added at 07:33 PM ---------- Previous post was at 06:36 PM ----------

Perhaps this commit here is fixing it, we'll know with the next nightly.
[Defy Android Development] ofmb:
black preview also in red lens
[Defy Android Development] gkai:
AFAIK, OV5642 is the SOC module, the lens is of unknown type and likely to change, given the various lens "colors" which are not always in sync with the underlying camera module. Imho there is 3 possible reasons for the lack of performance of the OV5642 in Defy:

- the module is mounted on the board using a low-bandwidth interface, maybe using only a few connection enough to use the OV5642 in a sort of "compatibility" mode or "generic" mode, a mode which is far from the advertised capabilities of the module. Then green lens defy owner (like me) are doomed, quality will never be much better than what we have.

- The module have all its connection linked to the OMAP3630, but there is some incompatibilities between this system on a chip and the SOC camera module, an incompatiblity that motorola was able to fix only using the "generic" low performance mode of the SOC module. They may not have tried hard enough, or maybe did not had enough time. We will probably not have more success...except maybe if some people knowing very well OV5642 and/or OMAP3630 low level driver hack the defy kernel (which would demand an open bootloader)

- the module is fully physically linked and there is no incompatibility between it and Defy CPU. But the moto engineers were asked by the management to produce a mid-end phone with no focus on photo/video. They rushed the product as soon as it worked, and at the time of the first update (or even before), defy+ was planned and keeping the SOC support in the poor state it is was decided. Then, we have a good chance to have a much better cam (maybe better than red one) if the bootloader is unlocked. If it is not, then even in this situation I wold not count on it, because it has not occured till now: a few people had time to try to hack loadable module and have tried already to improve video/pic quality, without much success...
[Defy Android Development] mick711:
And Walk to text don't work can't initialise camera just see black . But it's better than 23 Nightly for me because with the 23 i have FC with some apps.
[Defy Android Development] vap_66:
Are there any other ways to disable the LED light during battery charging, besides editing the ro.battery_light string in /system/build.prop and changing it to false? I'm using RC 1.5.

Also, thank you for this great ROM :D.
[Defy Android Development] marhensa:
actually changing the build.prop value is pretty easy mate..

if you don't have a handy app for changing that value, change the value of build.prop file within the zip before you flash it.

Sent from XDA-Developers Android Application​
[Defy Android Development] 2Pints:
Im on the 110923-0710 nightly, and im still having some issues with the wifi failing to conect, the only solution that ive found is this one below:

but each time i do that i need to re-enter all the passwords for each wifi network :(
[Defy Android Development] mick711:
Yes but it's easy , create text files with all password and copy past ;)
[Defy Android Development] RDrg:
I'll return to the previous build (the 09.23 one) because of the black preview of the camera :-(
[Defy Android Development] kgyuri:
+ 1 Not working.
[Defy Android Development] mick711:
Yes Camera don't work on Bayer device but i don't return to 23 Nightly i don't have FC with this built and i use my defy for Phone GPS and Internet on wifi but i would like that camera work :D
[Defy Android Development] juan296:
Hi epsy, I'm on rc 1.5, sometimes the fm radio turn off itself, can you fix this bug? :)
[Defy Android Development] Ricardo_Is:
Terminal Emulator type:

su

setprop persist.sys.charge_led off

reboot

EDIT: Thanks @AL, sometimes I type wrong words with Swype
[Defy Android Development] [] AL []:
sorry to be the third reply to this, but "f"missing and to be more exhausitve, here's what Maniac wrote on this 2 weeks ago:

Instead of setting ro.battery_light to true or false in build.prop, you can do the following in a shell (adb shell or terminal emulator):

•To switch charge LED off: setprop persist.sys.charge_led off

•To use white LED while charging: setprop persist.sys.charge_led white

•To use the existing yellowish mix: setprop persist.sys.charge_led rgb

This setting will be kept over new nightly flashes (until a data wipe).
[Defy Android Development] juan296:
thanks for the information, but i did this step and the led is blinking now... really, can i disable this? i don't want see this turn on in the night.

Thanks :)
[Defy Android Development] Ricardo_Is:
Worked for me.
[Defy Android Development] SpookyAwol:
Camera not working in 110924 and (as noted) 110925-1407
[Defy Android Development] [] AL []:
idk why this happens.

Have you tried to go to CM7 Settings/Interface/LED notifications/Advanced and Reset?

Otherwise, try the build.prop method or switch to white and then off again.

Just shooting in the dark here...hehehe
[Defy Android Development] maniac103:
I am not entirely sure (can't check right now), but I think in RC 1.5 it's still ro.battery_light in build.prop. The persistent property was added later.
[Defy Android Development] memz180:
Just updated to the later 110925 still a little choppy while scrolling but i can say its a little better camera not working at all and also i like the new stable recovery for the 2nd init anyone know what a tar backup is it comes down at the bottom hows that work?

So if we make a backup is it a different format can that version of 2nd init recover the tar if the backup is made?

Cheers
[Defy Android Development] remuseu:
i can confirm that camera is working in the 110926 nightly :)
[Defy Android Development] gkai:
Could you explain where you found the old wifi driver and how you included it in the 179-2 kernel modules? I'd like to replicate your work if it is not too difficult. I tried the 179-2 kernel and have the same behavior than the wifitest3 one :-( The difference are that it seems maybe just a tad smoother/more responsive (but maybe a placebo effect ;-) ), and it seems to use much much more power when wifi is active (i.e. when downloading/uploading, not when just on and inactive). Regarding power use, I have the same problem than with wifitest3: when using CPU settings, power draw climbs to 10-12%/8h...
[Defy Android Development] ccav2000:
Thanks for testing and reporting, I'll install it later.
[Defy Android Development] ofmb:
I concur.

red lens camera is working

http://www.youtube.com/watch?v=cQ_fnaJDsgA
[Defy Android Development] Cocolopes:
I wonder if this can be done on cm7? http://xdaforums.com/showthread.php?p=17582887
[Defy Android Development] ccav2000:
The new nightly seems to be missing some code for the new Ring Style Lockscreen. When I installed the nightly, the new style was active, so I went to the CyanogenMod options to check, and the new style is not included in the list. I selected the my old rotary one, now there is no way to go back to new Ring Style lockscreen.
[Defy Android Development] remuseu:
i rly dont see the point of that...u have some many launchers that can do something like that(not rly the notification bar, but one button all favorite apps)

what do u use ur home screens for ? just to look at the wallpaper ? :|
[Defy Android Development] sp8y:
Yes certainly - it's easy enough & you'll need a root explorer to change the permissions & also to change the ownership to "root" - here's a good guide that []AL[] posted some time ago.

http://xdaforums.com/showpost.php?p=16817819&postcount=10352

Have a look on epsy3 server for the BOOT177 file dated 110615-1323 & extract the tiwlan_drv.
[Defy Android Development] ofmb:
i think he can delete all the files except tiwlan_drv and flash. it's much easier
[Defy Android Development] sp8y:
Quick update from me - now 22 hours since battery charge & reboot & it was going OK (38 hours prior to this with no issue).

Suspend had only used 2mins 20secs until 2 hours ago & it just started using up a bit more CPU time - now sits at 7mins 53secs so it looks like the issue is still there BUT it does seem much better for me with this configuration.
[Defy Android Development] bergerac81:
I have flashed my defy just come back from assistance ( changed mb) with cm7 2.3.5 but now the battery is discharged after six hours of activity. Where is the problem? ( The assistance has changed also the battery)

TKS
[Defy Android Development] sg3707:
May be this has been told earlier also but can any one please let me know how to confirm if the drain is becasue of the suspend bug
[Defy Android Development] gkai:
Or I can make my special zip file, based on my prefered nightly with a few customization (I have customized some fonts and the battery indicator, adding a wifi module to it would be easy) :-)
[Defy Android Development] Sigray:
Whats the better for daily use http://defy.tanguy.tk/ nightlies or from the cyanogenmod website?
[Defy Android Development] sp8y:
I just use the tools that are bundled with CM7.

In the spare parts app select battery history> other usage> CPU usage - suspend if present will show up in here. What you want to see is low usage - any thing showing usage in hours is not good.

Also in applications> battery use keep an eye on the Android OS - if it starts to show a lot of use then it will tie in with the suspend use.

Also CPU Spy (from the market) can help to show whether the phone is getting into deep sleep - suspend prevents this so the phone would run more at 300mhz than it should.
[Defy Android Development] ccav2000:
Question: in the 26/09 nightly, can anyone select "Ring" as the lockscreen type?
[Defy Android Development] blackice_bg:
setprop persist.sys.charge_led white does not work for me?
[Defy Android Development] cohen84:
I updated the phone to 26.9 version and now i'm stucking on the google screen.

i can't enter to recovery and i went to the power_up+vol_down menu and done clear cach and data, still stuck :eek:

what can i do?? :confused::confused::confused::confused:
[Defy Android Development] memz180:
What version did you have previous to the update
[Defy Android Development] gkai:
Do you think I can change the tiwlan_drv.ko in system/lib/modules of a normal nightly (i.e. one that do not change the kernel), or the modules are updated only by the bootxxx nightlies? Becuase I tried to customize my favorite nightly (110918) and it worked for fonts/status bar, but I am not sure tiwlan_drv has been replaced. At least, the deppsleep issue is not resolved, while my base kernel is the 179-2. If it does not work, I have to customize a kernel nightly, and still apply my 110918 nightly afterward :(
[Defy Android Development] maniac103:
What version are you on?
[Defy Android Development] blackice_bg:
7.1.0 RC 1.5
[Defy Android Development] bergerac81:
Help me please
[Defy Android Development] UEman:
I can't select the ring-lockscreen.
[Defy Android Development] ccav2000:
Thank you, so it is not just me that I cannot see this option. I reported an issue to Epsylon3, but I wanted to be sure it is not happening only to me.
[Defy Android Development] [] AL []:
Hmmm! though one!...flip the coin...head: it doesn't ...right?

Well, I guess that if you say so is that you've tried the change through terminal as suggested in the last few pages.

Didn't you notice that maniac mentioned that this option was implemented some times after RC1.5? On which build did you try this on?

But nevertheless, you should also have seen that it's been suggested to do the change through a build.prop editing here, here, here and here...

There's more than one way to do it, but I'd go this way:

With RootExplorer navigate to "/system/" directory mount it as Read/Write (R/W) and open "build.prop" file with text editor, locate the "ro.battery_light=true" string and change it to "ro.battery_light=false". Save the file, remount the directory to read only (R/O) exit and reboot.

---------- Post added at 09:49 PM ---------- Previous post was at 09:11 PM ----------

Since you DID enter recovery [the stock one] and pretty much got rid of your settings and all your installed apps with your "power_up+vol_down" move, you should now start back from scratch and do the "power_up+vol_up" thing.

Unless you've flashed a Gingerbread full sbf the last time,

in bootloader mode, reflash a Froyo full sbf with RSD lite,

turn USB debugging ON,

root it,

reboot,

install 2ndinit,

turn USB debugging OFF,

reboot select "normal boot",

reboot again and this time vol_down ONLY at the blue led (6-7 seconds after powering up)

enter last stable [custom] recovery wipe all (cache, data and Dalvik) and install RC1.5 from zip on SD,

wipe battery stats (and optionally wipe cache and Dalvik again).

reboot and directly go and set your correct setting in Defy Baseband Switcher apk.

Later, you can re-enter custom recovery the same way to install the nightly of your choice and this time, only wipe cache and Dalvik cache -not data.

Read the big green "F.A.Q." link on the OP (post#1) of this thread carefully.