I just bought an Atrix 2 today for my girlfriend. Hi Atrix people
So could someone introduce me?
My phone is the photon and I love it! One thing I've noticed from browsing this thread is that there isn't much ics support going on. Could someone tell me why? I thought the only real differences between the Atrix and Atrix 2 is the cam and a few minor features.
Anyways I'm really just interested in what's going on with ics for the Atrix 2. Anything I should know or be up to date on for cm9 or anything ics?
Sent from my I9300 using XDA
Unfortunately we don't yet have an unlocked bootloader, which is holding up development. There are a couple of devs working on a bootloader bypass from what I've read. So as soon as they have it ready and working then I think development will start kicking. I think there are a couple of devs working on an ics port as well.(fingers crossed!)
Sent from my MB865 using XDA
Thanks for the quick reply. Has anyone tried communicating with other Motorola devs? Like from the photon, razr, current moto androids. With the photon I know that its bootloader was unlocked redneck style just to get the roms rolling. We had to sacrifice 4G (wimax) data but it was worth it.
Within a month we had several choices for ics with everything working. And anything gingerbread was perfect. No need for an "issues" section in OP lol
Sent from my I9300 using XDA
Uh, yeah. We have a few ROMs. There are very few actual issues. A lot of the problems come from people not knowing what they're doing or making simple mistakes (i.e they read something wrong) the phone itself is very solid and stock works great. Just make sure you root it.
Chrisruns said:
Uh, yeah. We have a few ROMs. There are very few actual issues. A lot of the problems come from people not knowing what they're doing or making simple mistakes (i.e they read something wrong) the phone itself is very solid and stock works great. Just make sure you root it.
Click to expand...
Click to collapse
I'll be rooting in a few days just sad that ics is almost nonexistent on this phone. The other roms from what I've read seem pretty solid. But the only one that I'm interested in is still barely alpha and from the OP its not stable enough to use as a daily...
Sent from my I9300 using XDA
Well, CM9 is actually fairly stable minus the radio and sd card functionality (which can be fixed by flashing a zip). And we're just waiting on bl unlock/bypass or a leaked early Moto build of ICS for our A2 so we can get the radio working.
ICS will be around sometime in July-September. We're hoping to get it through cheesecake probably in June or late May.
The CM9 Nightly build you are talking about is VERY shaky.
Most of these GB Roms are very smooth, fast and stable. I'm currently using Lithium and I love it.
Just be patient. It's coming.
We are supposed to get am ota release of ics in q3 of this year. That's not to far down the line.
Sent from my MB865 using XDA
When it comes to Motorola don't expect a leaked ics before its released. They aren't know for that. Also what zip do I need to get calling and SMS working for cm9? I started reading through the thread but got distracted working on my cm9 build for the inspire
Sent from my I9300 using XDA
tsdeaton said:
When it comes to Motorola don't expect a leaked ics before its released. They aren't know for that. Also what zip do I need to get calling and SMS working for cm9? I started reading through the thread but got distracted working on my cm9 build for the inspire
Sent from my I9300 using XDA
Click to expand...
Click to collapse
That might be true... but we got the 2.3.6 update from cheesecake months in advance, so once we have that we should have a stable CM9 build.
tsdeaton said:
When it comes to Motorola don't expect a leaked ics before its released. They aren't know for that. Also what zip do I need to get calling and SMS working for cm9? I started reading through the thread but got distracted working on my cm9 build for the inspire
Sent from my I9300 using XDA
Click to expand...
Click to collapse
Leaked? Of course not. We just pull it straight off their development servers .
Calling/sms/data do not work in CM9 for the A2 because we need a functional ICS radio which we don't have atm. Once Moto starts pushing early builds to their servers we should be able to pull the necessary radio files and get a stable(ish) CM9!
cogeary said:
Leaked? Of course not. We just pull it straight off their development servers .
Calling/sms/data do not work in CM9 for the A2 because we need a functional ICS radio which we don't have atm. Once Moto starts pushing early builds to their servers we should be able to pull the necessary radio files and get a stable(ish) CM9!
Click to expand...
Click to collapse
My e4gt, inspire, and photon the gingerbread radios work just fine. Also the first Atrix, captivate (all of the first Gen galaxy s series) all work perfect on ics. None of which have any kind of leak of ics. What makes this phone different with its gingerbread radio?
Sent from my I9300 using XDA
tsdeaton said:
My e4gt, inspire, and photon the gingerbread radios work just fine. Also the first Atrix, captivate (all of the first Gen galaxy s series) all work perfect on ics. None of which have any kind of leak of ics. What makes this phone different with its gingerbread radio?
Sent from my I9300 using XDA
Click to expand...
Click to collapse
Been kinda wondering this myself. Even the friggin' Droid X has CM9 and this phone is so much better specs-wise we couldn't just patch in a GB radio for now?
StrizzMatik said:
Been kinda wondering this myself. Even the friggin' Droid X has CM9 and this phone is so much better specs-wise we couldn't just patch in a GB radio for now?
Click to expand...
Click to collapse
I believe its possible without the sources from Motorola. I've seen several other roms do this just fine without any kind of manufacture support
I would like to look into this but I can't seem to find a rom.
Sent from my I9300 using XDA
My infuse got ics ported a few weeks back. The dev used a lot of gingerbread firmware to get it going.
Sent from my MB865 using xda premium
tmease1 said:
My infuse got ics ported a few weeks back. The dev used a lot of gingerbread firmware to get it going.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Exactly. We don't need help from Motorola. It would just make things easier. I miss the devs from the first Atrix. Geniuses when it came to porting ics to that phone and when I talked to some of them they told me this phone should be a breeze compared to the Atrix and photon considering the tegra CPU/gpu. Which at the time before the Xoom got ics they had nothing to go off of and pretty much completely redesigned the basic arm7 chipset to trick the phones into thinking that's what it had inside
Sent from my I9300 using XDA
From what I understand cm9 for the Droid 3 boots on our phones, except the radio doesn't work (obviously) and there's some sort of issue with SD cards.
Sent from my MB865 using xda premium
Scottyfer said:
From what I understand cm9 for the Droid 3 boots on our phones, except the radio doesn't work (obviously) and there's some sort of issue with SD cards.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
The SD card problem can be fixed (through a flashable zip). This is because other phones such as the Droid X have really common radios which developers have already written ICS drivers for. The Atrix 2 has a completely different radio that really doesn't have any similarities with any other Motorola. We only have a couple of actual devs really familiar with linux/android. We're lucky enough to have the Droid 3 build work as well as it does... Just wait. Only a couple more months
farshad525hou said:
The SD card problem can be fixed (through a flashable zip). This is because other phones such as the Droid X have really common radios which developers have already written ICS drivers for. The Atrix 2 has a completely different radio that really doesn't have any similarities with any other Motorola. We only have a couple of actual devs really familiar with linux/android. We're lucky enough to have the Droid 3 build work as well as it does... Just wait. Only a couple more months
Click to expand...
Click to collapse
We don't need to wait. Other devices have done it without help from other devices and even when done so it may pull from several other devices instead of just one. Also can someone explain to how joker was able to build a cm9 build for the Atrix 4G with only cyanogenmod sources and some Google parts? Do we not have anyone on this device knowledgeable enough of Linux or cyanogen to build from source instead of from the Droid 3 or use some of droids cm9 and build the rest from source? Ics drivers have been optimized for the CPU and we don't need a ics radio or ics radio drivers for ics. The Atrix and photon still use stock gingerbread radio and radio drivers for its build with minor ics tweaks to get them running. 90% of ics builds still use gingerbread radio source with no problem. The other 10% are devices with ics leaks or releases.
Btw can someone please send me the work that's been done so far on cm9 or do I need to get it from the Droid 3 forum? Has anything been done other than changing branding to get it working or was it just "oh its cdma guess we'll wait"?
Sent from my I9300 using XDA
tsdeaton said:
We don't need to wait. Other devices have done it without help from other devices and even when done so it may pull from several other devices instead of just one. Also can someone explain to how joker was able to build a cm9 build for the Atrix 4G with only cyanogenmod sources and some Google parts? Do we not have anyone on this device knowledgeable enough of Linux or cyanogen to build from source instead of from the Droid 3 or use some of droids cm9 and build the rest from source? Ics drivers have been optimized for the CPU and we don't need a ics radio or ics radio drivers for ics. The Atrix and photon still use stock gingerbread radio and radio drivers for its build with minor ics tweaks to get them running. 90% of ics builds still use gingerbread radio source with no problem. The other 10% are devices with ics leaks or releases.
Btw can someone please send me the work that's been done so far on cm9 or do I need to get it from the Droid 3 forum? Has anything been done other than changing branding to get it working or was it just "oh its cdma guess we'll wait"?
Sent from my I9300 using XDA
Click to expand...
Click to collapse
I personally have not done anything with CM9 due to the radio driver issue. Cogeary may have done somework on it. Try PM'ing him.
Related
sorry if there is an exact thread just like this, imagine there is but i wasnt able to find it. i just got my inspire today im familiar with android phones but i know the phone just came out so im wondering if someone can walk me through this, from what i understand ill need to root, flash the cyanogen7 rom then flash a kernel that will allow me to have sound. i was wondering which kernel i would need and what is the easiest root method currently available. thanks for the help guys!!
edit: there is no modified version of this with a different kernel that will allow us to flash the inspire kernel and make sound work??
http://forum.xda-developers.com/showthread.php?t=917271
There is not a CM7 for the Inspire yet. I can't wait until there is tho, I'm not a fan of Sense... but making due for right now.
Sent from my Desire HD using XDA App
i thought you could install any desire hd rom, there is a cyanogen7 rom for the hd right here. and just flash a kernel over it to get the audio working. or am i wrong?
http://forum.xda-developers.com/showthread.php?t=917271
cyanogenmod has its own kernel that's made specifically for AOSP. A normal sense kernel will definitely not work for it. It is cool though, I flashed it for a few minutes and it's wayyyy quick with the 1.51ghz kernel they have on there, too bad we don't have source to get sound yet
Yeah just played around with it. Superfast. Love all the gingerbread stuff too. Tried fladhing those kernels the phone wont boot
bump, i see people posting modified versions of cm7 for dhd do they have different kernels that would allow the sound to work on our inspires?
thatg said:
bump, i see people posting modified versions of cm7 for dhd do they have different kernels that would allow the sound to work on our inspires?
Click to expand...
Click to collapse
Yes, yes they do.
Check out the android development section. There is a working kernel for sound on CM7 and I'm using it right now.
Sent from my Desire HD using XDA App
Ok, so it looks like the Miui ROM posted on the I9000/Vibrant forums that uses the Custom Bilboa1 CM7 Kernel works for the Captivate.
Here is the Link to Bilboa1's Kernel thread:
http://forum.xda-developers.com/showthread.php?t=979206
Link to I9000 Miui ROM Thread:
http://forum.xda-developers.com/showthread.php?t=992251
Follow the direction on the I9000 thread and substitute the CM7 captivate kernel in. Also it is noted that you have to flash the CM7 kernel right after flashing the beta 3.zip file (the zip file installs a I9000 kernel). Good luck hunting
Sent from my SGH-I897 using XDA App
there is already a miui port but from the fascinate. i would love to see a more functional; version though. just need someont to get the aosp kernel straitened out and reorient it. but that takes a lot of work.
Miui was being worked on and it was dropped. Have to ask master because he was the thread Creator for the captivate port as to why it was stopped. He is a vibrant dev.
This is my Captivate. There are many like it but this one is mine
flashman2002 said:
Miui was being worked on and it was dropped. Have to ask master because he was the thread Creator for the captivate port as to why it was stopped. He is a vibrant dev.
This is my Captivate. There are many like it but this one is mine
Click to expand...
Click to collapse
it could be something as simple as one idiot making a flaming post, and master getting pissed off and quiting, but as far as i knew darkyy and DG were in on it too, and both of those are experienced on cappy. however, darkyy has his own rom to focus on and im sad to say it but it kinda looks like DG has moved to focus on his atrix. Not that i blame him, but i know that i will miss his work
ballz0iron said:
it could be something as simple as one idiot making a flaming post, and master getting pissed off and quiting, but as far as i knew darkyy and DG were in on it too, and both of those are experienced on cappy. however, darkyy has his own rom to focus on and im sad to say it but it kinda looks like DG has moved to focus on his atrix. Not that i blame him, but i know that i will miss his work
Click to expand...
Click to collapse
You mean like this http://forum.xda-developers.com/showpost.php?p=12006864&postcount=2104
MIUI was picked up by the french developer jblanc, and then tinkered some by another dev in i9000 land. It's basically the NS port of gingerbread miui jammed together with CM7 and bilboa's kernal for CM7 one. So we do need a reoriented kernel, as the one they are using is not the CM7 since it wouldn't boot properly. Please don't spam the thread with requests for ETAs like what happened to the old Miui thread.
http://forum.xda-developers.com/showthread.php?t=992251
I have been following that thread. It looks to be much further along than the last port. This one reads like it will end up being usable, once ported here. I am running cm7 and bilboa has a captivate version of his kernel. May have to give it a run when I can afford dealing with a soft brick
CM7
Wasn't asking for ETAl, just didn't know if anyone saw. Its not the port Master put out there it was the nexus S port the uses that custom CM7 kernel. It has some of the same problems as CM7 but its miui. Seriously this is an awareness thread no flame. We have a Bilboa Kernel for Captivate, is why I'm saying why it might be possible
Sent from my SGH-I897 using XDA App
I would not pay mind to those who enter threads just to criticize without reading or knowing what they are talking about.
If this works on the captivate it would have all of the same "bugs" as cm7 as it is using all the set up including a custom kernel built from cm7 source.
Reading the thread it its farther along than the last port as wifi, data, and calls work. It is also gingerbread where as the last port was 2.2.1.
CM7
sold1erjjt said:
Wasn't asking for ETAl, just didn't know if anyone saw. Its not the port Master put out there it was the nexus S port the uses that custom CM7 kernel. It has some of the same problems as CM7 but its miui. Seriously this is an awareness thread no flame. We have a Bilboa Kernel for Captivate, is why I'm saying why it might be possible
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry, didnt mean you specifically. Just a word of the wise for all the lurkers who read these threads
Sent from my SAMSUNG-SGH-I897 using XDA App
Yeah, it would just be interested to see. I've never personally seen Miui so it could be cool.
Sent from my SGH-I897 using XDA App
hope that they can make it a stable rom then port it to captivate..
i used to use MIUI rom on my nexus one and now it's the only thing i miss... it'll be great if MIUI rom b able to run on captivate!!!
mcord11758 said:
I have been following that thread. It looks to be much further along than the last port. This one reads like it will end up being usable, once ported here. I am running cm7 and bilboa has a captivate version of his kernel. May have to give it a run when I can afford dealing with a soft brick
CM7
Click to expand...
Click to collapse
Has anyone tried using it on the Captivate with Bilboa's kernel? I might have some time later today to try.
Ok I got it to boot following the instructions from the MIUI thread in the i9000 forums:
http://forum.xda-developers.com/showthread.php?t=992251
All I did was subsitute the captivate equivalent files from CM7. I also had to flash a captivate modem from the CM7 section too. going to test it out now.
Ok FYI after you do these steps and Flash MIUI Beta 3 it will install a i9000 kernel and modem. You will have to go after the initial steps and install a captivate CM7 Kernel and Modem.
So you used bilboas captivate kernel after you flashed the beta 3 zip?
CM7
doctahjeph said:
Ok I got it to boot following the instructions from the MIUI thread in the i9000 forums:
http://forum.xda-developers.com/showthread.php?t=992251
All I did was subsitute the captivate equivalent files from CM7. I also had to flash a captivate modem from the CM7 section too. going to test it out now.
Ok FYI after you do these steps and Flash MIUI Beta 3 it will install a i9000 kernel and modem. You will have to go after the initial steps and install a captivate CM7 Kernel and Modem.
Click to expand...
Click to collapse
Hows it running? I know GPS doesnt work in addition to the stuff that doesn't work on CM7, just didn't know for the Captivate.
Sent from my SGH-I897 using XDA App
I hop i 'll come to our Captivate T_T
tmhung said:
I hop i 'll come to our Captivate T_T
Click to expand...
Click to collapse
It already work, albeit it has bugs. Try it out
Samsung said they found a issue in the gb released and pulled it from their servers, is this True? Samsung claims to have the issue fixed by Friday.
Sent from my Official Gingerbreaded Samsung Infuse.
Axiomkid said:
Samsung said they found a issue in the gb released and pulled it from their servers, is this True? Samsung claims to have the issue fixed by Friday.
Sent from my Official Gingerbreaded Samsung Infuse.
Click to expand...
Click to collapse
Lol if it is. Maybe they will fix the touchscreen issues everyone's reporting... Lol
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Who cares?
sent from my baby girls rom
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045587&fm_seq=46249
Good to know there taking a look at it.
Sent from my Official Gingerbreaded Samsung Infuse.
At least we will have something else to look forward to. Plus 17 new threads about it. Lol
Sent from my MB865 using xda premium
Maybe they realized the FW they released was KL2, and not the "official" build...
Sent from my SAMSUNG-SGH-I997 using xda premium
Perhaps if we all ask real nice they'll put it back up prerooted...
Why Bother
Why bother with this total fail of an upgrade when there are so many better custom ROM's to choose from right here on xda?
I'm on Infused v2.2.3 and really like it but considering making the move to ZEUS soon.
I just can't see any reason to make a giant leap backward with the AT&T GB upgrade. It's just too little too late. YMMV though.
Maybe Samsung decided to use Zeus?
(Actually the GB release is running really well for myself. I haven't even rebooted yet since install last week.)
Sent from my SAMSUNG-SGH-I997 using Tapatalk
andrawer said:
Maybe Samsung decided to use Zeus?
(Actually the GB release is running really well for myself. I haven't even rebooted yet since install last week.)
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
I hope so but it wont be true!
Im glad they pulled the buggy thing...
sent from my baby girls rom
bass_me said:
Why bother with this total fail of an upgrade when there are so many better custom ROM's to choose from right here on xda?
I'm on Infused v2.2.3 and really like it but considering making the move to ZEUS soon.
I just can't see any reason to make a giant leap backward with the AT&T GB upgrade. It's just too little too late. YMMV though.
Click to expand...
Click to collapse
Yeah who likes a 100% working phone anyway, right?
meh.
now I know why there are no sources yet. and yeah the update is important if not just for sorcery code. never mind Samsung and att having respect for the customers....
think of how much better the roms can be if we don't have to mix libs from different leaks to fix video recording or playback and workarounds for the sdcard and wifi. and if they actually have HDMI. then we could swap kernels around without considering switching vold.fstab. yeah I hope the update is fixed soon so the code can be released finally.
someone is gonna have to get the update files and decrypt them to get a stock kernel though. (to extract initramfs and the root process will require a kernel to revert to until custom kernels are made.)
If you consider hdmi 100 percent, then I guess im running a 99 percent working rom......yea.....im good with that
sent from my baby girls rom
hey I'm using Zeus myself. but I use the kl2 kernel on it and it would be nice if you didn't need to change vold.fstab back to stock to do so. I just want source code for new kenrels that could be maintained as all the old kernels were developed by people who are no longer here.
Dani897 said:
hey I'm using Zeus myself. but I use the kl2 kernel on it and it would be nice if you didn't need to change vold.fstab back to stock to do so. I just want source code for new kenrels that could be maintained as all the old kernels were developed by people who are no longer here.
Click to expand...
Click to collapse
Dani, you are running zeus with the stock kernel?
I remembered dman said trying to run stock kernel in zeus will boot loop.
There were scripts not supported by stock kernel.
To make it run, just disable lagfix?
Just curious...
qkster said:
Dani, you are running zeus with the stock kernel?
I remembered dman said trying to run stock kernel in zeus will boot loop.
There were scripts not supported by stock kernel.
To make it run, just disable lagfix?
Just curious...
Click to expand...
Click to collapse
the init.d scripts wont run. that's true. but you should be able to change kernels after a reboot. its running for me. I didn't look at the scripts to see what other things I'm missing but the rom runs fine without the tweaks and lagfix.
Dani897 said:
the init.d scripts wont run. that's true. but you should be able to change kernels after a reboot. its running for me. I didn't look at the scripts to see what other things I'm missing but the rom runs fine without the tweaks and lagfix.
Click to expand...
Click to collapse
What would the point of running zeus without the tweaks?
I'm not sure that is why I ask. Isn't kinda like running stock uckl2?
qkster said:
What would the point of running zeus without the tweaks?
I'm not sure that is why I ask. Isn't kinda like running stock uckl2?
Click to expand...
Click to collapse
well I ran it with infuseion a few days, but I get the themes, the rom is deodexed, and when ever I deodex something it seems to run weird either slow or choppy. Zeus doesn't. I dunno what dman uses to deodex but it works better than what I have used.
I've tried a lot of ways the only from I got to work on my G2X is Genesis from Mr.Apocalypse and Hellfire before 1.6 and I don't know what I'm doing wrong. I do the regular wipe data/cache/Davilk and its a no go. I even used some new Nuliffier <-- lol I know that's not spelled right but I got that the single wipe and then tried to flash it and its a no go sooo can someone help me out and tell me if I'm missing something ??????
Sent from my LG-P999 using XDA
The only rom* I got to work
First line
Sent from my LG-P999 using XDA
Check rom integrity using md5? Might be bad download.
Sent from my LG-P999 using XDA
There's been a bug with 4.0.4 roms that requires you to flash it twice, one after another, nothing in between. Next time you try a rom like that, take note of how long it takes to install. If it only took a few seconds, it wasn't properly flashed. Flash again right away and you should notice it taking longer to install. Then flash your gapps and/or kernel if ya need it and reboot. Should be good.
Caliyork said:
There's been a bug with 4.0.4 roms that requires you to flash it twice, one after another, nothing in between. Next time you try a rom like that, take note of how long it takes to install. If it only took a few seconds, it wasn't properly flashed. Flash again right away and you should notice it taking longer to install. Then flash your gapps and/or kernel if ya need it and reboot. Should be good.
Click to expand...
Click to collapse
It doesn't effect the EB AOSP ROM. It's 4.0.3.
@Caliyork yeah your right I really ain't notice that but I'll be looking at that, have you been successful putting kernels on because I have the same problem with that ?? I mean I got one to go thru but when it fully booted up the touch didn't work and I couldn't unlock it so it wasn't functional. I had to restore and run a rom without a kernel.
Sent from my LG-P999 using XDA
are you flashing the proper kernel, sounds like you grabbed a kernel for a different phone, I'm guessing something from the Morfic collection?
Hmm could be, but I was in the g2x forum and I browsed for kernels and I got fauxs 123 kernel, Trinity, and Harshs and none of them seemed to have worked, I used Mr.Apocalypse and none of them went thru. Cud u give me links to see if any were the right ones ? Do you use OC/UV ?
Sent from my LG-P999 using XDA
All those that are directly in the forum are correct except maybe harsh his might've been a p990 kernel. Some phones don't play well with some kernels.
Sent from my LG-P999 using xda premium
mt3g said:
Some phones don't play well with some kernels.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Unfortunately, that bit is especially true for this phone. Bad quality control.
Caliyork said:
Unfortunately, that bit is especially true for this phone. Bad quality control.
Click to expand...
Click to collapse
Yeah I guess mines is too I think :/ do you know if it possible to fix that problem ???
Sent from my LG-P999 using XDA
I'm not sure referring to quality control is accurate, but phones do have bad batches or manufacturing tolerances and what not. Can't always get the cream of the crop.
That's practically the one reason why I chose the G2x instead of the HTC MyTouch 4G lol. Bad EMMC happens to die on you and you've got yourself an expensive brick.
Have you tried any other ROM other than ICS roms? Trying to figure out if the problem is restricted to those only. Might help.
desynch- said:
I'm not sure referring to quality control is accurate, but phones do have bad batches or manufacturing tolerances and what not. Can't always get the cream of the crop.
That's practically the one reason why I chose the G2x instead of the HTC MyTouch 4G lol. Bad EMMC happens to die on you and you've got yourself an expensive brick.
Have you tried any other ROM other than ICS roms? Trying to figure out if the problem is restricted to those only. Might help.
Click to expand...
Click to collapse
Haha yeah I've heard that before but I'm not sure if I have a bad batch because I got Genesis, AOKP, and Hellfire (ICS roms) to work fine but could not get any custom kernels that supported OC/UV to work on them. Uhh I actually been using nothing but ICS roms I never tried and other roms that supported GB just cuz I wanted to be updated. Are you on any other Roms or you using a ICS rom ?
Sent from my LG-P999 using XDA
I've used a lot of different ROMs, and they all work fine. But I'm on the stock LG 2.3.4 that was released lately, and that's been running really super.
Flashing ICS doesn't necessarily mean that you're up to date when a lot of things don't work. I've used AOKP, EB's AOSP, HFS and Owain's. I have multiple problems with data dropping, APN's disappearing when entering Airplane mode or mass storage just completely does not work. Not to mention, NO NETFLIX!
As far as kernel issues, make sure you're installing the appropriate ones for the P999 and make sure they're ICS specific and not for the GB kernels.
Edit: If I remember, EB's AOSP uses a modified Faux Kernel that supports OC right off the bat, so there's no need to flash a different kernel.
That's true never thought of it like that where can I get the rom you are using ???? And yeah I tried to get EB AOSP to work but it wont for me -_____- lol
Sent from my LG-P999 using XDA
I'm using a stock rom. If you feel adventurous then flash the new V21y baseband (50% likely to brick your phone hard). If not, I would just stick with GB. My all time favorite is WeaponG2x.
Sent from my LG-P999 using XDA
Okay this question has been bugging me for a while now. Everyone is waiting on RC aka Ricardo AKA..... on getting the ported p990 to then be ported over to p999. We have many fine Developers here like Eagleblood , Rafase282, tonyp, Kashamalaga and many MIA ones that may or may not return like nycelitemaster, owain94, x0xhellx0x and my favorite Mr. Apocalypse.
My question is simple and would love one of these guys to answer it if possible.
Why are we waiting for RC to port it over when anyone of you guy have done it before. Am I wrong when saying that most of you have ported P990 over to P999 before? I respect everyone I have named. You have brought new life to my G2X. JUst wondering why we wait for RC, like he is the only one who can do this. Please if I am missing something let me know. thanks
I believe they are waiting for a more stable release of CM10 for the P990 before they bother to port it over for the P999. They should have many of the same bugs that need to be worked out. There is no need to do it twice.
I felt the same thing. Can some of the Developers list above or others I missed confirm this? Maybe this can stop or slow down the rants. The only reason I feel it may not be a difficult thing to do it because of this guys post...
Lezo OS
Hello everyone.
This is a port of the P990 Lezo OS a CM based rom. I am not a developer, just someone who was lucky enough to have this work It's just another piece of a so called "Crack Flashing Series". There are plenty of roms provided to our community, and this also brings people with different likes and dislikes. I aim only to share some of the other roms out there with the community. Maybe you want to try something out inbetween updates from your favorite rom, well, try this.
None of this would out be possible without the help of guides from dubntz and blindndumb. If you like any of the ports thank them as well.
This guy has done it before with other p990 Roms with little experience.
When we were on Cm7 we were able to port roms by using the already created cm7 base. The problem now is we don't even have a P999 cm10 base to port with, which is why we're waiting on RC since he needs to create the base.
Sent from my Nexus 7 using xda app-developers app
That seems to make sense. thanks. Can any Developers confirm this. Is RC truely the only one? Or is he just the only one with the spare time to help us? thanks
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
nycelitemaster said:
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Don't we already have the drivers and Kernal? They are part of p990 and then don't they just need to port it over.
More then likely it would be easier to port tonyps experimental ics. We can compile a kernel for it and have the drivers. We just need the experience lol
Sent from my LG-P999 using Tapatalk
Here's what I think based off what I have read:
I think first and foremost, our Dev's who all own P990's are working in wrapping their wits around the sources for their phones, us and our G2x's are the red-headed step-children (figuratively) of LG. The phone has potential, but gets little attention. I also believe that the Devs are waiting for a kernel to be built with the new sources, which those sources have to be altered to work with the G2x, as they did for the O2x. Something which I don't think our Devs want to do. I may be wrong, but I would think that Bene, or Dj V. have the know-how to do it. Again, we're back to the fact that they're (understandably) going to do work for their phones first.
Sent from my LG-P999 using xda premium
As far as I know, the kernel sources for su660 has some issues compiling kernel for p999. It can be one of the reason why we don't have cm10 yet. I believe the developers are working on it. Also the kernel source comes with locked boot loader. So its essential to port old boot loader which is not locked to the new kernel. This might also be preventing other developers from building kernel. If I have time, I will try to see if I can compile the kernel with old boot loader or not this weekend. I am a full time science student. I think to port the p990 ROM we just need a p999 kernel and some p999 specific drivers such as ril drivers. I do hope the cm10 comes asap though. I might be wrong.
While I do not consider myself a developer, I thank you for listing me there. I personally do not have the time and knowledge required to build a cm10 base for the p999 based off the p990. The kernel and rom needs to be change to work for our phones. Also as it was said already, it would make no sense to make an early port, based on RC work which will most likely piss him off if we start kanging and using his work while it is not even stable enough to build for our phone. So I would say that out of respect and time/knowledge required most people able to make the port would either wait for help debugging the p990 version so it can be ported to other devices without the same issues to be fixed twice or more times.
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
guitarist5122 said:
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
who wants a kernel?
I've posted a kernel built from the cm10 lge-kernel-star repo in the dev thread, maybe somebody feels like taking it for a spin.
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
rosevilletoyota said:
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
Click to expand...
Click to collapse
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Rafase282 said:
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
Click to expand...
Click to collapse
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
bakedpatato said:
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
Click to expand...
Click to collapse
For my name the division is Rafa-sé It is just that in many places I cant use the é. SO I left it as an e and use use é for the phonetic part.
Morphine! :highfive:
Волк said:
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Is the lge_star_ril something LG was supposed to have included? From my (limited) kernel knowledge, that bit seems pretty vital to having a properly working phone.
Without it, how hard is it going to be to get working calls/data/gps without having serious battery and quality issues as you've alluded to?
It was missing from the old sources, and yea, like I said alot of the deal-breaking issues were due to that, the ICS (which I think was already hacked) was hacked into JB.
Sent from my LG-P999 using xda premium