yashsingh1/xdaforums huggingface dataset:
[Android Themes] PaY87:
New Version out for you! :)

1.1
-Vibrate on Answer, Hangup, etc removed until the trackball bug gets fixed
-Added some new icons
[Android Themes] adisa:
I am unable to download the xroms's theme from rapidshare. can you please post a mirror on androidspin and i would like it if you could always leave a miror on androidspin. thanks.
[Android Themes] PaY87:
Try this:

http://www.zshare.net/download/71597327c2da0dd6/

http://depositfiles.com/de/files/876g10uc6

http://www.megaupload.com/?d=2AQ6HAVB
[Android Themes] Oneofonex1:
Boot loop after flashing theme

I installed the newest xROM 2.1 and attempted to load the theme but it boot loops afterwards.

EDIT: theme works on version 1.0 but not 1.01
[Upgrading, Modifying and Unlocking] monstrx:
my friend tried to put different rom .. but he got update failed .. and after hat he even can't turn on bootloader .. :(

is there any chance to repair that .. or its gone ?
[Nexus One Android Development] TFJ4:
Really hope this is possible...you do great work!
[Nexus One Android Development] Nativedude:
Wow that would be sweet

Don't think we'd need it soon but man, just the bragging rights :P
[Nexus One Android Development] djnutz:
Very interested in this and nice find.
[Nexus One Android Development] Epoch kW:
Almost entirely possible from a hardware standpoint.

And I bet that is exactly it, a change in manufacturing process... the end result being a lower voltage requirement and stability at higher speed (and a longer run time at lower clock speeds).

Don't know how much of a boost we would see performance wise... lower battery life of course and more heat. Not a bad thing to start looking at however as who knows, we could be crying for a bit more speed in the not too distant future.
[Nexus One Android Development] swetland:
This sort of thing (pushing the CPU beyond the rated/validated max frequency and voltage) definitely falls in the "could permanently damage the hardware" category. Pushing the voltage out of spec tends to lead to fatal L2 cache errors, etc just for starters.
[Nexus One Android Development] KiD0M4N:
Totally agree there.
[Nexus One Android Development] DocRambone:
U can brick your nexus by flashing too. But we do it anyway.

So lets start to overclock:)
[Nexus One Android Development] swetland:
The industry has a lot of fear about "open" devices being a big money sink, largely due to concerns about increased RMA costs in highly competitive consumer electronics markets. If the community starts taking actions that lead to these fears becoming reality (third party software permanently damaging devices, etc), it becomes a lot harder to convince manufacturers that "more open" is good for them.

This is the kind of thing that will make it really difficult for me to effectively argue that the current unlocked bootloader warranty policy is overly conservative and should be changed to be more flexible in the face of hardware defects discovered post-unlock, etc.
[Nexus One Android Development] DocRambone:
The small fraction that do this will never have a impact on the manufactures.
[Nexus One Android Development] SilentMobius:
I'm with swetland here. Overclocking the CPU up to its rated max (Like the G1) is great, but hacking the kernel to push the CPU past its rated limit is just asking for trouble in a device with tolerances as tight as the N1, remember that in a desktop machine if you OC past the rating of the CPU you are always told to ensure you have sufficient cooling and have MB's that can handle the Vcore increase, no such thing is possible here.

Do you really think people are going to go "oh well I knew the risks" when their N1 fails after 6/12/18 months if it's been OC'd or do you think they're going to complain bloody murder on forums, making the image of the N1 even worse?

We're already trying to defeat the bootloader relock security. The combination of these two things has great potential to ruin Google's good work with HTC.

All IMHO of course
[Nexus One Android Development] DocRambone:
I have to disagree, HTC do not care about XDA's efforts.

As long is not a market app that overclocks nexus they wont notice.
[Nexus One Android Development] packetlss:
The warranty policy position is totally understandble, especially if you consider the hoardes of people that have bricked their devices on this forum, mostly due to thier own massive ignorance and inability to read :)

Personally I don't expect any warranty whatsoever after unlock, but I'm the kind of a nerd that has tons of bricked stuff at home after playing around with it too much :)

I just hope that HTC will be willing to fix obvious manufacturing errors (like dust under the screen, broken pixels) despite phones being unlocked. Just because they have the right to not fix it, there is no need for them to be asses about it. If someone tries to RMA a device with a cooked QSD in it due to overclocking, they deserve to be turned away.

Now if we can only be allowed to flash the splash screen, w/ the padlock superimposed on top if unlocked :)
[Nexus One Android Development] j.books:
I think people who have purchased and own a device have the right to do whatever they want to that device. And if they want to share what they are doing with others, I am interested to read it. As long as the risks involved are made clear, I see no harm in sharing. The vast majority of users will not attempt this anyway unless it is shown over time to be safe.
[Nexus One Android Development] ccunningham83:
I'm with swetland...

Anybody who thinks there is a small fraction of people who are on these forums who may brick their phones is a fool. Just think about how many idiot post are posted in the wrong section & how many people can't follow simple instruction to flash their phone. I think for every idiot that post that can't follow simple instructions, there are probably at least 10 people who are lurking and not posting at all. I lurked for as long as I could and didn't sign up until I had to so I could download a file or view a screenshot. The market has made the idiots flock to XDA by posting information in the market apps themselves or the comments. Just look at the comments that say "What is root and how do I get it? Hit me up at Badb0y09@gmail.com"

The point of this is, This forum is filled with both some of the smartest people I have come across and the dumbest. Either one there are a lot of. If there is a software update that pushes the phone faster, people will flash it. Even if they have been warned it could fry their processor (Like every post about flashing your phone could brick it).

I don't mind pushing the processor to the speed it was designed to run at, but I wouldn't want to push it any faster. How many fried $500 phones do you think it would take before they start to notice. It sure didn't seem to take google too long to notice Cyanogen and he wasn't even bricking phones.
[Nexus One Android Development] swetland:
Certainly, it's your phone and nobody's stopping you from doing anything with it. I'm less concerned about what people who are fully aware that they're pushing the hardware past its design limits do than what happens when somebody releases supercool-overclocked-tasty-rom.img or whatever and a pile of early adopter types who enjoy trying the new shiny and are pretty good at ignoring any and all warnings end up doing to their hardware.

It's been a long road to get to the point where these devices are shipping with unlockable bootloaders as a feature, not an exploit. We're certainly not done yet, as can be seen based on concerns about the warranty language around unlocking, etc.

I'm simply asking that people consider that actions taken here will impact future devices and possibly show some restraint when appropriate. I'd like to enable future devices to be *more* open, and will continue to work toward that goal, but the actions of this community, and others who create modified system images and make them available to broader userbases *do* have the ability to make my work much, much harder, or much, much easier.
[Nexus One Android Development] MarcusMaximus04@gmail.com:
Very true. Unfortunately, I'm not sure if there's a whole lot that can be done about that. We can limit what happens here to be sure, but some jerk dev, somewhere, will ignore the warnings and "give the people what they want" to make a quick buck.
[Nexus One Android Development] Driskol:
Im not sure if this is really necesary...

I think with 1ghz and 512mb ram we have enough for so long...

And of course, the only thing i like from the iphone, there is no reason to "put on steroids" a pda, just clean and improve the OS and optimize the apps...
[Nexus One Android Development] lbcoder:
The simple solution is to just make your hardware safe from software damage. Shut the thing down if it goes far enough out of spec to potentially damage something... like desktop CPUs will shut down when the temperature goes too high.
[Nexus One Android Development] j.books:
granted, this is complete speculation on my part. but I just find it farfatched that HTC cares much about people who brick their devices. It doesn't effect HTC's bottom line in any way. their policy is that if you gain access to functions that have the potential to damage the device's hardware, your warranty is voided. nobody can credibly blame HTC when someone overclocks ther device and it gets fried, so they lose neither money nor PR damage.

of course, anyone who promotes a hack for a device without properly disclosing the risks is irresponsible and wrong. likewise, so is someone who mods their device without engaging in the research to properly decide if it is worth the risk to them persoanlly.

as far as persuaduing HTC to be more open with their devices, I think it might be a little idealistic to assume that any device manufacturuer will ever change warranty policy regarding modding. making it easy to unlock the bootlaoder is nice of them, but its also of no risk to them because they're not liable for what happens to it if you do that. they will never take on added risk by exapanding their warranty coverage for people like us no matter how many people brick their phones or not.
[Nexus One Android Development] timothydonohue:
i'm with swetland here. he mentions, either in this thread or another, that the reason that the bootloader is locked, and unlocking voids the warranty, is not that the manufacturers are concerned with you putting on facilitative software, but are more concerned with people frying their hardware using poorly coded software that induces hardware failure (like overclocking the cpu would do, if temps can't be regulated, or perhaps frying something else with a perpetually blinking led/trackball light, or busting a speaker by cranking up the volume beyond spec).

i hadn't thought of those particulars when i was arguing for getting into the bootloader (which i'm still hoping i can do later, without warranty invalidation), because i only install previously tested software on my unlocked phones. i can completely understand where google and htc are coming from when i read threads like this where people are potentially gonna cook their phones, and if they break them, try and get an exchange on the htc/google dime.

i think htc/google should be responsible for manufacturing defects. i do not think they should be responsible if you fry your phone yourself
[Nexus One Android Development] DocRambone:
Back to topic: any news on the overclocking progress?
[Nexus One Android Development] humancyborg:
# cat scaling_available_frequencies

245000 384000 460800 499200 576000 614400 652800 691200 768000 806400 844800 998400 1267200

EDIT: EXTREMELY unstable, crashes with great frequency, but technically works. May need more voltage or something, but I can rarely get past the lock screen. ADB shell confirms that it is running at 1267200 though.
[Nexus One Android Development] Ace42:
I dont even think OC is even needed...The thing isnt even 3 weeks old and people already want to fry the damn thing, manybe they have a faulty one thats laggy as hell but i know mines is super slick.But the prob could be people expect wayyy to much from a phone.Maybe when NExus reaches EOL then we can OC it too death but for now just have fun and try not to break your new toy.

I wonder if the Moto Shadow will be the new phone that has the scorpion, it looks ok and has a KB.
[Nexus One Android Development] coolbho3000:
I do agree with swetland: It would be difficult to tell from a phone that just won't turn on and one whose processor was fried using this method, leading to more RMA headaches for HTC. I also think, however, that using common sense and accepting unlocked phones with, say, dead pixels should be a no-brainer for HTC. For those who have overclocked desktop processors before, 25mV can make a huge difference in temperature and stability, and who knows what that could do on the Scorpion.

Sorry if I offended anyone. This post was meant to pose a potential modification (thus its title "thinking ahead") based on some findings in the kernel. It's not meant to be an overt advocacy of actually going ahead and overvolting your processor/pushing it all the way to 1.3GHz. What we now know is that this is possible (thanks to humancyborg for testing), and that's one more thing we know about our phones, and one more thing we know about the Scorpion architecture that drives it. It's up to the individual user or kernel developers now to decide whether to try or use this (if it can even be done with stability).

Getting direct access to the hardware is a huge responsibility. The bottom line is, there are lot of us who would not try to return a phone we fried due to modifications, but there are a lot more who would (look at all the posts in the Dream forums asking "how do I intentionally brick my Dream" or "will HTC take back a Haykuro SPL-bricked phone"), and these people ruin it for everyone. I personally would like to tweak my own hardware as I please, even though there is oftentimes inherent risk in doing so.
[Nexus One Android Development] baruchs:
But what about underclocking?

Is it possible to underclock the device and lower the voltage so that it will consume less battery life? How much can be gained by it?

B.
[Nexus One Android Development] liem107:
I totally agree with this last idea, I tried the Acer liquid which is lower clocked than the N1 and I must say that you can't feel the difference (although it may be android 1.6 which is lighter). What I request from my phone is battery life. I don't see the point of overclocking it for daily usage because i don't spend my days benchmarking it or playing 3d games...(I use a psp for that). If underclocking and/or undervolting the cpu can bring substantial energy savings without affecting its functionnality then it may be the silver bullet that a lot or people are waiting for.
[Nexus One Android Development] chingy1788:
you guys are lucky

Acer still hasnt released the kernel source *shakes fist*

no overclocking for us liquid users...
[Nexus One Android Development] JanetPanic:
I may be wrong in what swetland is trying to say but... The reason that the warranty policy is so draconian about unlocking is because of situations like this. If users would act within reasonable parameters with an unlocked phone then there would be little to no added cost for supporting said unlocked phone. As an example cyanogen's current ROM has a very low probability of actually causing damage that would fall under warranty. Thus flashing said ROM does not significantly increase the cost for HTC. However overclocking the phone beyond specs can clearly have unforeseen consequences and actually damage the phone. The risk is much higher and the damaged units would increase the cost to support from HTC. If the user accepted that they had made a change that violated warranty that is one thing. History has shown though that users will go to some lengths to hide the cause of the damage in order to get the phone replaced under warranty even though the damage was their own fault.

A classic example of this were the significant number of bricked G1's due to flashing SPL. If the user had stuck to flashing only ROMS that would fit on their release of the G1 the risk was minimal. Instead they performed a much riskier operation and when it failed they did what they could to get HTC to replace the unit.

Unfortunately I find myself sympathizing with HTC's policy towards unlocked firmware. While the majority can and will modify the firmware within what could be termed reasonable limits there will be exceptions. And when the overclocker, extreme tweaker, or high risk modder damages his hardware chances are he will attempt to make HTC pay for it.

By officially condoning unlocking, from a legal standpoint, they open the floodgates to interpretation on responsibility. Condoning unlocking implies trust that the individual will act responsibly. As I said above, there are too many individuals not willing to take responsibility for their actions. It would make sense to have verbiage to allow for physical defects to still be covered but this gives the irresponsible more room to wiggle in a replacement for something that is their fault.
[Nexus One Android Development] MarcusMaximus04@gmail.com:
I agree with you for the most part, but there are certainly areas that aren't in the grey with respect to whether they're caused by a manufacturing defect or 3rd party code. A good example of this would be a screen that's loose or a dead pixel/line of pixels. There's simply no way software could cause those problems(alright, dead pixels is debatable, but highly unlikely) and thus they should be covered. In fact, those are pretty much the only ones that exist(unless the research into the keyboard issue proves that's a hardware defect, in which case that should also be covered). So it's really simple, if your problems has to do with actual hardware being loose or falling off then it should be covered, under any other circumstance it shouldn't.
[Nexus One Android Development] deprecate:
Give it a whirl and report results. :D
[Nexus One Android Development] swetland:
You can adjust the max frequency the device will scale the CPU to with the cpufreq parameters available to userspace. There is some power savings to be had running slower, but there is a tradeoff where you end up having to run longer to get the same work done and the biggest power savings to be had are those when the CPU is completely halted and powered down (which the system does at every opportunity).

At 768MHz max cpu you will likely not see a perceptible performance drop off compared to 1GHz (except in applications that are far more CPU heavy than memory bandwidth heavy, which is pretty rare).

At 460.8MHz max cpu you'll probably notice the slowdown, but that's the lowest frequency at the lowest power level for the scorpion core on the dedicated PLL. You can further step down to 384MHz, but at the same voltage level the speed vs runtime tradeoff is pretty linear and it mostly works out in the wash except that when the cpu is powered down the main oscillator (TCXO) can often be powered down along with additional PLLs, providing even more power savings.

245MHz is the lowest speed that there's any value to running the CPU at -- since you can't reduce the voltage any more at that level safely and whenever the scorpion core is powered on the modem core must also be powered on and the modem core is running off the 245MHz PLL, so there's no additional power savings to be had.
[Nexus One Android Development] Driskol:
I have my n1 undercloked to 576 without slowdowns :)

By now, theres no apps thats stress the cpu to use 1ghz :)
[Nexus One Android Development] mhaedo:
http://alldroid.org/viewtopic.php?f=312&t=1637

I'm sure someone will end up pushing it to 1.3ghz. Look at what these droid guys are doing :)
[Nexus One Android Development] rvashi:
Hey guys...what is this all about??

http://alldroid.org/viewtopic.php?f=247&t=1661

The guy has his at 998MHz but hitting 17.x mflops/s!!!

As one of the comments say on that forum, that must mean its running over 2GHz....I'm not gonna' act all smart and act like I know what I am talking about but, what do you guys think?
[Nexus One Android Development] coolbho3000:
JIT is purely a software tweak and is currently not completely stable (or so I've heard).
[Nexus One Android Development] rvashi:
A software tweak that can blast the Nexus wayyyyyy past the Droid @ 1.1GHz!!

That's saying something! :) Wish we could figure out a way to overclock this thing. Just for the sake of being much faster than the Droid, now.
[Nexus One Android Development] ShotSkydiver:
So, is the link you just posted stable? Is it worth actually doing?
[Nexus One Android Development] mhaedo:
The link he posted has nothing to do with overclocking. The person over at AllDroid is simply running Cyanogen's 5.0b with JIT enabled. JIT, as coolbho3000 stated, is simply a software tweak. Well perhaps more than just a software tweak, it totally changes the way Android executes code. It stands for "just in time" compilation, and allows software to run faster by compiling bytecode into native machine code at runtime which substantially increases performance.

The Nexus one would still be running at 998mhz. Once agian, it has absolutely nothing to do with overclocking.

By the way, the Nexus One is already faster than the Droid at 1.1ghz, or 1.3ghz for that matter.

http://www.greenecomputing.com/apps/linpack/linpack-by-device/

http://androidbenchmark.com/tops.php

No, JIT is not stable. I'd say it's worth doing to play around with, but not worth running on an every day cellphone that requires stability.
[Nexus One Android Development] rvashi:
okay so I gave this a shot... I'm using CynogenMod-Beta3...

Using HighMem kernel and JIT enabled, I have over 16 mflops/s!!!

And my Pi score went from near 3000 to about 1200!!
[Nexus One Android Development] mhaedo:
What voltage did you run 1267200 at? 1.275 or 1.3?
[Nexus One Android Development] Router:
i agree with Swetland 100/100. I am referring to overclocking Pentiums in the past century. Spread in chip quality was substantial, hence results were not obvious - some machines collapsed or went unstable (just like Humancyborg describes), some survived and pleased users, subj to a new heatsink. with much less tolerance in todays production QC, results are going to be much more predictable - and the damage to the hardware imho will be repeated in 99,9.....%. HTC (and any other production co) will never allow this. I admire the work though. Oh and I do overrev my Corvette to win a race regardless of what the consequences could be:-) but i see no tangible gain it OC to 1.3GHz anyways. however, I am no Dev, i am a user...

PS and excuse me shpelling, im Russian:-)
[Nexus One Android Development] baruchs:
Thanks for all the suggestions.

My main beef is that battery life for audio playback is poor - around 15 hours at most (cell on standby, no user interaction, no phone calls, not incoming emails, screen off the entire time etc.). The iPhone, under the same condition gets 24-30 hours depending on the model. I listen to podcasts and audio books a lot. For me it is a major annoyance.

Unfortunately, no perceptible changes in battery life during audio playback.

If everything else remains constant, power is supposed to be linearly related to frequency, and quadraticaly to voltage, which should be scaled down linearly with frequency. So a 25% drop in frequency with a corresponding 25% drop in voltage should improve power consumption for unit of time by ~2, or by ~1.56 for unit of work. There should be a net gain in battery life.

My guess is that during audio playback the frequency never rises over the minimum, so no gain can be achieved.

B.