Develop Bugs

[APP] Hacked Camera.apk

Hi,
--JPU version--
i modded the Camera.apk a bit.
Changes:
-take Pictures with pressing power button.
-Take pictures even if your battery is at 2%
You can apply it with my SGS Tools app or push it manually to /system or with Muspelheim (http://softdevs.wordpress.com/muspelheim/)
If you are not on JPU or newer, choose Camera_old.apk !
See the code changes here
Changelog:
Version 4:
-based on jpu
-exif data correct again
Version 3:
-focus before taking picture when using power key (not sure about it)
Version 2.
-use the power key instead of volume keys
Version 1
-initial release

Wow looks awesome, will try it! thanks

omg, i needed this last night... went to U2 concert and phone batt was too low (stupid me!!! lol).
Thanks anyway buddy, top stuff! Will give it a test run soon

Cool. So how do we zoom now
Sent from my GT-I9000 using Tapatalk

Does it eliminate auto-geotagging?

ickyboo said:
Cool. So how do we zoom now
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Pinch 2 zoom.
AnnihilatorSC said:
Does it eliminate auto-geotagging?
Click to expand...
Click to collapse
No.

gonna take a shot at the music player low battery aswell?

Hey thanks. Didn't relize that pinch zoom worked in camera. Nice work!
Sent from my GT-I9000 using Tapatalk

Just tried it mate, the volume buttons are still assigned to zoom?

any particular f/w is this for froyo only or also eclair?

AnnihilatorSC said:
Does it eliminate auto-geotagging?
Click to expand...
Click to collapse
This would be a welcome addition

Update:
-Vol down/up reassigned to zooming.
-press power button for taking picture.
-batt hack still included (still untested though^^)

Nice. Work. Testing now.

MAMBO04 said:
Just tried it mate, the volume buttons are still assigned to zoom?
Click to expand...
Click to collapse
Then something went wrong, if you installed it via my app, check if busybox is installed.
lgkahn said:
any particular f/w is this for froyo only or also eclair?
Click to expand...
Click to collapse
Should work on all froyo firmwares, not sure about eclair.

I tried upgrade Stock Apps from SGS Tools, but nothing happens. No Change.
No point in Upgrade Stock Apps is changing my System.
Edit: Stupid. I forgot the checkbox.

You have root and busybox is installed?
Next version of the app will show if there appears errors while applying..
Edit:

Fr4gg0r said:
You have root and busybox is installed?
Next version of the app will show if there appears errors while applying..
Click to expand...
Click to collapse
No everything works. Was my error, your app is working. The hacked cam is really nice.

Some suggestion for hacked gallery3d: enable autorotation at start and disable on exit.

Great work! Was searching earlier this week for an hack/app that would use the power button als capture button but could only find a very old thread about this on XDA.
Wondering why someone didn't attempted this before, it seems so natural. Samsung should have made this the default behavior in the first place, locking the camera with the power button caused pain when I accidentally pressed it the first time I got my SGS and it wouldn't respond..

Lynchy30 said:
This would be a welcome addition (geotag off)
Click to expand...
Click to collapse
Indeed it would. Either making it a selectable option or disabling it altogether is fine by me.
Nice work, btw.

[Q] Circle button recognized as back button and not acrual game button

Here's my problem: ever since I flashed CM7 and tried to tolerate all the FXProject defects (eg. No touchpads for Dead Space, no camera, no haptic feedback /vibration, no flash, etc.), there was one of those defects that really hurt me from inside... the fact that the circle button is treated ONLY as a back button, and not a game button. I'm aware there are files in the internal flash memory that set the phone's key layout (/system/usr/keylayout/) but I'm just to lazy to figure it out so I'll leave the question to the pros on the forum: How to fix it? I bought this phone considering I'm a dedicated gamer (still have a life tho ) and not being able to kick the opponent's face in Bruce Lee and every other kind of silly stuff you could do with this epicness we call Circle button is just pathetic. You could send me the Original stock rom key layout file(s) so I can replace/compare and fix. Thanks in advance

For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk

AndroHero said:
For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks

DanielEGVi said:
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks
Click to expand...
Click to collapse
On the pad, the default android actions are X=Ok or select and O=Back, Xperia play optimised games work in conjunction with the sony firmware to ignore the default android action while in a game thus allowing you to use the buttons for game inputs. If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
"Built from source" just means the rom was compiled from the source code provided by the Android open source project (Asop)

AndroHero said:
If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
Click to expand...
Click to collapse
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.

DanielEGVi said:
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.
Click to expand...
Click to collapse
It dosent happen for every game. For example gameloft games can use the O button no probs. Maybe you can get the results you want with a button mapping app. I think there is one in themes and apps

BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?

johnsongrantr said:
BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?
Click to expand...
Click to collapse
It is STILL a problem, but this thread will die and nothing will stop that. Sorry.
I already gave up and flashed Stock ROM and with lots of effort I have found nothing on the interwebs that serves as a fix to the O button. That's sad isn't it.

I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway

jacklebott said:
I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway
Click to expand...
Click to collapse
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...

DanielEGVi said:
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...
Click to expand...
Click to collapse
Nope, square is BUTTON_X and triangle is BUTTON_Y

i meant button_b but regardless, the keylayout is identical to the stock on aosp. I think the problem might be in the kcm binaries rather than the keylaout files. It's a theory I'm looking into

Remapping the home button

Ive been trying to make my home button function the same as the power button. First I made a nandroid and rebooted andthen went here--> System/usr/keylayout/generic.kl and changedkey# whatever-said-home to say POWER. rebooted and it didn't work, it worked just like normal. Then I went back and changed every key that said home to power anywhere in the keylayout directories and still, it works like normal! Any advice or knowledge to help me solve this puzzle?
Thanks!
Sent from my Kangadore 64

I'm on an aokp build BTW and I tried the button remapping app as well. Stubborn button =
Sent from my Kangadore 64

Well for starters, did you reboot?
There should be a thread in one of the US variants forums that tells you about the key layouts.
Theres also an app that will give you info on what button you just pushed.
Been a while so cant remember the name and dont know if itll be compatible, but maybe someone else does and will chime in.
Sent from my SGH-T999 using xda app-developers app

I've rebooted with every change. I tried theapp that tells you what button you pushed but it doesn't show what the power or home buttons key in as, its in the FAQ of the app I don't know what the issue is, I can change other buttons around but this one refuses to cooperate.
Sent from my Kangadore 64

mrtoast said:
I've rebooted with every change. I tried theapp that tells you what button you pushed but it doesn't show what the power or home buttons key in as, its in the FAQ of the app I don't know what the issue is, I can change other buttons around but this one refuses to cooperate.
Sent from my Kangadore 64
Click to expand...
Click to collapse
You have to edit the sec-keys.kl file to whatever you want then reboot. Generic.kl only takes effect if sec-keys.kl isn't there. So edit sec-keys.kl then reboot and you should be golden
Sent from my Galaxy Nexus using Tapatalk 2

@OP....
Got a better idea. Download apex launcher, and download screen off and lock.....
Open apex settings, behavior settings, home button...
Have it launch screen off and lock when pressed. Your phone will now turn off when you press the home button from your home screen.
Viola

@elesbb That worked like a champ! Thank you very much
Sent from my Kangadore 64

mrtoast said:
@elesbb That worked like a champ! Thank you very much
Sent from my Kangadore 64
Click to expand...
Click to collapse
Could you be specific as to what you changed exactly. I am also interested in this...... Thanks!

mrtoast said:
@elesbb That worked like a champ! Thank you very much
Sent from my Kangadore 64
Click to expand...
Click to collapse
Glad it worked!
dls5375 said:
Could you be specific as to what you changed exactly. I am also interested in this...... Thanks!
Click to expand...
Click to collapse
all they did was change what function the home button does. Look at a few posts up to see the file they changed and it's quite self explanatory, you will see a list of four buttons and their default assignments. Then you can either disable one by putting a # in front of the entire line or change them to say make the home function as a camera button.
Sent from my SGH-T999 using Tapatalk 2

elesbb said:
Glad it worked!
all they did was change what function the home button does. Look at a few posts up to see the file they changed and it's quite self explanatory, you will see a list of four buttons and their default assignments. Then you can either disable one by putting a # in front of the entire line or change them to say make the home function as a camera button.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
OK, I got it....just change HOME to POWER and reboot....thanks

dls5375 said:
OK, I got it....just change HOME to POWER and reboot....thanks
Click to expand...
Click to collapse
No problem. Let us know if you run into any issues!

[Q] Enable Software Buttons

Is there any way currently to enable software buttons on this phone? I just can not stand capacative buttons, they are simply awful in my opinion.

edda123 said:
Is there any way currently to enable software buttons on this phone? I just can not stand capacative buttons, they are simply awful in my opinion.
Click to expand...
Click to collapse
The only way I see enabling them is by enabling One Hand Mode. Of course the screen size is reduced then. With root it may be possible.

If rooted, you can try this:
http://www.gizbeat.com/2021/disable-or-enable-the-on-screen-virtual-software-keys-in-android/
There are also a few 3rd party apps that may help on Play.

Maybe it is worth buying this phone if I can fully disable the capacative buttons. Root is something I always acquire so that wouldn't be an issue. Exciting!

edda123 said:
Maybe it is worth buying this phone if I can fully disable the capacative buttons. Root is something I always acquire so that wouldn't be an issue. Exciting!
Click to expand...
Click to collapse
This works with JB and KK. Not sure about LP and ZenUI. I can give it a try for you.

Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.

Disabling capacitive buttons
Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
In order to disable those annoying you need to edit "system/usr/keylayout/ftxxxx_ts.kl" rather than formers... As you know commenting those lines :
# key 158 BACK WAKE VIRTUAL
# key 102 HOME WAKE VIRTUAL
# key 139 APP_SWITCH WAKE VIRTUAL
:good:

Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
When I went to build prop to add it, it was commented out. I deleted # but still no softkeys

lordpipa said:
When I went to build prop to add it, it was commented out. I deleted # but still no softkeys
Click to expand...
Click to collapse
Edit the model number prop. If you have the 64GB/4GB WW version, go into:
build.ze551.dual.2p3GHz.prop
Add the line there
Code:
qemu.hw.mainkeys=0
Reboot and enjoy soft keys.

Harfainx said:
Edit the model number prop. If you have the 64GB/4GB WW version, go into:
build.ze551.dual.2p3GHz.prop
Add the line there
Code:
qemu.hw.mainkeys=0
Reboot and enjoy soft keys.
Click to expand...
Click to collapse
I have the 4gb/32gb. Still the same place?

lordpipa said:
I have the 4gb/32gb. Still the same place?
Click to expand...
Click to collapse
Should be if it's the 2.3GHz version (which I think all 4GB RAM builds are).
Give it a shot. Worst case scenario... Nothing happens and you try a different prop.

Harfainx said:
Should be if it's the 2.3GHz version (which I think all 4GB RAM builds are).
Give it a shot. Worst case scenario... Nothing happens and you try a different prop. [emoji14]
Click to expand...
Click to collapse
It did but takes a whole lot of space, lol. Tnx again!!

how to transparent softkey?

Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
does this require root access? (newb here)

Anyone tried on latest stock MM ww134?
I tried adding on buildprop and buildprop 2.3ghz. Reboot and nothing happens.

i am trying since couple of days, still no use..
adding qemu.hd.mainkeys=0 is not showing any keys, i have a ZE551 model, and editing the build.prop is not doing anything

[Q] How do I enable softkeys on the American Zenfone 2 4GB RAM model?

I've tried editing every build prop file in the system folder and it fails to add software buttons.

TR88 said:
I've tried editing every build prop file in the system folder and it fails to add software buttons.
Click to expand...
Click to collapse
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.

cmendonc2 said:
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.
Click to expand...
Click to collapse
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.

TR88 said:
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.
Click to expand...
Click to collapse
The one that makes the softkeys floating at the bottom?

cmendonc2 said:
The one that makes the softkeys floating at the bottom?
Click to expand...
Click to collapse
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.

TR88 said:
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.
Click to expand...
Click to collapse
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.

cmendonc2 said:
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.
Click to expand...
Click to collapse
That's most likely the case, I was just getting frustrated and installed the app without thinking, oh well.
I just want the navigation bar because, at least from my experience, most apps that superimpose the buttons are never the same. They won't appear at boot, interfere with the keyboard, and require a gesture to make them appear.

Doesnt gravity box have an option? Never tried it though.. just saying it might work.

i saw someone doing this but cant remeber where. Look in the develompent forum or in Google+ asus zenui beta development

I've been using this app for the last two years. I can highly recommend it.
http://forum.xda-developers.com/showthread.php?t=2270198

Install LP xposed, and LP gravity box, go to "navigation bar tweaks" and tick "master switch" "enable navigation bar" and soft reboot done =]

You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.

You could use one hand mode until you find a working one.
Sent from my ASUS_Z00AD using XDA Free mobile app

Use Pie Control from the market

rlaw said:
You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.
Click to expand...
Click to collapse
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk

TR88 said:
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk
Click to expand...
Click to collapse
Strange it worked for me perfectly.