Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing
can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.
lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly
hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).
Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk
i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk
Okay so once again, another ROM has got bad after 2 weeks. FXP 349 build has got to be pretty much unsuable, the unlock button doesnt respond, and the UI crashes for a laugh now. Getting very frustrated with this phone. Its getting harder to not smash the hell out of it with a hammer.
I must be doing something wrong, but every ROM Ive used just degrades in performance to the point where I cant take how laggy it is, Ive missed phonecalls because the UI cant wake up and show the incall UI fast enough. There has to be something deep in this phone which causes bad performance.
Im moving to VanirAOSP, as it says in the title of the ROM that its fast and smooth. Lets see if it can outlast any other ROM I've tried.
Sorry for ranting, I just dont get it, is there some secret setting that everyones using and not telling about? Ive tried stock kernel with CM, williams kernel with CM, stock kernel with CrystalPA, same again with williams kernel. Art or dalvik, it seems to make no difference, no matter what, the UI will bug out. Im not moaning at the devs because I know the work they do is hard and is much appreciated. I just wish I knew why this phone cant last 2 weeks without needing to be wiped!
Every ROM gets laggy after a while. Just use some app to clear cache and thumbnails and you should be fine.
donk165 said:
Okay so once again, another ROM has got bad after 2 weeks. FXP 349 build has got to be pretty much unsuable, the unlock button doesnt respond, and the UI crashes for a laugh now. Getting very frustrated with this phone. Its getting harder to not smash the hell out of it with a hammer.
I must be doing something wrong, but every ROM Ive used just degrades in performance to the point where I cant take how laggy it is, Ive missed phonecalls because the UI cant wake up and show the incall UI fast enough. There has to be something deep in this phone which causes bad performance.
Im moving to VanirAOSP, as it says in the title of the ROM that its fast and smooth. Lets see if it can outlast any other ROM I've tried.
Sorry for ranting, I just dont get it, is there some secret setting that everyones using and not telling about? Ive tried stock kernel with CM, williams kernel with CM, stock kernel with CrystalPA, same again with williams kernel. Art or dalvik, it seems to make no difference, no matter what, the UI will bug out. Im not moaning at the devs because I know the work they do is hard and is much appreciated. I just wish I knew why this phone cant last 2 weeks without needing to be wiped!
Click to expand...
Click to collapse
I have a feeling you are installing too many apps running in background at once. My phone is super smooth, fast and responsive. I just either close apps after I am done with them (kill process) or don't install trash. Deleting some in-build rom apps which you never use could also help.
kwitu said:
I have a feeling you are installing too many apps running in background at once. My phone is super smooth, fast and responsive. I just either close apps after I am done with them (kill process) or don't install trash. Deleting some in-build rom apps which you never use could also help.
Click to expand...
Click to collapse
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
donk165 said:
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
Click to expand...
Click to collapse
I could give you a tip about Facebook app and Messenger. There is an app that lets you chat using Facebook app, meaning you can get rid of Messenger. Google it and you will find it, I can't recall the name now.
kwitu said:
I could give you a tip about Facebook app and Messenger. There is an app that lets you chat using Facebook app, meaning you can get rid of Messenger. Google it and you will find it, I can't recall the name now.
Click to expand...
Click to collapse
Well the way im doing it, i dont actually use messenger, its installed but frozen/disabled so it isnt used, this allows me to chat inside the facebook app but the only downside ive found is that the chat notification dont seem to be working. This was a fix I picked up while browsing the net. Ill try out this app if I can find it, the name would make it much easier to find
donk165 said:
Well VanirAOSP has sorted out my issues for now it seems. I dont really install many apps to be honest, I use the Micro PA Gapps package and I then remove Google Now Launcher, freeze the preinstalled launcher3, install Nova launcher. I have only 17 installed apps, Facebook is the only real hog app I think, I install messenger and then freeze it to get around the Facebook app not letting me use chat within the app. I do also play Marvel Contest of Champions, and I make sure to clear all running apps before playing games. I just feel like now on this ROM, the ram is clearing properly, swiping away apps is freeing up the RAM now.
I think the difference is that this ROM is based on AOSP, whereas before, I was using CM ROM's or Crystal PA which is pretty feature rich. Ill stick with this and see if it will last. This ROM just feels noticeably faster and the UI hasnt crashed once yet, even with a theme on!
Click to expand...
Click to collapse
And? Are you still satisfied with this rom after a while?
Well the 'ROM decay' creeped back in. I tried to counter it by cleaning things up but I had a few problems, nothing was working, I tried fix permissions from ROM toolbox and then my phone stopped booting, tried hard reset with the button on the back, couldn't get into recovery, pretty much died on me. I eventually got into recovery and caches wipes and that didn't work, I tried reinstalling the ROM and gapps without losing my data, it just got stuck on the boot logo, then recovery stopped working again, I eventually got in and had to wipe data, reinstall ROM and I finally got the phone booting again.
I'm not satisfied to be honest, its frustrating that I have to wipe the phone or reflash the roms so often, never has a phone been this bad for me. I'm selling it and moving to the OnePlus One in a few weeks, this phone has been nothing but headaches.
donk165 said:
Well the 'ROM decay' creeped back in. I tried to counter it by cleaning things up but I had a few problems, nothing was working, I tried fix permissions from ROM toolbox and then my phone stopped booting, tried hard reset with the button on the back, couldn't get into recovery, pretty much died on me. I eventually got into recovery and caches wipes and that didn't work, I tried reinstalling the ROM and gapps without losing my data, it just got stuck on the boot logo, then recovery stopped working again, I eventually got in and had to wipe data, reinstall ROM and I finally got the phone booting again.
I'm not satisfied to be honest, its frustrating that I have to wipe the phone or reflash the roms so often, never has a phone been this bad for me. I'm selling it and moving to the OnePlus One in a few weeks, this phone has been nothing but headaches.
Click to expand...
Click to collapse
IF you are going to stay or at least try for the last time, I suggest formatting /boot but please be careful as I dont really know what will happen if you reboot the device while /boot is empty.
As in PC, an empty boot partition will leave an inaccessible Operating System. If in phone they are the same then I guess it can be much repairable.
IF again it fails and you are still staying I suggest extreme formatting by using the PC Companion and start fresh.
These are still suggestions and I hope you will have a headache free adventures with One plus. Good luck
TechnoSparks said:
IF you are going to stay or at least try for the last time, I suggest formatting /boot but please be careful as I dont really know what will happen if you reboot the device while /boot is empty.
As in PC, an empty boot partition will leave an inaccessible Operating System. If in phone they are the same then I guess it can be much repairable.
IF again it fails and you are still staying I suggest extreme formatting by using the PC Companion and start fresh.
These are still suggestions and I hope you will have a headache free adventures with One plus. Good luck
Click to expand...
Click to collapse
Thanks for the advice, For me, its the lack of RAM on this phone which is my problem. After a reboot, i have about 300mb free ram, and as soon as I have more than one simple app running (or just one game), ill get a very slow UI, and I have to be very careful and patient with it or it will crash. To me, that is terrible, why would anyone think this is acceptable for a smartphone to just about be able to run an app and hold the interface together. When the System UI crashes, or the lockscreen, It frustrates me so much! The most important part of a touchscreen phone is the UI, without it, your just staring at a blank screen.
There has to be something deep in this phone (the kernel?) where its memory management is broken in someway, ive never experienced a phone be so unstable with 1GB of RAM. When I bought it, I was really hopeful it would be good, it was higher specced than my last phone, it had 4g, it had jelly bean updates coming out, and at the time, a future update to kitkat, and we had support from FXP and CM. What weve actually got is a half baked attempt at 4.3 by Sony, a cancelled 4.4 update, and weve been moved to legacy support by FXP when CM11 didnt even get to the stable point. We may have lollipop builds coming out which could be the savior for this phone, but im sick of waiting for something which might not happen. I just want to be able to rely on my phone and not spend half my screen on time waiting for something to crash and then restart.
Back on my Optimus L9, it has only 768MB ram and a lower clocked dual core CPU but that could run CM10 fine, I never ever had UI crashes, ever! I got lag from time to time, but nothing crashed. Thie SP has 100mb+ more RAM available and a higher clocked CPU but it feels so much more clunky and unstable compared to the L9, it should be the other way round. On my nexus 7 2012 which is similarly specced to the SP (apart from the tegra quad CPU) I again, had no UI crashes, I had lags, but at least things didnt crash. My friend has the Xperia L, which is lower specced than the SP and is only on 4.1, but again, he never gets UI crashes and generally, his phone can run games smoother than I can even though he has lower specs!
This phone, for me, just doesn't fit my needs. It cant really multi task how I would expect it to, and having the phone pretty much lock up if its writing to internal storage is a joke, installing an app from the play store, and not being able to bring down the notification bar to look at the progress without causing problems, to me just feels like something is seriously wrong. The lightbar was the only thing ive really liked on the phone to this day. At first, I was loving this phone, it was great, the only problem I had on 4.1 was that I couldn't play Injustice because it would close the game after a while. I thought, ill wait for software updates, hopefully Sony will fix it. Then the 4.3 updates came but they were buggy, but I held onto hope because at the time, 4.4 was in the pipeline. Then we got a few more 4.3 updates which did fix some bugs but this RAM problem was still there. So I gave up on Official software and tried out custom stuff. I've tried modified Stock ROM's where you get more features but the same inherent problems are there. Ive tried CM, but there hasnt been a stable release of 4.4 and the snapshot builds have also stopped. Vanir ROM is designed to be stable, its one of their highest priorities with their builds. And I definitely feel the difference, but this lack of RAM becomes more obvious with time, this week, I've seen my UI crash 4 times.
Ive done what you've said about fully starting fresh with PC companion Ive flashed stock FTF's and Ive done the PC companion method, Ive done that at least 5 times in the past. When I first do it, it seems like everything is okay. But without fail, after a month of use (usually less) the phone will bog down and the RAM issues return. Maybe my specific device has faulty RAM or something or maybe the storage is messed up. All I know is, this phone has not been enjoyable for me to use, lower specced phones are out performing it, and its value has plummeted in trade in stores like CEX, my old L9 that I traded into my local CEX is being sold for more money than an SP is.
Im sorry to rant but ive just had enough of this phone.
Ive got to flash the phone fully back to stock for when I sell it, so ill go back to full stock, and see if it will last.
donk165 said:
Thanks for the advice, For me, its the lack of RAM on this phone which is my problem. After a reboot, i have about 300mb free ram, and as soon as I have more than one simple app running (or just one game), ill get a very slow UI, and I have to be very careful and patient with it or it will crash. To me, that is terrible, why would anyone think this is acceptable for a smartphone to just about be able to run an app and hold the interface together. When the System UI crashes, or the lockscreen, It frustrates me so much! The most important part of a touchscreen phone is the UI, without it, your just staring at a blank screen.
There has to be something deep in this phone (the kernel?) where its memory management is broken in someway, ive never experienced a phone be so unstable with 1GB of RAM. When I bought it, I was really hopeful it would be good, it was higher specced than my last phone, it had 4g, it had jelly bean updates coming out, and at the time, a future update to kitkat, and we had support from FXP and CM. What weve actually got is a half baked attempt at 4.3 by Sony, a cancelled 4.4 update, and weve been moved to legacy support by FXP when CM11 didnt even get to the stable point. We may have lollipop builds coming out which could be the savior for this phone, but im sick of waiting for something which might not happen. I just want to be able to rely on my phone and not spend half my screen on time waiting for something to crash and then restart.
Back on my Optimus L9, it has only 768MB ram and a lower clocked dual core CPU but that could run CM10 fine, I never ever had UI crashes, ever! I got lag from time to time, but nothing crashed. Thie SP has 100mb+ more RAM available and a higher clocked CPU but it feels so much more clunky and unstable compared to the L9, it should be the other way round. On my nexus 7 2012 which is similarly specced to the SP (apart from the tegra quad CPU) I again, had no UI crashes, I had lags, but at least things didnt crash. My friend has the Xperia L, which is lower specced than the SP and is only on 4.1, but again, he never gets UI crashes and generally, his phone can run games smoother than I can even though he has lower specs!
This phone, for me, just doesn't fit my needs. It cant really multi task how I would expect it to, and having the phone pretty much lock up if its writing to internal storage is a joke, installing an app from the play store, and not being able to bring down the notification bar to look at the progress without causing problems, to me just feels like something is seriously wrong. The lightbar was the only thing ive really liked on the phone to this day. At first, I was loving this phone, it was great, the only problem I had on 4.1 was that I couldn't play Injustice because it would close the game after a while. I thought, ill wait for software updates, hopefully Sony will fix it. Then the 4.3 updates came but they were buggy, but I held onto hope because at the time, 4.4 was in the pipeline. Then we got a few more 4.3 updates which did fix some bugs but this RAM problem was still there. So I gave up on Official software and tried out custom stuff. I've tried modified Stock ROM's where you get more features but the same inherent problems are there. Ive tried CM, but there hasnt been a stable release of 4.4 and the snapshot builds have also stopped. Vanir ROM is designed to be stable, its one of their highest priorities with their builds. And I definitely feel the difference, but this lack of RAM becomes more obvious with time, this week, I've seen my UI crash 4 times.
Ive done what you've said about fully starting fresh with PC companion Ive flashed stock FTF's and Ive done the PC companion method, Ive done that at least 5 times in the past. When I first do it, it seems like everything is okay. But without fail, after a month of use (usually less) the phone will bog down and the RAM issues return. Maybe my specific device has faulty RAM or something or maybe the storage is messed up. All I know is, this phone has not been enjoyable for me to use, lower specced phones are out performing it, and its value has plummeted in trade in stores like CEX, my old L9 that I traded into my local CEX is being sold for more money than an SP is.
Im sorry to rant but ive just had enough of this phone.
Ive got to flash the phone fully back to stock for when I sell it, so ill go back to full stock, and see if it will last.
Click to expand...
Click to collapse
Its okay and I have read all of your post
It quite saddens me that some people isnt actually having fun with their SP. Shockingly enough, my SP does not face those mentioned problems (heck most of those that appears in the forum) but some exceptions goes to Stock Rom bugs and game problems.
This is my first android phone, I actually always wanted one but i am a teenager - i dont make money. But since my dad bought me this lovely sp, I have finally gained so much knowledge about android and it somehow further strengthens my Linux knowledge.
Maybe I was just lucky. Perhaps. But who knows if something is still wrong with my phone
I understand things will get older - people will buy new phones, developer will stop developing, people who got bored of customising etc. In fact I have seen so much decline of SP since the discontinued 4.4 update.
This is my first smartphone and I love it. It has an awesome community and awesome devs, but now it is getting old. Which quite sad to me.
I am saving for Ara phone (i hope it doesnt fail like smartwatches do). Since you are quite involved with many developments (i mean you customise your phone much like others), I hope your transition to a new device is a breeze. And above all, doesn't have the bugs that SP has.
LOL, I thought I was the only one with a "faulty SP".
My XSP has the exact same problems as yours. It is very annoying to change ROMS (or wipe data) every month.
The RAM is SO BAD on my SP, even though it only have 1GB of RAM, it should be a lot better. I didn't have such problems on my Motorola Defy + as I have with the XSP.
I thank so much that we have very nice developers, always trying to improve our user exp., but for some people like me it's difficult.
TechnoSparks said:
Its okay and I have read all of your post
It quite saddens me that some people isnt actually having fun with their SP. Shockingly enough, my SP does not face those mentioned problems (heck most of those that appears in the forum) but some exceptions goes to Stock Rom bugs and game problems.
This is my first android phone, I actually always wanted one but i am a teenager - i dont make money. But since my dad bought me this lovely sp, I have finally gained so much knowledge about android and it somehow further strengthens my Linux knowledge.
Maybe I was just lucky. Perhaps. But who knows if something is still wrong with my phone
I understand things will get older - people will buy new phones, developer will stop developing, people who got bored of customising etc. In fact I have seen so much decline of SP since the discontinued 4.4 update.
This is my first smartphone and I love it. It has an awesome community and awesome devs, but now it is getting old. Which quite sad to me.
I am saving for Ara phone (i hope it doesnt fail like smartwatches do). Since you are quite involved with many developments (i mean you customise your phone much like others), I hope your transition to a new device is a breeze. And above all, doesn't have the bugs that SP has.
Click to expand...
Click to collapse
Well atleast you have started on a better android device than my first one. My first was a ZTE Skate and this was back in the gingerbread days. 512MB RAM, Single core CPU, barely any internal storage. Im very used to using android in a minimalist way, but the SP just takes it to a whole different level for me, i cant take it! Im glad that you arnt having all the same problems Im having. The fact that not everyone is getting the problems is a frustration because unless its a widespread problem, people wont really be pulling together to fix it because they dont understand/experience the problems. It has to be some kind of manufacturing defect, maybe certain batches of RAM/Storage chips used in the SP are defective/bad performers.
I hope the XSP continues to work well for you!
Bruno_Puzoni said:
LOL, I thought I was the only one with a "faulty SP".
My XSP has the exact same problems as yours. It is very annoying to change ROMS (or wipe data) every month.
The RAM is SO BAD on my SP, even though it only have 1GB of RAM, it should be a lot better. I didn't have such problems on my Motorola Defy + as I have with the XSP.
I thank so much that we have very nice developers, always trying to improve our user exp., but for some people like me it's difficult.
Click to expand...
Click to collapse
Its a very weird problem, but its definitely RAM/Storage related.
I agree with you about the devs, I appreciate their hard work, it is great having all these ROM's to choose from when trying to solve the problems. It just seems it doesn't matter which ROM you are on, the problems will always be there. The problem must lie within the hardware or deep in the software side of things, beyond the ROM's like in the kernel or something. I dont know enough about those sides of a phone, but I can see just from using the phone, something isnt right.
It sucks that you are facing the same problems, but its nice to know im not alone in my experiences, its not just me.
If only we knew what the issue was, maybe there would be a chance to solve the issue.
I have the same problems with my phone exactly and am going to smash it with a hammer when I get a new phone. It is indeed so frustrating, I expect much more from sony!
i stopped to mess up with custom kernels, stock 207 is the best option.
Ondemand cpu governor + underclock to 1500mhz + greenify
Battery life + perfomance
My usage:
4 hours online gaming per day
+ some skype calls
Was about to put it as a [Question] but decided to place it as possible troubleshoot and experience for anyone with same problem.
Damn, was not expecting this and out of the blue.
I used my mi11ultra normally today, on Xiaomi.eu 12.5.11.0.
I order from Uber, while i waited, was playing asphalt 9. Then poof, lost my wifi connection. Could use mobile data.
At 30% battery remaining.
Couldn't connect to wifi and decided to reboot my phone.
For a few tries turning on wifi reboots my phone after freezing for a few seconds.
Sometimes it doesnt even turn on(no blue icon)
Turn off phone and let the heat dissipate. it's not hot today, and im using FHD res at 120hz, also haven't been playing for a long time, maybe 30minutes.
Tried restart i wiped daivilk and art cache on twrp.
Tried updating just now to 12.5.12.0 , nothing.
Tried Reset Wifi, bluetooth and mobile, nothing.
It lets me, sometimes, enable wifi, search for networks, connect and the wifi shuts down after about 5 seconds.
Right now as i was writing this and decide charged the phone so i could factory wipe. Im at 60% battery and the issue is gone for now.
I posting BOLD on battery comment because i found it that that was the issue oddly enough.
I'm charging the phone till 100% and will let you know if it happens again. "i hope i don't jinx it."
My greatest fear is that i would have to send it to repairs which takes time.
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
xwonic said:
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
Click to expand...
Click to collapse
Was it a Chinese version or global originally?
Chinese
speedtripler said:
Was it a Chinese version or global originally?
Click to expand...
Click to collapse
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
xwonic said:
Chinese
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
Click to expand...
Click to collapse
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
speedtripler said:
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
Click to expand...
Click to collapse
It had warranty, yes, and it was the Wifi module but ultimately i decided to get a refund.
Curiously i read it's a Mi 11 Series issue, if you decide to search in google "mi 11 wifi issue".
So i have to say farewell to Mi 11 Ultra Community.
My decision was done with several annoyances from Xiaomi and not for the hardware itself, all the crazy features and camera are badass.
Lack of optimization,
Missing gestures navigation with different launchers(which other manufactures already fixed long time ago in android 11...)
Generic updates(same changelog for all devices) and lack of transparency.
I still advise my friends and family to get a Xiaomi device for what they get for the price and i keep getting impressed by the hardware in these devices.
Also love the ecosystem and new features being added every MIUI version.
I got a POCO M3 with Android 10 Xiaomi.eu, that works gesture navigation and doesn't need third party apps.
I think it all comes down to software, because in the hardware department there isn't any complain from me.
I might even get a Poco X3 Pro for 170€ for a secondary device and install some AOSP rom there.
This decision might change in the future since Xiaomi said they are implementing a team dedicated for software issues, but not to this device.
Until then goodbye
Just my opinion,
seems like all hardware issues are happening to people who flashed non stock rom's.
Fingerprints before, and now wifi and Bluetooth.
Glad I am with global version and stock rom (tried .eu for a while and found it garbage). fingers crossed to stay happy
I've had the 11t pro for a little more than 2 months and even though it's not the best device out there, it does a pretty good job for a budge phone with such specs(in my opinion)
a few things I've noticed and not sure if others share the same frustration are:
after upgrading to miui 13.0.4 I noticed in top left corner (mic/cam)icons that show up when I open any app using them...any way to disable them?
when playing a game, I noticed phone sometimes lags so badly(though it's not a demanding game, visual wise) and I can't even have a whatsapp video call while playing without phone going terribly slow until I end the game.
sometimes out of the blue, the phone becomes super laggy even with no apps running, and I can't figure out what is causing it, so I end up restarting it.
if anyone has noticed anything else or has got any tips/tricks please share
p.s: is it doable to flash an eu rom on a device with global rom? I was told difference between both is google pay on european which doesn't exist on global, but I have it on mine.
RockyAJ said:
I've had the 11t pro for a little more than 2 months and even though it's not the best device out there, it does a pretty good job for a budge phone with such specs(in my opinion)
a few things I've noticed and not sure if others share the same frustration are:
after upgrading to miui 13.0.4 I noticed in top left corner (mic/cam)icons that show up when I open any app using them...any way to disable them?
when playing a game, I noticed phone sometimes lags so badly(though it's not a demanding game, visual wise) and I can't even have a whatsapp video call while playing without phone going terribly slow until I end the game.
sometimes out of the blue, the phone becomes super laggy even with no apps running, and I can't figure out what is causing it, so I end up restarting it.
if anyone has noticed anything else or has got any tips/tricks please share
p.s: is it doable to flash an eu rom on a device with global rom? I was told difference between both is google pay on european which doesn't exist on global, but I have it on mine.
Click to expand...
Click to collapse
The mic and camera icons is an Android 12 security feature to let you know when you might be listened to or seen, and I don't think it can be removed.
No idea regarding the game and slow downs. Sometimes with a major version change it is better to factory reset and set up from scratch, so that might help.
Yes you can flash different ROMs from other regions. The IMPORTANT thing is if your device came with a Global ROM and you unlock your bootloader and flash the Europe ROM, then you must not lock the bootloader again, if you do it will brick your device. You can put back the original Global ROM then lock again.
Hope that help.s
RockyAJ said:
I've had the 11t pro for a little more than 2 months and even though it's not the best device out there, it does a pretty good job for a budge phone with such specs(in my opinion)
a few things I've noticed and not sure if others share the same frustration are:
after upgrading to miui 13.0.4 I noticed in top left corner (mic/cam)icons that show up when I open any app using them...any way to disable them?
when playing a game, I noticed phone sometimes lags so badly(though it's not a demanding game, visual wise) and I can't even have a whatsapp video call while playing without phone going terribly slow until I end the game.
sometimes out of the blue, the phone becomes super laggy even with no apps running, and I can't figure out what is causing it, so I end up restarting it.
if anyone has noticed anything else or has got any tips/tricks please share
p.s: is it doable to flash an eu rom on a device with global rom? I was told difference between both is google pay on european which doesn't exist on global, but I have it on mine.
Click to expand...
Click to collapse
After updating from 12.5.21 to 13.0.9 I have experienced lags in various situation as well. After that I unlocked bootloader and flashed xiaomi.eu 13.0.4, but it's not much better. Now I'm thinking about downgrading to xiaomi.eu 12.5.10 or stock 12.5.21, that worked very well.
antykat said:
After updating from 12.5.21 to 13.0.9 I have experienced lags in various situation as well. After that I unlocked bootloader and flashed xiaomi.eu 13.0.4, but it's not much better. Now I'm thinking about downgrading to xiaomi.eu 12.5.10 or stock 12.5.21, that worked very well.
Click to expand...
Click to collapse
I use xiaomi Eu rom without any problem.
it is preferable for the first installation to use the script "windows_fastboot_first_install_with_data_format" then for the updates"windows_fastboot_update_rom.bat".
NOSS8 said:
I use xiaomi Eu rom without any problem.
it is preferable for the first installation to use the script "windows_fastboot_first_install_with_data_format" then for the updates"windows_fastboot_update_rom.bat".
Click to expand...
Click to collapse
I know that It was clean installation. On stock with MIUI 13 I had the same problems.
I'm now on version 13.0.9, jumped to this version from 12, clean installation. What I'm finding is Wi-Fi and Bluetooth turnoff around 23:30 each night, this seems to be some deliberate power saving function when the phone detects the person is likely asleep, and I can see in my access point log exactly when Wi-Fi disassociates and turns off, only turning on again in the morning when I unlock the phone. This may be related to having DND turned on using the schedule option, this is set from 22:00, but I have this set to still be disturbed by my contacts, so need Wi-Fi to remain connected. This all worked fine on version 12.
I can't see any settings under Wi-Fi or battery management to disable this. Anyone else seeing the same thing or have a solution?
PhilipL2021 said:
I'm now on version 13.0.9, jumped to this version from 12, clean installation. What I'm finding is Wi-Fi and Bluetooth turnoff around 23:30 each night, this seems to be some deliberate power saving function when the phone detects the person is likely asleep, and I can see in my access point log exactly when Wi-Fi disassociates and turns off, only turning on again in the morning when I unlock the phone. This may be related to having DND turned on using the schedule option, this is set from 22:00, but I have this set to still be disturbed by my contacts, so need Wi-Fi to remain connected. This all worked fine on version 12.
I can't see any settings under Wi-Fi or battery management to disable this. Anyone else seeing the same thing or have a solution?
Click to expand...
Click to collapse
Did some more Googling, found others having the exact same issue, see
https://www.reddit.com/r/miui/comments/tlxjjh
Appears to be a deliberate power saving feature, where the option to disable it, due to a bug or oversight, isn't available.
What is it with Xiaomi and their excessive battery saving modes.
wouldn't you find it under battery settings?
PhilipL2021 said:
I'm now on version 13.0.9, jumped to this version from 12, clean installation. What I'm finding is Wi-Fi and Bluetooth turnoff around 23:30 each night, this seems to be some deliberate power saving function when the phone detects the person is likely asleep, and I can see in my access point log exactly when Wi-Fi disassociates and turns off, only turning on again in the morning when I unlock the phone. This may be related to having DND turned on using the schedule option, this is set from 22:00, but I have this set to still be disturbed by my contacts, so need Wi-Fi to remain connected. This all worked fine on version 12.
I can't see any settings under Wi-Fi or battery management to disable this. Anyone else seeing the same thing or have a solution?
Click to expand...
Click to collapse
sorry previous reply was for you, but I used quote, not reply
RockyAJ said:
wouldn't you find it under battery settings?
Click to expand...
Click to collapse
That appears to be the bug in that the options to disable it are missing. There are no settings anywhere to disable it.