All SMS apps Full Closing on OpenSensation Nightlies - HTC Sensation

Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.

toejam316 said:
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
Click to expand...
Click to collapse
Might be an issue with OpenSensation (as you're using nightlies). Back up what you have, format everything but SD card, and I'd recommend trying a completely different non-nightly ROM, try AOKP m6. This way you can see if the SMS issue is related to OpenSensation or not. backup m6 THEN try the newest OpenSensation nightly to see if the issue is fixed. This way you'll likely be left with at least one ROM you can restore with working SMS functionality.

I might yet have to do that, although I would prefer to stay as close to vanilla as possible, that's why OpenSensation interested me - I think I'll try regressing to the CM9 RC2 on the official Cyanogen mod website first, then try other projects after that if that doesn't work. Does seem strange that no one else is complaining of this issues though, and I really can't see myself being the only one running the latest versions.
Oh yeah, the newest nightly and Tamcore kernel didn't work - the only thing that's changed is now I know I can't regress directly to my ARHD backup, yay!
This one's a bit of a thinker.

Well, I did a full wipe, installed the latest HyperSensation CM9 build and reinstalled the TamCore Kernel. Everything seems to be working now.
Thanks for the input, thread can be closed.

Related

[ROM] DamageControl v1.0 - Sense 2.1 w/video rec - LIGHTNING FAST! - 100% complete!

DamageControl Sense 2.1 ROM - Espresso optional! - 100% complete!
PLEASE READ THIS POST BEFORE YOU POST!!!
This ROM is now 100% for a reason! Please read below!
Why is this 100%
There is a fix for *nearly* every problem - just search the thread!
For things there isn't a fix for, there is a workaround that works better
The rest of the problems are problems that cannot be fixed until there is a better leak, we get our hands on the source of the kernel, or Sprint releases something. However, it should be noted that the problems are extremely minimal. Microscopic, even.
EVERYTHING IN THIS ROM IS FUNCTIONAL/SIZE]
There are workarounds to nearly everything. Things that cannot be fixed are problems with the leak itself. There is really no reason not to upgrade to this ROM as far as functionality is concerned - problems are MICROSCOPIC!!! If you believe the Sprint update really is going to come in two weeks, go ahead and use this ROM now! Changing to the official one will be easy!
This thread is 225+ pages long, you CAN and WILL find a fix to find a fix if you look for it!!!
Installation Steps:
-Download whichever ROM you want between Espresso or Normal (Decaf?)
-Rename the file to update.zip and flash like you would any other ROM. Note: it may be a good idea to wipe EVERYTHING!!! You MUST flash if you are coming from a different ROM.
If the ROM fails to boot, wipe your ext partition!!!
To get Apps2SD (Applications are stored on your SD card - must be partitioned!
-PARTITION YOUR SD CARD
MMS Problems?:
-If you have MMS problems, download this: http://damageless.kingspond.com/signed-mms-fix.zip
-Rename to update.zip and flash it to your phone.
-NOTE THAT HANDCENT WILL NOT SEND MMS!!! THIS IS NOT SOMETHING WE CAN FIX!!!
Other reported problems:
-Handcent will not send MMS. This is a problem with every 2.1 ROM and is not something that we can fix.
Tethering:
-Wifi tether is included.
-If you refuse to tether using wifi, you can use EasyTether Lite or something similar that is available in the Market.
Worse signal?
-You do not have a worse signal because of this ROM. It has less bars at the top.
Apps force closing all the time?
-Boot into recovery, go to Other and select the Fix UID option.
Invalid authentication with Google
-There is something wrong that is fairly deep, but it is a problem with the leak of the Eris 2.1 ROM. This only happens when you have a message or voicemail waiting.
Voicemail notification
-Go into the menu, then go to settings, click the call menu and then click Clear Voicemail Notification. Also make sure you change the voicemail service number to your own number!!!
Visual Voicemail
Use Google Voice or Youmail. We need something from Sprint to get Visual Voicemail to work.
Battery Life
Your battery life shouldn't change much. If you are experiencing problems, try the 'airplane mode' fix, and check your CDMA PRL settings.
Other Problems?:
-Try rebooting.
-If that doesn't work, backup your device through nandroid and then wipe everything!
-Search, then post. There are over 1,000 posts here, most likely someone has experienced the same problem as you.
SEARCH THE THREAD!!!
FAQ
Why won't Handcent send MMS?
Because it is an incompatibility issue.
Why can't I send MMS?
Because either you are not on Sprint or you need to apply the fix.
What is the difference between Espresso and the normal version?
Check the screenshots.
What about Visual Voicemail?
Until we get something from Sprint, this won't work. However, you can use Google Voice or you can use Youmail. Both work great.
My Google Voice doesn't work!
Use version 0.20 to fix it.
Bank of America, other apps don't work
Looking into this problem...
Superuser shows up blank
Make sure you have debug mode on.
What's Next for this ROM?:
I will continue to update this ROM with small fixes and things that are nice, but I consider this fully functional. I am going to work on smaller things that will enhance the ROM a bit. This isn't the last update!
About this ROM:
I decided to make this ROM after some other ROMs just weren't working out for me. Things were far too buggy, didn't seem to work very well, and it all seemed a little clunky. I decided that I would try to combine the best of the ROMs, not doing it the typical way (by just combining stuff I like), but by combining things to make it functional. This ROM is meant to be fast, stable and reliable. I will not add things that will load down the system or kill battery life.
I decided on the name (with help) because of the recent problems on XDA. The community was not united, and I thought the best way to unite everyone was to bring in a new ROM with a new vision and focus. This ROM has been incredibly successful in this way, thanks to those who started this ROM's thread out the right way. I believe we have a lot of good spirit here and we can continue with the attitude of helping one another and helping one another out, all personal interests aside.
I hope that you enjoy this ROM and find that it suits your needs.
Make sure you wipe if you are coming from a different ROM!!!
Microscopic quirks:
Trackball light intermittent
Asks you to log in when you have some type of message waiting
Special thanks goes to Avalaunchmods, gbhil, flipz, and everybody who has helped out and to every community member who has been supportive and uplifting! Each of you have helped in your own ways, and that is the essence of a true community.
Last updated on:
3/11/2010 at 10:55 PM - Normal!
3/11/2010 at 12:42 PM - Espresso!
Latest ROM:
1.0
Download here:
Build: 3/11/2010 10:55 PM
http://www.4shared.com/file/239487830/f20cf9b3/signed-DamageControlv1.html - v1.0
Torrent: http://members.cox.net/morbidpete/signed-DamageControlv1.zip.torrent
Mirror: http://onecoolpuppy.net/roms/signed-DamageControlv1.zip
Mirror 2: http://www.megaupload.com/?d=8EKNO308
You may need to wipe ext partition!!!!!
Screenshots:
http://damageless.kingspond.com/damageless_normal.png
http://damageless.kingspond.com/damageless_programs.png
http://damageless.kingspond.com/browser.png
Espresso:
Build: 3/11/2010 11:30 PM
URL: http://www.4shared.com/file/239506647/6a2728dc/signed-DamageControlv1Expresso.html
Torrent: <not yet available>
Mirror: http://onecoolpuppy.net/roms/signed-DamageControlv1Expresso.zip
Mirror 2: http://www.megaupload.com/?d=DWTY7FKB
Screenshots:
http://damageless.kingspond.com/expresso.png
http://damageless.kingspond.com/expresso_programs.png
http://damageless.kingspond.com/browser.png
I am usually not someone who asks for donations, however I am getting married soon and it certainly wouldn't hurt. You can donate whatever by clicking here. I strongly believe in open source and in developers working together towards a common good. I hope you all enjoy the ROM and that we can build this together.
Super-Special thanks goes to gbhil!
Scheduled Update: 3/12/2010???
Changelog (as of 0.999):
v1.0
Apps2SD
Memory settings
Multi-touch Maps
Default IM App
More bugfixes (MMS, etc)
Genie widget
Updated busybox
Misc. bug fixes
Version 0.9999
Adobe Flash updated to 10.1
Minor bugfixes & updates
Updated Market
Updated HTC Framework
Bug fixes
Video???? No way
It actually records?
Dam that's why I though I had some problems with my ADB but yes I agree with u in couple things I think the Rom is a lol crude but hey this guy did a great work making the cam work so maybe that is the reason why he miss somethings
Yes way. Try it.
damageless said:
The only reason I did this was because I was very disappointed in the ROM that flipzmode released because of how many things he broke trying to do his own thing. I was hoping he would release something functional before he decided to go mod everything but oh well.
Click to expand...
Click to collapse
Uh, what did I break?
damageless said:
Yes way. Try it.
Click to expand...
Click to collapse
does this one fix the sms errors that is the only problem i have with fresh.
i have to have less then 30 messages or it doesn't let me send any
flipzmode said:
Uh, what did I break?
Click to expand...
Click to collapse
Check your thread. I got your Rom this morning and loved it except there were too many bugs. I don't mean any disrespect. I will probably switch to your ROM when you get it worked out.
More 2.1 oh joy. Does this Rom fix the Facebook sync bug?
Good intentions, but way to burn the person responsible FOR EVERYTHING IMPORTANT WORKING! In the future try to not offend the real devs.
All that aside, I'll give it a try and let you know what I find.
brian2220 said:
does this one fix the sms errors that is the only problem i have with fresh.
i have to have less then 30 messages or it doesn't let me send any
Click to expand...
Click to collapse
I am honestly not sure. You tell me.
Wow, video recording does work! Nice job!!!
beyondinferno said:
Good intentions, but way to burn the person responsible FOR EVERYTHING IMPORTANT WORKING! In the future try to not offend the real devs.
All that aside, I'll give it a try and let you know what I find.
Click to expand...
Click to collapse
As I said, I don't mean to offend anyone. This simply worked for me and I thought others would be interested.
wow...ev3erything works.cam n video...thanx......fast too...more test will report back.work with new radio too
ADB works fine as long as you have the latest HTC Drivers from the HTC Sync software install and you set your phone to HTC Sync mode.
I can confirm protected and paid apps show in the marketplace. I can see...
- Google Goggles
- Twidroid
- ChompSMS
- Reality Browser 3.0
- Weatherbug Elite
- ShopSavvy
- Barcode Scanner
...and others too.
Nice!
I will clean it up a bit tomorrow and do some "real dev" work - (I have the skills but not th
PHP:
e time) so if you do find problems I may fix them in another release. But like I stated, I do not have the time so I will not maintain this over time.
damageless said:
I also realize I did very little to this ROM. I never claimed it as my own. I will clean it up a bit tomorrow and do some "real dev" work - (I have the skills but not the time) so if you do find problems I may fix them in another release. But like I stated, I do not have the time so I will not maintain this over time.
Click to expand...
Click to collapse
You're the first to fix video recording! I wouldn't call that "did very little".
Why would people even make any 2.1 roms after flipz roms?
His Roms are like the best no one can competite with him
Does wifi work for anyone? I can't seem to get it to start on this rom. It errors saying: "Unable to start Wi-Fi"
damageless said:
Alright, all I have done is taken some things from the gumbo ROM and the Fresh ROM to make a fully functional (as far as I can tell), 2.1 Sense UI ROM, signed it, and here it is for someone else.
I'm not sure if this will be useful to anyone or not. I will not maintain this ROM as I do not take any credit for doing anything other than combining some files and signing it. I am also going to modify a few things to get it working a little better and tweak it a bit, but it isn't something I plan on maintaining.
The only reason I did this was because I was very disappointed in the ROM that flipzmode released because of how many things he broke trying to do his own thing. I was hoping he would release something functional before he decided to go mod everything but oh well.
The one thing I have noticed is that ADB doesn't recognize the device. This probably has something to do with the kernel but like I said, I'm not providing support for this, just providing the resource. I'm sure something better will be released soon, but what the heck.
Again, I am not taking credit for anything here. Please donate to those who created the ROMs.
I should mention that I haven't tried visual voicemail and I am guessing it isn't working. Not sure if we have to wait for Sprint to come out with something or not.
I should mention that I have gotten Sprint TV to work on this, I'm not sure why other people are having problems. However, if you want Sprint TV, then you should simply copy the apk from your old ROM to the new one.
I will also update this to include apps2sd tomorrow. Also maybe get adb working. - I don't consider these to tools to be something that people use on a day-to-day basis which is why I call this fully-functioning. I also haven't fully tested everything, but as far as I can tell, everything works.
It is nice to have camera and video recording, though. All apps seem to show up in the Market. It does show Verizon stuff, and I need to make sure everything is on Sprint, but I will update it tomorrow to be a bit better. This is just a quick release. I will clean it up a bit, add some things to make it more functional and then release a better version.
Download here:
http://www.megaupload.com/?d=2BL7DNHS
Click to expand...
Click to collapse
Would you mind listing what exactly works I'm this Rom that did not work in Fresh 2.0b?
I am a little confused as to what exactly this Rom contains, and what gap you are attempting to fill by posting it.

[Q] CynogenMod 7 issues on the GTablet

I apologize if this is the wrong area for these questions. I'm having a few issues with my installation of CM7. I've tried looking in several places, but nothing seems to address my problems.
First thing I noticed upon installation was that I was never asked to set up my touchscreen or input my google information. I tried doing this manually by adding an exchange account, but that would not work. I next tried looking for my apps to see if they installed automatically this time around or not and none of my previous apps show, nor does market exist anywhere. Without any instance of market to be found I can't use any of the market fixes. However, without an inputted google id I don't think that would have mattered.
Can anyone guide me to where I can find help for these issues or post any possible solutions?
http://goo-inside.me/gapps/gapps-gb-tegra-20110118-signed.zip
Google apps - Flash right after you flash CM7. You might have to bypass the setup, but should be able to open the market and input google login. It won't auto download, but you'll have some market access.
http://forum.xda-developers.com/showthread.php?t=919958
Read the dev thread for other issue and such, don't have the time to dig through and help further.
chaelamity said:
I apologize if this is the wrong area for these questions. I'm having a few issues with my installation of CM7. I've tried looking in several places, but nothing seems to address my problems.
First thing I noticed upon installation was that I was never asked to set up my touchscreen or input my google information. I tried doing this manually by adding an exchange account, but that would not work. I next tried looking for my apps to see if they installed automatically this time around or not and none of my previous apps show, nor does market exist anywhere. Without any instance of market to be found I can't use any of the market fixes. However, without an inputted google id I don't think that would have mattered.
Can anyone guide me to where I can find help for these issues or post any possible solutions?
Click to expand...
Click to collapse
As the previous poster said, install Gapps. That will give you the setup screen the first time you reboot the GTab. As a word of warning, I wasn't able to bypass the first screen (touch the droid) on the main version posted in the development thread (the Beta05), even with the click around the screen. I was able to get past it right away on the "offical" build in post 18 of that thread, however (Beta01).
Let us know if that doesn't fix your problem.
Thanx alot guys. I was finally able to get market going by installing gaps and using the CyanogenMod 7 bet01. I ran into the seup screen issue with the Beta05 just like you warned. I didn't do the full market fix as everything I wanted was readily available. I'm not even sure if the full market is absent or not.
I am noticing that after you mount the USB connection you can't unmount. Also, my internal storage isn't recognized. I think there were fixes for some of this in Beta5. Is there a way to update to Beta 5 without having my previous problems or some other fix for the USB and storeage issues to anyone's knowledge?
flash to vegan5 and you will be way happier.
I tried CM7 and it had so many issues.
Once you flash vegan5 you will actually enjoy your tab
You can try flashing beta5 over beta1 and clear cache/dalvik. I'm not sure if that will work, but would be my best suggestion.
On the other hand, I actually agree with the previous poster saying that vegan is probably the better option at the moment. It seems much more stable and feature complete, even if it is froyo instead of gingerbread.
Either way, make a nandroid backup so you can go back if things go sideways.
I didn't get to post this before the responses. I did actually go ahead and flash over Beta01 with Beta05. I just didn't wipe the data or cache. Everything came back just fine. This fixed the storage and usb issues in Beta01. However, you have the previous audio issue from older builds where you have to plug in headphones and unplug them to get the audio back. I've tried VEGAn 5.1 and it works awesomely. I'm merely choosing aesthetics above overall functionality.
My tab has been delegated to fancy entertainment device (comics, casual browsing, games and video). It does all I need for now. I figure since VEGAn and CM7 are joining forces, why not do the switch early and test it out. I love where they're going with this ROM. I can't wait to get my grubby paws on a finished product.
Again, thanks big time for all the assistance. I generally skulk and read through the threads, but I love this place and all that everyone provides for the lesser technophiles like myself.
I thought maybe I could post my own problems to this thread?
So I'm on cynogen 6.1.1 on htc evo 2.2.1 kernal [email protected] #1
Anyway... I've tried 3 times to install the update to 6.1.2 today and each time it's gotten stuck around 58%. Any links to places I'm sure are there and I just couldn't find?
Also, for some reason, for the first time since I got my evo, I'm getting TONS of errors when attempting to send sms. theres a pink like traingle with a ! in the middle. Any suggestions?
How do I fix the bug with the camera?
You can email me if you like, at [email protected].
I am sort of inbetween a newb and whatever the next level would be, lol. This past week I was able to root, and install a custom mod, AND install an update to that customed mod (which is the one i'm on now) all w/o ever posting any questions to any forums. Hopefully that'll get me some brownie points?
Please PLEASE please!! I will even paypal $10 once I get this resolved.
On bended knee I beg (im not really this dramatic in real life )
Strlite85
strlite85 said:
I thought maybe I could post my own problems to this thread?
So I'm on cynogen 6.1.1 on htc evo 2.2.1 kernal [email protected] #1
Anyway... I've tried 3 times to install the update to 6.1.2 today and each time it's gotten stuck around 58%. Any links to places I'm sure are there and I just couldn't find?
Also, for some reason, for the first time since I got my evo, I'm getting TONS of errors when attempting to send sms. theres a pink like traingle with a ! in the middle. Any suggestions?
How do I fix the bug with the camera?
You can email me if you like, at [email protected].
I am sort of inbetween a newb and whatever the next level would be, lol. This past week I was able to root, and install a custom mod, AND install an update to that customed mod (which is the one i'm on now) all w/o ever posting any questions to any forums. Hopefully that'll get me some brownie points?
Please PLEASE please!! I will even paypal $10 once I get this resolved.
On bended knee I beg (im not really this dramatic in real life )
Strlite85
Click to expand...
Click to collapse
My suggestion would be to ask somewhere more appropriate. This thread is for a different version of CM, on a different device all together.
Try checking out
Evo dev
http://forum.xda-developers.com/forumdisplay.php?f=653
Evo general
http://forum.xda-developers.com/forumdisplay.php?f=620
CM
http://forum.cyanogenmod.com/forum/47-htc-evo-stable-mod/
lockedup
after I flashed Cm7 I get stuck on boot screen with the word android on the screen any body have a fix?
dexter230 said:
after I flashed Cm7 I get stuck on boot screen with the word android on the screen any body have a fix?
Click to expand...
Click to collapse
This usually means the installation was corrupted in some manner.
And it's usually because of a corrupt zip one would flash with.
You can reflash cm7 with another fresh downloaded file if you still have access to recovery mode.
Which I think you should be able becase the boot up process makes it up to the "Android" Bootscreen before it starts bootlooping.
From Advanced Recovery mode you can mount the USB option for the SDCard then transfer the fresh DL to your SCDard that way.
Also make sure you are using bekit's version .8 of CWM while in recovery mode.
Grab CWM v.8 from here
Other versions of CWM don't work well with the GTAB.

Wind P999 eagles blood update

Hi P999 users. Ive been experimenting with the Eagles Blood ICS ROMs and wanted to post some of my findings. I am not allowed to post in the relevant developer area where a detailed report would be useful so I will just post my feelings about the ROM's here for the next few weeks, until I am allowed to post more useful information.
I started out on the CM9 version of Eagles Blood, and then switched to a nightly AOSP ROM two weeks ago. I wanted to find out with AOSP was all about. This build felt very smooth. However crashes and force closing have cropped up in the past few days and this made me feel uncomfortable with the ROM's stability.
An update was released on the 20th so I felt the need to backup with Titanium and install the new ROM.
While installing the new ROM I read a notice in the changelog which confirmed my suspicion about the frequent new force closing. It seams there was some file corruption happening in previous builds... Maybe this was the reason mine was having issues??? How do I feel about this?
Anyways, after installing the newer ROM, and restoring my backup things were out of whack. Something about the restore had left some systems settings unusable and my Data connection was not working. Everything was force closing, even the android keyboard. I re-wiped and re-installed the ROM and backups with the same issues.
I decided to go back to build 4.0.3 and things have been good since. I had a feeling my Titanium backup was ruining my AOSP installations so this time I took a selective approach to restoring apps and did not restore system settings. My data connection is working again and my apps are working well. (Just to be clear I went back to the CM9 based version of EGB and not the AOSP version I was using which became unstable over time)
I do appreciate the AOSP development on behalf of EGB team but will be staying with the CM9 build for stability sake until file corruption issues are dealt with.
And that's how I feel about that.
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
good job
mt3g said:
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
Click to expand...
Click to collapse
MT3G thanks writing verbatim the solution I wrote into the OP.
*edit* the file corruption issue and the titanium backup fiasco are not related. It is my understanding that EGB team is aware of corruption cause by the early ASOP release and that they are working on it. I've decided not to use the AOSP version until they take care of it. (Solution / Workaround #1)
Maybe this is a big issue for someone who would not make the connection between restoring a system backup and the data connection not working anymore. I felt this was good information and that's why I posted it (Solution / Workaround #2)
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
exactly my thoughts, most people wold just freak out and say the rom was stupid or something, I read the post as he was saying he is going to wait for EB team to fix the issue where as it isn't going to be "fixed" lol. Unless you are updating the same rom or a rom that hasn't been extremely updated then it's possible for it work out okay. But using cm7 backing up and then going to cm9(4.0.x) and restoring is going to be a no go probably. i'm with Buru though except I just stay away from TB all together, I only use about 12 apps and no games.
update
Just a quick update. Its been almost 3 weeks on the EGB CM9 build 4.0.3. I've been very happy with it. Occasionally I install updates and I get strange behavior after. I've found that rebuilding permissions after an update is a good practice.
buru898 said:
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
Click to expand...
Click to collapse
I have restored email (with all accounts, data and app) as well as saved wifi locations before. I believe both of those are system settings and they never caused problems.
Sent from my LG-P999 using XDA
Try using GoBackup for apps, contacts (if you don't sync to your gmail), and some system settings. I like it more than TB. I'm not saying it won't cause FC's and that's because I don't know. But it might work better.

[Q] Messaging app not moving latest sms to the top

Hi,
I upgraded my Tab to 4.1.2 and have been having problems with my SMS. The Messaging app is not moving the thread to the top when a new text comes in, only when I reply.
ie the 10th thread in my list continues to be at the 10th position after receiving new messages. It doesn't get moved to the top which it used to. I thought it was a problem with the app and tried using Handcent. The same problem persists. It seems like there is something wrong with the time stamp of the thread not updating properly or something.
Anyone has any idea what's going on or what a solution might be? It's a big annoyance.
Thanks!
Hep, have this problem too. Very annoying.m I think samsung is doing this on purpose to force us to buy a new tab. Even though the 7.7 still holds it ground with the latest device.
Samsung is probably slowing things down on purpose too for this tab. I still notice a little lag.
I have the same problem.
same problem here, already tried a full flash (JB) still the same, i thought it was just GO SMS but I already uninstalled and and the problem persist, it's so annoying when you have to look for the one who sent u sms
In XDA, you'll find a mod to correct the date-time stamp for stock de-odex MMS.apk.
There are some simple guides, but you must be rooted first and most likely de-odexed.
Sorry, don't have the time right now to actually do a JB version for you, and also unable to test without device model (assume you have P6800).
I have previously modded a P6800 ICS app here : http://forum.xda-developers.com/showthread.php?t=2204628. 122 dl, and ZERO feedback. Didn't even know if it worked.....can only assume so.... This is not for JB, won't work. The JB MMS.apk needs to be modded.
It may not even solve your problem. But hey, at least there's a 'possible' solution if you're willing to try to mod yourself
Sent from my GT-I9500 using xda premium
I can't even begin to imagine how to mod an app. my skills are limited to just rooting and flashing roms. If I flash a custom ROM, say Cyanogen, will it fix the problem???
ok, I contacted Samsung about it and their advice was to do a complete factory wipe. I backed up my SMSs and tried it. After restoring the messages, everything was fixed. so there's the fix. but at the cost of having to restore everything after a complete wipe
Android sucks. Its the only os that forces u to do a full wipe for each updates.

Installed CM11 - everything else seems to work great, Chrome crashes immediately?

So, I'm obviously not remotely an expert when it comes to Android mods, but I'm finally fed up with being stuck on Android 4.1 - since it doesn't appear we'll ever get any upgraded qwerty phones ever again, I figured I'd try diy'ing it.
I have successfully flashed TWRP, rooted the phone, and installed what I believe(?) to have been the most recent version of CM11 (I figured it'd be cleanest to keep the phone closer to what it was designed for - I've seen tons of apps require 4.4 at minimum, not too many that require 5+): cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip. Was the most recent version I could find, anyway?
I booted it up and for the most part, everything seemed to be working. Everything except Chrome, which crashes reliably and immediately. I tried clearing all the caches (the app's cache + data, and the phone's, from recovery), uninstalling and reinstalling Chrome, I tried the beta version (crashes), I tried a fork, Brave (crashes). Other browsers are working fine, but I like Chrome.
One weird thing I did notice: I was thinking it might be a gapps issue, but weirdly, the Play store, gmail, maps, everything else just installed and seem to work out of the box before I did anything with gapps? I did also try flashing the most recent base 4.4.4 gapps zip from what I could tell (gapps-444-base-20170209-1-signed.zip), but I'm not sure how to tell if it actually did anything? It said it flashed successfully, but (other than having to wait for all my apps to recalculate because I cleared all the caches), nothing noticeably seemed to change on the front-end as a result, and yes, Chrome still crashes. Should I be using a different gapps install than that for the Photon Q? Or anything else I should check/try? Thanks!
Yay! Answered my own question, with sufficient digging!
Answer seems to be basically: the newest version of Chrome (v55) exposed some sort of weird incompatibility with CM, so the easy fix is just not to use it, at least for now. I sideloaded Chrome v54, and it stopped crashing, yay! Source: https://forum.xda-developers.com/showpost.php?p=70762641&postcount=198
Just FYI, the latest version available for this device is CM13.
They are working on Lineage.
Edit - seems you found the CM13 thread already
Yep - I'm glad to see people other than (and smarter than) myself recognize the Photon Q's unique place as being the final and, sadly, best qwerty slider available for our use, and that it therefore needs to be actively maintained even if Motorola won't... I just figured it'd be better to use an OS closer to the one the device was intended to be used with. Once I'm done testing CM11 out on my old half-working phone (re-purposed to a test phone) and push it to my new fully-functional one, I will probably at some point upgrade that first phone to the latest to try it out (probably once a Lineage build comes out, so I can be on a build that's actively being maintained). For right now, though, I figured I'd stick with CM11. Any case, looks like CM13 exposed the same Chrome issue, anyway.

Categories

Resources