yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
I'm sorry, I can't raise enthusiasm for further tests. This work should have been done by you before publishing.
[Nexus S Android Development] Windows X:
You're supposed to compare original file and patched one under the same environment if you want to test whether lowering latency will benefit anything to signal and noise graph. I thought it sounds weird about increasing volume and now I know why. If only difference isn't patched audio library, we can't reach to conclusion whether patched file will have any effects or not. But that's fine if you've lost your interests already. It's just too bad that you didn't show comparison between original and patched files alone without using platform file.
[Nexus S Android Development] DeuXGod:
With our without the patch the audio quality is the same, just a bit higher volume when patched, but that's it... I'm not trying to be disrespectful, just my 2 cents

Sent from my

( •_•)

( •_•)>⌐■-■

Nexus S

﻿(⌐■_■)

YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
[Nexus S Android Development] kong:
Thanks bedalus.

Case solved. (at least for me) :)
[Nexus S Android Development] Windows X:
That's not right environment to be acceptable. I'll try in same volume size and use wav format for uncompressed stream. The reason control is better because it has Voodoo volume at 27db while platform will increase it to 57db. How can we conclude the test with hardware volume difference at 30db?
[Nexus S Android Development] Windows X:
Too bad that my laptop can get down to only 30ms. As given tests having too many flaws like this

1. you did recording at different hardware volume gain. Control at -30db as Voodoo defaults and platform at new 0db. With 30db increased, there's no doubt that you'd expect more noise from higher db gain. I can't believe you didn't check this beforehand. 30db gain difference will give us very inaccurate results and your compensation won't cut it out.

2. Your test file format is WMA which is compressed format. For professional tests, it must be .wav format as decoder will impact DSP latency damaging continuity of bit-stream

3. You didn't specify test equipments. To test latency measurements, you need to test with equipments running at lower or equal to test subjects. I this case, you need to perform recording at 5ms latency or lower so we can see the impact of test subjects at full potentials.

I won't ask for retest but your given tests are not accepted for strict measurements. And I doubt he ever have a card capable of recording at 1ms latency.
[Nexus S Android Development] :
Unsubscribed. Avoid.
[Nexus S Android Development] Windows X:
For control having it has 30db less gain level. Sorry but I just can't accept that as I used to make proper tests in PC area with 1ms latency capable card. Too bad that test is not acceptable for both party but thanks for your time and effort with this ones.
[Nexus S Android Development] klinker:
One question...when i flash a kernel, i have to reflesh your mod, yes?

On the road with my Nexus S...
[Nexus S Android Development] Windows X:
No need. Since 2.0, platform is designed to work on most kernels. I'm refining script for better performance and stability wise hoping to release an update soon.
[Nexus S Android Development] klinker:
I know the mod suport many kernels but...now i had trinity t11 with your mod and now changed to t144 cv. Now i have to reflesh the mod to or not.

On the road with my Nexus S...
[Nexus S Android Development] Windows X:
From what I checked in 2.0, it doesn't have kernel installed. However, there's script involving governor changes and will clear all existing scripts in init.d so you should reinstall kernel with scripts to try and see if it works OK afterward.
[Nexus S Android Development] Windows X:
Some issues on Galaxy Tab P1000. It seems to have either low performance driver porting or hardware is not capable of responding well at lower latency. Something like this will happen when you push what beyonds its limit. Not all Android phones can run at significantly lower latency and tested Nexus S/Galaxy S can perform from 2048 buffer size down to 256 buffer size without having distortion. Quite sad news for me as power output of P1000 is way fuller than small phones can hold.

This file is recorded from general patch code having period size 448. What lies beyond that'll just make device freeze from playing sound. I'll try to raise buffer size to 896 as original code and see if it improves after I get back (current ones will have one period filled in buffer instead of 2).
[Nexus S Android Development] mihaits:
I found this thread a few days ago and I almost couldn't believe it. Audio latency has been one of the biggest problems in android for 3 years. Great work! :)

Will you ever make this for sgs2? Or it's not possible because of the lower quality audio harware (some Yamaha instead of Wolfson)? I'm not putting any pressure on you, just asking. ;)
[Nexus S Android Development] Supersaiyan.IV:
mihaits, read the description for nexus_s_fidelity_platform and install on your sgs2.

The sound issues have bugged me ever since this was published http://arunraghavan.net/2012/01/pulseaudio-vs-audioflinger-fight/

Sole thought of having my device aliasing sound by resampling by default made me cringe. However I'm not sure priority and buffer sizes will improve quality. But if you're going for it I suggest aligning the data structures and memory (data alignment) for better data accesses and loop delay consistency.
[Nexus S Android Development] mihaits:
The thing is, even though I may have some basic knowledge, i don't have any coding skills or knowledge of the way audio is handled so don't ask me to do it myself. From my understanding, the "platform" patch installs some init.d scripts that optimise the CPU governor, the I/O scheduler and some values for Voodoo Sound for audio quality/latency (but the audio hardware doesn't support VS, and, off course, there isn't a kernel for the galaxy s2 for with this mod), and the other patches add libs according to the patch chosen (hardware specific part?). Please correct me if I'm wrong or talking nonsense as I'm still relatively new to Android:). So I'm asking Windows X again: Is it possible to add support for Samsung Galaxy S II?
[Nexus S Android Development] Supersaiyan.IV:
mihaits, since this is based on voodoo sound it's the same as asking supercurio to add SGS2 support.

The development comment was meant for Windows X, but of you're going to make a dive into real-time DSP programming then that would be a great contribution to XDA ;)

Now I'm taking my statement back because aligned_alloc won't be here until the first C11 compiler is ready. There's support for it in linux, but it depends on _ISOC11_SOURCE which is a problem.

Source: http://man7.org/linux/man-pages/man3/aligned_alloc.3.html

If the data structures aren't cache-aligned then there's more improvement on the horizon.

EDIT: You can try cooking up an aligned_alloc from this though: http://code.google.com/p/nanoflow-c....h?r=8b1d97dea4d9a3dbbc46be9644a34f00dac0a58d
[Nexus S Android Development] mihaits:
Thanks:) All is clear for me now.
[Nexus S Android Development] Windows X:
For platform, it'll also optimize I/O and kernel settings. If your kernel supporting latency and granularity tweaks, it'd be a great plus for better continuity of audio performance. Supercurio once noted in GSIII having 100000ns granularity which is 10 times smaller than default and this platform can set that for you if kernel supports it. I'm more looking forward to Windows side though as Vista/7 can get this to as low as 100ns (1000 times smaller than GSIII).

For Galaxy SII, it uses proprietary audio library so there's no source code to modify.
[Nexus S Android Development] d1xt1r:
Hi Windows X,

Can you make new Fidelity Pack for the latest 3.6 Slim ICS with your latest tweaks (also you can add new version of Apex (if available) and etc.)? I tried twice with the package for 3.5 but i'm experiencing problems with UpdateMe application.

Thank you in advance.

Dex
[Nexus S Android Development] qetuol:
so how many people have perceived better quality and how many no/worse quality with this mod?
[Nexus S Android Development] xjerlzx:
HOLY **** IT TOTALLY BLEW ON MY ULTIMATEEARS TF10 (not a cheap set of earphones)

Its clearer smoother more detailed then putting flac on my phone.

Now testing the battery life =]
[Nexus S Android Development] melvinchng:
What is the most common zip to be used.

Accidentally sent from my Google Nexus S
[Nexus S Android Development] richlum:
@tycruickshank - Which zip did you use? Some of them say for music playback, but I'm not sure why that would be.

I'm interested in trying this on my Galaxy S, not for any improved audio quality, but purely to get low latency between triggering an event and hearing the sound.

I love Caustic too.

An example of incredibly poor (and inconsistent) latency I get is with any of the various drum apps.

There is latency when you tap a drum, but it you start playing the drums with a constant beat, the latency varies.

thanks,

Rich
[Nexus S Android Development] vonVideo:
For Galaxy Nexus GSM you me refer to http://xdaforums.com/showthread.php?p=26595843
[Nexus S Android Development] Windows X:
Looks nice vonVideo. Try to keep it down to 10ms or even 6ms if possible. Too bad I don't have GNex so I didn't compile any for you guys. Nexus S can get down to 6ms latency which is as good as iOS devices.

Anyway, I sold my Nexus S yesterday to friend and got Xperia P instead so project will be on hold until I can test them on my dad and brother's devices.
[Nexus S Android Development] tycruickshank:
I'm using the nexus s fidelity plus music.zip on rascream+trinity and there is very little latency when using caustic or any other similar app.
[Nexus S Android Development] sucka:
Well on my osciloscope i do not see any difference in the frequency output, so yeah no difference. sorry :)
[Nexus S Android Development] Windows X:
This is low latency mod and platform tweaks are what to keep low latency being more stable. I won't debate about sound quality improvements as I stated in first post already.

But if you want to seriously making proper measurements (One you did was wrong attempt as there's no hardware changes), you need to check on http://en.wikipedia.org/wiki/Audio_system_measurements There should be some relevant measurements like total harmonic distortion, phase distortion/delay, transient response, etc.
[Nexus S Android Development] lilvfr400boy:
Wish someone could work this on the HTC one x, I have to have an Ios device too at the moment for amplitube and amp software :-(
[Nexus S Android Development] sdhanjal15:
WHICH ONE?!
[Nexus S Android Development] MrSmileyJr:
will this allow us to finally record our phone calls?
[Nexus S Android Development] james300:
how this work i need to flash all the files ????

hi,how this work i need to flash all the files ????,or ican any one alone ?
[Nexus S Android Development] CADude:
Relevant!
[Nexus S Android Development] Windows X:
Good to hear jellybean has Galaxy Nexus working at 12ms but Nexus S Fidelity is already running at 6ms. I'm using Sony Xperia P right now and no longer own any models to test further improvements. I may buy again after 4.1 fully ported to Nexus S.
[Nexus S Android Development] osbaldov:
Does work for the nexus s 4g?
[Nexus S Android Development] Windows X:
It does.
[Nexus S Android Development] osbaldov:
I tried it and nothing has gone wrong. I'm running cyanogenmod rc1.
[Nexus S Android Development] melvinchng:
Fully "arrived", not port :D

Accidentally sent from my Google Nexus S
[Nexus S Android Development] cpaixao:
This patch would works on CM10 or JB stock?
[Nexus S Android Development] spider623:
trying right now the platform build on Oodies jb build and it works but breaks musicfx.apk

the sound is clear and loud btw it makes the rom a little bit slow
[Nexus S Android Development] mr.haqeem:
the sound is diff and nice but it break musicfx. how to fix it? i luv this mode. hope u can enable the music effect to fix that prob i think..
[Nexus S Android Development] euggie2000:
I dunno how you did it. My AOSP JB and SDK JB makes no sound after update to music and general versions.

Can anybody make this latency fix for stock JB?
[Nexus S Android Development] spider623:
quick question i really didn't have time to read if it was answered before but what is the max sound frequency that our sound boards can handle in Hz?(44100, 48000, 96000, etc) thanks is advance
[Nexus S Android Development] irishrally:
All standard sample rates from 8kHz to 96kHz are supported in the WM8994.
[Nexus S Android Development] xjerlzx:
most common flashed file?
[Nexus S Android Development] eldoro:
galaxy tab 10.1

Did anyone already tried with the galaxy tab 10.1? Any succes? Which patch do I have to use?

Just installed some music apps and the latency is very anoying...

eldoro
[Nexus S Android Development] eldoro:
anyone

anyone know something about the galaxy tab 10.1
[Nexus S Android Development] unicat13:
Any chance to work on Nexus 7 JB 4.2.1 (in stock rom in Caustic2 70ms latency) or any chance to port for Nexus7.
[Nexus S Android Development] Windows X:
As I already sold Nexus S to my friend who wants it for better music phone, it's been discontinued. I've been working on optimizing fidelity script instead for my Xperia P phone and Galaxy Tab.

I tried optimizing latency in Galaxy Tab 7/10.1 but result was hardly satisfying, I can reduce only few tens of buffer size which was not worth the effort. Things may be better for Tab once kernel 3.x is fully ported with proper clocksource and audio port.

For now, it's just this phone and Galaxy S that should have latency work done (Alsa SoC, WM8994, Voodoo, kernel 3.x). I may bid Nexus S once again for some projects to kill time with JellyBean if I'm lucky enough. Hope I won't get into audiophile debate crap again.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
Hi friends, im sad because my touchscreen dont works

My phone is a sk17 with unlock bootloader, root and the recovery still working

The problem strats when i chance the build prop of my phone, i change all the "SK17" to "WT19" to make work a rom.

Then i noticed my screen dont work, so i decide to install a rom via cwm.

I do that but the screen still no working, i only want to access to my build prop to change it again and make my phone works again

Please help me i am a noob :(

I access via pc to build prop file and it says "SK17" i think now it is hardware problem!! DX

Anyone can help me?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] triasbrata:
i think you must reinstall firmware
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gandhar:
did you flash a kernel when you installed the rom?

if yes then you must have flashed one for the wrong device, please chaeck otherwise flashing original firmware will make everything all right
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
So you think is software problem? Right? :D

ok i will flash a new kernel and other rom lets see what happend

Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gandhar:
best way to check, flash original firmware!

this thread has ftf if you don't have it

http://xdaforums.com/showthread.php?t=1568792
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
Thanks gandhar

I flash the sk17 tft with flashtool in flashmode

my cell starts but i can unlock it, the screen still doesnt work, i noticed the touch buttons i mean "back" and "options" dont work.

All fisical buttons works!

Any suggestion?? Please
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gandhar:
installing a ftf is like reverting it to a stock stage, if your phone was working then, it should work now. are you sure you installed sk17 and not st17?

i cannot think of any other reason for this..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] singh_dd93:
Try flashing Stock firmware 5 to 6 times. I read somewhere that some times touch drivers are lost which can only be restored by flashing stock again and again

You can also refer this thread
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
OMG!! i flashed it six times and the screen doesnt work )=

