Develop Bugs

[Q] Common problems of cm9, cm10 and cm11 already known?...

Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!

1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin

Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk

to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...

6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention

Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.

aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo

[Q] Phone no more recognized by the PC after installing ROM

Hi.
First of all, thanks for all you great people for working and developing for these phones.
Today, for the first time, I flashed my phone. Having android on Wave 2 feels great!
I installed CarbonRom but I'm not entirely satisfied with it and wanted to try to install some other ROM (like ZenDroKat, I heard good things about that one) and run into a problem. I noticed that my PC doesn't see the phone at all! There is no reaction, not sound when connecting the phone. I tried the front and the back usb-ports, and on our family laptop. The multiloader doesn't find the port either.
Although it did react in recovery mode (TWRP) and installed drivers for "Android Composite ADB Interface", whatever that is.
Or could I install a new ROM without trying to fix this?

Once i had a problem detecting my phone , i was so frustrated : what worked with me , maybe this sound silly but :
Does your phone charge with the USB cable :
if yes in mini USB port there is a tongue inside , trying raising it a little with a sharp metal
if no , maybe your cable is the problem .
between that and this , probable you can install Omni rom , by copying the rom to sdcard if you have external card reader , since you have already TWRP installed.

Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?

I have Windows 8 on my computer, when I update my windows with connected phone it shows Acer updates in Microsoft update menu. I update all, and after my computer didn't recognize my phone. Then I delete Acer drivers and it recognize again
Sent from my GT-I9000 using XDA Free mobile app

DkayBlack said:
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
Click to expand...
Click to collapse
i think Omni is better ,and stable ,try it

ice_ice said:
i think Omni is better ,and stable ,try it
Click to expand...
Click to collapse
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.

DkayBlack said:
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
Click to expand...
Click to collapse
Short development history: by Rebellos
The project has been started by Oleg in March 2011 - development progress has been made rapidly by him, however, he had been using JTAG Riff Box to make Wave oneNAND memory organisation the same like in Samsung Galaxy S (SGS) I9000 - phone with very similiar hardware to Wave. The problem is it's very expensive and advanced stuff. In the meantime mijoma found security hole in Wave's Bootloader3 (BL3) FOTA loading code and made PoC-exploit for that. That allowed me to create, with help of srg.mstr, mijoma and b.kubica, simple Badadroid bootloader, loading kernel zImage from moviNAND flash memory - this is where port has been made bootable on literally any Wave phone. However, oneNAND layout still remains untouched and by default kernel is configured to use SGS oneNAND partitions. So nbates66 and anghelyi put all their efforts into making this method of booting operatible. It succeed after few days and ShadowAS1 had released unofficial tutorial explaining how to bring up pre-alpha Android into S8500 device. The problem was that only 1 bootloader version was supported this time, mijoma came up with idea of making our FOTA bootloader capable of supporting alot of bootloaders - he created "BL Univ Boot FOTA". Oleg became very busy with his real life stuff so kernel development practically stopped. Currently I'm the most active kernel developer, altough I'm not so experienced as Oleg is and I'm learning from scratch so it goes very, very slow.
December 2011 - KB_Jetdroid contacted me and we started to work on Jet&Wave modem driver.
April 2012 - mikegapinski has joined the project to get things together and make first really working ROM.
9 April 2012 - Mike got ICS platform booting.
Mike has stopped maintaining platform so I took it over.
Oleg has finally got S8530 in his hands and made SCLCD driver for it. Praise him!
Both S8500 and S8530 versions are semi operatible. The most complicated, annyoing, and needed driver is Modemctl+RIL.
March 2013 - World's first working non-AT commands based RIL for non-Android phone has been released. Most of the implementation was done by KB_Jetdroid, me and Volk204, basing on opensource Replicant's RIL for Samsung Galaxy S.
April 2013 I finally fixed S8530 display driver.
September 2013 - we've got working microphone recording, and shortly after Tigrouzen found a proper patch fixing voice communication during calls.
22 September 2013 - we released first version capable of multicalls.
~~October 2013 - GPRS connections are working
Currently most of the core work is done.
We are working hard with Volk204 on RIL interface, doing small progress day by day.
en very brief : there was one team , that did all the work since the start ,"the Badadroid team" , Badaroid developed by Rebellos and Volk204 was a base for Omnirom ported by volk204 which he is the main developer now , and all those rom you see is basically noob roms , they copy the work of Volk204 , they are actually no developers in the first place, if Volk204 doesn't fix the bugs in his roms , their roms has them . i would recommend
Nand - use Omni rom http://forum.xda-developers.com/showthread.php?t=2800014
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Hero355 is also a good one but he has own bugs and he isn't around much this days , work on it stopped http://forum.xda-developers.com/samsung-tizen/bada-android/rom-carbonrom-s8500-s8530-t2840174
read this thread http://forum.xda-developers.com/showthread.php?t=1459391

Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
ice_ice said:
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Click to expand...
Click to collapse
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:

DkayBlack said:
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
Click to expand...
Click to collapse
THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
For me : Call diverting , not working
GPS not fully working
Roms is amazing , fast , but not so fast when installing Gapps ,(i did install them , but i disable all of it)
Battery life
don't get me wrong Omni is my daily rom , but this could be a problem if talk to much on phone , battery drop out fast , with average use it won't last 10 hours

[ROM] [6.0.x] Official CyanogenMod 13.0 Nightly Builds Oppo N3

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01

Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!

SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).

jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it

good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.

How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk

cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor

Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!

SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.

Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help

This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?

SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.

jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!

SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...

Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.

Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.

To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.

Man, you are the best! And what about sensors?
And where did you find this solution?

hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.

How to make this logs? i know nothing in programming (

[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