Anyone else experiencing the occasional crash/reboot?
The last couple of mornings my phone had woken me up... It's the Samsung boot sound, the phone has crashed and rebooted while I was asleep.
I have had a couple of crash/reboots while using it too...
Nope, no crash or reboot here.
Intratech said:
Nope, no crash or reboot here.
Click to expand...
Click to collapse
same here...
factory reset?
vinokirk said:
factory reset?
Click to expand...
Click to collapse
Thanks for the suggestion.... I have already factory reset once to get rid of the social hub settings...
Maybe it's an app I got installed then...
Nope. Its never crashed on me
Sent from my GT-I9100 using XDA App
mmm_ok said:
Anyone else experiencing the occasional crash/reboot?
The last couple of mornings my phone had woken me up... It's the Samsung boot sound, the phone has crashed and rebooted while I was asleep.
I have had a couple of crash/reboots while using it too...
Click to expand...
Click to collapse
does it reboot while it's on charge ?
Process Of Elimination...
List all the apps you have installed and then the guys here can give a YAY or NAY to those apps causing them the similar issue.
Double Post!!!.
Although it's probably unrelated, the LG Optimus 2x is having significant problems with freezes and reboots, and some users there also pointed out that the Moto Atrix seems to have similar problems too. The obvious commonality is the dual core processor.
As I said, probably unrelated but maybe worth keeping in mind if this becomes more widespread.
What wireless options do you leave on at night? (ie: wifi, gps, bluetooth....)
Some phones can get quite warm while left charging if lots wireless options are left on too.
However, for my Galaxy S 1 I only noticed it getting warm/hot around the top after extensive internet use with the screen on full brightness and either charging at the same time or having just been unplugged from the charger.
In the settings menu -> about phone check what is consuming the battery and it should help to see if there are any rogue applications that won't stop chewing power during the night.
using any latest gameloft games? have heard, that those not-so-legal copies of gl games are crashing devices.
Happened to me when I deleted the unwanted ASEC (or something) files form .android_secure folder in external sd card before uninstalling the apps and the device was connected through usb to pc. Well after two random boots it stopped just thank fully!
it can boot randomly when :
1. GSM signal is weak
2. Simcard is damaged or too old
3. Battery is too hot
4. Some APPS are moved to SD card (it allows you to move it, but actually, apps doesnt like it)
5. External SD card is slow, 4 or below classes, or too small sizes of sd cards (2GB-4GB) or too full of external sd card, ord sd card, or internal memory, etc. (shorly not enough memory
6. RAM!!!!!!, if more then 780mb ....,
7. too many WIDGETS...
8. too long standby
GUYS these are the main reasons, if you have all ok with above list, then you may have problems with OS, then flash and install back, or maybe HARDWARE PROBLEM (ram,cpu etc.)
GOOD LUCK!!!
Hey guys,
It happens to me too. For some reason it reboots, and when I check the battery stats, i see a major vertical drop, then it slowly regenerates the battery, but nowhere near the previous levels. I was on Batista KH3 ROM, now I though I'd try an official KJ3 ROM, but seems it hasn't done the trick. Tried everything from factory reset, to deleting cache and whatnot from recovery, but still no joy. The biggest battery muncher is Display, followed very regularly (unless I abuse some app or game) by Android System (not Android OS, mind you).
Any last words of advice before I send it to it's maker? (Samsung support, don't think about anything else, you crazy guys)
Thanks alot for your patience!
Cheers!!!
My Galaxy S II reboots once a day - in avarage - Hardware or Software problem ?
My Galaxy S II reboots once a day - in avarage - What kind of problem do I have ?
Is it hardware or software ?
Facts:
- Model: GT-I9100
- Android: 2.3.5
- Baseband: I9100XXKI4
- Kernel: 2.6.35.7.I9100XWKI8-CL616395 [email protected] #2
- Build: GINGERBREAD.XWKI8
- Kies has no updates for the phone.
I bought the phone 23th. of november 2011
I installed a 16GB MicroSD card
I installed all the apps that was using at the old phone (Galaxy I9000)
Phone was't able to run 24 hours without reboot.
By reboot I mean: A sound, the little 5 seconds Galaxy-movie, and asks for pincode...
No systematic in the reboot. Not a specific place, not a specific time, not by doing something special.
It never reboots when it is "open". It's always when it is lying on a table, or in my pocket.
==========================
OK. A factory reset. No apps installed, minimum of configuration.
Phone still reboots once or twice a day
=========================
OK. 16GB MicroSD disabled
Phone runs for 60 hours, then reboots, Then it runs for 22 hours and reboots
=========================
Right now: WiFi disabled... It has been running for 14 hours... waiting... Now 41 hours. (16dec,16:12) (not using wifi)
Update by 18dec: After 25hours I forced the tip of a plastic tooth-stick under the battery. After 60 hours I installed all my favorit apps, and it is still running... (88 hours)
Current conclution: Hardware - Bad implementation of battery-connectors...
Update by 3jan2012: Nope... Still not ok. Two reboots around x-mas and yesterday... once again.
I have been talking to Samsung, and they does not (officially) admit that the S II has a reboot-issue. They advice me to go to a repair shop, since the phone is fully updated and that they don't have more advices to give...
========================
More info:
Two colleques has the same phone, and they never reboots.
The one is a lower Android version: 2.3.4
The other is the same except Baseband: I9100NEKI2
If I return it to the shop they will send it to Samsung Repair, and after 10 days I will get it back. Or maybe a new one...
Pls. give me some advice..
Regards in advance
Thorkil
I've never experienced random reboot until now.
I just updated original ROM with 2.3.6 version an reboots hapan 2 a day!
I blame the new version 2.3.6 :/
Update
Hi guys,
It seems that the random reboot issue is gone now. After i went for the KI3 FW, the number of reboots went down at each charge and now they are no longer present. I didn't do anything, but i'm guessing it had something to do with the battery stats.
Hope this helps.
I had this issue the first day I upgraded my ROM. Then it stopped. I'm not sure if it was a random reboot or I accidentally shut it down while in my pocket (I don't use a lock screen). But it happened once, and it hasn't happened again since.
But I did get a weird error yesterday: It couldn't read my SIM card... I had to turn it off and back on to get it working again. Have any of you seen that before?
I've got exactly the same problem.
I recently did a reset to factory settings, but the problem is still there.
Running official 2.3.6 firmware.
I can't really think of a source.
Often it just restarts when it is in my pocket and I'm not using it.
Below you can see a screenshot of the battery stats a short time after the restart.
As you can see suddenly a huge amount of battery life is 'missing'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read about this problem at many forums around the internet.
I hope this is fixed soon, because it is really frustrating.
Related
Hello,
So, I have had a custom flash for some time. I don't use this phone too often and it sat off with a dead battery for about 2 weeks.
I plugged it in and turned it on. It booted into the custom rom for windows just fine. I went to reboot into Android like I normally would and it got stuck at the main boot screen but never displayed the rom / radio red text in the bottom left of the screen.
I've set it sit like that over night with no dice.
I have tried task29, reflashing HSPL, removing HSPL. I can't get anything to complete. It seems like as soon as anything tries to write into the phone's internal RAM is dies. I've tried flashing different radios but nothing takes once the 7 vibes hit.
Any ideas on what this is and any other ways to get around it. I've tried hard-resetting. When it says to press Vol-Up to boot it just gives me 7 vibes and a blank screen.
Where do I go from here?
Cheers,
Ech0
Here is what my boot loader says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Really, no one?
Im having the same problem guys... i have a tmo us hd2 1024... it is stuck at the stick together screen and the r,d,g red letter that appear, are not doing so... oddly enough it can flash roms...
sorry for my bad english...
you must install the latest stock-rom from sd-card.
copy the *.nbh from stockrom to the sd-card and renamed to leoimg.nbh.
just restart your hd2 and follow the text on the screen.
So what exactly is the significance of the 7 vibrations?
I got the same problem. I managed to reflash the phone after MTTY and flashed HSPL, bootloader, radio and ROM. Made hard reset. No luck, it freezes again and again.
I wonder what these 7 vibrations mean? Anybody know?
sorry to re dig up this thread but i have been having the same issues 7 vibrations and it just gets stuck on the boot up splash screen. Does anyone have a solution to this?
I have the same problem with my hd2 original rom... It first went a little warm on the back after heavy using with movie mp3 internet and youtube, it reboots and hang, had to remove the battery and wait to let it cool down....
I think it was a bug, so i downloaded the newest rom software from HTC and updated it... Now when i using it on the same way, movie internet mp3 and youtube it still reboots and hang, But it gives me 7 vibrations and stay in the boot screen,.. or it reboot again and again....
Remove the battery, cool it off and it works ok until.... it gets warm....
Called HTC and they sait that it could be a problem with the motherboard...!!! For now i am waiting for my device.... I send it to HTC for repair.... expect him any day now.... hope they fixed it.....
Just an update on my 2x HD2's.
Both went into repair and came back with "No Fault Found!'
So afterwards i sent it to a different repair centre who agreed with my diagnosis that the motherboard was faulty on both devices.
Subsequently they replaced the motherboard and now the HD2's are working as they should.
It used to lock up at around 33c. now with the replacement motherboard it runs fine even up to 45c! ( i used battclock to monitor device temp!)
Very interesting! I think I should send my HD2 for repair too. Did you use warranty service or paid money for the repair?
Always sent in for warranty!
My phone was bought in Frys. I asked my friend to bring it directly to T-Mobile office, they said "Go to Frys and let they repair it". He came to Frys, they said "It's T-Mobile thing, we can't help, give it to T-Mobile".
Please advise, how to get it repaired?
Call HTC or Tmobile and ask for the closest authorised repair centre. drop your device in directly with the proof if purchase and get it repaired.
T-Mobile declined to get it for repair once again. Friend of mine visited 2 T-Mobile offices and Radioshack shop and was sent to HTC everywhere. Maybe it's local Texas habit...
Will try to send it to HTC service.
Hi guys,
I've been faced exactly the same problem, but also have found (a bit of... strange, let's say... and temporary, somehow) solution. Read below...
I found out that the seven vibration signal indicates motherboard issues. AND - as in most of cases mentioned right here, in this topic - the error wasn't occuring immidiately, but after a few minutes since turning the device on. So what I thought is that the phone was simply overheating, or even if it was not - the temperature indicator wasn't working OK and as a result we were getting this error.
As I found this out after long hours of trying to get things work, here a quick guide how to fix what you probably messed up during your efforts:
1. If you tried to reinstall ROM or any other software using USB cable and things didn't go well - don't worry, it was the same for me. Firstly, we need to clean up. Run the installer on your PC again, then try again, the error will occur, and after it does follow the instructions on the screen UNTIL THE INSTALLER ASKS YOU TO CONTINUE AND INSTALL ANYTHING AGAIN. Don't do it, just pull the cable off the phone.
2. What you need to do now, is to download a new ROM, then copy it onto the microSD card, then rename to "LEOIMG.nbh". Turn the phone on with VOL- pressed down, and then confirm installation with the Power button.
Okay, we have got it all installed and... not working. Probably the white HTC splashscreen and nothing more. And after the reset, 7 vibrations again. Now, the magical trick.
Put your phone into the fridge. Seriously. Take out battery, put it into some plastic bag (so it won't get wet) and put it to the fridge. Wait 20 minutes or so, then turn it on and enjoy temporarily working phone. It was fine for me until I started to use Opera.
Further solution? Well, working on it.
P.S. Sorry for refreshing old topic, but the problem doesn't seem to be solved and I'm trying to push things forward.
Is anyone else experiencing these. I've only had the phone a few days but started to notice it once I put infected rom eternity on it not sure if it is a rom issue or a hardware issue
Sent from my PG86100 using XDA App
I'm having random reboots and I haven't even rooted/modded in any way. I got a system update earlier today, but it was doing it before that. It might be one of my apps, but it only happens when the screen is off and I'm trying to turn it back on to use the phone. I've tried factory resets and battery pulls so I figure its an app, or having the social lock screen.
Sent from my PG86100 using Tapatalk
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
mteezey said:
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It's definitely hardware. It's the proximity sensor, I believe. I picked up a phone call, and when I put the phone up to my face (I didn't touch my face to the phone, just my ear), the screen didn't shut off, and then rebooted. After it started back up, I called the person back, and when I brought the phone up to my face, the screen shut off as it should, and stayed in the call until I hit end, and it's still on. I received a second call and it had the same behavior. Reboot upon bringing it up to my face the first time, fine the second time. When I try to bring the phone out of standby I thought it was the live unlock screen I had (weather), but it seems to bee the light sensor or proximity sensor... boo..
[EDIT] Just did a factory reset. Market is installing my apps. We'll see how this time around goes.
So far so good. all my apps are re-installed. I have yet to check my games for my data, but I took a phone call and the screen turned off quickly when I brought it up to my face.
That's the same way it happened to me during a phone call but I was on hold for twwenty minutes with it on speaker and once they picked up I put it to my face and ....reboot. like you said boo
Well I got rid of eternity and with new rom(Olympus Trinity XE) and kernel mild anthrax I have not had a reboot yet. Its only been 12 hours but it was happening every few hours before.
Sent from my PG86100 using XDA App
heat
I usually have my E3D in it's Otterbox clipped on my belt, and no problems arise. Last week I went out to a bar and it was very warm in the bar, and the phone was in my pocket. It rebooted once out of the blue. I'll keep it on the belt clip.
Rooted, Stock rom.
I'm planning on getting am otterbox very soon.
As for rebooting, it's still doing it, once when a Words with Friends game wouldn't load and another time while trying to load Paradise Island. I'm now thinking it's the video driver.
I rooted my Intercept and changed the driver. I would rather not root this device if I can't unroot it...
Sent from my PG86100 using Tapatalk
Mines not rooted either and mine just rebooted like literally 3 times in a matter of 30 minutes
Sent from my PG86100 using XDA App
There is a rom to unroot. Its a stock rom once you flash turns your securities back on(s-on). Which is good in case you ever have to take it back to sprint.
Sent from my PG86100 using XDA App
I've only had one reboot with my new kernel. It seems now like its only when its on the charger I set a charging profile now to Max CPU speed of 648mhz with interactive governer gonna see if that helps. If not I'm gonna try a temperature profile.
Sent from my PG86100 using XDA App
From what I can do on an unmodified device, I found this in the "Tell HTC" log.
local_clk_disable_reg: clock 72 status stuck at 'on'
This happens a few times in the log. I've been taking screenshots of the log to post, but I haven't had the time to go through the whole log. The next time I get a chance, the phone has already rebooted 3 times. It's definitely not my app because it's no longer on my system.
Also, I don't know if this goes with it, but I sometimes have to do a PRL update to get out of roaming. I'm in my local, high-signal area... I'm eventually just going to call and get a replacement.
[EDIT]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here we go. Here's the error message, then it dumps the memory locations. In a minute I'm going to post a link to an album I have with the log, error to end.
Another oops 17 prempt smp.
Sent from my PG86100 using Tapatalk
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
mteezey said:
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
Click to expand...
Click to collapse
This is all untouched stock from Sprint.
But wait! It gets better! I wasn't using the phone last night, and it kept rebooting every 20 minutes +/-, then it gets stuck in a boot loop (which it's still stuck in). As mentioned before, I have to update the PRL every time I reboot the phone, so could it automatically be routing itself to a bad radio? Not that it matters, I have to factory reset anyway...
I went into recovery to do a factory reset (boo... going to try to adb pull my data, first) and I noticed that during the image check, two of the images are the "wrong" image (PG86DIAG and PG86IMG... something like that). Is this bad? I went from a Samsung Intercept to the Evo 3D so there's some major differences between stock recovery and CM01 heh.
Shooter XC Ship S-On RL
HBOOT version 1.50.0000 (used to be 1.4 and I only did the OTA update and install some apps/games)
eMMC-boot
Sorry for somewhat hijacking this thread, by the way. I just think it's strange to have all these problems on a stock device (though stock isn't great... ever). When I initially came on to search about it I noticed your post and jumped right in lol.
I'm glad I didn't root this thing right off the bat because of the watermark, and because of this stupid page fault.
I think wrong image thing is just your phone searchiibg for update IMG when you open the bootloader I would have to see exactly but its normal for it to check for pcwhateverimg. Whenever the bootkaoder opens. Since you have s on and don't have to worry about losing root access it night not be a had idea to update to the latest radios . Then if you still have the problem try to tIe it back. I haven't been having the problem anymore with a new kernel and new usb cord. Since it seemed to be when I plugged in. But as ling as I don't overclock above 1.6ghz I've has no problems Anymore
Shot from my Shoot3Rvo
I'm going with the acct holder (my bro-in-law) tomorrow to get a replacement. Seems we're not the only ones. There's another thread on here about this very topic...
As for rooting it, I need to read more, but doesn't it leave a mark saying it's been modded if it's 1.5 or greater, thus not returnable? I remember the Intercept doesn't have that so it was no problem switching back and forth, but it was a b***h to get a solid root...
Sent from my PG86100 using Tapatalk
I didn't read everything on hboot 1.5 but I know there is some different steps. I know there is a ROM to flash to get back to s on which is all you need for warranty to not be void I'm sure it says whether or not it works with that hboot.
Shot from my Shoot3Rvo
Awesome to hear there's a work around for the S-On. Looks like I got some reading to do when I get home from work!
Sent from my PG86100 using Tapatalk
Oh, this is so good it has to be fattening!
So I did a factory reboot and it lasted like 8 hours, whoopee...
I bring it in to Sprint and they have the tech look at it, estimating 45 minutes to an hour. Good, I had gift shopping to do. I come back and the girl gives me the (same) phone and asks me to log in. I do, and it updated my contacts, etc. She then said "He reset and updated the software so it should be okay now."
"... so why does it still say I'm roaming?"
"It does? Let me see."
She brings it to the tech, who performs the "magical" PRL update, which I TOLD them I HAD to do after every reset I did. Fine. It's working now, and I have no roaming charges, so not worried about the bill. I go home and enjoy the rest of my time before work. I get into my work parking lot, and the phone resets. Mother ****ers. I'm back in roaming, too!
Looks like I have somewhere to be first thing in the morning and to directly talk to the tech and ask, "Did you really think that a severe page fault that's embedded into the ROM would be cleared by a factory reset? The device needs to be flashed or replaced."
I told the girl straight up that I can fix it in 20 minutes, and that I rooted and modded my Intercept on Virgin Mobile (which they sign contracts at that location for heh) and it cleared up all my problems. Then, that I can't do that with this phone because I can't return it if it screws up again.
Ugh! Why do they release crap like this?! There are thousands of people that have this phone with this rebooting problem... Shouldn't there be a recall? Even on the Sprint customer forums there's posts about it, so Sprint KNOWS of this issue, especially if a manager replaced 8 devices in one day for the same problem.
So anyway, I'm on my way home from work, and I click the phone on to pull Pandora up, and it resets, but it doesn't go back to the home screen. It's stuck in a boot loop again! YES! I removed and replaced the battery and it did it again. I took the battery out and just set it on my desk, waiting for the tech to turn it on. Hooray that it got stuck, so I can rub this in his face. I should be working there, not him. (Sorry for my ranting, I'm just tired of Android problems because of carriers changing the software and locking it up. Google WANTS people to make the software their own!)
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
rigmort said:
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
Click to expand...
Click to collapse
I've seen that on another forum. Thank you for the SD card insight. Just as a precaution, I'm just going to pull all the crap off my card and format it with the SD Formatter. I don't remember what the "brand" is but I know it's the right one. Should I back it up and format through the phone, or use the adapter and format the computer way? I'm thinking phone...
I talked directly to the tech today and told her what the log said and that it needs to be reflashed. After the estimated time she gave it back saying that she ran it through every test their system can run and the software has no errors (which my logs say as well), but she reflashed anyway to make sure (I'm still not sure how she logged into my gmail if she reset it...) I have to call corporate for the roaming issue because I'm connecting to the wrong tower, which she doesn't have permission/clearance to change. If, after fixing the roaming, it still does reboot, it will be replaced. I'm still under warranty, so I'm curious as to why they're trying to keep me on, what I believe to be, a defective device... Because they can't detect anything wrong with it...
I have yet to install any apps (minus Tapatalk) and the phone has yet to reboot, and its been in my pocket all day so I would have felt it reboot. Shame because it's one of my paid apps (one out of 6), Paradise Island, Angry Birds (which wasn't opened at all during this, but it was installed), or Words with Friends. I also had ScummVM but the reboots started way before I installed it and the engines. Those are the only apps I installed the last couple times because I'm sick of reinatalling all my apps. Bigger shame because I can't install apps until I'm sure of what the problem is. Why have an amazing phone I can't use a paid app on? I'm just frustrated at this point... I have a lot of back traces to read through and no list of what is what because the phone has been cleared since then... Does the memory map stay the same no matter if it gets reset? I haven't done any Linux kernel programming so I'm learning as I Google which is what it's meant for.
I really want to Update the PRL to see if it will help with my battery life, which it should, but I don't want to change anything, in case it messes up again. It will be proof its defective. Ugh... What to do...
Merry Christmas, to those who celebrate the holiday! Happy holidays to everyone!
Sent from my PG86100 using Tapatalk
...I have a lot of problems typing with a touch screen so I edit a lot to correct things... That and my screen feels my fingertip before it touches the screen...
[EDIT] My SD card has been unmounted for who knows how long! I just remounted it as is to see if it starts rebooting.
I'm coming to the Evo 4G LTE (stock, not yet rooted) from the OG Evo (rooted, various ROMs, yada yada). I've held off on rooting, just in case I discovered a hardware issue (light leakage, etc.) and needed to swap out the device. So far I've discovered a definite problem, but I don't know whether it's a hardware or software issue, and I'm hoping someone in this forum can help me down the path of figuring out the cause(s).
Specifically, I'm seeing the following things happen, usually all at the same time, but intermittently:
1. Phone heats up, and battery takes a huge hit
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
3. Wi-Fi drops, as does my mobile data connection, so that I appear to lose all connectivity.
4. My app associations get reset. I usually have my URLs set to open with "Dolphin Browser HD", and mail set to open with "Gmail (Compose)", but after this happens they're back to the stock browser and mail app.
5. Can't enter any text. When I enter a text field/control, the keyboard appears (I use Swype, but switching input methods makes no difference), and I can type/Swype away, but no text ever shows up in the field.
This is happening about once a twice a day, on average, and is obviously driving me nuts. I haven't detected a pattern to when/why it happens. And I've been searching the forums, but I haven't seen anyone else reporting this same set of issues. I'm not sure whether it's my device (hardware/lemon), or maybe just a user app behaving very, very badly - I'm not enough of an Android dev to know where to look for clues...?
Any help very much appreciated. I haven't tried a factory reset, but I'm open to that. Also to rooting the phone, and/or contacting Sprint. I just didn't want to blindly do any of those things before asking the Android experts out there for some guidance.
Thanks!!
If it was me, I'd root and flash a new ROM or at least a rooted stock ROM. If that didn't work I'd unroot and exchange it.
I'd say try a factory reset first, but why not root and have it done as a by-product anyway?
Sent from my EVO using xda premium
I agree
If you dont want to root yet just do a factory reset. What is it going to hurt? If you do a factory reset try to just set the phone up with all stock options to see if your problem is fixed.
roachiepoopoo said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
jpbme said:
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
Click to expand...
Click to collapse
The same is with me BEFORE rooting, and after root and ota from xda
Look I want to thank you for posting this. I am NOT CRAZY. This has happenend to me from day 1, I returned the first EVO LTE (for other reasons) and it is still happening on my second EVO LTE
I finally got to the point that I was going to root my EVO LTE to fix this issue. I was going to root and flash and reset EVERYTHING. well surprise surprise nothing changed.
I have all the same problems you described but I lose my 3G about 15 times a day (especially when on calls) I have full bars but the 3G icon is gone and it states that I am disconnected. I can't figure this out. Everyone I appreciate your quick responses to this mans question but none of them work.
I have update profile and prl more times then I can remember. Flashed, wiped , reset everything. Help Me!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any new info on this topic? My 3G disconnecting is really annoying!!
Rooted, wiped, and switched to MeanROM - phone now works GREAT!
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
roachiepoopoo said:
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
Click to expand...
Click to collapse
NO!
So I flashed the Chameleon Rom, was running it for a while and still had issues. This weekend (during a wedding) I flashed MeanRom. And it is still happening. Does anyone know a real fix for this? :crying:
SilverZero said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
stompkins007 said:
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
Click to expand...
Click to collapse
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
slowfncar said:
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The issue I was having was only specific to the blank notifications... everything else has been pretty solid... BUT, there appears to be a light at the end of the tunnel. Last night I saw ClearnROM DE 1.4 was released, and had to give it a try. This time around I was very careful to do a full factory reset, Wipe of everything except storage cards via TWRP, Ran Superwipe script, and installed the latest CleanROM DE 1.4. The one thing I did differently after install was be very careful of what items I restored via Titanium Backup (making double certain it was only restoring app store apps, and no potential artifacts from previous ROMs.
Since doing this the phone has been solid. Haven't experienced the blank notifications, and the phone seems considerably more responsive than it was (which is nice, because it even seemed fast before doing this). Anyway, if anyone else is experiencing this, I recommend they do the same.
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
I don't buy Sprint's insurance and have had issues getting them to do warranty replacements, most recently with my EVO 3D's phantom screen touch problem (also 1st gen hardware). Sprint told me to ship it back to HTC and be without a phone for however long the warranty repair took. Really?
KatanaMan said:
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
Click to expand...
Click to collapse
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
KatanaMan said:
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
Click to expand...
Click to collapse
RE: SuperSU, it lives on the system partition with the ROM so it's protected from a factory reset since that only clears the data and cache partitions (where your user apps are stored).
Sent from my EVO LTE
Just a thought
You cold try ##786# and enter your MSL code for data connection issues. See here to use CDMA Workshop for those that are not rooted (or use MSL Reader from the market for rooted users). Its worth a try at least, before unrooted users decide to root. Keep in mind this will reset your phone to factory so if your going to reset, might as well do this to reset PLI, PRL and other params...
I've been having the overheating/battery drain issue since about a week after first getting the phone. I've tried Meanrom, Viper Rom, and Clean Rom and still come across the same issue with each one. I do complete wipes/factory resets when flashing the new roms and I'm on the latest firmware. When the phone overheats it's pretty much unresponsive. Today, I watched my battery drain from 15% down to 8% in about 10 minutes. I turned the screen off at 8% and went to turn it back on a few minutes later and found that the battery had completely drained by that time. I have no idea why this is happening.
Same here
I've been having this issue as well. It happened while I was stock, it happened after I rooted, unlocked, went S-Off. And it's still happening under MeanROM. Very frustrating!
I started having this issue about 4 or 5 days ago. randomly my phone will pop up SIM card removed, please restart. I restart the phone has no signal, I reboot once more and all is right with the world. It's starting to get annoying though. I've tried this with PA and SB and it happens in both. Additionally recently my GPS has been having one heck of a time locking when it used to take 10 seconds and with SB it won't even acknowledge that the GPS is even turned on. I don't remove my SIM card at all, the phone isn't dropped or treated harshly. Is this a hardware issue and should I contact Samsung for a replacement? I haven't flashed back to stock yet, but I think that might be my next step as if nobody has any ideas.
Any thoughts?
Current config:
Rooted, SlimBean 2.9.0, Radio UCFL6 Kernel 3.0.49-cyanogenmod-g00e92fa
Thanks
Theoriginalgiga said:
I started having this issue about 4 or 5 days ago. randomly my phone will pop up SIM card removed, please restart. I restart the phone has no signal, I reboot once more and all is right with the world. It's starting to get annoying though. I've tried this with PA and SB and it happens in both. Additionally recently my GPS has been having one heck of a time locking when it used to take 10 seconds and with SB it won't even acknowledge that the GPS is even turned on. I don't remove my SIM card at all, the phone isn't dropped or treated harshly. Is this a hardware issue and should I contact Samsung for a replacement? I haven't flashed back to stock yet, but I think that might be my next step as if nobody has any ideas.
Any thoughts?
Current config:
Rooted, SlimBean 2.9.0, Radio UCFL6 Kernel 3.0.49-cyanogenmod-g00e92fa
Thanks
Click to expand...
Click to collapse
I am having these issues as well that have suddenly surfaced. I have tried different Roms and other radios all with the same results. I recieve a pop up when for some reason it can't find a mobile network and wants me to reinsert my sim card. Data seems to work but no phone calls or txt msgs. Sometimes I'll have to reboot serveral times to get it back to operating normal. It's almost like something happens to my APN settings because I am unable to look at them when this happens, it just kicks me out.
itbull said:
I am having these issues as well that have suddenly surfaced. I have tried different Roms and other radios all with the same results. I recieve a pop up when for some reason it can't find a mobile network and wants me to reinsert my sim card. Data seems to work but no phone calls or txt msgs. Sometimes I'll have to reboot serveral times to get it back to operating normal. It's almost like something happens to my APN settings because I am unable to look at them when this happens, it just kicks me out.
Click to expand...
Click to collapse
It could very well be your APN settings. When unapproved flags are address, the network has the ability to knock you off of a custom APN to the high-priority APN profile. If your APN profile has the "Hipri" flag, which marks it as the default, and your network kicks you off of it, it will keep trying to connect using the bad profile. Which is why you shouldn't use that flag for custom APNs.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Jamesyboy said:
It could very well be your APN settings. When unapproved flags are address, the network has the ability to knock you off of a custom APN to the high-priority APN profile. If your APN profile has the "Hipri" flag, which marks it as the default, and your network kicks you off of it, it will keep trying to connect using the bad profile. Which is why you shouldn't use that flag for custom APNs.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
That makes some sense as it isn't a set amount of time before it happens, and it happens in different ROMS. But I'm using the APN that's in those ROMs, and it only seems to happen when my phone is idle. I haven't migrated my phone to Stock yet, but when it happens again, I think I just might.
Any Other thoughts?
Theoriginalgiga said:
That makes some sense as it isn't a set amount of time before it happens, and it happens in different ROMS. But I'm using the APN that's in those ROMs, and it only seems to happen when my phone is idle. I haven't migrated my phone to Stock yet, but when it happens again, I think I just might.
Any Other thoughts?
Click to expand...
Click to collapse
I'm in the same boat as you. Yesterday was unbearable. I must have rebooted my phone < 20 times during the course of the day. I've been through my devices with various roms over the years and this just stinks. I'm starting to think it's a hardware problem at this time or a faulty sim card.
itbull said:
I'm in the same boat as you. Yesterday was unbearable. I must have rebooted my phone < 20 times during the course of the day. I've been through my devices with various roms over the years and this just stinks. I'm starting to think it's a hardware problem at this time or a faulty sim card.
Click to expand...
Click to collapse
Have you attempted to replace your SIM or return the phone all the way to prerooted setup? My phone has been behaving the last couple of days (said it was no better than an Iphone, seemed to have taken it to heart), so I haven't tried wiping back to factory setup. It seemed to get really bad there for a while for me, I rebooted as much as 8 or 10 times a week or so ago, this week seems better. This week will be a good test because it's a holiday and a lot of people will be on their phones and we can see if it's an APN thing or a hardware thing. From my testing it's either hardware or network interfacting, not ROM unless it's Kernel, but if it were kernel a whole lot more people would be having these issues.
Theoriginalgiga said:
Have you attempted to replace your SIM or return the phone all the way to prerooted setup? My phone has been behaving the last couple of days (said it was no better than an Iphone, seemed to have taken it to heart), so I haven't tried wiping back to factory setup. It seemed to get really bad there for a while for me, I rebooted as much as 8 or 10 times a week or so ago, this week seems better. This week will be a good test because it's a holiday and a lot of people will be on their phones and we can see if it's an APN thing or a hardware thing. From my testing it's either hardware or network interfacting, not ROM unless it's Kernel, but if it were kernel a whole lot more people would be having these issues.
Click to expand...
Click to collapse
I haven't tried to revert back as of yet or replace the sim card. Had 2 issues so far today and I couldn't take it anymore so I ended up taking out my sim and brushing the contacts with an old toothbrush. I then cut a small piece of paper and slid it in with the card on the back of it. Its in there tight and making great contact now. Pretty sad that this is what its gotten to but I haven't had any issues yet. Will keep everyone updated though.
Sorry to dig up an old thread of mine, but I figured it would be better than opening a new one. The issue has changed a little. I'm still running into the issue of the network not connecting, but now seems to occur only when I reboot. I've rebooted my phone probably 30 or so times today and my network hasn't returned. I did notice something though. While I'm having this issue, I attempted to access my APNs list and it dumps back to settings. Anyone having these issues as well? Also anyone have any idea which service the APN/phone system rely on? maybe all that it needs is to be for stopped, cleared and restarted?
Thanks guys.
Galaxy Note SIM card removed please reboot
I'm getting this all of a sudden. I've been using a stock original ROM for 8 months, and 3 weeks ago I woke up one morning with this message. Every couple of days I was getting this message. I then went to the AT&T corporate store and got a replacement SIM card. This had no effect. So I thought, I'll try a new ROM and see if that helps, I backed up with online Nandroid, and loaded "[STOCK ROM] IML74K.UCLD3 for SGH-I717" loaded perfectly, and all functions seem to work so far. However, since I did this last night I've had to reboot the phone like 10 times. I've reseated the SIM card, but still get the error message.
Any ideas as to what could be causing this? I've read this thread and see the APN issue, but from what I've read here that seems to be part of the ROM loaded...
Back story, I tried the kies update around 8 months ago, and while it did update, all the icons would disappear from the notification bar, and then reload, every few minutes. If I was on a call during this, the call would be dropped. Since I couldn't undo the change through kies, I came here and went with what seemed to be the original stock ROM for the Note, but Kies no longer recognized it as a supported firmware. So when this issue happened I came back here to upgrade.
Fyrebaugh said:
I'm getting this all of a sudden. I've been using a stock original ROM for 8 months, and 3 weeks ago I woke up one morning with this message. Every couple of days I was getting this message. I then went to the AT&T corporate store and got a replacement SIM card. This had no effect. So I thought, I'll try a new ROM and see if that helps, I backed up with online Nandroid, and loaded "[STOCK ROM] IML74K.UCLD3 for SGH-I717" loaded perfectly, and all functions seem to work so far. However, since I did this last night I've had to reboot the phone like 10 times. I've reseated the SIM card, but still get the error message.
Any ideas as to what could be causing this? I've read this thread and see the APN issue, but from what I've read here that seems to be part of the ROM loaded...
Back story, I tried the kies update around 8 months ago, and while it did update, all the icons would disappear from the notification bar, and then reload, every few minutes. If I was on a call during this, the call would be dropped. Since I couldn't undo the change through kies, I came here and went with what seemed to be the original stock ROM for the Note, but Kies no longer recognized it as a supported firmware. So when this issue happened I came back here to upgrade.
Click to expand...
Click to collapse
this is a software issue i have finally gotten it fixed.
I had JB 4.1.2.
You will need to download ODIN and flash here are the firmwares for your specific phone.. http://forum.xda-developers.com/showthread.php?t=1771687
I used ICS and the problem has gone. Make sure you do a factory reset through stock recoveryt mode after the phone reboots from installing the new software. To get to this screen press volume up, home and power and let go when blue print comes at the top.
Is not software issue , is Note model issue. The way to fix it is making a paper with the size of the SIM and put the SIM and the paper together into SIM place. The Galaxy Note SIM card place is little more bigger than others phone and SIM is not contacting good there. I just tried on some phones , on all them working but on NOte the SIM was moving and it gaves the error. Here I add a photo of how is my Note looking, just to say my SIM card is white.
ShiftShapa said:
this is a software issue i have finally gotten it fixed.
I had JB 4.1.2.
You will need to download ODIN and flash here are the firmwares for your specific phone.. http://forum.xda-developers.com/showthread.php?t=1771687
I used ICS and the problem has gone. Make sure you do a factory reset through stock recoveryt mode after the phone reboots from installing the new software. To get to this screen press volume up, home and power and let go when blue print comes at the top.
Click to expand...
Click to collapse
i'm with Rogers in Canada, rogers isnt listed can i use the others safely?
dicecuber said:
i'm with Rogers in Canada, rogers isnt listed can i use the others safely?
Click to expand...
Click to collapse
See what I wrote some posts before
Enviado desde mi GT-N7000 usando Tapatalk 4
herna said:
See what I wrote some posts before
Enviado desde mi GT-N7000 usando Tapatalk 4
Click to expand...
Click to collapse
can you post a video of what you did? the pic doesn't work for me
dicecuber said:
can you post a video of what you did? the pic doesn't work for me
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi GT-N7000 usando Tapatalk 4
So I watched some videos and i think i understand how to do it by simply downloading the firmware and add the correct files to each one bl,ap,cp,home but I don't know what country firmware to use? I tried getting one that was from unknown country but there was no CP_xxxx file in it so do i get a different firmware? It was a Unknown country one.
Files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my tablet is also not rooted just a normal tablet on android 9 not sure if that matters
As to why i want to do this is my tab s3 is slower and feels like a cheap tablet now and want to go back lol
"my tab s3 is slower and feels like a cheap tablet"
Can you explain further on this? More lag when scrolling? Less apps are stored in memory (they need to reload from scratch when you switch to them)? Apps take more time to start?
Have you tried a system reset and start from scratch? Or tried a debloated custom Pie rom from the dev section?
Because there's lots of complaints on how Pie is somehow slower than Oreo, but I haven't see a thorough explanation, or actual data on this. In fact there's equally plenty of posts saying Pie is just fine.
Honestly I'm interested in knowing more, because I got this tablet already set up with Pie, and having fully reset it, I didn't encounter any lagging. It certainly feels smooth. Only issue is that I feel apps were killed faster than I thought, certainly doesn't give the impression of having 4gb of RAM. But I don't have a reference point, so I don't know if Oreo is better.
The device is still in warranty so I don't want to do any tweaks.
Pact said:
"my tab s3 is slower and feels like a cheap tablet"
Can you explain further on this? More lag when scrolling? Less apps are stored in memory (they need to reload from scratch when you switch to them)? Apps take more time to start?
Have you tried a system reset and start from scratch? Or tried a debloated custom Pie rom from the dev section?
Because there's lots of complaints on how Pie is somehow slower than Oreo, but I haven't see a thorough explanation, or actual data on this. In fact there's equally plenty of posts saying Pie is just fine.
Honestly I'm interested in knowing more, because I got this tablet already set up with Pie, and having fully reset it, I didn't encounter any lagging. It certainly feels smooth. Only issue is that I feel apps were killed faster than I thought, certainly doesn't give the impression of having 4gb of RAM. But I don't have a reference point, so I don't know if Oreo is better.
The device is still in warranty so I don't want to do any tweaks.
Click to expand...
Click to collapse
hello yes ive tried a reset before and its usually stuff like me pressing the home button or multi button and noticed 2 second delay and scrolling lags and the battery drains fast now i remember leaving it on standby fully charged and will check it back 3 days later and it be like on 20-40% and now it dies in 8 hours on standby mode maybe less/more.
as for other firmware this would be my first time doing anything like this which is why i made this thread because it wasnt containing a file that ive seen people talk about in videos/tutorials.
Hi, I have this error on ODIN: emmc write fail: aboot
Some clue to resolve it?
Thanks.
bitelmaniaco said:
Hi, I have this error on ODIN: emmc write fail: aboot
Some clue to resolve it?
Thanks.
Click to expand...
Click to collapse
What version of odin are you using? Use 3.13.1
I tried many time to reset and even wiped my tablet but the problem is still not handled. Snailed everytime. I dont know how to do it now.
My tablet is on stock 9.0 and it runs terribly. The entire interface feels sluggish and clunky. I turned off scale animations and switched to a super minimal launcher and it still feels like it takes .5- 1 seconds to react to any input. Even rotating the display lags by 3-5 seconds. I also noticed the volume has been nerfed with this firmware. Removing the annoying safety cap does nothing to the overall volume. I handly even use my tablet anymore since 9.0 made it feel worse than a $60 Chinese tablet from Walmart.
I managed to downgrade from 9 to 8 using T825XXU3BSD1 UK rom. It had right bootloader version that made the process possible. give it a try
Srambo217 said:
My tablet is on stock 9.0 and it runs terribly. The entire interface feels sluggish and clunky. I turned off scale animations and switched to a super minimal launcher and it still feels like it takes .5- 1 seconds to react to any input. Even rotating the display lags by 3-5 seconds. I also noticed the volume has been nerfed with this firmware. Removing the annoying safety cap does nothing to the overall volume. I handly even use my tablet anymore since 9.0 made it feel worse than a $60 Chinese tablet from Walmart.
Click to expand...
Click to collapse
Hi @Srambo217,
I have the exact same problem with my Tab S3 after upgrading to Pie. Is there any solution to this?
@Antonielli, did you manage get your tablet downgraded?
kitty035 said:
@Antonielli, did you manage get your tablet downgraded?
Click to expand...
Click to collapse
No, sadly I did not.
Antonielli said:
No, sadly I did not.
Click to expand...
Click to collapse
These are the steps I followed when I did it myself over a year ago. I Modified the steps since you are not rooting your device.
1. Download the firmware you need from a reliable source. (sammobile is a good place)
2. Go into settings on Device, find Build Number and tap on 7 times to unlock Developer Options.
3. Go into Developer Options and turn on USB Debugging and OEM Unlock (very important even though you are not rooting)
4. Download and install latest version of ODIN for Samsung and any drivers you need for your computer. Also extract the downloaded firmware in easy to find place.
5. Put tablet into Download mode (hold Power, Vol Down, and Home button together) and open ODIN.
6. Hook tablet to computer and make sure it show up in ODIN, then place the AP, BL, and CSC files in their right slots. Don't use CSC home file.
7. Click Start.
You are basically following the same steps that someone does to root their device only you are installing the factory firmware instead of a custom one. So please double check my steps with the steps posted by more senior members in the rom section. I do know that I was able to personally downgrade my device twice when learning how to install custom roms. I went from Android 9 to 8 both times.