yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
thanks rdaprix for your reply...

I don't intend to use it with goodlink..although it sounds tempting......I just have this one GPRS "Cannot connect due to an unkown reason" crop up on me once in a while.....it will be working fine and then it will stop working....I spent an hour with a TMobile data specialist over the phone the other day and he said to try a hard reset and if that didnt work to have the SIM checked out....needless to say, the HR did the tricl and got me back to normal. But I am getting tired of putting my stuff back in one by one....now I have just left everything out and its back to bare bones...

anyways...Im only looking to do the Caller ID downgrade IF it helps solve the GPRS issue ......if it doesnt, then I can just keep doing this....and save up for a real converged device that actually works.....

but please....do tell me what version and build the CallerID which is on the FTP build is?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
Re: Damn, Not so fast...

Just tried following the steps detailed before on page 2 and got this exact same error......can someone please tell us how to do this the right way???

I would like to downgrade my caller ID, if someone's wondering....

any help would be highly appreciated!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] efjay:
Here is the link ftp://xda:xda@ftp.xda-developers.com/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB To rename the files in use download a file explorer like total commander or gsfinder from www.pocketpcfreewares.com or freewareppc.com and rename each file to .old as it brings up the error on each file. Then you should be able to install the cab ok.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
thanks efjay.....I tried using total commander the first time and cut and pasted the files into a temp folder on my storage card......but the files aren't removed from the \windows directory and when I went back to the storage card folder,all files were gone except for the IA_CID_StratUp files.

strange......

1) should I MOVE the files or cut and paste them

2) should I rename the files before I move/copy them elsewhere or After, since they dont seem to be moving from the original folder.....

would appreciate the help
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] efjay:
You dont have to move them, just rename each file to .old as it is mentioned in the error message. When all are renamed the cab file will install.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
thanks efjay....perfect concise instructions....got my caller ID downgraded and now the clock is ticking...lets see if this solves my GPRS woes.....
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
ok I'm sorry to bug you all about this but something just came up....The CallerID program runs everytime we have to do a hard reset right? that means that it must reside in the Ext ROM too? or a link to run it must reside in there....so *IF* I ever do a hard reset (God I hope I don't ever have to!!!) the CallerID file which will load will be the.........original one or the downgraded one that I have put it ( since I replaced the original files with the downgraded version)..... :roll:

I just wanted to know if on HR the original files are loaded, then we would basically need to replace the caller ID cab in the ext ROM too?

thanks in advance!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] efjay:
Yes if you hard reset the original caller id cab will be reloaded. But you can edit your extended rom quite easily. Look for the xda-extended rom unlocker on the ftp and install it. Unhide your ext rom, soft reset, unlock then soft reset again. You can now replace the caller id cab. Easiest way is to rename the "working" caller id cab file to match exactly the one in the extended rom. That way you dont have to edit the config txt file. HTH
[Galaxy S III Q&A, (US Carriers)] neel2004:
Hopefully someone can help me here -- I haven't been able to find an answer to my problem even with several google and forum searches.

A few days ago, my AT&T version of the Samsung Galaxy S3 stopped working with wired headsets, but headphones still work. When I plug in a pair of headphones (2 stripes on the miniplug), I get balanced, stereo sound.

However, when I plug in a headset with mic (3 bands on the plug), I get no sound even though the phone acts like it is playing sound. I've tried different audio apps, headphones, and headsets, and the problem stays constant. Each headphone / headset also works on other audio sources.

I am AT&T's version of 4.1.1, kernel version 3.0.31-274808, and do not think any updates have been downloaded recently.

Any ideas what could be causing this issue? I used to have a headset plugged in for most of the day, and miss the remote and phone mic features a lot.

Thanks in advance for any help you can give.

TLDR: Wired headphones work on GSIII, but wired headsets give no sound. Help!
[Galaxy S III Q&A, (US Carriers)] prabhjots:
Did you try using the headset with another phone?
[Galaxy S III Q&A, (US Carriers)] slaphead20:
Wrong forum;)
[HTC One S] Rugged96:
Guys

I have to return to stock so that i can my phone back to HTC for factory work. It is not going back to TMOB.

With all that i have done i want to make sure i follow the steps and do everything.

I currently have upgraded to the latest firmware 3.14 and have HBOOT 2.15.0000. I'm S-OFF with Super CID.

what do i need to un-do in order to return to stock?

Can i simply flash a stock RUU and relock or do i need to put TMOB CID back on, go to S-ON, etc?

all help is appreciated.

Rugged
[HTC One S] Flashalot:
Run this command

fastboot oem writecid T-MOB010

Go Here

For unlocked to locked

Download RUU

Run ruu

And plz for the love of god make sure your on stock hboot (meaning all ready ran a ruu ) when you give this command or you will brick

fastboot oem writesecureflag 3

You should now be bone stock
[HTC One S] Rugged96:
that's exactly what i ended up doing. i had to run around 3 different threads to find the steps but i got it to work. thanks for putting it together in one place!
[HTC One S] Flashalot:
No problem glad to help
[HTC One S] Rugged96:
HTC is shipping me back my phone but i'm curious.

what are the odds that they repaired my version vs just sending me a refurb device?
[HTC One S] Rugged96:
okay...it looks like i got my exact same phone back...how do i 'undo' these steps? i assume it's easier than starting from scratch.
[HTC One S] Flashalot:
To being rooted or stock
[HTC One S] Rugged96:
I want to go back to unlocked, Super CID, S-Off and Root. since i was previously all those things do i start completely over?
[HTC One S] khan.orak:
Unlock/Root using Hasoon's AIO tool

if you don't mind answering, why exactly do you want to SuperCID/S-OFF?
[HTC One S] Rugged96:
I want to install the latest kernel and run cm10.1

Sent using Tapatalk 2
[HTC One S] khan.orak:
For that you need unlocked bootloader, custom recovery and root. No S-OFF/SuperCID needed.

In fact, largely, some folks have reported bricks running CM10.2 (4.3) with S-OFF.
[HTC One S] Rugged96:
I prefer to have S-OFF for the ease of flashing and I was planning CM10.1 not 10.2...i'm not ready for that fun yet
[HTC One S] Flashalot:
Mooneshie then fastboot oem writecid 11111111
[Android Q&A, Help & Troubleshooting] deadbunny:
it all started when i installed a faulty launcher

my phone's in a boot loop

when i try to slide the key into the lock on the lockscreen, it reboots.

otherwise touch is working fine (emergency call, status bar etc)

but since i can't open the lock, i can't access the home screen and apps and stuff..

obviously i tried recovery, but it doesnt have a factory reset option (strange). the recovery mode only has some phone tests and calibrates

the other hard key combination opens up some black screen with "fastboot mode" written. and that's it.

my phone is gingerbread 2.3.5, unrooted. the company is a less popular and cheap one but it's not china.

long story short, i cant get outta boot loop coz recovery doesnt have factory reset option

plz help!
[Android Q&A, Help & Troubleshooting] deadbunny:
thanks

i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.

fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
[Android Q&A, Help & Troubleshooting] majdinj:
In recovery, try to wipe cache and dalvik cache. If still, then you need to flash stock ROM
[Android Q&A, Help & Troubleshooting] WildfireDEV:
That is because when you ran those commands you wiped the rom on your phone completely so now when it tries to boot it has nothing to boot into. Please give the name of the phone so we can help you more.

**Press the thanks button if I have helped you.
[Android Q&A, Help & Troubleshooting] demkantor:
Erasing the user data and cache was good, but erasing boot erases your kernel, just find the one that came with your ROM and as long as its in .img format use fastboot to flash it and all should work great
[Android Q&A, Help & Troubleshooting] deadbunny:
yo, the prob is, it's a recent phone, but from qmobile

it's qmobile bolt a2 lite. i cant find the stock rom (it was released in 3 july 2013, i believe)

so, can't i install some other ROM that all gingerbread phones support? it has 1 ghz processor, 256 mb ram, and 200 mb internal storage

thanks
[Android Q&A, Help & Troubleshooting] deadbunny:
i have a 2gb micro sd card as well
[Android Q&A, Help & Troubleshooting] demkantor:
Then you have an issue, right now it sounds as you have no kernel maybe if your lucky the manufacture will respond to a request to release the kernel source or have a copy of factory firmware you can download.

Otherwise try to find someone with the same phone and see if they can get you a copy of the kernel
[Android Q&A, Help & Troubleshooting] deadbunny:
since i can't find the exact stock ROM for this lesser known brand, isn't there some universal gingerbread 2.3.5 stock rom? the manufactureres obviously use a modified version of google's stock gingerbread 2.3.5
[Android Q&A, Help & Troubleshooting] demkantor:
It won't work, you can't just flash some generic aosp ROM to your phone, if it were that easy every phone would have tons of ROMs

You need a device tree that contains all the proprietary drivers etc to build from source and just flashing a random kernel or ROM won't do you any good (possibly make things worse)

You need to contact the maker of your phone and request this or find someone who can get you a ROM dump
[Android Q&A, Help & Troubleshooting] deadbunny:
okay thanks
[Android Q&A, Help & Troubleshooting] qmobilea2:
Simple just claim ur warranty man!!
[Android Q&A, Help & Troubleshooting] deadbunny:
im not in pakistan dude. i moved to canada. that's the prob
[Android Q&A, Help & Troubleshooting] qmobilea2:
That's sad :(
[Nexus 7 (2013) Q&A] JayBomb999:
Update: Star this Android issue if affected: http://code.google.com/p/android/issues/detail?id=58401

I'm noticing intermittent bouts of erratic multi-touch on the Nexus 7 (2013) 16GB. I exchanged one device already hoping that it was a HW defect, but my second device behaves in exactly the same way.

Chrome, Dolphin, web-view, maps (especially maps) will often jump all over the place during pinch-to-zoom. Sometimes it works fine, but too often, it jumps zoom levels erratically. Edit: This also manifests as double taps and/or "ghost taps" when using the keyboard.

I've installed YAMTT (Yet Another Multitouch test) and I've observed the touch points disappear, change direction and even suddenly register a 3rd touch. None of my other devices do this.

I'm reluctant to exchange the device yet again, but I haven't read about anyone else who's witnessed this. Am I alone in observing this behaviour?

Edit: Here is a terrible video attempting to highlight what I'm seeing in YAMTT: http://www.youtube.com/watch?v=_ZRiMiNzs0U

And another video in Google Earth (fixed): http://www.youtube.com/watch?v=14cPiiM3Pwg

Someone else experiencing the issue: http://www.youtube.com/watch?v=Xpl26UgcuSs

FINAL UPDATE: I exchanged the device again and the issue is gone (so far). My advice: if you're experiencing this issue, return it. If it continues to happen, return it again until it works. :)

As a side note, for those experiencing the mushy/hard to press power button, that issue was fixed for me as well.

Final Update Part 2: I am sad to say the issue is still present after all. I'll admit that it is less prevalent than with my first two N7s and the "jumps" are less severe. However, it's still there and I'm not prepared to live with it. Therefore, I am returning the device to get my money back. I'll keep up to date with this issue, and I'll likely buy it down the road when a clear resolution presents itself. I know it would be a great tablet without this problem.

To recap my experience:

First N7 had erratic multi-touch, stiff power button, keyboard and other touch screen issues. Exchanged.

Second N7 had a good power button, but the erratic multi-touch and keyboard issues were still present. Exchanged.

Third N7 had a perfect power button and no keyboard issues, but the erratic pinch to zoom was still present (though less severe). Returned.
[Nexus 7 (2013) Q&A] Speedy Gonzalez:
it happen to mine while typing nothing a software update can't fix or even better custom rom ;)
[Nexus 7 (2013) Q&A] JayBomb999:
You're probably right. I was just concerned that no one else had mentioned it. I find this behaviour quite annoying. :)
[Nexus 7 (2013) Q&A] mi7chy:
Does the issue go away if you actually held it with the other hand (going by video)? Sounds like the behavior of the 1st gen N7.
[Nexus 7 (2013) Q&A] JayBomb999:
I'll try that, thanks. I have the original Nexus 7 as well and never noticed this issue. Could you elaborate a little? Was the issue eventually resolved?
[Nexus 7 (2013) Q&A] mi7chy:
It's designed to be used on a grounded surface either held in hand or on a grounded surface. It's an electrical behavior so I doubt software would change that. Please try held in hand and report back.
[Nexus 7 (2013) Q&A] jxr94:
I've got this a little bit, glad I'm not the only one with the problem, mine only does it when I hold it above me and use it lol. Everything else is fine with mine so I'm keeping it.
[Nexus 7 (2013) Q&A] samnoon:
Are you sure this is a software issue?

