Develop Bugs

[TOOLS] Screen ColourControl, Camera Enhancements, Screen Density, Boot Anim + MORE! - Samsung Galaxy Nexus

GALAXY NEXUS PHONE MODS
This is all part of the Galaxy Nexus ToolKit but I have made a new Thread for people who may not have noticed it, people who didnt need the ToolKit but may find some of the Mods useful or just people who want to talk about the Phone Mods specifically.
FUNCTIONS OF THE PHONE MODS SECTION V1.4 [GSM + LTE][13TH MARCH 2012]
Change the Screen Density (DPI)
CWM Recovery, Only 1 No in the Confirmation Screen
Camera Sounds (Disable/Enable Camera Shutter, Video Camera Shutter, Focus)
Camera Enhancements (Increase Video Bitrate, Sound Bitrate, Photo Quality)
Change WiFi Scan Interval (Time between scanning for new Wifi Access Points)
Startup Boot Animation Screen (Disable/Enable which affects Boot Time)
Screen Colour Control (Change Gamma Offset and Colour Multiplier)
--------------------------------------------------------------
DOWNLOAD
The Phone Mods are part of the Galaxy Nexus ToolKit. You can download the latest version *HERE* (no need to install drivers if you already have adb/fastboot drivers installed) and select option 18 in the Main Menu to enter the Phone Mods Section.
{
"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"
}
--------------------------------------------------------------
USAGE
STOCK ROM users will need to enter the Mods Section via the Galaxy Nexus ToolKit as most functions need an insecure boot image which is set up from the Model Selection Screen of the ToolKit. If you are running a CUSTOM ROM (with insecure boot image) then you can run the ModsSection.exe directly if you wish.
ALL Mods Section functions require you to be booted into Android and connected to the PC via usb with adb/fastboot drivers installed. If you havent done this already then refer to the Galaxy Nexus ToolKit Thread for setup instructions.
The Galaxy Nexus ToolKit and Mods Section are very tightly integrated and so is impossible to seperate the 2 parts unless I want to cut out Stock Rom users (which I dont) so please dont ask if I can split them up. I could but its just not worth it.
Lastly if you have any ideas for functions that can be added to the Mods Section or just want to discuss a particular function then feel free.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

*reserved for future use*

Already used your tool kit to root, unlock, and flash recovery!!! Awesome work you've done, it's too easy Glad to see you made a separate thread for this, I agree it got kind of lost in the original thread.
Sent from my Galaxy Nexus using Tapatalk

Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!

graymulligan said:
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
Click to expand...
Click to collapse
Thank you im sure your geeks learn alot from you lol
Disabling the boot animation knocks about 5 seconds off the bootup time and there are a few Roms with not very desirable graphics lol.
Please do report back I always welcome any feedback and ideas for additions.

I get an error when trying to backup the xml file...Any ideas?

Looks great . You don't happen to have a unix version?

If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
Are you using Franco kernel? Disable the fast usb charge.... Your good to go

MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
What Rom and kernel are you using?
Are you booted into Android and connected via usb cable before starting?
I dont know where the fast usb charge option is but as the previous user posted you can try to disable that and try again.
Also if you go back into the main ToolKit are you seeing the serial number under adb at the top?
Mark.

yyz71 said:
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
Click to expand...
Click to collapse
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot

MysticDeth said:
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
Click to expand...
Click to collapse
Glad it went well after the reboot
Mark.

io53 said:
Looks great . You don't happen to have a unix version?
Click to expand...
Click to collapse
I do want to have versions of the ToolKit for Mac and Linux if I can get some testers and/or people who can help me convert the scripts. Im guessing most of the scripts should work fine as they are just adb/fastboot commands but there may be differences with pauses and some search replace routines.
Do linux bash scripts work on unix?
Mark.

Wow.. that's more handy..
Thanks for the nee options being included in your tool..

What exactly does the camera enhancements option do?

Any news on the camera enhancement and weather it works?

bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)

frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..

bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
The enhancement does exactly what it states on the screen when you select option 4 in the phone mods section:
This mod focuses on the media_profiles.xml file in the /etc/ folder on your phone.
The x2 Quality Settings doubles the standard camcorder bitrate for 480P, 720P and 1080P [8M, 16M, 24M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 25000000.
The Medium Quality Settings push the camcorder bitrate up even more for 480P, 720P and 1080P [10M, 20M, 35M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 30000000.
The High Quality Settings push the camcorder bitrate up to the max for 480P, 720P and 1080P [14M, 30M, 50M] as well increase the Audio bitrate up to 128k and increase the Audio channels to 2. The duration setting has also been changed to 60 from 30 for the above formats. All the quality settings for the camera have been forced to 100 and the memcap setting has been pushed up to 40000000.
These 3 profiles are for testing and I hope you get improvements using them but if you want to you can customize either of them from the mods folder and push them back to your phone.
Click to expand...
Click to collapse
As for proof that the mod works I havent taken tests shots/videos with each mod but the stock bitrates for the camcorder are a bit low so increasing it can only benefit the quality of the captured image. Whether the highest setting is neccessary or not doesnt really matter as it is upto the end user to decide if they prefer it but I would definitely recommend applying at least the 2x setting .
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I put a compulsory backup step in every mod section so that even on custom roms the original file can be saved to your computer before it is altered and pushed back if you dont like the changes. There is absolutely no chance of screwing up the camera app as only bitrates and quality settings are altered.
MuayThaiFighter8 said:
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
Click to expand...
Click to collapse
A NAND backup isnt needed as the file to be altered has to be backed up by the ToolKit in order to proceed so it can be easily and safely restored if the user wants to.
Mark.

Ah okay, so stills aren't affected at all?

bemymonkey said:
Ah okay, so stills aren't affected at all?
Click to expand...
Click to collapse
Does noone bother reading my posts properly lol
If you read my above post the camera quality (stills) is pushed up by pushing the modded settings.
The 2x and medium profiles pushes the 3 quality values of stills upto 100, 85 and 75 (instead of 95, 80, 70). The high quality profile pushes all 3 values upto 100 (meaning there is no compression in the images taken).
Mark.

Related

[MOD] Hacked Camera.APK for better audio quality, usage with any battery life & MORE!
Final Update-
Some people have been asking for sourcecode/instructions, so once more, this is the method I used, all credit to Rafalense.
http://forum.xda-developers.com/showpost.php?p=10980448&postcount=268
Those of you wanting me to reupload the APK's, I'm sorry, I don't have them stored anymore, and I wouldn't put them up even if I did. They're based on ANCIENT firmware revisions, and whilst I can appreciate you still would like the functionality somehow, I'm not interested in taking on the project again at this time. Thank you very much for your continued use and desire for my work though, it's very flattering.
I won't be actively developing or supporting this anymore because of it's defunct nature. If you want something similar, I highly recommend the lgCamera app, which has a far better implementation of improved bitrates (select whatever bitrates you want in a menu.) You can get lgCamera on the market- I highly reccomend it.
Anyone who wants to pick up this project can feel free to discuss here or make a new thread, as you please. If you do, please include the link to the guide by Rafalense, as it was the basis for this mod and will doubtlessly be of use to someone.
(Original Post Below)
-----
In light of my new student status, and since my student loan doesn't even cover my accommodation... I have made a donate link.
If you use the mod regularly, please consider donating, it would really help me out. Don't worry if you can't though, the mod will always be free for all to use.
Thanks for all the support-
- Potatoman.
------------------------------------------------------------------------------
Hey folks-
It's with great pleasure that I'm releasing a hacked Camera.apk for you all today! This is my first android mod, so be gentle
Info-
The apk replaces the stock Camera.Apk in the Galaxy S II (or Samsung Captivate!), and has the following features-
- Allows use of the camera & camcorder at any battery life
- Records Audio in 192kbps/44.1Khz quality (CD Quality) rather than stock (64kbps/16khz quality)
- Increased Video Bitrate in 1080 and 720p modes* (See 2nd post for info and download link for this version)
- Optional No Sounds versions (for Standard and Highbit versions!). All of the features, None of the noise! Yes, even the autofocus noise is gone!
- HyperX-'s SuperHighBit version now available (See 2nd post for info and download link for this version)
I have left the settings for the 320x240 and 176x144 resolution modes as stock, so they will be the same size and with the same audio. This is to ensure video messages are kept within the filesize limits
Before/After Comparison (thanks robbiekhan)-
robbiekhan said:
Before:
After:
Treble is high for loud sources in this mod, I'm working on improving it in v2. for now, just stand further back like robbiekhan said - Potatoman
Treble seems high so apologies for that, car volume was higher than I realised ¬_¬
Click to expand...
Click to collapse
Additional info:
If you want to get rid of the shutter sound, create a file in /data called local.prop and add the line "ro.camera.sound.forced=0" and restart your phone. This removes both the shutter sound and the focus sound when your phone is on silent, but keeps the sound when it's not on silent. - llBlackenedll
Install Guide:
1) Root & install a file manager which lets you browse root
2) browse to /system/app, and rename your Camera.apk to Camera.apk.bak and your Camera.odex to Camera.odex.bak (for use as a backup to restore from)
3) Unrar my APK (password: [email protected]) and copy it over to /system/app.
4) Rename it Camera.apk
5) Close the file manager and run the Camera app from the main menu
6) IF the app fails to run, or the shortcut is missing, go back to the /system/app folder and try to install it (tap it in root explorer then "install"). This step is only a fallback, do NOT do this if it works already at step 5.
7) Enjoy!
ADB Install Guide- See 2nd post!
This mod was tested on my own Galaxy S II with KE2, KE7, KG1, VillainROM and CognitionROM firmwares.
-------------------------------------------------------------------------
Thanks all, hope you enjoy! Thank if you like it
(Download: http://www.multiupload.com/KHRWLERS4J)
(Download with no sounds: http://www.multiupload.com/NNR1SYDYL6 Same password. Be sure to remove cam_start.ogg, cam_stopp.ogg, Camera_click.ogg, Camera_click_short.ogg, Shutter_01.ogg and videoRecord.ogg from /system/media/audio/ui as well!)
-------------------------------------------------------------------------
Credits-
Potatoman - Sound implimentation & merging of features & Version Splitting/Maintainance
Soraxd - Original battery life functionality & upcoming music playing functionality
Rafalense - A great post which lead me through how to do this mod over on the Galaxy S forums
pulser_g2 - Original battery life functionality (with soraxD )
llBlackenedll - tip on how to disable shutter sounds
robbiekhan - Before/After Comparison videos
Antoniotdi - An excellent bugfix
hyperX - Great minds think alike eh? HyperX released a similar mod to this on the same day as me! Anyway, we'll be working together on cameramods from now on. Good news huh?
Knightnz - The ADB install guide

ADB Install guide (Thanks knightnz!)-
knightnz said:
How to install using adb with phone connected to your computer:
Copy the new .apk to the root of the internal sdcard of the phone. then run the appropriate set of commands:
STANDARD VERSION:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p9 /system
cp -r /sdcard/Camera.apk /system/app/Camera.apk
chmod 644 /system/app/Camera.apk
NO SOUND VERSION:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p9 /system
cp -r /sdcard/CameraSoundless.apk /system/app/Camera.apk
chmod 644 /system/app/Camera.apk
cd /system/media/audio/ui
rm cam*
rm Cam*
rm Shut*
rm Video*
Click to expand...
Click to collapse
-----------------------------------------
HyperX-'s SuperHighBit version released!
This is kept here because it isn't mine to remove, and I haven't heard from HyperX in a while. Please note I wont be able to support anyone with this if you choose to use it.
hyperX- said:
Since some of you know me... i imigrated from Symbian here to Android.
Now i am working on several mods with Potatoman to bring you more mods/tweaks stuff.
I have prepared a package, with the following settings:
1080p mode: Normal – 17 Mbit Fine – 24 Mbit – Super fine – 30 Mbit
720p mode Normal – 9 Mbit Fine – 13 Mbit Super fine – 17 Mbit
Both modes have audio at 48000 khz at 192 kbit
Download
Also for those, who are interessted, my site will be soon updated for an Android section.
www.hx-custom-roms.com
Click to expand...
Click to collapse
DISCLAIMER TO AVOID DRAMA-
I work on this in my own time as a project, as and when I see fit. At no point does using or donating to the development of this app entitle you to demand anything from me other than what has already been shared. The app is also for use "as is", with no warranty. Support is provided by me (and other helpful members) in this thread and in my PM box as and when we desire.
Anyone who takes an issue with this is more than welcome to not use the app, not post here, and otherwise avoid being a nuisance to the rest of us in this thread.

thanks it works

Nice will download it. But for version 2.. I am able film and listen to music at the same time now on KE7

Cool . Are you able to make the power button work as a shutter key when in the camera app ?

good work, thanks!

This looks great, can someone please upload it to an Android browser friendly file sharing site, like megashare.com for example. Many thanks.

pin spot still here ?

sorrowuk said:
Cool . Are you able to make the power button work as a shutter key when in the camera app ?
Click to expand...
Click to collapse
+1 Good idea

Screen brightness low
Hi nice work, thanks. I have one problem with it. When I turn on Camera screen brightness turns to the lowest value, so it is very hard to see what I am filming or photographing.

Potatoman said:
Info-
The apk replaces the stock Camera.Apk in the Galaxy S II, and has the following features-
- Allows use of the camera & camcorder at any battery life
- Records Audio in 192kbps/44.1Khz quality (CD Quality) rather than stock (64kbps/16khz quality)
Click to expand...
Click to collapse
Great work man!
Quesiton: does anyone think that there might be a little more video quality to squeeze out of the phone too, or is this already flat maxed out on 1080p at highest settings?

^^ The video quality is already very good. low light sensitivity is a lot better than iPhone 4, for example. I have tested side by side and the ip4 is blocky in low light and motion isn't as good.
Before:
After:
Treble seems high so apologies for that, car volume was higher than I realised ¬_¬

really good job! Works like a charm !!!!

Excellent, could you also fix the force close when running camera on LCD density 160?
It seems only working on the default LCD density 240.

Mine is working fine at 182dpi. But we need a few modifications to the design. It only looks usable at 240dpi.
Sent from my GT-I9100 using XDA Premium App

Thankssssssssssss waiting for v2

Samsung Galaxy S II gets 1080p 24 Mbit/s recording hack
http://www.slashgear.com/samsung-galaxy-s-ii-gets-1080p-24-mbits-recording-hack-31155902/

Wow, fast replies
zxz0O0 said:
Nice will download it. But for version 2.. I am able film and listen to music at the same time now on KE7
Click to expand...
Click to collapse
Really? Lucky you then when I tested on mine it closes the music player while camera app is open... but maybe it's because I'm not using stock music player. I'll test some more. Either way, enjoy:
sorrowuk said:
Cool . Are you able to make the power button work as a shutter key when in the camera app ?
Click to expand...
Click to collapse
I was thinking about trying this, I'll look into it. Shouldn't be too hard.
padlad said:
This looks great, can someone please upload it to an Android browser friendly file sharing site, like megashare.com for example. Many thanks.
Click to expand...
Click to collapse
Done. Password is potatoman: http://www.MegaShare.com/3306744. Enjoy
djase said:
pin spot still here ?
Click to expand...
Click to collapse
Can you explain what you mean? I don't understand
mdaaddic said:
Hi nice work, thanks. I have one problem with it. When I turn on Camera screen brightness turns to the lowest value, so it is very hard to see what I am filming or photographing.
Click to expand...
Click to collapse
Was your battery very low? I know if the battery is VERY low the brightness on the whole phone dims completely, but this isn't something I can fix. If not, it's an odd problem, I can't seem to replicate it... mine retains the brightness it is set to. Can you try enabling the "Auto Brightness" in settings (Display -> brightness -> automatic brightness) and see if it works better then? If not you may have to resort to enabling "outdoor visibility mode" in the camera settings to use it until I can replicate it to fix it.
Richdog said:
Great work man!
Quesiton: does anyone think that there might be a little more video quality to squeeze out of the phone too, or is this already flat maxed out on 1080p at highest settings?
Click to expand...
Click to collapse
Robbiekhan hit the nail on the head, increasing the bitrate doesnt necessarily increase the quality by a margin that is worth having... especially with the associated filesize increase. I managed to get it working at 32Mpbs bitrate, but the quality didnt warrant doubling the amount of space it used up.
robbiekhan said:
^^ The video quality is already very good. low light sensitivity is a lot better than iPhone 4, for example. I have tested side by side and the ip4 is blocky in low light and motion isn't as good.
Before:
After:
Treble seems high so apologies for that, car volume was higher than I realised ¬_¬
Click to expand...
Click to collapse
Thank you for the comparison videos! I'll add them to the first post for people to see as an example (if you don't want me to just let me know :3)
trUePN said:
Excellent, could you also fix the force close when running camera on LCD density 160?
It seems only working on the default LCD density 240.
Click to expand...
Click to collapse
KLoNe1 said:
Mine is working fine at 182dpi. But we need a few modifications to the design. It only looks usable at 240dpi.
Click to expand...
Click to collapse
As much as I'd like to, I'm not sure how to go about it. Did the camera app work before at those resolutions? I don't imagine it did, since I didn't change any of the graphics... which means its crashing because of something else. Probably needs a graphic redraw to suitable sizes for the resolutions, but that's quite time consuming and I can't really commit to something like that right now. Sorry.
ermacwins said:
Samsung Galaxy S II gets 1080p 24 Mbit/s recording hack
http://www.slashgear.com/samsung-galaxy-s-ii-gets-1080p-24-mbits-recording-hack-31155902/
Click to expand...
Click to collapse
Yeah but I did it first Mine was ready a few days ago, I just waited for a reply from soraxd as a courtesy before releasing publicly.
The method is the same for changing the video settings as it is audio, but I felt when testing that the difference in quality was not worth the difference in filesize. When I shot a video at 1080p with 36Mbps (that was the max I could use without the phone crashing) it looked virtually identical to the original one, but used up twice the space. If enough people really want it (though I don't see why) I will happily add the functionality to this apk, so you can enjoy the other features as well.
Hope this helped-
Potatoman

Potatoman said:
Wow, fast replies
As much as I'd like to, I'm not sure how to go about it. Did the camera app work before at those resolutions? I don't imagine it did, since I didn't change any of the graphics... which means its crashing because of something else. Probably needs a graphic redraw to suitable sizes for the resolutions, but that's quite time consuming and I can't really commit to something like that right now. Sorry.
Potatoman
Click to expand...
Click to collapse
It actually works on LCD density 160, but crashes when you try to scroll down at camera settings or change to videocam.
For now I switch density when I use my camera properly, np.

Password on the file
Edit: My bad, wrong password...

UPDATED: FEB 23, 2013 - FOR MA7
Mods found in the feature.xml (located in "/system/csc/feature.xml")
Edit on a PC or you may have issues. Use a (root) file manager to move it only.
As always, make a back up first...
1. Camera Shutter Sound Menu
Download Zip Here (LJC) for those that would like to just flash it.
Download Zip Here (MA7) for those that would like to just flash it.
(this is only the Camera Shutter Sound)
First- Edit the build.prop (located in "/system/build.prop")
From:
# Camera sound play enforced for SPR
ro.camera.sound.forced=1
To:
# Camera sound play enforced for SPR
ro.camera.sound.forced=0
Second- Change the feature.xml
From:
<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>
To:
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
Reboot and enjoy the ability to turn off and on the shutter sound.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Others you can change that I played with in the feature.xml (located in "/system/csc/feature.xml"). There's a lot more, I'll add to this list some more or if someone posts one below.
2. Reject option in contacts
From:
<CscFeature_Contact_DisableMenuAddToRejectList>true</CscFeature_Contact_DisableMenuAddToRejectList>
To:
<CscFeature_Contact_DisableMenuAddToRejectList>false</CscFeature_Contact_DisableMenuAddToRejectList>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3. Reminder notification option in messaging app
From:
<CscFeature_Message_EnableMenuRemindAlert>false</CscFeature_Message_EnableMenuRemindAlert>
To:
<CscFeature_Message_EnableMenuRemindAlert>true</CscFeature_Message_EnableMenuRemindAlert>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Taking a picture while on a call
From:
<CscFeature_Camera_EnableCameraDuringCall>false</CscFeature_Camera_EnableCameraDuringCall>
To:
<CscFeature_Camera_EnableCameraDuringCall>true</CscFeature_Camera_EnableCameraDuringCall>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5. joshbeach posted more below you can check out or
Download the Zip HERE (LJC) or Download the Zip HERE (MA7) to flash it all.
(this will also give you the Camera Shutter Sound Menu)
joshbeach said:
Theres a few more in features... I added all thes already in my ROM... But there are a few more...
such as joining contacts, ect. attached is my feature.xml if you want to use some of it.
just compare to what you have now.
The Biggest one to me is this: add to contacts section!!! allows u to join more than 5 contacts!
<CscFeature_Contact_SetLinkCountMaxAs>30</CscFeature_Contact_SetLinkCountMaxAs
here's the rest of the ones I changed in my ROMs. Just change the existing lines to this:
....
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6. Call Recording Mod
IF YOU ARE ODEXED... Delete the SecPhone.odex first!! (/system/app/SecPhone.odex)
Here is the Modded SecPhone.apk that will give you the Call Recording Feature. (/system/app/SecPhone.apk)
Note: If you are a person that uses or cares about the swap calls button during a call, this will take it away.
Be sure to wipe the Dalvik Cache...
Mod info was pulled from multiple Roms that had it, but credit goes to PhantomHacker I believe?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enjoy
Not responsible for any phone. Your on your own.
As always, make a back up first...
.

a454nova said:
IOTHiddenMenu Info-
These are the same as the GS3, found here. You'll need you MSL for some things. You can just call Sprint and they will give it to you. Also, they email it to you when you activate your device on their site.
##DEBUG# Menu (code: 777468)
is one I use a lot. The only place you can see the signal strength of your Lte or 3G. The bars at the top are for voice only.
##DATE# Menu
Here you can force LTE only, another I'll play with too.
##MSL# Menu
View - view current phone number/msid set.
Edit - write new phone number/msid
*#0*#
Test LCD, Touch, Pen, and other sensors.
Refer to link above for more...
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
EVERY SPRINT PRL - HERE and HERE
(Normal PRL is 55012)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
THEMING THE NOTE 2? These all seem to work great!
http://forum.xda-developers.com/showthread.php?t=1929217
(found by: dwigginstm)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STOCK SPRINT SAMSUNG GALAXY NOTE 2 TAR LJ1
In case links go bad as they seem to do from time to time.
This should be enough to get you in trouble, I'll get more posted soon.
As always, make a back up first...
.

Nice, thanks. Looking forward to some more tweaks!
Sent from my SPH-L900 using Tapatalk 2

a454nova said:
Mods found in the feature.xml (located in "/system/csc/feature.xml")
Edit using a (root) file manager.
1. Camera Shutter Sound Menu
First- Edit the build.prop (located in "/system/build.prop")
From:
# Camera sound play enforced for SPR
ro.camera.sound.forced=1
To:
# Camera sound play enforced for SPR
ro.camera.sound.forced=0
Second- Change the feature.xml
From:
<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>
To:
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
Reboot and enjoy the ability to turn off and on the shutter sound.
Pulled the info from here. Its easy to do.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Others you can change that I played with in the feature.xml (located in "/system/csc/feature.xml"). There's a lot more, I'll add to this list some more or if someone posts one below.
2. Reject option in contacts
From:
<CscFeature_Contact_DisableMenuAddToRejectList>true</CscFeature_Contact_DisableMenuAddToRejectList>
To:
<CscFeature_Contact_DisableMenuAddToRejectList>false</CscFeature_Contact_DisableMenuAddToRejectList>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3. Reminder notification option in messaging app
From:
<CscFeature_Message_EnableMenuRemindAlert>false</CscFeature_Message_EnableMenuRemindAlert>
To:
<CscFeature_Message_EnableMenuRemindAlert>true</CscFeature_Message_EnableMenuRemindAlert>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4.
Enjoy
Not responsible for any phone. Your on your own.
Click to expand...
Click to collapse
I tried this on my rooted Sprint SGN2 and cant get this to work. After editing build.prop and feature.xml, all the secondary keys disappeared on my soft keyboard. Reverting the two files from backup corrects the problem. Did anyone else try this?

mranonymous said:
I tried this on my rooted Sprint SGN2 and cant get this to work. After editing build.prop and feature.xml, all the secondary keys disappeared on my soft keyboard. Reverting the two files from backup corrects the problem. Did anyone else try this?
Click to expand...
Click to collapse
I'm stock, rooted, odexed, J1. Shouldn't have anything to do with your keyboard. What do you call secondary? I'll also upload a .zip for just the Camera Sound in a min too.
.

Nice Work!
Nice Work.
Theres a few more in features... I added all thes already in my ROM... But there are a few more...
such as joining contacts, ect. attached is my feature.xml if you want to use some of it.
just compare to what you have now.
The Biggest one to me is this: add to contacts section!!! allows u to join more than 5 contacts!
<CscFeature_Contact_SetLinkCountMaxAs>30</CscFeature_Contact_SetLinkCountMaxAs
here's the rest of the ones I changed in my ROMs. Just change the existing lines to this:
Camera
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_Camera_EnableCameraDuringCall>true</CscFeature_Camera_EnableCameraDuringCall>
Messaging
<CscFeature_Message_RecipientLimit>500</CscFeature_Message_RecipientLimit>
<CscFeature_Message_DisableMenuRequestMmsReadReport>false</CscFeature_Message_DisableMenuRequestMmsReadReport>
<CscFeature_Message_DisableMenuSmsDeliveryReports>false</CscFeature_Message_DisableMenuSmsDeliveryReports>
<CscFeature_Message_DisableMenuRequestMmsDeliveryReport>false</CscFeature_Message_DisableMenuRequestMmsDeliveryReport>
<CscFeature_Message_DisableMenuWapPush>false</CscFeature_Message_DisableMenuWapPush>
<CscFeature_Message_DisableMenuWapPushServiceLoading>false</CscFeature_Message_DisableMenuWapPushServiceLoading>
<CscFeature_Message_DisableMenuMmsCreationMode>false</CscFeature_Message_DisableMenuMmsCreationMode>
<CscFeature_Message_EnableLocalSymbolTable>true</CscFeature_Message_EnableLocalSymbolTable>
<CscFeature_Message_EnableReplyAll>true</CscFeature_Message_EnableReplyAll>
<CscFeature_Message_EnableUnifiedMmsRetrieveMenu>true</CscFeature_Message_EnableUnifiedMmsRetrieveMenu>
<CscFeature_Message_EnableMenuRemindAlert>true</CscFeature_Message_EnableMenuRemindAlert>
<CscFeature_Message_EnableGroupMessage>true</CscFeature_Message_EnableGroupMessage>
<CscFeature_Message_EnableMenuVideoCallInConvList>true</CscFeature_Message_EnableMenuVideoCallInConvList>
<CscFeature_Message_EnableSmsViewer>true</CscFeature_Message_EnableSmsViewer>
<CscFeature_Message_DisableOptionAttachVCalendar>true</CscFeature_Message_DisableOptionAttachVCalendar>
<CscFeature_Message_EnableEmailOverSms>true</CscFeature_Message_EnableEmailOverSms>
<CscFeature_Message_EnableSignature>true</CscFeature_Message_EnableSignature>
<CscFeature_Message_EnableScheduledMessage>true</CscFeature_Message_EnableScheduledMessage>
<CscFeature_Message_EnableSaveVMessage>true</CscFeature_Message_EnableSaveVMessage>
<CscFeature_Message_EnableAnonymousThread>true</CscFeature_Message_EnableAnonymousThread>
<CscFeature_Message_EnableMessagePriorityDuringComposing>true</CscFeature_Message_EnableMessagePriorityDuringComposing>
<CscFeature_Message_DisableMenuCBChannel>false</CscFeature_Message_DisableMenuCBChannel>
<CscFeature_Message_DisableMenuSMSC>false</CscFeature_Message_DisableMenuSMSC>
<CscFeature_Message_DisableMenuSmsInputMode>false</CscFeature_Message_DisableMenuSmsInputMode>
<CscFeature_Message_DisableSmscEditable>false</CscFeature_Message_DisableSmscEditable>
<CscFeature_Message_MinRecipientLengthAs>4</CscFeature_Message_MinRecipientLengthAs>
<CscFeature_Message_DisableLandscapeActionbarHide>false</CscFeature_Message_DisableLandscapeActionbarHide>
<CscFeature_Message_DisableDeleteButtonOnActionBar>false</CscFeature_Message_DisableDeleteButtonOnActionBar>
<CscFeature_Message_DisableRegisterToCalendar>false</CscFeature_Message_DisableRegisterToCalendar>
<CscFeature_Message_DisableAddRecipientsOption>false</CscFeature_Message_DisableAddRecipientsOption>
<CscFeature_Message_DisableConvertingEffectBetweenSMSMMS>false</CscFeature_Message_DisableConvertingEffectBetweenSMSMMS>
<CscFeature_Message_DisableBackgroundStyleWithImage>false</CscFeature_Message_DisableBackgroundStyleWithImage>
<CscFeature_Message_DisableDisplayNameAndNumberonTitle>false</CscFeature_Message_DisableDisplayNameAndNumberonTitle>
Contacts
<CscFeature_Contact_ExtendSpeedDialTo100>true</CscFeature_Contact_ExtendSpeedDialTo100>
<CscFeature_Contact_DisableSnsInfoInListView>false</CscFeature_Contact_DisableSnsInfoInListView>
<CscFeature_Contact_DisableAccountIconsInContactList>false</CscFeature_Contact_DisableAccountIconsInContactList>
<CscFeature_Contact_DisableCallDuration>false</CscFeature_Contact_DisableCallDuration>
<CscFeature_Contact_DisableMessageLog>false</CscFeature_Contact_DisableMessageLog>
<CscFeature_Contact_DisableMenuAddToRejectList>false</CscFeature_Contact_DisableMenuAddToRejectList>
<CscFeature_VoiceCall_TotalCallTime>true</CscFeature_VoiceCall_TotalCallTime>
<CscFeature_VoiceCall_RemoveCallButtonInLogsList>false</CscFeature_VoiceCall_RemoveCallButtonInLogsList>
Settings
<CscFeature_Setting_DisableMenuFindMyMobile>false</CscFeature_Setting_DisableMenuFindMyMobile>
<CscFeature_Settings_FindMyMobile>true</CscFeature_Settings_FindMyMobile>
Web
<CscFeature_Web_SetHomepageURL>http://google.com/</CscFeature_Web_SetHomepageURL>
<CscFeature_Web_Str_homeurl>http://google.com/</CscFeature_Web_Str_homeurl>
SIP
<CscFeature_Sip_DisableAutoCorrection>true</CscFeature_Sip_DisableAutoCorrection>
<CscFeature_Sip_AddWordType>Prompt</CscFeature_Sip_AddWordType>
Launcher
<CscFeature_Launcher_TotalPageCount>7</CscFeature_Launcher_TotalPageCount>
<CscFeature_Launcher_DefaultPageNumber>3</CscFeature_Launcher_DefaultPageNumber>

joshbeach said:
Nice Work.
Theres a few more in features... I added all thes already in my ROM... But there are a few more...
such as joining contacts, ect. attached is my feature.xml if you want to use some of it.
just compare to what you have now.
Click to expand...
Click to collapse
Saves my from digging. LIKE!!

a454nova said:
I'm stock, rooted, odexed, J1. Shouldn't have anything to do with your keyboard. What do you call secondary? I'll also upload a .zip for just the Camera Sound in a min too.
.
Click to expand...
Click to collapse
Here.. before
{
"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"
}
After...
Here's what I edited.

mranonymous said:
Here.. before
PICTURE
After...
PICTURE
Here's what I edited.
PICTURE
Click to expand...
Click to collapse
Not having issues here like that. I think somethings not saving right maybe. I would try not editing it on the phone or try the .zip I posted.

a454nova said:
Not having issues here like that. I think somethings not saving right maybe. I would try not editing it on the phone or try the .zip I posted.
Click to expand...
Click to collapse
I'll give it a shot. Thanks.
---------- Post added at 03:11 PM ---------- Previous post was at 02:46 PM ----------
mranonymous said:
I'll give it a shot. Thanks.
Click to expand...
Click to collapse
Editing on my computer worked. I guess using es file explorers text editor wasnt good.
Thanks!

Moving to Themes and Apps as this is a modification to apps and not a "mod" in the XDA sense of the word, meaning development work modding ROMs, kernels, etc.

Is there any sort of breakdown sheet on what some of these things do exactly? Some of them i wouldnt know exactly what changes they would be making by chaing from true to false or visa versus.
Thanks in advance.

chucktownscitch said:
Is there any sort of breakdown sheet on what some of these things do exactly? Some of them i wouldnt know exactly what changes they would be making by chaing from true to false or visa versus.
Thanks in advance.
Click to expand...
Click to collapse
I know I am a noob here, but what is the process to install one of the zip files above? Everytime I try it says the file is read only and system file and I can not replace it. Let me if someone has an easy way to install them. Thank you.

48548 said:
I know I am a noob here, but what is the process to install one of the zip files above? Everytime I try it says the file is read only and system file and I can not replace it. Let me if someone has an easy way to install them. Thank you.
Click to expand...
Click to collapse
That is a flashable zip. To install it you must be rooted, reboot to recovery and select install from zip. Then navigate to the directory you have the zip downloaded and select and flash it.
Otherwise again you will need to be rooted, and using a root file explorer you will need to manually modify the build.prop and/or feature.xml .
If you haven't rooted your device yet, there is a thread under general on how to root which has a youtube walk through which makes it very easy.
Hope this helps.
Sent from my SPH-L900 using Tapatalk 2

a454nova said:
*#0*#
Test LCD, Touch, Pen, and other sensors.
Click to expand...
Click to collapse
Holy sh!t. Word of warning:
DO NOT do the Wacom test late at night when your wife is already asleep. After you fill in all of the squares the phone emits a VERY LOUD TONE when it puts up the "Pass" message. Learn from my mistakes, please.

enormous said:
Holy sh!t. Word of warning:
DO NOT do the Wacom test late at night when your wife is already asleep. After you fill in all of the squares the phone emits a VERY LOUD TONE when it puts up the "Pass" message. Learn from my mistakes, please.
Click to expand...
Click to collapse
Sounds like you in the dog house.
Sent from my Galaxy Note 2 using Tapatalk 2

Thank you! So glad I can mute the camera now!

I've only changed the feature.xml setting for the contact reject list menu, it works, but made my stock email app inverted. I like it, so I'm not complaining, just giving a heads up. I think it is a side effect of modifying the file using Es file explorer on the phone. Stock, rooted, deodexed, stock kernel.
Sent from my SPH-L900 using xda premium

is there a mod to restore burst mode functionality like it is on the S3?
On my S3 Burst is its own mode and it does the AI Servo mode for focus (continious all the time adjusting auto focus) and when I press and hold the button BOOM it starts snapping pics.
the Note 2 is AGGRAVATINGLY different to the point where it won't work for what I need that burst mode for (shooting rockets)
in the note 2 there is no more "burst" mode instead its part of regular mode.
now if I sit their AI Focus works fine tap the button BAM instant shot BUT if I HOLD the button it does NOTHING first it does brand new full auto focus sequence AND THEN it starts the burst.
thats a huge problem when your "subject" is going to "poof" suddenly at 600mph ie it defeats the whole point of their "zero lag" improvements.
anyway to defeat that? to reenable burst as its own option with the ai driven focus and zero lag?

You might be able to try pulling the camera all from the s iii, I could be terribly wrong, but our cameras could be very similar.
sent from my ginormous Note II

Hey guys this is HTC One X GREAT camera BUG i found recently.​
PICTURE SAMPLES AT THE BOTTOM​
Credits:
Thx to Hamdir for testing my bug and providing us professional comparison.
Also thx to neuTrue for enchanting one of my photos to show us what we can do with some more software
Click to expand...
Click to collapse
Ok so anyway i found this bug when i was compering S3 vs HoX in deep , for those who missed it you can find it here
HTC One X vs S3 full comparison
Click to expand...
Click to collapse
As for the bug with camera :
1st how does this bug works:
Simply , it gets stuck between scenes which i found accidentally while comparing HoX Vs My cousins s3 lol.
Anyway to be more specific it uses 2 scenes at the same time which provides great photos @ night , probably best 2012 phone @ day and Night INDEED is HOX. and i'll dare to say it comes close to HTC One with this Bug.
Important: this bug works ONLY with SENSE ( maybe miue roms as well ) and i found this bug on 3.18 base ( also working with 3.19 base ) for those still on ICS idk would it work there or at lower bases probably does.
How to use this BUG/GLITCH:
Outdoors night photos
> Open camera
> Turn off flash
> Chose NIGHT scene
> Chose HDR mode
Click to expand...
Click to collapse
> Take a photo
This bug will add you an extra 100-300% more light to your photos. For even MORE light i'd say 50/100% more light do this:
After taking the photo , go to gallery>edit and AUTO ENCHANT it.
NOTE:
After this if you see boost in your display regarding brightness = bug is applied. Take a pic but be VERY VERY STEADY , even little movement will [email protected] up the photo.
NOTE:
If you don't see improvement from the start you gotta REPEAT the process , sometimes it takes more then 1 time to get this bug working.
Also you must notice this: When you apply NIGHT scene you should see CAMERA being LAGGY when moving , after switching to HDR if it stays laggy and gives more light = bug is working 100%
For indoor photos with bug
> Turn ON flash ( not auto but ON )
> Chose NIGHT scene
> Chose HDR mode [/QUOTE]
> Take a photo
NOTE:
If you're using Underclocked CPU i'd suggest you use minimum 1300mhz quad core, with less speed shutter isn't fast enough to catch the light with HDR
BUG with FLASH - 50%-150% more light then normal flash light photos:
Ok this bug works similar as first one.
> Open camera
> Turn ON flash
> Chose NIGHT scene
> Switch to BACKLIGHT scene [/QUOTE]
> Take a photo
Note:
When you switch to NIGHT mode you should see your camera being LAGGY , after switching to BACKLIGHT scene if your camera stays laggy = bug is working.
TIPS:​
1. Try to be still when taking photos especially with HDR BUG.
2. For more light use after taking the picture gallery effects - auto enchance , with picassa / instagram you can modify them even more to be even better.
Click to expand...
Click to collapse
Recommended GOVERNOR for this bug is INTERACTIVE + Deadline or RoW scheduler.
IMPORTANT
Q) Will this bug crash/kill my camera ?
A) I don't know , i've been using it for over 2 weeks now everything is working as it should.
If you guys gonna use this BUG would be nice if you could upload some samples as well :thumbup:
So NOTE if you gonna use this bug you use it at your OWN RISK so don't blame me if you [email protected] up your camera.
Thx to Hamdir for testing my bug and providing us professional comparison.
Also thx to neuTrue for enchanting one of my photos to show us what we can do with some more software
These pics were taken around 8-9PM And on the 1st pic you can see how i saw at night with my eyes.
Normal - ( this is how i saw with my eyes outside )
Night scene
HDR+ Night
MODIFIED via photoshop, you can do pretty much same with gallery effects or instagram/picassa
Click to expand...
Click to collapse
Hamdirs tests & Review ( thx mate ):
hamdir said:
HTC One X: Hidden Low Light Abilities (Firmware 3.19.401.1)
Did you guys know the One X has night vision abilities? check this out
Ordinarily the Flash can be used but it casts the photo in blue plus add abnormal shadows, at least you can counter the blue by setting the white balance to Fluorescent before taking the photo
The included Night scene is not as effective, it forbids the Flash, it locks to ISO 1250 and cuts the shutter speed in half for more exposure time, sadly the results are often bad and not useful
But then for very low light and still photos, there is a revelation that is the HDR mode, especially when combined with auto flash it can do wonders, auto flash will smartly use two quick flash bursts to get better exposures for HDR, surprisingly auto flash with HDR does not cast shadows neither does it tint the screen
Finally a bug discovered by Shan89, switch to Night mode and then immediatly back to HDR mode, the shutter will get stuck in slow mode collecting even more light, you can also combine auto flash for killer results!
The bug mode is highlighted below with an *
keep in mind the shutter will be very slow at this point and you need to be very still until the word "processing" appears on screen (to counter motion blur),
Equally the resulting photo will fail to record the correct shutter speed since it's a bug after all
Some of the following results were brighter than my own eyes
Click to expand...
Click to collapse
Outdoors:
Indoors:
2 more that were missing by Hamdir , thx mate !
Click to expand...
Click to collapse
Few more photos added by me
Note: none of these photos were edited , all are original.
Normal outdoor
Normal+ Flash outdoor
Night outdoor
Night+HDR outdoor
Indoor normal scene
Indoor Night scene
Indoor night + HDR
Click to expand...
Click to collapse

deleted

Nice bug!
Also I would like to know if this bug is found using stock Sense camera or lypota's extrim camera mod?

limzm said:
Nice bug!
Also I would like to know if this bug is found using stock Sense camera or lypota's extrim camera mod?
Click to expand...
Click to collapse
By lypota's camera mod, tho should work with stock as well

Hey shant, good thread, here are my photos for you to attach (they are currently not showing in your OP) also are you sure neutrue enchanted your photos?
{
"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"
}

hamdir said:
Hey shant, good thread, here are my photos for you to attach (they are currently not showing in your OP) also are you sure neutrue enchanted your photos?
Click to expand...
Click to collapse
Thx mate , and thx for the new photos :thumbup: , ill add them to the op when I get on pc , btw it wasn't him , who was it cuz he posted them ? Was it you lol ?
Sent from my HTC One X using xda premium

Shan89 said:
Thx mate , and thx for the new photos :thumbup: , ill add them to the op when I get on pc , btw it wasn't him , who was it cuz he posted them ? Was it you lol ?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
no i mean the terms enchanted did you not mean enhanced?

hamdir said:
no i mean the terms enchanted did you not mean enhanced?
Click to expand...
Click to collapse
Oh yeah lol , ill fix that later if I don't forget
Sent from my HTC One X using xda premium

