[UnORom][3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][29 July][Final]

JanSpatschek

Senior Member
Dec 1, 2012
315
54
0
Waidhofen
www.rlbrt.de
Found a huge issue!
If you try and lock the screen with an alarm set the phone will hard reboot to the HTC splash! Does this every time I lock my phone now, even with no alarm set :(
This was probably what I reported above.

Clean flashed this ROM today through 4ext and got a random reboot EVERY single time the display went dark after screen timeout. Like e.g. the screen went off and 10 seconds later the HTC splash screen showed up again. I will include a last_kmsg: https://drive.google.com/file/d/0B5xpEXQcSQncTmxGOGJNQk5iSk0/edit?usp=sharing
 
Last edited:

JanSpatschek

Senior Member
Dec 1, 2012
315
54
0
Waidhofen
www.rlbrt.de
Yeah must be, that last_kmsg is extremely useful! Hopefully somebody in the know sees it and can provide a fix.

Seems to point to something to do with 'clock-local.c' , sdc3_p_clk Status stuck at 'on' seems to be the problem I think.
Not that I know what that is!
Yeah, it wasn't like I didn't have multiple opportunities to get that last_kmsg ;) Weird, but I think this will be fixed soon. Must be something in the new kernel.
 

shantur

Senior Member
Dec 6, 2010
1,094
3,073
0
I got some progress on HDMI. Well, i just hex-edited quickly liboverlay.so to change the line "int Overlay::sDpyFbMap[DPY_MAX] = {0, -1,-1};" to "int Overlay::sDpyFbMap[DPY_MAX] = {0, 1,-1};" to make the device be fb1 by default and not fb-1 (I don't know how to properly fix it, it should be fixable without changing overlay.cpp). And i got hdmi semi-working, it's very buggy, sometimes the phone hangs completely. When i connect it first i can see the upper part of an image and the bottom part is blue. When i reconnect the cable i can see the whole image fine but the screen flickers every second or so so it's not usable. Attaching a patched liboverlay.so in a flashable zip if someone else wants to test and 2 fotos showing what i get.

Also I'm suggesting to Flemmard to add this line into init.pyramid.rc:
chown system system /sys/devices/virtual/graphics/fb1/hpd

Without this it gives more errors in logcat :)
This is something in progress.
 

cclaxx

Senior Member
Jul 5, 2012
144
48
0
milano
Strange, neither me or Flemmard have this issue. Can anyone else confirm this?
Also which nightly are you using
hi @shantur what are your thoughts on the battery draining? for me the consumer is really high but maybe the problem is my battery.
In any case I attach some screen of my consumption if it can help
Screenshot_2014-03-25-10-52-09.png

Screenshot_2014-03-25-10-52-57.png

Screenshot_2014-03-25-10-53-05.png
 

lovendsuicide

Senior Member
Jul 19, 2011
406
179
0
Porto
Strange, neither me or Flemmard have this issue. Can anyone else confirm this?
Also which nightly are you using
Just tried three times to set an alarm and had no problems locking and unlocking the screen multiple times...

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

hi @shantur what are your thoughts on the battery draining? for me the consumer is really high but maybe the problem is my battery.
In any case I attach some screen of my consumption if it can help
View attachment 2649017

View attachment 2649018

View attachment 2649019
Battery life seems pretty good, yesterday on the first charge I got 4h screen on time... the performance of this ROM is really good considering there's no overclock, that obviously helps for the battery life.
 
  • Like
Reactions: cclaxx

denis111

Senior Member
Aug 6, 2008
165
26
48
Barcelona
www.keygenmusic.net
Which line number you are talking about?
Not very important for now, i mean that one with fb1/hpd, here's pull request https://github.com/Flemmard/android_device_htc_pyramid/pull/1 . It will have no effect for now but without this line there will be more errors in logcat when enabling hdmi, so just add it for the future just in case if hdmi will ever be fixed. (Scince mako(nexus4) has it :) ).

I have fine battery life but max cpu frequency is 1188mhz.
 
  • Like
Reactions: cclaxx

shantur

Senior Member
Dec 6, 2010
1,094
3,073
0
Not very important for now, i mean that one with fb1/hpd, here's pull request https://github.com/Flemmard/android_device_htc_pyramid/pull/1 . It will have no effect for now but without this line there will be more errors in logcat when enabling hdmi, so just add it for the future just in case if hdmi will ever be fixed. (Scince mako(nexus4) has it :) ).

I have fine battery life but max cpu frequency is 1188mhz.
It is planned to be fixed :) lets see how it goes
 

cclaxx

Senior Member
Jul 5, 2012
144
48
0
milano
Just tried three times to set an alarm and had no problems locking and unlocking the screen multiple times...

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------



Battery life seems pretty good, yesterday on the first charge I got 4h screen on time... the performance of this ROM is really good considering there's no overclock, that obviously helps for the battery life.
thanks! so probably my battery is going to die... can you tell me what's your battery?
 

sjknight413

Senior Member
Dec 1, 2009
2,659
1,310
0
Brighton, England
Strange, neither me or Flemmard have this issue. Can anyone else confirm this?
Also which nightly are you using
It was fine for half a day, no issues whatsoever. But when I tried to set an alarm before I went to bed it all messed up! I'll try and reflash without a wipe and see if that does anything.

EDIT1: right I've dirty flashed the same build over the top and everything seems okay again, just rebooting to double check then I'll set an alarm and see what happens...

EDIT2: everything's okay now! i've had an alarm set for a while and have locked and unlocked multiple times, also left the phone locked for about ten minutes and it woke up again fine. i'm still hesitant though, i'm going to do a clean install of the next nightly just in case.

Also worth a mention, i said the focus on the camera was fine last night but it's now early afternoon, i have natural light pouring in to my room and it just won't focus whatsoever, even on the brightest objects that stand out clearly! also had major problems focussing out of the window into broad daylight.
 
Last edited:

shantur

Senior Member
Dec 6, 2010
1,094
3,073
0
I got some progress on HDMI. Well, i just hex-edited quickly liboverlay.so to change the line "int Overlay::sDpyFbMap[DPY_MAX] = {0, -1,-1};" to "int Overlay::sDpyFbMap[DPY_MAX] = {0, 1,-1};" to make the device be fb1 by default and not fb-1 (I don't know how to properly fix it, it should be fixable without changing overlay.cpp). And i got hdmi semi-working, it's very buggy, sometimes the phone hangs completely. When i connect it first i can see the upper part of an image and the bottom part is blue. When i reconnect the cable i can see the whole image fine but the screen flickers every second or so so it's not usable. Attaching a patched liboverlay.so in a flashable zip if someone else wants to test and 2 fotos showing what i get.

Also I'm suggesting to Flemmard to add this line into init.pyramid.rc:
chown system system /sys/devices/virtual/graphics/fb1/hpd

Without this it gives more errors in logcat :)
What did you use to hex edit, if you dont mind me asking?
 

denis111

Senior Member
Aug 6, 2008
165
26
48
Barcelona
www.keygenmusic.net
What did you use to hex edit, if you dont mind me asking?
Well, i was in windows so i couldn't compile so i just looked at the source code of liboverlay and found that the number of second fb device stays at it's default value (-1 defined in int array at the end of the file {0,-1,-1}) (from display-caf AFAIR) and searched for the sequence of bytes 00000000FFFFFFFFFFFFFFFF which is integers 0,-1,-1 and there was only one match in liboverlay.so, so i changed it to 0000000001000000FFFFFFFF. Any hex-editor will do, i used hex workshop :) Then executed 'chown system:system /sys/devices/virtual/graphics/fb1/hpd' right on the device in some terminal app :)
 

shantur

Senior Member
Dec 6, 2010
1,094
3,073
0
Well, i was in windows so i couldn't compile so i just looked at the source code of liboverlay and found that the number of second fb device stays at it's default value (-1 defined in int array at the end of the file {0,-1,-1}) (from display-caf AFAIR) and searched for the sequence of bytes 00000000FFFFFFFFFFFFFFFF which is integers 0,-1,-1 and there was only one match in liboverlay.so, so i changed it to 0000000001000000FFFFFFFF. Any hex-editor will do, i used hex workshop :) Then executed 'chown system:system /sys/devices/virtual/graphics/fb1/hpd' right on the device in some terminal app :)
Nice :)
 

oblitus

Senior Member
Oct 10, 2012
125
10
38
Bursa
Hi there.

I'm using this ROM for at least 8 hours and nothing very bad to say about it. No glitches, no FC's, no random reboots. That's the nicest KK ROM so far.

Minor things; I couldn't find the option of volume buttons to wake up the screen. Then I've installed Xposed framework and gravity to hav it option, but no good :( Also S2W is not enabled in this kernel I think. I really missed it already :crying:

Last one, If the phone restarted with the usb plugged in, PIN screen doesn't come up, usb storage screen comes. And if you back from it, you will go directly to the homescreen with no carrier signal. You have to put the phone in airplane mode or restart it again unplugged.

Other than these, thank you for this great job, man. Don't abandon us :)