Database Users

[FIX] Low incall volume

I've fixed the low incall volume problem. BIG thanks to Arva!!! If you are experiencing low incall volume all you need to do is this:
1. go with RootExplorer (or something else) to /system/etc/firmware
2. delete default.adcb and htcleo.adcb (make sure you have mounted read/write in the folder)
3. just copy the defaut.adcb from the attached file that Arva gave
4. restart the phone (not hot restart)
and presto!! you'll have so lowder incall volume that your ears will bleed
Again.. BIG thanks to Arva!!

Just applied the fix, works nice

Found Simple Fix,
-when you recieve the incoming call accept the call turn on speaker phone and turn it of again,

good idea.. but when you change the file you won't have to deal with it every time.. it can be a bit annoing

how do you do this???? Helpppp, this is really annoing!!!

bcandara said:
Found Simple Fix,
-when you recieve the incoming call accept the call turn on speaker phone and turn it of again,
Click to expand...
Click to collapse
Okay, you told us to delete htcleo.adcb, but there is no file to replace it in the file downloaded.
Also what do I replace the deleted files with?
default.acdb
or
update.default_acdb.sh
?>??
YOU SIR, ARE NOT CLEAR AT ALL IN YOUR DIRECTIONS.
I agree. This works as well but its really annoying as hell!

How do you even get to htcleo.adcb???

@lemonspeaker you dont replace htcleo.adcb.. you just delete it. and copy default.adcb, the other file is for the builds from cedesmith.
@daica13 get to file with rootexplorer.. and it's written in the first post where the files are located.. good luck

Well I tried your / his fix and yeap it worked !
Well I tried your / his fix and yeap it worked !
you'll have so lower in-call volume that your ears will bleed!
Click to expand...
Click to collapse
Well It didn't work that great! LOL But It Def made a big difference!

i cant delete these files
what now?

Wampirate said:
i cant delete these files
what now?
Click to expand...
Click to collapse
Use Rootexplorer to do it.
You need root access. And Change the files to read / write
I Used Rootexplorer not sure what the heck I was doing !
But it worked ! In-Call IS Fixed!

Yep.. Worked for me.
Thank you.

Got a fix for the speaker volume for ringer and notification being low too?Ive been searching for weeks.

I have deleted the two mentioned files, but I can't paste the new file.
All the maps are read/write, but when I paste the standard file nothing happens.
I used Rootexplorer.
What am I doing wrong?

I can't open root explorer, it says something like "root explorer has not yet managed to get permissions from superuser..."
I can't figure out how to get around this!
Any ideas?

thatsonlyme said:
I can't open root explorer, it says something like "root explorer has not yet managed to get permissions from superuser..."
I can't figure out how to get around this!
Any ideas?
Click to expand...
Click to collapse
You don`t have a rooted phone.

FileFixer said:
You don`t have a rooted phone.
Click to expand...
Click to collapse
BusyBox says it is rooted. It also says BusyBox not found!
I also tried using SuperManager and when I delete files it does nothing!

I have notice a strange issue. Since I Have applied this fix the boot time is about 90 sec. If I restore the original file, the booot time is about 45 sec. Why this?

thank you ,nice work

Worked like a charm for me! I couldn't paste the file using Root Explorer, so I tried Super Manager, and it allowed me to copy/paste just fine.

Your Device is not compatible with this item?

Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?

x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?

kylew1212 said:
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?
Click to expand...
Click to collapse
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.

x_Jack_x said:
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.
Click to expand...
Click to collapse
Something is wrong (obviously) is this the first SD build you've used? Check to see if theirs a newer version and try it because their could have been a bug.. Honestly I would recommend nand install but I understand not everyone wants that. I would have to at least try reinstalling it and possibly a different rom...
Hope that helped some!
Sent from my NexusHD2 using xda premium

Fix Market problem: AmeriCanAndroid HD2 GB2.3.7 CM7.1
x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)

I run NAND builds and this is something that I have noticed. For example an app would work just fine with typhoon CM7, but when running Hyperdroid CM7 it would give me the compatibility error like you're getting. My guess is it has something to with how the ROM is cooked, but I could be wrong; I'm still kinda NEWB

Sysifos said:
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)
Click to expand...
Click to collapse
I have tried this already.When I try to save the build.prop it has an error, and says unable to save.But when I reboot and go back to build.prop its changed to 240.. go figure.I also tried the market thing by clearing cache and force stop.Also tried ROM manager and fixing the permissions.Still nodda.I guess I can try a diff build.Any suggestions? Wanna do it the SD way.Im kinda new to the phone stuff.So easier is better for me atm.

First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App

Sysifos said:
First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thats probally my issue, the other tut like this i used didnt have the change permission thing.How do I change permission on such file?

After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.

When I long click build.prop.. theres no option to change permissions.

x_Jack_x said:
When I long click build.prop.. theres no option to change permissions.
Click to expand...
Click to collapse
What file manager do u use?
I use 'File Expert' as file manager and by long press on the file, a pop-up menu appears. It has 'Permissions' at the mid-lower part of the menu. Open it and just enable all-you will fix permissioms at the end..
I don't know how other file managers handle this, but I'm sure they do it somehow!
Sent from my HTC HD2 using XDA App

matoflash said:
After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.
Click to expand...
Click to collapse
I never changed model infos and works properly.. Can be done on SD builds though.
Sent from my HTC HD2 using XDA App

i use es file explorer.

x_Jack_x said:
i use es file explorer.
Click to expand...
Click to collapse
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.

matoflash said:
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.
Click to expand...
Click to collapse
On my es explorer, there is no setting that i can find.

x_Jack_x said:
On my es explorer, there is no setting that i can find.
Click to expand...
Click to collapse
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...

matoflash said:
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...
Click to expand...
Click to collapse
Well, it let me save the build.prop now.. did everything else. Still same error.

x_Jack_x said:
Well, it let me save the build.prop now.. did everything else. Still same error.
Click to expand...
Click to collapse
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.

matoflash said:
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.
Click to expand...
Click to collapse
That would be cool except I havd an HD2 not vision.And the board is leo not vision.Im not a phone DEV person, but somehow that doesnt look correct to me.If I changed my build.prop for htc hd leo to htc vision, it might corrupt my build.Maybe Im wrong, but I got this build out of the HTC HD2 leo android forums.

[HOWTO] Enable Auto Rotation for Lock Screen & Launcher

This is a quick walk through for editing the build.prop to allow lock screen and launcher rotation.​
I got tired of looking at my phone sideways while it was propped up landscape wise, in my case.
1. Locate "build.prop" in /system using your favorite file explore
2. Open it up and at the bottom add the lines
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
3. Save your edit and reboot.
Lockscreen rotation still not working for you???
A few users have reported that adding a blank line between the two, fixes this issue.
Once the phone reboots your lockscreen and Google Now launcher will rotate with the orientation of the device just like other apps do.
To undo this, simply remove the lines we added
:good:
Update: 11/10/2015
enigma9o7 Has figured out how to get this to stick even after an update! Head over to his post for the walkthrough and install guide!! Remember to give them a "thanks" for sharing the work!

Awesome I been wondering how to get this done.

Nice tip. I've always just used an app called Ultimate Rotation Control. Seems to work just fine on the Nexus 6. A quick build.prop tweak removes the need for a separate app for it, though. I might get around to trying this...eventually

can someone make a flash able zip for this please ?
thanks in advance

Anybody know how one would do this with adb?
N6

I used an app for quite some time but i disliked it running in the background.
Im not able to make a flashable zip. Maybe in time I will see if i can.
For adb, youd have to pull the build.prop, edit on computer then push it back. The instructions to do that are unclear to me

mrfuzzie23 said:
can someone make a flash able zip for this please ?
thanks in advance
Click to expand...
Click to collapse
You can install Nova Launcher and toggle the setting in there, or use the ultimate rotation app someone else mentioned.

Thx

If you set the DPI to 384 or less, this happens by default.

pavankp said:
If you set the DPI to 384 or less, this happens by default.
Click to expand...
Click to collapse
Thats good to know! Not surprising, the device is most likely changed to "tablet size" to the system. And they have full rotation.

Works great, thanks! (AT&T Nexus 6)

Would not work for me I get error saving

techrider6262 said:
Would not work for me I get error saving
Click to expand...
Click to collapse
Thats not good. What error are you getting?

eqbirvin said:
Thats not good. What error are you getting?
Click to expand...
Click to collapse
It just said error can't save and I tried a couple different time

techrider6262 said:
It just said error can't save and I tried a couple different time
Click to expand...
Click to collapse
gotcha. You are rooted, correct? and if so what file manager are you using to locate the build.prop?

es file explorer and i'm rooted.

in ES file explorer when you grant it root permissions, click on root, then mount R/W, make sure "/system" is RW instead of RO. (sorry if you already know this, im just trying to save time and figure your error out haha)

Thanks I got it working.:good:

Glad to hear it!

to each their own, I like being able to get OTAs so I'll stick with Ultimate Rotation Control

Qualcomm assertive display plugin for lg g3

Flash the zip file from twrp....it will add few lines in build.prop and also add a file to etc folder.
I found it at nexus6 forum...so share it with you...one lg g3 user confirm it works.
use adaptive brightness to get maximum potential battery save!
Lot of people tried this mod and told that adaptive brightness works better and faster with assertive display, also in direct sunlight display is more visible.
****Don't forget to hit thanks if it's work for you..****

Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?

massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder

massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
It will good for use adaptive brightness to get maximum potential battery save! Also adaptive brightness works better

Hello.. the ad_calib file. After moving it to etc folder any need to change permissions?

Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?

princedede said:
Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?
Click to expand...
Click to collapse
Yes you have to give proper permission....

anyone tried? and pls axplain installation, do we need to just flash both?

imamalemdar said:
anyone tried? and pls axplain installation, do we need to just flash both?
Click to expand...
Click to collapse
Just flash it

Anik49 said:
Just flash it
Click to expand...
Click to collapse
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...

imamalemdar said:
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...
Click to expand...
Click to collapse
Actually when i used it i found more vibrant screen....currently i am using fulmics 5.3 which also use assertive display plugin find both same...

Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.

gonk24 said:
Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.
Click to expand...
Click to collapse
Try it .....give us your result

Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions

kevinkehoe18 said:
Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions
Click to expand...
Click to collapse
I always thought it was rw-r-r

Anik49 said:
Try it .....give us your result
Click to expand...
Click to collapse
It's all flashed for now so we'll see. I'm already reminded of how I find auto brightness to be annoying. It's too dark when inside. I'm outside a lot during the day and keep brightness set at 70%. Inside at night I'll drop it to around 45%. Using auto set to 70% and being inside, the screen dims to what would be around 25% brightness. Too low, and I shouldn't have to set it above what's bright enough at the high end on manual.

So flash file no 1, wipe dalvik and cache, extract and place file no 2 in /etc?
And which permissions do I need to set?

Anik49 said:
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder
Click to expand...
Click to collapse
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...

Panther.zr14 said:
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...
Click to expand...
Click to collapse
you need root to add this line in your build.prop. have you rooted your phone?

Anik49 said:
you need root to add this line in your build.prop. have you rooted your phone?
Click to expand...
Click to collapse
Yes..but temporary with kingroot...

Camera pictures allways complette Green!

Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html

Did you change your DPI or Font-Size? Or did you mess with any kind of build.prop editor?

Do you have night mode one?

I didnt change anything. Thats why i Was so confussed about it.
just flashed the full 4.5.10 zip. Camera is now working again.

Dan3ll1 said:
Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html
Click to expand...
Click to collapse
I have seen this before on the HTC 10 the problem was actually because users had flashed a new ROM from a different base but had not updated their firmware.
See if this the case for yourself.
If your firmware doesn't match the base you're on then update it.

I dig this thread out because I have the same error again but this time i know why. Allways when i edit the build.prop and Reboot i cant take pictures because they are green. This time i tried to set the soundcontroll to 50 clicks for better adjustment. No big deal and no big change. And last time i tried to Set the Screen Resolution to 4k for YouTube vidz.
Question is why is the cam allways broke

Are you taking a picture of a green sheet?

worldsoutro said:
Are you taking a picture of a green sheet?
Click to expand...
Click to collapse
Damn bruh, that joke. U are one of the funny few?
But no i just take a Green sheet of a green picture....

why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.

OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works

OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
Nope, did not work. Still green when i edit the build.prop

Dan3ll1 said:
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works
Click to expand...
Click to collapse
U edited it? If you did youre doing it wrong. Just change permissions

OcazPrime said:
U edited it? If you did youre doing it wrong. Just change permissions
Click to expand...
Click to collapse
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic

Dan3ll1 said:
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic
Click to expand...
Click to collapse
What room are you on?

OcazPrime said:
What room are you on?
Click to expand...
Click to collapse
I am on OOS 4.5.13 with Franco Kernel

Dan3ll1 said:
I am on OOS 4.5.13 with Franco Kernel
Click to expand...
Click to collapse
Maybe just use the google camera. Its pretty good.

OcazPrime said:
Maybe just use the google camera. Its pretty good.
Click to expand...
Click to collapse
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps

Dan3ll1 said:
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps
Click to expand...
Click to collapse
Yikes. Maybe try clean flashing. Or going into twrp and trying the option Fix contents under the advanced tab.

Had the same problem.
Setting the build.prop permissions to 644 saved me.