Related
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!
Hey guys,
I use version 4.4.4-2015-02-18-jflte-NIGHTLY on my S4. Till this version updating works fine but now no updates are shown at the integrated updater. When I try to update by downloading the rom manually and flashing it with TWRP (2.8.4.0), I loose my IMEI and Baseband and have no connection to mobile network anymore. Restoring the backup let me use my phone again but updating my phone doesn't work.
I searched on the internet and found, it may be a problem with the modem and installing the modem after updating would fix it, but this solution didn't work for me.
Is there anyone with an idea what I can try?
Thank you!
The same problem
Hi,
I'm with the same problem that fukuk: I haven't had connection since February updates
I hope you can help us! Thank you very much for all your work
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Entropy512 said:
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Click to expand...
Click to collapse
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
jakew02 said:
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
Click to expand...
Click to collapse
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Same here I have this issue..
Still we wait for fix or explain how to fix it.
System and radio logcats from both a working and broken build would be useful, along with a dmesg
Also which exact jflte variant you have WHEN you post the logs.
The problem is, if you look through Gerrit's merge history, nothing was merged between February 13 and February 27.
The only thing that might have caused radio issues is https://gerrit.omnirom.org/#/c/11694/ - but that would've broken things on the February 14 build, and all builds from the 14th onward would be broken - but builds from the 14th to 18th are apparently OK?
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
alfayez0z said:
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
Click to expand...
Click to collapse
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
I have the GT-I9505 jfltexx, i will be glad to help if i can. I'm ready
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
jakew02 said:
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
Click to expand...
Click to collapse
Is there any update?
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Entropy512 said:
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
Click to expand...
Click to collapse
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
jakew02 said:
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
Click to expand...
Click to collapse
That's strange - how did it break on Feb 18 as opposed to some other time then?
I don't see any changes to qcom-common or msm8960-common for quite some time?
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
jakew02 said:
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
Click to expand...
Click to collapse
Yeah. Thanks for figuring out why it broke.
I still wish I knew how it was working from October through until the build server housecleaning in February, since it should not have been working.
Great, thank you!
When will it be possible to download it? Last available version is 2015-04-17.
Thanks you all, Confirm now it's working fine.
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!
Since the development thread is closed by OP request( sad but true ), and personally building a "port" of the ROM, i'm glad to help everybody as i can, with this thread.
It doesn't mean to be a development thread since i only build and implement some changes, but just to share comments, issues( like xposed one ) or just ideas to people who own this device ( CN or ROW ).
As a reminder you can find my builds here: LINK or just use OTA function in ROM.
And a big thanks to @frantisheq and @Electry for the works on CM13, and for the next, CM14.
reserved
Are someone try to flash Vibe Z2 (NON PRO) with this ROM?
don't do it, you will probably brick the phone.
K920/Z2 PRO only
Uploaded new build!
Should have Dec 5 patches, have a nice day
Try to install the latest build together with xposed. There is a boot loop with CM logo...... It seems to me there was such kind of problem......
That should be fixed by cm ? . Will apply the xposed fix in next build.
Thanks to inform me about this!
Tapatalk
updated build, with xposed patch, hoping now works fine
The latest build works fine for me. I installed it with xposed.
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Saamyo said:
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Click to expand...
Click to collapse
Could you please provide more details about this behavior and I try to reproduce it? Now I have not such kind of problem. But I can say that the UI sometimes has strange behavior. For example, the horizontal size of quick settings can be more widely than the size of the screen.
maybe it's something related to CM repo's and they will fix "soon".
give some days to see if they fix anything, i'll provide a new build.
In additional to my previous report I would like to add that the latest build cannot hold loading. At the previous build from 16 Nov I can run at the same time a navigation application and a video registration application. Now I cannot do the same because the device is rebooting due to overheating. I tried to figure out what is going on and found that the high limit of CPU0 temperature is set up to 85 C (it seems to me it is low....) and I cannot change it – try several tuning tools. And it is not only one reboot – there are several reboots….. After its a Bluetooth pairing was lost….. And I can repair a normal work only wipe cache & dalvik through TWRP and pair a Bluetooth once again…..
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
malaga82 said:
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
Click to expand...
Click to collapse
What information could I provide to you to help?
i just want to know if someone else have that overheating issue
Could you please prepare a build with "old" kernel? Who does not face the overheating problem can stay on the previous one
Solved games issue.
Hello!
Sorry for my English, I from Russia.
On roms later CM 13 2016.03.07 in file: build.prop, increase the value: dalvik.vm.heapsize= from 512m to 768m. This led to the errors in game Real racing 3 (insufficient free memory, missing textures, game crashes). With value 512m games work fine.
If install Adreno drivers from ROM CM 13 2016.03.07, game Gear.club also work fine. The difference can be noticed immediately after starting the game.
I also sent this message to frantisheq.
Happy new year!
Solved games issue.
Additional information to the previous post.
I was looking the file: default.prop, and the parameter ( dalvik.vm.dex2oat-xmx ) is set to =512m. System parameter ( dalvik.vm.heapsize=768m) overlap kernel parameter. Possible, if rebuild kernel with the value 768m, all be fine? I don't test this.
See: https://forum.xda-developers.com/g4/development/lineageos-unofficial-builds-h815-t3726177
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Wuddelchen said:
So, one can just flash this over the most recent official build, using e.g. TWRP? I mean, one doesn't have to wipe or anything like that?
Also, just curious, how much work was it getting from the last official to this, in terms of time spent "changing code"?
Click to expand...
Click to collapse
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Bleuzen said:
I think you can't flash this over the latest official build, because of the different signatures. I haven't tryed it, so I don't know, but I guess it won't work.
If you try it, write back if it works or not, so that other users know
I haven't changed the code of lineage, since it works so far without changes.
It is nearly vanilla lineage, just with updated:
- security patches
- features
- proprietary blobs
Click to expand...
Click to collapse
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Wuddelchen said:
Well, you can't flash over it, that much I can tell.
I just wonder how long the official build is gonna take, the phone is "new" (empty), but still, it takes time to set stuff up after a wipe...
Click to expand...
Click to collapse
Nobody knows. The bug exists since 2017-04-30, but nothing happens. And until the bug is not fixed, we don't get new official builds.
If you want to take the time to wipe and (re)setup your device is your decision.
But if you have the time, I would recommend it, mainly because of the security updates.
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
tulen_kobi said:
Do you know that I build unofficial? https://forum.xda-developers.com/g4/development/rom-lineage-os-14-1-lg-g4-t3704019
But we are now focused on Oreo. AOSCP is ready, I should have LOS 15 done in January. Do want to help us? We can add you to our telegram group.
Click to expand...
Click to collapse
No, I didn't know that
Uh, there is work going on? This is great! I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Great to her that there is still developing going on
Well, I help where I can. But I'm new to Android.
I have experience with Linux, use it every day, and now I know how to build LineageOS. I also can do Java programming.
But I never developed something with Android already. So I don't know how much I can help.
Bleuzen said:
I thought the device is dead, because nothing happens anymore on the LineageOS GitHub page for it. There is still no LOS 15.0 or 15.1 branch.
Click to expand...
Click to collapse
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Exabyter said:
I'm pretty sure that LG has announced they will release an official Oreo build for the G4.
Perhaps the LOS people are waiting for that to happen so they can use some of their sources as a jumping-off point for LOS Oreo? I got the impression that happens in some cases but I'm not a dev so not clear on the specifics.
Click to expand...
Click to collapse
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Bleuzen said:
Where did you read this? I never read this somewhere and I don't think that there will ever be an official Oreo build for the G4.
They not even bring Nougat to all G4s, why they should work on Oreo for this old device?
I think from LGs side, the G4 is dead.
Click to expand...
Click to collapse
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Exabyter said:
Hmm, perhaps I confused it with one of the other devices I had been investigating as a possible future project. (Eg, the HTC 10, LG V20, Moto Z, etc)
Someone in the following thread claimed it would happen for the G4, but others disputed it and a quick web search tends to reinforce that:
https://forum.xda-developers.com/tmobile-g4/general/android-8-0-oreo-thread-h811-t3680209
On the other hand, I think these people have released an Oreo ROM for the G4:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102
Click to expand...
Click to collapse
Yep, looks good. I already tryed Oreo but it isn't complete already. But I'm looking forward to use and recommend it as new daily driver when it's ready