I've been trying to get Cyanogenmod 10.2 for GT-I9105P working for serveral days now, and i wanted to ask, what is nessecary to use a Cyanogenmod 10.1 device tree with Cyanogenmod 10.2.
I already tried with two device trees now, one of them worked with cm10.1 the other one was not tested.
I am already using the new-style recovery.fstab.
With both I couldn't get behind the Cyanogenmod-Bootlogo.
Can anyone help me and/or knows the problem ?
Here are the device trees i used
1: https://github.com/Galaxy-S2-Plus-Cy..._samsung_s2vep with https://github.com/Galaxy-S2-Plus-Cy...ys2plus-common
2: https://github.com/KINGbabasula/andr..._samsung_s2vep (this is the one I already tested with cm 10.1)
Related
Hi there guys.
Is there anyone working on CM11 for now ? I can't find any info on CM site about i9100 (I believe it should work flawlessly as google wants to support older phones).
Just let me now, please !
Cheers
the guys from the team of CM now versed in the system, because there are many things requiring adaptation. So wait for CM 11 I think is closer to the new year
Here you go.. But it's still in testing stages.. You could test and report to the developer for its development..
http://forum.xda-developers.com/showthread.php?t=2523604
guru_iyer said:
Here you go.. But it's still in testing stages.. You could test and report to the developer for its development..
http://forum.xda-developers.com/showthread.php?t=2523604
Click to expand...
Click to collapse
cheers mate, I'll do my best )
You can use OmniRom instead
cortex69 said:
Hi there guys.
Is there anyone working on CM11 for now ? I can't find any info on CM site about i9100 (I believe it should work flawlessly as google wants to support older phones).
Just let me now, please !
Cheers
Click to expand...
Click to collapse
You can use OmniRom instead. I used CM 7, 9, and 10, with a Galaxy S1 and then S2. I recently switched to OmniRom because they had a working KitKat rom. Basically a group split off from CM after it became a company, and that group is called OmniRom. CM's i9100 development has all but stopped, but the OmniRom have KitKat rom nightiles that are quite stable. I'm using as my daily driver, and all features work. My phone is faster that it was on CM10.2.
OmniRom:
http://omnirom.org/about/
Download for i9100:
http://dl.omnirom.org/i9100/
XDA Forum thread:
http://forum.xda-developers.com/showthread.php?t=2562055
Nightly Changelog:
https://changelog.omnirom.org/#/i9100/next
Note: As per the XDA thread, you need SuperSU and GApps. Please use Paranoid Android's GApps modular mini. The full one didn't work for me, and others have said the same.
The only bugs I'm having with OmniRom are:
(1) Automatic time zone (set it manualy)
(2) The OpenDelta over the air updater doesn't work properly yet.
Jira bug tracker:
http://jira.omnirom.org/
Good luck.
Dave
Problems to execute Cm11 on my s2
Hello, I wonder if any Modder or Dev could help me.
I have a Galaxy s2 I9100 stopped there two years, and recently tried to install Cm11 him, and when I start the phone it loads the bootloader Cyanogem Mod, and then a message "Shutting Down Power Off" appears.
I tried using other versions as Slim Know, Paranoid, Pac Rom, etc ... and all the same thing happen. I decided to go back to official samsung 4.1.2 rom, it worked okay, but the phone does not load, an error appears stating that the phone battery with this high temperature, but the phone does not heat up, it is normal temperature coma.
I took the phone in technical assistance, which found that the problem is in the motherboard. I wonder if any Modder or Dev could help me on how to disable it in CM11 rom, or which file responsible for turning off the phone in case of failures. Thanks in advance
(Sorry for my bad english)
Handwriting to text
Hey
I was just wondering if cm11 has a handwriting to text feature.? I can't seem to find it, if it has it.
Hello all
I got nexus 4.
I am actually trying to build ubuntu touch and so far it works well (it somehow actually is smoother than the official).
The thing is, those annoying vibrations.... since its based on CM 10.2 in my case, I am wondering if someone can tell me where the vibration files are located (in CM 10.2) so that I can exclude them from source code while compiling code.
Ok so I have built cm11 for my device (galaxys s 4g), and ported cm11 from another device to (aries -> galaxy s 4g). CM11 has too much going on IMO and I just want pure aosp on my device, the problem is that there are no (recent) aosp roms for my device, or any similar devices.
So how do I port my device to a different flavor of android when there are no roms of that flavor?
What have I tried?
So far I have setup the aosp 4.4 repo to a different folder than my cm11 repo (the build environment files should be the same right?)
I tried using the manifest from the cm11 rom and buidling with aosp,that didnt work it didnt even finish compiling =(.
I browsed the aosp source for other devices by the same manufacturer, but everything looked completely different from what I am used to.
The most helpful guide in this direction sofar has been cyanogenmods guide but it has left me with more questions than answers.
What [I think] I need to know
Custom recovery - aosp doent seem to include a recovery, the cm guide says to start with the recovery. So i need to know if I need to add a custom recovery to aosp, or if i can install aosp roms from twrp without breaking it.
Binaries - It is safe to use the binaries used in CM11 for aosp/any other flavor, or are the binaries flavor specific? (im thinking they are safe to use, but not entirely sure).
Device files - what files should be safe to use for any flavor?
Kernel - Cm builds the kernel when you compile the rom (or so it says), does aosp build the kernel when you build the rom, or do I have to build the kernel separately? Is it safe to say use a CM11 kernel with an aosp rom?
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
spenceboy98 said:
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
Click to expand...
Click to collapse
I would recommend starting by using the device tree for your device that supports 12.1 and try using that tree to compile 13. To do this download the 13 code and put the 12.1 device tree in the proper folders (device, vendor, kernel) and try compiling a build and start seeing what errors you get. Let me know if you still have questions I'll do my best to help you out!
Hey guys,
As this phone is currently not supported by CyanogenMod, is there any alternative firmware available right now that works ?!?
I can only find some wip firmwares ... which lack a lot of functionality...
tnx
There is unofficial CM 12.1 with almost good content.
Also there is AOSPG rom which is working like stock but vanilla android based on your stock.
There are also several including 6.0 test setup and several other 5.1.1 builds that are growing their progress quite fast actually considering couple of months ago there were no roms for M4.....
I tried all of these, none of them work... the phone does not boot , it gets stuck at the sony boot logo, but it is mentioned in those threads that these roms might not boot because they are not finished.
The boot locker has been unlocked, and I have TWRP installed correctly.
So I guess we'll have to wait for the offcial CM 12.1 or 13 release then....
ADDOriN said:
There is unofficial CM 12.1 with almost good content.
Also there is AOSPG rom which is working like stock but vanilla android based on your stock.
There are also several including 6.0 test setup and several other 5.1.1 builds that are growing their progress quite fast actually considering couple of months ago there were no roms for M4.....
Click to expand...
Click to collapse