[AOSPA 4.4.2 KOT49H] [Beta] Defy(+) PARANOIDANDROID 4.0+ [18/01/2014]

Status
Not open for further replies.
Search This thread

Kayant

Senior Member
Jul 14, 2011
1,861
4,149
Code:
#include 
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you :p
*
* Also no eta's as am not a dev and solving bugs will be hard for me and this is done for fun....Thanks to 
Steve kondik for his nice sense of comedy :)

450j1ot.jpg


AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1

Download ROMS from DOWNLOAD HERE

Mirror here (Thanks to UncleDan) --> http://www.uncledan.it/android-files/motorola-defy-2ndboot/

1. DOWNLOAD YOUR ROM

2. DOWNLOAD THE LATEST BANKS 4.4 GAPPS PACKAGE - BANKS

3. FULL CLEAN WIPE (If coming from another rom/android version) - * system, cache & dalvik* or USE @TJKV safewipe script - Here

4. FLASH ROM & GAPPS

5. WIPE CACHE & DALVIK

5. RUN INITIAL SETUP & REBOOT

GIT
GERRIT
COMMUNITY + CHANGELOGS
 
Last edited:

Kayant

Senior Member
Jul 14, 2011
1,861
4,149
More Installation instructions, tips & Changelog

Installation Instructions coming from stock
  • If you are coming from stock OS (must be rooted with CWM) or an old build of GB, ICS, or JB then flash "defy_twrp_recovery_2.6.3.0.zip" from the links under downloads.
  • Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip (Credits to @YetAnotherForumUser for the wipe script)
  • Flash ROM
  • Flash Gapps
  • Reboot

Root Instructions
  • Go to Settings -> About phone
  • Tap on Build number 8 times
  • Go back to settings and go to Developer options
  • Enable Root for Apps or Apps & ADB per your choice

Bugs
  • Known bugs on CM11 by Quarx2k [here]
  • FM radio not supported at the moment
  • Some graphical issues from time to time. Happens in AOSP builds also Fixed now thanks to @steven676 & @struq for the heads up.
  • Tell me more if you find it ;)


Changelog
ART Runtime
ART is experimental, please do not report any bugs while using it.
  • The banks gapps supports ART.
  • Flash the ROM only and boot it up once, switch to ART.
  • Reboot into the ROM. This bootup takes a long time.
  • Reboot to recovery and flash ART compatible gapps and any other addon
  • Reboot

Thanks & Donations

Donations

to molesarecoming
to D4rKn3sSyS
to jaybob413
to aaronpoweruser
to Quarx
to Blechd0se

Thanks

To all current/past moto & defy devs including @Epsylon3, @maniac103, @Quarx, @walter79, @czechop, @kabaldan @YetAnotherForumUser @Blechd0se, @SlugZero @TJKV and to anymore I missed sorry :p


Credit

To the Omni team as always for a great rom and vision
To Google for providing us with awesomess
To Moto not really :p but thanks for the defy it's pretty awesome
To Goo for free hosting
To XDA for always me to share my hobby.
To @TJKV & @houstonn for shamelessly stealing their OP's :p
 
Last edited:

niksy+

Senior Member
Jan 16, 2012
1,357
1,082
Oh, this is sweet :) Downloading and will probably give it a go tomorrow if not now (both mine and phone's batterys are low :/ )
@Kayant Any comments on how it's working? No? :(
 

Pottkopp

Senior Member
Mar 10, 2010
393
212
currently downloading will report back with my experiences ;)

EDIT: are paranoid settings not included yet (+ halo)? :eek:
 
Last edited:

struq

Senior Member
Apr 1, 2012
72
278
PowerVR libs crash