This is the best bug i have EVER seen
This is probably a feature, and it work perfectly, I've just tried. See the difference between bug and a feature
Is there some feature to reduce grain in photos in low light conditions, it really anoys me? I've tried sharpness to -2, lock ISO to 100 but it has very little or no effect on grain...

First of all apologies, but do not know a thing, I have installed the mod. lyapota camera, however, I see in the pictures iso 1200, when the max. I see in the mod are 800, I see active hdr mode, I do not see that option in the mod, etc etc, that is what I do wrong?

Lo_RaT_PeNaT said:
First of all apologies, but do not know a thing, I have installed the mod. lyapota camera, however, I see in the pictures iso 1200, when the max. I see in the mod are 800, I see active hdr mode, I do not see that option in the mod, etc etc, that is what I do wrong?
Click to expand...
Click to collapse
...... Its pretty much clear in the op what to do , can't you simply press the button on the left which looks like camera ... In there you'll find hdr panorama etc , in scene selection you can chose night scene , normal scene etc ...
Sent from my HTC One X using xda premium

Added few more photos at the OP.

IT WORKS
Thank you Sir

Hi!
Nice bug!
Can you tell me which rom do you use? Beacuse I have Ordroid 14.0.0, and I don't have Night scene.

This is NO bug
I'm sorry to say so, but this is NO bug, it's a feature. And it's well known to photographers that in Manual mode you can always shoot better photo's then in Auto mode (with any camera).
Actually you managed to post a great tutorial on how to make better pictures, so I would recommend you to change the word "bug" in the title to "enhancement".
Furthermore great job!

webpatrick said:
I'm sorry to say so, but this is NO bug, it's a feature. And it's well known to photographers that in Manual mode you can always shoot better photo's then in Auto mode (with any camera).
Actually you managed to post a great tutorial on how to make better pictures, so I would recommend you to change the word "bug" in the title to "enhancement".
Furthermore great job!
Click to expand...
Click to collapse
Thx but still you're very wrong mate for many reasons , you're right when talking about digital cameras but as far as Hox goes you're very wrong.
1. Hox doesn't even have auto scene / mode selection , it can only change iso , condition , flash and that's about it , it will never chose night scene at night nor it will chose hdr when needed or any other scene / mode.
2. This bug seams to be working only on Hox and Hox+ , guys with snapdragon version reported it doesn't work for them , doesn't work on s3 as well nor nexus 4 , LG optimus etc since I tested it on many devices.
3. If this was a feature as you call it don't don't you think HTC would advertise this when releasing Hox and claim it as the best night camera phone for 2012 ? Cuz trust me none 2012 flagship can match Hox here. And HTC doesn't even know for this.
4. It is a bug for many reasons since you can use 2 scenes only when mixed with night scene we were never supposed to use 2 things at the same time , aside from that you are not able to use flash with night scene nor hdr unless you bug it this way , lastly this would be found out for sure 1 year ago if it wasn't bug and everyone would know about this .
Sent from my HTC One X using xda premium

