Related
Following on from another thread where people were asking about availability of apps to start a looping video recording app, I've started work on this, and have made some promising initial progress.
I'm having to do this with Mortscript since the only language I can code in is not suitable for writing phone/pc apps sadly, but so far it looks to be quite suitable.
If you're interested in this I'm afraid you'll have to be quite patient as I can't promise it will be complete by any date and I might even fail to complete it, but I'm posting up now because I believe that it's still useful at its current state.
Basically what the code does at the moment is as follows:
Tells you how much memory is spare on your SDcard
Asks you what you want the minimum remaining memory (in MB, ie when your remaining memory reaches a certain point the script stops recording)
Opens the camera in video mode
Begins recording
Once recording, the remaining memory is checked every 5 seconds
When the remaining memory dips below the amount you specified the recording stops, the camera turns off, and a message confirming remaining memory is displayed.
If you add the script to the appropriate start menu folder then you can add it as a home screen shortcut like any other app, so that just one touch will fire it up.
At present I have not started working on the actual looping functionality of the video, so it records until it reaches the memory limit you specify, or until you stop it manually, but I think this is still useful.
Now for the 'funny' important stuff:
Please understand this code comes with absolutely no promises/guarantees etc - if you choose to use it, you do so entirely at your own risk and I am not responsible for any outcome of doing so. I've run it several times and it has worked well for me, but there's no guarantee that it will behave the same for others.
I'm not going to be answering questions about the most basic stuff in relation to Mortscript. Please read up on the basics of what it is and what it does, and how you implement it before using this script. It's nothing personal, just that my free time is extremely limited so I can't afford to spend it answering potentially lazy questions.
Do as you wish with the script if you want to modify it and improve it, or just tailor it to your own needs. For instance, you may wish to do away with the question about minimum remaining memory and set a fixed amount so the recording begins from just one shortcut press. I've set it like that really for ease of testing but it may be handy for people who want to keep a certain amount of their card empty.
You may have to change minor bits of this script to make it work for you. Main example I can think of is depending on where the default location is for video recording files on YOUR phone (ie storage or card - it should be card for this script to work), and also the name of your card. On mine the card is called "Storage Card" - yours may be different and would therefore affect the script.
Other stuff I've not thought of yet but that people might whinge about.
In a nutshell though, I hope some of you find this useful, and at some point hopefully in the not too distant future this might be a bit more automated and do exactly as some of us wanted on the other threads about looping video.
If others want to use this as a base and finish the job I'm not going to be upset shall we say.
Script in post #2
Either download the zip file, unzip and place the script in an appropriate folder on your memory card, or copy this script code into a notepad file & save it, then change the files extension from .txt to .mscr & place it where it needs to live.
Script contents/zip download:
Code:
Free1 = FreeDiskSpace( "\Storage Card")
Freemb1 = Free1 / 1048576
Message((Freemb1& "MB left") , "Memory remaining:" )
Min = Input( "Remaining Memory Cutoff Limit(MB)?")
MinMem = Min * 1048576
set Mem, MinMem
Run( "\windows\camera.exe", "-v" )
WaitForActive "Camera",5000
mouseclick(240, 700)
set Delay, 5000
while wndActive "Camera"
sleep Delay
Free2 = FreeDiskSpace( "\Storage Card")
Freemb2 = Free2 / 1048576
if (Free2 le Mem)
# end recording & close camera
mouseclick(240, 700)
close "Camera"
Message((Freemb2& "MB left free") , "Memory Info:" )
#to do - delete the file just created
#to do - start recording again:
#mouseclick(240, 700)
endif
EndWhile
Reserved in case I need it for anything else....
This is interesting, will try after I read up on mortscript. One thing cought my eye, it seems with mortscript you are able to do software clicks on the screen (#to do - start
recording again:
#mouseclick(240, 700)
Would this mean we could have a way to asign a hardware key to take pictures in camera mode? I know this has nothing to do with your app, it just came to my mind after seeing your code. It would be nice to have a hardware key to take pictures with our HD2's.
Anyway I will be following your thread for updates on loop recording. Thanks for your work here.
Thanks for your comments mate.
I'm not sure about the hardware button in camera mode. It might be possible but I'm only a novice at Mortscript myself so I don't actually know. I would guess that if MS is capable of registering the activation of hardware buttons and distinguishing between them, then it should be possible but don't quote me!
A script to do that would I think have to effectively listen for the camera being activated, then once it is launched, listen for hardware key presses from a specified key which would in turn trigger the on screen mouseclick command.
Something for another thread I think but an interesting idea anyway. If you search through the mortscript examples thread (approx 70 pages!) you might find something that helps.
After a quick look at the manual this morning I think it's going to take me a little while to figure out how to delete the last created file in the DCIM folder, but once I have it sorted I will post up the amendments.
Run into a problem tonight with timestamps.
The time a file was recorded is showing up exactly 1 hour wrong from when it actually was made, so I have to try and figure this out. It's not the phone clock since the timestamp for the current time is spot on.
Go figure!
Thanks for posting updates for us. Hope you will find a solution, could it have something to do with summer/winter time? Or with local time? Don't know for sure of course, just trying to help.
I think there's a very good chance that's what it's linked to yes, but no idea how to get around it.
The dates where the clocks move forwards/back are not the same each year, so I can't hardcode it in. If there's a way I can get the script to check whether the phone's clock is using GMT or BST then that would likely solve it but I've no idea if that's possible.
Have raised a thread elsewhere to ask for help but no luck so far.
Well - I'm going to be struggling with this a bit guys.
I've not had any replies to the thread (http://forum.xda-developers.com/showthread.php?t=690134) asking about this time difference (I'm wondering if I have posted in the wrong subforum perhaps?) so I'm not really going to be able to get past the issue anytime soon. Kind of scuppers the project until I can work around that.
There is another way potentially of finding the correct file to delete, which would be to go through the mp4 files in the video folder, and create a list of them, sort it by time created, then delete the latest one.
But I don't know how to do that and there isn't any useful info that I can see in the Mortscript manual about sorting data, or even creating simple lists of data objects (unless this is the 'array' functionality?).
So I'm a little bit stuck sorry.
or: How to avoid rejected text message errors with lots of free space available
Background:
This post helped me a bunch and alleviated my issue with lost text messages due to "low space" errors. I'm using cMTD + eFOS [forum.cyanogenmod.com/topic/8711-read-this-recovery-and-installing-cyanogenmod6-firerats-cmtd-ennons-fso-gapps/] + magpie [forum.cyanogenmod.com/topic/9731-magpie-2010-12-07] on my nexus one and my "low space" threshold jumped from ~20mb (stock) up to ~40mb with all the mods. Clearly 40mb is more than enough space for receiving text messages [hell 20mb was more than enough, but I digress...]. Since my internal memory is much, much larger than default (~320mb on /data) I've set my threshold to 2% of the total space available instead of the 5% suggested in the post. At this ratio that drops my "low space" threshold down to ~10mb which is what I would expect it to be at by default.
So if you're having issues and need a real solution that isn't "just remove some of your apps so you have more free space" then try this mod. I would suggest making a copy of settings.db just in case you need to go back to default, but really there isn't much that you could break by doing this. Keep in mind that the number you're changing is a percentage and not a fixed number value, so mileage will vary from device to device. Play with the numbers and see what works best for you. The way I tested it was dropping a bunch of dummy files (actually just multiple copies of an .apk, don't forget to delete these when you're done testing ^_~) into /data/local/tmp until the free space message was displayed, then texted myself using gVoice [voice.google.com] and altered the threshold percentage until I got to a comfortable level.
As a side note, it would be *awesome* if there was an option in the Settings > CyanogenMod Settings menu that let us alter this value through a gui so we don't need adb. I would do it, but I have no confidence in my java programming skills =p *hint hint*
Anywho on to the meat of this post...
---------------------
Low on Space – Phone storage space is getting low.
Its a cursed message on my Android HTC Hero, but there is 16MB free on /data partition! I want my email to sync a bit more and I want to receive text messages and I dont want to delete any apps.
You need to have rooted your android device and have the android sdk installed and debugging enabled on your phone. I might package this recipe up into an apk for easy installation.
The default limit is 10% of free space, i’ve reduced mine to 5%, I don’t know if there are any terrible side effects. As you’ve already rooted your phone you’ve already probably voided your warranty
To reduce from 10% to 5% warning from your “adb shell”:
Code:
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> insert into secure (name, value) VALUES('sys_storage_threshold_percentage','5');
sqlite> insert into gservices (name, value) VALUES('sys_storage_threshold_percentage','5');
sqlite> .quit
# reboot
*** don't include the # or sqlite>, those are the console prompts... ***
Some firmwares seem to look for the setting in gservices but the latest android source looks like it looks for it in the secure settings, so i’ve included both for good measure.
---------------------
Note:
reposted (with a few edits) from [bryars.eu/2010/10/how-to-reduce-the-threshold-for-low-on-space-android-warnings/]
Disclaimer:
This is not my work / information / blog, but since it was a huge help to me and I couldn't find the information anywhere else I thought I'd post it here for others to use ^^
Additional information:
If you want more information or a gui to edit the settings.db file, use adb to pull the file from /data/data/com.android.providers.settings/databases/settings.db, edit settings.db using a program like SQlite db browser [blog.dreamcss.com/dev-tools/sqlite-database-browser/], then push the file back to the phone using adb and reboot.
Sorry for reviving an old thread but this is an excellent find, especially on my S-Off Desire when the phone complains about the lack of space at 30 MB!
Apps won't install or update, insufficient storage, 200MB free
Same here, sorry for reviving the thread, maybe I should have started a new one, but this topic has half the answer... this works perfect to stop the notification, but...
I still get the "Insufficient storage available." notification when I try to update or install an app.
I've looked around and searched here and on Google
I have the Galaxy S2 Skyrocket, with 2GB for /data, so it still has 200MB free. I know I've gone app crazy with over 200 apps installed, but that's not the point. I plan to organize and thin them out once I get some time to see which ones I want to stick with, but since there is plenty of space left, that shouldn't be a problem.
This is not related to the other issues I found on the forum (like this one or this one), and I know I can gain some space back by clearing caches and obviously by removing some apps or getting an sd card and moving apps to it. That's not the correct solution, those are all just workarounds.
Any ideas? Based on this topic, it would make sense that there is another key I can add to the database somewhere to lower the same threshold but for installing/updating apps.
@WebGuru, I am also interested in finding a way to lower the point at which my device start telling me insufficient storage. My S-OFF HTC Desire with custom HBOOT has 387MB /data and therefore I get insufficient storage prompts when I have ~35MB of space remaining. Most annoying. I've applied the DB update and I confirm it silences the notification only.
If I find anything useful I'll post it here.
Regards, Martin.
From what I understand the problem with app installs is due to the free space threshold value being hard coded into some aspect of the ROM itself and therefore no DB value exists nor can be created which will allow for adjustments. The issue would have to be taken into account by the ROM developer or by someone willing to hunt down the values and create a custom build with the appropriate fix.
I agree with WebGuru, the topic is still relevant and I have LG G2 5.0.1 16 GB version and have free ~500 MB and receiving insufficient memory. . . Has anyone knows any ROM files for solving this problem?
stupid low storage threshold value
Coolguy981 said:
I agree with WebGuru, the topic is still relevant and I have LG G2 5.0.1 16 GB version and have free ~500 MB and receiving insufficient memory. . . Has anyone knows any ROM files for solving this problem?
Click to expand...
Click to collapse
i think it is still relevant too, because i still experience on several modern devices.
the only possibility i found after hours and hours of crawling the web is to change value sys_storage_threshold_percentage and/or
sys_storage_threshold_max_bytes in /data/data/com.android.providers.settings/databases/settings.db which would be easy enought to do, if this settings.db would still be used and would not be deprecated by now (as far as i have understood).
based on the information i found the standard value is "10" for the percentage which for our modern devices nowadays is unnecessary much. additionally it is quite iphone-y imo to force this value on us without an easy possibliity to customize it to our own preferences/use cases, but that's another story of course. ^^
i would really appreciate any information, suggestion or help on this issue, i am quite desperate by now and have no more ideas where to look or what to try.
thx and greetz,
sUsH667
Does anybody know how to increase the mms size limit on the captivate? I'd like to increase it to at least 1MB
I don't know if that can be done.
When I attach a video/pic (Clearly over 1mb) it automaticly compresses it to send
SMaximus7 said:
Does anybody know how to increase the mms size limit on the captivate? I'd like to increase it to at least 1MB
Click to expand...
Click to collapse
I kno mikeymike moved the limit up to 600kb for the serendipity rom but I am not sure how he did it or how high is possible. Just letting you kno it can be done...
After some googling I came up with 600 kb being the highest AT&T can handle.
I set it higher than that (like 1mb) and things never got past "Sending...".
MikeyMike01 said:
After some googling I came up with 600 kb being the highest AT&T can handle.
I set it higher than that (like 1mb) and things never got past "Sending...".
Click to expand...
Click to collapse
I'm was trying to send a video that's maybe 400kb, and it wouldn't go. I know I can download handcent or chomp and change the setting in there but I like the stock sms app and would like to keep that. 600kb is all they can handle if they recently changed their settings. Back in August I had a windows mobile device which I tweaked to allow over 1mb to be sent and it allowed me. My daughter is starting to walk and I took a small video to send my mom that is about 400kb and it won't go. MikeyMike, can you instruct me on how to increase mine or is it something highly involved. I tried doing it yesterday but after moving the new mms.apk in, it fc'd, so I had to go back to the original from the rom.
Thanks for your help.
Mms.apk\res\xml\mms_config.xml
Code:
<int name="maxMessageSize">614400</int>
That's 600kb.
MikeyMike01 said:
Mms.apk\res\xml\mms_config.xml
Code:
<int name="maxMessageSize">614400</int>
That's 600kb.
Click to expand...
Click to collapse
That should suffice. Thanks for your help!
SMS size limit
I tried what MickeyMike suggested and it fc's after i put it back into system/app. I open the file from 7zip and edit it from within, then just save the file, that way i don't have to repackage.
SMaximus7 said:
I tried what MickeyMike suggested and it fc's after i put it back into system/app. I open the file from 7zip and edit it from within, then just save the file, that way i don't have to repackage.
Click to expand...
Click to collapse
You've got to decompile it with APK Manager.
Sent from my Captivate.
I've been reading about editing hsdpa and hsupa catagory numbers as well as the gprsclass number and seem to have improved my upload speed and possibly my download speed. In my basement, I usually see about 2200 kbps down and 1000 kbps up. Changing a couple numbers, I am now at a consistent 2500kbps and 1600kbps.
I'm running Android Revolution v3.0 with the 26.06.03.24_M2 radio.
ro.ril.gprsclass=12
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=7
ro.ril.hsxpa=3
I rebooted twice.
Could be purely coincidental, but I thought it may be worth sharing and discussing.
Would be great if you could elaborate a little more on the technical side of what these values actually do and stuff
All this is cut and pasted from other sites, it's not my own research.
ro.ril.gprsclass indicates the GPRS class of the target network :
Class 2 : 3 slots : 8 – 12 kbps upload / 16 – 24 kbps download
Class 4 : 4 slots : 8 – 12 kbps upload / 24 – 36 kbps download
Class 6 : 4 slots : 24 – 36 kbps upload / 24 – 36 kbps download
Class 8 : 5 slots : 8 – 12 kbps upload / 32 – 40 kbps download
Class 10 : 5 slots : 16 – 24 kbps upload / 32 – 48 kbps download
Class 12 : 5 slots : 32 – 48 kbps upload / 32 – 48 kbps download
ro.ril.hsdpa and ro.ril.hsupa catagories are similar where each catagory is a target for a maximum data rate. It may seem that higher is better, but another thread on the G2 forum seemed to show that if you went too high, something triggered to lower the speeds back down to below factory levels.
http://androinica.com/2009/12/14/hack-for-rooted-phones-promises-faster-2g3g-speeds/
http://forum.xda-developers.com/showthread.php?t=595108&highlight=amon Amon_RA has a lot of good insight as to what they mean.
http://en.wikipedia.org/wiki/High-Speed_Downlink_Packet_Access
http://forum.xda-developers.com/showthread.php?t=838388
setting hsupa to class 7 is netting me 2.7mbps uploads. Crap, that is faster than my uverse service!
OMG!!! its really fast I just did a speed test i got 4.7 down and 1.4 up...Nice
I edited my build.prop on my inspire and now I get 3000 down and 1673 up i was getting 1200 down and 600 up
Here are my full settings:
GPRS: 12
HSDPA: 10
HSUPA: 7
HSXPA: 3
I didn't change any other settings.
Any steps for those who have never edited this before?
Sportsguy15 said:
Any steps for those who have never edited this before?
Click to expand...
Click to collapse
I used prop editor ( I can't remember where I found it, but it is an apk. I used it to make the changes after backing up my build.prop. I will upload here in a few minutes.
Be warned, you can wreck your software pretty good messing with this file. Just some forewarning.
Well, I'm glad it wasn't just my imagination. Those settings I posted aren't necessarily the optimum setup for our phones, so a little experimentation may yield even better results.
Sportsguy15 said:
Any steps for those who have never edited this before?
Click to expand...
Click to collapse
There are several ways to do it, prop editor being a great one. Here's what I did step by step for the new guys:
MAKE A BACKUP OF YOUR ROM THROUGH CWM.
Download "root explorer" and possibly "mount /system (rw /ro)" from the app market.
Open up root explorer and select the system folder
Near the top of the screen there should be a "Mount R/W" button. Select it. If it won't let you change to R/W, go back and open up the "mount system" app. Select Mount r/w. Go back to root explorer and you should be able to now select Mount R/W in the system folder.
Long press build.prop and scroll down to "Open in Text Editor".
Make your desired changes, tap menu and then Save & Exit. It will automatically save your original build.prop as build.prop.bak and save your changes.
Reboot twice (once didn't work for everyone in the threads I was reading).
As id10terrordfw said, you could potentially mess things up with your rom, so be careful. If you aren't confident in what you're doing, it's probably best to just leave it alone.
I just made the changes but I wont be able to do any speed tests until tomorrow. I am on the Microcell at home.
wanted to share results from my tests today. i'm using CM7 for Inspire and my daily driver - att-inspired-rooted-signed.zip from attn1 - and on both ROMs my build.prop settings are:
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 10
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 3.
the APN settings for both ROMs are in first pic. pics 2-4 are from the att stock ROM and pics 5 & 6 are from CM7. i don't know if att is tweaking something, but i've been getting some crazy fast speeds. (doesn't hurt that i live in dallas).
Trying this as soon as I get my new rom flashed
I copied the propeditor.apk to the sd card and clicked it in root explorer then clicked install. Says it can't install because of problem pasring the file?
Got the prop editor installed using appinstaller. Sadly it looks like mine is already edited in coredroid.
gprs=12
hsdpa=10
hsupa=6
hsxpa=3
Don't think there are any settings above these current ones to improve speed.
So I changed
hsdpa=14
and got way better downloads. Changed my hsupa to 7 and it was like hsupa had been disabled again. Changed back to 6 and reoobted again and still acts like it struggles to limit itself to around 300 upload. Is this something in my build.pro or in my new flash of coredroid 3.2? I never had this problem with this rom before. my ro.ril.enable.dtm setting says 0. Not sure what that is but I'll change to 1 and see what happens.
FIXED: changed ro.ril.enable.dtm = from 0 to 1 and it seems to have fixed it.
EDIT also for some reason network was set to wcdma only.
Is there a way to unlock the stock APN settings in the rooted stock rom? Or should I just create a new one?
cant edit
everytime I try to edit build.prop and try to save it, it tells me its a read only and cant save. I tried prop editor and it can't even open it.
Av8tor86 said:
everytime I try to edit build.prop and try to save it, it tells me its a read only and cant save. I tried prop editor and it can't even open it.
Click to expand...
Click to collapse
You need to make sure the file system is mounted as Read/Write. If it's mounted Read Only you won't be able to make changes. I use Root Explorer, and when you go into System you tap the "Mount R/W" button, then open build.prop in text editor. If you use ES File Explorer, go into the settings, go to Root Options, then put a check for Root Explorer, and Mount File System. Now a long press on build.prop will allow you to open it as text, make changes, and save changes. What I like about Root Explorer is it automatically makes a backup of build.prop when making changes.
Excuse my ignorance but would I have to change this section as well?
Or just the top section as the following is around the middle section of the build?
"# ace RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 10
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 3"
Sent from my most memorable Inspire 4G
Hi there. About 5 days back I posted up a question over on the other forum section asking if there was any way to do this and never got any replies. I decided to go searching and found an awesome XDA user called tomascus who in the past has modified other device cameras and some of the Xperia Z range cameras to increase bitrates when recording. He was nice enough to modify the 4K camera APK for me and I wanted to share it with anyone else who has been looking for the same thing as I was. Remember to thank him if you see him around!
There are two files now three files.
The first is;
SuperVideoCamera-xxhdpi-release.apk
This is the file you want if all you need is the 4K bitrate increase. It's set to record [email protected] 80mbps.
To use it copy the file using a file explorer with root access to the
system/priv-app/SuperVideoCamera-xxhdpi-release folder and give it the permissions 644.
I would strongly suggest you rename the original rather than overwriting it or deleting it just in case something doesn't work or you want to go back to normal.
Clear the camera app's data/cache and restart then you should be good to go.
The second file is just a modified media-profiles.xml
You don't need this unless you also want to modify the bitrates of [email protected] and [email protected]
The APK above will change the 4K bitrate without needing this file.
You can use just this file on it's own and not the APK above if you don't want to change the 4K recording but want the increased 1080 and 720.
To use this one, copy the file to the system/etc folder and give it permissions 644 and reboot.
Again, I really think you should rename the original rather than overwriting it for the option of changing back.
I set the bitrates as;
[email protected]= 54mbps
[email protected]= 24mbps
These settings also apply to recordings taken using the Timeshift camera feature.
The third file is SemcCameraUI-generic-xxhdpi-release.apk
This one will modify just the [email protected] 60FPS bitrate up to 54mbps
To use it do the same as the first file and copy it using a file explorer with root access to the
system/priv-app/SemcCameraUI-generic-xxhdpi-release folder and give it the permissions 644.
Rename the original rather than overwriting it or deleting it just in case something doesn't work or you want to go back to normal.
Clear the camera app's data/cache and restart then you should be good to go.
As far as I have tested everything worked fine. Please let me know if you have any problems and I'll try fix them.
I've added copies of the original files on the next page in case anyone ever needs them.
Thanks for the input , I installed the apk and file.xml and I have not noticed improvement in video quality. What I have noticed is that the videos take up a lot more storage space than before ...
Thanks for the feedback. I've not done much testing of it myself yet. I've had time to playback one 4K recording I took on my 4K TV vs. A couple of other ones I'd taken before the mod and the new one does look slightly more crisp. The two videos are in different conditions so it could be the lighting. I'll need to take some before and after shots of the same thing and see how it looks.
The 720 and 1080, I agree, I can't see much of a difference except slightly more dark "noise" and a larger file size. It could be a limitation of the hardware or something. Perhaps it tells it to capture more and it tries - but it just can't.
It definitely needs more testing and more feedback from anyone else who wants to try it would be greatly appreciated.
Could other things also be incorporated like some manual unlocked controls ? Or maybe ISO control in 23 MP too? Some of the features from the other camera based thread for the xperias ?
I'm pretty sure I saw something like that for an old xperia camera and there was an xposed module for the z2 that unlocked the 20mpx in certain modes so I assume these things are possible. I'm not a developer in any way though and have no idea how to do that to be honest.
I've learned some stuff so far messing about with this about how to decompile and look through the code but that sounds like a job for someone who knows what they are doing
Juan_Largearm said:
I'm pretty sure I saw something like that for an old xperia camera and there was an xposed module for the z2 that unlocked the 23mpx in manual so I assume these things are possible. I'm not a developer in any way though and have no idea how to do that to be honest.
I've learned some stuff so far messing about with this about how to decompile and look through the code but that sounds like a job for someone who knows what they are doing
Click to expand...
Click to collapse
There's another thread there by xswxm containing the unlocked apk. Maybe that could be edited by you to gain these good features too.
Ashray_Vk said:
There's another thread there by xswxm containing the unlocked apk. Maybe that could be edited by you to gain these good features too.
Click to expand...
Click to collapse
I've had a quick look at that APK from over there and all I've really been able to see is the ISO names and values. I could change the values but as I don't really know what I'm doing I don't know where I'd begin to enable ISO control at 23mpx. There's nothing simple I can see like "change this to enable it" :laugh:
This is why devs get paid the big bucks and I'm definitely in over my head.
Maybe send off a PM to xswxm and ask him if he could mod the camera for you.
Juan_Largearm said:
I've had a quick look at that APK from over there and all I've really been able to see is the ISO names and values. I could change the values but as I don't really know what I'm doing I don't know where I'd begin to enable ISO control at 23mpx. There's nothing simple I can see like "change this to enable it" :laugh:
This is why devs get paid the big bucks and I'm definitely in over my head.
Maybe send off a PM to xswxm and ask him if he could mod the camera for you.
Click to expand...
Click to collapse
It's been unlocked already.
My request was to incorporate your mod into that apk.
Edit: just realised that there's a different apk for video, sorry about the confusion. Maybe I need sleep, lol
Ashray_Vk said:
It's been unlocked already.
My request was to incorporate your mod into that apk.
Edit: just realised that there's a different apk for video, sorry about the confusion. Maybe I need sleep, lol
Click to expand...
Click to collapse
Ahh seems we both misunderstood! No problem.
Rubensss said:
Thanks for the input , I installed the apk and file.xml and I have not noticed improvement in video quality. What I have noticed is that the videos take up a lot more storage space than before ...
Click to expand...
Click to collapse
OK so after a lot more messing around it seems there is a bitrate point at which there is no longer an increase in notable quality of the video but the file sizes still get bigger as you keep increasing the bitrate. 54 mbps to my eye seems to be a good maximum for 1080p and I couldn't see any real increase of quality after 22mbps on 720p. 54 1080p might even be too high still. I'd be interested to know what other people see in terms of quality.
hello friends
When i want to copy files with root explorer it gives me an error and siad failed to copy files, i try with es explorer and it says these files are read only system files, what can i do? I have z5 premium android 6 rooted
samantafs said:
hello friends
When i want to copy files with root explorer it gives me an error and siad failed to copy files, i try with es explorer and it says these files are read only system files, what can i do? I have z5 premium android 6 rooted
Click to expand...
Click to collapse
You need to mount the folder as read/write instead of read only or you can't make any changes inside it. Going by what you described you never tried to rename the files you were going to replace first which would give you the same error too and which I would advise you to do too
You'll be glad you didn't overwrite them if you want to change back at some point.
Original Files
Just in case you never kept the old ones and want them back later :laugh: