Related
We've sucessfully violated Samsung's Hardware-Based-Chain-Of-Trust once before by modifying the hardware , causing the device to boot from USB at which point we can upload an interceptor bootloader and then any unsigned code of choice.. This was done to resurrect dead devices and help promote development
It's time now to tackle the Galaxy S2(Exynos) platform. A lot of lessons were learned last time.. So we'll start this thing off by saying that it looks like they've removed UART functionality in this edition of Samsung processors. I can understand why... We were able to access a root prompt when the kernel loaded up to charge the battery, as well as clear the download counts, flash partitions and have other full access to the Serial Administration Console... So, it looks like there's no UART available.
I took the liberty of creating the Galaxy S2 Hack Pack which will help out. This contains the Public processor manual, the i9100 service manual and a ton of other helpful tools.
Contained within the Level 3 service manual was a processor pinout with each pin labeled. I yanked that out of the processor manual, put it into GIMP, flipped it, labeled it prepaired it. This contains all the pins and they're labeled.. but they're small, so I enlarged the ones we're concerned with.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's the i9100 board. I obtained this great image from ifixit.
Now, we can apply the overlay to the board and....
Now if we look to the left in the picture above we can see that there are 5 resistor switches. The right side is low and the left side is high. there are 3 high, 1 low and 1 disconnected.
The Development board for this processor shows only 5 switches though, 2 of the 7 signals we are concered with (xOM0 and xOM6) are hardwired and non-switchable. This leaves a promissing 5 switches.. However I don't know what to make of the one which is disconnected. Logically the shortest path would apply here and look something like this:
So, since xOM5 switched boot mode from OneNAND to UART>USB>OneNAND on the Hummingbird.. Considering xOM6 doesn't count on this device.. I'm thinking xOM5 could control boot mode on this device as well.
Any input? I have a i9100 here.
according to the documentation in the processor manual the xOM register may be read from 0x1000_0008, this is the OP_MODE register and it should contain a 8 bit binary word (2 hexidecimal digits) which displays the xOM value.
I've got many useful data already, but missing the most important one - complete Exynos manual. All I've got about CPU alone is 4,3MB document called "SEC_Exynos4210_pulbic_manual_Ver.0.00.01.pdf" it's incomplete.
Can you people look for newer version or any related documentation? It's very important to me to get such.
(Yes, I also have OrigenBoard schemas)
What may help in looking is that Exynos4210 marking is S5PV310/S5PC210 (don't mix up with Hummingbird which is S5PV210/S5PC110/S5PC111), sometimes it's also called as Exynos4 which is wrong name, because it's probably different CPU, but Samsung tends to mix up their own products so who knows.
The The xOM0 pin controls clocks. This pin is for sure irrelevant to changing boot order.
Here's some documentation relating to the boot
Code:
Owing to the recent increase in the prices of NOR flash memory and the moderately priced DRAM and NAND
flash, customers prefer to execute boot code on NAND flash and execute the main code on DRAM.
The boot code in Exynos4210 can be executed on external NAND flash. It will copy NAND flash data to DRAM. To
validate the NAND flash data, Exynos4210 comprises of hardware Error Correction Code (ECC). After the NAND
flash content is copied to DRAM, main program will be executed on DRAM. NAND flash controller uses
ACLK_133 clock, which is from clock controller (FSYS).
Analysis: ECC is used.. This may prevent changes to a live bootloader
Code:
Auto boot: The boot code is transferred to internal SRAM during reset. After the transfer, the boot code will be
executed on the SRAM.
Analysis: Code is executed in SRAM, this is different from DRAM in Hummingbird. It is possible that code may be injected somehow during reset... point of weakness to examine.
Code:
64 KB ROM for secure booting and 128 KB RAM for security function
Analysis: I do not like this Secure Ram thing.. We need more documentation to figure out how SRAM works.
Code:
The Watchdog Timer (WDT) in Exynos4210 is a timing device that resumes the controller operation after
malfunctioning due to noise and system errors. WDT can be used as a normal 16-bit interval timer to request
interrupt service. The WDT generates the reset signal.
Analysis: the Watchdog timer will initiate a reset if not reset. this timer must be reset every 65,536 units of measure. Apparently this is powered by the 100 MHz ACLK_100 signal. This could be a window of opportunity.. however it might be entirely too small if this is a 1:1 clock.
here is the Watchdog Timer calculation
Code:
1/(CLK/(Prescaler value + 1)/Division_factor)
where
CLK=100,00,000
prescaler value is 0 to 2^8-1. (0-255)
Division_Factor is 16, 32, 64, or 128.
So, the watchdog timer on this device can reset anywhere between .0003 seconds and .000000017 seconds... acording to my calculations.
Code:
Once the watchdog timer is enabled, the value of watchdog timer data (WTDAT) register cannot be automatically
reloaded into the timer counter (WTCNT). Therefore, an initial value must be written to the watchdog timer count
(WTCNT) register, before the watchdog timer starts.
Analysis: If we manage to get code booted onto the device, the watchdog must be kicked frequently during the boot sequence or disabled all together.
The watchdog timer may be disabled by setting 0x1006_0000 bit0 to a 0. this would render the watchdog useless as it will not reset the device.
We need manuals to find out the boot modes of this device. I will probe more this weekend, but we really need the finalized manuals.
just dropping in to say thank you guys for all your hard work. You guys rock the world!! I just ordered my Galaxy Tab 7.0 Plus HSPA+ with voice feature from Malaysia. This mod will be a huge help for development,etc.
This is a stock device
Code:
# viewmem 0x10000008 |hexdump
[INFO] Reading 4 bytes at 0x10000008...
0000000 2001 1011
0000004
The bits we are looking at is the "20". 20 makes out to b00100000..
Translated:
xOM0=0
xOM1=0
xOM2=0
xOM3=0
xOM4=0
xOM5=1
xOM6=0
Meaning these binary values must be inverted from HIGH to LOW... Or I am reading the wrong area of memory.
Rebellos, you mentioned that the device takes the OM register into memory at startup and it's likely not changed dynamically. Any insight here?
I thought I would begin locating UART. So... here's what I'm doing..
I set up the device to connect on startup to my wifi
I rooted the device
I purchased market app QuickSSHd and set it up to begin a root ssh connection
I removed the device from its case and taped the battery in place so that I could work with the board itself
Finally, I made this script which causes the device to echo "ttySAC0" to /dev/ttySAC0... same for SAC1 and SAC2. It also increments a counter so I know the device is still operational.
Code:
check=0;
mknod /dev/ttySAC0 c 204 64;
mknod /dev/ttySAC1 c 204 65;
mknod /dev/ttySAC2 c 204 66;
while [ 0 ]; do
echo -e "ttySAC0\n\n">/dev/ttySAC0;
echo -e "ttySAC1\n\n">/dev/ttySAC1;
echo -e "ttySAC2\n\n">/dev/ttySAC2;
check=`let $check+1`;
echo $check;
done;
Now I can probe the device and find the UART consoles. Each ttySAC corresponds to UART... UART0=SAC0, UART1=SAC1, UART2=SAC2.
We are most concerned with UART2, however, it would appear thus far, that I cannot locate any UART consoles on this device.
Here's how I probe:
UsbBoot seems to be invoked directly only when OM values are
0 low, 1 low, 2 high, 3 high, 4 high, 5 high, 6 high, 7 low
OM7 and OM0 looks to me to be irrevelant to booting order. But all of the infos I get are more or less guess.
Too bad for us. As default only OM5 seems to be high or all are low.
I badly need updated CPU manual, the one I have is nearly useless.
described as OM register = 0x10000008
non stated in manual other OM register = 0x10020000 (offset 0 of PMU block)
OM cache also used by iROM to inform IBL if it's supposed to invoke USB or UART boot is 0x10020980
They seems to differ alot between themselves, Adam is unable to find UART which is also bad.
Probably i'm stuck until Sammy release more detailed documentation about CPU. :/
I too am stuck as I cannot probe for more information without some sort of live debugging interface like UART. It seems that samsung may have messed up here because UART is available on models after this one like i777. We need more information. Here's what we need to continue and save bricked Exynos devices.
1. Datasheets on Exynos processor
2. Schematics or documantation. showing AP UART testpoints and/or locations
I just wanted to link this topic in http://forum.xda-developers.com/showthread.php?t=1313588
This shows the UART output we are expecting.. However the i9100 was made incorrectly so research on this device will be impossible. I am looking for a i777 to continue this project.
AdamOutler said:
I thought I would begin locating UART. So... here's what I'm doing..
...
We are most concerned with UART2, however, it would appear thus far, that I cannot locate any UART consoles on this device.
Click to expand...
Click to collapse
Hi, 2 things: (on a GT-I9100)
1. Why are you making new SAC devices, are they not already present?
Another way to check device types is by:
# cat /proc/tty/drivers
Code:
/dev/tty /dev/tty 5 0 system:/dev/tty
/dev/console /dev/console 5 1 system:console
/dev/ptmx /dev/ptmx 5 2 system
/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
rfcomm /dev/rfcomm 216 0-255 serial
g_serial /dev/ttyGS 253 0 serial "Datarouter" & see dun: (10,123)
ttySAC /dev/s3c2410_serial 204 64-68 serial SAmsung Console (UART)
serial /dev/ttyS 4 64-67 serial
pty_slave /dev/pts 136 0-1048575 pty:slave
pty_master /dev/ptm 128 0-1048575 pty:master
pty_slave /dev/ttyp 3 0-255 pty:slave
pty_master /dev/pty 2 0-255 pty:master
unknown /dev/tty 4 1-63 console
However, these are not always immediately available, when
not in use. E.g. You will not have an /dev/rfcomm unless you have
activated Bluetooth. In addition you can check your ttySAC's with:
# cat /proc/tty/driver/ttySAC
Code:
serinfo:1.0 driver revision:
0: uart:S3C6400/10 mmio:0x13800000 irq:16 tx:0 rx:0 DSR|CD
1: uart:S3C6400/10 mmio:0x13810000 irq:20 tx:205473 rx:1666 RTS|CTS|DTR|DSR|CD
2: uart:S3C6400/10 mmio:0x13820000 irq:24 tx:0 rx:0 DSR|CD
3: uart:S3C6400/10 mmio:0x13830000 irq:28 tx:0 rx:0 DSR|CD
4: uart:S3C6400/10 mmio:0x13840000 irq:320 tx:0 rx:0 CTS|DSR|CD
2. Have you set the USB connection behavior in the PhoneUtils (service/engineering) menu?
Dial: *#7284#
Code:
UART:
[[B]o[/B]] MODEM[B]*[/B]
[ ] PDA
USB:
[ ] MODEM
[[B]o[/B]] PDA[B]*[/B]
* is default SGS2 setting.
However, my problem is that if I change to USB-MODEM, then my PC no longer find the correct drivers, and I have no clue where to find them. Perhaps the Bada guys may know something about this...
---------------------------------- adendum --------------------------------
[EDIT 2012-02-15]
On second thought, this is really some kind of MUX, so you have to put your UART to point to PDA (AP)!
The sac2 device did not exist by default. It's easier to just create it when SSHing in.
Hey, I guess we need to promote this thread somewhere. I really would like to see some progress here, before we all start crying over our SGS-2's!
For what little its worth, if anything:
See my latest addition to the proprietary ATCs: AT+XSIO and AT+XTRACE.They may have something to do with specifying the UART (and other) debug ports. http://forum.xda-developers.com/showpost.php?p=21965170&postcount=3
Apart from that, there seem to be quite a few ways to "enable" various "debug" and log options (over different types of transport). Problem is (still) that they're not documented anywhere.
Also, since SGS2 should conform to all JTAG standards, there HAVE to be other lines for talking to AP. In addition, looking at the source of ServiceMode application, there are many references in there pointing to using other protocols (PCM, I2S, IPC, UART, USB) for debugging purposes. So even if pure serial is not currently available, the same log-stream may be found on a different transport, like mentioned or whatever the heck they use...
Please don't give up!
You should have a look at the special notes in this post. (It's just part of the manual.) Have you tried to activate that GPIO pin that is mentioned? I have also tried to trace all the Modem - AP connections and put the results in that thread...
Hi all
I am pretty new to the HD2 and android scene, coming from an iPhone. However am pretty technical, been a linux user since first slackware release in the early 90's, am a developer, been a unix admin, etc. I understand what RTFM is so my apologies if this has been answered somewhere before; but I have searched, read thousands of posts, and even came across my exact question, but nobody responded to it. So here goes...
In WinMo proximity sensor is working as you would expect.
In Android, many different ROM's and kernels, using different apps to test the sensors, proximity sensor returns 9 regardless of it being uncovered or covered. My understanding is the proximity sensor is top left of screen.
In fiddling around in a shell session on the phone (via adb) I noticed the file
/sys/devices/virtual/sensors/proximity_sensor
contains the line
proximity enabled = 0
I am at a complete loss as to what the problem would be. Seems like it is working for most people. Any help or pointers would be greatly appreciated.
Thank you
Download Z-DeviceTest, open this one and tap on proximity sensor.
Than look at your mentioned file and as U can see it is changed to
Code:
proximity enabled = 1
So it will be only enabled if needed (in calls for example).
You are right, when running Z-Device Test and selecting proximity sensor test, it does show proximity enabled = 1.
However, Z-Device Test shows Distance = 9.0000 cm regardless of if the sensor is covered or not. It never changes from 9cm.
When in call, the screen does not blank under Android.
On Win mobile, the screen blanks as expected when on a call and put up to your ear.
Anyone have any idea what the problem might be?
Bump. Anyone else experience this or have any idea what could be causing the proximity sensor to not work.
Works fine in win mobile 6.5.
I had a similar problem once where my proximity sensor and accelerometer wouldn't work and it was because I had too small of a system partition. I flashed the correct size and poof all was well again. I have no idea what exactly happened but I am assuming that when it flashed the sensor files were last and since there was no room they weren't written.
Not sure if you are having the same problem but it is worth checking out.
Sent from my NexusHD2 using XDA App
Thanks for the reply and suggestion.
I do not this that is my problem, my system partition is fairly large at 250 MB and is just 53% used. See results of df -h via shell.
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 205.6M 32.0K 205.5M 0% /dev
tmpfs 205.6M 0 205.6M 0% /mnt/asec
tmpfs 205.6M 0 205.6M 0% /mnt/obb
/dev/block/mtdblock3 250.0M 132.4M 117.6M 53% /system
/dev/block/mtdblock5 627.8M 161.9M 465.9M 26% /data
/dev/block/mtdblock4 45.0M 1.2M 43.8M 3% /mnt/cache
/dev/block/mmcblk0p2 114.4M 87.0M 21.3M 80% /sd-ext
/dev/block/vold/179:1
14.6G 1.9G 12.7G 13% /mnt/sdcard
/dev/block/vold/179:1
14.6G 1.9G 12.7G 13% /mnt/secure/asec
I had the same sort of problem, thought it was the rom. I used "Proximity Sensor Finder" to test it, and it permanently showed 0.0 cm.
It turned out to be the screen protector in the end. It must have been reflecting enough IR back that it thought it was covered all the time. Scissors fixed it though.
It might be worth checking it's not something simple like that...
No screen protector on.
Mine stays stuck at 9cm no matter if it is uncovered or covered. I guess just the opposite of you; it thinks it is never covered.
Tried installing proximity recalibrator tool as I read that helped some people with similar issues. However, can't get it to run, when it starts I get the error:
Code:
ps_kadc not found
My nexus LGE Barometer Sensor (BOSCH)* stuck at 988 - 989 h Pa its about 26,5 below real value(compared to forecast and second android phone).
I found no tool to calibrate this piece of hardware.
Checked value on 4.2.2 and 4.3.0. Always the same.
So now the question. Is this measurement inaccuracy common?
Can I fix it? Tried factory reset and barometer calibration apps from store but it all does not work.
If not - should I send it for a warranty fix(is this element replaceable or I'll get whole new board or phone?
*LGE Barometer Sensor (BOSCH); range: 0...1100; resolution: 0,01 (0,001%); power: 0,003mA;
Hello there,
I decided to post in here after doing extensive research online but having found no answer to my problem....
I have had a rooted (with NookManager) Nook Simple Touch that worked perfectly until I went travelling across tropical countries. Since then, I have seen a progressive degradation of the touchscreen, specifically I noted the following:
Buttons/icons in the lower half of the screen, when tapped, do no respond. Instead, buttons/icons directly above them (on the upper part of the screen) do respond to the action.
When the keyboard is active and letters are tapped, you get one of these random behaviours:
the letter appears on the screen, but 2 or 3 of them, even if the letter is tapped once.
the letter above the one tapped, appears on screen: e.g. I press "q" and "a" appears on screen; I press "backspace" and the letter "p" appears on screen.
Following the recommendations of many forums, I cleaned thoroughly my screen, however this does not seem to resolve the problem. I also performed a factory reset and re-root, still the problem persists (though, after a new factory reset, the erratic behaviour is less frequent, at start, but then It worsens as time goes by).
The only thing that changed is the fact that I am now travelling in hotter countries and maybe the Nook is sensitive to temperatures constantly above 30C. so I suspect it may be the cause.
Has anyone experienced similar problems?
Thanks
Marco
The processing for the zForce touch screen is done by a TI MSP430 processor.
This is separate from the main OMAP 3621 processor.
They communicate over I2C.
There are no user-friendly diagnostics built in.
It's difficult to identify problems.
I have a unit with a similar problem.
I've been starting to look into this.
I'd like to make a user app that deals with the more common problem of dirt and would actually indicate where the dirt is.
(The problem with this unit is not dirt either.)
I've got a new utility for debugging problems with the touch screen.
At the very least it should be able to tell you where the dirt is when it is dirt.
I need to do some polishing up on it.
The screenshot is a touchscreen with one touch in the middle.
The lines at the top and bottom are marginal performance of the edge sensors.
When there is no touch all the lines should be light gray.
The black indicates where it thinks there is an obstruction.
Thanks so much for your response, Renate.
I very much look forward to your tool!
It is quite a frustrating behaviour that seriously limits the interaction with my NST (last time it took me 1 hour just to be able to type a wireless password correctly!).
Marco
Here's an alpha version of the utility.
When you run it, most of the lines should be a light gray.
Touch some place and it will show black lines.
Paste a screenshot if you would please.
I may be hot on the track of what the actual problem is.
Questions:
Did this happen slowly over time?
Was it humid there or just hot?
Renate NST said:
Questions:
Did this happen slowly over time?
Was it humid there or just hot?
Click to expand...
Click to collapse
Renate,
I'll try your utility later on today, after rooting again my net, and then let you know.
In the meanwhile, to answer your questions:
- yes, the problem started occasionally and worsened over time. Now, after 3 months from when I first appeared, I can hardly use the touchscreen
- it is hot and humid.
New alpha version.
Light line - open pathway working correctly
Dark line - blocked pathway
Dashed line - maxed out LED drive, something not optimal
Sorry, the latest version:
Overview, an untouched screen should have all light gray lines of some kind,
a touched screen should have thick black lines near the point.
Thin light gray line - normal, open pathway
Thick dashed light gray line - maxed LED drive, open pathway
Thick black line - normal, blocked pathway
Thick dashed black line - maxed LED drive, blocked pathway
Thick long dashed black line - maxed LED drive, zero signal
This would all be easier if I could just use colors!
Well, I could, but you'd need to take a screenshot to see them.
Update: Download Touch.apk in the signature.
Renate NST said:
Thin light gray line - normal, open pathway
Thick dashed light gray line - maxed LED drive, open pathway
Thick black line - normal, blocked pathway
Thick dashed black line - maxed LED drive, blocked pathway
Thick long dashed black line - maxed LED drive, zero signal
Click to expand...
Click to collapse
HI Renate!
I just ran your latest version and yes, I do have a couple of "<"-shaped thick dashed black lines in the middle of the screen and one thick gray dashed line at the very top of the screen. All the rest is thin light gray.
I'm gonna take a screenshot of it as soon as I get around installing QtADB (and the SDK) on my netbook I am currently using while travelling.
I just noticed that if I rub quite hard my unresponsive keyboard (for 10/15 seconds), the letters start to work properly again, until I keep the keyboard open. When I close and re-open it, I need to rub the keyboard again for a few seconds to get it to work again.
This also applies to any other area of the screen (buttons/icons) that does not work properly.
Needless to say, this behaviour is quite random.
Any idea about the cause and the remedy?
Marco
Snapshot of my nook attached.
Hmm, that doesn't look too bad.
Do this in an ADB shell:
Code:
cd /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050
cat ledlevel
echo 1 > forcecal
cat ledlevel
You can do this with the Touch app running.
Touch (and release) afterwards to see if the V in the center disappears.
Post the ledlevel responses.
Renate NST said:
Post the ledlevel responses.
Click to expand...
Click to collapse
First ledlevel (before "forcecal"):
Code:
09 09 104 111 06 08 095 105 05 05 100 106 03 03 102 087 03 05 088 089 06 03 098 082 03 05 090 075 03 03 093 084 05 06 095 088 08 09 090 092 09 09 097 098
15 03 054 103 02 01 100 106 01 01 117 115 02 02 112 099 02 01 095 102 01 01 099 105 01 01 108 107 01 02 101 104 15 15 009 010 01 01 087 096 02 03 108 094 02 03 097 095 01 02 118 102 03 03 087 084 11 12 065 086
Second ledlevel:
Code:
08 08 071 078 05 06 079 076 03 03 078 076 02 03 075 082 03 05 080 087 05 03 080 075 03 03 092 073 02 03 082 081 03 05 078 067 06 09 080 090 09 08 095 088
15 02 050 075 02 01 087 079 01 01 086 082 01 01 101 087 02 01 078 100 01 01 097 077 01 01 079 080 01 02 094 089 15 15 008 009 01 01 083 090 02 03 087 079 02 02 078 077 01 02 086 082 02 03 076 077 12 12 094 082
I didnt notice any changes in the touch screen after the ADB commands, even after a few touches. I restarted the Nook and ran the touch utility again, still no changes. The same pattern is still there.
Marco
I've been playing with my problem Nook and I've gotten it a lot closer to working.
The mechanical alignment of the components is very critical.
It's all held together with double stick tape.
Especially the top end is sensitive, that has the biggest span of plastic in the IR (internal) bezel.
But I don't think that this is your problem.
marcoNST said:
Code:
... 01 01 108 107 [color=green]01 02 101 104[/color] [color=red]15 15 009 010[/color] [color=green]01 01 087 096[/color] 02 03 108 094 ...
Click to expand...
Click to collapse
Your problem is clearly related to the left side (LED side) at the vertex of the V.
The two LEDs on the left, above and below are getting a fine response out of the two photodiodes on the right used by the problem V.
Put on your reading glasses and look very closely at the left edge of the V for anything odd.
There could be dirt internally between the internal edge of the bezel and the LED.
The LED itself could be semi-fried.
The LED driver could be semi-fried.
Depending on how sensitive a camera (and how lousy an IR cut filter it has) you have, you might be able to see the problem that way.
In a darkened room, point the camera as low as possible towards the left edge.
With your finger on some part of the screen you might be able to see a dull red flickering.
My cell phone can see that if pointed directly at the LEDs on the disassembled unit.
There is also the trick of using a photodiode on a mic input to a PC.
Oh, a new version of Touch.apk
It doesn't show anything different, it just updates periodically without a touch.
That's helpful if you want to try pushing on the case to see if things change.
Update: Download Touch.apk in the signature.
Renate NST said:
Your problem is clearly related to the left side (LED side) at the vertex of the V.
Click to expand...
Click to collapse
There is also one dashed grey line at the top of the screen.
Could it be part of the same problem?
Should I look for dirt in that area too?
OK, I inspected the area (without camera).
The edges of the screen are made by 2 layers: the hard plastic black casing that touches the screen and the rubber-y dark grey wrap material glued above it. Well, because of the heat (most likely!), the glue has lost its grip in some parts (so much so that i can slide a needle in these parts), including the LED area and dirt has crept in. I removed some of the dirt with the needle.
The hard black casing is still well attached to the screen.
I still have the same LED pattern. Is there a safe way to open the Nook and remove the dirt?
At least i can exclude one cause.
M.
M
The very top and bottom horizontal lines have a couple of bad design problems working against them.
I wouldn't be surprised if all Nooks had problems there.
The optical problem with dirt would be dirt on the face of the dark green inner bezel.
If you have dirt under the bezel that would relate to a physical problem affecting the optical alignment.
Use the new version of Touch.apk and see if you can squeeze the case at the bad spot and make the V disappear.
Try also bending (lightly) the edge backwards and forwards.
Do this and also try doing a echo 1 > forcecal at the same time.
If you have to take the bezel apart to try to fix this you'll be opening up a whole new can of worms.
That's what I'm trying to solve with my 2nd Nook.
Hi Renate,
I tried your solution (repeat the forcecal), but no joy.
At this stage, I am going to get a new one (or second hand) very soon as I really need a functional reader for my travels and Nook suits me well.
But I wanted to thank you for your help and good luck recovering yours!
Marco
P.S. Also I need to thank you for your Library app, I have been using it since rooted and loved it!
This deserves a bump.
I had almost forgotten about this utility.
My screen was behaving flakey.
Using the Touch apk I could instantly see where the problem was, know where to clean, and confirm that the cleaning worked.
Some of you out there with aging Nooks could probably use this.
Download in the signature.
Not Working
I am in a similar boat with this. I apologize, but I wasn't sure if i would even be able to access the apk. The only sensors I know that definitely don't work are the ones that allow me to unlock my screen.
I've taken apart my Nook to look at the hardware and everything seemed fine, except for the fact that the tape around the screen was dirty. I wiped it down with a wet paper-towel, yet it still doesn't work properly.
It's not clear what your current situation is.
Your Nook is locked and you can't unlock it?
Do you have ADB running? You could delete the lock. (search this forum, it's there.)
Can you run Touch.apk?
Post a screenshot if you can.
@Nitewolf588 @Renate NST Here's the mod to turn off slide-to-unlock.
Very nice design android smartwatch, round screen
Bluetooth version : Bluetooth 4.0
CPU : MTK6580 1.3GHz,Quad Core
Network Frequency : GSM：850/900/1800/1900Mhz WCDMA ：850/2100Mhz
Screen Size : 1.33 inch
Screen type : Gorilla Glass 3
Resolution : 360*360 pixel
WiFi : 802.11b/g/n
RAM : 512MB
ROM :4GB
Camera :2.0MP
Battery type: Polymer lithium ion battery
Battery capacity : 480 mAh
Water resistant : IP67 Certified
Herberteten said:
Very nice design android smartwatch, round screen
Bluetooth version : Bluetooth 4.0
CPU : MTK6580 1.3GHz,Quad Core
Network Frequency : GSM：850/900/1800/1900Mhz WCDMA ：850/2100Mhz
Screen Size : 1.33 inch
Screen type : Gorilla Glass 3
Resolution : 360*360 pixel
WiFi : 802.11b/g/n
RAM : 512MB
ROM :4GB
Camera :2.0MP
Battery type: Polymer lithium ion battery
Battery capacity : 480 mAh
Water resistant : IP67 Certified
Click to expand...
Click to collapse
Any chance to see sample photos and videos from the camera, please? Thanks in advance
This video was made by the vendor so that photos you ask for may or may not appear.
The standard issue bamboo table accessory is a bit of a give-away
segafan said:
Any chance to see sample photos and videos from the camera, please? Thanks in advance
Click to expand...
Click to collapse
The photos clear enough.
pablo11 said:
This video was made by the vendor so that photos you ask for may or may not appear.
The standard issue bamboo table accessory is a bit of a give-away
Click to expand...
Click to collapse
don't understand what you mean, that just a review, show this product to the people. then they dicede this product good or not.
Feedback from the smartwatch:
AVOID IT
The touch is good, but it is always rebooting by is own, and if you have it connected to your smartphone, the battery doesn't last half a day, and i'm not kidding...
I think you received a faulty one.
Except for battery life and Rom capacity this is good purchase for the price (I paid it 83€), particularly if you use it as you have to...as stand alone watch phone with sim inserted and call diversion and occasionally as fitness/phone companion.
Here are my first impression after three days use:
- At the moment you can't change watchfaces, developers are still on work.
- gps is almost accurate if you use a sim
-step counter is not far from results shown on my Note 4.
- hr monitor isn't bad at all +2 in relation to Note 4
Problems? Many apps don't recognize the sensors... they act as them don't exist at all.
- google fit counts steps/no hr
- Shealth no steps count neither hr....
- endomondo no steps neither hr....
Have you tried some other apps? What are your results?
I don't use so much sinwear.
Remember you can't answer with your watch when bt connected to the phone. You have only a notification of incoming call.
I received all notification (no sms) Whatsapp/hangout/telegram/etc. But I can't answer to any of them.
I think this device is much better if you use it as a watch phone, with call diversion, als as an android wear.
I'm starting also to text the battery drain. (Mid brightness - 3-4 times on for warltching what time is it - rotation activating display off - gesture on)
Airplane mode - 1/2% per hour
2G only - 2% per hour
3G+GPS+shealth- 40% per hour
2G+GPS+BT(earset music)+shealth - 60% in 40 minutes. I think it reaches 1hour 10 no more.
IP 67 tested under spilling water, no problem with heavy sweating too, I don't put it in the water so far.
The two main problems are:
1_ battery drain - I need a double autonomy.
2_free ROM space - I have anything on the phone only 20 mp3 files, shealth and a weather app installed and only 430 mb free space...
If you need more rom space (like me) or battery autonomy you Finox q1/ourtime x01s (this is the new model, I didn't find much anywhere) or something else with 8GB rom...someone have it? Any advice?
After a week of very light use I started to experience so many problems...battery unstable, shuts down with 15^20%, bt disconnections, sudden not motivated shut downs and reboot...I don't know what happened. I contacted the seller and he agreed to take it back and give me a full refund. Probably I have received a defective item, however I wouldn't buy it newly.
Inviato dal mio SM-N910F utilizzando Tapatalk
Hello! anyone can install android wear on zeblaze blitz? or you can install more watchfaces by watchmaker?