yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] hailmary:
i recommend the baddest bad ass kang of maniac103 .... https://github.com/maniac103/android_device_motorola_jordan/downloads#download_168103
[Defy Android Development] coelho_:
yes I use it ......work fine !
[Defy Android Development] TJKV:
About the blinking led... On the older nightlies, maybe before a fortnight, it never blinked and I couldn't make it blink either, it only stayed on all the time till notif was cleared. I had tried in settings-> sound -> blink notif led, and also in cyanogenmod settings -> interface -> notif led and changing category and app settings there. The settings within third party apps like go sms also never did anything. It always stayed on. But the colour could be changed easily...

Now it only blinks, cannot change to stay on always and selecting different blink speeds doesn't really do anything. Something must be borked...

I'll try maniac's kang and see later...
[Defy Android Development] twa_priv:
New quarx nightly is up ... the defy+ nightly now boots fine with the 4.5.3-109 kernel. Thanks quarx.
[Defy Android Development] sakitobaki:
Led blinking is ok now.

Camera is also ok so far :-)

Defy red lense

German Vodafone Froyo based

CM7.2 Nightly 20120316
[Defy Android Development] Deonix:
Downgrade

I am after 2 weeks of stable ICS goodiness. I am kind of missing the fast CM7. CM9 runs smooth with good battery but it needs work, and that means time.

I am running the CM7 froyo Kernel.

It's gonna be Data Wipe, Cache Wipe (&dalvick) then flash what nightly i want no?
[Defy Android Development] sakitobaki:
you are still on cm9?

if you are on cm9 froyo kernel, then yes.

don't forget gapps for cm7... and to wipe cache and dalvik after.
[Defy Android Development] coolzarjun:
Maniac kang vs quarx latest nightly... which one you guys recommend ??

Please reply ..I need to flash one NOW

Sent from my DEFY
[Defy Android Development] hailmary:
thats pretty hard to weigh over. ive been using maniac. all good.

now im using quarx latest & its pretty much the same in terms of performance. --try both & see for urself,its the best thing to do in ur case.
[Defy Android Development] measel:
Well, I'm trying to keep track of stuff in my thread but what is really bothering me, is that I have no real clue about the differences. I know that the guys merge most of the improvements at some point so it's hard to decide which build to use. But I think right now bug tracking is really really hard because of all the different KANGS/builds/forks or whatever.

Especially for the Defy+/Bayer/Redlens build from Quarx it would be great to know if there is a significant difference to the Froyo builds.
[Defy Android Development] sakitobaki:
nightly by quarx 16.03.2012.

All I can say is that Quarx 20120316 nightly for Defy working great on my red lense.

Maybe the best of his nightlies so far.

Camera is working great except of some strange stripes showing sometimes in top right corner of capturing preview, but there are non of them on taken pictures (I remember similiar bug on stock eclair with those stripes, but on videorecording), video recording is great (so far I had only 2 short recordings), led notification is fixed and battery is great...

Also when selecting photo in gallery for viewing and when it starts to zoom for preview, some black dirt junk can be seen.

But as soon as zooming is finished, photo is ok and without any error.

---------- Post added at 03:46 PM ---------- Previous post was at 02:53 PM ----------

i've just edited my previous post because of some more issues...
[Defy Android Development] mihovil13:
What new stuff or changes does 1603 include?

DEFYing the Android planet with ICS
[Defy Android Development] hailmary:
it doesnt give any problems:D,just like maniacs latest kang.

only big noticeable difference is the (moto's nuance voice commander) - maniac has it & quarx dont - most of all both can play GTA3 & angry birds too LOLOLOLOL

i think u might as well just check the commits they make,its pretty hard to explain in a laymans manner so just here is it "analayze it yourself"...

im a bit lazy to elaborate further...

quarx: https://github.com/Quarx2k/android_device_motorola_jordan/tree/gingerbread

maniac: https://github.com/maniac103/android_device_motorola_jordan
[Defy Android Development] sakitobaki:
And no volume keys mute option :D

I'm not sure is there something new in call settings but I like them a lot.

Defy red lense

German Vodafone Froyo based

CM7.2 Nightly 20120316
[Defy Android Development] elguaxo:
What is kineto-cm7-defy-signed.zip? It was just uploaded by maniac103: https://github.com/maniac103/android_device_motorola_jordan/downloads
[Defy Android Development] maniac103:
I've posted a new nightly to my github account, plus a kineto addon package. It should give working T-Mobile Wifi calling. Everyone who's interested in that, please install both (nightly first, then addon package) and give feedback.

EDIT:

It's the aforementioned kineto addon package. Not interesting for you if you aren't using the T-Mobile US network.
[Defy Android Development] elguaxo:
Ok, thanks! :)
[Defy Android Development] Sigray:
maniac, is the camera app working fine (without freezing, etc) in your latest rom?

