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

[Lord_Flaya]

As for the two battery icons, you must be using gravity box or xblast which is overlapping with the stock icon and hence, the two batteries.

Sent from my MB526 using Tapatalk

Yes I did before. Noticed I had some leftovers from xblast on my backup.. cleaned up and it looks better. However the reboots still occur even with zram off.

Sent from my MB526 using XDA Premium 4 mobile app

 

[ktmbikerman]

Hi All, its been a while since I flashed a Defy, so if you could bare with me i'd appreciate some guidence.

I'm wanting to upgrade a mate's Defy red lense running CM7 to CM11

I installed the update recovery zip, rebooted back into custom recovery, then tried to install the CM11 zip, which gave a some error 7. I know this is related to the version of recovery, but I would have thought the recovery update zip on the OP was the correct one. Anyway, this resulted in a boot hang (on the M logo)

I'm busy reflashing the sbf at the moment... Any tips greatly appreciated

 

[hotdog125]

There's a TWRP zip by TJKV with which you can avoid having to install CM10/10.1 and directly install CM11 after sndinit.

Edit - http://forum.xda-developers.com/showthread.php?p=48501247

After root and sndinit, install this zip and reboot into this newer recovery. Then flash CM11 with banks core gapps.

Sent from my Nexus 7 using Tapatalk

 

[YetAnotherForumUser]

This is a cm patch in review: http://review.cyanogenmod.org/#/c/55805/. We will have it when it passes the review, though I don't know when that will happen as it has been there since dec 14. So I just pick it up in advance. Quarx doesn't use a forked repo of system/netd so I couldn't make a pull request.


Regarding the reboot issue, would you try disabling zRAM in Settings/Performance and see if it helps? zRAM is enabled by default in CM11 but from my experience in previous versions, it is not so stable and do cause ramdom reboots sometimes. Since this part of code in kernel hasn't been touched when we move on to 4.4, I guess the problem is still there.


+1 for this.
But 4.3 also use this command: https://android.googlesource.com/pl...r1/wifi/java/android/net/wifi/WifiNative.java

    public boolean setSuspendOptimizations(boolean enabled) {
        if (mSuspendOptEnabled == enabled) return true;
        mSuspendOptEnabled = enabled;
        if (enabled) {
            return doBooleanCommand("DRIVER SETSUSPENDMODE 1");
        } else {
            return doBooleanCommand("DRIVER SETSUSPENDMODE 0");
        }
    }

Maybe somewhere else is broken?

The interface to wpa_supplicant has been changed quite a bit, maybe it 'just did not work' in earlier versions. Another possibility is that mSuspendOptEnabled was set in previous versions but is unset in 4.4. The actual configuration (as shown in the 'Advanced' page of the wifi settings activity) was identical between the testdevices.

---------- Post added at 01:39 PM ---------- Previous post was at 01:23 PM ----------

Would it be useful to get such a log? Maybe I was misunderstood, but after the bootanimation I get the booted ROM ... I wasn't talking about bootloops but about the reboot-to-recovery issue on MB525, after Antiga Prime suggested that it could be due to an incomplete wipe.

Ah, in that case I misunderstood in assuming that you were talking about an actual boot loop.

---------- Post added at 01:54 PM ---------- Previous post was at 01:39 PM ----------

I have this issue too, but it's not new for me; I had it on CM10.2 and even sometimes on CM7. As a workaround, I use this Wifi Timeout app, which properly powers the wifi off when the screen is off, and back on again when the screen wakes. This app has the added advantage of allowing you to choose a custom wifi timeout length between 1 second and 5 minutes. (The default timeout length with android is 15 minutes after the screen goes off, so using this app to turn the wifi off more quickly may help to save battery.)

Strange that you had this issue on earlier versions while I did not... maybe your device configuration was different from mine? I have mine configured for 'Sleep except when plugged in' with 'battery optimisations' enabled. All the other options are turned off (background scanning, notification of new networks, etc). The devices are configured for 2.4GHz only, European channels.

While that app you mention would work, I'd rather fix the issue. Applying band-aids like this reminds me to much of 'that other operating system'...

 

[fede_arg]

I just updated to from 10.12 nightly to 29.12 (plus update) and now the home/back/search buttons work very weird.
Home button doesn't work almost at all and back button has to be pressed several times to work (I don't have "Allow custom buttons" enabled).

I reverted to 29.12 and everthing was smooth again, so I re flashed to 29.12 and again buttons not working.

I haven't seen any post about this bug on the thread, is it happening just to me?

 

[ktmbikerman]

There's a TWRP zip by TJKV with which you can avoid having to install CM10/10.1 and directly install CM11 after sndinit.

Edit - http://forum.xda-developers.com/showthread.php?p=48501247

After root and sndinit, install this zip and reboot into this newer recovery. Then flash CM11 with banks core gapps.

Sent from my Nexus 7 using Tapatalk

Thanks... all worked well from CM7 > Froyo > CM11

 

[maango]

I just updated to from 10.12 nightly to 29.12 (plus update) and now the home/back/search buttons work very weird.
Home button doesn't work almost at all and back button has to be pressed several times to work (I don't have "Allow custom buttons" enabled).

I reverted to 29.12 and everthing was smooth again, so I re flashed to 29.12 and again buttons not working.

I haven't seen any post about this bug on the thread, is it happening just to me?

I had the same issue on the 10.12.13 build but it solved by after flashing the 29.12 and then the 03.01.14 update (never used only 29.12)
However, I ****ed up pretty bad and needed to flash an .SBF and then moved from stock ROM directly to 21.12, after that it worked without any issue.

Hope this might help.

 

[Proverbs2]

Strange that you had this issue on earlier versions while I did not... maybe your device configuration was different from mine? I have mine configured for 'Sleep except when plugged in' with 'battery optimisations' enabled. All the other options are turned off (background scanning, notification of new networks, etc). The devices are configured for 2.4GHz only, European channels.

My configuration on CM10.2 was as follows: network notification on, background scanning off, avoid poor connections off, frequency band auto, United States region code, and battery optimizations off (if I remember correctly, although I have optimizations enabled now on CM11). The problem may have been due to a dirty flash from CM10.1, which is why I never reported it. (I did a clean install of CM11, though.)

I don't remember my configurations for CM7, and now that I think about it, I recall the problem there was a bit different: I had a problem with wifi wakelocks keeping the CPU out of deep sleep. Using the Wifi Timeout app solved the wakelock issue for me on CM7, and that's why I started using it. I haven't had the wakelock issue on CM10 or CM11, fortunately.

While that app you mention would work, I'd rather fix the issue. Applying band-aids like this reminds me to much of 'that other operating system'...

LOL

I agree with that principle in general, but this is such a minor issue that I don't want the devs to worry about it, at least until the bigger problems (like bluetooth) are solved.

 

[fede_arg]

I had the same issue on the 10.12.13 build but it solved by after flashing the 29.12 and then the 03.01.14 update (never used only 29.12)

I tried both:
- flashing 29.12 and the update without rebooting. wipe cache and dalvik.
- flashing 29.12, wipe cache+dalvik and let it boot once. flash update, wipe cache and dalvik and reboot.

Same issue in both cases

I may have to try doing a clean install but I don't want to start all over again :S

 

[hrk]

As i know the separation of commands are ;
So replace those : with ;
in

PATH=/sbin:/system/xbin:/system/bin[/FONT]

Sent from my MB525 using xda app-developers app

Those aren't commands, it's the explicit order in path resolution.

Using ; will result in the first expression being evaluated, then errors of "missing command", since the remaining items are just directory names.

Inviato dal mio HTC Vision con Tapatalk 2

 

[dkv2222]

Yes I did before. Noticed I had some leftovers from xblast on my backup.. cleaned up and it looks better. However the reboots still occur even with zram off.

Sent from my MB526 using XDA Premium 4 mobile app

Can't say about reboots because my defy is very stable. My uptime is just over two days. And the last reboot was a reboot I did. So...... Clean install maybe.

Sent from my MB526 using Tapatalk

 

[Rawwr]

i m unable to use xblast tools in cm11 :-s
please help

 

