yashsingh1/xdaforums huggingface dataset:
[Xperia Z Original Android Development] rlees85:
Another interesting one. Occasionally when I start my phone it hangs. It does the sony logo and the purple light thing and then just black. I have left it for 10 minutes in this state and there is no heat what so ever from the back - so I know it is not "optimising applications" - it totally hangs.

Doing the power button + vol+ trick it then reboots, but this time it does recompile all the applications again (black screen, but this time back is warm so I know its busy). Once complete everything is back to normal...

Happened twice in like 2 or 3 months, both on Saturday mornings interestingly... :)

No logs due to when it actually freezing there is no logcat and I have to force-reboot it. I will keep trying, if it happens again I will try and get logs and at least get the log of the boot afterwards. This is not a fix request, its probably a CM bug anyway. Its just a "anyone else had this?" sort of thing...
[Xperia Z Original Android Development] langeveld024:
Whew! Great! I can't miss my phone a single day, as it is currently my only device.

(Echt respect jongen! ;) )
[Xperia Z Original Android Development] andyvdsteen:
You are aware of the backlight-during-boot-issue, which is mentioned quite some times in the most recent posts?

To hard to tell if it is hanging or busy with things you don't expect it to be busy with.
[Xperia Z Original Android Development] andyvdsteen:
Who said I didn't miss it. :)

I can miss it for a short period if it is for a good goal.

(Graag gedaan, jochie! ;))

I am working on yuga and pollux since qsnc asked me to help him testing six months ago.

In the beginning he received very rare feedback, which made it less worth for him to continue this project (he considered ending yuga twice in the past six months). I don't think many people realized that this would have impacted infected's popular builds as well.

My goal was helping him to get this device in official nightlies. His project became mine as well (that is how I feel it). I now want to have this project finished; and we/he could be close! :) I am working on this together with him too long for a silent death.

There are now two bugs to solve which are blocking nightlies. The backlight-during-boot-issue and RIL-not-functioning after merging the official stuff last month.

For example: we worked on the backlight during a night, but didn't find any logic. This way of working was not efficient and very time consuming (qsnc developing, uploading, waiting for me to test, depending on how I report back, repairing stuff, uploading, waiting for my availability again, concluding that the fix wasn't sufficient, fixing something again, etc.).

Therefore I thought having a new phone would create an excellent oppertunity to speed up the proces and to realize our goal.

I won't sell the phone, so in a way there is still an advantage for me as well.

If we don't hit nightlies: at least I know we did all we could.

If we do hit nightlies: thank [MENTION=5145127]qsnc[/MENTION]. He did the work. Do respect his work. Being a "blind" developer, but still managed to create stable builds! Took him a lot of time, effort and patience to do this. I only tested his work and speeded it up by providing him a phone.
[Xperia Z Original Android Development] qsnc:
new build is up. works fine so far, except for the black screen on boot. this brings yuga up to par with the pollux builds. i am planning on activating nightlies for pollux, which will get these 2 devices off my back, and then take a closer look at yuga.

still, the more bugs you guys find, the less time i have to spend searching, so every bit helps.
[Xperia Z Original Android Development] swatchfb:
[MENTION=5145127]qsnc[/MENTION] is a dirty flash coming from previous build okay?
[Xperia Z Original Android Development] TpmKranz:
Newest build won't let me boot into recovery. I reflashed the TWRP 2.8.7.0 image via fastboot flash boot, got into the recovery, flashed your boot.img to /dev/block/platform/msm_sdcc.1/by-name/boot and the TWRP image to /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel and still can't access recovery. I tried rebooting into recovery from TWRP's reboot menu and this worked, but since CM12.1 doesn't seem to have an actual reboot menu, there is no way to access it again from my phone alone. I don't know if there are any useful logs to be taken in that stage of boot, but please tell me if there's something I can do.

EDIT: adb reboot recovery works, too.
[Xperia Z Original Android Development] Hexchain:
You'll need to enable "Advanced reboot" in Settings -> Developer Options. After that you'll be able to reboot into recovery or bootloader through Power button -> Reboot.
[Xperia Z Original Android Development] TpmKranz:
Thanks a lot, how could I have overlooked it all those times?

Problem of not being able to access recovery at boot remains, though.
[Xperia Z Original Android Development] __raptor__:
where is the download link??? :eek:
[Xperia Z Original Android Development] diemadedrei:
I know I should be posting logs, but I'm already back on the previous build since I really need the phone. I was having no call audio at all. Neither could I hear anything nor could the other person hear me. Enabling and disabling the speaker didn't help and Bluetooth headset didn't help as well. Just no sound.
[Xperia Z Original Android Development] hutilicious:
for the first time i had to setup my APN manually :D that was kind of weird, but apart from that no problems so far
[Xperia Z Original Android Development] projekt06:
It's temporarly gone.. '..will be back soon'

Maybe something is broken in the last latest release.

The new link will probably be posted in the same place as always.
[Xperia Z Original Android Development] andyvdsteen:
There seems to be an audio problem with inbound calls. That's why he removed the download link.

Good that he now has a device to play with. :)
[Xperia Z Original Android Development] peterlolty:
HI, im new in this post.

There are 4 "bugs", at least i believe this is not work as design.

1. Dialer and Contacts App ALWAYS request locations,

a workaround is that just use the privacy guard to denied the location access right.

( actually the Google play service and Google Fit also request location like this,

but i didn't expect the Dialer and Contacts App also need my location)

2. After i used the camera app (or any app that will use the camera, the back light ,etc) ,

then if I switch the phone to "Power Save" mode(the options in battery menu),

the phone will hang(no response) and i need to press the "power button & vol +" to force power it off.

3. The "Power save" mode is a bit slow then expected, it is too lag for normal use.

Is it possible to let user setting the CPU clock manually, rather than those 3 options in the battery menu?

4. VOICE_CALL system audio source cant be accessible. e.g.

The ACR Call recording app ( http://play.google.com/store/apps/details?id=com.nll.acr ) cant record the call at the default (VOICE_CALL) channel.

I can help to provide logcat if you want. Cheers.
[Xperia Z Original Android Development] andyvdsteen:
Logs are always needed to trace and solve bugs.

Since the download link of the latest build is unavailable for quite some time, it is unclear which build you are using.

Option one sounds like Google-design. These apps are not build by the CM ROM-developer.

Could option 3 be by design? It is power save-mode, so maybe CPU is also not operating in its highest performance.
[Xperia Z Original Android Development] TrueFriend-cz:
How long going download temporarily disabled? Real soon 3 days :)
[Xperia Z Original Android Development] leroy1703:
Just wait until the bugs are fixed
[Xperia Z Original Android Development] diemadedrei:
Power save mode has always been crappy on this build. I havent tested it on any other phone so far, though, so I cant say if its bad by design or just with this device and build. It throttles way beyond usability and often fails to go back to normal when you plug it in. May be its really just intended to have the phone not powering down and being able to receive important calls but not using it in any other way. If youre fast enough after enabling power save mode before it totally breaks down you can manually set the CPU governor and speed a little bit up.
[Xperia Z Original Android Development] peterlolty:
Would like to know, where can i set the CPU governor? as I cant found it in Performance Menu, even I turned on debug, adb, etc...
[Xperia Z Original Android Development] diemadedrei:
You can set it with lots of apps, I'm using setcpu for example, but just search for clocking or cpu or something similar in the play store
[Xperia Z Original Android Development] peterlolty:
My build is 0522 version, i mean the power saved mode is some how over-tuned, it tune down the CPU clock too much, so it appears very lag response and not able to be normal usage.

And really thanks for u guys, qsnc and andyvdsteen, and who help this rom...
[Xperia Z Original Android Development] andyvdsteen:
Please check the most recent build as soon as it comes available again, and check if the bugs are still there.

The 0522 isn't the best version to report bugs for, since the recent build has newest CM-patches and official Lollipop sources.

I only help with this ROM, qsnc does more then that. :)
[Xperia Z Original Android Development] LordAbhilash:
I have tried 0107 build for 4 days... Its quiet stable... but can tend to over heat if the phone is in 3G only mode with GPS on... Not sure if the problem is with the ROM or something else. Will get back to you if I get to know.
[Xperia Z Original Android Development] Yndi:
Has anyone an ETA for the next version?

I hate asking this myself, but I have to do a clean install and I wonder if I should wait, since the download link states 'really soon' some time already.

Today I set a pattern unlock which I don't normally use and now I can't unset it :(. It says it's forced by admin, account or sth. else. Great I hate unlocking the phone each time...

[MENTION=4363089]LordAbhilash[/MENTION]: I'm still on build 2205 and I have the same problem. I'm not completly sure if this came with the radio upgrade from lollipop!? Did you upgrade it(has to be done manually)? I can barely use GPS at all. It takes ages to get a fix and then the phone gets hot, really hot. Reminds me of the XZ 4 news shortly ago here on xda which could reach about 70°C on the outside. 70 I sure did not have today but I could not touch it at the upper (right) part. Navigation, at least with Gmaps does not work for me anymore. The phone gets too hot before navigation starts already, I certainly was below one frame/s. I wondered all the time why it did not shut down. When I rebooted it took maybe two minutes until the phone went off.

[MENTION=5145127]qsnc[/MENTION]: is there no shutdown value for the phone with the new themal management introduced some builds before?
[Xperia Z Original Android Development] buche23:
I have the very same thing. Due to the fact I have set up my companies exchange account on the phone. They tend to push security policies to the end users device (the downside of BYOD).

Anything like that on you phone maybe?

Cheers,

Buche
[Xperia Z Original Android Development] Yndi:
No, I only have two accounts(Google and MS as exchange) in settings which both should not enforce a security policy. If they would do so it would pop up on setup as a compies exchange account usually does.

Thanks for your ideas.
[Xperia Z Original Android Development] peterlolty:
I suggest you guys to check the private guards to see which APPS consumed your GPS and CPU, not just telling about the GPS leads to hot.
[Xperia Z Original Android Development] TheAvngrZ:
No, its not app depending the heath, its a problem with the new thermal menagement
[Xperia Z Original Android Development] andyvdsteen:
I believe a new build might take some time.

Other fusion-models also have inbound audio issues. Even on stock ROM. So the issue is larger and seems more complex.

Fusion devs are working on it.
[Xperia Z Original Android Development] TrueFriend-cz:
If i install Voxox then show message Error 505. Dev can you fix it? Thanks
[Xperia Z Original Android Development] qsnc:
new release up with fixed incall audio... all major things should work now, go ahead and give it a try

just to prove you wrong [MENTION=4814657]andyvdsteen[/MENTION] ;)
[MENTION=3022804]swatchfb[/MENTION]: if a wipe were (to my knowledge) required, i'd have noted it
[Xperia Z Original Android Development] swatchfb:
Thank you very much! [MENTION=5145127]qsnc[/MENTION] May I ask you again if full wipe is recommended or dirty flash coming from May 22 is okay?
[Xperia Z Original Android Development] macia10:
Link does not work :(
[Xperia Z Original Android Development] sigma9988:
DL link is wrong?!

Not Found

DL link is working now

Thanks :D
[Xperia Z Original Android Development] LP6:
It says in the OP that you should do a clean install unless you already have CM12.1, so dirty flash should be fine.

I just flashed over 20150522 and am waiting for the device to boot up, which also means that the DL link worked fine for me a while ago.
[Xperia Z Original Android Development] andyvdsteen:
Not fair: Some developer told me this, and I don't have a device to prove I am right. ;)

Good that it might be solved! Is it a workaround or a solution?

Is the backlight at boot also fixed? OP says it isn't.

Downloadlink doesn't seem to work. Downloadlink fixed
[Xperia Z Original Android Development] Yndi:
Hehe.

Lucky me that I was not able to do a clean install of the old build. Because I deleted the zip already[...] :D

Thanks

Edit: DL not working here too
[Xperia Z Original Android Development] diemadedrei:
Download worked for me, install went fine, incall audio is working, backlight while booting not. But since dirty flash I already had two random reboots. The first one was just after the first boot before I could enter the pin, the second one was while browsing. Both times it was a soft reboot. And at least the second time the phone was unresponsive for about a second after which it responded for a tenth second before it rebooted.

Here's a log https://www.dropbox.com/s/dki0fht0ayy0qjn/last_kmsg?dl=0
[Xperia Z Original Android Development] Yndi:
DL works now for me
[Xperia Z Original Android Development] peterlolty:
Did you wipe cache and rebuild the app cache?

I wanna know if it is the same stable as the 0522 version before flash it, as i will go a trip few days so I need a stable one.
[Xperia Z Original Android Development] diemadedrei:
I'm not sure what you mean by rebuild app cache, but I wiped cache and it did the infamous optimization at the first boot.
[Xperia Z Original Android Development] peterlolty:
That's what i mean, thank you so much!

Except the 2 soft reboots you mentioned, did it have reboots after that?
[Xperia Z Original Android Development] diemadedrei:
I've had another two reboots happen by now. One was while the screen was off, the fourth one while watching a video. I had two of these in the short time I had the 0701 build installed as well if that matters. May be someone who did a clean install (for which I lack the time right now) can tell if he also gets reboots?

PS: the video kept playing until the screen turned off but the phone was unresponsive as I tried to click the video to get controls for about a second
[Xperia Z Original Android Development] __raptor__:
I deserve reboots when seeking gps-position in WhatsApp and Google Maps.

ADB Logcat while google Maps is attached. I hope it will help
[Xperia Z Original Android Development] Yndi:
Hi,

here are some reports and thoughts:

Did a clean install.

....camera.zip: soft reboot after I openen camera for the first time. Did not happen again.

...no-response: phone totally stuck while I was typing, I think. Could be an app thing.

...clock_crash: clock crashed when choosing a new alarm tone for the first time. not reproducable for the clock but the same thing happened to the settings app when choosing a ringtone for the the first time.

As someone else posted before I think for the withdrawn build the energy-saving mode does not work as intended. Performance is too low to use, I was lucky enough to reset it to normal. But governor did not switch back (well, for the normal user it's ondemand in both cases but if you switch it entering energy.saving mode it should be reseted when going back to normal). When entering energy-saving mode live-display settings are ignored.

Be careful if your phone is on low battery because with standard settings it will enter energy-saving mode automatically.

The point of critisim on the live display: It does not change the color-temperature dynamically. It just switches between the two values.

Why is the LED not configurable for us? I mean the blinking one if new messages arrive. The setting is there but blocked.

The 'Performance' subsettings are gone for good now I guess or is it still there and unlockable like the developer settings?

About the heat: Nothing changed here so far but I got more than three and a half hours SOT time yesterday which is very good for me. Let's see how this goes on normal days where I don't have to cofigure the device.

Is there any possibility tha a voltage interface will be included or is this unwanted by CM?

To the ones which are more into this matter: The CM common problems(not specific to our phone like the live display I guess) should better be reported to CM Jira, right?

Best

Yndi

P.S.: Seems like CM is getting VoLTE ready. I'm just switching to 4G. Let's hope the provider unlocks this phone for VoLTE too,
[Xperia Z Original Android Development] qsnc:
a new build is up, fixing 2 non-critical but still annoying bugs.

exactly, stuff common to CM (do not forget that we are still speaking about NIGHTLIES here) has no place in this thread and should be reported elsewhere. this goes for performance settings (theyve been removed) and feature wishes (i could bet you will never see voltage control). also these things are out of scope here. i will NEVER ever support custom kernels, FOTA recoveries and whatnot. if anyone wants to play with this stuff, fine, but please: report bugs ONLY (!) when you run unaltered builds with the CM recovery and the kernel included in my builds.

i tried to reproduce the problems you describe, but i can not. all apps are rock solid, ive been running essentially this level of code for a week without a single problem. choosing an alarm tone however is not device specific, so i am quite sure it has nothing to do with the yuga port.

the led thing might just be a tiny configuration problem, ill have a look at it.

as for performance tuning, yes, that is still not finished. the default (non-energy saving) ones are working a lot better than ever before, at least on all devices i could test.... energy saving mode is quite low on my todo list - so many bigger issues to work out.
[Xperia Z Original Android Development] diemadedrei:
Thanks for your huge effort! I thought the notification led control was gone in cm 12.1 but I don't have another device to check. Would be great if that returned. I didn't have any reboots today so may be the rom had to settle first and becomes more solid.
[Xperia Z Original Android Development] andyvdsteen:
http://review.cyanogenmod.org/#/c/102755/

:)
[Xperia Z Original Android Development] LordAbhilash:
I can now tell that 0807 ROM can be used for daily usage without any major problems. It is smooth and stable enough. Thanks to qsnc.... YOU ROCK
[Xperia Z Original Android Development] swatchfb:
[MENTION=5145127]qsnc[/MENTION] I can confirm the reboot after using GPS on last build. Therefore I just tried "SatStat" and the device reboots.

I attached all files SysLog gave me, but there's no last_kmsg.txt. I don't know why.

Apart from that, this is the smoothest ROM since release.
[Xperia Z Original Android Development] qsnc:
i have a yuga in front of me, and i am using GPS in 3 different apps simultaneously. i can not reproduce this problem.

if you send me logs after the reboot, they will contain nothing at all but a normal boot. try using "adb logcat > log.txt" to get logs continuously and reproduce your reboot then.
[Xperia Z Original Android Development] peterlolty:
I also flash the 0708 version, and use the GPS (Google Maps and Life360), no reboots, errors or bugs found.

Thanks for [MENTION=5145127]qsnc[/MENTION], we now have a GREAT ROM for daily use. Also thanks any testers or helpers to help building this ROM.
[Xperia Z Original Android Development] swatchfb:
So maybe the problem was app-specific. I now noticed that I don't have the problem using Osmand~
[Xperia Z Original Android Development] andyvdsteen:
I believe it is merged.... :)

Backlight during boot.
[Xperia Z Original Android Development] qsnc:
new build up again. fixed some more annoyances thanks to having direct access to a yuga.
[Xperia Z Original Android Development] TpmKranz:
Thanks a lot, booting into recovery now works as expected and the screen is always lit during boot.

My MAC address is still not back to normal, though (it's supposed to begin with 18:00:2D):

EDIT: Is there a way to provide logs for this?
[Xperia Z Original Android Development] peterlolty:
Don't know what actually changed in 0709 build...

I just notified my Wifi Mac address has changed to 00:0a:f5:32:d6:84. And the wifi is worse then ever built before

Is that really a need to make all the MAC address of this device to be duplicated?

Because I have a licensed app keep track of my wifi Mac address

And I have lots of random reboot after flash to this build (i have clean the cache and optimize all app again)

logcat provide soon...
[Xperia Z Original Android Development] andyvdsteen:
[MENTION=5145127]qsnc[/MENTION] I don't have the device myself to check:), but it looks like the MAC-fix is not implemented again?

Two people reporting the same MAC. I believe I had the same MAC months ago on pollux and yuga (and they constantly kicked each other of the network).

See this post from the Pollux-thread.

If it is the same issue as in January, then it also includes a manual fix for those who need it.

---------- Post added at 17:18 ---------- Previous post was at 17:15 ----------

It is not of much use to report bugs if logs are not provided.

Very often (not only in this yuga-thread, also in many other threads) I see people suggesting that they will provide logs later, but eventually they never do.

Maybe because they do want to mention that something is not stable, they know they need to provide logs, but they don't know how.

If you don't know how, use an app like SysLog. It grabs all the logs. I also used this app to provide logs to qsnc.

If you do know, then please don't mention bugs without logs. If you really want to provide logs later, then maybe it is better to mention the bug later as well.

[MENTION=5272517]peterlolty[/MENTION] Don't feel personally offended. Maybe you would provide logs later. It is just that I see this very often, and your post triggered me to mention this.
[Xperia Z Original Android Development] qsnc:
its not the same issue as before, it was actually a copy&paste error i made. its already fixed. new build coming, might take a while tho... im off to get a beer ;)
[Xperia Z Original Android Development] LordAbhilash:
Bro Check me in.. Ill have beer here in your name. But alot of improvements though... Major break through in XZ I guess:laugh::laugh:
[Xperia Z Original Android Development] peterlolty:
You are right. Many people enjoy the gift but dont wanna pay some time to get a better one, and some guys like me seldom to catch the logcat, so it takes time for me to Google "how to logcat".

Btw, there is a logcat reproduce the reboot, i confirmed it always reboot even i don't touch it. The previous post is just to remind people who use it for daily to pay attention of these reboots problems.

[MENTION=5145127]qsnc[/MENTION] 2nd logcat provided, please check...
[Xperia Z Original Android Development] peterlolty:
For the 0709, I also wipe the cache and optimize apps again, still have reboots, so i flash back to 0708.

And the 0708 works perfect again now, will use it for daily purpose. Hope there will be fixes on the 0709 version.