yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] xalodogan:
I think i have a bad screen.

Today i went to a store and compared my Z3C with a another one. The weird thing my screen is more blue / Cold.

I checked the brightness and calibration on both. They where the same.

The other thing was i took a picture on both.....the black colors on the other one was more black. I hope not i also have a bad camera. I dont have those pink color phenomenem told by others.

Does anyone also had that fault ?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] davebugyi:
Can you tell when was your phone manufactured and where?

It's on the paper/sticker next to the the SIM card slot and the date should look like 14W41 (year 14, week 41). Maybe they used a different screen, which is a known policy. By the way, the HTC (M7) had 3 screen variants and 2 camera variants, but I did not hear if Sony uses 2 diferrent sensors.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] xalodogan:
My is 14w42. The demo one in store was 14w37 D5803.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] davebugyi:
http://xdaforums.com/showthread.php?t=2652220&page=1

Here is how to check it, but it needs root.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] frostitomik:
It's strange, but am I the only one who's display's white is actually more into red/pink, not blue? My display, especially on sunshine is all red-ish, so I have actually increased the green to make it more neutral... :eek:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] cyphomatic:
Did you check if the brightness settings were the same? When low light, the blue tends to get stronger.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] xalodogan:
It was the same. I will send it to Sony and see what they can find out.
[Omni Q&A] m0d:
I would like to port omni for the z3 compact,

If you could point me in the right direction in regards to repositories to include in my local manifest I would be very grateful.

From omni

android_device_sony_msm8974-common

android_device_qcom_common

android_device_sony_common

android_device_sony_qcom-common, seems to be missing a lot of proprietary files.

From CM?

android_device_sony_z3c

android_device_sony_shinano-common

android_kernel_sony_msm8974

Which caf repositories would I need?

Omnirom's kernel for 8974 is only for 4.4, will it do or should I use CM?

Do I need android_hardware_sony_DASH ?

Thank you in advance
[Omni Q&A] m0d:
Using

android_device_sony_z3c

android_device_sony_shinano-common

android_kernel_sony_msm8974

android_device_sony_qcom-common

android_device_sony_msm8974-common

android_device_sony_common

android_device_qcom_sepolicy

The first issue I had was

make: *** No rule to make target `.../omni/out/target/common/obj/JAVA_LIBRARIES/qcmediaplayer_intermediates/classes.jar', needed by `.../omni/out/target/common/obj/PACKAGING/boot-jars-package-check_intermediates/stamp'. Stop.

I tried adding android_hardware_qcom_media-caf-bfam and android_hardware_qcom_display-caf-bfam to the local manifest.

I tried removing projects android_hardware_qcom_media and android_hardware_qcom_display and replacing them with the above two and the error still showed up.

It only stopped showing after I commented out

# Media
#PRODUCT_PACKAGES += \
# qcmediaplayer

#PRODUCT_BOOT_JARS += \
# qcmediaplayer

from msm8974.mk in /device/sony/msm8974-common

Now I am getting,

/home/ne/zZz/omni/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/ne/zZz/omni/out/target/product/z3c/obj/ETC/sepolicy_intermediates/policy.conf
libsepol.check_assertion_helper: neverallow on line 297 of external/sepolicy/domain.te (or line 5288 of policy.conf) violated by allow vold vfat:filesystem { relabelto };
Error while expanding policy
make: *** [/home/ne/zZz/omni/out/target/product/z3c/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
[Omni Q&A] Entropy512:
You might want to try getting it up and running with 4.4 instead

Right now, find7 is the only non-Nexus 8974 we have running with 5.0, we're a bit behind on bringing up other devices. We also have yet to do any work on any of the z2 or z3 family. (I have a Z3 I plan on bringing up when I have the time... but I have no idea when I'll have the time...)
[Omni Q&A] m0d:
I am currently trying to get it to build recovery, but having some compile errors.

cp: cannot stat ‘/home/ne/zZz/omni/out/target/product/z3c/ramdisk-recovery.cpio’: No such file or directory

