yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] persiansown:
Google wanted the phone unlocked yes, but why do you think the regulator was put into place?

If google didn't care about people messing with voltages, they would have never implemented the regulator. Transistors and resistors DIE with extra voltage. Once they are gone, there's no bringing them back. I'm all for the advancement of the platform, but how exactly does this do that?
[Nexus One Android Development] maverick262:
I understand why everyone is up in arms about this but this wont stop future phones from having an unlocked bootloader. That's why there's a big ass warning stating that your warranty is invalid should you unlock it. Anyone who compiles this kernel and flashes it knows they are taking a huge chance of frying their phones so in my opinion, that's on them. Personally I didn't spend close to 600 bucks just to turn my n1 into a pretty paperweight, but should someone not heed people who know what they are talking abouts advice, its on them.
[Nexus One Android Development] bbuchacher:
All this will do is let the people who have no idea what they are doing, mess with something that we shouldn't mess with, or if we must mess with it, it should be a couple of people so that the masses don't get ahold of this and fry all their phones. 90 percent of ROMS here have the same warning label and I can guarantee that people probably don't even read them they just skip down to the instructions or to the download link. This is worse because it will actually fry their phones. If you are reading this do NOT attempt to do this. It will **** UP your phone.
[Nexus One Android Development] Gr8gorilla:
To install this, your phone must be unlocked. Thus it is not covered by warranty.

Now, HTC is charging a fee for repairs with an unlocked bootloader, unless it is dust under your screen or a dead pixel.

So every one who fries his processor and pays HTC for repairs, is going to make HTC money. Now you mean to tell me that HTC is going to be so upset that they made some extra cash that they are going to refuse to produce phones with unlocked bootloaders?

That makes perfect business sense, really. Let's cut off a source of potential revenue, because we don't like why we are making money?

Ok sure, that is a wonderful argument.
[Nexus One Android Development] Gr8gorilla:
oops double post.
[Nexus One Android Development] persiansown:
Actually they are covering hardware malfunctions. A CPU dying is a hardware malfunction (if they are running the device within specification). Now HTC has no way of knowing if a device simply died of its own accord, or if it was assisted with something like this.

Google had to fight with HTC to even get them to offer the unlocked bootloader option. Look at the Desire which is the same hardware, but has the system partition write protected with the SPL.

A point I can feel that can be argued is that Google wanted it to be bootloader unlocked so people could tinker with the system partition that can't damage the hardware. 99% of kernel tweaks can't damage the hardware, but this one DEFINITELY can.
[Nexus One Android Development] liam.lah:
Frying your processor is non of HTC's concern.
[Nexus One Android Development] Gr8gorilla:
As a side note, they unlocked the phone and made the source available.....the file is there when you download source......yes they set the voltage as safe.....yes this voltage could be damaging.......people have been overclocking processors for years, this is a natural extension of that, overclocking your smart phone which is really just a pc in your pocket.

Anyway, its here. If you want it, build it.

If it breaks your phone, buy a new one, or pay HTC to fix it.

I figure most people are to lazy to bother waiting a couple of hours to compile it, but for those who want the freq. table and other files may be of some use.
[Nexus One Android Development] coolbho3000:
I think the regulator was the only "secret" released here, and even then, people could have easily figured the regulator bit out using the kernel source files of the kernels that UV below 1000mV (whose binaries are released). This zip gets rid of the barrier between "noob devs" who can only compile and "slightly more experienced devs" who can run a diff, allowing "noob devs" to compile overvolved kernels. :p

I don't think this is "Google won't release unlocked phones again ever" big deal, it's just "Google/whatever company they work with to create the Nexus series of phones would be much less likely to honor warranty returns of bootloader unlocked phones in the future" big deal. Which is still a big deal, but we broke that by overclocking to 1.113 anyway, even undervolting is running the hardware out of spec.

Once your processor is fried, though, it is fried, and it could become hard to tell whether you unlocked your bootloader in the first place. This was the basis for many bricked G1 repairs. You could not tell that the phone was rooted because you flashed a bricked SPL. In this case, the splash screen would not show, and you would not be able to get into the bootloader. You'd have to physically read the NAND chip to check for the unlock flag, which would be more trouble than it's worth.

That said, those of you who compile this, please don't release binaries. :) The speed increase is negligible, even between the relatively safe 1.113 and the potential 1.267 "jesus" class phones can reach. It would still be bad if there were long term consequences to overvolting, and there very well could be - we obviously can't tell yet.
[Nexus One Android Development] Gr8gorilla:
I actually agree with you 100%. This can harm your phone. In my opinion the risk is not at all worth the gain. NOT AT ALL. I have this on my phone and almost never run the freq over 998 anyway.

I also don't think I should decide for people what knowledge, in an open source OS, that they should be privy to.

If I had posted a zImage or an update.zip I could understand the outrage, but for god's sake this is a how to and some source code.
[Nexus One Android Development] Eclair~:
I don't see why people care so much about other people on these forums, if someone wants to compile this kernel while knowing the risk then so be it. Is it because he is making the resources to do this available that this becomes a problem? Let people fry their phones and you go on with YOUR lives. If someone is idiotic enough not to heed the warnings that have been set in place, as said before, then there are greater problems here that are not relevant to this discussion.

These arguments are entirely not needed.
[Nexus One Android Development] Gr8gorilla:
Did you read the my opening post? Or just skim it? I explained how much extra heat is likely to be generated by the extra voltage. The calculations were actually done by an EE I work with, for 1.35v. The estimated heat increase at 1.35v is roughly 8% it will be lower at 1.325v. I am fully aware of the increased heat, and I also posted what it is likely to be so that anyone who COMPILES this has the knowledge as well.
[Nexus One Android Development] rheza02:
Thanks Gr8gorilla
[Nexus One Android Development] persiansown:
Yes but that only takes into account the voltages going into the processor. What about the addition of the second heat source, the battery? That throws off your numbers, as does the screen etc. The math won't hold up to real life usage.

Whatever, I'm done arguing over this. If HTC stops repairing hardware defects or if Google doesn't offer the next phone has hardware unlocked, just remember the points I made in this thread.
[Nexus One Android Development] Gr8gorilla:
Your welcome.
[Nexus One Android Development] wootroot:
oh look, a screen shot of someone voiding a software warranty

*looks down at my replacement n1 for a defective SD card slot, that was replaced after seeing the same screen, and voiding the same warranty*

hey kmobs, didnt you get a replacement n1 after unlocking yours? faulty sim slot right?

point is, when you clicked void on that screen, you voided a software warranty. The only way to void your hardware warranty, which covers general hardware defects, is to remove that "void" sticker from the phone.

If I fried my phone with this, and called HTC like 99.999% of the people who fried there phone the same way, HTC would replace my handset, at no additional charge to me.

EVEN if they knew about this thread, it would cost more money for HTC to take apart the phone and pinpoint the exact cause of the failure. It would cost less to simply replace the phone. After enough of this, HTC would learn its lesson about being so open and in the future, lock things down harder.

We dont want HTC getting all Motorola with there devices do we?

I promise you, every last noob that has read this thread would call HTC and get a warranty replacement after ****ing it up, no matter how unethical it is.

Please stop thinking that just because everyone who can and will do this, will not be harming the community when they get a replacement phone, especially the tards that do it a second time.

HTC is not the only one who would be affected by these kinds of actions, future manufacturers would also reflect upon this when deciding to offer devices similar to the Nexus One.

You mentioned earlier if we didnt like this, to goto an Apple device. It is actions like this that will push handset manufacturers to be more "Apple" minded in the future. Android is free and open source, but its merely code without a machine to run on. The handset manufacturers can and will lock down there devices harder and harder, slowing development on future devices to a crawl.

Have fun ****ing it up for the rest of us down the line by being naive now.
[Nexus One Android Development] Gr8gorilla:
Yes and I am sure it would be because I posted on how to compile a kernel with a few source files......wow, I will have singlehandedly won great victory for Apple, maybe I should call Steve and ask for a job?
[Nexus One Android Development] Stericson:
Well, I thought I would chime in here....

I completely see the danger in this, and understanding that if ANYONE actually does this to their device then they are foolish for doing it.

Let me Repeat...

THIS IS AN INCREDIBLY DANGEROUS MOD AND IF YOU BUILD THIS AND APPLY IT....KISS YOUR DEVICE GOODBYE.

BUT, this thread, wont be closed. locked or removed. The OP clearly stated the dangers of what he was proposing, he did not provide the compiled product, simply the means to accomplish the proposed.

This is a developers forum and this is development, while dangerous still development and as such, this is the correct place for this information.

We can discuss the dangers of this mod, but please stop flaming the dev for posting this information, any continuation of such an act will result in a ban.

Best Regards,

Stephen
[Nexus One Android Development] jlevy73:
Thanks again man. Ok, so I compiled everything according to the instruction in the OP including the audio hack. Took a while but kernel has been installed onto my phone. Booted fine and so far have only noticed a 5% increase in heat . However, to be honest whatever increase in clocking there is, I can't notice it at all (verified running at 1.17). Linpack score is 9.5 MFLOPS. I am going to run it a bit longer and then switch back to good ole pershoot's kernel.
[Nexus One Android Development] Six6Sicks:
C'mon Stericson, sometimes you gotta delete the thread with the future of development in mind. If HTC did decide to lock things down that would suck for ALL of us.

+1 for removal of this thread.........

If my vote even matters.
[Nexus One Android Development] Stericson:
If this was up for a vote, then your vote would matter, but since this IS NOT up for a vote, your vote doesnt matter.

This is a development community guys. This is Development. We have a brave soul trying it right now and who knows, maybe he will report back that this runs very well and maybe in the future we will all be doing it.

The point is this: This is development related material in a developmental forum. The dangers have been clearly marked and the lines drawn. If you choose to build this and apply it then that is your own doing with your product and what you do with that product of your own accord is no concern of XDA(though we do always love hearing the cool things you've done), mine, or anyone elses. If this had been posted as a rom/kernel with great stability and no warnings mentioned and people started having severe problems and it came to light that the OP had done some devious act to destroy peoples phones then we would act on the matter in the swiftest and harshest manner possible, but this isnt the case.

So for the last time, lets keep the conversation to a developmental discussion.

Any other material off topic will be deleted and may result in a temporary ban if needed to get the point across.

Best Regards,

Stephen
[Nexus One Android Development] liam.lah:
I promise you that no n00b knows enough about this to compile it themselves. Those warnings in large friendly letters in the opening post are enough to scare most people away, anyone smart enough to compile this kernel is smart enough to understand what it will do to their phone.
[Nexus One Android Development] jlevy73:
After about 2 hours of running the OC/OV kernel all is still good. Temperature has not ever gone above 38C and that's after a good 25 minutes playing Asphalt 5. I actually noticed a speed increase there. Normally I get a bit of lag, no lag whatsoever. I will continue to play around with it to see how it responds. But so far everything is stable (no reboots, FC's, graphics issues, etc). Even ran a stress test in SetCPU and received no errors.
[Nexus One Android Development] miphonematt:
Thank you jlevy73 for being brave enough to test this out for the rest of us (aside from the OP who is clearly also testing). I'm going to keep an eye on this.

Thank you Gr8gorilla for posting this. I'd already setup my build env thanks to Cyan's Wiki and some build env recommendations from pershoot, but didn't really have anything interesting/different to build with it yet. So I went ahead and compiled my kernel with the info, but don't intend to flash quite yet. Key word being yet.

I'm also pleased to see the thread back on topic. Thanks again Gr8gorilla, very cool stuff.
[Nexus One Android Development] wootroot:
i personally watched in irc as a noob compiled this, i think you are giving noobs a too little credit these days, if anything the letters in red will do two things

inspire some people to want to do it more, and inspire others to demand an update.zip from those who do compile it, eventually leading to the update zip in the wild, being passed around with little to no warning, and possibly even into roms by copy/paste winzip devs

with these files and the information that is available on this forum, it is increasingly easy to figure out how to compile this

and judging by the demand for the "Jesus Kernel" as it has been dubbed that kmobs created, i can imagine the amount of people who would want to compile this and release it as "the jesus kernel kmobs wouldnt give you"
[Nexus One Android Development] dagobert_29:
I don't need your protection thank you very much

I’ve read this entire thread and I can only say I’m disappointed by the narrow-mindedness of many posters. This is the quintessential arrogant developer who feels he/she needs to protect the masses from themselves. Thanks but no thanks. If I want to fry my phone, so be it. I paid for it, leave me alone.

The problem with many here is that they have a distorted view of reality. What’s discussed on these boards represents an insignificant percentage of Nexus users. An incredible majority of owners will keep this phone as is and buy/download apps off the market and be content. The actual number of people who will compile and install this onto their phones is even less significant, and those who will fry their phone and try to get HTC to replace it even less.

The point is that HTC does not give a **** what happens here because in the grand scheme of things, it has NO financial impact on the company. Someone said earlier that HTC won’t go through the hassle of tearing down the phone to determine the cause of the problem and this could not be more right. Paying a technician to assess this would far outweigh the actual cost of the device which is probable in the range of $300-$400.

If it were to become more widespread, trust me they will just invoke the warranty clause when you root the phone and be done with it. The disclaimer makes no mention of software only warranty. It says ANY warranty. If anyone wants to sue, then have at it.

Finally, with the dismal sales of the N1 in comparison with all their other HTC offerings, HTC is in no danger of suffering financially if a few people try and cheat the system.
[Nexus One Android Development] Eclair~:
Love how this guy thinks, that first paragraph were my thoughts exactly.. well stated more intelligently.
[Nexus One Android Development] Wysie:
Just my 2 cents, if anyone tries and fries his device, that sucks for him. But for all other intents and purposes, lets respect one another as part of this community :). I think its good information. True, someone will probably release a binary or an update.zip and so on, and someone else will flash it and may end up with a brick, but that's his responsibility. Not any of ours.
[Nexus One Android Development] dagobert_29:
I stand corrected

The two previous posts are starting to restore my faith that this board is frequented largely by rational people and not zealots.

The zealots just have more time to post. :-)
[Nexus One Android Development] Gr8gorilla:
I am taking my phone off the charger, setting it to max speed 1.17ghz with sleep standby at 275 and a temp override, and I am also setting it to clock down to 998 after drops below 50%.

This is to check stability and battery life.
[Nexus One Android Development] jazzor:
Hey thanks for posting this. We need more people who are daring enough to do things beyond what normal people can achieve.

I would have liked it more if people who develop with these kernels be a little more open and provide the necessary patches or sources which allow for inspection and verification that nothing wrong is happening (like you have done).

I'm specifically talking about pershoot and others who seem to like hiding the sources and just providing binaries. It amazes me the amount of noobs who will install a kernel binary from an unknown individual with no regard or understanding of how powerful the kernel can be if abused intentionally or unintentionally.
[Nexus One Android Development] cyanogen:
My 0.3333 cents on this whole overclocking debacle..

Do I think overclocking a mobile device that has little in the way of hardware safeguards is a dumb idea? Yes.

Do I think the OP is kind of an irresponsible douche for posting obviously dangerous stuff? Yes.

Will this be picked up by every Winzip filepusher ROM out there? Absolutely, look at the Droid community. Most of those guys care more about overclocking than they do about actually improving the software.

Should this post be deleted? Not in a million years. We all know where the path of suppressing information leads, it's not a good place.

The first part is key. Your average desktop CPU is a tank compared to these system-on-a-chip devices. As soon as someone fries their phone and then is absolutely crapping their pants because OMG NO PHONE, they will likely attack the OP as their first reaction, then call HTC to claim hardware defect, and we will all say "told you so".
[Nexus One Android Development] Gr8gorilla:
Can't say anything bad about pershoot. He has linked to his Github where I pulled all of these files from. I only edited the acpu-clock and boardmahimahi.c. All of Pershoots code is available. Just go to Github you can get all kinds of source files there, and with a little research you can learn to do neat things with them.
[Nexus One Android Development] Gr8gorilla:
Only one thing to say about that last bit....DANGER SPL, BRICKED G1, CALLED TO CLAIM DOA............quoted from the an interview with the master himself......

But on another note, I love your work, I donate and certainly will again! Even though you called me Douche........I still think your the ****!
[Nexus One Android Development] spyz88:
Thanks Gr8gorilla for releasing this and keep knowledge OPEN.
[Nexus One Android Development] jazzor:
I'm not saying pershoot is bad. In fact pershoot's undervolted kernel was what inspired me to tweak the android kernel in the first place. But as a person who had to start from scratch, I can't say that finding individual patches for the 'tweaks' people put in their kernels was an easy thing to do. It should not have to be so hard to know what modifications were actually done. That is all I am saying.
[Nexus One Android Development] pershoot:
All my source(s) are readily available (its linked in all my posts) and I try to make my changelogs as detailed as possible. This is so u can see what you are getting/flashing as well as be able to build freely on your own.

I freely share all knowledge that I have as well (you just have to ask).
[Nexus One Android Development] cyanogen:
I know, that's why I'm calling people out on saying that they don't care if they mess up their ****. I'm just as guilty.

And I meant douche in the nicest possible way :)
[Nexus One Android Development] persiansown:
I shared my UV kernel's table with all that asked. Ask intersectRaven ;)

Do I feel like knowledge should be hidden? Of course not. Do I think it should be in one easy zip for everyone to use? Absolutely not.
[Nexus One Android Development] Gr8gorilla:
THANKS!

I did say that I agree. The gains are completely not worth the risks at all. I will never recommend that someone do this. However the Knowledge should be available. Understanding how this works can help in understanding a lot about the cpu speed and what governs it. The knowledge is valuable, the implementation.......not so much.

I as the OP will recommend this to those who compile this: Run some bench marks, maybe put the Jitt add-on your phone too. Post some high pi or Linpack scores.

Then: Either set your cpu clock down to 1113 or flash a new kernel. One that doesn't increase voltage, and be happy with the knowledge that you gained from this.
[Nexus One Android Development] Gr8gorilla:
anyone who decides to go against all sane advice and compile this, please post your linpack and or pi scores. I have heard of some people getting 9.5 on linpack with a 1.26ghz kernel (persiansown) and someone here posted they got 9.5 with 1.17, it would be interesting to see what kind of scores people get.
[Nexus One Android Development] spyz88:
I wonder what the scores with this kernel + JIT would be :)
[Nexus One Android Development] jlevy73:
I've been running this kernel since this post began (last night). Zero instability, no heat problem, etc, etc. LInpack scores range from 9.3 on the low side to 9.5, running CM 5.0.6 test2. When I have a moment today I will run some benchmarks and report back my findings. I will also install JIT and see what kind of turbo boosting I get with that.

The bottom line is that this has been as stable as any other kernel I have used. I will continue to monitor as I put it through a full work day.
[Nexus One Android Development] Gr8gorilla:
That is pretty amazing as I can't get over 8.5 on linpack with this running.

NOTE: although it may be stable the extra voltage will most likely shorten the processor's life, even if it doesn't outright fry the device.
[Nexus One Android Development] cacheinjection:
after reading this thread i have decided that where the battery goes on my g1 im gonna link up to the mains and put 240 volts into my g1 that oughta speed it up a bit
[Nexus One Android Development] Daneshm90:
Can u post instructions ? thnx :D
[Nexus One Android Development] cacheinjection:
ahhh it wont work for you, your voltage isn't enough, in the UK we have alllllll the volts, but in Canada you cant handle the volts!
[Nexus One Android Development] Daneshm90:
Ah man, just for that imma move to the UK. Can't wait to try out your method.