yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] Steven 1:
App2sd is built in the ROM. Or look up dtapp2sd and follow the guide. Sbc is kernel related and isn't preinstalled into the ROM

This forum contains an SBC kernel that you can flash. Goodluck

http://xdaforums.com/showthread.php?t=1557248
[EVO 4G General] NxNW:
+3 on MikG. myn himself said if he wasn't running his own ROMs on an Evo 4G, he'd be running MikG:

http://www.goodandevo.net/2011/04/rom-dev-spotlight-myn-of-warm-rom-series-for-htc-evo-4g.html

plus it's still *very* actively supported.
[AT&T Samsung Galaxy Note I717] antoniouslj:
The audio DSP used in our Note's is the Yamaha YDA-165. While this is one of Yamaha's first offerings in the low power audio codec chip market, it's not a very good one. Wolfson chips have generally been said to beat it hands down, and if you examine a comparison Anandtech did between it's possible sister chip (or a really close relative) and the iPad 2's Cirrus chip, you can see why.

It has been discussed that there is a slight hiss when listening to headphones during moments when nothing is being played (in-between songs, for example). I'm here to see if we can discover exactly why this is and maybe uncover some solutions. I've attached the PDF of the YDA-165's cut sheet to this post so everyone can skim through it.

I have noticed that there is a noise gate on chip, however, it's only for use with the speaker if you'll look at the block diagram.

View attachment 958969

Here is my DMESG if anyone wants to see it: http://pastebin.com/f4WnJC7j

When I get more time, I'll fill this post up with some more observations about the codec.

The HP amp is nearly maxed out, power-wise. According to DMESG, it's being supplied with 2.6V out of a possible max optimal range of 2.86V. I don't know how to determine the HP amps' dB output though (It's probably set at 0 by default). The attenuator for the HP amp may be locked to a specific range by Sammy, although it's capable of (-36dB)-(0dB), which I assume it is probably also set at by default. If we can get the HP amp increased to 3dB, we'd be able to get more power out of the amplifier, utilizing the digital signal gain in the DAC less. Analog amplification as opposed to digital amplification always results in cleaner audio.

The minimum headphone impedance for the codec is 12.8 ohms.

Comparing the amplifiers SNR to both Wolfson and Cirrus shows that it actually produces less noise than both of the aforementioned manufacturers. This leads me to believe it most likely is either a crappy DAC to blame or simply bad shielding.

Another thing to take note, the YDA-165 in our Notes does not have the same model number as the one found in the GS2, which is YMU823. With no documentation on the YMU823, there's no way to know how different or similar the components inside are to the YDA-165.
[AT&T Samsung Galaxy Note I717] tenderchkn:
No attachments or poll. But yes, I do have the hiss.
[AT&T Samsung Galaxy Note I717] antoniouslj:
Forum software likes to publish the post before the author can write the poll... :confused:
[AT&T Samsung Galaxy Note I717] tenderchkn:
How can I tell if it is more than 16 ohms or not?
[AT&T Samsung Galaxy Note I717] antoniouslj:
Usually listed on the package. What model do you have?
[AT&T Samsung Galaxy Note I717] tenderchkn:
I have the AT&T I717.
[AT&T Samsung Galaxy Note I717] antoniouslj:
I meant the model of your headphones or in-ears, sorry. :)
[AT&T Samsung Galaxy Note I717] tenderchkn:
No worries - was slightly confused. :)

I have a pair of Bose QC2's, let me check the package.

EDIT: I can't find any reference to ohms in the manual or specs. But I did discover something interesting. On my headphones, there is a detachable audio cable with the "HI" and "LO" setting for "LEVEL". If I switch to "LO", obviously the volume decreases, but I also no longer hear a hiss. My guess is that the signal doesn't get amplified enough to hear the hiss. Anyway, which "Yes" option should I pick?
[AT&T Samsung Galaxy Note I717] antoniouslj:
I did some Googling, and it appears Bose doesn't do a very good job of listing product specs ANYWHERE.

The detachable audio "cable" most likely contains an in-line resistor and actually increases the resistance of the line to well over 16 ohms. I think we're on to something here. Don't select anything in the poll since, well, we have no idea what ohm ratings there is with those Bose QC2s.
[AT&T Samsung Galaxy Note I717] 00mred00:
Subscribed....you might also post in the skyrocket and tmobile galaxy s2 they have the issue too
[AT&T Samsung Galaxy Note I717] tenderchkn:
Obviously, I don't know much about the nitty gritty technical stuff, but it seems like additional resistance would effectively reduce or remove the hiss? Would this be similar to doing noise removal processing on an audio file?
[AT&T Samsung Galaxy Note I717] antoniouslj:
It's in how an amplifier works, really. Electrical equipment is more efficient when it uses more power. When you increase the resistance, you're effectively increasing the amount of power it takes for the amp to drive your headphones.
[AT&T Samsung Galaxy Note I717] flintdragon:
I think introducing more resistance would probably work (I'll try it tonight), but would be nice to completely understand how this sound chip is used in this device and maybe someone can whip up an app to really control the amp so people do not need to be carrying around extra equipment! (run on sentence but I'm not gonna edit it!)
[AT&T Samsung Galaxy Note I717] pj_rage:
30ohm W3s here. Definite hiss. When it is playing system sounds, you can very clearly hear when the output is turned on and off. Quite annoying, but the rest of the phone is worth it. FWIW, just for comparison sake, I didn't have any noticeable hiss like this (that I remember) with the iphone 4.

This is probably the wrong thread, but does anyone know if the drivers are built in for a USB DAC? I could always use mine I guess, but haven't even looked into it yet.
[AT&T Samsung Galaxy Note I717] antoniouslj:
It's beginning to seem like it's simply a lack of adequate shielding that's giving us this noise issue. It could also very well be the headphone amp too, but until we're able to manually control its output, there's no way to know for sure.

As far as the drivers go, I highly doubt Sammy included them in the stock rom. You'd have more luck on an AOSP build.
[AT&T Samsung Galaxy Note I717] flintdragon:
Found the inline attenuator and it works well but I have to turn the volume way high now. Hope I don't accidentally blast my ears if I forget to use the attenuator!
[AT&T Samsung Galaxy Note I717] crawldit:
I've got a pair of SHURE SE110's that are rated at 27 Ohm and I definitely have a hiss. I've owned them for a good 4+ years and have never experienced a hiss on any sort of player until the Note. I've got some Thinksound Ms01's coming tomorrow that are rated at 16 Ohm. After I burn them in I will give them a listen and see if they hiss as well.
[AT&T Samsung Galaxy Note I717] antoniouslj:
Interesting, however, without sensitivity specifications, the results would be moot. It appears ohms may be related, but I would need to completely throw driver sensitivity out of the equation.
[AT&T Samsung Galaxy Note I717] crawldit:
SHURE SE110 (Hiss) -

113 dB

27 Ohm

22 Hz-17.5 kHz

Thinksound Ms01 (TBD) -

93 dB

16 Ohm

18 Hz-20 kHz
[AT&T Samsung Galaxy Note I717] mitchjaz:
No hiss with Klispch S4A's.
[Galaxy Ace S5830 General] nbigaouette:
Hi all,

I started playing with my Samsung Galaxy Ace and would want at some point to install CyanogenMod on it.

An issue that arise is that I have the GT-S5830D variant (Telus, TLKI4).

To flash the recovery, I downloaded recovery-clockwork-4.0.0.9-galaxyace.img from http://download.clockworkmod.com/recoveries/ and tried to use "flash_image" as recommended on CyanogenMod's wiki, but flash_image fails. I think flash_image tries to access /proc/mtd which is non-existent on the GT-5830D while present on other GT-5830 variants.

So I used recovery-clockwork-5.0.2.6-galaxyace-fix.zip from http://xdaforums.com/showthread.php?p=18178563#post18178563 but this failed too. Looking at the updater-script in it showed an assert against certain models. I thus added mine to the assert, repackaged and resigned it. It flashed fine.

Before installing CM 7.2.0-RC1, I want to make sure I wont brick my phone. Looking at its updater-script, I see it's writing "boot.img" to "boot". My guess is that "boot" is a partition, but since the GT-5830D seem to be different enough, I wanted to verify first.

So my question is, does anybody knows the exact difference between the GT-5830D and any other GT-5830 variants??

Thanks a lot!!
[Galaxy Ace S5830 General] CallMeVentus:
The assert thingy allows you to specify what model this one should be flashed with .

It has no real effect .

Herpderp Defy.
[Galaxy Ace S5830 General] nbigaouette:
Ok thanks.

The assert is there to protect the user from installing a rom on a different phone. The assert needs to be strict so the rom is installable only on the supported phone, but not too strict as to prevent variants of the phone...

I was just unsure as to if the S5830D was enough the same as the S5830 so that even if the assert passes, flashing wouldn't brick the phone.

Yesterday, I installed CM 7.2.0-RC1 (da26c44f36032e202e7dd21c13bf14b7 from here get.cm/?device=cooper) successfully. The assert passed fine.

I must say I am deeply impressed by CM compared to stock!

Issues I've found:

Torch does not work. The application stays open, crashes all the time and restart. Only way to disable it is restarting.

Screen does not turn off during conversation. Proximity sensor not working?

"Menu" and "Back" buttons kind of randomly lights up for a couple of seconds every couple of minutes.

These are known issues though. Even the camera works!

Thanks CM dev and supporters ;)
[Galaxy Ace S5830 General] Clous87:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.

have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.

i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)

if this does work, is there a step by step guide to change the assert within the rom?

cheers

clous
[Galaxy Ace S5830 General] FrankyDoodle:
Why are you digging up old threads......

Sent from my Jelly Beaned Ace
[Galaxy Ace S5830 General] Clous87:
erm... thought it was pretty well explained.

Feel free to suggest a newer one that i can ask my question in...
[Galaxy Ace S5830 General] Tovagulet:
Just create a new thread...

You don't have to post your problem in another thread...
[Galaxy Ace S5830 General] Darkshado:
As long as you don't mess up your bootloader and have a working Odin install, it's pretty hard to completely brick an Ace. And yeah, don't necro old threads please.
[Galaxy Ace S5830 General] nbigaouette:
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:

http ://code.google.com/p/cyanogenmod/issues/list?can=2&q=model=cooper&colspec=ID%20Type%20Status%20Version%20Model%20Network%20Owner%20Summary%20Stars%20Priority

There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:

http ://changelog.bbqdroid.org/#cooper/cm7/next

The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
[Galaxy Ace S5830 General] Darkshado:
There, fixed it for you ;)
[T-Mobile myTouch 4G Slide] Some_dude36:
I am running Undead's ICS v5.3 and the display keeps turning on and off randomly and frequently .

Undead suggested i reflash ... so I did and it worked for a while and now its doing it again and it only did it on this rom and as far as I know im the only one having this problem . running the stock kernel .

