[App][2013-06-12] HwInfo


M1cha

Members
May 29, 2011
1,747
297

Attachments

  • hwinfo_screenshot.png
    hwinfo_screenshot.png
    104.1 KB · Views: 819
Last edited:
I've got almost the same.

Only one change

Enviado desde mi MI 2S usando Tapatalk 2
 

Attachments

  • uploadfromtaptalk1371050663121.jpg
    uploadfromtaptalk1371050663121.jpg
    40.6 KB · Views: 487
nice, only different camera. So either in the beginning or development they used different hardware or the stock kernel just is spammed with useless drivers.
 
Hi M1cha this si my screenshot. Hope it's helpful.Device MI2S
 

Attachments

  • Screenshot_2013-06-12-20-13-32.png
    Screenshot_2013-06-12-20-13-32.png
    129.7 KB · Views: 526
Mine. From a M2S 32 GB (the one with 13mpx camera)
 

Attachments

  • Screenshot_2013-06-13-09-59-56.png
    Screenshot_2013-06-13-09-59-56.png
    130.9 KB · Views: 462
MI2S 32GB (13MP rear camera):
the app gives me a different value for the sensor/driver of the front camera,
it reports an IMX132 sensor instead of the OmniVision one (ov2720)

View attachment 7346

My MI2S has been produced in November 2013.
Probably, recent MI2S have the IMX (Sony??) sensor instead of the OmniVision one:
https://github.com/mitwo-dev/propri...mmit/f25234bfa452a62c2abed2039e05361798db560d
I bought my phone in July and also have imx132 as front camera.

Sent from my MI 2SC (32GB) using Tapatalk
 
Mi2S 32GB,
exactly same with davfiala's..
 

Attachments

  • Screenshot_2014-02-26-15-09-56.png
    Screenshot_2014-02-26-15-09-56.png
    115.5 KB · Views: 376
Hi @M1cha, please I need help. I send my Xiaomi M2s for replacing its broken screen, and I think they have installed a non original/faulty one. It has some "stains" and also LED notification light doesn't work.
The app shows a difference with my previous screenshot. Last line says

Bus: i2c-4; Device 40048; Type video4linux; name: imx132 4-006c

instead of the previous

Bus i2c-4; Device 4-006c; Type: video4linux Name: ov2720 4-006c

Is this related to screen?
 
Hi @M1cha, please I need help. I send my Xiaomi M2s for replacing its broken screen, and I think they have installed a non original/faulty one. It has some "stains" and also LED notification light doesn't work.
The app shows a difference with my previous screenshot. Last line says

Bus: i2c-4; Device 40048; Type video4linux; name: imx132 4-006c

instead of the previous

Bus i2c-4; Device 4-006c; Type: video4linux Name: ov2720 4-006c

Is this related to screen?
just send me your full dmesg and I'll tell you what's wrong with your device.
 
Thank you very much for your attention. I hope you can see something helpful here.. I've just realized that proximity sensor doesn't work either.
 

Attachments

  • dmesg.txt
    88.1 KB · Views: 530
The hardware should be ok. But it looks like you'd have a whole new device because you have different cameras.
If your screen has stains you have to send it to repair again I think.
 
  • Like
Reactions: deini
Different camera? They only had to replace the screen :S Maybe it's only the front camera ? I don't want to believe they have cheated me that way.
Well, just in case someone from Spain reads this: DO NOT BUY IN TODOPAD.ES

PS: I just sent you a coffee because of your work with CM and your support to the community
 
  • Like
Reactions: M1cha
The hardware should be ok. But it looks like you'd have a whole new device because you have different cameras.
If your screen has stains you have to send it to repair again I think.
Hi again. As I suspected, the store is telling me that the problem with LED and proximity sensor are not their responsability.
Is it possible to say, looking at dmesg or logcat, if there is a hardware or software issue with both parts? Thanks again
 
Hi again. As I suspected, the store is telling me that the problem with LED and proximity sensor are not their responsability.
Is it possible to say, looking at dmesg or logcat, if there is a hardware or software issue with both parts? Thanks again
you can boot into cwm and try to manually enable the leds (/sys/class/leds/[red|green|blue/brightness).
if you dunno how todo this I can help you with teamviewer.
 
  • Like
Reactions: deini
I don't know if this is correct:
In recovery, I mounted system and opened an adb shell from pc and typed:
echo "1" > /sys/class/leds/red/brightness

But nothing happens. (the response in shell is a line with the command i entered)
 
since the value has to be between 0 and 255, 1 is hardly noticable. try sth higher like 200 :)
 
Ok, I remember that in my old HTC Desire, we used 0 and 1 for enabling and disabling button backlight.

But well, I 've tried now with 200 and still nothing, neither in blue or green. So I assume that it is a hardware problem...

Thanks!
 
The worst thing is that they're taking me as a stupid, and they say that I didn't tell'em that proximity sensor and LED were damaged. Well, they weren't! I should have record a video of myself making all test from the cit app before sending to them.

Time to open a legal complaint against them... and wait and wait and wait.

And just out of curiosity, can you notice the stains on this photos and videos? It's more noticeable at the bottom of the screen: https://www.dropbox.com/sh/hvmri7v4gtyione/tSt5Y-Wloa
 
Last edited: