yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] UpInTheAir:
Probably not fast dormancy, but although for SGS3, try this ;

1. Take a look at "FastDormancy Toggle for i9300"

https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300

2. You could also slightly UV & UC the CPU to 1400 MHz. (You can UV CPU with perseus kernel STweaks app, haven't tried the latest adamkernel)

3. Newer firmware may be better too
[Galaxy S 4 Q&A, Help & Troubleshooting] marci4na:
thanks but the app is not working for i9505. it says ok but when you look for the kernelwakelok you can see fastfdormancy agayn!!

any other info?
[Galaxy S 4 Q&A, Help & Troubleshooting] UpInTheAir:
Did you reboot after applying app changes?

Consider alternatives 2-3......

Heat issue (for some) has been discussed in many threads throughout these forums. Have a search ;)
[One (M7) Q&A, Help & Troubleshooting] dinodude:
I went into the the downloads section of the PAC man ROM site and I have noticed that the files for the nightly are not there and it shows this. http://pacman.basketbuild.com/index.php?dir=main/m7/nightlies/ -developers app I am living this ROM but I want to update it!
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Is there any way to get the s4 camera app to work on a nexus 4? And how can I get it to work? I downloaded the stock s4 rom, found the camera app, tried to install it and it didn't work. I wasn't surprised though lol. So is there a way to get it to install?
[Nexus 4 Q&A, Help & Troubleshooting] Chromium:
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
[Nexus 4 Q&A, Help & Troubleshooting] JaylanPHNX:
I don't know about brick, but it would definitely not boot.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Q&A, Help & Troubleshooting] exb0:
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Oh I see. Well I wasn't planning on doing it anyway :P but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
[Nexus 4 Q&A, Help & Troubleshooting] exb0:
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.

Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
[Nexus 4 Q&A, Help & Troubleshooting] Chromium:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.

Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Oh ok. That sucks :/
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
That's why each device on XDA has their own little section call home.
[Nexus 4 Q&A, Help & Troubleshooting] estallings15:
Probably the way they chose to assign the partitions on the device. It would be nice if there was a standard that everyone followed, but oh well.
[Nexus 4 Q&A, Help & Troubleshooting] rayiskon:
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
[Nexus 4 Q&A, Help & Troubleshooting] NuckFuggets:
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo :P
[Nexus 4 Q&A, Help & Troubleshooting] rayiskon:
in that case it shouldn't be called a Nexus anymore ;)
[Off-topic] majote:
usually in the forums there is a post where the new members can introduce themselves, in this forum, where is this post? a greeting
[Off-topic] 063_XOBX:
Did you even make the slightest effort to find it? Or was looking anywhere other than up your butt too hard?
[Off-topic] Danial723:
The fail is strong with this one....but here it is....second sticky

http://xdaforums.com/showthread.php?t=961655

"I didn't slap you, I high fived your face"
[Off-topic] LoopDoGG79:
Thing is OP, you've been a member since 2010. :what: You ain't exactly a "new" member.
[Verizon Samsung Galaxy S 4] fenguepay:
Is there any to access the music download through play music on another music app like poweramp on the gs4? The data and android folders have no files at all and I downloaded a few albums.
[MDA II, XDA II, 2060 General] fatboyslimfast:
With O2 launching the XDAIIi when will they be launching their music player for the X range? The website says soon but that's been there for ages.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] P.Mobile:
Just wanted to know if anyone has heard anything on aroma working for our device? i kno it works for the htc one.. i pray it starts working real soon so we can get some roms over on the sprint side..
[Thunderbolt Android Development] santod040:
★ ☆ [Kernel] NuK3RN3L | s2w+s2s | 01-21-14 | 1,900MHz | 3.0.84 | Sense/AOSP | ☆ ★

-NuK3RN3L-

OVERCLOCKED

Edition

Now added!

Santod's Mecha ICS Sense/AOSP Kernel

DOWNLOAD:

NuK3rn3l mecha Final

sweep2wake

sweep2sleep

16 Governors

TCP Controls

Zram/Swap

Linaro

OTG

01-20-14

Use Trickster Mod to enable Wake options

You need an updated version of Busybox from the Play Store to use Trickster Mod.

Once that's installed, open it and run the installer.

Then you can install Trickster Mod, grant it su permissions, and use it to enable s2w+s2s and adjust all other kernel settings and tweaks.

Trickster Mod can be found here.

-NuK3RN3L-

stock frequencies

current build

~ or ~

NuK3RN3L-

Overclocked Edition

1,516MHz Default/Max

current build 6-25-13

+ LagFree

-NuK3RN3L-

Aosp NuK3RN3L, with working wifi on Aosp ICS and Jelly Bean.

Only use this for this one on Aosp roms. (CM9/CM10)

[URL="http://www.androidfilehost.com/?fid=23017610006233856"]NuK3RN3L ICS/JB Aosp OC Edition

[/URL]

These have been well tested, but use at your own risk!

I am not responsible for you or your device or anything that you do to it!

​

Included Governors:

SavagedZen

lulzactive

adaptive

hyper

scary

skywalker

brazilianwax

fantasy

SmartassV2

interactive

conservative

userspace

powersave

lionheart

ondemand

performance

I will try and update my git repo every 7-90 days until I automate it into my buildbox process...

Compiled using the 4.4.3 gcc toolchain.

Big thanks to my buddy Ziggy for his help and inspiration.

XXPachaXX for his work on msm7x30

Flemmard for his work on msm7x30

Also to HTC for finally releasing the source code...

HTCDEV Source files: my copy

​
[Thunderbolt Android Development] santod040:
Reserved...

​
[Thunderbolt Android Development] santod040:
NuK3RN3L is also now booting with AOSP JellyBean.

Stay Tuned!!!!

​
[Thunderbolt Android Development] Milimbar:
Any chance of a dual boot setup?

Check out the Devil kernel and recovery for the note 2......

Would be nice to have a slimmed down AOSP ROM and a Sense one for when you wanted it.
[Thunderbolt Android Development] disconnecktie:
I'm not trying to be rude to anyone but let's keep the feature requests to a minimum until he gets the more important aspects worked out. There is a lot of testing going on with just what this kernel can do as we speak. I'm sure once things calm down the other features can be implemented.
[Thunderbolt Android Development] arizonaomnia:
Says AOSP in the title. Can this be used with the CM9 in this thread?
[Thunderbolt Android Development] santod040:
This can be flashed to any current ICS roms!

Sense and AOSP!

NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...

Looks like we may have an AOSP/Sense ICS Hybrid Kernel.

On Aosp, Data and Netflix BOTH work, camcorder not yet.

Will work on things with Joe to improve this.
[Thunderbolt Android Development] Virus:
Congrats on RLS brosif :) these guys are lucky you are still carrying the infected flame for this phone !!!!
[Thunderbolt Android Development] arizonaomnia:
Anyone know if it fixes the Gmail whiteout? I can live without the camcorder but the Gmail thing was too much.
[Thunderbolt Android Development] je2854:
Good to see you here [MENTION=2098136]Virus[/MENTION].

I haven't seen you since my EVO days!
[Thunderbolt Android Development] namurt:
i flashed both the stock and oc'd versions of this kernel over joe black's cm9 (which was also clean flashed... even wiped my sd) and wifi isn't working. it flat out won't turn on.

i don't have my tbolt in service anymore, so without wifi, i can't use it at all. wifi worked with the included kernel on joe's cm9 rom.

i'm a little pressed for time at the moment, but if a logcat would be helpful, lemme know and i'll post one when i'm back from vacation at the end of the upcoming week.
[Thunderbolt Android Development] santod040:
Yeah that's a known issue with flashing it seperate.

There's a couple things not included in the kernel zip, that have to be changed Rom side.

These changes are easily made and Joe should have an update posted soon with this kernel in it and the needed Rom files to have WiFi working.

Sorry for the inconvenience.

It's just become known it would work as well as it does.

Fixes and improvements to his Rom and this kernel are coming.

If he doesn't have it up soon, I'll post a patch for using this on his Rom.
[Thunderbolt Android Development] namurt:
sweet jesus, you are one amazing dev!

that was a lightning quick response, hah.

it's so nice to see our bastard child of a device still getting some love. :)
[Thunderbolt Android Development] arizonaomnia:
You know....if you WANTED to....you know, just for sh1ts and giggles.....you COULD post the version of this without working data, just to give a preview and let people play with it. I remember that Liquid did something similar with an early build of OCS for the Thunderbolt. Or not. Whatever you want to do is fine, of course.

*drooling*
[Thunderbolt Android Development] quickdraw86:
Yep, santod is the man, no doubt about it.

This device launched more than 2 years ago with froyo, was upgraded to gingerbread, eventually got ICS, and may yet see unofficial jellybean!? That's an amazing run for any phone IMHO.
[Thunderbolt Android Development] guinzo:
where i can find thunderbolt aosp jelly bean ROM...:confused:

olredi tried this kernel on Jelato ROM and make ma fone awesomely blasting fast :good:
[Thunderbolt Android Development] quickdraw86:
AOSP jellybean hasn't been released yet, they're still working on it.
[Thunderbolt Android Development] Green_Laser:
+1

Santod, Chief Executive Officer
[Thunderbolt Android Development] yumms:
Can anyone please test and see if Onavo works with this kernel? Thanks.

https://play.google.com/store/apps/details?id=com.onavo.android.onavoics
[Thunderbolt Android Development] iHateWebOS:
jellybean uses bcmdhd driver its one of the few differences between ics and jellybean kernel. ics kernel should boot sense3.6 or aosp cm9. a jellybean aosp kernel should boot sense 4 also which uses the bcmdhd driver.
[Thunderbolt Android Development] disconnecktie:
The ICS kernel we have now can boot our current WiFi driver just fine.
[Thunderbolt Android Development] iHateWebOS:
Yes, but that kernel won't boot aosp jellybeans WiFi driver.
[Thunderbolt Android Development] disconnecktie:
Haha if you say so lol. Just because its that way for one device doesn't mean it is the same for another. The ICS kernel source HTC sent us is a hybrid. It works for both sense and aosp with only minor adjustment. Be patient and you will see.
[Thunderbolt Android Development] iHateWebOS:
All ICS kernels are like that.... Very minor changes between sense and aosp.
[Thunderbolt Android Development] disconnecktie:
OK just to squash what started this. I know for a FACT that the WiFi driver from our ICS source works perfectly fine. I'm just going to leave it at that.
[Thunderbolt Android Development] Shadow Death:
If he did a little bit of reading around he would know that already though. :silly:
[Thunderbolt Android Development] iHateWebOS:
I'm sorry :o. I was misunderstood no trolling intended. What I meant is that HTC didn't send a hybrid kernel all HTC ICS kernels boot aosp up to cm9 with almost full functionality. I saw a screen shot of cm10.1, well that's jellybean and that will also boot with ICS kernel. However when CM went from 4.1 to 4.2 they switched over to the bcmdhd driver for WiFi. So when compiling CM10.1 you will need to make this change in the kernel.

Edit: same for sense 4. ICS sense 3.6 uses bcm4330 sense4/cm10.1 use bcmdhd. That's all I wanted to say
[Thunderbolt Android Development] disconnecktie:
No it doesn't for this kernel. The bcm4329.ko module works just fine for jb on the bolt. I know you're not trolling. Im just trying to inform you that the bolt kernel is actually a little different. The WiFi module from the ICS source compiles with cm10.1.
[Thunderbolt Android Development] Shadow Death:
As far as sense 4 goes I think he needs to look into NuSenseX.
[Thunderbolt Android Development] iHateWebOS:
Sorry guys. Anyway I'll play with this for a little bit tomorrow and send Santod some pull requests to make his life a bit easier.
[Thunderbolt Android Development] santod040:
NuK3RN3L Overclocked Edition Updated in OP!

More Governors Added:

Lulzactive

Smartassv2

7 More Modules added
[Thunderbolt Android Development] santod040:
One more time for tonight....

