yashsingh1/xdaforums huggingface dataset:
[Xperia Z Original Android Development] TheAvngrZ:
My phone was off during the night and after I pressed the power button and docked it into my docking station, the CM logo was normal with backlight on. Probably this helps something.
[Xperia Z Original Android Development] andyvdsteen:
We didn't really understand why backlight is off at all. (Well, especially qsnc, since I am not technical skilled on Android.)

We didn't find something logic in its behaviour.

Did a lot of testing with him recently; loads of boot.img's, complete builds, pushing files...

After that I restored a backup I made before all those testing. I also noticed a correct backlight one time. But it was gone again after a second reboot. Someone else mentioned it here earlier.

Now I also have several bugs I didn't have before. Overheated phone and high battery drain when screen is on. Looks like mpdecision is using a lot of CPU when screen is on, but all is cooling down rapidly when screen is off.

Also my Android Wear is no longer receiving any messages from the phone, even though the watch is connected (I am able to push watchfaces to it). As soon as I install qsnc's latest build (with Sony Lollipop blobs) the messages are received again. So it must be something in this 22nd build, but didn't have these bugs before the restore.

Sometimes Google Play Services is crashing.

Also have the idea that the backlight during normal usage isn't always giving the same brightness.

Bit confused about why this restore didn't give me back the stable situation that I had before making the nandroid backup.

Got another question to anybody...

His latest build doesn't have RIL (same for pollux, btw). He didn't have enought time left to fix it and suggested to update the baseband during his absence.

I couldn't really find reliable and clear instructions on how to do this.

Where can I find a recent baseband of yuga?

How can I flash a baseband?

How easy can I revert if it causes more issues? (How can I extract the present baseband?)
[Xperia Z Original Android Development] TheAvngrZ:
Yea, I can confirm too, that my yuga gets sometimes really warm (not warmer, than before the changes with the heatsystem - so really cool) and I have some problems after a reboot with a phone, which doesnt move as it should.

But 22nd build is good usable, when the mankos are known.

Hmmm, Baseband is a bit difficult

At my old LG L7 (p700) baseband was a flashable .zip file, which you flashed through recovery and then you had a new, if you wanted to change it, you just flashed a new .zip and a ROM-Update didnt changed something with baseband.

But yes, this is yuga and it could be very very different. So I think we need someone who really knows whats up :silly: :highfive:

Waiting for a new build exept I will be wait long haha :fingers-crossed:

Greetings into the Netherlands from Germany! I hope the weather gets warmer in the next days! :D
[Xperia Z Original Android Development] andyvdsteen:
If the weather won't, than at least my phone will! :)
[Xperia Z Original Android Development] Hexchain:
<del>Maybe get a complete official 10.6.A.0.454 image using flashtool and flash baseband partition only? And also get a 10.xxx.292 (current, didn't remember, sorry :P ) in case something fails.</del>

EDIT: My phone just came back from stock sony 10.6.A.0.454 (which is 5.0.2) and the baseband is still 9x15A-ACEFWMAZQ-30110089-64. Not sure if the above method really works...
[Xperia Z Original Android Development] andyvdsteen:
That is the same baseband I have.

Maybe [MENTION=585581]A-S[/MENTION] could check the baseband off his Sony Lollipop ROM?
[Xperia Z Original Android Development] TheAvngrZ:
9x15A-ACEFWMAZQ-30110089-64 is the number of mine too.

I never was on a stock Android-L, flashed Custom ROM while 4.4 was up-to-date.
[Xperia Z Original Android Development] rlees85:
Some CyanogenMod ROMs used too report the baseband version as a static value and not the actual baseband that is installed. Just wanted to make that warning first..!! Not sure if or not this applies to this ROM.

To flash the baseband:

- Backup First !! PS I take no responsibility if you lose everything as when I do a major flash like this I end up wiping/rebuilding from scratch anyway.

- Download FlashTool - http://flashtool.net

- Download Latest FTF for your phone (General section of forums is a good place to look)

- Use FlashTool to flash this FTF. You will lose everything.

- Boot the phone, confirm the baseband version in this ROM is the lollipop version (whatever that is, cannot find on Google). This will also update any firmwares that are out of date such as NFC.

- Wait a few mins, power off device, power back up and boot fully once more for good measure.

- Power off device.

- Flash boot.img from this ROM using FlashTool

- Format system/data/cache

- Install this ROM and restore your backup.

Just selecting "baseband" when doing the FlashTool bit may update the baseband without you having to lose everything. But as some custom ROMs do not report true baseband version as mentioned above its difficult to tell if it has been successful or not.
[Xperia Z Original Android Development] Olivier:
The baseband on Stock 5.0.2 is 9x15A-ACEFWMAZQ-30110212-82.
[Xperia Z Original Android Development] rlees85:
Been having this problem for a while on CM11/KitKat too. I've tried reflashing from scratch and its not fixed it. Maps also FC's a lot. I've put this down to GAPPS being horse poo. May or may not be the same problem your having...
[Xperia Z Original Android Development] Yndi:
Thanks for this important information. It is most probably the case with this ROM and [MENTION=5145127]qsnc[/MENTION] if this could be fixed it would be great.

I did the short version, only flashed baseband (be carefull you don't select what to flash but what to exclude from flash). After the first boot it took like 20s until network came up, I already thought I broke the radio and have to go back. Second boot was fine/normal.

In about phone the old version ...-64 is shown and when I read rlees85 post sth. else came in my mind: Maybe some bugs which only some users got are radio related, like the reboot bug I had for quite a time or even the call/loudspeker bug.

When I first flashed CM12 I wondered a bit about the radio because I did not know CM changes the version and I came from original KK .292 which had a newer verion than the one we CM always(since CM12 at least) had in about phone. ...-72 I think(the last two digits were higher).
[Xperia Z Original Android Development] shoey63:
Cm baseband will always show the same value, no matter what you flash using flashtool. It's hard-coded into the rom.

It doesn't actually reflect what your "real" baseband is.
[Xperia Z Original Android Development] TheAvngrZ:
The settings crashed after click onto the menu mobile networks (Mobilfunknetze in german), I clicked there, cause the device ran on H+, but I set it on 2G only...

log is attached.

EDIT:

Sometimes the heat is very high, after taking some pictures. The heat problem is sometimes a really problem, if you have a that warm device in your hand it dont feels nice.

EDIT 2:

When camera gets used, the phone gets very warm... This is really a problem, especially, wehn apps like snapchat are used.
[Xperia Z Original Android Development] rlees85:
Been running the last build now for a week.. here are my findings:

Using: cm-12.1-20150522-UNOFFICIAL-yuga.zip

Baseband: Latest, from Sony Lollipop firmware

So far, it is more reliable than CM11. The only bug I can really see is the boot screen. It goes black for a while, then the boot screen appears for a while, then phone is booted. This really should not be a show stopper for nightlies, especially when it is running much better than CM11! The gapps no longer force close all the time!! :D

No issues making lots of calls. There is a bug where the other person cannot hear me sometimes and my signal goes to 0. At this point I have to hang up and normally it drops from 3G to 2G. I will get a log of this when it happens again. It also happened (probably more regularly) on CM11. So it could well be my hardware.

Random reboots/freezes: none.

Heat: Yes phone can get warm when being used. Maybe ~2-3c hotter compared to CM11 (I am going by an app I made that puts the battery temperature as a notification). Again not a big deal for me as I don't use games. Seems like the sort of thing that will sort itself out with newer blobs/etc. If it bothered me I would be looking at the logs for mpdecision, hot plugging cores, thermald if it is used, etc but it doesn't...

Anyway just wanted to feedback. Cheers qsnc for your work. Look forward to this being an official nightly :) My Xperia Z has just turned 2 and I don't see why I can't get another year out of it at least.
[Xperia Z Original Android Development] andyvdsteen:
My opinion is that the black bootscreen (bootscreen is working, it is only the backlight) could be a blocker for nightlies. Maybe not for us, but those not in this thread might think that the ROM isn’t working ‘cause the screen stays black.

Also phone getting warm might be a blocker. Maybe not an issue for you because you are not a heavy user, but for others it could be.

I didn’t have any issues with temperature until I did some intensive tests with qsnc. After restoring to the previous situation, I had some annoying bugs I didn’t have before. Some of them also mentioned by others. Phone getting very warm when charging or screen on is one of them.

The “callbug” is interesting. Didn’t have it for quite a while. But I also mentioned earlier that this might not be a CM12-bug (more or less confirmed by you), and maybe not even a yuga-bug. I posted links earlier to topics from other devices. It might be an Android-bug. But not everyone agrees. Doesn't need to be a hardware issue with your device.

Anyway, I have a new phone now. Don’t know how to tell qsnc when he comes back. :)

No worries, I still own the Z (no plans to sell it). So I will still be able to support. Using another daily driver might also create new options in speeding the problem solving process, but I want to discuss that with him first. ;)
[Xperia Z Original Android Development] Yndi:
OK, wanted to report back before [MENTION=5145127]qsnc[/MENTION] is back. I hope I'm still in time.

First of all about the two logs I attached:

-#date-Bl-charge.zip: When I have the screen on and plug the phone to the charger, screen won't go off automatically. Log is taken after about three minutes screen on, it sould go off after one minute. No option for this is set in developer options. If I turn off the screen manually and later, while the same charging process use the phone again, behavior is as it should be. It's only when I plug it to charger with screen on. Reproducible.

-#date-Backlight.zip: Phones battery was totally empty and it went off without a normal shutdown. I plugged it to the charger and after some time the basic boot process started (I think the kernel, right?). I hit the power button as soon as it let me to boot completely. During the hole process backlight was on. Log was taken asap after boot. Maybe this helps fixing.

Some more words: After using the latest baseband for some time now I would recommend it to everyone with WiFi troubles(most of us I guess). WiFi got noticably better here, espacially when signal is low the connection stays alive. The most tested AP, at home, is a Fritz!box 7490 if anyone cares.

Performance-wise this ROM is great. As stated earlier I switched to interactive & deadline and I could not wish for more from a phone. But one more word here: shouldn't there be a governor selector in the performance options @qnsc?

Battery & heat: These are my two problems which are come to stay as it looks. On a normal day which I calculate with 18h before I can use the charger again I get 2,5h screen on time tops. I still hope there are some possibilities for improvement. As mentioned by others and myself already the phone tends to get hot every so often. So, not always but more often then not. While charging and while screen on (browsing or using other non-torturing) apps.

Since I installed the latest version I can remember two time when it got so hot, that I had to pull it out of my pocket again because it was pretty unpleasant. Again: is there any good way to log this?

That said, thanks for the effort qsnc!
[Xperia Z Original Android Development] rlees85:
CM11 did this too... If that helps finding out the problem (this one doesn't bother me though)

I know the bit I highlighted isn't your point, and your helping with the backlight on boot bug. But I think this is a good point, I am not 100% sure but I suspect CM11 did this too, but it would be nice if this one was fixable. Especially for people with EXT4 without journalling/etc.

Good point... especially on first boot! :good:
[Xperia Z Original Android Development] TheAvngrZ:
Maaaan whats up here?! :D

Hoping for a nice update soon :D
[Xperia Z Original Android Development] andyvdsteen:
You'll have to wait one more week. At least.
[Xperia Z Original Android Development] TheAvngrZ:
:good: :p :victory:
[Xperia Z Original Android Development] AndyYan:
Hi all :) I'm getting my own Z in a few days and would like to build (not develop - I'm a noob in that) CM12.1 for it on my own laptop in case the devs are busy with something else.

From what I've read for the past few pages, we have the boot time backlight bug, and as of now something's wrong with RIL. What's more, [MENTION=5145127]qsnc[/MENTION] is still on holiday. If I get it right, even if I figure out how to complete a build at this time, it won't be usable.

Nevertheless, I'd still like to ask how - I have official CM repo ready and had already built for other devices successfully. Problem is, since Z isn't in official CM12.x yet, "breakfast yuga" says that I lack the .mk file for it. Tried adding the custom kernel source (e.g. the one in Infected's thread) into roomservice.xml, didn't help. What files should I touch, then?

Thanks for any response!

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Xperia Z Original Android Development] Hexchain:
It's almost 4 weeks now... :P

My phone didn't even rebooted in this period, and is getting 430+ hrs uptime now.
[Xperia Z Original Android Development] andyvdsteen:
Maybe feels like almost four, but has just been three weeks. :)

