Related
I realize that it is early to create threads like this, but I wanted to know if it was just an error in my phone or in general.
I installed Android 4.4 compiled by Grarak but I can not read the sms, quend I get one if I try to read the app crashes
I only found this little guide now! In my case it worked!
http://forum.xda-developers.com/showpost.php?p=47042307&postcount=243&nocache=1&z=3127877558581531
Now it remains to be solved wifi and small graphical issues.
Just a Alpha project
maybe basic on nexus 5 some file
just waiting
I'm actually surprised how stable it is at the moment.
Q&A for [ROM][OFFICIAL] CyanogenMod 11 Nightly Builds for SGH-I747
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
net::ERR_EMPTY_RESPONSE errors with browsers
Hello,
I'm using Samsung Galaxy S3 - I9300 (International Variant) with Cyanogenmod Version 11-20141008-SNAPSHOT-M11-I9300
I have tried in different browsers (Google Chrome, Opera, Firefox, Next Browser) with all these I'm getting the errors (net::ERR_EMPTY_RESPONSE). Sometimes it is way to frequent making the mobile unusable.
I have searched for solutions but nothing has worked for me till now. Have raised a ticket with CM and link for the same is https://jira.cyanogenmod.org/browse/CYAN-5628
If you are having the same issues, please share your comments on the jira.
If you were able to fix the issue apart from doing things like clearing Dalvik cache, turning off 2 step authentication, editing access points, reinstalling CM or using a different browser please let me know.
I have done the above said things but still encounter the error randomly on multiple webpages, even some pages images or videos not get loaded. Have to do multiple refresh.
Will appreciate any help.
Cheers,
Prasi
Prasath.B said:
Hello,
I'm using Samsung Galaxy S3 - I9300 (International Variant) with Cyanogenmod Version 11-20141008-SNAPSHOT-M11-I9300
I have tried in different browsers (Google Chrome, Opera, Firefox, Next Browser) with all these I'm getting the errors (net::ERR_EMPTY_RESPONSE). Sometimes it is way to frequent making the mobile unusable.
Will appreciate any help.
Cheers,
Prasi
Click to expand...
Click to collapse
This is the forum for the i747 and i747m. You have the international version of the s3.
Sorry
audit13 said:
This is the forum for the i747 and i747m. You have the international version of the s3.
Click to expand...
Click to collapse
Sorry please ignore it, if any one has fixed please help.
Not sure what's going on with CM and the lack of NIGHTLY updates the past couple of days, but it is unusual for them.
I ran into the GPS issue with my Sprint S3 (SPH-L710) as a result of flashing one of the October NIGHTLY builds. I don't use GPS every day so I'm not sure how or why it stopped functioning. I had to flash the stock ND8 ROM (after a complete wipe), then opened up Androsensor and locked 22 satellites immediately. I rebooted into Recovery, ran a complete wipe of the phone, then flashed the Cm11-20141013 d2lte nightly and rebooted. GPS was fixed, locked 22 satellites with Androsensor, same as I did on the stock ND8 ROM. I opened a NIGHTLY regression issue but it was closed since the same issue was open for the M11 stable build.
Tap and Pay
Are there any plans to get tap and pay to work on d2lte? Google wallet is listed in the tap and pay settings, but the phone does not respond when held up to a payment terminal.
Above ^
The cm team is aware of the tap and pay issue its in the current bug list on cm site we'll have to wait n see if they fix it
canodroid15 said:
Above ^
The cm team is aware of the tap and pay issue its in the current bug list on cm site we'll have to wait n see if they fix it
Click to expand...
Click to collapse
Hi, I am essentially the CM team for this phone. Until open source pn544 HCE code becomes available we will not support it for this phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Couple of Issues with cm12.1 - Clock Stopped and GPS
cm12.1 - Moving this question to the proper thread!!!
Has anyone encountered any "clock stopped" errors when working with various apps?
Also some of the weather apps can't seem to obtain location from my GPS even though it is enabled. Anyone have similar issues?
default gps. conf file in /etc uses a testing time server. if you comment out that line with # and uncomment the time server for your region, gps may lock more reliably and quicker.
Q&A for [ROM] [NIGHTLY] [4.4.4] CyanogenMod 11 for Samsung Galaxy Nexus
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
CM11-M11 stable?
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Since a long time ago the native sip client has been fixed. There are other kitkat ROMs out there for other devices which still have an audio bug rendering the sip client useless. Could someone link me to this ROM's fix so other developers could apply it to their ROMs?
I've been trying to search for it myself but I can't find it. Thanks a lot! [emoji4]
Silpion said:
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Click to expand...
Click to collapse
The latest M release should be pretty stable.
Hello @Ziyan
Many thanks for your amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
ImTheDroid said:
Hello @Ziyan
Many thanks for you amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Click to expand...
Click to collapse
By the time they start pushing nightlies (in December), maguro should be fully functional (meaning it will be built too), or I may release test builds earlier
Codename89 said:
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
Click to expand...
Click to collapse
They said they'll build it on the weekend.
When Galaxy Nexus Maguro CM M12 build?
Hello Ziyan,
[Edit]: Sorry, I saw the previous post after I posted this question.
I still don't see the M12 for Galaxy Nexus Maguro. Although I see in another thread you mentioned that it will happen once you ask the CM team to build it, but nothing seems to have happened. Just wanted to have this last one of CM11 as it might be better to keep for a long time (in the light of the fact CM12 is coming but might take some time to stabilize). So, any idea, when is the build going to take place?
Thanks...
(I would like to post in the mail thread, but my post count seems to be a problem, anyway..)
After the update to cm11 m12 my phone works really smooth.
As other I noticed that generally the rom degrades its performance after some days probably because of the memory trimm.
I also evidenced performance issues in cm 11 m11 due to Google now voice detection of "Ok google" so I disabled it.
I registered in xda to thank you.
In the CM12 roadmap [1] there's:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release.
Click to expand...
Click to collapse
Currently CM11 kernel has SELINUX set to permissive to fix some bugs (in the dialer iirc), but enforcing should be possible. Just have to add some rules:
https://source.android.com/devices/tech/security/selinux/validate.html
Getting encryption to work without watering it down sounds impossible when it expects hardware backing, which tuna doesn't have. [2]
(Technically tuna hw has TEE support, but google disabled it for keystore already due to a power usage bug [3])
Edit:
Seems like Google left the old software encryption still in:
https://android.googlesource.com/platform/system/vold/+/69f4ebd
(use_keymaster == 0)
Didn't look at CTS yet if one still passes without hardware keymaster.
Or what's your take on it?
[1] http://www.gadgtspot.com/2014/10/31/roundtable-cyanogenmod-12-roadmap-leaked-fun-times-ahead/
[2] http://source.android.com/devices/tech/encryption/index.html#storing_the_encrypted_key
[3] http://nelenkov.blogspot.it/2012/07/jelly-bean-hardware-backed-credential.html
Same here...
Anyone else got problems with video playback in YouTube in the 20150201 nightly?
*Deleted
sorry, delete please
SELinux
Hi there Ziyan,
I don't know if it's a choice or something went wrong in the 05-10 CM11 Weekly build for the Maguro Gnex but the SELinux is disabled... Just wanted to point it out since i know that you guys usualy build with SELinux set to Permessive...
Have a good day
SELinux
Hi @Ziyan SELinux is still disabled in last weekly...
gps fix cm11 maguro
Hi Guys,
I can't get gps fix with cm11 maguro http://forum.xda-developers.com/galaxy-nexus/development/rom-cyanogenmod-11-kvt49l-samsung-t2405147
can anyone help me with this issue? I've tried 'fastergps' app without any luck
kernel left alone, I didn't changed it
Phone freezes and reboots right after wake up in CM11 20150626 Snapshot
Hi everyone,
I just updated the phone from CM11 nightly of a version maybe two months old to the latest CM11 20150626 Snapshot, and I get this problem.
Right after the phone reboots, the locking, unlocking works fine. After a while (seems every app finishes its starting up), when I lock the phone and wake it up, the phone freezes right away and reboots a while later.
Can anyone let me know how to identify or solve this problem? Thanks.
Edit:
Ok, I just did a factory reset and now it seems to be running ok.
Edit:
I finally found out it's because I forgot to flash kernel for the PGM app.. how stupid I am.
Thank for great ROM.
@Ziyan and any people who help to create the great ROM for our device, Last year we hope to use KITKAT and now we fulfill this great ROM. Thank you every one.
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
miir01 said:
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
Click to expand...
Click to collapse
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
levone1 said:
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
Click to expand...
Click to collapse
Thanks for the hint. Will search for more info in the forum. :good:
However, how would I know if I flashed a M5 kernel? I definitely wasn't aware of flashing it. My current kernel version is 3.4.0-cm-g1e19761
pr3ddi said:
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
Click to expand...
Click to collapse
I still have the package for cm-12.1-20150925-NIGHTLY-amami.zip on my phone. But can't downgrade to it because after flashing it, my z1c is stuck in the boot animation. I have waited at least 3 hours before I gave up and reflashed the newer version.
EDIT - sorry, link's dead. I should've checked it first. I would also be interested in trying an older build.
Does this help?
https://download.cyanogenmod.org/get/jenkins/127851/cm-12.1-20150928-NIGHTLY-amami.zip
Did anyone test cm-12.1-20151008-NIGHTLY-amami.zip ?
Changelog says that wifi and bt problems have been fixed.
www . cmxlog . com/12.1/amami
jira . cyanogenmod . org/browse/NIGHTLIES-1877
Giulio Cervera added a comment - Yesterday 4:28 AM
this was 2 issue:
1) the channel bonding
2) taimport was running with wrong timing, and BT and wifi mac address was not exported in /data/etc
fix for both is merged
Click to expand...
Click to collapse
pr3ddi
Just installed 20151008, I had been having major issues with wifi EAP previously (think i was on a MAY2015 build), this build's looking a lot better. The app launcher is alphabetized, and toast notifications have an icon from the app that generated them. I haven't tried bluetooth yet - my previous build was very bad with BT, I'm hoping this one's better.
Running 20151010 for over 6hrs now ...
wifi and bt are running stable and it looks like the issues have been resolved
pr3ddi
same problem
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
iSpammer said:
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Click to expand...
Click to collapse
Not sure, no idea if they share the same hardware etc?
I've found battery life is a LOT better in this build too. AudioFX still having its moments though.
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
ULT][MO said:
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
Click to expand...
Click to collapse
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.[/QUOTE]
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed
ULT][MO said:
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
Click to expand...
Click to collapse
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed[/QUOTE]
I'm using TWRP for my recovery. I believe you'll need to get an unlock code from the sony website for your phone before you can start rooting/flashing.
How to install (and root) Z1C
known issues for CM12.1 on Z1C
Note that my phone has experienced random reboots, about once or twice a day with CM21.1-20151008.
I tried to flash recovery in every mode God has invented but nothing: when I open flashboot i have evry time the same fu**ing message
"sending 'recovery' (8778 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.561s"
bootloader is unlocked, installed flashtool and relative drivers
Please guys help!
Sorry if I've posted in wrong place
Solved: I've repeated bootloader unlock procedure reported by Sony. Seems ok now
Has anyone trie 10132015 build if wifi is fixed?
amnher said:
Has anyone trie 10132015 build if wifi is fixed?
Click to expand...
Click to collapse
I tried, not fixed. For me wifi it's essential
I've been around a while so I'm not new to Android or to tech in general but I am new to this Slot A/B stuff and also new to using Verizon 5G/LTE.
After soft-bricking my new phone by flashing TWRP and crDroid 8.2 based on Android 12, everything seems to be working well except I noticed that I'm not receiving MMS. I went to APN settings but I'm not able to edit the existing ones and if I add a new one, I can't change any settings there except the APN field. I also noticed that my build.prop identifies my phone as LE2123. I confirmed before I modified anything that I have LE2125. Any thoughts on this?
Resolution:
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved
If I'm not mistaken crDroid is
LOS based where Derpfest is AOSP based
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
ive had that happen on occasion. the latest bug i seem to have acquired is that during the phone connection where and when the person making the call (me) in said scenario wait's for the other party to answer does not hear anything until either some one answers or their voicemail does.
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Elrey567 said:
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Click to expand...
Click to collapse
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
oneszero said:
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
Click to expand...
Click to collapse
just now read your previous post. DERP!
djsubterrain said:
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
Click to expand...
Click to collapse
I actually did post in the crDroid thread and got no response so then I made a separate thread
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
oneszero said:
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
Click to expand...
Click to collapse
It says lahaina
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
ekin_strops said:
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
Click to expand...
Click to collapse
In my defense, I opened a single thread, not multiple. When I didn't get a response for two days in the crDroid thread, I assumed that if I was going to get any support that a dev would ask for the logs or other info they need. I mean, what's the point of going through the trouble of obtaining logcat and uploading it just to be ignored
Also, FWIW, I searched around this forum and google for a while before I started this thread precisely to avoid this situation.
Anyway from what I'm gathering, it sounds like maybe LOS 19 for this phone is not quite ready. I think I'll flash TWRP and go back to crDroid 7 for a bit. I might try one of the AOSP variants but I've always leaned toward the LOS flavors in the past
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved