yashsingh1/xdaforums huggingface dataset:
[Other Tools & General Discussion] SOX404guru:
hope to create an app that runs in the background and can be activated using the wi-fi antenna (or cellular but not blue tooth antenna). Can it be done by any of the following methods:

1) Via a predetermined specific frequency,

2) Via a predetermined signal within a frequency,

3) Via alternating signals or frequencies (perhaps by scaling up or down even if a specific frequency can't be recognized),

4) Via on/off signals as with Morris Code,

5) Via alternating signal strength in a specific pattern, or 6) Via any other conceivable method.

Thank you in advance for your answers or suggestions.
[Other Tools & General Discussion] naklar:
Why not use a specific SSID to activate the app? It sounds like that might be an easier option. If you decide to follow this approach, this link might help you.
[G2 Android Development (D802)] Reginald476:
Official Builds of LiquidSmooth​

LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.

Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!

While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.

We ask that you do your part to know your device and know how to recover from problems before you flash!

Liquid Members:

Liquid0624

Deadman96385

jsnweitzel

Somber73

TheBr0ken

Cdub50

Features:

Linaro 4.8 GCC Toolchain
O3 Strict-Aliasing & ISO C++11 Mode
ARM Optimized String Handling Routines
Linaro and Code Aurora Optimaztions
Slim's DPI on the fly
Custom animation controls
TRDS 3.0 (Liquid Blackout in settings)
Active Display
Slim's QuickSettings
Ram Bar
T-Mobile Theme Engine
Privacy Guard
Built in SuperUser
Working WiFi Tethering
Cell Broadcasts
Slim's Configurable Power Menu
Slim's Configurable Nav Bar
Slim's Recents
Gamma Configuration support
Custom animation controls (Listview)
LockScreen Notifications
And way more than this...

Build Change Log:

**3/31**
Switched to IllusionRoms kernel (Omni base)
Switched to SaberMod 4.7 Toolchain for the kernel
Removed AOSB Recents
Stock Recents are default now (option of Slim's or OmniSwitch)
Removed Color Statusbar as it was buggy

**3/17**
Status Bar Colors (Settings > Interface > AppBar)
Keyboard Animation's (Settings > Display > IME Animations)
Custom Scrolling Values (Settings > Display > Scrolling Modifiers)
Battery Bar (Settings > StatusBar > Battery Icon)
App Side Bar (Settings > Interface > AppBar)
Performance Control Replaced with Kernel Tweaker
Starting with 3/8 builds there will be limited CWM support you can flash updates using it as long as you do do use the wipe data action in the app thanks Steve Spencer
When a notification was clicked in active display on some device SystemUI would FC, fixed by Jason Weitzel
Gesture Anywhere (Details later in the post)
Active Display cleaned up and features merged in from Omni (Details here http://goo.gl/9eNhQ8)
Internal Memory QS Tile
Bug Fixes:
App Settings do not launch twice on long press in slim recents
3rd Party app support added to trigger recents
Keyboard does not close when recents is opened
SlimRecents Multiuser Compatible
Add Long press menu to SlimRecents, it includes app info, Playstore link, Amazon appstore.
FC on Pinch fixed
Make Slim Recents follow Google Design standards
Smooth none holo-spinners
Smart Pulldown added to LiquidActions
Recents added to LiquidActions

Source Code:

[url="http://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
[url="https://github.com/IllusionRom/android_kernel_lge_msm8974"]IllusionRom's Kernel[/URL]

Downloads:

[url=" http://goo.gl/bDdAiC "]ROM Download[/URL]
[url=" http://xdaforums.com/google-nexus-5/themes-apps/gapps-t2012857 "]BaNkS GApps Download[/URL]

Screenshots:

​

Please Support Liquid by Donating HERE​
[G2 Android Development (D802)] Reginald476:
Know Issues - please do not post about bugs that you see on this list:

- Kernel Over Volt of +25-50 (may cause your device to run hot)

- Font Size picker does not work

- LCD Density force closes settings once you change the density and click the home or back buttons.

- Slim Pie needs a reboot before the trigger areas work

- There is no way to activate multi-window

- There is no way to disable Nav bar and pie currently

- OTA App is still in the testing phase, so it will be buggy so do not use it.

If you see something not in this list, let me know below. :cyclops:

New Features:

Custom Progress Bar.

LG apps known to work:

RieGo's LG QuickRemote v7

My personal settings:

System DPI at 400

Navigation Height at 36

Action Launcher Pro

Kernel settings:

TCP Congestion Control: westwood

I/O Scheduler: noop

CPU Governor: ondemand

MPU Voltages: -25 to all

CPU Frequency: Max 2265600
[G2 Android Development (D802)] Reginald476:
I do not have this device so I have not tested this build, there is a chance that you will get sent to fastboot, if you are not comfortable getting into recovery manually please do not try this until someone has been able to confirm. If it does not boot, I have a way to fix the build.

Please download a kernel just in case, this will allow you to boot. If this happens please let me know and I will fix it and re-upload.

Thanks!
[G2 Android Development (D802)] donoli74:
Booted just fine,no problem.:thumbup:
[G2 Android Development (D802)] Reginald476:
Thank you for taking the time to test and respond!
[G2 Android Development (D802)] snoopcool:
Booted fine ,fastest smoothest Rom ever on g2

Edit: after flashig other kernel i lost root

does someone now a solution..

Edit2:flashed root via recovery now i lost knock on lol..
[G2 Android Development (D802)] waleedshiekh:
Finally I can feel g2 on an aosp rom. Used it on n4 in past, loving it on G2. Thanks a lot dev. Please carry on making it better.
[G2 Android Development (D802)] ahmed534:
I like this ROM rly ! but got some random reboots :(
[G2 Android Development (D802)] Reginald476:
I am doing a build with the Furnace kernel, I want to see if that works better. Plus the kernel is not Over Volted so it should run cooler.

You can test this by flashing Furnace and see if it fixes your SoDs.
[G2 Android Development (D802)] crzykiller:
Will there be D803 support? All it needs is a different kernel. Is there a way to disable the "get prop d802" when flashing so we can flash this on the D803?
[G2 Android Development (D802)] schukje:
Liquid is an awesome rom but like all aosp roms sound is very low if you compare to stock based g2 roms. I use all kinds of mods to increase sound but not as good as stock unfortunately. This rom is awesome for the rest of the rom and one of the best aosp roms around. Hope they gonna pump up the volume in the future.

grtz from crazy bastard from Holland on my G2
[G2 Android Development (D802)] Reginald476:
Yeah, that should be fairly easy, I am getting ready to test a new build (for the vs980) once that is done and I have the same results I am seeing I will start up new builds.
[G2 Android Development (D802)] Dirtyzecrets:
I have used this rom on several devices, nice to see i on G2 also :)
[G2 Android Development (D802)] sspoko:
Guys someone can tell me why on every AOSP Rom I have low Wi Fi speed? On stock I've got like 2-4 time faster transfer, for example near router on stock i've got 50mb on Liquid i've got 25mb. In my room 10m from router on stock I have like 8mb transfer and on aosp 2-3mb. I miss AOSP Roms soooooo much. Can someone help me?
[G2 Android Development (D802)] greatgrandking:
fails to install the rom

i tried it sometime back and now and this rom doesn't install......all other aosp roms intall without any hiccup but with twrp recovery evertime i tried it says....failed ....doesn't install
[G2 Android Development (D802)] Orvils:
Same thing happens to me. At first I thought it was bad download, but after re-downloading three times nothing changed. Too bad.. Really wanted to try this rom.
[G2 Android Development (D802)] Reginald476:
Can you tell me exactly what error you are getting when flashing? On the vs980 using TWRP I have to unmount system after I wipe and before I flash the ROM, I can fix this in the ROM if it is needed. Other than that I would need to know what version of TWRP you are on.

Thanks!
[G2 Android Development (D802)] Orvils:
I get symlink some symlinks failed. I am on TWRP 2.6.3.4.

Unmounting system after wipe helped. Thanks.
[G2 Android Development (D802)] Reginald476:
Great, I will fix this in my next build, thanks for the feedback!
[G2 Android Development (D802)] greatgrandking:
twrp 2.6.3.3 ...... just says....." FAILED " on the install page once i swipe to install
[Hardware Hacking General] califauna:
Hi,

I'm trying to find a way to connect an external 3.5mm mic to my i9100 using a variable resistor (eg a volume controller in this case) to add impedance so that various mics with their different impedances can be connected freely, rather than just adding an inline resistor of arbitrary value.

A splitter like like could work perhaps:

http://www.ebay.co.uk/itm/310720331050?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649

I was just checking out this thread for a similar hack:

http://xdaforums.com/showthread.php?t=2072612&referrerid=0

and it says that impedance needs to be added in line with the mic so that the device recognises the mic as a mic (has to be above 1000 Ohms).

This has me wondering if, instead of adding a resistor in the cable that goes to the mic jack (or in the cable of the mic itself), it would be possible to use the splitting adapter above and plug a volume controller like the one below into the mic jack of the splitting adapter then the mic to the other end, like this:

http://1drv.ms/1c7ZwLY

Using the volume controller I can change the resistance between the tip connections of that cable, from 0 up to 1250 ohms, and then it jumps to infinity.

In the above photo the adapter is designed for nokias (OMTP) so the TRRS pinout is different to the i9100 (CTIA).

If I get a CTIA TRRS adapter, will I be abe to make this work using the volume controller?
[Hardware Hacking General] Renate:
This was fairly extensively covered in another thread.

My suggestion was just to capacitively couple the signal.

http://xdaforums.com/showthread.php?p=49625339
[Hardware Hacking General] califauna:
I've read that thread and it doesn't say anything about using a variable resistor of some kind so that many mics can be made compatible, nor the general principle behind the idea (if it works etc).

Thanks for your suggestion about capacitive coupling, but at this point Id like to know if and how the idea I described could work. Your suggestion entails a mic mixer, an attenuator, and learning about capacitive coupling, and my idea just proposes using a volume controller, so Id like to know if the idea is possible before trying something more involved.
[Hardware Hacking General] Renate:
What kind of mic do you want to attach?

A regular computer electret mic with FET? Just connect it.

A low impedance dynamic mic? Use capacitive coupling.

A line level from something? Use capacitive coupling and an attentuator.

There's no reason to use a pot, you'd use a fixed resistor, but you don't even want that.
[Hardware Hacking General] califauna:
I'd like to use dynamic mics, but not just one dynamic mic, like the above thread and mod assumes. My idea is to use a volume controller to control impedance added instead of using just a resistor with a fixed impedance, so that the impedance could be matched to any dynamic mic and thus made to work (as each dynamic mic has its own impedance). This is the reason I had for the idea of a variable resistor of some kind; so that one mod could be adjusted using the volume controller for whatever the impedance is of the mic which is to be attached, and thus the minimum impedance could be added in order to make the mic work. Thus, you're not just stuck with using the mic which the mod (the added resistor) is designed to work. I hope I have explained the idea clearly.

According to the responses, the MOD in the above thread seems to work, and it entails getting less components and doing less research than your idea of using capacitive coupling, so Id be interested to know why you recommend using capacitive coupling instead of the above resistor MOD. Have you found the resistor method not to work very well? In your view is capacitive coupling the better solution for some reason(s)?
[Hardware Hacking General] Renate:
The first point is that the mic presence/button press detection circuit actually works on resistance, not impedance.

A nominal 150 ohm impedance dynamic mic has a DC resistance much lower.

Throwing an ohmmeter on my Shure SM58 I get about 17 ohms.

Any other mic can't be that much different.

To build that out to greater than 1k you're going to need a 1k resistance.

There's no particular point in using something variable for fixed duty.

Depending on the bias circuit inside the cell phone, the lower the resistance of the mic, the lower the effective resistance of the bias circuit.

This will reduce the level of your signal.

The series resistance will also reduce the level.

It's best to have infinite load resistance and zero series resistance.

Also, that way you are not wasting 1-2 mA of bias current.

I did a test using a 470 µF electrolytic capacitor and a Shure SM58 mic.

470 µF is kind of humongous, but a few calculations on input impedance shows that you need a decent value for bass.

I was amazed to see that the level in the stock "Sound Recorder was only about 6 dB lower than using the internal mic.

I'm pretty sure that there was at least 10dB of AGC coming in somewhere.
[Hardware Hacking General] califauna:
Ok, thanks....but now I'm lost. Your explanation seems to be at odds with the resistor mod explanation, where we are told that are options are:

1. Buy a microphone with over 1000 ohms of impedance.

2. Add some impedance.

Perhaps this is just a terminology problem though. The main problem for me, is that the formula given there to calculate the resistance / impedance (they seem to be used interchangeably in places )which needs to be added, in order to detect the mic, is:

"1100 ohms - (ohms of your microphone stated in the manual) = ohms of resistor required to turn on the microphone".

According to that post, we should get the value of the impedance/resistance from the value stated 'in the manual', which means would be using the value for the impedance stated in the manual, not actually measuring the DC resistance (which you have told us we should do, as it gives a very different value from the nominal impedance). Does this mean that the above post is wrong, and we should in fact be measuring the resistance using a multimeter, not just taking the value of the nominal impedance given in the manual?
[Hardware Hacking General] Renate:
No, really, just forget the resistor stuff.

A regular computer electret mic with FET? Just connect it.

A low impedance dynamic mic? Use capacitive coupling.

A line level from something? Use capacitive coupling and an attentuator.

Get an iRig Pre (which has a balanced input and a preamp).

Use a USB mic and USB host mode on your device.

Use a USB preamp/ADC/interface and USB host mode on your device.

Attached is a recording of quiet acoustic guitar using a Shure SM58, Alpha Lexicon and a Nook Touch.
[Hardware Hacking General] califauna:
Thanks for your suggestion to use the 'capacitive coupling' method Renate NST, but unless using it offers some advantage over the resistor method, I cant see any reason for using it. The resistor method is less costly, and requires fewer components and less research ( I know nothing about capacitive coupling).

Can someone confirm which of the above is correct? In order to calculate the resistance/impedance which needs to be added, should we use the impedance of a mic stated the mic's manual (as explained in the resistor method post), or use a directly measured value for resistance using a Multimeter (as Renate NST says above)?
[General Questions and Answers] zeromentu:
Hi... i have my tablet for some time already, but i tryed to connect with OTG and i depared that i cant... So i have readed many topics and have seen to many things. some says that hardware is not compatible others says that is kernel.

I decided to download the kernel and search something about otg (i'm not a PRO) and i figured out this:

****://i.imgur.com/OZGMTOr.png

(replace **** with http cause i cant post due to dont have 10 post :D)

As i understand the driver is called when port power is enabled, it means that need's power.

My question is what if we disable that conditional jump of power port is connected and compile kernel, it must work?

I hope this topic reachs something cause many people wants this functionality

PS: I will search a bit more and post here if i see anything special

Thanks :)

Edit1: ****://i.imgur.com/lSfzeL5.png

I think this is where the problem is... if someone with more experience can help all memopad hd7 users we will be really grateful.
[General Questions and Answers] zeromentu:
Refresh

#Up
[General Questions and Answers] zeromentu:
Push

#push
[AT&T LG G2] Reginald476:
Know Issues - please do not post about bugs that you see on this list:

- Kernel Over Volt of +25-50 (may cause your device to run hot)

- Font Size picker does not work

- LCD Density force closes settings once you change the density and click the home or back buttons.

- Slim Pie needs a reboot before the trigger areas work

- There is no way to activate multi-window

- There is no way to disable Nav bar and pie currently

- OTA App is still in the testing phase, so it will be buggy so do not use it.

If you see something not in this list, let me know below. :cyclops:

New Features:

Custom Progress Bar.

LG apps known to work:

RieGo's LG QuickRemote v7

My personal settings:

System DPI at 400

Navigation Height at 36

Action Launcher Pro

Kernel settings:

TCP Congestion Control: westwood

I/O Scheduler: noop

CPU Governor: ondemand

MPU Voltages: -25 to all

CPU Frequency: Max 2265600
[AT&T LG G2] Reginald476:
I do not have this device so I have not tested this build, there is a chance that you will get sent to fastboot, if you are not comfortable getting into recovery manually please do not try this until someone has been able to confirm. If it does not boot, I have a way to fix the build.

Please download a kernel just in case, this will allow you to boot. If this happens please let me know and I will fix it and re-upload.

Thanks!
[AT&T LG G2] helyg:
Failed to flash on TWRP 2.6.3.3

I didn't try any other recovery as this one is the most stable.

I hope this works. I've missed this rom.
[AT&T LG G2] ossito2012:
I am way to chicken to be first, but I am geeked to get this ROM going, still running liquidsmooth on my Galaxy SkyRocket and Nexus7.
[AT&T LG G2] Reginald476:
For a few people on the vs980 and TWRP (myself included) we had to manually unmount system after wiping and before flashing, please let me know if that works.
[AT&T LG G2] helyg:
I gave it a few tries, but to no success.
[AT&T LG G2] Reginald476:
What is the error you are getting?
[AT&T LG G2] helyg:
That it fails to flash. I restored back to stock so I don't remember the exact response, but it said error flashing due to it being the wrong version. (had this error once when I accidently flashed a Rom for the international g2 instead of the d800.)
[AT&T LG G2] Reginald476:
Is everyone having issues with this not booting? If so I have a pretty simple/fast fix we can test.
[AT&T LG G2] Little Bigboy:
what exactly is going on with this rom ?
[AT&T LG G2] Reginald476:
I haven't had anyone able to test with me so I'm not sure exactly. I have things I can do to fix it but I need someone to test, I have the Verizon version. I figured most of you guys and gals would be messing with Stock KitKat, if you can't tell I'm jealous. ;)
[AT&T LG G2] ossito2012:
I think everyone is a little gun shy after a few scary moments of boot looping and recovery issues with G2. It seems like either D800 flashes good or you end up searching xda for help on getting back to stock. Or worse, you end up in adb land. I know I'm cautious after the first OTA sneaked through without permission and almost ruined my phone, thankfully I had TWRP, figured out adb, and there were some bad ass devs who saved the day. I am definitely not taking any risk.
[AT&T LG G2] ks2332:
Hey [MENTION=4855035]Reginald476[/MENTION] I'd be willing to test
[AT&T LG G2] dondadah88:
I'm considering purchasing this phone and this is the room I will be using how do others feel about the g2 and this room or should I go with the HTC one. Battery life is important to me. I'm coming from a nexus 4
[AT&T LG G2] ossito2012:
G2 is beast of a phone, and Liquidsmooth "will eventually" be a hell of ROM for the G2, just not yet. Keep an eye on rooting and recoveries for the newer firmwares though, those not quite cracked yet.
[AT&T LG G2] dondadah88:
Thanks a lot. I have been debating about this for 3 weeks now.
[AT&T LG G2] Reginald476:
I love my G2, it is hands down the fastest phone I have used and the battery on it is amazing, I don't have to worry about it if I miss skipping it at night. If you can stand to wait, HTC is going to be announcing the new One next month, might be interesting to see what they have.

Don't get me wrong, the G2 is awesome and I hope LG fixes some of the issues I have with it when they release the G3.
[AT&T LG G2] Reginald476:
No, I have not forgotten about you all, I was waiting for a feature to be released so I could make a new build, I am building now, if all goes well I should have dr87 and Furnace versions of LS for you all later today/tomorrow morning. See below for the included updates/changes!

**3/4**

Liquid Updates:

Slim's Recents

Fixes for native screen recorder

More multi-core boot optimization

Possible fix for poor speaker quality

Bump in speaker volume

Reduce volume in call

Add more steps for in-call volume

Edit: I have a Hangout that I am using if you would like instant access to stuff or to me, just add me on G+ or send me a message and I will add you. Just click my name and it has my G+ info. If you would like to test builds for me, let me know and there is a separate group for that.
[AT&T LG G2] Reginald476:
OP is updated! There are downloads for dr87 and Furnace Kernels.
[AT&T LG G2] Little Bigboy:
thaks will make a nandroid and flash this
[AT&T LG G2] ossito2012:
Well, I flashed the furnace and kept getting android.process popups, I then flashed the dr87.

It worked great, insane speed and almost everything worked as it should, but once again another kitkat ROM falls short, where you ask, take a guess, f'n Bluetooth, just turning it on was buggy, but once in car trying to connect, full bt fail, smh, back to perfection with flex. Does anyone have an explanation why bt is do difficult to make work.

I will add that if I had no need for BT I would definitely rock this for daily driver, it was just fast.
[AT&T LG G2] Little Bigboy:
unfortunately i'm having very low , i mean realy low in call volume . everything else seems to be working, didnt get to test bluetooth out yet. Im still running it and will give it 24 - 48 hours to make any solid statements
[AT&T LG G2] Reginald476:
For an immediate fix you can use a file browser and go to /system/etc and edit mixer_paths.xml search for <ctl name="RX1 Digital Volume" value="60" /> change 60 to 70 and that was what the value was set to. Otherwise it will fixed in the next build.
[AT&T LG G2] Ortanon:
I'm using the Furnace version and I only got the android.process popup once at setup. Nothing else after several hours of use and reboots.

The Bluetooth is working for me, too.

To be honest, the firmware is amazing. All the features I wanted, even if it is only 99% stable. But what's with this goofy-looking white Recents tool? Where's the Kill All button? Where's the option to use the default AOSP Recents?

There are some other things I'd like, but the Recents thing is the one that stands out by far.