Milestone + Cyanogenmod is compatible with ADK? - Motorola Droid and Milestone Q&A, Help & Troublesh

I have the latest Cyanongemod (Android 2.3.4) and i wish to know if it is compatible with Android Open Accessory Development Kit (ADK).
ADK is compatible only with Android 2.3.4 and 3.1 but im not sure if Cyanomgemod include the required libraries.

Hi!
I´ve been searching this for a while, and yes, cyanogenmod (at least nightly builds) support - you might have trouble getting other customs roms.
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Push nexus files from here:
forum.cyanogenmod.com/topic/26339-usb-accessory-mode-is-adk-supported-in-cm-7/
And upload demokit via eclipse.
Regards
Robson

robsondantas said:
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Click to expand...
Click to collapse
There is one problem - you cannot flash custom kernel on Milestone that is not signed by Motorola (locked bootloader). And the latest kernel that we have is 2.6.32.9, so that will not work.
If you want custom kernel (but without radio) you can try to have a fun with 2nd boot - http://droid-developers.org/wiki/2ndboot

Related

[PATCH] rmk kernel v2 for CM6

Details on my kernel were buried in the CM6 thread but I think it makes sense to have a dedicated thread:
Version 2 of my kernel build is available for CM6, which includes koush's camera fixes. I take absolutely no credit for any of the code. I'm merely building a kernel with a combination of patches which are known to work.
Details:
- Latest CM6 incredible kernel from Koush (taken from git repository)
- HTC wifi driver with wireless N enabled (this is the key difference)
- No overclock or undervolt.
- Uses Koush's (with Hydra's modifications) kernel installer scripts/tools.
Download:
http://www.fourty.net/ftp/public/android/kernel-rmk-cm6-v2.zip
<Insert usual disclaimer about not taking responsibility here>
good idea to make a thread for this, much easier to follow
updating the mash-up thread with a link...
curious though, alot of us have been getting lock up issues still related to the wifi bug i think (v2 with latest nightly)
ive had wifi off for three days now and havent had a lock up since
any ideas?
I am running this kernel with the Test 8 CM ROM. I have found that I am unable to start the WiFi Radio when attempting to use Wireless Tether. The WiFi Tether reports an issue starting the radio in its log.
I am using the newest release of WiFi tether that support AP mode, as opposed to Ad-Hoc.
Any thoughts?
Working well on the latest CM6 nightlies
rmk, you should incorporate the 2.2.1 gmail into the kernel too.
Yeah, why doesn't your kernel have gmail? You're really slacking rmk.
tats_06 said:
rmk, you should incorporate the 2.2.1 gmail into the kernel too.
Click to expand...
Click to collapse
joke?
if anything the gmail could be included in the mash up
i would personally not like to see it included with a kernel, thats ridiculous
I was just thinking out loud. No need to be rude. Have a nice day.
Still really new to this whole rooting business. Do I put this on the root of my SD, boot into recovery and flash the zip?
trombone dixie said:
Still really new to this whole rooting business. Do I put this on the root of my SD, boot into recovery and flash the zip?
Click to expand...
Click to collapse
just throw it anywhere on your sd card, then boot to recovery and choose to flash a zip from the sd card, navigate to it and then flash it (can be done from rom manager too)
Works flawlessly!
Sent from my Dinc using XDA App
each time i flash the new CM6 nightly do i have to reflash this kernel?
trombone dixie said:
each time i flash the new CM6 nightly do i have to reflash this kernel?
Click to expand...
Click to collapse
yea, because the nightly will have the standard cm kernel, not with rmk40's patch
theres also a mash up that i put together than includes this kernel as well as another small patch to mount /emmc on boot
ive been keeping up pretty good with nightly roms
invisiblek said:
theres also a mash up that i put together than includes this kernel as well as another small patch to mount /emmc on boot
ive been keeping up pretty good with nightly roms
Click to expand...
Click to collapse
which one is it?
CM6 Nightly 08102010-005435 mash-up (latest):
http://www.mediafire.com/?np50kfp38mfw62g
md5sum: 85ff8c7216fd94198950e6dc4f550f27
CM6 Nightly 08072010-004339 mash-up:
http://www.mediafire.com/?i9aykqnqx34oukd
md5sum: f0e06224355e480f4146068a6e8e47b7
CM6 Nightly 08032010-002702 mash-up:
http://www.mediafire.com/?c97mm8yf3mt58pf
trombone dixie said:
which one is it?
Click to expand...
Click to collapse
the build numbers correspond to the nightly build datestamps
the one called "latest" is gong to be the latest nightly build that ive mashed up. if there are any changes in tonights build, ill do another one
invisiblek said:
the build numbers correspond to the nightly build datestamps
the one called "latest" is gong to be the latest nightly build that ive mashed up. if there are any changes in tonights build, ill do another one
Click to expand...
Click to collapse
does the latest one have the rmk kernel in it?
trombone dixie said:
does the latest one have the rmk kernel in it?
Click to expand...
Click to collapse
they all do, thats the point of the mash up
cool beans. i was curious because i downloaded the latest one last night and my camera stopped working.
Hmmm...
Well, I flashed the updated kernal and now wifi tether won't work at all. I tried the 2.2 tether built in, it gives me an error, and I tried wireless tether, and it tells me that it failed to start the wifi interface.
Also, I'm not sure if this is just me for some reason, but whenever I use usb tether or wifi tether, my data connectivity fails after 10-15 minutes and I have to restart the phone. I'm running CM6-Test 8 and I have the latest baseband as well. Any thoughts?
Rmk or anyone, do u have link to Koush's CM6 test 8 kernel that ROM comes with? I would rather not full flash to just revert back to stock kernel ...thanks.

[Q] Stock Android

Hi guys,
I am really interested in figuring out the steps that should be followed in order to compile a stock android rom for i9000.
I find the phone amazing but really hate touchwiz and all samsung's applications.
Thanks in advance
compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje
JJEgan said:
compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje
Click to expand...
Click to collapse
I meant vanilla android, i am aware of resources where you can find stock samsung compilations (namely samfirmware -sorry but as a new user i cannot post links- although there's also an updated list in a thread somewhere in xda forums) and i also follow some of the custom made roms (currently i'm using Darky's v9.3).
I would like to get to know how to get my custom rom compiled and packged so i9000 can load it, the reason: i really dislike samsungs additions to android (touchwiz) and i haven't found a custom rom similar to what i am seeking.
For the first steps i suppose i should grab the code from aosp but i just don't know if i need some drivers (i suspect i do), and if so... where can i get these?
Then... once all that stuff is compiled, what are the steps that should be followed to make the compiled image flasheable?
Thanks.
I really thought that the custom ROMS in the dev section could be built as custom as you like via the kitchen. First take the bare Android 2.2.1 JPY/JS5 system and add the Gingerbread launcher as well as the market then off you go. Can't get anymore vanilla than that ?

[ROM][STOCK]SHW-M380W Korean Tab 10.1

As I make progress towards making us an overclocked kernel I will keep m380w users informed in this thread. Wish me luck!
June 16, 2012 Had to post an updated torrent file.
May 01, 2012 New Firmware Released (NOT ICS)
Attached is a torrent file for FD19
Dec. 08, 2011 Development Halted
Here's the latest. The source code that Samsung makes available seems to have issues. I have tried and tried again to reproduce a stock kernel that will boot with the initramfs. However, the defconfig provided does not match the .config extracted from config.gz. There are some big differences between the two. The defconfig supplied with the source code defines the board as p4 yet the .config from the kernel defines it as p4wifi. So naturally I have tried both and I have tried many, many other things. All for not.
I contacted FOSS and the response was to the tune of, "We sent your message to the dev. team. If they respond, we'll respond. Until then, just wait."
With that said, I see no reason to muck about with trying to make an overclocked kernel, when there is no indication that I have valid source code.
Nov. 24, 2011
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
SHW-M380W.EK10.7z
Rooting directions and files I have tested and do work with this release can be found here on XDA
Nov. 26, 2011
I made some progress and have extracted the initramfs from the EK10 kernel using koush's AnyKernel. See attachments. One step closer to an overclocked kernel.
Pershoot has graciously offered his time and resources and built a recovery cwm_5.0.2.7_kor for the m380w. Which now displays correctly on this device.
He included the following notes:
UMS is not implemented (so the option will not work).
no radio/extra partitions will be available.
Click to expand...
Click to collapse
koe1974 said:
As there are only a few of us in here and nobody in Korea seems to be developing this model, I took it upon myself to retain this ROM from my most recent bout with Kies.
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
HOME_SHW-M380W.EK10.1207_CL583812_REV00_user_ship.tar.md5
Rooting directions and files I have tested and do work with this release can be found here on XDA
I hope to offer an overclocked kernel in the near future but we'll have to see.
Click to expand...
Click to collapse
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
BeeGee_Tokyo said:
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
Click to expand...
Click to collapse
It is Honeycomb 3.2. The shw-m380w is a wifi model.
Sent from my SHW-M380W using xda premium
One of the most noticeable difference is the integrated digital dmb tv and radio receiver and antenna. With no change in the look and dimensions. It comes wifi with or without 3g.
koe1974 said:
Nov. 26, 2011
Pershoot has graciously offered his time and resources and built recovery-cwm_5.0.2.7-sam-tab-10.1_kor_odin.tar.zip
He included the following notes:
Click to expand...
Click to collapse
refreshed:
http://droidbasement.com/db-blog/?p=2439
pershoot said:
refreshed:
http://droidbasement.com/db-blog/?p=2439
Click to expand...
Click to collapse
Excellent! Just completed a backup and all worked as expected.
Thanks
Sent from my SHW-M380W using xda premium
Thank you so much pershoot and Koe1974. Now, CWM can operate normally with my device. Actually, my device model is shw-m380s with 3g and I would like to ask you is it able to upgrade by CWM with the custom roms of P7500 (as overcome rom) and the overclock kernel?
Hi pershoot. I've just made a backup for my kor tab (model shw-m380s). Please help me to check the boot.img attached and let me know my device is able to apply your kernel or not. Thank you in advance.
Your device is not compatible with my kernel.
pershoot said:
Your device is not compatible with my kernel.
Click to expand...
Click to collapse
Thank for your reply Pershoot. Yesterday, I tried to patch your kernel and my tab couldn't boot, so I had to back to its stock kernel. I also upgraded my tab to Overcome Rom with stock kernel and it works fine exclude one issue is the brightness level couldn't adjust anymore. Because I am not good at hex and linux coding, so I appreciate if you or other developers could help me (and people own this device) to fix my stock kernel to make it is suitable with CWM roms and able to be overclocked. Thanks alot in advance.
Just to share some of my experience, I have an M380W model, I installed pershoot's CWM-based recovery, backed up everything, and installed Galaxy Task 6.2 ROM for a try (and 6.3 update). The screen keeps scrolling, but this is solved by restoring boot.img within the recovery.
I then have the same symptom as phuonglev, the screen brightness level can't be adjusted (set to medium and looks so), and I sometimes have orientation problems.
Could all this be resolved with your specific kernel koe1974 ?
I don't imagine it will. All I am planning at this point is to enable overclocking. It will essentially be a stock kernel. It sounds as if it is something in the rom causing the problem. As much as we would like to think the korean models are the same, from past experience with a galaxy s 'shw-m110s vs gt-i9000', the roms are just not interchangable. It always seems that there is 'something' that does not work as it should.
Sent from my SHW-M380W using xda premium
How is your progress Koe? I'm waiting for the good new from you.
Awesome, can't wait to see some progress.
I thought I was the only one with problems trying to use tasks rom.
Just FYI for any other M380W owners out there, you can supercharge your tab. Made a big difference for me.
*Edit
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
aigoya said:
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
Click to expand...
Click to collapse
If you are on EK10 then it is probably the update for Polaris Office. However, if you are not running the stock rom, your device may be reporting that is an p7500 or p7510 which I think comes with QuickOffice. So it might be confused.
Sent from my SHW-M380W using xda premium
could you upload the rom to other source please?
samoelito said:
could you upload the rom to other source please?
Click to expand...
Click to collapse
This is the best I can do ( http://www.wupload.com/file/2662167342/SHW-M380W.EK10.7z ). If you prefer bit torrent, let me know.
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
[email protected] said:
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
Click to expand...
Click to collapse
To root just follow the instructions and you will be fine.
ek10.7z is just the stock rom for if you choose to revert from back. currently, there doesn't seem to be much development going on for the m380w so I uploaded it for those brave enought to try roms built for other 10.1 models. I always delete tons of stock apps so it's helpful to have a stock rom to get back it i need to.
is flashing ROMS still the same?
Just using Odin and put the file into the PDA slot?

[Q]Things to know before installing a Custom ROM

Hi,
I have been looking through various custom roms for optimus 2x and intend to install one very soon. Before installing i have some questions
1. What is baseband? How do i know which one to use?
2. What is the best/recommended steps to install a custom rom? I know what you have to do before installing a custom rom, what i meant is the order in which you should install custom rom, kernel, some performance packs and baseband, etc.
3. What do you look for in a rom before deciding to install one?
And finally, how can i help the development community?
1. baseband is the software for radio in the phone. You dont have to flash new, you can keep on you baseband from original rom, its not flashed automatically when you flash custom roms by clockworkmod. you only need to download lg getril for example from market and install matching rill to your baseband.
2.
step1: root phone
step2: instal clockworkmod
step3: download zip file with rom to your sdcard
step3: power off phone, then hold volume down + pover on(first volume button) until the clockworkmod starts
step4: backup phone in CWM
step5: every thread with custom rom have the manual how to flash in cwm, its easy.
You can read about it on modaco optimus 2x forum. Lets google it.
There are basically two types of rom for O2X, the one is based on the modified stock rom. the second one is cyanogenmod based rom, i like the cyanogenmod.
You should use matching kernel to type of rom(cyanogenomd, based on ofiicial), kernel is closer to handle hardware, i can imagine it like kernel is between hardware and ROM, ROM is between kernel and user.
3. you should try some ROMs and decide what you like.
EDIT
4. sorry for my bad english.
Your baseband is visible in Settings/About Phone. Try first to flash without changing it. Get the matching Ril with GetRil or LG Ril version in market.
To root you can use latest Superoneclick (see thread in dev section, it seems now to work with GB a well) or nvflash method (see rooting for dummies in dev section).
In the first case you instal cwm with ROM Manager from market, or your can flash it directly using Rusty!'s build (see stickies thread in dev section).
Nothing else to add to the above post. Two families of ROM as said, all coming from stock LG are based on 20L/M/O original ROM. Others are either cyanogen (see in Kang thread, as nightlies build bot is out of order for now) direct, or cyanogen derived (Miui).
Read carefully first posts in each ROM thread, and be sure to have always a back up.
Thanks tomsi91 and Striatum.
@Striatum_bdr
Your sig says : O2X Topogigi SP3 ROM upgraded to 20M - Horse Power 2x Kernel RC11 + Swap/Power Pack 9 lite - Ext4 - BB & RIL 0725 (V20L)
I wanted to know the order in which you installed it. Did you install the kernel first then added the rom or did you flashed the rom first then flashed kernel and the others in the order written in your sig
TIA
A bit of topic but anyways, my BB and RIL don't match so
1. If I match them what improvement would I have?
2. Do I really need to do it even if I am not having issues with call quality?
scrm3r said:
Thanks tomsi91 and Striatum.
@Striatum_bdr
Your sig says : O2X Topogigi SP3 ROM upgraded to 20M - Horse Power 2x Kernel RC11 + Swap/Power Pack 9 lite - Ext4 - BB & RIL 0725 (V20L)
I wanted to know the order in which you installed it. Did you install the kernel first then added the rom or did you flashed the rom first then flashed kernel and the others in the order written in your sig
TIA
Click to expand...
Click to collapse
No reason to flash kernel first it will be overwritten by ROM.
ROMs are always coming with a kernel!
First: ROM. A good thing is to boot then, and follow the First Run Configuration Wizard.
Second: Flash Kernel of your choice.
Third Power Pack if you want, mandatory with SPica's kernels to have all features.
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
C0D3N1N3R said:
A bit of topic but anyways, my BB and RIL don't match so
1. If I match them what improvement would I have?
2. Do I really need to do it even if I am not having issues with call quality?
Click to expand...
Click to collapse
No Problem = No change.
Golden Rule.
just to add.. don't forget to back up your messages/app data/whatnot with titanium backup or whatever
also note that a lot of the LG system apps will obviously be gone when going to CM7 for eg:
the camera for one thing has it's pros and cons. a lot of people seem to prefer the stock camera
the music player doesn't have a cool landscape mode
fm radio is **** with only 6 presets
sound recorder doesn't let you change quality
no built in memo pad (but you can always get one from the market anyway)
and the LG widgets (i like their weather and calendar widget)
"backup and restore" app which was quite useful (i believe it's made by Sprite).. but no worries since there's titanium anyway
although perhaps these system apps are backup-able as an apk in titanium?
Stock LG apps can effectively be backed up as apk, but they can't be run on CyanogenMod, so no interest.
I bought 2x 3 days ago. The lg gingerbread is fine. But not that impressive. I want to root it but the problem is rooting, voids your warranty. Is there is any way so that you can backup the android os given default (by lg), so that you can install it later to claim ur warranty later on. And is there is anything else? to do please correct me.
1. Backup your phone content(contacts, msgs etc)
2. Backup your factory installed OS (I don't know. how to do that).
3. Root your phone by some rooting software(superoneclick,etc).
4. Flash new cm7 rom or any custom mod.
5. Done? please correct me if i'm wrong.
Sent from my LG-P990 using XDA App
nzbrockstar said:
I bought 2x 3 days ago. The lg gingerbread is fine. But not that impressive. I want to root it but the problem is rooting, voids your warranty. Is there is any way so that you can backup the android os given default (by lg), so that you can install it later to claim ur warranty later on. And is there is anything else? to do please correct me.
1. Backup your phone content(contacts, msgs etc)
2. Backup your factory installed OS (I don't know. how to do that).
3. Root your phone by some rooting software(superoneclick,etc).
4. Flash new cm7 rom or any custom mod.
5. Done? please correct me if i'm wrong.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
There are many stock ROMs over in the dev section and there are even guides to show how to restore it. So just use the search button and read
About rooting there is one guide I would recommend you using it because it really explains everything
http://forum.xda-developers.com/showthread.php?t=1327599
Hope this helped
Sent from my LG-Stone from the Prehistory...
Nahh... Just kidding!
CM 7.2 Koboltzz KANG
IronKernel 32MB
Striatum_bdr said:
Stock LG apps can effectively be backed up as apk, but they can't be run on CyanogenMod, so no interest.
Click to expand...
Click to collapse
hmmm.. ****
Thanks for the reply mate... i would like to know if i flash cm7 in it , then the baseband and kernel will be updated automatically?
Sent from my LG-P990 using XDA App
Baseband can't be changed with cwm. Only smartflash. And a custom ROM always come with a kernel or it can't boot...
Better to go back to ext3, in case the new ROM doesn't format. And to be sure no residual file will be left and not overwritten, that could cause troubles.
Striatum_bdr said:
Baseband can't be changed with cwm. Only smartflash. And a custom ROM always come with a kernel or it can't boot...
Click to expand...
Click to collapse
Is there a newer basaband than 1035.21_20110725? This version is the same in all latest stock ROMS (V10D, V20L, V20M). Flashing the V20M (with smartflash) will have a different baseband although it will say 1035.21_20110725? I installed the leaked V20o but I have problems with signal loss after some hours in stand-by.
spyrosk said:
Is there a newer basaband than 1035.21_20110725? This version is the same in all latest stock ROMS (V10D, V20L, V20M). Flashing the V20M (with smartflash) will have a different baseband although it will say 1035.21_20110725? I installed the leaked V20o but I have problems with signal loss after some hours in stand-by.
Click to expand...
Click to collapse
It's one of numerous LG inconsistencies... Different BB with same number.
It seems in fact they are not the same. Try different Rils with GetRil, the 20o one but also the 20l etc...
Striatum_bdr said:
It's one of numerous LG inconsistencies... Different BB with same number.
It seems in fact they are not the same. Try different Rils with GetRil, the 20o one but also the 20l etc...
Click to expand...
Click to collapse
I did try different RIL when I had the V20o. I changed the RIL V20o Europe to V20L Italia which I had with V20M update which I did through LG official update. Do you think flashing V20M with smartflash and then installing the V20o will fix the problem?
Thanks

[Project] Build LG s sourcecode [GB]

Hey guys, I wanna start a new "little" project and hope for some help from the one or the other.
I just realized, that noone until now really compiled a stock ROM for our device.
That means, we can't get a fully customized ROM. I mean Zeus ROM is close to it, but it's pretty restriced, to the typical "tweaks" like kernel, theming and so on.
So I thought of trying to compile the sourcecode. It's still compiling, but if I already look at the build.prop, it looks like it's not building for our device, although I followed LG's advices that are:
Code:
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 2.3.4 gingerbread) from http://android.googlesource.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of P970_BDop_GingerBread_v20s.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
$ ./build/envsetup.sh
$ make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
So far it looks and is pretty simple. But like I said, with the commands mentioned, I think it doesnt build for our device.
Had to bypass some errors, since I am using a more recent toolchains as LG seems to have used, but since goolge is my best friend, he told me what to do
Now how can we get this sourcecode compiled?
Do I have to start like rmcc did? And add these files/add the content he added?
https://github.com/CyanogenMod/andr...mmit/04b8b02f13c62239dad2884530ad07b9fe3ebd60
Dont wanna mess up my building environment and start over again, that's why I am asking.
When typing lunch, it only shows:
1. Emulator
2. crespo (I think)
3. some HTC device
4. one more
at least I cant pick p970.
Would be nice, if we could get that done, since it would probably also work for our hopefully soon coming ICS!
Then we could get a VEEERY good ROM for our already lil bit old device
Hope we can make it and I am sure we can
All recommendations are welcome.
About that, you need to setup the proprietary binaries for LGE to be able to setup P970 for lunch. Beside that, the prebuilt must be of the similar version.
Sent from my LG-P970 using Tapatalk 2
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Huexxx said:
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Click to expand...
Click to collapse
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
It would be CM7...
LG's ROM source code is close to nothing... only mods to non-proprietary stuff... there is NOTHING more. so CM7 sources + LG's source = CM7 source... CM7 has used LG's stuff for its project...
The way IMHO is:
- Take latest Gingerbread AOSP sources.
- Take a existent target (as Crespo) and duplicate all the needed stuff with a different name... as P970.
- Once you can build P970 (a Crespo ROM will be generated), modify all the stuff with vendor blobs from CM7 and proprietary files from LG's GB.
- A way to understand what you are doing is to take AOSP complete code... CM7 complete code, and compare the way both sources compile the same target, (Crespo...) to obtain the differences... Once you understand how change from AOSP to CM7 for Crespo, you will try to make the opposite from CM7 to AOSP for P970...
Regards.
have good luck
:fingers-crossed:
Good luck for your project...:good:

Categories

Resources