EDIT: I have fixed my issue by flashing to the EDEN rom, because of the size alone it must write over some files that the utopia and beast do not so this was my solution.
When I first got my Adam I tested HDMI out and it worked fine, used it on 3 different tvs with no issues.
I switched to Utopia rom and I lost the ability at that time.
I then did complete wipe factory reset and flashed The Beast rom 1.2 and the HDMI still didnt work.
I then flashed The Beast rom 1.3 without a wipe and still no success.
Everything else works fine.
If anyone is having an issue with your HDMI out not working please post and also note if it never worked or if not when it stopped working.
I really hope there are no hardware issues we have to worry about...
Edit : Fixed
Just as an update post I have fixed my HDMI issue.
I decided to do a full wipe/cache clear and flash to the Eden rom in an attempt to get my HDMI working. To my delight the issue has been resolved. So if anyone loses their HDMI out you might want to flash to the eden rom with enhancements.
Im sure I can flash from here on and still have HDMI but im done for tonight.
no6969el said:
When I first got my Adam I tested HDMI out and it worked fine, used it on 3 different tvs with no issues.
I switched to Utopia rom and I lost the ability at that time.
I really hope there are no hardware issues we have to worry about...
Click to expand...
Click to collapse
I think these 3 lines would summarize the dismissal of it being a hardware issue.
Glad to see you got yourself fixed up. I would post and let the authors/devs of Utopia, of which Beast is heavily based on, about your findings.
-CC
EDIT: it seems others have not had the issue you experienced, perhaps something in the steps?
Related
Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.
internetpilot said:
Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.
Click to expand...
Click to collapse
Had none of these issues. Maybe reinstall your player apps onto the new platform, especially since MOBO should prompt you to download a specific codec pack... other than that, maybe let us know what formats you're using so we can give more precise info.
simonsgray said:
Had none of these issues. Maybe reinstall your player apps onto the new platform, especially since MOBO should prompt you to download a specific codec pack... other than that, maybe let us know what formats you're using so we can give more precise info.
Click to expand...
Click to collapse
I deleted/reinstalled both RockPlayer and MoboPlayer, but no joy. I even factory reset my A500, and then after basic configuring only installed Mobo and the exact same issues occurred.
I'm attempting to play xvid files that worked just fine using MoboPlayer, RockPlayer, and the stock player on stock HC 3.01, but they just wont play on stock HC v3.1. For me, this is a HC v3.1 dealbreaker.
Edit: Just got notified of 4.010.10 gen2, downloaded it, updated, and things are now working a lot better. A little quirkiness was going on in both RockPlayer and Mobo, but it went away when I deleted both apps and reinstalled. Since that update, the stock player works fine on these same xvid files again.
Maybe I'll stick with HC v3.1 after all! (unless the next incremental breaks it again like the 4.010.8 gen1 did)
I had the opposite experience. Videos that would not play smoothly in 3.01, now play great in 3.1. The only issue I am having with 3.1 is the dropping WiFi, but hitting the reset button seems to be solving that for now.
nithos1 said:
I had the opposite experience. Videos that would not play smoothly in 3.01, now play great in 3.1. The only issue I am having with 3.1 is the dropping WiFi, but hitting the reset button seems to be solving that for now.
Click to expand...
Click to collapse
When you say "solving" does that mean you have to do the reset thing regularly?
(It may just be a syntactic difference, but if it was fixed, I'd have said "solved it for now". "Solving" implies an on-going condition of fix and re-fix)(Genuine question - I'm not commenting on your use of English)
To the OP:
I have no intention of letting my A500 update to 3.1. I've seen waay too many posts of bugs and faults in it.
OK, the rooters and rom flashers all say to root and delete this and do that.. I say you shouldn't HAVE to root and delete to fix the update's errors!.
Nope, me = 3.01 for now. I'll see what 3.2 might be like..
I will not never and ever go back to 3.0.1 for 1 pure main reason
USB support of my camera... I plug and the gallery popup and can transfert the files directly without thinking something else... (I hope we will have some kind of create folder by date or else...)
Fluffbutt said:
I have no intention of letting my A500 update to 3.1. I've seen waay too many posts of bugs and faults in it.
OK, the rooters and rom flashers all say to root and delete this and do that.. I say you shouldn't HAVE to root and delete to fix the update's errors!.
Nope, me = 3.01 for now. I'll see what 3.2 might be like..
Click to expand...
Click to collapse
I have to pretty much agree -- I have seen more problems than benefit. With the latest incremental update things seem to be working a lot better, but I am worried about what the next incremental update could break.
I didn't see much of a purpose in updating my HTC Evo 4G phone from Froyo to Gingerbread either. I immediately went back to a Froyo based ROM until the same ROM dev came out with a custom Gingerbread ROM. These OTA's from the manufacturer aren't always the gold and jewels everyone anticipates.
sanaell said:
I will not never and ever go back to 3.0.1 for 1 pure main reason
USB support of my camera... I plug and the gallery popup and can transfert the files directly without thinking something else... (I hope we will have some kind of create folder by date or else...)
Click to expand...
Click to collapse
I never had two much of a problem hosting my Pentax DSLR camera on HC v3.01. It was sometimes slow to discover it, but then I started using the USB Mount All app everything USB was discovered quickly.
I'm still not 100% happy with my video performance on v3.1. It's much better with 4.010.10 gen2, but it's still not as good as it originally was with v3.01.
I was experiencing major issues with the Wifi after the update as well. It was really annoying.
So last week I tried a bunch of things. What worked for me was to set the wifi to turn off when the screen was off. Now, if I am still downloading things it stays connected with the screen off. Also, I still hear the notification sound when an email comes in even if the tablet has the screen off and nothing running. Its been one week and I haven't noticed a difference between it being on or off with the screen. I haven't had to reset the tablet nor have I had to delete any files. It runs perfecto mundo and doesn't drain any extra battery. Last night I lost about 8% overnight. Just something to try out.
No way I would ever go back lol. Using full keyboard and mouse with RDP makes this tablet take advantage of the speed and power of powerful desktop at home. ANd using the HoneyVillain ROM everything runs so well and smooth including all my videos.
In a word, no. I'd never go back. 3.1 has been great all around.
internetpilot said:
Is anyone else here tempted to go back to HC v3.01?
One of the main things I do on my A500 is watch downloaded videos, and I encounter quite a few problems with that on HC v3.1 that I never encountered on HC v3.01. MoboPlayer just flat out no longer works on my device -- I get nothing but unrecoverable lock-ups and force-closes. RockPlayer is still working (thankfully), but not in hardware mode. Even the stock video player can't play any of the files that I previously could.
Everything else that came with HC v3.1 is enough behind-the-scenes that I just don't notice it or it has no real world benefit for me. In other words, I definitely wasn't missing any of it back when I was running HC v3.01. I'm just not seeing any real world benefit to the v3.1 upgrade -- I'm only seeing negatives. I'm very tempted to go back.
Click to expand...
Click to collapse
When making a post like this, it's a good idea to just throw the build you're on out there. I for one have no issues with 3.1. I never had issues with the first build that came and I am not having issues with the recent build seeded yesterday. I use Moboplayer as well.
Did you do any sort of modding? ie: Did you get 3.1 or 3.0.1 unofficially through XDA or are you/have you been running completely stock? There must be some reason user A. is getting one result and B. another - if it's not faulty hardware then it's faulty software. However, you said you factory reset. The last thing I can possibly think of is that you modded and it's messed with the system somehow or there really is some faulty hardware.
I'm running 4.010.10, I came from 4.010.08. I've been running stock from day 1. I've never rooted, nor installed any ROMs or mods (wifi supplicant, etc.) from XDA and as I mentioned, no trouble at all.
johnnyb82 said:
...What worked for me was to set the wifi to turn off when the screen was off. Now, if I am still downloading things it stays connected with the screen off. Also, I still hear the notification sound when an email comes in even if the tablet has the screen off and nothing running...
Click to expand...
Click to collapse
So what you're saying is you have wifi set to go OFF when the screen is off but it stays ON?
And that's not something anyone considers to be a bug (regardless of if it helped your wifi stay on or not)???
I managed to snag a lapdock from amazon for 200$, got it today, and man has it been a headache.
it seems that both alien and cherrypie have put so much into their webtop over hdmi hacks that they caused a few issues with the lapdock.
Personally, every time I try to use it, the phone doesnt recognize it as a lapdock, it recognizes it as a monitor and keyboard. Touchpad doesnt work, USB seems inop, totally annoying, I'm still trying to figure out a way to revert to stock deodexed files so I can get around this.
I'm also finding that I can't for the life of me fix webtop2sd. multiple roms, busybox downloads and placement, all of it seems to just elude me. I had it working once on alien #4, then I couldn't boot past bootloader after applying the volume mod, which somehow is listed as a "dock fix" on the rom thread, but only caused more incompatibility problems (purely refused to go into webtop)
I really hate the thought of reverting to a stock rom, hell, i consider it not an option, has anyone else encountered this issue? I feel like the lapdock hasnt spread enough for people to voice these issues.
Edit- Testing a few more things to make sure the roms and hacks are at fault, seems like the smart thing to do before going through the trouble of making zip packages to revert stuff
will post findings
Edit 2 - So I went through the trouble of making HDMI hack reverting zips for CWM (PM me if you'd like it just in case) but it seems like things just work on cherrypie now, no modding, nothing
Edit 3 - And now webtop2sd works again too.....what in hell....okay then
in case anyone else has similar issues and wants to try to redo what i did
wipe data -> wipe dalvik -> fruit cake att 2.3 -> reboot and use -> cherrypie
I have absolutely no idea what is going on with this. Currently when i try and turn on bluetooth it will sit and think for about 15 seconds like it's turning the radio on, then just fail and go back to thinking the radio is off. When i try to activate wifi it does the same, but says error.
I am running neutrino 2.7, but was seeing this on 2.6 as well. I did a full wipe and re-install last night, and installed apps one by one to try and find what broke it. I thought i had identified google voice as the culprit, but with that uninstalled and almost no other apps installed bluetooth and wifi broke this morning.
if i flash a radio it will fix it maybe once in 5 tries, and only for about 20 minutes or so, then it fails again.
this started last week around the same time AT&T started throttling my data for going over 3.5gigs. No idea if that is related.
any ideas, things to try, etc?
Make a backup and flash the stock rom and stock radio for that rom, see if it still happens. I've read of others having wifi and bluetooth problems, you may try reading in those threads.
Sent from my MB860 using xda premium
Problem!!
you resolved the problem??? any idea???
nope, not yet. I've tried other kernels, and other versions of neutrino (was on EE, tried GT), nothing. Even with a clean wipe it's being dumb.
Downloaded the stock AT&T rom in fruitcake form, going to try that next.
From some reading i think there might actually be some phones with a hardware defect where some soldering wears out and starts messing up the bluetooth/wifi. I'm praying that isn't my phone because i'm well out of warranty.
i have the same issue on CM9 as of yesterday. no amount of wipes or different CM9 roms helps, haven't tried any GB roms yet though.
check this thread:
http://forum.xda-developers.com/showthread.php?t=1205775&highlight=wifi+error
i've read that.
flashed stock AT&T rom today, still have problems. not amused.
backing up my data, formatting all sd cards, wiping everything and trying again.
I'm with this problem too, Im running morrisoft rom since last month and I didn't any update, change configs or flash anything before It starts, so wierd...my wifi+bluetooth was working at night them in the next day it wasn't anymore lol..
(it happened today btw)
i ill try change my rom and see what happens...
same issue on a completely clean wipe. pretty sure at this point it's a hardware issue and not software.
I'll try the "fix" posted in the other threat at some point.
clean wipe has no effect. Wifi will sporadically work, bluetooth won't. I'm pretty sure based on how inconsistent the issue is this is a hardware issue. Not amused at all. No warranty left on this phone, and no upgrade until october.
This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")
taylrjones said:
This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")
Click to expand...
Click to collapse
They didn't want to repair it because they knew it had been unlocked? Are we talking about motorola?
same thing happened to mine..... it was a hardware issue, had it replaced...sorry..
firstly i have tried the search function but have had no luck.
im running the last cm9 nightly build from last november and everything is working ok apart form the camcorder??
it records a bit flakey and after X amount of seconds/minutes it just mutes the recordings?
ive tried learning sign language as a temporary solution but think it would be easier for someone to point me in the direction of a fix.
thanks much
I see nobody reply. I was never on CM9, but I can tell you this. I did not do full wipe of the phone and full sbf reinstall and I had GPS issue that nobody could solve. When I did that, everything started working like it should. Maybe this could help you.
ezantera said:
I see nobody reply. I was never on CM9, but I can tell you this. I did not do full wipe of the phone and full sbf reinstall and I had GPS issue that nobody could solve. When I did that, everything started working like it should. Maybe this could help you.
Click to expand...
Click to collapse
i did everything to the book when installing (all wipes etc). its just super annoying cause its the one thing i actually use on the daily lol
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Loopy Frog said:
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Click to expand...
Click to collapse
My N4 had a broken mic out of the box brand new lol. It was the latest batch, made in October 2013
I fixed it by getting a new mic because i diagnosed it wasn't a software issue
I ended up flashing "LRX08 B15.5S" from [L][5.0] Android L-pv N4 [B15.1 updated 10-27-2014] and I also put the "91u-a9: AOSP/L" Kernel from [KERNEL] [4.4.4/CM/(L)] [Bleeding Edge] Unleashed Kernel Series [91u-a9] [10/28/2014] Thinking there might be a chance it would fix my problem bringing it to 5.0 instead of 4.4.4.
I thought it worked all day yesterday without the data cable needing to be plugged in, I ran tests all day and it worked fine. Today is a different story though. I guess the data cable creates some form of initial connection the phone needs for my mic to work, and leaving it long enough it looses that connectivity. I'm not sure.
I don't have any intentions sending the phone in to get fixed, or repaired, as I'll be upgrading my nexus soon enough. I guess at this stage my fix is too cut the very end off of an old cable and have it in my pocket for incoming and outgoing calls. Anyone else have another solution?
Best Regards.
Loopy
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I believe that's what I did in the very very beginning of the problem, however on the possibly note that I didn't I'll do that just before Nov 3rd, if the official L is update is available then. Thanks ark
Yup...
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
flashed stock. Problem still persists.