Related
I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you
I want to start by saying THANK YOU FOR MIUI!!!! You are awesome. And they have got cm7 booting up on xt720 but only if you flash motoroi 2.2.1. But the touch screen is not working. If I were you I'd get with Mioze7Ae. He's the Guy to talk to about it. There is a thread with the ROM download in it in the general thread.
oyang06 said:
I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you
Click to expand...
Click to collapse
stlifey made a port of CM7 to XT701. That is here:
http://forum.xda-developers.com/showthread.php?t=1064090
If download links are dead there, let me know and I can mirror/reupload.
I think this is the main development page for the XT701 CM7, but the forum seems to be down for maintenance right now:
http://bbs.gfan.com/android-1297281-1-1.html
It doesn't work on XT720 yet. This is where things stand:
Using Milestone XT720 2.1 sbf
If you use a Milestone XT720 sbf, then it doesn't boot. I've been modifying it and have gotten it to go further with adb logcat working to get some messages out. This is the latest version I've been testing that makes it the furthest before rebooting:
http://www.multiupload.com/ULWN2ERP02
The radio panics and panic_daemon shuts down the phone. If you modify the init scripts, you can disable panic_daemon. Then it will boot to the point that zygote tries to start but has a library link problems so I've changed too many libraries .
From Korean Motoroi XT720 2.2 sbf
sktjdgns1189 figured out that if you flash the Korean Motoroi 2.2 sbf, root, install OpenRecovery, and apply the XT701 update without any modifications it boots up, but the digitizer doesn't work. You can do some things like long press the camera button to get the camera to come up and you can take pictures. See
http://forum.xda-developers.com/showthread.php?t=1118236
Eventually it will crash and reboot. The bad news is that for some reason after you flash the the Motoroi sbf on Milestone XT720, you can't use volume-up to enter OpenRecovery. So you have to use adb ("reboot openrecovery") to get back into OpenRecovery. But I haven't been able to get adb to startup. So that means you're back to sbf for the next try. I can't figure out why the touch screen doesn't work.
sktjdgns1189 has also figured out how to get the battery notification working:
http://forum.xda-developers.com/showthread.php?t=1124927
Edit: Forgot to mention that we're now pretty sure that sktjdgns1189 has a Motoroi XT720 based on his photos. I've reproduced most of his results on a Milestone XT720.
easye420 said:
I want to start by saying THANK YOU FOR MIUI!!!! You are awesome.
Click to expand...
Click to collapse
+1. Very fantastic work on MIUI. Great to see you looking into CM7 as well.
its going to be on android 2.3 right?
eejin2 said:
its going to be on android 2.3 right?
Click to expand...
Click to collapse
If someone gets CM7 working then yes that is Android 2.3
Thank you Oyang06 for Miui rom and I wait CM7
Sent from my XT720 using XDA Premium App
Looks like stlifey plans to release CM 7.1 for XT701 this weekend.
Off topic: Does anyone know what all the "ah"s that Google Translate adds means? I think wiktionary suggests "啊" == surprised+"!"? Also, does anyone know a good place to look up those four-character idioms? There's one about hunters that comes up a lot. Just curious.
lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"
khankuan said:
lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"
Click to expand...
Click to collapse
I see! The google translated posts just seem a little strange because I guess "ah" and "oh" would come at the front of the expression in English. It can seem like reading threads where everyone is talking about Candlejack and then sudde
Haha, just post here if you need any translations awaiting patiently for CM7 Gingerbread XDXD
i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
do you think we can get 2.3 miui running on our phone?
eejin2 said:
i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
Click to expand...
Click to collapse
Yeah, gingerbread is much more attractive than 2.2 and below all around. Plus it's supposed to be faster (and CM is supposed to be even faster) and have other goodies... would be so fantastic to see this for the XT720.
if you want to use adb
just use 2nd-init (default.prop : ro.secure=0, ro.debuggable=1, persist.service.adb.enable=1, persist.factory.allow_adb=1)
(and some code in init.mapphone_umts.rc (it for adb on bootup))
then you can use logcat/dmesg and etc even on bootup
wait and sad
CM7 would be a dream come true.
Best of luck guys, I will be watching
Wish I would know how to contribute to this happening... would make me feel better knowing I was making some progress. Well, hope this goal is attainable.
Dexter_nlb said:
Cyanogen from Milestone could easily be ported, like i did htc sense like on milstone... the issue is requirements and added extra button and fm radio.
but the rest would work from a milestone release.. fairly easy to do.
Click to expand...
Click to collapse
I don't wanna sound arrogant and I really appreciate what you guys are doing, but am I missing something?
My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App
mchlbenner said:
My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
No, Dexter posted that in his XT720 thread. I saw that the other day and was considering mentioning it, but I'm sure Mio and others are doing everything already.
Here's the post Dexter is responding to:
"From my understanding of the situation, Cyanogen is out of the question, for now. Dexter's roms are modifications of the official MOTOROI XT720 2.2 (KR) for our handsets. Due to the bootloader lock placed on the phone by Motorola, we can't compile our own systems based on the android sources.
Anybody correct me if I'm wrong with my situation assessment. "
Click to expand...
Click to collapse
Though if Dexter feels it's so simple I wish he would elaborate for the benefit of our devs, just in case he knows something they don't.
Is it possible to build a ROM off of an OS that doesn't officially exist?
Meaning, would I be able to build an Android 2.4 ROM, based off various SDKs?
And if so, how would I do this?
Thanks to all!
But Android 2.4 does exist, here's the proof: http://www.youtube.com/watch?v=lrAjgYDx7yU
twixter said:
But Android 2.4 does exist, here's the proof: http://www.youtube.com/watch?v=lrAjgYDx7yU
Click to expand...
Click to collapse
1- Isn't that a developer version of 2.3? Unreleased?
2- I wanted to build it off of 2.3, 3.0, and 4.0, if that would even be possible, and then have it look unlike anything Android has released yet.
And 3- Thank you for that video. I didn't think it existed
arikaru0 said:
1- Isn't that a developer version of 2.3? Unreleased?
2- I wanted to build it off of 2.3, 3.0, and 4.0, if that would even be possible, and then have it look unlike anything Android has released yet.
And 3- Thank you for that video. I didn't think it existed
Click to expand...
Click to collapse
2.x.whatever is just a software version. So if you are using the baseline code of 2.3, it is still a 2.3 gingerbread based ROM. And if it is a custom ROM, you can call it what ever you want. myrom 6.9..doesn't matter. The only way it is officially 2.4 is if you use the 2.4 source code as the baseline for your ROM. Implementing features from different software versions doesn't make it an official new version of android. When Cyanogen 7 came out based off of gingerbread, it had way more features than 2.3.3. But since it was based off of 2.3.3, the software version was still 2.3.3...Kind of a jumbled post, but hope it helped shed some light.
Just build it off of ics and put whatever features you want into it. I'm not really sure what you want to do. You could build it from froyo or something and make it look like something different.
Sent from my HD2
Please use the Q&A Forum for questions Thanks
Moving to Q&A
lowandbehold said:
2.x.whatever is just a software version. So if you are using the baseline code of 2.3, it is still a 2.3 gingerbread based ROM. And if it is a custom ROM, you can call it what ever you want. myrom 6.9..doesn't matter. The only way it is officially 2.4 is if you use the 2.4 source code as the baseline for your ROM. Implementing features from different software versions doesn't make it an official new version of android. When Cyanogen 7 came out based off of gingerbread, it had way more features than 2.3.3. But since it was based off of 2.3.3, the software version was still 2.3.3...Kind of a jumbled post, but hope it helped shed some light.
Click to expand...
Click to collapse
But could you modify the settings .apk to make it say 2.4? If not, then can you mix and match apps from different version system dumps, or would you need to modify them?
I'm totally new to this, so I don't know how to do any of this
Thanks!
arikaru0 said:
But could you modify the settings .apk to make it say 2.4? If not, then can you mix and match apps from different version system dumps, or would you need to modify them?
I'm totally new to this, so I don't know how to do any of this
Thanks!
Click to expand...
Click to collapse
But just modifying the ROM to say a different version doesn't mean anything. You can make your gingerbread based ROM say software version 1.5...but that doesn't make it a cupcake ROM...
No offense but you seem like you shouldn't be making roms anyway. Its very difficult.
Don't forget to hit thanks
Sent from my HD2
What news to day ?
What news to day ?
lowandbehold said:
But just modifying the ROM to say a different version doesn't mean anything. You can make your gingerbread based ROM say software version 1.5...but that doesn't make it a cupcake ROM...
Click to expand...
Click to collapse
Well, I just want it to say 2.4
michaelnv710 said:
No offense but you seem like you shouldn't be making roms anyway. Its very difficult.
Don't forget to hit thanks
Sent from my HD2
Click to expand...
Click to collapse
None taken, I just want to figure out how so I can make my own rom, due to the fact that all the roms available for the DInc are either really bad, or boring (except MIUI)
I agree, and I guess if your up to it there are some tutorials on the forums or Google it. It would be cool to see something new like that.
Don't forget to hit thanks
Sent from my HD2
How are the roms for the droid incredible "boring"? Have you looked at what newtoroot, jermaine, mcd, incubus, ihftp, and joelz have been doing for the phone in terms of development? Look in the dev thread, tell me inc2 mctwist is "boring." And then tell me that "android 2.4 is cool"
-My life is a shooting range, people never change-
watt9493 said:
How are the roms for the droid incredible "boring"? Have you looked at what newtoroot, jermaine, mcd, incubus, ihftp, and joelz have been doing for the phone in terms of development? Look in the dev thread, tell me inc2 mctwist is "boring." And then tell me that "android 2.4 is cool"
-My life is a shooting range, people never change-
Click to expand...
Click to collapse
I guess 'boring' was the wrong word. I've had the Incredible for a year, and I've gotten tired of Sense, I hate it now. I guess I should've specified farther- I hate Sense, and all the AOSP roms (other than MIUI) are boring.
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.
See page 19 for the seventh build.
Good job! Nice and clean in a new topic. KUTGW!
Sent from my HTC Desire using XDA App
Freaging sweet!
(sorry for spam but this is exciting)
Excellent stuff.
So will that mean close to full HWA?
If we're running any of the ICS builds which have the hardware hacks, this applies, right?
texasice said:
@ those who flashed Chaosz-X new kernel you need to remove this line from build.prop
Code:
ro.config.disable_hw_accel=true
Click to expand...
Click to collapse
@rootSU: I think it does, because it scores almost the same as GB Sense ROMs, and it gets pretty decent FPS at Quadrant (certainly smooth enough), so I think it works fine.
@pnw: haven't tested that, but you can give it a try, it seems pretty logical that it would help
Can't wait for the 3.0 kernel
Sent from my HTC Desire using XDA App
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
mattmanwrx said:
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
Click to expand...
Click to collapse
chaoz tried including the wifi module you use in the kernel in the system/lib folder? can't find it there on the newest kernel. This messed things up for tristan earlier
Oh crap, forgot to supply the bcr4329.ko indeed.
I'm going to try to get a running 3.0 by tonight, if I don't have it finished this evening, I'll upload the WiFi module from the build (using 2 different OS's to work on, Linux for compiling, and Windows for everything else, and working in Win is much easier for me ;p)
Edit: beginning with the really lame methods of getting 3.0 to run, first attempt is done I think, just copied over files, and modified some of them, nothing really special, starting compiling in 5 minutes.
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
*child said:
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
Click to expand...
Click to collapse
But does your wifi work? It didn't work for me...
Not too sure about the camera... it should work... as the added is just libs... the kernel does look at the libs, but doubt it would make a difference... just my guess...
sent from my HTC desire using xda premium
Wifi did not for me. Camera worked but I didn't test it extensively.
Sent from HTC Desire
Camera and wifi doesnt work But HW ac. is fine more speed
Wi-Fi also does not work
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
cant wait 3.0 kernel for n1
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
sweet..kernel 3.0!!
waiting ..waiting..
bunnahabhain said:
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
Click to expand...
Click to collapse
People start with windows at a young age
Sent from my HTC Desire using xda premium
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
I'd like to give it a whirl anyway.
mtnlion said:
I'd like to give it a whirl anyway.
Click to expand...
Click to collapse
ONLY with safestrap, right now. If you try to flash it with the bootstrap it will softbrick your phone.
--EDIT--
Remember safestrap is not really working right now... lfaber06 and I have some highly modified versions that really are not for the rest of the world yet, and my version has a custom compiled version of CWM, and is a little buggy.
jimbridgman said:
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
Click to expand...
Click to collapse
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
lfaber06 said:
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
Click to expand...
Click to collapse
PM me a link to hashcodes d3 CM7 ported ROM (if you have one, I have had a hard time locating a completed one), and not the source code, that is what I used to compile my CM7 port with. I would like to test something, I have a theory on this, that I won't share with everyone here, since it really would not be very interesting here to anyone not trying to port these over.... we will talk more about this in PM.
Thanks!
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
JRW 28 said:
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
Click to expand...
Click to collapse
that is version 2.3.4 we are on 2.3.5 and we HAVE to use ports from 2.3.5 no way around it.
Missed that little details
CM9 does work when flash through bootstrap, I tried it the other day...
farshad525hou said:
CM9 does work when flash through bootstrap, I tried it the other day...
Click to expand...
Click to collapse
Care to share???? Plz.... it may be helpful.
Sent from my MB865 using Tapatalk
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
farshad525hou said:
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
Click to expand...
Click to collapse
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
lfaber06 said:
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yes it sure does thanks, I flashed it, played with it, and I am taking a look at a few things with your CM9 ROM, and since we PM'd I have been digging into the D3 CM7.2 version that hashcode had created. I am not quite ready to flash it yet, but maybe something tomorrow, once I have the ROM to the point that I am happy to play with it on my phone and see what works and what does not.
It looks like the issue with my old CM7 ROM, from the logs I grabbed a little while ago, with logcat, were due to kernel driver files not found during loading, so it looks like my compile had issues linking to our kernel. I so wish I had the source for our phones kernel, it would make compiling CM7 so much easier, and NO the ME865 source will not due, so don't mention it here.
Jim
Glad I could help! Also @lfaber06, what do you mean by your ported version doesn't work? That's the one I flashed.
**Edit** Also the camera doesn't work, if you guys want in to that. Probably an incorrect driver or something...
So... any news to report on either CM7 or CM9?
farshad525hou said:
So... any news to report on either CM7 or CM9?
Click to expand...
Click to collapse
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
lfaber06 said:
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
Click to expand...
Click to collapse
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
farshad525hou said:
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
Click to expand...
Click to collapse
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
lfaber06 said:
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
Click to expand...
Click to collapse
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
farshad525hou said:
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
Click to expand...
Click to collapse
That's the thing idk... I assumed that it was a Sony radio BC when I Google rlidu300-ril.so I get a device tree for a Sony. We need to know what radio we have then we can start checking sources.
Sent from my MB865 using Tapatalk