Database Info

[Acer A210] CM10.2 and CM11 coming soon

Hi all,
Some of you may know me from the Korean phones section where I was developing fixes for bricked phones, as I no longer have a bricked phone at the moment I moved on.
What I moved onto is opening the devices trees for the A210 tegra 3 based tablet from Acer.
yes I know there are already a few cm10 compiles out there for the Acer Axxx devices but the A210 seems to have only closed sources on the cm side and kernel, example kiwi++ based kernel/James ROMs, (if the kernel is public,then I stand corrected)
Anyway, moving on,
My current tree for cm10.2 is available on github and I will start posting compiled nightly builds as the project moves on. And develops.
For now my builds will include the cm kernel, based off kernel/acer/t30-common , mainly because I know little about kernel hacking and the goal was to get cm10.2/11 booting and usable.
Current status
CM10.2
1. WiFi working
2. Touch working
3. Sound fully working
4 no internal/external SD card yet
5 USB devices are working
6 display has flicker but otherwise fully working
7 cwm is working, touch to follow
8 PA-gapps / play store working
9 battery life untested yet
10 custom kernel/CPU gov's - not started yet
CM11
same as CM10.2 status
You can find my cm10.2 online on github, my cm11 tree is staying closed for now while I iron out some hectic bugs that have the potential to brick the device (so far I keep loosing touch and sound even across ROMs)
Anyway, onto the meat of it , if you want to compile yourself, pull the trees from here
https://github.com/darkspr1te
I also want to document some of the development process here too, time allowing (mods gods allowing)
Compiled builds to follow for now, enjoy the reading.
Darkspr1te
Sent from my A210 using Tapatalk

[DEV] Porting kernel 3.10.x to d2 for Lollipop

As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!

Does your kernel compile and boot on cm11? If it does, there shouldn't be much problems in getting it working on L.

Any news? Does it compile?

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y

Ivan_Meler said:
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Click to expand...
Click to collapse
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
ztotherad said:
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
Click to expand...
Click to collapse
I know samsung does things like that (i have few other devices from them) but hey thats samsung and they are lazy so they dont want to update kernel version after device is relesed so they do this not to feel outdated on softwere side

Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works

frap129 said:
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
Click to expand...
Click to collapse
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
I was planning on working on that as well over the weekend.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays

Ivan_Meler said:
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Click to expand...
Click to collapse
I'm very new to the AOSP build process and didn't have much luck last night getting the CM device sources to play nicely with AOSP. I'm finding it difficult to find any relevant guides on porting over the CM device trees to pure AOSP. If you or anyone else can help by explaining the process or pointing to a guide that I may have missed, I'd be grateful. Plus the more people we have collaborating on his, the better our chances of getting Lollipop on our devices.

I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy

Restl3ss said:
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Click to expand...
Click to collapse
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?

polarEskimo said:
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
Click to expand...
Click to collapse
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)

Restl3ss said:
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Click to expand...
Click to collapse
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.

polarEskimo said:
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
Click to expand...
Click to collapse
I'll push what I've got to github after this experiment

Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much

Ivan_Meler said:
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Click to expand...
Click to collapse
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS

Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!
Build currently hangs at this:
Code:
host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night

Restl3ss said:
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Click to expand...
Click to collapse
I'm with you on that, I'd rather have pure AOSP than buggy CM nightlies. Also interesting choice of ROM name lol. Thanks for your hard work and I'm looking forward to pulling down your repos so I can take a stab at these compile-time issues.

[ROM][UNOFFICIAL][ALPHA][s2ve/p] Cyanogenmod 12.0

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:

[ROM][UNOFFICIAL][5.1.1][I9105/P] Cyanogenmod 12.1 [2016/07/21]

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.

Question Now Focusing On Custom Rom (LineageOS) For Our Galaxy Z Flip 3

Hello
I did Bought a Samsung Galaxy Z flip 3 demo version , i want to build TWRP for it
Spoiler: That is Done
yesterday i downloaded the Kernel source code from Samsung , now i just need TWRP Sources and and Create a Device Tree to built it
if you want TWRP for this phone , just comment down below (for some motivation)
Spoiler: that done too , look for the custom working kernel
Now For a The Custom Kernel
I Manage to Get A Custom Kernel Working with A lot Of Optimisations (Thanks @chrisaw and Others) on a Old OneUI (That System That Came with the Kernel) and it work well (it need some minor touches)
the Kernel Cant Work on Newer OneUI and Custom Roms (Pixel EXperience) because Of new Changes in Vendor Are not Compatible with the Kernel
A guess this Need A lot Of Working (Everytime Samsung do it their Way and Dont Care about The Correct Way)
ScreenShot of the Kernel
Spoiler: That is Done too too
now on Focusing on The Custom Rom , i download LineageOS 19.0 Source Code as i will build for 2 separate phones (Galaxy Z Flip3 'snapdragon 888' and UMIDIGI F1 Play 'Mediatek Helio P60') consecutively
this rom will be based on treble gsi patches but working only on Galaxy Z Flip3
i manage to build LineageOS 19.0 for Galaxy Z Flip3 , i will not share it now cause :
1 - it is not daily driver or usable , you can call it pre-alpha
2 - it has a lot of bugs that i saw , it could be other i didn't
3 - it is a Treble gsi just for testing purposes and does not have gapps (gapps needed to be included in the gsi not like a normal rom)
4 - i fix the fingerprint , now it is usable
5 - don't ask me about rear screen , it is perfectly not working at all (if you close the phone , the main display become black , rear screen have just samsung galaxy logo....)
6 - other things i forgot
Any Help will be appreciated
Stay Tune
Thanks

Yeah I'd like to see a fully functional TWRP

yes!

really appreciated!

I'm in

hells yeah

ok so i reinstall my ubuntu setup cause apt went broken , but now im good to start
my initial work is the device tree , it is still WIP
GitHub - shadowofleaf96/android_device_samsung_b2q: For building TWRP for Samsung Galaxy Z Flip 3 5G
For building TWRP for Samsung Galaxy Z Flip 3 5G . Contribute to shadowofleaf96/android_device_samsung_b2q development by creating an account on GitHub.
github.com
the kernel still not building , im working on it
thanks for waiting

GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com

twistedumbrella said:
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine

Shadow Of Leaf said:
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Click to expand...
Click to collapse
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.

twistedumbrella said:
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
Click to expand...
Click to collapse
ok
yes that what i will do , i will use the samsung open source kernel (android 12) , fix to boot recovery and boot the system , when it does that i will include your changes and see if it works or not

Thanks for your contribution。

Cyanide_zh said:
Thanks for your contribution。
Click to expand...
Click to collapse
you welcome

some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned

Shadow Of Leaf said:
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned View attachment 5671531
Click to expand...
Click to collapse
can you share the non-touch version?
i hope he can find the problem and fix it

Maroshall said:
can you share the non-touch version?
i hope he can find the problem and fix it
Click to expand...
Click to collapse
i think i fix the touchscreen problem and its working
there is some minor problems i will fix them and upload it here
also the kernel does not boot on oneui , i have to fix it

the work is done (or atleast it works)
you can check it here TWRP Thread
@twistedumbrella i build the kernel it works on twrp but no luck with OneUI (even with knox and other security measurements disabled) it does panic (kernel panic) i need to do some investigation regarding this , if you want to help i will upload my kernel source code soon​

I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.

twistedumbrella said:
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
Click to expand...
Click to collapse
ah ok thanks
for now i fix to kernel panic , now kernel boot in OneUI But after the loading icon the screens went black
so thanks again and sorry for disturbing you

No worries. I would rather you know I don't know, if that makes sense. Sounds like you are more than capable either way.