Hi,
I wonder why a2dp, hdmi, radio is working fully on modaco rom and cyanogenmod needs nvidia 's source to get that working, even thought both roms are gingerbread? Is it a question of kernel? hack? What is the magic?
Thank you.
Modaco's is based off LG's release, rather than publically available sources.
Thank you for your answer.
And what would prevent CM team to use the LG release to get all these things to work? I have even seen somewhere that LG released the source of their rom.
If I understand it right it has nothing to do whit LG´s sources instead it´s Nvidia who has to release their sources.
Correct me if im wrong but CM is based on google source and Modaco (Paul) tweaks stock rom from LG/NVidia. Stock roms have all the features of the phone working including a2dp and fm radio, however CM doesn't. CM also has problems with HDMI mirroring due to overscan i think.
Yeah, it is very different from Windows. A driver in Windows usually work in XP, Vista and Seven while in Android, well I don't know how it works.
Related
Hi guys, I've just got a Milestone, and I think that I should 'port' the TastyFroyo ROM that I already released for the Hero and make it available for the milestone. But I do have two questions:
1. I know we have leaked 2.6.32 kernels for froyo, but I really don't like the battery life that they provide. AFAIK we have the 2.6.29 kernel sources for our device. Do CM6 based ROMs work properly with the 2.6.29 kernel? We've got all hardware working on our Heros without any substantial modifications, using the 2.6.29 kernel.
2. Can someone point me to a functional vendor tree for Milestone?
Thanks,
Radu
see http://android.doshaska.net/cm6build
the first 0.01/0.02 versions of CM6 for Milestone were based on 2.6.29 kernel and 2.1 proprietary libs (as at that time, Motorola haven't started the work on froyo yet, 2.1 was all that was available).
My repos are of course currently based on use of the 2.2 proprietary leaked libs & executables/2.6.32 kernel.
https://github.com/nadlabak
Please note that on Milestone, there are more proprietary closed source files in use than on Hero, and the biggest issue is the very complicated ril implementation, as the ril functions are partly realized in BP and partly in AP (gkisystem etc). The main issue of the 0.01/0.02 CM6 for MM based on 2.6.29 kernel were occasional BP panics...
Thanks for your answer.
This is pretty unfortunate, as the leaked 2.2 and CM6 based ROMs work decent performance-wise, but the battery life is awful. Are the guys from Motorola supposed to release an official 2.2 update soon? Because that means that the kernel sources will have to be released too, making our life easier.
Dunno.
Meant to be released end of 2010.
Still waiting.
http://forum.xda-developers.com/showthread.php?t=920177
I think battery life of last CM mod is good almost like the official 2.1
i just looked at this video http://www.youtube.com/watch?v=j4NqT6u_ODk and started looking at honeycomb. When i first looked at the froyo video the the gingerbread video i noticed how fast our devs started working on the project i was just curious if this is already being worked on or if its even been seen thanks for any replys
AFAIK, the source hasn't been released yet. Supposed to be today.
Honeycomb is for tablets only. I don't think it will work on any phone.
pfrederickjr said:
Honeycomb is for tablets only. I don't think it will work on any phone.
Click to expand...
Click to collapse
from what ive heard it will be for phones as well
It's supposed to have some smartphone support...
http://www.engadget.com/2011/01/28/android-3-0-honeycomb-emulator-has-traces-of-smartphone-support/
Dude before we start hoping and dreaming for a honeycomb update to our phone why not lets see the gingerbread one get at least one stable release. Plus like others have said honeycomb is for tablets, for now.
From what i know, google is going to release android 3.0 as honeycomb for tablets and then later on work in and refine the smartphone side and release android 3.2 as honeycomb for smartphones.
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
By then there will be no devs left
--------
Sent from my Sprint SuperHero
Pocker09 said:
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
Click to expand...
Click to collapse
Notice: Don't take this as gospel truth, I'm not a rom modder, just a kernel hacker
The hard part in getting up and running on a new Android release has very little to do with the kernel. For the most part, the Kernelspace/Userspace APIs have stayed the same. Where the problems lie are in the Kernelspace Helper Libraries and their connection with userspace. We do not have the source code for all these libraries, which is why it's not just *POOF* it works every time a new android release comes out. My 2.6.35 kernel just means that any direct kernel dependence new android adds will be provided, but it does NOT solve these intermediary layers. There is, in fact, the possibility that a new android release won't be compatible with our libraries, and we'll be proper focked.
If we have CM7 and kernels for 2.3, and leaks of 2.3 from the i9000 and are able to use gingerbread base from nexus s ( think thats what cm7 uses? i cant remember...so if its wrong just insert name of correct phone back there), why is it that we havnt seen anything other than Cyanogen mod and MIUI (which doesnt even count cause its still just the CM7 base) on the 2.3 homefront? I am by no means complaining, just kind of confused. I would think that devs would be chomping at the bit to get their hands on 2.3 for their phones and start their rom modding magic. Anyone have some insight on this other than some sort of sarcastic remark or derogatory comment? lol
we only have the aosp source. and with that why port a basic aosp rom if you can have cyanogen? also there is miui. these are probably the most requested roms on any android version on any phone. an m9 port would be nice but i think the devs that can make the aosp ports better are part of these two projects. so rather than waisting time porting aosp and doing something original and asking the cm7 guys how they fixed this or that they are helping the cm7 and miui projects. also there are still problems and limitations with cm vs samsung. cm7 cant use the camera to it's full abilities. also samsung music player supports more codecs. plus the samsung roms are easier to port allowing time to work on features and tweeks. the reason the i9000 gingerbread hasnt bee built into a captivate rom is that without kernel source the roms would not be as functional as a 2.2.1 port or even cm7 because they would have problems reorienting the sensor mapping and remapping the headset. when samsung source drops there will be much more gingerbread roms and when cm7 is official there will be spinoffs
No source, no kernel, no ROM.
Sent from my Captivate
As of now, only cyanogenmod and MIUI are the only roms I know of that use compatible bluetooth. As I am fairly new to coding and do not think I could take on the job myself, I would like to know:
What controls bluetooth? (Modem, Rom, Kernel, Bootloader etc..)
Would it be possible to extract the bluetooth properties from cyanogenmod and implant them on a gingerbread rom?
Can someone please attempt this?
I decided to update to gingerbread and left this feature behind. after almost hard bricking my phone in the process, I will not be flashing back to froyo. I am currently running Illuminance 3.0 it that has any relevence.
Thank you .
-McSpammer
As for what controls bluetooth, the kernel is essentially what interfaces with the bluetooth hardware. But the bluetooth controls are present in the ROM
Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think
hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!
Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.
So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.