[Q] Nook Touch vs Color: technical hardware driver differences - Nook Touch General

Just waiting for my Nook Touch to arrive...
is there any internal pictures of the Touch?
I'm interested in the differences between the Nook Color and the touch. I believe they are very similar, but not identical, which is why CyanogenMod runs on the color but not on the touch. What are the differences, what drivers need to be added to have customs ROMs on the Touch?
When my Touch arrives I'll start poking around the filesystem and update this thread. Hopefully the kernel modules are kepts as modules rather than built into the kernel.
Edit :
Touch - http://www.techrepublic.com/blog/it...replaceable-same-processor-as-nook-color/2639
Color - http://www.zdnet.com/photos/nookcolor-teardown/487636
- and chipsets in the Color for kernel module drivers to compare with http://nookdevs.com/What_we_know
So to compare:
(Touch in Italics
Color in Bold)
3.7V 1530mAh, 5.66Wh Li-Ion battery (Model No: MLP305787)
6″ Pearl e-ink screen with Neonode zForce touchscreen
^ well, the Color has a real touch screen whereas the Touch uses a IR grid
800MHz Texas Instruments OMAP3621 applications processor
^ color has Samsung S3C6410 ARM processor (no major change)
Texas Instruments TPS65921B Integrated Power Management IC with USB HS Transceiver
Texas Instruments TPS65181 Power Management IC for E Ink Vizplex Enabled Electronic Paper Display
Texas Instruments MSP430F2272 16-bit Ultra-Low-Power Microcontroller
Texas Instruments CD74HC4067 High Speed CMOS 16-Channel Analog Multiplexer/Demultiplexer
Texas Instruments 2624I
SanDisk SDIN5D2-2G NAND Flash chip
Samsung K4X2G323PC-8G08 512 mobile DDR SDRAM
Lattice Semiconductor ispMACH 4032ZE CPLD
Jorjin Technologies WG7310-2A 802.11b/g/n Wi-Fi SiP module
^ Color has CyberTAN Technology (802.11 b/g) (libertas sdio sd8686), CM7 uses tiwlan_drv.ko More info: http://www.jorjin.com/WG7310-20.html
Now to determine what these parts are using for kernel modules...
Any other links for reference:
A slow mention at Cyanomod7 forums: http://forum.cyanogenmod.com/topic/30624-nook-simple-touch-mod/
Cyanomod7 for Nook Color, to study that image for alteration: http://www.cyanogenmod.com/devices/nook-color
Other notes:
Important - the Nook Color is known as the Encore on the CM7 github dev site:
https://github.com/CyanogenMod/android_device_bn_encore
edit: Definately no bluetooth -
Sorry definitely no Bluetooth. At first we thought it did but we were getting confused with a very similar chip (part number ending 0A rather than 2A). The block diagram for the chip in the Nook clearly has Bluetooth crossed out:
http://www.jorjin.com/WG7310-20.html
What made it confusing was that it still has `BT` in the specs, but this is referring to WiFi BT coexistance mode.
So the only way to add Bluetooth would be to get a 0A chip and replace it with the 2A chip on the board. But this scale of soldering is too fiddly to be worth it and practically impossible at this scale.
Hope this clears things up.
Click to expand...
Click to collapse

good summary. Anyone know the best way to get GPS with nook touch? I can't select 'allow mock locations' in settings to try tethering.
Any progress on cyanogenmod 7 for our device? The CM7 site thread points here and this thread points there.. but nothing else out there re CM7 for NT.

And what about partition table of internal flash? Does it look the same?

I wonder what happens if we just try loading CM7 onto the Touch that was designed for the Color.
Probably the screen input will fail. I've noticed that there's no /dev/input/mice
maybe there's something custom in /dev/socket
Code:
E:\ProgramFiles\androidSDK\platform-tools>adb shell ls -R /dev
/dev:
bc_example
pvrsrvkm
rm_server_in
pm_server_out
pm_server_in
timer
controlC0
pcmC0D0p
pcmC0D0c
DspBridge
vcsa
vcs
ptmx
tty63
tty62
tty61
tty60
tty59
tty58
tty57
tty56
tty55
tty54
tty53
tty52
tty51
tty50
tty49
tty48
tty47
tty46
tty45
tty44
tty43
tty42
tty41
tty40
tty39
tty38
tty37
tty36
tty35
tty34
tty33
tty32
tty31
tty30
tty29
tty28
tty27
tty26
tty25
tty24
tty23
tty22
tty21
tty20
tty19
tty18
tty17
tty16
tty15
tty14
tty13
tty12
tty11
tty10
tty9
tty8
tty7
tty6
tty5
tty4
tty3
tty2
tty1
tty0
console
tty
network_throughput
network_latency
cpu_dma_latency
log
binder
alarm
android_adb
android_adb_enable
twl4030-madc
ashmem
kmsg
urandom
random
full
zero
null
kmem
mem
snd
graphics
watchdog
ttyS1
ttyS0
usbdev1.1_ep00
usbdev1.1_ep81
usb1
block
i2c-2
i2c-1
rtc0
input
socket
pts
/dev/log:
radio
events
main
/dev/snd:
timer
controlC0
pcmC0D0c
pcmC0D0p
/dev/graphics:
fb0
/dev/block:
vold
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
/dev/block/vold:
179:8
179:7
179:6
179:5
179:4
179:3
179:2
179:1
179:0
/dev/input:
event2
event1
event0
/dev/socket:
wpa_tiwlan0
keystore
installd
dbus
zygote
vold
property_service
/dev/pts:
2
9
8
7
6
5
4
3
1
0
I'd love to have a go at CM7... but it's dicey. What would help a lot is being able to run live straight off the SD card so that any testing is done there without changing the nook itself.
re: partition table: I'll have to have a look. I'll see if I can push something like fdisk to it. See this thread: http://forum.xda-developers.com/showthread.php?t=1241728
re: Mock locations. I don't have that option either. I'm only on version 1.0.0. Perhaps we need to upgrade?

Hi all
I suppose many of us are dreaming of having CM (I hope . So as Nook Color and Nook Touch are almost the same from technical point of view I tried to install CM on my Nook Touch. I was sure that at least touch screen wouldn't work so it was just an experiment.
1. Installed Rommanager - success
2. Flashed CWM (4 Nook Color) - success
3. Reboot into recovery - failed (hang)
Any ideas?
P.S. Moderators, I suggest to move this topic to android development, not general.

Which hardware specs is right?
jago25_98 said:
Just waiting for my Nook Touch to arrive...
Touch - www.techrepublic.com/blog/itdojo/no...replaceable-same-processor-as-nook-color/2639
800MHz Texas Instruments OMAP3621 applications processor
Samsung K4X2G323PC-8G08 512 mobile DDR SDRAM
Click to expand...
Click to collapse
I'd like to buy an ereader, like Nook Simple Touch, Kindle Touch, or Sony PRS-T1. And I want to know the hardware before I buy it.
However, I am very confused about Nook Touch specs.
It says 800 MHz CPU + 512 MB memory here.
From B&N website, it is 600 MHz + 256 MB memory link www.barnesandnoble.com/u/Compare-NOOKs/379003181
Another post (mikecanex.wordpress.com/2011/06/13/nook-touch-rooting-june-13th-news) says it has a TI OMAP3621 CPU but the clock is 600 MHz (BTW: does BogoMIPS : 597.64 in the post mean 600 MHz?) and 228 MB usable memory.
According to wiki (en.wikipedia.org/wiki/Texas_Instruments_OMAP#OMAP_3) OMPA3611 clocked at 800 MHz is used in Nook Simple Touch.
Which one is accurate? If it is 512 MB, I will go for Nook Touch as it will be much better to load Android apps.
PS: Microcenter says Sony PRS-T1 has 256 MB memory. (www.microcenter.com/single_product_results.phtml?product_id=0375288)

Himalayas said:
Which one is accurate? If it is 512 MB, I will go for Nook Touch as it will be much better to load Android apps.
Click to expand...
Click to collapse
The NST has 2GB of flash memory used for internal storage + 512MB of DDR SDRAM
Edit: Just looked inside mine, it has a Hynix 256MB chip, so the 512MB claim over at techrepublic doesn't hold water.
---------- Post added at 11:53 AM ---------- Previous post was at 11:50 AM ----------
Did a check on my NST just to see how much of that chip is usable:
Code:
<6>[ 0.000000] Memory: 256MB = 256MB total
<5>[ 0.000000] Memory: 232448KB available (3328K code, 798K data, 144K init)
That might not be what you wanted to hear

Himalayas said:
Another post (mikecanex.wordpress.com/2011/06/13/nook-touch-rooting-june-13th-news) says it has a TI OMAP3621 CPU but the clock is 600 MHz (BTW: does BogoMIPS : 597.64 in the post mean 600 MHz?) and 228 MB usable memory.
Click to expand...
Click to collapse
It's clocked at 800mhz even if cpuinfo reports diferently

ros87 said:
Just looked inside mine, it has a Hynix 256MB chip
Did a check on my NST just to see how much of that chip is usable:
Code:
<6>[ 0.000000] Memory: 256MB = 256MB total
<5>[ 0.000000] Memory: 232448KB available (3328K code, 798K data, 144K init)
That might not be what you wanted to hear
Click to expand...
Click to collapse
eded333 said:
It's clocked at 800mhz even if cpuinfo reports diferently
Click to expand...
Click to collapse
Then the official B&N website give us correct memory (256 MB) but incorrect CPU frequency ( 600 MHz instead of real 800 MHz).
It is not as sweet as I thought. But at that price, we can't expect more, right? I may start looking at Sony PSR-T1, then.

Related

Windows Mobile 7.0 Requirements

Hi all does anyone know if this is the hardware requirements for WM7. It was taken from this website as a leak of info from microsoft. But is it genuine?
WM7 Chassis 1 Specification
Core requirements:
Processor: ARM v6+, L2 Cache, VFP, Open GL ES 2.0 graphics HW (QCOM 8k, Nvidia AP15/16* and TI 3430 all meet spec)
Memory: 256MB+ DRAM, 1G+ Flash (at least 512MB fast flash – 5MB/s unbuffered read @4K block size)
Display: WVGA (800×480) or FWVGA (854×480) 3.5” or greater diagonal
Touch: Multi-touch required
Battery: Sufficient to meet Days of Use LTK requirements.
Controls: Start, Back, Send and End are required (soft controls allowed as long as they are always present).
Peripherals:
Camera: 3MP+, flash optional, 2nd camera optional (VGA resolution sufficient)
GPS: aGPS required
Sensors required: Light Sensor, Compass (3 axis, 5 degrees, 100 Hz sample rate), Accelerometer (3 axis, 2mg resolution, 100 Hz sample rate)
USB: High speed required, 20 MB/s transfer rate.
BlueTooth: BT2.1 required, must run MSFT BT stack, CSR BlueCore6 or later recommended.
Wi-Fi: 802.11B/G required, must run MSFT Native Wi-Fi stack, Atheros 6002 or Broadcomm 4325 recommended.
Connectors: Micro USB and 3.5mm Audio required.
Options:
FM tuner: If tuner HW is present it will be detected and supported by the Media application.
Haptics
SD Card (Micro SD recommended)
DPAD, qwerty or 12/20 key keyboards all optional
Thoughts? It seems like a pretty solid foundation for the next generation of Windows Mobile.
It's as genuine now as it was a month ago when it was first posted. As far as I'm aware, no official requirements list has been produced by Microsoft. The internet has several different versions available though.
Havok316uk said:
Hi all does anyone know if this is the hardware requirements for WM7. It was taken from this website as a leak of info from microsoft. But is it genuine?
WM7 Chassis 1 Specification
Core requirements:
Processor: ARM v6+, L2 Cache, VFP, Open GL ES 2.0 graphics HW (QCOM 8k, Nvidia AP15/16* and TI 3430 all meet spec)
Memory: 256MB+ DRAM, 1G+ Flash (at least 512MB fast flash – 5MB/s unbuffered read @4K block size)
Display: WVGA (800×480) or FWVGA (854×480) 3.5” or greater diagonal
Touch: Multi-touch required
Battery: Sufficient to meet Days of Use LTK requirements.
Controls: Start, Back, Send and End are required (soft controls allowed as long as they are always present).
Peripherals:
Camera: 3MP+, flash optional, 2nd camera optional (VGA resolution sufficient)
GPS: aGPS required
Sensors required: Light Sensor, Compass (3 axis, 5 degrees, 100 Hz sample rate), Accelerometer (3 axis, 2mg resolution, 100 Hz sample rate)
USB: High speed required, 20 MB/s transfer rate.
BlueTooth: BT2.1 required, must run MSFT BT stack, CSR BlueCore6 or later recommended.
Wi-Fi: 802.11B/G required, must run MSFT Native Wi-Fi stack, Atheros 6002 or Broadcomm 4325 recommended.
Connectors: Micro USB and 3.5mm Audio required.
Options:
FM tuner: If tuner HW is present it will be detected and supported by the Media application.
Haptics
SD Card (Micro SD recommended)
DPAD, qwerty or 12/20 key keyboards all optional
Thoughts? It seems like a pretty solid foundation for the next generation of Windows Mobile.
Click to expand...
Click to collapse
Have you got it straight from Microsoft? If not its probably fake.
The fact that Microsoft hasn't released anything, no one here would know as there is nothing official to compare to.

FM Radio - Another approach

In my Captivate I noticed a kernel module with name Si4709_driver.ko
Si4709 is a FM radio receiver www .silabs. com /products/audiovideo/fmreceivers/Pages/Si470809.aspx (sorry, I can't post URL)
By default it is not loaded, but when I tried to load it, it did. Now we need to know what API is used for user mode programs.
It would also help if those who put i9000 ROM into Captivate (but have stock kernel) tried load module and then run FM radio app.
# cd /lib
# ls
modules
# cd modules
# ls
dpram.ko
rfs_glue.ko
j4fs.ko
multipdp.ko
param.ko
vibrator.ko
Si4709_driver.ko
dhd.ko
rfs_fat.ko
stgloc
s3c_bc.ko
pvrsrvkm.ko
scsi_wait_scan.ko
fsr.ko
drop_caches.ko
fsr_stl.ko
s3c_lcd.ko
# insmod /lib/modules/Si4709_driver.ko
# lsmod
Si4709_driver 15744 0 - Live 0xbf195000
vibrator 6744 2 - Live 0xbf191000
s3c_bc 2880 0 - Live 0xbf18b000
s3c_lcd 5060 0 - Live 0xbf184000
pvrsrvkm 205996 48 s3c_bc,s3c_lcd, Live 0xbf14c000
multipdp 30968 1 - Live 0xbf13f000
dpram 194152 10 multipdp, Live 0xbf10a000
param 10132 0 - Live 0xbf105000 (P)
j4fs 65604 1 - Live 0xbf0ef000 (P)
rfs_fat 235456 5 - Live 0xbf0b0000 (P)
rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)
fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)
fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)
#
Nice find. This may turn into something.
With the module loaded the FM radio app no longer has the error 'Unable to turn on FM radio." However, the FM app has no sound and cannot seek for channels.
dalingrin said:
With the module loaded the FM radio app no longer has the error 'Unable to turn on FM radio." However, the FM app has no sound and cannot seek for channels.
Click to expand...
Click to collapse
Looks like the hardware may be there after all, you were using the headphones right? If so then maybe the antenna isn't wired to the headset port.
Another note: Its is possible that hardware is not there. I found another tool that seems to test FM Radio
# ./si4709_test -h
How to control FM Radio (Si4709) .........
================================================================
Usage: ./si4709_test [controls] [value]
-p power, up|down si4709 power control
-s search, up|down|auto seek channel
-rstate, show si4709 radio state
-rssi, show si4709 rssi status
-r, on|off RDS/RBDS Enable/Disable
-rds, show Show RDS/RBDS data
e.g) si4709_test -p (up/down)
================================================================
# ./si4709_test -p up
# ./si4709_test -rstate
[FM RADIO] Radio State
================================================================
Power State = 0
Seek State = 0
================================================================
I tried to do the same on my wife's I9000 and it reported "Power State = 1"
So we may be out of luck with Captivate.
Not judging anyone but why worry about an FM radio when we have apps that do it all, about 4 of my local stations are on iheartradio and another 20 are from immediate areas around me.
When I used FM on my Nokia it was a battery drain more so than 3G.
I tied to run test with headphones connected. Attempt to power up device results in reboot.
Below is kernel log related to loading driver and connecting headphones:
<7>[ 197.626426] device: 'fmradio': device_add
<7>[ 197.628218] PM: Adding info for No Bus:fmradio
<7>[ 197.635228] bus: 'i2c': add driver Si4709_driver
<7>[ 197.665086] i2c-adapter i2c-8: NAK from device addr 0x10 msg #0
<6>[ 204.231953] [ JACK_DRIVER (jack_type_detect_change,404) ] 3 pole headset or TV-out attatched : adc = 46
I also noticed that after I load driver, I see device file called /dev/fmradio. It disappers when I unload driver. It looks like /dev/fmradio is a control device for radio chip (i found string /dev/fmradio inside si4709_test tool).
oh noes! I want the fm radio function.
for_ap1 said:
I tied to run test with headphones connected. Attempt to power up device results in reboot.
Below is kernel log related to loading driver and connecting headphones:
<7>[ 197.626426] device: 'fmradio': device_add
<7>[ 197.628218] PM: Adding info for No Bus:fmradio
<7>[ 197.635228] bus: 'i2c': add driver Si4709_driver
<7>[ 197.665086] i2c-adapter i2c-8: NAK from device addr 0x10 msg #0
<6>[ 204.231953] [ JACK_DRIVER (jack_type_detect_change,404) ] 3 pole headset or TV-out attatched : adc = 46
I also noticed that after I load driver, I see device file called /dev/fmradio. It disappers when I unload driver. It looks like /dev/fmradio is a control device for radio chip (i found string /dev/fmradio inside si4709_test tool).
Click to expand...
Click to collapse
Any way to compare pics of the Captivate mainboard with a Galaxy S? In the general Captivate forum there are pics of the board. Compare chip numbers and see if there are any unmatching chips.
zerosource said:
oh noes! I want the fm radio function.
Click to expand...
Click to collapse
lol I can see the use for it in a natural disaster, during Katrina the radio was all we really had but all the good channels were on the AM side.
decepticon said:
Any way to compare pics of the Captivate mainboard with a Galaxy S? In the general Captivate forum there are pics of the board. Compare chip numbers and see if there are any unmatching chips.
Click to expand...
Click to collapse
I looked at these photos and also at photos from FCC site, but resolution is too low to read chip markings. FM chip is very small in size, so it is really hard to find it.
It seems that receiver talks via I2S bus and also needs few GPIO lines to work. If I understand correctly, I2S bus has no explicit acknowledgment, so driver might not now that device is not present on the bus. I couldn't find detailed application notes for the chip, just brief description is available. I need to look at driver sources to understand how it works. Hopefully Samsung releases it.
Will Samsung or AT&T tell us if there is an FM chip in there or not?
cesierra said:
Will Samsung or AT&T tell us if there is an FM chip in there or not?
Click to expand...
Click to collapse
Maybe a brave soul, will tear the phone apart and finally give us a straight answer
wont be me though
In the source code for the captivate, there's is a folder called fm_si4709 containing many files pertaining to that radio. Perhaps someone astute w/ kernel stuff could work the magic and enable the HW if it is there...
Well, I looked at sources of the driver (i9000 and I897 are the same). It does not do anything with hardware on driver init. So successfully loaded driver does not mean that hardware is present. I need to find a way to compile driver with debug mode on. Another option will be to build a tool that probes I2C bus (i2cdump and i2cdetect) from shell.
Ok, I was able to build modules using Samsung sources and toolchain from Sourcery. I do not know if I can use it with stock kernel though. Will try to play with it, if I have spare time on weekend.
I just built the kernel using the sourcery toolchain: http://www.codesourcery.com/sgpp/lite/arm/portal/release1033
I enabled the debug flag for the FM radio driver (uncomment #define Si4709_DEBUG in kernel/modules/fm_si4709/Si4709_common.h)
I did an insmod of the compiled module (Si4709_driver.ko). Note the last few lines from dmesg (i2c_read failed & Si4709_dev_init failed) . Doesn't look promising.
<2>[277139.763458] --------Si4709_driver_init called
<7>[277139.766871] device: 'fmradio': device_add
<7>[277139.768313] PM: Adding info for No Bus:fmradio
<2>[277139.774798] --------Si4709_driver_init request_irq success 192
<2>[277139.779520] --------Si4709 i2c driver Si4709_i2c_driver_init called
<7>[277139.785779] bus: 'i2c': add driver Si4709_driver
<4>[277139.799406] ----- si4709_i2c_probe 94
<7>[277139.801782] device: '8-0010': device_add
<7>[277139.801979] bus: 'i2c': add device 8-0010
<7>[277139.802269] PM: Adding info for i2c:8-0010
<7>[277139.802442] driver: '8-0010': driver_bound: bound to device 'Si4709_driver'
<2>[277139.802555] --------Si4709 i2c driver Si4709_probe called
<2>[277139.807314] --------Si4709_dev_init called
<7>[277139.847935] i2c-adapter i2c-8: NAK from device addr 0x10 msg #0
<2>[277139.848866] --------i2c_read failed
<2>[277139.851148] --------Si4709_dev_init call over
<2>[277139.855568] --------Si4709_dev_init failed
<2>[277139.859757] --------Si4709_driver_init successful
Damn that sucks :-(. Wish we knew what the chip looked like so we could just see if its on the phone.
why would they put the drivers in, if there is no chip? This is just a hope.
I was think the same thing. I don't know much about kernel building but I would imagine if I was the guy at Samsung making it I wouldn't add sh!t that was useless
They didn't add a potentially useless driver, they just didn't remove it. Big difference

Windows 8/7 Aero isues.

I have an Alienware m17 r1 with the Core 2 Extreme Q3000 processor and the ATI Mobility Radeon HD3870X2 graphics card.
Let me start off by saying that Windows Vista works great with no issues at all.
Windows 8: Has a probelm that when I resume from sleep (open the laptop lid) everything just goes bizerk. I can't log in because the screen keeps on flickering on and off and what not. So I have to manually power down and reboot to get things working straight. After a reboot or fresh boot, everything works perfectly including games and stuff. It is important to not that there are no graphics card drivers for my graphics card for Windows 8, but as you will see with how Windows 7 acts, I don't think thats the issue.
Windows 7: I thought Windows 8 was what was causing the issues, so I downloaded a copy of Windows 7 Enterprise trial. Everything worked fine, I installed all the Windows 7 drivers for my laptop including the most up to date graphics card drivers. I closed the lid, opened it again, and bam, Aero stops working. And I can't fix it. And I also can't use the IE or some other applications. So I reinstalled Windows a few more times once without any graphics drivers except for the Windows one and once with the Alienware provided Windows 7 drivers and still the issue occurs. It also occurs after a fresh boot withouth logging in, closing the lid, and opening it and logging in.
I'm not exactly sure what it going on, although I'm sort of ruling out graphics drivers because in Windows Vista everything works perfectly. I was thinking about disconnecting the CrossFire cable to see if one of my graphics cards is the one having any issues, but I wanted your input first to see what the problem might be.
Other m17 owners seem to have Windows 7 running smoothly, but in my case its just not working.
I should also note that the first time I installed Windows 8, I used up the whole harddrive and eveything was working fine. And then a week later that issue started to happen. I then installed Windows Vista and everything was back to working order. I then decided to dualboot Windows 7 and Aero would just turn off after resuming from sleep. I haven't tried Installing Windows 7 on the whole harddrive yet because I don't think that would fix anything. Currently I'm back to Windows Vista on the whole harddrive. I also have a different BIOS that allows overclocking installed, but the system is not overclocked but rather undervolted from 1.2 to 1.186 if I remember correctly.
Here are the complete specs of the system from My Alienware PC Information:
II. Configuration
Processor(s)
Processor 1
Name: Intel(R) Core(TM)2 Extreme CPU Q9300 @ 2.53GHz
Manufacturer: GenuineIntel
Caption: Intel64 Family 6 Model 23 Stepping 10
Version: Model 7, Stepping 10
Processor Id: BFEBFBFF0001067A
Current Clock Speed: 2533MHz
Address Width: 64Bits
Data Width: 64Bits
Socket Designation: U2E1
Verified Hardware Device against Order: CPU-2.53C2EQX9300
Case Color: New Background
System Memory
Memory Module 1
Capacity: 2048MB
Bank Label: DIMM #1
Mem_Type: DDR3
Mem_Frequency: 1064 MHz
Verified Hardware Device against Order: MEM-MOBLDDR32GBP85EL
Memory Module 2
Capacity: 2048MB
Bank Label: DIMM #2
Mem_Type: DDR3
Mem_Frequency: 1064 MHz
Verified Hardware Device against Order: MEM-MOBLDDR32GBP85EL
BIOS Information
Manufacturer: Intel
Name: Ver 1.00PARTTBL;
Version: W841.B10
Version: ALWARE - 6040000
Motherboard Information
Manufacturer: alienware
Product: alienware
Serial Number: 0123456789012345
Version: alienware
Verified Hardware Device against Order: MB-W84017WUXGABLKPNT
Verify correct motherboard
Power settings optimized
Video Adapter
Caption: ATI Mobility Radeon HD 3870
Adapter RAM: 512MB
DriverVersion: 7.01.01.809
Verified Hardware Device against Order: MOBL-VM88XT512MBR1
Test Video Card
Hard Drive(s)
ST9320421ASG ATA Device
Model: ST9320421ASG ATA Device
Size: 320GB
Total Heads: 255
Total Cylinders: 38913
Total Tracks: 9922815
Tracks Per Cylinder: 255
Verified Hardware Device against Order: MOBL-HD320GB72FSEAR2
Optical Drives / Other Storage
Optiarc DVD RW AD-7561S ATA Device
Operating System: Microsoft Windows Vista Home Premium
DirectX Version: 10
Assembler Initials: RR
Tester Initials: AI
Test Date: 01/28/2009 10:06 AM
Burn-In/Benchmarks
3DMark 2006
Customer Information:
3DMark Score: 14,350.00 3DMarks
SM2.0 Score: 5,438.00
HDR/SM3.0 Score: 7,258.00
CPU Score: 3,721.00
Game Score: 0.00 Points
SM2.0 Graphics Tests
GT1 - Return To Proxycon: 44.83 FPS
GT2 - Firefly Forest: 45.81 FPS
CPU Tests
CPU1 - Red Valley: 1.20 FPS
CPU2 - Red Valley: 1.84 FPS
HDR/SM3.0 Graphics Tests
HDR1 - Canyon Flight: 85.68 FPS
HDR2 - Deep Freeze: 59.47 FPS
Unreal Tournament 3 Demo
Customer Information:
Average FPS: 61.83 FPS
Time Spent Over 30 FPS: 99.93 percent of total benchmark time was spent above 30 FPS
IRQ Configuration
0 System timer
1 Standard PS/2 Keyboard
2 -available-
3 -available-
4 -available-
5 -available-
6 -available-
7 -available-
8 System CMOS/real time clock
9 -available-
10 Intel(R) ICH9 Family SMBus Controller - 2930
11 -available-
12 Synaptics PS/2 Port TouchPad
13 Numeric data processor
14 -available-
15 -available-
16 Generic Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller
16 JMicron JMB36X Controller
16 Intel(R) ICH9 Family USB Universal Host Controller - 2937
17 Ricoh Memory Stick Controller
17 Ricoh SD/MMC Host Controller
17 SDA Standard Compliant SD Host Controller
18 RICOH OHCI Compliant IEEE 1394 Host Controller
18 Intel(R) ICH9 Family USB Universal Host Controller - 2936
19 AVerMedia A317 Mini-Card Hybrid Analog/ATSC
19 Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 1 - 2928
19 Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 2 - 292D
19 Intel(R) ICH9 Family USB Universal Host Controller - 2935
19 Intel(R) ICH9 Family USB Universal Host Controller - 2939
19 Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
21 Intel(R) ICH9 Family USB Universal Host Controller - 2938
22 High Definition Audio Controller
23 Intel(R) ICH9 Family USB Universal Host Controller - 2934
23 Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
190 Microsoft ACPI-Compliant System
Miscellaneous
Realtek High Definition Audio
Device Name: Realtek High Definition Audio
Description: Realtek High Definition Audio
Class: MEDIA
Service: IntcAzAudAddService
Driver Version: 6.0.1.5631
Driver Date: 5-26-2008
Vendor Id: 10EC
Device Id: 0269
Revision: 1000
Verified Hardware Device against Order: SND-VIN3INTHIGHDEFSS
Test Sound Card
Optiarc DVD RW AD-7561S ATA Device
Device Name: Optiarc DVD RW AD-7561S ATA Device
Description: CD-ROM Drive
Class: CDROM
Service: cdrom
Driver Version: 6.0.6001.18000
Driver Date: 6-21-2006
Verified Hardware Device against Order: MOBL-NEC8XDVDRWLSSAT
AVerMedia A317 Mini-Card Hybrid Analog/ATSC
Device Name: AVerMedia A317 Mini-Card Hybrid Analog/ATSC
Description: AVerMedia A317 Mini-Card Hybrid Analog/ATSC
Class: MEDIA
Service: AVerBDA6x_x64
Driver Version: 1.3.64.58
Driver Date: 6-23-2008
Vendor Id: 1131
Device Id: 7160
Revision: 0003
IRQ Number: 19
Verified Hardware Device against Order: MOBL-W840MINIAVERTVT
Intel(R) WiFi Link 5300
Device Name: Intel(R) WiFi Link 5300
Description: Intel(R) WiFi Link 5300
Class: Net
Service: NETw5v64
Driver Version: 12.0.0.78
Driver Date: 5-21-2008
Vendor Id: 8086
Device Id: 4235
Revision: 0000
Verified Hardware Device against Order: NIC-INTELWIREL533AN
Ensure Correct Network Card as invoiced
Final Checks
Inspect machine for exterior defects
Power and data cables connected properly and bundled neatly
Components securely in place with correct type and quantity of screws to prevent short circuiting
System powers on
All fans function
All LEDs function
Ensure BIOS updated
Ensure BIOS boot up sequence runs in proper order
Check for DMI Installation
System settings customized
Application and utility software installed and tested
Correct DirectX version installed
All hardware functions properly
Device drivers installed and tested
Verify Operating System against Order
System burn-in run to ensure system operates at peak efficiency
Run Scandisk
Empty Recycle Bin
Check for CDs in the drives
Test all ports
Run Disk Cleanup
Defrag the System Drive
Ensure Operating system installed, optimized, and purged of any unnecessary programs
Benchmark scores meet performance standards
Shutdown and unplug the system
Plug the system back in and ensure system boots up properly
Repeat previous 2 steps
Shutdown and unplug the systems
Check for Windows sticker Placement
Check for Setup Poster
Check for Customer Support Warranty Information
Ensure all periphials are with system
Mousepad Present
Agent ID card present
Ensure all cables are with system
Ensure all device manuals are with system
Ensure all driver disks are with system
Ensure all software CDs are with system
Ensure correct Recovery CD with system
Check for Power Cord
System cleaned and buffed
System poly-bagged, and packaged with Styrofoam to prevent damage during shipping
No scratches, dents, or other damage on peripherals
Peripherals sealed securely
Shipping box sealed securely
Correct shipping labels placed on peripheral boxes
Correct labels placed on shipping box
Sales invoice present
Shipping manager sign-off
Checklist present
System shipped to the customer
Installed Device Drivers
Microsoft AC Adapter, 6-21-2006, 6.0.6001.18000
Intel(R) Core(TM)2 Extreme CPU Q9300 @ 2.53GHz, 6-21-2006, 6.0.6001.18000
Standard PS/2 Keyboard, 6-21-2006, 6.0.6001.18000
Microsoft ACPI-Compliant Control Method Battery, 6-21-2006, 6.0.6001.18000
Synaptics PS/2 Port TouchPad, 6-20-2008, 11.1.18.0
Microsoft Bluetooth Enumerator, 6-21-2006, 6.1.6001.22000
Bluetooth Hands-free Audio, 5-12-2008, 6.1.0.4600
Bluetooth Hands-free Audio., 5-12-2008, 6.1.0.4600
Bluetooth L2CAP Interface, 1-23-2008, 6.2.0.1200
Bluetooth Remote Control, 5-12-2008, 6.1.0.4600
Bluetooth Stereo Audio, 5-12-2008, 6.1.0.4600
Microsoft eHome Infrared Transceiver, 6-21-2006, 6.1.6001.22000
High Definition Audio Device, 6-21-2006, 6.0.6000.16386
Realtek High Definition Audio, 5-26-2008, 6.0.1.5631
HID-compliant device, 6-21-2006, 6.1.6001.22000
HID-compliant consumer control device, 6-21-2006, 6.0.6000.16386
HID-compliant device, 6-21-2006, 6.1.6001.22000
Microsoft eHome Remote Control Keyboard keys, 6-21-2006, 6.0.6001.18000
Microsoft eHome MCIR Keyboard, 6-21-2006, 6.0.6001.18000
Microsoft eHome MCIR 109 Keyboard, 6-21-2006, 6.0.6001.18000
HID-compliant mouse, 6-21-2006, 6.0.6001.18000
HID-compliant consumer control device, 6-21-2006, 6.0.6000.16386
Optiarc DVD RW AD-7561S ATA Device, 6-21-2006, 6.0.6001.18000
ST9320421ASG ATA Device, 6-21-2006, 6.0.6001.18000
ATI Mobility Radeon HD 3870, 7-24-2008, 8.520.4.0
AVerMedia A317 Mini-Card Hybrid Analog/ATSC, 6-23-2008, 1.3.64.58
Ricoh Memory Stick Controller, 6-16-2008, 6.0.1.12
SDA Standard Compliant SD Host Controller, 6-21-2006, 6.0.6001.18000
RICOH OHCI Compliant IEEE 1394 Host Controller, 6-21-2006, 6.0.6001.18000
Ricoh SD/MMC Host Controller, 6-24-2008, 6.0.3.11
Generic Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller, 12-28-2007, 10.51.3.3
JMicron JMB36X Controller, 5-8-2008, 1.17.37.1
Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 1 - 2928, 1-30-2008, 8.6.1.1001
Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 2 - 292D, 1-30-2008, 8.6.1.1001
Intel(R) WiFi Link 5300, 5-21-2008, 12.0.0.78
ATA Channel 0, 6-21-2006, 6.0.6001.18000
ATA Channel 1, 6-21-2006, 6.0.6001.18000
ATA Channel 0, 6-21-2006, 6.0.6001.18000
ATA Channel 1, 6-21-2006, 6.0.6001.18000
facap, FastAccess Video Capture, 9-24-2008, 8.7.1.0
Microsoft iSCSI Initiator, 6-21-2006, 6.0.6001.18000
Generic volume shadow copy, 6-21-2006, 6.0.6000.16386
AuthenTec Inc. AES1610, 4-17-2008, 7.10.1.0
BCM2046 Bluetooth Module, 5-9-2008, 6.2.0.2600
2.0M Pixel Camera, 6-21-2006, 6.0.6001.18000
Click to expand...
Click to collapse
Sounds like Hibernate is causing the issue. Try turning it off
Open Command Prompt (run as administrator) and type
powercfg hibernate /off
CruciasNZ said:
Sounds like Hibernate is causing the issue. Try turning it off
Open Command Prompt (run as administrator) and type
powercfg hibernate /off
Click to expand...
Click to collapse
That didn't fix it. I reinstalled Windows and tried it.
Actually that command didn't help. I used powercfg -h off . I tries both on and off and Aero still disables. This is in Windows 7 by the way.
Sent from my MB865 using Tapatalk
Do a clean uninstall of your video drivers with something like driver sweeper then reinstall the latest ATI drivers.
If you've tried drivers id strongly suggest you start the way all "odd" tech issues are diagnosed.
Rip out anything none essential, including cross fire, bare bones and start from scratch.
If that works then start adding stuff back in.
if it didn't work then your issue is in whats left, most likely graphics or Moby related, but get back to us after doing the above and we'll go from there.
dazza9075 said:
If you've tried drivers id strongly suggest you start the way all "odd" tech issues are diagnosed.
Rip out anything none essential, including cross fire, bare bones and start from scratch.
If that works then start adding stuff back in.
if it didn't work then your issue is in whats left, most likely graphics or Moby related, but get back to us after doing the above and we'll go from there.
Click to expand...
Click to collapse
I had already tried all that driver stuff before.
Since it's a laptop, I decided to remove the CrossFire cable to no avail and then I started realizing that CrossFire wasn't actually working to begin with. I had noticed it before, but I didn't investigate further. I tried to reseat the CrossFire cable multiple times to no avail. The one time it did work, I restarted the computer and the second card disappeared.
So I hit some other forums for more info and one said that if I was having CrossFire issues, I should flash a different BIOS. So I flashed the stock Alienware BIOS and bam! Aero got fixed. So that got rid of that problem. Although I'm still stuck with no CrossFire. Removing the cable and putting it back in 10 or so times will get the second card to show up and then disappear again after a restart. According to my understanding, two cards have to show up in device manager when CrossFire is "working". So thats the only problem I have now, otherwise I've been using Windows 7 Enterprise for 2 days now playing Saints Row: The Third for a solid 5 hours with no crashes or anything. Although I'm still missing out on the performance of the second card.
Any ideas to troubleshooting this?
Sent from my MB865 using Tapatalk
Possibly the drivers?
I have three different machines with sort of similar problems. The Aero basically ****s up. It seems to be an issue with the latest ATI Drivers. I am using the version 11 I believe not the latest. That seems to be helping.
twistedR said:
I have three different machines with sort of similar problems. The Aero basically ****s up. It seems to be an issue with the latest ATI Drivers. I am using the version 11 I believe not the latest. That seems to be helping.
Click to expand...
Click to collapse
In Windows Vista the latest drivers worked fine. I haven't tried the latest ones on this computer yet, but my desktop does have the latest and it works just fine.
Sent from my MB865 using Tapatalk
Oh, I should have mentioned that I am running windows 7 on all three.

rEFInd on the Toshiba Encore WT8-A32

I have managed to boot to rEFInd on my Toshiba Encore in preparation for booting Ubuntu from a microSD card natively. I have not written up a guide yet from my notes because I don't think there will be much demand for this here on XDA. If enough people want to do this, I will turn this post into a guide. This boots directly from the UEFI partition with no USB stick needed. You DO need a USB stick to do the actual install.
Toshiba Encore booting to rEFInd: http://postimg.org/image/4lx3mnxzr/
Toshiba Encore booting to Grub2: http://postimg.org/image/p3rgtpqkp/
__________________________________________________________________________
Installing Ubuntu 14.10 to a microSD card on the Toshiba Encore:
Note: There are many problems right now with Ubuntu on the Encore. Touchscreen driver is broken as of kernel version 3.16. It's some kind of regression bug in the atmel-maxtouch driver(here is a program to debug our touchscreen: https://github.com/atmel-maxtouch/obp-utils).
You will need to prepare with:
A USB stick to do the install
Ubuntu 14.10 64 bit ISO(Daily build) http://cdimage.ubuntu.com/daily-live/current/
A microUSB OTG cable(if you use the StarTech cable mentioned below then you don't need this)
A high speed microSD card(Partitioned: 200MB FAT32 EFI partition, a large EXT4 partition, and a swap partition). I used this(was $21 on sale) http://www.amazon.com/gp/product/B00IVPU894/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
A Linux box to compile the latest versions of a few programs used to boot into Grub2 and Ubuntu. I will post the compiled versions but you should compile them yourself for security reasons.
Read this to get an idea what's needed to get rEFInd installed: http://www.rodsbooks.com/refind/installing.html#windows (there are extra steps not listed there)
The install will go from the usb stick booted from rEFIind to the microSD card. The Samsung PRO I am using only does ~20MBps so I'm guessing that is a hardware limit. I did the install without a swap partition and Ubuntu was unusable after opening up 4 or more programs so I added a swap partition to the end of my microSD card.
Getting rEFInd booting:
Turn off Secure Boot in the Encore bios. It should be possible to boot Ubuntu from a USB stick without turning off Secure Boot but I doubt it will ever be possible to do from a microSD card because the Toshiba Encore has no option to boot from a microSD card in the bios boot options.
Get rEFInd here: http://www.rodsbooks.com/refind/getting.html
Run these commands in an elevated permissions Windows command shell:
powercfg /h off
manage-bde -status c: (checks bitlocker status)
powershell
PS C:\> Disable-BitLocker -MountPoint "C:"
manage-bde -status c: (after above command finishes, makes sure your disk is really decrypted.)
Then follow this: http://www.rodsbooks.com/refind/installing.html#windows
All the commands are explained on rodsbooks website except disabling Bitlocker. This is optional but if something goes wrong along the way, you might find Windows 8 encrypted and unbootable.
Note: The command: "bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi" to get rEFInd set as the default EFI boot program did not take the first time I did it. You might have to run that commend a few times rebooting each time until your tablet boots into rEFInd. Once it does, you will see a graphic to boot Windows 8. I suggest changing rEFInd to text mode so that you can use the VOL UP, VOL DOWN, and Windows button(as enter) to scroll through the boot options. Use "textonly" option in the rEFInd config file to set this: http://www.rodsbooks.com/refind/configfile.html#adjusting
Installing Ubuntu(bleeding edge) 14.10:
Touchscreen does not work yet so I will update this section when I get it working.
_________________________________________________________________________
If you want to have power to your tablet and USB OTG access at the same time, here is what you need(both Amazon prime eligible):
http://www.amazon.com/gp/product/B0047AALS0/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
http://www.amazon.com/gp/product/B00KQES55M/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 (Any usb gender bender like this will do...there are cheaper ones)
Attach the USB gender changer to the black end of the StarTech cable and the attach a USB hub to the other end of the gender changer. Plug the red end into a 2.1 amp USB power source and the microUSB end into the Encore. Now the tablet will say "plugged in, not charging". You can now attach any USB device to the hub and Windows or Linux with see them. The tablet will have power but the battery will not charge.
bads3ctor said:
I have managed to boot to rEFInd on my Toshiba Encore in preparation for booting Ubuntu from a microSD card natively. I have not written up a guide yet from my notes because I don't think there will be much demand for this here on XDA. If enough people want to do this, I will turn this post into a guide. This boots directly from the UEFI partition with no USB stick needed.
Toshiba Encore booting to rEFInd: http://postimg.org/image/4lx3mnxzr/
Toshiba Encore booting to Grub2: http://postimg.org/image/p3rgtpqkp/
Click to expand...
Click to collapse
Hi
I wanna boot ubuntu on my encore Can You write the instructions how to, step by step?
Nice, not sure how many others own this tablet, the Venue 8 Pro seems more popular. But I bought an Encore for the microHDMI so I would love to see a guide.
Thank You, I would love to see a guide also, I own a Toshiba encore 32gb
Touch working? Wifi?
Thanks for posting the guide though!
Touchscreen driver works but needs calibration
SebMKd said:
Touch working? Wifi?
Thanks for posting the guide though!
Click to expand...
Click to collapse
Touchscreen bug:
Code:
i2c_hid i2c-ATML1000:00: failed to retrieve report from device.
Supposed to be fixed in kernel version 3.16 but so far in Ubuntu 14.10(kernel 3.16.0-23) TS is still broken. Internal WIFI works with a few tweaks. I am using a USB Atheros WIFI device for now.
I am running Windoze 8 and every few weeks I update Ubuntu 14.10 to see if the touchscreen works. I used to hack away at bleeding kernels to fix bugs like this but I am just going to wait for the Linux kernel devs to fix the touchscreen driver.
Edit: Booted into Ubuntu 14.10 after updating to the newest kernel and:
dmesg | grep i2c-ATML
[ 8.053603] input: ATML1000:00 03EB:8C12 as /devices/platform/80860F41:05/i2c-5/i2c-ATML1000:00/0018:03EB:8C12.0005/input/input6
Touchscreen works but is badly calibrated and the Unity side bar refuses to appear when the mouse is pushed to the left side of the screen. Not a very good trade-off! On the bright side, the former useless USB keyboard windows key now brings up the Unity sidebar.
Code:
[email protected]:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MOSART Semi. 2.4G Wireless Mouse id=9 [slave pointer (2)]
⎜ ↳ ATML1000:00 03EB:8C12 id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Logitech USB Keyboard id=7 [slave keyboard (3)]
↳ Logitech USB Keyboard id=8 [slave keyboard (3)]
↳ gpio-keys id=11 [slave keyboard (3)]
↳ gpio-keys id=12 [slave keyboard (3)]
[email protected]:~$ xinput list-props 10
Device 'ATML1000:00 03EB:8C12':
Device Enabled (130): 1
Coordinate Transformation Matrix (132): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (253): 0
Device Accel Constant Deceleration (254): 1.000000
Device Accel Adaptive Deceleration (255): 1.000000
Device Accel Velocity Scaling (256): 10.000000
Device Product ID (248): 1003, 35858
Device Node (249): "/dev/input/event5"
Evdev Axis Inversion (257): 0, 0
Evdev Axis Calibration (258): 1271, 1282, 3196, 3115
Evdev Axes Swap (259): 1
Axis Labels (260): "Abs MT Position X" (280), "Abs MT Position Y" (281), "None" (0), "None" (0)
Button Labels (267): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (136), "Button Wheel Down" (137)
Evdev Scrolling Distance (261): 0, 0, 0
Evdev Middle Button Emulation (268): 0
Evdev Middle Button Timeout (269): 50
Evdev Third Button Emulation (270): 0
Evdev Third Button Emulation Timeout (271): 1000
Evdev Third Button Emulation Button (272): 3
Evdev Third Button Emulation Threshold (273): 20
Evdev Wheel Emulation (274): 0
Evdev Wheel Emulation Axes (275): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (276): 10
Evdev Wheel Emulation Timeout (277): 200
Evdev Wheel Emulation Button (278): 4
Evdev Drag Lock Buttons (279): 0
Edit2: Here is the problem....the coordinates for calibration are off because the tablet is attached to an external monitor:
Code:
[email protected]:~$ xrandr
Screen 0: minimum 8 x 8, current 3200 x 1080, maximum 32767 x 32767
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 983mm x 576mm
1920x1080 60.0*+ 50.0 59.9 30.0 25.0 24.0 30.0 24.0
1920x1080i 60.1 50.0 60.0
1600x900 60.0
1280x1024 60.0
1360x768 60.0
1280x720 60.0 50.0 59.9
1440x576i 50.1
1024x768 60.0
1440x480i 60.1 60.1
800x600 60.3
720x576 50.0
720x480 60.0 59.9
640x480 60.0 59.9
DP1 disconnected (normal left inverted right x axis y axis)
DSI1 connected 1280x800+1920+0 right (normal left inverted right x axis y axis) 0mm x 0mm
800x1280 60.0*+
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
very interesting. It's what I need :good:
Any more news on this?
I managed to install Refind. Also, I managed to install ubuntu on sdcard. But in Refind not appears Ubuntu. How I can edit Refind to search the OS on sdcard?
Thanks!!
PainToad said:
Any more news on this?
Click to expand...
Click to collapse
Sorry for not getting back earlier on this but I wanted to exhaust all options before giving up on running Ubuntu on this tablet. The deal killer turns out to be the MicroSD card bandwidth. From what I can tell from the tests I have done while running Ubuntu from the MicroSD card, the BIOS is set to run the SD bus in DDR25 mode with no option to set it to DDR50 mode. DDR25 mode maxes out at about 18 MB/Sec and this is causing Ubuntu to lockup when disk I/O gets saturated.
With no option in the BIOS to set the SD bus to DDR50 mode, it is effectively a hardware limitation preventing Ubuntu from running properly.
bads3ctor said:
If you want to have power to your tablet and USB OTG access at the same time, here is what you need(both Amazon prime eligible):
http://www.amazon.com/gp/product/B0047AALS0/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
http://www.amazon.com/gp/product/B00KQES55M/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 (Any usb gender bender like this will do...there are cheaper ones)
Attach the USB gender changer to the black end of the StarTech cable and the attach a USB hub to the other end of the gender changer. Plug the red end into a 2.1 amp USB power source and the microUSB end into the Encore. Now the tablet will say "plugged in, not charging". You can now attach any USB device to the hub and Windows or Linux with see them. The tablet will have power but the battery will not charge.
Click to expand...
Click to collapse
I have a question. This method won't be charging my tablet, so my battery won't be destroyed?
BTW another question. Why card reader in this tablet is that slow? I have sandisk extreme micro sd (64MB/s write - ~ 60MB/s in my PC card reader) but reader in toshiba can only read/write ~26MB/s. I thought that this card will be great for my tablet, but now I fell like I wasted my money. I could better buy standard class 10 micro sd card...
rascal0pl said:
I have a question. This method won't be charging my tablet, so my battery won't be destroyed?
Click to expand...
Click to collapse
The tablet will receive a charge but the battery will not be charged. If your battery is at 100% then it will stay at 100%.
rascal0pl said:
BTW another question. Why card reader in this tablet is that slow? I have sandisk extreme micro sd (64MB/s write - ~ 60MB/s in my PC card reader) but reader in toshiba can only read/write ~26MB/s. I thought that this card will be great for my tablet, but now I fell like I wasted my money. I could better buy standard class 10 micro sd card...
Click to expand...
Click to collapse
It is an internal firmware limitation. There is supposed to be a BIOS setting to set the SD slot to a higher bandwidth level but this tablet does not have that option in the BIOS.
Card Reader of Bay Trail tablets is broken
The Card Reader of Bay Trail tablets is slow because is broken, no linux boot and is a read-only device with stock linuxes. You can patch the kernel and install some boot stuff in new partitions of Windows disk, but you can't boot from microSD. I also installed Android x86 and run fast, Android 4 and 6 stable versions, but I couldn't activate sound nor battery status. At least for my research, until today, if you have the 32 GB disk is very difficult you can play with dual boot, Windows is slow and wastes the hard disk, tablet mode of windows has no attractive (while Android is near perfection) and desktop mode is not friendly for touch-screen use, but for now it is stable and all the other tablet's devices works (touchscreen, GPS, Bluetooth, cameras, sensors, miracast), the battery management in this Atom environment has issues with linux and under Windows this x86 system doesn't seem so far away from ARM efficiency. I installed many GPL portable Windows applications in a minimal disk space, so for now linux and Android are worse for this tablet that seemed created for a Microsoft's skinhead.
UEFI boot
I forgot I have a 10 inches version of this tablet, 32 GB, Windows 10 32 bits upgrade (first upgrade) and BIOS 2.0
UEFI multi-boot is not so difficult with: rEFInd, easyUEFI Windows application (because Windows changes boot order), linux's Unetbootin for USB boot, bootia32.efi archive for some linux's installations (Ubuntu-gnome 16.04.1 64 bits requires at least 7-10 GB and swap, may be 32 bits is a bit better because it's less RAM hunger), ... before tests, you have to disable Windows's Bitlocker encryption (AES-128 Windows disk software encryption for this model of the Atom processor, I think without hardware assistance, that it's seamless for the user because UEFI includes shared key, if disk key is deleted Microsoft online user account stores a large password), secure boot, fast boot, windows session identification (Microsoft online authentication sometimes locks session start, probably cause some autocheck of a efi boot manipulation... may be was "default_selection" option of rEFInd for booting last selected OS), backup efi boot partition (copy the files after mount partition)... then I gparted the Windows disk form USB (with no data loss).
And if someone can the microSD boot, Raspberry Pi community recommends Samsung EVO+ 32 GB, for about 10 $/€ (be warned about scam versions), with the best by far random IO, far less from 20 MB/s, but may be important for linux, although I don't know if max random IO of the card reader had been reduced too (most probably yes... and a lot).
Another chance is wubi EFI, a Ubuntu Windows installer that now supports UEFI 32 bits (the non approved by free-software community secure boot only with UEFI 64 bits), this install linux in a big file (resizable) of a NTFS Windows disk (again microSD doesn't boot, it requires a rEFInd's Card Reader firmware and is not available) and linux runs in loop mode inside this file. I installed Ubuntu-gnome 64 bits and 32 bits (in this case the installer requires a command-line option). UEFI32 too requires EasyUEFI and secure boot and bitlocker disabled, I utilized a USB wifi stick (TL-WN722N) until internal wifi was configured... I found lots of issues, including slow internal-wifi, soundcard, battery status, processor stepping and hangs, and other users's solutions for different tablets have not always worked... then no usability research here. Anyway, wubi is not the best way to install linux, although it works and it's easy, and Windows complain less.
A last possibility for linux could be VirtualBox 32 bits, this supports microSD use and Atom processor includes hardware assistance supporting even linux 64 bits. Virtualize linux on this tablet is very slow and touchscreen is a pain.
After some time I returned the tablet to its original state with no data loss*, USB boot still there or the install in a fast (if well chosen) microUSB 3.0 stick or microSD-adapter... but no charger without the use of a less portable, and manipulation disconnections, cable adapter. I utilized a cheap "octopussy" cable from China (3 USB 2.0+ microUSB for charge... 3-4 $/€ or less), but this tablet is incompatible for simultaneous operation (USB OTG+charge), it don't charge while USB use and only I can do slow charge with a tricky: connect with charge mode, change to OTG mode and connect USB devices (warning: some Amazon's users report issues or damages in other tablets).
*bitlocker key changed with a new online password stored for recovery, and Toshiba recovery (Bios option) was broken, may be caused by gparted or some UEFI boot application or some of the installed OS, who knows... normal fixes solutions don't work, although windows own recovery partition worked. Toshiba utilizes a particular EFI directory and Windows doesn't repair it, I copied Toshiba BCD backed up file or, in case it doesn't work, BCD file from Windows recovery boot directory (may be a normal fixboot is required first).
Bug issues under Windows 10 update
After some time of use this tablet suffers issues, cause of its Bay Trail buggy platform, under Windows 8.1 and 10 (worse): Wifi disconnections and poor speed, laggy applications and touchscreen sometimes is unresponsive, miracast disconnections and choppy sound, although the whole system doesn´t hang. I did try linux last updates from http://linuxiumcomau.blogspot.com.es/ and now most work better (July 2017), probably in a short time I will uninstall Windows 10.

Android Emulator Performance is Extremely Unstable

First of all, hopefully this is the right place to post this type of question - if it isn't, do let me know.
I have a relatively new PC with 16 GB RAM, 10th Gen Core i3, 4 physical and 4 virtual cores (hyperthreading), I do not have an SSD. It runs Linux Mint and uses the KVM.
The first year or so after buying my computer, the emulator worked great - it was fast and I was having a great time working on my apps.
A couple of weeks ago, I realized that the emulator would occassionally become slower (around 50-60 percent, to be exact) for around a minute or two, before then becoming very fast for around 1-3 minutes.
It's very strange, it goes like so:
- Boot up emulator
- Starts off blazingly fast
- 2 minutes later it suddenly drops by around 50-60 percent in speed for around 1-2 minutes
- Becomes blazingly fast again for some time
(I sometimes use AOSP emulators, but in this case I will just give an example of the Google API emulator.)
This is incredibly frustrating - I use the emulator so many times, and I have a relatively new PC.
PC info:
```
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i3-10105 CPU @ 3.70GHz
CPU family: 6
Model: 165
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
Stepping: 3
CPU max MHz: 4400.0000
CPU min MHz: 800.0000
BogoMIPS: 7399.70
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art
arch_perfmon pebs bts rep_good nopl xtopology nonstop_
tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cp
l vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsav
e avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault
epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase t
sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed a
dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsa
ves dtherm ida arat pln pts hwp hwp_notify hwp_act_wind
ow hwp_epp md_clear flush_l1d arch_capabilities
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 1 MiB (4 instances)
L3: 6 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Itlb multihit: KVM: Mitigation: Split huge pages
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Mitigation; Clear CPU buffers; SMT vulnerable
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer
sanitization
Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB fillin
g
Srbds: Mitigation; Microcode
Tsx async abort: Not affected
```
Things I've tried:
- allocate more RAM to the emu (5 GB and 8 GB) it actually felt slower and more incosistent with more ram
- turn off other programs
- different tweaks (none of which worked)
I am looking for help as to how I can improve the emulator speed, as it feels as though you need some sort of NASA computer or 32 GB RAM Core i9 12th generation with an RTX 3090 these days to actually get **consistent** QEMU performance - very frustrating!
Any help would be appreciated -- the only fault I can think of with my PC is that I'm using a HDD, which may or may not be the root cause of this issue.

Categories

Resources