FORUMS
Remove All Ads from XDA

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

1,318 posts
Thanks Meter: 18,847
 
Post Reply Email Thread
8th December 2013, 09:44 AM |#1001  
Member
Thanks Meter: 278
 
More
AOSP build
For those who are missing AOSP, here is a fresh new build.
This is based on Quarx's repo (seems abandoned?), build with recent updates.

Notes:
Code:
2.6.32 kernel
updated to AOSP Android 4.4.1 (most parts of the system)
all hardware-related fixes in Quarx cm11 build
app2sd fixed
add apn list (aosp specific)
chromium black box fixed (aosp specific)
full language support
low_ram flag enabled by default, toggle with AeroControl
no defyparts, replace your own bp_nvm_default before flash
no fm
trimed ringtones
Bugs:
Code:
common bugs of defy 4.2+ (bt headset, no phonecall sound when bt enabled, mute mic...)
panorama not working
wifi-tether not working
occasional graphics glitches
you say ;) expect to have less random bugs than cm, or more
Why not complete 4.4.1?
Because there are problems that I can't fix.

Parts still at original 4.4:

* frameworks_av -need-> frameworks_native -need-> system_core --> hang at boot
stuck after green led, adb cannot connect
tried re-apply this fix, didn't help

*frameworks_opt_telephony --> broken mobile data
log attached

will be glad if you would like to help


download: https://drive.google.com/folderview?...EU&usp=sharing

Thanks to TJKV for guidance and of course Quarx for his fundamental work.
Attached Files
File Type: txt mobile_data_log.txt - [Click for QR Code] (159.8 KB, 49 views)
The Following 16 Users Say Thank You to struq For This Useful Post: [ View ] Gift struq Ad-Free
 
 
8th December 2013, 10:59 AM |#1002  
Senior Member
Thanks Meter: 2,754
 
More
Quote:
Originally Posted by struq

For those who are missing AOSP, here is a fresh new build.

tried re-apply this fix, didn't help

Nice
Yeah I'm waiting for that fix to be updated for 4.4.1 too.

EDIT: The log attachment gives a 404 error. Can you pastebin it?

Also it is better to wait for that fix I think, having some branches on 4.4 and some on 4.4.1 is a bit messy. Let quarx do it when he has time and then you can build aosp, or you can try to figure out how the fix should be for 4.4.1 and try building before

Sent from my MB526
8th December 2013, 12:59 PM |#1003  
Junior Member
Flag Barreiras
Thanks Meter: 3
 
More
Quote:
Originally Posted by justjr

Well, I've been using the EU baseband for somedays in Brazil, and 2 days ago changed to the right baseband with the MFUNZ_DEFY.BasebandSwitcherV4.1. It seems that changed baseband really helped with battery duration, europe was working but draining srsly power. I use to get 5/h minimum power drain with deep sleep, now gone down to 2/h again.
Also, I don't get any more problems with signal at boot, no need to toggle airplane mode. Hurray!

Does not work for me.

Enviado de meu MB526 usando Tapatalk
8th December 2013, 01:22 PM |#1004  
Euro_Rules's Avatar
Senior Member
Flag Mumbai
Thanks Meter: 83
 
More
4.4 Gapp is included ?
8th December 2013, 01:37 PM |#1005  
Member
Thanks Meter: 11
 
More
Is this ROM already stable for daily use? or what are we missing yet? I can't find this answer, the thread is a mess
8th December 2013, 01:59 PM |#1006  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by DEFIER

I have a red lens Defy+ and its running on 5-12 and its working normal for me. WIFI/3G/calls/Messages/e-mail have no issues at all.
But that's on on Dalvic that its without any problems. I tried ART and as with most others, found that it can be avoided for a while.

If you are flashing the 5-12 rom, get the BaNKS core GAPPS for 4.4 here.



I am using the 11-26 one that I have attached. The above link has 12-6 GAPPS now which I am not sure about.

Thanks DEFIER
I'm going to give it a try today
8th December 2013, 02:15 PM |#1007  
Member
Thanks Meter: 278
 
More
Quote:
Originally Posted by TJKV

Nice
Yeah I'm waiting for that fix to be updated for 4.4.1 too.

EDIT: The log attachment gives a 404 error. Can you pastebin it?

Also it is better to wait for that fix I think, having some branches on 4.4 and some on 4.4.1 is a bit messy. Let quarx do it when he has time and then you can build aosp, or you can try to figure out how the fix should be for 4.4.1 and try building before

Sent from my MB526

Do you encounter the same boot hang? I thought this is related to the gralloc fix because I couldn't figure out what else could cause booting problems.

