Develop Bugs

[ROM][4.4.4][OCT27] UNOFFICIAL CyanogenMod 11.0 BETA V0.3

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 ?

[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][6.0.1][OFFICIAL] LineageOS 13.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For instructions about installing or building for toroplus, see the wiki:http://wiki.lineageos.org/maguro_info.html.
Builds are available at https://download.lineageos.org/toroplus.
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico. Note that you must use the pico version unless you have resized your partitions.
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs, Ziyan
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-04-19
Last Updated 2017-03-25

After over a year and a half, we once again have official CyanogenMod builds.

musical_chairs said:
After over a year and a half, we once again have official CyanogenMod builds.
Click to expand...
Click to collapse
Yes we do and it's because of your perseverance . Thanks for keeping this old phone in the thick of it and carrying the torch !

Does it is necessary to flash it using attached recovery in cm download page?can we use twrp?

galuh said:
Does it is necessary to flash it using attached recovery in cm download page?can we use twrp?
Click to expand...
Click to collapse
You can use TWRP, I strongly recommend that. I think you'd need to use cm's recovery if you want to use cm-updater to automatically install ROM updates. But I think TWRP is the way to go.

After fresh installation i've got my net connection,but after sometimes i was found that my toroplus wouldn't picked up any inet signal,but i can use it flawlessly fine to male a phone call and texting.
Ps: sorry for my screwed english

So stoked to see this, I really appreciate this device getting some love!
I tried out cm-12.1-20160530-NIGHTLY-toroplus yesterday, and CM-wise everything looked great. No stutters at all, and some persistent app crashing I'd been having with CM 11 snapshot M8 went away.
Downside is that I couldn't for the life of me get it to activate on Sprint, via Ting. I even full deactivated it twice, waiting a couple hours and then assigning it a new phone number each time. I had to go back to CM 11 to get the phone side back, so it looks like the radio bits aren't ready yet. Still, great to see an update!

jtdev said:
So stoked to see this, I really appreciate this device getting some love!
I tried out cm-12.1-20160530-NIGHTLY-toroplus yesterday, and CM-wise everything looked great. No stutters at all, and some persistent app crashing I'd been having with CM 11 snapshot M8 went away.
Downside is that I couldn't for the life of me get it to activate on Sprint, via Ting. I even full deactivated it twice, waiting a couple hours and then assigning it a new phone number each time. I had to go back to CM 11 to get the phone side back, so it looks like the radio bits aren't ready yet. Still, great to see an update!
Click to expand...
Click to collapse
When you went back to CM11 you had to re-provision the phone since you had changed numbers right ? I'm on MM but I'm going to download and install the build you tried . I ran this 5.1 for quite some time and never had a problem You actually shouldn't have even have had to activate . When you changed numbers you definitely lost provisioning and would definitely have had to re-provision . If you are presently activated on CM 11 with GPS , Phone and data all working you should be able to clean flash this and reboot and just skip the activation screens . It's not needed and no need to wait . Just skip through it and it should all still work . Unlike CM 11 CM 12 has never been able to do a hands free or even manual re-provision for me . Just try what I suggested .

Max Frost said:
When you went back to CM11 you had to re-provision the phone since you had changed numbers right ? I'm on MM but I'm going to download and install the build you tried . I ran this 5.1 for quite some time and never had a problem You actually shouldn't have even have had to activate . When you changed numbers you definitely lost provisioning and would definitely have had to re-provision . If you are presently activated on CM 11 with GPS , Phone and data all working you should be able to clean flash this and reboot and just skip the activation screens . It's not needed and no need to wait . Just skip through it and it should all still work . Unlike CM 11 CM 12 has never been able to do a hands free or even manual re-provision for me . Just try what I suggested .
Click to expand...
Click to collapse
I had a working number with CM 11 before I installed the CM 12 build from ClockworkMod Recovery, but I didn't have GPS turned on (I wouldn't have thought it mattered.) Everything went smooth, but I noticed that the signal-strength had an exclamation mark and the phone side wasn't working. I can't remember if it came up with the hands-free dialogs then, or after I tried to reactivate it. I'll give it another go this weekend, thanks again!

jtdev said:
I had a working number with CM 11 before I installed the CM 12 build from ClockworkMod Recovery, but I didn't have GPS turned on (I wouldn't have thought it mattered.) Everything went smooth, but I noticed that the signal-strength had an exclamation mark and the phone side wasn't working. I can't remember if it came up with the hands-free dialogs then, or after I tried to reactivate it. I'll give it another go this weekend, thanks again!
Click to expand...
Click to collapse
@jtdev @musical_chairs I just clean flashed the 05/30/2015 official build . Right off the bat I had telephony and place a couple of calls . I had to finesse it a bit to get 3g going as it switching around several times from LTE/3G etc , after a reboot 3G popped right up and continues to be stable . I tried browsing and all was fine . I've also updated profile and prl successfully under settings/about phone /sprint updates .
Yeah , try it again and good luck on it . I'm on ringplus but 5.1 always worked fine on TING which I used until recently .
If it still doesn't work for you let me know and I can send you something to try which should work .

jtdev said:
I had a working number with CM 11 before I installed the CM 12 build from ClockworkMod Recovery,!
Click to expand...
Click to collapse
Yes but you stated you deactivated that number and tried a couple of others . When you deactivated that first number you could not have gotten ting going again without having to reprovision again on CM 11 and you would have lost that first number . There's no way you can change a number on Ting without having to re-provision again and losing that number for good . even restoring a nandroid wouldn't work without it .

Max Frost said:
@jtdev @musical_chairs I just clean flashed the 05/30/2015 official build . Right off the bat I had telephony and place a couple of calls . I had to finesse it a bit to get 3g going as it switching around several times from LTE/3G etc , after a reboot 3G popped right up and continues to be stable . I tried browsing and all was fine . I've also updated profile and prl successfully under settings/about phone /sprint updates .
Yeah , try it again and good luck on it . I'm on ringplus but 5.1 always worked fine on TING which I used until recently .
If it still doesn't work for you let me know and I can send you something to try which should work .
Click to expand...
Click to collapse
Just tried it again twice, I think I almost had it the first time.
Try #1: Turned on all radios in CM 11, rebooted to ClockworkMod Recovery, installed 5/30 nightly and OpenGApps-pico, and it came up in CM 12 with the 3G indicator right away! (Actually after a couple shell crashes.) I then updated profile (still 3G), and then updated PRL. It said the PRL update was successful, but it killed the 3G, nothing I could do to bring it back.
Try #2: Restored CM 11 backup, started over. Same setup sequence as before, no shell crashes this time, but I got the exclamation mark in the signal strength indicator again, and couldn't get 3G going.
I'm restoring CM 11 again now, going to have to put this aside for a while. Thanks for the feedback though, at least I know it's possible!

jtdev said:
Just tried it again twice, I think I almost had it the first time.
Try #1: Turned on all radios in CM 11, rebooted to ClockworkMod Recovery, installed 5/30 nightly and OpenGApps-pico, and it came up in CM 12 with the 3G indicator right away! (Actually after a couple shell crashes.) I then updated profile (still 3G), and then updated PRL. It said the PRL update was successful, but it killed the 3G, nothing I could do to bring it back.
Try #2: Restored CM 11 backup, started over. Same setup sequence as before, no shell crashes this time, but I got the exclamation mark in the signal strength indicator again, and couldn't get 3G going.
I'm restoring CM 11 again now, going to have to put this aside for a while. Thanks for the feedback though, at least I know it's possible!
Click to expand...
Click to collapse
You probably already know this so keep in mind if your preferred network is set to LTE you will have a 3G showing but no internet even though it's lit up 3G . You must set it to 3G preferred to have connectivity .
try flashing this file from recovery . It's a nice menu letting you pic your provider for ting , ringplus etc . The menu pops open a box so you select your carrier and applies the exact apn you need . I love it . Works great . Works on three sprint devices for me .
Credit for due diligence to @JakeG1984 for finding and spreading word , it's how I found it plus his useful info and post http://forum.xda-developers.com/showpost.php?p=66734418&postcount=10663
https://www.androidfilehost.com/?fid=24531035584725098
Credit for this apn selector should got to this guy @ChangeOfJinzo
http://androidforums.com/threads/al...-lg-volt-on-cm13-cm12-other-roms-too.1024839/

Good news everyone! I installed today's daily (cm-12.1-20160606-NIGHTLY-toroplus) and just as I was about to throw in the towel, my 3G indicator came on. It does however take 35+ seconds to go from airplane to 3G, which I can live with, I'm just used to it taking less than 2 seconds.
@Max Frost - I didn't use the utility you suggested, I got cold feet reading the backstory.

jtdev said:
Good news everyone! I installed today's daily (cm-12.1-20160606-NIGHTLY-toroplus) and just as I was about to throw in the towel, my 3G indicator came on. It does however take 35+ seconds to go from airplane to 3G, which I can live with, I'm just used to it taking less than 2 seconds.
@Max Frost - I didn't use the utility you suggested, I got cold feet reading the backstory.
Click to expand...
Click to collapse
What gave you cold feet out of curiosity . It flashes perfect , works perfect so I have no clue and would like to know the deterring factor for future reference . I only suggested it if you could not get it to work . I mostly use it on my other devices to get LTE . I might add I've never needed it to get telephony or 3G with this rom .

So, is this going to be the official thread for the Official CM 13 ROM too? I don't have any issues right now I just want to know where to ask if I do in the future. (I haven't run an official CM ROM in years now.)

Cardcaptor_RLH85 said:
So, is this going to be the official thread for the Official CM 13 ROM too? I don't have any issues right now I just want to know where to ask if I do in the future. (I haven't run an official CM ROM in years now.)
Click to expand...
Click to collapse
Thanks musical_chairs, we already have official CM13 builds .
I think that this topic will be about CM13 (As CM11 few years ago).

I guess this will be the thread for official cm-13.0 now. There is a cm-12.1 snapshot on get.cm, that can be discussed here as well.

charging support on Samsung HDMI dock
Is there a setting that I can change to allow charging from the official Samsung HDMI dock? I've got a pair of toroplus running this official CM13 build (one's snapshot and one's nightly), and neither one will charge while on the dock. The battery gradually depletes over the course of a few weeks, so it must be getting some power, just not enough to maintain a charge.
Both phones charge on their respective docks running stock or running zzpianoman's unified 6.0.1.

The default apn settings cause the phone to get really slow when preferred network was set to LTE/CDMA auto. I digged around the vendor RIL file, I noticed it queries for a numeric field when looking up APNs, I added this field to the apns file and now it doesn't get slow when switching networks.
Manual: Copy this file to /system/etc, go to APN network settings menu and press "Reset to default"
Also, to get LTE working temporarily on CM13, you can use my routefix script from OmniROM thread:
http://forum.xda-developers.com/showpost.php?p=68236074&postcount=24

Best Gaming Rom One Plus 3 2020

Hi guys,
I'm starting this thread hoping it will help someone. I personally searched all XDA and Google for an answer as I play heavy games one of them is Free Fire. I like playing the game at MAX FPS and Graphics. I was on the latest OOS 9.0.6. It was awful to me. As i got game lags and my phone got extremely hot. That's when it ventured in the search for the best rom or stock firmware to give me the best performance, stability and battery life. My battery life on 9.0.6 was really poor. I had battery drains of about 10-12% on idle overnight. I searched everywhere and all the threads were outdated and I needed a recent solution to my problem. I mean there's been a lot of newer One Pluses after the 3. But for the hardware that it has I was sure I could get more off my One Plus 3.
I tried Havoc , Evolution X , CR Droid, Lineage OS, Pixel Experience and all the OOS that where rolled out for the one plus. Yes I did alot of flashing and formatting. Since I never flashed just the OTA. I always flashed the firmware on that version and did a clean install always since i wanted a final verdict and didn't want to have a doubt on the dirty flashing. I used each rom and Stock Oxygen version for 4 days since i wanted to give the battery a couple of cycles before getting my final verdict on the rom.
I wrote the SOT time for every firmware or Rom that I flashed to not forget.
Finally I wont disrespect any rom developer out there saying there rom isn't good. As I for myself wouldn't be able to build one. Less without being paid. On the contrary I would like to say a HUGE THANK YOU!!!!!! to all the developers that take their time and build roms for us. I greatly appreciate every Developer here at xda. A big round of applause to you guys. You all are great!!!!.
All the roms are awesome and unique. I'm pretty sure it suits many, many, many users out there. As we're all looking for something different and different features in roms.
I tried all. And TADA!!! I'm on Oxygen OS 4.1.7 Android Nougat. Yes its far from the newest Android Version But the battery life on Idle is the best I have 0-1% battery drain overnight on idle with WiFi on all night. Game performance is awesome. I play Free Fire at Max FPS And Graphics with absolutely no lag. I use Whatsapp and Facebook Messenger and camera all day for my work and i'm able to reach back home after 8 hours work day with an average battery of 67%. To me it can't get better than this. Second in of the OOS was 4.5.1 a little better performance but battery drain was little higher. To me the exchange for a little performance difference to higher battery drain wasn't worth it. Again this is just my humble opinion and experience. Your results could be different. If you want to know my procedure and settings to get this on my One Plus 3. Feel free to ask. And as soon as i have a little time i can reply. Thank You XDA for the Best Forum on planet Earth.
Best regards,
Chimpzilla

How do you install that oos versión? Unbrick tools?

Is there any way to remove Google play from Oxygen OS 4.1.7 to make even lighter?

pls make a tutorial to install Oxygen OS 4.1.7

Chimpzilla said:
Hi guys,
I tried all. And TADA!!! I'm on Oxygen OS 4.1.7 Android Nougat.
Best regards,
Chimpzilla
Click to expand...
Click to collapse
Hi Chimp, thanks for writing your experience here. I had similar experience but used OOS 4.5.1, now want to switch back to OOS 4.1.7 but not finding any download link for it. Can you please share if you have any.
What do you suggest, using MSM Tool to restore to OOS 4.1.7 or just flashing it through TWRP on unlocked bootloader?
On OOS 4.5.1 I was trying to use Advance Kernel Tweaks but Magisk was not working with ElementalX kernel so gave it up.

Okay Guys. Sorry have been really busy. I installed with unlocked bootloader and TWRP. Wiped everything except internal storage. So that Custom Recovery gets replaced by Stock Recovery. Then I booted to system. And then back to recovery just to make sure I had Stock Recovery before Relocking bootloader. Once I had confirmed that i had stock recovery I booted to fastboot and relocked bootloader. After relocking your phone will be wiped please backup anything thats important to you. Every locking or unlocking of bootloader will wipe your data. Im not responsible. Once bootloader locked I booted back system. All firmware downloads can be downloaded from oneplusupdates website. Hope this helps.

Flashed 4.0.3 through MSM then used local update for 4.1.7, setting up my apps now.

mnsiw said:
Flashed 4.0.3 through MSM then used local update for 4.1.7, setting up my apps now.
Click to expand...
Click to collapse
where did you find 4.0.3 MSM ?

acetone802000 said:
where did you find 4.0.3 MSM ?
Click to expand...
Click to collapse
I have it in my OnePlus 3T backup files, it is available somewhere on web, but flashing it this way is just a waste of time, following OP is better option.

OP3T: https://oneplusupdates.com/device/oneplus-3t
OP3: https://oneplusupdates.com/device/oneplus-3
I'm downloading OOS 4.1.7 for test

Chimpzilla said:
Okay Guys. Sorry have been really busy. I installed with unlocked bootloader and TWRP. Wiped everything except internal storage. So that Custom Recovery gets replaced by Stock Recovery. Then I booted to system. And then back to recovery just to make sure I had Stock Recovery before Relocking bootloader. Once I had confirmed that i had stock recovery I booted to fastboot and relocked bootloader. After relocking your phone will be wiped please backup anything thats important to you. Every locking or unlocking of bootloader will wipe your data. Im not responsible. Once bootloader locked I booted back system. All firmware downloads can be downloaded from oneplusupdates website. Hope this helps.
Click to expand...
Click to collapse
Can I root stock ROM to debloat apps?

To remove updates notifications (be aware it's impossible to cancel)
activate dev mod in settings and USB debuging
adb devices
adb shell
pm uninstall -k --user 0 com.oneplus.opbackup

I was actually on OOS 4.5.1 lol older version are better sometimes than the new ones and not everybody know that i downgraded to 4.1.7 now and im testing it right now because i have nothing to do in home with this problem of virus...

Should I be worry with security vulnerability in older OOS?

Chimpzilla said:
I wrote the SOT time for every firmware or Rom that I flashed to not forget.
Click to expand...
Click to collapse
Can you share with us results?

Interesting topic. Which one lowest OxygenOs start support vulkan on oneplus 3?
I ask cause i buyed this phone some days ago with poor OxygenOs 9.0.5
I think about downgrade. I have bad battery life

What is the antutu score on the nougat OOS? On on paranoid android 7.3.1 getting 230,000 compared to OOS 9.0.6 which was around 200,000 and getting good battery life. Not sure if I should switch to OOS 4

Phid13 said:
What is the antutu score on the nougat OOS? On on paranoid android 7.3.1 getting 230,000 compared to OOS 9.0.6 which was around 200,000 and getting good battery life. Not sure if I should switch to OOS 4
Click to expand...
Click to collapse
Can you provide me link to download PA 7.3.1? I Couldn't find the link online.

aravindhsharma said:
Can you provide me link to download PA 7.3.1? I Couldn't find the link online.
Click to expand...
Click to collapse
https://www.celsoazevedo.com/files/android/oneplus3-aospa/

Phid13 said:
https://www.celsoazevedo.com/files/android/oneplus3-aospa/
Click to expand...
Click to collapse
firmaware 4.5.1 or 5.0.8? Thanks
and last TWRP?

LineageOS for Samsung S5 (SM-G901F)

Hi, I got a 2nd hand Samsung S5 model SM-G901F and compilation id MMB29M.G901FXXU1CQE3. I want to flash LineageOS on it but I'm not sure if the device is compatible. Looking into the official LOS website for compatible devices I see my device listed - I think - (https://wiki.lineageos.org/devices/kccat6) but without active development. Does the compilation ID matter? Does it really matter if I flash a LOS ROM that's not under active development? Are there alternative ROMs that I can flash on this phone? I just want to avoid GAPPS and bloatware, have some call recording functionalities and enhance my privacy.
Thanks!

Lee1010 said:
Hi, I got a 2nd hand Samsung S5 model SM-G901F and compilation id MMB29M.G901FXXU1CQE3. I want to flash LineageOS on it but I'm not sure if the device is compatible. Looking into the official LOS website for compatible devices I see my device listed - I think - (https://wiki.lineageos.org/devices/kccat6) but without active development. Does the compilation ID matter? Does it really matter if I flash a LOS ROM that's not under active development? Are there alternative ROMs that I can flash on this phone? I just want to avoid GAPPS and bloatware, have some call recording functionalities and enhance my privacy.
Thanks!
Click to expand...
Click to collapse
kccat6
Kernel Security patches stopped in april.

kurtn said:
kccat6
Kernel Security patches stopped in april.
Click to expand...
Click to collapse
Hi,
from the above Link : https://download.lineage.microg.org/kccat6/
i took the image : lineage-16.0-20211125-microG-kccat6.zip
for a test of "LineageOS 16 with microG "
and next I tried the image : e-0.19-p-20211125148133-dev-kccat6.zip from the link :
https://images.ecloud.global/dev/kccat6/
for a test of "/e/ OS" ,
both with the recovery : TWRP 3.2.3-0
on a Samsung galaxy S5 PLUS ( SM-G901F or kccat6 ) .
Both roms seem to be supported with updates
( meanwhile I made one OTA-Update successfully with both roms)
, but with both custom roms i had/have the big problem, that after shutdown from gui or via reboot -p the powerconsumption is untolerable high - if the accu capacity was 100 % before shutdown it's about 80 % an hour later.
At the moment i have installed the e/OS/ version from above and the phone is meanwhile rooted with magisk V23, which had no obvious impact on the problem with the powerconsumption.
Does anyone have an idea, if/how this problem can be fixed ?
Help woud be appreciated !

bikefreak1 said:
Hi,
from the above Link : https://download.lineage.microg.org/kccat6/
i took the image : lineage-16.0-20211125-microG-kccat6.zip
for a test of "LineageOS 16 with microG "
and next I tried the image : e-0.19-p-20211125148133-dev-kccat6.zip from the link :
https://images.ecloud.global/dev/kccat6/
for a test of "/e/ OS" ,
both with the recovery : TWRP 3.2.3-0
on a Samsung galaxy S5 PLUS ( SM-G901F or kccat6 ) .
Both roms seem to be supported with updates
( meanwhile I made one OTA-Update successfully with both roms)
, but with both custom roms i had/have the big problem, that after shutdown from gui or via reboot -p the powerconsumption is untolerable high - if the accu capacity was 100 % before shutdown it's about 80 % an hour later.
At the moment i have installed the e/OS/ version from above and the phone is meanwhile rootet with magisk V23, which had no obvious impact on the problem with the powerconsumption.
Does anyone have an idea, if/how this problem can be fixed ?
Help woud be appreciated !
Click to expand...
Click to collapse
I would not trust that battery charge level that much. It has only voltage measurement to to guess the stat of charge after a powered off period.

kurtn said:
I would not trust that battery charge level that much. It has only voltage measurement to to guess the stat of charge after a powered off period.
Click to expand...
Click to collapse
Thank you for the very fast response,
but it's not only a matter of a wrong display - if i tried the shutdown in the evening, the accu is really empty next morning - the smartphone can then not be started, there is no display, no vibration, nothing - the phone seams dead unless connected to a powersupply .
I've tried the shutdown procedure several times - as long as the mentioned custom roms are installed the accu is empty a few hours after ( the try of) a shutdown.
If i go back to the stock rom and use the same shutdown procedure the display of the accu-capacity decreases about 3 % within about 12 hours - and the phone can then be started again WITHOUT being connected to a powersupply .
I have tried this with two different accus which i had charged until 100 % before i started the tests and it was always the same effect.
Crazy, isn't it ?!

bikefreak1 said:
Thank you for the very fast response,
but it's not only a matter of a wrong display - if i tried the shutdown in the evening, the accu is really empty next morning - the smartphone can then not be started, there is no display, no vibration, nothing - the phone seams dead unless connected to a powersupply .
I've tried the shutdown procedure several times - as long as the mentioned custom roms are installed the accu is empty a few hours after ( the try of) a shutdown.
If i go back to the stock rom and use the same shutdown procedure the display of the accu-capacity decreases about 3 % within about 12 hours - and the phone can then be started again WITHOUT being connected to a powersupply .
I have tried this with two different accus which i had charged until 100 % before i started the tests and it was always the same effect.
Crazy, isn't it ?!
Click to expand...
Click to collapse
Oops. Can you try to boot into recovery and shut down from there?

i think , i tried the shutdown from recovery a few weeks ago but because I'm not absolutely shure about the result i will try this again and report later, here.
thanks and good bye !

Hi,
yesterday at 23:35 I bootet into TWRP with an displayed accu-capacity of 90% and made a ( try of ) shutdown vom TWRP via it's gui-function : Reboot --> Poweroff.
Today at 18:35 I tried to start the phone WITHOUT connected powersupply and it started into TWRP and displayed an accu-capacity of 89% - GREAT !
I think, that proves, that it's purely a softwareproblem of the installed custom-rom , or am I wrong ???

bikefreak1 said:
Hi,
yesterday at 23:35 I bootet into TWRP with an displayed accu-capacity of 90% and made a ( try of ) shutdown vom TWRP via it's gui-function : Reboot --> Poweroff.
Today at 18:35 I tried to start the phone WITHOUT connected powersupply and it started into TWRP and displayed an accu-capacity of 89% - GREAT !
I think, that proves, that it's purely a softwareproblem of the installed custom-rom , or am I wrong ???
Click to expand...
Click to collapse
Proof. Next step: find someone to fix that. Lineage.microg.org aswell as e.foundation do blind builds. Are you willing to join /e/ testing group and file a bug report in ?
Issues · e / Backlog · GitLab
GitLab Enterprise Edition
gitlab.e.foundation

Thank you for the fast response,
at the moment I'm not sure whether i fulfill the demands for a membership in an /e/ testing group - can you perhaps give me a link where i can get more information about it ?
good bye for today !

bikefreak1 said:
Thank you for the fast response,
at the moment I'm not sure whether i fulfill the demands for a membership in an /e/ testing group - can you perhaps give me a link where i can get more information about it ?
god bye for today !
Click to expand...
Click to collapse
https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home

kurtn said:
https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home
Click to expand...
Click to collapse
Hi,
when I click on the above link :
"https://gitlab.e.foundation/teams/test-team/documentation/-/wikis/home"
i get the message :
404
Page Not Found
Make sure the address is correct and the page hasn't moved.
Please contact your GitLab administrator if you think this is a mistake.
Is it sure , that the link is correct ?