Need to know for a little experiment I wanna try.
Sent from my SGH-I927 using xda premium
Pacman or cm10 both by dman who is in fact da man !
Sent from my SGH-I927 using xda app-developers app
They seem like there's too many problems with them.
Sent from my SGH-I927 using xda premium
There's a thread reporting current bugs.
Those bugs are still important but I can say that these ROMs already work very good.
Thanks to dman for original work and, lately, to spyke555 and kick who are really doing an excellent job (development was almost dead before they committed and i'm very thankful to them for what they are doing).
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
spitfire2425 said:
I've seen the current bug thread but it's for 4.2.2 I need 4.1.2
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
He already answered your question, the 4.1.2 weren't ever completed, they were abandoned... hence why the issues in those roms are still present.
Install PACRom 18.2 and then apply the fixes for keyboard etc. I think the fixes are in the litekernel thread. Put on the latest litekernel for 4.1 keyboard fix, lights fix and you'll have the best working 4.1.2.
Note - skype and bluetooth headset still won't work, pretty sure the camera issue with rotation is still present. I ran pacrom 18.2 for MONTHS without any issue except those listed and the wake lag.
I was trying to port something, not use it as a rom.
Sent from my SGH-I927 using xda premium
GPS and other features
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
myxoh said:
Uhm is any STABLE release with:
GPS Working (most important)
MUSIC Working
Skype Working
Camera Working
Google Now Working (this seems to be an issue from all custom Roms)
Since I've seen most these features working but none on the same ROM all together
Click to expand...
Click to collapse
Not for version 4.1.2 (jellybean)
Only ICS 4.0.xxx ...
****, somebody needs to make a sticky for the most current stable rom .. this question keeps coming up over and over and over in every forum and many threads.
myxoh said:
GPS Working (most important)
Click to expand...
Click to collapse
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
MUSIC Working
Click to expand...
Click to collapse
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype Working
Click to expand...
Click to collapse
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Camera Working
Click to expand...
Click to collapse
Current CM10.1 and derivatives have a fully working camera.
Google Now Working (this seems to be an issue from all custom Roms)
Click to expand...
Click to collapse
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Thanks for the reply
roothorick said:
GPS has always worked. Some of the technical data returned is invalid/bogus but Google Maps/Navigation is completely unaffected.
Again, it's always worked, so long as you don't have an app trying to record audio at the same time.
Skype works for text messages, but received audio in calls is corrupt. The core of the issue is audio playback breaks when an app opens the microphone. (Ironically, the microphone itself actually works fine, i.e. voice recognition has messed up audio cues but it does process what you say correctly.) Current hypothesis is it's a driver issue. Research is ongoing. This is a longstanding issue going all the way back to our very first JB kernels.
Current CM10.1 and derivatives have a fully working camera.
This is actually a known problem with Google Now itself, it depends on an instruction set the Tegra 2 doesn't have. The Galaxy R and the Galaxy Note 10.1 have the same problem, on ALL Jellybean ROMs, even official. Bug Google, not us.
There is a workaround: downgrade GNow to a working version (possibly by flashing old gapps), then disable "Hotword detection" in settings. Once that is turned off you can upgrade to the latest and it will still work.
Click to expand...
Click to collapse
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
myxoh said:
Thanks for the reply but:
1) GPS was not locking for me until I changed the gps.conf file in MOST of the ROMs I've tested.
2) Music didn't work on one rom I tested (now and then the music player started lagging and it automatically stopped every few seconds for a few milliseconds)
3)Thanks for the Skype reply; I was hoping there was some version with this fixed but evidentely not.
4)Camera flips orientation in all the roms I've tested. HDR just worked in 1 of them. Camera actually crashed from time to time in one of them.
5)Oh, sad about the Google Now fact. It's actually one of the main reasons I wanted JB
The skype thing Can't be a hardware issue since I've used skype several times before rooting my device. The issue you are talking about happens on google voice sometimes; therefore I'm guessing you're right on thinking that the problem is on the driver.
I'm very interested in ROM building since I'm an app developer for android and a C++ programmer; yet I've been too lazy to check how it worked. Are the drivers we are using open source? or are we just messing with the conf files trying to get things fixed?
Click to expand...
Click to collapse
hi,
thread how to compile from source:
http://forum.xda-developers.com/showthread.php?t=2071542
AFAIK drivers are not open source if they were there wouldn't be so much problems with them. They are ported from other devices similar hw but with code for them.
any news about JB and bluetooth headset issue?
this is the only thing that's been holding me back so far
myxoh said:
Uhm is any STABLE release with:
(...)
Click to expand...
Click to collapse
Where to find this "Uhm"? It was not listed here: http://forum.xda-developers.com/showthread.php?t=1621350
Related
I've been having this issue since the begining of my use with XAndroid 2.2 froyo...
When an incoming call comes in the caller is unable to hear my speak...and at times I am unable to place out going calls
How do I fix it?
Sent from my MSM using XDA App
You're using a very old kernel aren't you...
Update it please. GlemSom's site (the autobuild service) is unfortunately behind, but there's a couple of testing kernels floating around if you're brave.
With that said, I believe the "newest" on GlemSom's site has this bug fixed... AFAIK it was fixed quite a while ago!
or press incall your volume switch one time down then one time up,... i figured this out when i testing that old kernel
You guys may give this thread a shot: http://forum.xda-developers.com/showthread.php?t=893207
arrrghhh said:
You're using a very old kernel aren't you...
Update it please. GlemSom's site (the autobuild service) is unfortunately behind, but there's a couple of testing kernels floating around if you're brave.
With that said, I believe the "newest" on GlemSom's site has this bug fixed... AFAIK it was fixed quite a while ago!
Click to expand...
Click to collapse
Any chance you could post a link to the page you're referring to? I just installed the latest blazin cab off of the project android site last night and I'm having this same issue constantly. Any help appreciated as I love android, but can't do much without this fix.
Autobuild
It's in the FAQ, and on the first page of the thread where you probably went to the download link from...
Try these Kernal and modules http://forum.xda-developers.com/showthread.php?t=869992
Has anyone tried the newer kernals a GSM phone? I have had a lot of difficulty with this problem in the Froyo builds however Eclair works good on my Tilt 2 GSM.
jfarm03s said:
Has anyone tried the newer kernals a GSM phone? I have had a lot of difficulty with this problem in the Froyo builds however Eclair works good on my Tilt 2 GSM.
Click to expand...
Click to collapse
You're mixing terms here... the kernel is different from Eclair/Froyo - those are system images, the kernel is a completely separate piece. In theory you can run these kernels on Eclair no problemo...
Heck if Eclair works for ya, use it! Pretty sure this same problem would exist in that system with these new kernels...
But perhaps not - maybe you guys are all running into that system_server bug that's causing call issues..? Not sure.
Oh, and just an FYI... the majority of the developers have GSM devices
emt2rescue said:
I've been having this issue since the begining of my use with XAndroid 2.2 froyo...
When an incoming call comes in the caller is unable to hear my speak...and at times I am unable to place out going calls
How do I fix it?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
try using froyo X, calling and texting works 100% on my rhod-100 for me, also on some devices the camera works..
http://forum.xda-developers.com/showthread.php?t=904918
Hey guys, ive been using cm9 since Alpha 8 has come out, after reading the cm9 and cm10 official topics and im just confused.
Currently I know Modpunk has stopped working on CM9, and the camera is abit laggy and the video doesnt work etc
So what exactly works and doesnt work on cm10? As far as I know everything works except video because of the omx drivers, so tethering etc works, am I right? Please correct me.
CM10 alpha 1 came out last night, so is modpunk stopping work on CM10 or carrying on?
and, what would you recommend, staying on cm9 or going to cm10? Which one works better/is more stable
Also if I went about upgrading to cm10 would I just flash over my cm9 Installation, Thanks.
Im sure alot of people are wondering the same thing as me. I would extremely appreciate it if you guys could put my mind at rest.
I'm wondering the same thing. As far as I can see from CM10 threads, everything is working same as CM9.
BTW, modpunk stopped working on CM9/CM10 but you can download latest CM10 build from dudeman's thread.
first aidingM
aswerth said:
I'm wondering the same thing. As far as I can see from CM10 threads, everything is working same as CM9.
BTW, modpunk stopped working on CM9/CM10 but you can download latest CM10 build from dudeman's thread.
Click to expand...
Click to collapse
Are you sure modpunk has stopped? Alpha 1 was realeased yesterday, but I think that is his last work for wildfire s.
And does that mean GPS isnt working, ive seen that camera is fully working on cm10 now, if thats so then im going to upgrade if GPS is working also.:fingers-crossed:
I read that he bought a new phone. But, I'm not 100% sure, I didn't see any post from modpunk about that.
GPS is working on CM9 if you're lucky. I've tried Google Maps several times, but it takes so much time to get GPS signal. I'm not sure if it's same on CM10 too. I'll install CM10 tomorrow to check it.
Camera working partially on CM9/CM10. You can take photos perfectly but you can't record videos.
Okay so I installed CM10 Alpha 1 yesterday, As far as it goes these were all the bugs I faced with it:
1. Camera sucks balls. So does video.
2. statusbar a little laggy (Won't notice much)
3. When phone is in low brightness mode, the power button won't turn on the screen... (Workaround: enable wake from volume button and press them)
4. GPS doesn't work well.
5. Music playback was a little laggy, no matter what music player I used. IDK if it's ROM's fault or not.
6. Sometimes random things crash. (You wont even notice)
7. Calculator crashes.
8. OFC video playback oughta suck.
On CM9:
1. Camera works fine but a little laggy.
2. Video playback is ****ty.
3. GPS (I use AGPS patch so don't notice it often)
I guess that's it. I'm gonna stay with cm10 for a little longer and see whats in future.
Also if you wanna stay or move on depends on your own preferences, how much are you affected by these bugs?
sukhjit321 said:
Okay so I installed CM10 Alpha 1 yesterday, As far as it goes these were all the bugs I faced with it:
1. Camera sucks balls. So does video.
2. statusbar a little laggy (Won't notice much)
3. When phone is in low brightness mode, the power button won't turn on the screen... (Workaround: enable wake from volume button and press them)
4. GPS doesn't work well.
5. Music playback was a little laggy, no matter what music player I used. IDK if it's ROM's fault or not.
6. Sometimes random things crash. (You wont even notice)
7. Calculator crashes.
8. OFC video playback oughta suck.
On CM9:
1. Camera works fine but a little laggy.
2. Video playback is ****ty.
3. GPS (I use AGPS patch so don't notice it often)
I guess that's it. I'm gonna stay with cm10 for a little longer and see whats in future.
Also if you wanna stay or move on depends on your own preferences, how much are you affected by these bugs?
Click to expand...
Click to collapse
Hmm, from what youve said im going to stick to CM9, would you be able to help me with that GPS patch? Its really bugging me and I need my GPS.
YaqubYahya said:
Hmm, from what youve said im going to stick to CM9, would you be able to help me with that GPS patch? Its really bugging me and I need my GPS.
Click to expand...
Click to collapse
Here's the link. : http://forum.xda-developers.com/showthread.php?p=21445309
Enjoy.
sukhjit321 said:
Here's the link. : http://forum.xda-developers.com/showthread.php?p=21445309
Enjoy.
Click to expand...
Click to collapse
Thanked.
Thankyou
Hi guys, I'm new here.
I just installed CM10 on my Wildfire S (marvel) last night, and I'm quite pleased how it works.
I didn't try GPS and Bluetooth, so I don't know if they are working correctly, other things (except camera, of course) are quite good.
I wanted to ask about camera issue. Can someone point me where I could get more info about it? I don't quite understand why it isn't working properly. I thought maybe to take a look at it, if I manage to find the some spare time.
witchdoc_nix said:
Hi guys, I'm new here.
I just installed CM10 on my Wildfire S (marvel) last night, and I'm quite pleased how it works.
I didn't try GPS and Bluetooth, so I don't know if they are working correctly, other things (except camera, of course) are quite good.
I wanted to ask about camera issue. Can someone point me where I could get more info about it? I don't quite understand why it isn't working properly. I thought maybe to take a look at it, if I manage to find the some spare time.
Click to expand...
Click to collapse
Go and head over to the development forums in the wildfire s forums, the camera takes pictures fine but the preview has some artifacts, Qualcomm won't release the OMX drivers for video recording, so video recording MAY never work, but there is a person working on it.
YaqubYahya said:
Go and head over to the development forums in the wildfire s forums, the camera takes pictures fine but the preview has some artifacts, Qualcomm won't release the OMX drivers for video recording, so video recording MAY never work, but there is a person working on it.
Click to expand...
Click to collapse
Hmm, that really is a rough one. I thought that there was some minor problem with it.
Thanks for the answer, I'll head to development forums to see what I can find out.
Live in goo manager. Just thought I'd let you all know!
Just installed. Running smoothly, none of the issues I experienced in RC2 so far. Great work.
RC2 Stabel and Bluetooth audio
&Son said:
Just installed. Running smoothly, none of the issues I experienced in RC2 so far. Great work.
Click to expand...
Click to collapse
Anyone confirmed if the Bluetooth audio distortion on calls via in car systems has been fixed in this release?
mm0wkj said:
Anyone confirmed if the Bluetooth audio distortion on calls via in car systems has been fixed in this release?
Click to expand...
Click to collapse
Its a stable version so it should work. I can't answer because I hate BT lol But give it a shot. I'm also using the latest AK CYLON kernel. His work is usually flawless
Sent from my Galaxy Nexus using Tapatalk 2
heath2805 said:
Its a stable version so it should work. I can't answer because I hate BT lol But give it a shot. I'm also using the latest AK CYLON kernel. His work is usually flawless
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks Heath. Was a bit reluctant to reflash as I've spent a few days tweaking my RC1 build and have a shed load of apps loaded for my boys to play with..
I may wait until someone posts a positive on hands free before rebuilding again.
I don't use Bluetooth and can't confirm it working, but this ROM is just awesome!
It has all the features you will need and it runs really smooth. I can really recommend it. Only thing not working for me is sphere in camera - not a big deal though...
hudl said:
I don't use Bluetooth and can't confirm it working, but this ROM is just awesome!
It has all the features you will need and it runs really smooth. I can really recommend it. Only thing not working for me is sphere in camera - not a big deal though...
Click to expand...
Click to collapse
I don't have sphere option in mine. Wouldn't that depend on what gapps you used? I used the latest in goo 20130301
Sent from my Galaxy Nexus using Tapatalk 2
heath2805 said:
I don't have sphere option in mine. Wouldn't that depend on what gapps you used? I used the latest in goo 20130301
Click to expand...
Click to collapse
I too use gapps 20130301 from goo and have the sphere option. But when aligning the fist image, the "gallery" closes. I had it working on another ROM, but quality of sphere is really bad when shooting in a room (alignment), so I don't miss it. Maybe/hopefully Google improves it in the next version.
EDIT: Indeed the camera gives me more problems than just a buggy sphere... NO images are taken at all! Not even with a 3rd party camera app!
I think this is a major issue. I read that it should be fixed in Android 4.2.2 but apperently this is not the case. Interestingly I had it working in other 4.2.2 ROMs so maybe there is an issue with this LiquidSmooth release...
Anyone else has troubles with the camera?
hudl said:
I too use gapps 20130301 from goo and have the sphere option. But when aligning the fist image, the "gallery" closes. I had it working on another ROM, but quality of sphere is really bad when shooting in a room (alignment), so I don't miss it. Maybe/hopefully Google improves it in the next version.
EDIT: Indeed the camera gives me more problems than just a buggy sphere... NO images are taken at all! Not even with a 3rd party camera app!
I think this is a major issue. I read that it should be fixed in Android 4.2.2 but apperently this is not the case. Interestingly I had it working in other 4.2.2 ROMs so maybe there is an issue with this LiquidSmooth release...
Anyone else has troubles with the camera?
Click to expand...
Click to collapse
Mine is working just fine. Maybe try and redownload gapps and see if that's the issue. I'm not sure if the new gapps has an effect on camera apk though. If all else fails, you could always redownload the ROM and get a clean install.
Edit: Alright just checked and sphere is working here flawlessly.
Sent from my Galaxy Nexus using Tapatalk 2
BT handsfree still buggy
mm0wkj said:
Thanks Heath. Was a bit reluctant to reflash as I've spent a few days tweaking my RC1 build and have a shed load of apps loaded for my boys to play with..
I may wait until someone posts a positive on hands free before rebuilding again.
Click to expand...
Click to collapse
Bit the bullet and went for the update and tried Bluetooth handsfree. Still not working.:crying:
Connects fine, transfers contacts fine but audio during calls (at any volume level) is distorted and robotic (both ways). Even when connected there is intermittent bursts of quiet and distorted audio through the handset speaker which sounds like the connection is trying to drop out. HTC one, Sony Xperia, HTC Cha Cha, HTC Desire all work perfectly on the same car kit.
Tried all devices on a Saab (2008) Ford (2012) and Renault (2011) all the same. Other devices connect and audio is perfect, S3 distorted.
Anyone recommend a Kernel that they have confirmed BT functionality on in car systems?
heath2805 said:
Mine is working just fine. Maybe try and redownload gapps and see if that's the issue. I'm not sure if the new gapps has an effect on camera apk though. If all else fails, you could always redownload the ROM and get a clean install.
Edit: Alright just checked and sphere is working here flawlessly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for telling! I always do a full wipe when flashing ROMs but then I realised that other ROMs also had the same problem "suddenly". So I tried it once more with reverting to stock, re-rooting,... and now also deleted my backup of "Android" folder that I otherwise always restore to keep some settings. What should I say? It works again! Smooth and flawless (including sphere)! :victory:
mm0wkj said:
Tried all devices on a Saab (2008) Ford (2012) and Renault (2011) all the same. Other devices connect and audio is perfect, S3 distorted.
Anyone recommend a Kernel that they have confirmed BT functionality on in car systems?
Click to expand...
Click to collapse
Afaik Google implemented its own Bluetooth stack, which obviously is not that great...
"Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability."
http://developer.android.com/about/versions/jelly-bean.html
I'm afraid you will have to wait for Android 5 or other fixes... (can be wrong though. I'm not so firm with this matter)
I noticed many people here having BT issues. Not sure if this helps for calling but definitely helps for audio. Check it out.
http://forum.xda-developers.com/showthread.php?p=38973705
Sent from my Galaxy Nexus using Tapatalk 2
Bump for an awesome ROM!!!
Finally a stable release. Wish they had an "official" Galaxy nexus thread though.
Sent via Tapatalk on LiquidSmooth Galaxy Nexus
GherkinSavorus said:
Finally a stable release. Wish they had an "official" Galaxy nexus thread though.
Sent via Tapatalk on LiquidSmooth Galaxy Nexus
Click to expand...
Click to collapse
They had, but it's closed now. Don't know why.
Sent from my Galaxy Nexus using Tapatalk 2
But...
I thought TeamLiquid broke up into CarbonJB. Is Liquid coming back!?
Liquidsmooth jb v2.2 official is up in goo...
Sent from my Galaxy Nexus using Tapatalk 2
Not for toro plus :banghead:
Sent from my Galaxy Nexus using Tapatalk 2
Being that I'm a noob (<10 posts), I can't post this in the actual ROM thread (mods, please move if you deem it appropriate).
I wanted to ask if there was a way in Google Edition 4.3 to change the clock settings to *NOT* display the hour in bold font?
Is that functionality available and I'm missing it in the settings?
Thanks yeahmann for putting that together and to the entire XDA community for all the hard work!.
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
piotreks4 said:
Being that I'm a noob (<10 posts), I can't post this in the actual ROM thread (mods, please move if you deem it appropriate).
I wanted to ask if there was a way in Google Edition 4.3 to change the clock settings to *NOT* display the hour in bold font?
Is that functionality available and I'm missing it in the settings?
Thanks yeahmann for putting that together and to the entire XDA community for all the hard work!.
Click to expand...
Click to collapse
As far as I know you can't change the look and feel of the widget in 4.3, however you can always install Cyanogenmod cLock widget where you can customize it. Hope this helps.
Sent from my GT-I9505G using xda app-developers app
a103 said:
As far as I know you can't change the look and feel of the widget in 4.3, however you can always install Cyanogenmod cLock widget where you can customize it. Hope this helps.
Click to expand...
Click to collapse
It does help -- thank you.
I actually ended up flashing CM-10.2 because of the availability of better config options and am so far loving it.
Thanks again and best wishes!
P :good:
piotreks4 said:
It does help -- thank you.
I actually ended up flashing CM-10.2 because of the availability of better config options and am so far loving it.
Thanks again and best wishes!
P :good:
Click to expand...
Click to collapse
Whenever you get a chance can you please let me know how's CM 10.2 working for you so far? I mean can that be used as a daily driver with major things (GPS, Bluetooth, NFL, camera etc) working without any issues. If so please let me know which nightly did you flash.
Thanks.
Sent from my GT-I9505G using xda app-developers app
a103 said:
Whenever you get a chance can you please let me know how's CM 10.2 working for you so far? I mean can that be used as a daily driver with major things (GPS, Bluetooth, NFL, camera etc) working without any issues. If so please let me know which nightly did you flash
Click to expand...
Click to collapse
So far, CM 10.2 is rock-solid. I flashed The Sept 5 Nightly. Reason being - Friday gives me 2 days if something doesn't work.
I tried AOKP (too many options for me -- never thought I'd say that) and both Virgin and 'stock' GE (4.3) ROMs (a bit too stock for me).
I have so far set up email (GMail and Work using K-9 + Invitation Processor) and customized some options/appearance (cLock is da-shizznit). The camera works perfectly. I have not set up Bluetooth and not used GPS, yet, but will try both tomorrow on my way to/from work. One thing that I still need to figure out is the file-system layout inside Android (i.e. /storage/0 vs. /storage/legacy, etc...) as I'm apparently using 7.4GB out of 9.6GB available. This is probably because the stock T-Mo version left most of its guts behind and/or I incorrectly cleaned the device after having flashed all the ROMs.
One thing that I've noticed (with all the ROMs, except stock T-Mo) was that when you press the power button to lock/shut-off the screen, it ends up shutting off like an old-school TV. With the stock version, it would go dark seamlessly.
Regardless, I really enjoy having this phone now that I flashed CM on it. The fact that they provide an 'update-CM' option directly inside the settings is awesome in its own right. I'll update this thread once I give GPS and BT a run (can't promise I'll run TV apps on it, though -- that's not my cup-o-tea).
Best!
if you find certain things to be a bit buggy on CM, give Virgin Rom another try. the hardware elements of the phone work flawlessly. in an ideal world, someone would use Virgin Rom as a base and "Cyanogenize" it so that more things were customizable, such as Quick Setting toggles. CM is great, but the nightlies don't have the stability that the GE Roms have, obviously.
Thanks for your inputs...I guess back up of your old Roms may be eating up your internal space (if you have backed them up )...the old tv animation is the crt animation which Google introduced in ICS 4.0
a103 said:
Thanks for your inputs...I guess back up of your old Roms may be eating up your internal space (if you have backed them up )...the old tv animation is the crt animation which Google introduced in ICS 4.0
Click to expand...
Click to collapse
Aaah! Good to know (about the TV animation).
I haven't backed up my old ROMs, but I'll definitely investigate space usage once I find some time.
Tested GPS and BT this morning: played a few songs over the car radio streaming over BT - awesome.
GPS is working good, too. I get a lock within 10 seconds of starting any app requiring GPS.
Thanks to all!
piotreks4 said:
Aaah! Good to know (about the TV animation).
I haven't backed up my old ROMs, but I'll definitely investigate space usage once I find some time.
Tested GPS and BT this morning: played a few songs over the car radio streaming over BT - awesome.
GPS is working good, too. I get a lock within 10 seconds of starting any app requiring GPS.
Thanks to all!
Click to expand...
Click to collapse
Even I flashed the RC2 last night. Using it for a few hours only, but it's rock solid as you mentioned.
Sent from my SGH-M919 using xda app-developers app
Are there any known 4.3 or 4.4 ROMs with working phone mic?
I've used CM 10.2 Stable (4.3) and Carbon Rom (4.4.2). Both work great, the only issue is that the headset is not usable for calls (low mic output). My solution for now is using the earbud/mic, but I'm curious to know if anyone has made progress on this. Aside from this, the various ROMs are near perfect for my needs.
I'm not very knowledgeable on the details of writing ROMs, but would any type of source code release from LG help developers solve this? Curious to know what the main hurdles are for the devs and what tools they need.
Thanks.
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Neroga said:
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
markusrussell225 said:
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
Click to expand...
Click to collapse
Still no luck on a solid working phone microphone (low volume on other end). And the search continues.
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
markusrussell225 said:
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
Click to expand...
Click to collapse
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
ja.andro said:
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ask because this is a problem has existed on all known roms since 4.3.1 for the E980 on ATT. Never been able to get a straight answer anywhere so I figure I would generically post it. I have reached out to some devs but not luck.
Any success on your searching?
thureos said:
Any success on your searching?
Click to expand...
Click to collapse
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
markusrussell225 said:
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
Click to expand...
Click to collapse
I saw that solution but I went back to rooted and debloated stock, I am very pleased with speed and stability.
Thanks
i've made the edits suggested on that post and still get the same issue...i dont remember having this issue before but i thnk youre right and the previous roms werent 4.4...oh well i live on the phone for work so back to stock for me. for now i guess...wanting a new phone anyways, hope we get the g pro 2 or g3 soon