Related
If you are using the EVO based build, you can ignore this thread.
This fix is ONLY for Desire based build with EVO's Camera application.
PLEASE DO NOT USE THIS FIX IF YOU ARE USING THE EVO BASED BUILD.
First!!
After i fix the real 5MP capture in HTCCamera, i have also fix the Thunder Cloud Review window in HTCCamera today.
The fix APK is including the real 5MP fix and correct review window after you capture.
There is no more thunder & cloud strange picture again. You can also do some actions, like Share,Delete,Goto Media Gallery or Capture again.
What's the fix
1.fix the Thunder Cloud Review Window
2.fix the real 5MP
3.fix the Shutter Sound , if you use my old file, please download it again(Update @2010/11/07)
I have only test in Desire base, OTA 2.29
How to install it?
The APK CAN NOT INSTALL into your HD2 Android.
You have two way to install this fix.
Make sure your /system is Rear/Write not Read Only.
1. Putting the HTCCamera.apk into your HD2 SD Card using File Explorer with root access, copy the fixed HTCCamera.apk to /system/app and overwrite the original one, if you can find HTCCamera.odex in the /system/app, please delete it. In order to prevent the default shutter sound, you have delete(or rename) the camera_click.ogg in system. Go to /system/media/audio/ui and find out the camera_click.ogg, delete it or rename it.
I suggest you can use a Free root File Explorer called "Super Manager". The software you can search it on Market by "Super Manager" or "gpc". It is my design. It can help you move the fixed APK file into /system/app.
2. Using shell command
Code:
adb push HTCCamera.apk /system/app
adb shell rm /system/app/HTCCamera.odex
adb shell rm /system/media/audio/ui/camera_click.ogg
If you use it in your release build, CREDITS, thanks
How to use it?
First, you have using the last EVO-bases kernel and the attachment APK file.
After installing it, you just have to launch the Camera.
If you are lucky, you can enjoy the new real 5 Mega pixel camera without Thunder Cloud right now. You don't have to reset you HD2-Android.
Enjoy it!!
If the fix is helpful, you can donate to me. thanks
Awesome!
Thanks a lot. I've been looking for something like this for quite a while.
Oh yes !
Thanks a lot !
Thanks for your work. now fix HD recording
(i know its codec related)
i have tried this but it just disable review after photo taking, is it something wrong?
Worked like a charm for me. thanks.
I used Android Commander to copy the file, I tried using super manager like you said but it would copy the file incorrectly to 0.00k, weird.
Anyway works now.
Thanks man. Works great.
Great Job
Tested Work 100%
Thanks
Does this fix the widescreen picture at 5mpx resolution. I don't think so
Sent from my HTC HD2 using XDA App
Any one having this resolution with this?
2592*1944 (Real 5 Mega Pixel)
How is it possible?
I did as mentioned in the first post, cloud at preview has been successfully fixed, but I didn't get the real 5 mega pixel. I desire it!
Can some one please help me?
After replacing my Camera app I now have no camera app at all! I tried 3 or 4 times, downloaded the file twice and used 2 different root explorers, including the one suggested.
Anyone know what could be causing this?
I am using a Desire-based build for Tmo-US, and I upgraded the kernel to Hastarin r8 before attempting this.
EDIT: Nevermind, switched builds now fix is already applied
works for me!
Hiya, first a big thanks for this one, seems to work perfectly, getting full 5mp (2592 x 1944) res photo's without the cloud stuff, review window works well, seems to keep to the 5 second timeout i put in settings for it too.. replaced original file with android commander btw, just make sure u got usb debugging mode on for that to work
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
working with darkstone froyostone 3.2 with hastarin r8 + letama's pppd wrapper v0.3 here
edit: been trying some more settings, and it seems that setting the camera to widescreen just stretches the photo to widescreen, the picture looks squashed compared to what u see in the viewfinder(screen) before u take the photo. doesn't seem to be the case for the 4:3 mode though, taking pictures there just gives nice unsquashed photos
Perfect !
Thank for your hard work !
But how to ZOOM ?!
djbarney said:
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
Click to expand...
Click to collapse
Thanks for the work and I second the shutter sound request too.
noobshite said:
Thanks for the work and I second the shutter sound request too.
Click to expand...
Click to collapse
fix it now.
You can referrer to the first post
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Will next fix for Face detection?
shree.cse said:
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Click to expand...
Click to collapse
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
I remember 1 of the version from darkstone ROM, the camera face detection is working fine. But i can't recall which version is that.
iamgpc said:
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
Click to expand...
Click to collapse
Then what does this mean?
Fix: Real 5mpx
Sent from my HTC HD2 using XDA App
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).
Know issues:
1. Bluetooth toggle will not turn on
2. video codec makes first 10-15 seconds of video only green screen--(not noticed so much after install gapps and using chrome browser)
3. Camera not working
Resolved*
*testing phone had stock camera app disabled and was using open camera. With stock camera multiple crashes and unable to connect issue with camera. V3.5 has removed stock camera and added open camera to priv-app (preinstalled)
4. Microphone is also not working
V3.5 has fixed microphone.
5. video recording not working
V3.7 fixed video record for back camera only--also seems to have stabilized photo camera--(but still has crashed)
V-x-4.1 minor edits. Removed old renamed files. Removed apps and libs for fingerprint scanner. Swapped apns-config.xml from V21 to try get connection for more carriers. But it seems some devices are not able to even see imei from board V4.1 removed. Audio broken
x-v-4.6 has audio streaming partly functioning. Audio/ video plays some amount of time then stops. but will continues if playing through bluetooth. Further testing on speaker needed. Audio issue notIS present in FMRadio and unknown in phone. So far only in streamingMOST SOUND situations, like music apps and YouTube.
Also list of added apps primarily added for testing reasons
1. GPS test
2. AudioRecorder
3. File_Manager _es_file V3 (fewer ads)
4. OpenCamera
V5.0
removed extra fingerprint program, added MDDB folder (base band) trying to resolve 2 reports of lost IMEI on this rom. I have not had issue, so cannot confirm if adding these files has fixed problem.
V6.7-current beta
/system changes tracked on github
v6.7-or current /system
boot.img changes on github
https://github.com/mrmazakblu/Slim-port-boot-img
..
..
Install:
must have unlocked boot loader.
put rom file on sdcard and install with twrp =>Latest TWRP 3.1.1-0
you needs to install gapps.
http://opengapps.org/http://opengapps.org/
You need to enable navigation bar to get onscreen buttons.
settings >Navigation >Navigation bar >Enable navigation bar.
thanks to : @vampirefo this rom is ported from his build for the BLU Life Max
XDA:DevDB Information
Slim6 port for R1-HD, ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 's Blu Life Max SlimRom
Version Information
Status: Beta
Stable Release Date: 2017-06-16
Current Beta Version: x-5.0
Created 2017-06-09
Last Updated 2017-11-02
Thanks Great work I would like a RR.5.7.4
Enviado desde mi R1 HD mediante Tapatalk
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
meroher said:
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
Click to expand...
Click to collapse
there are 4 screen shots on the screenshot tab. But the look of any rom can be changes how you like with different launchers if desired.
Fixed the bugs except for the camera one.
New zip file in download tab.
Moved status from testing to beta.
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
vampirefo said:
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Camera Is Fixed*
I now have camera working on this slim port...
uploading built/port number 33 (X-3.3)
still needs small bug fixed, that will not screen cast to chromecast.
and first time I opened camera I did not have any on-screen navigation buttons(no way to exit camera). after some time buttons were available and next time it opened normal.
mrmazak said:
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Click to expand...
Click to collapse
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
vampirefo said:
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
mrmazak said:
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
Click to expand...
Click to collapse
Yes, ROM is built for 6737, R1HD and Life Max are almost the same phone, difference size, camera and 6737 instead of 6735.
Anyway good job.
Sent from my Life Max using Tapatalk
how is the performance vs stock with all bloatware removed?
deathblade200 said:
how is the performance vs stock with all bloatware removed?
Click to expand...
Click to collapse
Seems a little quicker on slim6
Great job, I like it
So is this a usable daily driver?
roboman2444 said:
So is this a usable daily driver?
Click to expand...
Click to collapse
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
mrmazak said:
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
Click to expand...
Click to collapse
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
roboman2444 said:
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
Click to expand...
Click to collapse
I do not think the camera fix here will help 7.
These lib files, "so" files, "blobs", call them as you will. Are still for Android 6 so , as I believe will not work on 7
mrmazak said:
Seems a little quicker on slim6
Click to expand...
Click to collapse
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
deathblade200 said:
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
Click to expand...
Click to collapse
They would be the same or about the same, a rom doesn't increase benchmarks, a custom kernel might, benchmarks have their place this isn't one of them.
To each their own I guess.
Sent from my Life_Max using Tapatalk
I have created a Magisk based DIY GCAM port for our 10's. Basically, it installs everything you need for it to work, and you try/select whatever GCAM you think works the best. All this will do is enable the extra features for GCAM
***SLOMO NOT WORKING ON OREO FOR ME***
Prerequisites:
2.xx.xxx.xx Nougat Stock sense, not sure about LOS or others (you can try, no guarantees).
3.xx.xxx.xx Oreo Stock sense, not sure about LOS or others (you can try, no guarantees).
Magisk 15.0 or newer (Uses 1500 template)
No Other GCAM installed (remove any prior to flashing magisk module)
REMEMBER TO SET ALL SETTINGS AND FC ONCE BEFORE USE!!!!!
What it does:
It replaces media_profiles.xml in system/etc : this allows for HEVC and 60fps
Oreo Version
It adds ARCore and ARStickers to system/app
It sets ro.config.calibration_cad=/system/etc/calibration_cad.xml
It adds res_ctrl.conf to system/etc
it updates all the various .xml files that have media settings within them
This is a free-for-all zip, meaning i dont care if you modify it, pass it off to other groups, help anybody else, etc.
I am not responsible if you get your phone messed up, it works for me, and for others. I will help as much as i can. Its a work in process, hopefully, it will make life easier for everybody. This is really close to being a DD, i will try other GCams as i find time. Im really waiting for Oreo on VZW, then ill really get into it. (AR Stickers, etc.)
Also, this is a HTC 10 thread, and while i dont mind helping people (I want everybody to have a working GCAM) this magisk module, especially the media_profiles.xml is very very very 10 specific. You can however, do the legwork, use this zip as a template, and make one for your threads/personal use as well. And i dont mind. Just dont come in here without a logcat with some phone that's not a 10 and say its broke. I will at least look at a logcat and help if its not a 10, but my demands have been expressed.
Also, for those with a 10.. Dont come in here and tell me its broke, not tell me anything relevant, have no logcat, and expect a fix...you will be meme flamed for my amusement...You have been warned. You should know better at this point!!!
Thanks
@Arnova8G2 Porting Gcam over to us, and listening to our needs
@tsalta Getting everything moving along, and testing with me
Link Nougat (DIY GCAM MOD)
https://www.androidfilehost.com/?fid=890129502657598199
Link Oreo (DIY GCAM MOD)
https://www.androidfilehost.com/?fid=746010030569969249
GCAM Repo
https://www.celsoazevedo.com/files/android/google-camera/
Old Versions Here
https://www.androidfilehost.com/?w=files&flid=256412
Enjoy
Changelog/Bugs:
DIY GCAM MODS: Everything but GCAM, Pick the one you like the best and use this mod to get the extras to work.
V31: Version back to 2 revs. 1: Skulshady V3.0, portrait works (6p or pixel 2017 zsl hdr +, that one has low light bug still), Tolyan009 v1.3.5, portrait doesnt work, more options (needs alot of configuration, pixel 2, 2017 pixel zsl hdr+ new, black level 64, hdr+ control on, turn off use google photos in debug settings)
V30: Oreo and Nougat: Added HEVC Back in, Removed Lens (Built into photos now), some people say slomo works in oreo now, you tell me Uses Arnova V7B6 Camera...too bad it's junk......
V28: Cleaned up media_profiles_vendor.xml and added HEVC support. (Slo-Mo at least loads the viewfinder now, getting warmer )
V24: Low Light/Flash Bugs fixed, increase sharpness might be better, still no slo-mo
V23: Same oreo bugs
v8 Nougat: Updated to arnova pixel2mod v6b14, probably the last good one
v8 Oreo: Initial release, has b14, and AR stickers, need someone to test it on oreo.
v7: 99.98% works, only "little" bug is if you take a low light/room is completely dark photo (front and rear), very rarely, but sometimes the camera app crashes.
v1: Initial release
Bugs: No front HDR, Slo-mo crashes went set to 240fps (120 is fine), can only take picture with hdr+ enhanced on for rear, view finder is a little slow for portrait mode rear.
V28: To ease confusion, 6P works with everything it appears, 2017 Pixel HDR ZSL has some issues in low/no light still (wanna help, PM @tsalta )
V24: Either works i believe
V23: I use nexus6P, you can use pixel 2 as well
v8: Use nexus 6P, it all works, you can use 2017 pixel zsl HDR+, but it will FC in dark/no light using flash.
How to modify the zip for your a new gcam:
1. uninstall gcam mod
2. reboot
3. Install gcam of your choosing
4. using root browser, copy directory from data/app containing google camera directory.
5. take the contents of that folder, copy the contents to the zip file, in system/app/GCAM, replace the contents in there.
6. reflash zip with new gcam
thank for share
aer0zer0 said:
I have created a Magisk based GCAM port for our 10's, based off of whatever GCAM is working mostly at the time. It has Google Lens support, portrait mode front and rear, HDR rear, Slo-Mo, 60FPS support.
Prerequisites:
2.xx.xxx.xx Nougat Stock sense, not sure about LOS or others (you can try, no guarantees).
Magisk 15.0 or newer (Uses 1500 template)
No Other GCAM installed (remove any prior to flashing magisk module)
What it does:
It replaces media_profiles.xml in system/etc : this allows for slo-mo and 60fps
It adds google_build.xml in system/etc/sysconfig: Lens
It adds nexus.xml in system/etc/sysconfig: Lens
It adds pixel_2017.xml in system/etc/sysconfig: Lens
It adds pixel_2017_exclusive.xml in system/etc/sysconfig: Lens
It adds GCAM in system/app:
This is a free-for-all zip, meaning i dont care if you modify it, pass it off to other groups, help anybody else, etc.
I am not responsible if you get your phone messed up, it works for me, and for others. I will help as much as i can. Its a work in process, hopefully, it will make life easier for everybody. This is really close to being a DD, i will try other GCams as i find time. Im really waiting for Oreo on VZW, then ill really get into it. (AR Stickers, etc.)
Also, this is a HTC 10 thread, and while i dont mind helping people (I want everybody to have a working GCAM) this magisk module, especially the media_profiles.xml is very very very 10 specific. You can however, do the legwork, use this zip as a template, and make one for your threads/personal use as well. And i dont mind. Just dont come in here without a logcat with some phone that's not a 10 and say its broke. I will at least look at a logcat and help if its not a 10, but my demands have been expressed.
Also, for those with a 10.. Dont come in here and tell me its broke, not tell me anything relevant, have no logcat, and expect a fix...you will be meme flamed for my amusement...You have been warned. You should know better at this point!!!
Also: Since for right now, there is really only 1 good working configuration, you will need to look at 3rd post for settings. Please fiddle as you like, post settings that are better than mine.
Link v1
https://www.androidfilehost.com/?fid=673956719939816978 (Latest Version)
Enjoy
Click to expand...
Click to collapse
Hello dude i see you are starting like you sayd befor im just wondering what version you used like a base?
Arnova 1.6 or maybe 1.2 ?
Just wondering
Thanks for the Share will test it now!
Edit: Yes 1.6 i guess or perhaps 1.7 but the feel is like more 1.6
Yes this is the most stable build with all the options that we can have the only one thing we gona miss is the Pixel 2017 HDR+ ZSL the ZSL works only with this presets and since the new versions it doesnt work anymore the last time was worked fine on V 1.2
---------- Post added at 09:20 AM ---------- Previous post was at 08:54 AM ----------
aer0zer0 said:
Changelog/Bugs:
v1: Initial release
Bugs: No front HDR, Slo-mo crashes went set to 240fps (120 is fine), can only take picture with hdr+ enhanced on for rear, view finder is a little slow for portrait mode rear.
Click to expand...
Click to collapse
well i can take pictures with HDR+ and HDR+ Enhchanced from the Back camera so it is working fine not bug.
Also the Front HDR+ is working what i mean is it is made to work only In portrait MOD so when you shoot Portrait with the Front and you have HDR+ portrait camera enabled will get the effect this is how the build is mean to work so you can remove this from the Bugs it is not actually a bug.
Slow mo crashes on stock Oreo
And also 60fps does not work
tsalta said:
Hello dude i see you are starting like you sayd befor im just wondering what version you used like a base?
Arnova 1.6 or maybe 1.2 ?
Just wondering
Thanks for the Share will test it now!
Edit: Yes 1.6 i guess or perhaps 1.7 but the feel is like more 1.6
Yes this is the most stable build with all the options that we can have the only one thing we gona miss is the Pixel 2017 HDR+ ZSL the ZSL works only with this presets and since the new versions it doesnt work anymore the last time was worked fine on V 1.2
---------- Post added at 09:20 AM ---------- Previous post was at 08:54 AM ----------
well i can take pictures with HDR+ and HDR+ Enhchanced from the Back camera so it is working fine not bug.
Also the Front HDR+ is working what i mean is it is made to work only In portrait MOD so when you shoot Portrait with the Front and you have HDR+ portrait camera enabled will get the effect this is how the build is mean to work so you can remove this from the Bugs it is not actually a bug.
Click to expand...
Click to collapse
Arnova 1.7 beta 1
It will only take pics on hdr+ if it decides hdr should be used. If you turn hdr off, it won't work.
Yea, I'm aware of the work around for front hdr+. But you can't just have hdr+ on the front camera in normal mode. So it's a bug still until we find a better alternative camera that works.
You can be the tester @tsalta if you like. I explained how to put different GCAMS in the magisk zip, so you can find the perfect version.
aer0zer0 said:
Arnova 1.7 beta 1
It will only take pics on hdr+ if it decides hdr should be used. If you turn hdr off, it won't work.
Yea, I'm aware of the work around for front hdr+. But you can't just have hdr+ on the front camera in normal mode. So it's a bug still until we find a better alternative camera that works.
You can be the tester @tsalta if you like. I explained how to put different GCAMS in the magisk zip, so you can find the perfect version.
Click to expand...
Click to collapse
Yes im planing to make one version same with 1.6 because 1.6 is more stable than 1.7 beta ad 1.7 in 1.6 will take pictures always with HDR+ or Enchanged whatever you want from the back camera.
and i think 1.6 is one idea faster no freeze slownes on the viewfinder
Los Ron (rr), HDR working, portrait mode too, but slow motion mode not
Thanks anyway)
@aer0zer0 i was planing to make another version but after alot of test the most stable build that work is 1.7 Beta 1 so thanks for the share.
I mean compared to the Other builds that have Portraid mode if not 1.2 is the most stable
Like ive sayd many times every build have some advantage and dissadvantages for example 1.2 is super fast and stable also has working Pixel config with ZSL in other hand do not have POrtrait
Well above 1.6 they have everything but the pixel config is not working and no ZSL at all.
Also i have some other builds that are Not Arnova diferent from different russian sites and i had the best Front + HDR+ mod and take amazing HQ selfies but only this is the advantage of the mod.
if we have somehow to make a mix like frankenstain from the mods we know who is best and work perfect to make One build that include all the things.
Thanks for the Magisk Module.
tsalta said:
@aer0zer0 i was planing to make another version but after alot of test the most stable build that work is 1.7 Beta 1 so thanks for the share.
I mean compared to the Other builds that have Portraid mode if not 1.2 is the most stable
Like ive sayd many times every build have some advantage and dissadvantages for example 1.2 is super fast and stable also has working Pixel config with ZSL in other hand do not have POrtrait
Well above 1.6 they have everything but the pixel config is not working and no ZSL at all.
Also i have some other builds that are Not Arnova diferent from different russian sites and i had the best Front + HDR+ mod and take amazing HQ selfies but only this is the advantage of the mod.
if we have somehow to make a mix like frankenstain from the mods we know who is best and work perfect to make One build that include all the things.
Thanks for the Magisk Module.
Click to expand...
Click to collapse
No problem, once Oreo hits, everything will be better, I'm sure
romixer said:
Los Ron (rr), HDR working, portrait mode too, but slow motion mode not
Thanks anyway)
Click to expand...
Click to collapse
You have a 10, right? The only thing I can think of is media_profiles.xml is not in the right spot.
aer0zer0 said:
You have a 10, right? The only thing I can think of is media_profiles.xml is not in the right spot.
Click to expand...
Click to collapse
Yes it is media Profile xml i never ever had Slow Mo to work no matter of the presets in best case just freeze and i found out that this heppand only in Viper Magisk ROM people who are with Lee Droid v 4 have Slow Mo working so im pretty sure its ROM related and thats why i leave it thats way i get tired of trying to fix it and just waiting the OREO.
@tsalta have you tried older builds, like in the 1.4s I would sacrifice portrait mode for clean front and rear camera implementation. The 10 was my daily driver till I got a essential phone mid September. So I haven't messed with it much. Are the bsg versions any good?
tsalta said:
Yes it is media Profile xml i never ever had Slow Mo to work no matter of the presets in best case just freeze and i found out that this heppand only in Viper Magisk ROM people who are with Lee Droid v 4 have Slow Mo working so im pretty sure its ROM related and thats why i leave it thats way i get tired of trying to fix it and just waiting the OREO.
Click to expand...
Click to collapse
You have to add Google's preset media configs to media_profiles.xml that's how it works. 240 fc, since the sensor can't handle it.
aer0zer0 said:
You have to add Google's preset media configs to media_profiles.xml that's how it works. 240 fc, since the sensor can't handle it.
Click to expand...
Click to collapse
I have the google preset for the slow motion but same the viewfinder freezes imideately when i press slow motion.
Anyway in the Magisk version u provide you have media profile xml with the settings and is the same if you have another idea how to add this google media configs let me know or write me them here to chek what i have now to see if they differ.
About the Gcam Mods.
I tested all of them by all i mean even builds that are not even listen on XDA.
for me Arnova 1.2 is one of the best for us because its fast and all HW levels are added to support level 3 so we HTC 10 users and many other devices that have and can handle camera 2 api have HW level 3 support.
In the 1.2 Bold Red build from Arnova even the Pixel 2017 ZSL HDR+ preset work in all conditions i never had a single crash there shooting day and night, the only one downside is that there is no Portrait MODE.
Another info like i mentioned befor i had one Build if you wish will upload it that it has the Most amazing fron Shooter with HDR+ it is based on BSG build but edited by some Russian folk from 4pda i used this mod only because of the front facing camera a slefie is about 5 mb in size Crisp and clear like you shoot it with back camera.
Other than that one of my Favorite as well is the ArtZ based Mod that is Pixel based Version 2.
Have everything working ZSL all is set to use Pixel configs have a Portrait Mod working and so on.
The only problem with this build is like i explain several times befor shooting in the dark when there is not Object to focus the app force crash it is somthing related to the Focus plus the Flash it is like the Flashligh do not work properpy in synhron with the Focus and the HDR+
but for a day and good light photos i got the best pictures with this ArtZ MOD.
---------- Post added at 03:55 PM ---------- Previous post was at 03:48 PM ----------
aer0zer0 said:
@tsalta have you tried older builds, like in the 1.4s I would sacrifice portrait mode for clean front and rear camera implementation. The 10 was my daily driver till I got a essential phone mid September. So I haven't messed with it much. Are the bsg versions any good?
Click to expand...
Click to collapse
Try this out just set up the camera on 1st run for Max Quality and shoot with the Front Camera in Good Light condition.
If we have somehow to see what settings use this apk for the front to implement in the 1.7 regular front will be Awesome.
https://drive.google.com/open?id=1wzNyFYW0C8Esz2yZb2M0-fvXTw_1p8Sf
tsalta said:
I have the google preset for the slow motion but same the viewfinder freezes imideately when i press slow motion.
Anyway in the Magisk version u provide you have media profile xml with the settings and is the same if you have another idea how to add this google media configs let me know or write me them here to chek what i have now to see if they differ.
About the Gcam Mods.
I tested all of them by all i mean even builds that are not even listen on XDA.
for me Arnova 1.2 is one of the best for us because its fast and all HW levels are added to support level 3 so we HTC 10 users and many other devices that have and can handle camera 2 api have HW level 3 support.
In the 1.2 Bold Red build from Arnova even the Pixel 2017 ZSL HDR+ preset work in all conditions i never had a single crash there shooting day and night, the only one downside is that there is no Portrait MODE.
Another info like i mentioned befor i had one Build if you wish will upload it that it has the Most amazing fron Shooter with HDR+ it is based on BSG build but edited by some Russian folk from 4pda i used this mod only because of the front facing camera a slefie is about 5 mb in size Crisp and clear like you shoot it with back camera.
Other than that one of my Favorite as well is the ArtZ based Mod that is Pixel based Version 2.
Have everything working ZSL all is set to use Pixel configs have a Portrait Mod working and so on.
The only problem with this build is like i explain several times befor shooting in the dark when there is not Object to focus the app force crash it is somthing related to the Focus plus the Flash it is like the Flashligh do not work properpy in synhron with the Focus and the HDR+
but for a day and good light photos i got the best pictures with this ArtZ MOD.
---------- Post added at 03:55 PM ---------- Previous post was at 03:48 PM ----------
Try this out just set up the camera on 1st run for Max Quality and shoot with the Front Camera in Good Light condition.
If we have somehow to see what settings use this apk for the front to implement in the 1.7 regular front will be Awesome.
https://drive.google.com/open?id=1wzNyFYW0C8Esz2yZb2M0-fvXTw_1p8Sf
Click to expand...
Click to collapse
So even using the magisk mod, slo- mo crashes? It works fine for me, just 240 crashes, 120 works fine
aer0zer0 said:
So even using the magisk mod, slo- mo crashes? It works fine for me, just 240 crashes, 120 works fine
Click to expand...
Click to collapse
Yes even the Magisk Mod and i know this heppans in Viper ROM i don`t know why.
Im sure if i flash now LeeDroid will work but like i say im just waiting OREO
tsalta said:
Yes even the Magisk Mod and i know this heppans in Viper ROM i don`t know why.
Im sure if i flash now LeeDroid will work but like i say im just waiting OREO
Click to expand...
Click to collapse
Works perfect here, what rom are you on?
Are any v35 users using a gcam mod? If so, can you share which one and your experiences?
Well for 5-th branch hands down the best one is GoogleCamera_5.2.025-Final_fu24-18c1.apk and can be found here
Regarding 6-th latest Gcam_6.1.021_Advanced_V1.7.190716.1800 by Arnova works flawlessly with this XML config.
On a project fi v35, the GoogleCamera_5.2.025-Final_fu24-18c1.apk was too laggy for me. I ran 01.MGC_6.1.021_G7_test_v1.apk and was able to snap pictures with front and rear, but the 02.MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk crashed on launch.
Will post a logcat once i can.
Have you properly applied the XML setting (step 8) after installing MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk?
Lag in viewfinder is cause by overloaded buffer in this version which is easily fixable either by applying XML as shown or by enabling the Buffer Fix switch in app Settings.
Nope, after installing the 02 apk, it crashes on launch so I don't get the chance. Tweaked settings w/ the other one and got it working at least, thanks!
You are welcome!
N.B.: If you want to have it working you need to follow the guide up to the letter, so whenever you get bored and want to try again just uninstall the current GCAM, restart your phone and start again.
Do not forgot to take again 2 pictures after installing 1st apk and to properly import the XML settings after installing the 2nd apk and starting it for the first time.
mcsterling said:
Nope, after installing the 02 apk, it crashes on launch so I don't get the chance. Tweaked settings w/ the other one and got it working at least, thanks!
Click to expand...
Click to collapse
Same problem, I can't do step 8 because the camera crashes when trying to open.
I have LG V30+ H930DS, and I use this two Gcams.
One is 90% wokring (maybe panorama doesnt work) but all other is perfect (wide, noraml, portrait front/back, HDR+, SlowMotion) and its fast. (To chagne between lenses, just hold switch button, it will redirect to settings, after you close settings lense will be changed.
The other one I use only for NightSight. This camera has problem with selfies, they have green tint. It also have Wide/Normal switch, ( just chage between selfie and back camera, and each time ju go back to main camera it will be diferent lense)
I'm satisfied with this phone, for me everything is perfect, but i found LG V35 for good price and I would like to konw if there is somebody with V35 who will try this two Gcams, and tell me does they work properly, or if there is some others which works good, because i wouldn't change V30 for v35 if I can't have good working Gcam.
https://drive.google.com/file/d/1PcSs31bSenYiC3At0p_1So6xpBA7SaGm/view
https://drive.google.com/file/d/1OsyM99VdOLjUMxRryoFtR15Wkqt6LSVG/view
Latest GCam with respective easy import settings can be found in one archive here
vlad48 said:
Latest GCam with respective easy import settings can be found in one archive here
Click to expand...
Click to collapse
Thank you for the link. I downloaded, installed and restored the supplied config file for my V35.
Regarding Night Sight, is there a setting to change to fix the choppy motion when moving around the viewfinder?
No way for now on improving Night Sight viewfinder lag.
vlad48 said:
Have you properly applied the XML setting (step 8) after installing MGC_6.1.021_BSG_Arnova_TlnNeun_04.02.19.12.54.apk?
Lag in viewfinder is cause by overloaded buffer in this version which is easily fixable either by applying XML as shown or by enabling the Buffer Fix switch in app Settings.
Click to expand...
Click to collapse
where is step 8 described? I can find no reference on how to apply this xml config.
Step 8 originates from really old installation guide.
Now you need only to install the camera apk and import the xml settings file.
Where/how to extract the xml file and how to import it afterwards you can check here
vlad48 said:
Step 8 originates from really old installation guide.
Now you need only to install the camera apk and import the xml settings file.
Where/how to extract the xml file and how to import it afterwards you can check here
Click to expand...
Click to collapse
Thanks. I must have been downloading wrong version, since double clicking didn't work. Tried again this morning and it works now.
After applying the xml fix to v6.1 camera, it works, but I wouldn't call it "good". It's super annoyingly slow to make pictures. 5.2 also lags substantially, and won't load xml settings. So far, lg camera is hands down better
so... MGC_6.2.030_MI9SE_V4_plus2.apk has been the only version for me that has worked without issue...problem is pictures are not clear. although the viewfinder is fixed with the buffer fix toggle, when taking photos its not quick therefore the pictures blur slightly.
do you all encounter the same and if not which version and configuration has given you a fast shutter?
Here is what I posted on arnova's thread with the suggestion of another member.
hachiroku said:
thanks...i Gcam_6.2.030_Advanced_BF_V2.2.1.190822.1145.apk works for my V35 as it seems BF means it has the buffer fix built in. shame it doesn't allow for zero shutter lag as for phones that don't need a buffer fix. as the OEM camera can take photos super fast.
here are my settings for my LG V35 on Pie on Gcam_6.2.030_Advanced_BF_V2.2.1.190822.1145.apk
back camera: Pixel 3 XL
front camera: Nexus 6P
AWBGains Mod: OFF, was causing GREEN photos with it on
RAW FORMAT: RAW_SENSOR
Image Format: JPEG (if i set YUV_420_488 GCam crashes)
P3 wide-color, Wide Color gamut
playing around with Custom Lib Repo by cstark and with Eszdman v2.6 beta 2
image quality is awesome, and no blur upon shutter snap as with other GCams! Thanks @arnova!
Click to expand...
Click to collapse
Hey everyone, I'm currently exploring some gcam options and I found that the latest Arnova Gcam works great with no lag (it does take a bit longer to capture a photo than it does on my sd820 device) but sadly it doesn't offer wide camera mode.
Now, there is the cstark camera and wide angle mode actually does work, but using the camera is impossible because the preview (you know, the thing you see on your screen before you take a picture) changes once every 5 seconds or something. I tried importing some xmls and that sped it up just a bit but not by much.
Is there some working version that was tested for v35? My v35 is Korean model
vlad48 said:
Well for 5-th branch hands down the best one is GoogleCamera_5.2.025-Final_fu24-18c1.apk and can be found here
Regarding 6-th latest Gcam_6.1.021_Advanced_V1.7.190716.1800 by Arnova works flawlessly with this XML config.
Click to expand...
Click to collapse
I get terrible stutter on the night site with this 6-th and the config file. Any fixes?
You need to be on Pie and you can use Gcam_6.2.030 with working Night Sight without lag.