Kitkat seemed to work fine, but as soon as I flashed CM12 nightlies, occasionally and randomly, the phone doesn't ring when people try to call, and I receive no incoming texts. I can send texts and call out fine.
If a few hours go by and I haven't gotten any texts, I'll send a text to myself & then the phone will push all my missed messages at once. Tried different messengers, but the same issue happened.
All my mobile settings are the same, I flashed back to Kitkat for 1 month to test and never had the issue. Flashed lollipop last night, and issue returned.
Any ideas? official kitkat is OK, but I'd really like to keep lollipop.
Thanks :good:
I'm having the same issue, been trying different CM12 builds with no luck. Rolling back to CM11 fixes it, though.
Text messages get randomly delayed, sometimes for hours. Apparently this isn't a common issue on CM12.
Me too
Installed the cyanhacker lollipop rom last night, so far I haven't had this issue like the CM12 nightlies were giving, strange.
Unfortunately the problem 'just' happened. back to kitkat for a while.
I've tried CM12 nightlies for a while, PA and Temasek, all had the same problem :\
I have this issue in CM11S on AT&T
This is the issue I'm having with CM12 as well. All of my SMS messages are either delayed or I don't get them, and my phone doesn't ring when called. I tried reflashing, factory wiping, and even installing other CM-based ROMs (Paranoid Android & VanirAOSP) with no luck. I reverted back to 11s on AT&T, and it is working as expected.
AustinVillan said:
This is the issue I'm having with CM12 as well. All of my SMS messages are either delayed or I don't get them, and my phone doesn't ring when called. I tried reflashing, factory wiping, and even installing other CM-based ROMs (Paranoid Android & VanirAOSP) with no luck. I reverted back to 11s on AT&T, and it is working as expected.
Click to expand...
Click to collapse
In the OnePlus One forum on the official site someone suggested disabling the Blacklist option to get around this issue. I tried it with the CM-12 nightly from 2015-03-17, but I still had issues.
I'm far from an expert but I think it is because cyanogen 12 has not been optimised for the OPO just yet, unless I am mistaken. i know you can get the rom itself from the cyanogenmod website but its not the oneplus version. could be something to do with that.
i'd say just hold off for two weeks til the official version is out and everything should be fine
I've been told that there may be an issue with TWRP recovery and using it to flash CM12 ROMs. They recommended using Philz (https://basketbuild.com/filedl/devs?dev=jgcaap&dl=jgcaap/philz_touch_6.59.1-bacon.zip), so I've flashed it, and re-installed CM12 (cm-12-20150322-NIGHTLY-bacon.zip). So far it seems to be working as expected. I'll update this post if I see a reoccurrence of the issue.
I just got the issue once again, and I'm not able to receive calls either. Reverting back to 11s.
My fear is that I'll continue to have issues even if I upgrade to an official Lollipop build.
Working with a development resource on the OnePlus One forum we've narrowed this down to an issue with the 4G radio which is odd because it works as expected in Kitkat. I have gone into Settings\Mobile Networks and set the Preferred Network Type to 3G. Clearly this isn't ideal, but now at least I'm able to receive SMS and phone calls. I'm going to try another SIM card (currently on Stream/AT&T) to see if it is an issue with my provider.
Latest twrp and cm12 firmware?
Sent from my bacon!!!!!
NickosD said:
Latest twrp and cm12 firmware?
Sent from my bacon!!!!!
Click to expand...
Click to collapse
I'm running TWRP 2.8.5.1, but I'm not sure about the CM Firmware. I only did a clean flash of the latest CM nightly, and I thought that it was included in the ROM zip.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's okay then. Maybe try another modem?
Sent from my bacon!!!!!
NickosD said:
It's okay then. Maybe try another modem?
Sent from my bacon!!!!!
Click to expand...
Click to collapse
I'm going to try this one: http://boeffla.df-kunde.de/bacon/modems/
Are you using greenify? If yes, degreenify sms app and phone, if you have them hibernated.
Sent from my bacon!!!!!
No I'm not using greenify.
AustinVillan said:
I'm going to try this one: http://boeffla.df-kunde.de/bacon/modems/
Click to expand...
Click to collapse
So I've wiped/repaired/formatted my phone, and flashed my ROM again. Initially, the SMS delay still occurred which I expected. I then flashed Full-CM12-23.01.15-modem-flashable.zip from the link above, since I started noticing the issue in January, but unfortunately I still saw the problem. I flashed Full-CM12-16.02.15-modem-flashable.zip this morning, and it appears to be working. If I see the issue again, I'll post an update.
Related
Official Gingerbread rom released for China 20F
Languages: English and Chinese.
Rootable.
Download: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP920/ABUOML/V20f_00/V20F_00.kdz
http://uploading.com/files/f1a452mb/V20F_00.kdz/
http://letitbit.net/download/34068.3f6b5bd994d6659acd00e47c3322/V20F_00.kdz.html
what about ghost calls?
I don't know anything about ghost calls,sorry.
I don't know what the issue is with ghost calls I'm on 20c with Rogers and I have never had a ghost call ever and I've had the up since it was released to us. Also I've been on several other roms with no such ghost call issues.
Sent from my LG-P925g using xda premium
My Thrill was having ghost calls only on 21A, all other versions were working fine.
I'm on 20E more than a week and no ghost calls.
This Rom maybe the good news(That solves Ghost calls). I think it is the first update from LG for GB ROMs. All other GB ROMs are the same (The difference is in regions/carriers)
arsen4oo said:
My Thrill was having ghost calls only on 21A, all other versions were working fine.
I'm on 20E more than a week and no ghost calls.
Click to expand...
Click to collapse
If it is the one for Middle East, then yes, you have ghost calls but you didn't discover that until now. 2 friends running the Rom told me about it.
According to some Chinese forums, the users there have not experienced any ghost calls whatsoever after flashing this rom. Just a heads up to anyone who's wondering about its effectiveness
What about battery stats???
Running it now, it is 22 Feb 2012.
Some screenshot for what differ in Chinese Rom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- You cannot login to your gmail account(No setup wizard for gmail), so, there is no market.
- There is only 2 languages, however, you can download localmore 2 from any other market and get your language.
Try to install market manually.See if it works.
http://minus.com/mdXsmqsyn
abo_mara7
Click to expand...
Click to collapse
Are you from Armenia?
arsen4oo said:
Are you from Armenia?
Click to expand...
Click to collapse
.....lol 7abibi abo-mara7
arsen4oo said:
Try to install market manually.See if it works.
http://minus.com/mdXsmqsyn
Click to expand...
Click to collapse
I've already did that, but it asks for you to login to your gmail account, and that is not possible! And No, I am not from Armenia.
ok i'm testing this rom.
Loaded kdz
Switched on the phone and started a factory reset ( i use the function form phone menu because recovery won't work in the correct way, I flashed kdz with clockworkmod recovery installed maybe is this the problem) then I rooted the phone with the script for 20x rom ( works without problems ) installed recovery than loaded gapps package download from cyanogen. Next reboot I have the wizard for gmail account and market too.
Under testing let's see if ghost or not ghost
dromico said:
ok i'm testing this rom.
Loaded kdz
Switched on the phone and started a factory reset ( i use the function form phone menu because recovery won't work in the correct way, I flashed kdz with clockworkmod recovery installed maybe is this the problem) then I rooted the phone with the script for 20x rom ( works without problems ) installed recovery than loaded gapps package download from cyanogen. Next reboot I have the wizard for gmail account and market too.
Under testing let's see if ghost or not ghost
Click to expand...
Click to collapse
Did pretty much the same except rooted with megatron script and installed gapps no problem, market works fine.
Root: http://vulnfactory.org/blog/2012/02/26/rooting-the-lg-thrill-optimus-3d/
gapps: http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
Edit: data connection does not work, update APN settings with your provider settings.
dromico said:
ok i'm testing this rom.
Loaded kdz
Switched on the phone and started a factory reset ( i use the function form phone menu because recovery won't work in the correct way, I flashed kdz with clockworkmod recovery installed maybe is this the problem) then I rooted the phone with the script for 20x rom ( works without problems ) installed recovery than loaded gapps package download from cyanogen. Next reboot I have the wizard for gmail account and market too.
Under testing let's see if ghost or not ghost
Click to expand...
Click to collapse
Good job guys plzzzzzz test the GC issue quickly and let us know
sak500 said:
Good job guys plzzzzzz test the GC issue quickly and let us know
Click to expand...
Click to collapse
30 test calls made 15 from mobile and 15 from landline and all connected, That doesn't mean there is no ghost call issue though
kidkoala_uk said:
30 test calls made 15 from mobile and 15 from landline and all connected, That doesn't mean there is no ghost call issue though
Click to expand...
Click to collapse
Thanks for the update. Possible for you to take it to low signal area or completely w/o signal and bring it out in open and test it? Normally mine developed if i was carrying the phone to my car in basement and then once i came out of it it would crash.
why the baseband version is the same as in v10D and others stock roms?
L6260_MODEM_SIC_01.1042.00?
sak500 said:
Thanks for the update. Possible for you to take it to low signal area or completely w/o signal and bring it out in open and test it? Normally mine developed if i was carrying the phone to my car in basement and then once i came out of it it would crash.
Click to expand...
Click to collapse
I am currently in an area that doesn't have a great signal, I also removed some apps using rootuninstaller and during which my mobile signal disconnected/reconnected, I then tested another call and it connected ok. Again this does not mean that its free from ghost calls.
Does anyone know how to fix the error when I try to tether? It was working fine a few days ago and it just stopped working. I have all the settings set up correctly. I've done everything to enable tethering prior to the error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hopefully this helps others whom had the error pop up for their wifi tethering. It did not fix my issues at all but it seems to resolve the problem for others.
Deleting or renaming /data/misc/wifi solves the problem for some. Sadly mine wasn't fixed by this but I'll keep this updated with what I find to help others.
https://code.google.com/p/android/issues/detail?id=62516
Sent from my Nexus 5 using Tapatalk
It works perfectly fine on a clean flash. It stopped working a few days ago and no settings pertaining to tether were changed.
This is the error I get.
This is on a clean flash, so the rom is able to work fine right out of a fresh install.
Sent from my Nexus 5 using Tapatalk
Any ideas guys?
Sent from my Nexus 5 using Tapatalk
I have installed the latest nightly of CM11 and I have the same problem.
Deleting or renaming /data/misc/wifi did not solve the problem for me...
Someone help?
mscosta said:
I have installed the latest nightly of CM11 and I have the same problem.
Deleting or renaming /data/misc/wifi did not solve the problem for me...
Someone help?
Click to expand...
Click to collapse
Has anyone reported that issue with CM? I'm running beanstalk which is based on CM. A few people have reported the issue and we have yet to figure out a work around besides a clean flash.
Sent from my SPH-D710 using XDA Premium 4 mobile app
Now updated for today's nightly CM11 - 10.04.2014 and the problem is solved ... thanks
free upload pictures
Wow today it started working again by itself. I haven't installed new apps. There's an update available for my rom but I don't want to risk updating and loosing WiFi tether.
Sent from my Nexus 5 using Tapatalk
I started having this issue on my N5 recently. I haven't changed much, other than update the kernel. I'm running Cataclysm with FauxKernel 16u_r2. I went back to the stock kernel with no change, I still get an error (and hotspot has always worked across all kernels I've usually run).
In my case, after the error, I am unable to turn WiFi back on unless I put the phone in Airplane mode and take it back out.
No one seems to have reported this issue on the latest FauxKernel, but I'll ask over there too. Maybe there's something everyone was using that broke this and why CM is now fixed. Would be nice to know what that was.
No no one fixed it till now and no one really knows why it happens. Happens on all custom roms including cm and stock. Something gets messed up during flashing the builds. That's why reports are more on custom ROMs than on stock. On last stock upgrade a lot reported this as well. There is even a ticket open on googles bug tracker for it.
Sent from my Nexus 5 using Tapatalk
havanahjoe said:
I started having this issue on my N5 recently. I haven't changed much, other than update the kernel. I'm running Cataclysm with FauxKernel 16u_r2. I went back to the stock kernel with no change, I still get an error (and hotspot has always worked across all kernels I've usually run).
In my case, after the error, I am unable to turn WiFi back on unless I put the phone in Airplane mode and take it back out.
No one seems to have reported this issue on the latest FauxKernel, but I'll ask over there too. Maybe there's something everyone was using that broke this and why CM is now fixed. Would be nice to know what that was.
Click to expand...
Click to collapse
Same issues here. Deleting the wifi folder didnt do jack but loose all my profiles. Im on cm 11 alwasy latest night. What are we missing here? Stopped working maybe a month ago
mickdubs said:
Same issues here. Deleting the wifi folder didnt do jack but loose all my profiles. Im on cm 11 alwasy latest night. What are we missing here? Stopped working maybe a month ago
Click to expand...
Click to collapse
I had to do a factory reset (delete all user data) and that fixed it. I then restored all my app data with Titanium Backup
Sent from my Nexus 5 using Tapatalk
mickdubs said:
Same issues here. Deleting the wifi folder didnt do jack but loose all my profiles. Im on cm 11 alwasy latest night. What are we missing here? Stopped working maybe a month ago
Click to expand...
Click to collapse
For me it comes and goes on it's own. I won't change apps or the rom and it'll change by itself. The only thing I do flash is my kernel updates. The kernel doesn't affect WiFi though so idk.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
For me it comes and goes on it's own. I won't change apps or the rom and it'll change by itself. The only thing I do flash is my kernel updates. The kernel doesn't affect WiFi though so idk.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Only a Factory erase or flashing another ROM worked for me.
Deleting the recommended folder did not help.
It's not cm. I'm stuck with it on stock. No ryme or reason
From my mobile telephony device.
Staggerlee66 said:
It's not cm. I'm stuck with it on stock. No ryme or reason
From my mobile telephony device.
Click to expand...
Click to collapse
I've gotten it on cm and Aosp based roms. I never ran stock, not even when I bought my phone did it boot into stock. It works flawlessly with cataclysm though.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
I've gotten it on cm and Aosp based roms. I never ran stock, not even when I bought my phone did it boot into stock. It works flawlessly with cataclysm though.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I didn't realize I had the issue till I seen your post in elementalx , I'm running stock .
FuMMoD said:
I've gotten it on cm and Aosp based roms. I never ran stock, not even when I bought my phone did it boot into stock. It works flawlessly with cataclysm though.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm sure u would have posted if u did but ill ask anyways , have u learn anything new on this subject ? (Broken tether)
Q&A for [ROM][5.0.2][Official]Dirty Unicorns Bacon
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.2][Official]Dirty Unicorns Bacon. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Du official 5.0.2 question..
I flash this ROM bat in setting info devices is write unofficial ??
A few things I've noticed
So, great rom, I've always been a fan of DU, and I'm glad my OnePlus finally gets it officially.
A few things I've noticed so far:
There is no timeout selector for the buttons backlight, I usually set it to 1 sec, but there's no way to change it from the 5 sec default.
If you turn on the on screen nav bar, the backlight for the buttons still lights up.
If you turn the device off while the buttons backlight is on, it will be stuck on until you turn the device on again. Only fix is to let it time out before locking the screen. (I believe this is a known issue).
In the settings, it reads DU version: UNOFFICIAL-v9.2
On initial setup, it defaulted to using MetroPCS for my carrier (I have T-Mobile) It worked fine when I changed it to the proper carrier. (This seems to be a problem in several roms)
Personal preference: I'd like, when charging, the battery percentage stay inside the circle instead of moving to the side of it.
Most of this is nitpicky (except for the button backlight stuck on when device is locked), I really think it's quite stable and awesome, I can't wait to see 9.3 come out.
Can anyone tell if boeffla kernel 3.1 is compatible with 5.0.2 du rom build 100415..
TIA..
Wifi fix after flash.
My Wifi was having issues, since I still had the old radio firmware. The lollipop modems can be found at http://forum.xda-developers.com/oneplus-one/development/radio-updated-modem-radio-files-oxygen-t3072516
Once I flashed the new modem with TWRP, WiFi works great.
kunal1540 said:
Can anyone tell if boeffla kernel 3.1 is compatible with 5.0.2 du rom build 100415..
TIA..
Click to expand...
Click to collapse
I am on latest weekly build. Not sure if Boeffla will work.
Oxygen radio/modem
Hi all,
First post
Loving DU!
Just wondering if its possible to flash: Full-oxygen-04-04-15-Bacon-modem-flashable.zip onto OFFICIAL-v9.3 build 3.4.67... Or maybe a better question is,.. would this improve reception at all?
Thanks
just wanted to say great job. Loving the latest weekly on bacon!
is it possible to remove the hardware keys?
sewb said:
is it possible to remove the hardware keys?
Click to expand...
Click to collapse
Yes, from Dirty Tweaks, System, Buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM deserves a 1000 thanks from me. I just love it. Looking forward to the next update!!
Hmmz I'm getting "Process system not responding" - not constantly - no idea what triggers it - running catlog for today...
Here's what I did yesterday - coming from Slimsaber -
Flash latest TWRP
Wipe cache - dalvik - system - data
Flash latest CM Nightly
Flash latest DU
Flash Slim-gapps beta fix
Everything seemed to be working fine... 2 crashes that I know of right now... phone just soft-reboots and then the "process system not responding" error... weird...
Probably gonna reflash stuff tonight - something wrong in my flash order?
I do not find in the settings - security - change the order of the numbers in the pin pad
language italy , where I can find them ! thanks
Version 9.4 Dirty Unicorns Bacon
Hey quick question. Does screen pinning work on this rom?
I am about to install this. Does xposed work with this rom? if so what version? Also, any known bugs? cant seem to find these answers anywhere. cheers
http://forum.xda-developers.com/showpost.php?p=61933341&postcount=356
Click to expand...
Click to collapse
I was under the impression this was fixed already. Check out: https://jira.cyanogenmod.org/browse/BACON-3275
I'm not having anymore issues with Bluetooth since this fix went in.
Boot loops - Need Flash help
I'm having an issue flashing this ROM. I just got an RMA replacement on my OnePlus so I am coming from CM11. I flashed CM12.1 Nightly (7/20 build) to get updated firmware, then clean wipe, and flashed DU. After rebooting, I get a boot loop at the OnePlus logo and DU never loads. Interestingly, if I fastboot flash back to CM11, clean wipe, then flash DU, it will load, but is missing the CM12 firmware/modem.
I'm using twrp-2.8.6.0.6-bacon-materialised as my recovery since twrp-2.8.6.0 doesn't load for me when flashing on top of CM12.1 nightly.
Anyone know how to avoid the boot loops while maintaining CM12.1 firmware? Any help would be greatly appreciated.
System UI has stopped
Hi
I have clean flashed (wiped system and caches), and installed the latest update, however my phone keeps giving me "Unfortunately, System UI has stopped". Any ideas please on how to solve?
Thanks
Hey der...m using Official DU..there is some problem in SuperSU (root) rooted apps are not working..please help me...I really liked this ROM very much.. Thanks in advanced..
Incall UI
I'm unable to access the Incall UI in the latest 9.6 . I clean flashed 9.5 then updated to 9.6 anybody has the same issue? any solutions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM12.1 is here for the D801, aka the T-Mobile LG G2.
This is a source build rom, which includes all the latest changes from cm. The nightlies are starting August 3rd.
Instructions
Official support is now limited to Kitkat and Lollipop basebands. CM-12.1 is based on a completely new kernel. This has enabled support for the latest basebands newer than jellybean.
While many people and devices are in various states we officially recommend flashing back to stock then fully updating your device before using cm-12.1.
If you are coming straight from cm-12.0 the rom will not boot.
Download cm-12.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
The latest will be available at:
http://get.cm/?device=d801
Gapps:
Official CM ones (soon):
http://wiki.cyanogenmod.org/w/Google_Apps
Click to expand...
Click to collapse
Known Issue
None!
Click to expand...
Click to collapse
Change Log
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
rashed
acree
Click to expand...
Click to collapse
Source
http://github.com/CyanogenMod
Click to expand...
Click to collapse
Works great, no problems encountered yet!
Edit:
Camera not working, also tried Motorola and Google cameras without success.
My D801 is running stock Lollipop 30B rooted with TWRP. Can I just flash the ROM+GApps normally? Or would I have to install a bootstack changer?
briand.mooreg said:
Works great, no problems encountered yet!
Edit:
Camera not working, also tried Motorola and Google cameras without success.
Click to expand...
Click to collapse
Update:
Camera is working in newest nightly.
I just flashed the latest nightly from the stock lollipop lg rom. I flashed the 20g bootstack, cm, and gapps. Once the rom booted, my phone would constantly freeze and reboot every few minutes. Is anyone here having this issue. Let me know if I missed flashing a file or something. Please and thank you
Sent from my LG-F350K using Tapatalk
Mobile Data Issues
I really want to use this ROM but it's got an issue that I can't seem to fix and it makes the phone almost unusable. I switched back to KK bootstack and installed the ROM and this part went off without a hitch. ROM booted fine but I couldn't get cell data. Tried a bunch of different things until I found out that the APN setting was wrong (I'm on Tmobile). I fixed that and data worked for a bit, was even able to run a speed test. However shortly after that the phone rebooted. Then it kept rebooting, finally figured out that whenever the phone connects to LTE it automatically reboots. No warning, no nothing, just one second the phone is up the next second it's at the LG logo. If I immediately turn on airplane mode at boot it works fine. I can then turn on WiFi and then mobile connection and it works without rebooting. Also of note, when it has one of the LTE reboots, it causes it to lose the saved password of the WiFi connection. If anyone has any tips please let me know! I'm at a loss here, I can provide logcats if it would be helpful!
---------- Post added at 07:21 PM ---------- Previous post was at 07:17 PM ----------
alexnaoumi said:
I just flashed the latest nightly from the stock lollipop lg rom. I flashed the 20g bootstack, cm, and gapps. Once the rom booted, my phone would constantly freeze and reboot every few minutes. Is anyone here having this issue. Let me know if I missed flashing a file or something. Please and thank you
Sent from my LG-F350K using Tapatalk
Click to expand...
Click to collapse
Try switching on airplane mode as soon as it boots up and see if that lets it run without issues for a bit. See my previous post for more info.
Hey guys I figured it out. I had flashed the 20G bootstack and had the same issue - reboot every time connected to LTE. Not only on this ROM but every AOSP 12.1 ROM. Switching to the 30b bootstack solved the issue for me.
thanasisc4 said:
Hey guys I figured it out. I had flashed the 20G bootstack and had the same issue - reboot every time connected to LTE. Not only on this ROM but every AOSP 12.1 ROM. Switching to the 30b bootstack solved the issue for me.
Click to expand...
Click to collapse
Can confirm this is correct thanasisc! Thanks for sharing so others know. I'm honestly pretty miffed right now because some kid posted in the other development forum that you needed the kk boostack which is a bull faced lie and actually causes issues. We need to see if we can get mods to delete that post so more people aren't led astray.
Can I get some help fixing the Mobile Data issue with cm12.1? I flashed a nightly build from Aug. 27th and everything worked perfect until I lost my T-Mobile LTE-4G-3G-Edge-whatever.
Also is it recommended to run a nightly build for a daily driver? Because I ordered a G2 strictly for stock android 5.1
does slimport work on this rom
What is the recovery.img that cm is providing? Should I install that first? I have never seen cm provide recoveries before.
Unofficial CM-12.1 update w/ Snap
Anyone interested in downloading a "newer than November" build of CM-12.1 for the G2, please visit the following page:
http://forum.xda-developers.com/showpost.php?p=66071230&postcount=1458
Build has the official CM-13.0 version of Snap integrated into the ROM w/ working HDR.
ONEPLUS ONE FIX COMPASS/GPS ISSUES
I don't have an OPO anymore, so I may no longer mantain this thread.​
Hi all.
After many months having this issue, I finally have a solution.
This is only a temporary fix in order to have your GPS functioning. It is not guaranteed it will work with future software/ROM updates.
I highly recommend you to open a warranty ticket here.
Now that I'm seeing many people having the same problem, I will share the solution with you.
What's the issue?
Impossible to calibrate or use the compass. GPS accuracy/tracking failures.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's the cause?
Firmware.
Now I know that this problem showed up when the new firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 (commonly known as 241) was released, many months ago.
Since the day it was installed on my OnePlus One I unconsciously started to have this issues.
I changed ROMs, wiped caches, did full clean installs (but maintaining the last firmware) and the problem persisted…
Some weeks ago CyanogenMod released a nightly with the baseband version .4.0.1.c7-00011-M8974AAAAANAZM-1 (commonly known as 011) and the problem was gone. At least until they had it reverted back to 241, when the issue automatically reappeared.
After reflashing the 011 version I came to the final conclusion that 241 was the cause.
I already let them know about this: you can see me "whining" about this when they reverted to 241, but they stated that they were not having such issue, ignoring the problem.
How to fix?
If you have such issue, regardless of the ROM you're using, you probably are with the 241 firmware version.
To solve it, simply flash the 011 013* firmware version.
Note: make sure you have TWRP 2.8.6.0 or 3.x.x in order to properly flash this firmware.
Please read the NOTES and UPDATES sections before you proceed.
You can find the firmware on the attachments or here.
You will have to re-flash it every time you update your Nightly or ROM.
NOTES:
None of the following situations happened to me. I just want you to be aware of them:
I am not responsible for any damage you may cause to your phone when trying to follow this guide.
When flashing things, you may end up with no IMEI. Be safe and backup your EFS partition following this guide.
If you can't access your network after flashing this modem, reboot your phone.
Hope this guide will help you!
Feel free to click "Thanks!" if it helped you!
UPDATE:
This fix is still working on all the COS13 updates!
EDIT 11/08/2016:
* Replaced 011 with 013 as the later won't break the proximity sensor.
Has anybody else tried it?
Could someone confirm this?
I'm very interested to solve this issue, but I can't take risks...
I had problems with Sky map, when my phone is flat down, compass works ok, but standing up it's shaky and rotates... So this didn't really fix my problem.
walent said:
I had problems with Sky map, when my phone is flat down, compass works ok, but standing up it's shaky and rotates... So this didn't really fix my problem.
Click to expand...
Click to collapse
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
waterdaan said:
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
Click to expand...
Click to collapse
Unfortunately i already have it like that
waterdaan said:
https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Changing /etc/sensor_def_qcomdev.conf fixed it for me
Click to expand...
Click to collapse
Hi people, unfortunately, in my file both version and numbers end in 5 ?
walent said:
Unfortunately i already have it like that
Click to expand...
Click to collapse
UPDATE:
This fix is still working on the COS13 updates:
GPS Issue with OnePlus One
Hey everyone, I'm suffering from a GPS performance of my OnePlus One. It's been TERRIBLE since I bought the phone in December of 2014!
I tried other software (Waze or Here maps), something is wrong with the hardware I believe.
I've updated my OPO to the latest official OS available.
I'd love to avoid rooting just for fixing my GPS.
Please see screenshots:
I'd appreciate your advice and help!
Thanks you!
Tried this fix and unfortunately it didn't work (currently on 20160708 cm13 nightlies)
I have tried it now, but unfortunately it didn't work. i'm with cm13.1-xxxxS1KN
nurunuru said:
Tried this fix and unfortunately it didn't work (currently on 20160708 cm13 nightlies)
Click to expand...
Click to collapse
It was working until the 20160706 CM13 nightly, until I sent my OnePlus One for RMA. I'm tired of this malfunction.
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
nipun03 said:
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
Click to expand...
Click to collapse
Good question!
nipun03 said:
Hey does it work with Lineage OS? I'm having firmware DI.3.0.c6-00241-M8974AAAAANAZM-1 on build 20170306 of Lienage OS or is there a way developers of Lineage OS can implement the new firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 in Lineage OS weaklies build? I would love to fix this problem once and for all
Click to expand...
Click to collapse
I don't have an OnePlus One anymore.
But since you're having the same old firmware (DI.3.0.c6-00241-M8974AAAAANAZM-1) in Lineage I assume the firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 would still work and fix the compass issue.
Do a nandroid backup and test it yourself
PS: you'll have to find the firmwares on another thread since my links were taken down and I no longer mantain this thread.
EDIT: Updated the firmware link with one working.
tfae said:
I don't have an OnePlus One anymore.
But since you're having the same old firmware (DI.3.0.c6-00241-M8974AAAAANAZM-1) in Lineage I assume the firmware .4.0.1.c7-00011-M8974AAAAANAZM-1 would still work and fix the compass issue.
Do a nandroid backup and test it yourself
PS: you'll have to find the firmwares on another thread since my links were taken down and I no longer mantain this thread.
EDIT: Updated the firmware link with one working.
Click to expand...
Click to collapse
Thank you for updating the firmware link.. Will definitely try it