yashsingh1/xdaforums huggingface dataset:
[Pixel C General] dkryder:
there have been a couple stories written mid last year that google wanted to phase out chromeOS and someway merge it with android, then late last year stories that no, that is really not the case google is gonna continue to develop both OS's. assuming that the merge thing was really going on inside google maybe that had something to do with the pixel c mess. about the write protect screw, one thing i had been thinking about is to figure out how to build a small trap door of sorts in the back cover at the point of the screw while at the same time clearing the adhesive to make the remove/replace easier. then, do an exchange plus maybe $100 [to cover mod/shipping]. but before i even attempt to do one device as a prototype i need to see the ifixit or similar teardown to get an idea, after seeing the affected insides, if something like that is even doable. but in theory someone would send in their stock unit and get back the mod device which would have quick easy access to the wp screw, assuming at this point it is something that can be done.
[Pixel C General] Rox598:
Aka the tablet doesn't know what it should be?

The rush to change it to Android could also show us why it's such a buggy mess. they already said they were gonna launch it at Xmas so I wouldn't be surprised to hear that ti didn't get a proper QA acessment and was just pushed out when they got Android "stable" enough.

The fact it's taken this long for even a statement from Google about the issues is ridiculous and why is it taking so long to fix?
[Pixel C General] cheep5k8:
I've actually helped a volunteer at Google to debug the WiFi issue, since they knew of me and knew my device is rooted, so I was able to perform diagnostic tests from the side of the device.

It seems to be very difficult to fix simply because it was, so far, not clear what exactly the reason for the WiFi issues is. It doesn't really seem like (only) a hardware issue with lost reception. The WiFi interface also massively drops packets/needs data retransmits, something is going wrong but it's not clear if that happens at the hardware level, the firmware level, or the kernel level.

I also tried to diagnose and possibly fix the WiFi issue myself; so far, no luck.
[Pixel C General] Rox598:
The WiFi issue is a strange one but I'm on my 2nd pixel and never had an issue with either of them for the WiFi and get max speed 2 floors away :S granted I'm using 5Ghz so not sure if that why. The only major issue is with the touchscreen (and sometimes lag) did you have a look at these at all?

With that WiFi issue people have do you reckon that is what's holding the update back so long? They seem certain the software is what's causing the screen to not respond.
[Pixel C General] cheep5k8:
I think that it is very difficult to fix, yes.

As for the touchscreen, my Xceed kernel has some patches for the touchscreen included from the chromiumos git which were not yet released as an OTA (I think), so maybe that would be worth a try.
[Pixel C General] Rox598:
I would give your kernel a go but I don't really want to mess around with the pixel C too much

As a whole i've kinda slowed down with doing anything to my Android stuff now.

I don't think those fixes have been sent out in the OTA but perhaps they were in the other factory image? I think chainfire said he flashed it and his touchscreen problems have yet to come back.
[Pixel C General] cheep5k8:
Possible. IIRC they were only recently commited, but somehow still might be in the new factory image.
[Pixel C General] Rox598:
well if the new update isn't released soon I may just suck it up and start trying out things to help.

Thinking about it since fixes were pushed to the Chromoniumgit is this tablet always gonna contain stuff from ChromeOS?
[Pixel C General] cheep5k8:
It can't not be a ChromeOS device. The entire board, basic hardware and firmware setup is built like a Chromebook. It has the Chrome EC, it starts up (boots) like a Chromebook, etc. This can't be realistically changed.

The "only" things really different from a Chromebook are:

