This rom is effectively the CM7.2 version of FXP140. I don't believe any changes have been committed to the es209ra sources since FXP130, but it does include the all the latest 7.2 commits made in the 2 months or so since FXP130 was released.
Background:
The USSD exploit was published last week and the Cyanogen dialer is vulnerable. I don't know if there's a USSD factory reset code for the X10 but frankly, I don't want to find out.
The exploit was patched in the CM sources recently and since FXP is no longer releasing 7.2 builds I thought I'd try and build the latest CM version from source for use on my X10 (rather than install some extra app just as a work around)
I was most surprised to get it compiled correctly first time, and I've been running it on my phone today without problems. I figured there are people here who don't have the time or inclination to compile the sources and might find this rom useful.
Installation
It's exactly the same as FXP 7.2 roms, so just follow this.
Colossus FXP install guide
You'll need the standard FXP 130 kernel, or a kernel that's compatible with FXP 130. The Kernel.sin file is included in the rom and you can make an FTF from that with Flashtool if you don't already have a suitable kernel to install.
Download link
http://www.mediafire.com/?6zkni41daaaieq7
Disclaimer: I'm not a developer and haven't made any changes, this is just a clean build of the very latest latest CM7.2 sources from Github: https://github.com/CyanogenMod/
will test.
REPOSTED!
Me test, too.
And I did, idk what kernel should I use, so it's a bit laggy for me. and Play store with Gmail isn't working. but everything else works good.
Sent from my SO-01C using xda app-developers app
will try it
working ok. if i could add the camera from cm7 M&M.. would be better. A lot of free ram, good 3d performance with Cosmic Kernel Mod.
I'm not sure which camera app M&M use, the APK should work as long as it's not the semc one (since M&M is based on stock rom/zmod).
what's USSD ?
USSD codes are special dialling codes that can be used to make a phone perform special functions (e.g. show the IMEI, access the secret menu on a sony stock rom).
See the link I posted originally for more details on the bug:
http://dylanreeve.posterous.com/remote-ussd-attack
It's most serious on Samsung phones as they have a USSD code that performs a factory reset without prompting.
Hi,
i use in my Roms CM-cam.apk
Greets maik
Gesendet von meinem GT-I9100 mit Tapatalk 2
Hi guys,
here is my boot.img extracted from my phone for 9100P NFC users.
It's a Siyah-Dorinmanx-V7.38 kernel with I9100PBULP3 radio.
It has the original stock boot screen logo,
now the most important thing, using
CM ROM
http://get.cm/get/jenkins/18028/cm-10.1-20130116-NIGHTLY-i9100.zip (CM for i9100)
+
http://forum.xda-developers.com/showpost.php?p=29960634 (NFC support for JB by jthatch12)
It will get you full support of NFC, no bugs finded yet, it works perfectly even has the original icons!
I tryed other custom roms claiming of having NFC support, but none of them had this level of support (no icons, bugs with turning NFC on/off etc.)
This is not my work! I only combined rom with kernel and NFC mod!
Thanks to the Dorinmanx and the CM team for doing such a great job and jthatch12 for his implementation of NFC in our devices.
I was very disappointed with the support of 9100P and was desperately changing roms to find something fully working, the best result I get is using this combination above.
Cheers for the great 9100P!
Hi all,
Googy decided to create a new kernel with the dual boot feature, sure you know.
As the title says, I'm interested in adapting a script a guy made for siyah kernel. It allowed to use the same apps in both roms. Here is the link to that thread:
http://forum.xda-developers.com/showthread.php?p=32662356
I've tried it but it doesn't work, I guess it must be adapted to the Googy kernel. Maybe the folders location have changed and also Android 4.2.2 has its problems because of the multiuser feature.
I would do it myself but I'm not so expert at all of this. I thought someone would be interested as well and is able to make the script work.
So, to sum up, it would be awesome if somebody could adapt the script and then we will be able again to share apps between both roms.
Hi, i got nice working zenfone port of lollipop 5.0
It have 500mb free ram and works very fast. Firmware is up to date. Will be good alternative for stock lg.
But wifi, camera and bluetooth does not work.
I rhink its a kernel problem.
With lg stock kernel (with asus ramdisk) is as i wrote but with cm12 kernel bluetooth works but touch is control only by circle point.
Ps every hw wifi bluetooth.. lib replace is a bootloop etc
Anyway i think it needs special kernel for this port,
Ps phones have the same cpu gpu etc very similar
Zenfone kernel source https://github.com/shakalaca/ASUS_ZenFone_A500KL?files=1
Dont know if lg shared their sources.
Anyone who have knowledge about building kernels (i dont have) please help thanks in advance
@Vagelis1608
@mobiusm
@Nikita Pro Android
@Zaaap72
@invaderjohn
Screenshots:
forum.xda-developers.com/showpost.php?p=69803370&postcount=14
Works
-ril
-touch screen
-zen apps
-UI
-DATA LTE ..
Does not work:
-wifi
-bluetooth
-camera
-no sdcard
?nfc?gpsgps
From what I understand, you used CM12 as base, right?
If you use the CM12 libs, does it bootloop?
Also, LG has shared their sources.
Vagelis1608 said:
From what I understand, you used CM12 as base, right?
If you use the CM12 libs, does it bootloop?
Click to expand...
Click to collapse
Thanks for answer.
No, stock 5.0.2 as base (but only zimage from kernel and firmare files from system\etc).and similar..
When i change libs to this from stock or cm i get bootloop.
I tried cm kernel but many bugs, only fixed bluetooth.
With lg kernel zimage and asus ramdisk rom works nice but must be something wrong with drivers because no wifi bluetooth and sdcard. Its possibble to fix it? By change some files from lg to asus kernel and build it?
WYPIERDAALAAC said:
Thanks for answer.
No, stock 5.0.2 as base (but only zimage from kernel and firmare files from system\etc).and similar..
When i change libs to this from stock or cm i get bootloop.
I tried cm kernel but many bugs, only fixed bluetooth.
With lg kernel zimage and asus ramdisk rom works nice but must be something wrong with drivers because no wifi bluetooth and sdcard. Its possibble to fix it? By change some files from lg to asus kernel and build it?
Click to expand...
Click to collapse
I think that you need to get some files from LG kernel ramdisk to the one you are using.
Try to capture a logcat of what is failing (e.g. capture a logcat while trying to turn on WiFi, Bluetooth, etc.). It should give you an idea of what is causing stuff to fail.
BTW, you can find LG's sources here: http://opensource.lge.com/index
Vagelis1608 said:
I think that you need to get some files from LG kernel ramdisk to the one you are using.
Try to capture a logcat of what is failing (e.g. capture a logcat while trying to turn on WiFi, Bluetooth, etc.). It should give you an idea of what is causing stuff to fail.
BTW, you can find LG's sources here: http://opensource.lge.com/index
Click to expand...
Click to collapse
Ok, i will make logcat but i never build from source.
I will upload rom today for test.
Ps in rc files in ramdisk i remove # from the lines about sdcard it should fix no sdcard read but it makes bootloop.
Ok, anyway i will make logcat and i'll write here.
If you will have any idea - go ahead.
LOL. 5.0 ported from zenfone with cm12 kernel... hells mix.
You will not fix wifi or camera via rebuilding kernel.
Nikita Pro Android said:
LOL. 5.0 ported from zenfone with cm12 kernel... hells mix.
You will not fix wifi or camera via rebuilding kernel.
Click to expand...
Click to collapse
5.0-5.0.2 api level 21- the same i used kernel from this old cm12 build (5.0.2 base).
I tried add missed lines in ramdisk files but bootloop ;\
I had no time yestarday but today i will try look for logcat.
If no solution by kernel rebuild so how to make it work if rom works nice, much better than stock lg.
WYPIERDAALAAC said:
5.0-5.0.2 api level 21- the same i used kernel from this old cm12 build (5.0.2 base).
I tried add missed lines in ramdisk files but bootloop ;\
I had no time yestarday but today i will try look for logcat.
If no solution by kernel rebuild so how to make it work if rom works nice, much better than stock lg.
Click to expand...
Click to collapse
I meaned that your idea to PORT abandoned android 5.0 (it's the worst version of new material-designed android versions) from another device to our and try to get working all parts (I am underlining word "PORT" again. That rom was BUILT not for our device specifies and have many wrong working blobs).
Nikita Pro Android said:
I meaned that your idea to PORT abandoned android 5.0 (it's the worst version of new material-designed android versions) from another device to our and try to get working all parts (I am underlining word "PORT" again. That rom was BUILT not for our device specifies and have many wrong working blobs).
Click to expand...
Click to collapse
Maybe its worst ver but works better than 5.0.2 from lg.
You meant that is too much differences between firmares to make this port fully working? Even if the calling sound 4g etc works without much firmware modyfing, same cpu gpu.. I though its possibble to make it bug free with KK will be better, more easy or its stupid idea?
Try this values from CM13 write in build.prop , i got less laggy 5.0.2
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
also min free for multitasking i use this down : ps ( @WYPIERDAALAAC will be good to find default values from CM 13, if you know write pls )
ro.sys.fw.mOomMinFree1=49152
ro.sys.fw.mOomMinFree2=61440
ro.sys.fw.mOomMinFree3=65000
ro.sys.fw.mOomMinFree4=70000
ro.sys.fw.mOomMinFree5=80000
ro.sys.fw.mOomMinFree6=100000
and delete line with min processor frequency 7xx , to have default 300mz this prevent owerheat ( if delete Zram have more lag, i keep him)
Sorry for this off topics
Boki11111 said:
Try this values from CM13 write in build.prop , i got less laggy 5.0.2
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
also min free for multitasking i use this down : ps ( @WYPIERDAALAAC will be good to find default values from CM 13, if you know write pls )
ro.sys.fw.mOomMinFree1=49152
ro.sys.fw.mOomMinFree2=61440
ro.sys.fw.mOomMinFree3=65000
ro.sys.fw.mOomMinFree4=70000
ro.sys.fw.mOomMinFree5=80000
ro.sys.fw.mOomMinFree6=100000
and delete line with min processor frequency 7xx , to have default 300mz this prevent owerheat ( if delete Zram have more lag, i keep him)
Sorry for this off topics
Click to expand...
Click to collapse
i'll try, thanks.
today i will upload new version of stock to my rom thread
(still as backup because re-builded system img looks like corrupted when i flash it by twrp,
no problem with system.dat but cant do that with stock system img)
Hi. I am happy that my old Smultron is not dead yet.
Due to its small size, I would like to reactivate it as a bicycle computer / fitness tracker. The apps that I usually use require Lollipop as a minimum.
I seem to remember that I half-heartedly tried the same already about a year ago, but did not succeed with installing the ANT+ services from the Playstore.
Currently, I am at CM13.
Now I found that in the AOKP FAQ, it is stated:
Q: Why is ANT+ not working?
A: ANT+ developers do not support our wifi chip (wl1271) beyond JB 4.1. ANT+ will never work except if we write the needed source code changes from scratch.
That leads me to the qestion: Is this true for all ROMs, or just AOKP? Or more in general: Which ROMs supports ANT+?
Umm... noone knows this?
a-dummy said:
Umm... noone knows this?
Click to expand...
Click to collapse
All Stock based GB and ICS ROMs afaik.
Dunno about JB and KK ROMs