Page 2 of 2 FirstFirst 12
Results 21 to 31 of 31
Like Tree18Likes
  1. #21  
    Quote Originally Posted by Sumy View Post
    Does it shows you when you look under "more info" is it HSTNH-I32C or HSTNH-I33C and what is hardware version or you have no such information, sometimes they forgot to put that too

    I guess the first two numbers (below) were ment for pre-production units, so only FB386UA and FB398UA were ever used with EVT and DVT units
    FB386UA#ABA - 16GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (Asia)
    FB398UA#ABA - 32GB Wi-Fi w/ 4G LTE Sierra Wireless data card - voice/sms capable (Asia)
    FB438UA#ABA - 16GB Wi-Fi (US, EU, Retail)
    FB439UA#ABA - 32GB Wi-Fi (US, EU, Retail)
    FB441UA#ABA - 32GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (ATT, US Retail)
    FB446UA#ABB - 32GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (EU, Retail)
    Missing Wifi+Gps version Go device....
  2.    #22  
    Quote Originally Posted by lemanho View Post
    Missing Wifi+Gps version Go device....
    I think that's FB396UA-EVT3 / HSTNH-I31C for 16GB
    HP Veer (daily driver), HP Pre 3, HP Touchpad Proper 4G/LTE (Sierra MC7710), HP Touchpad 32GB WiFi, Palm Pre 2
  3. #23  
    Quote Originally Posted by Sumy View Post
    Does it shows you when you look under "more info" is it HSTNH-I32C or HSTNH-I33C and what is hardware version or you have no such information, sometimes they forgot to put that too

    I guess the first two numbers (below) were ment for pre-production units, so only FB386UA and FB398UA were ever used with EVT and DVT units
    FB386UA#ABA - 16GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (Asia)
    FB398UA#ABA - 32GB Wi-Fi w/ 4G LTE Sierra Wireless data card - voice/sms capable (Asia)
    FB438UA#ABA - 16GB Wi-Fi (US, EU, Retail)
    FB439UA#ABA - 32GB Wi-Fi (US, EU, Retail)
    FB441UA#ABA - 32GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (ATT, US Retail)
    FB446UA#ABB - 32GB Wi-Fi w/ 3G/4G HSPA+ Ericsson data card (EU, Retail)

    It says HSTNH-132C. Interesting there are so many variants. Makes you wonder how few of each actually exist.
    Devices: Pre3 16GB (AT&T - webOS 2.2.4) | White TouchPad 4G 32GB (AT&T - webOS 3.0.5 + LunaCE)
    Remy X and Herrie like this.
  4. #24  
    I have a few sitting here, but I can't guarantee that their stickers match their internals:

    FB386UA-DVT "Config A" - APQ8060 (64MB) Rev 2 1.5Ghz, eMMC 32G Sandisk 4.3+, LPDDR2: 1GB Samsung, TI A6: v3.7, NFC IC: NXP, PCB: UMT, Antenna: Amphenol, Touchpanel: TPK + SZLens, Ericsson 3G module (/361 R1C CS)

    FB396UA-DVT "Config E" - APQ8060 (64MB) Rev 2, 1.5Ghz, eMMC: 16G Sandisk 4.3+, LPDDR2: 1GB Samsung, TI A6 *1: v3.7, No stuffing 3G parts, No mPCIE Connector, No P-sensor FPC, PCB: UMT, Antenna: Amphenol, Touch panel: TPK + SZLens, No WWAN antenna, NO GPS module + Bracket, Back cover 2 coat
    Author:
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    GO OPEN WEBOS!
    People asked me for a donate link for my non-catalog work, so here you are:
    Remy X likes this.
  5. #25  
    Quote Originally Posted by cbosdell View Post
    Thanks! Mine says FB386UA-DVT but I have a 32GB 4G variant. Interesting. Guess I'm no help with the EVT1 problem though.
    Quote Originally Posted by cbosdell View Post
    Probably a stupid question but how can you tell which one you have?
    also using novacom if device can not boot in to WebOS
    enter recevery Novacom bootie (vol up + power on)

    novacom -t open tty:// than press enter
    type printenv and enter
    and you get something like this, look under boardtype

    printenv
    T ? = -2
    T framebuffer = 0x7f600000
    T chargebypass = 1
    T boot_battery_threshold = 0x3
    T klog_len = 0x100000
    T klog_addr = 0x7ff00000
    T tablet_wod_support = 0x0
    T extended_timeout = 0x0
    T chainbootdevice = mmc0
    T bootaddress = 0x41000000
    T bootdevice = mmc0p15
    T bootfile = uImage
    T bootfs = ext2
    T bootargs-ramdisk = root=/dev/ram0 rw
    T bootargs = root=/dev/mmcblk0p16 rootwait ro
    T autoboot = fsboot
    T boardtype = opal-3G-dvt1
    T opal.lcd = hitachi
    Remy X likes this.
  6. #26  
    Funny. Showing some black label of back case ....

    Config A .FB386UA-DV1. CPU APQ8060(64MB) Rev2 1.5Ghz. eMMC 32GB Sandisk 4.3+. LPDDR2 1GB Samsung. T1A6 v3.7.NFC IC NXP. PCB UMT. Antenna Vendor Amphenol. Touch Panel TPK+SZLens. Ericsson 3G module (/361 R1C CS)

    Conf B. FB386UA-EVT3. CPU APQ8060 1.5Ghz. eMMC 16G Sandisk. LPDDR2 1GB Samsung. T1 A6 v3.7. NXP NFC IC. Ericssion 3G module. Antenna Yageo. TP with SZLens glass.Case don't care cosmetic. B-grade display. PCB vendor UNT.

    Config C. FB396UA-DVT-EU. CPU APQ8060 (64MB) REv2 1.5Ghz. eMMC 16GB Sandisk 4.3+. LPDDR2 1GB Samsung. T1 A6 v3.7 NFC IC NXP. No Stuffing 3G Parts. PCB UMT. Antenna Vendor Amphenol. Touch panel TPK+SZLens. NC WWAN atenna. GPS module Bracket.

    Conf D. FB386UA-EVT4. CPU APQ8060 (64MB) Rev 2 1.5Ghz. eMMC 64GB Toshiba 4.4 (32nm). LPDDR2 1GB Samsung. T1 A6 v.37. NFC IC NXP. PCB UMT. Proximity Sensor. TP with SZLens glass. Ericssion 3G module (/361 CS). Antenna Amphenol. Case don't care cosmetic.

    Conf E. FB398UA-EVT3. CPU APQ8060. eMMC 32GB Sandisk. LPDDR2 1GB Samsung. T1 A6 v3.7. NXP NFC IC. Sierra LTE module MC7700. Antenna Amphenol. TP with SZLens glass. Case don't care cosmetic. PCB Vendor UMT.....LTE MC7700 device

    Cod F. FB396UA-EVT3. CPU APQ8060 1.5Ghz. eMMC 16GB Sandisk. LPDDR2 1GB Samsung. T1 A6 v3.7. NXP NFC IC. No stuff for Wifi + GPS. No WWAN atenna. Antenna Amphenol. TP with corning glass. GPS module +Bracket. Case don't care cosmetic. PCB vendor Unitech.......GPS device

    Config E. FB396UA-DVT-Lo. CPU APQ8060 (64MB) Rev2 1.5Ghz. eMMC 16GB Sandisk 4.3+. LPDDR2 1GB Samsung. T1 A6 v3.7. No Stuff 3G parts. No mPCIE connector. No P-sensor FPC. PCB UMT. Antenna vendor Amphenol. Touch panel TPK+SZLens. No WWAN atenna. No GPS module+Bracket. Back cover 2 coat.

    FB386UA-EVT CPU Qualcomm APQ8060 (64MB) Rev2. eMMC Sandisk 4.3+ SDIN4C2-16G. Memory DDR2 Samsung K4P8G304EC-FGC1. IC Power Management T1 A6 v3.5A. Display: Hitachi 6.95 Display TX18D42VMOEAA. Touch Panel TPK-Corning Glass TCP-70B21. Battery STL 1S1P 2HPOOBP1C06G1A1. 3G module Ericsson KRD131 18/261/. Webcam Chicony CBFA1A3. Antenna Amphenol. Back cover for Square w/o square coil.
    Sumy likes this.
  7. #27  
    Quote Originally Posted by Herrie View Post
    They way I understood it from John Steffes is that the 1cm offset is caused by a different version of the TruTouch board to which the touchpanel is connected. This one is close to the mainboard, but it's a separate board. That explains your findings. I had the same. So far no solution for the 1cm. I'm sure there must exist a proper firmware somewhere to address it, just I haven't found it yet.....
    Wow I never saw this thread...

    I have been working on this for a while for a user of a Go, tried so many different things, customized firmware (webOS 3.0, 3.0.3, 3.0.4, and 3.0.5, Android from Touchpad/Touchpad 4G/Touchpad 4G other TruTouch hex files I have found inside Android builds including versions for Touchpad) etc... Have never gotten rid of 1CM off...

    But to add to what I have tried, I have access to a few Go's 1 EVT3 16G and 1 EVT3 32G and 1 EVT1 16G.

    Thought it might have to do with tokens, attempted to flash working tokens to device that had 1CM, it did not work, restored original tokens. (this was the most promising as the below tests)

    Only thing I can confirm.. Take EVT3 TruTouch Board put in EVT1 device, 1CM goes away, put EVT 1 TruTouch board into EVT3 device 1CM is also gone...

    Put EVT1 TruTouch board in EVT1 device 1CM is there...

    So maybe that will help? I have taken a break for a while, this was all from my memory, so I will have to look at my notes and review...

    Happy Thanksgiving if you live in USA...
    Last edited by John Steffes; 11/28/2014 at 08:53 AM.
    Mutoidi, Remy X and Sumy like this.
  8. #28  
    Only thing I can confirm.. Take EVT3 TruTouch Board put in EVT1 device, 1CM goes away, put EVT 1 TruTouch board inbto EVT3 device 1CM is also gone...

    Put EVT1 TruTouch board in EVT1 device 1CM is there...

    That's right. But I take a EVT 1 TruTouch Board (From andriod 2.2.1 Go device) and connect to DVT mainboard (Webos3.0.5 Go device). And flashed it to webos 3.0.5 with NDI . Also select to force touch panel. Still show 1CM off in the final...
    Sumy likes this.
  9. #29  
    Quote Originally Posted by lemanho View Post
    Only thing I can confirm.. Take EVT3 TruTouch Board put in EVT1 device, 1CM goes away, put EVT 1 TruTouch board into EVT3 device 1CM is also gone...

    Put EVT1 TruTouch board in EVT1 device 1CM is there...

    That's right. But I take a EVT 1 TruTouch Board (From andriod 2.2.1 Go device) and connect to DVT mainboard (Webos3.0.5 Go device). And flashed it to webos 3.0.5 with NDI . Also select to force touch panel. Still show 1CM off in the final...
    Again I was going from memory, but with the EVT1 TruTouch board I have (I have two of them), if I put them into the EVT3 device, all 1CM goes away, does not matter if flashed to webOS 3.0.5 or not... but I will have to review my notes... Again... it has been a long time testing this and that...

    I am not near my notes (as it is thanksgiving in the USA) but when I get the time I will review...
    Last edited by John Steffes; 11/28/2014 at 08:54 AM.
    Remy X, Sumy and MartinH@webos like this.
  10. #30  
    when I fixed some dead touchpad Go devices.Like replace screen/mainbard/touchboard connector...Most of result the fixed device will lost touch function. Need to upgrade or downgrade it and force touchboard.

    One interested thing if replace a andriod 2.2.1/2.2.3/2.3.3 Go mainboard. The touch function is OK no problem.....
  11. #31  
    I found that engineers which were putting tokens in to devices also made some mistakes like specifying too little or to much memory (FlashSize 16G, but it was 32G device or 32G, but it was 16G device)

    I have some early stage Go tokens from EX-HP guys.(Underground) Try to find it.....................

    Try to use NDI to flash device. Do not select " Skip Format of Media Pattition". Also creat a some extra MB on "Extra Root Partition Space" if you want....It will get real 16G/32G/64G in the device.

    For example to flash a 32GB touchpad. Flashing webOS 3.0.0 tar files will get over 29G space. Flashing webOS 3.0.5 tar files will get 27G space only...
    Last edited by lemanho; 11/29/2014 at 02:17 PM.
    Mutoidi and Sumy like this.
Page 2 of 2 FirstFirst 12

Similar Threads

  1. WebOS App Request: iGrann (blackberry instagram client) for WebOS.
    By PalmPixi_User23 in forum webOS Development
    Replies: 3
    Last Post: 03/27/2014, 10:57 PM
  2. Replies: 10
    Last Post: 08/20/2011, 02:39 AM
  3. Replies: 7
    Last Post: 03/06/2011, 05:45 AM
  4. Replies: 0
    Last Post: 12/21/2010, 04:51 PM
  5. Replies: 9
    Last Post: 06/15/2009, 07:45 PM

Posting Permissions