Root [Virgin Mobile/Sprint] [Rom] [ALPHA] [4.1.2] Cyanogenmod 10.0 Unofficial

[Andresramirezvzla]

I noticed that too. It worked fine in early versions. Seemed to pop up when I switched to compiled releases.

Is there any way to solve this problem?

 

[Andresramirezvzla]

Fixes the problem of the microphone adding or replacing the following lines in the file build.prop

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog
persist.audio.voice.clarity=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicered=flase
persist.audio.fluence.speaker=false

 

[Andresramirezvzla]

I have a new problem. When the phone is locked, the display remains lit with a black light.

 

[masterdbugger]

That is also a known issue, we've been working hard at it, but haven't been able to pinpoint the problem. Good job fixing the audio properties. The current workaround is to keep turning the screen on and off until it actually goes out, sometimes it takes a while. If you can fix that you'll be my hero<3

 

[Andresramirezvzla]

Fixes the problem of the microphone adding or replacing the following lines in the file build.prop

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog
persist.audio.voice.clarity=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicered=flase
persist.audio.fluence.speaker=false

UPDATE:

This problem can be fix with only replace the following line in the file build.prop:

persist.audio.handset.mic=digital

TO

persist.audio.handset.mic=analog

 

[Andresramirezvzla]

@xclusive36 I am working to fix the problem related with the screen. Actually i am a software developer in country Venezuela. I speak spanish but i attempt to speak english. I can help you if you need my help with anything.

PD: Excellent rom. I love it

 

[xclusive36]

UPDATE:

This problem can be fix with only replace the following line in the file build.prop:

persist.audio.handset.mic=digital

TO

persist.audio.handset.mic=analog

I figured it would be something as simple as that. Thank you

 

[xclusive36]

@xclusive36 I am working to fix the problem related with the screen. Actually i am a software developer in country Venezuela. I speak spanish but i attempt to speak english. I can help you if you need my help with anything.

PD: Excellent rom. I love it

A link to the device tree is in the first post. Ive ruled out the ramdisk or kernel. The problem is somewhere in the rom.

 

[daemon32]

Hi, I'm still new to the whole rom creation scene, but... I forked your repo on github to try and port the device tree to the T-Mobile variant of the F3, but I can't seem to figure out what proprietary blobs (particularly for the USIM and HSPA/LTE radio) to use from the stock firmware. What did you to to find out all of the symbol dependencies for the blobs you included?

I will also report:

- I do have a working installation on the T-Mobile variant
- The radio doesn't work (obviously)
- I'm not sure if the hardware video decoder is working (but it seems to be, in chrome anyway)
- The graphics drivers are odd in that when you are in an app using GLES or video playback and you switch the device to portrait or landscape, and vice versa, the framebuffer gets corrupted at the edges of the screen (but redrawing fixes it, you can still see the game or video you're playing).

EDIT: I got it to communicate with the baseband on the blobs from your rom (it reads the MEID, IMEI and ICCID correctly, but can't find a signal)
EDIT 2: I got it to find signal! (I only have a deactivated SIM, and no baseband unlock, so I can't test network connectivity)

 

[xclusive36]

I'm glad you got it to boot. In the beginning, it was all just trial and error. I copied whole folders and eliminated them all one by one. Expecialy the etc folder. Also check your build.prop It looks like you got it to work but you'll need someone to test it to confirm.

 

[Jerfson Paiva]

This Alpha run on LG Optimus F3 p659 from Brazil?

 

[xclusive36]

This Alpha run on LG Optimus F3 p659 from Brazil?

No. Boot is not the same

 

[Jerfson Paiva]

No. Boot is not the same

Thank you

 

[daemon32]

So I got an unlock code from some (apparently not so dodgy) ebay seller...
http://i.imgur.com/q4rv59o.png
http://i.imgur.com/i1ie4MU.png
http://i.imgur.com/q7Km1Jy.png
As you can see, I can't get LTE to work (I don't think it's an issue with the rom, it didn't work on stock firmware either, probably because my data plan doesn't include LTE!)

And if there's something I'm missing about making BBCode that hides my pictures, let me know!

 

[xclusive36]

So I got an unlock code from some (apparently not so dodgy) ebay seller...
http://i.imgur.com/q4rv59o.png
http://i.imgur.com/i1ie4MU.png
http://i.imgur.com/q7Km1Jy.png
As you can see, I can't get LTE to work (I don't think it's an issue with the rom, it didn't work on stock firmware either, probably because my data plan doesn't include LTE!)

And if there's something I'm missing about making BBCode that hides my pictures, let me know!

That's cool, I'm glad you got it to work. Upload it for me so I can post it to this thread for others to use.

 

[daemon32]

That's cool, I'm glad you got it to work. Upload it for me so I can post it to this thread for others to use.

Okay, here ya go: http://www.mediafire.com/download/u56bu0e7w0i7wjw/cm-10-20150601-UNOFFICIAL-fx3.zip

 

[xclusive36]

I've updated the device tree. It now compiles the boot.img with the rom. The ramdisk used is the sprint/virgin mobile ramdisk slightly modified. It requires the LS720ZV5 aboot.img to work. It will loki the boot.img during install.. To use the device tree on other variants, you'll need to include your own ramdisk and your own aboot.img that works with loki.

 

[xclusive36]

Okay, here ya go: http://www.mediafire.com/download/u56bu0e7w0i7wjw/cm-10-20150601-UNOFFICIAL-fx3.zip

Will this work on both t-mobile and metro pcs phones, or just t-mobile?
Also, does both phone, 3g, camera work?

also, have you applied the phone sound fix by changing digital to analog in the build.prop file?
Are you using the sprint/virgin mobile aboot.img and boot.lok or are you using your own?

 

[AquaVolt]

Will this work on both t-mobile and metro pcs phones, or just t-mobile?
Also, does both phone, 3g, camera work?

also, have you applied the phone sound fix by changing digital to analog in the build.prop file?
Are you using the sprint/virgin mobile aboot.img and boot.lok or are you using your own?

I'm pretty sure the t-mobile and metro pcs variants are interchangeable and as everything for one always ends up working for the other. So Even if it's made for the t-mobile variant it should still work with metro pcs

 

[xclusive36]

I'm pretty sure the t-mobile and metro pcs variants are interchangeable and as everything for one always ends up working for the other. So Even if it's made for the t-mobile variant it should still work with metro pcs

Have you tested it? Does it work for you?

 

[AquaVolt]

Have you tested it? Does it work for you?

I didn't try it yet and I'm probably not going to be able to as its finals week for me in school. I was just making a prediction from past experience.

 

[daemon32]

I've updated the device tree. It now compiles the boot.img with the rom. The ramdisk used is the sprint/virgin mobile ramdisk slightly modified. It requires the LS720ZV5 aboot.img to work. It will loki the boot.img during install.. To use the device tree on other variants, you'll need to include your own ramdisk and your own aboot.img that works with loki.

I'm not sure about the aboot magic, but my image includes the aboot that came with the Freedom kernel (it works just fine for me, on the T-Mobile LG-P659)...

Will this work on both t-mobile and metro pcs phones, or just t-mobile?
Also, does both phone, 3g, camera work?

also, have you applied the phone sound fix by changing digital to analog in the build.prop file?
Are you using the sprint/virgin mobile aboot.img and boot.lok or are you using your own?

Phone calls (sending and receiving), texts (didn't test MMS as I don't have a texting plan), and 3G data (HSDPA and HSPA+) work just fine, but as for the camera, the back one shows up as green for some reason (wrong image format?) and the front camera works just fine. The only thing you have to do for data to work is to put in an APN (it took me a while to accidentally push the menu key in the blank APNs screen!)

EDIT: Another thing that has been bothering me though, is that the vibrator doesn't work... I tried getting /sys/class/timed_output/vibrator/* to show up by enabling a bunch of vibrator-related kernel drivers, but I couldn't get it to show up... I also don't know what the /dev/tspdrv node does...

I lost my aboot ;( but I'm using the one from the Freedom kernel. The boot.lok is also from freedom (the overclocked one) as I like that one, but if it's a problem to include that (which it shouldn't, because it's GPL) I have my own version that I got working last night.

I'm pretty sure the t-mobile and metro pcs variants are interchangeable and as everything for one always ends up working for the other. So Even if it's made for the t-mobile variant it should still work with metro pcs

I don't see why not, as I used the Xperion (MetroPCS) firmware on my T-Mobile phone for a while, and everything works perfectly.

 

[xclusive36]

I'm not sure about the aboot magic, but my image includes the aboot that came with the Freedom kernel (it works just fine for me, on the T-Mobile LG-P659)...



Phone calls (sending and receiving), texts (didn't test MMS as I don't have a texting plan), and 3G data (HSDPA and HSPA+) work just fine, but as for the camera, the back one shows up as green for some reason (wrong image format?) and the front camera works just fine. The only thing you have to do for data to work is to put in an APN (it took me a while to accidentally push the menu key in the blank APNs screen!)

EDIT: Another thing that has been bothering me though, is that the vibrator doesn't work... I tried getting /sys/class/timed_output/vibrator/* to show up by enabling a bunch of vibrator-related kernel drivers, but I couldn't get it to show up... I also don't know what the /dev/tspdrv node does...

I lost my aboot ;( but I'm using the one from the Freedom kernel. The boot.lok is also from freedom (the overclocked one) as I like that one, but if it's a problem to include that (which it shouldn't, because it's GPL) I have my own version that I got working last night.



I don't see why not, as I used the Xperion (MetroPCS) firmware on my T-Mobile phone for a while, and everything works perfectly.

Ok, thanks for the information. I wouldn't worry about vibration. Masterdebugger just informed me he got it to work. Also, The boot.lok will need to be swapped out for the one from the t/pcs stock rom. GameTheory doesn't want his "Kernel" included in any rom other than his. Your right about it being GPL but that's what he wants.

I've made a few changes to the device tree, and am about to make a few more over the next day or so. Can you re-sync afterwards, and then recompile the rom with the changes?

 

[Member1614188]

Weird problem here. Wiped the whole device. (/system, all of it.) Removed certain apps in .zip because of this being a non-phone. (I have an i717 / Galaxy Note).. It will not go past the LG screen. The last time I used this device (wew, 2014) it didn't do this. Anyone else have this problem?

 

[xclusive36]

Weird problem here. Wiped the whole device. (/system, all of it.) Removed certain apps in .zip because of this being a non-phone. (I have an i717 / Galaxy Note).. It will not go past the LG screen. The last time I used this device (wew, 2014) it didn't do this. Anyone else have this problem?

Try re-installing the rom