Kaik541 has quit [Ping timeout: 244 seconds]
peterperfect has joined #teamhacksung
Kaik541 has joined #teamhacksung
<HillBeast> See this is what we love about Samsung: they can't even spell their own name.
CutMe has joined #teamhacksung
<HillBeast> Rebellos: What do you use to decompile bootloaders? IDA?
<Rebellos> Yes. It's not decompiling at all, it's disassembling.
<HillBeast> Well yeah wrong word.
<HillBeast> I'm assuming you're attempting to unlock it?
autoprime has quit [Ping timeout: 246 seconds]
chrmhoffmann has quit [Quit: Ex-Chat]
Rebell_ has joined #teamhacksung
KhasMek has quit [Ping timeout: 246 seconds]
Rebellos has quit [Ping timeout: 250 seconds]
Charkey has quit [Disconnected by services]
Charkey_ has joined #teamhacksung
done has joined #teamhacksung
autoprime has joined #teamhacksung
autoprime has quit [Client Quit]
UnknownzD has joined #teamhacksung
UnknownzD has quit [Changing host]
UnknownzD has joined #teamhacksung
methril has quit [Remote host closed the connection]
<Kaik541> xplodwild: the gapps you link to in your tf300t thread got deleted
DemonWav has joined #teamhacksung
peterunperfect has joined #teamhacksung
peterperfect has quit [Read error: No route to host]
peterunperfect has quit [Ping timeout: 246 seconds]
DemonWav has quit [Remote host closed the connection]
Rebell_ has quit [Ping timeout: 246 seconds]
<Entropy512> Sasmsung, Samsnug, eh whatever
KillKount has quit [Ping timeout: 248 seconds]
KillKount has joined #teamhacksung
pawitp has joined #teamhacksung
dmp450 has left #teamhacksung ["Leaving"]
<Entropy512> pawitp: Rebellos was looking for you earlier regarding some of the known issues with SD cards listed on the wiki - he's trying to figure out if it's similar to problems he's having with porting Android to the Wave
<pawitp> I don't even know what the problem is
<pawitp> it's just.. slow
<Entropy512> I think he was referring to that "write error on certain SD cards" bullet
<pawitp> that
<Entropy512> oh, it recovers and continues? (e.g. works but slow due to frequent errors?)
<mauimauer> install.c:151: error: undefined reference to 'scan_mounted_volumes'
<mauimauer> d'oh!
lidroid has joined #teamhacksung
moikop has left #teamhacksung [#teamhacksung]
autoprime has joined #teamhacksung
peterperfect has joined #teamhacksung
autoprime has quit [Remote host closed the connection]
peterperfect has quit [Client Quit]
<CutMe> hello
<CutMe> I want to build my app with cm rom.
<CutMe> anyone can tell me what .mk need edit?
autoprime has joined #teamhacksung
<HillBeast> You want it compiled with CM?
<HillBeast> You need to add it to packages I think'
<HillBeast> packages/app
<HillBeast> And add a reference to tell it to compile in somewhere like common.mk or something
<HillBeast> But this isn't really a teamhacksung question/
supercurio has quit [Quit: et Hop !]
g|byers has quit [Quit: Quit X-Chat Aqua For Mac Os X]
psyke83 has joined #teamhacksung
samosaphile has joined #teamhacksung
samosaphile has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
psyke83 has quit [Quit: Leaving]
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
techmik has quit [Read error: Connection reset by peer]
samosaphile has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosaphile has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
techmik has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
DemonWav has joined #teamhacksung
samosa has quit [Read error: Connection reset by peer]
samosa has joined #teamhacksung
DemonWav has quit [Read error: Connection reset by peer]
DemonWav has joined #teamhacksung
samosa has quit [Ping timeout: 246 seconds]
pawitp has quit [Quit: pawitp]
pawitp has joined #teamhacksung
DemonWav has quit [Ping timeout: 255 seconds]
DemonWav has joined #teamhacksung
sticky|away is now known as stickyboy
dhiru1602 has joined #teamhacksung
DemonWav has quit [Read error: Connection reset by peer]
DemonWav has joined #teamhacksung
DemonWav has quit [Client Quit]
stickyboy is now known as sticky|away
besthiroeu has quit [Quit: blah]
besthiroeu has joined #teamhacksung
<ohanar> hey, any can anyone tell me a way to get good values for power_profile.xml?
<pawitp> ohanar: decompile stock apk
dmp450 has joined #teamhacksung
<HillBeast> Anyone got any ideas why I can't get UART output on the Galaxy SL during decompression?
<HillBeast> I've checked uncompress.h
<HillBeast> serial.h
<HillBeast> And I am sure it is set right in the board-latona.c
<HillBeast> Anyone got any ideas?
<dmp450> if I wanted to build a kernel for the S3 from scratch, and I wanted to give it root, what would I have to do? I've ripped apart the boot.img and the ramdisk, but I can't see what I'm supposed to do with the su binary.
xplodwild_work has joined #teamhacksung
<Espenfjo> HillBeast: xplodwild_work is the uart master
<xplodwild_work> I am
<xplodwild_work> on SGS2 and Note at least
<dhiru1602> HillBeast: the last time codeworkx told me that there might be some issues with param.lfs
<HillBeast> An incompatibility with 3.x?
<HillBeast> dmp450: it's set by the default.prop I believe
<xplodwild_work> whats going on with uart?
<dmp450> HillBeast, is it the ro.secure=1?
<HillBeast> I get nothing at all from kernel 3.x
<HillBeast> In the stock kernel, I had to change a bit, like forcing the console to ttyS2, I also had to enable early printk
<HillBeast> But all of that was to get it to display after decompression.
<xplodwild_work> HillBeast: loglevel=?
<xplodwild_work> cmdline should be console=ttySAC2,115200 loglevel=7
<HillBeast> I think it's loglevel=4 set by the bootloader, but I can't change it as I cannot see the Sbl
<HillBeast> I don't even see Uncompressing Linux... booting the kernel
<HillBeast> Which I believe comes before loglevel kicks in.
<xplodwild_work> then something's wrong with your uart, or sw_sel is not 3
<HillBeast> SWITCH_SEL is set.
<xplodwild_work> though sometimes I have to reboot multiple times until I can see something
<HillBeast> It is working on kernel 2.6.35
<xplodwild_work> if switch_sel is set, you should see at least bootloader output
<HillBeast> Yeah that's what annoys me most, I can't...
<HillBeast> With the bootloader, I could at least check a few things.
<HillBeast> And the cable works fine on my G3
<HillBeast> And on my S2 it shows me the modem.
<xplodwild_work> ah
<xplodwild_work> wait
<xplodwild_work> HillBeast: flash a stock rom
<xplodwild_work> *#7284#
<HillBeast> How do you do UART on your S2?
<HillBeast> I'm on stock GB
<xplodwild_work> UART Mode: PDA
<xplodwild_work> then it should work fine
<xplodwild_work> that's one of the thousands samsung dialer codes
<HillBeast> It's already set to PDA.
<xplodwild_work> weird
<HillBeast> As I said, it's working on the stock (well slightly modified to allow UART) kernel.
<HillBeast> How does UART work on the S2?
DemonWav has joined #teamhacksung
<HillBeast> Do you use the external UART from USB?
<xplodwild_work> no
<xplodwild_work> I have a microUSB <=> serial cable
DemonWav is now known as DemonWav|SC2
<HillBeast> Yeah that's what I mean.
<xplodwild_work> then serial to usb
<HillBeast> What's the resistor you use?
<xplodwild_work> 328K iirc
<xplodwild_work> 523K*
<HillBeast> I might try that.
<HillBeast> Oh...
<HillBeast> I think that's what I'm on.
<xplodwild_work> actually that's this thread's OP that made it and sent it to me
<HillBeast> Yeah I'm using 523K...
<HillBeast> Damn so that's not going to help.
<xplodwild_work> but if sw_sel is 3 and UART mode is PDA, then you should have at least bootloader output
<xplodwild_work> maybe you can try with a kernel that works
<HillBeast> Well actually I'm not sure what SW_SEL is set to.
<xplodwild_work> enter bootloader interactive
<xplodwild_work> basically press HOME + POWER
<HillBeast> As I can only see the kernel
<xplodwild_work> this will give you the full output during bootloader init
<xplodwild_work> and keep pressing return on your keyboard
<HillBeast> Let me try that.
<xplodwild_work> (assuming your terminal routes the keypress to your serial cable)
<xplodwild_work> this should give you SBL> prompt
<HillBeast> Nah that didn't work.
<xplodwild_work> you're on a working kernel?
<xplodwild_work> well one that you said that works
<HillBeast> Yes.
<HillBeast> It just goes straight from battery in (with me holding home and power) straight to showing Uncompressing Linux...
<HillBeast> No Sbl> before that.
<HillBeast> I'm convinced Sbl is being output to ttyS0 or S1 or something.
<HillBeast> Not S2
<xplodwild_work> nah
<xplodwild_work> it's on s2
<xplodwild_work> unplug everything
<xplodwild_work> remove battery
<xplodwild_work> plug uart
<xplodwild_work> press home
<xplodwild_work> put battery
<xplodwild_work> if it doesn't boot auto, press power
<xplodwild_work> that gives me bootloader fine
<HillBeast> Yeah it's not working on the SL
<HillBeast> Trying that too doesn't give me the bootloader.
<HillBeast> Le tme try doing it on my S2 to make sur eI'm following the instructions right.
<xplodwild_work> SL works differently maybe
<xplodwild_work> but it 100% work on S2 and Note
<HillBeast> It must be.
<HillBeast> I can't think of any other reason why I can't see the bootloader other than that it's not outputting to the right UART.
<HillBeast> But that makes no sense.
<HillBeast> Why would Samsung do that?
<HillBeast> It means they have no debuggingb in service centres.
<xplodwild_work> I don't think they did
<xplodwild_work> yeah that would piss them for debugging themselves
<HillBeast> Yeah your guide works for my S2
<HillBeast> Which is cool because I didn't know that was how to get outpuit on the S2.
<xplodwild_work> (never ever run "emmc" in SBL btw)
<HillBeast> Yeah I've read it blanks the card or something.
<xplodwild_work> yup
<HillBeast> Also I have the VIS00M eMMC.
<HillBeast> Any reports on if that's the defective one?
<HillBeast> Or a defective one?
dmp450 has quit [Quit: Leaving]
<xplodwild_work> VYL00M is defective
<xplodwild_work> not remember the others
<HillBeast> Okay.
<HillBeast> I still won't risk it.
<HillBeast> Why does the VERSION variable say ' I9000XXIL'
<HillBeast> Samsung retardation?
<xplodwild_work> yeah
<HillBeast> Okay I found something...
<xplodwild_work> they kept the same bootloader
<HillBeast> I was holding down Enter and pressing home while putting the battery in
<HillBeast> And it just sits there at the Samsung/GalaxySL boot logo.
<HillBeast> As in the first thing it shows on screen when turning the device on.
<HillBeast> As if it's sitting in the bootloader.
<HillBeast> But I can't see it.
<HillBeast> Perhaps it receives input, but doesn't show output?
<xplodwild_work> hmm something wrong with your terminal maybe
<xplodwild_work> try to type "boot"
<xplodwild_work> then return
<xplodwild_work> see if it boots
<HillBeast> Nope.
<HillBeast> And reset doesn't do anything either...
<HillBeast> This is bizarre.
<HillBeast> If I hold home on it's own then it boots just normal.
<HillBeast> And space lets it go through
<HillBeast> I tried space as I know that doens't stop my G3 from booting.
<ohanar> pawitp: thanks :)
<HillBeast> So only enter stops it.
<HillBeast> Yeah only enter
<HillBeast> Other keys don't stop it either.
<HillBeast> Only the enter key stops it.
<HillBeast> But if I type any commands, it won't do anything.
<yath> wrong baud rate/parity/start/stop bits?
<HillBeast> oH NO RESET DOES WORK
<HillBeast> Ooops caps
<HillBeast> I typed reset blidnly and it reset
<HillBeast> So it lets me input, but not output
<HillBeast> I suspect boot didn't work because it needs the load_kernel command or whatever it is.
<HillBeast> Can't remember.
<HillBeast> xplodwild_work: Any ideas as to why it only does input not output on the Sbl?
hillerstorm2 has joined #teamhacksung
<xplodwild_work> no idea
<HillBeast> I think it's one of three things:
<HillBeast> Wrong resistor (unlikely)
kalgecin has joined #teamhacksung
<xplodwild_work> since you have input it's unlikely heah
<HillBeast> Broken Sbl with a bad IRQ or address
<xplodwild_work> hmm unlikely too
<HillBeast> Or the USB switch chip isn't switching (also unlikely)
<yath> or your rxd is just broken
<HillBeast> Nah it works from in Android.
<yath> hm
<HillBeast> I can see everything from kernel load.
<HillBeast> Kernel boot onwards is all fine.
<kalgecin> hey guys. anyone ran into guavalib errors while compiling from aosp?
<HillBeast> Lemme try blindly type a few commands like setenv SWITHC_SEL...
<yath> hint: use local echo
<HillBeast> Who?
<xplodwild_work> settings of your terminal
<HillBeast> Force on?
<kalgecin> i'm on 12.04 64bit probably missed some deps? don't see any misses though
samosa has joined #teamhacksung
<Wout`> damn you samsung, I'm seeing devices getting JB left and right
<Wout`> even the i9000
<Wout`> and the best selling phone of last year is getting nothing
lidroid1 has joined #teamhacksung
<kalgecin> hey Wout` those aren't official. i'm not aware of any company release official JB. or any statement on it on that matter
lidroid has quit [Ping timeout: 252 seconds]
<Wout`> I know, but unofficial AOSP is what I want ;)
<Wout`> but for the i9100 it's blocked by the crappy yamaha audio
<kalgecin> i'm trying to work on it but having trouble compilling. once there i'll see what is what and what i can hack in there
JieeHD|Offline is now known as JieeHD
sticky|away is now known as stickyboy
<HillBeast> Okay so I managed to change the SWITCH_SEL, and CMDLINE from the blind console.
<HillBeast> I nearly f**ked up the param because I forgot that it needed the omapfb set by the cmdline
<HillBeast> Luckily I posted my dmesg a while ago and I got my cmdline back from there.
<HillBeast> So now I have loglevel 7 on the phone.
<xplodwild_work> you can recompile kernel with forced cmdline if you bork it
<HillBeast> Yeah that's how I did it before.
<HillBeast> I did CMDLINE_EXTEND
<HillBeast> I had to port that to kernel 2.6.35
<HillBeast> But now I can access Sbl kind of.
<HillBeast> But not see it...
<HillBeast> Know of anyone who would know why this is?
samosa has left #teamhacksung ["Leaving"]
xplodwild_work has quit [Ping timeout: 245 seconds]
kalgecin_ has joined #teamhacksung
xplodwild_work has joined #teamhacksung
kalgecin has quit [Ping timeout: 244 seconds]
kalgecin_ is now known as kalgecin
rtfpessoa has joined #teamhacksung
pawitp has quit [Quit: pawitp]
besthiroeu has quit [Quit: blah]
DemonWav|SC2 has quit [Quit: Leaving]
Charkey_ has quit [Read error: Connection reset by peer]
dhiru1602 has quit [Ping timeout: 244 seconds]
kalgecin_ has joined #teamhacksung
kalgecin has quit [Ping timeout: 246 seconds]
kalgecin_ is now known as kalgecin
besthiroeu has joined #teamhacksung
gladiac1337 has joined #teamhacksung
lidroid1 has quit [Ping timeout: 255 seconds]
lowtraxx has joined #teamhacksung
mavvert has joined #teamhacksung
angelsl has joined #teamhacksung
lowtraxx has quit [Remote host closed the connection]
lowtraxx has joined #teamhacksung
dhiru1602 has joined #teamhacksung
Ingram has joined #teamhacksung
CutMe has quit [Ping timeout: 256 seconds]
lowtraxx has quit [Quit: Ex-Chat]
besthiroeu has quit [Ping timeout: 244 seconds]
datagutt has joined #teamhacksung
besthiroeu has joined #teamhacksung
datagutt has quit [Client Quit]
datagutt has joined #teamhacksung
repnzscasb has quit [Read error: No route to host]
noobnl has quit [Quit: noobnl]
peterperfect has joined #teamhacksung
hillerstorm has joined #teamhacksung
<dhiru1602> Is there no support for BML in the JB recovery CM10?
a90342 has quit [Remote host closed the connection]
a90342 has joined #teamhacksung
peterperfect has quit [Read error: Connection reset by peer]
cdesai has joined #teamhacksung
cdesai has quit [Remote host closed the connection]
cdesai has joined #teamhacksung
lidroid has joined #teamhacksung
besthiroeu has quit [*.net *.split]
gladiac1337 has quit [*.net *.split]
imnuts has quit [*.net *.split]
Entropy512 has quit [*.net *.split]
th3g1z has quit [*.net *.split]
AdamG- has quit [*.net *.split]
clandmeter has quit [*.net *.split]
imnuts has joined #teamhacksung
clandmeter has joined #teamhacksung
th3g1z has joined #teamhacksung
AdamG- has joined #teamhacksung
Entropy512 has joined #teamhacksung
gladiac1337 has joined #teamhacksung
besthiroeu has joined #teamhacksung
martinjlowm has joined #teamhacksung
UnknownzD has quit [Read error: Connection reset by peer]
kalgecin has quit [Ping timeout: 246 seconds]
fmauneko has joined #teamhacksung
done has quit [Ping timeout: 248 seconds]
IamSachin has joined #teamhacksung
kalgecin has joined #teamhacksung
Rebellos has joined #teamhacksung
DarkLegend has joined #teamhacksung
rodel has joined #teamhacksung
peterperfect has joined #teamhacksung
rodel has quit [Client Quit]
fmauneko has quit [Quit: leaving]
kalgecin has quit [Ping timeout: 246 seconds]
kalgecin has joined #teamhacksung
Rebellos has quit [Read error: Connection reset by peer]
Rebellos has joined #teamhacksung
rtfpessoa has quit [Read error: Connection reset by peer]
kalgecin has quit [Ping timeout: 246 seconds]
trackzz has joined #teamhacksung
Turtuga_ has quit [Read error: Connection reset by peer]
Turtuga_ has joined #teamhacksung
brgroover has joined #teamhacksung
brgroover has quit [Quit: Page closed]
moikop has joined #teamhacksung
moikop has left #teamhacksung [#teamhacksung]
supercurio has joined #teamhacksung
supercurio has quit [Changing host]
supercurio has joined #teamhacksung
kalgecin has joined #teamhacksung
lidroid has quit [Remote host closed the connection]
lidroid has joined #teamhacksung
stickyboy is now known as sticky|away
lidroid has quit [Remote host closed the connection]
lidroid has joined #teamhacksung
lidroid has quit [Remote host closed the connection]
lidroid has joined #teamhacksung
<codeworkx> supercurio: hi. how are your sound meassurements going for i9300?
<supercurio> hey codeworkx !
<supercurio> how are you?
<supercurio> codeworkx, I have tons of data & graphs
<codeworkx> fine, thanks. how about you?
<supercurio> cool too thanks :)
<koud_> I like data
<koud_> especially with graphs
<IamSachin> wow, two maestros discussing :D
<supercurio> codeworkx, that lead to some optimizations / modifications, that I shared with wolfsonmicro a few weeks ago
<codeworkx> i'm currently running my opensource audio hal. samsung seems to do heavy equalizing on their hal and messing up low frequencies.
<supercurio> codeworkx, I'm now preparing articles that show differences and explains what it is about
<supercurio> codeworkx, that's not the case
<supercurio> codeworkx, except on speaker and recording
<codeworkx> i'm talking about speaker :-D
<supercurio> the stereo recording path is software-equalized and process with bad taste
<supercurio> ah yes, every speaker is supposed to be EQed
<supercurio> codeworkx, btw I was thinking about working on an optimized processing (DRC+EQ) settings to contribute to your hal
<supercurio> after I saw your tweet
<supercurio> but didn't installed yet CM
<codeworkx> i'm finetuning it today and then i'll merge it in
<supercurio> codeworkx, I believe using hardware features should be better (mostly for battery life) than using software
<supercurio> codeworkx, BTW on Samsung ROM you can easily notice mediaserver CPU usage in battery stats: its when its processing audio for speaker
<koud_> 200usd for gn with little bit cracked screen, is it worth it?
<codeworkx> supercurio: curious what we can get out of this beast
<supercurio> codeworkx, however with new filters APIs it should be possible to setup also in software
trackzz has quit [Ping timeout: 265 seconds]
<supercurio> the only issue with using hardware DRC & EQ for speaker is when you know you have an output path that is speaker + headphone
<supercurio> WM1811 has only 1 stereo DAC
trackzz has joined #teamhacksung
<supercurio> so the EQ & processing will be applied on both speaker and headphones
<supercurio> but it's not so bad, it should happend only when you have a notification
<Wout`> supercurio: do you have friends at Yamaha by any chance? :P
<supercurio> Wout`, I had contacts with them (preparing NDA setup etc) at first, then no answer anymore after I worte the audio review for Anandtech ^^
<supercurio> I guess their interest in critic and feedback was not so sincere after all
<supercurio> codeworkx, anyway you can count on my contribution for the speaker EQ & DRC setup for CM
<supercurio> what Bumble-Bee showed me about the new the new hal is nice
<Wout`> supercurio: ah, so nothing of use in getting i9100 to work on JB? :/ too bad
<supercurio> Wout`, sorry I don't know enough about it to answer your question
<codeworkx> supercurio: :-)
<supercurio> codeworkx, also I'm not sure it will be possible with the HAL configuration
<supercurio> codeworkx, but I shall provide 2 profiles, one for "music" and one more generic that emphasis voice
<supercurio> I don't think the hal provides access to user-customization tho, so.. well, I'll give at least choice to you guys
<supercurio> thing is an EQ & DRC profile optimized for music gives you better bass response and balance between frequencies
<supercurio> but voice, when you listen to podcasts or nativation instruction appear less "lodu"
<supercurio> loud
<supercurio> so.. its really a compromise
rtfpessoa has joined #teamhacksung
rodel has joined #teamhacksung
krarvind has joined #teamhacksung
xplodwild_work has quit [Quit: Page closed]
<krarvind> https://groups.google.com/forum/?hl=en&fromgroups#!topic/android-platform/4qHMBrI88YU, idea on whats causing this? working from aosp source, split the framework.jar due to the too many methods.
<HillBeast> codeworkx: Have you tried UART on the Galaxy SL?
<cdesai> krarvind: you should try moving some other classes
lolwat has joined #teamhacksung
rodel has quit []
<krarvind> @cdesai: k, will try that
<codeworkx> HillBeast: yep. failed
<HillBeast> Did you get 'Uncompressing Linux'
cdesai has quit [Read error: Connection reset by peer]
<HillBeast> Or get nothing at all?
<krarvind> @cdesai: thats the commit i used
<krarvind> and that resulted in the error, i will try replacing video editor with another package
<supercurio> codeworkx, just tell me when you think its time for me to poke the HAL on Galaxy S III for the EQ and i'll work on that
KalimAz is now known as KalimAz|Away
<codeworkx> supercurio: merged the hal in and triggered a build. till now i didn't hear anything bad. but i want to make sure it works like it should. :-D
<imnuts> codeworkx would you be willing to help with jelly bean on the galaxy tab 2?
KalimAz|Away is now known as KalimAz
<imnuts> i was able to get it to build and boot yesterday, but i get nothing on the screen
<imnuts> however, i see setup wizard waiting for me if i capture the screen via ddms
<codeworkx> imnuts: push the cm9 hwcomposer
<codeworkx> imnuts: and it will work
<imnuts> ok, thanks :)
trackzz has quit [Quit: Bye]
<imnuts> i'll give it a shot then, and hopefully i'll actually be able to go through setup wizard
<supercurio> codeworkx, ok so back here
<supercurio> codeworkx, ok so I shall flash a snapshot, see how it is and start poking
<supercurio> codeworkx, did you already explored options or not yet?
lodder_ has joined #teamhacksung
lodder has quit [Read error: Operation timed out]
pawitp has joined #teamhacksung
lidroid has quit [Quit: Leaving.]
sixstringsg|afk is now known as sixstringsg
<codeworkx> supercurio: i did nothing. just throw the proprietary hal away and start doing the opensource hal. took me around 30-40 hours to make all devices working properly including bluetooth, incall and stuff
<supercurio> is the new hal very different from tinyhal?
<supercurio> I see the concepts are similar if not identical
<supercurio> and tinyucm/tinyhal, well it was supposed to be the same effort
maltloaf has quit [Quit: Leaving...]
<supercurio> peterperfect, ok I downloaded the snapshot you linked
<supercurio> peterperfect, I'll try that
<peterperfect> nice
<peterperfect> lets see what you listed on it :)
dmp450 has joined #teamhacksung
IamSachin has quit [Quit: Leaving...]
<supercurio> not all EQ registers are mapped in ALSA controls on Mark brown WM8994/WM1811 driver
<supercurio> if they were it would be straightfoward to enable the speaker EQ, then disable it without any kind of conflict
atinm is now known as atinm|work
<supercurio> basically, the Gain values for each 5 bands (-12 to +12dB) are exposed as controls
<supercurio> but not the (proprietary) coefficients used to set center frequency, bandwidth and FIR filter optimization of those bands
<supercurio> so, that's the challenge here, how to implement in the hal stuff which is not ALSA without making a mess
netmaxt3r has joined #teamhacksung
<supercurio> one option could be to use the default bands configuration, but the result will not be as fine-tuned as expected
<peterperfect> how do we know which coefficients is the fined tuned ones?
<peterperfect> measurement?
<supercurio> yes measurements, listening tests and manual tuning
<codeworkx> supercurio: let's say it's a mixture of wolfsons tinyhal and the galaxy nexus hal :-D
<peterperfect> wolxus hal
<supercurio> codeworkx, oh your implementation is not the same as AOSP / Nexus 7?
<supercurio> Jelly Bean I mean
repnzscasb has joined #teamhacksung
apple has joined #teamhacksung
apple is now known as Guest42201
Guest42201 has left #teamhacksung [#teamhacksung]
<codeworkx> supercurio: ics and jellybean is not much different
Blaguvest has joined #teamhacksung
Guest42201 has joined #teamhacksung
HillBeast has quit [Ping timeout: 246 seconds]
onner has joined #teamhacksung
lidroid has joined #teamhacksung
Guest42201 is now known as kaimyn
kaimyn has quit [Quit: kaimyn]
onner has quit [Client Quit]
Perka has quit [Ping timeout: 248 seconds]
DemonWav has joined #teamhacksung
<supercurio> codeworkx, ok I'll look at the source code instead of asking too many questions ;)
lidroid has quit [Client Quit]
DemonWav has quit [Remote host closed the connection]
Faryaab has joined #teamhacksung
rtfpessoa has quit [Read error: Connection reset by peer]
DemonWav has joined #teamhacksung
IamSachin has joined #teamhacksung
angelsl has quit [Remote host closed the connection]
DemonWav has quit [Read error: Connection reset by peer]
DemonWav has joined #teamhacksung
moikop has joined #teamhacksung
<koud_> is the audio chip that n7use any good?
Blaguvest has quit [Quit: b.vs.s]
<peterperfect> its wolfson i think
<peterperfect> if its wolfson its good
moikop has left #teamhacksung [#teamhacksung]
trackz has joined #teamhacksung
dhiru1602 has quit [Ping timeout: 244 seconds]
rtfpessoa has joined #teamhacksung
<lolwat> peterperfect, external components and pcb layout play a big role in dac sound quality
<lolwat> so it's not wolfson = good
Perka has joined #teamhacksung
<imnuts> well, when you start with a good audio chip, you have a better chance of good sound quality
<supercurio> Realtek ALC 5640,
<lolwat> imnuts, sure :)
<peterperfect> lolwat surely the chip implementation counts a lot on too
<peterperfect> and all its way to software layer too
<peterperfect> but
<peterperfect> if you have a capable chip
<peterperfect> im pretty sure supercurio can revamp its output
<peterperfect> ;)
DemonWav has quit [Quit: Leaving]
<lolwat> "The FiiO E10’s Wolfson DAC chip is rated at 117 dB of dynamic range but the E10 only delivers a modest 98 dB."
<supercurio> FiiO implementations are rarely good :(
<supercurio> lolwat, is it from NwAvGuy?
<lolwat> supercurio, be honest du you think samsung does better in phones?
<lolwat> supercurio, yes
<supercurio> yes Samsung does better
<supercurio> but it's not comparable directly
<supercurio> you know, between a DAC + an amp or a codec with DAC+Amp solution
<lolwat> we are talking about nwavguy :D now I could argue with subjective vs objective
<lolwat> but i don't
<supercurio> nwavguy measurements are awesome
<supercurio> and alaysis as well
<lolwat> i thought he was talking about the output of the dac not the amp in that sentence
<supercurio> ah yes E10 is only a DAC I think
<lolwat> i like nwavguy's blog
<supercurio> its a great source of inspiration
<lolwat> would love to see a sgs2 vs iphone vs somepopularphonewithwolfsondac dac comparison
<supercurio> and he has the *real* measurements tools
<lolwat> yeah
<supercurio> lolwat, yes many would like to see that
<supercurio> lolwat, wolfson proposed me to spend some time in their lab to produce those comparative measurements & analysis
<lolwat> woah
<lolwat> so will do you it?
<supercurio> and when I was there I was trained on the $$$ measurement tools they're using in their lab
<lolwat> cool
<supercurio> so once I'll have a working Voodoo Sound released I shall retun here and do that ;)
<lolwat> so did you actually measure phones yet or only some things to learn the tools?
<supercurio> they could very much do that themselves but they need someone independent for it to be credible
<lolwat> yeah makes sense
<peterperfect> great
<peterperfect> this is very amazing
<peterperfect> high level work
<lolwat> i heard the ti chips (especially twl6400) perform also very well, what do you think are they on the same leage as wolfson=
<peterperfect> omap is devs dream
<peterperfect> ask cody about it
<peterperfect> :P
noobnl has joined #teamhacksung
<supercurio> when I was there I was trained on an "AP2", its dedicated hardware with hardware filters, pre-amp and crazy 140dB SNR ADC
<lolwat> peterperfect, :) yeah ... but how is audio performace
KhasMek has joined #teamhacksung
<lolwat> 140dB SNR ADC <- omg
<supercurio> and during the training we were using a WM8994 dev board
<lolwat> like 100dB isn't audioble already
<codeworkx> yamaha.... HATE HATE HATE
<lolwat> :D
<supercurio> yes but to measure things accurately you need very accurate ADC ;
<supercurio> ;)
<lolwat> that equipment must have an incredible price
<supercurio> yes $30.000 something like that
<lolwat> woah
<peterperfect> strange that yamaha is used to do good audio stuff
<codeworkx> supercurio: any yamaha docs? :-D
<peterperfect> but i think miniaturization process and mobile implementation are not their thing yet
<codeworkx> dunno how we every should manage to write a hal for this thing
<codeworkx> without any infos
<supercurio> codeworkx, none at all :/
<supercurio> codeworkx, did you managed to get contact with them, sign an NDA?
<codeworkx> so... get mixer states from stock rom for every case
<codeworkx> and do try&error
<codeworkx> supercurio: they don't answer :-D
<supercurio> codeworkx, sorry they might have stopped comminication with third party after anandtech articles
<supercurio> codeworkx, coz I know i came back to them via Samsung and.. not neccesarily in good terms
<supercurio> codeworkx, oh the contact I had, you know
<peterperfect> well..thats a clever solution from them...i do crap stuff, so i dont talk to anyone no more
<supercurio> codeworkx, I called directly in Japan :D
<supercurio> but it was just after Galaxy S II release
<supercurio> codeworkx, did you got an answer or nothing at all ever?
<codeworkx> nothing at all
<supercurio> ok heret's the guy you can try to contact:
<supercurio> Susumu Kawashima
<supercurio> susumu_kawashima@gmx.yamaha.com
<supercurio> he's also on twitter: https://twitter.com/Torakawas
<codeworkx> thanks
<supercurio> and another email for him if the first one doesn't work: kawasima@emi.yamaha.co.jp
<supercurio> the message he sent me back then: http://pastie.org/private/i6ro6989ux3locmwwplka
<supercurio> but NDA.. well at that time I wasn't much interested, I only wanted to report issues with their codec & implementation not sign anything
<supercurio> so they could fix stuff before being exposed in the review
Perka has quit [Ping timeout: 260 seconds]
<supercurio> its his interest to receive more love from CM instead of "crappy proprietary drivers" comments so I hope he will be smart enough to answer
<codeworkx> supercurio: mailed. let's see what happens
<supercurio> cool
<codeworkx> hope the @cyanogenmod.com does magic :-D
<supercurio> last mail I sent him was 14 october 2011, teling him "I wrote the review (link)", please tell me if you're still interested in an NDA. No answer :p
<codeworkx> :-D
<codeworkx> i blamed you in the public, wanna work with me???
<peterperfect> :D
<peterperfect> ahaha
<supercurio> well, reaction from Wolfson and samsung was was pretty different back then, it was "thanks" instead
Perka has joined #teamhacksung
<supercurio> you know thanks for identifying flaws so we can improve or fix
<imnuts> codeworkx for the galaxy tab 2, are you using 4.0.3 proprietary files, or those from the 4.0.4 update?
<koud_> I really hope yamaha sees this as a chance to get some more cred in the dev community
<koud_> if they really do answer and deliver something useful
GTI9100 has joined #teamhacksung
<GTI9100> hey
<GTI9100> Anyone there?
Perka has quit [Ping timeout: 248 seconds]
<mauimauer> no
<koud_> if they play their cards right probably some tech blogs will write about that, could be good exposure
<supercurio> koud_, yes if they didn't decide "do not talk to hackers/OSS devs anymore ever" after reading critics in forums
<koud_> supercurio: well that is always the fear
<GTI9100> I noticed CM10 development has begun on GT-I9100G, any update for GT-I9100 considering it is the main international version.
<koud_> I think in general japanese companies are bit more afraid of that
<supercurio> koud_, manufacturers are very much afraid of the bad press or potential backfire, so except if somone inside is really pushing to open doors most prefer just not answering or interfering at all
<koud_> supercurio: and japanese corperate culture does not really encurage someone to push for anything :P
<supercurio> koud_, yep
<koud_> except maybe push themself to work harder :P
<codeworkx> GTI9100: move to #teamhacksung-support
<GTI9100> will do
<supercurio> koud_, if I remember correctly Susumu Kawashima spent time in the US and has a different culture
GTI9100 has quit [Client Quit]
<supercurio> koud_, or at least understands it, but guys like that in big corporation always have to fight internally and have little support from their colleagues, not seeing the point
<koud_> I hope they can see the good wibe wolfosn got
<koud_> from delivering the good to developers
<koud_> and how samsung and others create dev boards
<koud_> it is almost a must in the chip world
<supercurio> yes even if they're not praised for audio quality (they really have been bashed very hard for it)
<supercurio> they can make an honorable come back with drivers & docs
<koud_> yeah hope so
<koud_> and by now I think this chip should not be that secret
<koud_> getting bit old no?
<koud_> don't really know life of audio chips though
<supercurio> there's nothing secret about how to driver this chip
rtfpessoa1 has joined #teamhacksung
<koud_> speakers seems to live forever :P so might be same for audio chips
<supercurio> I mean, the driver is a bit strange
<supercurio> because it's a complete framework on top of ALSA (or behind alsa)
<koud_> I wonder if the samsung devs complained
<supercurio> it translates ALSA controls, via a bunch of layers into different hex values sent to the chip directly via i2c
<koud_> when working with it
<supercurio> that's why the driver is 1.5MB of C code ^^
Perka has joined #teamhacksung
<koud_> wow
<supercurio> it must be machine-generated, by a software building automatically drivers for many chips and several OSes
<supercurio> based on defined chip specs
<koud_> hmm
<koud_> does not seem very flexible
<supercurio> then guys from Yamaha come 2-3 months to work with the manufacturer for the hardware/software integration
<supercurio> messing with things here and there, not neccesarily in a "clean" way (hence the various ioctl added to the driver to make it work on the real device)
rtfpessoa has quit [Ping timeout: 240 seconds]
<supercurio> I'm not very optimistic about the outcome of the requests we can send them
<koud_> I can understand that
<koud_> but atleast worth a try
<supercurio> for docs, why not
<supercurio> but for any help concerning the machine-generated drivers...
<koud_> well atleast docs might give some help
<supercurio> codeworkx, what is it that doesn't work?
<koud_> if we have developers willing to work implementing it, and also has the skill implementing it
<supercurio> codeworkx, for ICS you would have to sniff and replicate each ALSA command and re-implement the same thing through the new HAL right?
<supercurio> for each path
<supercurio> (a lot of hard work)
netmaxt3r has quit [Read error: Connection reset by peer]
peterperfect has quit [Quit: Don't push the red button!]
Perka has quit [Ping timeout: 248 seconds]
<codeworkx> supercurio: right
<codeworkx> supercurio: not that hard. start music, run tinymix, copy to meld, diff it, write down
<codeworkx> and that for every case
<codeworkx> takes some hours
<supercurio> codeworkx, sometimes you have precisely timed events, like for DC Servo calibration
<supercurio> and command order to follow
<codeworkx> -.-
<supercurio> I mean sequences
Perka has joined #teamhacksung
<supercurio> so even if it output sound you can have nasty DC offset leaking current, burning speaker or stuff like that (in worst case)
<koud_> they don't put protection in hardware to prevent such things?
<koud_> or they just let software be able to do whatever it wants?
<supercurio> no typically you can burn a speaker (or earpiece, more fragile) with a DC offset. it gets hot and dies
<supercurio> I never tried but wolfson guy said they burned plenty in tests so.. ^
<koud_> :P
<koud_> I am curious how samsung will do for jb update
<supercurio> on Galaxy S I I9000 ? ;)
<koud_> :P
<koud_> that one I know :P
<koud_> do they have contract with yamaha
<koud_> to get support for some time
<supercurio> of course
<koud_> or for each update they pay to get it fixed?
<koud_> ok
<koud_> I wonder how long those contracts are
KhasMek has quit [Read error: Connection reset by peer]
<supercurio> long enough
<koud_> so usually contract expiring is not a cause of no more android updates you think? :P
<supercurio> they're constantly evaluating chips from several subcontractors for new devices anyway
KhasMek has joined #teamhacksung
<koud_> cause for
<supercurio> so if one causes issue with updates.. he will be out of the game and you don't want to be out of the game with samsung
<koud_> that's true
<koud_> the s2 must have done well for yamaha
<koud_> atleast in their bank :P
<koud_> maybe not for press
<supercurio> yes
<supercurio> S2, Galaxy Note.. pretty much everything based on this Exynos version
<supercurio> (Tab 7 Plus, Tab 7.7 ec)
<supercurio> etc
<koud_> out of that hardware maybe note would have the biggest chance of jb update
<koud_> or tab 7.7
Perka has quit [Ping timeout: 265 seconds]
<codeworkx> are the s3 headphones white?
<supercurio> I think so (not 100% sure)
<codeworkx> i've 5 pairs :-D
<koud_> lol :P
<koud_> any better than the s2 pairs?
<supercurio> you can become rich on ebay
<koud_> those sucked
<codeworkx> s2 are best
<codeworkx> s3 are crap
<koud_> really?
<koud_> you liked s3 one?
Ingram has quit [Ping timeout: 245 seconds]
<koud_> eh
<koud_> s2
<codeworkx> i'm not sure if they're from s2 xD
<koud_> I think probably not! :P
<koud_> I have to buy new headphones atleast every 6 month
<koud_> they always break
krarvind has quit [Ping timeout: 245 seconds]
<koud_> whatever brand I buy
<koud_> probably because I fall asleep with them
<codeworkx> ok, the black ones do better
<koud_> black with some silver?
<koud_> I think thats how the s2 ones looked like
<supercurio> koud_, every earphone are fragile.. no matter the cost :/
<codeworkx> yes
<supercurio> codeworkx, do you have a Galaxy Tab 2 as well?
<codeworkx> yes
<koud_> supercurio: yeah I found this out :/ always the cable that broke :/
<supercurio> codeworkx, I bought a cheap 7" 8Gb: bests evey other device in audio measurements :)
<JieeHD> Anyone know how to get around this - error: 'start_index' may be used uninitialized in this function [-Werror=maybe-uninitialized]
<codeworkx> reminds me of something. the 6 gtab2s need audio hal, too :-D
<codeworkx> damn
<supercurio> there's some slight differences in the configuration
<supercurio> like on the output channel mixer
<codeworkx> black != black
trackz has quit []
<codeworkx> this one is definately best
<codeworkx> dunno which device it came from
<koud_> probably with the best device
<koud_> gnexus
<codeworkx> dunno :-D
<supercurio> back to work (display expert, galaxy s iii) later guys!
sticky|away is now known as stickyboy
<koud_> supercurio: good luck :) looking forward to see your work :P
<supercurio> koud_, thanks, looking forward to release this software that's in progress for 1.5year old ^
<koud_> :))
<stickyboy> supercurio: I am going to be in Switzerland next week, gonna check out those Focal Spirit Ones... :)
<stickyboy> Definitely can't buy them in Kenya.
pawitp has quit [Quit: pawitp]
krarvind has joined #teamhacksung
lolwat has quit [Read error: Connection reset by peer]
trinode has joined #teamhacksung
peterperfect has joined #teamhacksung
IamSachin has quit [Quit: Linkinus - http://linkinus.com]
pier|afk is now known as pier
IamSachin has joined #teamhacksung
clarity has quit [Ping timeout: 252 seconds]
clarity has joined #teamhacksung
samosa has joined #teamhacksung
Tom^ has joined #teamhacksung
Perka has joined #teamhacksung
samosa has left #teamhacksung [#teamhacksung]
Rebellos has quit [Read error: Connection reset by peer]
gbyers|2 has joined #teamhacksung
Rebellos has joined #teamhacksung
gbyers|2 is now known as g|byers
<codeworkx> supercurio: one problem on my hal. we've now proper lows and bass. but had to lower speaker volumes otherwise it maybe gets killed. :-D
<koud_> if so it sounds like they had a reason to filter it :P
trackzz has joined #teamhacksung
<codeworkx> koud_: but it sound so much better now
<codeworkx> different world
<stickyboy> If I squint my eyes, the sound quality gets better on Gnex.
<koud_> codeworkx: maybe can make compromise?
<codeworkx> koud_: yep. build stronger speaker in
<koud_> X)
<codeworkx> :-D
<koud_> nokia had some great speakers
<koud_> in some of their phones
<koud_> and I remembering being very impressed with one of the early maemo tablets
<mauimauer> nokia...nokia...i've heard that name before
<peterperfect> btw
<peterperfect> what google is doing with motorola?
<peterperfect> nothing?
peterperfect has quit [Quit: OUCH!!!]
<stickyboy> Google! Set an alarm for tomorrow morning at 7.
<stickyboy> "Setting alarm."
<stickyboy> Hah
<pier> peterperfect: someone replied "patents" to this question
stickyboy is now known as sticky|away
AndChat|22484 has joined #teamhacksung
trackzz has quit [Ping timeout: 265 seconds]
<pier> codeworkx should put some watts on maguro and toro audio too :O
besthiroeu has quit [Quit: blah]
AndChat|22484 has quit [Ping timeout: 265 seconds]
<pier> g'nite ^^
pier is now known as pier|afk
trackzz has joined #teamhacksung
trackzz has quit [Client Quit]
atinm|work is now known as atinm|away
done has joined #teamhacksung
repnzscasb has quit [Read error: No route to host]
trackzz has joined #teamhacksung
datagutt has quit [Quit: Computer has gone to sleep.]
repnzscasb has joined #teamhacksung
JieeHD is now known as JieeHD|Offline
samosa has joined #teamhacksung
samosa has left #teamhacksung [#teamhacksung]
trackzz has quit [Read error: Connection reset by peer]
trackzz has joined #teamhacksung
trackzz has quit [Quit: Bye]
trackzz has joined #teamhacksung
peterperfect has joined #teamhacksung
peterperfect has quit [Changing host]
peterperfect has joined #teamhacksung
peterperfect has quit [Client Quit]
peterperfect has joined #teamhacksung
rtfpessoa1 has quit [Read error: Connection reset by peer]
<Entropy512> <supercurio> you know thanks for identifying flaws so we can improve or fix - does not sound like Samsung at all...
<Entropy512> <supercurio> they can make an honorable come back with drivers & docs - yeah... Samsung doesn't seem to realize that they could turn the whole eMMC mess from a PR disaster into a PR coup with just a little bit of cooperation
<peterperfect> really dont
<Entropy512> and as to Yamaha's driver - either machine-generated, or written by someone from a primitive tribe with no concept of 0
<Entropy512> or on SERIOUS mind-altering drugs
<Entropy512> codeworkx: I can try and resurrect my "improved" audio path debugging patch and clean it up a bit to make it less painful to read
<Entropy512> go/no go?
<supercurio> Entropy512, hehe hi :)
<supercurio> Entropy512, well both Samsung (you know who) and Wolfson were happy with the feedback
<supercurio> Entropy512, for Samsung well it can take ages to get things going in the right direction, but at least they listen
<supercurio> and Wolfson: just awesome and super reactive
<Entropy512> yeah, I have yet to hear anything negative about Wolfson
<Entropy512> as to Samsung... the whole XXLQ5/XWLPM fiasco has really made me lose most hope... The only reason I'm continuing is in the hope that at least some users might be able to have their devices resurrected
<Entropy512> it disturbs me though - even though Samsung claims to have a repair method, their service centers are still just tossing motherboards out and replacing them at great cost to the user if they're out of warranty
<Entropy512> now to dig up that old hacking patch from the micswap days...
<Entropy512> gah where is it
<Entropy512> :(
<koud_> <Entropy512> it disturbs me though - even though Samsung claims to have a repair method, their service centers are still just tossing motherboards out and replacing them at great cost to the user if they're out of warranty <- they should really apologize for this...
<supercurio> ah yes if it's at the user cost its not cool
<Entropy512> this is what bothers me the most about the situation - and why I consider even a 1% damage rate from stock recovery unacceptable - users are being told they have to pay for motherboard replacement in many cases
<Entropy512> yay
<Entropy512> I found my yamaha_debug patch, forgot I was instrumenting gingerbread. :)
<koud_> in general I think samsung is not that great of a company
<koud_> like many big korean companies they have some bribe issues, corrupted
<koud_> family run business
<koud_> just really hoping them to turn to the good side
<koud_> but they seem to stumble often
<Entropy512> I think part of it is a lack of understanding about how to look good in the eyes of Western customers
<Entropy512> especially the US
<koud_> yeah
<Entropy512> hiding your mistakes is seen by US customers as "cover-up" - that's a VERY dirty word here
<Entropy512> making a mistake, and then taking steps to correct it - most customers will forget the mistake, and remember how you handled it
<Entropy512> because it's assumed - everyone makes mistakes
<Entropy512> how you deal with them is what sets the good companies from the bad
<koud_> and I don't think they realise that even though they pretty much run different departments as different competing companies
<koud_> it still hurts their other branches when someone mess up
<Entropy512> yup - except for those that are themselves employees of megacorporations with similar issues
<Entropy512> they are simply seen as "Samsung"
<koud_> :P
<Entropy512> but even as an employee of a huge corporation that has occasional infighting - even my company is nowhere close to as bad as they seem to be with some issues
<koud_> also I think samsung is not used to be in spotlight like this
<koud_> in the days of flip phones and tvs
<koud_> it was not the same fan hype
trinode has quit [Read error: Connection reset by peer]
<koud_> but if korea has one thing that is similar to US it would be cellphone lockin :P
<koud_> 2 year contract and cheaper phones :P
<koud_> way worse than US :P
peterperfect has quit [Quit: Depression is merely anger without enthusiasm]
<Entropy512> yeah... They're not used to Android, where you're gauged against Nexus for quality and hackability
netmaxt3r has joined #teamhacksung
<Entropy512> they're in bad shape if none of the next Nexus series of phones come from them
<Entropy512> it says to people "samsung botched it bigtime"
<Entropy512> especially with Google pushing the Nexus a lot harder than they used to
<koud_> I am hoping for asus making nexus phone
<koud_> asus and google seems like good couple
<koud_> in general I like TW companies more than korean :P
<Entropy512> Yeah, however Asus has little phone experience - could be awesome, could be fail. However, in general, Asus DOES have a very good hardware quality track record
<Entropy512> As much as I'd miss AMOLED
<Entropy512> If it were OMAP-based or possibly even Tegra, I'd go for an Asus Nexus
<Entropy512> OMAP5 Nexus = TAKE MY MONEY
<koud_> :P
<koud_> same here
<koud_> I am bit afraid of tegra
<Entropy512> same
<koud_> I trust their engineers
<Entropy512> even if it were another Samsung Nexus - as long as it's Nexus
<koud_> not their head though
dmp450 has quit [Remote host closed the connection]
<koud_> they are too closed
<koud_> yes
peterperfect has joined #teamhacksung
<koud_> maybe I like asus more because I keep seeing asus sweden active on swedish forums and social media
trackzz has quit [Quit: Bye]
<koud_> and give people early builds to xda guys
<koud_> to get feedback
<koud_> wish I could see samsung do that, instead of just retweeting people praising them
<Entropy512> Asus is giving early builds too?
<koud_> that's what I have heard
<Entropy512> Sony is, if Sony had better hardware I'd definitely give them a try
<Entropy512> They opensourced their sensor HAL too
<Entropy512> but they're mostly Qcom
<Entropy512> :(
<koud_> Entropy512: I am afraid it was ericsson that did it :/
<koud_> could possibly go away now when they move to japan
<Entropy512> Yeah. I'm kind of watching them to see if things continue or they become "typical Sony"
<Entropy512> I probably would've bought one of their phones as a hacktoy if not for my worry they'll regress
<koud_> i feel just ericsson would have been better at phones
<koud_> but then again I am baised
<Entropy512> after all their tablet divison is apparently awful
<koud_> from sweden and ericsson is big part of my university town :P
<Entropy512> :)
<koud_> my mom got xperia s
<koud_> seems like nice phone
<koud_> except for horrible capacative buttons
<koud_> impossible to touch
<Entropy512> buttons had bad reviews I remember
<koud_> yeah, but i belive they were too kind
<koud_> those buttons are totally useless
<koud_> I have 20% success rate pressing them
<Entropy512> whoa
<Entropy512> what is all this shit in mcdebuglog.c and how do I turn it on?
gbyers|2 has joined #teamhacksung
g|byers has quit [Ping timeout: 252 seconds]
<Entropy512> ok that shit is very broken
<athurh> new kernels for the masses
<Entropy512> ?
<athurh> 3.0.37 and 3.4.5
<Entropy512> ah