Database Users

RK3066 (MK802 III) Flashtool and Android 4.4.2

Recently I found this interesting Tool ... and I successfully flashed "Allminipc_ug802_RT8188_4.4_720p.img" (Kitkat version) on my MK802 III using Debian Linux 7.5!
Regards, mistersixt.

In case someone is interested: I successfully installed the rk3066 drivers for WinXP using Moborobo, rooted the device with the kingo root tool, and I was able to installed the xposed framework 2.6, too, including XPrivacy, root cloak etc.
So I have a fully 4.4.2 running MK802 III with root access and Xposed framework!
Regards, mistersixt.

mistersixt said:
Recently I found this interesting Tool ... and I successfully flashed "Allminipc_ug802_RT8188_4.4_720p.img" (Kitkat version) on my MK802 III using Debian Linux 7.5!
Regards, mistersixt.
Click to expand...
Click to collapse
Very interesting..Any chance you could share the firmware image file and also let us know how has it been so far...is it fast enough and does the Wifi and Camera (UVC drivers compatible) work w/ this ?
Also could you confirm if this is for MK802III and not MK802IIIS...
Cheers

optimus975 said:
Very interesting..Any chance you could share the firmware image file and also let us know how has it been so far...is it fast enough and does the Wifi and Camera (UVC drivers compatible) work w/ this ?
Also could you confirm if this is for MK802III and not MK802IIIS...
Cheers
Click to expand...
Click to collapse
It is the MK802III, and the stick is running fast and stable. Wifi is as bad as with 4.1 ... but I think this is a general (or hardware related) issue, I am using it with a USB to LAN adapter anyway.
Concerning the camera I have no idea.
Regards, mistersixt.

mistersixt said:
It is the MK802III, and the stick is running fast and stable. Wifi is as bad as with 4.1 ... but I think this is a general (or hardware related) issue, I am using it with a USB to LAN adapter anyway.
Concerning the camera I have no idea.
Regards, mistersixt.
Click to expand...
Click to collapse
Hi,
Thanks for your response.
I've just installed this firmware on my MK802III and it seems no audio video app is working properly. Youtube does not show any video or sound. Neither can I play youtube in the browser.
No streaming media player works either. Only the local media files are playing properly.
The playstore seems to take ages to install apps because of speed, however when I check the internet speed using speed testing app it gives a good enough speed of 7Mbps.
Also i've noticed that there the wifi network connections are getting dropped abruptly. The wifi connection itself seems to be OK but connection from apps such as Airdroid drop out and upload from my local machine via Airdroid takes ages w/ speeds in Kbps.
Can this be fixed please.
Thanks,
OP

optimus975 said:
Hi,
Thanks for your response.
I've just installed this firmware on my MK802III and it seems no audio video app is working properly. Youtube does not show any video or sound. Neither can I play youtube in the browser.
No streaming media player works either. Only the local media files are playing properly.
The playstore seems to take ages to install apps because of speed, however when I check the internet speed using speed testing app it gives a good enough speed of 7Mbps.
Also i've noticed that there the wifi network connections are getting dropped abruptly. The wifi connection itself seems to be OK but connection from apps such as Airdroid drop out and upload from my local machine via Airdroid takes ages w/ speeds in Kbps.
Can this be fixed please.
Thanks,
OP
Click to expand...
Click to collapse
bumping this up..!

can confirm, that works great on Measy U2A.

MK802IIIs up and running
Works brilliantly on my MK802IIIs. Wifi is strong and Bluetooth works out of the box. Already rooted and CWM recovery installed. Now its time for some Xposed magic! Anyone has an idea which XBMC version will run best on this?

I'm using the ROM from this thread http://freaktab.com/forum/tv-player...73-full-1080p-modded-kit-kat-4-4-2-rk3066-rom
Super fast and stable, its like a new machine coming from the old JB ROM I had on there. I can actually use it now.
This ROM is for an Imito device but the MK802IIIS is identical hardware.
Few OC kernels in that thread to to play with.

ozzy lion said:
I'm using the ROM from this thread
Super fast and stable, its like a new machine coming from the old JB ROM I had on there. I can actually use it now.
This ROM is for an Imito device but the MK802IIIS is identical hardware.
Few OC kernels in that thread to to play with.
Click to expand...
Click to collapse
Hi,
The rom seems nice but I just can't get it to run correctly on my MK802IIS. I just flashed the rom on this thread (V 1.1 ) without flashing a custom kernel. Just flashed the entire rom. And after the first boot, I see the apps update (the optimization screen) and then I'm stuck on the screen where there is an Android icon on the top with a blue bar underneath. This screen just keeps blinking and seems to be impossible to pass. I can access the settings, but I found impossible to activate wifi or lan.
Ozzy, you seem to have a MK802IIIS, did I miss something during the flashing? Do I need to flah a custom kernel after flashing the rom?

Linkysly said:
Hi,
The rom seems nice but I just can't get it to run correctly on my MK802IIS. I just flashed the rom on this thread (V 1.1 ) without flashing a custom kernel. Just flashed the entire rom. And after the first boot, I see the apps update (the optimization screen) and then I'm stuck on the screen where there is an Android icon on the top with a blue bar underneath. This screen just keeps blinking and seems to be impossible to pass. I can access the settings, but I found impossible to activate wifi or lan.
Ozzy, you seem to have a MK802IIIS, did I miss something during the flashing? Do I need to flah a custom kernel after flashing the rom?
Click to expand...
Click to collapse
I just flashed the basic ROM with the unmodified kernel. I did try one of the OC kernels but it wasn't stable on my device.
The screen you mention doesn't sound familiar to me.
Did you do a full wipe?

ozzy lion said:
I just flashed the basic ROM with the unmodified kernel. I did try one of the OC kernels but it wasn't stable on my device.
The screen you mention doesn't sound familiar to me.
Did you do a full wipe?
Click to expand...
Click to collapse
Hi, thanks for your answer mate
Yeah I did a full wipe, that's why I don't understand what's happening to me. I see someone on the thread has the exact same problem, but doesn't precise on which device, so I preferred to ask you first, as we have the same device.
I'll just try the v.1.0, mabe that 1.1 version doesn't run on my key. Did you flash the 1.1 or the 1.0 ?

Hello
I know I am a bit off topic but this TV stick is based on the same CPU....Can somebody help me ?
I ordered this
http://www.ebay.co.uk/itm/Dual-Core...g-/111655649656?ssPageName=ADME:X:RTQ:GB:1123 and seller's understanding of the English language is very close to none
Can somebody tell me which webcam models does it support ?

I have just installed Allminipc_ug802_RT8188_4.4_720p on an MK802III. I have used it for an hour and installed all my apps etc.
Both sound and Wifi (Realtek) seems to work.

I've been using mine daily since I posted last time. It works fine except for some hick ups.
Sometimes during bootup it hangs with just 3 penguins on the screen.
And I'm running out of internal disk space all the time. I never did that on the official 4.2 even though I had many more applications installed then. Any ideas how to fix that?

Help please...
I have : BOARD
MK802IIIS
BOOTLOADER
unknown
BRAND
MK802IIIS
CPU_ABI
armeabi-v7a
CPU_ABI2
armeabi
DEVICE
MK802IIIS
DISPLAY
MK802IIIS-eng 4.2.2 JDQ39 eng.zs.20140312.150142 test-keys
FINGERPRINT
MK802IIIS/rk30sdk/rk30sdk:4.2.2/JDQ39/eng.zs.20140312.150142:eng/test-keys
HARDWARE
rk30board
HOST
hotack-desktop
ID
JDQ39
MANUFACTURER
rockchip
MODEL
RKM MK802IIIS
PRODUCT
MK802IIIS
SERIAL
FKO0EQZQGR
TAGS
test-keys
TYPE
eng
UNKNOWN
unknown
USER
zs
CODENAME
REL
INCREMENTAL
eng.zs.20140312.150142
RELEASE
4.2.2
SDK_INT
17
Its rooted just need to know how to UPGRADE THIS TERRIBLE DEVICE....

Tab P6800 need radio module

Hi all.
I use omni-4.4.3-20140607-p6800-HOMEMADE.zip, 6-2_GApps_Standard_4.4.3_signed.zip and cwm-6.0.2.3-p6800.tar over Odin3_v1.85.7z.
So, my tablet now work with android 4.4.3 but radio module isn't work =_= I dont have a tablet for LTE, so, as I think, a troubles from i815 was not happend to me. But in options i see that radio module not present.
May be someone know where I can take radio module and how I can paste it to the tablet?
Thanks.

admhome said:
Hi all.
I use omni-4.4.3-20140607-p6800-HOMEMADE.zip, 6-2_GApps_Standard_4.4.3_signed.zip and cwm-6.0.2.3-p6800.tar over Odin3_v1.85.7z.
So, my tablet now work with android 4.4.3 but radio module isn't work =_= I dont have a tablet for LTE, so, as I think, a troubles from i815 was not happend to me. But in options i see that radio module not present.
May be someone know where I can take radio module and how I can paste it to the tablet?
Thanks.
Click to expand...
Click to collapse
See that HOMEMADE in the string? This means you are running an unofficial build. P6800 is not an officially supported device, take this up with whomever created the build.

[Q] Galaxy s4 I9505 with Google edition andriod

Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan

dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan

dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.

[Q] Support for LG G3 with Cyanogenmod 12?

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!

[Q] Stock Cam on LineageOS 16

Hi,
I try to find a way, where I could install the Stock Cam from OnePlus5 to my LineageOS. I 'm not sure, but I think this must include also some Libs?
For the moment I only find articles for GCam or others, but the Stock Cam was not findable for me. So I would like to ask, if someone has experiances with that, or maybe put me to the link where it is explained (as I was maybe to tumb to find it )
Thanks in Advance!

As no Answers, I research further, and give here some infos, if others search for that also:
- It is possible to install the stock cam without additional things (like root or whatever) by downloading it from apkmirror
- link: https://www.apkmirror.com/apk/oneplus-ltd/oneplus-camera
- take care, it seems on OnePlus 5 not all versions running properly. The last real working version under Lineage OS 16 for me was 3.4.25
- I tested several versions of 3.8, where are on each app other problems (app crash, not choosable options, and so on)
- The link to standart Gallery is not working (I expect that the cam app assumes to open the oneplus galery, but I have others)
- you can test Versions by starting in a low version, then you can update to newer versions. The other direction (starting with high version, and downgrade is only possible by deinstalling the newer version).
- If I foud a stable 3.8-Version I will notice it here (3.5, 3.6, 3.7 are not on apkmirror, I assume that the big version-change is related to also other hardware needs for the cam, so this will cause maybe the problems...)
BR
MP

similar story and solution here:
OP Camera version 3.0.43 (I may try the suggested v 3.4.25, if I find time)
OP Gallery version 3.8.21
Do you have any gapps installed?

androidtel said:
Do you have any gapps installed?
Click to expand...
Click to collapse
Yes, I'm bad and use the most of Gapps
Anyway, maybe the point that 3.8 does not work could be related to Cam Framework which maybe must also updated... but on apk mirror only V1 is avalible... But I'm afraid to change something there on the Rom included stuff, as I need my phone running...