(Yes, he's back)
[Xperia Z Original Android Development] AndyYan:
Which leaves me wondering why there hasn't been any response to my post for a whole week.

Oh well, now that he's back, I guess things should get a bit warmer.

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Xperia Z Original Android Development] macia10:
Hm, I've just noticed that when turning phone one while connected to charger makes backlight work through all of boot process.
[Xperia Z Original Android Development] qsnc:
these 2 should fix the denials you see:

http://review.cyanogenmod.org/87919

http://review.cyanogenmod.org/87920

not really yuga related, but anyways ;) also, it shall be interesting to see if your script will be allowed to set properties at will (which i doubt), so youll probably be back at square 1 in regards to your problem...

the most extreme measure would be to set selinux into permissive mode... but that won't really solve anything for you.
[Xperia Z Original Android Development] hutilicious:
Hi [MENTION=5145127]qsnc[/MENTION]

is there any information about when full external binaries like ssh, hypershell etc. will come back?

Using cm11 I was able to connect to raspi with ssh and batch restore apps using Titanium Backup.
[Xperia Z Original Android Development] iKillCypher:
[MENTION=5145127]qsnc[/MENTION]

please refer to this

http://xdaforums.com/xperia-z/development/rom-cyanogenmod-12-unofficial-t2975458/page96
[Xperia Z Original Android Development] qsnc:
nope, no idea... im just a lowly device maintainer... try to join irc and ask one of the higher ups ;)

your attitude in this thread you linked is just embarrassing. please work on your attitude, and get informed before you accuse me and/or bug devs. these warnings have been there for a long time, and they are not the cause (not kernel panic, not kernel oops, a warning! check the code). i will say no more in this matter, not on this level.
[Xperia Z Original Android Development] Hexchain:
JuiceSSH is a good SSH/Mosh client.

And I have no problem with TitaniumBackup, have you enabled Root access in Developer Options?
[Xperia Z Original Android Development] hutilicious:
Yep of couse I have. I can backup apps but I cant restore. I have to set restore mode to interactive
[Xperia Z Original Android Development] Panaroma:
Sorry for the thump up ^^ wrong klick....

Just wanna say that for me its working great :)
[Xperia Z Original Android Development] andyvdsteen:
I have "No service" notification on the lockscreen, even though I do have service.

I noticed the same reported in _infecteds-thread.

No other bugs so far. Also no random reboots, but didn't have them the last few days on the previous ROM.
[Xperia Z Original Android Development] andyvdsteen:
I just had an unplanned reboot. WiFi was on, and I was out of range of my network.
[Xperia Z Original Android Development] AGGevorgyan:
The same issue here, but after receiving call operator info appeared.
[Xperia Z Original Android Development] qsnc:
uh, sounds like ril trouble... can you gather logs (last_kmsg in particular), and post them somewhere?

ril trouble again i suspect... it'll be difficult for me to debug these things, since i don't have a yuga... please try to gather logs (logcat, radio log)... maybe we can find the culprit...

hexchain, did you try the second patchset for the selinux rules i posted? i'd be interested to get feedback on your userinit trouble...
[Xperia Z Original Android Development] andyvdsteen:
Hope these are usefull!
[Xperia Z Original Android Development] emeemisri:
Profile setting FC after i tried too add profile or change profile
[Xperia Z Original Android Development] Hexchain:
nope, the userinit scripts still don't have a chance to execute.

dmesg:

<5>[ 18.425598] type=1400 audit(1423406092.271:4): avc: denied { getattr } for pid=214 comm="run-parts" path="/system/etc/init.d/90userinit" dev="mmcblk0p24" ino=472 scontext=u:r:sysinit:s0 tcontext=u:object_r:userinit_exec:s0 tclass=file op_res=-13 ppid=209 pcomm="logwrapper" tgid=209 tgcomm="logwrapper"
<3>[ 18.529724] init: Warning! Service setup_fs needs a SELinux domain defined; please fix!

audit.log:

type=1400 msg=audit(1423406092.271:4): avc: denied { getattr } for pid=214 comm="run-parts" path="/system/etc/init.d/90userinit" dev="mmcblk0p24" ino=472 scontext=u:r:sysinit:s0 tcontext=u:object_r:userinit_exec:s0 tclass=file op_res=-13 ppid=209 pcomm="logwrapper" tgid=209 tgcomm="logwrapper"

