One issue: when i turn on/off gps with google hands free activated the phone start recalling the last number
Sent from my A0001 using Tapatalk
Sent from my A0001 using Tapatalk
[EOL][ROM+KERNEL][6.0.1] Unofficial CyanogenMod 13.0 with 3.4.0 kernel [Apr 30, 2017]
- Thread starter Sultanxda
- Start date
Confirmed, I am also experiencing this bug. I'm on the 2016-06-03 build. My phone had previously found the 2016-06-10 latest build update, but when I attempt to download it using the tool, it fails.
It feels like there is some code that must have changed upstream in the update server - perhaps Sultan will do a workaround or patch soon. SUPER convenient to flash from this updater tool, hope we don't lose that feature.
Anyone experiencing this on the latest build?
Yes, I have this happening also. Just noticed it for the first time last night.
encryption and decryption
Hey everyone. I am wondering if encrypting works with this rom. and if it also works to decrypt this rom with the latest official twrp 3.0.2-0. i have read that there were some problems with decrypting cm13 but how is it with sultanxda cm12.1 rom ?
EDIT: ops wrong thread xD
Hey everyone. I am wondering if encrypting works with this rom. and if it also works to decrypt this rom with the latest official twrp 3.0.2-0. i have read that there were some problems with decrypting cm13 but how is it with sultanxda cm12.1 rom ?
EDIT: ops wrong thread xD
Last edited:
Just a note for people having bugs etc.
I have a found that sometimes random buggy behaviour can be a result of using themes.
I was about to post a query here about Android UI crashes while trying to load photos/videos and pdf's through my mail client and photo app but then decided to restore default/system theme. After a restore everything worked as normal.
This rom kicks ass!
Sent from my A0001 using XDA-Developers mobile app
I have a found that sometimes random buggy behaviour can be a result of using themes.
I was about to post a query here about Android UI crashes while trying to load photos/videos and pdf's through my mail client and photo app but then decided to restore default/system theme. After a restore everything worked as normal.
This rom kicks ass!
Sent from my A0001 using XDA-Developers mobile app
For those who cannot upgrade the ROM via OTA, are you still using TWRP 2.8.6.0? Sultan told us in his first post that we must now use TWRP 3.0.2-0. So if you are still using an old TWRP, load the new TWRP and try again.
We discussed this a few pages back.
There have been people with this issue (including me) that reccomend changing build.prop setting and mixer.paths.XML settings using a root file manager such as es file explorer. To find out which settings to change you'll have to look through the forums (sorry I can't remember).
In my case it turned out to be a hardware issue and I bought a mic ($7-$10) and replaced it. Good luck.
Trycalling someone use the speakerphone and see if the mic volume works OK. There are two mics in the phone one up top to the left and one on the bottom just left of the microusb port. Good luxk
In my case it turned out to be a hardware issue and I bought a mic ($7-$10) and replaced it. Good luck.
Trycalling someone use the speakerphone and see if the mic volume works OK. There are two mics in the phone one up top to the left and one on the bottom just left of the microusb port. Good luxk
I don't think is twrp problem. My twrp already updated few weeks ago....
I dont know which build broke it 0610 or 0603 or previous one
But my phone is 70% time on *searching for gps* in maps app while navigating
Gps lock takes forever to take place
I even tried flashing .4.0.1 firmware as sultan said there was improvement in gps lock for them, but no gain
Please help
But my phone is 70% time on *searching for gps* in maps app while navigating
Gps lock takes forever to take place
I even tried flashing .4.0.1 firmware as sultan said there was improvement in gps lock for them, but no gain
Please help
I let WhatsApp make a conversations backup, then reinstalled it. All is well now... I shouldn't have restored its data with TiBu.
As I already said, I tried it but it didn't work. It always wanted to restore my backup but it failed. I tried it several times. It always said that "unfortunately chat backup cannot be restored". And since I don't want to lose all my conversations I restored again via titanium.
(would also be interested why the 'old data from previous rom' should cause such a bug)
Where did you found a stable ubuntu[emoji87] [emoji15]
Send from my Oneplus One with Auditory Research in Sound Enhancement™
Hi,
each time I want to install an update I select to install it a a normal OTA update, but then when the oneplus one reboots the screen keeps in black and blinking.
Then I have to enter fastboot mode, boot a recovery image (twrp 3.0.2.0) and then it opens with openscriptrecovery installing the update.
is it normal way of installing updates with this rom?
i think It should install as a normal OTA update and that I have something wrong.
Can someone give me an explanation?
Thanks,
each time I want to install an update I select to install it a a normal OTA update, but then when the oneplus one reboots the screen keeps in black and blinking.
Then I have to enter fastboot mode, boot a recovery image (twrp 3.0.2.0) and then it opens with openscriptrecovery installing the update.
is it normal way of installing updates with this rom?
i think It should install as a normal OTA update and that I have something wrong.
Can someone give me an explanation?
Thanks,
Do you install supersu when prompted from twrp after the install? Because when I do that I get boot loop issues, from now on I do not install supersu after an OTA
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
1036Code:
/* * Your warranty is... still valid? * * 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. * */
This is the successor to my no-frills CM12.1 ROM: http://xdaforums.com/oneplus-one/orig-development/rom-kernel-unofficial-cyanogenmod-12-1-t3120259
Unlike other unofficial CyanogenMod builds, these builds are based off of the stable branch instead of the nightly branch.
Custom kernels are not compatible with this ROM unless otherwise noted. I will NOT provide support if you install a custom kernel.
ROM features:
- Based off latest generic CyanogenMod 13.0 stable sources (root access is NOT included)
- OTA updates via built-in CMUpdater
- OxygenOS camera libraries (no camera bugs and improved camera performance)
- Snapdragon Camera app by Qualcomm (comes with many unique features, such as high-speed recording with audio)
- Custom camera HAL I made myself from CAF featuring:
-Intelligent anti-shake algorithm (significantly reduces motion blur when capturing photos)
-Faster autofocus in low lighting conditions
-No stuttering/frame drops in camera viewfinder (viewfinder frame rate won't go below 30 FPS)
-Slow-motion video recording at 60 FPS, 90 FPS, and 120 FPS for 720p, and 60 FPS for 1080p
-High-speed video recording with audio at 60 FPS, 90 FPS, and 120 FPS for 720p, and 60 FPS for 1080p (you need to use the Snapdragon Camera app in order to use high-speed recording)
-1080p video recording with the front-facing camera
-2.5k 1440p video recording with the front-facing camera and back camera (only with the Snapdragon Camera app that comes with the ROM)
-4k video recording at UHD and DCI resolutions
-Manual focus
-Manual ISO control
-Slow shutter (ranging from 1/5000th of a second to 2 seconds)
-More picture sizes than plain OxygenOS, such as 9.7MP 16:9 - Many other misc. improvements under the hood
Kernel features:
- Based off latest CAF Marshmallow kernel source from Qualcomm (LA.BF.1.1.3_rb1.13)
- Removed lots of excessive bloat
- Rewrote battery driver (for the BQ27541 fuel-gauge chip; battery % readings are more accurate, there are various
safety mechanisms now, and you may get better battery life) - Rewrote half of the Synaptics touchscreen driver (over 2500 lines of code modified; your touchscreen may work better)
- Newest-available Synaptics touchscreen firmware
- Dynamic CPU input boost driver I wrote myself (makes the phone feel smooth without destroying battery life)
- CPU underclocked to 1958MHz by default (you can disable this; see why I did this in the FAQ in the 3rd post)
- Vibrator is automatically disabled when recording videos (so the buzzing noise doesn't get in the videos)
- Custom thermal control driver I wrote myself (features 8 thermal throttle steps; keeps the phone cool)
- LCD KCAL by Savoca
- Westwood TCP congestion algorithm (enabled by default)
- F2FS support
- NTFS support
- No placebo patches, features, or compiler "optimizations"
- Many other misc. improvements not listed here
Source code:
Kernel (cm-13.0-caf branch): https://github.com/sultanxda/android_kernel_oneplus_msm8974
Local manifest (contains the rest of the sources): https://github.com/sultanxda/android/blob/master/bacon/cm-13.0-stable/local_manifest.xml
Credits:
- CyanogenMod and its contributors
- CAF (aka Qualcomm)
- myfluxi (awesome friend with lots of amazing contributions)
- 69gm (loyal guinea pig)
- Open GApps
- If your name should be here and it isn't, then make me use an iPhone 4s running iOS 9
Installation instructions (for first-time installation):
First, perform a backup of your existing setup, and then perform a clean install (wipe /data and /system; TWRP is recommended). Next, try flashing the ROM and see if it installs; if it installs without any issues then congratulations! Now just flash a Google apps package, and then reboot.
If you get an error when trying to install ("oppo.verify_trustzone" error), then first you must install/use TWRP recovery 3.0.2-0. Next, download and flash the latest official CM13.0 snapshot. Then, without rebooting from recovery, wipe /system and flash my ROM. This process is necessary to update various firmwares (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, SuperSU (ONLY v2.65 OR HIGHER) if you want root access, and then reboot.
Installation instructions (for updating to a newer release):
If you are already running my CM13.0 ROM, then you can update to a newer version of the ROM via the built-in OTA updater or by simply dirty-flashing the new ROM build without wiping anything. HOWEVER, do NOT reinstall Google Apps after installing a new update.
Downloads:
ROM:
Google Apps (required): Platform: "ARM", Android: "6.0", Variant: "micro" or "nano" (I will not provide support if you install a different variant)
SuperSU (if you want root access): http://xdaforums.com/showthread.php?t=1538053
Disable CPU underclock (optional): http://xdaforums.com/devdb/project/dl/?id=15052
XDA:DevDB Information
CM13.0 with clean 3.4.0 kernel, ROM for the OnePlus One
Contributors
Sultanxda
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2015-11-06
Last Updated 2018-01-20282FAQ:
1. Could you add camera slow-shutter times greater than 2 seconds?
Answer: No, I cannot. The reason why exposure times are capped at 2 seconds is due to the proprietary camera libraries from OxygenOS. Only OnePlus and Cyanogen Inc. can modify the proprietary camera libraries, so there is no way for me, a regular consumer, to implement exposure times greater than 2 seconds.
2. Why did you use OxygenOS camera libraries? They don't have 4K camcorder support!
Answer: My custom camera HAL enables 4K camcorder support with Oxygen's camera libraries, so this isn't an issue. Cyanogen's camera libraries have had some issues with the camcorder since day 1. The big issue that I have been able to reproduce on all OnePlus One devices I've come across is graphical artifacts in recorded videos (look towards the right @25 seconds): https://youtu.be/LyIbb5wIyfY?t=22s
(issue report on JIRA: https://jira.cyanogenmod.org/browse/BACON-3582)
OxygenOS' camera libraries do not have this issue, and thanks to my modifications, we now have 4K camcorder support with the OxygenOS libraries, so not much is lost by using them. The OxygenOS libraries can also take pictures faster/better than Cyanogen's libraries.
3. Why did you underclock the CPU to 1958MHz? Yer crazy, bro.
Answer: At 1958MHz, the amount of heat generated by the CPU is quite a bit less than at 2457MHz, so the CPU is throttled less often (leading to better user experience), and battery life is better as well. The performance difference between 1958MHz and 2457MHz is also not really noticeable unless you use a benchmark application. If you want to remove the CPU underclock then flash the zip from the first post that disables the underclock. You must flash this zip every time you install a new ROM update.120Bug megathread?
So reading this entire thread and seeing the information is all scattered, I gathered the following points (the links are usually to the post where the bug/bugfix was reported):
As of Nov 21, 2015: http://xdaforums.com/showthread.php?p=63937573
Nov 9th:
- People coming from Sultan's CM12.1 ROM should NOT dirty flash, but (as expected), it is possible to dirty flash newer CM13 builds by Sultan on top of this, as reported on this post. For the moment, however, I recommend clean flashes, as some corrupted data issues have been reported, too.
- Stock SuperSU should be used, do NOT flash the SuperSU zip. Enable it on Developer Options.
- Gapps: apparently Now on Tap doesn't work with all Gapps packages. Recommended one is SLIM Gapps, or Banks Dynamic Gapps, according to this post by @firenxe. DeltaMM Gapps seem to be working fine, as well. OpenGapps DO NOT WORK, but apparently will on the Nov. 8 build.
- Even if you have the right package, Google Now on Tap will have issues with Software Keys. So, in order for it to work: turn Software Keys ON, turn Now on Tap ON, the disable Software Keys. This has to be done after every reboot, apparently. This post can also help.
- Facebook does not FC anymore, as Sultan reports on the OP.
- Changing the
notification(not anymore, as of Nov. 9 build) battery light behavior results usually in a FC. - Battery life seems to be a bit better than Lollipop, as reported on this post, by @vicky2131. @Sayed Khadri reported 5h+ SOT with moderate browsing and WiFi on.
- Restoring using TitaniumBackup seems to be a hit and miss thing for the moment. Some report it's just fine, some have created a restore zip using TB, and flashed it.
- Seems to be working with MultiROM (didn't find posts explaining how the got it to work), but only as secondary ROM, according to this post.
- APN settings have been reset on some phones. Make sure to write your APN settings down, just in case.
- Sultan reports this as a daily driver, and says he has encountered no issues with Snapchat.
- Apparently Hardware Buttons' brightness can't be changed, they just revert to stock values.
- There seem to be issues with charger sound notification. Apparently, when the plug-in sound is set to on, there's a SystemUI crash. Try to avoid using this sound setting.
- If WiFi is draining your battery, turn off Wifi and Bluetooth scanning in the Settings menu. Follow the instructions in this post to fix.
- Root seems to be hardly working on some File Managers, although no issues with CM File Manager have been reported.
- For Bluetooth music streaming setup, this post by @GruZone might be useful.
- Some users are saying the charging is pretty slow.
- Changing the Preferred Network Type will FC.
- Some issues with WhatsApp notifications have been reported, too.
- Nov 6th build doesn't have Advanced Reboot options.
@Sultanxda this post might be helpful.
I don't think I can keep up with newer bug reports, so whoever's maintaining this thread, feel free to base newer bug reports on this one.
UDPATE: Nov. 9. @HonsW expands on instruccions about MultiROM use (thanks!).
HonsW said:
@AmazingHorse adds:
AmazingHorse said:93
I just tried 14.1 on my OP3 and it's still too unstable IMO. I might make a 14.1 ROM for the OPO over the summer when it's more stable and when I'm not busy. Right now my school/work schedule doesn't leave me with a lot of free time
