[EOL][ROM+KERNEL][6.0.1] Unofficial CyanogenMod 13.0 with 3.4.0 kernel [Apr 30, 2017]
- Thread starter Sultanxda
- Start date
Arty A3 to Android 6 or higher?
Hello, i have Gigabyte Gsmart Arty A3. My stock firmware looks all different than others custom roms downloaded. All i can do is reinstall the stock via FlashTool with scatter file. Can you help me, how to get Android 6 or higher version to my phone? Thanks for replies
Hello, i have Gigabyte Gsmart Arty A3. My stock firmware looks all different than others custom roms downloaded. All i can do is reinstall the stock via FlashTool with scatter file. Can you help me, how to get Android 6 or higher version to my phone? Thanks for replies
G
GuestK0061
Guest
Tried a few MM roms and it seems the playstore download speed is slow. Somewhere between 200 and 300 kB/s, proper in nougat and oreo.
T
Thanhtho96
Guest
I have same problem when I installed jgcaap cm13 months ago. Don't know how to fix it
G
GuestK0061
Guest
T
Thanhtho96
Guest
I too had the same problem, every MM rom out there that I tried. I tried so many fixes too but theydid not work. I have 30 Mbps connection but playstore always downloads hardly at 512 Kbps to max 1 Mbps. All other downloads work fine though. Moved to Nougat and the problem is solved. Wonder what this issue could be.
D
Deleted member 6870501
Guest
[/COLOR]
I've been on jgcaap's cm13 ROM with the color os camera hal for the last 2 years and never experienced said issue. I use magisk for root and micro g instead of flashing google in to my ROM. I also use yalp store from the f-droid app store to access google play store apps. Its a complete proper replacement for the proprietary play store. It runs faster, uses less resources, and its fully open source. Getting download speeds up to 4MB/s on my unlimited t-mobile plan.
I agree that MM is old now, but many of the latest N and O ROMs completely lack sultan's camera hal. Without it the oneplus one's camera is poop.
I've been on jgcaap's cm13 ROM with the color os camera hal for the last 2 years and never experienced said issue. I use magisk for root and micro g instead of flashing google in to my ROM. I also use yalp store from the f-droid app store to access google play store apps. Its a complete proper replacement for the proprietary play store. It runs faster, uses less resources, and its fully open source. Getting download speeds up to 4MB/s on my unlimited t-mobile plan.
I agree that MM is old now, but many of the latest N and O ROMs completely lack sultan's camera hal. Without it the oneplus one's camera is poop.
@Sultanxda
I would really appreciate your help, cause I got a problem and you may know how to solve it. I had to chaged my old battrie for my oneplus one to a new one but the every OS is refusing to notice the change, i did test the real capacity using a Skyrc MC3000 prof. charger and ist about 3500mAh. When im in the recovery mode i can use the full capacitiy but every OS and kernel i have tested will ignore the real capacity and will only give me the estimatet capacity (1200mA) by the battrie IC gauge chip on the OPOs mainboard called BQ27541 from texas instrument. This chip ( BQ27541 fuel-gauge chip) is telling the OS im got only a 1200mAh battrie now because of his wear leveling algorithm wich can not be resettet as i know. Also this algorithm will not recognize the real capacity over time by trying to calibrate by charging and discharging (I teste every calibration methode i can find). Everey time my phone was fully charged to 100% (@4,313 Volt) and it is going down to 0% (@4,1 volt?) after a few minutes i can restart the phone(without charging) and i will get once more 60 - 90% rest batteri capacity until the battrie is really empty (3,5 volt). Is there any posibillity to make a workarround with your kernel, maybe you could bring the OS to use the same batterie guage algorithm as the recovery wich is calculating right or to bring the OS to ignore/bypass this information from the IC BQ27541 fuel-gauge chip.
I am still very satisfied with my OPO cause its still a good phone any answere would very nice.
---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------
[/COLOR @Sultanxda
I would really appreciate your help, cause I got a problem and you may know how to solve it. I had to chaged my old battrie for my oneplus one to a new one but the every OS is refusing to notice the change, i did test the real capacity using a Skyrc MC3000 prof. charger and ist about 3500mAh. When im in the recovery mode i can use the full capacitiy but every OS and kernel i have tested will ignore the real capacity and will only give me the estimatet capacity (1200mA) by the battrie IC gauge chip on the OPOs mainboard called BQ27541 from texas instrument. This chip ( BQ27541 fuel-gauge chip) is telling the OS im got only a 1200mAh battrie now because of his wear leveling algorithm wich can not be resettet as i know. Also this algorithm will not recognize the real capacity over time by trying to calibrate by charging and discharging (I teste every calibration methode i can find). Everey time my phone was fully charged to 100% (@4,313 Volt) and it is going down to 0% (@4,1 volt?) after a few minutes i can restart the phone(without charging) and i will get once more 60 - 90% rest batteri capacity until the battrie is really empty (3,5 volt). Is there any posibillity to make a workarround with your kernel, maybe you could bring the OS to use the same batterie guage algorithm as the recovery wich is calculating right or to bring the OS to ignore/bypass this information from the IC BQ27541 fuel-gauge chip.
I am still very satisfied with my OPO cause its still a good phone any answere would very nice.
I would really appreciate your help, cause I got a problem and you may know how to solve it. I had to chaged my old battrie for my oneplus one to a new one but the every OS is refusing to notice the change, i did test the real capacity using a Skyrc MC3000 prof. charger and ist about 3500mAh. When im in the recovery mode i can use the full capacitiy but every OS and kernel i have tested will ignore the real capacity and will only give me the estimatet capacity (1200mA) by the battrie IC gauge chip on the OPOs mainboard called BQ27541 from texas instrument. This chip ( BQ27541 fuel-gauge chip) is telling the OS im got only a 1200mAh battrie now because of his wear leveling algorithm wich can not be resettet as i know. Also this algorithm will not recognize the real capacity over time by trying to calibrate by charging and discharging (I teste every calibration methode i can find). Everey time my phone was fully charged to 100% (@4,313 Volt) and it is going down to 0% (@4,1 volt?) after a few minutes i can restart the phone(without charging) and i will get once more 60 - 90% rest batteri capacity until the battrie is really empty (3,5 volt). Is there any posibillity to make a workarround with your kernel, maybe you could bring the OS to use the same batterie guage algorithm as the recovery wich is calculating right or to bring the OS to ignore/bypass this information from the IC BQ27541 fuel-gauge chip.
I am still very satisfied with my OPO cause its still a good phone any answere would very nice.
---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------
[/COLOR @Sultanxda
I would really appreciate your help, cause I got a problem and you may know how to solve it. I had to chaged my old battrie for my oneplus one to a new one but the every OS is refusing to notice the change, i did test the real capacity using a Skyrc MC3000 prof. charger and ist about 3500mAh. When im in the recovery mode i can use the full capacitiy but every OS and kernel i have tested will ignore the real capacity and will only give me the estimatet capacity (1200mA) by the battrie IC gauge chip on the OPOs mainboard called BQ27541 from texas instrument. This chip ( BQ27541 fuel-gauge chip) is telling the OS im got only a 1200mAh battrie now because of his wear leveling algorithm wich can not be resettet as i know. Also this algorithm will not recognize the real capacity over time by trying to calibrate by charging and discharging (I teste every calibration methode i can find). Everey time my phone was fully charged to 100% (@4,313 Volt) and it is going down to 0% (@4,1 volt?) after a few minutes i can restart the phone(without charging) and i will get once more 60 - 90% rest batteri capacity until the battrie is really empty (3,5 volt). Is there any posibillity to make a workarround with your kernel, maybe you could bring the OS to use the same batterie guage algorithm as the recovery wich is calculating right or to bring the OS to ignore/bypass this information from the IC BQ27541 fuel-gauge chip.
I am still very satisfied with my OPO cause its still a good phone any answere would very nice.
HUGE THANKS to you Sultan!
For the last two and a half years I have used this great ROM on my OPO as daily driver and had zero issues and a well improved UI I loved using.
I have just now upgraded to HavocOS since it's really time to go for a newer version (which is astonishing to still get recent Android for our beloved bacon!).
I just wanted to thank you for making such a good product for me for years!
Cheers
For the last two and a half years I have used this great ROM on my OPO as daily driver and had zero issues and a well improved UI I loved using.
I have just now upgraded to HavocOS since it's really time to go for a newer version (which is astonishing to still get recent Android for our beloved bacon!).
I just wanted to thank you for making such a good product for me for years!
Cheers
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://forum.xda-developers.com/one...m-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://forum.xda-developers.com/showthread.php?t=1538053
Disable CPU underclock (optional): http://forum.xda-developers.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://forum.xda-developers.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
