• 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

SuperR said:
Texting sends and receives fine here with the exception of mms.

Sounds like you did not wipe data. That would account for the settings that carried over.

I got the new icons on the home screen as well. To delete, touch and hold, then drag to the trash can at the top.
Click to expand...

Could've sworn I did. Cache, Delvic Cache, than Data ... but now you have me wondering.

It would account for that setting coming in.

And sheesh! OF COURSE, long press and drag, it looked like it was embedded or something, so it didn't cross what's left of my mind.

Thanks Super.
 
I think I love this rom. I went back to b13 for a short while and was very irritated lol.

After using it for a few days as my daily, there are only a few minor annoyances.

1. If the screen is off and a call comes in, I usually can't see who the caller is.
2. When an app requests superuser privileges, you can't see the choices of how long it should be remembered. This one is easy to get around once you know where it is on the screen. Just because you can't see it doesn't mean it's not there :)
3. The proximity sensor does not shut the screen off while in a call
4. Opening settings in Messaging app FC's the app. Not able to change settings.
5. Only once out of several times, I plugged my wired headset in and the phone rebooted.
6. Bluetooth? lol

I m pretty sure 1 & 2 are the graphical issues you were talking about. Unfortunately they are still present on 2/13/14 build.

Seriously fantastic work man. I really appreciate the time and effort you are spending on this device :)
 
Super,

Another fresh install. Again that automatic downloading Play Store does, (meaning Titainium Backup has no bandwidth to start downloading) had to be turned off.

Again, get the half screen when starting T.B., and the too-too fast permissions to anticipate. and like "wack-a-mole" at an arcade, can be tapped
Oddly that doesn't happen with Rom Toolbox, (essentially a clone of T.B. with extra's.) I think that's the Superuser app with T.B. is responsible (being an older version maybe?).

Same as last time though, the previous "live" wallpaper, was again, in place, (after Cache/Delvic Cache, and Data Wipe, Factory Reset). So, I did, (if only through muscle memory) that same sequence the first time.

I'm loving it too.

Nice job ... tip of the hat to jetx2x,
(don't ware a hat but I'd tip it if I did.) :)
 
DimBulb said:
Super,

Another fresh install. Again that automatic downloading Play Store does, (meaning Titainium Backup has no bandwidth to start downloading) had to be turned off.

Again, get the half screen when starting T.B., and the too-too fast permissions to anticipate. and like "wack-a-mole" at an arcade, can be tapped
Oddly that doesn't happen with Rom Toolbox, (essentially a clone of T.B. with extra's.) I think that's the Superuser app with T.B. is responsible (being an older version maybe?).

Same as last time though, the previous "live" wallpaper, was again, in place, (after Cache/Delvic Cache, and Data Wipe, Factory Reset). So, I did, (if only through muscle memory) that same sequence the first time.

I'm loving it too.

Nice job ... tip of the hat to jetx2x,
(don't ware a hat but I'd tip it if I did.) :)
Click to expand...

I've noticed that sometimes ya gotta reRoot (twice) to get rid of TB's superuser/Root issues...
 
Re-ROOT? If it work's, than I'm glad you shared that, I'd never have guessed.

When I didn't get to give the permissions and it started up, it wanted nothing to do with that. Without permissions, then it's got no root access, and it's useless. Getting T.B. to HAVE root permissions again, was tricky. I tried something different.
In Rom Toolbox, app manager - T.B -Advanced, and hit fix permissions.
Started up again like normal.

These two apps compliment each other, and each can fix the other.
 
DimBulb said:
Another fresh install. Again that automatic downloading Play Store does, (meaning Titainium Backup has no bandwidth to start downloading) had to be turned off.
Click to expand...
This may be default for the rom, although nothing starts downloading whenI get it installed. I do get a notification that some apps need to be updated. I don't use titanium backup so I really know much about that.
DimBulb said:
Same as last time though, the previous "live" wallpaper, was again, in place, (after Cache/Delvic Cache, and Data Wipe, Factory Reset). So, I did, (if only through muscle memory) that same sequence the first time.
Click to expand...
The only thing I an think of is that the recovery is not wiping data for some reason. Which recovery are you using? I am still on 6.0.2.7. Or possibly the "custom" live wallpaper is actually the default live wallpaper. Mine had phase beam live wallpaper after fresh install.
 
I'd changed from that live phase beam to a water and leaves, and that's the "new default". Like it's saved personal settings, some place, somehow and it freaks me out that it can do that.

I've got the same Clockwork Mod Recovery 6.0.2.7.

Not big deals. Irritants is all.

Thanks.
 
Oh, you probably have google backing up your data and settings. Go into system settings, Accounts/Google, click your google account, and uncheck App Data. Or, did you sign up for a Cyanogen account? They might save your settings.
 
SuperR said:
Oh, you probably have google backing up your data and settings. Go into system settings, Accounts/Google, click your google account, and uncheck App Data. Or, did you sign up for a Cyanogen account? They might save your settings.
Click to expand...

During setup, fresh install, I choose what I want Google to do, and was pretty sure that was eliminating a problem. And I don't have a Cyanogen account, so skip over to sign in with Google.

It's worth a look. I'm in an older backup now, (so surprised at how nicely I had set up the phone months ago), so will restore later to the new upgrade and go check that out.


Thanks.
 
SuperR said:
Oh, you probably have google backing up your data and settings. Go into system settings, Accounts/Google, click your google account, and uncheck App Data. Or, did you sign up for a Cyanogen account? They might save your settings.
Click to expand...

OK, have unchecked the Data.

That's not a setting I've ever messed with in the past. Are you thinking it's causing that automatic downloading from Play Store after fresh install?

Well if it does, I'll leave it off. What else would that do, keep me notified of app updates?

Anyway, thanks a bunch Super.
 
Hey jetx2x. Here is the logcat output when I try to play a voicemail in the vvm app. To clarify, the vvm app works, I get voicemail notifications, they show up in the app and show how long the message is, and when you click play nothing happens. Any idea what may cause this?
Code: 
D/AwesomePlayer(  132): Before reset_l
D/AwesomePlayer(  132): printFileName fd(19) -> /data/data/com.coremobility.app.vnotes/files/VN-001C.AMR
E/AwesomePlayer(  132): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
E/AwesomePlayer(  132): LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
D/AudioTrack(  132): Turn on Direct Output for VOIP RX
D/AudioPolicyManager(  132):  profile found: device 1, flags 4001, samplingrate 8000,            format 1, channelMask 1
D/AudioHardware7x30(  132): AudioHardware::openOutputStream devices 1 format 1 channels 1 samplerate 8000
E/AudioHardware7x30(  132):  AudioHardware::openOutputStream Only one output stream allowed 
E/AudioTrack(  132): Could not get audio output for stream type 0
E/AudioSink(  132): Unable to create audio track
E/AwesomePlayer(  132): AudioPlayer start error
E/MediaPlayer( 7658): error (-19, 0)
E/Sensors (  658): sensor_hal set_prox_threshold_data error
E/MediaPlayer( 7658): Should have subtitle controller already set
E/MediaPlayer( 7658): Error (-19,0)
E/        ( 7658): Mod:Integration Line# -1 onError--->   what:-19    extra:0
E/        ( 7658): Mod:VnotesApp Line# -1 OnAudioPlayerError - ErrorType =5
E/MediaPlayer( 7658): stop called in state 0
E/MediaPlayer( 7658): error (-38, 0)
 
Here is the logcat when Messaging FC's while trying to open settings
Code: 
W/Resources(29973): Converting to string: TypedValue{t=0x10/d=0x0 a=-1}
D/AndroidRuntime(29973): Shutting down VM
W/dalvikvm(29973): threadid=1: thread exiting with uncaught exception (group=0x415a2c80)
E/AndroidRuntime(29973): FATAL EXCEPTION: main
E/AndroidRuntime(29973): Process: com.android.mms, PID: 29973
E/AndroidRuntime(29973): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.mms/com.android.mms.ui.MessagingPreferenceActivity}: java.lang.NullPointerException
E/AndroidRuntime(29973): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2215)
E/AndroidRuntime(29973): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2265)
E/AndroidRuntime(29973): 	at android.app.ActivityThread.access$800(ActivityThread.java:145)
E/AndroidRuntime(29973): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1206)
E/AndroidRuntime(29973): 	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(29973): 	at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(29973): 	at android.app.ActivityThread.main(ActivityThread.java:5081)
E/AndroidRuntime(29973): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(29973): 	at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(29973): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/AndroidRuntime(29973): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/AndroidRuntime(29973): 	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(29973): Caused by: java.lang.NullPointerException
E/AndroidRuntime(29973): 	at com.android.mms.ui.MessagingPreferenceActivity.setMessagePreferences(MessagingPreferenceActivity.java:320)
E/AndroidRuntime(29973): 	at com.android.mms.ui.MessagingPreferenceActivity.loadPrefs(MessagingPreferenceActivity.java:285)
E/AndroidRuntime(29973): 	at com.android.mms.ui.MessagingPreferenceActivity.onCreate(MessagingPreferenceActivity.java:176)
E/AndroidRuntime(29973): 	at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime(29973): 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(29973): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
E/AndroidRuntime(29973): 	... 11 more
W/ActivityManager(  658):   Force finishing activity com.android.mms/.ui.MessagingPreferenceActivity
W/ActivityManager(  658):   Force finishing activity com.android.mms/.ui.ConversationList
I/Adreno200-EGLSUB(  129): <CreateImage:896>: Android Image
I/Adreno200-EGLSUB(  129): <GetImageAttributes:1105>: RGBA_8888
W/ActivityManager(  658): Activity pause timeout for ActivityRecord{41ec6cf8 u0 com.android.mms/.ui.MessagingPreferenceActivity t70 f}
I/Adreno200-EGLSUB(  880): <ConfigWindowMatch:2081>: Format RGBA_8888.
I/ActivityManager(  880): Timeline: Activity_idle id: android.os.BinderProxy@41837748 time:22180066
 
Two thing's worth mentioning.

1:Again, in unofficial cm 11, and in T.B. to restore an app, (Nandroid Manager for this instance, but also others), and choose just the app not the app and data. This run's and run's and doesn't restore. Have to pull the battery.

That brings up #2

2: Put battery back in, close case, DON'T start the phone, but do plug in the charger.
The green android pops up, so I wait for the charger icon to start, that doesn't happen. I'm busy at the computer, phone right in front of me on the desk, so the next thing I notice is the Cyanogen boot animation start's, and sure enough the phone, turns on.

I'm just saying! Anyone else with anomalies or strange/different behaviors?
Those haven't happened on other Roms.
 
DimBulb said:
2: Put battery back in, close case, DON'T start the phone, but do plug in the charger.
The green android pops up, so I wait for the charger icon to start, that doesn't happen. I'm busy at the computer, phone right in front of me on the desk, so the next thing I notice is the Cyanogen boot animation start's, and sure enough the phone, turns on.

I'm just saying! Anyone else with anomalies or strange/different behaviors?
Those haven't happened on other Roms.
Click to expand...

Plugging in the device when it is off brings up andy and a solid red notification light. It does not seem to be booting, but i am not sure if it's charging either. Unplugging seems to have made it reboot.

In summary, don't plug in when the power is off. Only charge while the device is booted to android for now :)
 
DimBulb said:
Two thing's worth mentioning.

1:Again, in unofficial cm 11, and in T.B. to restore an app, (Nandroid Manager for this instance, but also others), and choose just the app not the app and data. This run's and run's and doesn't restore. Have to pull the battery.

That brings up #2

2: Put battery back in, close case, DON'T start the phone, but do plug in the charger.
The green android pops up, so I wait for the charger icon to start, that doesn't happen. I'm busy at the computer, phone right in front of me on the desk, so the next thing I notice is the Cyanogen boot animation start's, and sure enough the phone, turns on.

I'm just saying! Anyone else with anomalies or strange/different behaviors?
Those haven't happened on other Roms.
Click to expand...

I've noticed that if u pull battery and immediately place back in within a certain Short period if time, the phone will automatically just reboot instead of staying off..
 
nicely done gentlemen. heard you need an mms fix. thanks to superr for letting me know btw

take the forces apns, may need modification due to the lack of lte on the sequent, but it works flawlessly for the force.

next youll need to set the build.prop to sprint values, both virgin and boosts network values seem to be nothing but virtual hosts and arent compatable with cm, the values for that can also be found in the system.prop/build.prop for the force

wish i could help with bluetooth but all i know for sure is it will turn on with a standard hciattach command at a ridiculously low baudrate, 11500 baud or something like that its been a while
 
Another thing I've noticed, (not trying to dwell on all the wrong stuff, just mentioning "differences" noticed), in settings/battery, Battery Usage Data, isn't available.

Charging or Not-charging is all we have.
 
@jetx2x I think the mms problem could be in this file as it is missing the mms proxy

https://github.com/jetx2x/cm_androi...rlay/packages/apps/Mms/res/xml/mms_config.xml

edit: Although it looks like nothing from the apn is carrying over. Here is the message from logcat when pressing the send button on an mms using cm11 Mms.apk
Code: 
W/TransactionService( 9584): Exception occurred while handling message: { when=-54ms what=1 arg1=1 obj=transactionType: 1 uri: content://mms/2 pushData: null mmscUrl: null proxyAddress: null proxyPort: 0 target=com.android.mms.transaction.TransactionService$ServiceHandler }
 
Anu reason that my wifi and wifi tether quit after one day .. Or point me in the right direction ... It just wont load the tether and the wifi button is greyed out
 
SuperR said:
@jetx2x I think the mms problem could be in this file as it is missing the mms proxy

https://github.com/jetx2x/cm_androi...rlay/packages/apps/Mms/res/xml/mms_config.xml

edit: Although it looks like nothing from the apn is carrying over. Here is the message from logcat when pressing the send button on an mms using stock Mms.apk
Code: 
W/TransactionService( 9584): Exception occurred while handling message: { when=-54ms what=1 arg1=1 obj=transactionType: 1 uri: content://mms/2 pushData: null mmscUrl: null proxyAddress: null proxyPort: 0 target=com.android.mms.transaction.TransactionService$ServiceHandler }
Click to expand...

why are you using the stock mms.apk? thatll cause more problems
 
Anybody notice the contacts load slow when a call is coming in or when you open up messaging app? It will show the number than eventually load the contact's name, just throwing it out there.
 
check my github, i cant get to it but one of the branches should have all the right stuff, very short apn with none of that chinese letter crap and the mms.xml didnt seem to have the proxies either

also you did make sure to do a factory reset before testing any new apns right? it stores them in data on first run so just changing the file in system does nothing after that
 
junkie2100 said:
check my github, i cant get to it but one of the branches should have all the right stuff, very short apn with none of that chinese letter crap and the mms.xml didnt seem to have the proxies either

also you did make sure to do a factory reset before testing any new apns right? it stores them in data on first run so just changing the file in system does nothing after that
Click to expand...

This is the Mms.apk that was built with cm11. The logcat is from out-of-the-box so there was no changing apk's or xml's happening. Just trying to help track down the issue ;)
 
You must log in or register to reply here.
Back
Top Bottom