yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] paulle:
new build 20130123

seems a new build 20130123(experimental (see readme)) is out.
[Defy Android Development] ChirmiPlay:
"After install roms from this folder, Device will be no more waterproof!!!"

What? I thought that the waterproof feature was related with the phone's hardware, not with the software :/
[Defy Android Development] vaserbanix:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

STRANGE!

Defy will be no more water proof with 3.0 kernel???????????
[Defy Android Development] jassi32:
he is trolling so that noobs stays away !!!!!!
[Defy Android Development] m4ns0nite:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Well , i think that's a joke meant to make us not install that experimental build .
[Defy Android Development] KairosDev:
I'm backing up my phone as I type this, going to install the build, see what's different.

I'll keep you all posted.
[Defy Android Development] strana77:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

Why "no more waterproof" is written in readme notice?

;)

:D
[Defy Android Development] Fight4Music:
AW: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

It's a joke.

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] ulixess:
Oh man, look above.
[Defy Android Development] KairosDev:
Installed the new build over the latest 4.1.2 build while wiping cache before and after flashing. Data has not been wiped, booting now...

Update:

Not booting. Have now wiped data, cleared cache again, booting now...

Update 2:

Not booting. Have now wiped data and cache again, installed the rom again, cleared cache. About to start boot.

Update 3:

Dunno if it's supposed to do what it's doing, but it's just stuck on the Motorola logo with a constant red LED. Gonna leave it for another ten minutes or so.

Update 4:

I took the battery out and put it back in, now I've already got the CM Boot Logo. Dunno what that was all about, but it seems to be booting fine now.

Update 5:

Booted. The logo flashed at least 20 times while booting, but it's booted and working.
[Defy Android Development] Kayant:
To restore a CWM backup all you need to do is install a older version of CM, stock or another AOSP rom that used CWM then wipe all and restore your backup..... One way around this is once you have restored your backup you can create a twrp format backup using an app like orange backup then you can restore your backup natively from twrp next time.....

To go back to CWM requires quite a bit of editing in the recovery disk etc.... look at the commit called switch to twrp on Quarx's github the common device tree branch cm-10.1-2.6.32 so its a lot easier to do something similar to what I explained earlier.

Let's Go ^_^
[Defy Android Development] Pazzu510:
Everytime i install anything but 20130626 i get no keyboard.

I have tried so far installing 20130413 and 20130415 with and without gapps with no avail. Any recommendations?

Had to do a full SBf flash to get it finally working; but it is working now. :)
[Defy Android Development] luzifers:
I've installed CM10.1, and when I have problems with RIL, the phone reboots, but instead of rebooting the system (android) the phone reboots to the bootmenu, then I have always to select boot into the bootmenu,

This is really annoying, since if you don't realize your phone will be offline until you press on boot.

Any idea how to fix this problem?

Thanks!
[Defy Android Development] atulclassic:
a good option is Onandroid (Online Backup tool)

You can take both Nandroid & TWRP backups from the same tool.

The link is here

http://xdaforums.com/showthread.php?t=1620255
[Defy Android Development] cyrusct82:
It's not working. I had 2 RIL panics so no improvement.
[Defy Android Development] xinrag:
Hello!

Same problem here and less modem crashes with 2G as with 3G. I just wanted to say that it didn't helped here to wipe cache and dalvik cache again... so right now I disabled mobile data and just use wifi.

Best regards, Stephan
[Defy Android Development] liranvaknin:
I've installed this rom on my GF defy plus and it's working but it's awfully slow.

Like if she locks the device and then press the power key to wake it up it could take ~5 sec for the screen to light up.

Also launching apps like Whatsapp takes ~5 sec or even more.

Is there anything I can do to make her device faster? It's slow to the point of being irritating and unusable.

Thanks ahead guys.
[Defy Android Development] ldiomedi:
Install greenify from the store. So much better performance in my case, but something is bad on her phone, because from the first moment, cm10.1 was so smooth. May be some process it's using the cpu all the time. It's entering in deep sleep? Use betterbattery status or cpu spy to check that

Enviado desde mi MB526 usando Tapatalk 2
[Defy Android Development] FcukBloat:
has someone noticed that is not possible to change the options in settings > advanced > Audio effects and DSP ?
[Defy Android Development] kapil_dheer:
Use greenify as suggested. Also use v6 supercharger script. This does wonders do the rom.
[Defy Android Development] justjr:
I miss updates x)

Don't get me wrong, rom is fine. I just an update addicted. >:D
[Defy Android Development] sunil_defy:
yeah that is true...no update for 20 days..waiting eagerly for the next update and for the swipe keyboard to work.
[Defy Android Development] kryzeK:
I had problems with AOSP swype keyboard, since I install gapps-minimal-edited and never had problems
[Defy Android Development] mosta00:
SwiftKey, works perfect to me.
[Defy Android Development] atulclassic:
Waking up immediately after locking will not improve anyhow..give atleast 5 sec after locking the phone and wake it up..it is smooth as butter.

to make your phone fly..install ROM Toolbox Pro and raise the OOM values to Ultimatic from Memory Manager inside Toolbox.

You will not regret.
[Defy Android Development] justjr:
The stock keyboard works for me with swype. Bu tI use the Xperia Z keyboard here, wothout any flaws.
[Defy Android Development] FcukBloat:
we already gave to solution to make the stock keyboard to work but some people is definetively deaf or too lazy to try..

about the alarm strange for me it had always worked.. it sounds correctly every time..!!
[Defy Android Development] YetAnotherForumUser:
There might be a certain precondition to the alarm (not) going off. Have a look at the contents of the alarm table on your phone to see whether you have multiple RTC_WAKEUP events for com.android.deskclock scheduled to go off at the same time.
[Defy Android Development] Cocolopes:
Sorry to ask but this list:

Problems/TODO:

1 .BT-tethering not work.

2. BT-headset has problems.

3 .BT will not work, if FM is enabled.

4. Some problems with 3G data.

5. Video recording is not good.

6. USB-tethering not work.

Is for the stable kernel or for the other?
[Defy Android Development] matiasrey:
For the 2.6.32 one (stable).
[Defy Android Development] lorcotti:
Erro de RIL

this error was present RIL me up in stock rom (android 2.3.5 Retail Brazil) tried several other sbfs but all tava restarting because of RIL so I assumed that was because of the reboot baseband, installed several but all with same error then I found the Argentine personal baseband, after installed this baseband I had more trouble with RIL but I could not hear the person speaking during a connection and data connection was only on 2G signal and in some places fall or direct nor had signal.

cm10.1 installed this day 04/15 and then spent the baseband of Argentina, I am already more than 24 hours without any error RIL.

I search the files in the background baseband (/system/etc/motorola/bp_nvm_default/) and found a difference between the other baseband, a file was not in the baseband of the Argentine personal, so I think the file responsible for the error RIL at least in my case is the "File_Audio4"

I have helped

sorry my english.
[Defy Android Development] sunil_defy:
Minimal gapps link please
[Defy Android Development] atulclassic:
search between page no. 75-85..somebody posted the link
[Defy Android Development] TJKV:
Here's my link again. I had posted it before, but a long time back.

https://dl.dropboxusercontent.com/u/3097129/gapps-jb-20130301-minimal_cm10.1_edited.zip
[Defy Android Development] xinrag:
Hi!

Look in the FAQ, first post. The "... edited..." one has a working swipe keyboard.

Best regards, Stephan
[Defy Android Development] Walking dead:
OK guys enough of this discussion regarding swipe.

People having problem with swipe replace this lib file in system/lib permission set to 644.

u can find the file with in the zip extract it and keep the discussion of this thread and there is no need of minimal gapps(which contains this file) or what so ever.
[Defy Android Development] 9Lukas5:
"3g problems" are what exactly?

Is the connection cutting, no data transferred but connection there or how do I recognize that?

L
[Defy Android Development] niksy+:
Sometimes, 3G doesn't connect as soon as you request a connection, but takes a multiple number of retries, so it takes some time (half a minute, maybe less, maybe more). But, sometimes it connects straight away. No rules... :rolleyes:

Once it connects it's perfectly fine (or at least it is for me, dunno :/ )!
[Defy Android Development] ccav2000:
+1, that's exactly what happens to me too. If it does connect, it is fine afterwards.
[Defy Android Development] 9Lukas5:
Ok, that means, it some times needs a while to get a connection, but once the connection is established it stays and works.

What's about the change between the different modes (2g/3g)?

L
[Defy Android Development] ccav2000:
I experienced no issues changing between 2G and 3G, the phone behaves exactly the same for me.
[Defy Android Development] FcukBloat:
i wouldn't know what and how to check.. :sly:

[MENTION=535343]all[/MENTION]: when the call bug (no voice at all) appears, is it possible to fix it without rebooting the phone? that would be great sometimes i can't reboot the phone (for example in the middle of a gps training session) but i need to be able to make/receive phone calls.. :(

maybe restarting a service from the terminal?

thanks a lot my friends
[Defy Android Development] YetAnotherForumUser:
Look at the dump in my post, the first line shows the command I used to create it. In short, you need to run a command on the command line. The easiest way to do this and post the results here is by opening a remote shell through adb, gaining root if needed and executing the following command:

# dumpsys alarm

The first part of the output shows pending events, the second expired events and the third consists of alarm statistics.
[Defy Android Development] measel:
I guess if that would be possible, it would be the solution in place. so no it is not possible w/o a reboot.
[Defy Android Development] kozaks:
Change it and press ok. It does apply. Only problem is that while selecting an option, radio button does not get selected
[Defy Android Development] Tausif Ahmed:
Just a thought....

just a thought.......how long would it take to make it a complete stable 4.2.2 kernel 3.0 rom?? :confused:
[Defy Android Development] disadjusted:
For me it has been sufficient to turn BT on & off again, this works even DURING a call :cool:
[Defy Android Development] Kayant:
I don't even think Quarx's can truly say well but a update on the current status would be nice ;) .... That's why devs don't do ETAs usually because they can say one thing but unexpected things might come up doing development or their presonal life.... but am sure we are all hoping its soon because next version of android will probably need it that's if our device can handle it ram wise and system install size..... I think it would make 4.1.2+ better.

Let's Go ^_^
[Defy Android Development] YetAnotherForumUser:
Carpe diem

It'll take as long as it takes to wrinkle out the last bug. There is a slight danger of the sun going supernova before that happens - it all depends on whether the sun has enough mass to actually go supernova - so if I were you I'd just use the phone with one of the available distributions (this one being a prime candidate) and carpe diem.

Bugs crop up all the time. The 3.x kernel is not ready yet. Getting it 'completely stable' will be hard since parts of the distribution - the radio interface layer being the major culprit - are both closed source as well as unstable (those two often seem to go together, alas). Even if the thing seems completely stable for user A, you'll find user B complaining about horrible battery consumption. This will end up being caused by some interaction between the set of programs on user B's device.
[Defy Android Development] xufooo:
MMS problem

Hi, everyone.

i have encountered am mms problem and i've posted this in the ask thread, but no reply. so i hope someone can help me here, thanks.

http://xdaforums.com/showpost.php?p=40983737&postcount=207

im using EDGE, not 3G.
[Defy Android Development] unixr0cket:
what about 3.0 kernel?

does someone has new news? it is still on developmet?
[Defy Android Development] frozenwaverider:
I had this problem, for me filling in authentication type in mms access point settings fixed it

Good luck

MB525 Red lense
[Defy Android Development] FcukBloat:
thanks a lot that would be great I will try and report back!! :)

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

thanks your are right didn't notice that!

so actually what is better using those sound options in advanced settings or the DSP manager settings? why double settings?

thanks!
[Defy Android Development] nostupidthing:
is hwa disabling still needed for cm10.1? i don't seem to see the app there?
[Defy Android Development] FcukBloat:
never disabled hwa for any apps and rom is perfectly smooth
[Defy Android Development] sunil_defy:
any fix for the 2G/3G toggle. Dont know why the build has become extremely slow lately. Had to work with minimal apps.
[Defy Android Development] xufooo:
thank you very much for your help.

the link seems fixed, but still cannot get the contents.
[Defy Android Development] frozenwaverider:
Hello, glad that helped

Try sending yourself a mms if you can send & receive its is truly fixed

Not sure why but I too had that, even though I fixed it, I still couldn't receive messages from before it was fixed,(it was as if your ph had reported it received, so the server deleted it) see who sent them & ask to resend(after you have tested it works) & delete the messages prompting to download

MB525 Red lense
[Defy Android Development] sunil_defy:
appears development on 2.6 is frozen. any news ?
[Defy Android Development] niksy+:
No it isn't :) Quarx has been merging up on new changes, along with adding a fix or two, just hours ago - https://github.com/Quarx2k?tab=activity

*and what ccav2000 said down below ;) *
[Defy Android Development] ccav2000:
Never forget that Quarx's main occupation is to be a student. Perhaps he's studying for exams, summer is close after all.
[Defy Android Development] sunil_defy:
That was really helpful thanks from me and everybody waiting for an update.
[Defy Android Development] xufooo:
Finally, I give up. When I send an mms, the link break again. I've returned back to cm10, everything works like a charm. Thank you all the same.
[Defy Android Development] kryzeK:
I feel that we finally have an update, and many improvements!
[Defy Android Development] YetAnotherForumUser:
Patched DeskClock.apk, only logs a single RTC_WAKEUP event

Now that I have a working CM10.1 build again I can finally post a patched DeskClock.apk which uses the AlarmManager as it was intended to be used. Since I only just built it I can not state with certainty that it solves the silent alarm bug I mentioned before but it does get rid of the multiple more or less identical entries in the alarm table:

# dumpsys alarm
Current Alarm Manager state:

Realtime wakeup (now=2013-05-07 16:33:35):
RTC_WAKEUP #3: Alarm{4119c228 type 0 com.android.providers.calendar}
type=0 when=+21h57m16s554ms repeatInterval=0 count=0
operation=PendingIntent{411b3f98: PendingIntentRecord{4113f478 com.android.providers.calendar broadcastIntent}}
RTC_WAKEUP #2: Alarm{414752b0 type 0 com.android.deskclock}
type=0 when=+13h46m24s90ms repeatInterval=0 count=0
operation=PendingIntent{414752a0: PendingIntentRecord{40e2f878 com.android.deskclock broadcastIntent}}
RTC_WAKEUP #1: Alarm{41080c80 type 0 com.google.android.gms}
type=0 when=+9h26m24s90ms repeatInterval=86400000 count=0
operation=PendingIntent{40f7d6a8: PendingIntentRecord{41080b90 com.google.android.gms startService}}
RTC_WAKEUP #0: Alarm{40e0b428 type 0 com.google.android.gms}
type=0 when=+5h58m0s745ms repeatInterval=0 count=0
operation=PendingIntent{40e0b418: PendingIntentRecord{40e3fa28 com.google.android.gms broadcastIntent}}
RTC #1: Alarm{40f8f1a8 type 1 android}
type=1 when=+19h26m24s90ms repeatInterval=0 count=0
operation=PendingIntent{410142d8: PendingIntentRecord{410142a0 android broadcastIntent}}
RTC #0: Alarm{40e0e310 type 1 com.android.calendar}
type=1 when=+7h26m24s90ms repeatInterval=0 count=0
operation=PendingIntent{40e13678: PendingIntentRecord{40dcf788 com.android.calendar broadcastIntent}}

The patch is a simple as it was in CM10:

diff --git a/src/com/android/deskclock/Alarms.java b/src/com/android/deskclock/Alarms.java
index 341e37c..8b3366b 100644
--- a/src/com/android/deskclock/Alarms.java
+++ b/src/com/android/deskclock/Alarms.java
@@ -451,7 +451,7 @@ public class Alarms {
intent.putExtra(ALARM_RAW_DATA, out.marshall());

PendingIntent sender = PendingIntent.getBroadcast(
- context, 0, intent, PendingIntent.FLAG_CANCEL_CURRENT);
+ context, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT);

am.set(AlarmManager.RTC_WAKEUP, atTimeInMillis, sender);

@@ -477,7 +477,7 @@ public class Alarms {
context.getSystemService(Context.ALARM_SERVICE);
PendingIntent sender = PendingIntent.getBroadcast(
context, 0, new Intent(ALARM_ALERT_ACTION),
- PendingIntent.FLAG_CANCEL_CURRENT);
+ PendingIntent.FLAG_UPDATE_CURRENT);
am.cancel(sender);
setStatusBarIcon(context, false);
// Intentionally verbose: always log the lack of a next alarm to provide useful

I'll test this version for a few days with recurring alarms. If it works as intended I think this patch should be applied to CM10.1 (all branches) while the bug remains in AOSP. I posted this updated version of the patch to the relevant bug report on the AOSP bug tracker.
[Defy Android Development] sevenrock:
And keep in mind that last weekend were the Easter holidays in Russia ;)
[Defy Android Development] labsin:
Developers don't check these often. There were 5-10 bugs about Belgian dutch keyboard not being AZERTY.

I made the changes and followed:

http://source.android.com/source/submit-patches.html

I had to wait a release cycle and update the patch every release but it got merged.
[Defy Android Development] YetAnotherForumUser:
OK, I'll see if I can get my ${expletive_body_part} in gear and submit it 'the canonical way'...
[Defy Android Development] sa3e1:
New Nightly 07.05.13 is up: http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/

edit: Sorry got confused :P It's CM10 indeed...
[Defy Android Development] prateekranka:
Changelog please :)
[Defy Android Development] Fight4Music:
Wrong thread, it's CM10 not CM10.1 :)

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] SkarlosBME:
But maybe he will compile one for the CM10.1, his recent releases for the two versions came almost at the same time:)
[Defy Android Development] atulclassic:
Battery heating up too quickly

Just after 10 minutes of gameplay (Temple Run), my battery heated up by 9°C..could anyone help please?
[Defy Android Development] Freeman85:
Turn back to 1GHz, it's working ok on 1 Ghz.
[Defy Android Development] shubhu2604:
can we just change a few files with one from any other rom to improve video rec quality..?? or any other solution..??:o:D
[Defy Android Development] atulclassic:
i was also thinking to do so..can anyone give me the original vsel values
[Defy Android Development] Freeman85:
Use "vsel calculator" - it's available on Forum, or even in play store.
[Defy Android Development] lscalex:
Ad hoc Wifi

Hi, I cannot connect to ad hoc Wifi network..... How to fix it? Thanks!
[Defy Android Development] atulclassic:
vsel calculator formula is freq/20+2..i want default values.
[Defy Android Development] FaulFels:
Look here.
[Defy Android Development] FcukBloat:
here it seems it doesn't do the trick.. just tried with no success :(
[Defy Android Development] YetAnotherForumUser:
For those of you who can't wait...

Now that I got the build system working again I made a build based on Quarx' repo as it was at 20130508. This is the build I currently have on my device (an MB526 for those who need to know), it seems to run without major malfunctions for now. Wifi works as intended. The build identifies itself as '20130507' because I did not delete build.prop between builds.

If you feel the urge to run a more recent build than Quarx' 20130415 for some reason you can download this 'unofficial' (for whatever that means) build here:

cm-10.1-20130508-UNOFFICIAL-mb526.zip

cm-10.1-20130508-UNOFFICIAL-mb526.zip.md5sum (the md5 for the build is [FONT="Monospace, Courier New"]8c8812760e53c1e9932acef98bedb01b[/FONT] )

This build does NOT contain the patched version of DeskClock.apk, if you want that you can download it from my earlier post.

As to whether running this build has any tangible benefits over Quarx' last build I have my doubts. It works, but so did 20130415. If you spot anything in the change logs which piques your interest but you are unable or unwilling to build your own image this one might be worth a try.
[Defy Android Development] FcukBloat:
thanks.. just one question, do you know if the call bug (no voice sometimes) is present in "your" build? thanks! :)
[Defy Android Development] ulixess:
Hi, regarding to the call bug ... its even on my S3, so I think its a CM bug.

But there are some "fixes". Play some sound during boot (eg with tasker) or play some system (!) sound bevor a call (eg screen lock-/unlocksound). This works fo me and others ;)

Little OT: How can I download from Mega with android?
[Defy Android Development] grandpa2007:
Mega from Playstore

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] FcukBloat:
yes maybe it can works when I make a call but when I receive it.. how to know when it will happen.. :p
[Defy Android Development] Matzemink:
Can someone tell me how to get back to other ROM's?

I wiped cache, data and system with TWRP and now I've got problems with the cache partition. I get the following error messages in stock recovery and also in CM10, CM7 recovery:

E:can't mount CACHE:recovery/command
E:can't mount CACHE:recovery/caller
E:can't mount CACHE:recovery/log

I already flashed SBF, tried wiping through adb, wipe in CM7/CM10 recovery... but the problem persists :(

Some ROM's don't boot (CM7), some do (WIUI v4) but crash when you try to login to your Google Account.

It's just CM10.1 with TWRP where I can wipe cache and data and where I get no error messages.

I think you won't get this error, when you've checked "rm-fr" in twrp settings... well it's too late for me.
[Defy Android Development] Antiga Prime:
I always get those error messages in stock recovery after wiping with CWM, so I hardly would think it's a TWRP issue, and it's never prevented me from flashing anything else, whether through CWM and/or RSD. I think your phone might have other issues.
[Defy Android Development] slimshady76:
Thanks YAFU! When you say "Wifi works as intended", do you mean it won't jam other devices connected to the same router/hotspot?
[Defy Android Development] YetAnotherForumUser:
I have never noticed any Wifi jamming related to the Defy so I am not the right person to ask. This is on a network served by an Asus RT-N16 running DD-WRT, mixed g/n mode, serving around 10 devices. We also have wireless audio in the same building which uses the 2.4GHz band. Maybe the Wifi jamming is limited to a specific subset of router/firmware/device/standard combinations, or maybe we're just lucky?
[Defy Android Development] Mario.D:
I have the same jamming issue with a rt-56u and also a rt-n16 both of them are on default firmware.

Skickat från min MB526 via Tapatalk 2