- It is a touch-only device (there's the Chromebook Flip but it at least also has a keyboard)

- The storage partition layout has been partially changed so that Android can deal with it

and

- Instead of, at the very end of the boot sequence, booting ChromeOS, it boots Android. But actually, this is the least spectacular and least intricate part about the Pixel C's nature (even though of course a complex matter from a pure Android point of view). Both ChromeOS and Android use a Linux kernel. I'm not even entirely sure whether the Pixel C kernel contains any greater Android-specific adaptations that make it different from a ChromeOS kernel, aside from having a slightly different build configuration. When the Android kernel finally boots (from inside a ChromeOS boot image, may I remind you), it just expects to find a specific partition layout, which is there, and not the biggest problem to arrange. And after that, it just needs the right drivers, and it runs.

So, yes, the Pixel C is very much a ChromeOS device.. a Chromebook without keyboard, if you will, even if there are some people adamantly claiming the opposite. It just happens to run Android.
[Pixel C General] atg284:
Thank you for this post, information, and your efforts! It really sounds like this is a Frankenstein device. I returned mine because I didn't have confidence the google devs would be able to fix the poor wifi (especially wireless N) any time soon as they were requesting debugging reports from users here:

https://productforums.google.com/fo...ce=footer#!msg/nexus/CM9tv3pjTfQ/QY0xGoTMAgAJ

There were simply too many problems. I had wifi and touchscreen issues on both units I tried. Again, thanks for the info and effort. I keep reading about this device with hope it all gets fixed but that seems like it might be a while. :(
[Pixel C General] Rox598:
Yep I totally understand now. Man what a Frankenstein tablet :eek: but as long as they fix the issues with touch and some lagging here and there I'll be totally happy with it (as long as multi window is in N)

But since its a ChromeOS device could say Google release a flashable Chrome OS for it that would work? For people who have the keyboard anyway. Not saying they would but I'd much prefer Chrome OS tbh
[Pixel C General] cheep5k8:
Yes, they theoretically could very much do so.
[Pixel C General] brando56894:
Wow I knew this thing was a pain in the ass for you to dev on since I've been following your root/kernel work but I didn't know that it had an EC with it's own processor and OS, that's crazy! I was thinking what you and the other poster said above, and I'm sure in due time someone will compile ChromeOS to run on this baby.

That's exactly what I'm thinking, there are a lot of things that point to it (Sundar moving from the ChromeOS team to Android, stories stating that it will happen sometime in the near future, the gigantic Chrome Android statue at the GooglePlex). They initially developed this either as a pure ChromeOS device or it was supposed to be (and most likely will be) the first device to run the merger of the two. I'm thinking something like tablet mode running the Android UI when it's not docked and when it is, it uses the ChromeOS UI, or maybe something far similar which is already possible in some forms on ChromeOS: it was meant to be a ChromeOS device that ran Android apps but the UX sucked since ChromeOS isn't meant for touchscreen use so they scrapped it and went with Android until all the kinks could be worked out. I'm going to assume the next major Android release for the Pixel C will tell us why the device was built this way, considering that the Reddit AMA about the Pixel barely mentioned anything other than "Wait for the next Android release! We have a lot of interesting things coming!". They clearly want us to mess with it since they provided us with factory images and an unlockable bootloader so we're probably the Guinea Pigs that will find all the issues so that Google can focus on fixing it and merging the two codebases together. I/O 2016 is only a few months away! :D
[Pixel C General] feng2345:
I also met some problem when worked with pixel c. I want to disassemble the boot.img as a android boot.img, but failed. When I looked into it with hexedit, I found it is a CHROMEOS image!!! A android kernel was in it, but not as a android image format. I think, I need to read the chromeos image format first in order to extract it, do you also does it in the same way?
[Pixel C General] cheep5k8:
Yep. Actually the image is based on the arm64 FIT boot image format. It's really a bit complicated, but if you have any more questions just ask.
[Pixel C General] feng2345:
Thank you for your reply.

I have extracted kallsyms and disassembler from boot.img of pixel c. Very intresting.
[Pixel C General] feng2345:
I have another question, where can I get the official source code of pixel c? The code in website github.com/md5555/android_kernel_google_dragon/ seems very different from NVIDIA l4t release(developer.nvidia.com/embedded/linux-tegra-archive). Which one is used by google pixel c team?

Thanks
[Pixel C General] cheep5k8:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18
[Pixel C General] feng2345:
Great!

Thank you very much.
[Pixel C General] CrazyPeter:
ChromeOS devices are selling really well, particularly in the education sector, they vastly outsell iPads. Android is by far the dominant tablet and mobile OS. Any merge could mess up either or both winning formulas.

I think the pixel C story will become clear eventually, the the hardware was ready long before the software was. I think we are going to see Android become a much better desktop laptop OS and it does smart stuff when the keyboard is attached, the OS window manager makes it behave like A laptop, when it's undocked from the keyboard, Android behaves like a tablet again.

Right now, using the keyboard feels awkward, as occasionally you have to use the touchscreen too...
[Pixel C General] feng2345:
Hi,

I got a 0day on pixel c. I want to exploit it. But it is difficult to debug, so I want to add some debug info in the kernel. The problem is when I repacked the boot.img, the kernel can't boot up. Is there some instructions to build the kernel and repack it in a right way?

Thank you.
[Pixel C General] unfnknblvbl:
OP, I'm curious; have you managed to turn off the write protect for yourself, and if so, how did you work out that it was the front camera?
[Pixel C General] brando56894:
No he didn't, I believe one of the Google devs told him when we was trying to figure out systemless root.
[Pixel C General] Alxoom33:
Lovely rant! Enjoyed your detailed perspective on The PixelC. I didn't appreciate all of the problems Developers are having with this device. Looking forward to flashing EXeed 8.03 kernel.
[Pixel C General] Nex5x:
** Update edit: I got my pixel c to boot but still have not fixed the backlight and touchscreen is not working. I know the EC controls the backlight, at least a chromium os dev page said it does in devices generally. Tried flasing Marshmallow to go back to the original android version, not fixed and only booting to recovery. Will try 8.1.0 again and sideload root, hoping maybe there is some chance twrp will be more effective in doing a clean install. Not sure what else to do. Wish I could flash the EC with a USB SuzyQable debug cable.

OP or if there happens to be anyone else.... I read much of the Chromium OS Dev group pages and everything here. I really don't like this convoluted EC ChromeOS boot and peripheral management. My screen backlight stopped working and after flashing stock 8.1.0 and 7.1.2, I actually opened up my Pixel C to reseat the flex cables. It won't even turn on as temporaeily disconnecting the battery did something to where the EC doesnt complete it's boot or possibly verifications. It just pulses the rainbow bar twice before abruptly shutting of the light. I tried the battery reset method Google cites for charging issues (disconnect cable while holding power + volume up and down then releasing and waiting 30 sec before charging it for 5 min).

I am thinking that the problem with the EC/ AP (android) combination is the EC and android get out of sync somehow on the rewritable portion of the EC. The EC controls the backlight and probably the Synaptics capacitive touch controller. For now I just need it to boot again. If I touch the metal case quickly during the two rainbow pulses it shows my battery status correctly. The development powerpoints say there is a Battery Cutoff/Shipping state but doesn't mention how to boot normally after the battery being briefly disconnected. Unfortunately it seems their custom servo debug board is needed to diagnose and flash the EC firmware, which would not be standard.
[Pixel C General] therevan:
[MENTION=4867279]cheep5k8[/MENTION] Long story short, I managed to remove the front-facing camera ribbon inside my Pixel C, and re-attach the screen, with everything working.

Long shot, but now that I've done this, would it be ... fun? ... to try and built/install ChromeOS on this device? If not fun, possible? :)

Wanted to offer myself up as a test case, if you wanted to see if it was possible to wipe out the storage and load something neat on.
[Pixel C General] Alxoom33:
About 6 months or so ago, I looked into this question and contacted several Chrome OS developers about potentially porting Chrome OS to the Pixel C. The response was not positive. Apparently, if it was doable, it was extremely difficult and would involve significant reprogramming.
[Pixel C General] KaedeNashi:
I want to know，If i want to change the hardware information，I must to change the EC firmware？Because i changed the DRAM from 3GB to 8GB.Reboot the pad after my changed the DRAM，it only display 3GB，Whether it's settings or ADB command extraction

I reflash the ROMs，it have nothing change。
[OnePlus X Q&A, Help & Troubleshooting] Vennesch:
Anyone has this problem?

It's quite a process to unflash, back-up, reflash everything + it is quite anoying for a person to test it on. Can anyone tell me what could be wrong?

My settings:

I am on latest stock Oxygen 2.2 (happened before upgrade as well)

BlueSpark Kernel 79 (happened on stock as well)

Xposed: Gravitybox, Greenify, Youtubemods

WalkmanMod
[OnePlus X Q&A, Help & Troubleshooting] Vennesch:
Problem still persists, stock same result, no one with this problem?
[OnePlus X Q&A, Help & Troubleshooting] Xeon3D:
Also happens to me sometimes. I found that lowering the volume helps. At least people stop complaining.
[OnePlus X Q&A, Help & Troubleshooting] Gorg2331:
This solved it for me: http://xdaforums.com/oneplus-x/general/fix-echo-fix-v1-0b-2016-01-19-t3296693/page2#post65950353

---------- Post added at 09:25 PM ---------- Previous post was at 09:21 PM ----------

It seems like the mic records the sound coming from the speaker of the phone. Echo cancellation should cut this off, but it seems like its not working properly. If you mute your phone the problem disappear, which should back up my theory.
[Android Q&A, Help & Troubleshooting] Kalyan:
Hi All, I was wondering if it is possible to link 2 devices such that they serve as e-leashes to each other.

It will be similar to an anti theft BT device that tags to cellular phones and tablets, which beeps to let one know when they move away from their devices.

Considering most people own at least 2 devices which have BT, is there an app that will tag 2 phones or a tab using and a phone using BT so each works as leash for the other?

I am sure it will be mighty useful and work better than a BT tag which people use to prevent losing stuff.

Thanks

Kalyan
[Galaxy Note II Q&A, Help & Troubleshooting] sumeetbais:
Hello all,

since last 2 weeks, every time my phone switches off and when I turn it on, it gets stuck at the Sam. galaxy note 2 logo forever. I've tried restarting, removing battery but it doesnt helps. It all started when I was on a call and my phone just switched off.

Since then I've flashed my phone 6 times with different roms (Initially i thought boot sware got corrupt) like RR (lollipop and Marsh), nightly but issue still persists. I've also noticed that hardware key (menu and back key) have stopped working completely from last 3 days. If i continue to keep my phone on throughout it works alright untill it switches off again. Because of this, I have to flash my phone and go through installation of all apps which is tedious and irritating.

I'm not able to figure out what the problem is. Please help me understand the issue and suggest an appropriate solution.

Awaiting response. Thanks in advance :)

Best regards,

Sumeet Bais
[Galaxy Note 4 Q&A, Help & Troubleshooting] volkantipi:
Hi, how to install stock email? I can set up your email application. But I can not install the Exchange services.
[Shield Tablet Accessories] ibriysraylite:
[MENTION=4132130]ibriysraylite[/MENTION]

Moderator Edit:

7. Do not spam, sell or trade on the forums.

If you wish to advertise a product, simply contact us. We can provide ads but you are not permitted to just post it in the forums. If you do, it will be removed and you're likely to receive a ban.

On the 30th Nov 2012 the Marketplace closed. The buying, selling, trading and / or exchanging of any item is now prohibited on XDA, in any forum or via Private Messages. We now use www.swappa.com
[BlackBerry Priv] kkkok8051:
Look premium n handy.
[BlackBerry Priv] taiber2000:
i have the skinomi full body protraction fro the realy 4g. it's great but after a while it deteriating. i'm gonna try a glass protection, if it failed i will buy the skinomi again.
[8125, K-JAM, P4300, MDA Vario General] rusar:
i did a hardreset on my tmobile mda and i lost my win startbar please anyone ith a solution

is there anywhere i can get wm5 software to load it agan if its possiible

PLEASE HEEELP!!!!
[8125, K-JAM, P4300, MDA Vario General] dharvey4651:
A solution waits for you in your PM. :cool:
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Soncomander:
Hello, everyone! This is more a bug report to [MENTION=4881398]PolishVodka[/MENTION], I'm a newbie and can't reply on his thread.

Recently I flashed [5.1.1] Resurrection Remix, using NFC configuration. Now he can't recognize my SIM -- is a Brazilian SIM (TIM).

I found the solution, just reflash without NFC configurations, even my phone have compatibility with NFC.

Previous ROM = CyanogenMod 12.1

Please, post any information about NFC and I9070P or a workaround to enable it.

:D
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] PolishVodka:
Unpack archive (or do this pushing directly files), go to /janicep/system/lib and delete "tee" folder. Now copy "tee" folder from /system/lib to /janicep/system/lib. Repack and flash Rom again with NFC configuration.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] Soncomander:
It worked!! :D

