Database Develop

[Kernel] CM7 Kernel 2.3.4 (Voodoo Sound v8, Color, LEDNotify, OC/UV) [05/04/2011]

CyanogenMod 7 Voodoo kernel.
Sound, Color, Tinyrcu, Nodebug, and more!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before going any further, please know this is for CM7 Gingberbread 2.3.3 ONLY.
Note: There is no conversion process, CM7 already uses proper file systems everywhere by default, so, it's not needed.​
Disclaimer:
From bilboa1: This kernel is provided as-is without any warranty. I'm not here to provide support, etc. Although I might when I'm able to, but don't count on it. If your phone explodes, it's your problem.Updates are not guaranteed as well.
Credits:
Credit for this kernel goes to bilboa1, I'm just posting it here for ease-of-access.
Thanks to Supercurio for making those great enhancement patches and to the Teamhacksung/CMSGS/CM7 contributors for the CM project.
- http://forum.xda-developers.com/showthread.php?t=979206
- http://project-voodoo.org/
- http://forum.cyanogenmod.com/forum/8...erimental-mod/
Main features:
Voodoo Sound v8. - Need I say more?
Voodoo Color. - Again, you should know this by now.
LEDNotification. - Not "BLN" - No app required - Use CM quiet hours for scheduling.
Overclocking. - 1.3Ghz max.
UnderVolting.
Extra governors. - Smartass, Interactive.
Various tweaks. - JPX screen timings.
Sometimes testing stuff. - Stuff from teamhacksung before it goes into their stable upstream.
Changelog:
Fixed battery info/display (Upstream) (NEW)
Some fixes for new recovery (NEW)
Upstream sync. (NEW)
Some fixes for new recovery. (NEW)
Test of new scripts.
Fixed said new scripts since test failed.
Supports GB 2.3.4 (Upstream)
Reviewed some code.
Removed governors: ondemand is better in their current state anyway. (NEW)
Allocate more memory to FIMC0 / fixes googles goggles FC. (NEW)
Upstream sync.
Requires latest CM7 nightly for compass, etc.
Supports bml_over_mtd at flash time.
Voodoo Sound v8.
Some touch-key tweaks.
Fixed touch key inactive on boot.
Added usb dock/audio/etc patches. (Testing - xcaliburinhand.)
Tweaked default haptic feedback intensity. (Slightly softer.)
Changes in LED handling. (Possibly fixes most remaining issues.)
You need this to control the LEDs CMParts see here to install properly (Doesn't install like a regular apk, the reason is its not really an app, it's part of CM7 with modified setting panel for LEDs)
LED on on resume has been disabled for now (keyboard woes - I think.)
Touch key: Enforce recovery routine during r/w failures (Fixes: Touch keys flash and stay off when missing a call - Possibly other weird situations.)
LED stay on when screen off as long as notifications are not deleted. (Due to popular request.)
Fixed liblight for quiet hours/LED issue.
Touch keys light up at resume for a short time. (Like Samsung ROMs)
LED notification respects CyanogenMod's 'Quiet hours' (Settings -> Cyanogen -> Sound -> Quiet hours) Setting LEDs to dim during quiet hours will disable led notifcations during those hours (So it's like BLN schedule except its using the CM feature.) - Thanks for that suggestion.
Fixed keys light time out. (I was being dumb with calls during interrupts, sorry.)
Coolya's battery experiemental tests: allow charging at higher temperature. (Like JPX), changed adc.
Added CONFIG_MODVERSIONS for Voodoo module support. (Future market app.)
Headphone fix. (Upstream issue - Means no play/pause/mic buttons, but at least you can listen to music like before.)
Added smartass - Currently doesn't go under 400mhz. (Not default and just testing.)
Stable OC at 1.3ghz, probably! (At least, 'more stable.' Report if you still crash.)
Fixed voltage table display. (No more '?' in Voltage App.)
Voodoo sound patch v6.
Higher refresh rate and timings, taken from JPX (thx morfic) - Results in 10fps boost in games and smoother scrolling elsewhere.
More info on changelog here; https://github.com/kangsterizer/android_kernel_samsung/commits/android-samsung-2.6.35
Download: http://kang.project-voodoo.org/f/CM7/Vibrant/CM7_Vibrant_kernel_kang_20110504_r10_update.zip (05/04/2011)
FAQ:
Q: Has anyone tested this? Can you confirm it's working?
A: Yes, I can. It's running great so far!
Q: Does this have BLN support?
A: It has it's own built-in LEDNotification.
Q: Can I flash over Eugene's kernel?
A: Yes, you can.
LED Support FAQ here: http://pastebin.com/ySBSaw4u
Extras:
Netfilter/iptables fix: http://kang.project-voodoo.org/f/iptables-cm7-kang.zip
CPU Spy: Android Market Link
(It graphically shows the time the CPU spends in each state, as well as the current kernel info. A pretty simple app.)