NuK3RN3L Overclocked Edition Updated in OP, now with LagFree Governor as well.
[Thunderbolt Android Development] je2854:
could we possibly have SIO and ROW added? :D
[Thunderbolt Android Development] solcam:
Great work Santod. Bliss Rom doesn't have that script, so I'm still good right? Just install, apply governor, and jam?
[Thunderbolt Android Development] santod040:
Yes sir, that's correct.

I went ahead and added the Aosp OC'd NuK3RN3L for Jelly Bean and ICS Aosp roms(CM9/CM10) to the OP.

It now has working wifi on both cm9 and cm10 for those interested.
[Thunderbolt Android Development] Shadow Death:
Your link points to the original kernel you posted. I went to your page and found the correct one. :p

Edit: I'm not too sure. I tried the "-NuK3RN3L-

Aosp NuK3RN3L, with working wifi on Aosp ICS and Jelly Bean.

Only use this for this one on Aosp roms. (CM9/CM10)" kernel which wifi wouldn't work for me but the LagFree version worked flawlessly.
[Thunderbolt Android Development] santod040:
Thanks, Link fixed...
[Thunderbolt Android Development] iHateWebOS:
Tb users are lucky to have Santod. He's always around it seems. When I was looking for testers, he was the only person that responded to me :D . great dev y'all got here. :thumbup:
[Thunderbolt Android Development] Shadow Death:
I was going to but when I read your post I was running around town like a mad man.
[Thunderbolt Android Development] Dark Jedi:
Yeah santod is da man. He never gave up on the bolt kept pressing on while others threw in the towel and moved on to other phones. Took the leaked ICS build and made it use able while others failed at it. Now with source released his work can release the beast that was chained up by HTC dragging their feet.

Wish I had my bolt still lol. You got my rezound ROM ready Santod? Lol
[Thunderbolt Android Development] iHateWebOS:
You better go back to rez forums before I tell neo your over here :p
[Thunderbolt Android Development] Dark Jedi:
If you tell him I will deny everything and say you hacked my account. :p
[Thunderbolt Android Development] mcpo117:
Just tried the new kernel for CM9 and wireless tether is not working as well as USB mass storage mode. Anyone else having an issue with either of these? I wiped cache and dalvik but didn't do a full wipe because I'm lazy and didn't want to have to set everything back up, is that the issue?
[Thunderbolt Android Development] santod040:
The issue is, you are dealing with a brand new kernel, built from actual ICS source for the Thunderbolt.

Whereas, CM9, was compiled and patched to work with older existing GB source.

So, you will have some things on the current CM9 build which was made before source, that won't work due to the built in GB source, such as the camcorder not functioning, funky Ril connections, Netflix..etc.

Whereas with the new kernel Netflix works, display is smoother, data/ril should get better, as more builds are made working the source into them as well.

Can't have a rom compiled using blobs from GB, to work on ICS and then use the proper source to make a kernel and expect it to fix everything.(may be a good Q. for rom thread)

The rom now has to be redone essentially in order to fully utilize this new kernel for everything it offers.

As of right now, it's a trade off to use either kernel, some stuff will be broken either way.

Things all need to be dialed into the new source, until that happens, you are looking at a properly compiled ICS/JB kernel on a ICS/GB rom.

I'm sure once CM9 is reworked, it should all come together much better. Been talking with Joe about this.

That is the issue, if that helps explain all these little questions at this point in time. I hope that it does.

Let me know. :)

There are other full ICS roms here as well...which work quite well with it.

Not self promoting, just stating facts, in case anyone is interested and maybe unaware.
[Thunderbolt Android Development] je2854:
I am pretty sure no one would care if you are self-promoting... It is well deserved! (:
[Thunderbolt Android Development] ridenickel9:
Agreed!!
[Thunderbolt Android Development] twistedumbrella:
Yeah yeah yeah, rebuild the camera hal... I got the memo lol. Now that the drivers will return valid errors it's possible. The secret behind the original wasn't some enlightened mastery of the source. It was literally "error: need camera parameters for x" so add parameters for x. Video didn't work because it was designed for the kernel we have now, then backported for the kernel then. All it needs now is stripping the backport.
[Thunderbolt Android Development] santod040:
Yeah we have camera and vidcam functional now for JB, :good: just haven't had a lot of time to redo ICS again yet.

Thanks for the insight though and past and present efforts you've done on the camera Hals.
[Thunderbolt Android Development] twistedumbrella:
With CM9, it should be as simple as reverting the hack in frameworks and using the blobs from the ICS build. The only thing stopping that before was the kernel not working with it.
[Thunderbolt Android Development] solcam:
Is there a thread for the Jelly Bean CM10.1 ROM that one could follow to keep up with newer development?
[Thunderbolt Android Development] quickdraw86:
Not currently...
[Thunderbolt Android Development] blackshoes:
I think that's a great idea! I would love to see any updates or news on the JB development. Alpha and Beta releases could be an added bonus.
[Thunderbolt Android Development] santod040:
There's not much point in doing that at this stage.

There was a preview posted.

I don't think a thread full of questions or ETA requests will help much.

There is a thread HERE regarding status, but it's not something any of us that are working on it started, or are going to be updating regularly.

There's not much to report regarding status on any regular basis anyways.

It can pretty well be summed up by saying, everything works except radio(data,sms,calls,etc) at this point.

When/if that gets resolved, it will be ready for consumption.

Not a lot to talk about until then, as far as progress.

I'm sure the hours and miles of logs we have would just bore everyone to death anyways.

Trust me, it's being worked on by several of us and many many many hours have been poured into it already.

When it's done, everyone not hiding under a rock will know.

As was mentioned when the preview was posted, there was no desire to make a thread for it or to do a lot of discussion based on it.

It was just something for everyone to play with while they wait.
[Thunderbolt Android Development] je2854:
*thumbs up*
[Thunderbolt Android Development] je2854:
where can I find the code/source/c files for custom governors/schedulers??

I have everything needed but these custom files....
[Thunderbolt Android Development] yumms:
Can someone please test to see if Onavo Extend works on this kernel, thanks. :good:

https://play.google.com/store/apps/details?id=com.onavo.android.onavoics&hl=en
[Thunderbolt Android Development] twistedumbrella:
Is this a modified or unmodified version? Edit: Nevermind

I started getting everything pushed to git to add all the flashy governors and schedulers so it's probably easier to start where you were. Bringing over everything that'll work from the Nexus

I have all the schedulers in and the governors started. It's all pushed to git to grab it.
[Thunderbolt Android Development] mechanizedmedic:
I would LOVE to have a JB ROM without data, MMS/SMS, and phone! So long as WiFi functions I could really use a good media player ROM for my retired TB.

Sent from Hell.
[Thunderbolt Android Development] twistedumbrella:
Wow... http://www.amazon.com/gp/offer-list...ie=UTF8&qid=1375226817&sr=1-23&condition=used
[Thunderbolt Android Development] Shadow Death:
Twisted.... I just loled haha!
[Thunderbolt Android Development] mechanizedmedic:
woe is me! in my stupidity i have earned your condescendence by expressing genuine interest in something that you have put effort into! may the lord thy god smite me and my enthusiasm from these interwebs! ...save me 4chan, save me!
[Thunderbolt Android Development] twistedumbrella:
My English professor once told me an extensive vocabulary cannot replace lack of substance.

Save the drama for your school play. It's a joke.
[Thunderbolt Android Development] mechanizedmedic:
I was making a joke too, but I suppose irony isn't for everyone.
[Thunderbolt Android Development] santod040:
Try here....
[Thunderbolt Android Development] rprussell:
So... ah...

I flashed this over the LiquidSmooth 1.51MR3 and it just hangs at a black screen after the initial "HTC."

Thoughts? Did I do a bad thing(tm)?
[Thunderbolt Android Development] disconnecktie:
You probably need to make sure you clear caches or that you flashed the correct version.
[Thunderbolt Android Development] rprussell:
Did it - and tried both ICS and JB versions. (The glory of a brand new phone is it doesn't matter how much I wipe data or reflash a ROM, there's nothing to lose!)

I noticed a comment in that thread about how dead that ROM is, so moved on to "GalaxyClone 5."

Seems to be working for the moment, and contains an OC kernel by default, so yay.

(This thing beats the snot out of my Droid X2 btw. Dual core HA!)