[Q] Android Wear SmartWatch Hardware DIY topic

Hello everyone, i want to ask something about Android Wear OS and Hardware Specs which is related my Bachelor of Science Thesis subject. First of all, I searched the forum; there were no answers about my question, I also searched developer.android.com/wear and there were no extra information, it contains information about well-known smart watch developers' products such as sony, samsung, lg, etc...

so, my intention is building both software and hardware parts of a special version of android wear device. that means, i need to etch special pcbs, solder chips onto that pcbs, mount capacitive touchscreen, build metal body (cnc cutted) on hardware side

then i must reconfigure, rebuild and fine-tune the stock android wear rom for my specially built hardware, for example my design includes 9-DOF IMU sensor, then i must write its driver (*.so) for my hw, and so on...

And the question is, i want to know if there is any documentation or technical datasheets, example pcb designs, hardware compatiblity lists, reference diy projects, etc?

thanks guys
-fatalblade.

Possible hardware failure? Unable to boot - claims no OS and won't mount data etc topic

I think my phone may have had a catastrophic hardware failure but I am hoping not and maybe some of you clever people can help me resurrect it.

I have been running KK ParanoidAndroid without any problems for a few months. Yesterday I tried to boot it up and after showing the Google screen the screen went black then a single horizontal white line appeared 3/4 way down the screen. It stalled there forever so I pulled the battery and booted into TWRP recovery. It seemed to take a lot longer than normal but did boot into TWRP OK.

Once there however TWRP reported no backups, no OS and no storage space (0 MB). I couldn't mount any partitions,. I tried factory reset but it appeared to fail and just made the phone vibrate for a while. The log shows:

Unable to mount - /system, /cache, /data etc and something about no valid partition for MTP

Then the screen greyed out, faded to black and the phone powered off. Now it seems pretty much non responsive.

Any thoughts, other than bin it and get a new phone?

[Q] Hardware home button does not work on first press (for screen shut down) topic

I am currently running the CM12 nightlies, stock kernel. I don't know for sure when this started but it has been this way for a few months.
I have long press home (hardware button) set to turn off the screen. It only works however, after I have tapped it once since it woke the last time.

Most of the other long press actions seem to work ok with the home button.

I read about some issue with the home button and how it was waiting for a double tap, so the single tap didn't seem to work, but that does not seem to be the issue, as the fix for that (turning off the double tap function) does not fix my issue.

I have only read of two other people with this same issue, but no solutions.

Is battery drain possible due to hardware damage? topic

So over the course of time I have used many different ROMs and also have had 5 batteries for my Note so far.

All ROMs gave me terrible battery life, except the stock android for around the first year, eventually it started giving me terrible battery life too.

So that got me wondering, is it possible that some kind of faulty hardware on my Note's motherboard is causing those battery drains?

GPS hardware failure...I think? topic

The aGPS works well enough that I haven't spent a lot of time troubleshooting, but sometimes I do need a full on GPS, and it flat out doesn't work.
I followed all the instructions for GPS Status & Toolkit, accidentally left it for a couple hours outside (fortunately it stayed nice), and it never found a single satellite.

I then installed Faster GPS, and tinkered with the gps.conf settings a bit, and it made no difference.
One thing notable is the GPS_DEBUG was set to 1 = "Error"...not sure if that is related, but even after changing that variable and confirming it stayed after a reboot, no improvement.

I also took it apart and the blue antenna appears to still be intact and properly seated, so I don't think that's a factor. Didn't see any burnt chips though, either.

Any ideas?

screen driver issues, or hardware? topic

i'm going to try a diff rom, but i'm running the nightly 21'st CM12 rom this started happening after i upgraded.


its a pain to get on to some items on the screen this way. here is what the touch debug show's i have a whole LINE down the screen that is dead. -- see attached.

Attached Thumbnails

 

[Q] Disable Hardware Buttons [LP] topic

Is the any way to disable the hardware buttons in lollipop? :)
The "Generic.kl" method is no longer working. :(
Thank you! :D

issues after software repair. Can I do a hardware check? topic

Hello folks,

My mothership made a suicide attempt (sudden bootloop) and showed some strange behaviour recently. It was solved sort of with a reset, but since the problem could not be replicated I figured it must have been a software fault after one of the many little updates Sony has pushed out recently gearing up for the Lollipop.
So I decided to do a software repair. So far so good, but for some strange reason I am stuck on an older version of What's New. Could this possibly be a server issue with Android 5.0 on the way?

Also, is there a good way to check for hardware problems? I am going to run some benchmarks but any input would be appreciated.
(I am on stock, unrooted btw)

[Q] Front camera. Hardware component not working = CM10/CM11 Call UI crashes topic

Hello,

I’ll start with telling you that my front camera is broken (hardware problem). Since I almost never use it, I don’t miss it and I don’t want to go have it fixed yet if I don’t need to.

Due to what seems a very strange implementation of the stock camera app, it doesn’t work at all (I’m getting a force-close on launch with error message „Unfortunately, Gallery has stopped”). Gallery itself works. My suspicion is that when I launch the Camera app, it tries to get both cameras’ properties „in advance”, regardless of the fact that I only want to use the rear one (which is the default on app startup!) and it fails, because it’s broken.

Some other apps, like OpenCamera, only try to fetch the front camera’s data when I actually try to switch to it and therefore work nicely when using the rear camera (what’s more, the OpenCamera doesn’t CRASH, it handles the error gracefully by just displaying a nice message that the front camera might be in use by another app).

So, I didn’t bother at first. But then I’ve decided to become ninja and installed Cyanogen10 (10.2.1 maguro, stable version, then cm-11-20150209 nightly) and it turned out that… the call ui is not working!!! I attached to adb and saw at logcat the following stack trace:

02-13 14:25:21.061 2209-2233/com.android.camera2 E/AndroidRuntime﹕ FATAL EXCEPTION: Thread-200
Process: com.android.camera2, PID: 2209
java.lang.RuntimeException: Fail to get camera info
at android.hardware.Camera._getCameraInfo(Native Method)
at android.hardware.Camera.getCameraInfo(Camera.java: 221)
at com.android.camera.CameraHolder.<init>(CameraHolde r.java:169)
at com.android.camera.CameraHolder.instance(CameraHol der.java:123)
at com.android.camera.util.CameraUtil.openCamera(Came raUtil.java:468)
at com.android.camera.PhotoModule.openCamera(PhotoMod ule.java:1869)
at com.android.camera.PhotoModule.access0(PhotoMod ule.java:96)
at com.android.camera.PhotoModule$OpenCameraThread.ru n(PhotoModule.java:234)

Even though I never ever use video calls, the call ui seems to need the camera info no matter what (I’ve tried to find something in the settings, but haven’t noticed anything related to disabling video calls). The effect: the logic is working (the call is initiated), but I do not have any UI to handle it, only force closes over and over again. The same with incoming calls - logic working, ringing, but no ui.

The camera bug was acceptable, but this is not. So, now, let’s think of possible solutions:

1) revert to stock Android (I don’t want to do that!)
2) get the sources of Cyanogen, change the system call app behaviour for my needs, build my own ROM and flash it (not really a good solution, since I would have to repeat the same fix with every update)
3) MAYBE there is a way to dig into system files and change some value that indicates whether front camera is available? MAYBE it’s possible without modifying some .so libs or other binaries or the kernel? Do you think it would help? (I would still have to do it after every update, but perhaps less problematic)
4) other ideas?

I’ve found only one similar topic, where the fix is hardware-related: http://forum.xda-developers.com/show....php?t=1745208

Anyway, I don't think that these errors (in stock camera and CM's call ui) HAVE to be there. Front-facing camera is not absolutely necessary for these apps, it's a feature, so why is its lacking practically disabling them? This should be implemented better. But that's my opinion.

Please help who can. I don’t have the necessary knowledge of Android system (yet :) ) to handle it all by myself.

hardware differences topic

Is there any hardware difference between Note 4 variants?

I broke my screen and bent the housing. On ebay, there is a replacement part for Sprint Note 4 (N910P) and the seller says that it will not work for other variants.

Can anyone confirm this?

Since the shield and the ouya and similar hardware, would it be possible to get the o topic

Sent from my Nexus 4 using XDA Free mobile app

Hardware or ROM SD card issue (4.4.4 NHA) topic

I'm in a bit of a pickle. I'm on rooted stock 4.4.4 and recently got a wild hair to go to lollipop. I have an 8 gig Patriot SD card. Not enough room to pull off a Nandroid, etc. I have a brand new 16 gig SanDisk laying around and a brand new 32 gig Samsung EVO card that I just got in. Neither will mount properly, or reliably. Android claims it's blank and will not mount/format it. I have to slide it in and out (don't get cute with that...) until the phone mounts it and then it's in a partial read/write state. However, if I put the old 8 gig card in, all is well. I do not have SD card encryption enabled. I have tried the SD Fix applications, they find nothing wrong. If I put the card into a laptop, everything is perfectly fine.

So I'm to the point where I may have to completely ODIN my phone just to see if it's a ROM problem. I cannot back-up because of the card issue. :crying:

Any bright ideas?

thank you much

Camera and Flash not detected (hardware issue?) topic

Well I have a unique issue I can't find much info on. This is not the 5.0 lollipop bug with the camera becoming inaccessible. I'm currently running 5.0.1 factory image rooted.

The problem: My camera and Flash are not usually detected when I boot the phone. Even if I reboot. I thought this was something with the rom so I reflashed 5.0.1 cleanly, but the problem persisted.

The only time they are detected and work is if I press on the area where the flash and camera are located and tap it with something heavy. The problem is that I don't think the flash and camera are really related. I've opened the phone and they in separate areas. Could it be a motherboard issue? Anyone know about hardware stuff like this?

Sent from my Nexus 5 using XDA Free mobile app