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 (
Related
ColorOS 2.0 for G Pro by WS008
Based on CM10.1 (4.2.2) and ColorOS Patchrom
Please take note that although this ROM is based on CM10.1, it is not merely a modification to the CyanogenMod. It uses a similar method to MIUI in building the ROM. You will get a ColorOS experience instead of a CM one by flashing it.
About ColorOS
ColorOS is a firmware based on Android with intensive modifications. It was created by Oppo and originally ran only on Oppo devices such as the Oppo Find 7. In 2014, Oppo started its Patchrom Open Source Project and allowed the ROM to be ported to other Android devices.
The ROM is ported by the Chinese developer WS008. The development of the ROM has stopped (for a long time...)
Features
ColorOS features
Added SmartMax to the kernel.
Zipaligned.
Rooted, SuperSU.
Smooth as CM10.1.
Improved battery life.
Double tap to wake.
Slide to wake.
Included Aroma Installer. You may choose which variant you have and whether you want GApps when flashing.
Screenshots
How to install
Install custom recovery (PhilZ Touch recovery recommended) (There are issues with TWRP.)
Wipe Data/Cache/System (Important)
Flash zip -> Select Your variant -> Select GApps
Downloads
From ColorOS official server.
Known Issues
NFC not working.
FAQs
1. Why 4.2.2?
The ColorOS Patchrom currently only supports Android 4.2.2. The update can only made by Oppo. We will try to update to KitKat as quickly as we can once Oppo releases the KitKat update to the Patchrom.
2. Why Chinese?
The ROM is in Chinese by default (Sorry, we cannot change it unless Oppo does something.) You may switch to English in Settings (设置).
If you like this ROM, please click the "Thanks" button. We will also appreciate a lot if you connect to the Internet at least once after flashing for statistical purposes.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Thank you very much @JTJTJ.
Eventhough you are not the developer, but your action helps us very much as we do not have that great assortment of roms.
Cheers.
TNX :good:
For some reason i couldn't connect to my WiFi network. Also i was able to choose Hebrew language but the interface changed to English.
olorin said:
TNX :good:
For some reason i couldn't connect to my WiFi network. Also i was able to choose Hebrew language but the interface changed to English.
Click to expand...
Click to collapse
Which variant are you using? I will feedback to the developer and see what we can do.
g0at1 said:
Thank you very much @JTJTJ.
Eventhough you are not the developer, but your action helps us very much as we do not have that great assortment of roms.
Cheers.
Click to expand...
Click to collapse
More than happy to bring ROMs here
Did you know is is Possible change the 4G icon to LTE i on T-Mobile
any help?
Sent from my LG-E980 using Tapatalk
We need to at base 4.1.2 in order to flash this rom right bro?
going to try just backed up dho commtio 4.4.3 and flashed cmw
Not working on F220K
Sorry, but i've tried to install it several times on F220K, the installation process completes well and then it does'nt boot, then i tried F240k variant and it installed and booted well, but it had some graphics glitches on F220k, any help would be appriciated,
It doesn't boot on my phone
Flashed the E988 variant
ROM installed fine but everything is in Chinese. Color OS looks beautiful. I wish they added more steps in English for initial set up. This thread will be hard to maintain in English unless we are able to install in English.
pramod1969 said:
ROM installed fine but everything is in Chinese. Color OS looks beautiful. I wish they added more steps in English for initial set up. This thread will be hard to maintain in English unless we are able to install in English.
Click to expand...
Click to collapse
Can i happen to ask what rom where you on when you flashed this rom? I tried installing this and MIUI on kitkat but it won't boot past lg logo after installation. Were you able to test he battery life?
blitzkriegger said:
Can i happen to ask what rom where you on when you flashed this rom? I tried installing this and MIUI on kitkat but it won't boot past lg logo after installation. Were you able to test he battery life?
Click to expand...
Click to collapse
Any update with this Rom? I am very interesting to install. But I need NFC too
fariznur said:
Any update with this Rom? I am very interesting to install. But I need NFC too
Click to expand...
Click to collapse
I have just installed the rom. It works pretty well. NFC seems to work (didn't try with another phone though).
You can flash it with CWM in Freegee.
There is a tutorial to get english on Youtube:
Thanks to let us try ColorOs
UPDATE: It's not too bad, I'm not 100% sure what the OTA does but I'm on the 06/16 build. I'll try and see if I can get the double-tap wake to work in a bit. Just seeing if I can change the Chinese keyboard to an English one since installing Google Keyboard from the Playstore FC's. Overall: not bad at all.
EDIT: Forgot to mention, the speaker sounds noticeably better on here. I'm not sure what's different but the quality is great.
May I know how to disable NFC function? I click disable but it still keeping enable. Is it a bug?
So, I tried this before, and I loved the features. I couldnt however get wifi and stuff to work. I want to try it again, but the zip wont download correctly :/ It is "invalid"
EDIT: If anyone has the same problem, download and use DAp. It downloaded it without making it invalid, lol.
'
Anyone else have problems with getting stuck a LG logo upon first booting after install? I found that it can be fixed by copying 'wcd9310_mbhc.bin' and 'wcd9310_anc.bin' into '/system/etc/firmware/wcd9310/' (files available from here). I packed them into the ZIP, reinstalled, and am now having a colorful os.
The non-existence of those files causes this error upon install, though it wasn't reported by the installer--it claimed success!:
Code:
symlink: failed to symlink /system/etc/firmware/wcd9310/wcd9310_mbhc.bin to /data/misc/audio/mbhc.bin: No such file or directory
symlink: failed to symlink /system/etc/firmware/wcd9310/wcd9310_anc.bin to /data/misc/audio/wcd9310_anc.bin: No such file or directory
Which, I think, caused a nasty loop of '[CAM/E][ERR] ce1702_i2c_rxdata failed!' errors upon first boot, keeping me from advancing past that mocking LG logo.
UNOFFICIAL CyanogenMod 11.0 BETA V0.3
by MisjugdedTwat a.k.a. BangL
WHAT IS THIS?
This is an UNOFFICIAL build of CM-11.0 ( CyanogenMod 11.0 ) for Huawei Mate (hwmt1_u06)
I am basically just continuing the work of others by merging and compiling, so credit goes to surdupetru, joestone, asyan4ik, mrAlmid and all coders who contributed to CyanogenMod.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
*/
REMEMBER
If you choose to use my unofficial build, pls don't post your issues and/or request in the official CyanogenMod forums. My builds contain unofficial code and MAY affect the official debugging process.
I do this in my free time, for free. Never forget that
Take care and do backups before flashing!
FIRST INSTALLATION (of THIS rom)
!!! BACKUP EVERYTHING !!!
Make sure your bootloader is unlocked, and install TWRP 2.8.1.0
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot into TWRP
Do a FULL WIPE (system, data, cache, dalvik) ! - you can try to keep data, but it will most likely fail booting.
Install the ROM, using TWRP
Install the Gapps, using TWRP (optional)
Reboot to system
UPDATE INSTALL (when you already have another version of this rom installed)
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot to recovery
Wipe system
Install the ROM, using TWRP
Wipe cache & dalvik
Install the Gapps, using TWRP (optional)
Reboot to system
LATEST CHANGES
V0.3
V0.2
CM SOURCES MERGED UP TO:
Change 110843 - manifest: Remove vendor/cyngn repo
http://review.cyanogenmod.org/#/c/110843/
INCLUDED KERNEL
whirlwind.kernel
KNOWN BUGS
a2dp is not running perfect, but it runs. - sometimes.
Nfc is probably not working at all, not sure.
GPS acts a little weird sometimes.
Video compression results in pure trash.
Clock might get desynced
DOWNLOADS
Please note this build is for bug-hunting purposes only, yet! (Plain CM is boring anyways)
I am just starting to build for this device and with this build am currently trying to get a stable basis for other roms.
My goal is having a fully working code-base for any AOKP-based 4.4 ROM.
So PLEASE join the testing phase, try every ****ing functionality on your phone and report the results here, so i know whats done and what needs to be done. Thanks!
Rom
https://www.dropbox.com/sh/gd42e500zsrl7e0/AACjh4We8ZjULayjWFL7Y1lla?dl=0
Gapps
Use any "ARM - 4.4" package from open gapps (i recommend the nano variant)
Bootloader/Recovery
If you are still on a locked bootloader, having an unrooted stock rom, or an old twrp installed, use this updated unlock/recovery suite for windows and linux:
TWRP 2.8.1.0
SOURCE CODE
https://github.com/hwmt1-u06/android
NOTICE:
I removed the asound codecs, which increases the sound volume dramatically. I wanna enjoy my music loud, when i'm sitting in the bus!
This kinda ****s up the speaker, since its too loud now, which causes clipping.
I use the Equalizier in CM's DSP Manager to reduce the speaker volume (by turning all levels around -6db)
Having loud volume, and the ability to decrase it, is better than having silence and no ability to increase it, right? Thats like going to the hair stylist and wanting longer hair.
Cool, thanks for your effort!
Will give it a try when I feel I have enough time
UPDATE V0.2
CHANGES
Fixed rebooting to recovery
Changed some default system props related to adb and root
Thats it, any bugs?
Otherwise i will now focus on porting more aokp roms, building twrp and a maybe a kernel.
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
sijben said:
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
Click to expand...
Click to collapse
Its probably both messed up as well in this ROM, i don't have the hardware to test those functions. Maybe you can tell me
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
SvenHee said:
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
Click to expand...
Click to collapse
its meant like this:
- first install the first installation of THIS rom
- update install is when you already have this rom installed (e.g. v0.1) and you wanna update to another version of this rom (e.g. v0.2), and keep your apps, data and settings.
and remember to backup first!
EDIT: Updated instructions in first post
Very good, thanks!
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Thanks for tests your reports, guys!
let's see..
SvenHee said:
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Click to expand...
Click to collapse
Wait.. what? Are you telling me a2dp is working perfectly fine? I did not expect that at all!
Yeah, i will port more ROMs, but first i had to have my own kernel (see below) :fingers-crossed:
blankulus said:
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
ive already patched in a tweak to help that problem atleast a little, i am not sure if theres more i can do.
as far as i know it's a well known jb/kk-problem on devices with very low ram... i had an LG O2x, which hab like 500MB ram or something... it was pretty much ununsable when someone called. i remember something like they started to remove the incallUI from the permanently-open list - if you know what i mean. and that's why it's causing this problem.
i don't really have this problem at all, to be honest. so maybe you can help it by removing some service-apps.. or maybe theres some app to force another app to stay loaded? i don't know, just an idea.
tauio111 said:
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
Click to expand...
Click to collapse
arg... P6? different kernel?
so your report doesnt really help me, since i dont even know what the exact differences between the MT1 and the P6 are, and most off the hardware related stuff is kernel related!
Good to see it's running well for you, though.
But thank you very much, srsly.
btw: you are having the wifi dropping too? thats weird, i was sure thats a kernel & /system/lib/modules thing.
...which is why i focused on kernel building for now. It seems like some people are smashing any modules they can find at their kernel until it works somehow. - this is a huge mistake. kernel modules in /system/lib/modules MUST be built against the exakt same kernel, they will be used on.
To be sure to have that clean, i felt like i need to get into that stuff as well. - and i actually just succeded like 30 minutes ago.
I will try out some things on this build, and when everything seems stable to me, i will even release my own kernel, which will always be shipped with the correct modules
But that will be HIGHLY experimental, and for the MT1 only!
Only had minor hiccups when browsing the internet at the same time.
Now testing the second session of music
Edit: A few more hiccups in one session, pretty good play a bit later. Very usable.
Installed and so far its very smooth
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
SvenHee said:
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
Click to expand...
Click to collapse
interesting.. is there any cm based rom, where you dont have that problem?
Carbon was the only 4.4.4 rom by Mr. Amid I got working, I know now (with your explanation) that I should have wiped data too when flashing a new rom.
I can not recall having the Maps problem with 4.2 roms.
UPDATE V0.3
CHANGES
Fixed /data/share paths in frameworks-base and system-core
System-props and init.rc script optimization
Using wpa_supplicant_8_ti instead of wpa_supplicant_8
Prebuilt B331 kernel and kernel-modules removed
Built whirlwind.kernel #2 from sources
Built wifi modules against whirlwind.kernel #2
Is a2dp, gps and wifi better with this build, or maybe even worse?
Will I be able to upload videos to instagram ?
Hello all
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
Thanks
bonuzzz - my friend, thank you for the tablet. thanks for the support and help during the entire time working on 6.0.1
Schischu - thank you very much, this is realty great job on creating aosp for tab s series
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!
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. Reboot recovery
6. Flash firmware
7. Flash gapps
Known Issues
Bluetooth
Camera
Old working gapps: open_gapps-arm-6.0-micro-20160106.zip: https://drive.google.com/file/d/0B-6nm7Jks0W5TndJQ09HR0JDRTA/view?usp=sharing
Gapps - if you get "Unfortunaly, Setup Wizard has stopped" on first cm load. This is common problem.
Try find older version: 22 March or early (my link). Or you can delete Start Setup app: go back to twrp - Mount -> system, then Advanced -> File Manager -> system\priv-app\SetupWizard - select current folder and delete. Then reboot in system.
Links
6. 20160406: the April update of the Google Security systems: https://drive.google.com/file/d/0B-6nm7Jks0W5QVVwSHV5RUgxUmc/view?usp=sharing
5. 20160401: https://drive.google.com/file/d/0B-6nm7Jks0W5bWJfZjZuME9Gcms/view?usp=sharing
4. 20160331: https://drive.google.com/file/d/0B-6nm7Jks0W5VTJfdWdma1FFb0U/view?usp=sharing
3. 20160330: fix sdcard, gps: https://drive.google.com/file/d/0B-6nm7Jks0W5bVBJR3VFMXEwVWc/view?usp=sharing
2. 20160330: first cm 13.0 build: https://drive.google.com/file/d/0B-6nm7Jks0W5YUhROVNBN1dacG8/view?usp=sharing
1. 20160329: first aosp 6.0.1 build: https://drive.google.com/file/d/0B-6nm7Jks0W5NEZCMmROb2dQSHM/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 6.0
Sources
cm13.0 branch, in readme file (see device tree) all instructions for build.
CyanogenMod: https://github.com/CyanogenMod/
AOSP: https://github.com/Schischu/
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Camera issues when using the default camera app, or is it a hardware issue? I use the camera fairly often.
@Valera1978 Awesome work my friend! Congrats for one more wonderful work! You rock!
Thanks, I'm gonna try it.
Valera1978 said:
Hello all
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
That's fantastic news @Valera1978 ! Was thinking of trading this machine in because lack of development. But in the same time I love it. It's a brilliant device and it's a pity so few people has found that out. So THANKS A MILLION Valera!
Click to expand...
Click to collapse
Huray. You are awesome.
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
Click to expand...
Click to collapse
Are you going to work more on it? Because you have it for limited time, will be there someone else to continue?
Kubas_inko_CZ said:
Huray. You are awesome.
Are you going to work more on it? Because you have it for limited time, will be there someone else to continue?
Click to expand...
Click to collapse
The p900 will be available till end of the weekend, may be the next week also.
My plan simple - push another developers to continue work with cm13. In this limited time I want:
- make stable cm13 - building right now, hope today evening will be the first results
- clean-up my device/kernel/vendor (almost done)
- try fix camera - look like this is big issue for all exynos cm13 devices, but need at least try fix
And then I really hope thompatry will continue work with cm13.
And hope my sources will help make cm for related note pro 12.1 p901 and tab pro t900/t520. At least t900/t520 use the same kernel and very similar hardware.
Buggy Setup Wizard
How can I skip the buggy Wizard? It keeps popping up error messages.
My tablet was always diferent. I wasnt able to update to official lollipop (stuck on boot animation or every proces crashed) Cm12 is laging. And now, the android 6.0.1 is stack at boot screan animation. I also bricked it with official lollipop (from cm11 to official lollipop) and unbricked it with official kitkat. I really dont understand it. I need to do more with my little android development skills (i have successfully ported cm11 to friends phone, but only thanks it have little difrences from the official cm11 for the supported device) i dont know if u understand it but it doesnt matter
No way!! I wasn't expecting this.
I don't like posting this kind of useless message but I had to write a big THANK YOU. The thank you button doesn't cover how grateful I am for bringing a 6.0 ROM to our big guy.
Does the s-pen work? I can't flash it right now.
GRellinas said:
How can I skip the buggy Wizard? It keeps popping up error messages.
Click to expand...
Click to collapse
Sorry. I forgot to thank you for your work.
Please help me solve this problem with the buggy setup wizard. It keeps coming and I can't do anything .
GRellinas said:
Sorry. I forgot to thank you for your work.
Please help me solve this problem with the buggy setup wizard. It keeps coming and I can't do anything .
Click to expand...
Click to collapse
I had the same problem. Couldn't get past it. So I did a new clean install and this time without Gapps. The rom runs fantastic. Went to apk mirror and downloaded the latest GMS and installed it. Then I went to settings to add my G account. And couldn't go thru with it cause GMS keeps crashing. Don't know why. Gonna uninstall it now and install an older GMS
---------- Post added at 08:25 PM ---------- Previous post was at 07:40 PM ----------
thools60 said:
I had the same problem. Couldn't get past it. So I did a new clean install and this time without Gapps. The rom runs fantastic. Went to apk mirror and downloaded the latest GMS and installed it. Then I went to settings to add my G account. And couldn't go thru with it cause GMS keeps crashing. Don't know why. Gonna uninstall it now and install an older GMS
Click to expand...
Click to collapse
Edit: Tried an older variant of GMS and no success. Well just have to wait. Meantime its awesome running MM on what I thought was a dead device.
Thank you for this Valeria. Really appreciate you doing this. I've encountered most of the problems previously mentioned. Installed with Gapps. No joy. Did another install without. Running OK. One thing nobody else has mentioned is I can't see my external sdcard. Tried 3 different ones. 32, 15 and 4 GB. No luck with any. As for ROM. Nice. Fast. Smooth. Cheers
Cm 13.0 build is ready. Please see first post how to solve gapps problem. Tomorrow I'll check what is wrong with gapps. And then I'll start fix small problems. Still a lot of work, but now with working cm.
Wanted to first say I'm extremely grateful for your work; I've been keeping an eye on the CM threads here for weeks because this upgrade could make the P900 work like a new tablet.
I rely on it daily for college, so I'm kind of hesitant to flash just yet. But for those of you who try this ROM, I'd be very interested to know:
1) S-Pen -- For a separate S-Pen (the one with a separate eraser in addition side button), do the extra buttons work natively in LectureNotes or similar apps or does something else (e..g, "CM S Pen Add-on") need to be installed?
2) Encryption -- Does encryption/decryption work with TWRP 3.0.0.0 (or an earlier version)? Haven't had much luck getting TWRP to decrypt 5.0.2 stock, but as long as the OS can decrypt -- and I've been able to make backups -- I haven't worried about it.
3) Multi-Window -- In CM13, how adjustable are the windows? Can you achieve a setup where 2/3 of the screen is for one app while another app gets 1/3?
4) Camera -- Is it just the stock camera app that's having trouble? Would another app (e.g., Open Camera) work?
5) Microphone -- Is the mic working okay (e.g., for an app like LectureRecordings)?
6) Screenshots -- Is there a good solution for editing screenshots? Something that supports S-Pen? Being able to quickly crop and import things into LectureNotes is very useful. Noticed a new app called "Screen'it" in the store that might eventually be a good stock replacement, but I'd like to know if anybody's got a better solution.
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
Okay... No Bluetooth. [Oops, correcton, Blue tooth *does* work.] No external sdcard. But very fast. Thanks and looking forward to usable version.
shonkin said:
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
---------- Post added 30th March 2016 at 12:33 AM ---------- Previous post was 29th March 2016 at 11:44 PM ----------
Okay... No Bluetooth. No external sdcard. But very fast. Thanks and looking forward to usable version.
Click to expand...
Click to collapse
Thank you.
Yes, you are right, something wrong with the latest gapps. On p905 with latest gapps we are geting the same start wizard problem.
I finished the firmware late at night and had no time to check the different gapps.
Today will be full test and cleanup.
Remove sertupwizard from /system/priv-app to skip wizard. You can do it with twrp file manager
There is rallye no bit different betwene android 5.1.1 (cm12.1) and android 6.0.1 (cm13). The only one i really like is multi window. But still awesome work Valera.
---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------
Can it be gaps version problem? Because i use micro and have no problem with it. (Yet)
Valera1978 said:
Thank you.
Yes, you are right, something wrong with the latest gapps. On p905 with latest gapps we are geting the same start wizard problem.
I finished the firmware late at night and had no time to check the different gapps.
Today will be full test and cleanup.
Click to expand...
Click to collapse
shonkin said:
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
---------- Post added 30th March 2016 at 12:33 AM ---------- Previous post was 29th March 2016 at 11:44 PM ----------
Okay... No Bluetooth. No external sdcard. But very fast. Thanks and looking forward to usable version.
Click to expand...
Click to collapse
You're absolutely right. Installed open Gapps 0322 Pico and no problems with GMS. Restoring all my apps now. Tried with Pico Gapps 0330 first but no luck. Thanks for your tip ?
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
https://download.lineageos.org/bacon
Currently Maintained by jrior001/
https://www.cyanogenmods.org/forums/topic-tag/jrior001/
Install instructions
https://wiki.lineageos.org/devices/bacon/install
Upgrade from official Lineage OS 14.1 possible but as usual clean install is better. Good time to wipe that phone clean.
Please update TWRP to the latest. If you have this device and don't know how to install please follow above procedure.
If you have device encryption enabled, consider removing as its a bit touch and go. As usual always have a full backup and separate copy of your data/pictures.
And the caveat you are responsible for what you do with your device applies and no one else is responsible for your action. People may be able to help if you ask kindly.
Official channel released finally on the 18th of July 2018.
Super effort by Devs specially jrior001, so please donate if you can.
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
which is d stable twrp version???
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
3.2.1-0
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Is that cyanogenmods website some kind of fan site? It doesn't look official.
Kernel
Is anybody working on the included Kernel?
The background of my question is that I am experiencing spontaneous reboots when physically leaving a Wi-Fi connection, particularly my home Wi-Fi.
This defect was present in LineageOS 14.1 as well. There I could solve the problem completely by installing the latest Franco Kernel. However, in LineageOS 15.1 the Franco Kernel leads to very frequent soft reboots, like 5 in one hour, so I am now back on the stock kernel.
The only workaround I know is to disable Wi-Fi before leaving a Wi-Fi area, then re-enabling it.
Before other users jump in and state that they don't have this defect, not everybody has it. It is not clear under which conditions the defect shows up. It may depend on certain apps being present. But obviously it is not the apps' fault, as the fact proves that the Franco Kernel resolved it in LineageOS 14.1. Not to mention that no app has the right to reboot the system.
sn809 said:
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Click to expand...
Click to collapse
No sir....actually im nt frequent user of xda forums these days
NetGuard via VPN is not working for me. Under 14.1 was everything ok.
Hardware buttons backlighting is very dim for me even when set up to 100% brightness.
sn809 said:
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
Click to expand...
Click to collapse
The Development section is for users to post their own development work, not links to the development work of others. Please refer to the sticky posted here and be sure to follow the forum rules.
THREAD CLOSED