They haven't been heavily tested, but IRC seems relatively content with them. Mind you, these were never meant for the Fascinate, but the Mesmerize.
Voodoo
ec10_voodoo.zip
or
http://adbdev.com/danknub/ec10_voodoo.zip
Nonvoodoo
ec10_nonvoodoo.zip
or
http://adbdev.com/danknub/ec10_nonvoodoo.zip
Once again, thanks jt1134 for his scripts.
adrynalyne said:
They haven't been heavily tested, but IRC seems relatively content with them. Mind you, these were never meant for the Fascinate, but the Mesmerize.
Voodoo
ec10_voodoo.zip
Nonvoodoo
ec10_nonvoodoo.zip
Once again, thanks jt1134 for his scripts.
Click to expand...
Click to collapse
ill give it a go . thank you .
Downloading now. Any notable differences over your eb16 kernel?
Hi Adrynalyne!
Just installed. Everything's looking good so far. Will need more time with it though. Thanks.
Installing now. Hopefully no explosions =P
EDIT: I've played with it for 5 or 10 minutes now. Seems quite nice. I'll test the battery and all that fun stuff tomorrow.
Thanks adrynalyne.
Curious about this, however my battery is just settling in on EB01 so ill wait and see what everyone thinks...
Sent from my SCH-I500 using XDA App
A description of features would be nice, thanks!
Downloading and installing
Sent from my SCH-I500 using XDA App
Same here, but since i'm still getting only 30hrs max on light usage I figure what the heck.... give it a try.
chargerfn909 said:
Curious about this, however my battery is just settling in on EB01 so ill wait and see what everyone thinks...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
fitti28 said:
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
Click to expand...
Click to collapse
I wiped both caches (dalvik+ regular) and then flashed right over EB16. No issues here.
I don't know about the monitoring dummy kernel but I'd be surprised if it wasn't in here.
MaskaMage said:
Same here, but since i'm still getting only 30hrs max on light usage I figure what the heck.... give it a try.
Click to expand...
Click to collapse
That's excellent! I never go easy, between texting, this place, and the web in general in lucky to get 17 or so hours lol.. I can charge all day at work or whenever I need if I'm not going to be home though..
Sent from my SCH-I500 using XDA App
fitti28 said:
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
Click to expand...
Click to collapse
You should be fine flashing over eb16 but adrynalyn would have said they have the dummy file if they did. Plus they are very new (ec10 is code for march 10th 2011), so I doubt they have any mods yet.
Sent from my SCH-I500 using XDA Premium App
They have the dummy file.
There, I made you honest.
Not that it matters, but for those interested Quadrant scores (voodoo):
1470, 1593, 1659, 1641
So don't use your precious Quadrants as a reason to not install this
So an average quadrant of 1600??
Sent from my SCH-I500 using XDA App
Flashed over SC 2.9.1 w/ stock EB01 kernel ... (non-voodoo here)
> Wifi still works! Already major improvement over the EB16s for me.
> *228/2 PRL update worked
> Still holding a wakelock on Gps Location Provider on boot, don't know if that has anything to do with the Kernel or not. Running a GPS app clears the lock just as it did before.
> Quadrant (non-voodoo): 946
So far so good. Will see how the battery is tomorrow.
cat /proc/version:
Linux version 2.6.32.9 ([email protected]) (gc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #1 Thu Mar 10 12:52:44 KST 2011
Many thanks as always Adrynalyne!!
kuronosan said:
A description of features would be nice, thanks!
Click to expand...
Click to collapse
fitti28 said:
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Click to expand...
Click to collapse
Description:
It does mostly everything EB16 does, in mostly the same way.
Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.
There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.
This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.
That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.
On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.
So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.
If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.
And just in case I hurt anyone's feelings, I'm not singling you two out, and I'm not flaming you. This is a general public post aimed at addressing the overall concern behind this issue that comes up in every new dev thread. You both seem genuine and non-confrontational, but there is a wide range of people who come into these types of threads and whine and complain. So it's nearly guaranteed that someone else will enter and be like "OMG guize my phone iz broked how come you didnt say phone is broked???!!!!!" Then, everyone can point to this post.
GizmoDroid said:
Description:
It does mostly everything EB16 does, in mostly the same way.
Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.
There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.
This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.
That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.
On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.
So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.
If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.
Click to expand...
Click to collapse
Very nicely said. But i think most of the time when people ask they are not trying to be rude or annoying. They are just not aware or hoping the person who leaked it might have the changelog as well.
Thanks adrynalyne...
Related
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Daswolven said:
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Click to expand...
Click to collapse
im not the flaming type....but this is really unnecessary.
wasupwithuman said:
im not the flaming type....but this is really unnecessary.
Click to expand...
Click to collapse
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Daswolven said:
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
Click to expand...
Click to collapse
if you notice i did not flame you... I could have, but i respect you as a xda member... I just said this was unnecessary, because it is. Like namebrandon said, join the irc channel, but starting a topic like that, then just saying some nonsense, really doesnt need to be done... Your a senior member, we need to be a good influence for the new people. Like i said, i've seen you help out and i respect that; but lets try to keep the Android Development to Android Development. If it's something like this atleast file it in general.
namebrandon said:
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Click to expand...
Click to collapse
I'm one of those people... First kernel i've ever compiled.
and/or you could harass samsung for the kernel signing keys, no coding ability required.
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
jt1134 said:
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
Click to expand...
Click to collapse
really?
you have the signing key for the kernel?
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
jt1134 said:
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
Click to expand...
Click to collapse
my bad.
I was misinformed.
http://forum.xda-developers.com/showthread.php?t=796171
ksizzle9 said:
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
it's wasup_with_u_man....DAMNIT!!!
Yes jt1134, but as your post says, no customer kernel.
Sent from your mom's house via my fascinate.
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Daswolven said:
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Terror_1 said:
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Click to expand...
Click to collapse
See, now THATS funny.
wasupwithuman said:
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Click to expand...
Click to collapse
Lol, I had it so bad on my N1 I would test every fourth nightly CM release with four different kernels for performance and battery. I think I had about 200 advanced quadrant screenshots to delete.
Sent from my SCH-I500 using XDA App
Just thought some might be interested in this (so sue me, i had to ask it):
http://nookdeveloper.zendesk.com/en...-updated-1-2-source-code?page=1#post_20056491
We will be publishing the updated source in the coming weeks. Thanks for your patience.
Click to expand...
Click to collapse
It will be interesting to see what their new source brings, and what we can use from it. Here is hoping that it is sooner rather than later...
EDIT: Well, i am happy to say it didn't take long.. have at it here: http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor-source-code.zip
Awesome news! The faster we can get dalingrin the updated kernel source the better!
Does complying with the gpl allow for a reasonable delay? Because once you get into grey areas like that, what's reasonable? 2 weeks? 3 months?
Obviously they have the source already, so I don't understand when companies release it some time afterwards.
Aye. I hate the "weeks" portion.. given that its out, i dont think its unfair to demand it now. As it is though, i think the GPL gives 60 days (??) for them to publish the code though, so it may be a while.
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
ArmitageID said:
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
Click to expand...
Click to collapse
There isn't much an updated kernel will do to help the Honeycomb SDK.
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
They will do whatever they want until someone sues. What if we lost?
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
I may have been wrong (and will happily say its not the first time); but i did do some reading and found this: http://gplv3.fsf.org/wiki/index.php/User:ashawley/Making_copyleft_work_with_implied_compliance
Not sure if it is totally relevant though..
Source Code
I got this:
Dear Brandon Bennett,
Thank you for your inquiry.
Barnes and Noble will post the updated source code in the near future.
There is still no specific date yet. The link will be posted under terms
of service on the website.
Please accept our sincere apologies for any inconvenience this may have
caused and we look forward to hearing from you.
Sincerely,
Ella
Customer Service Representative - Digital Support
Barnes & Noble
http://www.bn.com/
Visit our NOOK Support site for the latest updates and downloads at:
http://www.barnesandnoble.com/nook/support/
Click to expand...
Click to collapse
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
nemith said:
I got this:
Click to expand...
Click to collapse
Thanks for the info. The nook dev board had another update:
Well, if history is a guide, we released source of 1.0 about 2-3 weeks after launch...
Click to expand...
Click to collapse
As i replied, the anxious part of me does not understand any delay really, other than trying to keep the source code away from us "hackers" for as long as possible. The code is obviously in use, so why not release it?
Ah well..
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
chadamir said:
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
Click to expand...
Click to collapse
Perhaps, but the code is already shipping - its not to say an update can't get pushed out, but just because we can't see the source, doesn't mean current violations are excused.
As it is, the linux kernel is GPL; they can't not release it. So again, i am still frustrated at the hold up...
Probably just the usual corporate speed. They don't like to publish anything before they have to, if only for liability and exposure. Probably the last thing on the rollout list, too.
poofyhairguy said:
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
Click to expand...
Click to collapse
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
Rock on good sir.. That sounds most exciting indeed!
Perhaps a silly question, but to the end user- what will the difference be between the current and .32 kernel? Faster/better/stronger/able to make cappuccinos?
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Nburnes said:
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Click to expand...
Click to collapse
The clock/governor issue is because only the performance governor is compiled into the kernel right now. The broken SD warning is mostly fixed and I believe the same for the battery.
HALLO THAR me again. Ninphetamine 1.0 didn't go so well did it? I thought I'd lost my mojo. Some even had me wondering if my prior good works had been the freaky sort of flukes that would have been better spent on guessing lottery numbers than giving you lot new toys. I was down. Broken. Beaten. So much so even my sarcasm had left me, opting to close the thread after the billionth stupid question rather than scythe down the scum that floats atop our gene pool with my usual aplomb.
Down but not out the Ninphetamine team went back to basics and discovered this mysterious random reboot was still present. Many WTFs were uttered. So we seriously downgraded our building tools. Still random reboots. Many WTFs were screamed from the rooftops. Then someone "helpfully" mentioned that older Samsung ROMs were also plagued with a random reboot issue that disappeared some time a few ROM releases later. The same person "helpfully" mentioned that the Samsung kernel source was released around those early releases. I say "helpfully" instead of helpfully because it would have been HELPFUL if it'd been mentioned before hours had been spent reversing patches and performing voodoo ritual chants to try and get to the bottom of the problem. I looked back on Samsung's source website and discovered a recent KERNEL UPDATE and patched it into my source. BOOM, random reboots gone.
WELL THANKS A ****ING BUNCH SAMSUNG. I am so pleased it didn't occur to you to update your available sources after you'd discovered it was a kernel problem causing the reboots. Full marks for it completely slipping your collective mind that, while being fully aware people would be producing their own works for this phone (I know you're aware because of how you didn't lock the bootloader), it wouldn't be a GOOD ****ING IDEA to perhaps at least release a patch for the problem if not the updated source. MONTHS it's taken you, literally MONTHS.
I hate you. However, I also love you. At least you -did- release an update (albeit being later than the pope to a contraception conference) and your cockup only served to reignite the fire that is my rage.
So, Ninphetamine 2.0. It's true that war drives innovation and the war on the random reboot certainly had us trying many different things and making various discoveries. Many of those have been applied to the now working base so everything I promised for Ninphetamine 1.0 is there and then some.
EVEN FASTAR!!!11. Yep. Get a good tail wind at your back, throw a dice on a double six three times in a row and you can even break 4000 on Quadrant at stock speeds WITHOUT ANY CHEATING. I know Quadrant is largely a meaningless test, results rendered utterly useless by all the retards that mount everything to a ramdisk before running so they can masturbate furiously at HIGHER NUMBERS firmly and unironically of the belief that it increases their self worth and reputation. Performance is smoother however and responsiveness improved as well over Ninphetamine 1.0. Remember if you're the sort that does care about Quadrant scores, given that Android has the attention span of an eight year old child after consuming enough sugar to kill a diabetic in seconds, Quadrant needs 2-3 runs before the OS realises it might be a good idea to make sure the app has the CPU and memory resources it actually wants. Or you can flip the governor to the Performance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FASTURER THAN EVAN FASTAR!!!!!111oneeleven. Speaking of people that like to furiously masturbate over high yet meaningless numbers, the overclocking feature is back with a few bug fixes for good measure. As before it's capped at 1600MHz. We haven't added the GPU clocking yet as it's important to ensure that the current feature set is stable before adding even more. The voltage control interface is also included. Remember, if you're the type of idiot that understands nothing of overclocking or undervolting or how CPUs work in general, don't come crying to me when you try and run 1.6GHz at 800mV and find you have problems. The issue isn't mine, it's yours. Take it up with your parents who are also your aunt and uncle, remember if you can to thank them for providing further evidence that inbreeding is bad and produces morons that aren't capable of functioning in society. Thanks.
Base still at 2.6.35.11. After patching in Samsung's fixes to their own incompetence I'm pleased to note that we're able to stay at least at 2.6.35.11 base, thus keeping many important fixes, improvements and performance boosts from the main kernel team headed up by God himself Mr Linus Torvalds. You thought I was God? While flattered no, I am merely a disciple ready and willing to deputise for when he's too busy.
So download it, run it, break it. Remember, asking me things covered in my initial posts will anger the Android Gods and at best will result in your public ridicule at worst will result in a few plagues upon your dark dingy basement where you no doubt reside.
If you're going to report problems I want more than "HLAP MAI PHONE BROKED". Try and recreate the issue while running logging (instructions on how will follow in a FAQ post). If you're overclocking/undervolting or any combination of the two, stop it and see if your problem persists.
Don't report every single issue you have to me either. It's possibly a kernel issue if overall stability is affected, if you get a full reboot from the boot logo (NOT the boot animation, dropping to boot animation means Android crashed, not the kernel) or if you get a full lockup. If you find that in life in general people tend to stop talking when you're around, or they don't quite seem sincere when laughing at your jokes, it's probably you, not me, that's at fault because you're a bit of an idiot.
Now, there's been a couple of testers that have suffered a rare random reboot. I have a theory on this but to prove it, I need a wider audience. There will be a downloadable kernel that is SOLELY for anyone that suffers a random reboot under NORMAL (normal clock, normal voltage, no tegrak, using OnDemand governor) circumstances.
Download links will be in the download post. If you ask where download links are, I'll give you a very custom one of your own and who KNOWS what that kernel might do. You've been warned.
TO REITERATE - READ THIS
All new downloads should download the release version. Only people who get an unexplainable reboot while running under stock 1.2GHz (or less) conditions at normal voltage with no OC software installed should download and install the workaround version.
Thanks
Unlimited thanks to my wife for her boundless patience with my Android obsessions.
Many thanks to my genius partner netarchy.
Many thanks to my harem of testers, pulser, designgears, Ante0, mattgirv, Obihoernchen, Kullt, Veyka, Lenny, yoda and Rawat.
Download Links
Ninphetamine version 2.1.3 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.1.2 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.1.1 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.1.0 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.5 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.4 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.2 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.2 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.1 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.1 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.0 Release Edition
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Ninphetamine version 2.0.0 Workaround Edition
As stated earlier, only download this version if you have issues with the release version.
TAR file for Odin/Heimdall/CWM app.
ZIP file for flashing via Clockwork Mod Recovery.
Changelog
2.1.3 Release Edition
Re-enabled kallsyms (thanks supercurio for the heads up).
Fixed initramfs to provide support to custom ROMs that use startup scripts in /system/etc/init.d (thanks designgears).
2.1.2 Release Edition
Added a workaround for some ROMs bootlooping after a wipe of /data due to incorrect permissions on the new subdirectories created. Appears to be a ROM bug, perhaps KH3 related, would be handy if ROM developers could look for a fix.
2.1.1 Release Edition
Added FUSE and CUSE support.
2.1.0 Release Edition
Update to Samsung XXKG5 source (Update2)
Added GPU clock control interface (currently has no GUI)
Minimum CPU voltage now properly clamped at 800mV
Misc tweaks and fixes, see github commit log to cfs-exp for full details
2.0.5 Release Edition
Improvements to BLN battery usage.
Changes made to touchpanel sensitivity when the phone is charging to resolve issues for people using certain screen protectors that stop registering user input when on charge.
2.0.4 Release Edition
BLN support added.
RAM console (/proc/last_kmsg) added.
Workaround edition deprecated.
2.0.2 Release/Workaround Edition
More VPN features added.
JHash updated to version 3.
2.0.1 Release/Workaround Edition
CIFS support added.
2.0.0 Release Edition
Samsung's latest source update applied to base.
Kernel base updated to 2.6.35.11.
Overclock up to 1.6GHz.
Voltage control via SetCPU or Voltage Control from 800mV up to 1500mV.
BFQv2-r1 IO scheduler added and set as default.
Optimised EXT4 mount options.
Various other performance related tweaks.
2.0.0 Workaround Edition
As above, but with some patches applied to workaround errata inherent to some Cortex A8/A9 processors.
FAQ
How do I change my GPU clock speed?
Either wait for GUI support to appear in the form of an addition to SetCPU or a standalone GUI, or if you're confident with a terminal:
Code:
adb shell
cat /sys/devices/virtual/misc/gpu_clock_control/gpu_control # To view current settings
echo 267 300 > /sys/devices/virtual/misc/gpu_clock_control/gpu_control # Sets GPU clock from 160/267 to 267/300
We currently have a 450MHz maximum clock and 10MHz minimum clock. The presence of these values does not necessarily mean your GPU can run at these speeds, like all overclocking your results can and most likely will vary. Do not come crying in this thread because you broke your phone or set fire to your desk or gave yourself third degree burns. Actually, do, I enjoy a good laugh.
Hey any update on you guys getting FEATURE done or CHANGE I'd like?
Given that I'm away on honeymoon in two weeks and we're expecting Samsung to release sources actually used with 2.3.4 Any Day Now (tm) any new features are unlikely to appear until September, unless you're part of my IRC Testing Crew and we start testing new features ready for the release of the next major version. So stop asking.
Uncle Hacre, I had a nasty crash and my phone rebooted, I want to help you debug this, what can I do?
Code:
adb shell cat /proc/last_kmsg > lastkmsg.log
Then zip up the lastkmsg.log file and attach it to your post informing me of the issue.
I simply must have every possible second of battery life available, other kernel devs are disabling adb and logcat to make this happen can you do this please battery life is very important to me as I often spend days in Outer Mongolia with no access to power and that extra thirty minutes of battery life could be the difference between me tweeting I've lost my toes to frostbite or not!
Debugging features in the kernel are already disabled. Have I disabled adb/logcat? No. Will I? No. I'm at 50 hours uptime on my phone with just under 40% battery remaining. I see no battery issue. Whether the life can be slightly improved or not, removing a key debugging function from the land of custom ROMs is an incredibly stupid idea. What if you flash a custom ROM and there's an issue and the ROM developer needs debugging information to fix it? What if you install an app that has a problem and you cannot give any feedback to the app developer? Are you prepared to flash a kernel that has adb enabled any time you have an issue? For the minor gains in battery life it isn't worth it.
There's a ClockworkMod Recovery with a higher version number than the one you're providing surely bigger numbers means better why aren't you providing it?!?!
I'll update CWM Recovery as and when a version appears that provides a feature or fixes a bug that we're afflicted with.
WAAAAHHHHHHH QQ I have to wait ONE ENTIRE SECOND for my phone to wake up from standby!!!111oneeleven. This is totally unacceptable and it is ruining my life!!!
Of course it takes a second to wake up from deep sleep. Everything has been shut off, the CPU placed in low power mode and the entire OS placed into suspend. I don't know about you but it takes me far longer than one second to be fully coherent and responsive when I wake up in the morning and I've only got one brain to worry about, the SGS2 has two of them! Shut the whining up about this complete and utter non issue.
What ROMs will this work with?
The kernel has been tested with VillainROM 2.0 and 2.1. It should in theory work with any ROM based on a stock SGS2 ROM. However if your ROM developer requires a custom initramfs for features you may encounter problems.
How do I overclock my CPU?
Use SetCPU or Voltage Control, ensure you have the latest version.
How do I change the voltage of my CPU?
Use SetCPU or Voltage Control, ensure you have the latest version.
I cannot use adb install anymore.
We're aware of this and are working on a solution for the next release. In the meantime adb push the apk to the phone and install using a file browser.
My phone was running fine for hours but I just now had a random reboot. What should I do?
Learn to read. Download and install the Workaround Edition.
I have Tegrak installed while using your kernel, does that make me an idiot?
Yes.
Super Happy Fun Time
Should you arrive in this thread bereft of the basic intelligence required to remember to breathe in and out as needed and you ask questions/make posts that clearly demonstrate this fact, I'll be sure to give you the attention you deserve in this very post.
geistteufel said:
I don't see bfq scheduler in set cpu, is it normal?
Click to expand...
Click to collapse
Yes it's normal. Your IQ isn't. What on Earth possesses you to even open SetCPU if you're looking for schedulers in there? Do you also complain to car manufacturers when you can't find your spare tyre in the engine bay or you find that a motorbike has no ashtray?
saintxseiya said:
Hi,
do i have to set setcpu in some way or is the kernel all doing by itself?
Cheers.
Click to expand...
Click to collapse
If only I had taken the time to write a FAQ post, on the first page of this thread that would answer this question...
golf60 said:
wipe cache and dalvik cache before flashing....
Click to expand...
Click to collapse
I'd really like it if people with a shoe size rivalling IQ would refrain from giving advice to users of our kernel. Advising to wipe cache/dalvik before changing kernel is akin to advising checking tyre pressures because the gearbox just fell out.
Kollegah said:
Is this kernel compatible with cm7?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Or in other words: "Hi, I'm too lazy to read threads or use the search function." This has been addressed in several posts in this very thread.
Cygnuss said:
So what does this version do VS the 2.0.0?
Click to expand...
Click to collapse
Wow, I really wish I'd taken the time to put a changelog on the first page after the download links. If I had, then surely no one would need to ask me what's changed in new releases. Thank you so much for highlighting my failing!
Logi_Ca1 said:
Is anyone else running 200Mhz at 475mv? Works fine on my phone, passes stability test 2.11 as well. Or maybe there's a softcap for the minimum value?
Click to expand...
Click to collapse
It would seem I live in a parallel universe, one where I'm sure I write things down yet they do not appear. This can be the only explanation for you not seeing "Voltage control via SetCPU from 800mV up to 1500mV" in the THIRD POST ON THE FIRST PAGE. Well there's that explanation, or there's you being a moron. Hmmm...
varenathan said:
Dear all,
How to install Ninphetamine version 2.0.1 Release Edition using ODIN? I have downloaded it "TAR file for ODIN" here : http://forum.xda-developers.com/showthread.php?t=1179814
, n extract it and found this zImage. Please tell me how to use this zImage?
My kernel version at the moment : I9100XXKG1 but my PDA/PHONE/CSC = KG2.
Thanks n sorry if this question has been replied before but i couldn't find it anywhere.
Click to expand...
Click to collapse
varenathan said:
But i found it's not a .tar file, it's zImage. Is this the same? sorry for nob question..
Click to expand...
Click to collapse
varenathan said:
Thanks mate! Just realized it's a .tar or .zip in notification, but when i open it in windows, it shows only ninphetamine-2.0.1-release.
So, another Question. Is it possible to flash back my last Kernel version if i flash ninphetamine (just in case, something wrong with it)? How to do that?
Click to expand...
Click to collapse
varenathan said:
thanks mate! Usefull information indeed!
EDIT :
How to take out the zImage and where to find it from the last ROM which i've just flashed before i flash ninphetamine?
Click to expand...
Click to collapse
varenathan said:
I have I9100XXKG1.
Okay, thanks again. I thought i should move the zImage from my sdCard and then place on my PC and then i can flash it to a new Kernel.
So blessed today, found these people who help me
Click to expand...
Click to collapse
varenathan said:
hahaha.. be my guest. I am just trying to be a good user for my phone
Click to expand...
Click to collapse
varenathan said:
Which i have already made, but i am not sure for the kernel version, as i always get the new version from my ROM Developer it's included, n shouldn't flash it seperately
Click to expand...
Click to collapse
AND THE CURRENT THREAD RESIDENT INEPT BUNGLING RETARD AWARD GOES TO:...you. How the hell did you even manage to find this thread? In fact how did you even manage to survive long enough to use a computer? Or am I looking at this from the wrong perspective, should I be thrilled that a Chimpanzee has managed to procure a PC and an SGS2 and already managed to flash a custom ROM to it? You sir are the reason new scissors are labelled with "Warning: contains sharp objects". Answers to all of the questions you've asked are freely available throughout the SGS2 forum and in the form of guides all over the internet. So not only are you bereft of the basic intelligence required to figure out which way is up, you're also lacking the kind of effort that's required to carry out the most simple tasks like "find a useful collection of words" and "read a useful collection of words". Shame on you.
-Zork- said:
Have a question about this kerel, I got 1 % drop per hour in standby ( sleeping 8 hour and wake from 100% go down to 93%). Is it normal?
Click to expand...
Click to collapse
No it's not normal. This is outrageous. Thank you for submitting this bug report so that myself and netarchy can get to work right away on the part of the kernel that is supposed to suspend the space-time continuum when your phone goes into standby so that it uses no power whatsoever. You see we weren't sure whether to suspend time or have it invent hydrogen fuel cells and circumvent the battery during Deep Sleep so we opted for the far easier suspension of space and time. I'm awfully sorry that our experiment failed and we'll now look into kernel code that can combine matter and anti-matter for a low power sustainable reaction so that you lose no precious battery life at all while the phone is in standby. Or you could do us all a favour, including yourself and turn your phone off and never ever touch it again. That way the number of people you communicate with will be curtailed, your phone will never lose power and you'll never need to sully one of my threads again. You have all the intellectual creativity of a box of hair, a command of language worse than that of a deaf mute and an ineptitude so offensive it cannot be summed up in a single word, so I'll try three: You're a moron.
Warrimonk said:
Can't seem to get 1.6ghz stable at all, even at 1.5mV. Running lightening 4.1 and this kernel. any tips?
Click to expand...
Click to collapse
Yes. Kill yourself. Asking such a question means you're clearly beyond help, have no clue about overclocking and don't deserve such a nice phone. Free up some oxygen and resources for the rest of us please, thanks.
CrimsonAxe said:
This might sound dumb, I'm using Litening rom 4.1 with Ninphetamine 2.0.2
What app should i use to underclock my voltage? i tried Voltage Control and after i've got my settings done, i try to check the current battery voltage it's still at 4004mV? Does that mean the application is not working?
Click to expand...
Click to collapse
Might sound dumb? No no, it IS dumb. 4004mV is how much voltage is remaining in the battery you twatneck. Why are you asking what app you should be using when it is clearly stated ON THE FIRST PAGE OF THE THREAD?. How has it escaped your grasp when editing voltages that are all ~1000mV that over FOUR THOUSAND millivolts might just be something else?? In fact how did the words BATTERY VOLTAGE not clue you in after changing CPU VOLTAGE? You're a (unfortunately) breathing example of never underestimating the lowest level of stupidity. If brains were chocolate bars yours would be labelled "Fun Size".
NeoPhyTe.x360 said:
And do you think that #twiter word in my signature, is a fail? Maybe you don't understand why I put things like this
SARCASTIC MODE ON
I put twiter in a text, but in the hyperlink I'm seeing twitter, oh **** i'm clever!
Click to expand...
Click to collapse
NeoPhyTe.x360 said:
my twitter was deleted months ago, man.
Since Feb, 2011, and Google knows
Click to expand...
Click to collapse
NeoPhyTe.x360 said:
And you are a moderator?
Maybe you have to understand it first, because I don't think that people in usa are much clever.
Click to expand...
Click to collapse
This guy calls himself a developer. Yes your "#twiter" link is a fail because a: it isn't spelled properly and b: it 404s. Why keep it there if it's a dead link? Because you didn't know until it was pointed out to you, that's why. As for "I don't think that people in usa are much clever"....oh the irony. If your kernels run as well as you post I'm sure scattered around the XDA userbase is a smattering of dead or unresponsive SGS2s. Which wouldn't surprise me. Taking a look at your kernel thread it's clear that you've as much clue as a lobotomised Orang-Utan. More steps on your CPU frequencies than there are on the stairway to heaven, you think somehow that 500MHz uses less power than 200MHz, governors included that anyone doing five minutes of research would know they're unstable, you advertise standard kernel features as unique features in your kernel (CFQ, CFS, boy those sure are new features!) and to top it all off you've got the cheek to take code from Ninphetamine and then come here and ****post. I've more chance of developing film in direct sunlight than you have of developing anything close to competent and the fact that you have the audacity to consume bandwidth on the internet offends me. If braincells were matchsticks you couldn't light a candle, so kindly return to your thread full of fail and leave us big boys and those of us with IQs higher than room temperature to get on with grown up things, mkay?
NeoPhyTe.x360 said:
I have been living in Chester this spring/summer some months, and maybe I'll go in september, so I hope we could meet, because maybe my braincells can't light a candle, but I know that my fists yes. Coincidences of life...mate
Click to expand...
Click to collapse
Holy **** an actual threat of violence from the internet. Hahahahahaha. At least I think that's what it is. You "know that your fists yes"....I can only assume this is a threat...unless you're chatting me up and want to fist my bottom? I'm not that way inclined mate, sorry.
Tarek82 said:
Try running 1.6ghz under a different rom, I have no problem running 1.6ghz with Cognition S2 using set cpu
Click to expand...
Click to collapse
I'm revoking the other guy's retard award because you've single handedly come into the post and shown us in fewer than 20 words just what being a hap-hazardous retard with an IQ smaller than a bullant's testicle and the sharpness of a dull stick of butter what being a retard is all about.
No no, please, pray tell, how running a different ROM will magically make a CPU run at 1.6GHz when it wouldn't before? This, you cretinous simpleton, is akin to giving a steam roller a paint job and expecting it to pull an extra 100mph as a result. Please promise me that's the last time you ever post on the internet, because if you keep this up you'll dilute the global IQ so much we'll all start eating our shoes.
apache86 said:
I realy appreciate your work but arent you going a little too far with your language and comments? you mentioned your wife at some part of the long story at the first post (who can actually read all this? are you an author as well?). are you also talking to her like this when she doesnt understand somthing? your kids? im definitely not jealous in her
Now come down a little bit with your language and dont help us if you cant do that as a fully grown man (are you a grown man?)
This is the common nature of people, asking dumb questions somethims but on the other hand, do you realy expect them to know as much as you do on changing kernels and messing with them? the fact that you might have no life does not mean you should take it out on others isnt it?
Now come on, tell me what you think about my post, dont spare any word of it!
Click to expand...
Click to collapse
Oh yippee the language police arrived. I'm so pleased you found the opportunity to take time away from your perfect life your perfect wife your perfect children and your perfect job situated high within that glorious and shining ivory tower of yours to descend upon us normal folk to educate us about our terrible language and vulgar manner of insulting those whom we only see as morose shambling idiots who cannot even manage to search a thread, whereas you see them as gleaming examples of humanity, bereft of love, attention and experience.
Well, as you're now down here on planet Earth, you globulating and sickeningly sweet preacher of goodwill, may I first introduce you to the word hypocrisy. Often rife among your dogooding kind, it means that you sit on high quaffing down pints of innocence and regurgitating it upon us regular folk as some kind of moral education, while still sneering like a ****ing 1930s cartoon villain. If you could get the shine of your halo out of your eyes for a few seconds and deign to look upon the unwashed masses, you'd recognise that dishing out lessons in manners doesn't often mix well if you throw in a dash of "insult their lack of any life worth living" or "let's have a pop at his wife".
You sir, are a **** but not only that, you're the worst type of ****. I'd rather deal with 20 of EACH of every idiot that precedes you in this posted collection of horrors than one of you, you vile and pathetic excuse for a human being. How dare you feign to come into my thread and chastise my use of language when you can't even ****ing spell let alone string a sentence together. You're not only offensive to the morals you're offensive to the eyes, you write down pure eye cancer and I implore you to stop.
I have never and will never excuse anyone's lack of common sense. There's a difference between not knowing and not even having the wherewithall to help your sodding self. I berate the latter and assist the former, whereas you don't flap your ****in caviar chompers unless there's some moral crusade to embark upon. How about you be honest with yourself and realise that you only arm yourself for combat and mount upon your trusty forum steed to put right what mere mortals like me have wronged, to give yourself grace and relief from the sorry, putrid and langquidly depressing state your own life is in. How about you spend even half the effort you spent ejaculating that illiterate and berating post into my thread, on sorting your own miserable existence out and then maybe we'd both be a lot happier. Your insignificant blip of an existence wouldn't be quite so worthless to you and maybe, just maybe, you'd keep your hypocrisy laden lectures to yourself which would in turn make me very happy indeed.
****, LOLed so hard I woke up my kids!....thank you!
Nice one, will try soon. Btw i love your epic stories in your OP
oh jesus i'm dying after reading the whole story in op ...rotfl
edit: just to say something useful, i'm going to try it!
rocketpaul said:
Nice one, will try soon. Btw i love your epic stories in your OP
Click to expand...
Click to collapse
You should start with 7
Swyped from my Galaxy S II using Tapatalk
Artius89 said:
oh jesus i'm dying after reading the whole story in op ...rotfl
edit: just to say something useful, i'm going to try it!
Click to expand...
Click to collapse
If you die, you cannot enjoy the even better entertainment next time round... So try and survive
@ninpo, did you remind them that anyone trying to use it with Tegrak is subject to capital punishment?
Any plans for CM7?
pulser_g2 said:
@ninpo, did you remind them that anyone trying to use it with Tegrak is subject to capital punishment?
Click to expand...
Click to collapse
Yes, read the thread, don't make me make you my first example in post #5, you know I will.
Cool intro, thank you guys for all the time and effort you put into this. Downloading now and testing on villain 2.1.
Cheers!
saifbechan said:
Cool intro, thank you guys for all the time and effort you put into this. Downloading now and testing on villain 2.1.
Cheers!
Click to expand...
Click to collapse
No problem.
This kernel will make your phone turn into a blowjobs and pudding machine.
In all srsness.
Its great, use it, love it <3
Your a funny dude you must be Scottish surely?
Sent from my GT-I9100 using XDA App
Nice work, I'm looking forward to this kernel as it evolves. Will be testing it out tomorrow.
I'm especially looking forward to GPU frequency and voltage control, as I'm running my GPU at 750mV instead of the default 1000 and the phone runs noticeably cooler when playing games, and thus logically would mean superior battery life while gaming. This would be a killer-feature in future releases, for me at least.
It would also be interesting to know if we'll eventually get "internal voltage" control some day. My deduction is that that would be the voltage for most things other than the CPU and the GPU like for example the hardware decoder/encoder as being the most significant part of the SoC, if it truly is things like the decoder, then it would boost battery life for video playback by some amount.
dibdab214 said:
Your a funny dude you must be Scottish surely?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
"British by birth, English by the grace of God".
AndreiLux said:
Nice work, I'm looking forward to this kernel as it evolves. Will be testing it out tomorrow.
I'm especially looking forward to GPU frequency and voltage control, as I'm running my GPU at 750mV instead of the default 1000 and the phone runs noticeably cooler when playing games, and thus logically would mean superior battery life while gaming. This would be a killer-feature in future releases, for me at least.
It would also be interesting to know if we'll eventually get "internal voltage" control some day. My deduction is that that would be the voltage for most things other than the CPU and the GPU like for example the hardware decoder/encoder as being the most significant part of the SoC, if it truly is things like the decoder, then it would boost battery life for video playback by some amount.
Click to expand...
Click to collapse
The next logical step is to work on voltage/clock control for the GPU. We'll then look at the internal voltage and what it affects. Not all Samsung's code is easy to follow.
Hacre said:
Yes, read the thread, don't make me make you my first example in post #5, you know I will.
Click to expand...
Click to collapse
Ahhh... Wasn't there a minute ago Place bets on when you need an extension of post 5 due to 40k character limit? ;0
I'm still running the original stock VZW/HTC ROM. I know, I know, slow adopter... I'd like to root and go with a ROM that delivers better battery life and a basic debloat. However, nearly every ROM I read about seems to have a major (in my humble opinion) flaw. A non working camera or video camera, non working voicemail notification, malfunctioning signal strength bars, no 4G, etc., etc.
Is my only choice really a Froyo ROM? I'm not willing to stomach any major loss of functionality (or apps), be it phone, camera, calendar, GPS, navigation, various google apps, Bluetooth, WiFi, 3G and 4G, working signal strength bars, etc. I guess I am also in the "I prefer Sense" group but also have not given non Sense ROMs any time.
If responding I kindly request a few sentences of explanation/clarification rather than just saying "Get ROM X, it rocks, it is the best". Thanks in advance.
Everything works on most the gb roms, with some needing certain fixes to fix certain things. Gingeritis 3d, with chingys new radio is tits imho
Sent from my TBolt using my f***king thumbs...
Well, I'm not going to give you a few sentences, but I can tell you that I use Gingerth3ory (link in my siggy) and everything works, including vvm as long as you apply the bootable zip fix for that. Before, vvm was the only thing not working.
Camera, videocamera, wifi, 3g, 4g all work. I switched to youmail for vvm because I wanted netflix over stock vvm so that meant a GB ROM.
I highly recommend Droid Theory's latest Senseless Rom. This is the smoothest and quickest ROM of his yet and that is saying something. There is a large mod community if you're interested in that. Most importantly, DT is very responsive and provides great support. He will be coming out with an update very soon to fix the market issue.
Sent from my ADR6400L using XDA App
http://forum.xda-developers.com/showthread.php?t=1176922
http://forum.xda-developers.com/showthread.php?t=1187545
http://forum.xda-developers.com/showthread.php?t=1187545
Just showing there's been 3-4 other similar posts in the past few hours, just to avoid fragmenting answers or not getting the answer you wanted.
Just follow my link in my signature.
Synergy is the way to go.
Thanks folks.
OK we have votes for Gingeritis 3d, Gingerth3ory and Droid Theory's latest Senseless Rom. Has anyone ran more than one of these? Any important compare/contrast between them? I care much more about stability and battery life over eye candy. Those are my top 2 concerns. If those things are improved over the stock VZW/HTC ROM I should be happy. The biggest problems with this stock ROM for me are maintaining a data connection when switching from 3G to 4G and back. Also the speed of the GPS lock is very slow. How are these things in these recommended ROMs?
(yareally: You posted 2 identical links but mentioned 4 threads. Yes the questions in some of these were related to mine but certainly were not identical request.)
I'm going to venture a guess you haven't actually looked at the threads or the dev's pages. Most have a thread for bug reports. GB ROMs are about as solid as any OTA these days. If you're new to flashing DO NOT, DO NOT use Synergy. It's a frankenstein project with no official stable release and a constant onslaught of nightlies with no end in sight. STAY AWAY FROM NIGHTLIES. Try BAMF. Try Gingeritus. Try Eaton. Try GING3R3DTH3ORY. Try something that's known to work and isn't revised several times a week. From the sounds of it, Eaton might be what you want. It looks and works very much like stock.
swamp2 said:
Thanks folks.
OK we have votes for Gingeritis 3d, Gingerth3ory and Droid Theory's latest Senseless Rom. Has anyone ran more than one of these? Any important compare/contrast between them? I care much more about stability and battery life over eye candy. Those are my top 2 concerns. If those things are improved over the stock VZW/HTC ROM I should be happy. The biggest problems with this stock ROM for me are maintaining a data connection when switching from 3G to 4G and back. Also the speed of the GPS lock is very slow. How are these things in these recommended ROMs?
(yareally: You posted 2 identical links but mentioned 4 threads. Yes the questions in some of these were related to mine but certainly were not identical request.)
Click to expand...
Click to collapse
last one was a miscopy, there was another one at least on the front page, but I was half asleep at the time. I said 3 to 4 btw, not 4. There have been lots though of rom reccomendation postings though and felt you would get a better idea by reading what other people had asked already.
i'm using Synergy with the "06275r" radio and the dreamKernal. i also have SetCPU on set to "performance". it runs really smooth and the battery life is better then stock.
i've tried pretty much every ROM out there and have had this running for several days now. i like it and will keep it for a tad bit longer(why just a tad? i can't help it.. i like to keep trying new ROM's)
loonatik78 said:
If you're new to flashing DO NOT, DO NOT use Synergy. It's a frankenstein project with no official stable release and a constant onslaught of nightlies with no end in sight. STAY AWAY FROM NIGHTLIES....Try something that's known to work and isn't revised several times a week.
Click to expand...
Click to collapse
I have to disagree. Just because Synergy is updated every night does not mean you must flash reflash every day. The nightlies have very minor revisions (adding HTC Car Panel, changing the host file for better ad blocking, changing the Market icon color, changing the email splash screen, etc). If you don't need the newest revisions, then don't flash the latest nightly until something comes along that you really want/need. Synergy nightlies aren't released because it is an unstable rom. Quite the contrary. I have tried roms from 4 other devs and Synergy is the fastest & smoothest of them all. The only time I've had lockups or reboots is when I overclocked too much, which would have happened on any rom.
Don't be dissuaded from trying Synergy because there are nightly updates. If anything, that should tell you the devs are committed to making it better.
sublimaze said:
I have to disagree. Just because Synergy is updated every night does not mean you must flash reflash every day. The nightlies have very minor revisions (adding HTC Car Panel, changing the host file for better ad blocking, changing the Market icon color, changing the email splash screen, etc). If you don't need the newest revisions, then don't flash the latest nightly until something comes along that you really want/need. Synergy nightlies aren't released because it is an unstable rom. Quite the contrary. I have tried roms from 4 other devs and Synergy is the fastest & smoothest of them all. The only time I've had lockups or reboots is when I overclocked too much, which would have happened on any rom.
Don't be dissuaded from trying Synergy because there are nightly updates. If anything, that should tell you the devs are committed to making it better.
Click to expand...
Click to collapse
I don't agree with that and I'll tell you why. Let's say I tell Joe Bob to go try synergy. He does, and downloads who knows what on whatever night. Then he has a problem... Now what? Try to decipher Ziggy's advice? Try another nightly version? As far as I'm concerned nightlies are for developers. I think that because that been the whole point of nightlies from the beginning. I'm pretty sure CM was the first, but even they did that in support of a release candidate aiming towards an official release. I wouldn't tell someone "Go try a CM nightly!" even if they were looking mostly solid. I've read almost all of the thread for synergy. It's hardly a work without error. I don't believe that project is dedicated to producing reliable ROMs. They show no sign of such in any form, be it a release candidate or a final release. It appears to be a few developers tinkering and experimenting, in many cases against the law, and I cannot in good faith suggest someone fresh on the scene jump into one of the most convoluted ROMs for the Thunderbolt.
I've been using nightlies for INC and they've all been stable for the past several months. They just keep adding features. At first it sort of bugged me that I never had the most updated version but then I just lived with staying with my version for several months until I got bored enough to flash the latest.
If nightlies isn't your thing then that's fine but I don't see a reason to tell other users to stay away from them. Generally they *will* have more bugs because the dev's don't thoroughly check the ROM's before they release - they expect the people who flash to find the bugs and then they fix it in the next releases, but after a while all those bugs are gone- then they move to adding a new feature and that may have a bug, and the cycle continues.
But in most cases these bugs are very minor and overall the ROM is superior in performance / battery / features than other ROM's.
POQbum said:
I've been using nightlies for INC and they've all been stable for the past several months. They just keep adding features. At first it sort of bugged me that I never had the most updated version but then I just lived with staying with my version for several months until I got bored enough to flash the latest.
If nightlies isn't your thing then that's fine but I don't see a reason to tell other users to stay away from them. Generally they *will* have more bugs because the dev's don't thoroughly check the ROM's before they release - they expect the people who flash to find the bugs and then they fix it in the next releases, but after a while all those bugs are gone- then they move to adding a new feature and that may have a bug, and the cycle continues.
But in most cases these bugs are very minor and overall the ROM is superior in performance / battery / features than other ROM's.
Click to expand...
Click to collapse
Please read what I wrote. I would not tell a NEW user to try a nightly. That would be stupid. The last thing some virgin flasher needs is to flash some nightly that got some new test kernel cooked into and its quirky as hell, or some jazz like that. We ALL wanted our first flash to work and not freeze or crash. I'm telling a NEW user to stay away from nightlies, not the experienced guy. I don't care how stable one night's version might be, or if almost all of them are. They are test beds and you don't know what you're getting night to night. And NO nightly I've ever used has been quirk-free.
loonatik78 said:
Please read what I wrote. I would not tell a NEW user to try a nightly. That would be stupid. The last thing some virgin flasher needs is to flash some nightly that got some new test kernel cooked into and its quirky as hell, or some jazz like that. We ALL wanted our first flash to work and not freeze or crash. I'm telling a NEW user to stay away from nightlies, not the experienced guy. I don't care how stable one night's version might be, or if almost all of them are. They are test beds and you don't know what you're getting night to night. And NO nightly I've ever used has been quirk-free.
Click to expand...
Click to collapse
Well.. I've had plenty quirk-free. But the Incredible nightlies are more polished than the thunderbolts.
I think you shouldn't tell them not to flash a nightly, just warn them of possible issues and explain to them what they are (and they would see this anyway because every nightly thread I've been to explains this)
POQbum said:
Well.. I've had plenty quirk-free. But the Incredible nightlies are more polished than the thunderbolts.
I think you shouldn't tell them not to flash a nightly, just warn them of possible issues and explain to them what they are (and they would see this anyway because every nightly thread I've been to explains this)
Click to expand...
Click to collapse
if someone is starting a thread like this, reading threads probably ain't in their game plan. I don't give advice to strangers I wouldn't give to a friend. You run something like a version of BAMF and you're running something a dev has hung his hat on. Not so with a nightly because there will be another tomorrow night! Telling a noob to try a nightly, regardless of stability, is like telling your kid to learn to drive behind the wheel of a Kenworth. If something goes wrong, its going to become a bigger deal than it would be if the guy had flashed 2 or 3 ROMs. This seems real obvious to me. Are you forgetting your first experience rooting and flashing ROMs? I'm not gonna warn someone of the dangers of doing something I consider stupid. I will say "If you want to do something stupid, go flash a nightly for your first ROM. If your LUCKY it will all work right. If it doesn't, go fly a kite because you're own your own, bro."
Thanks for the further comments. Let's not try to get too side tracked on one ROM with many nightlies. I definitely prefer to steer clear of a ROM with nightlies. I'd like to let others do all that valuable beta testing and simply benefit from their work. Selfish - sure but uncommon - no.
Just to clarify some personal details that may help with recommendations. I've read many of the posts here from the devs themselves on their ROMs. However, slogging through hundreds of pages on a small handful of ROMs is not my idea of fun... I'm quite computer/phone literate but have not done programming in years. I also work in the software industry. After years of crappy and unstable WinMo devices and plenty of random freezes, resets and data loss, I've found a pretty nice new home with Android. I'm not afraid to experiment, trouble shoot, etc. However, I want a phone to USE much more than to constantly tinker, repair, troubleshoot, etc. I'd like a really mature, stable bulletproof ROM along with the ability to have GB and keep Sense. It is incredibly difficult for me to read the oftentimes massive features lists on the first page of any given ROM thread and distinguish it from other competing offerings. Despite being pretty computer literate, most of those pages are nearly entirely "greek" to me.
Perhaps there is no single best ROM or recommendation but I am going to continue to read all the replies here and hopefully get my choice narrowed down. Of course I realize no ROM choice is permanent. I'll just say again I like to USE my device rather than constantly "tinker".
Cheers.
InfuseTh3ory ... Try it.
Since you like Sense then check out Gingeritis
http://www.themikmik.com/forums/viewforum.php?f=271
Sent from my ADR6400L using XDA App
gingertheory is a nice solid build that I've been running the last couple of weeks. No big deal breakers as far as bugs.
I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
No such thing as correct or incorrect, it is all personal taste. Some might like one ROM over another. Does that make it better than another? Nope.
Take cars for example. Some people like to leave it stock. Some might like to increase its performance and add engine modifications. Some might like it to handle the roads better so they might upgrade its suspension. Others might like to change its appearance and paint it and add body-kits. Is one car better than the other? Depends on who you ask.
Harry_Y said:
I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
Click to expand...
Click to collapse
This thread will get real out of hand.
But before it dissapears. the main reason most of us say its bad, is with the history of At&t's releases. They mess stuff up, have issues within the kernals, and a big BIG issue with them right now that w/o source, we dont know if its fixed.
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
gsrrr said:
No such thing as correct or incorrect, it is all personal taste. Some might like one ROM over another. Does that make it better than another? Nope. .
Click to expand...
Click to collapse
not taste/opinion in the fact(from their history) that the coding is a mess. and broken everywhere.
You come to a developer forum to run fully stock?
That's what goes through my head when I see people afraid of flashing.
If you want the AT&T firmware at least wait for somebody to post a debloated version since your going to disable them anyways or actually learn how to do it yourself. Since you have access to the forum with so much information.
Maybe take it 1 step further and grab the AT&T firmware and customize it to your liking, you don't even have to post it just use it.
This isn't a great thread cause Versus threads go nowhere...
MotoMudder77 said:
This thread will get real out of hand.
But before it dissapears. the main reason most of us say its bad, is with the history of At&t's releases.
They mess stuff up, have issues within the kernals, and a big BIG issue with them right now that w/o source, we dont know if its fixed.
........
Click to expand...
Click to collapse
Thank you
Harry_Y said:
I had started a thread I just got the official ICS Upgrade
In that thread some had indicated that a custom ROM should
be used and not the the official ICS Upgrade from AT&T.
In an effort to not get that thread of track i will ask here:
What is the real difference with the AT&T Official ICS ROM and the Custom ROMs?
I am fully aware AT&T has loaded a bunch of junk in,
and I went through and disables and deleted much of it.
But what truly is so awful about it?
And if it truly is so bad, what is the "Correct" ROM to use?
Thank you
Click to expand...
Click to collapse
Dude. Do the math. You're posting in a development forum that strives on customizing, building, and creating custom sh$t for our devices. Why would you think that 90% of the people here are looking for and using custom roms?
gsrrr said:
No such thing as correct or incorrect, it is all personal taste.
Some might like one ROM over another. Does that make it better than another? Nope.
- Snip -
.
Click to expand...
Click to collapse
I can appreciate people wanting to customize their devices.
That being said customizing just for the sake of customizing is not really
of interest to me; Increased functionality or an issue being corrected is.
So the real question for me would be what real issues with the
Stock ROM get corrected? and what Real features get added.
Thank you
task650 said:
Dude. Do the math. You're posting in a development forum that strives on customizing, building, and creating custom sh$t for our devices. Why would you think that 90% of the people here are looking for and using custom roms?
Click to expand...
Click to collapse
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Harry_Y said:
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Click to expand...
Click to collapse
Go to the dev section, pick a random rom thread and look at the features.
That is just an example of what is beneficial.
Harry_Y said:
I fully understand that, I also realize people get emotionally attached to things.
What I'm trying to learn is what is the Real advantage with the custom ROM.
Thank you
Click to expand...
Click to collapse
There are many different things. Mods add to the functionality of the phone. Take the 14 toggle mod for instance, no need to enter settings to change common things. Skip tracks with volume buttons. You can also increase battery life with various kernels by UV/uc. It allows you to make your phone function and do what you want it to. The stock firmware is too limiting in this ability
Sent from my SGH-I777 using xda premium
Harry_Y said:
I can appreciate people wanting to customize their devices.
That being said customizing just for the sake of customizing is not really
of interest to me; Increased functionality or an issue being corrected is.
So the real question for me would be what real issues with the
Stock ROM get corrected? and what Real features get added.
Thank you
Click to expand...
Click to collapse
Of course there is an increase in functionality or else why would devs create custom ROMs. What each ROM has that differs from others are listed in their respective threads. Check it out and see if any interest you. If you are satisfied with stock, stay stock. Not a big deal.
LiLChris06 said:
You come to a developer forum to run fully stock?
That's what goes through my head when I see people afraid of flashing.
Click to expand...
Click to collapse
Honestly, I used to hang around here for the community - but that's quickly turning me into a simple lurker.
I'm extremely interested in the developers work. However, I find that the stock factory firmwares are every bit as good or stable as anything that gets turned out in the dev areas. The stock ROMs also do everything I need and want. Plus, I don't like AOSP Android, and that seems to be what everybody is focusing on these days. Also, the 3rd party roms generally have too much changed, removed or added for my tastes.
Edit: Oh, and while I generally like the OEMs code, I have no problem using a good 3rd party kernel.
AT&T releases are typically buggy. The developers here either fix those bugs, or use firmware bases from the international version that are more robust and stable. It is too early to know what bugs this UCLE5 release may contain, but the original AT&T UCKH7 firmware had lockscreen security issues, the official AT&T update UCKK6 broken bluetooth hid and serious power management issues. The AT&T ICS leaks leading up to this version, UCLD3 and UCLD4 had a very serious flaw in the kernel which caused several people with the I777 to lose their device due to eMMC chip damage. Since the kernel source code for the current official AT&T UCLE5 has not been released yet, it is not possible to confirm that the kernel supplied with the UCLE5 release is free of this serious issue. Therefore, it would be advisable to either not run this firmware, or use a modified rooted version in which the kernel is replaced with a known safe kernel.
creepyncrawly said:
AT&T releases are typically buggy. The developers here either fix those bugs, or use firmware bases from the international version that are more robust and stable. It is too early to know what bugs this UCLE5 release may contain, but the original AT&T UCKH7 firmware had lockscreen security issues, the official AT&T update UCKK6 broken bluetooth hid and serious power management issues. The AT&T ICS leaks leading up to this version, UCLD3 and UCLD4 had a very serious flaw in the kernel which caused several people with the I777 to lose their device due to eMMC chip damage. Since the kernel source code for the current official AT&T UCLE5 has not been released yet, it is not possible to confirm that the kernel supplied with the UCLE5 release is free of this serious issue. Therefore, it would be advisable to either not run this firmware, or use a modified rooted version in which the kernel is replaced with a known safe kernel.
Click to expand...
Click to collapse
Thank you for a very clear explanation.
raduque said:
Honestly, I used to hang around here for the community - but that's quickly turning me into a simple lurker.
I'm extremely interested in the developers work. However, I find that the stock factory firmwares are every bit as good or stable as anything that gets turned out in the dev areas. The stock ROMs also do everything I need and want. Plus, I don't like AOSP Android, and that seems to be what everybody is focusing on these days. Also, the 3rd party roms generally have too much changed, removed or added for my tastes.
Edit: Oh, and while I generally like the OEMs code, I have no problem using a good 3rd party kernel.
Click to expand...
Click to collapse
you definitely haven't been running an android device if you say this (marked in BOLD). Considering the fact that for our device in particular, they have released BS that is not only buggy as hell, but has bricked a ton of devices. I think you should probably do a little research before making such bold comments. :laugh:
I got board enough to try the full LE5 including kernel. So far better than D4 and previous ics. Tegrak works as it does on the 9100 base kernels so that tells me i777 is catching up or has caught up. Could be just odex, but all benchmarks higher than on any of the aokp or 9100 sammy roms I've tried.
I'd like to see someone customize this if it remains stable. I've added 15 toggle from other roms, but I jusy like having firmware meant for device.
I-777 UCLE5
Tegrak oc/uv 1.452 ghz
Stable & Fast
task650 said:
you definitely haven't been running an android device if you say this (marked in BOLD). Considering the fact that for our device in particular, they have released BS that is not only buggy as hell, but has bricked a ton of devices. I think you should probably do a little research before making such bold comments. :laugh:
Click to expand...
Click to collapse
lol
I've been running Android devices and flashing firmwares since 2009.
I also haven't seen any of the bugs or issues mentioned on this forum. Doesn't mean they don't exist. The stock 2.3 rom that came with my GS2 from AT&T was amazingly, impressively stable compared to what came with my Vibrant, or even ANY of the community roms for it.
UCLE5 bug:
unable to use wide image for wallpaper, so you can only get a fixed wallpaper, not a scrolling wallpaper. This bug was present in the leaks, and has not been fixed in the official release.
creepyncrawly said:
UCLE5 bug:
unable to use wide image for wallpaper, so you can only get a fixed wallpaper, not a scrolling wallpaper. This bug was present in the leaks, and has not been fixed in the official release.
Click to expand...
Click to collapse
IMO, non issue.
raduque said:
IMO, non issue.
Click to expand...
Click to collapse
Yes, many would not care. Many would. Ask AT&T or Samsung, and they will probably say it is a feature.