Camera and Screen Issue--suppose I've found the key problem

[Guest Piscium]

had 1 full day test:

trouble shoot: The touch is not working in the 1st booting once we changed battery,

and quickly re-install the battery normally can resolve the problem--

(disconnect the battery golden finger with the phone and quickly re-connect it)， the phone will auto power on and boot w/o press the power button,

then generally the touch will be ok, and it will be always ok untill next changing of battery--( reboot the phone generally will ok with touch)

what cause it happen? will it be resolved? and why it will be working after quick disconnect reboot?(forget it if it's difficult to explain, I just wanna know more of phone and Linux )

It's really a headache problem which is interfering me and others every day...

for the rest:

1. camera: work stable, the photo quality seems improved, not as good as ZTE ROM, but better than last version, you did the improvement?

2. video rec: work stable, the quality seems less good as ZTE ROM(my own opinion)

3. game: after half day running of the phone, I started gaming in the afternoon, 《Dungeon Hunter》quit abnormally when the game is in loading,I tried several times it was all the same situation, and then I rebooted the phone, and everything is ok, I suppose this is because of insufficient of RAM.

4. phone: working stable, the power using is normal, shorter about 10-20% than ZTE ROM but it's understandable on 2.3.7( since it's working faster).

5. I know there's a leak ROM of Libra 2.3.5 from several weeks ago, everybody saying it's an official ROM leak, and seems it is, because I heard everything is working including camera. It had GPS problem in the beginning and now seems someone fixed it,

Later on I will try it also.

Edited October 29, 2011 by Piscium

[Guest Piscium]

Dear Tom G,

I learnt how to use abd shell, and now submit the logcat and dmesg under the situation of touch not working,

Check the info in the attachment: catNdg.rar

here is when I re-install battery and touch workingtouch-ok-logNdg.rar

Also I give this to burstlam from hiapk forum here in China

Edited October 29, 2011 by Piscium

[Guest Tom G]

The logs at least give some errors to look at. It sounds similar to a problem that was fixed in the old kernel, but I tried using the fix from the old kernel and that didn't help you. Burstlam has also built a test rom using the patch from the old kernel (he mentioned it here), so you could also try that one but I expect you will get the same result. I'll try to look at it tomorrow.

Bad

<3>[01-01 00:00:01.710000] [1: swapper]synaptics-rmi-ts 0-0022: synaptics_i2c_read FAILED: read of register 238

<3>[01-01 00:00:01.710000] [1: swapper]synaptics_ts_get_func_addr: error reading PDT

<3>[01-01 00:00:01.710000] [1: swapper]synaptics_ts_get_opmode: error reading device status

<3>[01-01 00:00:02.000000] [1: swapper]synaptics-rmi-ts 0-0022: synaptics_i2c_read FAILED: read of register 120

<4>[01-01 00:00:02.000000] [1: swapper]wly: synaptics_i2c_read, x, �,f,�,,

<3>[01-01 00:00:02.310000] [1: swapper]synaptics-rmi-ts 0-0022: synaptics_i2c_read FAILED: read of register 120

<4>[01-01 00:00:02.310000] [1: swapper]wly: synaptics_i2c_read, x, �,f,�,,

<3>[01-01 00:00:02.620000] [1: swapper]synaptics-rmi-ts 0-0022: synaptics_i2c_read FAILED: read of register 120

<4>[01-01 00:00:02.620000] [1: swapper]wly: synaptics_i2c_read, x, �,f,�,,

<4>[01-01 00:00:02.640000] [1: swapper]synaptics-rmi-ts: probe of 0-0022 failed with error -1

Good

<4>[01-01 00:00:01.419999] [1: swapper]wly: synaptics_i2c_read, :, 0,�,,T,M,1,5,4

<4>[01-01 00:00:01.419999] [1: swapper]wly: synaptics_ts_probe,max_x=1867, max_y=3096

<6>[01-01 00:00:01.419999] [1: swapper]input: synaptics-rmi-touchscreen as /devices/virtual/input/input0

<6>[01-01 00:00:01.419999] [1: swapper]synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode

[Guest Tom G]

Please test this and provide logs (dmesg is all thats really needed). Link

Thanks.

[Guest Piscium]

Got it, recharging my battery and will do it tonight, forgot my spare battery in the office....

[Guest Piscium]

Dear Tom,

Great job!!!

1. The touch is working after the 1st booting, and I tried several times by take out the battery, reboot, power off and on, all working good.

2. Just when I reboot and connect to my computer to before making dmesg and logcat, I found the touch point moved about 1 and half icon place to the right side, then I go on and made dmesg and logcat.

Then I reboot again, the touch was ok, and then I made dmesg and log again.

logcatNdmesg.rar

3. Camera and Video rec. working ok.

4. The phone run much quick than last 3 version of test ROM, I felt it after st boot--great!

I will go on testing for the touch, photo, video and app running(include gaming), power using in the next several days!

Thank you Tom! So closing to the success on this issue!

Good day!

Syne

[Guest Tom G]

I'm more confused now than I was before. It looks like it should be completely failed when your getting the touch point moved. Still its good progress, I'll look at it more tomorrow.

If you had compcache enabled previously it would not have actually worked. It is fixed in the test rom so that may be the speed increase you are seeing. Compcache isn't needed for the 512MB devices, but should have some benefit for the 256MB devices.

[Guest Piscium]

Good morning Tom,

I can understand only half about the touch problem, take it easy, will be found out.

Also I was too far to be professional like you,

However, I started to know what should be the correct way to give you feedback.

I'll learn more, I'll see what stage I can reach in the future.

For the 2nd point.....yeah..you've been 100% right, I never tried compress cache yet in order to keep stable working for test(just my own..thoughts, I started use android only 1 month and tried CM7 about 2 weeks, every thing is new), any way, since it was fixed, is it still required to enable this option?

Ask me more if you wanna more feedback, and teach me how to do it.

Best Regards,

Syne

Edited October 31, 2011 by Piscium

[Guest Tom G]

Try this one. I think it should work. Link

[Guest burstlam]

Try this one. I think it should work. Link

Tom,

the touchscreen alignment is incorrect with the latest vesion (still shifted to left hand side)

[Guest Piscium]

Hi 2 experts, I didn't try the new since I just saw it, and burstlam already replied.

Do you still need me to flash it and give the logs?

Well, it's really the stage of "nightly" :D

Edited October 31, 2011 by Piscium

[Guest burstlam]

Hi 2 experts, I didn't try the new since I just saw it, and burstlam already replied.

Do you still need me to flash it and give the logs?

Well, it's really the stage of "nightly" :D

sure~ especially the log with touching and moving over it

fellows in hiapk only give quick reply on result

[Guest burstlam]

here is a dmesg from a chinese blade user.

alignment is not correct even with a wipe and reinstall

dmesg.txt

[Guest burstlam]

" Paste Bin link"

it looks to me that he is using a focaltech ts indeed.

Edited October 31, 2011 by burstlam

[Guest Tom G]

I need a log showing the initialisation, so just after booting.

[Guest Tom G]

" Paste Bin link"

it looks to me that he is using a focaltech ts indeed.

That looks like the older test rom, not the current one.

[Guest Tom G]

I just realised the link for the new test rom was incorrect, it was linking to the old test rom which explains users getting the same results.

Try this one. Link

[Guest Piscium]

I saw it is writing test2...but I still tried...ok, will do it again~

any way, I saw on CM 2 new published ROM, this is the one or nothing to do with that?

Also can I have a test ROM which have data2ext and swap on sd enabled? enable the virtual button function as well if possible.

Edited November 1, 2011 by Piscium

[Guest Piscium]

hey guys,

see the fresh logs as attched~

good day!

dm5.txt

cat5.txt

Edited November 1, 2011 by Piscium

[Guest Tom G]

hey guys,

see the fresh logs as attched~

good day!

dm5.txt

cat5.txt

That log shows it working normally. Try recreating the condition that was causing the problem before (fully powering off the device, then get a log after first boot). If the problem occurs you should see a few i2c read errors from the synaptics driver in dmesg.

[Guest Piscium]

I tried about 10 times, the touch is all working ok,

How ever, I saw i2c errors in the dmesg,

<4>[01-01 00:00:01.429999] [1: swapper]gpio 31 request is error!<4>[01-01 00:00:01.429999] [1: swapper]cypress_touch: probe of 0-000a failed with error -16<3>[01-01 00:00:01.690000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.690000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.690000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<3>[01-01 00:00:01.710000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.710000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.710000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<3>[01-01 00:00:01.729999] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.729999] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.729999] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<4>[01-01 00:00:01.750000] [1: swapper]ft5x0x_ts: probe of 0-003e failed with error -1

also more here, something related with camera?:<3>[11-01 02:11:45.520000] [67: mt9p111_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)<3>[11-01 02:11:45.540000] [67: mt9p111_wq]mt9p111_workqueue: rc != -ENOINIT

more:

<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]mt9t11x_sensor_dev_probe: rc=0xfffffffb,model_id = 0x0

try to fix them also

[Guest Tom G]

I tried about 10 times, the touch is all working ok,

How ever, I saw i2c errors in the dmesg,

<4>[01-01 00:00:01.429999] [1: swapper]gpio 31 request is error!<4>[01-01 00:00:01.429999] [1: swapper]cypress_touch: probe of 0-000a failed with error -16<3>[01-01 00:00:01.690000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.690000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.690000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<3>[01-01 00:00:01.710000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.710000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.710000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<3>[01-01 00:00:01.729999] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)<3>[01-01 00:00:01.729999] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166<6>[01-01 00:00:01.729999] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.<4>[01-01 00:00:01.750000] [1: swapper]ft5x0x_ts: probe of 0-003e failed with error -1

also more here, something related with camera?:<3>[11-01 02:11:45.520000] [67: mt9p111_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)<3>[11-01 02:11:45.540000] [67: mt9p111_wq]mt9p111_workqueue: rc != -ENOINIT

more:

<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]mt9t11x_sensor_dev_probe: rc=0xfffffffb,model_id = 0x0

try to fix them also

Those are to be expected on your hardware.

<4>[01-01 00:00:01.429999] [1: swapper]gpio 31 request is error!

<4>[01-01 00:00:01.429999] [1: swapper]cypress_touch: probe of 0-000a failed with error -16

Cypress touch screen did not respond.

<3>[01-01 00:00:01.690000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)

<3>[01-01 00:00:01.690000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166

<6>[01-01 00:00:01.690000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.

<3>[01-01 00:00:01.710000] [1: swapper]msm_i2c msm_i2c.0: (007c) Error during data xfer (-5)

<3>[01-01 00:00:01.710000] [1: swapper]ft5x0x_ts 0-003e: Fts_i2c_read FAILED: read of register 166

<6>[01-01 00:00:01.710000] [1: swapper]wly: Fts_i2c_read, FT5X0X_REG_FIRMID = 166.

Focaltech touch screen did not respond. You have a synaptics touch screen, so you don't have the hardware these two are looking for.

<3>[11-01 02:11:45.520000] [67: mt9p111_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)

<3>[11-01 02:11:45.540000] [67: mt9p111_wq]mt9p111_workqueue: rc != -ENOINIT

<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]msm_i2c msm_i2c.0: (007a) Error during data xfer (-5)

<3>[11-01 02:11:46.630000] [68: mt9t11x_wq]mt9t11x_sensor_dev_probe: rc=0xfffffffb,model_id = 0x0

You have a Samsung s5k5acgx camera sensor, not one of the mt9's. There may also be errors for the ov5642 in there somewhere. This is just hardware not present in the device failing to initialise. The touch screen problem isn't really fixed, it is just handled better. When the problem occurs you should still get a few of the error below.

<3>[01-01 00:00:02.000000] [1: swapper]synaptics-rmi-ts 0-0022: synaptics_i2c_read FAILED: read of register 120

<4>[01-01 00:00:02.000000] [1: swapper]wly: synaptics_i2c_read, x, �,f,�,,

Then you should see "synaptics_i2c_read failed. Falling back to polling mode."

Edited November 1, 2011 by Tom G

[Guest Piscium]

Thanks for explaining, clearly understand the situation, fow now seems I could not get wrong situation, once this will occur(if have), I will make the logs.

other questions is--in the beginning I informed the photo quality went down, and you confirmed this problem since there's some features have stopped working, were these features fixed to work is the current ROM?

[Guest burstlam]

The alignment issue with synaptics ts seems to be handled with fix3.

indeed, there's another issue with camera sensor. waiting the dmesg

Edited November 1, 2011 by burstlam

[Guest Tom G]

Thanks for explaining, clearly understand the situation, fow now seems I could not get wrong situation, once this will occur(if have), I will make the logs.

other questions is--in the beginning I informed the photo quality went down, and you confirmed this problem since there's some features have stopped working, were these features fixed to work is the current ROM?

No, I haven't looked at any of the camera problems yet and I don't know when I will.