CyanogenMod 13 For F320
Please NEVER upload this rom to other forum or file share service.
Please contact me before modifying this rom.
Originally Posted by cyanogen
Code:
#include
/*
* 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.
*/
Click to expand...
Click to collapse
Recommend Recovery : TWRP 2.8.7.X or above
Working on CM13
- Cellular(Call&Data)
- Wi-Fi
- GPS
- Sensors
- seLinux
- SD Card(w/ exFat FS)
- and all features except below
Not Working on CM13
- VoLTE
Known Bugs
- Not reported
Change Log
- Sep 4
* Merge latest kernel and device sources from cyanogenmod
- June 12
* Merge latest kernel and device source
* Fix battery icon width
- May 15
* Kernel Timer changed(100hz to 300hz). it increases performance without more power costs.
* TCP buffer define location changed(init -> overlay)
- Apr 10
* Fix Lockscreen's shortcut starts apps(camera, googlenow, etc...) while touch other area.
- Apr 3
* increase speak volume from F320K Stock Lollipop's mixser_path.xml
* merge d802 kernel, g2-common source.
- 14 feb
* fix media playback error when seek.
* change default governor to ondemand and customize for msm8974 ap.
* change iosched on init.g2.rc ( bfq -> fiops: for more battery)
* fix invalid number.
- 27 Jan
* sync latest cyanogenmod repos. system is more stable.
- 10 Jan
* Update init.g2.rc
> android 6.0 has changed storage mount like externalSD or USB OTG.
I change storage mount(fstab and etc...). Now can Boot!
* Change Default Governor: SmartassH3
* Change Default IO Sched: fiops
* update power_profile for f320*
- 8 Jan
* rebase all source
- 25 Dec
* Add IOSCHED, CPU GOV, ExtSD, EXFAT
Installing Guide
Precondition :
KK Bootloader and LP BootStack are required in order to install this ROM.
You may also need new Modem for working radio
1. Flashing LP BootStack (If upgrade old version, this is not needed)
1-1. Wipe factory reset, Wipe /system (IMPORTANT, Never Dirty Flash from CM-12.1 or others.)
2. Flashing Modem(If you first install)
3. Flashing CM13
4. Flash Gapps
5. Reboot
Source Code
Github : https://github.com/whdgmawkd
android_device_lge_f320, android_device_lge_g2kr-common,android_kernel_lge_msm8974_kr
Special Thanks to
CyanogenMod (Rom Source)
TheMuppets (CM vendor)
lg-devs (LP BootStack)
mpeople (KitKat Bootload for each F320S/K/L)
Download Link
I'm not fluent in English. Sorry for my poor English.
Modem : https://www.androidfilehost.com/?w=files&flid=46208
It was included KitKat Bootloader and LP Modem and etc.
Stable ROM : https://www.androidfilehost.com/?w=files&flid=46198
Download "cm-13.0-20160903-UNOFFICIAL-f320.zip"
Customized ROM by @pipyakas : https://www.androidfilehost.com/?fid=24591023225176446
* Changelog
- Compiled with UBERTC 5.3 for the rom and Architoolchain 4.9 for the kernel
- -O3 optimization flag, I'm working on further optimizations like graphite or full archidroid optimizations
- 3.4.112 linux kernel, I added 2.65ghz CPU OC and 650mhz OC, for the kernel I'm trying to implement zram and fastcharge, also I'm looking to modify ondemand governor for better balanced between performance and battery
This is my experimental build with some changes I like, everyone feel free to test it and give me feedbacks, also any advice would be awesome as I only have a month of experience in android building
Gapps : Use anything support 6.0.X. Recommend OpenGapps.
Merry Christmas.
Thank you for your work.
I shall test it. if it has the same bug i have with another marshmallow rom, i will re use the report i did on the prev rom. wish me luck
It won't boot on my F320L. It gets stuck at LG logo. My steps: Wipe data, cache, system, dalvik. Install F320L_KK_bootloader_plus_LP_bootstack.zip. Reboot to recovery. Install ROM. Is it supposed to boot on F320L?
wont boot on f320k. tried from Vanir 6.0.1 (f320 also) and didn't work. there is no reason for me to flash a bootloader/stack because I am on marshmallow. Please help
Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more
adriannxda said:
It won't boot on my F320L. It gets stuck at LG logo. My steps: Wipe data, cache, system, dalvik. Install F320L_KK_bootloader_plus_LP_bootstack.zip. Reboot to recovery. Install ROM. Is it supposed to boot on F320L?
Click to expand...
Click to collapse
For F320S/K
somboons said:
For F320S/K
Click to expand...
Click to collapse
Previous versions cm12.1 booted and worked fine. It should work on F320L outside Korea.
did anyone manage to boot on this rom? mine won't go past the LG logo
f320s .The same as yous.can't boot with LG LOGO .
liusi522 said:
f320s .The same as yous.can't boot with LG LOGO .
Click to expand...
Click to collapse
I'm Hoping @parkjh0821 Senpai can fix this
planning on fixing the fact it won't go past the LG logo ? don't worry, take your time its usually like this on all first builds XD
I'm sorry for late.
I found It cant boot because rom has critical problem. but I dont know why it cant boot.
boot image is OK. maybe overlay(ExtSD Patch) make this problem.
but I dont have enough time to build new cm13.
it will take long time to release new build.
parkjh0821 said:
I'm sorry for late.
I found It cant boot because rom has critical problem. but I dont know why it cant boot.
boot image is OK. maybe overlay(ExtSD Patch) make this problem.
but I dont have enough time to build new cm13.
it will take long time to release new build.
Click to expand...
Click to collapse
It's not your fault. It's just your job no return.Just Do your own thing.
When you have a new building in your free time, I'll test.Thanks
its ok. take ur time. aslong as in the end, we will have a booting cm13
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
parkjh0821 said:
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
Click to expand...
Click to collapse
Continue trying, good luck!
parkjh0821 said:
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
Click to expand...
Click to collapse
Thank you for your work.I will test tomorrow .
tested
wont go through the cyanogen mod boot animation
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
This rom is for the Asus TF300T with or without dock.
Special thanks to: XpLoDWilD, bumble-bee (for tf201 device tree from which this original tree was inspired), loganmc10, dasunsrule32, jruesga, cyanogenmod, pawitp, etc.....
recent changelog:
- DRM with widevine fixed (that makes google play movies work). Thx go to stargo!
Older changelog:
- f2fs added
Changelog for version 0.2:
- resync with CM-12
- sync kernel with lots of stuff from grouper (and/or thoemy's endeavoru).
Chris
Not working:
- dock battery status
- GPS orbit downloads
- some dock keys (including wake up by pressing dock keys)
Installation instructions:
- put zip on sdcard
- reboot to recovery (seems that you have to first: unmount /data).
- flash zip
- wipe (have not tried if upgrade from kitkat works and won't test this anyway)
For newer updates with CM updater and/or if you want f2fs, you might need a new recovery. Here is the cm recovery from 5-FEB-2015: recovery-cm-5-FEB-2015.img
Flash this with:
adb reboot bootloader
fastboot flash recovery recovery-cm-25-JAN-2015.img
fastboot reboot
Chris
CM12!
Get ready to flash!
Definitely worth a flash.
Dear chris,
Is it work on canvas 2 plus????
Chipset is mtk6589..
Waiting for your reply...
If not please work on this...
Thanking you..
I tried to encrypt the device. I Let it run for ~3 hours. Stuck on boot.
But great start
EDIT: SO Ill start testing this ROM now
Got my first reboot. And RIGHT now in this time of this writing my second reboot
Here is the first log. Second to come.
EDIT2: Second log added
Any developpement
@chrmhoffmann
I see you uploaded a huge bunch of patches for CM12. Thank you very much for all your efforts
[GER]Roxxor said:
@chrmhoffmann
I see you uploaded a huge bunch of patches for CM12. Thank you very much for all your efforts
Click to expand...
Click to collapse
No prob. I just re-synced the kernel with stuff from grouper. Those things are not really necessary for cm-12.0
EDIT: there's a new 0.2 version that has recent changes.
Chris
willing to try
I loaded the Omni version which worked but was a little slow - using ART not DALVIK. If anyone else tries this, I found the experience was interesting - you will have to choose a small(er) version of GAPPs to fit on the system partition. I used the version on the XDA PA-GAPPs site that was just over 200 MB in size. I'm back using CM11 because I use this puppy every day.
Official cm12 is out but no tf300
Selinux is not in enforced mode so I can't enable nightlies. That's a must for cm now. If any one can help me on that...
Chris
hi, just had a go with the rom seems very good but i couldnt connect to the internet, keep up the good work
thanks
chrmhoffmann said:
Selinux is not in enforced mode so I can't enable nightlies. That's a must for cm now. If any one can help me on that...
Chris
Click to expand...
Click to collapse
And how was that in cm11 then?
Sent from my TF300T using XDA Premium 4 mobile app
androidjel said:
And how was that in cm11 then?
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It was not a hard requirement to have Selinux enabled in cm-11.0. It is now a minimum requirement from CM.
BTW: I have fixed the major selinux denials now and the tf300t is now accepted on the official CM nightlies.
Chris
Since I installed cm snapshot 12 it won't appear any nightlies updates.. How can I search them with the cm updater?
igoigo said:
Since I installed cm snapshot 12 it won't appear any nightlies updates.. How can I search them with the cm updater?
Click to expand...
Click to collapse
Download a nightly and place it in the cmupdater folder. Go to your updater and flash the nightly that shows up. After reboot you will see nightly's again.
chrmhoffmann said:
It was not a hard requirement to have Selinux enabled in cm-11.0. It is now a minimum requirement from CM.
BTW: I have fixed the major selinux denials now and the tf300t is now accepted on the official CM nightlies.
Chris
Click to expand...
Click to collapse
So we will see cm12 official nightlies appear on cyanogenmod.org soon?
counterfeit187 said:
So we will see cm12 official nightlies appear on cyanogenmod.org soon?
Click to expand...
Click to collapse
Ones just finished being built downloading now
Thank you guys, for the awesome work you do!!!
Edit: Is there an installation guide?
I cant seem to get this to clean install
ricktendo said:
Thank you guys, for the awesome work you do!!!
Edit: Is there an installation guide?
I cant seem to get this to clean install
Click to expand...
Click to collapse
What's the issue? You should be able to flash this with the existing CWM recovery (from the CM11 thread).
Chris
Intro:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
*/
About CyanogenMod:
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Not working:
- Using device microphone instead of headset mic in calls
You need the newest version of TWRP to flash this rom!
Downloads:
20160826
Google Apps (not required)
Installing guide (thanks to @Amish):
Download the rom and copy it to sd card
Boot into bootloader and flash this recovery
Boot into recovery
Wipe data/factory reset
Wipe cache partition
Select install zip from sd card.
Install the rom-zip.
Extract boot.img inside the roms zip-file.
Boot into bootloader and flash the kernel:
Code:
fastboot flash boot boot.img
Reboot your device, it will take about 10 to 20 min to boot.
Russian installing guide (thanks to @VFox777):
XDA:DevDB Information
CyanogenMod 11, ROM for the HTC One V
Contributors
jonas2790, rastomanchik
Source Code: https://github.com/AndroidPrimou/android_device_htc_primou/tree/cm-11.0
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Stable Release Date: 2016-08-26
Created 2015-03-15
Last Updated 2016-08-26
Changelog:
20160826:
- Security fixes
- Reverted some wifi changes
20160702:
- Fixes of the may and june android security bulletin
- Kernel security fixes
- Increased wifi voltage and other wifi changes
20160413:
- Fixes of the april android security bulletin
- Kernel security fixes
- Added a workaround to use handset microphone when calling with headset
- Fixed some audio bugs
20160312:
- Fixes of the March android security bulletin
- Added vdd sysfs interface for voltage control
20160207:
- Fixes of the February android security bulletin
20160108:
- Important security fixes from the android security bulletins
20150916:
- Set the default scheduler to FIOPS
- Added some NAND tweaks
- Minor kernel security fix
20150826:
- Security fixes for new Mediaserver vulnerability
- OTA server optimizations
20150816:
- Fixed the stagefright vulnerability
- Increased available ram
20150712:
- Based on final cm11 snapshot
- Enabled standalone power collapse for battery saving
- Increased earpiece volume
20150620:
- Wifi disconnecting bug fixed
- Music force-close bug fixed
- Wifi-direct support added
- Fixed screen flickering bug
- Panel initialization time improved
- Flashlight now also works when screen is off
- Disabled low-ram ui
20150527:
- Internal storage support (Micro-sd still is the default storage)
- Added DeviceSettings control for doubletap2wake tapping-height
- OTA-Updating support
- Enabled app switching button
- Reduced wifi scanning interval to 15s
- New bcmdhd kernel driver with updated firmware
- Fixed wifi and bluetooth bugs
- Decreased zram size to 128mb
- Fixed noise cancellation for speakerphone
- Improved earpiece sound quality
- Much smaller changes
20150502:
- Using better memory allocation
- Camera bugs and crashes fixed
- Performance improvements
- Changed default governor (Intelliactive)
- Has some wifi bugs again...
20150425:
- Wifi bugs fixed
- Bad earpiece sound fixed
- Added flashlight toggle for quicksettings
- Enabled sd card swapping without reboot
20150421:
- Much more available ram (363mb)
- Device specific settings app added
- Added sweep2wake and doubletap2wake
20150414:
- Video recording bug fixed
- Bass bug fixed
- New kernel with much changes
- Increased zRam size (256mb)
- Much other changes
20150321:
- Headset button issue fixed
- Signal-strength fixed
- ro.config.low_ram enabled (everything should be faster and smoother now)
- Set permissions for /dev/diag
- Enabled zRAM
20150319:
- Earpiece bug fixed
20150318:
- No Gapps workaround needed
- ADB security turned on again
- Disabled KSM
- Updated CM sources
- Some minor changes
- Bug: Earpiece doesn't work
20150315:
- First release
- ADB auth turned off
What are the differences between this and Rastomanchiks file?
Neff_V said:
What are the differences between this and Rastomanchiks file?
Click to expand...
Click to collapse
Not really much differences, I disabled the low_ram prop to get some nice kk effects and I enabled ksm, which may improve performance.
CM file manager works and I didn't include OpenCamera.
By the way: I wrote 1ceb0x, who also had this problem with shpongle and he used precompiled binaries. If we can get those binaries to run on kitkat, bass will work.
Its like dream come true i will flash it asap
gapps and some screenies please.
Thanks.
Installation failed
Amish. said:
Installation failed
Click to expand...
Click to collapse
Short answer: Use my latest twrp.
Long answer: You need a selinux enabled kernel in your recovery. The function set_metadata_recursive which sets selinux-contexts and permissions doesn't work without a selinux supporting kernel.
jonas2790 said:
Short answer: Use my latest twrp.
Long answer: You need a selinux enabled kernel in your recovery. The function set_metadata_recursive which sets selinux-contexts and permissions doesn't work without a selinux supporting kernel.
Click to expand...
Click to collapse
yes i did that..and installation was successfull but now my phone is bricked or what idk...htc logo came once and then black screen past 1-2hrs...cant get into bootloader..no adb..no response to any button..
Amish. said:
yes i did that..and installation was successfull but now my phone is bricked or what idk...htc logo came once and then black screen past 1-2hrs...cant get into bootloader..no adb..no response to any button..
Click to expand...
Click to collapse
Did you flash the kernel (boot.img in archive)?
Hold the power button for about 15 seconds and it should reboot into recovery.
jonas2790 said:
Did you flash the kernel (boot.img in archive)?
Hold the power button for about 15 seconds and it should reboot into recovery.
Click to expand...
Click to collapse
i did a full wipe and flashed the cm11.zip..i tried all those things..holding power button and all nothing..on using adb commands now its saying device is offline.
Thanks for screenies.
Amish. said:
i did a full wipe and flashed the cm11.zip..i tried all those things..holding power button and all nothing..on using adb commands now its saying device is offline.
Thanks for screenies.
Click to expand...
Click to collapse
You can't brick your device by flashing a rom.
Is your phone S-Off or S-On?
Try plugging it into a charger, maybe it has run out of battery.
jonas2790 said:
You can't brick your device by flashing a rom.
Is your phone S-Off or S-On?
Try plugging it into a charger, maybe it has run out of battery.
Click to expand...
Click to collapse
s-on is root right? s-on as per my memory.
Amish. said:
s-on is root right? s-on as per my memory.
Click to expand...
Click to collapse
No, S-On is the HTC restriction for rewriting some partitions, like the kernel partition if you're in recovery mode.
If your phone is S-On (it is by default, even with root and unlocked bootloader), you have to flash a kernel by rebooting into fastboot mode.
So if you didn't flash the kernel, you know the problem now. Did you already get it working again?
jonas2790 said:
No, S-On is the HTC restriction for rewriting some partitions, like the kernel partition if you're in recovery mode.
If your phone is S-On (it is by default, even with root and unlocked bootloader), you have to flash a kernel by rebooting into fastboot mode.
So if you didn't flash the kernel, you know the problem now. Did you already get it working again?
Click to expand...
Click to collapse
I used to directly flash the roms.zip file..never flashed kernel separately..nope its not working..htc one v is the only phone i have..:*
Amish. said:
I used to directly flash the roms.zip file..never flashed kernel separately..nope its not working..htc one v is the only phone i have..:*
Click to expand...
Click to collapse
Can you open a thread in the help forum for this please? What exactly is happening with the phone?
jonas2790 said:
Can you open a thread in the help forum for this please? What exactly is happening with the phone?
Click to expand...
Click to collapse
i guesss it was battery drain or what...it started now...i flashed the kernel using fastboot and adb commands..i guess i will fall in love within few minutes...does boot take long time?
Amish. said:
i guesss it was battery drain or what...it started now...i flashed the kernel using fastboot and adb commands..i guess i will fall in love within few minutes...does boot take long time?
Click to expand...
Click to collapse
Just finished uploading my new build
Yes, first boot does take a really long time.
jonas2790 said:
Just finished uploading my new build
Yes, first boot does take a really long time.
Click to expand...
Click to collapse
Put installation section also..now what should i do...update? i had flashed pico PA-gapps
Amish. said:
Put installation section also..now what should i do...update? i had flashed pico PA-gapps
Click to expand...
Click to collapse
You can do it without a wipe, but I wouldn't, I always do a full wipe.
jonas2790 said:
You can do it without a wipe, but I wouldn't, I always do a full wipe.
Click to expand...
Click to collapse
can we start dreaming about cm12?
Code:
#include
/*
* 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.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Also, there are sister threads for working on pollux, yuga and dogo.
Changes:
- Jan 30: Initial release
- Feb 5: kernel updates, audio HAL modernization
- Feb 9: WiFi updates
- Feb 13: volume rocker wakeup, sdcard hotplug, camera focus changes, cleanups
- Feb 16: new call fix
- Feb 27: F2FS support
- Mar 1: audio update
- Mar 3: smooth boot animation
- Mar 6: more audio updates
- Apr 3: first 12.1 build
- Apr 20: radio fixed
- Apr 22: Android 5.1.1
- Apr 27: tons of cpu and gpu governor updates/fixes, wifi updates
- May 1: gpu gov and wifi updates
- May 7: app2sd fixes, selinux updates, fixed power hal, OSS THERMAL MGMT, wifi fixes
- May 10: plethora of core kernel and platform updates, init changes
- May 22: scheduler and platform updates, reworked kernel configuration
- July 7: lollipop blobs, init update, new sensor drivers, kernel updates
- July 11: fix booting into recovery by toggling volume keys, fixed wlan&bt mac config, fixed off charging mode
- July 20: fixed gps problems under certain circumstances
- July 30: lp kernel updates, als adjustments, led color configuration from ui, gps problems fixed, leds in offline charging mode
- Aug 6: row io scheduler, open source gps hal, fix sd card access and thermal config, update sepolicy and power profile
- Aug 20: minor init updates, thermanager config
- Aug 26: backlight fix, thermanager updates
- Sep 10: io schedulers: include fiops, bfq - use it as default
- Sep 17: sony 5.1 blobs, init changes, performance management in recovery
- May 9: initial CM13 release
- Jul 5: loads of kernel changes, audio hal, and probably plenty of stuff i forgot
All builds are synchronized with the latest CM tree. For the specific updates to fusion3 and yuga, see the source link below!
Download:
For the brave CM13 DEVELOPMENT BUILD:
cm-13.0-20160707-UNOFFICIAL-odin.zip
Dirty-flashing on existing 12.1 upgrades normally to CM 13. Beware you will need compatible GApps though!
Nightlies are now available:
Official download site
This thread will however remain the prime location for testing new stuff and support on yuga.
Installation:
If you have anything other than CyanogenMod 12.1 on your device, do a full wipe, and get Android 5.1 compatible gapps!
F2FS support: take a look here
Testing:
Some very important "rules" for this:
- Run unmodified versions (no FOTA recovery, no modified kernel, no Xposed framework, etc.)
- Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least.
- If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
I will have to ignore all other "problem reports" as they are essentially useless.
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also pollux, odin, and so on).
http://review.cyanogenmod.org
W o W
Hi, Qsnc.....
permission to try your build...
thanks to develop Lollipop for our great ZL :good:
Hi,
whats the Different to the other CM12.1 Thread?
My Problem is, that in all Android5.x.x Versions for Odin, Soundhound is not working, and in Whatsapp call the other hears me very bad, or only a cracking.
I believe, that this is the same issue.
shufuking he has been building cm for odin for a while now why switch? Im curious why you too are building cm for odin now?
i am the device maintainer for fusion3 devices these days. so why use this? because i don't just build from sources, i contribute to them. this thread is meant to help me find errors BEFORE i merge changes into the official cm source tree. and to get feedback and logs on builds i provided - i do not attempt to fix bugs on untrusted builds.
so in short: feel free to use "daily builds" from other sources. if it turns out that i do not get feedback on these builds, i'll just leave these devices behind, and focus on pollux and yuga instead.
qsnc said:
i am the device maintainer for fusion3 devices these days. so why use this? because i don't just build from sources, i contribute to them. this thread is meant to help me find errors BEFORE i merge changes into the official cm source tree. and to get feedback and logs on builds i provided - i do not attempt to fix bugs on untrusted builds.
so in short: feel free to use "daily builds" from other sources. if it turns out that i do not get feedback on these builds, i'll just leave these devices behind, and focus on pollux and yuga instead.
Click to expand...
Click to collapse
Thank you for trying to maintain Odin, qsnc. Question: Isn't Yuga essentially the same as Odin internally? Which means if you decide to continue Yuga, you might as well support Odin.
Baron1971 said:
Hi,
whats the Different to the other CM12.1 Thread?
My Problem is, that in all Android5.x.x Versions for Odin, Soundhound is not working, and in Whatsapp call the other hears me very bad, or only a cracking.
I believe, that this is the same issue.
Click to expand...
Click to collapse
Ok, i quote myself....
Can you do something about the cracking, and the not working Soundhound? What logs you need?
thanks for this. will give feedback soon
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Thanks for this ROM. Great Rom!
Baron1971 said:
Ok, i quote myself....
Can you do something about the cracking, and the not working Soundhound? What logs you need?
Click to expand...
Click to collapse
these problems only happen in those apps? are they reproducible? do others have the same problem(s)?
Ultramanoid said:
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Click to expand...
Click to collapse
you tell me, thats what this thread is for.
qsnc said:
these problems only happen in those apps? are they reproducible? do others have the same problem(s)?
you tell me, thats what this thread is for.
Click to expand...
Click to collapse
For me, it is reproducible! I have these Problems, since i use Lolipop, and i read here, that other People here have the same Problems,
Gapps doesn t works...
cmndst said:
Gapps doesn t works...
Click to expand...
Click to collapse
yo are you clueless? what is anyone supposed to do with this post, how could they possible help you... please read more topics on this forum before posting again thanks!! search how to get good logs or something man geshhh!
Ultramanoid said:
Want to install this and give it a full workout, but does it have a working CWM recovery ? Last time I tried ( with an FXP build ) it didn't, and had to flash a TWRP one or I'd have had no working recovery on the device.
Click to expand...
Click to collapse
It has working CyanogenmodRecovery (not CWM), but is only accesible over advanced reboot options activated in developer Settings and not through key Combinations.
Whatsappcalls and Soundhound are working flawless for me, like everything else withs this rom. :good:
qsnc said:
you tell me, thats what this thread is for.
Click to expand...
Click to collapse
sonar21 said:
It has working CyanogenmodRecovery (not CWM), but is only accesible over advanced reboot options activated in developer Settings and not through key Combinations.
Click to expand...
Click to collapse
Thanks.
I wouldn't say it is a working recovery; can't make backups, can't install GApps ( chokes on signature... ), etc. So one is forced to try to stick TWRP in FOTAKernel. I'm not sure what the purpose of CM's recovery in its current state is.
Edit : Managed to flash GApps but still, really spartan recovery with almost no options, I'd definitely warn users about this.
Edit 2 : With TWRP recovery in FOTAKernel I've been using the ROM as daily driver on this device; no difference or remarkable bug in what I use compared to newer devices I already had on 12.1. Of course it's an older build and lacks features from more recent nightlies, but seems pretty solid so far. Thanks for making this available.
new build available. been off on holidays for a while, and working on pollux and yuga.
what is the status quo of this release?
qsnc said:
new build available. been off on holidays for a while, and working on pollux and yuga.
what is the status quo of this release?
Click to expand...
Click to collapse
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Ultramanoid said:
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Click to expand...
Click to collapse
+1
Ultramanoid said:
Dirty flashed an FXP build over your last one, now dirty flashed this build over FXP's and all's well. In fact these unofficial builds for the ZL work better than the official ones for the Z2, I have to say. Can't find a bug in anything I use on this device.
Click to expand...
Click to collapse
Sorry if I'm missing something, but where is the FXP CM12.1 for ZL?
Note: Official CM13 builds for Oppo Find 7a/s have been released as of 4th December 2015
Unofficial CM13
- Marshmallow-
for
Oppo Find 7a/s
An early taste of Marshmallow...
The original Developer is Wuxianlin.
You can find the ROM download links here - http://pan.baidu.com/s/1jGETpbC#path=%2FCM13-Find7
Mirror (Latest Only) (By Spoonymoon):
cm-13.0-20151127-UNOFFICIAL-find7.zip
https://mega.nz/#!DpVDEKSR!Y-SxMCw83UQAeBQ6txrXZ3-b-IKz_Q7Z1uSu-kpcl6o
cm-13.0-20151110-UNOFFICIAL-find7s.zip
https://mega.nz/#!igMylYRL!pAtLqr8g3Kb8R-NqhfAUnAq8gENhsiia86YOFpwd8eM
- Disclaimer -
Code:
#include
/*
*
* 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.
*/
Click to expand...
Click to collapse
Source Code:
Code:
[url]https://github.com/CyanogenMod/android_device_oppo_find7s/tree/cm-13.0[/url]
[url]https://github.com/CyanogenMod/android_device_oppo_find7/tree/cm-13.0[/url]
[url]https://github.com/CyanogenMod/android_device_oppo_find7-common/tree/cm-13.0[/url]
[url]https://github.com/CyanogenMod/android_device_oppo_msm8974-common/tree/cm-13.0[/url]
[url]https://github.com/CyanogenMod/android_kernel_oppo_msm8974/tree/cm-13.0[/url]
Installation -
For Color OS 2 & 2.1 Users (4.4.2 & 5.0) -
Use third party recovery to Backup (TWRP).
Download Color OS 1.2.8>HERE<
Boot into ColorOS recovery
Wipe data and cache
Flash ColorOS 1.2.8 (It took 5-10 min for me to complete)
Let it boot. Then again reboot to custom recovery (TWRP)
Wipe-> data, cache, dalvik cache, system.
Flash CM13. Reboot.
It takes 5-6 minutes to boot in the first run, so don't do anything stupid.
For Color OS 1 Users (4.3) -
Reboot to custom recovery (TWRP), Have Backup.
Wipe-> data, cache, dalvik cache, system.
Flash CM13. Reboot.
For Custom ROM Users (4.4.x/5.0.x/5.1.x) -
Reboot to custom recovery (TWRP), Have Backup.
Wipe-> data, cache, dalvik cache, system.
Flash CM13. Reboot.
GApps (Mini) - http://downloadmirror.co/android/ss
WORKING :
Unified Storage
Calls/Messaging
Bluetooth
WiFi
GPS
Torch
WiFi Hotspot
Root access
Camera
BUG LIST :
Not all CM customization options integrated
Skyline Notification
Storage
NFC
List will expand if more bugs are found . . .
PATCHES :
Root fix : http://www.mediafire.com/download/713gjcvl9b89mor/BETA-SuperSU-v2.52.zip
Screen density fix for 7s(X9076/X9077) : http://www.mediafire.com/download/t0x9ue80kgql6hg/find7s_patch.zip
Wow now thats fast. Gonna try this soon.
Manas1796 said:
More content is upcoming shortly
Unofficial CM13
- Marshmallow-
for
Oppo Find 7
An early Taste of Marshmallow...
The original Developer's name is "Wuxianlin".
You can find the direct link here - http://pan.baidu.com/wap/shareview?...d7&page=1&num=20&fsid=758500377301006&third=0
Code:
#include
/*
*
* 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.
*/
Installing Instructions -
For Color OS 2 & 2.1 Users (4.4.2 & 5.0) -
Use third party recovery to Backup (TWRP).
Download Color OS 1.2.8>HERE<
Boot into ColorOS recovery
Wipe data and cache
Flash ColorOS 1.2.8 (It took 5-10 min for me to complete)
Let it boot. Then again reboot to custom recovery (TWRP)
Wipe- data, cache, dalvik cache, system.
Flash CM13 (Takes ~40 sec). Reboot.
It takes 3-4 minutes to boot in the first run, so don't do anything stupid.
For Color OS 1 Users (4.3) -
Reboot to custom recovery (TWRP), Have Backup.
WIpe- data, cache, dalvik cache, system.
Flash CM13 (Takes ~40 sec). Reboot.
Click to expand...
Click to collapse
How do I download ? mirrors ??
I saw this posted on the OPPO forums by the same "Wuxianlin", it raises my suspicious eyebrow as it linked to a chinese site with nothing but chinese that google struggled to translate.
I don't dare download it
This is awesome mate….
Thankyou, but NOT able too do from baidu whitout been registered…
Plz provide mirror someone????
I'll flash and test, for sure
Thx in advance
Edit: but why flash cos first??, there's no lvm or special remapping needed, it's cm13??
spoonymoon said:
This is awesome mate….
Thankyou, but NOT able too do from baidu whitout been registered…
Plz provide mirror someone????
I'll flash and test, for sure
Thx in advance
Edit: but why flash cos first??, there's no lvm or special remapping needed, it's cm13??
Click to expand...
Click to collapse
yup i think there is no lvm support just like cm12. waiting for mirror too.
spoonymoon said:
This is awesome mate….
Thankyou, but NOT able too do from baidu whitout been registered…
Plz provide mirror someone????
I'll flash and test, for sure
Thx in advance
Edit: but why flash cos first??, there's no lvm or special remapping needed, it's cm13??
Click to expand...
Click to collapse
StormTrooper89 said:
yup i think there is no lvm support just like cm12. waiting for mirror too.
Click to expand...
Click to collapse
Yup, it has no support for LVM just like CM12 and 12.1
Screenshots will be coming up soon.
I am downloading the ROM with "JDownloader 2 BETA". It does not require a baidu account. My internet speed is pretty slow (Max 60kB/s), so it will take a while before I can upload any screenshots
EDIT: Hey guys the mirrors are up! & LVM is supported
wow Wuxianlin is great, isn't the same dev who made cm12 early builds? i will install after they fix the storage bug, i use my find7 as daily driver... so is a bit too early for me maybe
i hope that the new way to format sd cards as internal storage introduced in M could finally stop forcing me to deal with lvm/coldbird things
thanks for the interesting post and thanks to who made mirrors of course
-lorenzo- said:
wow Wuxianlin is great, isn't the same dev who made cm12 early builds? i will install after they fix the storage bug, i use my find7 as daily driver... so is a bit too early for me maybe
i hope that the new way to format sd cards as internal storage introduced in M could finally stop forcing me to deal with lvm/coldbird things
thanks for the interesting post and thanks to who made mirrors of course
Click to expand...
Click to collapse
Too bad lvm is officially a way to have all internal storage in one place. We can only hope cm will merge it in their rom.
StormTrooper89 said:
Too bad lvm is officially a way to have all internal storage in one place. We can only hope cm will merge it in their rom.
Click to expand...
Click to collapse
I hoped it to, but afaik cm team never talked about any unificatiom method and in their official support they generally avoid this kind of workaround so if i can use a class 10 micro SD with decent results in installing and using apps will be fine to me..
EDIT: i find out a way to open that site with firefox and downloaded the description.txt in the folder, translated from chinese to english with google translator and got this:
Here is stored in the adaptation to Android6.0 Find 7 (CM13)
Subdivision Related:
Android 6.0 the vold dynamically mounted storage, but there seems to be some bug, for Find7 factory district ext4 format internal card mount has a problem, but the 5.0 merge partition is no problem
Screen Related:
CM kernel Find 7 Standard Edition R63419 batch of LCD compatibility is not good, resulting in the video, so this batch friend patience omnirom good caf drive there merge
Brush into the method:
1. brush into twrp recovery
2. Enter TWRP, Shuangqing, brush into ROM package, bug fixes package, ROOT patch, RE Manager patch (Standard Edition plus brush find7s_patch.zip)
3. Restart, eating cotton candy bars
Known bug:
1.NFC
2. Camera incidental FC
3. Built-in browser has problems
The built-in file manager as a problem, put a patch RE Manager
Click to expand...
Click to collapse
the translation is bad but seems that also a couple of zips has to be flashed apart from the rom itself and the gapps, for sure for rooting i see in the folder that the dev has put supersu 2.52 beta
Keeping a close eye on this thread so I can test as soon as the main bugs are handled
downloading via browser ends browser application... i tried downloading fdroid apk...
So anyone try to merge the stock oppo storage "3GB(apps)+23GB(video,photos,music, etc...)" with new Android M format function??
http://www.androidpolice.com/2015/0...or-accessed-normally-with-no-additional-apps/
can someone link me a gapps package compatible with this rom? the one i used broked the installation wizard and i can't go on
-lorenzo- said:
can someone link me a gapps package compatible with this rom? the one i used broked the installation wizard and i can't go on
Click to expand...
Click to collapse
http://downloadmirror.co/android/ss
Worked for me...
spoonymoon said:
Edit: but why flash cos first??, there's no lvm or special remapping needed, it's cm13??
Click to expand...
Click to collapse
You need to flash ColorOS because of the Modem issue. The original CM source code used the ColorOS 4.3 Modem as reference and built their ROM. And they still continue to use that source so just for installing the 4.3 modem, you have to install COS 1. ( Note: If incompatible modem is used, your carrier service would not work and you will not receive any signal )
There is a newer version out today, but i can't download it from "baidu"! Maybe someone can add it to driver folder?
Nu_Pogodi said:
There is a newer version out today, but i can't download it from "baidu"! Maybe someone can add it to driver folder?
Click to expand...
Click to collapse
added
Just me with bootloop on today's version?
DISCLAIMER
Code:
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.
Steps to install:
(0. Install any 6.0 rom)
1. Factory reset
2. Make sure you format /system and /data to ext4 for the install
2. Install ROM zip, you will get a warning about partition size change of system if its the first time you flash, just flash it a second time to confirm the change, this will erase your data partition!
3. Please do NOT install Gapps (you can still do it, but at your risks)
4. Reboot
5. Wait for a long time
Known Bugs:
- First boot is slow
- RIL sudden crash (?)
- Webkit render issues with the latest cm14.1. It will be fixed in the next build.
- CM's FileManager is bugged
Features:
- Stock Cyanogenmod 14.0
- Dirty CoW patched kernel (anyone cares ?)
- kernel built with GCC 6.2.1 with -03
- F2fs support on /data but not on /system
- Bigmem enabled (no cma for now)
- sdcardfs support to come someday
- Zram enabled
Please note that this rom is not ready for daily usage yet, it's an alpha.
Downloads:
Android 7.0:
http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
Android 7.1.1:
http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip
I will provide mirrors later if needed.
Please check the MD5 !
094fa2133073f22cea28e80d18a628e5
HUGE thanks to @xc-racer99 for his AMAZING work on his variant, without him, this woudn't have been possible at all.
XDA:DevDB Information
CyanogenMod 14.0, ROM for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99, sooti
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2016-10-28
Last Updated 2016-12-23
Reserved
Changelog:
23/12/2016
Android 7.1.1 r6
No more crashes due to the graphic driver
Working ril (except data on the first boot apparently ?)
Fixed internal storage issues
Updated kernel
Latest TWRP (without their new app, tell me if you want me to add it back)
20/11/2016
Latest CM 14.0
As people wanted, cmc is back
Tweaked art settings (lag should be gone)
Fixed video recording
Fixed MTP crash
Fixed adb authkey issue
Disabled SDcardFS
More stable RIL (but there are still issues with 3g)
28/10/2016
Initial release
Reserved
FAQ & tips :
Where is SuperSU ?
You don't need to flash SuperSU, just enable it under the Developer options.
How to change Bigmem modes ?
You can change it in advanced parameters>Bigmem
What are the best schedulers/governors/...
That's up to you, personaly, I like the combinaison of smartassV2 and bfq.
But ... how to change them ???
You can use Kernel Adiutor or any other app like that.
When will you release the next build ?
Don't ask for ETA ..... and wait.
Something isn't working, please fix it, please PLEASE
Logcat. No logcat == no fix.
If you don't know how to logcat properly, read this.
My phone is bootlooping ,what can I do ?
Pull battery and restart. Also don't forget to do a factory reset before flashing this rom.
Can you add X feature on your rom ?
No. I wont add additional features, this is stock cm. The only thing I might add is signature spoofing support.
Here are a few additional tips to get the most of this rom :
Format /data in f2fs in TWRP
OC your cpu if it can handle it
Use Bigmem
Don't install unnecessary apps
Remove apps from startup
(Wait for the next build)
Wow!!! It is impossibly! Big thanks!!!
+1
:good:
Link is up, make sure to check the md5sum and tell me if you experience issues.
Logcats appreciated !
Ok, just tested it. Was compared with AOSP 7 from x-racer99.
Seems CM14 more laggy in games. Not so smooth like an AOSP. But problem probably is not in the kernel. Cause i was also use x-racer99 kernel on your CM14 rom. Look at this videos with Mega Jump game:
https://youtu.be/ueyjuPu3BgA AOSP rom by x-racer99
https://youtu.be/FWbCNKZdAdE Cyanogenmod 14 rom with x-racer99 kernel.
Second video is not so smooth with a lot of jerks. May be problem in low memory killer settings, or GFX drivers, or V-Sync, or build.prop tweaks, i do not know.
Also i prefer CMC instead Voodoo Color. Because VoodooColor have two bugs since android 2.x.x. It is yellowish tint of all screen (CMC have more right white balance) and green bug on low backlight with high gamma settings, look at this video:
https://youtu.be/gkP7VgWbTlY
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
About CMC, you can tweak voodoo by yourself, but yeah if many people want me to switch to CMC, I will do it.
Coldwindofnowhere said:
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
Click to expand...
Click to collapse
You can just download Subway Surfer from market or another place and try to make run this game more smoother. Some times Subway Surfer have bad responce on touch and can hung up after long play. Also can try this on Mega Jump or other dynamic game.
Thank you!
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
P.S. Issue with MXplayer was resolved by itself after reboot phone.
M1n3cr4f7.G4m35.2015 said:
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
Click to expand...
Click to collapse
Um pull off the battery, start the phone again. Got this issue once but no idea why.
jupiter5700 said:
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
Click to expand...
Click to collapse
Bigmem patched, I haven't tested 720p videos tbh.
This rom can run on samsung wave?
thinhx2 said:
This rom can run on samsung wave?
Click to expand...
Click to collapse
I haven't tried but as it's really similar to the i9000, you should give it a try.
Coldwindofnowhere said:
I haven't tried but as it's really similar to the i9000, you should give it a try.
Click to expand...
Click to collapse
Screen is different. You think driver display of i9000 can work on wave?
thinhx2 said:
Screen is different. You think driver display of i9000 can work on wave?
Click to expand...
Click to collapse
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Coldwindofnowhere said:
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Click to expand...
Click to collapse
You can public your kernel for aosp 7 of ss s1?
thinhx2 said:
You can public your kernel for aosp 7 of ss s1?
Click to expand...
Click to collapse
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commits/staging
No way man, nice work
Android 7 N for s1
Ejgjskfkcisvjj hahah