Root [Virgin Mobile/Sprint] ROM Creation Question

[moore.bryan]

So, a few questions for the good of the cause; perhaps some rhetorical, perhaps not:

1. Now that we have CWM Recovery for the Optimus F3 and two excellent ROMs--namely Psycho Billy Cyanogen Flavored Rom and Solar ROM--the proof-of-concept time is done; shouldn't we be seeing dozens of other ROMs?
2. If other ROMs can be put on the F3, Y U NO Cyanogenmod?
3. If one were interested in learning how to build/port a ROM to the F3, where would you have them start? Move next?

Thank you to a great community!

 

[chucksaysblah]

So, a few questions for the good of the cause; perhaps some rhetorical, perhaps not:

1. Now that we have CWM Recovery for the Optimus F3 and two excellent ROMs--namely Psycho Billy Cyanogen Flavored Rom and Solar ROM--the proof-of-concept time is done; shouldn't we be seeing dozens of other ROMs?
2. If other ROMs can be put on the F3, Y U NO Cyanogenmod?
3. If one were interested in learning how to build/port a ROM to the F3, where would you have them start? Move next?

Thank you to a great community!

I have asked this very same question. I would love to see a port of miui for our phone. It is being worked on currently so we will have a working cm rom we just need to be patient. After the cm rom is done then it will be easier to port other rom using the cm as a base to build from.

 

[Kasenomateru]

I've tried to port cm 11 to this device but I couldn't get it to install and since then I haven't tinkered with it lately due to this unknown error I got

 

[Kasenomateru]

So, a few questions for the good of the cause; perhaps some rhetorical, perhaps not:

1. Now that we have CWM Recovery for the Optimus F3 and two excellent ROMs--namely Psycho Billy Cyanogen Flavored Rom and Solar ROM--the proof-of-concept time is done; shouldn't we be seeing dozens of other ROMs?
2. If other ROMs can be put on the F3, Y U NO Cyanogenmod?
3. If one were interested in learning how to build/port a ROM to the F3, where would you have them start? Move next?

Thank you to a great community!

Also I think its because we don't have our bootloadrs turely unlocked only a work a round like loki'd

 

[moore.bryan]

I have asked this very same question. I would love to see a port of miui for our phone. It is being worked on currently so we will have a working cm rom we just need to be patient. After the cm rom is done then it will be easier to port other rom using the cm as a base to build from.

Do you happen to know who's working on the CM port?

I've tried to port cm 11 to this device but I couldn't get it to install and since then I haven't tinkered with it lately due to this unknown error I got

Are you, Kasenomateru, the one referenced above?

Also I think its because we don't have our bootloadrs turely unlocked only a work a round like loki'd

There's CM for other loki'd phones, no?

 

[moore.bryan]

Also, what is the difficulty in porting, say, the CM nightly for the Optimus G to the F3?

I know these are noob questions, but I'm seriously considering getting involved in development, but have no idea where to start!

Also, could one simply edit the build.prop of a CM nightly to try and see if it'll install on the F3? And, what's the F3's "p#;" that is, the Optimus L9 is "p760."

 

[sonophilos]

Difficult. We'd need a device with almost identical hardware to port like that.
Also, our bootloader is still technically locked, which is one of many causes CM in development still isn't booting.

The Virgin Mobile Optimus F3 has a model number of LS720. It does not follow the P# naming scheme. No, we totally can't just edit a build prop and have a booting CM. There are so many problems with that.

Hope this helps.

 

[xclusive36]

Do you happen to know who's working on the CM port?

I'm working on a cm port. I'm trying to port cm from the LG Motion. I'm having issues with the booting process. I've gotten it to boot to the cm boot animation. To boot further, I need to diagnose the issue. I'm guessing that there is a conflict somewhere but I need to rule out another issue first.

For some reason, I've not been able to compile a full version in about a week. Errors keep popping up that were not there before. weird ones that shouldn't be there. Missing files that were there before. I was hoping to have something to show by the end of the month but thats not going to happen until I figure out what's going on.

 

[xclusive36]

I'm just going to delete everything and start over. 60+gigs.. sigh

 

[jmpiv4]

I been tinkering MIUI but it's best to base it from a cm port rather than a stock rom.. I also chose the Sony Xperia SP for MIUI as the donor ROM, I can get far enough in the boot to get a logcat but I'm getting a lot of jar errors.....

 

[cell2011]

MIUI would be nice on our phone i think

 

[moore.bryan]

Difficult. We'd need a device with almost identical hardware to port like that.
Also, our bootloader is still technically locked, which is one of many causes CM in development still isn't booting.

The L7/L9 seems to have similar hardware in most cases; the most significant differences seem to be in screen size... any reason why porting doesn't seem to be focusing on those two devices that you know of?

The Virgin Mobile Optimus F3 has a model number of LS720. It does not follow the P# naming scheme. No, we totally can't just edit a build prop and have a booting CM. There are so many problems with that.
Hope this helps.

It does; thanks. Can you point me somewhere to start learning about why there would be "so many problems" with editing the build.prop?

I'm working on a cm port. I'm trying to port cm from the LG Motion.

Any reason why you chose to port from the Motion?

I'm having issues with the booting process. I've gotten it to boot to the cm boot animation. To boot further, I need to diagnose the issue. I'm guessing that there is a conflict somewhere but I need to rule out another issue first.

Mind sharing what the other issue is?

For some reason, I've not been able to compile a full version in about a week. Errors keep popping up that were not there before. weird ones that shouldn't be there. Missing files that were there before. I was hoping to have something to show by the end of the month but thats not going to happen until I figure out what's going on.

Could this be a behind-the-scenes CM change?

I been tinkering MIUI but it's best to base it from a cm port rather than a stock rom.. I also chose the Sony Xperia SP for MIUI as the donor ROM, I can get far enough in the boot to get a logcat but I'm getting a lot of jar errors.....

Like what I asked of xclusive36, is there any reason why you chose the Xperia for your donor ROM? Could the issue with jar be some of the java manifests being specific to the Xperia or doesn't it work that way.

Thanks you all who are responding... like I wrote, development is something I'd like to get in to, but am not sure where to start and/or learn.

 

[xclusive36]

Originally Posted by sonophilos View Post
Difficult. We'd need a device with almost identical hardware to port like that.
Also, our bootloader is still technically locked, which is one of many causes CM in development still isn't booting.

The L7/L9 seems to have similar hardware in most cases; the most significant differences seem to be in screen size... any reason why porting doesn't seem to be focusing on those two devices that you know of?

There are allot of phones to choose from. I just picked one that I new was somewhat similar.

I'm working on a cm port. I'm trying to port cm from the LG Motion.

Any reason why you chose to port from the Motion?

It's hardware is similar to the LG Optimus F3. They also had issues with the bootloader and couldn't get it unlocked. I was also told to model our phones device tree after the LG Motions from a dev on irc. Afterwards by PlayfulGod that it may not be a good idea because they used 2nd-init instead of loki.

I'm having issues with the booting process. I've gotten it to boot to the cm boot animation. To boot further, I need to diagnose the issue. I'm guessing that there is a conflict somewhere but I need to rule out another issue first.

Mind sharing what the other issue is?

The other issue is that it was setup to use 2nd-init but its not. It's not pointing to another set of init files. It's booting up to the boot animation off of the stock ramdisk. I didn't want to get into it because I didn't know if it even needed it or not. But I need to rule it out as an issue first. Since I can not get access to adb, i'm having an issue diagnosing it. Not being able to access adb is also an issue in of it's self.

For some reason, I've not been able to compile a full version in about a week. Errors keep popping up that were not there before. weird ones that shouldn't be there. Missing files that were there before. I was hoping to have something to show by the end of the month but thats not going to happen until I figure out what's going on.

Could this be a behind-the-scenes CM change?

No, I had to hard reset my computer while it was compiling the other day. Since i'm running ubuntu inside of vmware, some files became corrupted. Some also disappeared.

 

[jmpiv4]

Like what I asked of xclusive36, is there any reason why you chose the Xperia for your donor ROM? Could the issue with jar be some of the java manifests being specific to the Xperia or doesn't it work that way.

Thanks you all who are responding... like I wrote, development is something I'd like to get in to, but am not sure where to start and/or learn.

I picked the Xperia SP because it uses the exact same CPU and it was the only one used it that was already ported to MIUI,

The manifests are a big possibility.

 

[moore.bryan]

I picked the Xperia SP because it uses the exact same CPU and it was the only one used it that was already ported to MIUI,

The manifests are a big possibility.

Do we know of any other phones with our CPU?

 

[jmpiv4]

Do we know of any other phones with our CPU?

Here is a small list
Mobile Processors | Qualcomm Snapdragon Processors

Here is the processor MSM8930 (Snapdragon 400)
If you search something like amazon with "MSM8930" it would give you a list of some phones also.

 

[xclusive36]

I'm thinking about changing direction. Instead of using the LG Motion device as a base to port cm, i'm going to switch to the HTC One mini.

Even though both use msm8960, The LG motion uses adreno 200, our phone and the HTC One Mini, uses adreno 305.

The HTC One Mini is also officially supported by the Cyanogenmod Project.

Here's the device tree:
https://github.com/CyanogenMod/android_device_htc_m4

What do you guys think?

 

[xclusive36]

Also after looking it up, the Xperia SP uses msm8960t with Krait 200

Edit. Sorry, looked at it wrong.

We both use krait 200. Xperia SP uses adreno 320

 

[jmpiv4]

Also after looking it up, the Xperia SP uses msm8960t with Krait 200

Edit. Sorry, looked at it wrong.

We both use krait 200. Xperia SP uses adreno 320

How in the hell did I miss it that bad?

Any Way Here's a copy from Wikipedia (cleaned up a little)

Snapdragon 400

Model Number: 8930
Semiconductor technology: 28 nm LP
CPU Instruction Set: ARMv7
CPU: Up to 1.2 GHz dual-core Krait 200
CPU Cache: L1: 32 KB, L2: 1 MB
GPU: Adreno 305
Memory Technology: LPDDR2 @ 533 MHz
Wireless Radio Technologies: LTE

Nokia Lumia 625
Samsung Galaxy Express (GT-I8730)
HTC One mini (601e)
Samsung Galaxy ACE 3 LTE (GT-S7275)
Samsung Ativ S Neo
HTC 8XT
LG Optimus F3
LG Optimus F3Q

reference: Snapdragon (system on chip) - Wikipedia, the free encyclopedia

Seams I was looking at the chipset and not the actual processor, I was using Qualcomms site and on their site they go by groups instead of individual processors when searching. And Even with this list above the cpu varies.

 

[xclusive36]

We both did. I assumed. You know what they say about assumption don't you?
It's the mother of all $*#$ ups. lol