yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] Phascinate:
I upgraded my Nexus 4 from Stock Root to Android 4.2 yesterday via the OTA update. Now, whenever the device plays a sound that has a bit of a high pitch, it makes a clicking sound either at the end of playing the sound, or at the beginning.

It is very noticeable in Minecraft Pocket Edition. Whenever you walk over wood, it clicks like crazy.

So I downloaded the Minecraft Wood sound, and played it on loop in PowerAmp. Clicking like crazy, even with headphones on. Whenever I play a sound with low pitch, like the Minecraft Snow sound, it never clicks.

Why does it do this? It never does this on my brother's Nexus 7, which is also running 4.2.2. I re-flashed the 4.2.2 stock, but that didn't help at all.

Is there any way to go back to 4.2.1 again? Is this a problem other people are having too?
[Nexus 4 Q&A, Help & Troubleshooting] LavaJoe:
Yes, on my new Nexus 4 16GB (just got it today, and upgraded it to 4.2.2 soon after powering up), I sometimes hear a little click right before the normal button "click" feedback sound. It only happens on some button presses, and it seems to be more likely to happen if it is the first touch in a short while. I have never heard a click after - just before the normal sound.

I, too, am wondering if this is a software issue. Anyone else heard the same effect? Note that it is somewhat subtle.
[Nexus 4 Q&A, Help & Troubleshooting] ooohhaaahh:
I've heard it to, I guess it's the speaker being powered on. It's only every once and a while that I hear it
[HTC One X] chriscowley:
Hi, I need the RUU file which has the CID ORANG001. Does anybody know where I can download it?

Thanks guys!:good
[HTC One X] Mr Hofs:
Wich main version number ?
[HTC One X] chriscowley:
2.17.61.3

I'm pretty sure it's this one.
[HTC One X] Mr Hofs:
There is no RUU available, but you can go here

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

And download the matching nandroid backup ! Restore it including the boot.img and the stock 2.17 recovery. After that you can update ;)
[HTC One X] chriscowley:
The 2.17 appears to be a broken link, would the higher version work if i downloaded it? It's this one;

Nandroid Backup 3.16.61.6 CID ORANG001 thanks to billd2439
[HTC One X] Mr Hofs:
Depends on your hboot. Did you already updated the phone to JB ? If not then you can not use it because that's the JB version.
[HTC One X] chriscowley:
I updated my phone to a Cyanogen 10 Mod which is running Jellybean.
[HTC One X] Mr Hofs:
Well that's no guarantee because those roms also run on the lower hboots, check the top of the bootloader and read what hboot number you have
[HTC One X] chriscowley:
My HBoot is: 1.12.0000
[HTC One X] Mr Hofs:
Then you need the 2.17 nandroid backup or a lower one. I contacted the owner of the nandroid backup already so i hope to hear something soon.
[HTC One X] chriscowley:
Thanks man, that's really appreciated :)
[HTC One X] Mr Hofs:
Its your only option, a lower ruu will not work because we dont have s-off. A lower nandroid backup would work but that is also missing in the list....

I will let you know when i have news about the backup :thumbup:

---------- Post added at 04:26 PM ---------- Previous post was at 04:05 PM ----------

There is another way to get a JB hboot and flash a JB rom ! Check this thread

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

You can download the matching firmware package for your cid !
[HTC One X] chriscowley:
Thanks man, downloading the now! Will let you know how it goes
[HTC One X] chriscowley:
Will this work even if I have done most of the steps for unrooting? All i had left to do was run the ruu file as administrator (thought i had the right one earlier) and then follow the steps. I haven't tried to reboot my phone but I have relocked it.
[HTC One X] Mr Hofs:
Yeah whats on the phone is not important, the trick is to enter the bootloader and lock the bootloader (as you said you already did) then perform the commands gien in the thread and flash the firmware. It will lift your hboot to 1.36. After that you unlock th bootloader again and flash a custom recovery and perform a full wipe and then install the desired JB rom
[HTC One X] Mr Hofs:
Oke update, got rid of some issues by using teamviewer....phone is up and running on JB !

:D
[HTC One X] LiamKenny:
heya, i tried to get back to stock on a thread before and it never worked. my hboot is 1.36. and im also locked to orange. help? :)
[HTC One X] nogotaclue:
if you follow the instructions in this thread>>>>>http://xdaforums.com/showthread.php?t=1975140 you will get you back to stock, and it does work, I have gone back to stock many times with the method posted here. so if it doesnt work for you then you are doing something wrong
[HTC One X] LiamKenny:
thank you man!! cant believe it was that easy in the end
[HTC One X] sepultador:
I have cwm and twrp installed. How can i solve that problem?
[HTC One X] TToivanen:
Why new thread? :confused:
[HTC One X] sepultador:
Because i have no usefull help on the other.
[HTC One X] Mr Hofs:
I would like to point out that double posting is not allowed on xda, what is the difference with the other thread. People will read the same thing and have instantly the answer this time :cool:

Its a strange issue i definitely admit that.......
[HTC One X] sepultador:
I am sorry, but i really dont know where else i can get help.
[HTC One X] Mr Hofs:
And i feel your despare.....what if you deinstall rommanager/Rom toolbox (its a crap piece of software anyway) and only reflash a recovery with the fastboot commands, then enter it and check if it works.....

Its a strange issue and the right guy (or girl) has to scroll by and see the problem. This might take time
[HTC One X] treebill:
what do you mean two recoveries? when you boot it goes to one and when you into boot recovery the other?
[HTC One X] sepultador:
I did flash everything with fastboot comands. No rom toolbox.
[HTC One X] sepultador:
If i go to recovery it goes to twrp. But if i go to boot and then choose recovery it goes to cwm.
[HTC One X] treebill:
did you try erasing the recovery partition completely then flash CWM or twrp ?

fastboot erase recovery
[HTC One X] sepultador:
Is it safe to do that? I have two recoveries but the phone says it has no root access.
[HTC One X] Mr Hofs:
you dont need root acces to wipe the recovery .... it has nothing to do with the rom, go ahaead and delete it then flash back one of them
[HTC One X] sepultador:
If i do fastboot erase recovery will it erase both recoveries?
[HTC One X] Mr Hofs:
let's hope so
[HTC One X] sepultador:
I have two recoveries but the phone says it has no root. I manage to put the phone working again with the original software. Yesterday he asked to update from 4.0.4 to 4.1. I said Ok and when i installed the upgrade did not work. Gives error.
[HTC One X] Vcek:
reinstall your firmware.zip it will install stock recovery then you can flash the one you want
[HTC One X] Bloodbreed:
Did you try what is on this page

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

???

If you get stuck at one point of this page post i ll try to help.

Go directly to option 2
[HTC One X] sepultador:
Can you explain better?
[HTC One X] sepultador:
My is missing there.
[HTC One X] sepultador:
Missing cid
[Sprint HTC EVO 4G LTE] jbhtexas:
Hello!

After taking the OTA 3.16 upgrade (S-ON, rooted), I've now got a problem where the phone start rolling to voicemail and not ringing for incoming calls. I've been upgraded now for three days, and it's happened each day. It seems to happen after a few hours of inactivity. A reboot or turning airplane mode on/off will bring the phone back online.

Any thoughts or suggestions as to what might be going on? Any suggestions for trouble shooting tips?

Thanks!
[Sprint HTC EVO 4G LTE] jbhtexas:
Just an update...I did some testing this morning, where I was calling my phone at regular intervals. After about 3 hours, it stopped ringing and started rolling directly to voicemail.
[Sprint HTC EVO 4G LTE] zmag:
Try hitting Update profile, if it's still wonky you can always call customer service and they'll guide you through to fix it.

