yashsingh1/xdaforums huggingface dataset:
[Pixel C Q&A, Help & Troubleshooting] McChen147:
Here's maybe a clue on at least some of the touchscreen issues, I found out that it might be somehow related to autobrightness?

When I first got my Pixel C, I didn't have any touchscreen issues that others have reported. Just today, I noticed that auto brightness was not working, the screen was not adjusting to the ambient light (I've had auto brightness on ever since I got the tablet and it has worked until now). Manually adjusting the slider (with auto brightness still enabled) did not change the brightness. Hmm...odd. So I rebooted thinking that might fix it. After the reboot, I finally saw the touchscreen issues that others have reported. Missed taps, interpreting swipes as taps, etc. Auto brightness still wasn't working, brightness slider still didn't do anything. Rebooted again, same thing. Disabled auto brightness, rebooted and the touchscreen issues disappeared.

However, auto brightness still wasn't working. With auto brightness disabled, the slider worked to adjust the brightness. With it enabled, the screen didn't adjust brightness by itself and the slider didn't adjust brightness either. What finally worked to fix the auto brightness was to clear the cache from android settings, reboot into recovery and wipe the cache from there.

Maybe this information will help someone else too.
[Pixel C Q&A, Help & Troubleshooting] Chainfire:
I've seen the issue occur with and without auto-rotation set, and have also seen it work fine in both cases.
[Pixel C Q&A, Help & Troubleshooting] xargs1:
Same here. It's not a "workaround".
[Pixel C Q&A, Help & Troubleshooting] Rox598:
Having issues with mine too

Swiping will sometimes act as touches, it's really annoying when scrolling through Youtube.
[Pixel C Q&A, Help & Troubleshooting] xargs1:
After playing with my second unit for three days, it still doesn't have the problem. The one thing I've taken care to do is not power it off or reset it.
[Pixel C Q&A, Help & Troubleshooting] Rox598:
just went on mine there and something is happening

I'm sure animations aren't playing smoothly atm and while I was scrolling it would stop every few seconds so I turned on pointer location and while dragging my finger about it stops for a microsecond.

When I say animations weren't smooth it was like they were going at a much lower FPS

EDIT: Even after a factory reset I can't use my touchscreen smoothly anymore it keeps jumping about and occasionally being fine.
[Pixel C Q&A, Help & Troubleshooting] oRAirwolf:
Out of curiosity, has anybody with WiFi or touchscreen issues tried flashing the MXB48K factory image from here? https://developers.google.com/android/nexus/images?hl=en

My Pixel C is up to date, but it is running the MXB48J image. I have not had experienced any of the WiFi or touchpad problems others have reported here, but I was thinking that there hasn't been any word on what this "K" image is and maybe it is a newer version of the device firmware. Perhaps this version has updated WiFi and touchpad drivers? I'd flash it myself, but it wouldn't help much since I am not seeing any problems to begin with.

Thoughts?
[Pixel C Q&A, Help & Troubleshooting] Rox598:
after several reboots and a factory restart it's fine now.

Not sure if it's worth mentioning but while it was happening my whole tablet was fricken freezing now it's heated up it's okay.

Not sure if it's related though.
[Pixel C Q&A, Help & Troubleshooting] WMDRY:
My replacement tablet does not have any issues, afaik. It is a much improved experience. It is even smoother than it was when the old tabled worked pretty well every other reboot.

