• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Team Osiris][ROM][Beta] Unofficial CM11

I can't test this now, but it may fix visual voicemail. You will need the apk installed (maybe in /system/app with proper permissions - not really sure), and will need to change your /system/build.prop file.

Find these 2 lines
Code: 
ro.cdma.home.operator.numeric=311870
ro.cdma.home.operator.alpha=Boost Mobile
and change them to this:
Code: 
ro.cdma.home.operator.numeric=310000
ro.cdma.home.operator.alpha=Chameleon
Save, reboot, and test.
 
SuperR said:
I can't test this now, but it may fix visual voicemail. You will need the apk installed (maybe in /system/app with proper permissions - not really sure), and will need to change your /system/build.prop file.

Find these 2 lines
Code: 
ro.cdma.home.operator.numeric=311870
ro.cdma.home.operator.alpha=Boost Mobile
and change them to this:
Code: 
ro.cdma.home.operator.numeric=310000
ro.cdma.home.operator.alpha=Chameleon
Save, reboot, and test.
Click to expand...

I'll give it a shot in an hour or so. Maybe someone can test before that
 
Permissions seem to be the problem with vtt-boost.apk (visual voicemail). This is a section of my logcat while trying to run it
Code: 
W/PackageManager(  662): Not granting permission android.permission.MODIFY_PHONE_STATE to package com.coremobility.app.vnotes (protectionLevel=18 flags=0x8be45)
W/PackageManager(  662): Unknown permission com.sprint.internal.permission.SYSTEMPROPERTIES in package com.coremobility.app.vnotes
W/PackageManager(  662): Unknown permission com.sprint.permission.INSTALL_UPDATES in package com.coremobility.app.vnotes
W/PackageManager(  662): Not granting permission android.permission.INSTALL_PACKAGES to package com.coremobility.app.vnotes (protectionLevel=18 flags=0x8be45)
W/PackageManager(  662): Not granting permission android.permission.INTERACT_ACROSS_USERS to package com.coremobility.app.vnotes (protectionLevel=50 flags=0x8be45)
W/PackageManager(  662): Not granting permission android.permission.INTERACT_ACROSS_USERS_FULL to package com.coremobility.app.vnotes (protectionLevel=2 flags=0x8be45)
 
wam_anthony said:
Used to everything being crisp lol you gonna develop for pa aokp or pacman after this??
Click to expand...

jetx2x said:
After I get my other PC fixed (which should be soon)... This PC builds too slow for me to be willing to do more ROMs... This isn't the only device I'm wanting to work on
Click to expand...

Once everything is close to being fixed and i re-install linux onto my PC i can bring my aosp Carbon 4.2 Rom up to 4.4 thanks to jetx and his kitkat source.
 
Just wanted to add, when I was using this ROM, awesome features BTW, I found it very laggy, and Skype would just not open up at all, also the function buttons do not light and no vibration. Apps seem to take longer to open, a lot of times it required a reboot. But definetaly an awesome effort plz keep up the good work, this device is horrible for a heavy user.
 
therealaliq said:
Just wanted to add, when I was using this ROM, awesome features BTW, I found it very laggy, and Skype would just not open up at all, also the function buttons do not light and no vibration. Apps seem to take longer to open, a lot of times it required a reboot. But definetaly an awesome effort plz keep up the good work, this device is horrible for a heavy user.
Click to expand...

you took the words out of my mouth lmao. is your notification light pulsing? mine seems to just stay lit instead of pulsing.
 
This rom is using 3.0.8 kernel, which if i remember correctly has a memory leak. Not sure if it was patched, but it may be why we are experiencing some lag.
 
To chevanlol... You won't be able to get a build with what is on my git... I have pulled a ton of patches from else where to get this ROM to even build let alone boot... I'll get all of my patches and external repos organized and make sure to include instructions and my local manifest in the device tree

Edit: and as for the 3.0.8 kernel... I backported ion to it but that breaks the ICS adreno libs because they use pmem... And I haven't gotten the libs from 4.1.2 to work nor some mako adreno libs I found... Need to update kgsl and some other stuff I think... The part that's really ticking me off though is that I can't get the 3.4 kernel to boot the stock libs either... I would love to simply use it rather than backport half of it to 3.0.8
 
I can't remember if the light pulsed or not for notifications but I do know i didn't see it turn on at all even while charging, I thought for a sec that my charger was unplugged but it turned out it was charging just not turning on the light, but still an awesome effort, I'm watching this thread every few hours every single day, am really excited to see what comes of this.
 
chevanlol360 said:
Once everything is close to being fixed and i re-install linux onto my PC i can bring my aosp Carbon 4.2 Rom up to 4.4 thanks to jetx and his kitkat source.
Click to expand...

Is that ROM like aokp? Or cmish? And idk if u take request but I would love to have a ROM with halo <3 like a pacman ROM or something
 
I'm currently using kikat as my Dailey and will give an overall of it also. Just like to give it time rather than just bash it
 
chevanlol360 said:
Camera doesn't work on any aosp ROM for this phone but jet might change that soon;)
Click to expand...

I'm not doing any dev work for the rest of the night due to school work... but let me ask this... did opening cam on the other 4.1 and 4.2 roms lock the phone? or is that new with me and kitkat?
 
jetx2x said:
I'm not doing any dev work for the rest of the night due to school work... but let me ask this... did opening cam on the other 4.1 and 4.2 roms lock the phone? or is that new with me and kitkat?
Click to expand...

New with you. On the others it just said can't connect to camera and u would click ok and it exits out
 
Still working on getting a kernel to boot with ion.... Whether it be 3.4 or 3.0.8... None of these adeno libs seems to like these kernels... Can't figure out why although I'm testing something new out out in about 40 mins when the build finishes
 
throwing together a build for you guys tonight...

https://github.com/jetx2x/cm_android_device_warp2/commit/23800be7d4baf5f5db23bcacfd5eff4dda969e92

Idk if the new camera wrapper will change anything... worth a shot though... hopefully mms is fixed after this also...

btw checkout my changes to the 3.0.8 kernel...

https://github.com/jetx2x/kernel_zte_warp2/commits/ion-wip

it STILL won't boot the stock 4.1 nor 4.2 mako adreno libs... think the stock 4.1 libs require a change somewhere in the rom whereas the 4.2 libs require more kernel work... the kernel included in this build I just started won't be the ion enabled version due to the obvious reason of no boot yet... well let me rephrase that... it does boot... just no display :\
 
You must log in or register to reply here.
Back
Top Bottom