Maybe if i install a rom from another model like mini or live with walkman

I thought that because whent the problem starts i change my build prop to make run a wt19 rom! with the boot_official_port_mango kernel, maybe my phone thinks its another phone xD
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dv2y:
Well, you can always restore your phone with the Sony app and start again.

Anyway, I don't think its a good idea to try to use a ROM made for another device.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
I read in other post i have to flash it via seus

Do you know where i can download it?

I just found pc companion
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dv2y:
On PC Companion, start the "Support Zone" and you can restore from here. I think Sony dont support SEUS anymore, but you can find it in some forums or download sites.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gandhar:
here's SEUS

http://dl.dropbox.com/u/63607856/temp/Update_Service_Setup-2.11.7.13.exe

btw i am not sure that SEUS works with unlocked bootloaders, still no harm in trying.. good luck
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Kobzar666:
Fix

Try the fix from here

It helps me.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
Thanks Kobzar666

But its is a fix for st15

lunatic2nuts :

-STEP 1: Install lastest firmware .62 for st15i. - use Flashtool

-STEP 2: Then via CM from zip install hybrom_v10. for minipro (sk17i)

-STEP 3: Then again flash lastest firmware .62 for st15i

And in future be carefull, and stay away from minipro ROMs

so i have to interchange i mean

-STEP 1: Install lastest firmware .62 for sk17i. - use Flashtool

-STEP 2: Then via CM from zip install hybrom_v10. for minipro (st15i)

-STEP 3: Then again flash lastest firmware .62 for st17i

someone can upload HYBROM v10

the files in the official post are private :eek:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Someguyfromhell:
Doesn't have to be Hybrom v10. It is a rare solution anyway...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
so i can flash any rom just have to be be for st15??
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] BlackArtsInc:
Something like that happened to me with an X8 with unlocked bootloader and custom ROM.

Everything was fine for a month and then literally out of nowhere the phone s speaker stopped working! Just like that! No alarms,no ringing...nothing!

Before throwing away the phone,I gave it a shot and re flashed stock locked bootloader and ROM and everything started working again!

I then sold it and got a mini! :-D

N.

Sent from one of my 4 iPads.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] R10MaRiOo:
I Fix It!!

Thanks for everyone who try to helps me, I fix it flashing it with wotan server, yes i have to buy a credit! But now everything works again :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] KhemaraS.:
Try to reflash firmware via wotan client
[Samsung Galaxy Nexus] patalo:
I got this much today and I feel happy with it. I got up at 6, had school and text in crappy service for whiles at a time. I did charge It once but for like ten minutes. Stock everything, do I get good battery? :D
[Samsung Galaxy Nexus] Ruxin:
It is possible to get better battery performance than that, but as long as it's suitable for what you need it for, then that's the important thing.

If you're interested, there's always lots of information in threads about custom ROMs and custom kernels regarding the amount of battery people manage to wring out of their phones.
[Samsung Galaxy Nexus] brianisme:
Could be improved. Have you checked your phone for wakelocks to see if there is any apps or services eating up unnecessary battery? Try flashing a kernel/ROM as well. Highly recommend Franco's kernel.

These are screens captured this evening. Using Franco's r121 kernel and stock ICS IMM76I on stock 1750mAH battery.
[Samsung Galaxy Nexus] patalo:
Thank you! Will try it. Can I just flash in recovery on completely stock rom? I want to make sure it's compatible
[Samsung Galaxy Nexus] andQlimax:
Look my...everything stock

View attachment 1027825View attachment 1027830View attachment 1027833

But everything depends from ur use

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] The Nexus Project:
1hr 42 minz of screen on time isnt so hot. a 3hr average is considered decent
[Samsung Galaxy Nexus] YoungAceAtlanta:
i wish i could get past 6hrs of battery life with playing music.. im thinking about buying a extended battery

and yes im using Franco m3, AOKP 34
[Samsung Galaxy Nexus] martonikaj:
Seriously. His signal was pretty ****ty over the course of the battery though.
[Samsung Galaxy Nexus] HeCareth:
on

Yeah everyone is comparing apples and oranges, Wifi and Wireless, LTE and GSM, etc..

Yes you will get almost 2 days of battery life if you are on a strong WiFi signal the majority of the time. If you understand wireless technology it all makes sense. Regardless of the signal wifi or network connection when the signal is weak the phone is using more power to keep the connection alive. In turns of power usage Wifi uses less power than 3G which uses less power than 4G. For LTE devices here usually how your battery life ranks 1 being the best.

1. WiFi signal 4-5 Bars

2. WiFi signal - 2 - 3 Bars

3. 3G Signal - 4-5 Bars

4. 4G Signal - 4-5 Bars

5. 3G Signal - 2-3 Bars

6. 4G Signal - 2-3 Bars
[Samsung Galaxy Nexus] bloodydamnhell:
I don't know yet about the Nexus specifically, but in most cases it's much easier on the battery to idle on UMTS than WiFi. However, since most of us have our phones in constant contact with the Googleplex, there's a fair amount of data transfer when the phone is otherwise idle. That muddies the waters quite a bit.

It also depends to a large degree on whether your AP can allow WiFi clients to sleep like they do on the cellular networks or not. I'm not positive about cdma2000, but in GSM and UMTS the phone spends most of its idle time with the radio off. It only has to wake up every 5-10 seconds to listen for pages from the network.

Some WiFi APs have working 802.11e WMM, but others are broken. Presumably anything modern is more likely to have working power save, but it's always been hit-or-miss for me despite the standard being some 7 years old now.

If there's a point to take from this, I guess it's that whether wifi or 3G drains your battery less isn't something you can make a blanket statement about, as with almost everything related to battery life.
[Samsung Galaxy Nexus] case0:
I don't believe that..
[Samsung Galaxy Nexus] HeCareth:
You don't have to take my word for it..http://smallbusiness.chron.com/uses-battery-3g-wifi-27139.html
[Samsung Galaxy Nexus] martonikaj:
Overall, WiFi uses less power than 3G/4G. WiFi uses more "idle" power keeping connected, but much much less "transmitting" power. It transmits for shorter periods of time (short active connection) and over a shorter distance (no power to boost signal), both reducing usage.

Even if it was break-even power wise, you'd rather be on WiFi to save data usage.
[Android Q&A, Help & Troubleshooting] Phr3d13:
Anyone got any themes that they would like to share?
[Android Q&A, Help & Troubleshooting] No4g4Me:
Delete post please
[General Questions and Answers] z33dev33l:
Got a friend that wants to know.
[General Questions and Answers] Ascertion:
If he's a new customer, he can get it for a cent at Amazon.

http://wireless.amazon.com/Samsung-...nt-spring&pf_rd_p=1363335682&pf_rd_s=center-1

If he's upgrading, Amazon's still got it for $149.99.

I just checked Letstalk.com (Walmart) and it's $159.99 on upgrade. You can't beat Amazon's price for new contracts.