CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (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.
*/
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.
Device-specific source code for the Samsung Galaxy S II Plus are available from:
https://github.com/andixlm/android_device_samsung_galaxys2plus-common
https://github.com/andixlm/android_device_samsung_i9105
https://github.com/andixlm/android_device_samsung_i9105p
https://github.com/andixlm/android_kernel_samsung_galaxys2plus-common
Compatibilitiy Patches: https://github.com/doriandiaconu/build_tools/tree/cm-12.1/patches
Do not submit bugs on CyanogenMod issue tracker
Downloads
ROM: https://basketbuild.com/devs/DorianDiaconu/CM12.1
GApps: http://opengapps.org
What works?
RIL (Calls, SMS, Mobile Data)
Wi-Fi
Bluetooth
GPS
Camera
Video playback
Audio (playback & recording)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Everything else not listed under "Known issues"
Known Issues
There are no major hardware issues
Installation:
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod or TWRP recovery with SELinux support. Older CWM will result in a "status 7" error.
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
FAQ
Q: Can you include Feature X into your ROM?
A: No. This ROM will have CyanogenMod's feature set.
Q: Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
A: No. This is an AOSP ROM and cannot have TouchWiz applications.
Q: Can you include call recording?
A: No. CyanogenMod does not include call recording to avoid potential legal issues.
Q: What kernel does this ROM use?
A: A slightly modified version of the stock kernel, the source code is linked above.
Q: I've heard that Broadcom doesn't release source, how can you make this ROM?
A: Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Q: Can I use your ROM as a base?
A: http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Q: Can contacts be saved to phone/SIM?
A: No. It is not supported in AOSP-based ROMs.
Q: Can I send files over Wi-Fi Direct?
A: Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Q: Will you add OTA support?
A: No.
Video Review:
Reporting bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your:
- Phone model (I9105 or I9105P):
- Radio (baseband):
- CM version:
- CM Download URL:
- GApps version:
Did you:
- Wipe:
- Restore with titanium backup:
- Reboot after having the issue:
Are you using:
- A task killer:
- A non-stock kernel:
- CMSettings/Performance settings (other than stock):
- Other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- @pawitp
- @CoolDevelopment, @LuK1337, @GHsR and other I9105/P and I9082 devs
If you like it, use it and don't forget to press the "Thanks" button or send me a beer via PayPal.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy S II Plus
Contributors
doriandiaconu
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 4.2.2
Based On: CyanogenMod
Version Information
Status: Stable
Created 2016-04-19
Last Updated 2016-07-21
So what is new from the 15th January build??
insanix said:
So what is new from the 15th January build??
Click to expand...
Click to collapse
Dorian after update,rom freeze in samsung galaxy screen.
Nice job, i will try it now :fingers-crossed:
Edit: It's how anastasiszn said, phone freeze and "Samsung GALAXY SII Plus GT-I9105P" screen xD
I'll fix it today as soon as i get home
Sent from my GT-I9105P using XDA Free mobile app
anastasiszn said:
Dorian after update,rom freeze in samsung galaxy screen.
Click to expand...
Click to collapse
Yeap! Freeze in boot screen
I fixed it. Now uploading.
doriandiaconu said:
I fixed it. Now uploading.
Click to expand...
Click to collapse
Not fixed, still freezing at boot
Yes not fix
Στάλθηκε από το GT-I9105P μου χρησιμοποιώντας Tapatalk
Guys, it might've been a source bug.. It wasn't syncing properly. Now it looks ok.
I'm doing my homework tomorrow again.
*hint hint*
Hmm, downloaded the build last night, but no results, stuck at boot splash screen(the one that says the model name). I'll check it out today, see if it got fixed. Cheers!
EDIT: Nope, still keeps the splash screen. See if you can fix it somehow, i'd love to see the new build, really.
Booting issue fixed.
Sorry it took me so long. Now we have an up-to-date version of CM12.1. Enjoy!
Hello!
Just wondering if i can use this ROM for the non-NFC version of the phone (gt i9105)? If so is there any step that must be followed in addition to the ones already mentioned?
RaXeDge said:
Hello!
Just wondering if i can use this ROM for the non-NFC version of the phone (gt i9105)? If so is there any step that must be followed in addition to the ones already mentioned?
Click to expand...
Click to collapse
Yes you can. Flash nfc destroyer after flash rom
cracker12 said:
Yes you can. Flash nfc destroyer after flash rom
Click to expand...
Click to collapse
I tried it but got a status 7 error saying that the device is a s2ve and not a sv2ep. And could you also provide the link for the nfc destroyer? Thank you
RaXeDge said:
I tried it but got a status 7 error saying that the device is a s2ve and not a sv2ep. And could you also provide the link for the nfc destroyer? Thank you
Click to expand...
Click to collapse
Install twrp for 9105p and try again. Nfc destroyer: https://s.basketbuild.com/filedl/devs?dev=GHsR&dl=GHsR/galaxys2plus/NFC-DESTROYER_LOLLIPOP.zip
What changed in this version?
Hi Dorian,
Can you tell me what changed in this version, 28/5/2016
thx,
Rene
Can anyone connect to wps ?
Στάλθηκε από το GT-I9105P μου χρησιμοποιώντας Tapatalk
After a day of use my phone freeze when i open bassicaly apps like dialer or messaging and i need to take out my battery.
Related
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Come to #omni on Freenode, and have a chat to one of the core developers (they are listed at the top of the user list) - they will be able to help you get your device merged
Please note, in order to add a new device, we will require a maintainer on an ongoing basis for it, to ensure someone is able to investigate bugs that users report on a device. Without this, we unfortunately cannot enable nightly builds for a device.
will a cm kernel tree work for the most part with just a few changes?
azoller1 said:
will a cm kernel tree work for the most part with just a few changes?
Click to expand...
Click to collapse
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
pulser_g2 said:
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
Click to expand...
Click to collapse
Along these lines, do NOT remove copyright attributions of a changed file. You may ADD copyrights to a header, but do NOT remove anything.
maxwen said:
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
Click to expand...
Click to collapse
Most likely kernel change will be that reverting out that MDP sync point mess used by CM's AOSP+CAF frankendisplay. Can't link to it from my current location.
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
TF300T
OK here goes..
For the Asus Transformer TF300T the kernel forked from the CyanogenMod github:
https://github.com/scanno/android_kernel_asus_tf300t/tree/android-4.3
And the device tree, modified to get OmniROM to finish the build and get a bootable result:
https://github.com/scanno/android_device_asus_tf300t/tree/android-4.3
Hopefully it will be added to the OmniROM github.
n3ocort3x said:
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
Click to expand...
Click to collapse
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
AL_IRAQI said:
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
Already on my github
https://github.com/Grarak/android_device_samsung_i9500
kernel tree
https://github.com/Grarak/android_kernel_samsung_exynos5410
proprietary
https://github.com/Grarak/proprietary_vendor_samsung
exynos 5410 repos:
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5410
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5-insignal
https://github.com/intervigilium/android_hardware_samsung_slsi_openmax
pretty much ^^
I'd like to maintain for l900 and i605 (Sprint and Verizon Galaxy Note 2).
device trees
https://github.com/omnirom-slickrick/android_device_samsung_l900 (sprint tree)
https://github.com/omnirom-slickrick/android_device_samsung_i605 (vzw tree)
https://github.com/omnirom-slickrick/android_device_samsung_t0lte (note 2 common tree)
https://github.com/omnirom-slickrick/android_device_samsung_smdk4412-common (same as tree on omnirom github but actually more updated and device settings added back)
kernel
https://github.com/omnirom-slickrick/android_kernel_samsung_smdk4412 (just have needed device settings commits added back in)
thracky said:
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
Click to expand...
Click to collapse
we already making progress but it needs more work to be done.. at least we are now in system with working wifi, and display but modem doesent work.. something for tomorrow, and i dont want to hijack this thread too sorry if my question was in the wrong section but i thought i mention it because of the post above mine. nevermind i cann offer to maintain m7ul as already discussed with maxwen and oin IRC but a lot of work needs to be done:
here are my sources, device trees are usable but kernel needs more work as said above:
device trees:
https://github.com/n3ocort3x/android_device_htc_m7ul
https://github.com/n3ocort3x/android_device_htc_m7-common
https://github.com/n3ocort3x/android_device_htc_msm8960-common
kernel: its a modified one but its no problem to bring it back to stock features and will push as soon asap the modem stuff is sorted out
https://github.com/n3ocort3x/android_kernel_htc_m7
EDIT modem fixed, only BT left
@sykomaniac , look at first post and become a maintainer
pulser_g2 said:
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Post a link here to the device tree (and kernel repository) for review, and tell us what device it is (give model numbers and board names and as many details as possible )
Click to expand...
Click to collapse
We have quite a few things that aren't working like bluetooth, camera is buggy, H/W vsync, gps, and fm radio.
https://github.com/SeannyM/android_device_samsung_kylessopen
https://github.com/SeannyM/ba2x-kernel
gt-s7560m with quadband gsm and 850/1900/2100 WCDMA/UTMS
We have a MSM7227a cpu armv7 clocked at 1008mhz stock.
645mb of usable ram
4gb of storage with 1.7 usable
233 dpi 800x480 4inch screen
Adreno 200 enhanced
5mp camera 1.3 front facing
hopefully we can get something official
single sim
Gtab2 10.1 Wifi & 3G (p5110 & p5100)
There you have my device tree for omni
p5110 :
https://github.com/sevenup30/android_device_samsung_p5110
p5100:
https://github.com/sevenup30/android_device_samsung_p5100
omap4-common (had to edit it cuz of duplicate libion entry):
https://github.com/sevenup30/android_device_samsung_omap4-common
other dependencies required from CM & Themuppets
kernel :
https://github.com/CyanogenMod/android_kernel_samsung_espresso10
samsung proprietary:
https://github.com/TheMuppets/proprietary_vendor_samsung
samsung hardware:
https://github.com/CyanogenMod/android_hardware_samsung
apps samsung service:
https://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
Everything is working (sound / wifi / bluetooth / video playback) BUT!
I must edit build.prop by hand to get sound working until omni build process take care of "product_build_prop_overrides" into custom_XXXX.mk
see:
http://forum.xda-developers.com/showthread.php?t=2484747
Original Samsung Galaxy Note
Samsung n7000 initial bringup:
Modified CM n7000 device: https://github.com/chasmodo/android_device_samsung_n7000/tree/android-4.3
Modified CM galaxys2-common: https://github.com/chasmodo/android_device_samsung_galaxys2-common/tree/android-4.3
CM smdk4412 kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-10.2
Samsung proprietary stuff: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.2
Samsung hardware tree untouched from OmniRom.
Device info:
Board platform - exynos4
SOC - exynos4210
Board name - smdk4210
Kernel specifics - unified kernel and recovery
It compiles fine using the repos listed above, but throws up a kernel assert error when flashing the Rom. Several compilers for different devices complained about it in the 'All the answers' thread. The way out of this is to flash a CM10.2 kernel immediately after the Rom flash aborts, then Omni boots up fine.
What works:
1. telephony
2. mms
3. WiFi
4. GPS
What doesn't work:
1. data
2. bluetooth turns off as soon as you turn it on
3. both sdcards are invisible from Android; all your stuff is there when you drop into recovery, though
4. Settings/Storage FC when tapped - see #3
5. Performance options also FC
6. Notification drawer cannot be pulled down
Camera cannot be tested because it shuts down as soon as you start it, saying: "No external storage available" - again, see #3
Galaxy Note II / N7100 (International)
Samsung Galaxy Note II / N7100 Bring up details.
I have a working build of the Omni rom for the N7100. Below are the details on what is working and not working. i have been using it for the last 2 days, so far not crashes or reboots all seems to be working fine. i cherry picked a few commits and included it into my build
Working :
WIFI
DATA -3G & 2G
Telephony & MMS & SMS
GPS
Sound
Camera (Both Front and Back)
SD card
Performance control
Notification drawer & Lights
Multi-Window
roadrunner
Not Working :
BT
Backlights(if i install a custom kernel then the lights work)
Device Tree for N7100 - https://github.com/tilaksidduram/device_samsung_n7100
Device smdk4412-common - https://github.com/tilaksidduram/android_device_samsung_smdk4412-common
smdk-4412 Kernel (3.0.100) - https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
samsung hardware - https://github.com/CyanogenMod/android_hardware_samsung
DEVICE: GT-N7100
sources
https://www.github.com/UtkarshGupta/android_device_samsung_n7100
https://www.github.com/omnirom/android_device_samsung_smdk4412-common
https://www.github.com/omnirom/android_hardware_samsung
https://www.github.com/omnirom/android_kernel_samsung_smdk4412
https://www.github.com/TheMuppets/proprietary_vendor_samsung
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
dstruct2k said:
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
Click to expand...
Click to collapse
I think a few are... There has been chat of it in the IRC channels.
Device name: LG Optimus 4X HD
Codename: P880
Board name: X3
Chipset: Tegra 3 AP33
Everything works, except button backlight.
https://github.com/Adam77Root/android_device_lge_p880
https://github.com/Adam77Root/android_kernel_lge_x3
https://github.com/TheMuppets/proprietary_vendor_lge
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.2 (Kitkat), 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 11.0 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 data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* See post #2
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.
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
Links
CyanogenMod: (use latest build: cm-11-*): http://download.crpalmer.org/nightlies/picassolte/
* See second post for more details about the nightlies
CWM Recovery: (use latest build: cm-recovery*): http://download.crpalmer.org/downloads/picassolte/
* The ZIP cannot be flashed in recovery. You need to unzip it and then flash the .tar.md5 that it contains using odin.
Google apps addon: (use latest kk gapps)
Download: http://goo.im/gapps
Mirror: http://download.crpalmer.org/downloads/gapps/
Source Repos::
* vendor
* kernel
* device: tabpro-common
* device: picassolte
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Unofficial CyanogenMod 11.0 for PicassoLTE, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Testing
Created 2014-06-18
Last Updated 2014-08-19
Nightlies
Nightlies:
Download:
SM-T525 (picassolte) nightlies folder
Known Issues:
* splash screen: On boot the screen will go black for 5-10 seconds (same for the cwmr) until the CM boot logo appears. This is just cosmetic.
* most of the bugs on JIRA for mondrianwifi.
Changelogs:
* Main CM changes (ignore device_samsung_mondrianwifi): cmxlog for mondrianwifi
* Tabpro common device changes
* Tabpro common vendor blob changes
* Picassolte specific device changes
The changelog contains all changes made to that branch. Each nightly will be tagged and looks like:
7cd5c0b (HEAD, tag: nightly-20140808, m/cm-11.0, github/cm-11.0) mondrianwifi: init: Configure minimum GPU speed
The tag(s) that say "nightly-xxxxxxx" indicate that all changes from this commit down are in that nightly. Therefore, you can see what has changed since a specific version by looking for all entries between your current night's tag and the one that you are going to download and install.
Reserved
The broken entry for the splash screen means that you will get about 5 seconds of a blank screen after the Samsung splash screen and before the CyanogenMod splash screen shows up. That's normal, albeit a little disconcerting.
This is still a very early build. Pay attention to what is broken before deciding that you want to use it.
What is working should be quite stable. It is based off of the work I've done on the 8.4 mondrianlte which is very solid.
edit; nvm, thought i read this as t520... damn exynos.
New build: 2014-06-20
* Major audio changes, fixes voice recognition
* Synced to latest CM code
Finally there's at least one good AOSP ROM for this tablet... I wonder why is the development so dead for it?
New build: 2014-06-22
* Fixes bluetooth
* Fixes camera (and camcorder)
* Fixes compass sensor
Great thing to see development for this 10 inch device! I have 1 question, how much does this one differ from the T520?
Sent from my L800 using Tapatalk
Cryonic90 said:
Great thing to see development for this 10 inch device! I have 1 question, how much does this one differ from the T520?
Sent from my L800 using Tapatalk
Click to expand...
Click to collapse
Very different. This is of very limited value for the t500 as it would need a completely different kernel and would be a very large effort.
New build: 2014-06-23
Fixes:
* caller id
* conference calls & call waiting
* keymaster firmware issues
All that is left is:
Broken:
* external sdcard
* splash screen
Unknown:
* lid switch
so I'm changing the title from ALPHA to BETA to reflect the progress.
Is anyone using this? I got a PM from someone saying that the last build has broken WiFi but no line else has mentioned anything being broken?
I can look into whether or not I posted a bad build tomorrow, but I wanted to confirm that people are actually running this?
Yay for a 10.1 LTE rom!
I'm holding out for when external sd card support is fixed, and I'll give it a go
Yap, same here...
sent from htc one...
New build: 2014-06-26
* external sdcard should be fixed
* audio improvements
* kernel changes from samsung's sm-t320 updates
* general cm upstream changes
Thank you. Installed and everything i have tried is working great.
My Kingdom for this on the WiFi version.
SomeGuyDude said:
My Kingdom for this on the WiFi version.
Click to expand...
Click to collapse
+ 1
Will exynos ever be supported?
Trust me to buy the only tab that doesnt get CM support! lol
$50 for CM on T520
jonlad1 said:
+ 1
Will exynos ever be supported?
Trust me to buy the only tab that doesnt get CM support! lol
$50 for CM on T520
Click to expand...
Click to collapse
Asked an answered numerous times... Not likely to ever get cm.
works great and no bug so far ...
Ty
Just one question : can you post the original deoxed samsung keyboard 4.0 because i prefer it ...
Thank you
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (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.
*/
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.
Device-specific source code for the Samsung Galaxy S2 Plus are available from https://github.com/luk1337/android_device_samsung_s2vep,
https://github.com/luk1337/android_device_samsung_s2ve and https://github.com/luk1337/android_kernel_samsung_galaxys2plus-common.
Compatibilitiy Patches: https://github.com/luk1337/build_tools/tree/cm12
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: https://s.basketbuild.com/devs/LuK1337/CM12
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Bluetooth headset isn't working
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (s2ve or s2vep):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- CoolDevelopment, pawitp and other s2ve/p and i9082 devs
XDA:DevDB Information
[ROM][UNOFFICIAL][ALPHA][s2ve/p] Cyanogenmod 12.0, ROM for the Samsung Galaxy S II Plus
Contributors
LuK1337
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-11-16
Last Updated 2014-11-16
NOTE: I'm still building s2ve, I'll upload it later.
Can't wait
can't wait for test! so excited
Awesome
PLease dont forget the Non NFC edition.. keep up the good work
essuraj said:
PLease dont forget the Non NFC edition.. keep up the good work
Click to expand...
Click to collapse
you can easily flash P-recovery and enjoy the dev's work
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It will be uploaded today,just be patient!
Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Buy me SSD or better PC then I would build it faster.
LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
Oh, sorry, i don't want to be ungrateful,but i'm really excited and i want to try it...:angel:
LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
First of all: thank you so much for this amazing work! I can't wait to try!
How long do you think will it take?
Because for me the day ends in 3-4 hours
So i can't add contacts to my phone or sim ?
About Gapps?
Thank you very much : LuK1337!
Does somebody know what Gapps we must use in this rom?
I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Newku said:
So i can't add contacts to my phone or sim ?
Click to expand...
Click to collapse
You can save contacts on Phone but not on sim.
NW2000 said:
I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Click to expand...
Click to collapse
Ok. Thank you!
LuK1337 said:
You can save contacts on Phone but not on sim.
Click to expand...
Click to collapse
thank you very much luk
Can We flash with normal cwm, exept 6.0.5.1?
it looks pretty good.
i tended to think that we wouldn't get that soon cm12, but luk is the best dev,also,grand duos devs.
we wait for ur build uploaded.
thank you man.
LuK1337 said:
[*]Install ClockworkMod recovery with SELinux support
[*]
Click to expand...
Click to collapse
Does it work with PhilzTouch by hacky?
I can't wait :victory: :victory:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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.
*
*/
LineageOS 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). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 15.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
SELinux works in permissive enforcing mode
You need at least OxygenOS 5.0 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 15.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Created 2018-01-23
Last Updated 2018-11-16
Frequently Asked Questions
When you're about to ask a question, read the FAQs below, otherwise it'll be ignored.
Rule: NEVER ask for ETA
Q: Can we port treble to our device?
A: NO, unless OnePlus supports treble in official OxygenOS. Treble is trouble, treble is fake news. From my point of view treble brings zero benefit to the device. You already have countless custom ROMs, treble won't bring more fancy ROMs to the device, it just brings endless trouble to device maintainers. The most important point is, some of our proprietary vendor blobs aren't fully decoupled from /system, so fake Treble won't achieve the same effect as Google announced, especially when upgrading to new Android versions via GSIs.
Q: It VoLTE working on our device?
A: I don't know. My carrier doesn't support VoLTE/VoWLAN, but I've added necessary IMS stack to the ROM, and there're actually some users reported working VoLTE. If it doesn't work for you, DON'T issue me, I'm unable to fix it. Notice: If you strongly believe your carrier does support VoLTE/VoWLAN but the toggle doesn't even show up in settings, tell me your carrier's MCC/MNC number (check http://www.mcc-mnc.com/)
Q: Please add support for sRGB/DCI-P3 as cm-14.1
A: Our kernel does support them, you can enable it via sysfs toggle: /sys/class/graphics/fb0/srgb and /sys/class/graphics/fb0/dci_p3, maybe some apps could help you do this easier. The frontend is WIP(in fact it's already under reviewing, will be merged soonDone)
Q: Please add xyz features or fix UI/UX related bugs/regressions
A: All feature requests and UI/UX related stuff should go to LineageOS JIRA: https://jira.lineageos.org, I only take care of hardware-specific stuff.
Q: Can you make my device bypass SafetyNet?
A: https://www.lineageos.org/Safetynet/
So... its start... official?
Yes!!! :victory: Going to try it out once I'm done with work
Nice work! Gonna install it asap and report any issues.
Device OP3T, not rooted, encrypted.
I list here whatever I am able to find:
Charging doesn't make a sound nor vibrate, no matter what settings.
Option to switch hw keys light on/off is missing (i know not real issue, but many prefer them off)
Display modes missing sRGB, DCI-P3
Thank you! Will install and give feedback after few hours.
EDIT:So far so good. Very good for an alpha. But we should wait for official to daily use i think.
Edit again: Official rollout has been started. Except some kernel issues(fixable with custom kernel), great rom. Okay for daily use, no crashes or random reboots. Thanks anyone who put work on it.
Sent from my OnePlus 3 using XDA Labs
twentyfourinc said:
So... its start... official?
Click to expand...
Click to collapse
Nope, not official. Look at Zip name.
After install this build TWRP 3.2.1-0 cannot mount data partition (it's has encrypted) without any error.
good
Another Oreo Rom....
dimon2242 said:
After install this build TWRP 3.2.1-0 cannot mount data partition (it's has encrypted) without any error.
Click to expand...
Click to collapse
I'm wondering if this is the f2fs loopback problem.
Is your data partition f2fs or ext4?
Sent from my OnePlus3T using XDA Labs
valimakik said:
Nice work! Gonna install it asap and report any issues.
Device OP3T, not rooted, encrypted.
I list here whatever I am able to find:
Charging doesn't make a sound nor vibrate, no matter what settings.
Click to expand...
Click to collapse
if you only find this bug, its like beta more than alpha, this is great.
thank you all developers!!
atoyu said:
if you only find this bug, its like beta more than alpha, this is great.
thank you all developers!!
Click to expand...
Click to collapse
So far only that, but i am work atm so i don't have time tinker with everthing.
but it really feels good even at this point.
valimakik said:
So far only that, but i am work atm so i don't have time tinker with everthing.
but it really feels good even at this point.
Click to expand...
Click to collapse
may i know which open gapps you flash??
atoyu said:
may i know which open gapps you flash??
Click to expand...
Click to collapse
Unofficial 8.1 gapps. I used aroma to choose apps that i use.
https://forum.xda-developers.com/redmi-note-3/development/gapps-opengapps-t3720449
Srgb or dci-p3 working?
tashimotor said:
Srgb or dci-p3 working?
Click to expand...
Click to collapse
No, it doesnt have those options atm. And that what is in developer options won't do anything.
Can u try switch it on in kernel auditor app?
tashimotor said:
Can u try switch it on in kernel auditor app?
Click to expand...
Click to collapse
I am not rooted atm, i can check it out later today.
valimakik said:
Unofficial 8.1 gapps. I used aroma to choose apps that i use.
https://forum.xda-developers.com/redmi-note-3/development/gapps-opengapps-t3720449
Click to expand...
Click to collapse
thx for the link, as open gapps didn't list 8.1 for download, can i use 8.0 gapps?
edit: after research , seems somebody have problems when flash 8.0 gapps on 8.1 rom, i try to flash 8.1 gapps.
LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, 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.
*
*/
LineageOS 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). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 19.1 builds for Edge S / Moto G100. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
I have not implemented dynamic model detection yet, so the displayed model is always "Edge S" regardless of your actual hardware, this is not a bug.
Installation:
https://wiki.lineageos.org/devices/nio/install
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Special thanks to Electimon, this work is heavily based on his prior ones.
......
Changelog & Download:
2022/2/20 initial release:https://yukomoe-my.sharepoint.com/:...NPj4EdAKJwWzcBuIHXiDPzmHiNUB05M37v-Q?e=cUvmJQ
Video over LTE (ViLTE) probably doesn't work
2022/3/13:https://yukomoe-my.sharepoint.com/:...hPgpSvGHD7EuUBsAbKHzrf_9ppXNgZVLT5wg?e=0ZdHA4
Sync latest source and update to Android 12L
2022/3/20:https://yukomoe-my.sharepoint.com/:...BOs1iw7RXB0BIBbBDtvTA9T96hu4wmM0Z2_g?e=9mDL0e
Sync latest source
Fix Wifi display
Fix status bar height for certain apps
Add indicator for fingerprint sensor
Less aggressive high refresh rate scheduling
Display color composition tweaks
Other minor changes
2022/3/21:https://yukomoe-my.sharepoint.com/:...ZOo1OD0OKzDakB8OVvEsdgCJodeQh0d77r5Q?e=FKUfy7
Emergency fix for crash when recording fingerprints for the first time
2022/3/27:https://yukomoe-my.sharepoint.com/:...9Ai-nTJsfs95EBs2qLuwuRCyppY0KGRa8XLQ?e=cRjujv
Sync latest source
2022/3/27 and later official release:https://download.lineageos.org/nio
The size of ZIP file only 746M? i remember the size of 19 alpha version is 2G.
Thanks
seems to work good!
was unable to enter recovery using the official LOS recovery but using Electimons LOSRecovery the install went ok
Nice.
Very good ROM, but few points:
1. Location not working
2. Please allow fingerprint unlock only when power button is pressed, like in stock ROM.
3. Please allow three finger swipe screenshot.
delete
dianlujitao said:
LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
Click to expand...
Click to collapse
This is the same phone for this build correct? I ask because the information on the pages are completely different.
Motorola Moto G100 - Full phone specifications
www.gsmarena.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org
Ryu945 said:
This is the same phone for this build correct? I ask because the information on the pages are completely different.
Motorola Moto G100 - Full phone specifications
www.gsmarena.com
Info about nio variants | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
I Don't quite get your question
the links both refer to the moto g100/Edge S codename "nio" phones
there is no notable difference between device descriptions between the links
and yes this build is for that phone
henkery said:
I Don't quite get your question
the links both refer to the moto g100/Edge S codename "nio" phones
there is no notable difference between device descriptions between the links
and yes this build is for that phone
Click to expand...
Click to collapse
There is a difference in the stated amount of RAM and SoC used. I thought it could be an entry error but I wanted to make sure.
Ryu945 said:
There is a difference in the stated amount of RAM and SoC used. I thought it could be an entry error but I wanted to make sure.
Click to expand...
Click to collapse
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side
henkery said:
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side
Click to expand...
Click to collapse
Snapdragon 870 5G and Snapdragon 870 are not two different SoCs?
henkery said:
ah I see what you mean now
the SoC stated is the same but there does not exist a 12gb version of the g100, this must be a mistake on gsmarenas side
Click to expand...
Click to collapse
Pretty sure the 256gb version is paired with 12gb ram
Ryu945 said:
Snapdragon 870 5G and Snapdragon 870 are not two different SoCs?
Click to expand...
Click to collapse
yes ，it's same
does it not support matriel you？
dianlujitao said:
LineageOS is a free, community-built, aftermarket firmware distribution of Android 12, which is designed to increase
Click to expand...
Click to collapse
I unlocked the boot loader and installed the recovery in both slots. Then I told the bootloader to boot into recovery. It doesn't work. It just freezes. I just see it go the the Motorola log and freeze.
Ryu945 said:
I unlocked the boot loader and installed the recovery in both slots. Then I told the bootloader to boot into recovery. It doesn't work. It just freezes. I just see it go the the Motorola log and freeze.
Click to expand...
Click to collapse
Using whichever working recovery for the first install is okay. It's tricky to develop a universal working recovery image due to how a/b works.
Thanks for the new Build!
for the gapps users out there, you will have trouble finding a working gapps version as the sdk version has been upped and no public gapps package out there supports it yet but you can workaround this by just changing the supported sdk to 32 in the gapps props file
Is location working now?
los19.1 bug found：wifi display not working，plugs device and boot the phone，usb will not working
[20.03.2022]
So I'm after my first tests and:
1. texting/calling/internet wifi/5g works
2. the speed is very good
3. gps is catching relatively fast, you have to wait few seconds in application
4. turn to mute (gesture) - there is no vibration reaction that phone is muted.
I haven't noticed any bigger bugs, we will see how it will behave during the day,