When I read through your posts, I would conclude that some component/sensor is at fault and causes the input lag, the brightness error for one user, my random shut-downs and the orientation lock "workaround". Maybe if any of the components is a bit off, the input fails due to some strange software error handling. Just keep in mind, we are a quite small group who got faulty devices. There is not much attention to this problem aside from this place here.
[Pixel C Q&A, Help & Troubleshooting] bennyboy_84:
Soooo... Received my second unit on the 23rd and it ran fine for 2 days. Then the exact same thing that hapenned with the first one hapenned. I picked it up after 5-6 hours of inactivity and it was frozen (screen wouldn't turn on) so had to hard reset it.

Immediately after booting it, the screen became irresponsive exactly like my first unit. Reboot in safe mode, and then I got repeated message that Google play services had crashed so decided to delete cache/app data of Google play services and reboot : tablet back to smooth as butter experience but all widgets I had installed were gone : had to put them back one by one (assuming this might be normal when you wipe Google services data and/or boot in safe mode?).

I have no idea if all of this is linked altogether but with my previous unit I tried everything and the screen would remain irresponsive, hence why I decided to RMA it whereas this one rebooting into safe mode and clearing cache/data from Google play services immediately solved the issue.
[Pixel C Q&A, Help & Troubleshooting] Hazzo31:
Same here. Working perfect first week. Today got the touch screen bug. Restarted two times and in the second one everything is working fine. Is obviously software related. Let's hope there is an update around the corner to fix this and many bugs.

Enviado desde mi Pixel C mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] cheep5k8:
My kernel for the Pixel C incorporates fixes for the touchscreen which haven't been released yet as a factory image or OTA.. I can't really test this since I haven't had the issues myself, but maybe someone who has could give it a try.
[Pixel C Q&A, Help & Troubleshooting] Hazzo31:
I prefer to be stock with this one. In the end hacking devices with not stock software always gave me inconsistences. It's sad but true. You might get benefits but there always tradeoffs :s . I'll wait for a proper Google release. Thanks!

Enviado desde mi Pixel C mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] Rox598:
my replacement machine (same model # as the last one) was fine since I got it (2nd of jan) and has been until I turned it off 2 days ago and ever since the touchscreen issues have taken hold of it :/ but now this time safe mode does work and the screen is fine on it.

Le Goog needs to come forward about this.

Left safe mode on for over a day and just now rebooted and it's fine in the normal mode again
[Pixel C Q&A, Help & Troubleshooting] rubene66:
If i restart my tablet without touching it i got touch screen lag problem if i power on the tablet holding it with my two hands touching the back and front i got 0 touchscreen problem when it boot up and work great.
[Pixel C Q&A, Help & Troubleshooting] harmohn:
Well Google's finally acknowledged that it's software related and are working on a fix.
[Pixel C Q&A, Help & Troubleshooting] EvansJD:
Good to know, thanks for sharing.

At least its software!
[Pixel C Q&A, Help & Troubleshooting] gtaadicto92:
My píxel c is starting to have extremely choppy zoom gestures. But it does not have problems with swipes.

Enviado desde mi Pixel C mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] EvansJD:
My standard routine is to boot to recovery and wipe cache, reboot, reboot to safe mode, reboot to normal

May take an extra couple of reboots but at some point the glitches are gone.

I use the Facebook app to figure out if all is good or not; smooth scrolling = OK, jerky movement = reboot again

Hope the fix is soon!
[Pixel C Q&A, Help & Troubleshooting] gtaadicto92:
Wiped the cache and the data got damaged!!! Have to do a factory reset :(

Enviado desde mi XT1039 mediante Tapatalk

---------- Post added at 10:10 AM ---------- Previous post was at 10:05 AM ----------

Now it is stuck in a boot loop!!! Google logo and 4 circles for 1 second, then reboots and so on

Enviado desde mi XT1039 mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] EvansJD:
Wow, that is not good.

Wiping cache only should have absolutely no impact as far as I'm aware. It was advise given when I phoned Google over the issue
[Pixel C Q&A, Help & Troubleshooting] gtaadicto92:
Finally returned the Píxel C. I hope the next unit is good.

Enviado desde mi XT1039 mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] bennyboy_84:
Anandtech review of the Pixel C is out ... Here's the Software section (page 8).

http://www.anandtech.com/show/9972/the-google-pixel-c-review/8

Yup, pretty much sums it up! Get on it Google!
[Pixel C Q&A, Help & Troubleshooting] Rox598:
That's the first review i've read that mentions the touchscreen issues

Funny how all the other reviews never mention it. Google need to get this fixed already! still no updates or even acknowledgement from Goog about it.

EDIT: Huh Google are sending that guy a new tablet with pre-release software that fixes it?
[Pixel C Q&A, Help & Troubleshooting] aeppacher:
this seems like acknowledgement to me

https://productforums.google.com/forum/#!topic/nexus/rRnzdN5lbRA;context-place=topicsearchin/nexus/Pixel$20C
[Pixel C Q&A, Help & Troubleshooting] Rox598:
Only seeing that now

It's great they actually said something about it but need to he a bit more open which they probably won't do as I'll hurt sales.
[Pixel C Q&A, Help & Troubleshooting] Rox598:
The new update actually seems to have fixed this (Yeah I know Google confirmed that it did but I'd rather make my own judgements on this stuff)

So far it's not put a foot wrong :D
[Pixel C Q&A, Help & Troubleshooting] charesa39:
Where did El Goog confirm it? Haven't seen anything of them confirming any fixes in the February update.
[Pixel C Q&A, Help & Troubleshooting] Rox598:
https://productforums.google.com/forum/m/#!topic/nexus/rRnzdN5lbRA;context-place=forum/nexus

Orrins posts a Google employee
[Pixel C Q&A, Help & Troubleshooting] charesa39:
Awesome. Thanks! That's good news. May end up buying one either this month or next. Hopefully, they'll have the random WiFi issue figured out by then.
[HTC One Mini 2] DRAFF:
My HTC One Mini 2, when takes photos with flash, they are all with a purple hue evident.

Do You know what it is and how to fix them?
[HTC One Mini 2] GuestK00204:
look at settings. its possible you are using a custom setting.

enter cam and in settings, reset to original.
[HTC One Mini 2] DRAFF:
...same at default setting
[HTC One Mini 2] DRAFF:
anyone helps?
[HTC One Mini 2] GuestK00204:
i think you best contact HTC.

When its faulty hardware they usually fix for free.
[HTC One Mini 2] Pietro000:
I can fix it :) pietro151@gmail.com
[Miscellaneous Android Development] sambosat:
Good evening all.

My cousin just brought me his galaxy grand prime G530H and the phone was booting but very slow. He asked me to format it for him. So I hard reset the phone and wiped data but when I started the phone, the virus is still there and the phone was not working properly it even has a launcher of its own (hola launcher). It looks as if the virus became part of the system. I'm not able to uninstall it. The only thing I was doing is to disable it. But once I connect to the internet, the phone hangs and I can't do anything. What is the solution. is there a way to wipe it. This is the first time I see this. anyone had this issue before. Please need your assistance.

Ok here is another update. I tried to flash it with original stock rom from sammobile using Odin. I load everything and click start.

the writing fails with the following error

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Binary Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1100)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> aboot.mbn

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Anyone can suggest anything

Not sure if had applied an update that caused to become like that but this is my only conclusion and my cousin is saying that he did not do anything. Is there an image that I can restore it with that will undo this
[Miscellaneous Android Development] sambosat:
Ok guys Please ignore my problem. I was able to find the solution in another thread and found the correct flash and flashed my cousin's phone and now it has been revived. Thank you XDA
[Motorola Droid 4] dreikk91:
Good job :D
[Motorola Droid 4] Shobai:
Thanks again!
[Motorola Droid 4] joefuf:
Excited.
[Motorola Droid 4] Shobai:
Installed 151214 this morning over the top of 151210.

The "low in call volume " issue appears to be fixed, as per the notes above; I've had a few phone calls this morning with only one issue:

I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. [MENTION=3457922]stargo[/MENTION], is that related to the issue you've fixed? Or will that be something silly at my end?
[Motorola Droid 4] rblanca:
hahahaha thanks stargooo one step more for our droid 4!
[Motorola Droid 4] stargo:
Hi,

All low-level audio-routing problems should be fixed, this sounds like a problem with the IncallUI (it probably did not specify that the audio should be routed over the headphone out). Haven't looked there yet...

Cheers,

Michael
[Motorola Droid 4] Shobai:
Thanks Michael, much obliged!
[Motorola Droid 4] Shobai:
Apologies for the double post! [MENTION=3457922]stargo[/MENTION], I think this may have been mentioned in the CM12 thread - I've got "Playback control" turned on under Buttons, but a long press of the volume keys doesn't have any effect on playback. The volume keys work properly for volume, though.