Thanks for the new flavor of KitKat.;)
I had a brief test of this ROM and managed to trigger the same PowerVR libs crash as in my own build of AOSP. :(

Steps to reproduce: run heavy load apps like Maps or Chrome, after a while, open Settings or Dialer. This could be quite random though.

logcat
E/GraphicBuffer( 2769): unflatten: registerBuffer failed: Invalid argument (-22)
W/GraphicBufferMapper( 2769): registerBuffer(0x390b58) failed -22 (Invalid argument)
dmesg
<6>[ 936.725433] PVR_K: HWRecoveryResetSGX: SGX Hardware Recovery triggered
<6>[ 936.725463] PVR_K: SGX debug (SGX_DDK_Android sgxddk [email protected])
<6>[ 936.725463] PVR_K: (P0) EUR_CR_CORE_ID: 01120000
<6>[ 936.725494] PVR_K: (P0) EUR_CR_CORE_REVISION: 00010205
<6>[ 936.725494] PVR_K: (P0) EUR_CR_EVENT_STATUS: 20000000
<6>[ 936.725524] PVR_K: (P0) EUR_CR_EVENT_STATUS2: 00000018
<6>[ 936.725524] PVR_K: (P0) EUR_CR_BIF_CTRL: 00000000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_INT_STAT: 00004002
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_FAULT: 003C9000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_MEM_REQ_STAT: 00000002
<6>[ 936.725585] PVR_K: (P0) EUR_CR_CLKGATECTL: 00222220
<6>[ 936.725585] PVR_K: (P0) EUR_CR_PDS_PC_BASE: 00005034
<6>[ 936.725616] PVR_K: Found MMU context for page fault 0x003c9000
<6>[ 936.725616] PVR_K: GPU memory context is for PID=2769 (ndroid.settings)
<6>[ 936.725646] PVR_K: PDE valid: PTE = 0x903c8001 (PhysAddr = 0x903c8000, valid)
<6>[ 936.725646] PVR_K: Flip Command Complete Data 0 for display device 1:
<6>[ 936.725677] PVR_K: SRC 0: (Not in use)
<6>[ 936.725677] PVR_K: SRC 1: (Not in use)
<6>[ 936.725677] PVR_K: Host Ctl flags= 00000006
<6>[ 936.725708] PVR_K: SGX Host control:
<6>[ 936.725708] PVR_K: (HC-0) 0x00000001 0x00000000 0x00000000 0x00000001
<6>[ 936.725738] PVR_K: (HC-10) 0x00000000 0x00000001 0x0000000A 0x00030D40
<6>[ 936.725738] PVR_K: (HC-20) 0x00000065 0x00000000 0x00000003 0x00000000
<6>[ 936.725769] PVR_K: (HC-30) 0x00000227 0x0005ACF6 0x25E5B434 0x00000000
<6>[ 936.725769] PVR_K: (HC-40) 0x00000000 0x00000000 0x00000011 0x0338021D
<6>[ 936.725799] PVR_K: SGX TA/3D control:
<6>[ 936.725799] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
<6>[ 936.725830] PVR_K: (T3C-10) 0x0F0EA9C0 0x00000000 0x00000002 0x00000000
<6>[ 936.725830] PVR_K: (T3C-20) 0x0F00AEA0 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-50) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-60) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-70) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-80) 0x00000000 0x0F1F5658 0x00000000 0x0F000000
<6>[ 936.725952] PVR_K: (T3C-90) 0x9F9E2000 0x0F16C500 0x00000000 0x0F119840
<6>[ 936.725952] PVR_K: (T3C-A0) 0x0F0F2FA0 0x0F1F5658 0x0F119840 0x00000000
<6>[ 936.725982] PVR_K: (T3C-B0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725982] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.726013] PVR_K: (T3C-D0) 0x0F000000 0x8000B000 0x8004B000 0x0F004000
<6>[ 936.726013] PVR_K: (T3C-E0) 0x0F00A420 0x0F00A740 0x0F120CA0 0x0F120CA0
<6>[ 936.726043] PVR_K: (T3C-F0) 0x00000000 0x00000AD1 0x00000AD1 0x00000000
<6>[ 936.726043] PVR_K: (T3C-100) 0x00000003 0x00000001 0x00000000 0x00000000
<6>[ 936.726074] PVR_K: (T3C-110) 0xEC9A3BC9 0x00010002 0x0002B801 0x00000018
<6>[ 936.726074] PVR_K: SGX Kernel CCB WO:0x8A RO:0x88
Full log attached.

This does NOT happen in CM11 or SlimKat. I used to think that there was some Quarx or CM patches I missed in frameworks/native. Since you seem to use Quarx's branch of frameworks/native directly, this possibility could be ruled out. I also tried replacing system_core and bionic, problem not in there too.

Some more info: Nexus S(aosp & slimkat) and Galaxy Nexus(slimkat) also suffer from this crash.
 

Attachments

  • dmesg.txt
    65 KB · Views: 9

Kayant

Senior Member
Jul 14, 2011
1,861
4,149
Thanks for the new flavor of KitKat.;)
I had a brief test of this ROM and managed to trigger the same PowerVR libs crash as in my own build of AOSP. :(

Steps to reproduce: run heavy load apps like Maps or Chrome, after a while, open Settings or Dialer. This could be quite random though.

logcat
E/GraphicBuffer( 2769): unflatten: registerBuffer failed: Invalid argument (-22)
W/GraphicBufferMapper( 2769): registerBuffer(0x390b58) failed -22 (Invalid argument)
dmesg
<6>[ 936.725433] PVR_K: HWRecoveryResetSGX: SGX Hardware Recovery triggered
<6>[ 936.725463] PVR_K: SGX debug (SGX_DDK_Android sgxddk [email protected])
<6>[ 936.725463] PVR_K: (P0) EUR_CR_CORE_ID: 01120000
<6>[ 936.725494] PVR_K: (P0) EUR_CR_CORE_REVISION: 00010205
<6>[ 936.725494] PVR_K: (P0) EUR_CR_EVENT_STATUS: 20000000
<6>[ 936.725524] PVR_K: (P0) EUR_CR_EVENT_STATUS2: 00000018
<6>[ 936.725524] PVR_K: (P0) EUR_CR_BIF_CTRL: 00000000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_INT_STAT: 00004002
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_FAULT: 003C9000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_MEM_REQ_STAT: 00000002
<6>[ 936.725585] PVR_K: (P0) EUR_CR_CLKGATECTL: 00222220
<6>[ 936.725585] PVR_K: (P0) EUR_CR_PDS_PC_BASE: 00005034
<6>[ 936.725616] PVR_K: Found MMU context for page fault 0x003c9000
<6>[ 936.725616] PVR_K: GPU memory context is for PID=2769 (ndroid.settings)
<6>[ 936.725646] PVR_K: PDE valid: PTE = 0x903c8001 (PhysAddr = 0x903c8000, valid)
<6>[ 936.725646] PVR_K: Flip Command Complete Data 0 for display device 1:
<6>[ 936.725677] PVR_K: SRC 0: (Not in use)
<6>[ 936.725677] PVR_K: SRC 1: (Not in use)
<6>[ 936.725677] PVR_K: Host Ctl flags= 00000006
<6>[ 936.725708] PVR_K: SGX Host control:
<6>[ 936.725708] PVR_K: (HC-0) 0x00000001 0x00000000 0x00000000 0x00000001
<6>[ 936.725738] PVR_K: (HC-10) 0x00000000 0x00000001 0x0000000A 0x00030D40
<6>[ 936.725738] PVR_K: (HC-20) 0x00000065 0x00000000 0x00000003 0x00000000
<6>[ 936.725769] PVR_K: (HC-30) 0x00000227 0x0005ACF6 0x25E5B434 0x00000000
<6>[ 936.725769] PVR_K: (HC-40) 0x00000000 0x00000000 0x00000011 0x0338021D
<6>[ 936.725799] PVR_K: SGX TA/3D control:
<6>[ 936.725799] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
<6>[ 936.725830] PVR_K: (T3C-10) 0x0F0EA9C0 0x00000000 0x00000002 0x00000000
<6>[ 936.725830] PVR_K: (T3C-20) 0x0F00AEA0 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-50) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-60) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-70) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-80) 0x00000000 0x0F1F5658 0x00000000 0x0F000000
<6>[ 936.725952] PVR_K: (T3C-90) 0x9F9E2000 0x0F16C500 0x00000000 0x0F119840
<6>[ 936.725952] PVR_K: (T3C-A0) 0x0F0F2FA0 0x0F1F5658 0x0F119840 0x00000000
<6>[ 936.725982] PVR_K: (T3C-B0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725982] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.726013] PVR_K: (T3C-D0) 0x0F000000 0x8000B000 0x8004B000 0x0F004000
<6>[ 936.726013] PVR_K: (T3C-E0) 0x0F00A420 0x0F00A740 0x0F120CA0 0x0F120CA0
<6>[ 936.726043] PVR_K: (T3C-F0) 0x00000000 0x00000AD1 0x00000AD1 0x00000000
<6>[ 936.726043] PVR_K: (T3C-100) 0x00000003 0x00000001 0x00000000 0x00000000
<6>[ 936.726074] PVR_K: (T3C-110) 0xEC9A3BC9 0x00010002 0x0002B801 0x00000018
<6>[ 936.726074] PVR_K: SGX Kernel CCB WO:0x8A RO:0x88
Full log attached.

This does NOT happen in CM11 or SlimKat. I used to think that there was some Quarx or CM patches I missed in frameworks/native. Since you seem to use Quarx's branch of frameworks/native directly, this possibility could be ruled out. I also tried replacing system_core and bionic, problem not in there too.

Some more info: Nexus S(aosp & slimkat) and Galaxy Nexus(slimkat) also suffer from this crash.

Much thanks for testing it's great to have your expertises on this ;)..... Yh it's not too surprising it has the these issues because AOSPA is very close to AOSP compared to SlimKat which still has most have it's source patched up with CM patches for hardware support. Yh I also though it was to do with bionic, system_core,native, skia. I guess not :p. I will see what I can find and will relay a solution if I find it first ;)
 

TJKV

Senior Member
Jun 25, 2011
1,927
2,747
Thanks for the new flavor of KitKat.;)
I had a brief test of this ROM and managed to trigger the same PowerVR libs crash as in my own build of AOSP. :(

Steps to reproduce: run heavy load apps like Maps or Chrome, after a while, open Settings or Dialer. This could be quite random though.

logcat
E/GraphicBuffer( 2769): unflatten: registerBuffer failed: Invalid argument (-22)
W/GraphicBufferMapper( 2769): registerBuffer(0x390b58) failed -22 (Invalid argument)
dmesg
<6>[ 936.725433] PVR_K: HWRecoveryResetSGX: SGX Hardware Recovery triggered
<6>[ 936.725463] PVR_K: SGX debug (SGX_DDK_Android sgxddk [email protected])
<6>[ 936.725463] PVR_K: (P0) EUR_CR_CORE_ID: 01120000
<6>[ 936.725494] PVR_K: (P0) EUR_CR_CORE_REVISION: 00010205
<6>[ 936.725494] PVR_K: (P0) EUR_CR_EVENT_STATUS: 20000000
<6>[ 936.725524] PVR_K: (P0) EUR_CR_EVENT_STATUS2: 00000018
<6>[ 936.725524] PVR_K: (P0) EUR_CR_BIF_CTRL: 00000000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_INT_STAT: 00004002
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_FAULT: 003C9000
<6>[ 936.725555] PVR_K: (P0) EUR_CR_BIF_MEM_REQ_STAT: 00000002
<6>[ 936.725585] PVR_K: (P0) EUR_CR_CLKGATECTL: 00222220
<6>[ 936.725585] PVR_K: (P0) EUR_CR_PDS_PC_BASE: 00005034
<6>[ 936.725616] PVR_K: Found MMU context for page fault 0x003c9000
<6>[ 936.725616] PVR_K: GPU memory context is for PID=2769 (ndroid.settings)
<6>[ 936.725646] PVR_K: PDE valid: PTE = 0x903c8001 (PhysAddr = 0x903c8000, valid)
<6>[ 936.725646] PVR_K: Flip Command Complete Data 0 for display device 1:
<6>[ 936.725677] PVR_K: SRC 0: (Not in use)
<6>[ 936.725677] PVR_K: SRC 1: (Not in use)
<6>[ 936.725677] PVR_K: Host Ctl flags= 00000006
<6>[ 936.725708] PVR_K: SGX Host control:
<6>[ 936.725708] PVR_K: (HC-0) 0x00000001 0x00000000 0x00000000 0x00000001
<6>[ 936.725738] PVR_K: (HC-10) 0x00000000 0x00000001 0x0000000A 0x00030D40
<6>[ 936.725738] PVR_K: (HC-20) 0x00000065 0x00000000 0x00000003 0x00000000
<6>[ 936.725769] PVR_K: (HC-30) 0x00000227 0x0005ACF6 0x25E5B434 0x00000000
<6>[ 936.725769] PVR_K: (HC-40) 0x00000000 0x00000000 0x00000011 0x0338021D
<6>[ 936.725799] PVR_K: SGX TA/3D control:
<6>[ 936.725799] PVR_K: (T3C-0) 0x0F003000 0x0F003120 0x0F002000 0x00000000
<6>[ 936.725830] PVR_K: (T3C-10) 0x0F0EA9C0 0x00000000 0x00000002 0x00000000
<6>[ 936.725830] PVR_K: (T3C-20) 0x0F00AEA0 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-30) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725860] PVR_K: (T3C-40) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-50) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725891] PVR_K: (T3C-60) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-70) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725921] PVR_K: (T3C-80) 0x00000000 0x0F1F5658 0x00000000 0x0F000000
<6>[ 936.725952] PVR_K: (T3C-90) 0x9F9E2000 0x0F16C500 0x00000000 0x0F119840
<6>[ 936.725952] PVR_K: (T3C-A0) 0x0F0F2FA0 0x0F1F5658 0x0F119840 0x00000000
<6>[ 936.725982] PVR_K: (T3C-B0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.725982] PVR_K: (T3C-C0) 0x00000000 0x00000000 0x00000000 0x00000000
<6>[ 936.726013] PVR_K: (T3C-D0) 0x0F000000 0x8000B000 0x8004B000 0x0F004000
<6>[ 936.726013] PVR_K: (T3C-E0) 0x0F00A420 0x0F00A740 0x0F120CA0 0x0F120CA0
<6>[ 936.726043] PVR_K: (T3C-F0) 0x00000000 0x00000AD1 0x00000AD1 0x00000000
<6>[ 936.726043] PVR_K: (T3C-100) 0x00000003 0x00000001 0x00000000 0x00000000
<6>[ 936.726074] PVR_K: (T3C-110) 0xEC9A3BC9 0x00010002 0x0002B801 0x00000018
<6>[ 936.726074] PVR_K: SGX Kernel CCB WO:0x8A RO:0x88
Full log attached.