Thanks!
[Verizon HTC One (M8)] GMCPCS:
Hi all,

I'm stuck on this screen after trying to do a factory reset:

[IMG="HTC Sense Home Update"]http://xdaforums.com/attachment.php?attachmentid=3622925&stc=1&d=1453818414[/IMG]

I rooted to S off, and have been using TWRP to flash; the previous ROM was NuSenseven's. I decided to switch to a Venom, which was a premature idea, since Verizon hasn't gone to Marshmallow yet. So I flashed a 4.6.1 ROM, and that started issues. (Going from Marshmallow ROM to a Lollipop ROM?) BTW, I have a trouble ticket on Venom's page also.

I did a factory reset, to see if I could get back, and this is what I am stuck on. I can browse the device on a PC, but I no longer have ADK access, since I am at work.

TWRP can't seem to find the previous backup, although I can see it. (The SD Card was formatted during the factory reset) I don't know enough to be useful, just enough to be dangerous. I would like to revert back to the NuSenseven, or anything to get past this white screen. My next try will be to access an ADK computer, so I can install the updated firmware, if I can't get TWRP to find the backup file.

Thanks for any and all help,

gmcpcs
[Verizon HTC One (M8)] GMCPCS:
I was able to recover, I did a factory reset in TWRP rather than using the wipe/ factory reset in bootloader. I have my phone back now.

