It is just a sneek peek of upcoming ICS. Not intended for daily use.
What is currently working:
Phone
Sound
Sensors
Lights
Wifi
Bluetooth
USB mass storage
HW keyboard (ALT lock too)
Keyboard backlight
HW/SW keyboard toggling (thx Hashcode!)
OpenGL (3D)
Multitouch (more points + multitouch fixed)
Keyboard layout switching
Fixed PIN unlock (thx Nadlabak!)
Camera support (thx Rondoval!)
What is not working:
Video recording
Video HW decoding
Probably still a lot of minor issues
Other known issues:
ADB debugging shouldn't be disabled
Latest version for phones with European GB kernel:
http://code.google.com/p/cm-milesto...9-20120305-NIGHTLY-milestone2-eu.zip&can=2&q=
Latest version for all other phones:
http://code.google.com/p/cm-milesto...9-20120305-NIGHTLY-milestone2-ch.zip&can=2&q=
If your phone is stuck on red Moto logo, it means you have chosen a wrong version and you need to recover your phone from the SBF file.
Google apps 4.0.3:
http://www.fileserve.com/file/VMntMjB/gapps-6.0-IML74K.zip
Repository:
repo init -u git://github.com/tezet/android.git -b ics
Many thanks for tpruvot and Quarx2k for their tremendous work which made a solid fundaments for this ROM!
Nice
Tezet, have you tried to build ics with new 2.3 european kernel?
will5 said:
Nice
Tezet, have you tried to build ics with new 2.3 european kernel?
Click to expand...
Click to collapse
Not yet. I doesn't have high priority on my todo list
tezet said:
Not yet. I doesn't have high priority on my todo list
Click to expand...
Click to collapse
when i was testing the defy 4.0 port. i have the same issue on usb connection. and i found that when usb connect, nothing were written to /sys/devices/platform/usb_mass_storage/lun0/file.
normally, /dev/block/vold/179:0 should be written to there.
but more instersting is that after i use dual sd mount widget. even i uninstall it(not reboot), my usb can work normally. but after reboot, it buggy again.
---------- Post added at 01:21 AM ---------- Previous post was at 01:15 AM ----------
will5 said:
Nice
Tezet, have you tried to build ics with new 2.3 european kernel?
Click to expand...
Click to collapse
european kernel seems to have some check on system version or bl version. as some guys said in other thread. flashing only euro kerenl/devtree will not boot at all. so maybe ch kernel is another possible choice.
edit: just heard some news from defy section, they seems to use gb kernel in future 4.0
Nice Work
Very good to see that you guys are working on this new Android to Milestone 2, this make me don´t want to trade my cellphone!
I´d like to thank you for your great work, and as soon as this version is working i will try!
looks promise. thanks you,tezet!
It looks sooo beautiful! I am awaiting it eagerly!!!
great work guys.....looking forward for this....
Great!!
but my razr might come next week.....
I won't sell my ms2 anyway, after move to razr I can be a tester on new roms and not to fear many things don't work as I got another phone to use
Sent from my Milestone 2 using XDA app
Good job!!
But since I flashed my phone to the official GB, it seems that I must wait for a while.
Fortunately, I like the new blur, though the ram usage is much higher than CM7...
I will keep waiting for the stable version!
Thanks for your great work
Looks amazing tezet! when i got my MS2 at the start of the year i never would have thought some of the stuff that has been done with CM on the MS2 could have been done.
A great dev team has made this possible!
this is great news! i can't wait to test this! thanks a lot for making this possible guys.
Endless7 said:
just heard some news from defy section, they seems to use gb kernel in future 4.0
Click to expand...
Click to collapse
Endless7: Can you give a link where you read that?
Really appreciate your work Tezet. Thanks!!
sahilarora911 said:
Endless7: Can you give a link where you read that?
Really appreciate your work Tezet. Thanks!!
Click to expand...
Click to collapse
https://github.com/tpruvot/android_device_motorola_jordan/commits/ics
https://github.com/Quarx2k/android_device_motorola_jordan/commits/ics
n3ptun3 said:
https://github.com/tpruvot/android_device_motorola_jordan/commits/ics
https://github.com/Quarx2k/android_device_motorola_jordan/commits/ics
Click to expand...
Click to collapse
Thanks n3ptun3!!
But I am not used to github repos.
Does the mention of "Temporary fix permissions for gb kernel" is what you ppl are referring to? Are they talking about GB kernel that came with Euro GB update of M2?
sahilarora911 said:
Thanks n3ptun3!!
But I am not used to github repos.
Does the mention of "Temporary fix permissions for gb kernel" is what you ppl are referring to? Are they talking about GB kernel that came with Euro GB update of M2?
Click to expand...
Click to collapse
It has nothing to do with Milestone 2. It's the kernel from one of Defy's GB roms.
I've managed to get keyboard working apart from 'B', which really puzzles me. Interestingly ALT lock is now working This is due to new, very flexible keyboard handling introduced in honeycomb.
There seems to be bug in keyboard lid detection, the logic was inverted.
Thank you for your awsome work and looking forward to other builds.
Endless7 said:
european kernel seems to have some check on system version or bl version. as some guys said in other thread. flashing only euro kerenl/devtree will not boot at all. so maybe ch kernel is another possible choice.
edit: just heard some news from defy section, they seems to use gb kernel in future 4.0
Click to expand...
Click to collapse
I also thought of that. I started playing with CH GB kernel (actually I just boot up out of it). For those stuck with UK GB we can just prepare builds based on this kernel (at least I think so .
tezet said:
[...] For those stuck with UK GB we can just prepare builds based on this kernel (at least I think so .
Click to expand...
Click to collapse
It would be great
Related
What a crazy 3 months it has been, with life in general getting in the way of development, but it's over and here is a release for everyone!
For the full list of changes please see the changelog at http://bit.ly/aH0ioL.
*Please note*
All Google apps that are available for download from the market will no longer be included in the CCRoms Google apps package, to facilitate updating the apps the way Google intends.
Also this release is FROYO, Gingerbread will most likely be our next release with this gem version's features ported to AOSP Gingerbread.
The Main Highlights:
Obsidian for the Droid X is now a fully stable build, some minor bugs might still exist, but otherwise it is rock solid.
Tanzanite for the Droid 2 is also stable build, since it is so close to the Droid X.
Emerald for the HTC Evo is also stable for all pre-2.10 and 2.02 hboot updates.
Sapphire is just as stable as ever.
Ruby has been updated to the Miui ril for better connectivity and is more stable than ever.
That's right we are now on 5 phones, Thanks for all of your support everyone!
Now for the important part, Obsidian 2.0, Ruby 2.0, Sapphire 2.0, Tanzanite 2.0 are released!
All Downloads are available under the downloads section on our wiki: http://wiki.ccroms.net
Be sure to read the wiki pages fully for known issues and install instructions for certain roms.
NOTE: Emerald has been having some kernel issues and 2.0 will be delayed slightly.
wow. amazing. thank you guys soooo much! so nice to have a true aosp rom
can you post some screenshots?
if you notice any bugs please post them to the bug tracker (bugs.ccroms.net)!
(be sure to check if the bug exists before posting a new one)
hope everyone likes the release!
caseyman4285 said:
can you post some screenshots?
Click to expand...
Click to collapse
it should look like stock android 2.2.1 exactly.
I was about to come put a notice up here that Tanzanite had dropped, glad to see you guys beat me to it and it's here on XDA
jrhoades858 said:
it should look like stock android 2.2.1 exactly.
Click to expand...
Click to collapse
ok thanks.
Well, this just made my day.
In your first post it says tanzinite for D2 is stable but on wiki has it listed as beta. Am I looking at wrong download on wiki page?
Sent from my DROID2 using XDA App
willjohnson said:
In your first post it says tanzinite for D2 is stable but on wiki has it listed as beta. Am I looking at wrong download on wiki page?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It's beta and very much not ready for daily use. Wait a little while for the bugs to be ironed out if you need a fully working ROM.
i've taken tanzanite offline momentarily due to some unexpected issues with it booting back into a proper recovery. if you have already installed it i apologize for the oversight. SBFs work fine and only /system and /preinstall are overwritten during installation of tanzanite.
either way, i hope to have this resolved ASAP.
sorry again for the mistake :C
Hideaki02 said:
It's beta and very much not ready for daily use. Wait a little while for the bugs to be ironed out if you need a fully working ROM.
Click to expand...
Click to collapse
Thanks. Gotta be stable for me. Use my phone for work.
Sent from my DROID2 using XDA App
cvpcs said:
i've taken tanzanite offline momentarily due to some unexpected issues with it booting back into a proper recovery. if you have already installed it i apologize for the oversight. SBFs work fine and only /system and /preinstall are overwritten during installation of tanzanite.
either way, i hope to have this resolved ASAP.
sorry again for the mistake :C
Click to expand...
Click to collapse
IT happens. I tested last night before the pull and had massive battery drain, failure to program, slow and jilted performance, and got into a boot loop when I rebooted the phone.
I"m back on my previous ROM but I'm still incredibly excited to see a stable of this ROM.
Thanks for all the work!
Have these issues been resolved yet?
I have some time to mess around with this today, but waiting to hear back on jobs, so can't take time to sbf and such either.
whats the dx version called? obsidian or something? any way, heres what i did. i flashed the 2.0.1 version for the dx cus i know its probably got more attention then the d2 version. then i flashed kejars dx to d2 port .zip from here http://forum.xda-developers.com/showpost.php?p=9896754&postcount=4 I saw camera listed as a known bug but im taking pictures just fine no video though, and the alt lock button doesnt work. you can still lock alt by double tapping alt. no video, no alt. lock are only 2 issues ive found so far. this rom is very smooth and responsive.
Copied what this guy ^ did and everythin g works except the gps alt lock and camcorder also another I noticed was the accelerometer doesn't work either
Sent from my DROID2
mikeyinid said:
whats the dx version called? obsidian or something? any way, heres what i did. i flashed the 2.0.1 version for the dx cus i know its probably got more attention then the d2 version. then i flashed kejars dx to d2 port .zip from here http://forum.xda-developers.com/showpost.php?p=9896754&postcount=4 I saw camera listed as a known bug but im taking pictures just fine no video though, and the alt lock button doesnt work. you can still lock alt by double tapping alt. no video, no alt. lock are only 2 issues ive found so far. this rom is very smooth and responsive.
Click to expand...
Click to collapse
What bugs were in obsidian when u flashed it?
Can u still SBF if u flash obsidian?
jaypatel32795 said:
What bugs were in obsidian when u flashed it?
Can u still SBF if u flash obsidian?
Click to expand...
Click to collapse
The only bugs I've found with obsidian on my d2 is alt lock doesn't work, gps doesn't work, camcorder doesn't work(camera does), acceelerometer doesn't work and I haven't had a chance to check usb
Sent from my DROID2
whezzel said:
The only bugs I've found with obsidian on my d2 is alt lock doesn't work, gps doesn't work, camcorder doesn't work(camera does), acceelerometer doesn't work and I haven't had a chance to check usb
Sent from my DROID2
Click to expand...
Click to collapse
Usb works and I'm almost positive accelerometer did to. But I could be wrong. Issues along the same lines as the ud release for dx/d2.
Sent from my DROID2 using XDA App
mikeyinid said:
Usb works and I'm almost positive accelerometer did to. But I could be wrong. Issues along the same lines as the ud release for dx/d2.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Idk. My accelerometer didn't work. I even tested with an app. Nothing
Sent from my DROID2
THE DEVICE HAS BEEN MODIFIED SO THAT IT CAN NOW SHOOT BOTH RED(NEW) AND GREEN(OLD) CAMERAS.
I've been unable to make green lense kernel modules work well with new kernel. GB kernel is dicks!
So i performed a fusion of 2.3 firmware onto 2.2 kernel via 2nd-init.
Pros:
Stable kernel
No ultra-bright buttons
Cons:
Somewhat slower than official 2.3
Live Wallpapers don't work
Contents:
2.2 (3.4.2-177) kernel
4.5.134 ramdisk
EGL drivers from Froyo
Camera libraries from Froyo
Sensors library from CM7
libsurfaceflinger/libserver_init from Droid2 GB OTA
libcamera wrapper by me, based on CM7 wrapper by maniac103
BlurCamera ported from Froyo (GB one is not stable)
Installation:
Install official GingerBread via nandroid + fixed sbf
Install 2nd-init recovery 0.6.1 or later
Install zip from recovery
Download:
http://tihiy.net/files/greenlens/GreenBread_1.1_release.zip
Make mirrors.
Disclaimer:
This is tested on latest (134) leak but may work on older or newer releases. I'm interested in results on those.
This is beta mod of beta firmware with frankenstein-esque methods
This may or may not work on red lenses
I'm not responsible for your damages
Please don't spam this thread with bugs, don't start flamewars and don't whine
Thanks to everyone in CyanogenDefy team!
Mention me if you're using my work.
GOOD。
but i used CM7 now.
I guess this will cause usb and wifi tether to not work?
This is great. i have red lense but this makes gingerbread development able for everyone.
This is just a great work for green lensed phones....
ephumuris said:
I guess this will cause usb and wifi tether to not work?
Click to expand...
Click to collapse
Usb thether seems not working (was it ever working? dunno), 3g-wifi tether works.
great job,
i tried to mix old kernel with new ramdisk&/system - apparently failed.
Amazing, I will wait some day and I'll try for sure
Anyone already running it? If so how is it.
Sent from my MB525 using XDA App
XDA, I'm dissapoint! Why are you afraid to try?
Simplestas said:
XDA, I'm dissapoint! Why are you afraid to try?
Click to expand...
Click to collapse
im trying it rite now, will post feedback asap.
good job!
my defy with green lense works fine!
thx
I'm really happy this has finally been done. I've sold my Defy few days ago and I regret that I could give the official 2.3 ROM a try. Good work !
works like a charm in my green lens defy. by the way, its the first time im running official 2.3.4, 4.5.1-134. i found it a bit laggy in comparison with nordic froyo and miui. maybe i need some reboots. im runinng shadow´s rooted version by walter (nandroid + fixed sbf).
EDIT: in the OP theres an advice that says live wallpapers dont work, im at wpclock 1.5.3 working as well.
yes dont work live wallpaper!
iaio72 said:
good job!
my defy with green lense works fine!
thx
Click to expand...
Click to collapse
is the recording still choppy like in CM7 or as smooth as froyo
Help?
I have a stock gingerbread unrooted and I wanna try this. I've been searching, and it seems that the only way to get the phone rooted is having froyo first and flashing a nandroid. I am really lazy to go back to froyo. Is there any way to root GingerBlur?
I dont understand its for kernel 2.2.2 but we want for Gingervread kernel
But thanks
Is there any problem except live wallpapers.How is performance?I shld install and try this.
Is it support touch focus???
mick711 said:
I dont understand its for kernel 2.2.2 but we want for Gingervread kernel
But thanks
Click to expand...
Click to collapse
How many times does it needs to repeated there is no such thing as gingerbread kernel. Kernel is one thing android version is another! Gingerbread can work with 29 32 35 kernels. Moto uses 32 to GB and froyo too.
I have picked up an old project I was working on, getting Eclair on our phones.
Now you might think, why Eclair, it is much older than Froyo and we already have Gingerbread!?
The answer is simple, just because we do not have Eclair roms for our phones
Some people here think newer is always better, but that is not always the case
Eclair is already booting, but I have some FC's and launcher does not work correctly. Neither any other things work.
I was trying to get a logcat, but could not connect using adb.
Perhaps someone else can give me a solution for enabling adb?
What did I use to get eclair booting up?
Froyo bootimage
Compiled Eclair using Froyo-libs and kernel.
If you want to take a look at it, here is a pre-pre-alpha where nothing works
It is not the latest, because I'm already solving some problems.
Reserved for future use
Why are you doing this?????
Raffy 97 said:
Why are you doing this?????
Click to expand...
Click to collapse
Damn ---^^^open your eyes wide n read d first post!
Sent from my LG-P500 using Tapatalk
First: Congrats
Second: Provide some logcat,maybe you have same problem as mine in OMFGB (missing resources in apks)
Third: Upload to your gitHub,I'll have a look
BTW: Could you check if you have any /build/core/kernel.mk? Really getting mad with that error on CM6.
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
_Arjen_ said:
Could not get any logcat
But it's solved
Launcher is working now!
Updated build.prop, checked if some files existed, but some were missing.
Guess I forgot something in device-files
Now working on sd-card mounting, gsm and wifi, if these are fixed I will provide an updated zip (this zip contains generic build.prop )
Click to expand...
Click to collapse
Non-working RIL could be caused from three things:
You missed LG services into makefiles/.rc files (if you want I can PM you some strings to add to .rc files)
Wrong libs (easy to check)
Non-prelinked libraries (define TARGET_PRELINKER_MAP (or some like that) into device_thunderg.mk and modify prelink-linux-arm-msm7xx7 or some like that with names of unlinked libs. You can see what stuff isn't prelinked with a debugging-enabled linker you can find into Swift-sense Mur4iK GT540 post. For prelink address,use google because I don't know
Would this have any actual speed benefit?
Sent from my LG-P500 using Tapatalk
You will absolutely encounter speed differences with Gingerbread.
You will even have more space available, romsize is rather small
_Arjen_ said:
You will absolutely encounter speed differences with Gingerbread.
Click to expand...
Click to collapse
yes performance will be 2x(low) xD
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
ccdreadcc said:
yes performance will be 2x(low) xD
Click to expand...
Click to collapse
Reply to my private message
Sorry for offtopic
Sent from my LG-P500 using XDA Premium App
CAF Code right?
BTW,Did you build kernel together with the system? If so check your kernel.mk into /build/core. I'm getting mad at it.
Sent from my LG-P500 using XDA Premium App
No, this one is just AOSP with some LG crap
And booting using original LG Froyo kernel for now
Seems most compatible
Perhaps later a custom kernel will be used
Sorry for this off topic, but, good job and good luck ^_^ i hope you can successfully do this i loved the older builds of android an would love to go back to it, i wish i could help in some way and this is the best i can do :3 but good luck
What's up with RIL Arj?
_Arjen_ said:
If you can't contribute anything usefull, do not react here, I was glad SWEATTAIMI has stopped with it after many warnings and now you start
Anyway, Eclair is more smooth than Gingerbread on our phone (at least this version)
Click to expand...
Click to collapse
whaa xD what now lmao,
good to see we can use eclair hope the look is as i remember D:
It is still as simple as Eclair is, it still uses the KISS principle
_Arjen_ said:
It is still as simple as Eclair is, it still uses the KISS principle
Click to expand...
Click to collapse
It didn't boot for me so i were not able to test
Sent from Mexico
The one posted here just boots to UI but launcher etc FC. (that is why it is called pre alpha)
Got one with working launcher now, but spent some time on OMFGB with Bytecode and CM9.
As soon as all is working I will release a beta.
I write this new thread because that`s important new
experiences i think!!!!!!!!
I found out that now you can choose Gingerbread or Froyo Kernel
on your CM9 (versions from 4.february 2012)
I´ve installed CM7 Kang RC1 3 feb.2012 , you can find it here
http://forum.xda-developers.com/showthread.php?t=1470721
http://fitsnugly.euroskank.com/gigglebread/index.php?id=jordan
And in second boot ICS CM9 Nightley 4.feb.2012 , it can be found here:
http://forum.xda-developers.com/showthread.php?t=1353003
http://tanguy.forumdoandroid.com/
http://defy-cm.net/defy-cm9-nightly/
First i was on CM7(Froyo Kernel) -- Everything exept. the known issues was working....
Then i Flashed the CM9 kernel wich could be fount in the upper links
and Everythings......... works .......
For me thats new because of in my last experiences with those Roms ,
there were two Versions with different Kernel usage :
CM7/CM9 version for Defy with Froyo kernel
CM7 /CM9version for Defy/Defy+ with Gingerbread Kernel
And now one and the same CM7 can be used on both kernel
And the gingerbread telephone network bug in 2nd boot is fixed!!!!!!!!!!!
3d Gallery works in ICS!!!
Thanks to kang,epsilon,walter,quarks ....
This should not be in the development section.
Passa91 said:
This should not be in the development section.
Click to expand...
Click to collapse
its still nice for the devs, to see some appreciation.
Sent from my MB525 using xda premium
so...if I flash CM9 from 04/02/2012... then flash the GB kernel zip.....the rom will work?...Its that what are you saying?
jufa2401 said:
its still nice for the devs, to see some appreciation.
Click to expand...
Click to collapse
No, that's what the "thanks" and "donate" buttons are for.
@bone101 : Thanks! Exciting report!
Can you specify what hardware you have, Defy green/redlens, Defy+ ?
and also specify what SBF build you use as base before you flash ?
When you write "Froyo kernel" and "Ginger bread Kernel", do you mean: "CM7_Kernel-signed.zip" and "CM9_Kernel-signed.zip" (Fritolays http://forum.xda-developers.com/showpost.php?p=20148046&postcount=1624 )
or do you refer to some other Kernel files ???
(I guess the 2 filenames below are the same as the ones fritolays re-packed. I'll update here when i get answer )
CM9-ICS-multiboot kernel_2.3.4.zip = the kernel from CM9-ICS-MR0-111207-jordan.zip
CM7.1-11-kernel_2.2.2.zip = ?
http://forum.xda-developers.com/showthread.php?t=1353003&highlight=cm7+kernel+froyo&page=162
So much stuff around we needs to be very specific so that we understand eachother.
You might want to check this thread where I am trying to collect some info about the Kernel versions that are used in the CM7 & CM9 builds after 7:th December 2011
http://forum.xda-developers.com/showthread.php?t=1477554
-----------------------
Info about my DEFY PLUS
System Version: 45.0.74.MB526.Retail.en.DE
Model number: MB526
Android version: 2.3.4
Baseband version: EPU93_U_00.60.00
KERNEL VERSION: 2.6.32.9-gbad50c3
[email protected] #1
Build number: 4.5.1-134_DFP-74
I flashed CM9 over Feb 4 build, it bootloops.
ICS is working very good, but it has very little in common with CyanogenMod.
It is very AOSP-like now.
If you are okay with vanilla Android, then you can use ICS very soon (because camera will be working soon, I think).
If you are like me, and need the functions of CM that make CM so great, than ICS isn't usable at all (for now) for you.
bone101 said:
Thanks to kang,epsilon,walter,quarks ....
Click to expand...
Click to collapse
there is no Kang but Fuzz.... kang means it's sort of before nightly version...
The only unusable functions fir the ics 31st nightly was the camera, other than that, all major phone functions work. Froyo kernel. but everything is better than cm7
Got a Headache? It's all in your Head.
Sorry for wrong forum...
Defy MB525 red lens....
I mean CM7kernel-signed.zip = froyo 2.2.2 kernel (signed.zip) and CM9kernel-signed.zip=gingerbread 2.3.4 Kernel (signed.zip)
I Flashed CM7.2 Kang over CM7.1-stable in
How to install each rom pls. look at the at their developers posts!!
Now can i flash walters builds (to get HD record and play HD Video)
and have CM9 ICS in 2nd boot
DHT-22 Kernel works too for both roms....(look at MS2Ginger builds from walter79)
Pls. move this tread to the place where you tihnk its belong
I have the red lens defy running defy+s 236 rom. Can i flash cm9 with that?
cm9 defy+
will someone please tell me the latest cm9 build for a defy with sbf defy+ 2.3.6?
soxvirus, flanagan..
[ICS] "CM9" Experimental Builds for the Defy !
http://forum.xda-developers.com/showthread.php?t=1353003
builds for 2.3.6 defy+ found in first post
I need 2nd init to install CM9? What version of 2init?
Can I have the stock GB rom and CM9 with 2nd init?
soxvirus, search the forums, read the guides !
first study this basic guide: http://forum.xda-developers.com/showthread.php?t=1216982
then study the specific CM9 version+thread you are interested in.
salingpusa said:
The only unusable functions fir the ics 31st nightly was the camera, other than that, all major phone functions work. Froyo kernel.
Click to expand...
Click to collapse
ONLY the major functions of the phone are working.
The little things that make all the difference between CM and Vanilla Android aren't even finished yet.
Read here:
http://www.cyanogenmod.com/blog/progress-on-cm9
This was posted today.
salingpusa said:
but everything is better than cm7
Click to expand...
Click to collapse
Nope. Just not true. In CM7 everything works just fine AND the excellent configurability of a true Custom Rom is there. That is what I expect from CM.
The ICS Versions for the Defy are very good, but they lack those parts of CM that make it excellent. And that is not the Quarks' fault or Epsylon's fault, it just isn't finished yet.
salingpusa said:
Got a Headache? It's all in your Head.
Click to expand...
Click to collapse
I'm not sure what you mean. Are you talking to me ? It sounds like an insult.
Just because the current CM9 Roms are good enough for you, it doesn't mean they are good enough for everyone.
thedoginthewok said:
Got a Headache? It's all in your Head.
Click to expand...
Click to collapse
I'm not sure what you mean. Are you talking to me ? It sounds like an insult.
Click to expand...
Click to collapse
It's not, it's his tapatalk signature, you can see it in every post he makes. Don't get all fired up so fast, we're all on the same team here. We should all meet for a beer. Or five
Relax, learn, enjoy you DEFY's, spread the knowledge, I think that's the policy we all follow
niksy+ said:
We should all meet for a beer. Or five
Click to expand...
Click to collapse
Definitely sounds like an awesome plan
My first intention to open this thread was that its possible to run the new CM7 and CM9
on Defy or Defy+ --- the same Rom for both
But now im think its not possible , because i´ve tried to install MS2Ginger 3.0NG-RC which work very well, but my CM7Fryo in 2nd boot dosent...
I will try my luck with CM9ICSFroyo in 2nd, maybe 2nd boot need CM9/ICS
CM9/ICS for Defy+ would work
I originally released this rom on 2fastforums.com (http://2fastroms.com/showthread.php?5435-WIP-18-Dec-2012-CM7-Kernel-CM-msm7x30) and now feel it is ready for release on XDA. (Site is currently down for unknown reasons)
CM7 for HTC Merge/Lexikon
Click to expand...
Click to collapse
Code:
Features:
-100% stock CM7 from source
What works:
Almost everything
Click to expand...
Click to collapse
What doesn't work:
MMS on USC?
Jittery Compass
Click to expand...
Click to collapse
Instructions
1) Flash recovery through bootloader or fastboot
2) Boot into recovery and factory reset, also go into mounts and format system
3) Flash Rom
4) Flash GApps
Click to expand...
Click to collapse
Downloads
Recovery: http://d-h.st/users/e334/?fld_id=6766 (Either one will work, I personally prefer v5.0.2.8 Capacitive Touch)
ROM: http://d-h.st/users/e334/?fld_id=6727
GApps: https://www.box.com/s/79bpq0ywdxcf4093t926 (thanks liamf1!)
Click to expand...
Click to collapse
Source
Kernel: https://github.com/jianC/htc-kernel-msm7x30
Lexikon Device Tree: https://github.com/jianC/android_device_htc_lexikon
Lexikon Proprietary Vendor Tree: https://github.com/jianC/android_vendor_htc
Click to expand...
Click to collapse
All my changes are documented on github.
Credits: Cyberblade (CDMA fix), liamf1 (beta tester/helpful feedback) 2fast4u88, Cyanogenmod & Team, Kali-, Neopeek & Team, UnitedDev & Team, and everyone else who contributed.
Please leave any feedback about bugs/problems/glitches/etc and I will try to fix them.
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
faille13 said:
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you on here too
Lol yeah, I'm everywhere.
Sent from my HTC Merge using Tapatalk 2
---------- Post added at 01:34 PM ---------- Previous post was at 01:12 PM ----------
I don't get around here too often. I haven't seen a dedicated forum for my merge yet.
Sent from my HTC Merge using Tapatalk 2
GPS problem
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Gytixas said:
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Click to expand...
Click to collapse
Hmm.. i'll look into it.
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Mistake
sorry sorry, GSM works perfect, Just needed to reboot. Thanks a lot. but Bluetooth and GPS doesn't work either. Plz fix these bugs ! Thanks
nikoloz995 said:
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Click to expand...
Click to collapse
+1
development of the firmware is?
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
lexikonlover said:
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
Click to expand...
Click to collapse
APN backup and restore app worked for me on US Cellular (backup apn from stock install, then restore to CM7), though I had to switch to GoSMS as a messaging app for MMS to send properly (stock app would receive but not send MMS - SMS worked normally in both). I had no success manually entering the apn info - didn't seem to have any effect when I tried.
@JianC
I found an issue with the 20130121 version from Jan 21 you posted on 2fastroms: If the phone is left on the charger it will charge all the way up, then discharge all the way back to zero while still plugged in. It still displays that it is at 100%, but then abruptly drops to whatever the actual charge level is after a few minutes of use. I've tried wiping battery stats to no effect and it works properly in stock rom. This is the only bug I can't seem to work around... Any fix or suggestions for things to try would be most appreciated! Thanks again for your work on this ROM!
Fixed GPS (and other issues), please see OP!
EDIT: I'll look into the apns issue... I don't use my Merge on CDMA so it's a stab in the dark.
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
jianC said:
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
Click to expand...
Click to collapse
CM10.1 availible to test?
DJ_MiX said:
CM10.1 availible to test?
Click to expand...
Click to collapse
Nope, he working on kernel .
http://review.evervolv.com
Sent from my HTC Merge using xda premium
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
linuxsociety said:
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
Click to expand...
Click to collapse
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
@ everyone: CM9 for the htc merge is here!: http://forum.xda-developers.com/showthread.php?p=44487058#post44487058
jianC said:
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
Click to expand...
Click to collapse
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
linuxsociety said:
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
Click to expand...
Click to collapse
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
jianC said:
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
Click to expand...
Click to collapse
This sounds about like the exact same issues that was experienced when I was helping hashcode work on the original kindle fire device and getting it to work with ICS. I 'think' with the HTC it shouldn't be near as hard to resolve the issue to get full hw acceleration, memory mappings camera/gps and all the extra bells and whistles if we make an attempt at backporting the necessary support into the .35 kernel instead of trying to upgrade * to 3.x which will be adding to the work and break more things than it fixes. Since HTC apparently isn't going to be releasing any updates for the device it looks like it is going to be left all up to us to make one of two decisions:
1) backporting kernel - only the few things remaining needed for our current working GB kernel to have full support for ICS/JB roms
OR
2) updating to 3.x.x and merging HTC fixes and 3rd party patches -through several mainline kernel patches and keeping the proprietary htc addins compatible.
My opinion/suggestion:
I'd think of the two options that backporting would be the most logical answer to the equation since we are only missing support for few things and you already have everything working except the camera, ION, BINDER(?), and other >=3.0.0 android patches. Plus the device is pretty well coming to a good place to say cease development work and either enjoy the device or upgrade to something newer. So if we could get JB support or even just ICS working fully I think 99.99% of all owners/users would be more than 99.99% happy!! I know I would be very happy myself!