balint933 said:
Hi!
Nice bug!
Can you tell me which rom do you use? Beacuse I have Ordroid 14.0.0, and I don't have Night scene.
Click to expand...
Click to collapse
Viper 3.5.4 , I used sd , black pearl , renovate and some other roms as well it works on every Rom based on 3.18 base + , maybe works on lower bases as well , dunno. All I know is that I found this when comparing Hox vs s3 and I was on 3.18 base. Btw I also got lyoptas camera mod , not sure does it work on stock camera ... It should anyway.
Sent from my HTC One X using xda premium

Shan i saw your new results, you know this trick is using extreme slow exposure so really you need to hold your hand still, try to place your device on a surface
also the normal HDR+auto flash mode gives almost as good results with much faster shutter (the bug even brighter)

This is awesome. Thanks man! The cam's finally putting it's f2.0 aperture to good use :thumbup::thumbup:
Sent from my HTC One X using xda app-developers app

hamdir said:
Shan i saw your new results, you know this trick is using extreme slow exposure so really you need to hold your hand still, try to place your device on a surface
also the normal HDR+auto flash mode gives almost as good results with much faster shutter (the bug even brighter)
Click to expand...
Click to collapse
Yeah , i was in a rush to take these pics fast and upload since gf was rushing me to go @ some dinner , anyway i found that if we use quad lock @ 1500 it gives better results lol since HDR is CPU demanding and i use max freq @ 1000 mhz
Anyway nice thing is this bug really takes great advantage of f2 when we have little light source near by :victory:
Qwerty123 \m/ said:
IT WORKS
Thank you Sir
Click to expand...
Click to collapse
Np

