[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)

spalnndsstest

Senior Member
Jun 23, 2014
86
12
0
Perhaps it is easier to by a new batterie?
yes, but it might come discharged, it happend to me already,

the battery of my phone works well, but now the phone doesnt want to charge, and i brick it trying to solve it,

i guess i will end up buying a new phone, and wait for a charger from china, i dont want spaned 30$ in spain for a charger, when i can get it fro 2,5$ shipped from HK

i will give a try connecting directly the usb cables to the batterry, but still i am not sure if this can damage the batt receiving 5v
 

spalnndsstest

Senior Member
Jun 23, 2014
86
12
0
I cannot get RSD Lite to recognize the device even after installing MotorolaDeviceManager drivers,
dont' success to reflash an sbf file... any idea about why windows and RSD Lite dont recognize it?
 

wmiki75

Senior Member
Oct 27, 2011
267
25
53
I installed cm-11-20141027-EXPERIMENTAL-kernel3.0-mb526.zip foe my Defy, from TWRP.
It seems to be fast, but every restart, the phone forget every settings, and want to set up from the language settings :(
I want to install any ROM, but i unable to enter the recovery.
Power ON, and volume down is show a ! dead android. :(
Any other way to enter recovery?
 

wmiki75

Senior Member
Oct 27, 2011
267
25
53
Not working :(
Start from the beigining RSD lite, new sbf, framaroot, 2indinit.
Now i search a fast 4.0+ ROM, but i do not know, what is the best :(
I want to run KODI or SPMC on Defy.
 
Last edited:

spalnndsstest

Senior Member
Jun 23, 2014
86
12
0
Try this instead
does not work, but hotwiring the battery made the trick, i get the message "OK TO PROGRAM; TRANSFER MODE USB"
looks like i need to flash sbf file to make it comes to life again, however the RSD Lite software does not recognize the phone,
i have motorola device manager drivers installed but still no luck,

i have access to the stock recovery, but i need an "update.zip" file to flash, i dont know where to find the stock rom in upade.zip format, or just any rom that can work to flash it, since for some reason its not detected in the pc when i connect it, not recognized device, damn,
 
Last edited:

wmiki75

Senior Member
Oct 27, 2011
267
25
53
How can i make full wipe, between 2 another CM11 install?
TWRP wipe not clear everything on the resized partitions.

Edit:
I start from SBF files.
I found SBF-s, from here:
FW-Defy-Stock
Simple Guide-XDA
XDA-Custom SBF topic

Now, my problem is:
I unable to install GAPPS
Tried the: minimal_Slim_AIO_gapps.4.4.2.build.4.6.zip from TWRP 2800, but it is failed.
Error message: Not enough partition size.
What can i do?
 
Last edited:

Schattenspieler

Senior Member
Oct 18, 2011
87
18
38
I have the occasional random reboot and XDA Premium 5 crashes on startup from time to time. Minor irritations!
I was just looking into this again as random reboots for me increased over the last months, drastically, and found this:
Here is my updated list of the known bugs for the 01-24 nightly (download mirror here) together with jajb's GApps Minimal Edition for Android 4.4.x [240 DPI], as an information both for the Defy users and for @Quarx, @Blechd0se, @SlugZero, @struq, @htto, @m.ksy, @YetAnotherForumUser, @CBongo and the other devs for the further development of CM11.
[…]
Now for the bugs:
30 - Random reboots: This bug doesn't occur anymore at least since 03-15 nightly, as has been reported by several users for the stock frequencies an Vsels. :) Please note that overclocking and undervolting can lead to random reboots and that CM11 is more sensitive for this than e.g. CM7 (using the same OC/UV settings), as several users have reported. Also overclocking the CPU to 266 MHz can lead to random reboots or telephony layer problems, so Quarx set back GPU to default 200 MHz since 06-09 nightly. If it's stable for you, you can still overlock GPU to 266 MHz via Aero Control.
Checking with Aero Control it seems to me, that GPU clock was/is set to 266MHz by default. I set it to 200MHz and my impression is, that there have been no random reboots so far. But I'm not sure, yet, because in another thread was mentioned:
OT: Speaking of which, why does the "Random Reboot Checker" never notifies about it? Aero control can have a debugger built-in, sort of like logcat but more 'powerful' and we can finally put all these log-less speculations behind us!
But at least for now I have not become aware of any random reboots since.
It may also just be coincidence, because their occurence used to fluctuate heavily over time. I'll keep an eye on it and report back:
Edit: Still so much better with GPU @ 200 MHz. Maybe the cell is just worn out and so the overclock kicks it to hard? However, it helps my setup.

ps: I still suffer from the "black screen bug", where the cell is on, but it doesn't react to any button press, so I have to restart it.
 
Last edited:
  • Like
Reactions: iwan2do

spikeofax

Senior Member
Nov 2, 2014
74
13
0
London
I was just looking into this again as random reboots for me increased over the last months, drastically, and found this: Checking with Aero Control it seems to me, that GPU clock was/is set to 266MHz by default. I set it to 200MHz and my impression is, that there have been no random reboots so far. But I'm not sure, yet, because in another thread was mentioned:But at least for now I have not become aware of any random reboots since.
It may also just be coincidence, because their occurence used to fluctuate heavily over time. I'll keep an eye on it, anyway, and report back in a few days.

ps: I still suffer from the "black screen bug", when the cell is on, but it doesn't react to any button press, so I have to restart it.
I'll have a look and report back. Thank you.

Sent from my ASUS_Z00A using XDA-Developers mobile app
 

iwan2do

New member
Aug 10, 2011
1
1
0
I had two problems. Random shut downs and random reboots.

Shut downs were unrelated to CM. I figured out one day that my battery is losing contact and that makes it shut down. I tried tapping my phone upside-down on the palm of my hand and it would immediately shut down or reboot. To resolve this I just put a thin piece of plastic next to the battery so that it fits more tightly. No more shut downs after that.

For random reboots I changed GPU clock to 200MHz with Aero Control 3 days ago and I had no problems since then.

Edit: I have 254 hours uptime now so this seems to be the solution for the reboots. Thanks Schattenspieler.
 
Last edited:
  • Like
Reactions: Schattenspieler

FLFS

New member
Jan 1, 2017
2
0
0
Hi, I'm having a weird issue with my Defy.
It's running Quarx CM 11, and it had some random reboots / power offs related to battery and clock, but was working OK-ish until 1:00 AM (approximately) today (01/01/2017). When I woke up around 8:00 AM I found it was stuck in the "Welcome to Cyanogenmod" screen. I tried to configure again my account, time zone, etc, but then it started to pop up error messages: Media Storage stopped, android.process.acore stopped, android.process.media stopped, and some others related to apps randomly crashing. I managed to type in my account settings, it restarted as is supposed to, but then again showed the welcome screen.
I just want to know if there is any solution to this, other than reflashing the phone.
Also, I just found out in XDA that CyanogenMod is officially dead, but I don´t think that's directly related to my problem. The most similar issue I found is from 1st Jan 2013, when some HTC devices had a similar trouble caused by hardcoded "2012" references, and contacts with DOB Feb 29 (It was something like 2012 (as 2016 too) was a leap year. The harcoded references caused some issue with contacts, alarms, calendar, etc when not in a leap year)

UPDATE Jan 2 2017: Phone boots with errors, but after factory reset from TWRP seems to work. Google account logs in OK, Titanium Backup installs OK, going to reinstall all the apps.

UPDATE Jan 3 2017: Defy OK, all app backups I had worked fine, except from some minor configurations. The fact that it stopped showing some errors on Jan 2 makes me think this was something like the HTC 2012-2013 leap year bug (The devices were affected only on Jan 1 2013).
 
Last edited: