[REQUEST][ICS]Bezke_XXKP8 Port - AT&T Samsung Galaxy S II SGH-I777

Can someone please port or Hellraise this GSII ICS rom? http://forum.xda-developers.com/showthread.php?t=1393569

I tried Hellraising this Rom about two days ago to no avail... Hopefully someone can port it for us ..

robertmoore208 said:
I tried Hellraising this Rom about two days ago to no avail... Hopefully someone can port it for us ..
Click to expand...
Click to collapse
Bummer I hope someone can do something soon, I feel like our phone is way too awesome to not already have a stable version of ICS.

robertmoore208 said:
I tried Hellraising this Rom about two days ago to no avail... Hopefully someone can port it for us ..
Click to expand...
Click to collapse
Obviously hellraiser won't work, the kernels are incompatible for one thing
Sent from my SGH-I777 using XDA App

International models always come first as manufacturers can do as they please with them and not worry about carrier interference. Devices like ours get official updates after our carrier has their hand in it (mainly to add bloatware and lock us out of certain features they don't want on their network).
Sent from my SGH-I777 using Tapatalk

Nick281051 said:
Obviously hellraiser won't work, the kernels are incompatible for one thing
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Is there no ICS kernel for the i777? Can't we mod the GSII kernel to work on our device? Pretty much the only difference between our devices is the trackpad.

1) Not development
2) Nothing is going to happen until ICS goes official for I9100, try searching

Why is this in the dev forum?? Have you looked/searched through general forum? There is already a sticky on ICS and a thread about CM9. Read through both of those threads and your question has been answered numerous times. NOTHING CAN BE DONE UNTIL OFFICIAL SOURCE DROPS.

DanDroidOS said:
Is there no ICS kernel for the i777? Can't we mod the GSII kernel to work on our device? Pretty much the only difference between our devices is the trackpad.
Click to expand...
Click to collapse
obviously not, have you been reading at all? There's a few more differences than that and the international version doesn't have a tdackpad
Sent from my SGH-I777 using XDA App

Guys the only thing not working if you flash the int version is touch keys and in call audio apart from that if u want a tablet it works perfect.
Also, kk6 modem works with it fine.
Sent from my SGH-I777 using Tapatalk

Sorry if I came across like an a hole lol
Sent from my SGH-I777 using XDA App

akira02rex said:
Guys the only thing not working if you flash the int version is touch keys and in call audio apart from that if u want a tablet it works perfect.
Also, kk6 modem works with it fine.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
And how can those be fixed?
The phone isn't usable without any of them.

Touchkeys and incall audio are MAJOR issues.
Touchkeys are an EASY fix with kernel source - but due to the structuring of the kernel code, they are NOT fixable without it. (Unlike the Captivate/I9000, where I9000 kernels did pass the keycodes on to userland for the extra touchkeys - I9100 kernels don't.)
Working incall audio when the touchkeys are broken is kinda pointless. Also, it's VERY likely that incall audio will require some mc1n2 tweaking to work around the lack of I777-specific audio libraries. (e.g. the "swap the libraries" trick from Hellraiser won't work.)

Entropy512 said:
Touchkeys and incall audio are MAJOR issues.
Touchkeys are an EASY fix with kernel source - but due to the structuring of the kernel code, they are NOT fixable without it. (Unlike the Captivate/I9000, where I9000 kernels did pass the keycodes on to userland for the extra touchkeys - I9100 kernels don't.)
Working incall audio when the touchkeys are broken is kinda pointless. Also, it's VERY likely that incall audio will require some mc1n2 tweaking to work around the lack of I777-specific audio libraries. (e.g. the "swap the libraries" trick from Hellraiser won't work.)
Click to expand...
Click to collapse
Slightly off topic, but why would or what would make Samsung elect to change the way the kernels work like they did from Captative/I9000? I mean the I9100 and I777 are similar(same cpu, etc) like the I9000 and Captivate are.
Btw, I'm sure this is a question you've struggled with too, but wouldn't it be easier for samsung too? One less thing that needs changing

akira02rex said:
Guys the only thing not working if you flash the int version is touch keys and in call audio apart from that if u want a tablet it works perfect.
Also, kk6 modem works with it fine.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Those are 2 pretty big problems. Kk6 works fine if you just want 3g and have no need to use your phone as a(get ready for it) PHONE!
Sent from my GT-I9100 using XDA App

eep2378 said:
Slightly off topic, but why would or what would make Samsung elect to change the way the kernels work like they did from Captative/I9000? I mean the I9100 and I777 are similar(same cpu, etc) like the I9000 and Captivate are.
Btw, I'm sure this is a question you've struggled with too, but wouldn't it be easier for samsung too? One less thing that needs changing
Click to expand...
Click to collapse
short answer: carrier influence
Sent from my SGH-I777 using Tapatalk

iXNyNe said:
short answer: carrier influence
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
If that is really the case, ATT is dumber than I thought(I really thought they were dumbasses already)

Entropy512 said:
Touchkeys and incall audio are MAJOR issues.
Touchkeys are an EASY fix with kernel source - but due to the structuring of the kernel code, they are NOT fixable without it. (Unlike the Captivate/I9000, where I9000 kernels did pass the keycodes on to userland for the extra touchkeys - I9100 kernels don't.)
Click to expand...
Click to collapse
Current CM9 builds are using hacked Gingerbread kernels (correct), and as such we have sources, meaning that even if the Hellraiser hack mods userland files, the touchkeys could be fixed with a kernel mod, correct? I know you won't work on it as its a lot of work for a temporary hack, which I understand. I'm just wondering from a technical perspective if its possible?
Working incall audio when the touchkeys are broken is kinda pointless. Also, it's VERY likely that incall audio will require some mc1n2 tweaking to work around the lack of I777-specific audio libraries. (e.g. the "swap the libraries" trick from Hellraiser won't work.)
Click to expand...
Click to collapse
If it isn't too difficult to explain, what do you mean by "lack of i777 audio libraries"? Do the i9100 and i777 use the same DAC(the mc1n2), and do they use the same audio libraries? Is it just that the use of different libraries would require more in-depth tweaking than Hellraiser does currently, or just an i777 specific build?

jjesusfreak01 said:
Current CM9 builds are using hacked Gingerbread kernels (correct), and as such we have sources, meaning that even if the Hellraiser hack mods userland files, the touchkeys could be fixed with a kernel mod, correct? I know you won't work on it as its a lot of work for a temporary hack, which I understand. I'm just wondering from a technical perspective if its possible?
Click to expand...
Click to collapse
Not unless something has changed - they were using hacked GB kernels and had VERY bad results. Every recent release (up until codeworkx stopped releasing because of the noobs) used an initramfs repack of an I9100 ICS kernel.
If it isn't too difficult to explain, what do you mean by "lack of i777 audio libraries"? Do the i9100 and i777 use the same DAC(the mc1n2), and do they use the same audio libraries? Is it just that the use of different libraries would require more in-depth tweaking than Hellraiser does currently, or just an i777 specific build?
Click to expand...
Click to collapse
Same DAC, but the wiring of inputs and outputs to the DAC is different. This is why microphone audio in calls is screwy when you run I9100 audio libraries on an I777.
The easiest and most robust fix is to swap in audio libraries from an I777 like Hellraiser does. However, since we don't have I777-specific audio libraries that are compatible with ICS, we can't use the easy way out that Hellraiser did.

Related

(Q) i9100 kernal porting

Is it possible to port kernals from i9100 forum to our device? They have so many different kernals and mods that we don't have and it would be nice to get them ported to our devices. Entropy has done as Fantasic job with hellraiser and it have given is the ability to port a large number of roms over in the i9100 forums. The only thing that we are missing that would complete the merge between our device and the i9100 would be kerenls. Is this possible? What are the hardware differences that would cause a problem when trying to do so? Obviously the soft keys and mapping are different but we have a fix for that. Is the processor the same? Any devs out there on our side have any feedback on this?
Sent from my GT-I9100/i777 using xda premium
jgrimberg1979 said:
Is it possible to port kernals from i9100 forum to our device? They have so many different kernals and mods that we don't have and it would be nice to get them ported to our devices. Entropy has done as Fantasic job with hellraiser and it have given is the ability to port a large number of roms over in the i9100 forums. The only thing that we are missing that would complete the merge between our device and the i9100 would be kerenls. Is this possible? What are the hardware differences that would cause a problem when trying to do so? Obviously the soft keys and mapping are different but we have a fix for that. Is the processor the same? Any devs out there on our side have any feedback on this?
Sent from my GT-I9100/i777 using xda premium
Click to expand...
Click to collapse
Mainly a few defconfig tweaks, and also possibly initramfs tweaks.
It should be a matter of taking a defconfig for an I9100 and changing the correct options via "make menuconfig" - don't remember exactly which those are.
I am not sure i know what that involves but how difficult would that be
I've had this phone for a few weeks now and I've been rooting for only 3 weeks and its the greatest mobile experience of my life. The freedom of Android and the versatility and power of rooting makes the SGS2 the all around greatest phone on the planet in my opinion. I'm currently using Unnamed 1.3.1 with Entropy's DD and this combo has been an awesome experience so far. I recently experimented with the Siyah kernel (I9100) and loved the variation of governor choices and the power that the kernel provided. I'm also a huge fan of Entropy's kernel because of the great balance of performance and battery life, however when OC to 1.4 or 1.6, the Siyah kernel provided so much more power based on bench tests. After experimenting for an hour I went back to Entropy due to the issues with the soft keys. If a port of the Siyah kernel is not coming any time soon to the AT&T i777, does anyone know of a patch or mod that can fix the issue with the soft keys when using a kernel like Siyah that's made for i9100 on our AT&T i777 ? Any help or feedback on this issue will be greatly appreciated.
Sent from my SAMSUNG-SGH-I777 using XDA App
kevtn8 said:
I've had this phone for a few weeks now and I've been rooting for only 3 weeks and its the greatest mobile experience of my life. The freedom of Android and the versatility and power of rooting makes the SGS2 the all around greatest phone on the planet in my opinion. I'm currently using Unnamed 1.3.1 with Entropy's DD and this combo has been an awesome experience so far. I recently experimented with the Siyah kernel (I9100) and loved the variation of governor choices and the power that the kernel provided. I'm also a huge fan of Entropy's kernel because of the great balance of performance and battery life, however when OC to 1.4 or 1.6, the Siyah kernel provided so much more power based on bench tests. After experimenting for an hour I went back to Entropy due to the issues with the soft keys. If a port of the Siyah kernel is not coming any time soon to the AT&T i777, does anyone know of a patch or mod that can fix the issue with the soft keys when using a kernel like Siyah that's made for i9100 on our AT&T i777 ? Any help or feedback on this issue will be greatly appreciated.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
There is already a patch for this included in Hellraiser package that Entropy made. There is also a patch for the home button haptic feedback.
Sorry if I sound really dumb asking these questions as I'm definitely a noob when it comes to rooting. However, isn't Hellraiser a rom for i777? So if I want to use the Siyah kernel with the soft key patch it would have to be with Hellraiser? The reason I'm asking is because I really love Unnamed so far. Its my first rom and its so smooth and efficient. Also, what if I wanted to try out a particular rom for i9100 on our phone? Same soft key issue would arise right? It seems from the OP that a possible solution also has to do with Hellraiser. If this is true I'm confused as I thought Hellraiser is a particular rom for i777. Please elaborate.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hellraiser is a porting tool to take ROMs from I9100 to I777. Among other things, it replaces the kernel.
To get the touchkeys to work right when trying to compile an I9100 kernel for I777, at the very least you need to set "Target Locale" to NAGSM in the System Type menu within "make menuconfig"
You will also need to set CONFIG_MAX8922_CHARGER in the defconfig. I forget where in "make menuconfig" this is buried
You will also have to choose an appropriate initramfs - the one that comes with the kernel you're porting may work. Also, the approach various devs use for pulling in the initramfs differs from kernel to kernel. Many devs don't even provide their initramfs in their source repos (good luck pulling a clean one from SiyahKernel... LZMA/XZ compression makes this nearly impossible.)
Thanks for the insight Entropy but I'm way too raw in rooting to grasp some of the stuff you are trying to explain. Also I want to say thank you for the awesome work on your daily driver kernel (which i'm happily still using). In regards to Hellraiser, what do you mean by "replacing the kernel"? Do you mean that Hellraiser will allow i777 users to use i9100 roms with a compatible kernel of their choice? Finally, what are the chances of some developers porting a i9100 kernel over to i777 like Siyah? Based on your previous post, it shouldn't take too long right? I believe this would breathe extended life and possibilities into the i777.
Sent from my SAMSUNG-SGH-I777 using XDA App
kevtn8 said:
Thanks for the insight Entropy but I'm way too raw in rooting to grasp some of the stuff you are trying to explain. Also I want to say thank you for the awesome work on your daily driver kernel (which i'm happily still using). In regards to Hellraiser, what do you mean by "replacing the kernel"? Do you mean that Hellraiser will allow i777 users to use i9100 roms with a compatible kernel of their choice? Finally, what are the chances of some developers porting a i9100 kernel over to i777 like Siyah? Based on your previous post, it shouldn't take too long right? I believe this would breathe extended life and possibilities into the i777.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
What I mean is that Hellraiser takes the kernel from an I9100 ROM and replaces it with an I777 kernel (right now, mine.)
Someone can try porting a kernel if they want, but I have ZERO interest in putting any effort into porting Siyah. Judging by all the problems people are constantly having, half the features are broken. Also, gokhanmoral does not respect the GPL and publish source for his betas, so it's impossible to separate one change from another.
Thanks for the explanation Entropy512. I was able to get in touch with Gokhanmoral and i'm currently testing out a Siyah port for i777 for him now. Regardless of which kernel i'm using with Unnamed rom now, I can not thank you enough for all of the hard work that you've put into your DD kernel. It will always be one of my main kernels. I can not say enough great things about it. I'm just experimenting right now to see if I can get some more power out of this phone at similar frequencies and this is where the Siyah kernel comes into play.
Sent from my SAMSUNG-SGH-I777 using XDA App