Now if I can figure out this SD card issue.

Take it easy,

gmcpcs
[Verizon HTC One (M8)] bigblueshock:
Hey,

Yeah usually flashing a different OS version on top of each other is a no no. Especially going downwards is shooting a bullet through your phones OS.

Best practice: Wipe/factory reset, wipe cache/dalvik, wipe system, then flash the new ROM you want. (after you back up everything of course, and TWRP backup too if you're unsure)

In terms of SD card, you can try easeus mobisaver for android. Its a free program to attempt to recovery deleted files off an SD card. You may get some.. Results aren't guaranteed, but I've had some luck in the past. I believe the free version lets you recover one file at a time. Can try that and see where it gets you.
[Verizon HTC One (M8)] GMCPCS:
Here's a further update on the HTC One M8 and my specific issue. I suggest googling "Android Marshmallow and adoptable storage". In my process of flashing different ROMs, one time I formatted my external SD card as "internal storage". (More is better, right?) Unfortunately this creates issues for those who are rooted and flashing ROMs using TWRP. This may have created a "bootloop" issue? But this article's method to fix bootloop issues is what I ended up doing:

http://wccftech.com/fix-sd-card-as-internal-memory-on-android-6-issues/

From what I have read, it is much better to just format your external SD card, (HTC M8's are still devices that have those) as "removable storage" rather than as "internal storage". Sometimes it's hard to find a solution to your problem, if you don't know what you don't know:)

Here's a few posts and articles: (The more you read, the more you know)

http://xdaforums.com/crossdevice-dev/android-one-general/guide-struggling-adopt-sd-internal-t3219284

http://xdaforums.com/lg-g3/general/marshmallow-careful-adoptable-storage-t3287375

http://xdaforums.com/moto-x-style/h...le-storage-t3267294/post64587489#post64587489

https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/

http://www.androidcentral.com/inside-marshmallow-adoptable-storage

http://wccftech.com/fix-sd-card-as-internal-memory-on-android-6-issues/

Take it easy,

gmcpcs
[Verizon HTC One (M8)] migiwara:
Hi i also have the same issue with my HTC one M8. My phone has never been rooted but i got this problem after trying to factory reset because i had some network issues. i can use the drop-down notification tray to get into the setting but i cant access anything else. I am a noob so please help me i need my phone back.
[Verizon HTC One (M8)] dottat:
Ruu will be your fix. Find the matching s-on ruu for your phone in the stickied post in the general section.
[X Play Q&A, Help & Troubleshooting] dreinulldrei:
Hi there,

I noticed there's an app with the name of SoundRecorder.apk in the apps directory, however, Android does not show any app in launcher that could record audio. So I am wondering... where is it, the Sound Recorder?

Thanks!
[X Play Q&A, Help & Troubleshooting] K.khiladi:
Maybe for FM radio recording.
[X Play Q&A, Help & Troubleshooting] Smokey Mc Pot:
That is the Android default key app for voice dictating... you can download the sound recorder shortcut from the play store to gain direct access to the app...

Example:

https://play.google.com/store/apps/details?id=com.thinkleft.soundrecorder
[X Play Q&A, Help & Troubleshooting] dreinulldrei:
Thanks... Just to clarify... The app you linked... Is it a shortcut or another install of the app?

Thanks!
[X Play Q&A, Help & Troubleshooting] Smokey Mc Pot:
Actually that link is for the ported app.

You can find Shortcut apps on the play store like this one:

https://play.google.com/store/apps/details?id=com.kayan.nurav.soundrecorder

Or you can look in here on xda for the same unbranded shortcut.