They prolly going to send a "reset signal" (or w/e it's called) and make you enter a few pound-pound commands :p
[Sprint HTC EVO 4G LTE] jbhtexas:
Thanks for the reply. I will probably have to call CS. I've already done update profile and PRL, did a battery pull sim, and played with a number of settings, all to no avail.

After further testing, the problem occurs in as little as one hour. Also, making an outgoing call will (in addition to restart and airplane mode on/off) solve the problem for another hour or so.
[Sprint HTC EVO 4G LTE] donc:
I have been seeing the same issue. I was at 3.15 when the issue started so I relocked and took the upgrade to 3.16. I am now rooted again with s-off, 3.16 FW, latest MeanBean with the same issue happening from time to time. Profile update as well as the latest PRL have been applied. I am wondering if it could be an issue with the area I am in. I know that sprint was doing some additional tower work for LTE here in the north Plano area where I live.
[Sprint HTC EVO 4G LTE] jbhtexas:
I'm wondering the same thing now as well. My phone was rolling over early this morning, so I reset it, was going to let it "break", and then this afternoon when I had some time, call CS with it in the rolling-over state. I took the phone with me when I went out for lunch, and then ran some errands. I've been home now for several hours, and the problem hasn't resurfaced. FYI, I'm in south Arlington.
[HTC Desire S] lukehayward86:
hi

ive been follwing instruction on androidforums.com/incredible-all-things-root/531353-how-unlock-downgrade-achieve-s-off-htcdev.htm (not enough post to set as link) and got to instruction 4 where i have been denied permission to push the flash image.

luke@luke-N61PA-M2S:~$ cd Desktop/miniadb

luke@luke-N61PA-M2S:~/Desktop/miniadb$ md5sum mtd0.img

34307be744275f1db1dd16af04c37839 mtd0.img

luke@luke-N61PA-M2S:~/Desktop/miniadb$ md5sum flash_image

0098a7dd6600b55fac34fc6645be5d7a flash_image

luke@luke-N61PA-M2S:~/Desktop/miniadb$ md5sum PB31IMG.zip

31bb1611a0fa8197d447c0438426717e PB31IMG.zip

luke@luke-N61PA-M2S:~/Desktop/miniadb$ adb push flash_image /data/local

failed to copy 'flash_image' to '/data/local/flash_image': Permission denied

Can anyone give any insight, im running ubuntu if that makes any difference
[HTC Desire S] hisname:
I don't know much about Ubuntu. could you dual boot to Windows? anyway questions go here http://xdaforums.com/showthread.php?t=2143855

Sent from my supercharged :tank:
[HTC Desire S] BillGoss:
Write the file to /data/local/tmp. Only root has write access on /data/local .

Sent from my HTC Desire S
[Galaxy S III Q&A, Help & Troubleshooting] zyclops1:
I want to install note2 live wallpaper on my s3, im not rooted on stock rom xxellc.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Try it yourself but it is a much bigger screen .

jje
[HTC Inspire 4G] Vitthal1990:
i have rooted my inspire 4g with aahk, now i m in stock at&t 2.3.3 with sensé 2.1.

i want fully working ics rom with sensé

and what kernel or radio need for me

Android version

2.3.3

Htc Sensé version

2.1

Baseband version

12.56.60.25U_26.10.04.03_M

Kernel version

2.6.35.10-gd2564fb

htc-kernel@and18-2#1

Build number

2.47.502.7 CL93396 release keys
[HTC Inspire 4G] amanvishnani:
I think Sabsa Prime is working...

Sent from my Inspire 4G
[HTC Inspire 4G] Vitthal1990:
sandals prime has very serius bugs of media and memory card format in v14
[Thunderbolt Q&A, Help & Troubleshooting] ShafferinPa:
Unrooted my phone to get new ics, had a teatering app to let me use the hotspot worked great. Now with new ics and rerooted i cant get any of them to work. Anyone figure this out yet???? (Dont really want to downgrade to get it back)
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
You need to be more descriptive. What tethering app were you using? If it is wifi tether what were your settings?
[Thunderbolt Q&A, Help & Troubleshooting] ShafferinPa:
I did have wifi tether for root users. Didnt change any thing but ssid my galaxy note 10.1 picked it right up and worked great now with this new ics it loads push the thing to start tethering and it tells me its loading with errors
[Thunderbolt Q&A, Help & Troubleshooting] ShafferinPa:
In the log of the app..

Disabling fowarding.......done

Disabling NAT rules...done

Stopping softap....failed

Stopping tether interface...failed
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
Change your device profile on the thunderbolt to the rezound profile, check routing fix
[Thunderbolt Q&A, Help & Troubleshooting] ShafferinPa:
That fixed it thank you very much is there anything else i might want to do.....?
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
If you're in public make sure to use a security method and check access control so other people can't jump on your tether. If you enable access control you have to allow the connection either by selecting it in the pull down or from the menu of the tether.
[Thunderbolt Q&A, Help & Troubleshooting] ShafferinPa:
Ok thanks again
[Verizon Samsung Galaxy Note II] JeramyEggs:
Alright, I know if I search, I can find hundreds of articles about how this happens on amoled screens. I am not trying to beat a dead horse, but this will be my first amoled screen. How bad are the black spots? At what point is it bad enough to get a replacement? Being a "power user"(5 hours screen on a day), will the screen degrade before a 2 year contract is up? I jumped on a Rezound when it first came out, and it has burned me, I just don't want to feel let down because my screen went to pot 6 months in. Thanks
[Verizon Samsung Galaxy Note II] nosympathy:
A second post? Really?

Sorry you don't like the answers but here we try again. Every single one of them will have it. Never seen an AMOLED screen that doesn't. Second you could get one worse or get one better. Pure gambling. Also, it doesn't get worse over time.

Apparently all this looking around and searching you didn't bother to read what you found.
[Verizon Samsung Galaxy Note II] ChaoticWeaponry:
I've had the phone for 3 months, at least 8 hours of screen on time per day, everything still looks like it's brand new.
[Verizon Samsung Galaxy Note II] kimdoocheol:
Get insurance and don't worry about it.

The only reason I got insurance on this phone was purely because of the screen.
[Verizon Samsung Galaxy Note II] adrynalyne:
Screen defects don't require insurance.
[Verizon Samsung Galaxy Note II] kimdoocheol:
Huh? I've called with my old DROID and got a replacement because the colors were messed up on the screen slightly.

Also I got a replacement before because the headphone jack had some static.

Never had an issue. They also cover water, physical and and if it gets stolen so yeah... Not encouraging anything but it is really easy to get a replacement.
[Verizon Samsung Galaxy Note II] kintwofan:
What he's saying is for a screen defect the warranty would cover it. So there's no need to pay for insurance.

Sent from the dark on a Note 2
[Verizon Samsung Galaxy Note II] JeramyEggs:
Thanks for the responses, except for the douche response from no sympathy. If you dont like stupid questions, dont respond with stupid answers, just skip it. Glad you were able to rage anonymously at a stranger. I asked because i have read that after 1000 hours, the screen degrades. If you do the math, that means the screen starts going out in 7 months. Since this is my first screen that is a amoled, i wanted someone with experience with them. I was asking for personal experience, and it was helpful. Thanks guys.
[Verizon Samsung Galaxy Note II] nosympathy:
You created two threads for the same purpose. Also if that is what you were worried about why didn't you say that in the first place about the 1000 hours etc.

Sorry that I tried to help you the first time only for you too make a second thread asking pretty much the same thing.

Also I can be far worse than this and have been. I am sorry I tried to help you since you don't seem to want help.
[Verizon Samsung Galaxy Note II] JeramyEggs:
First, this is my one, and only thread about this. Second, the lightning bolt post isnt mine. It is the reason I asked. Third, I did read multiple articles, and threads, and the answers were all over the place. And fourth, I really like your roms on the incredible, thanks for building them. I think you got confused on the posts, and could see how you could get annoyed at someone spamming the same question, unfortunately, you got confused. I will give you the sympathy that you refuse to give others. Kinda hard to go all hard assed when apparently, you cant read the posts correctly to begin with. Why don't yoy take your own advice, and read before making comments. Here is where you posted in the thread you thought I created

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

Screen defect

And this is the thread I created. See different people. Similar question, but not really. I knew about the defect, just wondered how wide spread, and bad it really was. Really, not trying to be a little $#! T about it, but your attitude sucks. The reason there is a Q n A is for stuff like this. Hope we end up on the same side of the next arguement.;)
[Verizon Samsung Galaxy Note II] adrynalyne:
Thank you for that explaining that :)
[Verizon Samsung Galaxy Note II] nosympathy:
That's weird. My xda app is showing the same avatar for you and the other guy but it is different on the computer. I went off of that. Sorry! Lol. Fooled by the xda app. Thought you were just posting twice because you didn't like my answer before since these threads are so close and your post in this one mimics what I told the other guy too do.

I generally do have a bad attitude on here. Mostly because when I first joined this site people actually read first and read second and read third before doing things. Now people just either post questions without reading or post issues because they didn't read first. I generally give the person crap but still answer their questions. Could be worse and I could just be a jerk.

Also I don't think I ever made ROMs for the incredible?! If I did go me for doing something I didn't know I did! Haha. I've only released two ROMs and they were for the GSIII back when it first came out and no one could figure out how to deodexe them correctly and I decided I was going to learn how to dev and do it myself. That also led me to get a shorter fuse as if I could teach myself as much as I did, then why should everyone else always get a free ride and just be handed answers.

I also am man enough to admit that I got you mixed up with someone else here. Still doesn't mean you should have resulted in calling me names as to be fair we really didn't need a second thread with this as you could have asked your question in the other thread first.
[Verizon Samsung Galaxy Note II] JeramyEggs:
Yeah, I should have posted in the first thread, my bad. I try and answer my questions in searches, and by doing so, I end up in all kinds of different forums. I took yout post the wrong way this morning, and didnt read it until later. Could have sworn I ran a no sympathy rom on either the incredible, or nook color. Anywho, was just trying to get a feel for how bad it is, and if it will bother me beyond belief. Like i said, no hard feelings, and thanks.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Just thought I'd put this out there. You WILL get AMOLED burn out just by using the phone. The second the display goes on for the first time the organic substrate is already starting to decay, it's just the way it is.

The catch is how long before you start seeing burned in app drawer rings and notification bars all over grey/white images. I'd expect if you use the phone for hours a day with the brightness up pretty high you could start seeing the burn outs in less than 6 months. They claim something like 15,000 hours of lifetime for the blue pixels, which have it the worst of the 3 colors, but people report seeing them in less than 500 hours. Brightness definitely has a huge impact as running with max brightness will result in much faster burn out.

Does it really matter though is another question. Before anyone flames my post and the information I provided as saying "well you're gonna get a new phone in less than a year anyway" just know that not everyone does that. Some people like to ride out their phones until they really feel it's time to get a new one. With this device I'd anticipate people riding it for at least 3 years and being very satisfied even at the end of the third year, with the performance. That means for those people holding onto this device they should be aware of ways to minimize burn out so they don't end up with eyesores 12 months into ownership.

As for the black spots, yep. Every single AMOLED device I've ever owned (around 4) they've all had it. Very disappointed that my Note 2 has them. Not all of them do but I wouldn't be able to tell you the odds of finding one without the splotches. Just know that I can certifiably say I know what to look for when searching for these spots and my brother's Note 2 100% does not have them. At all. Yeah, I am jelly.

So if you want to play the return/exchange game trying to get a display without the splotches good luck to you. Me personally? My display has 0 dead/stuck pixels. This to me is worth far more than a display with no spots but dead/stuck pixels. And that is my 2 pennies.
[Verizon Samsung Galaxy Note II] mrlaigle:
OFF TOPIC: Nosympathy is that a supra in your signature?
[Verizon Samsung Galaxy Note II] xdadevnube:
I have a minor black streak that is only visible when the screen is displaying a black image. Even a small amount of color on the back background makes it difficult to spot.

Overall I am very happy with the Note 2 screen.
[Verizon Samsung Galaxy Note II] vasilisaerox:
my n7100 after a year now its a horror in the dark..first was some dots and now its in all the screen
[HTC Inspire 4G] alemones:
Hi there, I update my android to 4.0 , bu the original camera don´t record anyvideo.When a press red button to record, nothing happens. How can i fixed this?

Regards

Alemones
[HTC Inspire 4G] bananagranola:
What ROM? What version? What recovery? What version?
[HTC Inspire 4G] alemones:
android version 4.0.3.0.2.0.1.0

Kernel version:

CM7

HOW CAN I discovery what rom is run?
[HTC Inspire 4G] bananagranola:
Well, what did you flash, and also, did you full wipe (system, data, cache)? Or go to Settings - About phone. If your kernel version is CM7, that is not ICS, it's Gingerbread. And make sure your recovery is up to date.
[HTC Inspire 4G] alemones:
This is the nformation that I post..Only this...
[HTC Inspire 4G] bananagranola:
...there should be a longer kernel version, a XX build date, an Android version, a build number, etc...

And again, what/when did you flash, and did you full wipe, and is your recovery up to date?
[HTC Inspire 4G] alemones:
Ireset to factory only the phone, nor the sd card..root the phone and install.

this all the information in the config

android version 4.0.3.0.2.0.1.0

Kernel version: 2.6.35.14-aospX-cheesecake

root@linux #6

Build date Fri Mar 23 16:21:12 EDT 2012

Version Number IML74K
[HTC Inspire 4G] bananagranola:
That is not the kernel you said you had earlier. Where did you get that you had CM7? You have aospX. From http://xdaforums.com/showthread.php?t=1460820. You do not have the latest version. Download the latest version from from that link. Update your recovery, whichever it is (you still haven't told me). Back up your current setup, nandroid or Titanium Backup or both. Wipe system, data, and cache. Then flash the ROM from recovery.