Related
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
ro.product.device=holiday
Click to expand...
Click to collapse
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Do not use these settings if you own a rogers/Bell HTC raider! Changing them will turn all of your X710a's pictures/video blue! I can not speak for other versions of the raider but the x710a is affected. I just figured this out after playing with all the settings in the camera app, and I even contemplated calling HTC!!! I had to revert the values back to original to get the camera to work normally.
Hmm, I noticed that issue to but just thought it was the Rom. That's interesting. Anyways, I fiddled around with the settings and discovered that it was this line that messing up the camera
ro.product.device=pyramid
So I'd recommend the switching this back to 'holiday' and when you need/want to download (or update) an app, simply switch this back to 'pyramid' and when your done restore it back to holiday.
What are the apps that we are expected to gain? Can you give us an idea what we are missing out on?
You can't know your limits until you exceed them.
The apps I gained were GTA3, Order and Chaos Online, Snapdragon GameCommand, and Desert Winds.
has anyone tried playing order and chaos after changing the file name back to correct the camera issue? I have read elsewhere that the game will give you issues on rooted devices
Spartoi said:
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Click to expand...
Click to collapse
This method doesn't seem to work anymore.. in the play store it will still list it as incompatible.. unless there is something else needed to be done?
I have flashed Miracle v4 for my phone.
Following the tutorial, i was able to get stuff like camera and calculator works.
But was unable to get sound recorder to work, it force closes everytime i press 'start recording'.
Any help ? Thanks in advance.
There now is a fix for it. Read the first few posts in the original Miracle V4 thread you should find the solution there!!
Thanks.
I read thru the first few posts again.
If you are talking about the tutorial which is this :
TUTORIAL 5: Recover System Apps than have been removed from V3
-- Place your desired app or apps on your sd-card
-- Use Root Explorer and copy them
-- Go to system\app and press the Mount R/W button on right top
-- Paste the app or apps you have selected
-- Long press what have you just pasted and set permissions to rw-r--r-- for each app
-- Reboot phone
Yes, i followed this. Was able to recover apps like camera. But sounds recording doesn't work.
If i misses out something, can you help me with pointing me to the particular fix for it ? I've done searching, and no people seems to be asking about sound recorder.
Thanks
rhythmyun said:
Thanks.
I read thru the first few posts again.
If you are talking about the tutorial which is this :
TUTORIAL 5: Recover System Apps than have been removed from V3
-- Place your desired app or apps on your sd-card
-- Use Root Explorer and copy them
-- Go to system\app and press the Mount R/W button on right top
-- Paste the app or apps you have selected
-- Long press what have you just pasted and set permissions to rw-r--r-- for each app
-- Reboot phone
Yes, i followed this. Was able to recover apps like camera. But sounds recording doesn't work.
If i misses out something, can you help me with pointing me to the particular fix for it ? I've done searching, and no people seems to be asking about sound recorder.
Thanks
Click to expand...
Click to collapse
Just download the latest version. It has a the video recording fix, BLN fix and 30volume step
Recording sound for me works perfectly, no FCs.
no it's not about that, it's something to do with video recording as well. There is a fix there I managed to sort the problem out myself. Alternatively you could redownload v4, the dev has now updated the original rom with the fix's added.
My video recording is working after changing the "true false" code stuff (not sure what it is called)
However the sound recording doesnt work.
I guess i will just do a reflash.
But an extra question, if i do a reflash, do I have to re backup all my apps and data ? Or i can just reflash without going to factory reset, dalvik wiping etc ?
Thanks
You can just flash over the top but you might have to reinstall some of you stock apps ie sms, music, gallery ect..
Thanks guys. I reflashed and it is working now.
My sound recorder works but in 3gp format. Is there a way to make it mp3 or whatever format?
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
Android 7.0+ See this
Donated
@Charles_l |
@drago10029 |
@LluisAzm |
@spitsyn Sergey |
@vexierspiegel |
@starbase64|
@ Anders Grandt|
@ Singgih Putra -Mi 4c Indonesia|
@ Shaneel Chanderpaul | @sopebird
$150 needed for new device
OLD OP for Android MM and 7.0
::::::::::::::::::::::::::::::::::::::::::::::::::::: 6.0 / 7.0 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Extract libmmcamera_imx377.so from this https://www.androidfilehost.com/?fid=457095661767120784
Using Some Root File Browser/Explorer
Copy libmmcamera_imx377.so to /vendor/lib/ if file size shows 0b then vendor tripping .
In Case vendor/lib tripping delete libmmcamera_imx377.so from vendor/lib/ and copy modded lib to /system/lib/ instead
Set Chmod 644 or rw-r-r permission
Reboot
Install This APK https://www.androidfilehost.com/?fid=385035244224403590 give requested permissions
In API Camera 2 Select 1080pHS Video Profile > Record Video
it may FC on First Run is a known bug
Should Work FOR MM/N some 7.1.1 roms might be give some trouble consult your rom dev
If you press record but it does not start recording switch to pic mode take a picture switch back to movie mode then record
Trouble with mounting vendor renaming copying Check this GUIDE
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: OLD MM ONLY BELOW :::::::::::::::::::::::::::::::::::::::::::::::::
Code:
[HIDE][STRIKE]Made this app to make it easier to copy modified Libs
There three things you can do with the
Backup original lib
Install Modified lib
Install Custom Media Profile .
The lib may work Nexus 5X as Well.
To get 60fps working
1. Install Lib Changer.
2. Install Freedcam.
3. Run Libchanger
3.5 Grant app root permission
4.Tap on the blue are with SELECT MOD
5.Select 60fps_1080p you be asked to be reboot .
6. After Reboot relaunch lib Changer if freedcam is installed Tap on the Yellow Area to install Custom media profile.
7.Start Freedcam In the menu scroll down to api tap on it and select camera1 make sure it's not in camera 2 mode.
8. Scroll up whilst still the menu select 1080pHFR in video Menu if its not showing exit relaunch lib changer repeat step 6.
9. If had to repeat step 6 start freedam then in mode select right side of ui select Movie Mode if video profile is set to 1080HFR and lib is applied click on the shutter button to start Recording .
10. Enjoy 60fps Video
Latest Freedcam Build -?> [url]https://github.com/troop/FreeDcam/releases[/url]
Sample Video [media=youtube]UBMuIA0vkdc[/media]
Update ::::::::::::::::::::::::::::::: 11/18/2016 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
app-release.apk Supports N and MM also added HTC10 60fps[/STRIKE][/HIDE]
For Stock Camera See this post
http://forum.xda-developers.com/showthread.php?p=70748865
Having issues getting 1080pHFR, after doing step 6, i go into settings, make sure the API is set to camera 1, and check the video profile,
1080pHFR doesn't show up, so i repeat step 6, reopen the camera select movie mode, go into video profiles and 1080P HFR still doesn't show up, any ideas?
defcomg said:
Made this app to make it easier to copy modified Libs
There three things you can do with the
Backup original lib
Install Modified lib
Install Custom Media Profile .
The lib may work Nexus 5X as Well.
To get 60fps working
1. Install Lib Changer.
2. Install Freedcam.
3. Run Libchanger
3.5 Grant app root permission
4.Tap on the blue are with SELECT MOD
5.Select 60fps_1080p you be asked to be reboot .
6. After Reboot relaunch lib Changer if freedcam is installed Tap on the Yellow Area to install Custom media profile.
7.Start Freedcam In the menu scroll down to api tap on it and select camera1 make sure it's not in camera 2 mode.
8. Scroll up whilst still the menu select 1080pHFR in video Menu if its not showing exit relaunch lib changer repeat step 6.
9. If had to repeat step 6 start freedam then in mode select right side of ui select Movie Mode if video profile is set to 1080HFR and lib is applied click on the shutter button to start Recording .
10. Enjoy 60fps Video
Latest Freedcam Build -?> https://github.com/troop/FreeDcam/releases
If you like my work donate link in my profile
Click to expand...
Click to collapse
Thanks @drago10029 and @jal3223 for testing
DeathSentinels said:
Having issues getting 1080pHFR, after doing step 6, i go into settings, make sure the API is set to camera 1, and check the video profile,
1080pHFR doesn't show up, so i repeat step 6, reopen the camera select movie mode, go into video profiles and 1080P HFR still doesn't show up, any ideas?
Click to expand...
Click to collapse
Same here all I see is 720phfr which fails
DeathSentinels said:
Having issues getting 1080pHFR, after doing step 6, i go into settings, make sure the API is set to camera 1, and check the video profile,
1080pHFR doesn't show up, so i repeat step 6, reopen the camera select movie mode, go into video profiles and 1080P HFR still doesn't show up, any ideas?
Click to expand...
Click to collapse
Hmmm try going into DCIM/FreeDcam/config/ and delete CustomMediaProfiles.text retry 6 or copy it manually attached it below
defcomg said:
Hmmm try going into DCIM/FreeDcam/config/ and delete CustomMediaProfiles.text retry 6 or copy it manually attached it below
Click to expand...
Click to collapse
Copying from the .text file and replacing my current profile worked perfectly!,
Thanks for the quick reply and the help, its appreciated!
defcomg said:
Hmmm try going into DCIM/FreeDcam/config/ and delete CustomMediaProfiles.text retry 6 or copy it manually attached it below
Click to expand...
Click to collapse
That worked but the file properties are still 1080/30
---------- Post added 24th July 2016 at 12:19 AM ---------- Previous post was 23rd July 2016 at 11:58 PM ----------
Seems the app isn't replacing the lib file.
joeyddr said:
That worked but the file properties are still 1080/30
---------- Post added 24th July 2016 at 12:19 AM ---------- Previous post was 23rd July 2016 at 11:58 PM ----------
Seems the app isn't replacing the lib file.
Click to expand...
Click to collapse
Strange its working 100% but my device is not running marshmallow something similar happened during testing where libs stayed the same even after replacing them will try and delete before copying over new ones think it's something to do with the root binary.
But I will attach the libs to whoever wants to copy them manually while I get that sorted
Extract the zip copy the file to system/vendor/lib/ delete or rename the stock lib by adding .bak to the end of the file name then copy it over set permission to rw-r-r
Libmmcamera_imx377.zip working 60fps
htcNexus2.zip experimental 80fps+ 1080p
Flashable Zip Nexus 6P/5X provided by @przemcio510
defcomg said:
Strange its working 100% but my device is not running marshmallow something similar happened during testing where libs stayed the same even after replacing them will try and delete before copying over new ones think it's something to do with the root binary.
But I will attach the libs to whoever wants to copy them manually while I get that sorted
Extract the zip copy the file to system/vendor/lib/ delete or rename the stock lib by adding .bak to the end of the file name then copy it over set permission to rw-r-r
Libmmcamera_imx377.zip working 60fps
htcNexus2.zip experimental 80fps+ 1080p
Click to expand...
Click to collapse
I'm running pure Nexus rom btw. When I looked in the lib replacer install folder there is a lib folder under that but it's empty if that helps
joeyddr said:
I'm running pure Nexus rom btw. When I looked in the lib replacer install folder there is a lib folder under that but it's empty if that helps
Click to expand...
Click to collapse
Did you give the app SD card access ?
it stores the temp lib in sdcard/Libchanger/ I also just remembered the 6p vendor is another partition and not part of /system so try /vendor/lib/ path
It should work on all MM ROMs these lib stays pretty much the same
Works!! Been waiting for something like this since the launch of this phone! One question: is it possible to make this mod work on different camera apps (for example: google camera)?
MrTemz said:
Works!! Been waiting for something like this since the launch of this phone! One question: is it possible to make this mod work on different camera apps (for example: google camera)?
Click to expand...
Click to collapse
Possibly via smali editing
defcomg said:
Did you give the app SD card access ?
it stores the temp lib in sdcard/Libchanger/ I also just remembered the 6p vendor is another partition and not part of /system so try /vendor/lib/ path
It should work on all MM ROMs these lib stays pretty much the same
Click to expand...
Click to collapse
So I manually replaced it and it's working but seems to of killed the slow motion option in Google camera.
joeyddr said:
So I manually replaced it and it's working but seems to of killed the slow motion option in Google camera.
Click to expand...
Click to collapse
It kills only 120fps only 240fps is untouched
defcomg said:
It kills only 120fps only 240fps is untouched
Click to expand...
Click to collapse
Google camera crashes when I select slow motion from the menu.
joeyddr said:
Google camera crashes when I select slow motion from the menu.
Click to expand...
Click to collapse
Hmm weird but I can workaround it so freedcam outputs 720p at 240fps .
Or try copy stock lib then in Google Camera select 240fps exit copy back modded lib and try reopen Google camera see if it crashes .
Third possible option is to trick it into thinking 60fps is actually 120fps so when it looks for it no crash happens
Here is a log of the crash.
Also want to say that if I use the 5:4 lib Google camera does not crash but I don't have the 120/240 option
joeyddr said:
Also want to say that if I use the 5:4 lib Google camera does not crash but I don't have the 120/240 option
Click to expand...
Click to collapse
Right that lib was capped to 120fps but actually outputted at 240fps .
Attached lib with the same cap in freedcam select 720pHFR it will record at actual 240fps which you can slow down in post.
I do not understand how you want to explain a simple step by step. I try to follow the steps you teach. It has not been a resolution of 1080p 60fps.
Hi folks,
Using stock OOS (4.1.6 from last year) and the stock camera, I get a green screen instead of the picture for any picture taken with A-HDR mode, which seems to be the default and I can't get it to persistently turn off.
Anybody else seeing this, and is there a fix? I've updated to a recent version of the camera without solving it (though, if I open camera, and change to HDR instead of A-HDR, it works for a while).
PRobably time to update my OS but everything else is working...
Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
rdNNNN said:
Had the same thing happening me before. Fixed it by setting the right permissions on build.prop rw-r--r-- AFAIK
Click to expand...
Click to collapse
Frankenscript said:
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
Click to expand...
Click to collapse
HOT DAMN!
That seems to have fixed it. No idea why, but THANKS MATE!
may i know how to fix this? what build.prop file? can someone guide me step by step on this?
Frankenscript said:
Interesting! The build.prop file itself needs to have these set? How bizarre that they might get set wrong. I'll investigate and report back.
Click to expand...
Click to collapse
/system/build.prop is definitely installed with 0644. There is no conspiracy "they", who changed the shipped permissions, but it has been done by you. Most probably: build prop editor, copy build.prop with something, that doesn't honor the perms of the existing file, but unlinks and recreates the file with a umask of 666 (i.e. esexplorer) or a flashable zip manupulating build.prop. This list is far way from completeness.
BTW: you'd also check (and fix if necessary) the selinux context!
SlaJaZz said:
may i know how to fix this? what build.prop file? can someone guide me step by step on this?
Click to expand...
Click to collapse
As you can see above, many things can go wrong when messing with build.prop. As long as you don't know what you are doing, I highly recommend to enpower yourself to check and change permissions on a system file by knowledge. For now do a clean flash (including format of system), and all system files will have the shipped (and correct) permissions and sepolicy context - until you do something, that changes these.