yashsingh1/xdaforums huggingface dataset:
[Epic 4G Q&A, Help & Troubleshooting] Led4lyf:
Ok so I reflashed my theme and still nothing. The gps button just seems like it is not connected to turn on the gps on. I don't know what to do. Anyone else.
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Reflash the ROM without the theme and try it.
[HD2 General] essexgt425:
Is it possible to install the latest version on Windows onto my hd2?
[HD2 General] AA--92:
You can take a look in the HD2 development forums

http://xdaforums.com/forumdisplay.php?f=531

Its possible to install windows mobile 6.5 and windows phone 7 on HD2
[HD2 General] orb3000:
.

Thread moved to HD2. Would advise you to read forum rules and post in correct section.

Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
[HD2 General] anseio:
I do not believe it's possible, unless WM6.5 can be run from SD card. WP7 must be run from NAND.

Curious. Why the two?
[HTC Sensation] Styron:
Guys, can someone provide the stock boot & down animation for HTC Sensation 4g (ROM Android Revolution HD 3.6.7)? Thank you.

Here's the original boot and down animation for the HTC Sensation 4G (T-mobile rom).

Bootanimation:

download

here

Downanimation:

download

here

Instructions for installing:

1. Download the file(s) to your SD Card

2. Open

Root Explorer

(or an app like it)

3. Copy the file you wish to move

3. Paste to directory /system/customize/resource

4. Set file's permissions to:

- First Column: all three checked

- Second Column: first one checked only

- Third Column: all three unchecked

5. Copy & paste the file bootanimation.zip to directory /data/local (not change permissions)

5. Reboot to test

Enjoy!
[HTC Sensation] mexxxico:
You have it in my sig.
[HTC Sensation] Styron:
Thank you for your reply. It's a bit wrong.

I need to stock animation that goes into the new phone on the official rom.
[HTC Sensation] mexxxico:
In |BOOT & DOWN Animation| HTC Black you have a four files.

Last file Original White boot&down animation.zip.

After I root my phone, I saved the animation on the HDD.
[HTC Sensation] Styron:
Thank you! I need more stock boot&down animation of the original ROM T-mobile.
[EVO 4G General] cesjr02:
Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.

Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.

Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now. :o

Am I overlooking something? Any help will be appreciated, thanks!

Edit: My current rom and kernel are in my sig.
[EVO 4G General] alaman68:
so are you monitoring this via setcpu on Decks?
[EVO 4G General] cesjr02:
Yes I am, is there a known issue?
[EVO 4G General] alaman68:
My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.

I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.
[EVO 4G General] cesjr02:
Is there a good way to monitor the CPU without setCPU? Thanks
[EVO 4G General] quocamole:
check out "system panel"

edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.
[EVO 4G General] cesjr02:
Thanks, I like that app a lot.

Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.

Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
[EVO 4G General] picklerick:
My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.
[EVO 4G General] alaman68:
so if you do this:

or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency

what is the frequency while it is sleeping?

1. you may need to overclock just a bit

2. you may want to reflash rom without wiping the data and see if that helps

3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
[EVO 4G General] cesjr02:
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.
[EVO 4G General] cesjr02:
Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.

Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.
[EVO 4G General] cesjr02:
Definitely experiencing the problem with other kernels. I'm out of ideas.
[EVO 4G General] alaman68:
Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
[EVO 4G General] alaman68:
Did you restore any apps with titanium backup by chance?
[EVO 4G General] cesjr02:
By the way, I appreciate all your help alaman68.

Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.
[EVO 4G General] alaman68:
Trying, you could try a sense rom for a day and check the scaling for a benchmark.

Is there anything else you are running? Undervolting, v6... Anything else?
[EVO 4G General] cesjr02:
Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?
[EVO 4G General] alaman68:
if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?
[EVO 4G General] cesjr02:
I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.

I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)

I'll report back
[EVO 4G General] cesjr02:
Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.
[Galaxy 3 Themes and Apps] Shankermk:
Is there any 2G 3G switcher app for g3 .... Most of the apps in maket just take you to the setting menu where non Samsung / galaxy phones can choose between 2g and 3g.. but since we dont have that option is there a work arnd, ??? i baiscally want to be in 2g mode till i unlock the phone.... no point paying for data and losing battery at the same time....
[Galaxy 3 Themes and Apps] FadeFx:
You could use tasker to automate this. It is not free, but worth every cent. I for example use tasker to switch to 2g when screen is off and to 3g when its on. Due to some problems with cm7 on sgs it takes some seconds, but i am pretty sure it works well on g3