Thanks.
[Xperia Z Original Android Development] andyvdsteen:
Sometimes I don't hear the caller. The caller is able to hear me. A workaround is to put the phone on speaker during the call (which isn't always a bood workaround).

The problem resolves itself after some time.

I don't experience this very often. Probably because I am not on the phone that much.
[Xperia Z Original Android Development] AGGevorgyan:
My issue is vise versa. I can hear caller, but he can't hear me. This issue is case most of time. But sometimes everything is ok.
[Xperia Z Original Android Development] qsnc:
yes indeed, very useful. the crash definitely happens in the wifi driver. stay tuned, i'll contact you about a test version privately...

there still seems to be a call to logwrapper dangling around somewhere... did you use both commits i posted on gerrit? and if yes, please try to find the remaining logwrapper call, it needs to go away ;)
[Xperia Z Original Android Development] deepongi:
sorry for hi-jacking your thread also .. :D but why are you going to make a private build for a single user, when the wifi driver seems its a general issue, and all users should try it to help debug? :)

just my opinion.

regards.
[Xperia Z Original Android Development] Hexchain:
Yes, I'm currently using gerrit 86942 (yuga-calling), 86943 (yuga-calling), 87919 and 87920.

Here you are: vendor/cm/prebuilt/common/bin/sysinit another logwrapper call.

Just curious: What's wrong with logwrapper?
[Xperia Z Original Android Development] qsnc:
you are most welcome to "hijack" this thread ;) the answer is rather simple: i dont have a yuga at my disposal, so i can't test - and debugging something requires a) an experienced user with b) fast feedback and c) some knowledge about what's going on... i might have borked wlan completely in an attempt to fix it, so i'd rather have it tested privately before a bigger group of users starts complaining :)

please fetch 87919 again. nothing is wrong with logwrapper per se, but the trouble is that if you run something with logwrapper, itll run in the context of logwrapper... and since google doesnt seem to want to do domain transitions for logwrapper, its better to remove it (so that the processes run in their own context).
[Xperia Z Original Android Development] andyvdsteen:
Try it again.

It didn't make any difference for me. I think I had backlight during reboot one time (don't remember if it was charging), but it was off again after another reboot.
[Xperia Z Original Android Development] andyvdsteen:
I have send my yuga device to Austria for a while. Making qsnc less depending on me (he doesn't own this device himself), thus making the developing more efficient. Hoping this will speed up the problemsolving process. We cannot guarantee that this will result in official nightlies, but I do hope this will help.

Give the device some time to arrive, and give qsnc some developing time. So a little more patience please, but do know that CM on yuga is not dead yet. :)

Pollux uses the same modem as yuga. Yuga had no RIL in his latest builds, so succes for yuga might also be a succes for pollux.

So also for pollux-users (as myself): a bit more patience please. :)
[Xperia Z Original Android Development] LordAbhilash:
Thanks Andy for your kindness in keeping our device still in CM picture... And I am most thankful to our qsnc for taking such an effort keeping our device alive though he doesn't have one... Thank you guys... Waiting for the next builds.. Hopefully it ll be a nightly.....:D:D:D
[Xperia Z Original Android Development] TheAvngrZ:
:good: Great news! What a great support! :good:
[Xperia Z Original Android Development] andyvdsteen:
I have been working on this device for quite some time now, together with qsnc after he asked me to help him with testing.

Sometimes even until late in the night.

So it would feel a bit like an unfinished project if I would stop it now that I have another device. I felt having another device was creating this opportunity.

Having another device has nothing to do with CM status by the way. Still a verynice device (with CM12.1 unofficial), but is because of possibilities at work.

Still want to keep the device, just not as a daily driver.
[Xperia Z Original Android Development] macia10:
Checked it few times already and works the same way everytime. Turn your phone off connect to charger and power it back on. Backlight through whole boot process :)
[Xperia Z Original Android Development] thorte:
Confirmed. Same behaviour on my device.
[Xperia Z Original Android Development] DroidFan:
I can also confirm this behavior. Have noticed several times when battery had run down completely. I plugged into charger and turned on, and backlight is on through the whole boot process.