[Lord_Flaya]

Can't say about reboots because my defy is very stable. My uptime is just over two days. And the last reboot was a reboot I did. So...... Clean install maybe.

Sent from my MB526 using Tapatalk

Is clean install..

Sent from my MB526 using XDA Premium 4 mobile app

---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------

i m unable to use xblast tools in cm11 :-s
please help

I use it, works good tho some elements isn't compatible yet. Update to latest version and compliment with gravity box, is my tip. Sorry if OT

Sent from my MB526 using XDA Premium 4 mobile app

 

[su8044]

I did a full system wipe before Installing 29/12 , 03/01 update and core gapps. After that thetering was missbehabing a bit but worked. I installed the fix but it did nothing. I just wanted to let you know that I have the defy 525 red lens, and:
- reboot to recovery does not work
- thetering works only after connecting phone to PC, turning on thetering and then rebooting PC while connected.
- I have no random reboots whatsoever. 22 hours uptime only though
- Wi-Fi and Mac address shown without problems
- no idea on Bluetooth issues, i haven't used it yet

My defy is faster and more responsive than ever, @Quarx and google really did their homework on 4.4 kitkat. Thanks to all developers specially @Blechd0se, @TJKV and @okij

tapatalk 4 or xda app? which is better?

 

[imharshadpatel]

s2w bug

@Blechd0se I am using latest cm11 (29/12) with update 3/1 on my defy plus. I enabled s2w. it is working only one way. i mean if i sweep over touch buttons from right to left, screen turns off.but then i m not able to turn it on by any sweep gesture. if i turn screen off by power key, then only i can wake the phone by sweeping on touch keys from left to right.

 

[Android_74]

@Blechd0se I am using latest cm11 (29/12) with update 3/1 on my defy plus. I enabled s2w. it is working only one way. i mean if i sweep over touch buttons from right to left, screen turns off.but then i m not able to turn it on by any sweep gesture. if i turn screen off by power key, then only i can wake the phone by sweeping on touch keys from left to right.

That's strange +_+

Sent from my MB526 using XDA Premium 4 mobile app

 

[leandrolutz]

@Blechd0se I am using latest cm11 (29/12) with update 3/1 on my defy plus. I enabled s2w. it is working only one way. i mean if i sweep over touch buttons from right to left, screen turns off.but then i m not able to turn it on by any sweep gesture. if i turn screen off by power key, then only i can wake the phone by sweeping on touch keys from left to right.

I did'nt get it...
To enable it you did the process by ADB or terminal emulator?

 

[prateekranka]

@Blechd0se I am using latest cm11 (29/12) with update 3/1 on my defy plus. I enabled s2w. it is working only one way. i mean if i sweep over touch buttons from right to left, screen turns off.but then i m not able to turn it on by any sweep gesture. if i turn screen off by power key, then only i can wake the phone by sweeping on touch keys from left to right.

+1

Sent from my MB526 using xda app-developers app

 

[mauroaraujo]

+1

Sent from my MB526 using xda app-developers app

I had this problem also...
However, the biggest proble is: All te time that I reboot my mobile, I must to anable it again...

 

[Proverbs2]

I had this problem also...
However, the biggest proble is: All te time that I reboot my mobile, I must to anable it again...

If you enable S2W with S2W Switch Free and use the "set on boot" feature, you'll only have to enable it once

By the way, @Blechd0se noted in an earlier post that S2W only seems to work for a few seconds after turning off the screen. After that it becomes unresponsive, or at least less reliable. In my own experiments, I found that S2W can still wake the phone, even after the display has been off a long time, but it takes a lot of attempts. For example, I'll swipe my finger back and forth on the screen for half a minute, and then the screen will finally turn on

In contrast, if I try sweeping immediately after the screen goes off, I can usually wake the phone in one or two sweeps. These gestures can be anywhere on the screen, and almost any gesture works: swiping left to right, right to left, or even drawing circles on the screen.

Edit: I also have the bug mentioned above by @imharshadpatel. If I turn off the screen using the sweep gesture (over the touch buttons from right to left), then I cannot wake the device by any gesture, even after many attempts.