----------------------------------------

tapatalked
[Galaxy 3 Themes and Apps] Shankermk:
thank you sounds exactly like wat i need will check it out...
[Galaxy 3 Themes and Apps] thomaske 11:
You can also install extended controls from the market. It's an app to make a widget with much toggles. Wifi on/off, 3g/2g switcher, gps,...
[Galaxy 3 Themes and Apps] Shankermk:
thanks will chk that too

Got Tasker still figuring it out its not the simplest app out there
[Samsung Galaxy Nexus] w1nter456:
Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.

www.youtube.com/watch?v=BIFRYY25fDo

Thanks dnlsmy.

www.youtube.com/watch?v=y_mO_K7OYR0

Update 1

Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk

Update 2: Lee Johnston explain of "volumegate" issue

Let's talk about the Google Nexus "volumegate" issue.

Today Google said that they have fixed the problem in software, and that a fix is coming.

I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.

I'm a Systems Engineer and also a Developer. I deal with things like this every day.

What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.

However things like this can be fix fairly easily in software. It's called debounce.

When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.

Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.

This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.

And people will be saying "wow, I was wrong, Google rocks

Cheers,

Lee

Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
[Samsung Galaxy Nexus] dnlsmy:
Yeah, and for further proof, he does it in the bootloader screen of the GNex

http://www.youtube.com/watch?v=y_mO_K7OYR0

This seems like it's a hardware fault entirely.
[Samsung Galaxy Nexus] TiltedAz:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
[Samsung Galaxy Nexus] martonikaj:
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.

This would fit with people saying its happening when the phone is in 2G networks.
[Samsung Galaxy Nexus] oscillik:
well you're mistaken then. the test is not inconclusive at all.
[Samsung Galaxy Nexus] TiltedAz:
Ok, gotcha.

Still could be software and even if it were hardware a little software patch could resolve it.
[Samsung Galaxy Nexus] oscillik:
no software patch can fix this. the phone has inadequate RF shielding.
[Samsung Galaxy Nexus] smalltownbird:
My bionic which I know is a different device does something similar. When I put it next to my corded work phone and the bionic switches to 4g it causes the speaker on my work phone to male a distortion noise even when it is hung up. So I can see where the radios cause some sort of interference on these 4g phones
[Samsung Galaxy Nexus] vash1053:
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.

Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
[Samsung Galaxy Nexus] DammitCubs:
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
[Samsung Galaxy Nexus] dadsterflip:
Would that have anything to do with the nfc chip?
[Samsung Galaxy Nexus] oscillik:
please read this post

---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------

it has nothing to do with the NFC chip or aerial
[Samsung Galaxy Nexus] chandlerweb:
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
[Samsung Galaxy Nexus] oscillik:
yes, exactly - the internal radio on the Galaxy Nexus is causing the problem. that is why those of us who have been affected by this hardware defect have been so vocal about it.
[Samsung Galaxy Nexus] Danrarbc:
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).

Either way, the phone needs a hardware rev to improve shielding.
[Samsung Galaxy Nexus] marcogiudice:
This is why I effing hate Samsung they always screw something up... Looks like the g-nex us going to be a big failure.. Hint hint goggle you should of stick with HTC to make your nexus line phones
[Samsung Galaxy Nexus] oscillik:
the bootloader is akin to a BIOS on a computer. it is very low level.

it needs a hardware fix.
[Samsung Galaxy Nexus] Danrarbc:
Yeah, figured it was. And trying to work around it by analyzing radio signals to detect if it is a real button press or interference would be very hard too, they're going to have to do something about the phones already sold - this is a huge issue.
[Samsung Galaxy Nexus] qnet:
This is indeed bad. I guess this makes my decision easier about getting one from Hantec. Hopefully the Verizon version doen't have this issue since it uses different frequencies however, this may be the reason they haven't released it yet.
[Samsung Galaxy Nexus] GN_ICS:
Nexus exchange?

The fact that Samsung have begun replying to peoples comments on their UK Facebook page asking for an email to be sent to technical support including their home address suggest they intend to replace the phone. It`s a great phone and it should never have happened but it`s how Samsung/Google deal with it.

For those who haven’t read the Facebook comment from Samsung :

Samsung UK Hi *, to ensure we investigate thoroughly could you please send the following details to uk.technical@samsung.com: Serial Number, IMEI number, date of purchase, place of purchase, details of issue

your name, address and phone number. We will get in touch as soon as we have more information.
[Samsung Galaxy Nexus] Baguett:
if this is a hw-failure, then what will Google/Samsung do about it?

im sure they know, or will know about it soon, and i dont expect them to just dont care about it :d
[Samsung Galaxy Nexus] Danrarbc:
And even if it isn't having them, seeing it in the GSM version may mean they want to be extra-thorough in testing to make sure it or another issue doesn't make it into customers hands.
[Samsung Galaxy Nexus] C64c:
Seriously disturbing.
[Samsung Galaxy Nexus] qnet:
Agreed and, I have no issue with them doing that.
[Samsung Galaxy Nexus] mcgon1979:
Unreal. 1000s of units due to ship first thing tomrrow morning from Handtec and Clove in the UK (including my own). This is going to be a nightmare for sure....

:confused::confused::confused:
[Samsung Galaxy Nexus] randypurcz:
They will probably do something similiar to what Apple did to fix the antennagate issue (if the problem is widespread).

Supply an RF shielded encasement for the phone, a sleeve for the battery, or battery cavity. I guess this based on some of the supplied videos showing how the defect is triggered.
[Samsung Galaxy Nexus] Egan:
It has nothing to do with the radio, since its not used in bootloader. It is however a hw issue.
[Samsung Galaxy Nexus] mcgon1979:
This issue may be limited to the initial batch of phones that was released.

Clove and Handtec are due to post out 1000s tomorrow. They are aware of this issue and do not want 1000s units being sent back to them over the next weeks.

This is what Clove had to say on their blog. I think it is promising.

We now have the Samsung Galaxy Nexus in stock at Clove Technology and will begin shipping orders tomorrow. We are aware that some users that purchased handsets from other outlets last week have reported problems with the volume changing erratically. We have been in touch with Samsung regarding this and have been told that our stock has since been through an additional quality control check and should not have the problem. Nonetheless, we will also be testing several handsets ourselves to check for the problem this evening.

http://blog.clove.co.uk/
[Samsung Galaxy Nexus] oscillik:
incorrect. it does have something to do with the radio.

the internal radio is emitting RF interference that is causing electromagnetic interference with the volume rocker.

the phones need a recall, and a new hardware revision needs to be manufactured.
[Samsung Galaxy Nexus] cellzealot:
Just an FYI. This issue does not appear to be present on the CDMA/LTE variant and someone I spoke to who would absolutely know about it if it existed on those devices was completely unaware of the problem. I have not seen it on my LTE engineering device. It is a Toro rev 8 hardware 32GB model.
[Samsung Galaxy Nexus] BrandoHD:
If it's a hardware issue, why is it not affecting all the devices???

I think that there is a variable that has not been discovered as yet.....
[Samsung Galaxy Nexus] oscillik:
you likely do not live in a country where 900MHz networks exist, so you wouldn't be able to test this out unless you have an RF generator that can generate the frequency.
[Samsung Galaxy Nexus] Egan:
Its actually a volume rocker issue. But can be replicated by the interference caused by certain radio frequencies. Its important to know its not the radio itself :).
[Samsung Galaxy Nexus] NexusoftheUniverse:
Quick heads up. Some online retailers (see Clove) are saying that Samsung is aware of the problem and that new shipments of the phone have been through additional quality control. That havign been said I don't know what this means for people who already have the phone and have this problem...
[Samsung Galaxy Nexus] oscillik:
it likely does affect all devices, but there are certain conditions that must be met to trigger the fault.

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

you said it "had nothing to do with the radio" which is false.

I highly doubt that Samsung knew about this, considering that the first reports weren't coming in until Friday night, after hours. This stinks of bs
[Samsung Galaxy Nexus] Egan:
It still has nothing to do with the radio. You can replicate it with any RF generator. It has everything to do with RF, but not this radio component itself.

I rest my case ;).
[Samsung Galaxy Nexus] oscillik:
wrong, it still has something to do with the internal radio.