The log is about broken data connection after merging telephony.
http://pastebin.com/wHQiW91G
To explain a bit more, when the phone tries to connect (about every few minutes or so), the E sign (I'm on EDGE network) appear and vanish in a second, although the previous fix by Quarx was still there. I was suspecting this commit is causing this. As shown it is included in slim too, do you have similar problems?
The Following User Says Thank You to struq For This Useful Post: [ View ] Gift struq Ad-Free
8th December 2013, 02:24 PM |#1008  
Senior Member
Thanks Meter: 151
 
More
Quote:
Originally Posted by struq

For those who are missing AOSP, here is a fresh new build.
This is based on Quarx's repo (seems abandoned?), build with recent updates.



Notes:
Code:
updated to AOSP Android 4.4.1 (most parts of the system)
all hardware-related fixes in Quarx cm11 build
app2sd fixed
add apn list (aosp specific)
chromium black box fixed (aosp specific)
full language support
low_ram flag enabled by default, toggle with AeroControl
no defyparts, replace your own bp_nvm_default before flash
no fm
trimed ringtones
Bugs:
Code:
common bugs of defy 4.2+ (bt headset, no phonecall sound when bt enabled, mute mic...)
panorama not working
you say ;) expect to have less random bugs than cm, or more
Why not complete 4.4.1?
Because there are problems that I can't fix.

Parts still at original 4.4:

* frameworks_av -need-> frameworks_native -need-> system_core --> hang at boot
stuck after green led, adb cannot connect
tried re-apply this fix, didn't help

*frameworks_opt_telephony --> broken mobile data
log attached

will be glad if you would like to help


download: https://drive.google.com/folderview?...EU&usp=sharing

Thanks to TJKV for guidance and of course Quarx for his fundamental work.




Installing right now. Seems good so far. I had a lot of trouble with the last slimkat+art. The phone would crash all the time while restoring apps with TB or installing from market. Now no crash at all (still restoring). Gapps still force closes but that's not a big deal, I think.

I have yet to reboot the phone to see, if there are boot hangs that require pulling the battery. With Slimkat I had to pull the battery a couple of times each time till the phone would eventually boot up fine. I suspect it's an issue with the gapps cause without any gapps, the phone would boot without any troubles.
8th December 2013, 02:32 PM |#1009  
ennarr's Avatar
Senior Member
Flag Algiers
Thanks Meter: 196
 
More
WIFI Tether
Anyone managed to make wifi tether work on 5 Dec Build?

for me it does'nt work
The Following User Says Thank You to ennarr For This Useful Post: [ View ] Gift ennarr Ad-Free
8th December 2013, 02:43 PM |#1010  
Senior Member
Thanks Meter: 2,754
 
More
Quote:
Originally Posted by struq

Do you encounter the same boot hang? I thought this is related to the gralloc fix because I couldn't figure out what else could cause booting problems.

Yes I get that boot hang too without that fix on 4.4.1.

Quote:

The log is about broken data connection after merging telephony.
http://pastebin.com/wHQiW91G
To explain a bit more, when the phone tries to connect (about every few minutes or so), the E sign (I'm on EDGE network) appear and vanish in a second, although the previous fix by Quarx was still there. I was suspecting this commit is causing this. As shown it is included in slim too, do you have similar problems?

See here, you can make the log more useful, for example by including the time of each event to correlate to when you saw the E flicker etc. You can look for the offending log entry and then search for that log event in the source code to see where the error happens. For example take this message (i've chosen one at random, not necessarily the problem message)

Code:
D/MobileDataStateTracker( 1644): hipri: setDetailed state, old =CONNECTING and new state=CONNECTED
Google searching for "MobileDataStateTracker" gave me this link. In there searching for "and new state=" gave me the location of the log entry. Now look at the history of that file and see what commit it is related to etc. At least that's what I would do

Quote:
Originally Posted by Hasuris

I have yet to reboot the phone to see, if there are boot hangs that require pulling the battery. With Slimkat I had to pull the battery a couple of times each time till the phone would eventually boot up fine. I suspect it's an issue with the gapps cause without any gapps, the phone would boot without any troubles.

What gapps did you use? No problems here with the slim based gapps I uploaded. Also check with dalvik if you are using art...anyway tell in my thread not here
The Following User Says Thank You to TJKV For This Useful Post: [ View ] Gift TJKV Ad-Free
8th December 2013, 03:17 PM |#1011  
Senior Member
Thanks Meter: 151
 
More
Wuhu, no boothangs for the AOSP-build!
Post Reply Subscribe to Thread

Tags
baseband switcher, led, quarx for world emperor, quarx is still a god

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes