[JB] [CM10] [4.1.1] CyanogenMod 10 for the ZTE Crescent [ROM] [Last updated: 01/09]
#22
Posted 17 July 2012 - 10:34 AM
MadEye Moody, on 17 July 2012 - 03:22 AM, said:
Pretty much. It was all working in the first build which was even closer to AOSP. (The day after the source was released to AOSP.)
#23
Posted 17 July 2012 - 11:08 AM
Devices:
HTC ONE V (Unlocked Bootloader/TWRP installed) running myONEv RC8.0 FX+ and flashing between Provision/CM10/Paranoid Android.
ZTE Crescent (OSF2)- Paranoid Android 4.1 (Sold)
Samsung Galaxy I5500- CM7 (Sold)
________________________________
My Ported Roms:
MoKeeOS (Alpha) | GB MIUI (Alpha) | KonstaKang (Alpha)
| AtomicMod (Beta) |
SwedishSnow (Fully working) | H3 Blues
Help me by testing out my ported ROMs and let me know what works/doesn't work and post here
#24
Posted 17 July 2012 - 12:54 PM
Everyone at office had a good laugh when I tried to call a friend
Edited by MadEye Moody, 17 July 2012 - 02:42 PM.
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#25
Posted 17 July 2012 - 06:02 PM
I understand that you will be busy with coding, so please advice me when you are free
Edited by MadEye Moody, 17 July 2012 - 06:03 PM.
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#26
Posted 17 July 2012 - 06:06 PM
#27
Posted 17 July 2012 - 10:19 PM
Quote
The preview builds released thus far were fairly close to AOSP base features. Time for that to change
The linked commit includes:
- Power menu Reboot
- Power menu screenshot
- Profiles
- Lock screen Calendar
- Lock screen Weather
- Notification light customization
- Battery light customization
- IME Selector notification toggle
- and a few more things to support Settings
This is the first set of many features that will make their way into source, slowly bringing CM10 up to feature parity with CM9, then surpassing it.
https://plus.google....sts/afgwpdBBkkD
Edited by PsYcHoKiLLa, 17 July 2012 - 10:19 PM.
#28
Posted 18 July 2012 - 02:39 AM
#29
Posted 18 July 2012 - 03:45 AM
Dazzozo, on 17 July 2012 - 06:06 PM, said:
I already have CM9 in ~/android/source/cm9
I should do the following?
~ $ mkdir ~/android/source/cm10
~ $ cp -r ~/android/source/cm9/.repo ~/android/source/cm10
~ $ cd ~/android/source/cm10
cm10 $ repo init -b jellybean
cm10 $ repo sync
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#31
Posted 18 July 2012 - 01:31 PM
#32
Posted 18 July 2012 - 02:13 PM
No actually this: http://developer.and...jelly-bean.html
#33
Posted 18 July 2012 - 02:18 PM
Edited by PsYcHoKiLLa, 18 July 2012 - 02:28 PM.
#34
Posted 18 July 2012 - 02:51 PM
How are the CM specific feature integration going along, any news?
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#35
Posted 18 July 2012 - 02:56 PM
from
<project name="Dazzozo/android_device_zte_blade2" path="device/zte/blade2" remote="github" revision="ics" />
to
<project name="Dazzozo/android_device_zte_blade2" path="device/zte/blade2" remote="github" revision="jellybean" />
And in future, the other two?
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#36
Posted 18 July 2012 - 05:36 PM
MadEye Moody, on 18 July 2012 - 02:56 PM, said:
from
<project name="Dazzozo/android_device_zte_blade2" path="device/zte/blade2" remote="github" revision="ics" />
to
<project name="Dazzozo/android_device_zte_blade2" path="device/zte/blade2" remote="github" revision="jellybean" />
And in future, the other two?
Other two? You should only have the device and the props.
#37
Posted 18 July 2012 - 06:01 PM
Dazzozo, on 18 July 2012 - 05:36 PM, said:
<project name="CyanogenMod/zte-kernel-msm7x27" path="kernel/zte/zte-kernel-msm7x27" remote="github" revision="ics" />
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#38
Posted 18 July 2012 - 06:07 PM
MadEye Moody, on 18 July 2012 - 06:01 PM, said:
<project name="CyanogenMod/zte-kernel-msm7x27" path="kernel/zte/zte-kernel-msm7x27" remote="github" revision="ics" />
That is pulled automatically via cm.dependencies. So no, it is not needed.
You just need the props (still on ics) and the device (on jellybean).
#39
Posted 18 July 2012 - 07:14 PM
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
#40
Posted 18 July 2012 - 07:37 PM
make: *** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/blade2/system/app/RomManager.apk'. Stop. make: *** Waiting for unfinished jobs....
Shell script (cron ready) to automate syncing, compiling and trimming(requires zip_trimmer.sh) CyanogenMod (currently for CM10, with just a few modifications, will work with CM9 source) : https://www.dropbox....htly_release.sh
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account


Back to top









