I used 11-7_GApps_Core_4.4_signed.zip from androidfilehost[dot]com/?fid=23212708291674813
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)
- Thread starter Quarx
- Start date
@Quarx -
Please fix the link for the recovey - whould be - http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip.
Good job on this one!
You've made it for the Defy before all the Samsung/HTC mods got it right.:good:
Hey guys, please test this gapps and let me know if it works fine. I cannot test it myself until WiFi works, unfortunately.
EDIT: Removed the link, apparently doesn't get flashed successfully. Will look into it when I can.
About Slimkat, I cannot compile it fully until the slim guys merge a few things into their repos. I could fork the repos and do it myself but if they are going to do it themselves later then there is no point really. Also I'd rather wait for Quarx to finish his work first and then do mine, since he seems to be very active on git right now
EDIT: Removed the link, apparently doesn't get flashed successfully. Will look into it when I can.
About Slimkat, I cannot compile it fully until the slim guys merge a few things into their repos. I could fork the repos and do it myself but if they are going to do it themselves later then there is no point really. Also I'd rather wait for Quarx to finish his work first and then do mine, since he seems to be very active on git right now
Last edited:
I'm also waiting for WiFi to become operational before I try KitKat, right now my DEFY is my backup device since I replaced it back in September, so it has no SIM card to connect via 3G.
Couldn't add a Google Account with 11-7_GApps_Core_4.4_signed.zip from androidfilehost[dot]com/?fid=23212708291674813
I clicked Accounts, then Google, then nothing happened, no new window, like I did not click on it.
Confirmed bugs what occured: No Wifi, No phone call (Hungary)
Features I miss: Volume rocker wake, Mute sound when changing Sound power
It's very cool considering it's not for daily use yet...!!!
I clicked Accounts, then Google, then nothing happened, no new window, like I did not click on it.
Confirmed bugs what occured: No Wifi, No phone call (Hungary)
Features I miss: Volume rocker wake, Mute sound when changing Sound power
It's very cool considering it's not for daily use yet...!!!
[non-dev/offtopic]
I tipped one of the major Dutch IT websites and they wrote an article on the Defy as one of the first 512MB devices with 4.4, thanks to Quarx! Here's the link (Dutch):
http://tweakers.net/nieuws/92479/eerste-android-44-rom-voor-smartphone-met-512mb-ram-verschijnt.html
I tipped one of the major Dutch IT websites and they wrote an article on the Defy as one of the first 512MB devices with 4.4, thanks to Quarx! Here's the link (Dutch):
http://tweakers.net/nieuws/92479/eerste-android-44-rom-voor-smartphone-met-512mb-ram-verschijnt.html
I think its not related to this gapps package because im using it on my n4 with cm11 and Google acc is working fine.
So the problem is somewhere in our rom.
Gesendet von meinem Nexus 4 mit Tapatalk 2
Little OT: KitKat for the Defy made the news in one of the most important android blogs in spanish: http://www.elandroidelibre.com/2013...ivos-con-512mb-ram-como-el-motorola-defy.html
Assuming you could enter the boot manager (by pressing 'volume down' when the blue led comes on during boot) you probably could have pushed a functioning recovery to the device through adb. One of the problems I've seen with recent recovery is the absence of a functional /etc/fstab, leading to failure when it tries to mount filesystems. If this is the case you can just mount them manually. Boot the phone into the boot manager and enable adb (tools -> adb). Unzip whatever flashable zip you intend to push to your device - I'll take update-recovery.zip as an example. Open a shell on the device. Mount the filesystems you intend to push files to. Push the files to the device. Modify the file attributes according to the edify script (META-INF/com/google/android/updater-script). Run sync. U
mount the file systems. Reboot, go to the boot manager and try to start recovery.
Code:
(on host)
$ mkdir recovery
$ cd recovery
$ unzip /path/to/update-recovery.zip
$ adb devices -l
List of devices attached
0123456789ABCDEF device usb:1-3
DEADBEEFDEADBEEF device usb:1-2
The phone is attached to usb:1-2
$ adb -s usb:1-2 shell
# mount
...list of mounted filesystems appears, if the target filesystem (usually /system) is not mounted you'll have to mount it manually:
# mount /dev/block/mmcblk1p21 /system
(on host)
$ adb push system/bootmenu/2nd-boot/ramdisk-recovery /system/bootmenu/2nd-boot/
$ adb push system/bootmenu/2nd-boot/zImage /system/bootmenu/2nd-boot/
(on phone, through adb)
# ls -l /system/bootmenu/2nd-boot/
(the files you just pushed should be there, if not, rinse, repeat)
# chmod 644 /system/bootmenu/2nd-boot/*
# sync
# umount /system
# reboot
when the blue led comes on press volume down to enter the boot manager, from there start recovery
Works fine for me. You have to format ext4.it worked for me after that.
Sent from my MB526 using Tapatalk
After installing this rom or 4.3, how can I go back to cm7 without having to flash with rsdlite!
Im really tired of doing this!
Thanks!
Sent from JAGs phone!
Im really tired of doing this!
Thanks!
Sent from JAGs phone!
Cause of BAYER camera not working - now for the solution...
The BAYER camera does not work as many have noticed. Running strace on the MediaServer process (which interfaces to the actual hardware) produces the following output:
The failure happens when the code tries to mmap2 a region:
EINVAL can mean quite a few things here. The library is exactly identical to the version used in earlier releases, it used to work there. Given this fact I'd look at bionic (the C library) as the first candidate for this bug. There has been quite a bit of change in bionic, eg. is has been changed over from plain C to C++. Of course it is always possible that something else causes the EINVAL error but bionic looks like a good first start.
The BAYER camera does not work as many have noticed. Running strace on the MediaServer process (which interfaces to the actual hardware) produces the following output:
Code:
[pid 2616] open("/system/lib/libbayercamera.so", O_RDONLY) = 21
[pid 2616] read(21, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0أ\0\0004\0\0\0<z\1\0\2\0\0\0054\0 \0\4\0(\0\23\0\22\0", 52) = 52
[pid 2616] mmap2(NULL, 4096, PROT_READ, MAP_PRIVATE, 21, 0) = 0x40b3e000
[pid 2616] madvise(0x40b3e000, 4096, 0xc /* MADV_??? */) = 0
[pid 2616] lseek(21, -8, SEEK_END) = 97588
[pid 2616] read(21, "\0\0\220<A2>PRE ", 8) = 8
[pid 2616] mmap2(0xa2900000, 98304, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa2900000
[pid 2616] madvise(0xa2900000, 98304, 0xc /* MADV_??? */) = 0
[pid 2616] mmap2(NULL, 89408, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 21, 0) = -1 EINVAL (Invalid argument)
[pid 2616] close(21) = 0
[pid 2616] munmap(0x40b3e000, 4096) = 0
[pid 2616] mprotect(0x40e64000, 4092, PROT_READ) = 0
[pid 2616] mprotect(0x40721000, 4092, PROT_READ) = 0
[pid 2616] mprotect(0x404b2000, 4092, PROT_READ) = 0
[pid 2616] mprotect(0x40145000, 4092, PROT_READ) = 0
[pid 2616] mprotect(0x4000f000, 4092, PROT_READ) = 0
[pid 2616] writev(9, [{"\6", 1}, {"JordanCameraWrapper\0", 20}, {"dlopen() error: dlopen failed: couldn't map \"libbayercamera.so\" segment 1: Invalid argument\n\0", 93}], 3) = 114
Code:
[pid 2616] mmap2(NULL, 89408, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 21, 0) = -1 EINVAL (Invalid argument)
Fix for Bayer camera: https://github.com/Quarx2k/android_system_core/commit/7d82982f9e868a67fda6acf077b00cea0f8d1361
At least, we can get preview now
At least, we can get preview now
Format data into ext3, flash CM7 as usual.
If you're tired of doing this then why did you install a distribution which was clearly marked as alpha-quality, not ready for daily use?
That aside it should not be to hard to go back without flashing stock. You could try flashing it with current recovery, just make sure to format /data and /cache to ext3 as cm7 probably does not like ext4. Or maybe just flash stock anyway to make a clean break from all this meddling, and return when you're well-rested?
@Quarx hey, you may already be aware of this but there are some big-ish changes incoming on CM for the TI wlan, most importantly this one: http://review.cyanogenmod.org/#/c/51224/
No idea if that'll help getting things working on Kitkat, but maybe it's worth a try.
As always, thanks for the great work :good:
No idea if that'll help getting things working on Kitkat, but maybe it's worth a try.
As always, thanks for the great work :good:
error (6) Installation aborted.Hey guys, please test this gapps and let me know if it works fine. I cannot test it myself until WiFi works, unfortunately.
About Slimkat, I cannot compile it fully until the slim guys merge a few things into their repos. I could fork the repos and do it myself but if they are going to do it themselves later then there is no point really. Also I'd rather wait for Quarx to finish his work first and then do mine, since he seems to be very active on git right now
Last edited:
Preview as in 'image on screen portraying subject camera is pointed at'? Not here, see my previous post for the reason. This was tested with the current repo, including the linked change. the camera app launches to a black preview.Fix for Bayer camera: https://github.com/Quarx2k/android_system_core/commit/7d82982f9e868a67fda6acf077b00cea0f8d1361
At least, we can get preview now
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