I've been using my phone for months already and have not experienced this...my messaging app always closes upon hitting the back button on my phone (GT-N7000)...a week ago I rooted my phone using the cwm.zip method and all was ok. I check for brick bugs (negative) and all the stuff are working fine...read the thread here saying cwm.zip can brick my phone I immediately looked for a solution...but before I installed a new kernel I tried installing busybox using the app called BusyBox Pro from google play...I noticed that when I open my messaging app and hitting the back button...it won't close, I'd have to go inside task manager and manually close it from there...I've also read some people saying that this was normal...does that mean that when I got my phone brand new that it wasn't normal because it was closing the app previously???
Anyways I tried flashing a new rom (stock ICS rom) (did not wipe I just flashed the stock rom from Mobile Odin) and did a factory reset afterwards...still the same...i did this twice with the same result...messaging app is still not closing properly. Now I have rooted my phone again using the safe method provided in this forum flashed the superSU and the busybox afterwards and flashed the Philz kernel using Mobile Odin as my final step.
I did find a way to fix this by ticking on the developer options "do not keep activities" and it does close the application when I hit back (I don't think checking the "do not keep activities" is also a proper fix anyways) but now this will leave me with another problem of the new message notification (1 inside the red circle) not going away even if all messages are already checked. Both situations are quite annoying so if anyone out there has any solution to this would be of really great help to us who has this problem...
I saw a few threads saying to replace the mms.apk file with a new one and they did say it fixed their problem...i dunno if this is a good idea but if it is where can I get the apk for the stock messaging app for ICS 4.0.4? would any expert recommend this? It does not have any CPU usage...only takes up RAM and I know this is not much of an issue but it is really annoying as hell and is weird.
as you already have flashed ics again, I am not sure of replacing the mms.apk will resolve the issue. anyhow the mms.apk can be found in rom you downloaded. open up the rom using 7z and the factoryfs.img file. now using sgs2ext4.jar and linux reader you can extract the mms.apk.
Other option is to install a wipe gb rom and the upgrade to ics again
Message App
nokiamodeln91 said:
as you already have flashed ics again, I am not sure of replacing the mms.apk will resolve the issue. anyhow the mms.apk can be found in rom you downloaded. open up the rom using 7z and the factoryfs.img file. now using sgs2ext4.jar and linux reader you can extract the mms.apk.
Other option is to install a wipe gb rom and the upgrade to ics again
Click to expand...
Click to collapse
I thought factory resetting would do the trick but done it twice and it did not...it was not like this before...wish there is a solution other than flashinig a new rom. By using a 3rd party app...will it disable my stock messaging app? maybe that will work what do you think?
like go sms or something?
nokiamodeln91 said:
like go sms or something?
Click to expand...
Click to collapse
yes i think...will that overwrite my messaging app or disable it or will I be having 2 messaging apps? sorry noob question.
What does wiping do? Maybe that's what I didn't do reason my message app stayed this way...
3 wipes
wipe cache
wipe data - same as factory reset
wipe dalvik
the wipe I mentioned was to format the system as we do on Windows and then install the new os again like fresh.
I don't know. May be you will have 2. but if the go sms is able to read your text messages as well the you can go in to application - all and disable the messaging
nokiamodeln91 said:
3 wipes
wipe cache
wipe data - same as factory reset
wipe dalvik
the wipe I mentioned was to format the system as we do on Windows and then install the new os again like fresh.
I don't know. May be you will have 2. but if the go sms is able to read your text messages as well the you can go in to application - all and disable the messaging
Click to expand...
Click to collapse
So factory resetting = wipe data right? and the cache and dalvik is not wiped in this process? hmmmm...I'm really wondering what the ^&(& happened to my messaging app and why this issue won't go away...really weird.
Anyways still trying to replace my stock mms.apk with something else...but none seems to work...i have set the permissions correctly but still I only get a black screen and then force closes after. Trying this method before resorting to a 3rd party app which I really am not into...I like my phone stock and clean and this abnormality in its performance is making me crazy. Sorry it's like an obsessive compulsive behaviour LOL.
I guess instead of trying so many things, it's better that if you install a wipe gb rom and then test the message app. If all ok and then upgrade to ics back
nokiamodeln91 said:
I guess instead of trying so many things, it's better that if you install a wipe gb rom and then test the message app. If all ok and then upgrade to ics back
Click to expand...
Click to collapse
I tried replacing the modified mms.apk from rocketrom v8 LRK build and still unsuccessful. Hmmm still trying to burn all possibilities before I flash a new rom again. Thanks!
I have tried installing a 3rd party SMS application and disabled the stock message application and still the problem persists. Will try one last idea afterwards I'll be off to flash a new GB rom and upgrade back to ICS.
Related
every time i restart my phone (on latest jpy 2.2.1)
my phone starts to vibrate, random apps close like google maps, handcent and doesnt seem to like what i do anymore with my phone
i really dont have a lot installed on my phone i even deleted every app i have
after a factory reset all is fine, but after awhile itr happens again
i just dont want to do factory reset all the time and re install and phone nrs etc
anyone else with this problem?
my phone is un-rooted jpy 2.2.1
Make a complete wipe/factory reset and reflash the firmware.
Mr.Hunk said:
Make a complete wipe/factory reset and reflash the firmware.
Click to expand...
Click to collapse
i have done this quite a few times allready and that i just dont want to keep doing,.. after reset and reflash it is ok for awhile but after a few months use im back at square one
Do you have any Lagfix enabled? Got start-up issues too after I enabled DATA_LOOP and BIND_DATA options. Just flash a Titanium Backup or disable this and make a factory reset after that.
Sent from my GT-I9000 using XDA App
blockbusta said:
Do you have any Lagfix enabled? Got start-up issues too after I enabled DATA_LOOP and BIND_DATA options. Just flash a Titanium Backup or disable this and make a factory reset after that.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i removed lagfix too on a previous time this all happened so i guess it hasnothing to do with that either
Make a clean phone format everything including internal sd and system .
Install Eclair and wait to see if problem solved .
Do not upgrade to 2.2.1
If the phone fails on Eclair then its hardware .
jje
JJEgan said:
Make a clean phone format everything including internal sd and system .
Install Eclair and wait to see if problem solved .
Do not upgrade to 2.2.1
If the phone fails on Eclair then its hardware .
jje
Click to expand...
Click to collapse
not so great news then...
i tried rooting when i was on eclair, because i had the problem since then already but i blamed it to eclair..
worth to send the phone off for repair then?
worth to send the phone off for repair then?
At least ask a Samsung Service centre .
jje
I had a similar problem when i was with 2.2.1 JPX (without any lagfixs) + root, sometimes when the I restared the phone everything started to crash, and I had to do a factory reset to fix those FC..
I've done a complete format (internal SD..) and flashed 2.2 with speedmod kernel (no lagfix) + root, and so far so good, i've made a lot of restarts, and no problem..
Foremost, I apologize if this has been asked and answered before. I've been searching for weeks...maybe I'm a bad searcher.
My issue is that I have been experiencing random force closings on random apps, including random partial reboots when unlocking the Unlock screen (screen freeze then goes to Rom intialization screen). Sometimes Dolphin HD closes when loading pages, same with stock browser and Opera Mini, though sometimes the same page will load fine (both with JS on and off and with Flash turned off in Froyo ROMs). Swype (v.2.15) will sometimes close when typing in the search widget or an SMS message in both ChompSMS and stock messaging app. Titanium Backup and Astro sometimes close when scrolling down the app list. The only consistant factor that I can think of is available RAM or the processor overheating.
I have installed multiple ROMs thinking its ROM-specific, but the same behavior manifests in each one. I've tried Assonance 5.2, Cognition 3.04, Phoenix 4.5 and Serendipity 5-1.4.
With each new flashing I first use Odin to get back to stock, then use Odin to Master Clear, then root the phone, then install Clockwork, flash it's recovery app and then use Clockwork to flash the new ROM.
I did fresh installs of any apps I installed from the Market as I know user data from 2.1 will cause issues with 2.2.
Because I thought it was a RAM issue I installed Autokiller Memory and used the 'Optimum' preset.
After all this I still have the same issues with random apps closing and the phone doing ROM reboots when at random times I unlock the phone. Can anyone give me some guidance?
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
diablo009 said:
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
Click to expand...
Click to collapse
I'll give your ROM a shot.
Stupid question - Do all ROMs have kernels and modems cooked into them? I was just thinking that I've been flashing tons of ROMs lately and I'm not sure of the most stable kernels to have.
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
avgjoegeek said:
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
Click to expand...
Click to collapse
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
DRoc740 said:
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
Click to expand...
Click to collapse
When u restore to stock, format the internal SD from within windows. (Ok, I won't contest anyone's arguments on this, but I personally find it easier than doing a master clear and to wipe off even the basic folders android os format creates.)
And, I would recommend u download a fresh copy of 5.5, with a kernel that does not have any OC in it, to play safe. 5.5 is available in two versions - one with OC kernel, and one with non-OC kernel.
It could be a case of kernel too. Try swapping kernel and see if that helps. Not all kernels go well with all hardware. That's the reason I swapped to xcalibur kernel as soon as I loaded 5.5.
I think, personal opinion here, u could do away with clockwork recovery too. U cud download the cwm console update.zip and put it on ur sdcard root. And apply the update.zip with in console in stock to load up CWM console. This is the most non-intrusive way of going to CWM console as far as I know.
I've been running stock since yesterday with zero issues. My force closing issue usually appears within an hour of flashing a new ROM so this is a very good sign that its a flashing and not a hardware issue.
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Maybe its a kernel issue as I think i've exhausted all other options. I'll try xcaliburinhand's v2.3.2 01.31.2011 and see if it works.
Any other suggestions?
DRoc740 said:
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Click to expand...
Click to collapse
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
diablo009 said:
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
Click to expand...
Click to collapse
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
DRoc740 said:
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
Click to expand...
Click to collapse
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not now be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
diablo009 said:
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
Click to expand...
Click to collapse
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
DRoc740 said:
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
Click to expand...
Click to collapse
welcome to the world of flashing. let me (us) know if u need any more help
diablo009 said:
welcome to the world of flashing. let me (us) know if u need any more help
Click to expand...
Click to collapse
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
DRoc740 said:
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
Click to expand...
Click to collapse
did you restore anything with titanium backup?
Pirateghost said:
did you restore anything with titanium backup?
Click to expand...
Click to collapse
No, didn't restore anything.
I flashed the update and had the force closings within a few minutes while I was typing an SMS using Swype.
Bumping
I have the same problem
Hello. I've got mu SGS for about an year. I recently installed an ICSSGS ROM on it and I enjoy it but it's kind of sluggish. Also a "low space remaining" notification appears and I don't know how to get rid of it.
I want to ask you how I can clear the internal 6 GB on my phone and make it run smoother(can I just delete everything or are there some system files?), how I can install the Semaphore kernel and a good ICS ROM for a smooth experience and some games.
Thanks in advance!
Monitox said:
Hello. I've got mu SGS for about an year. I recently installed an ICSSGS ROM on it and I enjoy it but it's kind of sluggish. Also a "low space remaining" notification appears and I don't know how to get rid of it.
I want to ask you how I can clear the internal 6 GB on my phone and make it run smoother(can I just delete everything or are there some system files?), how I can install the Semaphore kernel and a good ICS ROM for a smooth experience and some games.
Thanks in advance!
Click to expand...
Click to collapse
I think you would just go to Settings - Backup & reset, select Factory data reset.
This will put your phone back into the "brand new" state when it first came out of the factory.
You'll lose all your apps, data and custom settings that you've been using.
Best thing to do now is to flash a new ICS like Slim Ics, Dark knight 5.5 or TWICS (i've tried these and they are very good roms). You can download one of these rom into .zip archive, put it into your device and flash via recovery. After that, you can flash a kernel of your choice in the same way (if it is in .zip format) or through Odin if it is in .Tar format
Factory reset means wiping all data and apps except system apps and data.that will clean your phone from all apps u installed after flashing the last rom(of cause u wipe everything when installing a new rom) this will get rid of any lag or sluggishness u are experiencing.
But first try wipe cache and dalvik in cwm.
Next download "easy cache cleaner" from play store and clean your cache.this normally solves the problem
Ps. I know the adds are annoying,but it's one of best free cleaners. To get rid of the adds download "droidwall" and check the apps that need internet/data connection and apply.it's like a firewall only the apps u allow permission have internet/data connection
i recently upgraded ota from xxlpy to xxlrg. unit is original n7000 germany. never used Odin or such to install firmware.
the problem is, on every restart, the note will say that it is upgrading and installing new apps similar to what happens when the first boot after upgrading. this will take a long time to start from power off or reboot. verified this happens every time. this never happens before when i upgraded from gb to xxlpy.
everything else seem to run ok . i have root and unrooted using simple unroot with supersu without problem. i have titanium pro for backup but afraid to factory reset because of the brick issue. appreciate any feedback.
thanks.
muzz.
Sent from my GT-N7000 using xda app-developers app
muzzsharpe said:
i recently upgraded ota from xxlpy to xxlrg. unit is original n7000 germany. never used Odin or such to install firmware.
the problem is, on every restart, the note will say that it is upgrading and installing new apps similar to what happens when the first boot after upgrading. this will take a long time to start from power off or reboot. verified this happens every time. this never happens before when i upgraded from gb to xxlpy.
everything else seem to run ok . i have root and unrooted using simple unroot with supersu without problem. i have titanium pro for backup but afraid to factory reset because of the brick issue. appreciate any feedback.
thanks.
muzz.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
In the phone setting uncheck the automatic update.
jonpaslim said:
In the phone setting uncheck the automatic update.
Click to expand...
Click to collapse
nope. tried that just to make sure. that setting is for checking if there are any new updates available. thanks anyway. if you read my post again, what happens is that the upgrade to XXLRG (4.0.4) was successful, just that it does the first boot installation (s-memo, crayon. wallpaper etc) again and again on each reboot or start from power off. this makes reboot taking more than one minute. others have same problem?
any guru here have some clue?
tia
muzzsharpe said:
nope. tried that just to make sure. that setting is for checking if there are any new updates available. thanks anyway. if you read my post again, what happens is that the upgrade to XXLRG (4.0.4) was successful, just that it does the first boot installation (s-memo, crayon. wallpaper etc) again and again on each reboot or start from power off. this makes reboot taking more than one minute. others have same problem?
any guru here have some clue?
tia
Click to expand...
Click to collapse
nobody having this problem of XXLRG reinstalling apps?
anyway, today another OTA notification saying theres another update.
should i go for it?
regards,
You need to do factory reset. Either to go back to GB and then do wipe, or flash a safe ICS kernel (speedmod, notecore, franco, etc) and do full wipe in recovery. Never do factory reset or full wipe in stock ICS.
kopitalk said:
You need to do factory reset. Either to go back to GB and then do wipe, or flash a safe ICS kernel (speedmod, notecore, franco, etc) and do full wipe in recovery. Never do factory reset or full wipe in stock ICS.
Click to expand...
Click to collapse
can you please explain why i need to factory reset?
muzzsharpe said:
i recently upgraded ota from xxlpy to xxlrg. unit is original n7000 germany. never used Odin or such to install firmware.
the problem is, on every restart, the note will say that it is upgrading and installing new apps similar to what happens when the first boot after upgrading. this will take a long time to start from power off or reboot. verified this happens every time. this never happens before when i upgraded from gb to xxlpy.
everything else seem to run ok . i have root and unrooted using simple unroot with supersu without problem. i have titanium pro for backup but afraid to factory reset because of the brick issue. appreciate any feedback.
thanks.
muzz.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
if your getting every reboot on your phone 'Android is upgrading applications..', case here is that you have some apps (I would guess you restored apps from titanium pro) that are deodex and some are odex. Check on your apps again under titanium apps and delete all odex files extension for the same app name. There might be one or more apps that have odex files inside. This is the cause of that message everytime you reboot your phone.
Or the simple way is go back to Stock GB, upgrade again to XXLRG and when you have everything already flashed to LRG.. DON'T restore apps anymore (from your Titanium backup), go clean from now on in just redownloading those apps you have fresh in Google play.
Cheers!
I've got a GT-I9350, and I've been on RipperROM for a while, and I just flashed v20 onto my phone.
Now I can't receive any phone calls at all, the ringtone goes, but the screen goes black, then com.android.phone crashes.
Tried wiping my data, clearing google framework, all that, still doesn't work. I'm in desperate need of help this is killing me.
Try reflashing the rom or install your back up
Tried both, tried downloading a fresh version of RipperROM, wiped all my data, cache, dalvik, several times, fixed my permissions, and it's still crashing.
lankks said:
Tried both, tried downloading a fresh version of RipperROM, wiped all my data, cache, dalvik, several times, fixed my permissions, and it's still crashing.
Click to expand...
Click to collapse
Use another rom .
Or reach ten posts and ask in the rom thread .
lankks said:
I've got a GT-I9350, and I've been on RipperROM for a while, and I just flashed v20 onto my phone.
Now I can't receive any phone calls at all, the ringtone goes, but the screen goes black, then com.android.phone crashes.
Tried wiping my data, clearing google framework, all that, still doesn't work. I'm in desperate need of help this is killing me.
Click to expand...
Click to collapse
i'm using ripper rom v20. I was not have a problem like u. Somebody used ripper rom give me opinion about battery drain?
hoangphi0311 said:
i'm using ripper rom v20. I was not have a problem like u. Somebody used ripper rom give me opinion about battery drain?
Click to expand...
Click to collapse
Don't know why I'm getting this and you're not, but I think it's a repeat of a known problem in the i9300 posted here:
http://forum.xda-developers.com/showpost.php?p=33003918&postcount=2683
It doesn't happen if I haven't flashed JB Domination Theme btw.
In general I'm getting FC in almost every rom I flash. Really don't know why it's gone this bad. I switched from PA to RipperROM because my phone app started suddenly acting up.
Now since this post I've tried a few roms.
Flash PA -> get a crash trying to log on to google account (google framework FC)
Flash Sentinel -> ASOP Keyboard FC, can't write anything, back button doesn't work
Flash RipperROM -> I have a functional phone as long as I don't flash any themes, don't trust this to last at all
Should I go back to stock in odin and then root again?
lankks said:
In general I'm getting FC in almost every rom I flash. Really don't know why it's gone this bad. I switched from PA to RipperROM because my phone app started suddenly acting up.
Now since this post I've tried a few roms.
Flash PA -> get a crash trying to log on to google account (google framework FC)
Flash Sentinel -> ASOP Keyboard FC, can't write anything, back button doesn't work
Flash RipperROM -> I have a functional phone as long as I don't flash any themes, don't trust this to last at all
Should I go back to stock in odin and then root again?
Click to expand...
Click to collapse
There is a stock pre-rooted rom for odin.
Maybe try Slim Bean rom?