Related
Hello,
Firstly, I want to thank and congratulate Quarx for his incredible work on the development of OS of our "old" Defy
I installed yesterday CM10.2 -nightly version of March 2, 2014.
After "testing" many ROMS CM10.1/CM10.2/CM11 I think keeping this one because it seems really stable , fluid and reactive .
So far , no reboot "telephony problems" , no slowdowns , no memory saturates everything seems functional and operational.
I have not yet tested the GPS
The battery consumption seems more than adequate ( - 35 % in 9 hours with WIFI and 3G enabled and disabled GPS).
First question:
Why New ' CM10.2 -nightly ' are not detected in the "update Cyanogenmod " menu (as in CM11 ) ?
Is it a bug or is it due to the lack of incrementals for CM10.2 ?
One last question
Why some applications from Google PlayStore are no longer compatible with the defy + in CM10.1 or CM10.2 while they were under CM9 or CM10 ? (Iron Man The Official Game , for example)
thank you for your answers
Sorry if my English is bad, I used a translator ...
Glad you found a ROM that works for you... That's because official support has now moved to CM11. Since that is the new way forward.
A.K.A. 4.4.x
Battery drain sounds fair. If you intend to preserve battery some more switch 3G off or move to 2G. Just a suggestion.
valhallen.282 said:
Glad you found a ROM that works for you... That's because official support has now moved to CM11. Since that is the new way forward.
A.K.A. 4.4.x
Battery drain sounds fair. If you intend to preserve battery some more switch 3G off or move to 2G. Just a suggestion.
Click to expand...
Click to collapse
thank you for your answer and also for the tip 3G / 2G : Bien:
Q&A for [ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2
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][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2. 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!
Kosh_swe said:
Cm10.2 is all BUT stable! ...
My hardkeys (back/menu/home) stopped working ONLY on flxo/Vanir firmwares, ive tried both cm10.2 (20140204_cm_10.2_skomer-ota-eng.flx, which is supposed to be "rock solid", i dont want nightlies since this phone is going to my gf so im after a stable firmware) but i've also tried latest nightly vanir 4.4 but that got the same bug in it!
...
Click to expand...
Click to collapse
@Kosh_swe, have you found a solution? I also failed to get the Vanir ROM to work and I'd consider the flox CM10.2 ROM. Your post suggest that my radio would be dead in flox, too.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
Matt64 said:
Hey guys,
I recently compiled flxo CM11.0 rom with STE OMX support (from TeamCanjica).
I've been testing it for a couple of weeks, for me everything seems ok (no reboots, camera working ...)
I didn't test bluetooth hand's free, but it's certainly still broken.
You can download this rom from my dropbox account :
xxx
I'm also trying to compile Ubuntu Touch for S7710, I'll let you know when the rom will be flashable.
Click to expand...
Click to collapse
@Matt64, could you provide a hands-on on how to do the compiling?
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
Testing radio issues
Hi to all,
I just tested radio issues on my phone. I was researching, why radio is not working.
Here are results, maybe it will help. Anyway, I have my GT-s7710 for testing and I can do some tests or catch some debug informations if needed.
It seems that problem why radio is not working is located in modem-supervisor process. In original firmware, this process is responsible for uploading firmware into dbx500 platform chip. But in CM, there is no such process.
I am not expert, but it seems to.
I tried to use old modem-supervisor process to make everything working.
Services line from original fw:
Code:
service modem-supervisor /system/bin/modem-supervisor -r -f /dev/dbx500_mloader_fw -i /sys/devices/platform/ab8500-i2c.0/chip_id -c monitor -t 0
but it needs to be changed because /sys/devices/platform/ab8500-i2c.0/chip_id changed to /sys/devices/platform/ab8505-i2c.0/chip_id
Problem is that firmware event for loading firmware is never generated and firmware is not uploaded.
I have some dumps and traces if you need them. Thank you for your work!
Lukas
loneraver said:
I tried it, and got none of the "known" issues. Give it a try. If you get any issues, you can always flash back to stock rom.
Click to expand...
Click to collapse
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
if you have a real headset - please try with that one again and tell me
an idea
The 7580's phone hardware is almost identical to the 7710. The processor in the 7580-higher heights, but the hardware buttons and then there are all of the functions, but it has the 4.2.2 firmware, which allow moving to the SD card. Somehow it should possess to operate from 7710.
I'm Hungarian, sorry if the translation is wrong, happened with google.
Okay so I am having the same problem with HW buttons as many others before me...
http://forum.xda-developers.com/showpost.php?p=51234756&postcount=329
http://forum.xda-developers.com/showpost.php?p=51253847&postcount=333
http://forum.xda-developers.com/showpost.php?p=54973574&postcount=362
Click to expand...
Click to collapse
After clean 1st boot after the installation the buttons are working perfectly, but after reboot (2nd boot) they are not working properly. Only long presses are working (google search by long press of menu button, kill aplication by long press of back button, last apps by long press of home button).
So? There is no such responde on how to fix that..!
DaGrizzly said:
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
Click to expand...
Click to collapse
In my cited post I refer to a previously made post where I listed the devices:
loneraver said:
I tested it with logitech ue9000 and samsung hs2000.
Click to expand...
Click to collapse
Both are real headsets with working mics.
Know it's OT but if it's true it's exiting:
Miui for our phone coming?
http://forum.xda-developers.com/showthread.php?p=58720490
Sent from my GT-S7710 using XDA Free mobile app
Sent from my GT-S7710 using XDA Free mobile app
Try other
this one is very very STABLE :
http://forum.xda-developers.com/showthread.php?t=2689010
XCover 2: BT hands free - Problem fixed yet?
Hey developers,
I was wandering if the BT problem has been fixed for Cyanogenmod Version 10.2 for XCover 2.
BT hands free. Connection/pairing works, but the audio path is broken.
Thanks a lot!
baseband wipe
I can't get Cyanogenmod 10.2 working. Everytime installation wipes my baseband.
When I install the Stock ROM SIM works again - but after flashing CM again also wipes baseband again.
My Installation-Tools:
Odin v3.07
CMW: 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
CM: 20140204_cm_10.2_skomer-ota-eng.flx.zip
Is there any chance to install the baseband (I think it's inside the modem.bin)?
No network available in Polish Play
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
sk_8x said:
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
Click to expand...
Click to collapse
Forget CM en try Vanir or MIUI these are more up2date. Also CM11 is alpa with camera bug:
First look at: http://forum.xda-developers.com/t/xcover-2
Vanir
Second, I use Vanir 4.4.4 daily. It has some bugs, but not some bugs that makes it unstable. Known issues:
Start/Stop navbar after every restart
Use this solution to fix connection errors after a fresh Flash: http://forum.xda-developers.com/showpost.php?p=60411469&postcount=612
Other small bugs:
2G/3G quick setting and normal settings dont work properly because of absence of LTE
Navigation Ring and immersive mode causes dead touch screen space
DSP manager doesn't work
After using Vanir 4.4.4 I never want to go back! It's that much faster, more free RAM en better battery performance. Because of the better RAM performance, you must kill apps more often else it will drain the battery quicker :silly:.
Best way to Flash with 4.4.4 is to first flash Clockworkmod through ODIN, then do the usual Full Wipe --> Wipe Cache --> Flash Rom --> Flash GAPPS. Here is a video of someone doing these things. P.S. in this video the process is speeded up also reboot can freeze the system (just remove battery after a couple of minutes)
Files
Vanir: https://drive.google.com/file/d/0B7agwkTbiz0pNHZMQlpudkR4NUU/view
GAPPS: https://mega.co.nz/#!kokjzJwT!eqmMam5r5N2kWvtmSMy4QnaHnxvoqhDtr_joSDU5anI
MIUI
Another option is MIUI (used on the the popular Chinese Xiaomo phones). Instead of the Vanir build, this build is still being maintained. But because it's based on Vanir it has most likely has the same bugs. Never tried it because I prefer stock Android.
2nd, the connection error fix for vanir could also work for CM (vanir uses stuff from CM).
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Yup, i confirm, doesn't work on lg g3. Pitty.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
WOW great news!!
Thank's very much :victory:
mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:
Any progress ?
ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/
Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!
When Moto X Play is getting official CyanogenMod 13? Any updates?
Nitish247 said:
When Moto X Play is getting official CyanogenMod 13? Any updates?
Click to expand...
Click to collapse
Probably never. Does it matter? No, not at all. What is better about an official version compared to the unofficial? Nothing at all.
But why? Any specific reason? All Moto phones till date have official CM.
It's my understanding cm13 will turn official some day.
Nitish247 said:
But why? Any specific reason? All Moto phones till date have official CM.
Click to expand...
Click to collapse
If you are following the cm13 thread then you would know that squid has told that he would push for the cm13 build to become official but there is no estimated time.
Sent from my XT1562 using Tapatalk
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Great news. Laud your hard work have a great year ahead squid2
Sent from my XT1563 using Tapatalk
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Thanks! Thats' awesome! :good:
We expect lux on official CyanogenMod list soon
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
I tried the version from the 25th of December, and I don't have any issue with it (I own a dual sim xt1562) and only have one sim inserted, but just after the boot I was prompted for the pin code. So I won't be of any help...
I'm running the 24.11.18.lux_retasia_ds.retasiaall.en.03 retfr version as my main version, so all my partitions were updated to 6.0
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
Wouldn't bother trying it yet; leave it to devs, but if you want the updated one is here https://androidfilehost.com/?fid=24727369092696651 thanks to codeworkx and genesixx
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
bangishotyou said:
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
Click to expand...
Click to collapse
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
CraigHardy said:
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
Click to expand...
Click to collapse
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
ashtreylil said:
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
Click to expand...
Click to collapse
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
AngryManMLS said:
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
Click to expand...
Click to collapse
i thought i was forgetting something, thanks:highfive:
[ROMs] Source for LG H811 (T-Mobile) CM-14 Nougat
I have begun building CM-14 (Android AOSP 7.0.1, Nougat) for H811 and will post ~weekly builds here. The builds are from the CyanogenMod and Muppets (vendor proprietary) sources on github. This I will do until a developer at CM takes on the task of creating official "nightly" builds for LG H811 CM-14.
Please report problems here and I will forward them on to official CyanogenMod devs.
2016-10-04: Don't expect great things right away. On first builds the phone app crashes continuously and it will soak the battery dry in a few hours.
2016-10-07: The build today is working relatively nicely. Earlier problems may have been partly my error. I've been running today's build all day without major problems. Battery drain is higher than CM-13.0 version but not terrible. I'm planning on running this ROM over the weekend to see what bugs pop up. Only two so far – the external sd access as reported earlier; and flakey navigation button editing. Give it a try!