[Firmware][Toy][XXLPH]Baby Pacifier LPH 2/23/2012

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?

[Kernel][GB] holoNote Kernel 0.1 (Ghost Touch detection removed)

Notice: Saurom RCV users, there is a fix so that you can flash other kernels. The problem was caused by an incompatible library being flashed over Saurom's RTL modded library. In the future, my kernels will ship without modified libraries, and a cwm zip containing only the libraries will be offered (for those who need them).
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Edit: There also seems to be a pleasant side effect that I hadn't noticed... keyboard input is improved. Makes sense I suppose, since now there isn't this constant check for false touches slowing things down. Let me know if you see this on your device.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Saurom RC5 -- holoNote kernel is bundled already, but if you want to flash a different kernel you must apply a cwm zip containing a RTL modded lib
TPC V2 -- Works fine
Rogers -- Works fine
Kallsyms version of my Kernel is now up (file ending with suffix 'k'). Please confirm that it is working for you guys that use that feature (I do not).
Per request: Version without su/busybox (and install script) is now up. Please NOTE: this kernel does not remove root, just no longer installs root.
An oversight of mine has resulted in android reporting kernel version unavailable. Apps such as cpuspy report correct kernel name/ version.
https://github.com/hololight/sgh-i717-kernel
When you flashed this was it on top of a custom rom or stock? Just trying to decide if I want to flash on top of saurom.
Flashed on Saurom RC4 and it booted fine. It seems I don't have anymore keyboard problems with this kernel either. I can finally type fast again!
Sent from my SGH-I717R using xda premium
As stated above, I have only tested this on stock att rom. That said, as Da_G's kernel works with Saurom, I can not see how this would cause any problems.
As people confirm it works in 'X' situation, I will update the op.
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Any chance of getting this with the kallsysms function that DA_G implemented in one version of his kernel 0.2? Thanks it would allow us more screen improvement with the touchscreentune app available (which works well to re-calibrate the pens offsets btw)?
Heard from:
Saurom RC4 -- Works fine
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
Please hit THANKS button if I help you, I have very low self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
Quick question. Which of the three versions of Da_G's kernel is this from. I'm using his one with the kalysms (so?)
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope to have a version with kallsyms up later today.
Sent from my SAMSUNG-SGH-I717 using XDA
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Kallsyms comming soon.
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
OMG, yesterday i was trying to analyze why my keyboard is missing keypresses when i type quickly and i came to the conclusion that it must be some sort of an accidental touch algorithm that works in the background!
I'm going to check this out!
Thanks!
Op updated with kallsyms support kernel... enjoy.
gonna flash and report back its nice to see another dev here
What's Kallsyms?
lowspeed said:
What's Kallsyms?
Click to expand...
Click to collapse
Da_G has a build of the kernel with this:
Version 0.2 CWM Zip (with KALLSYMS + KALLSYMS_ALL for debugging)
The original request came from someone who wanted to use an app to help fix the spen issues which required this I believe.
hololight said:
Op updated with kallsyms support kernel... enjoy.
Click to expand...
Click to collapse
Thank you! Amazing!
My phone will eat your Apple!
Not discounting your work here - and this is just my opinion.
It might've been better to work with DaG and get him to integrate this into his kernels. do you plan to re-release every time he makes changes to his kernels?
Can i use this on my rogers galaxy note? Will i loose lte on rogers or nfc? Thanks
Sent from my SGH-I717R using Tapatalk
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
OK tested it out. I don't think it helped.
hololight said:
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I wasn't trying to start anything, it was a serious question though. Are you going to release a new one after DaG does changes to his kernel?
hololight said:
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Ok so far seems fine on my rogers note but when checking kernel in about phone i get unavailable? Grat work by the way
Sent from my SGH-I717R using Tapatalk