I had camera freezing problem with all earlier builds (Epsylon, Quarx, and your builds too), but in the Euroskank roms working fine without any freezing.
[Defy Android Development] ttld1oh1:
It either shows "Wi-Fi Calling: Connection Error\n W009.3 Unable to connect. Failed location update" or stuck at "Wi-Fi Calling: Enabling...."

Very promising start though! Thanks
[Defy Android Development] [] AL []:
edit:

like they say, reserved for later...

sorry
[Defy Android Development] maniac103:
Heh, that's the state I have since quite some time :-/

Did you install it on my today's nightly? If no, please do, it's expected that it doesn't work on older nightlies.

If you did install it on my today's nightly: Did you select the US T-Mobile 3.4.2 baseband in the baseband selector? If no, please do, reboot and retry.

If that doesn't help: Are you able mess with files in /system and/or mess with build.prop?

If so, please do the following:

Fetch the archive of files from here

Copy the files in system/etc/motorola/comm_drv in the archive to the same place on your phone

Reboot, retry

If it didn't work yet, copy over system/lib/librilswitch.so to your phone (keeping the path again)

Reboot, retry

If it still didn't work, copy over system/lib/libril-moto-umts-1.so

Reboot, retry

If it still didn't work, also copy over system/lib/libgki.so

Reboot, retry, it must work now.

After doing that, please tell me the minimum amount of files you needed to copy. If for some reason anything goes wrong, just reinstall the nightly.
[Defy Android Development] Manulu:
Hi Maniac. Can i use your latest nightly with gb kernel? Thanks for the reply.
[Defy Android Development] maniac103:
Nope. My nightlies automatically install a Froyo kernel, though.
[Defy Android Development] Manulu:
Wonderful! Thanks!
[Defy Android Development] Deonix:
what gapps to flash with CM7. I see a lot on go inside? The last hdpi ones?

Sent from my CM9 Rocking Defy
[Defy Android Development] hailmary:
maniac, what is inside that kineto zip,whats that for? something fischy?:D
[Defy Android Development] Otto.BR:
The latest GB version still is 20110828, and there is also the "new google talk version" (I belive this uses the camera for video chat... not sure).

He explaned that a few posts back... here.
[Defy Android Development] coelho_:
it,s an apk for phone by wiffi if you have t mobile
[Defy Android Development] ttld1oh1:
Thanks for replying. Sorry, I just got back from work (14hour shift!) I tried to switch back and forth from US T-Mobile 3.4.2-107-4 and US T-Mobile 3.4.2-107-9 without success. The link you provided for the files to fetch displayed this message: "400. That’s an error.\n Your client has issued a malformed or illegal request. That’s all we know."

BTW I flashed your latest RC1 over Quarx' 120316. I messed with files in system\bin before but normally I had a habit of restoring nandroid after experimenting. Waiting for your new link. Thanks again!

---------- Post added at 10:48 PM ---------- Previous post was at 10:36 PM ----------

It's Wi-Fi calling for US T-Mobile only. Very convenience if you are in an area that has no phone coverage. People can call your T-mobile phone number when you are connected to Wi-Fi. However, you cannot use it if you are out of the US though. I tried once while vacationing in Cancun, Mexico; but had to use Skype instead (with different phone number, of course).
[Defy Android Development] maniac103:
The file was uploaded to the CM Bug Tracker, attached to comment #62.

Thanks for trying - I unfortunately can't do it myself :(
[Defy Android Development] ttld1oh1:
I'm trying right now and will report the results. Thanks

---------- Post added at 08:43 AM ---------- Previous post was at 08:23 AM ----------

Thanks for keeping your fingers crossed for me. IT WORKS right after I "Copy the files in system/etc/motorola/comm_drv in the archive to the same place on your phone" and reboot as you suggested. By the way, the files already exist, you have to overwrite them. Thanks again!!!
[Defy Android Development] maniac103:
That's ... way better than I feared :)

May I use you as a test dummy to test which of the 6 lines differences made the actual difference? If yes, please do the following:

