Root [ROM] Quattrimus JB (CM10, AOKP41)

[ChuckL333]

I've been running and following this rom since the first release and I must say that so far, it has been very good. I've switched back from CM10 to AOKP various times and as of now I only have one complaint.

When sending text messages through the default SMS app that are longer than 160chars it breakes it up into multiple text. When trying to do the same thing through another application like GOSMS the message fails to send at all.

I understand this is a restraint of SMS but the case here is a verizon-to-verizon text message where the SMS length should be increased to (3) pages. On stock ICS this worked. For more info, MMS does work fine and sending/receiving pics is a breeze!


EDIT/UPDATE: Even more info on the subject: I've tried changing and adjusting the SMSC setting in the Phone Information settings. Using GOSMS I've also tried changing the 'User Agent', 'User Profile URL', and 'APN Configuration' (MMSC). Nothing so far has seemed to have worked, but maybe someone here with more insight can figure something out.

 

[tdm]

I've been running and following this rom since the first release and I must say that so far, it has been very good. I've switched back from CM10 to AOKP various times and as of now I only have one complaint.

When sending text messages through the default SMS app that are longer than 160chars it breakes it up into multiple text. When trying to do the same thing through another application like GOSMS the message fails to send at all.

I understand this is a restraint of SMS but the case here is a verizon-to-verizon text message where the SMS length should be increased to (3) pages. On stock ICS this worked. For more info, MMS does work fine and sending/receiving pics is a breeze!


EDIT/UPDATE: Even more info on the subject: I've tried changing and adjusting the SMSC setting in the Phone Information settings. Using GOSMS I've also tried changing the 'User Agent', 'User Profile URL', and 'APN Configuration' (MMSC). Nothing so far has seemed to have worked, but maybe someone here with more insight can figure something out.

I don't know where third party apps would get their configuration and I don't have a spectrum with service anymore. Maybe Neph or d2a could track this down...

 

[Nokoko]

When sending text messages through the default SMS app that are longer than 160chars it breakes it up into multiple text. When trying to do the same thing through another application like GOSMS the message fails to send at all.

EDIT/UPDATE: Even more info on the subject: I've tried changing and adjusting the SMSC setting in the Phone Information settings. Using GOSMS I've also tried changing the 'User Agent', 'User Profile URL', and 'APN Configuration' (MMSC). Nothing so far has seemed to have worked, but maybe someone here with more insight can figure something out.

I've had the same issue, it is annoying! I got GOSMS to work by checking the Split Large Messages box under Send Settings. Still splits them like the stock app but at least it sends them. Says that option is useful for phones on CDMA networks...? Didn't have it checked before CM and long messages were grouped as one on my end, although I believe they were still split during transmission.

 

[ChuckL333]

I've had the same issue, it is annoying! I got GOSMS to work by checking the Split Large Messages box under Send Settings. Still splits them like the stock app but at least it sends them. Says that option is useful for phones on CDMA networks...? Didn't have it checked before CM and long messages were grouped as one on my end, although I believe they were still split during transmission.

The stock app will split the messages fine for me, however GOSMS will not without the split SMS settings enabled. CDMA networks can only send 160 character messages through SMS to different networks. Over the same network, such as a Verizon to Verizon phone message, the messages should be grouped up to a total of 3 160 character messages before being turned into an MMS. I'm honestly not sure what the issue is or what could be causing this, but it's almost as though my phone registered through Verizon doesn't actually know it's running on the VZW network, which could ultimately lead to this being solved by simply changing settings.

Like I said, I've tried many different settings, turning on/off radios including WIFI and reflashing both CM10 and AOKP several times.

When I'm running the stock ICS OTA my SMS messages are grouped together as normal when sending over the VZW network. They look that way when sent, and my girlfriend confirms that's how she receives them. (She is on the same network)





::: The only current work around to this that I've found so far is within the stock messaging application. Once you notice that your message is going to be over 160 characters or more than one page, simply hit menu and add a subject to your message (can be blank). By doing this your message will be turned into a MMS message so that it can be sent as a whole instead of being split up. This works for now, but it would be nice to actually solve the issue at the source as this could get annoying after awhile.

 

[ortrigger]

The problem most likely lies in the ril files. The rom isn't recognizing that it is running on the vzw network and that is where the issue will continue to lie with this phone. Honestly, it's probably a bug we're going to have top live with if we want to continue using cm10. If it's a deal breaker for you, there are some pretty nice stock-based roms to chose from.

 

[tdm]

Got my wife a TF300 for Christmas and I tried enabling "Tablet UI" on my phone just for kicks to see how it looked compared to the real thing. Unfortunately, it didn't boot. Logcat shows it wanted to use the sw600dp resources but my ROM compression script deleted these.

I haven't seen anyone complain so I assume nobody has tried enabling "Tablet UI". But adding the tablet resources adds about 5mb so I am thinking about including them in the next beta.

Thoughts?

 

[sosaudio1]

You will need root for adb or you will need to change udev permissions. I never mess with udev, I just do "sudo adb start-server". Then you can access the adb server as any user.

After you do that and plug in the phone, what does "adb devices" say? Or "lsusb"?

Awesome.....so within the Spectrum-Freedom folder call "sudo adb start-server"? I think the last install of Ubuntu on my lappy I did do the UDEV changes.


*****NEVERMIND I AM ROOTED******

LET THE GAMES BEGIN!!!!!

 

[Neph81]

Got my wife a TF300 for Christmas and I tried enabling "Tablet UI" on my phone just for kicks to see how it looked compared to the real thing. Unfortunately, it didn't boot. Logcat shows it wanted to use the sw600dp resources but my ROM compression script deleted these.

I haven't seen anyone complain so I assume nobody has tried enabling "Tablet UI". But adding the tablet resources adds about 5mb so I am thinking about including them in the next beta.

Thoughts?

I'd be willing to have a few more MB of space be used if it means getting some features added it. I mean really, what else would we use that space for anyways.

 

[IMUcarmen]

Got my wife a TF300 for Christmas and I tried enabling "Tablet UI" on my phone just for kicks to see how it looked compared to the real thing. Unfortunately, it didn't boot. Logcat shows it wanted to use the sw600dp resources but my ROM compression script deleted these.

I haven't seen anyone complain so I assume nobody has tried enabling "Tablet UI". But adding the tablet resources adds about 5mb so I am thinking about including them in the next beta.

Thoughts?

I had thought about enabling that feature a few times but never did. Guess thats a good thing

I definitely support enabling it.

 

[ChuckL333]

The problem most likely lies in the ril files. The rom isn't recognizing that it is running on the vzw network and that is where the issue will continue to lie with this phone. Honestly, it's probably a bug we're going to have top live with if we want to continue using cm10. If it's a deal breaker for you, there are some pretty nice stock-based roms to chose from.

Its almost a deal breaker but I don't really have many options.. all of the other stock ROMs that I have found do not have Bluetooth working which is a must for me.

Maybe there could be a way to modify the default SMS application to auto convert messages to MMS once they get larger than 160 characters??? That would solve the issue here.

 

[reeseboy]

Got my wife a TF300 for Christmas and I tried enabling "Tablet UI" on my phone just for kicks to see how it looked compared to the real thing. Unfortunately, it didn't boot. Logcat shows it wanted to use the sw600dp resources but my ROM compression script deleted these.

I haven't seen anyone complain so I assume nobody has tried enabling "Tablet UI". But adding the tablet resources adds about 5mb so I am thinking about including them in the next beta.

Thoughts?

Yes please...

I'd be willing to have a few more MB of space be used if it means getting some features added it. I mean really, what else would we use that space for anyways.

^^That ^^
I couldn't have said it better myself.

 

[Neph81]

The problem most likely lies in the ril files. The rom isn't recognizing that it is running on the vzw network and that is where the issue will continue to lie with this phone. Honestly, it's probably a bug we're going to have top live with if we want to continue using cm10. If it's a deal breaker for you, there are some pretty nice stock-based roms to chose from.

Unless someone can provide a logcat of exactly what GoSMS is doing when this message send fails, then I'm not going to believe this is a RIL issue, especially when the stock SMS app works just fine. This sounds like it's a bad config issues on GoSMS apps end. I also don't believe they send thru their own server after the issues we had trying to get GoSMS to work on CM9 and it failed repeatedly.

Its almost a deal breaker but I don't really have many options.. all of the other stock ROMs that I have found do not have Bluetooth working which is a must for me.

Maybe there could be a way to modify the default SMS application to auto convert messages to MMS once they get larger than 160 characters??? That would solve the issue here.

The stock SMS app is already modified. These setting are coded into the SMS app when it's compiled.

https://github.com/thebigq/cm_devic...rlay/packages/apps/Mms/res/xml/mms_config.xml

 

[MrB206]

I can attest to the gosms issue. I had to turn on 'message split' for messages over 160 characters, but never had to before. I'm guessing it's an app issues with the OS, because a few other apps like rom toolbox are acting up too.

 

[sosaudio1]

So I installed CM10 then went to AOKP to see the difference and in AOKP, I couldn't get gallery to show anything....went back to cm10 because I can't handle pink unicorns (LOL) and wanted to see about the gallery issue and it works fine in cm10....

Thoughts?

Really wanting to see if I should go back to AOKP vs CM10 as well....what does everyone think?

 

[mrgoodpaul]

Is this happening to anyone else?

Every once in awhile when I pull down the status bar it flashes and when I swipe off a notification it flashes then too. It did this in both aokp and cm10.

 

[ChuckL333]

Unless someone can provide a logcat of exactly what GoSMS is doing when this message send fails, then I'm not going to believe this is a RIL issue, especially when the stock SMS app works just fine. This sounds like it's a bad config issues on GoSMS apps end. I also don't believe they send thru their own server after the issues we had trying to get GoSMS to work on CM9 and it failed repeatedly.

The stock SMS app is already modified. These setting are coded into the SMS app when it's compiled.

https://github.com/thebigq/cm_devic...rlay/packages/apps/Mms/res/xml/mms_config.xml

Actually, with the stock SMS app on both CM10 and AOKP it just splits the messages into more than one of over 160 characters. Is there anyway to have it switch to MMS as soon as it hits 161 characters?

 

[blueracer90]

Actually, with the stock SMS app on both CM10 and AOKP it just splits the messages into more than one of over 160 characters. Is there anyway to have it switch to MMS as soon as it hits 161 characters?

MMS sends over data while SMS goes over the network. People who aren't on an unlimited dataplan might not want that. I still have the unlimited so I don't care. I guess it also depends on how many long messages you send. I know that for most of my messages 160 is enough

 

[blueracer90]

Unless someone can provide a logcat of exactly what GoSMS is doing when this message send fails, then I'm not going to believe this is a RIL issue, especially when the stock SMS app works just fine.

Working on getting you a logcat. I have never done this so I am trying to google how to do it. NOOB ALERT!

EDIT: I know I am doing something wrong but I am using emulator in Rom Toolbox pro and when typing logcat to start it i get "Unable to open log device '/dev/log/main': Permission denied 1|u0_a80@android:/ $
Any hint on what i need to do?

 

[blueracer90]

Hey Neph81 got the logcat for you
https://docs.google.com/open?id=0Bze7ykIiCQ73ZlVlQlBSRUFTT1k

pulled it with logcat instead of through emulator. Let me know if this helps.

 

[Nokoko]

Actually, with the stock SMS app on both CM10 and AOKP it just splits the messages into more than one of over 160 characters. Is there anyway to have it switch to MMS as soon as it hits 161 characters?

I would not want it to switch to MMS, it seems like it's really just a convenience thing, the messages send just fine, they're just split up.Why is that such a big deal?

 

[Staticaxe]

So my only real issue with this ROM so far is the battery life. Seems to drain very quickly. I tried the deep sleep battery app but I didn't like the delay for wifi and data to come back on after unlocking the screen. Anyone using anything else on CM10 with success? Thanks!

 

[blueracer90]

So my only real issue with this ROM so far is the battery life. Seems to drain very quickly. I tried the deep sleep battery app but I didn't like the delay for wifi and data to come back on after unlocking the screen. Anyone using anything else on CM10 with success? Thanks!

I got 30 hours out of my battery with sending about 50 to 75 texts and some email checking. Data was on 4g or Wifi the whole time except for 9 hours while I was sleeping then I turned to airplane mode. Using deadline and conservative. Try that or powersave, but it will start lagging in powersave.

 

[ortrigger]

I keep mine clocked to 1242 with ondemand and deadline and get great battery life. I also turn off animations and keep my brightness down.

 

[Lykarsis]

I've got mine set to 1674 and ondemand, as long as I keep data switched off when I'm not using it, I get about 17 hours on CM10.

 

[MrB206]

I keep mine clocked to 1242 with ondemand and deadline and get great battery life. I also turn off animations and keep my brightness down.

Same here. I find underclocking suits my device better. It's a shame, but the jump to 1.512 really takes a toll on my battery.... Even with the interactive governor.