This does NOT happen in CM11 or SlimKat. I used to think that there was some Quarx or CM patches I missed in frameworks/native. Since you seem to use Quarx's branch of frameworks/native directly, this possibility could be ruled out. I also tried replacing system_core and bionic, problem not in there too.

Some more info: Nexus S(aosp & slimkat) and Galaxy Nexus(slimkat) also suffer from this crash.

So far you've looked at system/core, bionic, f/n right? Did you by any chance make a build before updating tag to 4.4.1/4.4.2? If you did were the crashes happening then too?
 

gyorgyszemok

Senior Member
Dec 10, 2012
65
8
You can edit the settings.db file located in /data/data/com.android.providers.settings/databases and add a row to the "system" table with "volume_wake_screen" and give it a value of "1".

Or you could also use xposed + xposed additions and remap your keys through there.

First suggestion does not work for me
 

struq

Senior Member
Apr 1, 2012
72
278
So far you've looked at system/core, bionic, f/n right? Did you by any chance make a build before updating tag to 4.4.1/4.4.2? If you did were the crashes happening then too?

My first aosp build is 4.4.1 with some parts remained at 4.4.0. And yes, the crash has been there since.
Pure 4.4.0 would be Quarx's 1110 build. I didn't stay on that for long so I can't say about it.
 

TJKV

Senior Member
Jun 25, 2011
1,927
2,747
Did you reboot? You have to reboot; worked for me on 2 different ROMs.

This will depend on whether the ROM source has the frameworks part of this feature implemented. The other part would be in settings app. PA has started from scratch for Kitkat, so has slimroms. So chances are the frameworks/base bit doesn't exist yet...unless you mean it works for you on this rom too?
 

Antiga Prime

Senior Member
Sep 25, 2012
994
637
This will depend on whether the ROM source has the frameworks part of this feature implemented. The other part would be in settings app. PA has started from scratch for Kitkat, so has slimroms. So chances are the frameworks/base bit doesn't exist yet...unless you mean it works for you on this rom too?

No, I haven't tested PA, but it worked on CM 11 and the first Slimkat, even though it was not in the settings app; adding "ToggleFlashlight" in the database file also worked, as in, it added the Torch tile after reboot. Of course, I don't know all the inner-workings of Android, so I wouldn't know about it having to be in the frameworks, I basically just played around with the database file and found I could change/add things regardless if they were implemented in the settings app or not.
 

TJKV

Senior Member
Jun 25, 2011
1,927
2,747
My first aosp build is 4.4.1 with some parts remained at 4.4.0. And yes, the crash has been there since.
Pure 4.4.0 would be Quarx's 1110 build. I didn't stay on that for long so I can't say about it.

How did you take the logs? I'm unable to connect to adb over usb on the 20th dec build. Mounting SD Card to the pc isn't possible either. Any reason you changed it to mtp from mass storage?
 

struq

Senior Member
Apr 1, 2012
72
278
How did you take the logs? I'm unable to connect to adb over usb on the 20th dec build. Mounting SD Card to the pc isn't possible either. Any reason you changed it to mtp from mass storage?
I can connect to adb, even without root. I had to force install generic "Android Composite ADB Interface" driver instead of Moto driver (in Windows), but it's been like this since Quarx switched to new USB stack. I can connect adb in cm11, slimkat and kayant's pa too.
I changed to MTP because personally I use it more than UMS. It has such advantages: no need to unmount sd in android so you can access sd from phone in the meantime, less potential damage to sd/filesystem when unplug unexpectedly. Anyway its the Android/AOSP trend.
I thought there was UMS available in the mode selection notification, but there isn't.:cyclops: I've found the right CM patch to enable it andI will port that when I have some time.
Right now it can be reverted in /system/build.prop, either before or after flashing.
 
  • Like
Reactions: bhupatib
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    Code:
    #include 
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you :p
    *
    * Also no eta's as am not a dev and solving bugs will be hard for me and this is done for fun....Thanks to 
    Steve kondik for his nice sense of comedy :)

    450j1ot.jpg


    AOSPA 4.0+ PARANOIDANDROID [beta]
    Kitkat 4.4.2 KOT49H android-4.4.2_r1

    Download ROMS from DOWNLOAD HERE

    Mirror here (Thanks to UncleDan) --> http://www.uncledan.it/android-files/motorola-defy-2ndboot/

    1. DOWNLOAD YOUR ROM

    2. DOWNLOAD THE LATEST BANKS 4.4 GAPPS PACKAGE - BANKS

    3. FULL CLEAN WIPE (If coming from another rom/android version) - * system, cache & dalvik* or USE @TJKV safewipe script - Here

    4. FLASH ROM & GAPPS

    5. WIPE CACHE & DALVIK

    5. RUN INITIAL SETUP & REBOOT

    GIT
    GERRIT
    COMMUNITY + CHANGELOGS
    15
    More Installation instructions, tips & Changelog

    Installation Instructions coming from stock
    • If you are coming from stock OS (must be rooted with CWM) or an old build of GB, ICS, or JB then flash "defy_twrp_recovery_2.6.3.0.zip" from the links under downloads.
    • Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip (Credits to @YetAnotherForumUser for the wipe script)
    • Flash ROM
    • Flash Gapps
    • Reboot

    Root Instructions
    • Go to Settings -> About phone
    • Tap on Build number 8 times
    • Go back to settings and go to Developer options
    • Enable Root for Apps or Apps & ADB per your choice

    Bugs
    • Known bugs on CM11 by Quarx2k [here]
    • FM radio not supported at the moment
    • Some graphical issues from time to time. Happens in AOSP builds also Fixed now thanks to @steven676 & @struq for the heads up.
    • Tell me more if you find it ;)


    Changelog
    ART Runtime
    ART is experimental, please do not report any bugs while using it.
    • The banks gapps supports ART.
    • Flash the ROM only and boot it up once, switch to ART.
    • Reboot into the ROM. This bootup takes a long time.
    • Reboot to recovery and flash ART compatible gapps and any other addon
    • Reboot

    Thanks & Donations

    Donations

    to molesarecoming
    to D4rKn3sSyS
    to jaybob413
    to aaronpoweruser
    to Quarx
    to Blechd0se

    Thanks

    To all current/past moto & defy devs including @Epsylon3, @maniac103, @Quarx, @walter79, @czechop, @kabaldan @YetAnotherForumUser @Blechd0se, @SlugZero @TJKV and to anymore I missed sorry :p


    Credit

    To the Omni team as always for a great rom and vision
    To Google for providing us with awesomess
    To Moto not really :p but thanks for the defy it's pretty awesome
    To Goo for free hosting
    To XDA for always me to share my hobby.
    To @TJKV & @houstonn for shamelessly stealing their OP's :p
    11
    Heads up.... New build coming tomorrow. So far so good I have not had any graphical issues yet... Also i disabled the low memory flag by default as it seems to preform better without it. I will also see if I can get a build of Omni ready .

    Edit - spoke too soon on the graphical issues :p completely froze my phone had to remove the battery to reboot. Man I wish I knew where this problem is hopefully Quarx's can find a fix soon :)


    Let's Go ^_^
    9
    @Kayant Can I port this Rom to the Nexus One. It'd be much appreciated. Thanks

    Sent from my Nexus 4 using Tapatalk

    Go mad :) Just a thanks in your OP if your are successful... Good luck :D

    @TJKV @struq

    I think the patch works because to make pvr crash and cause the glitches if I have a lot of apps running then switch to tapatalk or dailer it usually appears with the patch it doesn't :). The error log still appears in logcat but it doesn't result in any graphical glitches.

    I will be uploading the build now for people who want it :)

    Also look forward to Omni rom coming soon ;)
    7
    Hi there,
    i'm trying to bring to you a fresh build of paranoid android (with 4.4.4 source tree).
    As far as i'm talking, i have a working build but it has some bugs/lacks such as not working theme engine, reboot when setting a new background image (o_O), defy parts not showing up in settings, voice quality filters and maybe other things i'm not noticing.
    The last two should be easy to bring because we can use Quarx2k code.
    About the first two i really don't know what to do, i will try with a clean build.

    I will keep you updated
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone