Develop Bugs

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74

I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!

Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?

bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.

fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.

I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4

Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!

I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app

If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app

I am definitely willing to help in any way I can.

I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...

grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.

Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?

mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.

Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.

JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?

droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source

JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!

Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.

Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

CyanogenMod versions for Wildfire S

Hi,
I am really full of compliments about the good work of some guys that have done a good job in building the actual CyanogenMod versions for Wildfire S.
Thank you sooo much!!
But what I currently do not completly understand...
Why are most of the CM users really happy about version 10.2 or version 11.0 (like orig. CyanogenMod or WFSY) when those versions - last version of CM 9.2.2 included - do not even have GooglePlay/PlayStore and Data2SD (or Link2SD) installed?...
The last (and obviously most advanced CM version) CM9 (alpha9, v.9.2.2) would already be a wonderful solution for the WFS phone (I tested it!!) and it is said to be nearly finished (even video camera is working now at the version of Olivier) BUT both mentioned, absolutly necessary components are missing (and nobody mentioned it yet). Or what can I do with a phone where I cannot install new apps at all?..
So what is it that I misunderstand?...
I would be very happy if anybody could inform me about how I can find a version that has a complete set of system apps or how/where I can find both missing components to complete them by myself. (and even more happy if the cyanogenmod update function would still find some updates)
Otherwise I would guess that not any of the existing CM-based versions for Wildfire S can be used at all...
Should all the past work for creating a CM version (Android 4.x !!) for the (unfortunately!) one and only COMPACT smartphone on the world, 'Wildfire S' (I must admit, it is in fact!!) should have been completly in vain ???... I couldn't believe it.
Thank you guys very much for your nice explanations!
All the best to this wonderful community,
from Falk

CyanogenMod said:
Google Apps are the proprietary Google-branded applications that come pre-installed with most Android devices, such as the Play Store, Gmail, Maps, etc. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately.
Click to expand...
Click to collapse
Gesendet von meinem Xperia Z mit Tapatalk

Hi Olivier,
many thanks for your tip. You did not mention the point directly but I could answer most of my questions by mayself then.
Now I installed CM9 'cm-9-20140720-Olivier-marvel' together with 'CronMod-INT2EXT+_signed'. Works pretty fine!
Only little questions have been left now...
1.) How can I sort my app icons by subjects/folders (s. HTC Sense)? This Trebuchet launcher does not seem to support anything like that. If there is no chance, which launcher would you suggest instead?
2.) There is no really 'useful' version of CM10 or CM11 for WFS yet, is there? I couldn't find. Do you think there will be s.o. still working for a final version next time?... (why is Wildfire but not Wildfire S an official CM development?)
2b.) At your current version CM9, is there any problem left that should still be fixed? Everything works fine here yet...
3.) Therefore the OTA updater for CM would be a fine feature like in CM9 vers. 9.1.0 (but no updates found yet!). But your current CM9 version does not support it any more. Any reason for that?
3a.) Are updates possible anyway without flashing the whole ROM?
3b.) Is there anybody managing OTA any update of CM (v. 9..11) for WFS?
3c.) Are OTA updates from cm9 to cm11 possible?
4.) Skype does not react when clicking the icon to start it. Any idea what is the problem?...
5.) Some system programs (e.g. contacts or call manager) do not have that nice design than before. There is no chance/choice to exchange them?... (if yes, how and where to find alternatives?)
Thank you again for your final responses!

First of all this really does not belong in the development section, in Q&A perhaps.
And you just can't ask every single think that comes up in your mind, you gotta search a little bit and try it out for yourself.
Now, 1. Trebuchet does support folders but not auto-arranging. Most of the popular launchers support this.
2. The current CM10 and CM11 are perfectly functional and working. Though they lag a bit (which is fair considering our old device). And the wildfire only had an official CM7 which is very old now.
2b. If you don't have a problem it does not contain a problem.
3. OTA is working for CM11. But for CM9 a OTA makes less sense considering that its stable now.
4. No idea.
5. Again you have to look for yourself, nobody can babysit you all the time.

thanks very much!
Okay, maybe question 1 might belong to Q&A. That's it. Sorry.
To make you understanding (sorry to write again so much!)...
to 1.) Did not expect that it would support it. So I did not even search for!... Thanks, this drag/drop solution is more than perfect!!
to 2.) Sorry, then I am not able to find them. I searched a lot and found actual version like 'WFSY11.0-WFS-V5.5, 20140723' or 'cm-11-20140726-NIGHTLY-marvel' where not even back button or Android option menu worked. Lots of functions are missing. I did not try 'cm-11-20140810-NIGHTLY-marvel' but do not expect more within one month. The same with cm version 10.2. In a thread I read that it was give up because cm11 is already working better.
**** So would you please give me the link to the finished versions of cm10 and cm11, please? ****
(a patch for the video camera problem seems to be existing shortly now...)
to 2b.) My first problem I saw was missing updater in cm9 for version 10 and 11. And the strange Skype problem. And video problem was fixed JUST before!! BT seems to have restrictions as well. So there is good reason to ask this question!?..
to 3.) It seems as if simple updating from Android 4.0 to 4.2 (cm10) and 4.4 (cm11) isn't possible!?... Officially it seems to work. E.g. OTA of Samsung offered update from 4.2.2 to 4.4. Strange!... How/why does it work here?...
Remark: So I suppose it is CyanogenMod which does not support it... It will not work without 'Titanium Backup' here...
to 4.) I suppose you will have the same problem!? Maybe you have opportunity to try out quickly!?... Skype really does not seem to run on WFS cm9+INT2EXT+. Isn't that strange?... (I reinstalled it already. No chance.)
to 5.) I asked this HERE because it belongs to SYSTEM apps (contacts or call manager) that cannot easily be exchanged, as far as I know!... Can they?...
There is one thing I would like to add, after your remarks to my point 2... Maybe I could not find the right sources. But this is because there is no resource pool (about WFS at XDA anywhere. Instead there just appear 'lonely' links in some threads. And instead of telling/explaining the systematics (if there is one) you guys generally just mention the fact (e.g. a link). So this makes it hard for non-insiders. You understand what I mean?...
(so e.g. I will have to ask (in another thread) how I can find the 'FM radio' app (no streaming!) which is missing in CM9 - instead of just looking at the right page where they are collected)
I would be really happy to get to know at least where you guys have found the informations for all what you do when 'cooking' new versions, etc.!...
Cause then I would have read about all that much more!... Instead of blaming me. Sorry, if I do not have that general info that you got already.
Maybe you understand better now!?... Would be fine.
Anyway, thanks a lot for your short repsonses. Have a nice day!

Again only things that are directly related to development are to be placed in development section. And NO if you have a problem with a rom you have to ask it in Q&A. Read the development forum rules in the stickies attached to the top of the section.
And you could also try reading through the stickies in the general section. It will give you some understanding.
Now CM10 and CM11 works, the threads are pretty high in the development section, you can find them if you look. The version of CM11 you used is the right one (the NIGHTLY) and back button does work. Try the later versions. Officially updating to a higher version is different and large corporations can spend time and money to make it work. But it just is not possible (or rather safe) with the variety of unofficial roms. You could try but most probably fail. You can install different apps for call and messaging and they will work. Search for those apps. CM9/10 works fine and have very less amount of problems. Now remember that this is a very old device and the devs are doing it NOT as a profession. So every single thing will never work.
Now as a last your largest problem is you think everything will be written somewhere in front of your eyes. It will not be. You have to use Google before asking a question. And also you just have to calm down and fix your attitude.

aWFSuser said:
First of all this really does not belong in the development section, in Q&A perhaps.
Click to expand...
Click to collapse
That was my fault, I'd moved this out of a thread and mistakenly put it in the Development section. All sorted now.

thanks again for your time to answer!!
I know, I sound as if I would not know which hard work you guys do. But I do, aWF Suser. And I mentioned that already in the beginning.
And I have heard already from your collegues that it would be a good idea if things could be organised some better. The official cm versions e.g have a central resource pool. Or the android-Wiki and CM-Wiki notes are all out-dated (from 2012) !!... Etc.
But PLEASE understand this more as a suggestion than a criticism - from a user that in your eyes only expects and criticises but cannot give. This is not the case!
Thank you!
I know it is an old smartphone I have. And I would have bought a new one already a long time ago. But even Samsung Galaxy Mini is too big in size and some important functions you will only find in the big version. Why is that so? Nobody can explain!... (i would pay the same price for a small phone!!! Handy devices must not be worse and more expensive than big ones!!)
The WFS is just the only really COMPACT smartphone all over. And I am sad that the industry detected a trend to bigger displays. The opposite is the trueth. Nearly all my friends e.g. like to have a compact phone but those always a beginner versions/hardware which cannot be understood at all.
Really sad. It is a big strange hole in products on market, isn't it?...
Unfortunately you did not give me tips how I could find a way to get more familiar with what and how you guys are doing. Is it a secret? I could imagine to do some work here as well. I am very interested in how you are doing your development work!...
Thank you again...

Now it is sure...
Olivier's last CM9 version still has bugs, not only the problem with lgCamera and Skype but also at the akku loading status.
It seems as if it is not correctly refreshing. The loading curve (s. settings) slows down a lot and shows e.g. after 4 hours loading still 43%. But after rebooting it changed to the right value finally: 100%.
So again my question before, as Olivier unfortunately put away the OTA update function (but ment that it is not necessary anymore):
How can this version be fixed?
As far as I know you don't offer patches but only complete ROMs...

Okay first sorry for being rude as posting in the development section was not your fault.
Now the main problem with our device is not that its old but that it has a armv6 cpu which is not supported by later android versions. So development for developers is tougher and bugs will remain. I mentioned the general stickies before there you can find some useful guides.
And have you installed GAPPS in CM9 because some apps depend on it and won't work without it.
And just to be clear, I'm not really a developer but just a user like you.

I never said CM9 doesn't have bugs. It's is clearly stated in its OP that:
modpunk said:
This ROM is not meant for daily use!
Click to expand...
Click to collapse

Hallo Olivier,
never mind. But I just understood it like that. As you gave the reason for the OTA non-support in your ROM.
So if I misunderstood you... what is your reason then?...
In fact it would bring us forward if you could please comment my questions and/or give tips to solve the mentioned problem.
@so please give me a chance to fix the akku status bug. This is really annoying.
Can you confirm that problem? And if so will you fix it?
And if so how can I update it by OTA updater? Or alternatively at least by a patch but not by a new complete ROM !?...
@TO the Skype problem...
First of all: can you confirm my problem?...
To your question: I used your ROM from 20th Aug. (119.518 KB) This one contains already gapps, I suppose. Cause Google Play and the other stuff was already installed!...
@TO lgCamera...
This wonderful camera app worked fine with EQDKP (v.2.3.5) but now it is too slow and hops a lot. Can you confirm that?
And if so do you have any idea why this is a problem?...
@how can I add FM Radio (analog) support?...
Thank you very much for your feedback!
PS: So if the last version of CM9 is not ment for daily use... which CMx version is it then? Is there none?...
Currently your cm9 works fine. Only those three problems so far...
Do you care for my bug messages?... (or where can I post them?)

Hallo aWF Suser,
yes, I know the problem with the arm version. You must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or errors are not heard or cared for so that bugfixes will not be available at all...
By the way the phone Wildfire (without 'S') is supported by Standard CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. previous message) obviously contained GAPPs already. GooglePlay atc. was already installed. So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems when flashing ROMs. For nearly each ROM I have to change the recovery. Is there any that can read all 'formats' of zip files?...

Falk2 said:
Hallo aWF Suser,
yes, I know the problem with the arm version. So you must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or bugfixes are not available at all...
By the way the phone Wildfire (without 'S') is normally supported at CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. next message) obviously contained GAPPs already. GooglePlay atc. was already installed.
So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems with ROMs. For every second ROM I have to change the Recovery. Is there any that can read all 'formats' of zip files?...
Click to expand...
Click to collapse
The Wildfire is listed officially only for CM7 (gingerbread) . After that it has not been supported. I am not asking you to read the rules, in the stickies in general section there is a thread that lists some guides to some useful things. And is OTA that necessary because in most cases a dirty flash is enough to upgrade from one version to another as long as its the same android version. Upgrades between different android version would not be possible even with OTA (as lots of things change, it will probably end in a bootloop). I am not using CM9 currently so can't speak for that.

So then which CM version are you using on your WFS? And why?
I flashed cm11 shortly but it still has too many problems. E.g. the camera app crashes after successfully recording a video, the launcher only has two pages, launcher does not seem to support folders, etc.
Do you know where I can find the actual todo list? (AndroidWiki unfortunately is not maintained anymore!)
I will give Paranoid 4.45 a try yet. Maybe this is better!?...
Otherwise I will keep cm9 and hope that we can find out why Skype is not running.
Oooh, that is important... I can make a 'dirt flash'? This is very fine!! Then OTA is not that necessary, of course. But there is still no reason to left it away, is it? Especially because all this observing and searching for the update is NOT necessary! Can't understand Olivier here...
Could you comment my PS as well, please?...
(error log: "cannot load volume /misc. Can't partition non-vfat: /sto .. (vfat)")

http://forum.xda-developers.com/htc-wildfire-s/development/cyanogenmod-10-t2908631
is there any better rom than this rom? how can i improve battery life with screen on? i want it for daily driver, i do not use bluetooth ad2p but i dont know what armv7 features means...
for me its affordable atm and give a new life to the oldie and shiny wfs

Which rom is the most stable for everyday use?
(With working wi-fi tethering)

P605 - cm13??

Hi,
Anybody has any information about this --> http://www.cmxlog.com/13/lt03lte/ ??
OMG.

Oh man, i am envious on p605, now. I hope p600 will also get official support with working camera and screen mirroring...

Issues
itsita said:
Hi,
Anybody has any information about this --> http://www.cmxlog.com/13/lt03lte/ ??
OMG.
Click to expand...
Click to collapse
It is great news.
I tried 25.03.2016 nightly as I wanted to have some themes on my Tablet. Here are some issues I encountered.
Sim card was not recognized.
Gapps setup failed to start and showed error.
Others I could not test as I was unable to move forward from setup error.
I am back on AOSP 6.01. Works great, rarely display driver fails.
Will try in fortnight time, may be remaining bugs will squashed by then!

drchohan said:
It is great news.
I tried 25.03.2016 nightly as I wanted to have some themes on my Tablet. Here are some issues I encountered.
Sim card was not recognized.
Gapps setup failed to start and showed error.
Others I could not test as I was unable to move forward from setup error.
I am back on AOSP 6.01. Works great, rarely display driver fails.
Will try in fortnight time, may be remaining bugs will squashed by then!
Click to expand...
Click to collapse
Thanks for testing!
The gapps issue is known for all CM devices right now so hopefully it will be fixed soon.
For the sim issue i saw some ril patches merged today so again i guess it's not device specific
I looked through the git of the developer who merged our device and it looks promising... he merged all the sources from the last p607 5.1.1
Wish we could thank him!
Sent from my SM-P605 using Tapatalk

CM13 2016.03.30 Nightly Test
itsita said:
Thanks for testing!
The gapps issue is known for all CM devices right now so hopefully it will be fixed soon.
For the sim issue i saw some ril patches merged today so again i guess it's not device specific
I looked through the git of the developer who merged our device and it looks promising... he merged all the sources from the last p607 5.1.1
Wish we could thank him!
Sent from my SM-P605 using Tapatalk
Click to expand...
Click to collapse
Experience of latest Nightly 30.03.2016
Sim Card does not get recognized.
I got the Gapps working by following this method http://forum.xda-developers.com/showpost.php?p=66094943&postcount=207
Gapps used were http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
OpenGapps does NOT work.
Super User and Xposed Works well.
Themes work.
I am using it for last few hours. ROM is stable and just works except telephony.
Looking forward to have working Telephony!
Thanks to CM for supporting our Note.

Awesome, i will start to test soon as possible

Experience on Update 04.04.2016
Telephony is still working for me. (sim card is not recognized).
I have reverted back to AOSP Rom P605 http://forum.xda-developers.com/galaxy-note-10-2014/development/rom-android-6-marshmallow-t3254901
I wanted themes on my tablet, so tried this Layers Manager https://play.google.com/store/apps/details?id=com.lovejoy777.rroandlayersmanager
It works well on tablet. But before Layers Manager is installed Tablet has to rooted and Busy Box installed. I used this busybox application. https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Layer themes can be seen here http://forum.xda-developers.com/android/themes/0-themes-official-mega-rro-themes-t3011075
Hope it helps.
For time being I think I would be staying on AOSP.
I hope it helps!

SIM does not work
I install CM 13 on my P605 but my SIM card is death and I lost my IMEI

As we all are encountering the same problem with the SIM card I guess I can conclude it's not because of some stupid mistake of mine
But where can one report bugs in the nightlies? The cyanogenmod JIRA says very clearly that no Nightlies bug reports are to be added to the CYAN project and the NIGHTLIES projects only accepts regressions from the last snapshot... So where to report bugs like ours?

Does cm13 support ntfs filesystem for micro sd-cards?

Yesterday install the version of 13th and I was surprised functioning for good , is the rom less lag 've had in this tablet.Parece the rom progresses quickly , I hope that is compatible soon with Screen Mirroring, S Pen, SIM card and SD Card as it will be the best ROM by far above the rest ...
No choice but to wait a little longer , sorry for my English and because there is already an official thread at XDA ? ...
SL2

Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?

OlafLostViking said:
Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?
Click to expand...
Click to collapse
I installed it yesterday - it was working surprisingly well. From what I could tell, it was working except for the following issues:
1. Can't remap the 'menu' hardware button
2. Camera not working/installed
3. Sim card not working
External SD card, wifi, google apps etc all working nicely.

OlafLostViking said:
Any news about the SIM card issue? Is anybody here using the LTE successfully his/her lt03lte with CM13?
Click to expand...
Click to collapse
I did a clean install of the cm-13.0-20160426-NIGHTLY-lt03lte.zip build but unfortunately the SIM card is still not recognised [emoji22]
Had a brief play and found it running smoothly but I need the SIM to work so it's back to AOSP 6.0.1 for now.
Sent from my SM-P605 using XDA-Developers mobile app

Tried a clean install of the 20160429 Nightly... still no SIM card detection chaps... wonder if @Schischu has committed any of his RIL work to their builds?

I have tried this ROM (cm-13.020160501-NIGHTLY) nothing majorly wrong with it except:
1. I don't have a sim card to test 4g/3g connectivity, so can't test phone/message/GPS functions as well. So these parts are unknown.
2. The quick view drawer (in home screen when you hold from top and swipe down to bring out system/profile/recent notification drawer), it display nothing except basic information like time/date profile head bubble. It will not display ANY notifications even you have new email etc. It always display "No notifications"
3. No lock screen, at all. So you can't preview any information like above. When you press home button it brings up your home screen straight away. If you have pattern lock / pin lock, yes you will have a lock screen normally, however again it will not have any notifications even you have new ones.
4. No USB connection option. On my Oneplus One (bacon) with CM13, when you connect USB cable to the PC, you can choose USB function from "charging" to something like "data transfer" etc. However, on my P605 (lt03lte) it displays nothing (since it can't display any notification). Even after enable USB debugging mode (which is called Android debugging in CM13), enable Debugging notify, changing "Select USB configuration" from "charging" to any other modes, none of above work. This is huge problem for me because this simply means I can't transfer any files from my PC to tablet and the mirco sd card.
5. For some reason all data from my micro sd card are not accessible, or I should say are not naturally supported. When you try to view eg. photos from micro sd card, and open "Gallery" provided, it will shows "0 images/videos available". However, it can be accessed when you go to Settings>Storage & USB>Portable Storage and you will see the micro sd card there. So you can copy files from system storage to micro sd.
6. It takes longer time to boot up compared to my Oneplus One and will have completely black screen (scary long waiting time, estimated about 15 seconds long) when you downloaded and flashed newer ROM. So be patient if you are updating. I experienced that "black screen" every time when I update my ROM or reinstalling through TWRP.
7. Camera not working, not a big issue for me but maybe for some people.
All processes I never experienced any softbrick.
I am not sure if it is just me or everyone is experiencing the same things. I will be glad if someone could point me the right direction to fix any of the above issues...
Other than above it is an awesome ROM, definitely cleaner compared to stock ROM.
If you wish to update to Marshmallow on your P605, I strongly recommend Schischu's Marshmallow ROM from xda-developers. (Google search: p605 marshmallow) It is very stable for me and seems no faults.
I am currently still sticking with "cm-13.020160501-NIGHTLY" ROM and hoping it will fix above issues when updates,
Feel free to ask me any questions,

im finding that i lose root when i upgrade everytime. and when that happens, if i charge with the device and switch it off, the battery icon stays there without disappearing

Ikaruga 斑鳩 said:
If you wish to update to Marshmallow on your P605, I strongly recommend Schischu's Marshmallow ROM from xda-developers. (Google search: p605 marshmallow) It is very stable for me and seems no faults.
Click to expand...
Click to collapse
While I agree that Schischu did good work you should mention that some things aren't working with his ROM, either. My main problem is encryption, for example. The CM is the very first custom ROM I found that is capable of encrypting the tablet (mandatory for a mobile device with personal data of me and other people, in my opinion).

With this rate of updates, soon we will have the best and final rom for our tabletas.He tested rom Schischu , but CM works much the better.You you need to solve the SIM , SD card and S Pen.Solo have to wait , yours would that opened in an official XDA thread to be attentive to feedback from users who are testing ...
SL2

Edit:
This is our maintainer! @Rashed97
Hi Rashed, above are some observations regarding a few bugs in the ROM, which i guess you are aware of.
Thank you for your work!

[ROM][P905][UNOFFICIAL] LineageOS 15.1 | Android 8.1 Oreo 20180708

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Links
LineageOS Builds:
6. 20180708: fix crash in RealVnc app: https://drive.google.com/file/d/1autEPJKDlBhsSFfuvMqsdQm9bGLB9WNm/view?usp=sharing
5. 20180707: gps, IR, drm: https://drive.google.com/file/d/1nB-PiNsB-cF2D7wFHxz4Y-QMkQp_Sz-i/view?usp=sharing
4. 20180706: https://drive.google.com/file/d/1oSVWlUHhwhWui4sAwhUir0Xyk_coKMmO/view?usp=sharing
3. 20180103: ril (calls + mobile data), small fixes: https://drive.google.com/file/d/1vATLmjfSkTNnl8iojOE0dwTc8XyAOY-S/view?usp=sharing
2. 20171231: 15.1 (8.1): https://drive.google.com/file/d/18SWSyNfkqgyr-P5rD2gdyqBCbgAQK4oP/view?usp=sharing
1. 20170929: 15.0 (8.0): https://drive.google.com/file/d/0B-6nm7Jks0W5OHF1T2ttR3Bzbk0/view?usp=sharing
Gapps
https://opengapps.org
Recovery:
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/Lineageos/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
Thanks to davidmueller13 for help with the config and initial run.

@Valera1978: That sounds very interesting. Thank you for your work.

Installed as a test, which went fine. Unfortunate is does not recognize my sim card
I do get the message insert sim card. Removed and reinserted, but still does not see it.
Further testing g to be done.
Ralph

@Valera1978
Hey my friend, really awesome to see you back with such outstanding rom!
Thank you very much for such amazing work!

I have tested this ROM for a few days.
When starting the device it gives a message system process stopped.
Next error I get insert sim, does not look to be recognized yet.
Further I did not get issues, with the basic programs.
Looks promising
Thank you for all the work on this!
Ralph

@Valera1978
Thanks for the releasing Oreo for the P905. It is sad that there is still no new 12" Note tablet on the market that take it's place. Especially because of that we all appreciate your work so we are not forced to abandon the device.
However I sincerly hope that you continue to release 14.1 versions until this rom is out of alpha. I and presumably others use that version as a daily driver. You skipped september security updates, I presume you couldn't find the time, so I hope for an october release. It is sad that android now needs monthly security updates but it seems it's the way things flow these days.
Kind regards,
mnemonic-de

mnemonic-de said:
@Valera1978
Thanks for the releasing Oreo for the P905. It is sad that there is still no new 12" Note tablet on the market that take it's place. Especially because of that we all appreciate your work so we are not forced to abandon the device.
However I sincerly hope that you continue to release 14.1 versions until this rom is out of alpha. I and presumably others use that version as a daily driver. You skipped september security updates, I presume you couldn't find the time, so I hope for an october release. It is sad that android now needs monthly security updates but it seems it's the way things flow these days.
Kind regards,
mnemonic-de
Click to expand...
Click to collapse
I'm sorry, all september worked with a oreo. I do not forget the lineage 14, I did several test builds, and fixed the pressing of the left button with the s-pen (tasks switching). There is yesterday's build - publish it or wait a couple of days and post a september security update?
In any case, I will continue to work with lineage 14, I really do not like consumption in standbye mode, I want to try another kernel. Also, there is still a problem with adjusting the volume during calls.

@Valera1978,
thanks for clarifying that. I think everybody who uses your rom understands that this is a one man show and your time is limited. Regarding publishing, of cause I can't speak for anybody than myself I presume that people would agree to skip the september updates. The october updates are already available and regarding security I think digital, either everything known is patched and you are secure as far as it possible or your are not. I don't think it makes much of a difference if you have more or less vulnerabilites.
One thing that might interest other people in regards of security update is blueborne. I'm curently not sure on which level this must be patched. If it's the driver level than things might get difficult for devices that went out of support. Your last rom 0823 shows vulnerability regarding that bug collection.
Thanks for your continued work on that rom.
Kind regards,
mnemonic-de

Dont know if this is a known bug but after installing this version i have problems playing videos. Both in the facebook app and on websites with integrated video

@Valera1978 are you using the same Lineage 14.1 kernel? The work needs improvements (in the part of the calls mainly) but for an alpha version is very good. Thank you!

Just curious
Is this rom being developed actively or was it more "Proof of concept" right now.
Asking because i have some issues that i could live with for a while, while it is being developed, but as i see no updates i am thinking of going back to 14.1

I don't use sim card therefore wi-fi only. From the remarks it looks like this alpha is working well except for the mobile functionality. I think I will give it a go if the basics of Google calendar and email are working via Wi-Fi.

Early experience :
Issues
- being used wi-fi only
- does not play videos at all. Some apps think they can play videos but don't initiate and stand still at time=0. Others seem to be smarter and give message video can't be played. I tried YouTube, Chrome, VLC, and Plex
- developers rights enabled but missing nifty reboot menu to boot into other options such as recovery. BTW this does work my Los 15 mido phone
- camera not working with any camera app I tried.
The good :
- seems to be faster.
- battery life also seems to be better, although not hugely so
- S-pen is working. Experience in Squid is good which is this tablet's main use
- Oreo's feature set is very nice once you get used to it. Interactive notifications are hard to miss.
- magisk works perfectly.

Could this possibly work for the T900? Being y'all say Wi-Fi works.

For p900 please

Any development for P900

The P900 has a different SoC iirc so you are most likely going to find a version for that in a different thread.

The p900 is officially supported by lineage so you could probably get it directly from the source! Nevermind not released just yet, probably soon though!

I tried the first version, released in September but it was not good because video playback (Facebook, youtube, dailymotion, etc.) was not working.
Has anyone tried the latest version and if you, can you confirm if the video playback works.

I have used this a couple of days now. For the purposes I do use it , all works fine.
Earlier question on video playback, I use vlc and this works.

[ROM] [Unofficial] [LOS15.1] Lilly's LineageOS CookieJar

Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/

Mine mineminemineminemineminemine

Another one

It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.

javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.

Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.

Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.

working like a champ but having issue with the figer print

karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip

Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?

kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.

Download link is not working
Link is not working bro. Send me link

Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.

Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.

Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.

Enjoying the new build so far! Pretty good for me.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip