[ROM][UB][OFFICIAL][Lollipop 5.1][AMAMI] PAC-ROM LP-MR1

[AllAboutTech]

hi,

Lollipop 5.0 source released by Sony. It is any help?
http://developer.sonymobile.com/201...-aosp-source-code-and-binaries-now-available/

thanks.

 

[drbiggy]

is it recommended to use the ota feature of this rom?
ord would that download a pac version that is not optimized for z1 compact?

 

[Deleted member 4819888]

hi,

Lollipop 5.0 source released by Sony. It is any help?
http://developer.sonymobile.com/201...-aosp-source-code-and-binaries-now-available/

thanks.

Already knew that, but thanks for making the effort

is it recommended to use the ota feature of this rom?
ord would that download a pac version that is not optimized for z1 compact?

If you're using my optimised build then I'd recommend that you don't use ota, but if you use official nightlies then go right ahead

 

[AllAboutTech]

hi,

maybe it helps. for GNEX it seems it's working also RIL and data: "I tried disabling SELinux and recompiling as suggested by @aosp. Data on 3G now works, so I can confirm the problem is related with SELinux."

thank you.

 

[Deleted member 4819888]

hi,

maybe it helps. for GNEX it seems it's working also RIL and data: "I tried disabling SELinux and recompiling as suggested by @aosp. Data on 3G now works, so I can confirm the problem is related with SELinux."

thank you.

Thanks for the info! @GethPrime is currently handling 5.0, so for further findings, please report them directly in his thread

 

[drbiggy]

If you're using my optimised build then I'd recommend that you don't use ota, but if you use official nightlies then go right ahead

Could you specifie some optimisations that i would miss? I aprreciate the effort

 

[Deleted member 4819888]

Could you specifie some optimisations that i would miss? I aprreciate the effort

sure, here are the things you'd lose:
1. GreatDevs kernel (you can restore it by flashing it later if you want)
2. Optimized toolchain for ROM (Sabermod). This gives arguably better performance.
3. TWRP recovery. That can also be flashed seperately
4. High touch sensitivity toggle in Settings->Languages & Input->High touch sensitivity

Other than that, OTAs and my customized builds are the same

 

[notwigga]

I am experiencing a bug in FauxSound. When i listen to music with spotify, and i pause the music and minimize spotify, then the FauxSound settings are reverted back to standard when i start the music again. I dont remember having this bug before, so i guess it has something to do with the new kernel

 

[BokeB]

I've noticed a bug. Systemui crashes after setting an alarm or switching sound profile from power menu. It occurs only one time after booting the phone. If it's crashed once it's working fine until next boot. I've attached a log. The reason for crash is the "updateicon" method. Tested with some themes and its still the same error. Only with original holo theme this is not happen. Any idea to fix this?

 

[Deleted member 4819888]

I am experiencing a bug in FauxSound. When i listen to music with spotify, and i pause the music and minimize spotify, then the FauxSound settings are reverted back to standard when i start the music again. I dont remember having this bug before, so i guess it has something to do with the new kernel

not sure how this is happening to you, but I just did what you said multiple times and the bug didn't happen. Also, Spotify can't really access FauxSound, so it might be another app that you have that triggers this

I've noticed a bug. Systemui crashes after setting an alarm or switching sound profile from power menu. It occurs only one time after booting the phone. If it's crashed once it's working fine until next boot. I've attached a log. The reason for crash is the "updateicon" method. Tested with some themes and its still the same error. Only with original holo theme this is not happen. Any idea to fix this?

This doesn't happen on my system, and I do use a different theme (Colorphobe). This could happen due to the specific themes you're using

 

[BokeB]

Tried with colorphobe and the problem was the same. Tried some things to find out what the problem is. In the last step i cleared data of "designs". After reboot it seems to work. So if somebody has the same problem, just clear data of " designs" and problem is gone ? Thanks.

 

[drbiggy]

Hi, i flashed the latest nightly yesterday and i am now experiencing issues with magnetic charging. I get the charging animation but the battery % keep going down.
Anyone had that problem before ?

 

[Heroxis]

I have to reset (power + vol up) my phone like 5 times a day since the last two releases. I hooked it up to adb and read logcat while the problem occured. (screen stays black).

