Related
Hello - I've been searching these forums and the wiki and Google too looking for a solution to this but so far, can't find a solution so hope members here can help:
I recently got another XDA Exec and a week ago, the phone mic stopped working. I know its not a hardware problem as the phone can record my voice for notes.
I've done a few hard resets and each time, nothing changes, so am truly baffled.
I'd be very grateful for any answers to this, and apologise in advance if I have missed an answer that has already been posted - I have tried searching, honest!
Cheers,
JB
Jon Brown said:
Hello - I've been searching these forums and the wiki and Google too looking for a solution to this but so far, can't find a solution so hope members here can help:
I recently got another XDA Exec and a week ago, the phone mic stopped working. I know its not a hardware problem as the phone can record my voice for notes.
I've done a few hard resets and each time, nothing changes, so am truly baffled.
I'd be very grateful for any answers to this, and apologise in advance if I have missed an answer that has already been posted - I have tried searching, honest!
Cheers,
JB
Click to expand...
Click to collapse
Try another ROM...perhaps?
I could do, but before I attempt anything like that - something I've not done before - I wanted to figure out how to remedy it with the existing ROM, which is the O2 one installed without all of O2's own stuff.
It was working perfectly well with this ROM before....in fact the only thing I can think of that might somehow have caused this was me pairing the XDA with a bluetooth handsfree set the same day. It might just be coincidence, it might not - I can't tell.
I suppose what I'm hoping for is some guidance re any settings on the device that I don't know about that have caused this, or the necessary registry edit to remedy the problem. Its odd that the phone mic worked before then stopped working, despite hard resets with the same ROM. Forgive my naivety, but I thought ordinary user-level tweaks didn't affect the core settings of the ROM....or am I wrong?
Cheers,
JB
PS - Lower Hutt! I remember seeing it through the mist one day after catching the ferry from the South Island before heading off to Cuba Street for a boozy afternoon...
Yup, got exactly the same problem before buying my HD.
I thinked that my micro was dead and didn't try to fix it before.
Just now i got here to search another rom to test and i saw this thread highlighted
The rom on my universal is TOMAL 8.0 or more i don't exactly remember the version, what's yours ?
I will download another version to check if the micro will be alright and give some feedback
Jon Brown said:
I could do, but before I attempt anything like that - something I've not done before - I wanted to figure out how to remedy it with the existing ROM, which is the O2 one installed without all of O2's own stuff.
It was working perfectly well with this ROM before....in fact the only thing I can think of that might somehow have caused this was me pairing the XDA with a bluetooth handsfree set the same day. It might just be coincidence, it might not - I can't tell.
I suppose what I'm hoping for is some guidance re any settings on the device that I don't know about that have caused this, or the necessary registry edit to remedy the problem. Its odd that the phone mic worked before then stopped working, despite hard resets with the same ROM. Forgive my naivety, but I thought ordinary user-level tweaks didn't affect the core settings of the ROM....or am I wrong?
Cheers,
JB
PS - Lower Hutt! I remember seeing it through the mist one day after catching the ferry from the South Island before heading off to Cuba Street for a boozy afternoon...
Click to expand...
Click to collapse
Could be a range of reasons, from some program install or addition to the software set to files going missing. Trying a new ROM or reflashing with the original (but believe me, once you try new WM6.1 You'll probably never go back) might be one of the solutions. Flashing of ROM is a piece of cake, however, I recommend reading as much as possible on the procedure and ways to remedy the unexpected situations before you begin. Everything you may possibly need and answers to all your questions is contained in a Wiki - have a look and ask questions if you cannot find answers and are completely stuck.
Heh, Lower Hutt is on the opposite side of the harbour, coming from SI.
I reflashed with TOMAL 8.9 and micro works very well now
i readed too fast yesterday and didn't see that you're using the original rom, like enigma1nz suggest you, i suggest you too to try a 6.1 rom, it's really great and improve a lot the speed/touch felling/etc for the universal.
Plus it's really easy to flash a rom, it's not necessery to read a lot of documentation,
you just need to connect your universal to pc with activesync (4.5)
and launch the exe file from the rom
I for the life of me cant figure out why my camera is completely dead! I have FULLY wiped all caches,everything under 'WIPE' via AMONS and even formatted my SD card as well as trying an alternate SD card(both 8GB--C6speed)--never had a problem w either card on ANY ROM...ALL OF A SUDDEN the past 2days my camera goes to a FULL BLACK SCREEN,when pressing the CAMERA icon. Occasionally the taskbar will remain uptop but will timeout when screen display shutsoff. Now if i launch CAMERA via DESIRE ROM(KING),ill get the notice about clicking trackball to resume camera but as soon as i click it,the message dissapears and the screen will go back to black screen again...and repeat. I SWEAR i have DONE MULTIPLE COMPLETE WIPES AND REFORMATS so im left to believe its THE HARDWARE itself! CAN ANYBODY PLEASE LEND ME A HAND IF the similar problemhas occured...On the Nandroid backups that ive restored from FULLY FUNCTIONING bkups,if i launch NEXUS TORCH it will say CANNOT ACCESS LED---this is THE ONLY info besides the "camera wake message"mentioned earlier that i can provide. Thanks in advance and pleas edont flame for NOT being in Q&A bc this is more of a DEV related restore question.
**oh and BTW--I DID TRY TO INSTALL the DESIRE R2 cam fix and does nothing. I tried it when all was working fine early in the week and it did nothing to help FLASH timing for me,so i NAN restored back to prior state and CAMERA continued working until about THURSDAY night--regardless--PHONE is in OUT OF BOX STATE--MINUS UNLOCKED and it STILL doesnt work!---PEACE and Happy Mothers Day to any Mothers out there in XDA world!
***Captain Obvious to the Rescue!!***
Your hardware has malfunctioned. Contact HTC for a repair.
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
ghostrida said:
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
Click to expand...
Click to collapse
1. i should have known you were from Philly and cant read--I TRIED STOCK ROM
2. CAPS is to put highlights on key terms so idiots dont read over the fact that I DID TRY STOCK ROM---see how that helps?
3. Thanks for your informative responses---any suggestions from CAPTAIN OBVIOUS how to get service on a ROOTED device without being charged full price on the phone?? Ahhh--thought not!--So i tried here to see if anyone else had similar situation. AGAIN-thanks for your help as well SERIAL TOON--geez
If it's a hardware failure they won't charge you.
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
What do you base this on...Heresay?
BlueScreenJunky said:
If it's a hardware failure they won't charge you.
Click to expand...
Click to collapse
I didnt intend to sound rude,im just a little pissed right now..I Only ask bc i already had an issue in January days after receipt of phone. Issue was solved by sending me a new battery bc other was causing random shutdowns (ive since forwarded this info to another XDAmember that had exact same issue and they give him replacement phone at 1st but issue continued to occur--i told him about my story after he posted his problem, he contacted them this weekend and confirmed with me today that a new battery was on the way..see my public IM's for info). Anyway,when i was dealing with the battery issue they said they would definately NOT be able to fix under warranty bc the phone is rooted and unlocked. I can attest to the few people on here that said theyve been successful in such cases,but either way,IVE ALREADY STATED that i tried the DESIRE R2 camera kernal to see if that helps,so im not going to be dishonest and tell them i havent tried anything other than custom roms. Again..positive suggestions or similar experiences with warranty info would be appreciated....trollers looking for a funny post or to degrade people can eat one!
joshlusignan said:
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
Click to expand...
Click to collapse
Thanks JOSH, ill look into it tommorrow--as i stated tho--i feel im being dishonest for trying the DESIRE R2 cam and saying that they should cover it---uninformed people will assume THAT couldve caused it,even though i used phone afterwards for a few days w no side effects
Hey Milton, like others have mentioned in here might want to try flash back to stock and seeing if the problem persists. If it does then your looking at a hardware problem and you should contact HTC/google for repair.
Yea...i was thinking that from get go--(hardware prob). Im on cheesy STOCK ROM right now and have been for cpl hrs...but its obvious its gotta be hardware...NOW comes the crappy part of trying to explain it to HTC when attempting to get an RMA!--Yee Haa!
MOD PLEASE CLOSE OR DELETE---THANKS!
Milton, among the items on the very small list of things folks around here want in return for helping you is that you lay off the caps. Doesn't highlight anything that you'd want to highlight.
Doug
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
As for your phone. Call Google which will probably have you call HTC. People have gotten their rooted devices fixed for free if it's a genuine hardware problem and nothing caused from the rooting process.
milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
You should send it to HTC for repair. Charging fee or not, but thats the only option to you right now because its a hardware failure.
mikroN1 said:
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
Click to expand...
Click to collapse
I was thinking the exact same thing, don't know where he must have learned how to type. Then you criticize people from Philly, or whatever its called somewhere, for not knowing how to read. I would say mirror that advice and learn how to type.. type properly.
Torch will work until camera app is used then it wont work again until i reboot. After reboot, torch will work ONLY on regular/lower setting. MAX brightness will not work. Toggle back to LOW setting and torch will work again. Im going to try what DOUG suggested bc that is the only thing i havent tried yet...but the way torch and camera are acting up and requiring reboots keeps me willing to try software tricks first...WHAT ties the TORCH's HI setting to the camera app adn yet keeps the LOW setting seperate!??..ill try the TORCH dev real quick for some insight on how the two work hand in hand.Thanks for anyone using their time to help instead of criticize. Sorry for mocking ones ability to read but i was quite [email protected] time bc i lost a major function on my phone.My apologies to all
Seriously Milton? More?
milton007 said:
Please DONT lend assistance to someone like this. IF they cant bither to read THE MOST SIMPLEST instructions, they should NOT be attempting this in the first place...thats just sheer ignorance...
Click to expand...
Click to collapse
The attitude, hostility and the caps are not welcome here.
Along with the others I have no sympathy for you. Learn proper grammar and get a better attitude.
Troll much? Go tell your mother happy mothers day if you have that much time to pull up old posts from people asking questions in a 'kernal forum' about basics. Basics that anyone should know, if not they stand a much better chance on damging their phone. It wasnt being ignorant. Since you know everything there is to know about everyones posts, tell me where the topic dealing with my specific camera issue has been previously posted and ill be glad to read and search thru that forum. I wasnt the one asking questions about something mentioned in the OP (uh oh i used caps--oh geesh-someones gonna be saaad now!)and numerous pages before. Im sorry i dont spend all my life on forums to know that only words approved for caps are indeed CAPITALIZED. Petty little boy-and by the way, i was trying to stress your good advice by typing your name in caps so people would credit you with the help-Sorry to have taken your precious time sir. Good day.
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
hey, so ive traded my phone 2 times as some people already know that and reinstalled gun bros, im experiencing something i havent experienced in the other 2 phones which is weird touchscreen issues, sometimes the controls work sometimes they dont when i touch them, the main issue is with movement keys on the upper side of the screen or when viewed horizontally on the left side of it.
Anyone experiencing random glitches with the touchscreen? as in sometimes even though youre touching it the phone doesnt detect it and you have tap the touchscreen again to work?
Thanks in advance!
EDIT: this mostly happens when im "multi" touching it
Maybe you should take a video using a multitouch test to actually see the issue.
bcam117 said:
Maybe you should take a video using a multitouch test to actually see the issue.
Click to expand...
Click to collapse
Heya thx for the reply i can say its a false alarm, it semms its the update fault. phew
as many others are complqining now in the forum of glu
Hi fellow Gun Bros players I do not mean to hijack this thread but I would like to ask if anyone is able to connect with facebook in the new version (2.0)? My friends on LG O2X and HD2 can connect no problem but for some strange reason I cannot.
I was on Villain ROM 1.4 and I even flashed to 2.0 to see if it helps, but so for no go for me.
Any feedback would be appreciated. Thanks in advance.
Dextrosan said:
Hi fellow Gun Bros players I do not mean to hijack this thread but I would like to ask if anyone is able to connect with facebook in the new version (2.0)? My friends on LG O2X and HD2 can connect no problem but for some strange reason I cannot.
I was on Villain ROM 1.4 and I even flashed to 2.0 to see if it helps, but so for no go for me.
Any feedback would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Sometimes mine connects while other times its stuck in the loading screen trying to connect... i havent messed with stuff like adding bros cause i dont know how to anyways, ive added some in facebook gun bros but they dont appear on my phone.
I got this thinking I am buying the best machine available for streaming and from day once , have been plagued by problems.
First on opening the unit, the AC adapter was faulty. It turned out to be a piece of plastic stuck between the contacts.
Anyway I solved that problem on my own as shipper refused to entertain any claims outside the USA.
Then when it finally got going, I noticed most apps had loading circles going around, and were waiting to download. Tried everything possible and they would not move ahead . Finally cleared cache and data on the Google Play Store app and the app started downloading for precisely one application then it stopped and again same circling. I had to clear data on the Play store app every time to update each and every app on the machine.
Then i couldnt find my favorite apps in the app store. Turns out , Shield does not support. Ok, no problem, i said lets compromise and move on.
Downloaded MX Player Pro from the Play Store and sat down to watch a 1080p movie on the USB drive and again the loading circle popped up on the screen. Buffering on a 1080p file from a usb 3.0 flash drive !!! I copied the file onto the HDD and again the same problem. I had no idea how to watch this movie, BTW had watched it a night before perfectly on my Alphawise H96 Pro+.
Then one by one all the apps started crashing.
I decided to do a factory restore which lasted 2,5 hours. After restore, same problem, all apps crashing.
I do not have anything connected to the Shield , no usb drive. no air mouse, nothing. Both ports are empty.
The surprising thing is even Google play store crashes , also the Lean back Launcher and the system crashes.
I called up Nvida support and they say we do not support the Shield as you are not in the USA. Guys, even the chinese from Aliexpress support you and give a replacement if item is faulty. All they ask is a video showing the problem. In todays times, there are going to be non us customers buying from the Usa, you need to support them also.
Stuck with a Lemon.
Cannot even sell it off as whoever buys it from me will throw it back in my face. The dam thing is just a few days old.
Havent slept three nights, trying to solve the problem, got finally tired and have connected the Alphawise to the TV and Shield goes back into the box
There are lots of other people complaining about similar issues but no fixes from Nvidia ?
If someone can please suggest something which I can try, I will be highly obliged. Else I am stuck with a $300 paper weight.
I did a Full Reset (2.5 hours) once and a Fast reset , hoping it would solve the problem. But no luck.
Please help, someone, please.
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
DreadfulDrummer said:
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
Click to expand...
Click to collapse
I have the 2017 shield pro. and all though I wouldn't say it has been a nightmare, it hasn't been without its problems; such as apps randomly not responding with a message saying close the app or wait...slow down of apps opening at all to include settings not opening...streaming apps to include Netflix not playing or simply force closing...even Leanback Launcher stopping with the message Leanback Launcher has stopped...close or wait....I finally bit the bullet after posting on this forum and getting no response and did a wipe of data and dalvic from TWRP and re-flashed the 6.1 or 6.2 firmware. It seems to be running smooth so far. Got my shield from amazon. wouldn't expect this many problems from a $300 device that claims to be the best on the market. When it works without problems it is a great device!
Hope you get it sorted out. If nothing else works, it may be worth it to fastboot boot TWRP if you have an unlocked bootloader...wipe data and dalvic and install the 6.1 firmware update.
Real sorry to here you had so many problems Mate. Hope they sort it for you ....But if they fail to deliver (which they really should not, Take no excuses from them ,Polite but firm)
You have the option to get a Donner clone from a thread based in these forums ,along with further help in the threads below.
https://forum.xda-developers.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580
https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
I would almost Guarantee that it is your Hard drive at fault ...as your descriptive clearly points to this as the culprit.
I have read a number of post and comments in them threads ,and it is invaluable ... I am Dam sure many will bend over backwards to help you out.
Real shame the same can not be said concerning NVIDIA ...Hopefully they see your Dilemmas and respond dutifully.
Good Luck!
Best Regards,