Database Develop

g1 button remap for global search?

With the latest release of cyanogens update I started using the global search which I really love but unfortunately htc didn't give us a search button like the mytouch 3g has, I also find that I don't use the camera button at all so is it possible to remap the camera button to function as a quick launch for the global search like we can remap the end key?

I was wondering the same thing.
I have been looking at the filesystem & the /system/usr folder contains the folders "keylayout" and "keychars".
Inside the keylayout folder are several .kl (presumably .kl stands for key layout) files. If you edit them you should be able to change what ANY key on the device does, in theory anyway.
The qwerty.kl & trout-keypad.kl files appear to be the same unless I am missing something. They seem to be the layout files for normal US Dream devices. There is also trout-qwertz.kl which seems to be for the French QWERTZ key layout. I don't know how the trout-keypad-v2.kl & the trout-keypad-v3.kl are different from the traditional trout-keypad files, however you can look at that yourself.
I am looking at the trout-keypad.kl file for my ADP1 and am kinda struggling with a few of the keys. Obviously all I believe you have to do is change the line:
"key 212 CAMERA" to "key 212 SEARCH"
The SEARCH label is typically mapped to key 127.
However, I am at a loss as to what key 211 could possibly be, it is labeled as FOCUS, could it be when you press the camera key halfway down to focus in the camera app & key 212 be fully pressed?
I will do a little exploring & I will post back with my test results when I push the file to /system/usr/keylayout on my device later. Since they are just files I don't believe that you need to resign an update that contains them, you should be able to just push them to the device.
If it works I will upload the modded file here.
EDIT 1: You should also be able to add the tag WAKE in the next column over (where the other WAKE or WAKE_DROPPED tags are) if you want that key to wake the device.

Yeah I saw those files but can't do anything with them atm since I'm out and about but I assumed that they pertained to the slideout keyboard only so Ill look at them when I'm home.

They appear to be for ALL keys on the device, there are also some for BT headsets.
I updated all of the files with the camera & focus keys mapped to search, however it accomplished nothing. It still launches camera. I am running the JACxROM, but I am gunna try it with my old CM 3.6.8.1 build (which I preferred over JACxROM anyway). I'll post back later.

Geniusdog254 said:
They appear to be for ALL keys on the device, there are also some for BT headsets.
I updated all of the files with the camera & focus keys mapped to search, however it accomplished nothing. It still launches camera. I am running the JACxROM, but I am gunna try it with my old CM 3.6.8.1 build (which I preferred over JACxROM anyway). I'll post back later.
Click to expand...
Click to collapse
I was wondering if u edited the zip file then flashed it. Maybe that might help. I was thinking of doing something like this for myself but wasnt sure where to start

All I did as of yet was change the files, push them, and reboot. I am in the process of making an update and flashing it. Also, it didn't work with the first method on the CM build. The update I am signing will be based on the CM build.
One thing I also don't understand, is the *.kcm.bin files in the keychars folder. When I open them in a hex editor I cant understand them, are they encrypted, do they need unpacked, am I just an idiot??
EDIT: I'm an idiot. Just pushing the files doesn't work. For whatever the odd reason, it seems you have to package them in an update.zip file & sign them. It works great now. You can either push the button halfway down (FOCUS) and it will pop up, or push it all the way down (CAMERA) and it will pop up.
I can't upload the whole CM update (don't have the bandwith) but I will try to make an update.zip that contains just the new files (kinda like a theme update.zip file) and upload it.

Ok. I can't figure out how to make a plain update.zip with the files needed.
I put them in an update.zip file containing two directory trees:
META-INF/com/google/android/ which contains update-script (my custom one for this)
and
system/usr/ which contains all of the .kl files that needed modified.
My update-script file is as follows:
copy_dir PACKAGE:system SYSTEM:
What am I doing wrong? Whenever I try to flash the update I get an error that says "Syntax error in update script". I'm using the same convention used in theme update-script files. What should I do?
PS: The update is being signed, I'm not that stupid

Geniusdog254 said:
Ok. I can't figure out how to make a plain update.zip with the files needed.
I put them in an update.zip file containing two directory trees:
META-INF/com/google/android/ which contains update-script (my custom one for this)
and
system/usr/ which contains all of the .kl files that needed modified.
My update-script file is as follows:
copy_dir PACKAGE:system SYSTEM:
What am I doing wrong? Whenever I try to flash the update I get an error that says "Syntax error in update script". I'm using the same convention used in theme update-script files. What should I do?
PS: The update is being signed, I'm not that stupid
Click to expand...
Click to collapse
Cool I can't wait for this. If all goes well I can remove the search widget to free up space and memory. U should drop this by cyanogen so he can include it in the next update. I'm sure this would go great with the global search once the bugs r worked out of it.

Well since I can't figure out the stand-alone update.zip here are the plain files so that you can just add them to /system/usr in your update.zip of choice and re-sign it. I have PMd Cyanogen about this and will see what he says.
Glad I could help guys!
EDIT: Words of caution. I am not responsible if you screw up with this. Also, if you just press the camera button it will bring up the search box, but if you hold the camera button it brings up Voice SEARCH (not voice dial)
EDIT 2: I've added two new versions. The "keyboard_mod_cam-norm_focus-search.zip" file makes it so if you press camera completely down then it still opens camera, but if you just press it halfway down (to focus mode) it brings up search. Holding it at halfway still brings up voice search *see edit three*.
The "keyboard_mod_cam-search_focus-norm.zip" file makes it the opposite. Pressing all the way down opens search, pressing halfway down still focuses if you are in the camera app. Holding it all the way down still brings up voice search *see edit three*.
And of course the original file stays the same. Either position brings up search and holding still brings up voice search *see edit three* from any position.
EDIT 3: OK, it seems that voice search is only activated on a long press on CM 3.6.8.1! If you are using the latest (CM 3.9.11.2) it does NOT activate voice search anymore.

Can't you just use the original update and replace what you need in there?
Ok whoa you work fast but thanks for it! Hopefully cyanogen considers adding a setting for it, thanks so much!

thelamacmdr said:
Can't you just use the original update and replace what you need in there?
Ok whoa you work fast but thanks for it! Hopefully cyanogen considers adding a setting for it, thanks so much!
Click to expand...
Click to collapse
Yea thats exactly what I had to do to make it work, just replace the files in the original update and re-sign it then flash it. You can use any of the versions I posted to replace the files and it will work for you too.
And no problem. I haven't gotten a reply from Cyan yet but I did PM him.
Thanks for the compliment btw lol.

Ha ha well great job! Can't wait to get home and flash with this in it =D.

worked great thanx! i used ADB File Explorer v0.3 by makethetick makes pushing and pulling apk's a brezze no need to remember commands! if anyone would like to try it head over here, its the the op a few headers down
http://forum.xda-developers.com/showthread.php?t=532719

Hmm. It worked for you by pushing? I couldnt make it work that way, I had to flash a custom update that I put the files in. Did you do anything extra? Change permissions? Did you reboot? Check if it still works after a reboot, because mine didnt.

its still working after at least 4 reboots. did u pull out the stock files b4 u pushed it? in the abd file explorer i deleted the stock then just pushed from there. as of now this is my 5th reboot (once i find a setting i like i get update my nandroid). if u need to drop my a line faster than the forum check my signature for my gmail

Using the JacHero 2.1 which has camera key remapped to search. Don't seem to be able to reassign to camera - what's the keycode for the G1's camera button? Thought it was 211 (focus) 212 (take piccy).
Oh I should probably say hi - first post lol. I'm a bit n00bish but I have successfully reflashed this G1 5 or 6 times with different roms and haven't asked loads of questions without reading instructions - but can't figure this camera issue out. Cheers
Sorry about this post! All info was supplied earlier in thread! Mustve been a long day at work that day!

Android Market and AOSP

Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.

someone needs to close this thread before this flame war gets any bigger

tekgek said:
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you tried just pushing with adb? By development do you mean cooking or compiling your own?

Please be respectful of others ...
I taken the time to cleanup this thread and move to Q&A where it should have been. If someone has an answer post a reply; plans to respond using trolling tactics are ill-advised.
If the thread goes OT again, a moderator will be forced to close it and likely remove it ... would be nice if it didn't have to come to that.
Regards,

I am building this directly from AOSP, from scratch. Thanks to the mod for cleaning up the flame war, by the way

Oh, from AOSP. How are you adding them in? AOSP does NOT include the Google Apps by default, I'm not expert in ROM building but I am sure there are some .libs needed (I know GTalk requires some) and possibly need the other Google Apps as well.

And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
./adb install alpha-1-signed/system/app/Vending.apk
898 KB/s (1274068 bytes in 1.384s)
pkg: /data/local/tmp/Vending.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Click to expand...
Click to collapse
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
EDIT: For all of you who are currently viewing this thread, how many of you would like a very fast (possibly faster than OpenEclair), stable, no-frills Android 2.1 ROM? I would like your opinions, because this will give me a good idea of how many people would be interested in this kind of thing.
Tekgek

tekgek said:
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
Tekgek
Click to expand...
Click to collapse
It's good to know that you are missing libraries
Your best bet is to compile your rom, and then compare it to a rom that already has the google apps included (WesGarner build, CSDI, etc...) and see what libs are missing from yours, add them in and then try again

I was having the same problem too. I am gonna try this too.
And ya besides the libraries, the aosp build doesn't include some of the framework files and permission files too, like the framework files relating to gtalk and google maps should be added as well to the system/framework folder and the permission files in system/etc/permissions relating to gtalk and maps should be added as well.

I tried with all the missing libraries but with no luck...there must be some other files tooo. Gonna continue on Thursday.

Did you try resigning the apk file?

Not really. I am gonna try that too. Got coll tomorrow so may be later tomorrow. By the way did you got the video working?? I tried pushing some libraries from supereclair. But not workin till date. it works in his build though.

College is more important than android, imho. whenever you get the chance .
I hope to get video working in the future, but not right now. My primary computer (the core i7 rig I use for all my computer work) needed an OS reinstall, so I have made no progress since my post on ADB. My fist priority is to get the basics working, then I'll work on the other issues, like video playback and the camera. However, as of right now, I am re-downloading the source, and hopefully building it in the very near future, expect an update tomorrow, and maybe even a finished product (keep in mind that this is ALPHA, so don't expect anything wonderful).

Alright, I got it... mostly. The market appears installed, now all I need to do is make it not crash. Whenever I select the market app, I get a white screen, and then the home screen. I'm also getting a force close on the gapps process. What am I doing wrong

How did you got market show up???
The gapps framework file is also missin in the /system/framework folder in AOSP build.
Did you tried pushing the missing file?

I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.

tekgek said:
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
Click to expand...
Click to collapse
ya its com.google.android.gtalkservice.jar

okay, added it in, still getting a force close on the gapps. Where to go now???

As i mentioned earlier there are some files missing in system/etc/permissions. Did u tried pushing those files.

All permission files are in place, all gapps are resigned. The framework is in place. The setup wizard i also resigned, which now crashes. If anyone has any suggestions please post them. I am at my wit's end here.

[MOD] Display A Custom PLMN (with no SPN)

I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper

Very cool mod. I will try this out when I have the time!

thank you

Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?

Hey could you make me one and either PM me or post it up?

I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?

How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"

Did not work on Modaco R9, CM7 or The Cracker builds...

nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.

I have all the files in the proper folders but it still doesn't work. Modaco R9

for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.

tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.

Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t

Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

[MOD] Front Facing Video fix for AOSP builds

In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
********Update********
it may be necessary to clear data on camera/gallery app after updating the media_profiles.xml file
also adding flashable zip file

ej1911 said:
In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
Click to expand...
Click to collapse
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....

jco23 said:
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
Click to expand...
Click to collapse
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.

ej1911 said:
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
Click to expand...
Click to collapse
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM

jco23 said:
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
Click to expand...
Click to collapse
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.

ej1911 said:
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
Click to expand...
Click to collapse
got it working now.
i downloaded the file this time, e-mailed it to myself, copied it to the "system/etc" folder, changed permissions, renamed the org as .bak, renamed the new file as .xml, then rebooted. after reboot, I went into the camera app and once again got a force close. however, I tried playing around with the settings "record mode" from 1020 to 480, and then went back to FF camcorder, and it recorded! I then changed the "record mode" back to 1080, and FF camcorder worked just fine.
so I think you are correct, perhaps one needs to clear cache/data in the gallery prior to use.
thanks for the tip and the mod! nice work!
to resolve your AOSP keyboard force closing problem, try wiping system before installing the update. this worked for me.

Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )

The flashable zip worked perfect for me. Thank you so much!
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com

arrrghhh said:
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
Click to expand...
Click to collapse
Argggh merged it into cm code. All it should flow to all ROMs as they sync and build.
Sent from my XT907 using xda app-developers app