Guest KonstaT Posted September 3, 2014 Report Posted September 3, 2014 (edited) I wrote a simple app that pulls some information for individual hardware components on ZTE Open C / Kis 3 / variants. It doesn't require any special permissions and it simply fetches the information from kernel nodes ZTE has kindly put in place. :) Kis3Info-v0.7.5.apk http://konstakang.com/devices/kis3/Kis3Info I'd appreciate if you'd post the model of your device (Open C, Kis 3, V811W, MEO/Moche Smart A16, Beeline Smart2, ZTE V811, Skinny V811, Optus Hop Smart, etc), county/place of purchase and screenshots of the app. Android has a native screenshot functionality and you capture a screenshot by using volume down + power key combination. Here's screenshots from my device (Open C, UK eBay): Edited January 8, 2017 by KonstaT
Guest KonstaT Posted September 3, 2014 Report Posted September 3, 2014 17.3. 2015 v0.7.5: use material design (on Lollipop API level 21) add partition size info add modem version info (only visible when running CM builds) more descriptive sensor info 4.11. v0.5 add partition layout info (Open C vs. Kis 3) 31.10. v0.4.1: small layout update 18.10. v0.4: add ambient light/proximity sensor info 14.9. v0.3: add settings menu use proper versioning (requires uninstalling previous version first) 6.9. v0.2: more touchscreen information 3.9. v0.1: initial release
Guest hecatae Posted September 4, 2014 Report Posted September 4, 2014 my zte open c is identical to yours Konstat.
Guest okmikel Posted September 5, 2014 Report Posted September 5, 2014 My phone (open C, Amazon DE) is identical too except ro.boot.hwversion, I have "wkzA.4" there.
Guest KonstaT Posted September 5, 2014 Report Posted September 5, 2014 Thank you both for testing. I'm not sure what ro.boot.hwversion property is and if it's used for anything. I think it's some value passed from the bootloader so it might also depend on flashed stock firmware version.
Guest spalock Posted September 14, 2014 Report Posted September 14, 2014 Sorry if that question sounds stupid: your app only works under android right?
Guest KonstaT Posted September 14, 2014 Report Posted September 14, 2014 Sorry if that question sounds stupid: your app only works under android right? Yeah, it's an Android app. You can get the same info on Firefox OS (well, on Android too) with few commands in shell. cat /proc/driver/accel cat /proc/driver/alsprx cat /proc/driver/camera_id_back cat /proc/driver/emmc cat /proc/driver/lcd_id cat /proc/driver/ts_information getprop | grep ro.boot.hwversion
Guest spalock Posted September 14, 2014 Report Posted September 14, 2014 (edited) From E.Leclerc (FR): cat /proc/driver/accel 0x33 cat /proc/driver/camera_id_back BACK Camera ID:GALAXYCORE,GC2235, 2M Bayer sensor cat /proc/driver/emmc HYNIX H9DP32A4JJMCGR 4G eMMC cat /proc/driver/lcd_id IC:ILI9806C+TXD; Glass:CMI; Resolution:480*800 cat /proc/driver/ts_information name : goodix i2c address : 0x5d IC type: goodix GT9137 firmware version : 9137_1030 module : JianBang-9137 getprop | grep ro.boot.hwversion [ro.boot.hwversion]: [wmfA.4] It looks like only the touch screen differs from yours. Edited September 16, 2014 by spalock
Guest Pipotron3000 Posted September 21, 2014 Report Posted September 21, 2014 ZTE Open C FR (they are all dark blue) from Materiel.Net : cat /proc/driver/accel 0x33 cat /proc/driver/camera_id_back BACK Camera ID:GALAXYCORE,GC2235, 2M Bayer sensor cat /proc/driver/emmc HYNIX H9DP32A4JJMCGR 4G eMMC cat /proc/driver/lcd_id zte(ILI9806C)_wvga_4.0Inch cat /proc/driver/ts_information name : goodix i2c address : 0x5d IC type: goodix GT9137 firmware version : 9137_1030 module : JianBang-9137 getprop | grep ro.boot.hwversion [ro.boot.hwversion]: [wkzA.4] If it can help ;)
Guest hylli Posted September 22, 2014 Report Posted September 22, 2014 (edited) @KonstaT: I have the same version as you on your screenshot. I bought it from German Amazon Marketplace from this market: http://www.amazon.de/gp/aag/main?ie=UTF8&asin=&isAmazonFulfilled=&isCBA=&marketplaceID=A1PA6795UKMFR9&orderID=&seller=A1VPA58JLEVNOC Hylli :) Edited September 22, 2014 by hylli
Guest ipk1 Posted January 11, 2015 Report Posted January 11, 2015 (edited) Here's the screenshots from the KIS3 Info, as you asked for in the other thread about my random freezes upon incoming phone calls. Purchased in germany. Edited January 11, 2015 by ipk1
Guest KonstaT Posted January 11, 2015 Report Posted January 11, 2015 Here's the screenshots from the KIS3 Info, as you asked for in the other thread about my random freezes upon incoming phone calls. Purchased in germany. Thanks, that looks identical to mine. It's some french Open C's that also have a proximity sensor (which could possibly lead to in-call problems I can't reproduce without having one on my device). Please test the previous build I suggested.
Guest Copro Posted January 22, 2015 Report Posted January 22, 2015 Tried to run it on my ZTE Kis3 max because I already thought about trying the KonstaT CM ports but just got: Exiting, your device is not a ZTE Kis 3! Currently running stock Android 4.4.2 which is good - but because of trouble of having to map user space directories on the external SD card e.g. with osmand was thinking about looking into Cyanogen alternatives.
Guest KonstaT Posted January 22, 2015 Report Posted January 22, 2015 Tried to run it on my ZTE Kis3 max because I already thought about trying the KonstaT CM ports but just got: Exiting, your device is not a ZTE Kis 3! Currently running stock Android 4.4.2 which is good - but because of trouble of having to map user space directories on the external SD card e.g. with osmand was thinking about looking into Cyanogen alternatives. That is correct. Your device is not a ZTE Kis 3! Anything you'll find in this forum will not work on your device. Your device has completely different hardware (MediaTek crapware on yours vs. Qualcomm chipset on this one).
Guest Huesos66 Posted February 14, 2015 Report Posted February 14, 2015 (edited) ZTE Open C Movistar - Venezuela Edited February 14, 2015 by Huesos66
Guest hecatae Posted February 14, 2015 Report Posted February 14, 2015 cat /proc/driver/accel0x33cat /proc/driver/camera_id_backBACK Camera ID:GALAXYCORE,GC2235, 2M Bayer sensorcat /proc/driver/emmc HYNIX H9DP32A4JJMCGR 4G eMMC cat /proc/driver/lcd_id IC:ILI9806C+TXD; Glass:CMI; Resolution:480*800cat /proc/driver/ts_information name : goodix i2c address : 0x5dIC type: goodix GT9137 firmware version : 9137_1030module : JianBang-9137getprop | grep ro.boot.hwversion[ro.boot.hwversion]: [wmfA.6] oh and a proximity sensor 0x39
Guest KonstaT Posted February 15, 2015 Report Posted February 15, 2015 Here's from trickett93's Kis 3 (UK EE). This device has GT960F touchscreen which is not supported in the goodix touchscreen driver with the current kernel source code ZTE has released. Touchscreen is non-functional in custom ROMs.
Guest hecatae Posted February 15, 2015 Report Posted February 15, 2015 Here's from trickett93's Kis 3 (UK EE). This device has GT960F touchscreen which is not supported in the goodix touchscreen driver with the current kernel source code ZTE has released. Touchscreen is non-functional in custom ROMs. Screenshot_2015-02-15-14-41-39-2.png Screenshot_2015-02-15-14-41-55-2.png That's not nice, do we need to ask EE or ZTE for source code?
Guest KonstaT Posted February 15, 2015 Report Posted February 15, 2015 That's not nice, do we need to ask EE or ZTE for source code? Yes.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now