[hlte][2014/DEC/07][CM11/12] Yank555.lu kernel v1.1c-beta6

[Raver099]

Uhm it didn't reboot btw, just got stuck like you..

[yank555]

I just don't know about CM on the hlte

JP.

[Raver099]

As we speak it seems stable again....

[yank555]

I've reenabled mdnie hijack (recovery config update) ... booted ... unlocked and boom ... battery pull.

I think I'll just remove mdnie hijack altogether, colors can be changed in CM anyway.

JP.

[yank555]

CM11 Beta Kernel Update

A quick compiliation with mdnie hijack completely removed.

Changelog CM11-hlte v1.1-beta14 (22/07/2014)

• removed MDNIE control interface
• updated some Aroma default for Yank555.lu profile

• Removed, same as beta13 minus mdnie which is absolutely fine

[yank555]

I've restored all my apps, started each one of them, restored config, the whole 9 yards, not a single glitch on beta14 ...

Of course, now I wrote this, I have jinxed it

Rebooted (manually to go to recovery), and battery pull ...

So we have a change, if it's progress, that's another question

JP.

Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.

[Raver099]

I don't get it. What happened exactly mate?

[capnkrunch]

Man, sounds like CM is a mess right now. I went back to deunified after a frustrating series of events involving 2 random reboots within less than 10 minutes when I desperately needed my phone working and luckily the htlexx works for me. Off topic question (hltexx thread locked so I can't ask it there), where did you get the source for the hltexx kernel? t
There's no old deunified CM repos so that I could find. Did you just checkout whatever the last preunification commit was?

One more question relating to my troubles with compiling this guy: what version of Ubuntu do you run on your VM? I've been using 14.04 but I wonder if 13.10 is the answer to my problems.

Also, I recently developed some first hand respect for your decision to stop keeping this patched up to the lastest 3.4.x. I've been playing around with my manta's kernel since giving up on this one and decided to start by patching up to 3.4.99. I've spent the last week and a half sorting through the rejects and fixing compile errors and I'm still not done. It's hard to imagine I didn't create a number of runtime errors as well after that mess. I'm pretty sure stability will end up being adversely affected and performance boosts will be negligable. Overall seems like a waste of time.

[yank555]

I don't get it. What happened exactly mate?

Well I was happy, as all went smooth setting all my ~300apps up, so I wanted to share my happyness, and I was typing that, boom screen went black

So yes, CM is a mess right now for hlte (at least), I agree with my forespeaker

JP.

Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.

[yank555]

Man, sounds like CM is a mess right now. I went back to deunified after a frustrating series of events involving 2 random reboots within less than 10 minutes when I desperately needed my phone working and luckily the htlexx works for me. Off topic question (hltexx thread locked so I can't ask it there), where did you get the source for the hltexx kernel? t
There's no old deunified CM repos so that I could find. Did you just checkout whatever the last preunification commit was?

Yes, you could just check out to the last commit before unification, somewhere around Jan. 30th.

But in my case I had my hltexx kernel, and rebased to a new repo when I went over to hlte, so I just reactivated my old repo

One more question relating to my troubles with compiling this guy: what version of Ubuntu do you run on your VM? I've been using 14.04 but I wonder if 13.10 is the answer to my problems.

Oh I have a very old buddy, 10.10, never change a winning team

Also, I recently developed some first hand respect for your decision to stop keeping this patched up to the lastest 3.4.x. I've been playing around with my manta's kernel since giving up on this one and decided to start by patching up to 3.4.99. I've spent the last week and a half sorting through the rejects and fixing compile errors and I'm still not done. It's hard to imagine I didn't create a number of runtime errors as well after that mess. I'm pretty sure stability will end up being adversely affected and performance boosts will be negligable. Overall seems like a waste of time.

Agreed, speed boost is not what I'd expect from upstreaming, more of small bug fixes, hence stability, but as you very well put it, risk of screwing up a conflict and reducing stability makes this rather pointless, espcially given the effort required

On 3.0.y that went pretty smoothly for my i9300 kernel, 3.4.y has been more challenging, or I've grown less patient, also an option

JP.

Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.