Post Reply

[R&D] System Dump, FSTAB, ADB, FASTBOOT, HARDWARE and Screenshots

OP Childofthehorn

1st July 2014, 10:32 PM   |  #1  
Childofthehorn's Avatar
OP Recognized Developer
Flag DFW, Texaaas
Thanks Meter: 164
 
252 posts
Join Date:Joined: Jun 2010
Donate to Me
More
FSTAB:
http://pastebin.com/LN75y6Jj

Build.Prop:
http://pastebin.com/ehgwGL8A

System Dump:
http://www.mediafire.com/download/ux...YSTEM_DUMP.zip
*Copyright owned by Samsung and Google

Getprop
http://pastebin.com/2mhPZhLV

Hardware Info
https://www.youtube.com/watch?v=NNtBzOiXLPw

SPRAT ADB
ENABLE ADB
- Tap on top right of watchface
- scroll down to Settings
- Scroll down and tap About
- Tap Build Number 5x's
- Go back to settings and Development Options should be available
- Enable ADB debugging
- Plug in the charger dock with a USB connected to the computer
- Authorize on your Phone for USB


SPRAT RECOVERY
RECOVERY MODE


SPRAT FASTBOOT
FASTBOOT/BOOTLOADER Mode
Last edited by Childofthehorn; 2nd July 2014 at 11:38 PM.
The Following 9 Users Say Thank You to Childofthehorn For This Useful Post: [ View ]
3rd July 2014, 05:22 PM   |  #2  
Childofthehorn's Avatar
OP Recognized Developer
Flag DFW, Texaaas
Thanks Meter: 164
 
252 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Codename: SPRAT

Product: Gear Live

Key Specs:

- Qualcomm 400 chipset (Quadcore msm8226 - Same exact one as Moto G!)
- Adreno 305
- OpenGL 3.0 support
- 320x320 screen (hdpi)

Sensors / Parts:
- Invensence MPU6515 MEMs Gryo HERE
- AK8963c 3 Axis Compass and Hall effect sensor HERE (TOGETHER 1 +2 = InvenSense MP92M 9-axis Gyro + Accelerometer + Compass)
- Heart Rate Detector ( didn't see what the chipspec was).
- Samsung Driver abstracted "sensors" (just conglomerates info from the existing sensors).
- MAX77836—MUIC
- STMicroelectronics STM32F401 Cortex M4 microcontroller
- Qualcom PM8226 power management IC
- InvenSense ICS-43430 microphone
- Cypress Semiconductor CYTMA54 touchscreen controller


* holding for space *
Last edited by Childofthehorn; 8th July 2014 at 07:42 PM.
3rd July 2014, 10:21 PM   |  #3  
GigilinE's Avatar
Senior Member
Flag Napoli
Thanks Meter: 1,462
 
576 posts
Join Date:Joined: Apr 2010
More
Quote:
Originally Posted by Childofthehorn

.......

Sorry but app and priv-app and framework is complete or is not?
5th July 2014, 10:21 PM   |  #4  
Childofthehorn's Avatar
OP Recognized Developer
Flag DFW, Texaaas
Thanks Meter: 164
 
252 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by RevengeDevTeam

Sorry but app and priv-app and framework is complete or is not?

Its what I could get by doing a pull of /system. It should be complete.

Remember that the WEAR is a build type in Android.I don't quite get why they built so many of the components for Cellular into it though... probably just easier to have it be complete binaries.
19th July 2014, 10:01 PM   |  #5  
Fastboot commands extracted from aboot:
Code:
continue
reboot
reboot-bootloader
preflash
flash
boot
oem lock
oem enable-console
oem disable-console
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge 0
oem off-mode charge 1
default settings:
Code:
adamoutler@adamoutler-desktop:~/Downloads$ sudo fastboot oem device-info
...
(bootloader) 	Device tampered: false
(bootloader) 	Device unlocked: false
(bootloader) 	Charger screen enabled: true
(bootloader) 	Display panel: �������������������������������������������
You'll want disable-console, enable-charger-screen, and off-mode-charge 1 in order to get stock functionality with best battery life. For debugging, you can switch these options.

UART boot log: http://pastebin.com/M5ctEFtT

It was said that the Gear Live should only be running one processor. You can see in the UART log that there are 4 processors active. Here is /proc/cpuinfo which confirms this.
Code:
shell@sprat:/proc $ cat cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 38.40
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 3

processor	: 1
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 38.40
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 3

processor	: 2
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 38.40
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 3

processor	: 3
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 38.40
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 3

Hardware	: Qualcomm MSM 8226 (Flattened Device Tree)
Revision	: 0004
Serial		: 0000000000000000
The Following User Says Thank You to AdamOutler For This Useful Post: [ View ]
19th July 2014, 10:21 PM   |  #6  
Recommendations for developers to increase battery life:
1. Remove useless drivers such as:
Code:
  SCSI subsystem initialized
Code:
 SCSI Media Changer driver v0.25
Code:
 sdhci: Secure Digital Host Controller Interface driver
and many others
2. Disable unused processors, or offer a "power saving" mode to disable those additional processors
3. examine processor scaling
4. reduce use of SELinux. it's worthless.
4a. when device is near phone, phone security is off
4b. turning on ADB and accessing storage is easy as security is disabled on the phone
4c. because of the above reasons the device causes the phone to be insecure
4d. the device is wasting battery on its own security while reducing the security of the phone.

5. enable thermal max frequency
Code:
[    4.700499] msm_thermal:disable_msm_thermal Max frequency reset for CPU1
[    4.700509] msm_thermal:disable_msm_thermal Max frequency reset for CPU2
[    4.700517] msm_thermal:disable_msm_thermal Max frequency reset for CPU3
6. above all: audit your logs.
The Following 2 Users Say Thank You to AdamOutler For This Useful Post: [ View ]
20th July 2014, 06:06 PM   |  #8  
Member
Flag Milwaukee
Thanks Meter: 1
 
42 posts
Join Date:Joined: Apr 2013
Anyone having this issue? Trying to unlock my Samsung Gear Live. ADB recognized device, Enabled communication through my phone, watch boots just fine using "ADB reboot bootloader" however, when entering "fastboot oem unlock" I get "waiting for device"?

Yes my watch is plugged in to my computer. I have tried several different ports. Any help?
I couldn't find the answer to this using the search function.

Thanks guys

*Edit*

I figured out the issue. If anyone is having this problem visit here:
http://stackoverflow.com/questions/2...-or-lg-g-watch
Follow the directions accpet one thing. Toward the bottom you will see a post telling you to install a "Samsung Device" instead of a generic "Android Device" Make sure you install the "Samsung device" if using a Gear Live.
Last edited by 20mmrain; 20th July 2014 at 06:59 PM.
21st July 2014, 02:38 AM   |  #10  
This device charges VERY slowly, and on top of that, it's also picky about the charging port. In order to be sure you're always charging, you'll want to use a USB condom. This is important because many aftermarket chargers are unlabeled.



Here you can see it won't charge at all on an "Apple" charger


And it charges well on an "Android" charger with D+ and D- tied together.




The good news is that the charging rate is generally controlled by software, so if samsung would release kernel code, we could likely fix this.
Last edited by AdamOutler; 21st July 2014 at 02:41 AM.

The Following 2 Users Say Thank You to AdamOutler For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
android wear, gear, gear live, watch
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Gear Live Android Development by ThreadRank