ICS DEVS UPDATE THREAD ONLY

All ICS kernel updates can go here. This is for Entropy, LipShitz, Task and any other who is actually working on the ICS kernel.
If you post here, it will be deleted on the spot so just fair warning...
First!
These are always my latest *unsupported* builds:
i9100 Touchwiz Based Roms: http://www.cheatersedge.org/android/i777/TWzImage.tar
AOSP Based Roms: http://www.cheatersedge.org/android/i777/AOKPzImage.tar
Red5 said:
If you post here, it will be deleted on the spot so just fair warning...
Click to expand...
Click to collapse
Come at me bro!
j/k..
Seriously guys.. No fooling around!
Fenny maybe I missed it but do you have a thread to discuss this tw kernel. So far so good. I had already converted OmegaRom 5.1 with everything and was just waiting on a kernel. So far so good. I am gonna look through my notes on how/where to fix the home haptic feedback but other than that all 4 buttons seem to working perfectly. I have sent a pm to the des of OmegaRom to see if they wanted it ported (help porting it to our phones) but i have heard back from them so far. Will continue playing with it with your kernel and test it out. I have run the OmegaRom for about three days already and have had any issues so testing with your kernel is now upon me. Thanks for your work on this. Rich
Fixed: All keys and home haptic working now, though home haptic seems lighter than the other keys.
Sent from my SGH-I777 using xda premium
Until things are cleaned up better, there aren't going to be threads. There's enough to be done and enough things are still not working right that new threads aren't justified yet.
https://github.com/Entropy512/initramfs_galaxys2_ics
https://github.com/Entropy512/kernel_galaxys2_ics
used to build the attached zImage. If you don't know what to do with a raw zImage, this isn't ready for you yet. Simple as that - there is a lot of things missing (like, don't set any profiles in SetCPU with reduced clock frequencies, bad things will happen) - I still haven't tested flashing zips in CWM. nandroid backup/restore seems to work but no guarantees.
You still need to disable Samsung Noise Reduction or use a hacked Phone.apk along with a hacked /system/usr/keylayout/sec_touchkey.kl (see Hellraiser on github) for it to work in a reasonable way. There's probably a large pile of **** still broken. Don't pester me with bug reports - there's a pile of stuff I KNOW I still need to address.
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Entropy, not stating a fact and you KNOW a heck a lot more than I so take this with a grain of salt. I have been playing with lots of different files on a ported/converted i9100 ICS Rom (Omega Rom 5.1) and used these for the usr files and have seen the screen wake issue. http://db.tt/DUe4afdh Maybe it has nothing to do with these though. I have changed many other things like csc folder, csc other files, many other things also. Also I am using the kernel posted by Fenny if that matters or is much different than yours a I have tested it out yet. I only replied here because one of the files I removed was the gpio file completely as other files inside seemed to have the same configurations. Maybe I am WAY off base here. If you want to try the Rom i converted already to see if anything helps let me know and I will send a link to you. Thanks for all your hard work.
Sent From My KickAss ATT SGS2 SPORTING my CobraRom
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Better off doing how its being done... if use another developers ... you just mirror same issues...if build yourself you know whats what.
Tap-Tap Talking
Entropy512 said:
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Click to expand...
Click to collapse
Isn't 4.0 a total new build from Sammy? Honestly.... from what I'm looking at...I don't see ginger GPIO being compatible..but should be if all they used was duct-tape and staples to parse another kernal together.I'm buying a laptop. You guys use sdk? Entropy..what program are you using for kernal popping? Give me area you want help....will do
Tap-Tap Talking
LipShitz said:
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
Click to expand...
Click to collapse
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Entropy512 said:
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Click to expand...
Click to collapse
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Fenny said:
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Ill make sure it stays at the top.
LipShitz said:
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Click to expand...
Click to collapse
I'll catch up on your PMs soon.
I think I've found the screen wake bug: I misread the #ifdefs in the Gingerbread kernel, and realized they unmap the HOME key GPIO.
There was no such unmapping in the ICS kernel - so the GPIO was left mapped to HOME but left floating, which explains both random wakes and spurious HOME presses. It's also why the patch I posted this morning caused guaranteed screen wakes on resume - GPX3(5) is the HOME GPIO and was set to pulldown by that patch - it's an active-low GPIO.
Attached is a test kernel zImage and two patches - if these solve screen wake for those experiencing it, I'll push the patches to github and probably release the first Daily Driver ICS tonight even though I still haven't fixed SetCPU hangs.
This kernel is for Touchwizz firmwares only - if it solves the problem for everyone I'll work with the CM9 maintainers on integrating the attached patches, which apply to the current state of my github repo.
Let me know when you get to test point. Shoot it over if you want.
I have started writing a new program that will enable you to do parcing of 2 total diff Kernals,full factory and custom ROMs., yank out APK's and cook me dinner. What It will prob be 2gig in size..will streamline it. But when done--- WE WILL RULE THE WORLD!.. yea ok.
Tap-Tap Talking
Here is a kernel I compiled to work with MIUIv4 for this weeks update 2.3.23:
http://www.mediafire.com/?5bm1l4t1bmbd8bm
All good... little laggy(prob CPU hang) 200-1200 CPU set? No wake issue yet. I'm on 1.5 hours.
Tap-Tap Talking
I restarted phone and stuck on startup logo(samsung bla bla bla) i need to hook it up to laptop and flash it. Will not go into cwm with power and both volume. Im on my infuse.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Sorry Double Post

[CANCELLED] Voodoo Sound for Galaxy S Wi-fi 4.2

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

Categories

Resources