Flashed and running smooth.

Tested. Color is amazing. Thanks so much.
Sent from my SGH-T959 using XDA App

Does no debug finally mean a better battery life?
Sent from Bionix 1.3 high on Voodoo

We need Voodoo lagfix (ext4) .....

adyscorpius said:
Does no debug finally mean a better battery life?
Sent from Bionix 1.3 high on Voodoo
Click to expand...
Click to collapse
why does debug mode take away extra battery?

Does this has BLN?

iwapu said:
Does this has BLN?
Click to expand...
Click to collapse
It does not.
supercurio posted; If neldar (poor student) has enough resources to build a Nexus S (i doubt he would rewrote it only for CM)

Confirmed, this kernel is very quick. Voodoo color completely fixes the warm color issue. Great work.

Thank you for sharing looks great!

wow
This really worked out. Thank you dude or Dudette? lol

shownuff said:
This really worked out. Thank you dude or Dudette? lol
Click to expand...
Click to collapse
***nvr mind***

Running smooth so far...hopefully battery is hella better (cannot get much worse than it already was).

Flashed it nothing exploded so I guess were good lets see how the batt is....i was getting 10hrs with heavy use wifi always on
Sent from my SGH-T959 using Tapatalk

dxtrlabs said:
Flashed it nothing exploded so I guess were good lets see how the batt is....i was getting 10hrs with heavy use wifi always on
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
LUCKY....I got maybe 8 with marginal use.

try to recondition battery it work for me I was getting 5hrs before. What I did was charge up til full batt the drain wiped charged to 100 or in our case 95 hehe and draind and wiped again and that got batt better. Or maybe just luck.
Sent from my SGH-T959 using Tapatalk

I'll try it again

Fantastic kernel!!
Sent from my SGH-T959 using XDA Premium App

apollo15rover said:
Fantastic kernel!!
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
THIS!!!!!!!

dxtrlabs said:
try to recondition battery it work for me I was getting 5hrs before. What I did was charge up til full batt the drain wiped charged to 100 or in our case 95 hehe and draind and wiped again and that got batt better. Or maybe just luck.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
can you explain it with more clarity? my battery only last 4-5 hours :S

[Q] RAM Manager app to prevent redraws

Hi,
This is sort of a continuation to a thread I made a few weeks ago, which was about launcher redraw problems I had with every single launcher I tried. I'm on FroyoPro v2.5, and on the recommendation of a fellow board member (thanks, Dagger) I'm running Nemus launcher. Basically, whenever i install or uninstall an app, my launcher prompts me to either force close or wait, and when I choose wait, it becomes slow for the next five or ten seconds and then returns to normal. It was worse before, but ticking "Lock launcher into memory" solved the most of the problems. Seems that the lack of RAM was actually the source of the problem.
I was recommended the SuperCharger script. However, I needed a newer version of BusyBox to install it, so I scrapped the idea for the fear I might brick the phone.
I investigated further for a solution, and found the app called RAM Manager (free version), which was made by a developer here at XDA. I installed it, set the "balanced" profile, and it actually fixed the problem. No redraws so far, and I even think the launcher is a tad smoother than before.
Has anyone tried this app? Is it a good thing to have or would you rather recommend I try something else? Are there any apps like it that are perhaps more efficient? It seems that all I need is better RAM management for the issue to be solved.
EDIT: Forgot to add the link to the XDA thread: http://forum.xda-developers.com/showthread.php?t=1305060
So far so good. Battery seems more or less unaffected. No negative effects on AnTuTu and Quadrant benchmark scores. Played five games in total, seemingly no negative or positive effects. What are your feedbacks on this?

The ram manager is actually a substitute to the supercharger script.
I personally recommend it if you are having ram issues.
Also you may freeze or uninstall the useless apps(mainly system apps) so as to free more memory.

Hm, now two days into the testing I've noticed that launcher redraws still do happen on occasion. However, it also seems that this app does the job well the moment it started and several minutes after running, but its effectiveness sort of degrades afterwards. Two days after I don't even notice any difference than before. What's the reason behind this? Is it fully compatible with CM ROMs?
There's only one more thing that I would also like to try before dropping this whole issue completely. Obviously it's a RAM thing, because running the backup I made a day after flashing FroyoPro seems to have no problems until I choke it with more apps. Then the same thing starts occurring. Not much can be done with the limited RAM X8 has.
However, what do you think about tweaking the VM heap size and MinFree values in CM settings? Is it possible to alleviate the problem with some tweaks from there?

Ahhhhhhh
V6 supercharger is just a ....beep.....
Before using that my antutu benchmark was 4005 - after installing script my score had a freefall @ ~3500~ ( lost 500 scores)
I'm using ram manager pro too, I can say that its awesome for setting to -multitasking option ( 3 apps at the same time)
HIGHLY RECOMMENDED
Sent from my E15i using Tapatalk 2

jay-z-s said:
Ahhhhhhh
V6 supercharger is just a ....beep.....
Before using that my antutu benchmark was 4005 - after installing script my score had a freefall @ ~3500~ ( lost 500 scores)
I'm using ram manager pro too, I can say that its awesome for setting to -multitasking option ( 3 apps at the same time)
HIGHLY RECOMMENDED
Sent from my E15i using Tapatalk 2
Click to expand...
Click to collapse
Yes, and I might actually try buying this app. Even though it didn't resolve the redraw issue completely, the general feeling of better performance seems to linger. I'm going to keep running the free version for a few more days and see what would happen

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There you go...
Download "system tuner pro" or any similar apps from market.
Press "tweak " button
Set "hidden apps" option to maximum value (now its 24mb but u can raise it to 32 or higher )
That's it...
*launcher pro OR adw launcher are too light and don't need to increase memory (I use adw with Widgets without reddraws

Use thishttp://forum.xda-developers.com/showthread.php?t=1987032
It works for me.
Just install the apk and tick both yes and run at boot.
sent from my phone using hands and brain...

[Q] AHD custom kernel and settings

Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL

[] AL [] said:
Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1893050

Ok thanks for the link.
I wasn't searching at the right place and on the wrong device forum...
So in an attempt to make this thread useful, I'd ask again: anybody wants to share their experience with that kernel on AHD?
I mean other than getting a phone that can basically now running up to 2GHz and down to 96 MHz, what did you get from it?
- How (and how much) undervolting did you do?;
- Any noticeable and verifiable battery saving doing so?;
- Any before/after benchmark results to share?
- any observations, bugs or just general opinion on the subject?
Personally, I've noticed once or twice that the phone had a hard time waking up when I used 144MHz (forgot the exact value) as min cpu frequency (no undervolting). The screen would not turn on with either volume rocker or power button...it only did after a lot of insisting... And that was just within a couple hours of testing.
I've since reverted to CM11 kernel since I was eager to find out if a semi-dirty (no stock rom reflashing first) nand backup restore would switch the kernel back. And it did, but then I've also re-installed CM11-M8 for other reason/issues... (that too brought back CM kernel - at least that's what the "about phone" is giving).
Anyhow, the debate is open on the usefulness of that custom kernel. If no one dare to pitch in here, I'll just ask a moderator to delete the thread...
But I'm still eager to find out about how to undervolt as I always did on my Defy.
Cheers
/A

I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.

quasihellfish said:
I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.
Click to expand...
Click to collapse
do you mean may 25?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sliker90 said:
do you mean may 25?
Click to expand...
Click to collapse
No. "CLICK TO SHOW CONTENT", then download the latest version (May 23) that doesn't use SaberMod. Only reason I was using that was because arrrghhh mentioned that SaberMod thing was experimental and may have issues. So I just chose the safe option.

ok thank you

sliker90 said:
ok thank you
Click to expand...
Click to collapse
Since you're a new xda member, I'll remind you that there is a button specially made to thank people... Look at the bottom left of the post useful to you...
As far as the undervolting goes, I found that the free app called "Trickster Mod" can do voltage changes. So I've done a bit more testing with the May 23rd anykernel and my results weren't that great....
First, I went too aggressively and try to lower the voltage by 150mV for every cpu frequency and that made the phone reboot as soon I applied it. I mention this because the lesson here is to
*** NEVER SET THE "apply settings on boot" OPTION UNTIL YOU ARE ABSOLUTELY SURE THAT YOUR NUMBERS WORK FINE. ***
Not doing so might make your phone unbootable and you might not even be able to boot to recovery/bootloader mode to revert kernel/settings....
Ok, that being said and since I'm after battery saving while the phone is in use*, I then went ahead and lowered by a more reasonable 50mV for each frequency (the app let's us move by 25mV steps). That 'worked' fine and I've experienced no sudden reboot. BUT, after some time (30 minutes), I've noticed some slowdowns and I've also had issues with an app that stopped creating video thumbnails. So all in all, that called for the end of my testing and I restore my CM11-M8 nandroid as I'm not going to live with such drawbacks for some slight (still yet to be proven) battery improvements.
So no custom kernel for me afterall.
.... Should this thread be deleted???
You guys tell me.
Cheers
/AL
- - -
*: hence I see no point of lowering the minimum cpu frequency: my phone does not take excessive power when on iddle, it deepsleeps fine and I use airplane mode at night..
*': some have argued that increasing the max cpu frequency allows the phone to complete tasks faster and return to a low power state sooner resulting in a lower overall battery use. I have my doubts on this and I'm pretty sure that it depends on what kind of task the phone is mainly doing. Anyhow, this is not something worth testing at this time... My AHD does its job just fine at the stock max cpu f.