Thanks again!
[Motorola Droid 4] LuH:
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
[Motorola Droid 4] Bobcus Leper:
Flash the build from the 14th.
[Motorola Droid 4] Septfox:
Whoa nice, you got it running. Not that there was ever really any doubt ;)

I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:

How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
[Motorola Droid 4] Bobcus Leper:
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
[Motorola Droid 4] Careless_:
So has the build from the 14th fixed the DATA issue?

By no LTE/CDMA support right now, does that mean I wouldn't be able to receive emails and online push notifications unless I am on WiFi or they are Text/SMS based?
[Motorola Droid 4] Cain77:
hi, can i have noob question? is there some tutorial how to make own build (i have tried to google what to do in which order but i didnt have much luck - create folders, get local manifest, init repo but when and how get omap4 common files required for build...)?
[Motorola Droid 4] Narevek:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.

I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
[Motorola Droid 4] Careless_:
So by finding this out, it would seem that the Data connection for any provider is not functioning due to a permissions issue in which the OS cannot write the given APNs from the "search" function to the file which stores the data... is that correct?
[Motorola Droid 4] stargo:
Hi,

Great :)

Does it work after a reboot, too?

Or do you then need to toggle airplane mode again? It might be that toggling airplane mode is what actually causes the connection to be established. Judging from the radio logs I have seen, the RIL responds with an error after bootup and toggling airplane mode might fix it.

Btw, for the people on UMTS: I'm testing a fix for the crash of com.android.phone after boot.

EDIT: Confirmed by [MENTION=1070688]joojoobee666[/MENTION]: toggling airplane is enough to get data working

Cheers,

Michael
[Motorola Droid 4] LuH:
Yup, switching Vibrate on touch off in sounds settings helps from this build on. Thanks, I have decided to make this my primary system, so far great impression :)

I second that; especially Trebuchet, Settings, dialer, contacts and messaging are way more responsive. I clean installed system (1218 build; wipe /system, install just this and Open GApps Pico) with keeping data from 12.1, it went pretty smooth.

Also it's been laying in standby for about 12 hours now, Wi-Fi on, and it's still charged ~96%. Either it's a battery level reading bug and will soon drop fast, or huge improvement over L - usually I'd lose 10% - 20% at least.
[Motorola Droid 4] hearkenoath:
GREAT JOB I was looking forward to CM 13 since June. However, right after flashing GAPPS the processes crash and can't make any progreses. Doesn't matter if I use Slot 1 or 2, already tried mount no-mount /system and /data.
[Motorola Droid 4] Septfox:
Well, I'm not claiming to know for sure if either is an actual issue...the best way to see is to try it out. For science!

Safestrap was last updated significantly in the KK/CM11 days, though, so I wouldn't expect it to have a clue about ext4 encryption, let alone have access to the keys needed to read it...

As far as information, its just a modified RAMdisk configuration that mounts your SD card as internal storage, and the actual internal SD/eMMC storage as external; thus swapping the SD cards.

Be aware that:

This will make removing the card a bad idea (if you need to upgrade to a bigger card, you can shuffle stuff off the old card/onto the new card with a computer and Safestrap in USB mode).

If you've moved any apps to SD via the built-in App2SD thing, you'll want to move them back to the phone first, since applying the swap will probably break them.

Some future changes might require an updated SDswap. Always make a backup before updating to a new nightly, in case something breaks (though it should in general be pretty safe). Edit: always reflash SDswap when you install a new nightly (as you would with kernels/gapps/etc), since the CM13 package overwrites it.

Edit again: I went ahead and swapped all my stuff between int/ext storage, and applied SDswap out of curiosity.

I then went to store some apps on my freshly-swapped-in card...and found that Marshmallow (and maybe Lollipop, never checked) actually prompts you to choose the destination when you use the native App2SD; you can choose either the internal or external SD. I'd just automatically assumed it defaulted to the first external device available, as KK and before did.

So, at least as far as this application is concerned, there's no real need to apply the SDswap. I personally can't think of any other application for it either, since most apps will let you choose where you want to store any extra data they create. *shrugs*

Edit again: I lied :v

With a "vanilla" setup, sdcard1 isn't selectable as an install location.

At a guess, swapping gets the external SD card marked as permanent storage, enabling app2SD for it. I'm not sure why internal storage isn't the opposite, though; maybe it's still using the configuration from storage.xml (which I forgot to delete).

Gonna go bug joojoobee about it in his own thread.

Edit yet again: checking \data\system\storage.xml post-swap finds that both internal and external SD cards are marked with a userflag of 0.

External SD, set as Portable Storage, had a flag of 3 pre-swap.

Amusingly, both show up as Portable Storage in Settings > Storage.
[Motorola Droid 4] daniel_m:
Just in case anyone here would like to try out SELinux in permissive mode and hasn't heard about joojoobee666's custom kernel yet:

http://xdaforums.com/droid-4/development/wip-marshmallow-custom-droid-4-razr-oc-t3281830

joojoobee666 was kind enough to compile the "1.4Ghz Kernel LV (Low Voltage)" with SELinux set to permissive :o
[Motorola Droid 4] Bobcus Leper:
[MENTION=1070688]joojoobee666[/MENTION], I successfully installed you new permissive 1.4 GHz LV kernel. This is the first 1.4 GHz kernel that has ever booted on my RAZR. The only problem is, there are none of your kernel features. Everything is like the default kernel. There are no custom governors, and the maximum clock speed is 1.2 GHz.
[Motorola Droid 4] daniel_m:
This is probably the wrong thread.

At least on my Droid 4, cm-14-OC-14LV-permissive-2016-02-13.zip runs at 1.4GHz with custom governors. I have not tried out the new kernel joojoobee666 made available a few moments later (cm-13-OC-14-LV-PM-2016-02-13.zip).
[Motorola Droid 4] joojoobee666:
Yeah, something may have gone wrong when I compiled. Definitely the wrong thread here but I pulled them for now.:silly:
[Motorola Droid 4] martin9959:
proximity sensor vs voip calling

Has anyone experienced problems with voip calling in CM13? Whenever the proximity sensor switches the screen off, audio in both ways stops immediately. This happens only for voip calls (I have tried built-in sip, csipsimple and whatsapp calling), not for normal mobile phone calls. I have this since I upgraded to CM13 (and still in the today's nightly), but I did not have it under CM12.1. The proximity sensor itself is working as expected (and was working in CM12.1, too).

Any insights are highly appreciated :)

EDIT: Fixed (at least) as of nightly of 10 April
[Motorola Droid 4] walter7901:
If you have wifi problems like wifi did not reconnect to AP. Use this settings for /system/etc/wifi/wpa_suplicant.conf :

update_config=1

ctrl_interface=wlan0

eapol_version=1

ap_scan=1

fast_reauth=1

Works for me. Settings are from cm11

Gesendet von meinem XT894 mit Tapatalk
[Motorola Droid 4] martin9959:
Just to clarify: It is not a wifi problem - wifi stays connected and can be pinged, I have "Keep WiFi on during sleep" set to "always".
[Motorola Droid 4] daniel_m:
Oh wow, Marshmallow is a nightmare when it comes to storage. :mad:

1) Link2SD is broken since it either cannot access /data/sdext2 or the second partition of the SD-card. Logcat doesn't give away anything useful and permissive SELinux doesn't help either.

2) I managed to format the "internal SD-card" to ext4 and use it as internal storage. Our 3 GB data partition is still messing things up. Apparently, Android uses temporary files when "moving" apps and I have a feeling these are located on /data. When there is too little space on /data, moving an app fails, even though there is plenty of space on sdcard0.

3) Many apps apparently do not have write access to the external SD-card.

Wonderful! :crying:

Btw., where is the container for /mnt/asec located? It should be on sdcard0, but I cannot find anything (root explorer and "show hidden files" activated).

Edit: The second partition of the external SD-card can be mounted to /data/sdext2 after it was "ejected". I still have to find out if Link2SD can link apps to this partition. Creation of the mount script still doesn't work. Probably a permission issue. I will try to find out how to prevent Android from mounting the second SD-card partition during boot ... or unmount it and re-mount it to /data/sdext2 with an init.d script.

Gotta love Marshmallow. Very excitement, many fun, such possibility! :D