I have tried various Lollipop roms on FLO and it sounds like my speakers are blown. I went back to DU8.2 and the same thing.
I settled on Omnirom nightlies of 4.4.4 and no sound issues.
I tried both ElementalX and Glitch for Lollipop. No fix. Flashed SimpleAOSP, DU9, and a slew of others with no fix. I do comprehend the fact that Lollipop roms are still under development.
I did not have the issue on stock Lollipop from the google website.
Could this have something to do with their blobs/binaries?
Or am I missing something?
Thanks
Related
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
re: 4.2.2 roms
jdsung said:
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
Click to expand...
Click to collapse
That's an easy questiion, like I have been saying all along none of the cm10/aosp/aokp or ported roms
are ready for prime time, they are good for those who want to experiment with a few features not found
in stock t999 4.1.1 Touchwiz Jellybean roms. None of the cm/aosp/aokp roms even have the Wifi calling feature.
That's why after trying all the aosp/aokp/CM and ported roms I have come to the conclusion above.
So unless you like experimentation only flash T-Mobile T999 stock 4.1.1 Touchwiz Jellybean roms
or any of the custom roms which are based on T-Mobile T999 Touchwiz v4.1.1 Jellybean stock rom.
The best custom T999 T-Mobile Touchwiz Jellybean 4.1.1 based rom in my opinion
is the Wicked v9.1 custom rom, check it out you won't be disappointed.
Good Luck!
You could always try to flash your 4.2.2 Tim of choose and choose not to restore Google backup, Google backs up settings. If it works without setting up your account then go from there.
Sent from my SGH-T999 using xda app-developers app
Well from what I've been reading the 4.4.2 update came a big jump in audio for the nexus 5. But what I'm curious about is that I think the drivers for Viper Audio are conflicting somehow with the 4.4.2 update. I've done every possible thing I can think of,read of, etc etc. I've had success on 4.4 and 4.4.1 ROMs without fail installing the viper drivers but 4.4.2 says no no fool I don't like those. I'm using the latest 2.3.1.5 version of viper but no success with either 2.3.1.3 or 2.3.1.5. If anybody has had success with it by messing with the viper settings please help! :crying:
x.0ni.x said:
Well from what I've been reading the 4.4.2 update came a big jump in audio for the nexus 5. But what I'm curious about is that I think the drivers for Viper Audio are conflicting somehow with the 4.4.2 update. I've done every possible thing I can think of,read of, etc etc. I've had success on 4.4 and 4.4.1 ROMs without fail installing the viper drivers but 4.4.2 says no no fool I don't like those. I'm using the latest 2.3.1.5 version of viper but no success with either 2.3.1.3 or 2.3.1.5. If anybody has had success with it by messing with the viper settings please help! :crying:
Click to expand...
Click to collapse
Viper seems to be doing fine on 4.4.2 and I use Spotify and Google Play Music. Maybe your S2 doesn't like you?
i tried Cyanogenmod 11 nightly, , CM11 Linaro and SlimKat 4.4, and everywhere i have the same problem, only the front camera works. in stock roms like LRS, everything is fine, as expected. i tried different camera apps, but the problem remains the same, the camera doesn't work, only the front camera does. there isn't even a button in the camera app to switch between back and front camera, as if i only have one.
is there a fix or a workaround for this? not having a camera is a dealbraker for me, but i really don't want to stay stock. i flashed multiple times, used different gapps versions, did factory resets and reboots, nothing seems to help, the stock version was 4.4.2 v50020. anyone else experiencing such problems?
WEIRD!!!!
I'm having the same problem. My Gpad came from the factory with 4.4.2 installed. and when I try to put any custon rom, this problem is with the camera. any solution? :crying:
Yes. The same problem. Maybe cyanogen team (Bug: CYAN-4444) can find solution.
same problem here, tryied every rom and kernel and nothing. only stock firmware back camera works.. can anyone help us?
read in one SlimKat thread that using the Google Camera from play store would work with all the custom roms, since it uses a different API than other apps.
Haven't tried myself, but you can give it a try
Google camera doesn't work better for me. This is very annoying
effraie said:
Google camera doesn't work better for me. This is very annoying
Click to expand...
Click to collapse
For me neither. Also in the latest builds where infected said the back camera should be fixed, it doesn't work for me.
The problem with camera is present on not only custom roms. It exists on official v50010a firmwares after downgrade. Possibly it's driver\kernel problem, which is caused distinction in camera's modules. Maybe new revisions of the G Pad use some other modules, than older ones.
Any directions to fix it ?
IMHO, they need to get out driver for camera from official 20a. But how it function with kernel, this is the big question that must be solved.
So, there is nothing i can do, except waiting somebody solving that issue ? No mistake on my side ?
Having no back camera is really not a problem to me, but i can't stand having something misconfigured...
Both cameras working for me slimkat 6.2
Not for me....
Some have problem... most don't, something different about your gpads ?
Sent from my Kin[G]_Pad ™
Rear camera not working too
Hi
For me the rear camera won't work too.
My G Pad is a V50020d with stock 4.4.2. I installed the Cyanogenmod 11 via CWM Philz Touch.
Same problem here
tried cm11, paranoid e now um on mahdi, no back camera on any of 3 roms
I haven't tested other custom roms, but Infected's CM11 M9 won't fix the back camera for me.
My G Pad (stock V50020a) is made in Brazil, there might be something to do with this driver or component-wise.
There is a source codes of the last firmware and kernel for the g pad on the lge site.
Maybe, it will help developers to add support for our camera module in the cyan kernel.
Same problem here... Spanish lg g pad 1 month of use
Did the G3 even get 4.4.4 ?
Just searched for the term 4.4.4 but not a lot showed up in the results. Not had this G3 long, still not sure I even like it after coming from a Nexus 4 with 2 years trouble-free usage, the lag from this G3 occasionally annoys me and I feel like going back to my Nexus 4.
This is, I value xposed framework, app compatibility, and stability more than just having the latest thing. Lollipop isn't bad, chupa chups(?) Is great but not enough to give up the above.
Another thing, I still don't have any updates showing up in software updates, on 4.4.2 UK 855 G3 on 3 network, only LG ones.
So, are there any decent 4.4.4 ROMs? And would a dirty flash over 4.4.2 be OK?
Many thanks for any help.
John.
There are, as of now, no stock or custom 4.4.4 based ROMs. LG skipped 4.4.4 and went from 4.2.2(or 4.4.2, please correct me if I'm wrong)->5.0.
Went straight from 4.4.2 to 5.0
Theres the cloudyg3 rom (the previous version of the rom is kitkat) but with no further development since it went to lollipop.
You have to go with the upgrades ,i dont like myself LL but we have to move forward
I appreciate that we cannot dwell in the past but Lollipop on G3 just ain't ready for primetime, and could be many updates away from getting there. Kitkit runs better than most admit, has the best compatibility, best battery life, and has xposed.
With some tweaks, scripts installed such as the mem script, and lots of bloat removed or disabled, KitKat runs really well. And I believe there can be more done to it, more tweaks, more bloat disabled - I still see quite a few apps running that could possibly be removed.
ISSUE: Rotation not locking in Landscape mode
My device was rooted and I tried whatever Lollipop 5.1 ROMs are available even with different Kernels. Still I wasn't able to fix the rotation not locking in Landscape mode. I asked many people for help but sadly nothing helped. Everybody said this is a model specific issue. Now finally I'm back in the stock ROM [Android version: 4.4.2/NO ROOT/STOCK RECOVERY]. I don’t know what affected that issue, Bootloader? Kernel? But I deliberately want to stay on the stock 5.1 experience.
Somebody please look into this issue.
Thanks
Have you tried Stock 5.0.2?
And it COULD be an app preventing the tablet from staying in landscape mode. Did you install anything when trying the 5.1 custom roms?
And just to be sure: With Stock KitKat everything works as it should?
edisso10018 said:
Have you tried Stock 5.0.2?
And it COULD be an app preventing the tablet from staying in landscape mode. Did you install anything when trying the 5.1 custom roms?
And just to be sure: With Stock KitKat everything works as it should?
Click to expand...
Click to collapse
I was using actually Candy5 earlier version which was based on the 5.0.2. But when 5.1 is available who wants to go back ;P
Apps are not causing this issue because I tried flashing just the CM12.1 even without gapps, this issue persists. I doubt this is related to modem.img since it's a device specific issue.
Any ideas to fix this?
It would be interesting to test if the issue persists with stock 5.0.2 on your tablet. If it is, it could be a hardware defect. Maybe the gyroscope is faulty.
edisso10018 said:
It would be interesting to test if the issue persists with stock 5.0.2 on your tablet. If it is, it could be a hardware defect. Maybe the gyroscope is faulty.
Click to expand...
Click to collapse
For your information I was using this ROM(aosp_v500-ota-eng.adrianomartins_5.1.1_r1_20150422) for a while and the rotation was perfect even from the first boot itself. But I was not satisfied with the battery life of this ROM. So I decided to try any other 5.1 ROMS like CM12 or Candy5. But they all have this issue. So not a hardware issue confirmed.
@Sarun said:
For your information I was using this ROM(aosp_v500-ota-eng.adrianomartins_5.1.1_r1_20150422) for a while and the rotation was perfect even from the first boot itself. But I was not satisfied with the battery life of this ROM. So I decided to try any other 5.1 ROMS like CM12 or Candy5. But they all have this issue. So not a hardware issue confirmed.
Click to expand...
Click to collapse
So it seems to be a problem with CM based roms (as Candy 5). I'm out now...
Hey! I have the same issue on CM 12.1. I would LOVE a fix for his because I use landscape rotation lock a lot. The only help I can give is I noticed it started on 5.1. On 5.0, it was fine.
mach01 said:
Hey! I have the same issue on CM 12.1. I would LOVE a fix for his because I use landscape rotation lock a lot. The only help I can give is I noticed it started on 5.1. On 5.0, it was fine.
Click to expand...
Click to collapse
I have reported this issue in many threads they all either ignore this issue or fail in solving this.
Yeah it's an annoyance but not one big enough to sway me from CM. I really need it fixed though.