I remember back when I had an HTC Desire, it had multitouch issues but the fault lay with the digitizer and no update could fix it.
[Nexus 7 (2013) Q&A] JayBomb999:
I've tried gripping in both hands, from the bottom bezel, on the table and on the couch. Still, I see this behavior. It's not constant, but it's prevalent enough that I don't know if I'm going to keep it.

It sucks because otherwise I really love it.
[Nexus 7 (2013) Q&A] player911:
I dunno. I'm seeing weird anomalies with mine. Moving 2 fingers around, a random 3rd pops up.

Hopefully just software woes. The Galaxy Nexus did this, N7 did this, and now the new N7. Its rare. Haven't had a problem.

Sent from Nexus 7 FHD from XDA Premium HD
[Nexus 7 (2013) Q&A] Brenex:
I just ran the same tests you did using YAMTT and did not have any of the same problems. I haven't noticed any mutlitouch issues either.
[Nexus 7 (2013) Q&A] justThisGuyHere:
I found this thread looking for someone else who was having the problem I was - my device was doing exactly the same thing in Google Earth. Thanks for posting it!

Oddly enough now that I've found this thread, the device isn't doing that anymore. It's tracking perfectly in Earth and also in YAMTT.

It tracks fine when being held in one hand, on a grounded or not surface, when touched with one hand or two.

Very odd.
[Nexus 7 (2013) Q&A] GreenXSniper:
I had this issue with my 1st n7 2nd gen (which i bought yesterday). I returned it to bestbuy and got a new one which seems to be fine.
[Nexus 7 (2013) Q&A] JayBomb999:
I've already exchanged it once and each had this issue. I think I'm going to try again tomorrow. I'll report back.
[Nexus 7 (2013) Q&A] adamhlj:
I had a similar issue with google earth on my 1st gen N7. I can't test it anymore, tho, because its sitting at the bottom of a lake. But it would randomly zoom out or in like crazy or jump halfway across the world.
[Nexus 7 (2013) Q&A] nba1341:
I have this issue extremely annoying. My keyboard double presses letters at times, zooming I have ttrthe problem, trying to long press a link I also get it unregistering touch

I hope this. Is. Software I don't waqmt to return this. Otherwise perfect device. You can see it happoening as I try to type
[Nexus 7 (2013) Q&A] carfreak715:
This actually happened to me for the first time about an hour ago. As said before, I hope this is a simple software bug, and not some serious hardware issue. Quite frankly, I have a feeling that going through a return is going to be messy, as I've bought mine from my local Gamestop.

From a GNex
[Nexus 7 (2013) Q&A] JayBomb999:
The gentlemen that posted the following video said he exchanged his device and the problem went away: http://www.youtube.com/watch?v=Xpl26UgcuSs

I know it's only one person, but this leads me to believe it might be a hardware/quality issue. I have exchanged mine once for this issue already (Best Buy) and it was extremely easy. I am going to exchange one more time and will report back my findings.
[Nexus 7 (2013) Q&A] JayBomb999:
I didn't mention the keyboard issue. I too am seeing ghost taps when typing.
[Nexus 7 (2013) Q&A] player911:
Hmmm. No ghost taps here. I've been on xda a lot since I got this.

Not good though. Could just be a bad batch. Seems like the dead spots would be caused by a hardware issue... Bad connections or something.

Sent from Nexus 7 FHD from XDA Premium HD
[Nexus 7 (2013) Q&A] sonnydroid:
I bought mine on 7/26, had the multi-touch issue and I was finally able to exchange mine today at Best Buy. The new one I just got doesn't have the multi-touch issue (on the JWR66N firmware). Afraid problem might come back if I update, so I'm going to hold off till we receive more info.
[Nexus 7 (2013) Q&A] Liquidretro:
This is really what I want to know, if its the software update causing it (Fixable) or if its hardware problems and I need to exchange mine. I feel like my time to exchange with Amazon is probably running out.
[Nexus 7 (2013) Q&A] mensaphone:
Ditto to all the above. Just one additional point. My original had a bit of the curved back syndrome, this one seems much flatter.
[Nexus 7 (2013) Q&A] thedeadletters:
There's a lot of discussion regarding if this is a hardware or software problem and both sides have very valid points. Unfortunately, I don't think Google has addressed the issue properly. I bought mine on 7/26 and waited for some sort of response from them and all we have are several forum posts from affected users. Sure, there are some replies from Google employees, but none offer any substantial information related to a solution. Sad to say, but I decided to return mine today and buy a new one once this is resolved.
[Nexus 7 (2013) Q&A] :
Went to another Staples that said they had some left. Once there the clerk tells me he thought they did have some however they were returns and added they had lots of returns because of the touchscreen. I think I will wait a while before purchassing another or at lease test it before going home.
[Nexus 7 (2013) Q&A] :
Do you guys think its a software issue ? I sure hope so :/ love this thing.
[Nexus 7 (2013) Q&A] delfin2003:
can more people who exchanged their tablets chime in on this? Is your new tablet having these issues? What's the assembly date? Mine says its 06.2013 on the side of the box and I am having issues and also hoping that this is a software bug rather than a hardware problem but like many others I did two updates as soon as I got my tablet so I couldn't test
[Nexus 7 (2013) Q&A] canoo:
I had originally bought mine from a staples. They had no more in stock so I returned it and picked one up from Future Shop (Canadian Best Buy). I haven't done the update to JSS15J. Running JWR66N right now. Zero touch screen issues what so ever. I never even got to test out my original N7 with this build. Scrolling is buttery smooth, pinch zoom is working perfect, no ghost taps while typing this whole post. Every second word would mess up on my last one running JSS15J. I don't plan on upgrading to JSS15J at all for now. Google has 14 days from me to fix the multitouch issues in JSS15J. If its not fixed by then I'm sad to say I'll probably return the tablet...
[Nexus 7 (2013) Q&A] Sud0lit3:
Strange issues

Hello,

so I've been reading this thread trying to figure out if I have a defective device or not so I made a video to get some assistance on this matter from XDA.

The video is only 40 seconds long if XDA can help assist and say if this is normal (potential software bug) or if its a hardware malfunction. this way we can maybe post the video and explain if this is normal or not to other users so they can make a decision on either exchanging the device or not.

Some things to note: areas that it seems to not pick up will work on the second swipe. so I can't really claim that its dead areas. also everything about this one I have is basically perfect no dust or dead pixels or backlight bleed. This is the only problem that I've noticed which is why im asking for the assistance of XDA

Video Link: http://www.youtube.com/watch?v=DWwS_pTblNg&feature=youtu.be

I really appreciate it your help.
[Nexus 7 (2013) Q&A] canoo:
Those red marks are supposed to be from a second touch on the screen. But since you are using only one finger they are erroneous, i.e., they aren't supposed to happen. In the touch tester mode try placing two fingers on the device and overlapping the the lines in the X axis and Y axis. This is where the issue really presented itself on my Nexus 7.
[Nexus 7 (2013) Q&A] Sud0lit3:
Yea I'm definitely experiencing the X & Y axis issue where it just completely freaks out. While testing for that I came across this happening on my device. Do you think it's a hardware issue and that I should return it?

I have yet to come across anyone else with this issue but I found in the past that sometimes people just don't want to post because they don't care enough but I am curious to know if anyone else is experiencing this multi-touch problem as well.
[Nexus 7 (2013) Q&A] delfin2003:
Same here. I waiting to see if google releases a fix for it in the next week, or I might have to go and get it either swapped our or returned

---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------

It might be, even though some guys say they swapped theirs out and a new one with a newest build does not have these issues...so I donno. I sure hope it is a software fix
[Nexus 7 (2013) Q&A] Sud0lit3:
I found that a high rate of these people refuse to do an update on their device in fear that the problem will return :/ this makes it really difficult to tell if it's software or hardware.
[Nexus 7 (2013) Q&A] canoo:
None of us are 100% sure what the problem is or if it's fixable via OTA software update. If it's not fixed with an update in the next two weeks I'm not willing to risk that it's not a hardware issue and plan on returning mine (Currently running JWR66N on a second device with zero touch screen issues so far). I plan on keeping mine at JWR66N for about a week to really get a feel for it. After that I'll update and see if I notice a difference. A significant amount of people have claimed their device was perfect in JWR66N and then had broken multitouch after updating to JSS15J. So who knows...

I can't post links but if you do a Google search with "Google groups nexus 7 (2013) erratic" you'll find a thread with even more people who have the issue along with a couple replies from a Google employee early on (no recent replies on the issue).
[Nexus 7 (2013) Q&A] delfin2003:
I'll be watching this thread closely for your feedback after you update to JSS15J. If you start experiencing issues then it's definitely a software problem and I am willing to wait for a fix from google and not return mine.