-----> pressing power button
I/PowerManagerService( 1266): Going to sleep by user request...
-----> pressing power button again
E/QCOM PowerHAL( 1266): Failed to acquire lock.
I/PowerManagerService( 1266): Waking up from sleep...
D/audio_hw_primary( 391): adev_set_parameters: enter: screen_state=off
V/msm8974_platform( 391): platform_set_parameters: enter: screen_state=off
V/msm8974_platform( 391): platform_set_parameters: exit with code(0)
D/audio_hw_extn( 391): audio_extn_set_anc_parameters: anc_enabled:0
E/audio_a2dp_hw( 391): adev_set_parameters: ERROR: set param called even when stream out is null
I/WindowManager( 1266): Lock screen displayed!
D/DisplayPowerController( 1266): Unblocked screen on after 68203207 ms
D/audio_hw_primary( 391): adev_set_parameters: enter: screen_state=on
V/msm8974_platform( 391): platform_set_parameters: enter: screen_state=on
V/msm8974_platform( 391): platform_set_parameters: exit with code(0)
D/audio_hw_extn( 391): audio_extn_set_anc_parameters: anc_enabled:0
E/audio_a2dp_hw( 391): adev_set_parameters: ERROR: set param called even when stream out is null
-----> letting screen timeout occure
I/PowerManagerService( 1266): Going to sleep due to screen timeout...
-----> pressing power button again
E/QCOM PowerHAL( 1266): Failed to acquire lock.
I/PowerManagerService( 1266): Waking up from sleep...
D/audio_hw_primary( 391): adev_set_parameters: enter: screen_state=off
V/msm8974_platform( 391): platform_set_parameters: enter: screen_state=off
V/msm8974_platform( 391): platform_set_parameters: exit with code(0)
D/audio_hw_extn( 391): audio_extn_set_anc_parameters: anc_enabled:0
E/audio_a2dp_hw( 391): adev_set_parameters: ERROR: set param called even when stream out is null
I/WindowManager( 1266): Lock screen displayed!
D/DisplayPowerController( 1266): Unblocked screen on after 68271215 ms
D/audio_hw_primary( 391): adev_set_parameters: enter: screen_state=on
V/msm8974_platform( 391): platform_set_parameters: enter: screen_state=on
V/msm8974_platform( 391): platform_set_parameters: exit with code(0)
D/audio_hw_extn( 391): audio_extn_set_anc_parameters: anc_enabled:0
E/audio_a2dp_hw( 391): adev_set_parameters: ERROR: set param called even when stream out is null

 

[drbiggy]

i can also confirm Heroxis problem, although it happened only twice to me in 2 days.

 

[Deleted member 4819888]

i can also confirm Heroxis problem, although it happened only twice to me in 2 days.

I have to reset (power + vol up) my phone like 5 times a day since the last two releases. I hooked it up to adb and read logcat while the problem occured. (screen stays black).

The logcat doesn't contain anything unusual. The same appears in my logcat when i lock/unlock the device.
Can you provide a kmsg? Maybe it's the kernel.
Also, were there any changes in any kernel parameters (governors, voltage etc..)?

 

[drbiggy]

Hi,

just wanted to say that my phone hard bricked yesterday.

After i had thatr magnetic charging issue i installed the "normal " new pac man nightly, and after a few hours my phone just wouldnt start up anymore.
No hard reset possible, no flash or fastboot mode possible. just a red blinking led when its at the wall charger.

I dont't blame your rom, but i don't know what happened so i just wanted to give everybody a heads up.

I sent my phone to sony, maybe i still get warranty. I will report back.

 

[AllAboutTech]

hi @oshmoun,

by any chance did you managed to fix the RIL and data connection for Z1c?
you need any help in testing something?

thanks.

 

[Deleted member 4819888]

Hi,

just wanted to say that my phone hard bricked yesterday.

After i had thatr magnetic charging issue i installed the "normal " new pac man nightly, and after a few hours my phone just wouldnt start up anymore.
No hard reset possible, no flash or fastboot mode possible. just a red blinking led when its at the wall charger.

I dont't blame your rom, but i don't know what happened so i just wanted to give everybody a heads up.

I sent my phone to sony, maybe i still get warranty. I will report back.

So sorry to hear that
Thanks for the heads up too!
It'd also help if you describe the magnetic charger problem you mentioned, and also tell us if you made any changes to the kernel (overclock, undervolt etc..)

hi @oshmoun,

by any chance did you managed to fix the RIL and data connection for Z1c?
you need any help in testing something?

thanks.

Sorry i didn't have time to do anything lately (family issues), but from what i read, Krabappel is working on fixing this. He's much more experienced than me

 

[drbiggy]

Well, the phone seemed to be charging ( saying it was charging etc) but percentage did not go up.
Using micro usb to charge worked well and resulted in a normal charging time.

No kernel modifications were made no over under cloking or volting.

Maybe i just got a bad device in the first place

 

[Deleted member 4819888]

Well, the phone seemed to be charging ( saying it was charging etc) but percentage did not go up.
Using micro usb to charge worked well and resulted in a normal charging time.

No kernel modifications were made no over under cloking or volting.

Maybe i just got a bad device in the first place

thanks for the explanation!
it does seem to be the device, but that still doesn't exclude the ROM and kernel from being the issue.
At least now people know what symptoms to look out for!
I'll post a warning at the top of the first post for people to see, thanks again!
and sorry again for your device, hopefully sony will give you an answer regarding the source of failure :fingers-crossed:

EDIT: done! warning in first post. I sure hope no one will report the same issue