if the internal radio wasn't there, there wouldn't be an issue with the volume rocker receiving EMI from the RF interference being spewed out by the cellular radio.

ergo, it still has something to do with the internal radio because it is a causality.
[Samsung Galaxy Nexus] atomic_dude:
We'll find out soon if samsung fixed the latest batch. The first sim free phones should get delivered within 24h, isn't it?
[Samsung Galaxy Nexus] sblantipodi:
in italy two nexus has no problem.
[Samsung Galaxy Nexus] oscillik:
have you tried performing the test by using a separate 2G handset near to the volume rocker while making a call on the separate 2G handset?
[Samsung Galaxy Nexus] nospamjl:
i don't quite understand the last few pages.

As the problem is happening in boot mode before the sim has kicked in why would only 900mhz only users be affected?

Surely it could happen to all users.
[Samsung Galaxy Nexus] qnet:
Yeah, I'm not totally sure but, I believe your correct. I think T-mobile uses the 1700Mhz and 2100Mhz GSM networks in the U.S. Verizon is totally different.
[Samsung Galaxy Nexus] oscillik:
exactly. it can happen to all users, if they happen to be in close proximity to another phone that happens to run on 900MHz

it is definitely only the 900MHz frequency band that is causing the RF interference on the volume rocker.

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

as far as I'm aware, the US doesn't use 900MHz for any of it's GSM networks. I have no clue about CDMA based ones though, because that system is completely silly :p
[Samsung Galaxy Nexus] mhunt407:
Put an email template up here http://www.tekcore.co.uk/2011/11/samsung-galaxy-nexus-2g-erratic-volume.html for anyone wanting to email samsung about this issue.

Its not just a minority that it is happening to. Its rather frustrating!

But Samsung on their Facebook are recommending emailing their technical team so the issue can be "investigated". Email away!
[Samsung Galaxy Nexus] nospamjl:
so the question of which sim or frequency u r on is irrelevant?

It depends on OTHER 900mhz devices being close to your own phone?

Is that contrary to the reports that show only 2g users affected?
[Samsung Galaxy Nexus] oscillik:
no it isn't irrelevant. If you are on a network that uses 900MHz you will undoubtedly encounter this issue.

If you are not on a network that uses 900MHz you may encounter the issue by proxy of being close to another phone that does operate on a network that uses 900MHz.
[Samsung Galaxy Nexus] dawgpound6985:
http://www.tweetdeck.com/twitter/P3Droid/~c0x5g

Maybe Google/Samsung will have something more official soon?
[Samsung Galaxy Nexus] oscillik:
whoever posted that has a few more chromosomes than the rest of us.

Many people in the UK live in areas, or have to travel through areas, where there is patchy 3G reception and thus their phone drops to a 2G signal coverage.

not to mention that there

is no fix for this issue

.
[Samsung Galaxy Nexus] dawgpound6985:
Yeah I'm doubting its a software fix as well but P3Droid is legit. He's very well known with the Droid side of things so I can't really rule him out if he says its fixed. I guess we'll find out soon enough.
[Samsung Galaxy Nexus] oscillik:
I don't care if he is well known with the droid side of things, he is wrong. there is no fix for this other than getting a new handset that is from a batch of hardware that has been revised.
[Samsung Galaxy Nexus] Danrarbc:
The buttons are probably polled at a specific rate that 900mhz in particular matches up to (although wouldn't 2g on 1800 also do it too?), a multiple or something? We already know GSM interferes with circuits due to the time division (the TD in TDMA), I believe WCDMA can also be on the 900 band I bet it doesn't interfere this way.

If it is a polling interference issue they may be able to tweak that poll rate.

If they can adjust the polling with a firmware update no new hardware needed.
[Samsung Galaxy Nexus] dawgpound6985:
Sounds very plausible. I'm sure Samsung knows how to fix it without having to do a massive recall.
[Samsung Galaxy Nexus] oscillik:
how can you adjust the poll rate for something that cannot be changed? the problem happens in the bootloader screen.
[Samsung Galaxy Nexus] Chrono_Tata:
Remember that a band is a range of frequencies. It could be anything from around 850 to 950 MHz that is causing the interference. Let's say if it's 950 MHz signal causing the problem, then double of that is 1900 MHz which is outside the range of the 1800 frequency band.