Any ideas as to what would cause display to turn on and off frequently at random ?
[T-Mobile myTouch 4G Slide] Emmanuel U:
ask him....theres alot of stuff he put in it....How long have you been using it?
[T-Mobile myTouch 4G Slide] Some_dude36:
I been using it a while . I already asked him he had no idea what was the problem and said hed never heard of the problem before :(

Are there any other roms out there that are fully functional ? mms BT wifi 1080 cam 8mp camera ect ect ? im bout done with this rom which sucks because other than this problem its flawless but this is a huge problem
[T-Mobile myTouch 4G Slide] Limewirelord:
He always says that.

Are you S-OFF or HTC Unlocked?
[T-Mobile myTouch 4G Slide] Some_dude36:
S-off I just downgraded to ICS 5.2 well see if that works

nope 5.2 is doing the same thing

are there any roms that everything work?
[T-Mobile myTouch 4G Slide] wesnah:
Try bulletproof 1.1
[T-Mobile myTouch 4G Slide] Coug76:
Bulletproof and Undead's Rubix Expresso work like a charm.

Hastily spouted for your befuddlement.
[T-Mobile myTouch 4G Slide] blackknightavalon:
I had this exact problem with his ROMs. I fixed it by flashing Pyr'O'Ice.

Posted from Spaceball One
[T-Mobile myTouch 4G Slide] Some_dude36:
Bulletproof 1.1 it is ...
[T-Mobile myTouch 4G Slide] AgentCherryColla:
Lolz Undead saying that he's never heard of an Issue on his Rom :O Shocked! ;D

It's Always Sunny in XDA
[T-Mobile myTouch 4G Slide] Some_dude36:
He left doubleshot anyways , hes on the sam gsII now ...... so I think maybe he just didnt wanna deal with glitches anymore ...

Bulletproof is lookin slick .... im not a huge sense fan but ill give it a spin
[T-Mobile myTouch 4G Slide] blackknightavalon:
I told him that I kept having unmounting issues with my SD card and even gave him a few logcats. :3

Posted from Spaceball One
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
I found your problem. :D

Seriously there's at least 1 ROM that's offering everything u need on XDA. I guarantee it! Why not try one out??

Typed by ---- oh wait! I'm schizophrenic!
[T-Mobile myTouch 4G Slide] Some_dude36:
which rom is that ??????????? i switched to bulletproof ... its cool but im always on the lookout.
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
I was just being a tushi hole

.... What do u require in a ROM? What did ICS Splashed offer that others you tried lacked which you felt you need?

Typed by ---- oh wait! I'm schizophrenic!
[T-Mobile myTouch 4G Slide] Some_dude36:
MMS 1080 vid bt wifi camera batt life tv out is awesome but not required and i like sense cameras

bulletproof is cool but im @ 17hrs with 18% battery left :(
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
Have u used the new Kernels for Bulletproof?

Typed by ---- oh wait! I'm schizophrenic!
[T-Mobile myTouch 4G Slide] Some_dude36:
Nope ..... link?

nevermind i found it ... just a lot of stuff to sift through on the OP bulletproof xD i got it though now I just need to figure out which is best for battery life but still stable uh oh I see a 1.7ghz kernel in there ... i wonder if i could set cpu the freq down so id have the option for 1.7 but still have good batt ?
[T-Mobile myTouch 4G Slide] Some_dude36:
ok it must be the phone ... i just flashed the batman lock ring and the display just turned on by itself :( and this chick who got a new iphone been makin funna my droid saying it sucks cause the screen turns off and on by itself i was hoping it was the rom but i guess not im gonna hafta get a new phone or something ..... cause i cant deal with the screen doin this
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
Yes you may do that, the 1.7 is just the max it will set your processor to, under-clockable.

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

Also keep in mind, dual core means two cores running at the assigned speed...I run at around 700 on most profiles i have setup in SetCPU because thats 1.4 ... keep that in mind you dont need a whole lotta power for our device :D
[Motorola Droid 4] phrir1:
Can anyone tell me if this can be used on our phone running cm9? I've never got to deep into scripts but this made me curious.

ICS V6 INFO

Thanks in advance for any input....
[Motorola Droid 4] RueTheDayTrebek:
Personally, it seems a little drawn out. You already have a Droid 4 at 1.2ghz dual core. Not sure if a whole lot more power is warranted.

That's the kinds of thing where I would wait for the Fastboot files, a signed stock rom, and a clockworkmod that you can flash through Rom Manager.

Root, debloat, get a new launcher in there and sit tight.

To brick or not to brick.

Been there, done that, no bricking for me, again....

C
[Motorola Droid 4] podspi:
Honestly, on the OG Droid V6 was a lifesaver, but I'm not sure if it is necessary on the D4, it does have 1gb of RAM after all! :D

That being said, I would put the chances of this script bricking your device to be pretty low, but of course, YMMV. I can say for sure it never bricked my D1. Hopefully my D4 isn't going to start running out of RAM any time soon...

Edit: There does seem to be ICS-specific info there, so I would assume it should work as long as you follow the directions. Still probably not necessary for the D4. Any laggness is probably due to alpha/betaness
[Motorola Droid 4] jy3ng4:
I tried running the V6 Supercharger script on my stock rooted D4 yesterday and it caused some problems so I had to restore a nandroid backup. I used option 6 (500HP Balanced) and got a force close notification for Titanium Backup immediately upon reboot. When I tried uninstalling/reinstalling TB, I got a low storage space notification, even though I have several GB free for apps.

I'm not sure if I did something incorrectly but just thought I'd share my experience as a warning.
[Motorola Droid 4] phrir1:
Thank you guys for all the input.

sent from OC'd ICS D4 using xda
[NFC Hacking] lucasmine:
Is it possible?
[NFC Hacking] martonikaj:
It should read and wake the device, no?
[NFC Hacking] RTContent:
As I understand the technology, this isn't possible with the screen completely off. It's a security feature that the secure element only turns on when the screen turns on. So it should be a hardware limitation not a software one.
[NFC Hacking] lucasmine:
the thing is, I can't seem to read with the screen on but no unlocked yet....

só its kinda boring having to turn it on, then unlock the read the tag...
[NFC Hacking] RTContent:
It depends on the app. Some apps unlock it automatically like Google Wallet. So it depends on if the dev has added that feature.
[NFC Hacking] elmo61:
correct, the nfc card turns off when screens off
[NFC Hacking] phanover:
My understanding is that the NFC service is disabled not the hardware and this could be changed with a custom ROM.
[NFC Hacking] Redline32:
I've tried it both ways, screen off and screen on with Google Wallet and though it takes more time for it to open the app and prompt me for my PIN when I just pull it out of my pocket and tap it, it does seem to recognize the NFC tag (at the POS at least) even with screen off.

So I'd have to agree, I think it's up to the dev.
[NFC Hacking] phanover:
I'm hoping that one of the NFC devs sees this and can request one of the ROM developers to allow the NFC service to be active when the screen is off. I'd make this request myself over on the One X developer forum but I don't yet have the required 10 posts :(
[NFC Hacking] krohnjw:
Google Wallet doesn't unlock the device in ICS - it did in Gingerbread. It did this because the NFC Service and polling loop started when the device was awake, yet still locked. This changed in ICS.

It is the service being disabled.

http://grepcode.com/file/repository...4.0.1_r1/com/android/nfc/NfcService.java?av=h

See ApplyRouting where checks are explicitly made to see if the screen is unlocked before enabling. In theory the service could be modified and compiled into a custom rom to behave like Gingerbread (where it worked with the screen locked but on).

In Gingerbread ApplyRouting was maybeEnableDiscovery and the only check was mScreenOn

http://grepcode.com/file/repository...apps/2.3.3_r1/com/android/nfc/NfcService.java
[NFC Hacking] LoveNFC:
So, it's definitely possible to enable NFC with the screen on but still locked. But what about the OP's main question? Is it possible to keep the NFC service active 24/7 with some hackery?
[NFC Hacking] krohnjw:
Possibly I haven't looked at that part of the service, the code's all there though (assuming there isn't anything in the blobs preventing it).
[NFC Hacking] kml60664:
how about read NFC tag in lock screen?
[NFC Hacking] Bardamuz:
can this be include in one existing apps (the one you create) or only in rooted device ?
[NFC Hacking] krohnjw:
You'd need to modify the actual NFC service - so it would need to be part of a modified ROM.
[NFC Hacking] fajarep:
I think that is not possible, "action" in NFC is kinda to emulate user activity..., I don't that that "user activity" can be done when screen off/locked...
[NFC Hacking] Bardamuz:
when screen is off NFC stop working , except if you root the device it will not be possible to make it run when screen is off/locked
[NFC Hacking] cy80rg:
Evening gents,

I have a simmilar requirement for a project - to enable the NFC-read capability with the screen off / device locked.

I understand this is disabled as a security measure, to stop running instructions from external tags without user knowledge.

However, does this "lock" apply to simply reading a tag, and confirming the responce?

I read in various places that there is a "mod" to allow NFC with the screen locked.

Would this need to be done on a rooted phone?

My intention is completely legit - the final app would be installed from the Play store, with permissions required being accepted by the user etc as normal.

Could this "Read NFC with screen off" be authorised and enabled as part of the apk payload installation?

(FWIW, if this is possible, I would need to "ping" (run NFC search, read responce, confirm tag ID) every x-minutes).

THX :)
[NFC Hacking] forid200:
It should be possible to "override" the security feature of turning off the NFC reader when your screen is off through a custom, modified kernel. And to those who say that it's a hardware limitation, it's not. At least not on my phone, I used to have this before, on an older version of Android. Now I'm running a CM based rom, on Android 4.4.4, and it doesn't seem to detect NFC cards at all when the screen is off.

But I like it this way, so I'm not complaining.
[NFC Hacking] MaxDeavy:
Hi, in AOKP KK you can set the NFC Polling Mode to "screen off", "screen on locked" and "screen on unlocked (standard)"

Maybe look af github for the code.

greetings from Germany
[NFC Hacking] :
It is indeed possible to read an NFC tag while your screen is off/locked!

how?

There is an xposed framework which enables your phone to read nfc tags in lock screen, and it is called

"NFC LockscreenOFF enabler"

this module also allows a particular NFC tag to unlock your device without any data written on the tag itself, by using the NFC tag ID

i am using this module and it is really helpfull for me :)

I hope i helped you, if you have more questions let me know
[NFC Hacking] ipois0n1:
bugged under 4.4.x
[NFC Hacking] MathewBrack:
seconded I use this xposed module with my nfc implant to unlock my phone, can't rate it highly enough :)
[NFC Hacking] dimex:
You still using KK with the Xposed Module? I have an xNT myself, but find the NFC smart unlock in Lollipop stupid because you have to maintain NFC contact with the tag and still swipe a swipe-to-unlock screen. If someone can find a working solution for Lollipop with the Xposed mod functionality I'll switch to lollipop.
[NFC Hacking] MathewBrack:
Aye, I'm using Note 2 CM11 nightlies on 4.4.4 until their is a fix for xposed. I knew lollipop came with an NFC unlock but didn't want to give up xposed, it's rather an unfortunate situation because that sounds ridiculous. It's a shame that the NFC compatible lock screens on the market all suck compared to default.