Database Users

Trying to get Camera from 5.0.2Hr5

Hi there,
I tried running the Camera from Haykuro's build on my image.
After copying libcamera.so libqcamer.so and libcameraservice.so to /system/lib and changing the Camera.apk in /system/app my Camera and Camcorder disapperead, somebody can tell me the trick?

I don't know what image you are running, but it isn't that simple. The HTC camera.apk requires lots of htc frame work libraries to work. You will have to edit and repack your own boot image to include the com.htc*.jar libraries into class path, and the add and replace some of those libraries to your image. It will require lots of time to test and debug what is missing. It definitely isn't as simple as replacing few .so files and the apk. By the way I couldn't get it to work either but I gave up when I realized I had to rebuild boot.img. Haykuro will probably be able to get it to the adp 1.5 image soon.

I have read somewhere where Haykuro posted this to use H build cam. He did state that it's not quite 100% working and that he'll add this to the new 1.5H build.
adb shell reboot recovery
adb shell mount /system
adb shell rm /system/app/Camera.apk
adb shell rm /system/lib/*cam*.so
adb push libcamera.so /system/lib
adb push libcameraservice.so /system/lib
adb push libqcamera.so /system/lib
adb push Camera.apk /system/app
adb push HTC_Gallery.apk /system/app
adb shell reboot
t4c said:
Hi there,
I tried running the Camera from Haykuro's build on my image.
After copying libcamera.so libqcamer.so and libcameraservice.so to /system/lib and changing the Camera.apk in /system/app my Camera and Camcorder disapperead, somebody can tell me the trick?
Click to expand...
Click to collapse

Hi there,
Thanks for your replay.
I got cam working but got bad problems with force close everytime I try to make some settings. After some tries the camera won't come back up again, what I did:
copy system/lib/*cam* to my build
Camera.apk
HTC_gallery.apk
modified /system/etc/permission/platform.xml for finding the pimlib.

t4c said:
Hi there,
Thanks for your replay.
I got cam working but got bad problems with force close everytime I try to make some settings. After some tries the camera won't come back up again, what I did:
copy system/lib/*cam* to my build
Camera.apk
HTC_gallery.apk
modified /system/etc/permission/platform.xml for finding the pimlib.
Click to expand...
Click to collapse
If you wouldn't mind, send me your platform.xml ([email protected]) I'm 90% sure I know how to fix it to work. Db files are usually the root of all force closes. Settings, acore, messaging... if you have a db with variables that don't exist or missing ones that were added to the apk a crash occurs. I am pretty sure I know what files to fix and we can pack an apk for this...

Hey Twistedumbrella,
thank for your answer and your help, I just sent the xml file.
I am very excited...
Regards

I'd love to get the HTC camera working on the JF 1.5 build. All the camera image adjustments were great. Lemme know if you need someone to test things.

Please Post The steps & Platform.xml Whatever U Did
I am Gona Make A Seperate Thread Of All The apps Ported From Haykuro's Sapphire Builds To JF 1.5
I have Currently Ported The H-Virtual Keyboard To JF 1.5

Yeah i have been waiting for someone to do this...
if you need tester i will gladly do it... =D

ATM I wait for twistedumbrella, he got the cam working but I am completly stuck with this thing.
H cam will make photos but if I try to configure something the cam close forces all the time.

t4c said:
ATM I wait for twistedumbrella, he got the cam working but I am completly stuck with this thing.
H cam will make photos but if I try to configure something the cam close forces all the time.
Click to expand...
Click to collapse
Packing it into an update and testing as we speak

I got the force close problem.
Does anyone find out how to fix it ?
I am running JF 1.5, I push all the .so files also add files into /system/framework
and replace the platform.xml with the one online said for the JF 1.5 HTC app.
The camera will run into a Gray mode, and if I clicked on any icons it will show "force closed"....

[REQ] Pays black bar and icons for CM 5.0.8

Now that we have a CyanogenMOD 5.0.8 on Desire, I am missing black bar and great icons from Pays...
I tried editing framework-res.apk myself but for some reason, after editing, signing, pushing and rebooting, I get FC on every single app on my phone. I don't have problems signing other apks.
Could somebody please edit this, shouldn't be too much work with the right procedure...
THANKS!

you don't have to sign it actually if you adb push it, I never sign it. Just be careful that images are the same resolution and especially look at the 9.png files cause they're not that simple to edit. Is the rom deodexed?

nikosrs4 said:
you don't have to sign it actually if you adb push it, I never sign it. Just be careful that images are the same resolution and especially look at the 9.png files cause they're not that simple to edit. Is the rom deodexed?
Click to expand...
Click to collapse
End up in a boot cycle if I don't sign. Didn't touch *.9.png's
Yes, rom is deodexed. Could signer be the problem? This is not the first ROM i had problems with framework-res....

did you change the permissions? chmod etc?
could you post the stock framework-res.apk?

No, m8, no chmod, chown or anything, just pushed it... Does it have to have specific permissions? I am just about to upload it...
EDIT: Uploaded
View attachment framework-res.apk

well, I use chmod 644.
also check this, I found it now. http://forum.xda-developers.com/showthread.php?t=695701

I changed the battery icons with some I know that work on mine. plz chmod 644 after you adb push it, then we'll know..
http://forum.xda-developers.com/showpost.php?p=6456982&postcount=14

Sorry for responding so late. Will give it a go this weekend (hopefully) and will let you know the results. Thanks!

Thank you! Finally got chance to try it and yes, right permissions was the cause for my trouble.

GPS fixed on Captivate. Combination of 2 methods + detailed steps

This is how I fixed my GPS issue on Captivate. It would not lock on, not even after 5 minutes of me standing still.
Found this thread - http://forum.xda-developers.com/showthread.php?t=786486
Was trying to follow the steps and realized I wished it was spelled out more. So this is what I am doing in this thread, to make it easier for everyone else, if they decide to try. After an hour of googling commands and trial and error - its done, and my phone's GPS locks on under 10 seconds.
I downloaded that zip file. Then installed Droid Explorer on my PC. I already had USB drivers installed for the Galaxy S, so during install I unchecked it. When I opened Droid Explorer I realized I cant write to the /system/bin and the other two. The Write permissions for the system folder were not set, so when I dragged files over - they wouldnt copy over to my phone. It would kinda "refresh" but files wouldnt show up in there.
Easy way seemed to be to buy and install Root Explorer on my phone from the market. And click on Mount R/W for the system folder. However I am waiting for credit card replacement in the mail and was so fed up with GPS that I wanted to do it NOW, and was not gonna stop until its done. Today.
So the other way to make /system/bin , /system/etc and /system/lib folders writable was thru command prompt.
First off my phone has Cog 5.5 on it so it is rooted.
1. set phone in usb debugging mode and connect to pc
2. navigated to my sdk/tools directory on my hard drive. In my case it looked like this
Code:
cd c:\sdk\tools
<hit enter> but it depends on where you downloaded and unzipped your android SDK folder
3. typed
Code:
adb shell
<hit enter> then
Code:
su
<hit enter> to give me root access to the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone will ask if you want to grant permissions to unknown, hit Yes.
4. Now we need to set system as writable. While googling commands it seemed that the command should be
Code:
mount -o rw,remount /system
But in my case that didnt work, telling me location was invalid. I obviously was missing something. Duh! correct location! So -
type
Code:
mount
<hit enter> It will list the root directory. We need t locate exactly where system is on the phone. In my case it was /dev/block/st19 /system
So the command should be then
Code:
mount -o rw,remount /dev/block/st19 /system
<enter>
then
Code:
chmod 777 /system
<enter>
Code:
chmod 777 /system/bin
<enter>
Code:
chmod 777 /system/etc
<enter>
Code:
chmod 777 /system/lib
<enter>
Code:
exit
<enter>
and one more time
Code:
exit
<enter>
The folders are now writable.
5. Opened Droid Explorer, copied files over, lbstestmode launch app was already installed on my phone. So it didnt have to do that step, as it was in j101399j's thread
6. Rebooted the phone, opened lbstestmode, deleted GPS data.
Started testing. It wouldnt lock. Went to Get Position Test in lbstestmode app. It would see the sattellites, 8 of them but wouldnt give me my lat/long! So I remembered this post - http://forum.xda-developers.com/showpost.php?p=9150551&postcount=7862 by cnewsgrp
and changed
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
Click to expand...
Click to collapse
Didnt even have to reboot. Went to Get Position Test again and it saw like 8 or 9 satellites and had * next to 4 of them in 10 seconds. Give me my lat/long with precision. Wanted to mention that I tried cnewsgrp 's method a week ago, just by itself, and it gave me no results.
So to summarize. Combination of those 2 fixes worked wonders for me. And the Captivates GPS issue is definitely not hardware based.
I do have a question however,lol, how do I revoke write settings for my system folder, and go back to how it was? Would that be
Code:
chmod 755
?
I hope these detailed instructions help someone.

And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.

chmod 777???
NO THANK YOU!!

zerojay said:
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
Click to expand...
Click to collapse
it didnt change file settings inside folders, just folder setting

also this is where I got chmod 777 from - http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://karuppuswamy.com/wordpress/2009/04/25/mounting-system-partition-in-read-write-mode-in-android/
was obviously for android.

There's a reason why 777 permissions weren't there to begin with
also I love how there are currently 7 views and 6 replies. which means almost everyone is going - Aaah!!!!! NOOO!!! Must post and warn her!!!

my phone's GPS locks on under 10 seconds
Click to expand...
Click to collapse
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads

sinoth said:
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
Click to expand...
Click to collapse
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
Yes there is a
"a reason why 777 permissions weren't there to begin with"
Click to expand...
Click to collapse
It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.

bmvik said:
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
Click to expand...
Click to collapse
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
I agree. I'll let you know regarding tracking as I test. Before however, not only it would take 5 min to lock on, but would lose me while I was driving, constantly. Accuracy was jumping to 200 meters or so. So instant lock was a good sign to me.

bmvik said:
Yes there is a It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
Wow, the cluelessness.

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
For me it does. I have been using GPS with any issues for past few days. And to give credit what ever steps I have posted have been around for a long time just search for "Vibrant GPS fix". The only reason I needed to do that was my GPS stopped working after applying Cog 2.4 ROM with is Vibrant ROM. I applied Vibrant GPS fix and voila GPS now works!!
I must stress here that I have had no GPS issues with any of the Captivate ROMS or Stock ROMS. I usually get lock in 10 - 30 seconds and it tracks well for me. I used GPS test and I an see around 8-9 satellites with S/N ratio of 35 and accuracy of 16.5 regularly.

Oh the boogeyman
I also would like to add, had anything went wrong during these steps - I would've just reflashed my phone to another Cognition ROM and started from scratch. Voila!

bmvik said:
Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
bmvik said:
Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Click to expand...
Click to collapse
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.

installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
Thank you. I mean, really.
fatttire said:
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
Click to expand...
Click to collapse
Let me spell it out for you. In this thread http://forum.xda-developers.com/showthread.php?t=786486 OP suggests
2. Using root explorer or droid explorer, copy the files from each folder.
Click to expand...
Click to collapse
For root explorer to be able to write to system folder it would HAVE to change that folders permissions. I didnt have the app, so changed them manually, then used droid explorer. Then changed permissions right back to 755.
cnewsgrp said:
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
Click to expand...
Click to collapse
Well I just copied the files from the zip file I linked to in the OP, over to the system/bin, /etc and /lib I dont know how screenshot would help

aaaand uhhhhhh can you non-haters vote the thread up, plz? some 5 haters hit 1 star

OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App

skinien said:
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol stop using the samsung keyboard the period is in the wrong spot.
btw op can you plz post some tracking results with mytracks or something. Locking on is not the problem, tracking is.
If you do ill vote this thread up

Testers needed: Default Orientation Portrait v2

Testers no longer needed...turns out there is no improvement to the old version. Back to the drawing board.
Hello all,
I made a slight change to the PhoneWindowManager.smali and it seems to improve how quickly the orientation switches to portrait after a reboot (has been working immediately after first unlock for me). From my limited testing I also feel it will be less glitchy as sometimes weird things happened with the orientation in the current one. I am looking for a few others who would be willing to test and make sure everything is good.
The PhoneWindowManager.smali is attached
The instructions on how to install are here (Advanced users only)
Thanks for your help

Do you need to install the original portrait mod that you linked to to use this?

It's a smali script, it only relys on the original file to modify.
I'm willing to test for 191 if you make the edited policy.jar

marvin02 said:
Do you need to install the original portrait mod that you linked to to use this?
Click to expand...
Click to collapse
Don't need the original mod, just follow the same steps only use the smali file attached to this thread.
Sent from my Dell Streak 2.2.1 (339)

@jhotmann
I am stuck at the 10th point of ur instruction that is :
10. Put dexopt-wrapper into the correct folder with the correct permissions
> cd /system/bin/
> busybox cp /sdcard/dexopt-wrapper . (yes after dexopt-wrapper is a space and a period)
> busybox chmod 755 dexopt-wrapper
> cd /sdcard/
when i give 2 and 3rd command, it says
cant stst /sdcard/dexopt-wrapper: No such file or directory

Ok...........it was all done properly
But what result i got is . it now stucked in landscape completely and it looks really odd
waited but still its lanscape

yeah it seems to be still the same as the old one...the easiest way to get it out of being stuck in landscape is to open the camera app...Testers no longer needed as it is no improvement over the old version.

Testers
Hello jhotman
I'm sorry i saw this post too late, but if you need any testers in the future please PM me.

[ROOT]Xperia Z1 Touch Screen Tweak

Since there's no thread about fixing this here in Z1's forum, I'd make one with possible fix on the crazy touch screen problem.
As far as I know, this is a firmware-related problem, and can be fixed by tweaking down the touch screen sensitivity. You'll need
to be rooted to use this modification. Always remember, try at your own risk, and don't forget to hit thanks button if I helped!!
HOWTO:
1. Take a backup with CWM or TWRP.
2. Use any root explorer that you like, and navigate to /system/usr/idc/.
3. Copy the file "clearpad.idc" to somewhere else, like the SDcard storage for editing.
4. Open up the file with Jota+ or the text editor of your choice, and find the line "touch.filter.level". By default it would be 2, but
here I would suggest a value of either 5 or 6 for lowered sensitivity.
Code:
touch.filter.level=6
5.Save the file and then mount /system as writable.
Code:
mount -o remount,rw /system /system
6. Paste the modified clearpad.idc back to /system/usr/idc/ and set correct permissions.
Code:
cp clearpad.idc /system/usr/idc/ && chmod 644 /system/usr/idc/clearpad.idc
7. Remount /system as read-only and reboot.
Code:
mount -o remount,ro /system /system && reboot
Well, this worked for me, and as I know there are lots of people out there irritated by this problem, this should provide a proper
method for restoring the functionality for their Z1's. Now a greasy screen and slight moisture would not upset the touch screen unlike before.
p.s. I'm on NUT's .290 with C6903. This should also work for other models and Android versions.
If this worked for you, then please kindly click on the THANKS button down below <3

I posted this fix already.
I have already posted this fix in 2 threads.

I just did, after testing will post my results
Enviado desde mi C6906 mediante Tapatalk

aznrogerazn said:
Since there's no thread about fixing this here in Z1's forum, I'd make one with possible fix on the crazy touch screen problem.
As far as I know, this is a firmware-related problem, and can be fixed by tweaking down the touch screen sensitivity. You'll need
to be rooted to use this modification. Always remember, try at your own risk, and don't forget to hit thanks button if I helped!!
HOWTO:
1. Take a backup with CWM or TWRP.
2. Use any root explorer that you like, and navigate to /system/usr/idc/.
3. Copy the file "clearpad.idc" to somewhere else, like the SDcard storage for editing.
4. Open up the file with Jota+ or the text editor of your choice, and find the line "touch.filter.level". By default it would be 2, but
here I would suggest a value of either 5 or 6 for lowered sensitivity.
Code:
touch.filter.level=6
5.Save the file and then mount /system as writable.
Code:
mount -o remount,rw /system /system
6. Paste the modified clearpad.idc back to /system/usr/idc/ and set correct permissions.
Code:
cp clearpad.idc /system/usr/idc/ && chmod 644 /system/usr/idc/clearpad.idc
7. Remount /system as read-only and reboot.
Code:
mount -o remount,ro /system /system && reboot
Well, this worked for me, and as I know there are lots of people out there irritated by this problem, this should provide a proper
method for restoring the functionality for their Z1's. Now a greasy screen and slight moisture would not upset the touch screen unlike before.
p.s. I'm on NUT's .290 with C6903. This should also work for other models and Android versions.
If this worked for you, then please kindly click on the THANKS button down below <3
Click to expand...
Click to collapse
too bad, it doesnt work. tried change to 1 or 7, but problem still exist.
there is already other thread talking about tis.

chunlianghere said:
too bad, it doesnt work. tried change to 1 or 7, but problem still exist.
there is already other thread talking about tis.
Click to expand...
Click to collapse
then what can we do?

rasoooli said:
then what can we do?
Click to expand...
Click to collapse
Ive got the problem too with no AFS on the phone ://
Currently, Im able to solve the problem by wiping the phone for like 10secs with my tshirt. After that the touchscreen ALWAYS works flawlessly for like 5 mins. Im going to buy a new protector tomorrow and hope that that is going to fix this issue!

Richylitschy said:
Ive got the problem too with no AFS on the phone ://
Currently, Im able to solve the problem by wiping the phone for like 10secs with my tshirt. After that the touchscreen ALWAYS works flawlessly for like 5 mins. Im going to buy a new protector tomorrow and hope that that is going to fix this issue!
Click to expand...
Click to collapse
Hi everybody!
For me, if i turn off the screen (only with the power button, nothing more), the problem fix during some time (sometimes 5 minutes, sometimes hours).
I have the latest stock version, locked bootloader and rooted. Xperia Z1 C6093.

i think the many problem with the touch screen is by taking of the asf that sony puts on these phones. i took it of 2 days ago and since then it was always doing strange touchscreen things like making selections out of it's own or thinking there where 2 fingers on the screen.

omaroe666 said:
i think the many problem with the touch screen is by taking of the asf that sony puts on these phones. i took it of 2 days ago and since then it was always doing strange touchscreen things like making selections out of it's own or thinking there where 2 fingers on the screen.
Click to expand...
Click to collapse
mine never take out ASF already have strange touchscreen