yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] okij:
That's the right place to quote Frank Lloyd Wright: "The thing always happens that you really believe in; and the belief in a thing makes it happen." ;)

So go for it, we know that you can make it real! :)

One question though about the current CM10.2: As we know, BT is not fixed yet and we also know that it's difficult to fix. Could you make any further tests in the meanwhile and probably any progress about this?

I'm asking this, because CM10.2 - besides the known bugs - is a solid base by now and a daily driver for many of us. I'm actually not needing BT audio myself (my car e.g. doesn't have BT), but I know that many of us use it and therefore stay with the CM10 nightlies (which - in my experiences - for some reason are not as stable as CM10.2 was from its first release on in terms of random reboots and such things).

As we heard from Blechd0se, you already have a daily job after finishing your studies. I hope that you enjoy it and wish you success with it! And of course we hope that you have some spare time left for the development of CM for the Defy! ;)
[Defy Android Development] SlugZero:
Data connectivity issues

Here is a patch for the build.prop of Quarx's latest build that removes the skipbrokendatacall RIL "feature". This caused that notifications of a network connection loss (or a changed national roaming provider) were not forwarded to the system, therefore the system never tried to re-establish a data connection. I believe that data connectivity should be a lot more stable with this patch, but it might also introduce new issues.

If someone wants to try this and still has data dropouts: I would be interested in logfiles, ideally with the exact time when the dropout happened. Please use the following command for logging, it also logs radio related stuff:

logcat -b radio -b main -v time |tee /sdcard/logcat.txt

Thank you for the hints, actually I was already digging in those files today... :)

You are right, the MotoWrigleyRIL we are using right now is nothing more than a set of workarounds for bugs in the Motorola RIL BLOB, and I am sure we can do a lot more than that. However the Motorola binary has very limited functionality and it will be pretty hard to work around those. For example I did not yet find a way how to get the IMEI out of it. If you have any hints here, I would be grateful, but I think there is no need for repo syncing yet. I will need some more time to understand the exact mechanisms first, but I will try my best;)
[Defy Android Development] SlugZero:
Oh, I forgot - this might be interesting regarding Bluetooth. The developers of the (in 4.1 working) BlueZ stack are working hard on an Android 4.2+-port of their stack to make a "drop-in replacement" of the (crappy) Bluedroid stack. I tried to compile it and it actually talks to the hardware, but it's still far from being ready. Maybe we just need to be a little more patient here:)
[Defy Android Development] Benoe:
Are you sure that it is the BT driver or the BT stack that causing our problems with BT?

The distorted sound maybe, but maybe the other issue (mute, unable to switch outputs) is related to some audio-routing code. Like some of this kind of code was removed here: https://github.com/Quarx2k/android_device_moto_jordan-common/commit/51ac1b087df1d9fa99be5552a56c84fddf8870d4

I could be really wrong, though.
[Defy Android Development] okij:
I'm sorry, but this morning my Defy+ had a random reboot after about 84 hours of uptime (which very rarely happens for me with CM10.2 in comparison to CM10 and CM10.1 - probably this time the memory leak issue hit me, since I have the assumption that this also is related on how many apps are being updated automatically by the Play Store, which varies quite a lot). The good thing is that I didn't have battery drain in those 3.5 days / 4 nights of uptime, which means that so far you fix seems to work. :)

At least I used the opportunity of the unwanted reboot to install [MENTION=4841764]SlugZero[/MENTION]'s fixed build.prop from tonight, as well as the older, working hostapd that SlugZero posted two days ago, so I can now test them too. ;)

So testing your fixed kernel to address the ehci_pm / battery drain issue starts from zero again for me... I hope that this time I will reach an uptime of about a week to give you some more profound feedback if your fixed kernel really works, but from my experience so far I'm still very positive about it! :cool:
[Defy Android Development] georgegpzx:
works just fine to me...just batt levels...but who cares...lol
[Defy Android Development] ela1103:
we are also believe
[Defy Android Development] jblyth:
Help - I am locked on the red "M"

I have just tried to flash the latest version (as I have done many times before) and I am now locked on the red "M".

How do I recover from this?? I don't get any led light and I can't get back into recovery!

Many thanks

John
[Defy Android Development] defim:
1 I did not need it with 4.1

2 see 1

3 more ram, yes.for apps? No!

If an apps start another is being killed to hold 100mb free! So it allows down the device, because all has to be started all the time

4 was also not needed with 4.1...

---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------

No one remembers?
[Defy Android Development] hotdog125:
For battery I suggest starting by wiping system, data, cache using defy full wiper. 4.3 is faster than 4.1/4.2 for me, I don't know why it is slow for you. As or HWA, you can disable it for apps which do not need it. About the RAM and dpi 'problems', the devs do this in their free time and enjoy doing it, so small complaints like those are not needed . The new memory management is the reason for the RAM 'problem'.

[MENTION=4916555]okij[/MENTION] Till now I did not experience the ehci_pm wakelock bug. My uptime is 4 days on Slimbean with latest kernel. Usually this bug hit me during the 2nd day of uptime, but I'm not sure whether it is completely fixed as more testing is needed.
[Defy Android Development] pasor1:
:good::good::good::good::good::good: Data drop issues solved for me with this patch !!!!!!!!!!!!!!

No new bug ;)

Now I hope to see a debugged bluetooth as soon as ...

Thanks to all developers !
[Defy Android Development] runeupo:
HWA settings, well, am on 4.1...:D

my settings are all blank except:

system-ui

android system

phone

providers.telephony

contacts

providers.contacts

dialer (i use exDialer)

more hwa-checked = more phone-slow-down in my experience. Perhaps different in 4.3. Try and let us know.

[mb525red taki_jeden 09052013 [SlimBased]]
[Defy Android Development] srijithn:
Though out of topic.. I could not stop asking.

I also have an Atix HD with CM10.2 ., But how can i include this native USB Mass storage option to it. By default i get only MTP device option.,