I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Edit:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Sources: Android Source

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..

Puddi_Puddin said:
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Click to expand...
Click to collapse
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?

0xelectron said:
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
Click to expand...
Click to collapse
Maybe because it is a **** ton off work? Or noone has the knowledge?

Puddi_Puddin said:
Maybe because it is a **** ton off work? Or noone has the knowledge?
Click to expand...
Click to collapse
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.

0xelectron said:
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
Click to expand...
Click to collapse
Yes.. Maybe a proper after processing is more work? I have no clue how you need to do those things.. But if it was easy I'm pretty sure someone would've done it already.

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.

Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).

Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
I get that they want protect their camera code to stay ahead in the game. But, I still don't understand why, we(community) are missing that, we are not able to produce the same quality as theirs. I think either its too hard, or, maybe we don't have required information about the camera module or something like that.

AcmE85 said:
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Click to expand...
Click to collapse
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?

0xelectron said:
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
Click to expand...
Click to collapse
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg

0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app

Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?

defcomg said:
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Click to expand...
Click to collapse
I don't have examples currently, but, I've noticed that the post processing of aosp is generally inferior compared to stock. Also, it doesn't have features such as 60fps video recording and proper EIS/OIS.

AcmE85 said:
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
Click to expand...
Click to collapse
I think I'm not explaining myself properly. What I'm trying to ask is that why the the quality/features of the the camera in custom roms a little inferior compared to stock OOS? I did some digging and found out that most of the capabilities are included in the hal api, and it's implementation, I think is provided by Oneplus. I can be totally wrong (correct me, if I'm).

0xelectron said:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Click to expand...
Click to collapse
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at

defcomg said:
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
Click to expand...
Click to collapse
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!

0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
Hex Workshop CPP Bookmark
{
"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"
}
attached the offset bookmark as well as the chromatix source if youd like to check it out

0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Sent from my ONEPLUS A3000 using Tapatalk

fcisco13 said:
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Click to expand...
Click to collapse
You're right. I didn't understand. But, that's a good thing. I'm learning. I'm digging. I'm doing something I would've not done, normally. For example, the first simple answer didn't satisfy me, so, I started learning the inner workings of the android camera. Second complex answer gave me more in-depth knowledge then I leaned, and it is making me study more to understand. So, say what you want, but, I'm thankful for both the answers. Thank you everyone!

RROS for moto e5 is here and this is what you need to know
bugs
- no
Download
GKart_builds - Browse /nora/ResurrectionRemixOS at SourceForge.net
builds by GKart
sourceforge.net
credits
- thanks to resurrection remix OS team for the sources of the ROM
- thanks to @whodat711 for the vendor and common sources
Sources
- ROM https://github.com/ResurrectionRemix
- Kernel https://github.com/motoe5/android_kernel_motorola_msm8937 (twerk-X)
- vendor https://gitlab.com/the-flash/proprietary_vendor_motorola
greetings and enjoy

Thank you. I found it works great. Now we have one option other than LOS for nora. nora was not abandoned (lol)! Where is android_device_motorola_nora? I cannot find it.
Edit: What I noticed is about data connection. Phone and SMS seems okay but internet access via SIM does not work. Is it my personal issue?

Korin67 said:
Thank you. I found it works great. Now we have one option other than LOS for nora. nora was not abandoned (lol)! Where is android_device_motorola_nora? I cannot find it.
Edit: What I noticed is about data connection. Phone and SMS seems okay but internet access via SIM does not work. Is it my personal issue?
Click to expand...
Click to collapse
on the device tree search in google
I will confirm your problem with the mobile network later.
have patience

I flashed the ROM on my device today and most things seem to be working fine, inclidung mobile internet. However I'm having the exact same video/audio recording issues that I had with the LineageOS ROM for Nora. (see here https://forum.xda-developers.com/t/...-e5-nora-recovery-64bit.4235721/post-85658449 )
I have noticed both ROMs use the same kernel. Could that be the issue and does anybody know who to contact to make the issue known?

froggeroo said:
I flashed the ROM on my device today and most things seem to be working fine, inclidung mobile internet. However I'm having the exact same video/audio recording issues that I had with the LineageOS ROM for Nora. (see here https://forum.xda-developers.com/t/...-e5-nora-recovery-64bit.4235721/post-85658449 )
I have noticed both ROMs use the same kernel. Could that be the issue and does anybody know who to contact to make the issue known?
Click to expand...
Click to collapse
Did you try to change the camera application that comes by default for another?

G.Kart said:
on the device tree search in google
I will confirm your problem with the mobile network later.
have patience
Click to expand...
Click to collapse
works perfect for me
what you can do is check the APN

G.Kart said:
Did you try to change the camera application that comes by default for another?
Click to expand...
Click to collapse
Yes, I checked both the default app and used Open Camera. The problem is exactly the same in both cases. I have also found that the problem only seems to start appearing after you turn off the phone for the first time. Still worked fine on the very first boot up and generally I think the phone might have to be running for a while (15 mins or so) for the problem to appear.
I also took a quick look at the gitlab link for the vendor files and as the most recent commit it mentions "Nuke useless camera blobs". Any chance those blobs might not have been all that useless after all?
Edit: the gitlab also says something like "Lineage 17.1" at the top, so I assume those vendor files are also shared between both ROMs?

froggeroo said:
Yes, I checked both the default app and used Open Camera. The problem is exactly the same in both cases. I have also found that the problem only seems to start appearing after you turn off the phone for the first time. Still worked fine on the very first boot up and generally I think the phone might have to be running for a while (15 mins or so) for the problem to appear.
I also took a quick look at the gitlab link for the vendor files and as the most recent commit it mentions "Nuke useless camera blobs". Any chance those blobs might not have been all that useless after all?
Edit: the gitlab also says something like "Lineage 17.1" at the top, so I assume those vendor files are also shared between both ROMs?
Click to expand...
Click to collapse
Nora xt1944-4?

G.Kart said:
Nora xt1944-4?
Click to expand...
Click to collapse
My device is XT1944-2

@G.Kart or anyone else who might know: Do you think the missing camera blobs innthe vendor files might be a probable or at least possible explanation of the issue? If so, is it possible to just flash an older version of the vendor files on the current device or would that require a reset or recompiling of the whole ROM?

froggeroo said:
@G.Kart or anyone else who might know: Do you think the missing camera blobs innthe vendor files might be a probable or at least possible explanation of the issue? If so, is it possible to just flash an older version of the vendor files on the current device or would that require a reset or recompiling of the whole ROM?
Click to expand...
Click to collapse
try this camera
https://t.me/MotoE5Roms/77365

G.Kart said:
try this camera
https://t.me/MotoE5Roms/77365
Click to expand...
Click to collapse
This one produces completely broken videos (photos are fine). I can only find them in the gallery app (not in VLC) and play them in neither.

froggeroo said:
This one produces completely broken videos (photos are fine). I can only find them in the gallery app (not in VLC) and play them in neither.
Click to expand...
Click to collapse
The camera in devices where it usually fails with that camera is fixed but in your case I do not know what is happening
for other models the camera works so the blobs are not the problem (or at least I don't think so)

G.Kart said:
for other models the camera works so the blobs are not the problem (or at least I don't think so)
Click to expand...
Click to collapse
If I'm reading the gitlab correctly, it's only nora that seems to have some camera blobs removed. The commit is only mentioned in the nora folder.
If it's easy to put in the old vendor files, I'm willing to give it a shot either way, but I'm not sure what would be the correct way to do that.

froggeroo said:
If I'm reading the gitlab correctly, it's only nora that seems to have some camera blobs removed. The commit is only mentioned in the nora folder.
If it's easy to put in the old vendor files, I'm willing to give it a shot either way, but I'm not sure what would be the correct way to do that.
Click to expand...
Click to collapse
Need rebuild

That's unfortunate. I did manage to narrow down the problem quite a bit more though which might also help with reproducing it. The problem actually doesn't occur with the first reboot, as I first suspected, but rather it occurs after you turn off the screen/put the phone to sleep.
So immediately after you boot up the phone the camera still records video fine (sometimes the app crashes after reboot though and cannot be opened, another reboot fixes it). But after you put the phone to sleep by pressing the power button (probably also if it goes to sleep automatically) the discrepancy starts showing up. So if you put your phone to sleep for five minutes and record a two second video, the resulting video will be 5:02 with the sound at the beginning and video at the end. If you put the phone to sleep again, the video length of the next video increases by about the same amount.
So the video length = actual video length + (time phone has been asleep since last reboot - 10 seconds or so). If you only put the phone to sleep for a few seconds, the discrepancy doesn't start yet, it has to be asleep for ~10 seconds or more.
So if anyone has the same device, they can try reproducing it by booting up the phone, taking a 5 second video, putting the phone to sleep for a few mins and then taking another 5 second video. The second video should then be of excess length.
So my guess would be that either the audio recording and video recording functionalities use different variables for timekeeping in the first place (time active vs time turned on) or that putting the phone to sleep kills some sort of time keeping functionality (maybe to conserve battery?) that the audio recording relies on while leaving the video equivalent untouched or vice versa.

Additional information: This is the crash report I got when the camers app crashed on me before I even opened it the first time (usually doesn't happen). Not sure if it's related to the other bug or whether there's a pattern behind the crashing:
Hastebin: Send and Save Text or Code Snippets for Free | Toptal®
Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.
hastebin.com
These are some error reports I got when trying to record a video with "Simple Camera App" from.the F-Droid store. Also not sure if it's related because that app doesnt even work for taking pictures.
{
"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 default app, Open Camera and Focal all record photos and videos, but the videos all have the length/timekeeping problems. The app you that was linked here also crashed when trying to take a video.

froggeroo said:
That's unfortunate. I did manage to narrow down the problem quite a bit more though which might also help with reproducing it. The problem actually doesn't occur with the first reboot, as I first suspected, but rather it occurs after you turn off the screen/put the phone to sleep.
So immediately after you boot up the phone the camera still records video fine (sometimes the app crashes after reboot though and cannot be opened, another reboot fixes it). But after you put the phone to sleep by pressing the power button (probably also if it goes to sleep automatically) the discrepancy starts showing up. So if you put your phone to sleep for five minutes and record a two second video, the resulting video will be 5:02 with the sound at the beginning and video at the end. If you put the phone to sleep again, the video length of the next video increases by about the same amount.
So the video length = actual video length + (time phone has been asleep since last reboot - 10 seconds or so). If you only put the phone to sleep for a few seconds, the discrepancy doesn't start yet, it has to be asleep for ~10 seconds or more.
So if anyone has the same device, they can try reproducing it by booting up the phone, taking a 5 second video, putting the phone to sleep for a few mins and then taking another 5 second video. The second video should then be of excess length.
So my guess would be that either the audio recording and video recording functionalities use different variables for timekeeping in the first place (time active vs time turned on) or that putting the phone to sleep kills some sort of time keeping functionality (maybe to conserve battery?) that the audio recording relies on while leaving the video equivalent untouched or vice versa
Click to expand...
Click to collapse
try using other gapps

G.Kart said:
try using other gapps
Click to expand...
Click to collapse
Which apps specifically? Not sure I understand how that's supposed to change anything.

Gapps needed?