yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] gen_scheisskopf:
It's a kernel config option only, for a510 it's CONFIG_ACER_SECURE_MOUNT and it is accessible in menuconfig or by hand- in .config change "CONFIG_ACER_SECURE_MOUNT=yes" to "# CONFIG_ACER_SECURE_MOUNT is not set" (as for kernel compilation- there are many tutorials floating around)

Start recovery and just

adb shell
cat /etc/fstab

or

adb pull /etc/fstab [path on your pc]

I've never used any recovery builder but kernel and ramdisk/initramfs (where recovery is placed) are separate files, you can unpack boot.img and just modify what you need (note- linux machine required, virtual one will do)
[Android Q&A, Help & Troubleshooting] MaluNoPeleke:
Is it already disabled in the source code?

mv@mv-5755G ~/Dokumente/kernel $ grep -R -i 'CONFIG_ACER_SECURE_MOUNT*' ./*
./arch/arm/configs/picasso_mf_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_m_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./fs/Makefile:ifeq ($(CONFIG_ACER_SECURE_MOUNT),y)
[Android Q&A, Help & Troubleshooting] gen_scheisskopf:
It seems that it's disabled.
[Android Q&A, Help & Troubleshooting] dobie62:
Is there a zip file for Acer 210 tablet now 4/2013
[Android Q&A, Help & Troubleshooting] u.k-f:
There is a real lot available for A210:

Pure root (German)

CWM recovery (German)

Custom Kernel

CM 10.1 like ROM

What are you looking for?

regards Uwe
[Android Q&A, Help & Troubleshooting] dobie62:
This is it but in English please.
[Android Q&A, Help & Troubleshooting] tomschmidt:
A210

Are the A210 and the A510 similar enough to use the same kernel, ROM's or Recovery?
[Galaxy S II Q&A, Help & Troubleshooting] Demikos89:
Hi guys. Sorry if this has been answered before. I searched with no results.

Im curious to know if the new Jelly Bean update for our Samsung Galaxy S2 will have the latest TouchWiz 5 Interface in it. For those who are not familiar with this Touchwiz 5 word, well, to make it more simple to you, will the new Jelly Bean update for the S2 have the interface like the one is Samsung Galaxy S3.

Ive seen a lot of the new low/mid-end phones made by Samsung are being made with TouchWiz 5, so I thought this has not to do with hardware as it has to do with software, so Im sure our S2 is good enough to handle TouchWiz 5.

If someone of you have any information, i'd be happy to know.

Thanks.
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
This is the dedicated discussion thread for Galaxy SII Jellybean update:xdaforums.com/showthread.php?t=1736726. So ask your questions there.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Skyrocket2:
if my device is in the download mode and not USB connected, how do I exit the download mode?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Hold power until it reboots
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Skyrocket2:
Thanks.:good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MasterDecker:
Offer it 3 strips of bacon.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tennisjunkie:
And some OJ
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] MasterDecker:
GREAT, now you want his phone stabbe to death.
[General Questions and Answers] letsflyak:
I have a S-OFF merge with a custom rom, ver 2.2

Kernel 2.6.32.17-g788be6b3

htc-kernel@and18-2 #1

Fri Sep 10 2010

I rooted it and put on a custom ROM off the net quite a while ago i forgot the procedures etc.

My question is, i want to go back to factory ROM (gingerbread 2.3) is there anything that may brick my phone if i attempt to download the ROM from HTC website and go thru the process of trying to install the factory ROM?

If i recall i may have tried to install the factory once before and it failed, what would the procedure be for getting my phone back to factory ROM so it will update to 2.3?
[Galaxy S II Q&A, Help & Troubleshooting] lasic.2000:
Hey!

I want to make flashable .zip that will not extact files but delete them.I mean what do I have to write in updater-script to delete some apps ??

EDIT : Is it: delete("system/app/NameofApp.apk");
[Galaxy S II Q&A, Help & Troubleshooting] lasic.2000:
No answer? Shame on me :(

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] Mantulis:
Hey.

To remove files you'll want:

mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");

delete("/system/app/blah.apk");

unmount("/system");

Your mount command will probably be different, so check the CM update-script for the equivalent one.

More info http://xdaforums.com/showthread.php?p=17684719

Good luck mate:)
[Galaxy S II Q&A, Help & Troubleshooting] lasic.2000:
Big thanks to you mate :D.

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] Mantulis:
Happy to hear that ,,noob" can help Senior member :D
[HTC One X] ExoticMe:
sorry vcek didnt upgrade yet but i bet its problem with the 10.2 report it to mike or ask at the IRC
[HTC One X] AlexIvasuc:
did you update the hboot?i have the same problem,updated yesterday to maximus 4(Relock=>flash firmware=>unlock=>flash img=>recvery=>rom the normal method),tried everithing(revert to ics,change ics kernel,switched jb rom to insertcoin/arhd 10.2) the sensors(light/proxy) are still dead.
[HTC One X] Vcek:
**delete**
[HTC One X] AlexIvasuc:
cid HTC_032 andro sensor reports -Light:waiting for event Proximity:waiting for event(or failed)
[HTC One X] Vcek:
Exactly same errors show up, i hope its not hardware error. Lets wait for the official OTA's so we can flash a better firmware.
[HTC One X] AlexIvasuc:
forgot to ask to the touch keys light up?mine light up if i tamper with the energy saving function/brightness on JB,but they stay light up until a reboot
[HTC One X] Vcek:
yes the lights themselves are working but the sensor which turns them on is the problem. (they flash too when holding power button to reboot)
[HTC One X] Vcek:
lets hope the HOX hboot release will have a base version 3.09.401.100 or larger xD
[HTC One X] AlexIvasuc:
i hope that the stock jb ruu will fix our problems:-s
[HTC One X] Vcek:
good news, the OTA(only certain users) which included this hboot was for testing purpose and hence official release should have a higher version number
[HTC One X] AlexIvasuc:
that is good news,where did you get that info?
[HTC One X] omar302:
My HOX has CID of HTC_J15 & both sensors are working fine after flashing the Firmware with 1.23 Hboot. Running IncertCoin JB.
[HTC One X] Vcek:
Can you please pm me your serial number?
[HTC One X] omar302:
It starts with HT242

But why do u need the serial number.?
[HTC One X] Vcek:
Because i want to isolate the cause of this problem, and it seems that CID is not the problem. My s/n starts with hw25(EDIT: HT251, my bad) which might be a newer or older hardware version.
[HTC One X] omar302:
There was thread about the serial numbers, I remeber that HT stands for Taiwan made, while HW was China made.

Also, my 242 stands for April 2, 25 means sometime in May.
[HTC One X] Vcek:
So I have a newer version (variant 0)
[HTC One X] omar302:
Yes you have a newer build, but it was made in China.

Check this post for details on the serial numbers.
[HTC One X] BenPope:
SH is for Shanghai, China.

HW doesn't exist.
[HTC One X] Vcek:
I edited my post It was meant to say HT25(HT251W) not HW25
[HTC One X] AlexIvasuc:
S/n:HT25 cod:htc_032,sensors not working
[HTC One X] Vcek:
it seems that we both have HT25 in common maybe thats a lead
[HTC One X] Vcek:
Added some logcat debugs to OP with some clues to the cause of the bad sensors (if any chef's can help)

E/Sensors ( 743): Couldn't open /dev/lightsensor (No such file or directory)
E/Sensors ( 743): LIGHTSENSOR_IOCTL_ENABLE failed (Bad file number)
E/SensorService( 743): Error activating sensor 17 (Bad file number)

So far it seems that it's a soft-problem
[HTC One X] Vcek:
added bugreport seems some phones might have different sensor types :

DUMP OF SERVICE sensorservice:
Sensor List:
Panasonic 3-axis Acceleration sensor | The Panasonic Android Open Source Project | 0x00000000 | maxRate= 100.00Hz | last=< 0.0, 0.0, 9.7>
Panasonic 3-axis Magnetic Field sensor | The Panasonic Android Open Source Project | 0x00000001 | maxRate= 100.00Hz | last=< 0.0, 0.0, 0.0>
Panasonic Orientation sensor | The Panasonic Android Open Source Project | 0x00000002 | maxRate= 100.00Hz | last=< 0.0, 0.0, 0.0>
Panasonic Gyroscope sensor | The Panasonic Android Open Source Project | 0x00000006 | maxRate= 833.33Hz | last=< 0.0, 0.0, 0.0>
Panasonic Rotation Vector | The Panasonic Android Open Source Project | 0x00000003 | maxRate= 833.33Hz | last=< 0.0, 0.0, 0.0>
Panasonic Linear Acceleration | The Panasonic Android Open Source Project | 0x00000004 | maxRate= 100.00Hz | last=< 0.0, 0.0, 0.0>
Panasonic Gravity | The Panasonic Android Open Source Project | 0x00000005 | maxRate= 100.00Hz | last=< 0.0, 0.0, 0.0>
CM3602 Proximity sensor | Capella Microsystems | 0x00000012 | maxRate= 0.00Hz | last=< 0.0, 0.0, 0.0>
CM3602 Light sensor | Capella Microsystems | 0x00000011 | maxRate= 0.00Hz | last=< 0.0, 0.0, 0.0>
9-axis fusion disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
9 h/w sensors:
handle=0x00000000, active-count=0, rates(ms)={ }, selected=66.7 ms
handle=0x00000001, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000002, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000006, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000003, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000004, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000005, active-count=0, rates(ms)={ }, selected= 0.0 ms
handle=0x00000012, active-count=1, rates(ms)={ 66.0 }, selected=66.0 ms
handle=0x00000011, active-count=1, rates(ms)={ 1000.0 }, selected=1000.0 ms
1 active connections
[HTC One X] Vcek:
Found a workaround for lightsensor using "Lux auto brightness app" set front camera as lux-reading-source. :good:

But i think no way around proximity :(
[HTC One X] ykooze:
s-off

cid:11111111

HBoot:1.23

S/N : HT253W******

My proximity and light sensors are not working with sense4+ available (ARHD,Insertcoin,OrDroid ...).

:crying:

---------- Post added at 03:19 PM ---------- Previous post was at 03:10 PM ----------

Confirmed that it‘s caused by S/N.

Becase my cid is [11111111] and s-off.

But the two sensor are not working with S/N:HT253W******
[HTC One X] Vcek:
Yes it seems that all the new OneX's HT25(and newer) have this problem :rolleyes: , (could be to different hardware/sensors builts)

I most likely think that it will be fixed by the official release of JB, for now all we can do it wait,

hope that some developer could elaborate,
[HTC One X] AlexIvasuc:
cant you downgrade using official ics ruu,having s-off and all....?
[HTC One X] ykooze:
yes with s-off

---------- Post added at 07:59 AM ---------- Previous post was at 07:43 AM ----------

Yes I have it.
[HTC One X] Vcek:
try downgrading you hboot and see if the sensors work again.
[HTC One X] AlexIvasuc:
Use a stock urc ics ruu,stock 2.17 should be fine.
[HTC One X] ykooze:
Yes ,it's not working only with 1.23HBoot ,the older ones are OK !
[HTC One X] AlexIvasuc:
Perfect,so it's the hboot,official jb will fix our issue!
[HTC One X] ykooze:
I'll test the OTA_ENDEAVOR soon ~:silly:
[HTC One X] Vcek:
The leaked OTA contains the same 1.23 hboot so im guessing it should cause the same problem, make loads of backups just in case :D
[HTC One X] ykooze:
Yes, the same result.

I think what I can do is only waiting ...:(
[HTC One X] Vcek:
Try flashing the new 1.28 hboot released by football (you can downgrade with s-off) tell me if the sensors work now.
[HTC One X] ykooze:
Unfortunately，it's still not working with hboot 1.28
[HTC One X] Vcek:
damn htc noobs releasing wrong drivers xD
[HTC One X] ykooze:
Easy, tomorrow I'll test maXimus v4.2 based on One X 3.14.401.600 with new kernel .
[HTC One X] Vcek:
Alex tested it and it didn't work :confused:

I think who ever is leaking those firmwares is working on old HOX's
[HTC One X] AlexIvasuc:
Already tested max 4.2 and new hboot confirmed sensors are not working:-<
[HTC One X] ykooze:
This is the firmware I flashed yesterday (checking MD5 SAME).

It's not working as I said before.

So any news?
[HTC One X] Vcek:
We have to wait for the official release.
[HTC One X] trongnghia2411:
Mine are not working either and my MODEL is HT243!

So it's not only model 25 :D
[HTC One X] abd-hamdan:
The same problem

S/N ht24y

the proximity sensor and auto light

waiting for fix from htc or Dev's

with my regards
[HTC One X] ykooze:
It seems that the problem is not only with S/N:HT25.
[HTC One X] Untraceable95:
mine is ht25 and it is not working
[HTC One X] dredre2017:
Ever since I upgraded to 1.23, 3/4 of the way down on my screen was intermittently a deadzone and would not register any touches. I upgraded to 1.28and now it looks like this is constant. A reboot used to help but not anymore. Also, my sensors are not working either.

HTC ONE X Int'l (Tegra Quad Core V0) S-ON

CID: HTC_001

Base: 3.14

ROM: JB ARHD 11.1 Sense 4.5

Kernel: Stock(ARHD)

Recovery: CWM v5.8.4

Radio: 5

HBoot: 1.28
[HTC One X] beast1944:
Man this sucks, would've never upgraded to 1.28 if I know such an issue existed, devs should post somewhere on the HBOOT 1.28 thread that this issue exists, and that people should be careful (((

I guess at the moment there is no way to downgrade to something lower than 1.23?
[HTC One X] Vcek:
Can you post your serial no. starting 4 digits ?
[HTC One X] altbla:
My hox is HT25 and the sensors are also not working..

I dubt i would have tryed the new hboot if any dev mentioned the possibility of this problem..

But other than this, insertcoin is working great!
[HTC One X] Vcek:
The only dev which knows of this is Mike1986 and he said he will report this to HTC.

Another dev simply told me he doesn't have this problem.
[HTC One X] mrdey:
Same problem here... Proximity and light sensor not working.. Using OrDroid 4.2.2 on HT25 HOX.
[HTC One X] lightning5791:
Hate to kill your theory but I have an HT23 that has dead accelerometers on hboot 1.28.

Using Androsensor the following sensor are dead (waiting for event according to Androsensor):

-accelerometer

-gyroscope

-magnetic field

-orientation

Light, proximity and sound are working fine even though I think the measured sound levels are 10-15 dB too low
[HTC One X] Vcek:
I think you are having a different problem, could be due to the same reason tho(incompatible drivers)

try testing your hardware with HTC's diagnostics : call *#*#3424#*#* and check your hardware.
[HTC One X] lightning5791:
G-sensor test hangs... All other seems ok. I did drop the phone a while back but I think that the issue pre-existed that the whoopsie. But whatever the case may be, I can't send it on an RMA because JB hasn't been released for HOX yet...
[HTC One X] Vcek:
you can send it back to htc and ask for a quote on fixing
[HTC One X] beast1944:
HT25 btw like the others. HT253 To be more specific
[HTC One X] ykooze:
As I know, HTC will release JB for our HOX in Asia on 26th this month (Just tomorrow in my time-zone).

I hope the new hboot in the coming release will fix our bug.

And I will test it in the first time.

You guys, just wait my report since I have a HOX with s-off

:laugh:
[HTC One X] Vcek:
If it doesn't work then we all have a reason to get a free replacement XD
[HTC One X] Vcek:
new firmware with hboot 1.31 should be included in this JB OTA 26/10 testing it in a few hours, will extract the firmware.zip later

new firmware.zip only flashable for cid: HTC_621 , if S-OFF you can change cid : fastboot oem writecid XXX_XXX

Couldn't flash it waiting for my S-OFF friend ykooze xD , or my J15 release :/
[HTC One X] ykooze:
Tested the 1.31 Hboot，It's still not working ~

SAD! :crying:
[HTC One X] Vcek:
Ok let's calm down,

Q1)what is the original rom you had when you got the phone? Mine was x.xx.415.xx

Q2)Did you try to flash the whole ota?

Q3)Can you confirm again that downgrading makes the sensors work?

I'm sure that HTC is not stupid and until they release our own official update we can stay calm.
[HTC One X] ykooze:
Ok, this is mine:

A1)Original Rom :x.xx.709.xx

A2)I did flash the whole OTA

A3)I can confirm it.

Because I have downgraded the hboot for several times and the sensors were working well.

But when upgraded to hboot1.23 or higher ones,as you know,they are died.
[HTC One X] Vcek:
downgrade to the latest ICS ruu and get the ota from software-update option in your phone. If it still doesn't work, you can go straight to HTC and raise you middlefinger.
[HTC One X] beast1944:
I thought it wasn't possible to downgrade???
[HTC One X] Vcek:
If you look close in the screenshots of ykooze, you will see he is S-OFF, you can downgrade with S-OFF :/

Anyways ykooze can you try with the 1.14.xxx.xx HOX+ ROMS ? maybe it will work ... nothing to loose
[HTC One X] ykooze:
You know, Asia Taiwan released JB.

So, I flash the latest ics of Taiwan by ruining ruu first. And then connected to WiFi, got the OTA .

Still not working.

Well, I will test the one x+ 1.14.xxx.xx

I try to communicate with HTC online, they just told me to send my phone for repair. :thumbdown:
[HTC One X] ykooze:
The same, it's still not working with 1.14.xxx.xx
[HTC One X] Vcek:
Thanks for your efforts, all we can do now is wait for more firmware.zip releases and hope they will work. Or go to repair and you should get free replacement/fix.
[HTC One X] ercliou:
Got the same problem this morning after update (HTC__621)

S/N: HT253

New hboot 1.31

Light and prox sensors dead

Edit: updated to ROM based on last 3.14.401.16 OTA.
[HTC One X] beast1944:
Yeah but he upgraded to 1.31, with S-off, what about downgrading to something below 1.23, from what I understand, that's not possible.
[HTC One X] ykooze:
My device has been s-offed. So I can upgrade or downgrade the hboot freely ,believe it or not.
[HTC One X] Vcek:
From what i have read, HTC and other manufacturers(most electronics) secure the bootloaders from exploiting by users, so once you upgrade you can't go back to old ones to exploit any security holes, this is done on htc devices by S-ON. S-OFF basically removes all fimware/CID/deviceID checking and this can cause loads of problem within the warranty which HTC wants to avoid.(I think its even possible to flash another devices' bootloaders if S-OFF which might/will burn your "chips".

Remember HTC doesn't care what you do with your phone as long as you don't return it for warranty-repairs.
[HTC One X] beast1944:
So basically what you are saying, if you lock your device flash an older version of hboot and then unlock again, you won't be experiencing this problem?
[HTC One X] ykooze:
Yes, when downgraded the hboot below 1.23, It works ok.

By the way, relocking bootloader for upgrading or downgrading hboot is not necessary since got s-off
[HTC One X] beast1944:
Does anybody perhaps have a link to any hboot earlier than 1.23?
[HTC One X] BenPope:
It's no use, you can't flash it without S-Off.

But the hboot can be extracted from the RUU and OTA files, from what I hear.
[HTC One X] Vcek:
i dont think firmware.zips are included in any ruu's(they are extracted already and u can't flash its component indiviually), but definitely in some ota's if they upgrade the firmware
[HTC One X] matt95:
no problems at all here... :)
[HTC One X] Vcek:
S/N ?
[HTC One X] matt95:
S/N: HT23Z
[HTC One X] carlowise:
I can't run the test anymore???? I'm on JB hboot 1.28 HT242 Insertcoin 11.5.0. Phone doesn't recognise comand #*#*3424#*#* for test.???

tnx
[HTC One X] ykooze:
Flashing the ruu 2.17.xxx.xx ,I got the hboot below 1.23

---------- Post added at 08:38 AM ---------- Previous post was at 08:32 AM ----------

You can just get the hardware-test-app from Google play, such one app called androsensor.
[HTC One X] Imyeltekin:
I have hboot 1.28 i have same problem.. S/N : HT24Y

is there any news about it?
[HTC One X] Vcek:
HT24Y ? if Y a number please give it to know whats the exact date of manufacture.

And so far no solutions, however you can substitute the light sensor with the front camera with "lux dash" brightness app.
[HTC One X] Imyeltekin:
if you want to know Device S/N ; HT24YW110***
[HTC One X] Vcek:
Confirmed different hardware cm3628(proximity) and cm3629(light) vs. cm3602(2-in-1 sensor) reported in debug

./sys/bus/i2c/drivers/cm3628
./sys/bus/i2c/drivers/cm3628/uevent
./sys/bus/i2c/drivers/cm3628/unbind
./sys/bus/i2c/drivers/cm3628/bind
./sys/bus/i2c/drivers/CM3629
./sys/bus/i2c/drivers/CM3629/uevent
./sys/bus/i2c/drivers/CM3629/unbind
./sys/bus/i2c/drivers/CM3629/bind

Ykooze, i need you to check sys/bus/i2c/drivers/ in an old hboot version, report the cm36** directories found. Thanks
[HTC One X] Thömy:
cm3628 and CM3629 are the names of the i2c drivers the kernel registers. It then decided on runtime which to use.

cm3602 is a name used in the source code and in sensors.endeavoru.so which probably denotes a class of sensors. Both cm3628 and cm3629 should be 2-in-1 sensors.

The output of the first messages that appear in /proc/kmsg would be interesting. Look for lines that contain "[PS][cm36". It might me neccessary to interrupt the boot process with "adb reboot" and then grab /proc/last_kmsg instead.

It could look like this. Output might differ because I'm on CyanogenMod. Also my sensors work. But maybe I can help somewhere.

[ 0.000000] parse_tag_als_calibration: als_kadc = 0x6da51177
[ 0.000000] parse_tag_ps_calibration: ps_kparam1 = 0x50530306, ps_kparam2 = 0xffff0a12
[ 3.218443] [PS][cm3629]psensor_init ps_type = 1
[ 5.922366] [PS][cm3629] cm3629_probe
[ 5.960968] [PS][cm3629] cm3629_read_chip_id, chip_id value = 0x82, 0xc0, ret 0
[ 5.961332] [PS][cm3629]cm3629_probe: lp_info->ls_cmd = 0x84!
[ 5.961535] [PS][cm3629] cm3629_probe: ls_cmd 0x84, ps1_adc_offset=0x00, ps2_adc_offset=0x00, ps_debounce=0x0
[ 5.965714] [LS][cm3629] lightsensor_set_kvalue: ALS calibrated als_kadc=0x6da51177
[ 5.966080] [LS][cm3629] lightsensor_set_kvalue: als_kadc=0x1177, als_gadc=0x13ef
[ 5.966436] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[0], a
[ 5.966637] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[1], c
[ 5.966991] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[2], e
[ 5.967348] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[3], 9a
[ 5.967547] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[4], 13c
[ 5.967900] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[5], e44
[ 5.968250] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[6], 1795
[ 5.968446] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[7], 2111
[ 5.968796] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[8], 2a8d
[ 5.969151] [LS][cm3629] lightsensor_update_table: Calibrated adc_table: data[9], ffff
[ 5.969608] [PS][cm3629] psensor_set_kvalue: PS calibrated ps_kparam1 = 0x50530306, ps_kparam2 = 0xFFFF0A12
[ 5.969977] [PS][cm3629] psensor_set_kvalue: PS calibrated inte_ps1_canc = 0x12, inte_ps2_canc = 0x0A, ((ps_kparam2 >> 16) & 0xFF) = 0xFF
[ 5.970792] [LS][cm3629] ls_initial_cmd, cmd[0] = 0x85, cmd[1] = 0x0
[ 5.977997] [PS][cm3629] psensor_initial_cmd, finish
[ 5.979984] [PS][cm3629] cm3629_probe: Probe success!