Is there any reason as to why it would be better|easier to try 4.4?

since in both cases z3c is not supported.

If you can help me with suggestions in regards to the error I will be grateful
[Omni Q&A] Entropy512:
With 4.4 we at least had some Sony 8974s up and running, but we have yet to do a bringup of any Sony with 5.0 yet.
[Omni Q&A] m0d:
Thank you for the suggestion.

I will try and check to see if it will be any easier.

The problem I am having is with the custombootimg.mk, since CM uses android_device_qcom_common which has the dtbToolCM. Omni includes the dtbTool in the 8974-common repo.

in the oppo mkbootimg.mk (the 8974 sony devices also have a similar code in regards to dtbTool)

I believe I have to add something of the sort:

## Imported from the original makefile...
KERNEL_CONFIG := $(KERNEL_OUT)/.config
MSM8974_DTS_NAMES := msm8974
MSM8974_DTS_FILES = $(wildcard $(TOP)/$(TARGET_KERNEL_SOURCE)/arch/arm/boot/dts/msm8974pro*.dts)
MSM8974_DTS_FILE = $(lastword $(subst /, ,$(1)))
DTB_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%.dtb,$(call MSM8974_DTS_FILE,$(1))))
ZIMG_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%-zImage,$(call MSM8974_DTS_FILE,$(1))))
KERNEL_ZIMG = $(KERNEL_OUT)/arch/arm/boot/zImage
DTC = $(KERNEL_OUT)/scripts/dtc/dtc
define append-msm8974-dtb
mkdir -p $(KERNEL_OUT)/arch/arm/boot;\
$(foreach MSM8974_DTS_NAME, $(MSM8974_DTS_NAMES), \
$(foreach d, $(MSM8974_DTS_FILES), \
$(DTC) -p 1024 -O dtb -o $(call DTB_FILE,$(d)) $(d); \
cat $(KERNEL_ZIMG) $(call DTB_FILE,$(d)) > $(call ZIMG_FILE,$(d));))
endef
## Build and run dtbtool
DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbTool.oppo.msm8974$(HOST_EXECUTABLE_SUFFIX)
INSTALLED_DTIMAGE_TARGET := $(PRODUCT_OUT)/dt.img
[Galaxy S III Q&A, Help & Troubleshooting] Raesandemmasdad0912:
Does anybody have just the stock Rom you can use on Odin
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
There is no stock 4.4 on the i9300.
[Galaxy S III Q&A, Help & Troubleshooting] RazorMC:
As mentioned earlier, there is no stock KK firmware for i9300.

Though you can try some of the ported ROMs. They are close enough to stock in most ways.

I prefer the unofficial CM12 roms btw :p
[Galaxy S III Q&A, Help & Troubleshooting] Darke5tShad0w:
You need to go and ask in the american s3 threads.

This is for the i9300 model.
[X 2014 Accessories] xnifex:
In case you've never had one, dbrand has pretty nice skins for the Moto X.
[X 2014 Accessories] NWKENT:
Yeh..planning on order Moto X Pure Edition next week, since the blue N6 64GB still waiting..and was thinking of wood backplate..but..now that I've seen yours, and others dbrand..maybe I'll go with black back panel, and apply one of these..Thanks for your encouragement and post..

BTW..beautiful device you have..

:)

Exclusive Moto user since 1989..

XT1080M Droid Maxx Developer Edition

http://waynekent.com/page6.html

"Praise Jah" YOU people.!
[X 2014 Accessories] xnifex:
Thanks. I love the blue accents, makes the grilles in the front look so nice. Yeah I have a carbon fiber back for the n6 as I was sure I was going to purchase that. I need to sell that.
[X 2014 Accessories] NWKENT:
Yeah..I was thinking blue, or orange..would look nice, like yours..and cheaper than the wood, other Moto panels..

And if the Moto site ever has the N6 I want, and receive it, I'll keep you in mind, and check back with you, if you still have the dbrand and wish to sale..

Which model X do you have, and what do you think so far, with the device.?

I really like the CF look..like on my Droid Maxx..

Anyhow..thank you, and take care..

Exclusive Moto user since 1989..

XT1080M Droid Maxx Developer Edition

http://waynekent.com/page6.html

"Praise Jah" YOU people.!
[X 2014 Accessories] xnifex:
I have the Pure Edition on Tmobile & love it. Great phone & really nice coming from the Nexus 4.
[X 2014 Accessories] Pilz:
I've been using dbrand skins for a while now and they are excellent. I would recommend these to anyone who wants a nice skin. I just ordered my wife a Moto X Pure Edition so maybe she will want a skin for it. Hopefully dbrand will also release their pink carbon in addition to their limited edition blue carbon.
[X 2014 Accessories] 66racer:
I might end up getting the black carbon if I get bored of the white, but here is a pic of the white for those curious.
[X 2014 Accessories] xnifex:
just picked up the blue to replace my black carbon fiber. I think it'll go nice with the blue accents I have.
[X 2014 Accessories] 66racer:
I agree, post picks when you get it. Im sure it will look great.
[X 2014 Accessories] gotzaDroid:
Just ordered the blue carbon too. I already have a blue back, so I justified it because I'm not changing the color of the phone.
[X 2014 Accessories] chad24taylor:
Anyone have any experience using these with a Diztronic case? I had a Toast wood skin, and it was just thick enough to make cases fit awkwardly. I usually only put a case on when I go to the gym, but it's extremely important for me to have that protection.

Basically, is it thin enough that it doesn't affect case fit?
[X 2014 Accessories] Pilz:
Is the Toast thicker than a vinyl skin? The Diztronic fits fine if you have a skin like dbrand on your phone but I've never had a toast wood skin so I don't know.
[X 2014 Accessories] pacobahyba:
I got a dbrand for my xt1097 and it is amazing. Gave me a possibility for customizing my x (since motomaker is not available in Brazil) and delivery had no issues so I am now a fan. But, I am indeed looking for a decent screen protector to use. I had to remove mine to install the front piece of my skin but I am rather clumsy and I am scared to death that I am using this thing without a screen protector. Do you guys have any suggestions?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] lanabanana:
Hey,

I just want to start by saying that I'm a complete newbie when it comes to tinkering with phones, and all this happened because of my deadly curiosity.

So, today I was bored and thought I'd root my phone (Sony Ericsson Live With Walkman) (a friend helped me do it a year ago on another device), which I succsessfully did.

Then, after a bit of browsing, I found out about custom roms and whatnot and tried installing one. After hours of reading tutorials about it I somehow ended up at something called a locked bootloader, which I've tried unlocking through a program called S1 tool with the help of a testpoint device (safety pin + wire combo). It was somewhere around this point that my phone stopped showing any sign of life (pushing the power button, trying to enter flash mode, connecting it to my pc and the wall charger does nothing).

The only thing that even remotely tells me my phone is still alive is called ZEUS Flash Device, which shows up in my device manager every time I connect it through the mini-USB cable.

As I understand I may have achieved a so-called hard brick state on my phone, and probably need to get a new one.

I would like to know if there's any way to undo all the horrible things I have done to my lovely phone.

I would be really thankful for any kind of help.

Thanks in advance
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] karandpr:
Go to a phone repair shop to get it repaired. You will require Medusa Box or SE Tools Box to restore the phone.
[AT&T Samsung Galaxy S 5] Veight:
So it seems that UBSM actually requires stock launcher which I have either frozen or deleted as I use nova and had no need for it. This ended up causing my phone to be stuck at the ATT logo in black and white, is there any possible way of getting out of UBSM? I have seen a few fixes but I was thinking if maybe charging the battery to full would take it out of UBSM.
[AT&T Samsung Galaxy S 5] Rakuu:
No, charging full wont turn it off, would kind of defeat the purpose lol, not like you couldnt have tried this any way though, its not a huge hassle to charge. The fixes are posted, you know where they are as youve said, do that and you should be sqaured away.
[AT&T Samsung Galaxy S 5] Veight:
Thanks. Yeah, I got it taken care of, didn't have a TB backup so I had to manually re-install everything which I was hoping to avoid. This time, I did set it up right and can use UBSM without any issues. :D
[JAMin, XDA Neo, S200 General] kanpuria:
Hi! all