Open mmins_telephony.cfg in an editor on the PC, change the line 'SIMTK_4BYTE_CELL_ID_AVAILABLE = 00' (line 177) to say 'SIMTK_4BYTE_CELL_ID_AVAILABLE = 01'.

Copy the file to /system/etc/motorola/comm_drv, reboot, retry - does it still work?

If yes, change 'ATT_RAT_BALANCING_MOBILE_AVAILABLE = 01' (line 18) to 'ATT_RAT_BALANCING_MOBILE_AVAILABLE = 00'

Copy, reboot, retry

If it still works, change 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 00' (line 256) to 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 01'

Copy, reboot, retry, you get the idea ;)

If it still works, change 'LOCAL_RINGBACK_TONE = 00' (line 264) to LOCAL_RINGBACK_TONE = 01'

Same procedure again...

Hopefully it should refuse to work now, the other differences look unrelated

After that, please tell me the first setting that caused it to fail. Bonus points for finding out the actual setting that caused it (that is, retry with only change 2 and reverted change 1 if it failed after change 2). :)

Thanks a lot.
[Defy Android Development] [] AL []:
Really no big deal and just to share a couple simple observations..

but I've noticed that on Maniac's March 20th,

1) I've experienced videocam freezes on the first use (2-3 videos); upon closing and re-starting of the camera, things seemed fine - but I admit that I did not test extensively.

2) there seems to be a flag about the window orientation listener that keeps being displayed [see pic 1]. Again it's nothing problematic, but it does fill the logcats as it is a constant flow of verbose: up to 4-5 entries every second.. - so it makes tracking real issues more difficult...

And since I talk about logcats, there's something that I've noticed for a long time (every other builds): an error flag this time for ConnectivityService [see pic 2]. It's just that I believe that the wording is wrong: "not failing over to mobile ...".

It might fail to connect to wifi or something and then have to fall over something else (or not) - but not: "not failing over to"... ;)

Other than that, the build is pretty awesome [and thanks Maniac103 btw], but like I've mentioned earlier, it uses slightly more power in airplane mode than Epsylon's latest - so that along with the 1st logcat thing above makes me choose Epsylon3's build. I can't wait for his next one... :p
[Defy Android Development] ttld1oh1:
I changed the values for those variables in the order that you listed and WiFi Calling failed at 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 01'

After failing, I reverted the values in reverse order beginning with 'ATT_RAT_BALANCING_MOBILE_AVAILABLE = 01' but WiFi Calling kept failing

Finally, when I reverted the value to 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 00' and WiFi Calling worked again; so 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 01' was definitely the cause. Also rebooting with 'PWR_UP_DOWN_ON_RF_SETTING_AVAILABLE = 01' made my widgets load much longer.

It took me 1 1/2 hours just to finish this small test. Hat off for your time and contributions.

Thanks!
[Defy Android Development] [] AL []:
Good news for the kineto.

Like everybody I guess, I wish that wifi calling could work from everywhere...

Is there hope that with some magic and free vpn access this would somehow become possible?
[Defy Android Development] maniac103:
It's there to debug the unwanted rotations. A user on android-hilfe.de can reproduce it pretty reliably. I'm working with him to root cause the issue. I think I may have found the issue, but I don't want to promise too much :) Once the issue is found, I will remove that debug output.

Thanks a lot. I'll make a new nightly with this change, which will (hopefully) finally make kineto work out of the box. It took long enough to achieve that :)

EDIT: New nightly uploaded which hopefully should have Kineto working out of the box (when installing Kineto addon - ttld1oh1, can you please confirm that?) and hopefully should also have the unwanted rotations fixed (can one of you guys please also confirm?). Orientation debug code is also removed.
[Defy Android Development] [] AL []:
Certainly can and did - not to test the kineto here in China;), but for the unwanted rotation was certainly worth a test..

And yes!! things are much better now with screen rotations and finally I'm be able to always leave them on and even remove the rotation toggle powerwidget altogether :)

My easy way to test that was always to do as much multitasking as possible and have high cpu load and scroll through the xda app threads. But mostly, just having some music playing in the background and scrolling through Astro folders listings would trigger it. But no more of those unwanted rotations :):):)

Once again: excellent work Dan.

I don't forget you...your turn will come for donation soon enough...you've been next on my list for a long time... :D
[Defy Android Development] sakitobaki:
New defy nightly is up!

http://quarx2k.ru

Motorola Defy red lens

German Vodafone Froyo based

CM7.2 nightly 20120316
[Defy Android Development] ttld1oh1:
I flashed your new build, wiped cache, wiped Davik cache, rebooted, entered CWM, flashed kineto-cm7-defy-signed.zip, rebooted, turned on WiFi, enabled Wi-Fi Calling and...

... It WORKS OUT OF THE BOX!!! :)

Thanks a lot for a great job.

FYI: I tried to turn kineto off and back on, turn wifi off and back on, go out of wifi coverage and back in... It still works flawlessly!
[Defy Android Development] markos807:
And what about 720p recording?
[Defy Android Development] maniac103:
Great :) I've uploaded a new nightly with the final solution: The Wifi calling app is shipped with the ROM, but disabled by default. In order to enable it, go to Settings -> Device settings and tick the Kineto checkbox. It may be that your launcher doesn't pick up the change immediately; in that case, just reboot.
[Defy Android Development] ttld1oh1:
Working flawlessly!

Thanks a lot.
[Defy Android Development] hailmary:
hi maniac my "idol" is there any chance this will be available to any other sim?;)
[Defy Android Development] maniac103:
I don't see a chance for that. The kineto app actually queries the network whether you're allowed to use it.

Sent from my Defy
[Defy Android Development] mark.peters:
maniac103

The only UK network that supports WiFi calling at the moment is Orange (aka Everything Everywhere) ... although they have partnered with TMobile, it's only the Orange customers that can use it at present.

It's installed on most of their ROMs as an app titled Signal Boost, but this is a re-badged Kineto app. http://www2.orange.co.uk/servlet/Satellite?c=OUKService&pagename=OUKPersonal&cid=1306843176798

O2 customers can also look forward to WiFi calling in the next couple of months, this being branded as 02 Connect, http://o2labs.co.uk/products/o2-connect.html and also http://blog.o2.co.uk/home/2011/11/o2-connect-making-calls-and-texts-simple.html but not sure yet if this is again a Kineto branded app, or something different.

Cheers

Mark
[Defy Android Development] pedromole:
maniac103

Before I download and test the new nightly with wifi calling, should this work on the UK Orange network or is it USA only.

If it is expected to work then I will test it and send you some money as I was one of the people who offered up the bounty :-)
[Defy Android Development] vankja:
I installed this ROM, and from the fist look of it, it is AWESOME :D

I do however have the wrong Gapps (made for ICS CM9, build of 12 march). So whenever I try to log in to the market (shouldn't this be Google Play also?) When I enter my information of my account, it sais server error (But i'm connected by wifi)

I have a Defy Plus, wich version of Gapps do I need please (if possible, post link?)

Can anybody help me with this please, then my phone will be perfect :D

Grtz
[Defy Android Development] Otto.BR:
here

Somoene else asked the same question just a couple of pages back...
[Defy Android Development] pepcisko:
look at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps

or you can go to http://goo-inside.me/gapps which will help you select the appropriate gapps version.
[Defy Android Development] vankja:
Thanks guys, working like a charm!

:D
[Defy Android Development] [] AL []:
Maniac103: as promised, I've just sent a few poker chips your way. :) Just a small token of appreciation for your work; thanks man.

...and while I'm here:

what's the deal with usb charging with the phone off/battery to 0% now?

Today, I've decided to leave my phone run out of battery before charging it

[I've restored and nand yesterday w/o fully charging and I had (was expected) big battery drops then] and had the following issues:

- I tried to charge it from my desktop's usb port for a while and I only saw a white led but no charging animation; so not knowing if it was really charging or not;

- Unplugged it and connected it to the wall charger: charging animation appeared and left it charging until I saw 3% level;

- then reconnected it to usb: white led again, then boom! I get the android with an exclamation mark and I had to pull the battery out;

- put the battery back in charged a little more by wall charger and then booted the phone up; then things were fine with usb charging...

Is usb charging just too weak for charging a dead battery properly?

I haven't tried charging through usb when phone is off lately and I know this was a problem not too long ago and I thought this had been fixed...

Are those two things related anyway?

I'm just wondering if all this is to be expected or not... as it might be problematic for people having their phone battery going empty and only having a laptop available to do the charging...

Thanks.
[Defy Android Development] Epsylon3:
in fact charger detection is the number of connections

with a charge only cable (2 wires +/-) you can have charge-only from a laptop...

charge-only mode from a pc make others problems : if you pull (or switch) the battery and usb is connected, it will go to charge-mode and you waste your time :p
[Defy Android Development] maniac103:
To be honest, I'm not sure, as I can't test it myself. The best idea really is trying it and telling me :)

Thanks a lot :)

In that case, it likely didn't boot and thus didn't charge.

I think that's the case, yes. In any case, I don't think we can do much here, that's a bootloader/kernel/battd thing.
[Defy Android Development] [] AL []:
OK then, thank you both for your answer.

I was under the false impression that the charge-only mode (moving liquid battery mode) was possible over USB on a dead battery.

But lesson learned: if you only have a laptop available for charging, don't let the phone battery die and make sure the phone has enough power to boot up first.

/A
[Defy Android Development] maniac103:
Nope. The only thing that will make the phone start up with a dead battery is a wall charger (that is, a charger with USB D+ and D- shorted). I've learned that at work once where I didn't have the wall charger adapter with me. Good thing we have lab power supplies there :D (which BTW showed that the Defy happily uses 1.5A and more in that state...)
[Defy Android Development] szacuken:
What is it?

http://quarx2k.ru/other/musb_vreg.ko

Test module OTG USB?
[Defy Android Development] ndanl:
from where can i download the builds from maniac?
[Defy Android Development] sakitobaki:
https://github.com/maniac103/android_device_motorola_jordan/downloads

Motorola Defy red lens

German Vodafone Froyo based

CM7.2 nightly 20120321
[Defy Android Development] [] AL []:
Just to illustrate my recent observations once more...

I wouldn't want to trigger an ETA alarm; I just would like to confirm that once more and that I also find myself looking for a new Easter bunny build 5 times a day... :D

() ()

(o o)

> " <

But seriously; I feel really bad asking anything like this; or devs are real workhorses and how can I dare to ask for more..
[Defy Android Development] rvd_516:
I think the link to download is not working...as multiupload is down for some days now....can anyone please share alternate download links..
[Defy Android Development] Bumble99:
Wow, just installed Maniac's 23 March KANG and it is silky smooth. Just saying.
[Defy Android Development] pphsien:
Defy+ nightly from Quarx:D

bug report:

0321 & 0323 BootMenu don't have CPU CLK4&Vsel4

It works normally though.;)

Sent from my Red Lens Defy with Kernel:4.5.2-109 DHT-22~
[Defy Android Development] jorgeoro:
Is there a changelog for quarx's nighties ?
[Defy Android Development] ndanl:
installed latest nightly from maniac and cant download anything from market, any ideea?
[Defy Android Development] ndanl:
nevermind, updated to play and it worked
[Defy Android Development] ndanl:
ca I get battery circle somehow like in cm9 ?

thanks
[Defy Android Development] sakitobaki:
Well, this is my battery:

49% left for 12h 54min.

It was better on 20120316.

I could post screenshots, but for some reason I can't upload with xda app.

Motorola Defy red lens

German Vodafone Froyo based

CM7.2 nightly 20120321
[Defy Android Development] sakitobaki:
CM7.2 nightly 20120321 battery

Here are the screenshots
[Defy Android Development] ganesh0992:
I am in MS2ginger currently and i want to try quarx's latest cm7 nightlies for my defy plus....being new to this i dont how to switch between roms...can anyone help me with steps???

And what doesnt work in the nightlies??

Thanks a lot !!
[Defy Android Development] adi4motion:
@maniac103 i'm experiencing some battery drain on your previous build... The battery only lasts like a day or so without much use. I noticed that it stays on 300Mhz more than in deepsleep (in 27 hours it stayed 14,5 on 300Mhz and 12.36 in Deep Sleep) and most of the time the phone was in my pocket or laying on the table with no wi-fi and with 2G data active.

Can you take a look at this. In the mean time i will try your latest (23) build.
[Defy Android Development] ganesh0992:
I have a defy plus with MS2Ginger(2.3.6) currently...to flash cm7 or cm9 nightly builds do i need to flash froyo or i can do it straight away from 2.3.6?? and do i need to flash any kernel??

Detailed steps wud help a lot :D

Thanks :D
[Defy Android Development] ktmbikerman:
GSM Radio

I have a question for all the clever people out there:

I've found a stock rom (2.3.6_4.5.2-109 DHT25) that gives me excellent GSM and data connectivity. Is it possible to take the RIL from this rom and use it in CM7, or any other custom rom?

If someone can point me to the right files I'll do some experimenting?

PS. I've taken the /system/etc/motorola/bp_nvm_default file from the stock South Africa rom to get the correct baseband for my country already.

Edit: Found this thread... should do the job
[Defy Android Development] YahsCE:
Why new quarks build says "exp"?