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
Related
CyanogenMod 7 (w/ Gingerbread 2.3.4) for Vibrant
Not supported anymore due to issues with dialing 911. We strongly suggest that Vibrant users of CM7 save their data and install a Samsung ROM and restore data to it
Save this post
Since this obviously replaced the previous CM information. There is still no gps support, correct? I know it was stated in all of the old info, but I didn't see any mention of it in the new logs. I just wanted to confirm prior to going ahead with the installation.
zyrinx said:
Since this obviously replaced the previous CM information. There is still no gps support, correct? I know it was stated in all of the old info, but I didn't see any mention of it in the new logs. I just wanted to confirm prior to going ahead with the installation.
Click to expand...
Click to collapse
http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/issues/detail?id=95
Excellent. Thanks. A simple "No" would have sufficed, but I do appreciate the link to current issues.
Does this mean that this CM7 is from the OFFICIAL CM people and not the things that our devs here made?
xriderx66 said:
Does this mean that this CM7 is from the OFFICIAL CM people and not the things that our devs here made?
Click to expand...
Click to collapse
Official CM will be made from what we build here. There is not "Official people" as such - teamhacksung are the ones doing the SGS specific stuff for CM.
anyone else having issues flashing todays update? I flashed it now my phone will not boot.
Indeed. There were several posts in the development thread about it causing boot issues. It's only with the Vibrant though. They suggested flashing a new kernel/old kernel and that should fix it.
zyrinx said:
Indeed. There were several posts in the development thread about it causing boot issues. It's only with the Vibrant though. They suggested flashing a new kernel/old kernel and that should fix it.
Click to expand...
Click to collapse
Sorry - that is only to go back to previous. We will be uploading another soon if we've fixed what we think we just fixed. But to get your phone back, just flash an older kernel, and then flash 5/1 update and you should be on CM7 again, ready for new update which will happen soon I hope.
Awesome. Looking forward to it.
I know these numbers are irrelevant, but what kind of quadrant numbers is this running at?
Curious as to the lack of GPS functionality, is it because of a lack of open source drivers?
And if it is, then why do other GalaxyS devices have working GPS when (i dont think) they dont have any more new open source files then us?
karimsaud21 said:
Curious as to the lack of GPS functionality, is it because of a lack of open source drivers?
And if it is, then why do other GalaxyS devices have working GPS when (i dont think) they dont have any more new open source files then us?
Click to expand...
Click to collapse
Different GPS chip on Vibrant.
Amazing thread.
Everyone should know he also does not have a Vibrant and works mostly on the Captivate. The fact he is aiding us, speaks volumes. I hope you all appreciate his extra efforts.
I tried to make an install guide (signature). Its not perfect, but it may help (differences from the video)?
I totally agree s15274n . Btw cm7 rocks
Sent from my SGH-T959 using XDA Premium App
Quick question, does the latest build charge while powered off? Don't want to flash to find out.
Sdobron said:
Quick question, does the latest build charge while powered off? Don't want to flash to find out.
Click to expand...
Click to collapse
No, it will turn on. Tho why it matters I never understood. We will support low power mode someday I'm sure, but very low priority. Just turn the screen off, use quiet hours ...
Thank you for posting this. I have a quick question though. I lost my USB driver cable to my vibrant (I charge it via a plugin charger now.) Is there any possibility that I can install CM7 via the Marketplace (from Clockwork Mod or the another automatic install app) without going through all these steps?
I will be coming from Nero....
Thanks for all your hard work!
Quick question I flashed cm7 yesterday and have been amazed by everything except one thing. The color levels specifically the blacks are horrid. I can't use any wallpaper that has shades of blacks or it just looks very low quality. Is this a voodoo thing?
Sent from my SGH-T959 using XDA App
This is more of a general suggestion to those making the TB GB roms and adding the kernel to them or thinking about it..
Since it would appear reading through the posts and trying out the kernel for myself, I have found that the current GB kernel just gives my phone fits and it appears that other's have the same issue. I know it works for some, wish mine did. But can we get or keep the GB Roms separate from the kernel for a bit?
My phone runs GB fine without the kernel, and it sounds like it runs fine for others as well, since the kernel appears to add issues, it makes it hard to try out Roms that have the kernel included.
Its just a suggestion and at least at some point down the road I (or we) could try the kernel(s) as it matures more. And for those that the kernel works on, they can use it..
Thanks!
If your talking about random reboots just let it throw a few, every time I change a GB kernel I get a few, then after that it's totally fine.
Me too. Mine usually reboots a few times right after I install and then just works.
Sent from my ADR6400L using XDA Premium App
I don't quite get what you're saying. Every rom has a kernel. It's basically what allows the software to communicate with the hardware. You can't take the kernel out of a rom or you don't have a complete functional operating system.
You need to remember that the leak was a test version, kind of like a cyanogenmod nightly. So things are going to be broken. They will fix them over time, especially as new leaks emerge.
In the meantime, if you are having problems, just go back to froyo for now. It's fast and fully functional. Gingerbread will be unleashed with ALL of it's greatness soon enough. Then we'll be anxiously awaiting ice cream sandwich
sent via rooted THUNDERBOLT with Tapatalk
sgtguthrie said:
I don't quite get what you're saying. Every rom has a kernel. It's basically what allows the software to communicate with the hardware. You can't take the kernel out of a rom or you don't have a complete functional operating system.
You need to remember that the leak was a test version, kind of like a cyanogenmod nightly. So things are going to be broken. They will fix them over time, especially as new leaks emerge.
In the meantime, if you are having problems, just go back to froyo for now. It's fast and fully functional. Gingerbread will be unleashed with ALL of it's greatness soon enough. Then we'll be anxiously awaiting ice cream sandwich
sent via rooted THUNDERBOLT with Tapatalk
Click to expand...
Click to collapse
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread. New kernels will come and the current ones are being worked on. What you may want to try is going into console and using speedtweak.sh to up the voltage if you are having reboot problems.
I know it gets hard to answer every question with a meaningless philosophical argument invalidating the question itself, but then again the forum has a minimum post count.
twistedumbrella said:
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread.
Click to expand...
Click to collapse
Exactly, I have no problem running the default kernel that comes with GB Gingerjane 1.2 Rom as their is another kernel to possibly fix camera issues and they are separate downloads. Once I load that kernel I start having all kinds of problems, I restore my backup and all is good. I have seen some posts that others run into a similar issue. I thought it would just be good to keep them separate right now if possible. Its possible that some of the other GB Roms would work too, but I have the same issue with those and they include the new kernel as well for camera fix. So I have assume (I know bad word) that the common issue with mine and possibly others just could be that kernel for whatever reason.
twistedumbrella said:
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread. New kernels will come and the current ones are being worked on. What you may want to try is going into console and using speedtweak.sh to up the voltage if you are having reboot problems.
I know it gets hard to answer every question with a meaningless philosophical argument invalidating the question itself, but then again the forum has a minimum post count.
Click to expand...
Click to collapse
"Meaningless philosophical argument"? I really don't see where you get that from, but whatever...
Also, a low post count doesn't mean you're a noob, just not as active at xda. This isn't the only forum site on the Internet.
I just saw something on twitter, jcase was posting the stock gb kernel in his thread, so there you go...
Edit: it's posted, happy flashing...
http://forum.xda-developers.com/showthread.php?t=1082001
Edit 2:
It's in the lightning rom thread too.
sent via rooted THUNDERBOLT with Tapatalk
sgtguthrie said:
I just saw something on twitter, jcase was posting the stock gb kernel in his thread, so there you go...
Edit: it's posted, happy flashing...
http://forum.xda-developers.com/showthread.php?t=1082001
Edit 2:
It's in the lightning rom thread too.
sent via rooted THUNDERBOLT with Tapatalk
Click to expand...
Click to collapse
Thanks.. that works too.
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?
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
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?