i was trying to get my 818 working with the a2dp profile and i've got the info on that with the tornado thread.

i downloaded the regeditSTG software but was unable to edit the registry. can anyone guide me to a thread or help me getting the right software cos Resco and Mobileregistryeditor are not working on my phone.

Thanks!!!!
[JAMin, XDA Neo, S200 General] levenum:
Try PHM reg edit. Never faild me.
[JAMin, XDA Neo, S200 General] vijaysv:
could u tell me which radio rom ur using. my config is

ROm Ver: 2.20.7.34

Radio : 02.61.21
[Ascend Mate 7 Q&A, Help & Troubleshooting] boovilly:
Hi,

Just received my Mt7 L09 today and wanted to be sure if there is a factory applied screen protector or not?

I have read/heard there is, but I am unsure if mine has one applied. It is very good if there is one.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
yes there is .. u should see line on top .. near camera and speaker ..
[Ascend Mate 7 Q&A, Help & Troubleshooting] boovilly:
Should there be a discernible line?
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
man just u cant miss it.. only if u ar blind or somethin..
[Ascend Mate 7 Q&A, Help & Troubleshooting] boovilly:
Looks like I don't have one applied then. There is no line at all on my device.

Thanks for your help.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
u can order it.. it's cheap on ebay..
[Ascend Mate 7 Q&A, Help & Troubleshooting] mirchichamu:
My one also have no screen protector applied. And I didn't apply also on gorilla screens.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
Gglass is scratchy..dare to scratch it with keys or something :) you wont do it..

Only if we had sapphire glass is anti-scratchy
[Ascend Mate 7 Q&A, Help & Troubleshooting] mirchichamu:
I didn't apply any screen protector on my sgs2 which was gorilla glass. I used it for 3 years without screen protector or any cover. Not a single scratch on the screen. Similarly I didn't apply any screen protector on my Coolpad 9976A. Since almost 2 years, I am using it but no scratches at all.
[Ascend Mate 7 Q&A, Help & Troubleshooting] blackinfinity:
Yes it is factory applied. Every one has it. But I would really recommend to take it off.

Fingerprints att fat marks attach very easily
[Ascend Mate 7 Q&A, Help & Troubleshooting] ci00aaj:
Neither of mine came with a factory applied screen protector...both from Amazon.fr
[Ascend Mate 7 Q&A, Help & Troubleshooting] boovilly:
Possible link there. Mine came from Amazon.fr also. Saying that, I read reviews on that site saying that people had received devices with screen protectors. No big deal anyway :)

Merry Christmas everyone
[Ascend Mate 7 Q&A, Help & Troubleshooting] ci00aaj:
Could I ask if you have a screen defects on your phone? I've had 2 phone from amazon.fr and both have had "wavey" screens around the speaker and bottom
[Ascend Mate 7 Q&A, Help & Troubleshooting] NiceCarpet:
My L-09 version doesn't seem to have any issues like that - nor major backlight bleed.

Here's a screenshot of what the factory-applied protector looks like if you're wondering if you have one. It's pretty obvious.

[IMG="Screen Protector"]http://i.imgur.com/q26x9Dw.png[/IMG]
[Ascend Mate 7 Q&A, Help & Troubleshooting] boovilly:
[MENTION=2967402]NiceCarpet[/MENTION]

Thanks for the picture. Definitely clears up the confusion as to whether or not there is one. 100% certain now that I don't have one.
[Ascend Mate 7 Q&A, Help & Troubleshooting] Simona Simmy:
I already said this b4 .. if u read thread properly you would know..
[Samsung Galaxy Nexus] poo706:
poo706 presents... LIQUIDSMOOTH LOLLIPOP - UNOFFICIAL

Things to note

Same kernel as Ziyan's CM12 (EXT4 only)

F2FS supported on /data and /cache only, /system must be EXT4

For F2FS use one of the following Full_Auto kernels: R1, R4.5, R5, R6, R7, R8, R10, R10, R11

Linaro toolchains for both ROM and kernel

Liquid Optimizations

CM12 Theme Engine

Deodexed: First boot will take a long time!

Clear all recents on a regular basis to reduce lag, they survive a reboot!

Su binary is not included, install SuperSu from recovery: http://download.chainfire.eu/supersu

Use as small gapps as possible, I've had luck with the minimal edition from here: http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330

Changelogs:

2/20: Boot animation memory leak fix

2/13: Switched from Layers to CM12 Theme Engine (clean flash this build)

2/10: Resynced source

1/27: Reverted minor F2FS change, Linaro 4.8.4 for ROM, Linaro 4.9.1 for kernel, deodexed

1/24: Minor change regarding F2FS, HW decoding working again, YouTube working, navbar customizations

1/18: ROM (but not kernel) supports F2FS on /data and /cache, torch tile fixed

Credits and thanks:

LiquidSmooth team: https://github.com/LiquidSmooth

[MENTION=2633638]Ziyan[/MENTION]: https://github.com/Ziyann

[MENTION=3390093]MWisBest[/MENTION]: https://github.com/MWisBest

[MENTION=1048318]zzpianoman[/MENTION]: https://github.com/zzpianoman

[MENTION=4531957]musical_chairs[/MENTION]

[MENTION=4608636]bsmitty83[/MENTION] for the Full_Auto kernel: http://xdaforums.com/galaxy-nexus/development/lollipop-kernel-fullauto-r1-aosp-cm-t2994371

[MENTION=4758810]Nautilus74[/MENTION] for repacking Full_Auto with ramdisks

[poo]
[Samsung Galaxy Nexus] jcruz942:
Thanks so much for the continued support. Managed to get it to boot up and get through set up. Only real issue that I've seen so far was that it wouldn't connect to the network. Nothing comes up under baseband in the settings, can't make calls or send sms, also messaging crashes trying to compose new. Other than that it runs smoothly and looks very promising. Keep up the good work!
[Samsung Galaxy Nexus] poo706:
Crap! My toroplus no longer has service, so I couldn't check phone or data. I'll look into it.

[poo]
[Samsung Galaxy Nexus] jcruz942:
Awesome if you need someone with service to test it I'm more than up for the job.
[Samsung Galaxy Nexus] poo706:
I'm making a test build right now to see if I fixed data and voice. If that doesn't do it, I have a few more commits that I'll try. Since my toroplus isn't activated any more, I will ultimately need some testers. I hope to try it out and get it posted tonight, but good chance I'll have to wait until I get home from work tomorrow.

[poo]
[Samsung Galaxy Nexus] poo706:
I won't bother releasing yesterday's build, still no baseband. Hopefully the next one will be a winner. If I don't get to it before then, I should be able to make another build on Thursday.

[poo]
[Samsung Galaxy Nexus] Swamphound:
I just activated my sons old toroplus on Ting and ready to test.

Sent from my Ting Toro Plus Nexus using Xparant Red Tapatalk
[Samsung Galaxy Nexus] poo706:
1/4 added to the op. We have baseband! Someone please report on voice, data, and messaging please. Note that no superuser is included, you'll need to install supersu. And use as small gapps as possible.

[poo]
[Samsung Galaxy Nexus] namtombout:
Everything seems to be working. Thanks poo
[Samsung Galaxy Nexus] GuinnessX:
So happy to see this coming along! I've been holding off on any LP ROMs because they are all so damn bright... Do you have "Total blackout" and/or the CM12 theme engine incorporated yet?
[Samsung Galaxy Nexus] poo706:
No blackout or theme engine yet. But it does have a dark theme.

[poo]
[Samsung Galaxy Nexus] thelgog:
im on the 1/4 build i just get a ! on my signal bars but i pick up signal n stuff i would usually get like 3 bars of lte where i am put i only get the 3 bars and no data is this just an unsolved bug??
[Samsung Galaxy Nexus] cr08:
So a stupid question on my part after parsing the lollipop rom threads in this section: Is it my understanding that other than camera use a lot of the bigger bugs are nailed down now? ie: Data/Voice works. How's video playback in the youtube app for example? Anything to stop this from being a daily driver at this point? My main uses for the GNex at this stage are data/wifi/text use with minimal voice. Camera use is very sparse to the point I can live with a third party app. Video playback is a big one though with Youtube being about 95%. And music/podcast playback.
[Samsung Galaxy Nexus] poo706:
I'm not sure how good video playback is, I would certainly welcome your input if you'd like to give it a shot. Other ROMs have made progress with video playback, long SMS's, and the camera, but I haven't started focusing on that stuff yet, I'm still trying to get data going on toro.

[poo]
[Samsung Galaxy Nexus] poo706:
1/11 added to the OP.

- Camera works, including flash

- Torch tile doesn't work, but DashLight app does

- Haven't tested, but should have fixed HW decoding with MX Player

[poo]

Edit: Also turned on Liquid Optimizations: https://github.com/LiquidSmooth/android_build/commit/151bdb50158cf0485c4fa1e3b6429a8f2848f8ff
[Samsung Galaxy Nexus] jcruz942:
Just flashed the 1/11 build and sending text is whonky. I can open the texting app but if I try to open a conversation it forces close. Tried textra, stock app, google messenger, and gosms all of them have the same issue for me. Tried it both with and without Bsmitty's cm kernel so it wasn't effecting it. Calls do work. Not sure if anyone else is having this issue. Gonna try to re-download, see how it goes, and report back.
[Samsung Galaxy Nexus] poo706:
I take it you don't have this issue with other LP toroplus ROMs? If so, which ones?

[poo]
[Samsung Galaxy Nexus] jcruz942:
Correct on cm12 and fml.
[Samsung Galaxy Nexus] poo706:
Looks like I'm having it too with the stock messanger, Tapatalk too. You? Is that musical_chairs's cm12 you're referring to?

Since I'm seeing it too I'll grab a log and see what I can do.

[poo]
[Samsung Galaxy Nexus] jcruz942:
Yes it is musical_chair's cm12 sorry for any confusion.
[Samsung Galaxy Nexus] poo706:
I think I know exactly what the problem is. This is the first build that used the previous build's chromium compilation as a prebuilt. I'll resync and recompile tomorrow with prebuilt chromium turned off. I remember something similar to this with kk.

[poo]
[Samsung Galaxy Nexus] poo706:
Added Google Drive mirror to OP.

[poo]
[Samsung Galaxy Nexus] poo706:
1/13 added to the OP.

- Disabled prebuilt chromium, which should fix all of the app crashes

[poo]
[Samsung Galaxy Nexus] jcruz942:
Just flashed the 1/13 build and can confirm that the texting bug is squashed. Only quirk I've found is the bootanimation being scaled down, which doesn't really bother me since I always change the bootanimation. No other things to report as of yet. Running it with BSmitty's r5 cm kernel, no performance changes but so far so good.
[Samsung Galaxy Nexus] poo706:
I just confirmed that myself. Too bad I can't use prebuilt chromium at the moment. It reduces 8.5 hour builds down to 5 hours. As far as the boot animation, when it's full screen, it runs incredibly slow and choppy. After a bunch of experimenting, that's as big as I can make it to keep it mostly smooth.

[poo]
[Samsung Galaxy Nexus] jcruz942:
So update I can't record videos with either stock or 3rd party tried with open camera and it was a no go, however taking photo works perfectly fine. Second is pretty weird I tried to watch videos on youtube but I cant seem to get it to work it stays loading forever and after a while says connection error, but if I use viral a 3rd party youtube player videos play without a hitch. At first I thought it was probably the kernel so I did a complete wipe, clean flash with only the 1/13 build and gapps and ran into the same issues.