Don't use. Thanks
May or may not work. I just need more info
Saw as a feature of NucleaROM so I was curious.
https://www.qualcomm.com/news/snapd...ay-power-efficient-technology-thats-easy-eyes
XPeria and Nexus 6p had made patches but the XPeria one didn't do anything for me and the 6p one had a little screen resolution change needed.
Download files
Look at picture in direct sunlight
Backup phone
Install zip in twrp
Now look at picture in sunlight and see if dark letters are more legible
Adjusts pixel gamma and color help with daylight viewing
Cool feature thanks for sharing
Is this for stock only or will it work in AOSP based Roms?
I think chinese stock rom had the function built in.. Toggled few times didn't noticed anything...
Just read the article.. Quite interesting.. Will try to add it in the badboyz rom..
Sent from my ZTE A2017U using Tapatalk
Is this not already in all stock versions?
It is in A2017G:
joaste said:
Is this not already in all stock versions?
It is in A2017G:
Click to expand...
Click to collapse
I'm not on stock now (A2017U here), but it most certainly wasn't last time I checked.
KwesiJnr said:
I'm not on stock now (A2017U here), but it most certainly wasn't last time I checked.
Click to expand...
Click to collapse
Well, I've had it on my A2017G since at least B10 (I got the phone with B06 but updated immediately to B10, so don't know if it was on B06).
I mean, I flashed this on NucleaROM and I booted just fine. I'm not so sure if I notice any thing however​. I am not sure if this was baked in yet to NucleaROM or not and maybe that's why? Have not had much time to follow along with the threads with as much detail as I would have liked.
joaste said:
Is this not already in all stock versions?
It is in A2017G:
Click to expand...
Click to collapse
It's not in 2017U stock
Sent from my ZTE A2017U using Tapatalk
It's already in NuclearROM from what their features say. I hadn't seen it in the stock settings unless it's in the latest Nougat, at least it wasn't for me on the U.S phone. I'm on LineageOS which is lacking it. Just check in /system/etc for the ad_calib.cfg
On 2nd glance I think LineageOS does include a file called calib.cfg which does the same thing. So you may have to check and see if it's already using assertive display.
Looks like it's in the LOS ROM as generic code but needs calibration (screen size and gamma values). I'd hold off on using it unless it ends up in a ROM. I don't think it's unsafe, just may or may not do what you want it to do.
In LineageOS build.prop
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/calib.cfg
ro.qcom.ad.sensortype=2
`SBR` said:
I think chinese stock rom had the function built in.. Toggled few times didn't noticed anything...
Just read the article.. Quite interesting.. Will try to add it in the badboyz rom..
Click to expand...
Click to collapse
It may or may not work.
There's already a file in Badboyz called /system/etc/calib.cfg but I don't think it's actually calibrated.
May need to get the file from the Chinese ROM and compare if it is indeed used though, from the sound of it, ZTE didn't calibrate it properly.
In the build.prop you'd see the lines I mentioned above.
In the calib.cfg file I imagine if it was properly configured it would at least show
# frame width
1440
# frame height
2560
The fact the Xperia one had weird lut values (1,2,3,4...) told me they maybe didn't calibrate it
I assume a manufacturer actually has tools from Qualcomm to calibrate these things for shipment in a device for a phone's particular display.
jawz101 said:
It may or may not work.
There's already a file in Badboyz called /system/etc/calib.cfg but I don't think it's actually calibrated.
May need to get the file from the Chinese ROM and compare if it is indeed used though, from the sound of it, ZTE didn't calibrate it properly.
Click to expand...
Click to collapse
I just found the calib.cfg file from the Stock 7.1.1 from a2017G. was gonna post that there was one but it seems you're already aware of that lol
If you want the file I can send it to you. It says something about 1080x1920 so I'd guess it's rather not calibrated
Choose an username... said:
I just found the calib.cfg file from the Stock 7.1.1 from a2017G. was gonna post that there was one but it seems you're already aware of that lol
If you want the file I can send it to you. It says something about 1080x1920 so I'd guess it's rather not calibrated
Click to expand...
Click to collapse
Well, it's just a guess. There was something in the XPeria thread which mentioned adjusting that part to be your screen resolution. I'm also guessing to have it completely calibrated you'd need to know the detailed specs on the display as well as having a utility from Qualcomm to make the proper calibrations.
https://qrd.qualcomm.com/en/resources/tools
I'll try it out on LineageOS and report back once I've done enough testing.
God this is botherimg me a lot... I'm on stock B02 and the assertive display overlay flashes on and off every time I touch the screen. If I get root I'll try to change the values. I don't know if it will work though cause I've never been able to mount system R/W even after disemmcwp
New findings, sort of: this is from the stock B02 from A2017G. The config file says 1080 1920 but there's another file with a suspicious name over there:
/system/etc/qdcm_calib_data_zteSAM_S6E3HA3_SAM_25601440_5P5Inch.xml
It weights like 3.5 mb so root browser doesn't even want to open it...
Related
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
seansk said:
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
Click to expand...
Click to collapse
anyone? please???
seansk said:
anyone? please???
Click to expand...
Click to collapse
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
frodoboy said:
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
Click to expand...
Click to collapse
Yes thats exactly what I did in root explorer in sys/camera_led_status/low_cap_limit, I set it to 5, 1, 0, did not make any difference. Also Its retarded that you cannot use flash while you're in a call....if you talking to someone and trying to take a picture it says you cannot use flash since you're in a call....wtf does that have to do with the flash!!! There should be a file somewhere in the sense UI system to change these settings, If anyone has found anything please share...or if you can think of something please share as well...
I actually like the dialer and contact aspect of sense UI and how it integerates and automatically finds linked friends, how it updates friends status in facebook and twitter, (although they still need to integrate google plus)...all the other stuff of sense I do not like...I've changed to ADW ex...and widget locker...
I doubt there's a way to get that stuff with a senseless rom since its so integerated into the system...If there is I would flash another rom in a sec and just install that aspect of sense....
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Binary100100 said:
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Click to expand...
Click to collapse
you gotta be kidding me!!!!
question 1. Are the other roms the same?? I"m unlocked and rooted but on stock rom. do senceless, beastmod or revolution have the same problem...I'm guessing they would since they use the same camera apk...or maybe not, If not i'm flashing to something else RIGHT NOW.
questions 2. are we ever going to see CM9 on the amaze....screw sense I want ICS AOSP asap...
seansk said:
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
Click to expand...
Click to collapse
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
frodoboy said:
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
Click to expand...
Click to collapse
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
seansk said:
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
Click to expand...
Click to collapse
I would suggest in the forum that consists of the kernel that you are using.
Example:
If you have QuikSense then post the request in the QuikSense forum or PM the developer (in this case xboarder56) directly.
If you use Faux's kernel then post it in that thread.
No need to start a new thread for a request. However if you feel that it is absolutely necessary do it in General because the Development section is not really a section mod requests.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
Thanks Binary. You are sooooo smart!!
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
faux123 said:
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
Click to expand...
Click to collapse
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
seansk said:
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
Click to expand...
Click to collapse
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Binary100100 said:
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Click to expand...
Click to collapse
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
seansk said:
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
Click to expand...
Click to collapse
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Binary100100 said:
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Click to expand...
Click to collapse
omg rotflmao........so basically we really can't fix the hotspot issue or the call issue!!....I'm beginning to not like HTC...and I definitely don't like sgs2...I better start designing my own phone....the N1 never had this kind of BS problems....I used it as hotspot...called...took pictures alll the way down to 0 battery and it was made by HTC...what changed??? I still like my N1 better lol...hopefully next year we'll get
new years resolution dream phone:
720p super amoled PLUS "not pentile" screen
8 or more Mega pixel back side illuminated sensor with a f/2.2 or less and a wide lense camera lense with good optics and good audio quality while recording video.
able to use flash without limitations!!!!!!!!!!!!!!!!!!!!!!!!!
no flash bleed into camera sensor that requires 3 rounds of electrical tape
No screen bleed from the soft buttons
10 hour talk talk battery preferably over 2200 mAMp battery
STOCK ICS with custom amazing camera software like that amaze has now.
NO CARRIER BRANDING NO BLOATWARE. is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them...ok maybe this last one is asking too much.
is this so much to ask???
seansk said:
...is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them... is this so much to ask???
Click to expand...
Click to collapse
Ummm... yes. I believe the best you can do is create a phone with a jackhammer for a vibration mode, shove it in the patients mount and keep calling it. But of course some other people would use it for... inappropriate purposes.
Example from one of SassyBoB's reviews: https://market.android.com/details?...t=W251bGwsMSwyLDEsImNlbml4LmFuZHJvaWQudmJyIl0.
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
danial.aw said:
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
Click to expand...
Click to collapse
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Ya I did message him... Unfortunately I believe he is busy
[r.]GimP said:
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Click to expand...
Click to collapse
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
SnowLeopardJB said:
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
Click to expand...
Click to collapse
Stuff like this keeps schooling me every day, brain starting to hurt
That being said, I setup an Ubuntu environment earlier today, from one of the guides in chef central, using 12.04 64bit, got all the packages, but i'm terrified to sync a potential 10 gigs of stuff, what exactly should i be syncing to on github for our device, and say for illusion rom to try building from source?
and as I side project today, I nearly got a zte x500 to take a custom rom and recovery from the stock recovery, after noticing ZTE signed their packages with the test keys, just needed to figure out the mmcblk for recovery for the cricket score <edit> I know the syntax that particular updater script needs now, but dont have access to the phone til monday. the person is getting a new phone anyway but it's my pet project to flash a custom rom and recovery from the stock recovery and good practice doing updater-scripts from scratch </edit>
Been a fun day.
danial.aw said:
Ya I did message him... Unfortunately I believe he is busy
Click to expand...
Click to collapse
I am not "busy" haha, just on vacation without my computer out of country
Ahh well hope you have fun and get back to your computer soon times lol
Hey Morris any chance you are back and kicking?
morrislee said:
I am not "busy" haha, just on vacation without my computer out of country
Click to expand...
Click to collapse
Just checking, would it be possible for you to make an inversion patch for your hybrid modem?
I have been around for a while and I have had a G3 before but I just picked one up again and I am using it as my daily. Now, I have tried a few ROMs, such as JasmineROM and CM12.1 snapshot and I have been having some issues.
I really cannot STAND how stock LG software looks. It is atrocious to me. That being said, I really am trying to avoid a stock-based ROM if that is at all possible. Now, with CM12, I haven't had too many problems. The phone does get pretty sluggish sometimes (taking 1-2 seconds to open apps and such), the camera takes FOREVER to open, take a pic and switch between the front and rear camera. And possible the MOST annoying is when I have been on WiFi for a decent amount of time, my data will not work unless I go screw with my network settings and change it back and forth from Global to LTE.
My question for everyone: What is the best ROM you have used? Something with a high pixel density would be nice as stock just has everything so big and ugly. Battery life is nice and I really need decent camera and data performance. Any suggestions? Thanks everyone!
I've been using xdabbebs 2.0, and I know you said you didn't like stock ones. But it's been the best for me since it came out. Battery and performance have been amazing. Also xdabbebs xcam is the stock of camera but he's tweaked it and it's so much better. I've never had good luck on aosp roms for the g3. I hope this helps
Sent from my g3 using XDA Labs
I was going to say the same thing as @jurington. Although I'm on @xdabbeb 's completely stock (besides my own debloat) 46A Marshmallow, his VS985 v2.0 is overall the best in my opinion.
jurington said:
I've been using xdabbebs 2.0, and I know you said you didn't like stock ones. But it's been the best for me since it came out. Battery and performance have been amazing. Also xdabbebs xcam is the stock of camera but he's tweaked it and it's so much better. I've never had good luck on aosp roms for the g3. I hope this helps
Sent from my g3 using XDA Labs
Click to expand...
Click to collapse
roirraW "edor" ehT said:
I was going to say the same thing as @jurington. Although I'm on @xdabbeb 's completely stock (besides my own debloat) 46A Marshmallow, his VS985 v2.0 is overall the best in my opinion.
Click to expand...
Click to collapse
Thanks guys. I decided to give it a try and the only thing I don't like is how the navbar is white most of the time. But, I went ahead and installed Xposed to get around it. I can get used to this. Thanks guys. As far as 6.0, how is that rom?
Exleh said:
Thanks guys. I decided to give it a try and the only thing I don't like is how the navbar is white most of the time. But, I went ahead and installed Xposed to get around it. I can get used to this. Thanks guys. As far as 6.0, how is that rom?
Click to expand...
Click to collapse
Glad you like it. I highly recommend some of the few "tweak" commands he mentions in the OP, too.
I always changed the navbar color in the stock settings. Settings / Display / Home touch buttons. I like dark, too.
6.0 is pretty nice, even more fluid than 5.1.1 in my opinion. There is some details it appears LG/Verizon didn't consider with the handling of USB OTG. Some have had the same trouble with the regular MicroSD access, but at least with X-plore File Manager that I use, the MicroSD hasn't been a problem. For USB OTG I have to navigate to root / mnt (I think) / then the serial number of the USB OTG device. I can and have marked it as a "Favorite" in the file manager so I can go right to it, but it's sloppy and doesn't report how much space is used or available when I access it this way.
It had been a while since I bothered with Greenify - I've largely been keeping things simple on the G3, but I use Greenify's aggressive doze feature and I do believe it makes a difference. No numbers to share, though. I've been playing with my phone a lot more since Marshmallow came out, doing back ups, experimenting, testing things etc so I can't really report numbers on battery life.
roirraW "edor" ehT said:
Glad you like it. I highly recommend some of the few "tweak" commands he mentions in the OP, too.
I always changed the navbar color in the stock settings. Settings / Display / Home touch buttons. I like dark, too.
6.0 is pretty nice, even more fluid than 5.1.1 in my opinion. There is some details it appears LG/Verizon didn't consider with the handling of USB OTG. Some have had the same trouble with the regular MicroSD access, but at least with X-plore File Manager that I use, the MicroSD hasn't been a problem. For USB OTG I have to navigate to root / mnt (I think) / then the serial number of the USB OTG device. I can and have marked it as a "Favorite" in the file manager so I can go right to it, but it's sloppy and doesn't report how much space is used or available when I access it this way.
It had been a while since I bothered with Greenify - I've largely been keeping things simple on the G3, but I use Greenify's aggressive doze feature and I do believe it makes a difference. No numbers to share, though. I've been playing with my phone a lot more since Marshmallow came out, doing back ups, experimenting, testing things etc so I can't really report numbers on battery life.
Click to expand...
Click to collapse
Seriously? I don't even need that module then lol. I rarely use OTG but I haven't had issues with my SD card so that's good. I have been playing around a lot lately too so battery life is up in the air.
the 3minit battery mod doesnt work at all tho, when I flash it I get (SystemUI has stopped working), no matter what even with a clean install.
Exleh said:
Seriously? I don't even need that module then lol. I rarely use OTG but I haven't had issues with my SD card so that's good. I have been playing around a lot lately too so battery life is up in the air.
Click to expand...
Click to collapse
Definitely no problem with the MicroSD card or USB OTG on @xdabbeb 's VS985 v2.0 since it's based on 35B / 5.1.1.
the 3minit battery mod doesnt work at all tho, when I flash it I get (SystemUI has stopped working), no matter what even with a clean install.
Click to expand...
Click to collapse
At least a couple of us had problems with the 3Minit Battery Mod that a user (sorry I forget your handle if you're reading this) made for 35B.
For me, it worked perfectly fine until restoring a TWRP backup that was made after it was installed, then FCs like you describe.
Dirty flashing the ROM etc would fix the ROM and it might've been possible to get the mod working again doing that and then re-flashing the mod, but it just wasn't worth it to me even though I have one animated battery icons on there, and I used to make the mod for a different phone.
jurington said:
I've been using xdabbebs 2.0, and I know you said you didn't like stock ones. But it's been the best for me since it came out. Battery and performance have been amazing. Also xdabbebs xcam is the stock of camera but he's tweaked it and it's so much better. I've never had good luck on aosp roms for the g3. I hope this helps
Sent from my g3 using XDA Labs
Click to expand...
Click to collapse
RAW its working for you?
jomtos said:
RAW its working for you?
Click to expand...
Click to collapse
Been working fine for me since it came out. Are you having problems?
Sent from my g3 using XDA Labs
XenonHD and Broken are great for custom. Nice features. Broken boots real fast. If you want tons of features you can use the unofficial DU build, and if you have wanted to try AOKP, they release official vs985 builds.
I am pretty content on the VS985 2.0 build but I am now having trouble getting vipermod working lol.
jurington said:
Been working fine for me since it came out. Are you having problems?
Sent from my g3 using XDA Labs
Click to expand...
Click to collapse
Yes with raw option ON the camera just close itself after taking the photo and the dng file have like 8bit size. I think its because is based on 5.1.1.
Exleh said:
I am pretty content on the VS985 2.0 build but I am now having trouble getting vipermod working lol.
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I used this one to get viper working on lollipop and marshmallow. Scroll down till you see 2 downloads, and use the one called lolliviper and flash it in recovery and should be good to go. Uninstall any previous vipers you may have installed.
jomtos said:
Yes with raw option ON the camera just close itself after taking the photo and the dng file have like 8bit size. I think its because is based on 5.1.1.
Click to expand...
Click to collapse
And I don't use the raw option, but everything else is working fine for me.
Sent from my g3 using XDA Labs
jurington said:
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I used this one to get viper working on lollipop and marshmallow. Scroll down till you see 2 downloads, and use the one called lolliviper and flash it in recovery and should be good to go. Uninstall any previous vipers you may have installed.
And I don't use the raw option, but everything else is working fine for me.
Sent from my g3 using XDA Labs
Click to expand...
Click to collapse
I got it working now using the mm beta.
My C5 Ultra is rooted fine with that guide, it is working. But some xposed mods (probably because this is a Sony ROM) isnt working and GravityBox got some bugs (ex. Navigation Bar changes dimensions on every reboot but its actually at the right value) this is actually something other than troubleshooting and Q&A because I figured out the reason while writing. But in some Xperia titled modifications there is still bugs thats the thing that bothers me. So yeah device works with root and xposed BUT modules and/or somethings are broken.
When it comes to boot animation, device just dont seem to want to change it. OEM file is custom System is custom but it still uses the default boot animation. It just feels weird. Permissions, everything is alright but it aint working.
charackthe said:
My C5 Ultra is rooted fine with that guide, it is working. But some xposed mods (probably because this is a Sony ROM) isnt working and GravityBox got some bugs (ex. Navigation Bar changes dimensions on every reboot but its actually at the right value) this is actually something other than troubleshooting and Q&A because I figured out the reason while writing. But in some Xperia titled modifications there is still bugs thats the thing that bothers me. So yeah device works with root and xposed BUT modules and/or somethings are broken.
When it comes to boot animation, device just dont seem to want to change it. OEM file is custom System is custom but it still uses the default boot animation. It just feels weird. Permissions, everything is alright but it aint working.
Click to expand...
Click to collapse
Is your device deodexed? This may be part of the problem if it isn't.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Is your device deodexed? This may be part of the problem if it isn't.
Click to expand...
Click to collapse
Honestly I dont know deodex etc. things. Ive never tried to learn never wondered honestly. But i will look it up
charackthe said:
Honestly I dont know deodex etc. things. Ive never tried to learn never wondered honestly. But i will look it up
Click to expand...
Click to collapse
I looked if thats the case and my ROM is odexed because System apks have ".odex" files in arm64 folders. So what does this mean?
aidy.lucas said:
Is your device deodexed? This may be part of the problem if it isn't.
Click to expand...
Click to collapse
Thanks for the info. In slowly figuring out deodexing things. Unfortunately imma have to use PC and I'm away from mine. I will keep XDA updated about this. People might not be developing this device too much but it deserves to be developed due to its screen size. Before C5 Ultra I had a Galaxy Mega 6.3 and that phone didn't had too many developers either. I think this is weird why people don't know to develop some ROMs modifications or something else to these big screen devices. This seems kinda unfair. Another example my old rusty Galaxy S3 still has ROMs coming out for it. When I said rusty i mean it, it doesn't charge anymore the port has been oxidised. I don't know whats the real reason behind this situation but I'm kinda sure that its something about chips, systems, bootloader, Samsung got knox now I don't know I started to talk ****.
My questions may seem dumb but I have never owned a Samsung phone.
I know samsung likes their bloatware and proprietary methods. Can I avoid all the samsung bloat and a samsung account and still use the phone? Are there ROMs that give a stock android experience?
Also what are you guys seeing for SOT? Im coming from a Asus ROG 6 Pro.
Any bugs you guys are experiencing? My 6Pro is so full of bugs that has pushed me to move brands.
You don't need a custom rom, you don't even need to root it, just use universal android debloater gui from github or adb app control to remove all the bloat (both include good instructions and details about what to remove) and going through first time set up you don't need a samsung or google account.
Unless you are using an international version there is no custom ROM option. The 918U and U1 models don't have the option to OEM unlock and flash ROMs.
You can easily umbloat using the mentioned universal android debloater.
Ui downloaded the 5.0 or sth like that and updated, then it all went south.
Stayed with the 5.0 version and it works great.
As for the ROM I put Nova Launcher and it works fine
Not the same but as long as the X3 camera shoots ****ty pictures I'll leave it warranty capable
Rouvster said:
You can easily umbloat using the mentioned universal android debloater.
Ui downloaded the 5.0 or sth like that and updated, then it all went south.
Stayed with the 5.0 version and it works great.
As for the ROM I put Nova Launcher and it works fine
Not the same but as long as the X3 camera shoots ****ty pictures I'll leave it warranty capable
Click to expand...
Click to collapse
What's wrong with your x3? Mine's impeccable. Didn't hear about any other complaints whatsoever.
treahuggs said:
My questions may seem dumb but I have never owned a Samsung phone.
I know samsung likes their bloatware and proprietary methods. Can I avoid all the samsung bloat and a samsung account and still use the phone? Are there ROMs that give a stock android experience?
Also what are you guys seeing for SOT? Im coming from a Asus ROG 6 Pro.
Any bugs you guys are experiencing? My 6Pro is so full of bugs that has pushed me to move brands.
Click to expand...
Click to collapse
No bugs. Phone is super smooth and battery is amazing. About bloatware you can find everything you need in XDA thread called "Samsung Galaxy One UI - Optimization Guide".
Pungasul said:
What's wrong with your x3? Mine's impeccable. Didn't hear about any other complaints whatsoever.
Click to expand...
Click to collapse
Well, I used the "remove noise" or whatsoever option.
But for a X3 zoom I find the quality more than disappointing.
My Vivo X70Pro shots better photos.
Applied goodlock camera assistant, a bit better, and even gcam.
But quality just sucks for such a "high end" model...
Hoping on a FW fix though since with gcam its quite less worse
No issue here with 3x zoom with my S23U camera (B-version, EUX), just stock point&shoot....
Something like this ?
I'll retry with more natural light.
Maybe that's the issue.
Was pretty dark the time I took the picture
Awesome, thanks for the replies. Since there is no custom roms, do we still have unlock and root available? At bare minimum i would like to install AdAway got universal ad blocking.
treahuggs said:
Awesome, thanks for the replies. Since there is no custom roms, do we still have unlock and root available? At bare minimum i would like to install AdAway got universal ad blocking.
Click to expand...
Click to collapse
We can unlock and root. Look for the guide in this sub forum. Root will tripped knox tho, so some samsung app won't work. I would suggest using adhell to block ad
Mrxyzl said:
We can unlock and root. Look for the guide in this sub forum. Root will tripped knox tho, so some samsung app won't work. I would suggest using adhell to block ad
Click to expand...
Click to collapse
No magisk module or similar to get around this?
My biggest concern is just losing the samsung camera, I hear other cameras apks dont work well with the phone.
Rouvster said:
Well, I used the "remove noise" or whatsoever option.
But for a X3 zoom I find the quality more than disappointing.
My Vivo X70Pro shots better photos.
Applied goodlock camera assistant, a bit better, and even gcam.
But quality just sucks for such a "high end" model...
Hoping on a FW fix though since with gcam its quite less worse
Click to expand...
Click to collapse
Please try to activate night mode before switching to x3. Also in low light you need to be VERY still for the sensor and ISP to work its magic.
Moreoever, keep your lenses clean as much as possible.
These 2 photos I just shot now in a very dimly light room.
treahuggs said:
No magisk module or similar to get around this?
My biggest concern is just losing the samsung camera, I hear other cameras apks dont work well with the phone.
You will lose samsung wallet, I think. you should just use adhell for ease
Click to expand...
Click to collapse
Pungasul said:
Please try to activate night mode before switching to x3. Also in low light you need to be VERY still for the sensor and ISP to work its magic.
Moreoever, keep your lenses clean as much as possible.
These 2 photos I just shot now in a very dimly light room.
Click to expand...
Click to collapse
Thx for the info, I will give it a try.
Just wondering why someone would apply night mode while using light in their living room
But if works like this, this is what it is .
Thanks for the info