I have been trying to find mods/tweak the camera. Unfortunately don't know how to hex edit so and bin files so until someone helps, full raw isn't capable unless you use a modified opencamera with camxoverridesettingsOfUltra.txt edit.
echo exposeFullSizeForQCFA=TRUE >> /vendor/etc/camera/camxoverridesettingsOfUltra.txt
Otherwise here are some prop files I have found specific to the 12s ultra. I know these make some good tweaks and don't add multiple at once and write down the ones you do. Lanthanum toolbox or any good prop editor makes it easy.
It took me hours to do this, and I did not write down all the specific things that they do, as some of them didn't have much info. I will try to update the info per prop when I have time, or you guys can post what it does, thanks.
persist.service.camera.cache_num
persist.service.camera.his_num
persist.service.camera.jank_enable
persist.service.camera.debug
persist.sys.invisible_mode
persist.service.camera.frame_offset
persist.vendor.camera.privapp.list
persist.sys.privacy_camera_radius_ratio
persist.service.camera.fps
persist.vendor.camera.capture.crop.update
persist.vendor.camera.sll.bypass
persist.vendor.camera.Dump.MIALGOutputMax
persist.vendor.camera.fusionswitch
persist.vendor.enable.sat.fusion
persist.vendor.camera.noisereprocess
persist.vendor.camera.rawDump=RawPlain16LSB10bit?
persist.camera.LEUELCPPLO
persist.vendor.camera.miaihdrindexbypass
persist.vendor.camera.bps.unenable
persist.vendor.camera.debugmaxgain
persist.vendor.camera.snmotionlevel
persist.vendor.camera.xmthumbheight
persist.vendor.camera.use_RX=bdns?
persist.vendor.camera.ispwholedump
persist.vendor.camxdump.minwidth
persist.vendor.camera.ispv3.soc.pg
persist.vendor.camera.dumpjpeg
persist.vendor.camera.bps.debug
persist.vendor.camera.ispv3.forcespi
persist.vendor.camera.xmthumbwidth
persist.vendor.camxdump.minwidth
persist.vendor.camera.quadCFA.darkRatio
persist.vendor.camera.quadCFA.shortGain
persist.vendor.camera.REMOSAIC.enable
persist.vendor.camera.quadCFA.exposure
persist.vendor.camera.sr.ZSL
persist.vendor.camera.quadCFA.adrcGain
persist.vendor.camera.quadCFA.userDefined
persist.vendor.camera.memory.freeBufferThreshold
persist.vendor.camera.quadCFA.aecGain
persist.vendor.camera.mapid
persist.vendor.camera.imx989.LongExpTime
persist.vendor.camera.imx989.fps
persist.vendor.camera.imx989.ShortExpTime
persist.vendor.camera.imx989.DOL2Manual
persist.vendor.camera.imx989.LongAnalogGain
persist.vendor.camera.imx989.FLL
persist.vendor.camera.imx989.ShortGain
persist.vendor.morpho.options
persist.vendor.camera.aiasd.disableSNSC
persist.vendor.camera.AIIE.bypass
persist.vendor.camera.mimovie.dump
persist.vendor.camera.videobokeh.bypass
persist.vendor.camera.enabledewarpdump
persist.vendor.camera.disableGPUSIMODS(opencl)
persist.vendor.camera.disableGPUBufferMap
persist.vendor.camera.enableMlDriver
persist.vendor.camera.REMOSAIC.debug
persist.vendor.camera.swfusionHybrid
persist.vendor.camera.enablemfnr
persist.vendor.camera.algoengine.jpeg.dump
persist.vendor.algoengine.sll.forcemode
persist.vendor.camera.sll.bypass
persist.vendor.camera.sll.time
persist.vendor.camera.capture.bypass.hdralgo(hdrraw)
persist.camera.settings.hlg
persist.sys.real_blur_max_radius
persist.sys.real_blur_max_sat
persist.sys.real_blur_max_black
persist.camera.capture.app.clearshotdump
There will be more to come mod wise and tweaks. I wish there was more people attempting to bring out the full capabilities of this camera.
Is there a tutorial on how to use the modified opencamera on the 12S U or where I can find them?
It seems OP found a way to set full raw output using this thread here: https://forum.xda-developers.com/t/camera2-api.4011239/post-87440051
I haven't yet followed the steps but I think the discussion should continue / steps should be documented in this thread to continue building upon this work for our device.
Related
I'm Linux & BSD literate, and used to administering servers, compiling programs and kernels from source. I've also managed to root and flash my Magic, following advice found here. What I'd like to do is gather up some info on how to build ROMs for the Sapphire platform.
I'm already poking around the Android Wiki FAQ and the Dream dev forum on this site. There's quite a bit of info there but some of it is out of date and I've not found much that's Sapphire-specific. I also plan to take apart the .zip files released by Haykuro and others and compare/diff configs to get a feel for things.
My intent is to put together enough info to allow anyone to pull apart a released ROM and replace the dialler, add some language support or some extra apps, maybe make some other simple changes.
What I need is any pointers on:
1. Sapphire-specific info.
2. Any danger of bricking my Magic by messing around with home-made ROMs.
3. Anything else that might be useful.
Hopefully I'll be able to put together a rudimentary HowTo for the wiki, which others can add some fine-tuning and extra info to.
Thanks for any input.
I think this is a very good idea!
It would simplify things if everybody would understand how exactly custom ROMs are created.
1 - Be aware that there are different Magic HW versions...
2 - I don't think you can brick your magic as long as you make backups via nandroid.
3 - A few things I think should be in the wiki :
- how to completely setup a linux environment and which applications you need to be able to build custom ROMs.
- Explain how the android OS is working, explain what boot, hboot, recovery, system is, how the partitions work, etc..
- What are test-keys, what is the difference with and release-keys.
- How to sign.
- How to dump the recovery.img, boot.img without having root access.
- What to change into the recovery.img and boot.img to get root.
- How create an update.zip
- How to make backups with nandroid and how to restore them..
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Do keep us up to date as to what you find by dissecting the ROMs, had a look the other day briefly but didn't have time to play yet,
Also waiting for info/confirmation that as long as you just flash bad roms its not possible to brick your phone only if you play with SPL's and such
fxn said:
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Click to expand...
Click to collapse
Oh, I'm sure the knowledge is scattered around the place - sharing is one thing, bothering to document is quite another!
The only thing I don't expect to find openly shared is traceable leaked material, and frankly I can live without that.
Hi there,
I am fairly new to custom ROMs etc and recently installed LeeDroid 4.3.0 successfully. However, I also wanted to try out a custom ROM and installed Faux' kernel too (mainline).
Battery drain became a lot better, but there's an optional feature to under voltage the CPU. According to the guide in the thread, I have to put
Code:
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
somewhere. Can someone tell me in where I have to put this in detail? Any other things I should take care of / should be aware of?
If this topic was discussed already (sure it was), please don't hesitate to link me to it, I just couldn't find anything via forums search.
Thanks!
You can run it with a terminal emulator directly on your phone or through adb/shell on your pc.
Either way, it's not going to stick and you should repeat the operation after every reboot if you want to keep the UV.
You can add that line to a script, though, so that it is executed automatically after every boot.
I usually add that line to the init.post_boot.sh script in /system/etc (between the other MSN8660 tweaks). The alternative is adding a file in the init.d folder.
nTraum said:
Hi there,
I am fairly new to custom ROMs etc and recently installed LeeDroid 4.3.0 successfully. However, I also wanted to try out a custom ROM and installed Faux' kernel too (mainline).
Battery drain became a lot better, but there's an optional feature to under voltage the CPU. According to the guide in the thread, I have to put
Code:
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
somewhere. Can someone tell me in where I have to put this in detail? Any other things I should take care of / should be aware of?
If this topic was discussed already (sure it was), please don't hesitate to link me to it, I just couldn't find anything via forums search.
Thanks!
Click to expand...
Click to collapse
you could just get System Tuner Pro from the market and UV that way
Thanks, got it with Grandelama's method.
Grandelama said:
You can run it with a terminal emulator directly on your phone or through adb/shell on your pc.
Either way, it's not going to stick and you should repeat the operation after every reboot if you want to keep the UV.
You can add that line to a script, though, so that it is executed automatically after every boot.
I usually add that line to the init.post_boot.sh script in /system/etc (between the other MSN8660 tweaks). The alternative is adding a file in the init.d folder.
Click to expand...
Click to collapse
how did u put it in the init.post_boot.sh?
i cant do that cuz cannot write to that
and writing tool have super user permissions,
that file cannot be editing
or can? if - how?
I have created a mostly-functional build of OmniRom 5.1 (Lollipop) for the T959V
However, I don't have enough posts to post in the development section or to put in links. Does somebody want to do this for me? If so, let me know.
The current status of it is:
What works
Taking pictures (very laggy switching between FFC and rear)
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
What is definitely not working
App to SD - not working on i9000 either, complains about insufficient space fixed in git
Tv-out as Omni's aries-common has removed it
Video recording - only captures fuzz fixed in git
What is untested
Everything else
What is probably not working
Microphone mute option doesn't work during calls - not working on i9000
GPS - I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset (hence why I have no clue on the status of the GPS) and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess from teamacid and others' device trees.
Selinux is set to permissive as I don't know how to create the proper policies for the GPS.
For a download and more information, see drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk (replace "*" with "/")
Source code can be seen under my github account (username is xc-racer99 there as well) under the android-5.1 and android-5.1-t959v branches
Ooooomg ...im wait ....is amazing the new proyect .....thanks thanks
Quick update:
I've got the video record to work properly now as well as being able to move apps to the SD card.
Selinux is left!
Should I upload a build?
Sure...I have a spare phone somewhere that I can test it. Do you have a Gapps package to go along with the ROM? As far as GPS is concerned, back when Beanstalk 4.4.2 was being worked on, a patch was developed to make GPS work...I'll have to root around in my files and see if I can dig it up...I think the developer deleted all the Beanstalk threads for some reason or another.
Yeah, I took the GPS files from CM-11.0 but I can't test if they work. With regards to the Selinux portion of things, only some parts of it were being enforced in KitKat while everything is now being enforced in Lollipop. GPS was not enforced in KitKat so the policies for it were not in place.
I haven't tried any gapps on it yet but I would recommend trying any of the three from the Omni i9000 thread
forum.xda-developers.com*galaxy-s-i9000/i9000-development/rom-t3054101 (again, replace "*" with "/")
I'll upload a new build as soon as I can verify that it boots - it fixes several issues such as apps2sd and camera that weren't working in the one I already have uploaded.
Also, I'm curious as to what the command "cat /sys/class/sec/gps/hwrev" shows. In CM11, one of the GPS files check this and depending on what it shows it loads a different file. Does this mean that there are two hardware variants of the SGS4G?
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
xc-racer99 said:
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
Click to expand...
Click to collapse
Link shows Not Found Error 404
Sammpls said:
Link shows Not Found Error 404
Click to expand...
Click to collapse
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Doesn't work... Why use google drive when there are others better for uploading your files.
xc-racer99 said:
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Click to expand...
Click to collapse
Sammpls said:
Doesn't work... Why use google drive when there are others better for uploading your files.
Click to expand...
Click to collapse
I was using Google Drive as its something I have an account for already and has plenty of space on. Do you have a suggestion of a site I should use? In the meantime, a direct link to the file is https://drive.google.com/file/d/0B7vXjzo0Hj-iZ0YtQTdoTG5KVW8/view?usp=sharing Hopefully this works...
Google Drive isn't bad at all. I was suggesting that you use another cloud service for uploading the files if it didn't work. (which i didin't do a really good job telling you that)
Thanks, that link works!
Alright, I have opened a devDB thread at http://forum.xda-developers.com/gal...official-omnirom-5-1-galaxy-s-4g-sgh-t3146611
Please post anything there and do not use this thread as I will not be monitoring it.
Google drive is at least better than Mega(especially if you use non top-end devices).
We currently need to override navigation_bar_height value from the framework-res.apk package. Based on Android documentation, this can be done by placing an apk in the system/vendor/overlay folder that will only contain the values that we wish to override. Once the system restarts, it will read the new values and use them to load the operating system.
We have found a sample project that we have followed, but haven’t been able to make it work. Please see the link below, it also has instructions on the page, and a lot of information can be found on the web for this override method.
Sample project: //github.com/ReinhardStrauch/framework-res-overlay-sample
Requirements:
• Android 5.0 (Lollipop) or higher - Rooted.
Deliverable:
• The sample project working in both Lollipop and Marshmallow
I am willing to pay a bounty of $1500 to make this sample project work, and another $500 if you have a simpler method. FYI, just changing the value is not acceptable. Although you will need a rooted device to be able to test, the final version we will be preloading on a non rooted device.
PM me if you want to take a shot at it.
EDIT: We already have this project completed.
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Kaksrocks said:
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Click to expand...
Click to collapse
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Mr. JAVI said:
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Click to expand...
Click to collapse
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Kaksrocks said:
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Click to expand...
Click to collapse
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
https://forum.xda-developers.com/android/themes/official-google-play-store-dark-theme-t3977061
Mr. JAVI said:
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
Click to expand...
Click to collapse
Great. Thanks for the information you provided.
You were pretty helpful.
So again thanks.