[Kernel][GB] holoNote Kernel 0.1 (Ghost Touch detection removed) - AT&T Samsung Galaxy Note I717

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

Related

[REQ] Droid X Multi Touch Keyboard *Font Issue Fixed*

I currently have the Droid X Multi-Touch keyboard working on my Vibrant, but the only issue is the font. I know its not that big of a deal but a fix would be nice?
For those who have it, provide link for US who love the keyboard!!!
THxXXX
Supposedly its in the new Axura ROM, you could pull it out of there.
thegreatcity said:
Supposedly its in the new Axura ROM, you could pull it out of there.
Click to expand...
Click to collapse
I have already tried that method. It aprently only works on Froyo 2.2, not 2.1 and most of us are running 2.1
Bumpp
Sent from my SGH-T959 using XDA App
I also would want this for 2.1, hopefully Master can give us a hint
Sent from my SGH-T959 using XDA App
if you use it on any other device i9000/captivate the letters are fixed also on any rom for vibrant with the i9000 kernel so the issue with the kb originates from our kernel
Vibrant - Bionix Fusion 1.1 - JAC's Xmod kernel v1 - ext2 lag fix
kennyp987 said:
if you use it on any other device i9000/captivate the letters are fixed also on any rom for vibrant with the i9000 kernel so the issue with the kb originates from our kernel
Vibrant - Bionix Fusion 1.1 - JAC's Xmod kernel v1 - ext2 lag fix
Click to expand...
Click to collapse
I don't believe so. Its, more likely then not, due to a library issue, since the vibrant theme is slightly different than others.
Has anyone tried it on JI6.
blinksilver said:
I don't believe so. Its, more likely then not, due to a library issue, since the vibrant theme is slightly different than others.
Has anyone tried it on JI6.
Click to expand...
Click to collapse
Hi,
I've tried the Droid X (2.1 mod version) keyboard on all the JI series leaks, and the final OTA JI6, and the keys still render tiny, for me.
I've also tried pushing the libjni_latinime.so from a captivate rom to my phone, and still no luck, tiny keys.
So, I'm lost on anything else to try except thinking its somehow kernel related, since flashing a rom with a kernel built from i9000 source, renders the keys properly.
If I remember correctly, even in the earliest days of Vibrant modding, when flashing the very first clockwork recovery betas (the versions that actually included kernels built from i9k source and weren't simply loaded into the ramdisk the way it is now) the keys rendered properly too, can anyone confirm?
I still hope we get this fixed, since GPS is a deal breaker for me, so until we have a vibrant froyo leak to pull GPS drivers from, I'm sticking with 2.1 builds.
Anyway, cheers everyone, =)
s0niqu3 said:
Hi,
I've tried the Droid X (2.1 mod version) keyboard on all the JI series leaks, and the final OTA JI6, and the keys still render tiny, for me.
I've also tried pushing the libjni_latinime.so from a captivate rom to my phone, and still no luck, tiny keys.
So, I'm lost on anything else to try except thinking its somehow kernel related, since flashing a rom with a kernel built from i9000 source, renders the keys properly.
If I remember correctly, even in the earliest days of Vibrant modding, when flashing the very first clockwork recovery betas (the versions that actually included kernels built from i9k source and weren't simply loaded into the ramdisk the way it is now) the keys rendered properly too, can anyone confirm?
I still hope we get this fixed, since GPS is a deal breaker for me, so until we have a vibrant froyo leak to pull GPS drivers from, I'm sticking with 2.1 builds.
Anyway, cheers everyone, =)
Click to expand...
Click to collapse
11/5/2010 Forget you people
I hope someone can fix this. I absolutely love the Droid X multi-touch keyboard. Its the most accurate and fastest I've ever typed on a touchscreen QWERTY keyboard. With the keys font size fixed it'll be 10/10
Anyone, please
I tried ripped the version from the Rom itself but I get a parsing error.
nothing yet?
I've discovered only one good alternative to multi-touch keyboard. Its a Smart Keyboard. By default it slower but if you decrease multi-type delay and swipe-sensivity it will became better.
This thread is Major FAIL. Where is the fix....
Master needs to post what he did.
vinnydakid said:
Master needs to post what he did.
Click to expand...
Click to collapse
I think he want that feature to be exclusive for his roms...
eortizr said:
I think he want that feature to be exclusive for his roms...
Click to expand...
Click to collapse
I doubt it, if it was just exclusive to his rom, you could just ripe out the apk.
blinksilver said:
I doubt it, if it was just exclusive to his rom, you could just ripe out the apk.
Click to expand...
Click to collapse
Hi,
The only problem is the version is his 2.2/Axura rom isn't modified to work on 2.1, now, if someone can point me to a howto on modifying the keyboard to work on 2.1, I'd do that tonight, lol.
UPDATE:
I re-downloaded Master's newest Axura 1.0.3 and decompiled so I can diff the KeyboardView.smali files (this seems to be the file controlling the key font size) and I don't see any difference in the code between the two relating the private field that motorola use mKeyTextSize, so at this point, its beyond me, hopefully master will be kind enough to post his edit, or another dev can look into this.
Sorry, but I just don't see why the keys display fine on i9k/captivate/fascinate/etc., but tiny on the vibrant, and yet display fine on the vibrant with an i9k kernel.
Cheers, =)
s0niqu3 said:
Hi,
The only problem is the version is his 2.2/Axura rom isn't modified to work on 2.1, now, if someone can point me to a howto on modifying the keyboard to work on 2.1, I'd do that tonight, lol.
UPDATE:
I re-downloaded Master's newest Axura 1.0.3 and decompiled so I can diff the KeyboardView.smali files (this seems to be the file controlling the key font size) and I don't see any difference in the code between the two relating the private field that motorola use mKeyTextSize, so at this point, its beyond me, hopefully master will be kind enough to post his edit, or another dev can look into this.
Sorry, but I just don't see why the keys display fine on i9k/captivate/fascinate/etc., but tiny on the vibrant, and yet display fine on the vibrant with an i9k kernel.
Cheers, =)
Click to expand...
Click to collapse
He did not have to edit the smali file in the 2.2 keyboard, just the 2.1 keyboard(most likely for personal use). it works just fine since all the 2.2 roms are using a modded i9000 kernel. That said, you are bringing up a really good point, why is the kernel causing such interesting behavior.