Cant opt for native USB Mass storage. Tried it thru terminal and build.prop tweaks ., But no success:(
[Defy Android Development] prateekranka:
Try and get into the bootloader mode and start afresh from sbf. Hope it helps
[Defy Android Development] Proverbs2:
With the new default suspend/resume settings, the delay on wakeup problem (bug #5) is back for me: the screen usually takes nearly 2 seconds to turn on, even though the lockscreen camera setting is turned off and I don't use multiple lockscreen pages.

Setting suspend_enabled to 0 or raising suspend_freq to 600 seems to help.

By the way, I love having the ability to adjust these parameters in the Aero Control app! :) However, I can't make the settings stick after reboot. I enabled the "Set at Boot" option in Aero Control, but after every reboot suspend_enabled goes back to 1 and suspend_freq goes back to the default value of 300 MHz. The same thing happens even if I manually change these values in /sys/devices/system/cpu/cpufreq/interactive/

Am I missing something?
[Defy Android Development] sevenrock:
ftr, here is the corresponding diff:

--- cm102_backup/device/moto/jordan-common/device.mk 2013-10-20 00:11:34.150772366 +0200
+++ cm102/device/moto/jordan-common/device.mk 2013-10-24 20:12:16.074244181 +0200
@@ -49,7 +49,7 @@

# telephony props
PRODUCT_PROPERTY_OVERRIDES += \
- ro.telephony.ril.v3=skipbrokendatacall,signalstrength \
+ ro.telephony.ril.v3=signalstrength \
ro.telephony.ril_class=MotoWrigley3GRIL \
ro.telephony.call_ring.multiple=false \
ro.telephony.call_ring.delay=3000 \
[Defy Android Development] okij:
fwd: Data corruption + WiFi-Hotspot problem

I got a private message from [MENTION=5500340]phirsch[/MENTION] (who isn't allowed to post in the devs forums yet) with two findings which might help to track further down the reasons for bug #19 (data corruption) and bug #20 (wifi tethering), although there are already workarounds / fixes for those bugs.

(Short question to the devs and the moderator: Could someone probably help phirsch with this?)

Now for phirsch's findings, especially [MENTION=4841764]SlugZero[/MENTION], [MENTION=513620]Quarx[/MENTION] and [MENTION=4855459]Blechd0se[/MENTION]:

(For the wifi tethering bug, I'm not quite sure if phirsch basically found the same solution that SlugZero found by posting the older hostapd version, so I forward it anyway: :))
[Defy Android Development] Proverbs2:
speaking of data corruption...

I have good news and bad news. The bad news is that enabling the has_journal feature for the /data partition, as suggested by [MENTION=4841764]SlugZero[/MENTION] here, does not prevent the issue. :crying:

I've just succeeded in reproducing the problem with the has_journal feature enabled. (I pulled the battery while running Stability Test.) The phone successfully rebooted, but it appeared as though I had done a factory reset: I saw the Cyanogenmod welcome screen.

(I am presently using the October 20th Quarx build with all of the various patches and tweaks mentioned on [MENTION=4916555]okij[/MENTION]'s very helpful bug list.)

The good news is that I can confirm [MENTION=5500340]phirsch[/MENTION]'s claim:

After deleting accounts.xml using TWRP recovery's file manager, I was able to see all of my apps and settings (although I had to go through all of the account setup processes again).

Interestingly, however, after successfully completing this process, I was still unable to restore a TWRP backup of my data! Restoring the /system partition was no problem, but when I tried to restore /data, I got an error message: "failed". In order to restore data, I first had to reformat the data partition using the tools option in bootmenu (as I had done in previous cases of data corruption).

UPDATE: I just performed the experiment again (this time by draining the battery), and I this time the phone got stuck at the boot animation. So I rebooted, went into TWRP, and mounted the /data partition, then used TWRP's file manager to replace accounts.xml with a backup that I had saved on the SD card. Unfortunately, the phone still did not boot. Next, I tried deleting accounts.xml, and again the phone got stuck on the boot animation.

So, it appears that [MENTION=5500340]phirsch[/MENTION]'s method does not work in all cases. It seemed to help in the case where the phone was able to boot to the Cyanogen welcome screen, but did not help in the case where the phone was unable to boot at all.

Edit2: On second thought, it is also possible that deleting accounts.xml made no difference even in the first case. I rebooted and tried phirsch's suggestion as soon as I saw the Cyanogen welcome screen; so for all I know, my apps and settings might have been intact even before I deleted accounts.xml the first time. Hence, I can't be sure that phirsch's solution helped in the first case either.
[Defy Android Development] caleb2003:
Flashed the latest build with miminal Gapps but cannot get past the Cyanogenmod wizard. The previous and next buttons don't seem to work on it although I can swipe through the pages but when it comes to finish I cannot, I can't get past that screen at all.

Any ideas?

Thanks
[Defy Android Development] srijithn:
I used to remove the CMaccount.apk from the ZIP file along with unwanted media files too., :o

This directly shows the google welcome screen instead of CM account.
[Defy Android Development] okij:
Bug #13 ("ehci_pm" is causing battery drain due to wakelocks) is not solved yet

@ Blechd0se:

Tonight the battery drain occured again (after less than one day of uptime), with many ehci_pm hits in WakeLock Detector, see attached screenshots. :(

So bug #13 unfortunately isn't solved yet with the kernel from 10-19. At least we know this now for sure. :)

I also generated dmesg and logcat and attached it to this post.
[Defy Android Development] Blechd0se:
Yes that's when the app really gets useful, users can easily change parameters for their needs :)

I couldn't reproduce these problems, Defy wakes up as normal, but i can have a look at it. Either i do some fancy things like last time

or i just bump it to 600 Mhz.

Btw: Set at Boot is not implemented yet, so it restores the default value on each reboot (for security reasons).

My guess is that somewhere in the ext4(3) filesystem are some bugs that cause this issue. Its such a random issue.

Ok good to know, i will see if i can get rid of those wakelocks :) Also thanks for the logs!
[Defy Android Development] steelbreeze:
What is the normal amount of free RAM ? Mine is below 30Mb most of the time and the device slows down like hell. Whatsapp is what is used most. For the rest, I am using Greenify to stop background processes.
[Defy Android Development] justjr:
I was getting this problem after update, with a reinstall I fixed it, doesn't needed to wipe nothing (cache only).

Now is normal again, around 100mb without zram (just disabeld, feels like zram is freezing apps), ~175mb with zram 28%.
[Defy Android Development] su8044:
Is i said in a previous post some days ago, i was testing to see why this happened and found out that battery drain happens with the mobile network, not wifi (possibly because bleashdose's kernel fixed wifi but mobile network battery drain still persists). I have some screenshots to show this. The first 2 are wifi on, bt and mobile network off. The other two are wifi and bt off, mobile network on. So it's obvious that battery drain still persist when mobile network is on.
[Defy Android Development] defim:
Three days after moving from 4.1.2 to 4.3.1:

Battery dry fixed for me. I lost in 7 housr 10% with bt off, wifi on.

Also the UI respons so quick as it was with 4.1

Why? I'm not sure. I've now disabled most apps in HWA. Also i've cleaned the cache for all apps. Strange but cool :)

BT car headset: I've tested it. It connects and works "a little". The voice sounds like a robotic voice ^^

I've still the problem with empty space on the desktop at bottom and top. :(
[Defy Android Development] runeupo:
blue tooth probs are well known, they are bugs 1, 2 and 17 on [MENTION=4916555]okij[/MENTION]'s summary, here: (link is as well under [MENTION=513620]Quarx[/MENTION] OP "problems")

http://xdaforums.com/showthread.php?p=45733352

[mb525red taki_jeden 09052013 [SlimBased]]
[Defy Android Development] suttaroom:
Curious

Quick question... Isnt it possible to jump from CM9 to CM10.2 w/o any issues provided the required wipes ( wipe data, cache,dalvik) are done. .. or would the kernel/recovery have to upgraded ?

Recovery

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

Kernel

Froyo - kernel-froyo-222-179-4-signed.zip
[Defy Android Development] TJKV:
[MENTION=4841764]SlugZero[/MENTION]

Removing skipbrokendatacall from build.prop is a huge improvement for data connectivity for me. When data loss occurs (every hour or so) it immediately loses signal momentarily and regains a data connection within a minute or so. Earlier I had to turn off and turn on data manually to make it lose signal etc, and sometimes even toggle airplane mode to get it working again. This by itself makes the data connection infinitely more useful for me, so a huge thanks!

The cause for the actual data loss remains unknown to me, and I have been really busy past few weeks so couldn't do any testing/log getting. But I'll try to get you some of my logs this weekend.

Sent from my MB526
[Defy Android Development] Kemby13:
This may sound silly to some of u guys, but i gotta ask anyway... I installed the newest build after already having CM10 on my defy (red lense).

I entered TWRP and tryed to wipe before the install, but i got a message: "could not mount data/cache". So i entered the Mount menu and tryed to manually

mount data and cache, but it failed every time.. So i went and installed the Rom anyway and it's working, sort of.. Now, every time i reboot the phone everything

seems to "reboot", in another words i always get the welcome message by CM wizzard and all the settings i have set are on default... Tryed to flash TWRP again,

but it always says: could not mount data and cache.. What can i do?
[Defy Android Development] Lord_Flaya:
Try full wipe to ext4 and flash again. Also try wiping dalvik after flash.
[Defy Android Development] vvoytex:
Hi. May then you should go to stock recovery and do factory reset before you flash latest Quarx release.

I did it in this way and my defy is flying with no issues. Good luck
[Defy Android Development] Kemby13:
Thx for your replies guys...

I just entered the stock recovery, btw it has the similar messages like twrp:

"E: Can't mount CACHE:recovery/command"

"E: Can't mount CACHE:recovery/caller"

"E: Can't mount CACHE:recovery/log"

Should i proceed and do a factory reset?

I cant actually remember when these messages apeared first, but when i think of it,

i believe it was actually when i used stock recovery to wipe cache instead of CWM...
[Defy Android Development] Antiga Prime:
Your /data partition is ruined/not formatted properly, therefore nothing gets stored. You should either do as recommended by [MENTION=4669272]Lord_Flaya[/MENTION], which is to format the /data partition (I'd do it from the bootmenu and not from Stock Recovery), or start again from SBF.

Those messages appear when you try to use Stock Recovery after you've wiped/formatted your partitions with CWM/TWRP.
[Defy Android Development] imharshadpatel:
[APP] Defy Helper v1.1

its really good that our defy can run all the

android version available, but new versions of

android requires more processing and battery.

Keeping this in mind and reading repeated posts

of users about battey and overclocking, I made a

small app which gives some battery saving and

cpu overclocking tips.

Its my first app and made in defy plus only and i

tried to keep it simple and small.

v1.1

explanation added for battery tips.

App attached.

if u liked my work hit thanks.
[Defy Android Development] bone101:
I don't know what the cause of you problem is....

But my last way to q. 10.2 after flashing stock ROM through rsd lite

was rooting ...

Copy bootmenu folder from extracted rom. zip into system.

Then reboot into twrp recovery where I flashed the rom.zip & restored my backup.....

I didn't wiped from stock recovery

Just wiped data & system before I flashed the stock.sbf

(I had an sudden reboot in TWRP recovery after I wiped data & system )

PS.: Flash SBF
[Defy Android Development] ennarr:
did someone noticed this?

http://quarx2k.ru/cm-10.2-20131026-NIGHTLY-mb526.zip

but it's only 100MB
[Defy Android Development] defim:
huch, nevermind :) please remove this post
[Defy Android Development] Fight4Music:
[MENTION=4521310]ennarr[/MENTION]

It's not flashable :(

Gesendet von meinem Nexus 4/Defy+ mit Tapatalk 2
[Defy Android Development] imharshadpatel:
it is still uploading so keep clam.
[Defy Android Development] Fight4Music:
Quarx removed the file, i think there went something wrong while uploading.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Defy Android Development] Kemby13:
Thx for the info, i did reformat in ext4 from the boot menu and the TWRP is working once again as it should.. No error messages.

Flashed the latest CM10.2 build than minimal gapps and everything is working fine... :good:

Thx!
[Defy Android Development] niksy+:
What .. is .. this.. ? :D

http://quarx2k.ru/just..zip..file.zip

P.S. Downloaded and checked build.prop, it's the new (26/10/2013) CM10.2 nightly. But I haven't flashed it just yet, so no guarantees :p

It's a debug build for other developers that are joining forces with Quarx :cool:
[Defy Android Development] cmcooper123:
http://gyazo.com/5e5d746e69c9044fede22ba887906f07

hehehehehehehehehehe
[Defy Android Development] Fight4Music:
Don't flash it, its a Debug Build ;)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Defy Android Development] justjr:
just a beautiful nice neat zip file x)
[Defy Android Development] Antiga Prime:
I haven't had a data corruption since I stopped using CM 4.1.2 "cm-10-20130626-NIGHTLY-mb526" build, but interestingly enough, the "format /data to EXT4" option in the bootmenu specifies that it disables journal:

#Disable journal
/system/bin/tune2fs -o journal_data_writeback $PART_DATA
/system/bin/tune2fs -O ^has_journal $PART_DATA
/system/bin/tune2fs -o journal_data_writeback $PART_CACHE
/system/bin/tune2fs -O ^has_journal $PART_CACHE

Could it be that people getting data corruptions are specifically the ones who are formatting their /data partition from the bootmenu? I can't remember the last time I formatted my /data partition, but I always use the Aroma Wiper 2.0, and AFAIK, it only deletes files, but does not format. I could have my /data partition formatted with has_journal for a long time and not even remember it.
[Defy Android Development] HammDefy:
These messages are because of a full wipe in stock recovery. Go to boot menu an do a Format Data and Cache to ext4, then all should be fine again (helped in my Defy) ;)

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] pl4yeR:
I'm facing a strange issue, my phone cannot connect to mobile data (3g) when wifi tethering is on. In the moment when I turn tethering off data is back. Is somebody else having this issue?

In dmesg I can see lot of messages related to wifi and ipv6 and I was wondering if this has something to do with my problem. If somebody see some clue to point me in the right direction I will be glad ^^
[Defy Android Development] darkvier:
Google maps does not work for me. The application starts well but does not show the maps, otherwise everything goes black
[Defy Android Development] Proverbs2:
Enable HWA for Google Maps.
[Defy Android Development] darkvier:
I tried it but doesnt work

PD: Now it works, but yesterday doesnt work by activating or deactivating HWA

I think it was a problem of google maps servers (?)
[Defy Android Development] hotdog125:
HWA is required, no problem with servers. I think HWA settings FCed before you changed it.:laugh:
[Defy Android Development] rtk217:
my phone just committed suicide on me, i have been using the 20.10 for a week. suddenly in the middle of phone conversation the phone just rebooted and got into boot loop, tried clearing cache and dalvik cache, resetting the cpu settings and other stuff but nothing works...
[Defy Android Development] deysmacro:
try increase the 4th vsel by 1.. still bootloops? increase again by 1 and repeat (if necessary) until 6 times... if the problem still there, clean install it (hopefully you dont have to) ...
[Defy Android Development] hotdog125:
You might have been hit by the data corruption bug. Take a backup of data and wipe data.
[Defy Android Development] defim:
Since the update to 4.3 from 4.1 Eclipse tells me

using device '0123456789ABCDEF'

How can i change this number back?
[Defy Android Development] rtk217:
don't know what the issue was, playing with the vsels did not help at all. i had to wipe the phone.

now i have mokee, decided to give it a try.

---------- Post added at 08:14 PM ---------- Previous post was at 07:56 PM ----------

don't know what the issue was, playing with the vsels did not help at all. i had to wipe the phone.

now i have mokee, decided to give it a try.
[Defy Android Development] habbinfo:
hi, i am using cm-10.2-20131020-NIGHTLY-mb520, is for motorola bravo, and my phone battery is discharging much, even with the screen turned off
[Defy Android Development] atulclassic:
why using bravo rom for defy??