Hi guys!
After receiving a lot of request to support Galaxy Player lines I decided to buy a Galaxy S Wi-Fi 4.2 in order to provide a quality Voodoo Sound support for this device.
I don't know yet if I'll do the same for 4.0, 5.0 and previous device, with your help maybe − usually I prefer owning devices to be sure to provide good support and solid fully tested update.
I've just received it (it's not even rooted) I'm convinced its a great platform already.
Really accessible price, zippy system, reasonably good IPS display for the price providing an okay color rendering and of course a lovely WolfsonMicro audio codec: I like it!
Too bad my unit is defective because only one speaker of the two works so I'll have to return it, but I figured I could say hello to you guys
If you have questions and requests, I'm listening.
Sorry I don't have an ETA yet, sometimes I'm slow, but I know is that I'll do it right.
EDIT:
Eww just noticed, a required kernel config option (KALLSYMS_ALL) is missing which make the port hazardous.
Maybe it will not be possible eventually.
So to be clear, its possible it won't happen. I don't know yet.
EDIT 2:
Listening tests gave me the impression it doesn't sound as good as I expected from this codec so I didn't wait and measured the output.
THD and IMD+Noise levels are the highest I found on any WM8994 / WM1811 device so far, jitter is present too.
0.017% THD instead of 0.011%
0.019% IMD+Noise instead of 0.012%
.. and that's enough to sound off to my ears.. f*ck my life.
RMAA measurements for Galaxy S Player 4.2 Wi-fi
Nice, thanks for the support. I don't own a 4.2 but this is great. Hope you get them some nice sound improvement.
We do have some voodoo port for the 4.0 (as it have the WM8994) but I don't know if it's really it's true power that it's revealed here. It should have the same config because the WM1811 for the 2.6 kernel uses the same kernel drivers as the WM8994. Also thanks for your consideration! :good:
Also isn't it possible to add the KALLSYMS_ALL config option?
zaclimon said:
We do have some voodoo port for the 4.0 (as it have the WM8994) but I don't know if it's really it's true power that it's revealed here. It should have the same config because the WM1811 for the 2.6 kernel uses the same kernel drivers as the WM8994. Also thanks for your consideration! :good:
Also isn't it possible to add the KALLSYMS_ALL config option?
Click to expand...
Click to collapse
Well my long term project is a fully parametric EQ with some ambitious volume and dynamic range management stuff so I rewrote the whole thing from scratch in this purpose.
Its very complex and takes a hell lot of time but eh, why not.
However after listening tests and then measurement I'm not too sure the hardware implementation on this device is worth it and probably not the sound quality I expect for "Voodoo Sound".
So, I don't know.
For KALLSYMS_ALL, it's what allow to insert the driver in memory − at the right place.
As my target is standard firmware & kernel + root only, it compromises severely the feasibility.
Lots of doubts as you can see so far!
I'm still searching a way to root the 4.2 I have without flashing anything as I have to send it back because of the faulty speaker.
Rooting will allow me to prototype Voodoo Sound change and measure if the sound quality can reach requirements or not.
supercurio said:
Well my long term project is a fully parametric EQ with some ambitious volume and dynamic range management stuff so I rewrote the whole thing from scratch in this purpose.
Its very complex and takes a hell lot of time but eh, why not.
However after listening tests and then measurement I'm not too sure the hardware implementation on this device is worth it and probably not the sound quality I expect for "Voodoo Sound".
So, I don't know.
For KALLSYMS_ALL, it's what allow to insert the driver in memory − at the right place.
As my target is standard firmware & kernel + root only, it compromises severely the feasibility.
Lots of doubts as you can see so far!
I'm still searching a way to root the 4.2 I have without flashing anything as I have to send it back because of the faulty speaker.
Rooting will allow me to prototype Voodoo Sound change and measure if the sound quality can reach requirements or not.
Click to expand...
Click to collapse
The project seems big indeed. I would speak french if I could (would be better) but I think in your case it would be good to flash a custom kernel, then root it and then reflash the stock one. Also just knowing, does the I9300 have voodoo sound with them? It could explain a bit of why the YP-GI1 is not that good with the sound (they do have the same chip as far as I can see).
zaclimon said:
The project seems big indeed. I would speak french if I could (would be better) but I think in your case it would be good to flash a custom kernel, then root it and then reflash the stock one. Also just knowing, does the I9300 have voodoo sound with them? It could explain a bit of why the YP-GI1 is not that good with the sound (they do have the same chip as far as I can see).
Click to expand...
Click to collapse
WM1811 is capable of excellent audio performance if the hardware implementation allows it, you can compare YP-GI1 measurements with Nexus 10 ones.
Flashing a custom kernel, hmm as there's no way to return to stock it won't do the trick for me :/
Rooting this device seems like a nightmare without flashing uncertain modified firmware and having no way to go back to stock.
I guess this is not a good platform for Voodoo Sound deployment and will probably just return the device, not matching the requirements in terms of audio quality, ease of rooting and driver maintenance ability.
supercurio said:
WM1811 is capable of excellent audio performance if the hardware implementation allows it, you can compare YP-GI1 measurements with Nexus 10 ones.
Flashing a custom kernel, hmm as there's no way to return to stock it won't do the trick for me :/
Rooting this device seems like a nightmare without flashing uncertain modified firmware and having no way to go back to stock.
I guess this is not a good platform for Voodoo Sound deployment and will probably just return the device, not matching the requirements in terms of audio quality, ease of rooting and driver maintenance ability.
Click to expand...
Click to collapse
Yeah well it took some time just to make the device rooted soo... But I do think we have some potential here but because of the lack of devs working with this particular device, the task is a bit harder. You could try a port for the 4.0 the 4.2 port what do you think?
zaclimon said:
Yeah well it took some time just to make the device rooted soo... But I do think we have some potential here but because of the lack of devs working with this particular device, the task is a bit harder. You could try a port for the 4.0 the 4.2 port what do you think?
Click to expand...
Click to collapse
Yea too bad there's no full firmwares available.
Mine is an XXLC3.
My priority is audio quality so it's not really about porting code.
Isn't 4.0 discontinued?
supercurio said:
Yea too bad there's no full firmwares available.
Mine is an XXLC3.
My priority is audio quality so it's not really about porting code.
Isn't 4.0 discontinued?
Click to expand...
Click to collapse
Ok I see, yeah as far as I know, the 4.0 is discountinued but I think you can find some at some shops in internet.
zaclimon said:
Ok I see, yeah as far as I know, the 4.0 is discountinued but I think you can find some at some shops in internet.
Click to expand...
Click to collapse
Okay, I looked for other easy rooting methods.
I could make a cf-root equivalent with 2 devices but I don't have 2 devices, and the device I have is faulty (dead speaker) so I can't modify it before returning it.
Audio quality doesn't seem promising enough, kernels symbols are missing.
I'll ask the seller a return & refund, sorry guys − project canceled so far: FAIL on each most important requirements with this device, I'm disappointed
supercurio said:
Okay, I looked for other easy rooting methods.
I could make a cf-root equivalent with 2 devices but I don't have 2 devices, and the device I have is faulty (dead speaker) so I can't modify it before returning it.
Audio quality doesn't seem promising enough, kernels symbols are missing.
I'll ask the seller a return & refund, sorry guys − project canceled so far: FAIL on each most important requirements with this device, I'm disappointed
Click to expand...
Click to collapse
When you speak for 2 devices, you speak about the 4.0 and the 4.2? If yes the 4.0 can even be rooted with superoneclick (if it's not 2.3.7) If it is, just flash a custom kernel and it should be good (it's a france rom and kernel so if you want to come back, you should have no problem).
Anyway, good luck. :good:
zaclimon said:
When you speak for 2 devices, you speak about the 4.0 and the 4.2? If yes the 4.0 can even be rooted with superoneclick (if it's not 2.3.7) If it is, just flash a custom kernel and it should be good (it's a france rom and kernel so if you want to come back, you should have no problem).
Anyway, good luck. :good:
Click to expand...
Click to collapse
Concretely, I would have need 2 4.2 devices.
Rooting first one with /system to dump the kernel, rooting the second one with a root-injected stock kernel to dump original system and restore it on the first device.
This method would allow to build a stock+root kernel which is my preferred rooting method if no exploit is available.
4.2 is not vulnerable to exploits currently in town.
supercurio said:
Concretely, I would have need 2 4.2 devices.
Rooting first one with /system to dump the kernel, rooting the second one with a root-injected stock kernel to dump original system and restore it on the first device.
This method would allow to build a stock+root kernel which is my preferred rooting method if no exploit is available.
4.2 is not vulnerable to exploits currently in town.
Click to expand...
Click to collapse
This was the method originally made to root the 4.2, except that they've not made the root-injected kernel (like the cf-root method).
zaclimon said:
This was the method originally made to root the 4.2, except that they've not made the root-injected kernel (like the cf-root method).
Click to expand...
Click to collapse
Yes I'm sure.
However only the US ROM is available around and breaking Wi-fi function for many makes it an unreliable method, stock+kernel would probably be better.
supercurio said:
Yes I'm sure.
However only the US ROM is available around and breaking Wi-fi function for many makes it an unreliable method, stock+kernel would probably be better.
Click to expand...
Click to collapse
Well why don't you try it?
It's a shame to see that this is cancelled. However, what about the 4.2's audio is so intriguing? Maybe there'll be more luck with the other GP variants. Thanks for trying this out, our dev community is pretty small and I always get a great feeling when I see XDA celebrities like supercurio and AdamOutler on this forum. P.S. You wrote RootKepper in your signature instead of RootKeeper. Just pointing that out.
supercurio said:
Yea too bad there's no full firmwares available.
Mine is an XXLC3.
Click to expand...
Click to collapse
I have a Galaxy S Wi-Fi 4.2 XET (Hungarian), but setting it to Italy I could update the firmware throught Odin and save it.
Originally I had XXLC3, updated to XXLF1
You can find this full firmware here: [ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin.
After that I've installed from GP the busybox installer.
supercurio said:
Yes I'm sure.
However only the US ROM is available around and breaking Wi-fi function for many makes it an unreliable method, stock+kernel would probably be better.
Click to expand...
Click to collapse
Result: SGP 4.2 rooted without flashing kernel with only one device and no problem with wifi.
Hope this could help, and it isn't too late
AW: [CANCELLED] Voodoo Sound for Galaxy S Wi-fi 4.2
Ozelot64 said:
I have a Galaxy S Wi-Fi 4.2 XET (Hungarian), but setting it to Italy I could update the firmware throught Odin and save it.
Originally I had XXLC3, updated to XXLF1
You can find this full firmware here: [ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin.
After that I've installed from GP the busybox installer.
Result: SGP 4.2 rooted without flashing kernel with only one device and no problem with wifi.
Hope this could help, and it isn't too late
Click to expand...
Click to collapse
Can you share your rooted lf1 tar? Thanks!
Gesendet von meinem Nexus S mit Tapatalk 2
ChaosChris said:
Can you share your rooted lf1 tar? Thanks!
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2110593
Related
Will the AT&T version of the SG2 get rooted? And also be able to get custom ROMs? Just want to be ready when I pick up my SG2 Sunday. Going to sell my Nexus S.
Sent from my ThinkPad Tablet using XDA Premium App
Anything with running on top of a Linux kernel can be rooted. And being all the sgs2 models were rooted
fairly quickly after they were released i'm sure it won't be long for the ATT sgs2.
Plus the source for the kernel has already been released which will just make it go faster.
Sent from my SAMSUNG-SGH-I897 using XDA App
I give it 24 hours after the first one officially leaves the shelves.
Warning: Created with Swype
joeybear23 said:
I give it 24 hours after the first one officially leaves the shelves.
Warning: Created with Swype
Click to expand...
Click to collapse
Hopefully we don't run into as many issues as the Epic 4G Touch community. Their root method at the moment involves flashing a pre-rooted kernel. And this kernel randomly causes loss of service for many users. Luckily though they're CDMA and we're GSM. I wouldn't be surprised if we were able to borrow the root method from the I9100.
kletiz said:
Hopefully we don't run into as many issues as the Epic 4G Touch community. Their root method at the moment involves flashing a pre-rooted kernel. And this kernel randomly causes loss of service for many users. Luckily though they're CDMA and we're GSM. I wouldn't be surprised if we were able to borrow the root method from the I9100.
Click to expand...
Click to collapse
Being so similar, I'm hoping so too.
kletiz said:
Hopefully we don't run into as many issues as the Epic 4G Touch community. Their root method at the moment involves flashing a pre-rooted kernel. And this kernel randomly causes loss of service for many users. Luckily though they're CDMA and we're GSM. I wouldn't be surprised if we were able to borrow the root method from the I9100.
Click to expand...
Click to collapse
They did not have a working source for the e4gt kernel when rooting that last month. From the messages I've seen posted it looks like source for the ATT gs2 has been released which will make things allot easier - as long as it is an actual working source for a stock kernel for the ATT gs2 (fingers crossed)
Sent from my SAMSUNG-SGH-I897 using XDA App
kletiz said:
Hopefully we don't run into as many issues as the Epic 4G Touch community. Their root method at the moment involves flashing a pre-rooted kernel. And this kernel randomly causes loss of service for many users. Luckily though they're CDMA and we're GSM. I wouldn't be surprised if we were able to borrow the root method from the I9100.
Click to expand...
Click to collapse
We are going to need the same method (flash custom kernel). That's the only way to root the latest version of GingerBread. Hopefully it is done correctly since there are already existing ones from i9100.
joeybear23 said:
I give it 24 hours after the first one officially leaves the shelves.
Warning: Created with Swype
Click to expand...
Click to collapse
I give it less than that .
Hopefully yes! I'm getting this on Sunday, and want to root it ASAP.
i tried to root it with superoneclick, didnt work
Rooted
The only root method I could get to work with the AT&T Galaxy 2 was the kernel method. My AT&T SG2 did work after flashing the non secure kernel and was rooted but I lost my Back, Search and Voice call ability.
Funny, I would think you would lose home and search, considering the international one has a back and menu capacitive buttons but no search button and a physical home...
... ... ...
AFAIK, if we can get a 1:1 dump of the stock kernel image, we can install the community one, install root, su, busybox, etc... and the flash the stock kernel back to restore lost functionality.
Yeah would be nice to have a one click root and root the SGII while your at the store. and tether your ThinkPad tablet.
Sent from my ThinkPad Tablet using XDA Premium App
ROOT
I didn't think rooting like the captivate would work for the SG2..Hopefully their'll be plenty of XDA threads goin on after launch!!!
kletiz said:
Hopefully we don't run into as many issues as the Epic 4G Touch community. Their root method at the moment involves flashing a pre-rooted kernel. And this kernel randomly causes loss of service for many users. Luckily though they're CDMA and we're GSM. I wouldn't be surprised if we were able to borrow the root method from the I9100.
Click to expand...
Click to collapse
I don't think that'll happen. A lot of the problems with the E4GT were not due to the device, but due to inexperience and lack of coordination of some of their developers. I can't believe how long it took them to figure out that you could root a /system dump and use that to extract a kernel from a stock device...
I'm still 50/50 on purchasing a device. If I do and alton987 gets the system dump I asked for in his thread, I think I'll be able to get a stock kernel extracted and /system rooted within a few hours of purchasing - again, if I decide to go ahead.
Might wait too... Luckily I'm in my thirty days. I can get it an play with it. I've heard phone call quality isn't as good ( it is a phone after all). That may be my tie breaker to keep my infuse untill the Galaxy 2 HD comes. Call quality was annoying on my captivate.
mjgspr95 said:
Might wait too... Luckily I'm in my thirty days. I can get it an play with it. I've heard phone call quality isn't as good ( it is a phone after all). That may be my tie breaker to keep my infuse untill the Galaxy 2 HD comes. Call quality was annoying on my captivate.
Click to expand...
Click to collapse
Call quality is MUCH better than my infuse. People can actually hear me!
brock.higdon said:
Call quality is MUCH better than my infuse. People can actually hear me!
Click to expand...
Click to collapse
I have had some people complain about issues hearing me on the Infuse, although on stock ROMs you could disable Samsung Noise Reduction - there might be some tweaking in Gingerbread in this regard. Most GB kernels don't have the A1026 stuff enabled because:
1) It isn't documented at all
2) Device drivers in the root of menuconfig are scary - implies that they were put into the kernel in a half-assed manner
3) It's such a ***** to test it.
If there were a good way to test call quality with the Infuse I'd work the issue more.
THIS FIRMWARE IS A TOY. IT HAS MAJOR ISSUES.
eortizr said:
ICS for i777 is not coming any time soon,,, the so called 'devs' are not smart enough to figure it out...
Click to expand...
Click to collapse
(more quotes to come boys and girls!)
Since apparently, if there isn't a crappy bugridden barely usable ICS firmware somewhere in the development forum, development is "stopped" and "dead" - I figured I'd put up something for the little babies with their sense of being entitled to everything in the world a little firmware to suck on so maybe they'll shut up.
So here is Baby Pacifier - A minimally usable (but at least safe to flash) ICS firmware based from the I9100 XXLPH leak, using most (but not all of) my Sh1tROM tutorial guide to deodex, debloat, and partially Hellraise (CSC only - no modem/audio/kernel)
It contains Chainfire's CF-root initramfs-repacked kernel, so includes functional CWM. Note that internal and external SD cards are swapped compared to normal Samsung CWMs. (This is actually the Android standard going forward and I'll likely change DD soon to reflect this.)
It also includes the softkey workaround akira02rex pointed out in his thread in General (link later...) Note that this workaround is easier said than done, I'll be writing a short guide about my experiences with this later.
http://dev-host.org/HM2 - The usual - Nandroid your current firmware, wipe data in CWM, flash this in CWM.
The softkey hack makes twlauncher look like ass - LauncherPro seems to be nicer in this regard.
HARDWARE TOUCHKEYS DO NOT WORK. CALL AUDIO IS TOTALLY BROKEN IN THE FIRMWARE, AND ONLY PARTIALLY FUNCTIONAL (you need to disable Samsung Noise Reduction on every call) WITH THE ATTACHED KERNEL. THIS WILL NOT CHANGE BEFORE I9100 ICS KERNEL SOURCE IS RELEASED. DON'T ASK FOR FIXES - THESE CAN'T BE FIXED BEFORE THEN.
Data seems to work however with any I777 Gingerbread modem (I'm using UCKH7). This does not flash a new modem.
For some reason, since implementing the CSC hack, no ringtones or notification tones show up for selection on first boot. They do afterwards.
I'll add a few more details later (probably tonight)
When you're done playing, enter CWM and Nandroid back to a usable firmware.
I've attached a hex-edited variant of CF-Root that fixes some of the call audio issues (I can hear my voicemail now, and mic works if you disable Samsung Noise Reduction during a call). However expect some audio issues to remain. See http://forum.xda-developers.com/showpost.php?p=22889718&postcount=26 for more details on how this got haxxed.
I reuploaded the kernel with a fixed updater-script so that it flashes properly now.
For a high-level overview of the hexedit hack - see http://forum.xda-developers.com/showpost.php?p=23005998&postcount=204 - You'll need a Linux box and the ability to read and understand a bash shell script.
First! I might as well play with it for a little.
Sent from my SGH-I777 using xda premium
But entropy when will the kernel source drop? Im just kidding. Gonna flash for ****s and giggles.
Lol love the name...
sent from interspace on my hacked telly...
Entropy I knew you were a great dev. But your patience and dedication make u a good person. Thanks for all u do. May try this when I get home.
Sent from my GT-I9100 using Tapatalk
My touchkeys and audio don't work!
J/K, thanks for this might give it a try just for giggles later on.
I like playthings.
LOL @ Baby Pacifier name.
Been using this for almost 2 hours. It's pretty functional minus the things that are not functioning .
Not sure if I'm digging the touchwiz integration, but this is obviously not polished.
Surprised this thread doesn't have 300 replies and that the dev host servers haven't crashed yet.
Thanks for sharing.
Entropy512 said:
THIS FIRMWARE IS A TOY. IT IS NOT USABLE AS ANYTHING OTHER THAN A PLAYTHING.
(more quotes to come boys and girls!)
Since apparently, if there isn't a crappy bugridden barely usable ICS firmware somewhere in the development forum, development is "stopped" and "dead" - I figured I'd put up something for the little babies with their sense of being entitled to everything in the world a little firmware to suck on so maybe they'll shut up.
So here is Baby Pacifier - A minimally usable (but at least safe to flash) ICS firmware based from the I9100 XXLPH leak, using most (but not all of) my Sh1tROM tutorial guide to deodex, debloat, and partially Hellraise (CSC only - no modem/audio/kernel)
It contains Chainfire's CF-root initramfs-repacked kernel, so includes functional CWM. Note that internal and external SD cards are swapped compared to normal Samsung CWMs. (This is actually the Android standard going forward and I'll likely change DD soon to reflect this.)
It also includes the softkey workaround akira02rex pointed out in his thread in General (link later...) Note that this workaround is easier said than done, I'll be writing a short guide about my experiences with this later.
http://dev-host.org/HM2 - The usual - Nandroid your current firmware, wipe data in CWM, flash this in CWM.
The softkey hack makes twlauncher look like ass - LauncherPro seems to be nicer in this regard.
CALL AUDIO AND HARDWARE TOUCHKEYS DO NOT WORK. THIS WILL NOT CHANGE BEFORE I9100 ICS KERNEL SOURCE IS RELEASED. DON'T ASK FOR FIXES - THESE CAN'T BE FIXED BEFORE THEN.
Data seems to work however with any I777 Gingerbread modem (I'm using UCKH7). This does not flash a new modem.
For some reason, since implementing the CSC hack, no ringtones or notification tones show up for selection on first boot. They do afterwards.
I'll add a few more details later (probably tonight)
When you're done playing, enter CWM and Nandroid back to a usable firmware.
Click to expand...
Click to collapse
I likey the toys
Galaxy S II
I still hope the whiny babies keep making whiny threads to whine about. I like seeing them get trashed.
Jk. I know it drives you crazy. Thanks for your continued hard work.
Sent from my SGH-I777 using Tapatalk
I LOL'd when i saw that quote in the OP. Haha i so remember that being said- glad somebody hung on to that ridiculous statement
sent from my Galaxy SII
Is the link down?
Sent from my SGH-I777 using Tapatalk
Pure win.
We love you, Entropy.
oh man....this rules.
Haha love the name, gonna play with it tonight when the day is over. I still would love to know why the audio routing is so different between us and the i9100. I wonder if sammy planned this all along.
whoops
I'm late i guess! lol. i can download it but its like 1/2MB or something. can't wait to fiddle with it later when the link is working again! thanks
Hmm, I'll check the link tonight... Including checking the MD5sum against what I uploaded.
As to the call audio - I think AT&T seems to really like using some weird call audio processing chip (Audience) that isn't in international devices - I know that was the case on the I9000 vs Captivate - however I'm not sure if we even have that chip in the I777.
To be honest, I haven't paid too much attention to it. It hasn't been a major issue on Gingerbread.
There is just enough audio-specific stuff in the kernel that is different between I9100 and I777 that I'm not going to mess with it until I've got kernel source.
See https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/sound/soc/codecs/mc1n2/mc1n2_cfg.h vs https://github.com/Entropy512/linux...master/sound/soc/codecs/mc1n2/mc1n2_cfg_gsm.h
If DIO port 1 is related to call audio (maybe it is maybe it isn't) - then we absolutely need kernel source to even start working call audio.
Which leads me to - there are Gingerbread experiments I can play with.
According to this, which points to this, says the GSII has it.
Good call, I figured we still had that pesky audience chip. I remember on my captivate which I still have whenever we ran a i9000 rom with i9000 modem it would bypass the audience chip. Wish that was possible on the I777. Still can't see any improvements from that chip on either phone. I wish AT&T would keep there paws off the damn devices.
Also Entropy, any good place I can start reading up on kernel development or at least some place to read up about what is being accomplished in those drivers?
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
danial.aw said:
To us canadian users stuck on the JB modem's.... pretty much the only problem I have noticed by installing the hybrid modem made my morislee is that the autorotation is inverted...
I was wondering if there was a way to make some other xposed module or patch of sort to invert the inversion ....
Not having autofocus while taking a video really blows ...
So if anyone got ideas... do brainstorm please...
Click to expand...
Click to collapse
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Ya I did message him... Unfortunately I believe he is busy
[r.]GimP said:
I would hit up @morrislee and ask what he needs from you to make your own hybrid variant, he cranked out the ones for us after the mako versions extremely fast, seems like a nice enough dude, and this way you wont need any wacky workarounds.
Click to expand...
Click to collapse
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
SnowLeopardJB said:
A hybrid modem will most likely not fix the rotation issues. The issue is with the dsps.* image files in the modem. They are the firmware that is sent to the Hexagon DSP processor, and they are signed, so they most likely cannot be modified. They control sensor function, which includes both rotation and camera autofocus. A userspace patch would be needed to fix autorotation if those firmware files are used.
Click to expand...
Click to collapse
Stuff like this keeps schooling me every day, brain starting to hurt
That being said, I setup an Ubuntu environment earlier today, from one of the guides in chef central, using 12.04 64bit, got all the packages, but i'm terrified to sync a potential 10 gigs of stuff, what exactly should i be syncing to on github for our device, and say for illusion rom to try building from source?
and as I side project today, I nearly got a zte x500 to take a custom rom and recovery from the stock recovery, after noticing ZTE signed their packages with the test keys, just needed to figure out the mmcblk for recovery for the cricket score <edit> I know the syntax that particular updater script needs now, but dont have access to the phone til monday. the person is getting a new phone anyway but it's my pet project to flash a custom rom and recovery from the stock recovery and good practice doing updater-scripts from scratch </edit>
Been a fun day.
danial.aw said:
Ya I did message him... Unfortunately I believe he is busy
Click to expand...
Click to collapse
I am not "busy" haha, just on vacation without my computer out of country
Ahh well hope you have fun and get back to your computer soon times lol
Hey Morris any chance you are back and kicking?
morrislee said:
I am not "busy" haha, just on vacation without my computer out of country
Click to expand...
Click to collapse
Just checking, would it be possible for you to make an inversion patch for your hybrid modem?
Hello XDA
I'm not looking for basic advice on rooting or anything like that since I've been tinkering with mobile phones for quite a while, but I recently got my hands on an i9300. I would just like to know how should I set it up for a daily driver.
How do I make the stock ROM faster? Root and remove bloatware?
Also how can I get more volume out of the phone, my headphones (ATH-M50) barely have any volume at all. I heard these S3s supposedly have great sound quality and something about a high end DAC from Wolfson.
Any help appreciated.
For root read the guides. For sound, e.g. Custom kernels allow tuning volumes.
Start here : http://forum.xda-developers.com/showthread.php?t=2148708
Sent from my GT-I9300 using xda app-developers app
The custom kernels work with the stock ROM? Can you point out a few for me to look at?
Oh, and thanks for the response.
~NEET~ said:
The custom kernels work with the stock ROM? Can you point out a few for me to look at?
Oh, and thanks for the response.
Click to expand...
Click to collapse
Kernels are in the development section index.
http://forum.xda-developers.com/forumdisplay.php?f=1566
http://forum.xda-developers.com/forumdisplay.php?f=1566
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Sound there are a number of sound threads .
~NEET~ said:
Hello XDA
I'm not looking for basic advice on rooting or anything like that since I've been tinkering with mobile phones for quite a while, but I recently got my hands on an i9300. I would just like to know how should I set it up for a daily driver.
How do I make the stock ROM faster? Root and remove bloatware?
Also how can I get more volume out of the phone, my headphones (ATH-M50) barely have any volume at all. I heard these S3s supposedly have great sound quality and something about a high end DAC from Wolfson.
Any help appreciated.
Click to expand...
Click to collapse
I'd suggest to change the stock rom for a lighter one, samsung personalization makes it a little heavy imho
At the moment i'm on Rom Revolution HD v29 (based on official firmware XXEMG4) and is very fast (thanks to some tweaks, like UI fully rendered by GPU, for example)
you can try Viper4Android (i've this installed, both with stock kernel and Boeffla's v3.0 ) and customize a lot of things!
Removed. Lack of interest. MOD: Please remove this thread. Thx
Hi, Im looking for the way to get a real quality sound of the iPhones , Galaxy s with voodoo audio, Galaxy s2 and s3 with siyah kernel (voodoo audio).
I have been testing a lot of mods to get more output level ,editing a file from Android system folder. Now i have louder sound,
but the real problem of the sound output, its a kernel problema.
I found some comunities specialized with sound quality portable devices, and all say the same; the s4 (all models) its a great phone but a **** player ...
they said that the sound have a problem mainly with the low band frequencies., impedance problems,
at practical purposes, you can hear that the audio is not enough `"powerfull" .
Try to listen carefully one of your favorite songs, with your S4 and your Mac, or your pc... (with a good headphones), the sound of the kicks will be less stronger, with less punch...
some people say that the s4 have a great amplifier, but its controlled with a bad software, who manage the sound digitally when should be analogically.
I think that the only way to fix this audio quality is editing the kernel.
i dont know what parameters use the user "Super Mercurio" to create Voodoo Audio, but... it Works and the audio of the S, S2 and S3 Works correctly with it like an iPhone (iPhone,because i dont know why but allways have a great balance between software and hardware).
Siyah Kernel Works good in the s3 model with audio because include Voodoo Audio too. And Siyah is developed by the user Gokhanmoral.
Im trying the imposible to fix this problem but i dont know really what to do...
Do you think that could be something to do , to fix this audio problem with CM (or editing the stock kernel)??
here is one post of audiophiles users talking technically about it :
http://www.head-fi.org/t/655546/samsung-galaxy-s-4
thanks
I think you wrote in the totally wrong thread about this, since this mainly about the voltage problems between the I9506 and N9005 and
I doubt that anyone of us think about the sound quality right now but more about the line "If I test it will it melt my screen?" kind of concern.
I know there are some really awesome audio mods for HTC but since I don't own an Iphone nor will I ever I think this is way way wrong
forum.
/Abs
Besides, the sound in an ajfon is nothing compared to the HD-pack for HTC.
pablogalanmusic said:
Hi, Im looking for the way to get a real quality sound of the iPhones , Galaxy s with voodoo audio, Galaxy s2 and s3 with siyah kernel (voodoo audio).
I have been testing a lot of mods to get more output level ,editing a file from Android system folder. Now i have louder sound,
but the real problem of the sound output, its a kernel problema.
I found some comunities specialized with sound quality portable devices, and all say the same; the s4 (all models) its a great phone but a **** player ...
they said that the sound have a problem mainly with the low band frequencies., impedance problems,
at practical purposes, you can hear that the audio is not enough `"powerfull" .
Try to listen carefully one of your favorite songs, with your S4 and your Mac, or your pc... (with a good headphones), the sound of the kicks will be less stronger, with less punch...
some people say that the s4 have a great amplifier, but its controlled with a bad software, who manage the sound digitally when should be analogically.
I think that the only way to fix this audio quality is editing the kernel.
i dont know what parameters use the user "Super Mercurio" to create Voodoo Audio, but... it Works and the audio of the S, S2 and S3 Works correctly with it like an iPhone (iPhone,because i dont know why but allways have a great balance between software and hardware).
Siyah Kernel Works good in the s3 model with audio because include Voodoo Audio too. And Siyah is developed by the user Gokhanmoral.
Im trying the imposible to fix this problem but i dont know really what to do...
Do you think that could be something to do , to fix this audio problem with CM (or editing the stock kernel)??
here is one post of audiophiles users talking technically about it :
http://www.head-fi.org/t/655546/samsung-galaxy-s-4
thanks
Click to expand...
Click to collapse
Oh, sorry,you're right Absolon, this not the correct thread
however, I'm trying to fix a distortion problem of the ample and DAC , not to boost the sound with eq to get a louder bass,etc…
thanks
pablogalanmusic said:
Oh, sorry,you're right Absolon, this not the correct thread
however, I'm trying to fix a distortion problem of the ample and DAC , not to boost the sound with eq to get a louder bass,etc…
thanks
Click to expand...
Click to collapse
No worries. I never used my phone as a walkman. Ever. My battery can't handle 467 installed programs and then playing music at the
same time
But really, you can't have an Iphone as a reference for sound! Come on! It's not THAT good.
If you really want a reference, go to a audio-shop and listen to some Krell stuff. Then everything sounds bad
And finally, my experience tells me that it's waaay much about what ear-peaces you have. I had, until I of course misplaced them some
really nice ones that cost like an iPod back then. But I'm much for bass. My EQ at home is a V because I hear too well on the midrange
and being this old fart I can still pick up really high freqs. But then I listen mostly to classical music and that has to be flac even if I know
that a CD is not catching it all. That is why my friend went over to real vinyl and radio tubes to get "that" sound. But I rather buy more
disk to my computer(s)
/Absie
I didnt read your life story... but I think it would be great to have some development for our i9506.
Sent from my GT-I9506 using Tapatalk
mezo91 said:
I didnt read your life story... but I think it would be great to have some development for our i9506.
Sent from my GT-I9506 using Tapatalk
Click to expand...
Click to collapse
My "life story" was more for the people wondering where I was. Now they know.
But as I wrote in another post today (somewhere here) I doubt that it's worth it, if someone can't pitch in and do the real work we have to do,
because there is not many keyparts missing between the two phones.
Hi absolon I couldn't read all you wrote but actually I've got a team working on porting cm 11 to the i9506, development hasn't started yet , I'm still recruiting one more dev , if you wanna be in just tell me , your knowledge will be useful for the development .
Sent from my GT-I9506 using Tapatalk
I used to own a note 2 and flashed roms twice a week sometimes twice a day ?
I really miss flashing new roms. ?
Sent from my GT-I9506 using Tapatalk
mezo91 said:
I used to own a note 2 and flashed roms twice a week sometimes twice a day ?
I really miss flashing new roms. ?
Sent from my GT-I9506 using Tapatalk
Click to expand...
Click to collapse
me too... [emoji30]
Gesendet von meinem GT-I9506 mit Tapatalk
can we ask a developer from note3, s4, note2 community to make for us a custom rom? he can create and we test it maybe and give feedback?
Sent from my GT-I9506 using Tapatalk
.....
Absolon said:
I need to get a dmesg (besides the files) from a real v4.3 Knoxed I9506!
Code:
dmesg > /storage/emulated/0/I9506_v4.3_knox_1.txt
Here the problem is that you can't do it as a normal user but has to be root but I think this should work:
Code:
[B]Make sure all is granted and fine [/B]
adb shell
su -
[B][I](grant it in the phone)[/I][/B]
[B]Reboot[/B]
adb shell "su -c dmesg > /storage/emulated/0/I9506_v4.3_knox_1.txt"
[B]or if that doesn't work[/B]
[B][U]adb shell
su -
dmesg > /storage/emulated/0/I9506_v4.3_knox_1.txt[/U][/B]
Want to cry more? Get me that 4.3! (And a copy of Hawkies)
/Abs - Over and out
Click to expand...
Click to collapse
Hi
Okay, just rooted my phone to get you that dmesg thing.
The command that i underlined is the one I used, and it worked fine.
(I can not help you with Hawkies)
https://dl.dropboxusercontent.com/u/3316850/I9506_v4.3_knox_1.txt
Why are I missing the first from my log?
Turbo-fingers
Notfast said:
Hi
Okay, just rooted my phone to get you that dmesg thing.
The command that i underlined is the one I used, and it worked fine.
(I can not help you with Hawkies)
https://dl.dropboxusercontent.com/u/3316850/I9506_v4.3_knox_1.txt
Why are I missing the first from my log?
Click to expand...
Click to collapse
I assume you did grant su in your phone first?
Yes, my bad, replace " with '
Code:
This should be the general syntax: su -c 'command1; command2; .... ; commandN'
The reason why you get it so late is because you didn't catch it fast enough and the ring buffer got full and threw away the first.
The only success I got was with that su command. It was under Linux. Never tried it in Windoze.
It takes some practice so don't be sad. I think that was my 3rd time I managed to catch it fast enough
/Absie
Absolon said:
I assume you did grant su in your phone first?
Yes, my bad, replace " with '
Code:
This should be the general syntax: su -c 'command1; command2; .... ; commandN'
The reason why you get it so late is because you didn't catch it fast enough and the ring buffer got full and threw away the first.
The only success I got was with that su command. It was under Linux. Never tried it in Windoze.
It takes some practice so don't be sad. I think that was my 3rd time I managed to catch it fast enough
/Absie
Click to expand...
Click to collapse
I can´t get the multi command thing to work on windows.
But here is one from 5.980385sec
https://dl.dropboxusercontent.com/u/3316850/I9506_v4.3_knox_8.txt
<6>[ 11.338924] EXT4-fs (dm-0): mounted filesystem without journal. Opts: errors=continue
This is the best yet [ 1.682904]https://dl.dropboxusercontent.com/u/3316850/i9506_v43_2.txt
Edit:
[ 1.646265]
https://dl.dropboxusercontent.com/u/3316850/i9506_v43_3.txt
Edit 2:
[ 1.595058]
https://dl.dropboxusercontent.com/u/3316850/i9506_v43_4.txt
Turbo-fingers with low pressure kick-in
...
Yes a 4.3 knoxed i9506.
The best one yet is with a script manager set to run at boot. It takes at while for my windows 7 to be able to talk to my phone after reboot.
I even tried to see if I could resize the ring buffer to by me more time. But no luck.
if you see my text files size they are smaller then yours, 4.4 may have a larger buffer?
...
Notfast said:
Yes a 4.3 knoxed i9506.
The best one yet is with a script manager set to run at boot. It takes at while for my windows 7 to be able to talk to my phone after reboot.
I even tried to see if I could resize the ring buffer to by me more time. But no luck.
if you see my text files size they are smaller then yours, 4.4 may have a larger buffer?
Click to expand...
Click to collapse
Maybe @DeHAWK could compile a kernel with a 256kb ring buffer since he has a working env?
Try one with a real ext4 for speed as well
/Abs