[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?

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

[ROM] CM10 PURE AOSP 4.1.2 JB-Final.

Hello People,
This time i bring you a cm10 build from the man it self "Hashcode" for our beloved Nook Tablet.
He is the one who took at his shoulders the Kindle Fire kernel and rom development and skyrocket their sales(Amazon).
I think no more needs to be said about the awesomeness behind this developer but to show our appreciation for finding the time to compile a test release from Nook Tablet Git.
We all expect more to come from this great day forward but nothing is promised and we all need to give our feedback and report issues from this ROM in this thread.
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it... there is always stock and CM7.
New Rom Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20130123-UNOFFICIAL-acclaim.zip
Changelog:
- Added SIO and V(R) I/O Schedulers
- Sync with CM10 (a lot of changes)
- Disabled SR v3 and enable SR V1P5 as default.
- Patched Sensor(KXTF9) timing for faster response in games (from 100ms to 40ms)
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121207-UNOFFICIAL-acclaim.zip
Includes:
- 3 new CPU governors (LAZY-DYNAMIC_INTERACTIVE-WHEATLEY)
- Added safeboot settings for Silicon Performance (1.2Ghz)
- Added actual OSWR logic for mpu when turned on
P.s
Forgot to re-enable SR V1P5 Next time
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121128-UNOFFICIAL-acclaim.zip
- Deep Sleep really fixed this time, sorry guys
- I/O Tweaks for speed
- Better memory timings
- More Logical values added to CPU idle code
- Better Battery Life expected.
- 1.2Ghz CPU as default.
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121121-UNOFFICIAL-acclaim.zip
Includes:
- Reverted Kuzma's Emif changes so device can deep sleep again
- Removed SmartReflex 1P5 and downgraded to SmartReflex V3 for more compatibility with troublesome nooks
- Added O3 flag on compile for speed optimization
- Silicon Performance Enabled = 1.2GHZ CPU
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121115-UNOFFICIAL-acclaim.zip
Includes:
- 10 touch driver taken from Nook HD and adjusted to Multitouch compatibility by Mik_os
- New Backilight Led driver taken from Nook HD and adjusted to our github compatibility by Mik_os
- Still CM10(4.1.2) (JB4.2=CM10.1) sync
- Kuzmas excellent new drivers from Nook HD Source
- Bug fixes
All credits goes to our development team Kudos guys for an exceptional work!
In my opinion this is considered daily driver rom because:
Known Issues:
-None
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121107-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121107-Hashcode-acclaim.zip
Includes:
-New PVR Driver DDK [email protected]
-New WLAN firmware R5.SP3.03
-Greatly improved kernel thanks to all the nice developers in here
-All fixes Implemented:Touch/Accelerometer/PVR Graphics/LG Panel.
ROM Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121023-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121023-Hashcode-acclaim.zip
Flashable Recoveries(Put into sdcard and flash from recovery like a rom)
http://celticstorage.co.uk/cm10/CWM_v6.2.7_emmc.zip
http://celticstorage.co.uk/cm10/TWRP_v2.3.3_emmc.zip
Thanks goes to Succulent (HD)
Gapps:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
And as always,
Enjoy your Nook.
Added a flashable package from a new code implemented into rom by Mik_os
This will give you peace of mind in touch controller firmware flashing as it is very user friendly and straight forward.
Just flash this with recovery and you will find a new package in android app drawer that can test and see what firmware version you are at and offer you the opportunity to flash the other. Other can be 2 or Multitouch and depends on what firmware you are at the moment you run the application.
Nice!!!!!
* DISCLAIMER *
To be perfectly clear: This was a flash .zip built straight from the device/kernel sources that the current NT devs have worked very hard on.
I built it as a test case to see if there were compile issues and/or other external problems with the existing builds compared to the Kindle Fire builds which don't show the same issues.
THIS ROM IS NOT NEW. I didn't do anything but sync down the 2 acclaim projects press "go" on the compile.
Only issue I see of now is apps on SD card still disappear when nook reboots. I will report any other issues as I see them.
Thanks for all your hard work devs on the nook. To think I was about to give it up for a nexus 7. No way now I love this thing. :thumbup:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Downloading , i'll flash this rom
thanks u so much.
mikenexus said:
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Click to expand...
Click to collapse
the same felling with you. and.... Mic does not work...
Note:12/10 build had a workable Mic (SGT7+CM10+Cherry Picks,By meghd00t)
http://forum.xda-developers.com/showthread.php?p=31400856 this has the mic fix. Search around a little and you can find answers
Sent from my Droid using xda app-developers app
createpassword said:
Anyone? Its a pretty simple question...
Click to expand...
Click to collapse
I think is a simple flash to find out. The truth is out there.... (drums)
So my friend has the 16gb Nook Tablet.. will this work on it? And really? Everything works?!?!?! No more screen of death? Mic works too??!?! Netflix?!?!
I wanted to comment i tried this one and i have the same problem with all cm10 roms....after a few minutes....it wont let me download anything...like i try to download and it reaches 100% but says still in progress and freezes everything because once that hapens and you try to reboot or power off it just loads but does not reboot or power off....
Sent from my Nook Tablet using xda app-developers app
createpassword said:
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
I don't think anyone owes you anything at all. Such entitlement....
Sent from my Barnes & Noble Nook Tablet using xda premium
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
This is a development rom in the development section of the forums. It seems to me it would be better for you to return your wife's nook to stock. This rom was posted for testing and bug reporting.
Sent from my DROID RAZR using xda premium
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
I haven't had any reboots or hangs on my NT 16 GB, but it's only been 12 hours. I'll test it over the weekend more to see if I can make the permanent jump from CM7.
this rom have mixer or not.
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
No. I put it on my mother's 16GB Nook Tablet and it's miles better than CM7 was. Not perfect but no serious flaws.
Has anyone experienced download problems that cause lag that doesnt allow you to reboot or poweroff or do anything?
Sent from my Nook Tablet using xda app-developers app
I have rooted every device I own. I also have a Nexus 7 and a Nook Tablet. In somewhat of defense of the guy earlier working 10 hours, wife and 4 kids sometimes it is easier to ask rather than "just flash it". I want to use my Nook so my kids ages 2 and 4 can watch Netflix on long car trips. The Nook is much more of a tank than the Nexus 7 and would bee much less bummed if the Nook gets broken over my Nexus.
I'm not saying my time it's any more important than yours. And it doesn't take any more effort to answer a simple question than it does to tell someone Rio flash back to stock.
I would like to know if Netflix works on this build? If so I will flash it ASAP. If not I will not get my Nook out of my nightstand and will keep checking back once and a while.
Thanks.
Sent from my DROID SPYDER using Xparent ICS Blue Tapatalk 2
Random reboots seems to be fixed.
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
My deepest apologies.
It was an error from my part so i went and fixed my statement in Official post.
Thanks again for pointing out my huge mistake.

[Q] Stock TW 4.1.2 kernel

Hi All,
I'm looking for a stock TouchWiz (TW) Kernel for JB 4.1.2.
No OC, no BLN, just a stock kernel.
I know they are included in several roms, but i'm trying to add it to a rom that doesn't offer a stock kernel version. I found one that was close, but for whatever reason it removed vibration control.
The OC versions (with and without) both remove the function of my capacative buttons.
So my question is... Does anyone have a stock TW 4.1.2, non OC kernel or if not, would a dev be so kind as to rip it and make one available?
Thanks so much for your assistance.
-Logic
Logic717 said:
Hi All,
I'm looking for a stock TouchWiz (TW) Kernel for JB 4.1.2.
No OC, no BLN, just a stock kernel.
I know they are included in several roms, but i'm trying to add it to a rom that doesn't offer a stock kernel version. I found one that was close, but for whatever reason it removed vibration control.
The OC versions (with and without) both remove the function of my capacative buttons.
So my question is... Does anyone have a stock TW 4.1.2, non OC kernel or if not, would a dev be so kind as to rip it and make one available?
Thanks so much for your assistance.
-Logic
Click to expand...
Click to collapse
the only thing I can think of which may come close, but I don't know cause you didn't say what ROM you are running and they need to be compatible, might be a KERNEL from BLOWNFUZE. it is 4.1.2 made for BIGFAU and his BLACK JELLY. I was trying to compare what it has and what you dont want. maybe you should look for yourself, you can find it on p.115 of AOKP ROM thread.
might be as close as you can get without finding some one to tear their work apart for a single request. PHASE KERNEL would be the only other I know of, but it has OC/UV.
unless there is something I don't know about, which IS possible as unfortunately I dont know everything.
good luck
whatever you try, make a back up first buddy
Logic717 said:
Hi All,
I'm looking for a stock TouchWiz (TW) Kernel for JB 4.1.2.
No OC, no BLN, just a stock kernel.
I know they are included in several roms, but i'm trying to add it to a rom that doesn't offer a stock kernel version. I found one that was close, but for whatever reason it removed vibration control.
The OC versions (with and without) both remove the function of my capacative buttons.
So my question is... Does anyone have a stock TW 4.1.2, non OC kernel or if not, would a dev be so kind as to rip it and make one available?
Thanks so much for your assistance.
-Logic
Click to expand...
Click to collapse
Here is what I found.
http://forum.xda-developers.com/showthread.php?p=44059263
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
captemo said:
the only thing I can think of which may come close, but I don't know cause you didn't say what ROM you are running and they need to be compatible, might be a KERNEL from BLOWNFUZE. it is 4.1.2 made for BIGFAU and his BLACK JELLY. I was trying to compare what it has and what you dont want. maybe you should look for yourself, you can find it on p.115 of AOKP ROM thread.
might be as close as you can get without finding some one to tear their work apart for a single request. PHASE KERNEL would be the only other I know of, but it has OC/UV.
unless there is something I don't know about, which IS possible as unfortunately I dont know everything.
good luck
whatever you try, make a back up first buddy
Click to expand...
Click to collapse
The rom I'm running is [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0 but my intention was just to have the kernel as a standalone option for those that just want the stock kernel.
The problem I'm having with the OC kernels (Fuze and Da_G) is that the capacitive lights are not working with them. Fuze's works for for BLN, but i'm not using BLN. Functionally, both of those kernels are super fast and I have no issues with stability or performance.
For now, I'm ok with living without it as it's a nice to have and not a need so I respect your opinion in being the only one to request such a kernel. My sole thought was just to have it as an option for those that don't need/want OC and are fine with stock functionality for the kernel.
I didn't think AOKP kernels could be used with TW roms, am I mistaken in that?
Logic717 said:
The rom I'm running is [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0 but my intention was just to have the kernel as a standalone option for those that just want the stock kernel.
The problem I'm having with the OC kernels (Fuze and Da_G) is that the capacitive lights are not working with them. Fuze's works for for BLN, but i'm not using BLN. Functionally, both of those kernels are super fast and I have no issues with stability or performance.
For now, I'm ok with living without it as it's a nice to have and not a need so I respect your opinion in being the only one to request such a kernel. My sole thought was just to have it as an option for those that don't need/want OC and are fine with stock functionality for the kernel.
I didn't think AOKP kernels could be used with TW roms, am I mistaken in that?
Click to expand...
Click to collapse
that is true, but as I said and as BLOWNFUZE states in his post, he designed it for BIGFAU and his ROM. its sounds and looks as if ANTHONY has provided an option too. his is the PHASE KERNEL though isn't it ? that's why I went back and edited my original for you to make back up, whatever you do.
let us know what you try and if it works, others may be curious.
Logic717 said:
The rom I'm running is [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0 but my intention was just to have the kernel as a standalone option for those that just want the stock kernel.
The problem I'm having with the OC kernels (Fuze and Da_G) is that the capacitive lights are not working with them. Fuze's works for for BLN, but i'm not using BLN. Functionally, both of those kernels are super fast and I have no issues with stability or performance.
For now, I'm ok with living without it as it's a nice to have and not a need so I respect your opinion in being the only one to request such a kernel. My sole thought was just to have it as an option for those that don't need/want OC and are fine with stock functionality for the kernel.
I didn't think AOKP kernels could be used with TW roms, am I mistaken in that?
Click to expand...
Click to collapse
I posted a link to a TW Stock rom that was ripped from BlackJelly by Anthony(Stock_TW_4.1.2.zip), Isn't that what you wanted? I haven't tried it as I am running the Fuse Kernel with [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0
captemo said:
that is true, but as I said and as BLOWNFUZE states in his post, he designed it for BIGFAU and his ROM. its sounds and looks as if ANTHONY has provided an option too. his is the PHASE KERNEL though isn't it ? that's why I went back and edited my original for you to make back up, whatever you do.
let us know what you try and if it works, others may be curious.
Click to expand...
Click to collapse
Yeah, I realized the BlownFuze was meant for BlackJelly and it works just fine with the ROM I'm using. The [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0 uses the Da_G version 4 which has a slow charge issue, that's why I reverted to v3 which doesn't have the slow charge issue. Da_G is working on that, but even with that Kernel the capacitive buttons don't light up so in that regard, they are both great kernels that OC, and are stable, but don't enable the capacitve so they're in the same boat for me.
The phase kernel I need to try again to verify that the capacitive buttons don't light up, but if memory serves, it only works fluidly with smartass V2 as the governor. Again though, with the capactive issue, it's in the boat with the other OC roms.
Those were the only Kernels (one exception that I'll note in response to the next post) for 4.1.2 TW that I was able to locate which lead me to the post. I certainly have headed your advice regarding a backup and I have 2 just in case .
As I said, it's a nice to have, not a requirement. I'll update this if anything changes.
GPFerror said:
I posted a link to a TW Stock rom that was ripped from BlackJelly by Anthony(Stock_TW_4.1.2.zip), Isn't that what you wanted? I haven't tried it as I am running the Fuse Kernel with [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0
Click to expand...
Click to collapse
Yeah, I tried that one as Anthony linked it in the thread, but it removed vibration for me and I ended up missing several notifications during work hours because of it.
Otherwise, it worked just fine in terms of capacitive buttons lighting up. You're welcome to try it and confirm my findings.
GPFerror said:
I posted a link to a TW Stock rom that was ripped from BlackJelly by Anthony(Stock_TW_4.1.2.zip), Isn't that what you wanted? I haven't tried it as I am running the Fuse Kernel with [ROM][4.1.2][Padawan-Kang] Prophylactic 1.0
Click to expand...
Click to collapse
my bad GPFERROR. good eye in finding that
I had a nandroid of the stock 4.1.2 ROM so I just went into TWRP and restored only the boot image from the stock ROM which gave me the stock kernel. Everything is working fine.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
i have been running phase kernel on stock rooted 4.1.2 for months and have never had issue with lights not working. are you sure its not a rom issue. and the obvious did you check to make sure touch key lights are not turned off?
s89281b said:
i have been running phase kernel on stock rooted 4.1.2 for months and have never had issue with lights not working. are you sure its not a rom issue. and the obvious did you check to make sure touch key lights are not turned off?
Click to expand...
Click to collapse
****EDIT**** Confirmed that it's not a kernel issue.
Thanks for this info, I suppose I didn't think about it being a ROM issue that would impact the lights. I have double and triple checked that setting toggeled it off/on and tried each one of the options with each kernel.
I guess I just assumed it was the kernel.
Any idea what in the ROM controls that? I'll reply in the original thread to see if we can figure that out.
Thanks very much for confirmation that it's not the phase kernel that' causing the touch key lights issue.
-Logic

Categories

Resources