[Kernel] [Virgin, Sprint, Boost] RevKernel [WIP] [Write Protect Removed]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CurbThePain's RevKernel - Desire 510 Ed.
"A Brutal Kernel"
Disclaimer
I am NOT responsible for anything that happens to you, your phone, or anything as a result of flashing this kernel. It is of your choice to flash said kernel and or proceed to root your phone. So dont blame me if your phone is dead, it is YOUR fault.
Features:
Code:
F2FS Filesystem support
Write Protect Removed
Less aggressive interactive gov
Overclocked Ram to 566MHz
Overclocked Gpu to 477Mhz (will not be visible) test this and tell me if you get any performance jumps in gpu intensive games.
To do:
Add better touch drivers (maybe)
Add ram space and trim already used ram.
Add any optimizations possible.
FYI's
Code:
Requests,
You guys should request any feature you want added! :D I'll get around to
trying to add all of it!
Give me time.
I am a very busy person, I have school and a almost full time job. I'll work as
hard as I possibly can on all of this but you have to be patient.
I am sorry if I say something will be uploaded and its not. I don't have a way
to do builds and its hard to work on ROM's without constant access to a pc.
I will try to update the OP if plans change.
Fixed (Cameras, WiFi, any lags or old bugs)
XDA:DevDB Information
RevKernel, Kernel for the HTC Desire 510
Contributors
CurbThePain, Rbheromax
Version Information
Status: Beta
Created 2014-12-09
Last Updated 2015-3-07​

How is this different than your other kernel other than added Boost Mobile support?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969

Kolma said:
How is this different than your other kernel other than added Boost Mobile support?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Click to expand...
Click to collapse
Look at the tags. Im working on adding dt2w and the smartass gov. cpuboost (better power to performance managment) wheatly and intelleactive are already working. me and rbheromax are trying to get this all sorted out. His current builds have broken wifi. Mine had wifi at first and i didnt modify any wifi drivers so it SHOULD in theory work.
All in all at the end of the day (not today) the kernel will end up featuring dt2w, 3 new govs, overclock, maybe voltage control, and support lots and lots of file systems. Oh cant forget write protect is removed lol.

Reserved
Sent from my 0PCV1 using XDA Free mobile app

Faux sound support?

Hmmm feature request...well fauxsound, row scheduler(others), I think this kernel can be throttled up to 1.5 or 1.8 ghz per core, but for battery saving, 1.5, maybe seeing if you can update some of the drivers(personally when I hit them c++ books(c) I would modify), screen configurations if possible like faux, but I do not think HTC allows developers to mess with the display driver, and possibly extfat4 partitioning.

Shryvone21 said:
Hmmm feature request...well fauxsound, row scheduler(others), I think this kernel can be throttled up to 1.5 or 1.8 ghz per core, but for battery saving, 1.5, maybe seeing if you can update some of the drivers(personally when I hit them c++ books(c) I would modify), screen configurations if possible like faux, but I do not think HTC allows developers to mess with the display driver, and possibly extfat4 partitioning.
Click to expand...
Click to collapse
As for the kernel level cpu oc at the moment its not possible. Every attempt has resulted in a non booting kernel. For now my development will be slow until i can get my hands on a laptop. Sorry guys. Ill update my kernel and rom in unison from here on out (usually) but its gonna be a while. Sorry again everyone. Thanks for the suggestions though I will get to do some tinkering this saturday and next saturday. Ill report back then.

New image uploaded!!! (It is in the downloads section) If you cant download it heres another link:
http://www.mediafire.com/download/5d1iwc4brvey8z0/boot100.img

@ anyone running this please post me the output of /sys/kernel/debug/msm_cpufreq

Where's the download link

Will this work for Boost Mobile?

Flashing this kernel gets rid of all Roaming related options from the phone, before I used to see the option to enable roaming, plus enable/disable roaming guards and enable roaming for domestic and internationally, all that is gone after flashing this kernel. Since I have a roaming agreement with Sprint and I travel alot, I can't do without the ability to roam, therefore I restored my /boot nandroid backup and that brought back all roaming related options.
Question: Why did the OP remove roaming from this kernel? Many people NEED this, Or is there something that I was supposed to do in order to bring it back?

Possible Solution for low In-Call volume Nexus 6

I had a problem that the In-Call volume was way to low on the Nexus 6 and after a firm search on different site's I found out that a possible solution was no a near distance future.
Hack.... even Google itself has given it a small-priority - Issue 80817: Nexus 6 - Low in-call speaker volume
So I began to experiment with volume apps in the Google Play store and found a solution which helped me to raise the In-Call volume on calls significantly! - https://play.google.com/store/apps/details?id=com.firestorm.vc
Just install and make sure that you enable the In-Call Volume in the settings and set it on maximum value. Save settings and go....... Descend volume during a call.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No need to go Pro - it's a set and forget app.
Hope it will fix the problem for a lot of users until Google will fix this...... Thanks button is on the right.

NoLips said:
I had a problem that the In-Call volume was way to low on the Nexus 6 and after a firm search on different site's I found out that a possible solution was no a near distance future.
Hack.... even Google itself has given it a small-priority - Issue 80817:Nexus 6 - Low in-call speaker volume
So I began to experiment with volume apps in the Google Play store and found a solution which helped me to raise the In-Call volume on calls significantly! - https://play.google.com/store/apps/details?id=com.firestorm.vc
Just install and make sure that you enable the In-Call Volume in the settings and set it on maximum value. Save settings and go....... Descend volume during a call.
No need to go Pro - it's a set and forget app.
Hope it will fix the problem for a lot of users until Google will fix this...... Thanks button is on the right.
Click to expand...
Click to collapse
Difficult, to really hear if it goes up, thought it did, seemed to increase and slightly distort, but could be placebo as I so wanted it to.
Ultimately I would rather adjust some system files rather than have another application, especially an ugly one. Sorry and thanks.
Sent from my Nexus 6 using Tapatalk

ben_pyett said:
Difficult, to really hear if it goes up, thought it did, seemed to increase and slightly distort, but could be placebo as I so wanted it to.
Ultimately I would rather adjust some system files rather than have another application, especially an ugly one. Sorry and thanks.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
For me the volume was definitely increasing without distortion, sorry to hear that it wasn't working for you.
Yes I know, I also search the solution into editing some system files. But no luck so far.
I still hope that franciscofranco can find a solution for this and make it a kernel option to adjust.
On this moment I also experiment with Tasker and the In-Call options to achieve more loudness, we shall see. But for now it's better then it was, at least workable (for me).

NoLips said:
For me the volume was definitely increasing without distortion, sorry to hear that it wasn't working for you.
Yes I know, I also search the solution into editing some system files. But no luck so far.
I still hope that franciscofranco can find a solution for this and make it a kernel option to adjust.
On this moment I also experiment with Tasker and the In-Call options to achieve more loudness, we shall see. But for now it's better then it was, at least workable.
Click to expand...
Click to collapse
In which case I'll give it another try and leave it installed for a few days, turned to maximum, so that I can take a few calls and see if I struggle to hear the caller as I normally do.
Unfortunately Franco said there was nothing he could do when asked.
Sent from my Nexus 6 using Tapatalk

ben_pyett said:
In which case I'll give it another try and leave it installed for a few days, turned to maximum, so that I can take a few calls and see if I struggle to hear the caller as I normally do.
Unfortunately Franco said there was nothing he could do when asked.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Did you save the settings and did reboot? I don't remember that I did - but you can try. And I searched Franco's topic where he's stating that, but all I could find was that he wasn't suffering from a low In-Call volume problem.
I didn't find a post where he told that it wasn't possible. Can you give a link?

NoLips said:
Did you save the settings and did reboot? I don't remember that I did - but you can try. And I searched Franco's topic where he's stating that, but all I could find was that he wasn't suffering from a low In-Call volume problem.
I didn't find a post where he told that it wasn't possible. Can you give a link?
Click to expand...
Click to collapse
I did set, but don't believe reboot needed
Here is Franco's comment you're right he didn't say it wasn't possible http://forum.xda-developers.com/showthread.php?p=60214759 although it's been raised a couple of times in thread and he's never given us any options.
Sent from my Nexus 6 using Tapatalk