Related
Hello,
I am using a Non rooted Rogers canada samsung captivate.
I recently upgraded through KIES to Froyo.
The two issues I am having are:
1) Wifi, i use juice defendor, so when i enter my house wifi is enabled automatically, many times, there is an error, and i cant click wifi on until a reboot, then it works fine for a while until it will happen again.
2) The notification bar doesn't slide down at times, and the only way to fix this is by rebooting. These two things are very annoying as they happen on a daily basis, or every other day.
I have seen these issues happen to others, so I know im not the only one, but I cant find a solution anywhere.
Any help would be appreciated.
anything i can do? would a factory reset help and a full reinstall?
Bigal77 said:
anything i can do? would a factory reset help and a full reinstall?
Click to expand...
Click to collapse
It might but to be honest I have never seen a stock rom that is not buggier then any custom rom i have run. What you could try is start from scratch and see if the prob happens on an out of the box set up. If it does then it is an issue with the rom, if not then install your apps one by one to see if one of them is covering it. My advice? Grab one of the custom roms build from the Rogers 2.2 update like Cog or Firefly.
Try uninstalling juice defender.
I had the same problem with notification panel not sliding down after installing juice defender. I uninstalled it and the problem went away.
Did you solve the problem with the notification dropdown? Was it Juice Defender? I am experiencing the same issue.
I have problem number 2 too. No juice defender or any power saving tool or what not running in the background. Happens only once in a while although so its not killing me
Same problem here. I can't pin it to a specific program. But I think it has something to do with a certain notification because it always does it when I download a program or install a new program.
I've experienced both but after OCLF (which requires root) the notification bar issue doesn't happen. I've recently moved on to a stock kernel injected with voodoo lagfix (courtesy of supercurio) after having tried speedmod which gave me horrible battery life.
My battery life is good enough that I just leave wifi on all the time to avoid issue #1. When the wifi issue happened, going to airplane mode and back would fix it too without a full reboot.
k the best thing to do in your situation as people new to xda is if you are unrooted and want to stay that way go into the rogers store and say your touchscreen is buggy which to me seems like the issue you are having. also if your on the stock rogers 2.2 as i was for a coupple months all i can tell you is that its super buggy (as you could probobly tell from that terror they called an install). if your confident and want to get your feet wet with a great custom rom i would go with firefly that should fix any issues you have its a fuly stable final release and best part its based on rogers software not at&t so it will work flawlessly with the network and most likley fix any problems you are having
Don't use 100% pure stock
Use tweaked - with EXT4 LagFix, OC/UV, Sideloading enabled, rooted, VoodooSound, with GPS fixes.
Older Cognition 3.4 was Rogers based - I can recommend that.
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
I, personally, loved the MIUI & CyanogenMod but they, in my opinion, have their downfalls.
MIUI: No app drawer, I like having just 1 page on the homescreen & all the excess apps/games in the drawer, but its layout (customization options (lockscreen/homescreen wallpaper, themed messaging app), bootlogo, etc.) is great but, the worst part was the simple fact that it would be fine over night, then the next day it started booting out the wifi, phone or even put my phone into airplane mode which I could not get out of no matter how many reboots or battery pulls I did.
CyanogenMod: No texting or phone calls at all, it has been awhile since I used it but it either could send & not receive texts/calls or vice-versa, either way just like w/ MIUI, its awesome in every other aspect.
I was just wondering if there are any other custom ROMs for the Samsung Mesmerize SCH-i500, in particular, that are similar to those two, themed and/or fully customizable options, I can't think of the words I'm looking for, I guess a standalone custom ROM that is FULLY STABLE (calls, texts, wifi, bluetooth, no AUTOMATIC airplane mode, etc. I mean EVERYTHING FULLY WORKING) for my, above mentioned, phone, does not have to be debloated/dexed/deodexed, either way.
i am running miui 1.12.9 with glitch kernel v13.1 EH09 radio
for what i use it all works. sms, bt, mms (wifi off), phone, alarm clock, etc..
miui control panel for the app drawer feature. maybe if you had an older version you might want to check out this newer one.
but as for other roms i have not tried any, if i get bored i might try something else but not until i read up on it so i know what im getting into.
combatarms said:
i am running miui 1.12.9 with glitch kernel v13.1 EH09 radio
for what i use it all works. sms, bt, mms (wifi off), phone, alarm clock, etc..
miui control panel for the app drawer feature. maybe if you had an older version you might want to check out this newer one.
but as for other roms i have not tried any, if i get bored i might try something else but not until i read up on it so i know what im getting into.
Click to expand...
Click to collapse
I was using MIUI.us_mesmerizemtd_1.12.9_Eng_Deo_ZipA_Signed_dfgas-911fix and it was about 2:30 in the morning when I finally fully restored to stock rooted 2.3.4 Gingerbread, wiped data, cache partition dalvik cache and finally rebooted after installing MIUI, I finally went to sleep at 5 in the morning after setting it all up.
I awoke at about noon & it was still running fine but I ran busybox installer so I could update the su binary & had to reboot, this was roughly between 3 - 3:30 in the afternoon &, after reboot, it just started f***ing up.
Absolutely no phone signal at all, I tried the phone activation code but it was never activated, wifi, even right next to the router, was not detected, tried a few reboots but nothing, it kept saying it was in airplane mode, when I opened the notification bar, deactivated airplane mode, it never turned back on again but only in the notification bar, in the settings menu, after turning it off & exiting the menu or going to another menu, regardless if it was from within the settings menu or not it automatically switched back on when I returned back to it, I don't know, if I can get it to work, I can live without the app drawer, its just that good to me.
I even tried the MIUI360P_ENHv3.1_universal_s enhancer thing but that just mad it so that, I forgot exactly what it was called, something about com.android.phone. (something) process kept having to be force closed but every time I pressed force close within 2 or 3 seconds it did it again & it kept repeating this over & over again, I had to pull the battery just to get out of it, but by what I saw in the forums after I tried it, its actually meant for Samsung Galaxy S II I9000, whereas I have the Samsung Galaxy S I i500, I kind of rushed into it in the hopes that it would fix the issues.
So I've had a few similar problems with recent ROMS i have flashed.
I'd been using CM9 and CM10 for a while, but got tired of lag and bugs. I thought I'd go back to GB for a while and reflash after some bugs had been worked out.
From CM10 odin'd back to GB stock with CWM and root, then installed AEON purely by reputation. That lasted for about a week. The phone had all kinds of issues with the battery. The battery level would often be all over the place (i know this sometimes happens after a reboot.) After a full charge the phone would stay on for about 4-12 hours, and simply turn off. Prior to shutting off the battery would read at 50%+.
Every time the phone shut off like this I could charge it all day and it would not restart. The only way it would start is if i pulled the battery, plugged in the carger and reinserted the battery. Once I did that an empty battery would show up on the screen. However it was not the normal green one with gradients that would show up, but simply a white box showing no charge. If i held down the power button eventually the normal battery charging screen would show up and it would reboot.
I'm assuming the phone was misreading the battery level for some reason. I tried clearing battery stats. No change.
So I thought 'time for a new rom'
I'm not certain if I went back to stock before this.
So from there I went back to CM9 and then to CM10. The battery issues remained, and two new issues arose.
My reception in the notification bar would turn to an empty triangle. It was not a misreport. I could not make calls or access the internet.
Also whenever i went in to airplane mode it would be grayed out in the power menu. It was impossible to turn off airplane mode without restarting.
I'm not on the most recent verison of liquid smooth. The issues remain, but I don't think it's the ROM as others don't seem to be having these issues.
Does anyone know any reason for this?
My understanding of flashing is that it's essentially a list of folders and files that replaces or adds to existing ones on the phone. Does it actually erase anything? Obviously it leaves our simcards and picture files. It also seems to leave app folders.
And just to be clear I wiped user data, cache, fixed permissions, etc. IMEI is still there, so i don't think that's the service issue. I did not restore any apps with titanium backup for similar. Everything was installed from the play store.
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
magnetboard said:
Whenever you flashed back to stock, do you happen to flash boot loaders?
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I flashed back to GB so I don't think that was necessary. I've not had the other bootloader issues with garbled display, etc.
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!