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
Related
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
Hey guys, I recently found an SPH-P100 in a dumpster (score! :victory and I was quite disappointed to see that there's a terrible lack of development for these devices. As such, I've forked the newest device configuration available on github, and I'll be working to release a wider variety of ROMs and to complete hardware support as much as possible. Unfortunately, there is very little I can do to address the complete lack of 3G support, as I have no service whatsoever on my device.
Now, the ROM! This is a clean build of PAC-man 4.3 for p1c. I have removed the hardcoded verizon-specific properties and model identifiers as a first step towards proper support of both Verizon and Sprint models, but no functionality is changed from the newest CM10.1 builds.
I notice that there are not any PAC builds for p1(l|n) posted either, so if there is adequate interest I may begin builds for those devices as well.
TWRP 2.6.3.0 is the included recovery, and has full SELinux support. (Compatible with KitKat ROMs!)
Downloads
PAC 4.3.1 -- Build Date 1-17-2014:
p1c: Androidfilehost | Direct MD5: 5b817c6c94753f136e3fa7b98d6326c0
Changes:
First build of PAC for this device
You are definately right. As of right now, there are no developers working on the p1c. The last one i remember was stimp0z, and his son broke his tab. So, all the developers are now gsm based. Terenceng does have a kit kat version for the p1c. I have it on my other tab. Anyway, the developers all went to kit kat.
If i can be of help, let me know.
Sent from my SCH-I800 using xda app-developers app
Deep Nox said:
You are definately right. As of right now, there are no developers working on the p1c. The last one i remember was stimp0z, and his son broke his tab. So, all the developers are now gsm based. Terenceng does have a kit kat version for the p1c. I have it on my other tab. Anyway, the developers all went to kit kat.
If i can be of help, let me know.
Sent from my SCH-I800 using xda app-developers app
Click to expand...
Click to collapse
as of now, there's one developer working on p1c, then :3
if you have 3g service on your tabs, i could use your help... as i understand it 3g hasn't worked on any p1c model since the linux 3.0.x port?
I have 3g on one tab, but it's on galaxy cubed. My other tab is on terenceng cm11 mod. Kit kat. If you could make a zip file with a patch to flash on kit kat, i could try it out.
Sent from my SCH-I800 using xda app-developers app
ultravioletnanokitty said:
Hey guys, I recently found an SPH-P100 in a dumpster (score! :victory and I was quite disappointed to see that there's a terrible lack of development for these devices. As such, I've forked the newest device configuration available on github, and I'll be working to release a wider variety of ROMs and to complete hardware support as much as possible. Unfortunately, there is very little I can do to address the complete lack of 3G support, as I have no service whatsoever on my device.
Now, the ROM! This is a clean build of PAC-man 4.3 for p1c. I have removed the hardcoded verizon-specific properties and model identifiers as a first step towards proper support of both Verizon and Sprint models, but no functionality is changed from the newest CM10.1 builds.
I notice that there are not any PAC builds for p1(l|n) posted either, so if there is adequate interest I may begin builds for those devices as well.
TWRP 2.6.3.0 is the included recovery, and has full SELinux support. (Compatible with KitKat ROMs!)
Downloads
PAC 4.3.1 -- Build Date 1-17-2014:
p1c: Androidfilehost | Direct MD5: 5b817c6c94753f136e3fa7b98d6326c0
Changes:
First build of PAC for this device
Click to expand...
Click to collapse
Deep Nox said:
You are definately right. As of right now, there are no developers working on the p1c. The last one i remember was stimp0z, and his son broke his tab. So, all the developers are now gsm based. Terenceng does have a kit kat version for the p1c. I have it on my other tab. Anyway, the developers all went to kit kat.
If i can be of help, let me know.
Sent from my SCH-I800 using xda app-developers app
Click to expand...
Click to collapse
ultravioletnanokitty said:
as of now, there's one developer working on p1c, then :3
if you have 3g service on your tabs, i could use your help... as i understand it 3g hasn't worked on any p1c model since the linux 3.0.x port?
Click to expand...
Click to collapse
first up - great to see someone working on development for the p1c - good score finding one in the bin!
to make things clearer - i was never a developer for the p1c, my old tablet (the p1 GSM version) was broken by my youngest son recently. my work on the p1c was purely guess work / diagnosed via my testers. p1c lost it's support from it's main developer (jt1134) before kernel 3.0 was released so without a developer to work on p1c related issues, it was hit and miss all the way. both humberos and myself had it booting, but it never worked with data (though attempts were made). now due to a generous donation from one of my CDMA testers, i will soon receive a Sprint tablet he has spare so i can continue developing - which means it will be a lot easier for me to work on issues facing the CDMA variants (but will never be able to test data myself as I live in Australia, not USA).
however - the more developers that work on the p1c the better, so please keep working on whatever you can - also working on something different to CM is definitely called for as i believe the users deserve a choice between custom ROMS for their SGT7.
if you wish to have a crack at data already - shoot me a pm and i'll give you some commits to look into that may help you on your way.
I am another P1C user, the last build around here that worked for me was alrodger's 4.1.2
Terenceng's does not work on my P1C, I am on verizon and it doesn't find the carrier and never activates.
P1C is only $75 on ebay these days for refurbished, great value.
I was kinda hoping to find a kitkat build for p1c that works but none exists and doesn't seem forthcoming by anyone.
I guess I will try 4.3.1
Does this have working usb and wifi tether? That's a biggie for me.
---------- Post added at 06:43 PM ---------- Previous post was at 06:19 PM ----------
Okay I get the same failure trying to install this that I got with alrodger's final build.
using TWRP from the last kitkat flash, I wipe everything except the external sd card
then I try to install the rom and I get
assert failed: getprop("ro.product.device") ==
and a long list of devices
does that mean I have a device not in that list?
it then says
"E:Error executing updater binary in zip"
Also on 4.1.2 on my Sprint tab 7. I'm downloading and will give it a run. I dont have 3G but I'll report back after install.
terenceng is working on 4.4 and has "Coming Soon" for the PC1 but been a while. so now one is working on 4.4.
thanks ultravioletnanokitty for giving the P100 some love.
Update : ROM installed with out issue also used PAC gapps. WiFi OK camera OK feels quicker than 4.1.2. So all good for last 30 minute of use. Thanks for this rom dude nice job.
Cheers
update: okay I remembered how to get back to basics and I used heimdall to sideload cwm bootloader recovery
very fun looking rom, however it suffers from the same problem as Terenceng's:
it does not find the verizon radio/carrier and crashes when I try to manually activate it
_ck_ said:
update: okay I remembered how to get back to basics and I used heimdall to sideload cwm bootloader recovery
very fun looking rom, however it suffers from the same problem as Terenceng's:
it does not find the verizon radio/carrier and crashes when I try to manually activate it
Click to expand...
Click to collapse
Could u link to the cwm I can't seem to find it... thanks!
TaPpEd from my nOtEwOrThY N2
Hi again, as stated before I do not have 3G connection plan on my Sprint tab, So I cannot test connectivity to 3G. All other functionality I can test.
Rom working nicely, few issues with following apps:
Netflix: movie never starts playing
Youtube: video never starts playing, "There was a problem while playing, Touch to retry"
Pandora: Audio does not start
Google Play Music: Audio does not start
Timely alarm clock: The set time to ring caused app stop
Navigation in all these apps is OK just issue when playing something
Apps working well:
iHeartRadio: Working OK
Gmail: Ok
Camer: pictures OK
Ebay: seems to be working ok but have not tested placing a bid
Let me know what else I can check, weekdays have little time to test but should be able to get something done.
Let me know what you want me to check or report on?
Cheers
jrbxx7 said:
Could u link to the cwm I can't seem to find it... thanks!
TaPpEd from my nOtEwOrThY N2
Click to expand...
Click to collapse
http://cmw.cmfs.me/p1/p1c/recovery/cwm-5.0.2.7-p1c.tar
http://wiki.cyanogenmod.org/w/Install_CM_for_p1c
_ck_ said:
http://cmw.cmfs.me/p1/p1c/recovery/cwm-5.0.2.7-p1c.tar
http://wiki.cyanogenmod.org/w/Install_CM_for_p1c
Click to expand...
Click to collapse
Thanks
TaPpEd from my nOtEwOrThY N2
BelannaBi said:
Hey great job on the ROM, however I have found some bugs. Upon installing the keyboard didn't work. I installed hackers keyboard. Web videos and audio also do not seem to work either. I was also wondering if charging with USB while the device is on could be enabled.
Sent from my SCH-I800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
media playback is flat-out broken in all p1x 4.3+ roms, i believe... also, i've never found charging while the device is on to work at all... if i leave it plugged into my laptop with the screen off overnight, it gets up to 99%. if i want to fully charge it the only option i've found is to power it off and plug it in. i don't have the original samsung charger or cable, though, so that could be it. regarding the keyboard, are you using gapps? i am on my tab, and i don't have any issues... it could be an issue with the aosp keyboard, though.
I just also recently picked up one of these guys, my actual intentions for mine is to get it on verizon prepaid using a extravert as a donor phone and tethering the 3g. I seen a guy offering a service to flash them but I am a bit unsure I would rather do it myself. Have you ever looked into this yet. You might get more bars with verizon than you do with sprint. Plus at like 10 bux a month unlimited internet isn't tp bad ( if you buy a $30 card good for 3 monthes IE $10 a month)
Let me know if I can be of assitance, Looking to flash a light weight rom.
blazin6969 said:
I just also recently picked up one of these guys, my actual intentions for mine is to get it on verizon prepaid using a extravert as a donor phone and tethering the 3g.
Click to expand...
Click to collapse
It is my understanding (but not firsthand experience) that verizon can detect this within a couple of months and kill the imei, so be careful.
Instead I got onto a friend's family plan for $10 a month legit (but data cap of course)
Do I install this in recovery?
Sent from my SCH-I800 using Tapatalk
MVD
_ck_ said:
It is my understanding (but not firsthand experience) that verizon can detect this within a couple of months and kill the imei, so be careful.
Instead I got onto a friend's family plan for $10 a month legit (but data cap of course)
Click to expand...
Click to collapse
Lets say I work for Verizon in a department that has privy info and tools at my disposal and I will tell you we have a tool called MVD it is a Mobile Virtual Diagnostic it can detect root and will show if the tool is run. The thing is it is only loaded for tools that have the most current version of My Verizon application installed 10.0 or higher. Anything prior to that it won't load your info so root can't be seen with general tech tools. Just FYI... I am happy you all are working on SCH-I800 But I can't seem to find the the Root and Tar files to load... Any image files link?
vzw said:
Lets say I work for Verizon in a department that has privy info and tools at my disposal and I will tell you we have a tool called MVD it is a Mobile Virtual Diagnostic it can detect root and will show if the tool is run. The thing is it is only loaded for tools that have the most current version of My Verizon application installed 10.0 or higher. Anything prior to that it won't load your info so root can't be seen with general tech tools. Just FYI... I am happy you all are working on SCH-I800 But I can't seem to find the the Root and Tar files to load... Any image files link?
Click to expand...
Click to collapse
WOW nice info. Thanks. Another reason to remove every bit of verizon bloat.
TaPpEd from my XpOsEd 4.4.2 NIII
Anything new with this ROM?
ultravioletnanokitty said:
media playback is flat-out broken in all p1x 4.3+ roms,
Click to expand...
Click to collapse
Well, that explains the lack of sound and the fact that all video apps crash.
Seriously though, this ROM is a significant improvement for me compared to Cyanogenmod 9.1 (4.0.4). My Tab is far more stable than it was, and has only crashed on me once, forcing me to do a factory reset.
Can I flash back to an earlier ROM, say 4.2.2 or 4.0.4, without bricking my Tab? I have seen on the AT&T Galaxy S 3 (SGH-i747) board that S 3s that updated OTA to 4.3 will hard brick if flashed to an older ROM, so I am concerned.
Also, how close in hardware is the p1c to the Galaxy S GT-i9000? I have several i9000 ROMs on my computer, and if it is close enough, I might be able to get media working on mine. Worth a try. :fingers-crossed:
Any1 tried Lollipop? any issues? which rom?
AGNBSL said:
Any1 tried Lollipop? any issues? which rom?
Click to expand...
Click to collapse
Yes. Search Google for "FML Galaxy Nexus". There is an XDA Thread with the ROM on it, detailing the issues. Off the top of my head, the issues are camera and others. It's still pretty stable though for such an early build
I have to tell you I used the one that adamgraver is talking about and I loved it! I moved back to kit kat for stability reasons but I really loved it!
Sent from my Galaxy Nexus
adamgraver said:
Yes. Search Google for "FML Galaxy Nexus". There is an XDA Thread with the ROM on it, detailing the issues. Off the top of my head, the issues are camera and others. It's still pretty stable though for such an early build
Click to expand...
Click to collapse
There are also the nightly/test CM12 builds by Zyian since yesterday... http://forum.xda-developers.com/showpost.php?p=57155931&postcount=3753
applerulez1 said:
I have to tell you I used the one that adamgraver is talking about and I loved it! I moved back to kit kat for stability reasons but I really loved it!
Click to expand...
Click to collapse
What do you mean "for stability reasons"? I consider trying out the lollipop ROM from here:
http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064
Known issues are :
- Stock Camera app isn't working yet. Aftermarket ones, such as Camera ZOOM FX, might work however.
I don't care much about the stock camera app. But I am wondering how things go with calls, SMS, MMS, mobile data etc... i.e. usability.
The treads says: "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast. They don't include the usual FML optimizations either, but they are surprisingly snappy already..." which to me is a little confusing... If I would like to use it as a daily-driver, what are the concessions to be made?
Thanks a lot in advance for your input.
Best,
-a-
It became really slow really quickly had major crash issues as well. It couldnt play youtube, bluetooth and wifi had issues. It would just lock up a lot no matter how many resets I did. An update is going to be really soon so keep your eyes open for it, I cant wait!
Lollipop is in my opinion officially stable now if you use osmosis and neph's kernel and settings. Go check em out!
Sent from my Galaxy Nexus
They didn't show up for me on xda so i went digging and found on their site
http://dwnld.aicp-rom.com/?device=jfltexx&type=all
Working good on m919
Is everything working fine? Or is the bug list similar to cm12?
Sent from my GT-I9505G using XDA Free mobile app
aamir123 said:
Is everything working fine? Or is the bug list similar to cm12?
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Working good for me as of now, I will be able to answer better after Tomorrow when I put my phone through a full day at work.
If it's anything like CM12, all I need is for camera to work along with the other already working features from CM12 and I'll be fine using this as my daily.
gapps?
Just noticed Aicp also has jfltetmo 5.0 builds on their site, not sure if any different than jfltexx builds.
interesting, I'll check it out. thanks.
12/6 build and GPS icon popped up, made me mad thinking I was going to need a different ROM again, then poof no icon, so far it's looking like it's working right.
mwhitt said:
12/6 build and GPS icon popped up, made me mad thinking I was going to need a different ROM again, then poof no icon, so far it's looking like it's working right.
Click to expand...
Click to collapse
hey can you tell me about any bugs you found because i'm on a different cm12 build and i wanna know if that one would be better or not
projectexonaut said:
hey can you tell me about any bugs you found because i'm on a different cm12 build and i wanna know if that one would be better or not
Click to expand...
Click to collapse
Aicp 12/6 build so far has been The Best I've found for me at the moment, only bugs I've noticed so far are:
in recent tab, after you clear them random ones will pop up.
No GPS problems yet, I haven't set up Google now or Google map yet is the only thing different I've done with this setup, not sure if that's what screws up GPS .
Custom ringtones and notification tones and alarm sounds have to be manually moved to /system/media/audio to stick through a reboot.
Haven't tried BT yet and won't till Monday morning.
I used one+ camera and working fine.
Alucard kernel, and used st tweaks to set GPS region.
Auto time zone issue, I don't travel out of my time zone anymore so I just set it manually.
And I used banks minimal l gapps
GOOD NEWS CM 12 on E980 every thing work LTE-phone work.
http://forum.xda-developers.com/optimus-g-pro/general/data-voice-heard-phone-t3061313
DangNavyCM12-F240L-Fix fix dial audio after I mod .
PS.. when update the new rom voice not heard,don't forget to update my mod .
By DangNavy
Now I can go spring fishing, 2 days of the testing, happy got my lollipop ,any girls want some.HA HA HA
PS...Don't forget give me some love
Go fishing
Audio call fix
Can you explain what this does exactly? I have needed to install your mod for every CM nightly, and also for Blisspop on my e980 running on tmobile. Just curious what it does, in case your patch file stops working for new version.
Thanks again!!
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
damainman2015 said:
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
Click to expand...
Click to collapse
In the earlier version of the blisspop, the dev had changed the values in the build.prop file so the users would not needed to do so them selves. Since this was such an old issue according to that posting, perhaps dev thought that it was no longer necessary to change those two values.
Hi I'm using stock g4 ux4.0 lollipop g pro v12 final rom and during phone calls I have to use headphones whit mic because there is no sound without them . Will this fix work for me?
It may, though I think with the ROM you're using there is a patch for the sound issue, check the dev's thread first. Otherwise try the solution we've discussed here with prop.mod editor anyway, since it will not harm your device even if, it doesn't fix your problem. Just remember to reboot the phone once you're done with changing the values.
hawkwind212 said:
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
Click to expand...
Click to collapse
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
ShadySquirrel said:
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
Click to expand...
Click to collapse
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Couldn't agree more. Since this is variant specific thing, I won't change anything... I've put an info about that in Slim's thread, but it looks like people really don't like reading.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Just wanted to state, this patch is what fixes the no call audio issue for me while utilizing the TMobile network.