Develop Bugs

Common Blu Kuban problems

I am running the Blu Kuban, and have been having problems with talk failing and random reboots. I follow the Rom posts from devs pretty regurly. I have seen that Ruj, and others reccomend removing the themed version of talk, and installing the stock version that is availble in the Rom updater. I tried this about a week ago, but even after fixing permissions in the recovery my phone would keep restarting till I reinstalled the rom. I was working just fine after a fresh, and wiped out install up untill a few days ago. I am getting the messages again that my talk app is failing, or sometimes not responding. It was not untill I started messing around with goveners that I started having this issue. I had the default hyper after install, but switched it to wheatly. It was not untill I switched to hotplug two nights ago that I have been having issues with talk. I was having the same problem with the newset Kuban kernal with random reboots of the phone, and thought it was with govener, as that is all I have changed in Ex tweaks. The mods I have installed are; Blank pull down, No rotate/no landscape/no crt, In call sms notification, and finally no battery bar. My restarts of the phone have been random, they can be from anything from loading facebook, turning on wifi, adjusting phone volume, to even putting phone to sleep. I guess after my long rant of problems is there anything that I can do differently to make phone run better? I am not overclocking or underclocking. Have not played with voltages. I turned my screen off profiles off too. I am thinking that unless it gets worse, I will wait for Ruj, to release any new kinds update. Is it the kernel that is giving the problem? I saw someone posted to try older kernel version, is that very dependable?
Also I know this post is getting pretty long, but can someone please tell me if there is any sort of geographical list of modems that work best in certain area's? http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/Modems this showed me that there is a bunch to try, but I want to know which ones work best in area before I go messing around. Does Sprint use different ones in different locations is what I am asking about modems.

There is a talk fix in the 4th post of the faq.
As far as the modems, they are kind of a subjective choice. My phone is best on fg20 and my wife uses fe22. You just goes try them all until you get one you like. I currently use the latest Kuban kernel and do not have any reboot issues. If you keep having issues I would recommend a fresh install or setting extweaks back to the defaults, then making adjustments one at a time until you are happy with the setup.

ROM issue or Phone issue?

Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.

gaveup said:
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
Click to expand...
Click to collapse
It's quite possible that your phone isn't handling the 3.4 kernel very well. Although, did you try Task's last update (4/9)? I haven't had lockups on the last couple builds.
But if you keep getting them, revert back to a 3.0 kernel/ROM build until 3.4 is more stable.

[Q] Has switching to a custom kernel solved anyone's random reboots?

I bought my N7 (Flo) in early January and am loving it except for the random reboots. I did a factory restore and on the first boot got up to around 92hrs of uptime with about 50% battery usage before a crash. Subsequent boots aren't quite hitting that mark. As everyone knows it's hard to tell at exactly what intervals as it will crash while it is sleeping, not just in use.
Has switching to a custom kernel provided better stability for anyone?

Yes. I can only speak for CM11 but flashing Glitch kernel completely stopped the reboots and also the random buzzing noise from the speakers.
I didn't try the kernel on stock (also had reboots) but go ahead it might work. Make a nandroid first.
I really thought the reboots were hardware related but after going through three devices, 16 and 32gb models and 06, 07 and 08 build dates, they all randomly rebooted. Glitch has solved it (again at least on CM11). I'm sure it's a software problem now.

So, here's my experience with this. I bought my first nexus 7.2, at a best buy in north Dallas, in October. I experienced random reboots, right out of the box, about once a day, usually when I was browsing chrome, or when the tablet was sitting on the home screen without being touched. My gf bought a nexus 7.2 as well, at the same store in November, and she was not experiencing any random reboots, hers has always been stock, to this day (my suspicions began). I figured it was a software, or app problem, and waited for a fix from Google, or my app developers. Tried various custom Roms in the meantime (cm11, dirty unicorns, silmrom, and many more). I also tried various kernel's, in combination with said Roms (Franco, ElementalX, glitch, bulletproof). I had random reboots with all combinations of Roms and kernels. Did a factory data reset after every update from Google, and tried it for a week or so every time. Still experienced random reboots. I finally got fed up and took my table back in early January, to the same best buy in north Dallas. After receiving my second tablet, I kept it stock for a week, and then restored my preferred twrp backup, that I had taken with the rebooting tablet ( stock 4.4 krt16s, xposed framework, ElementalX 2.2 @1.7 and 450, with the motoX dalvik and bionic patches). With the new tablet, I have not experienced one random reboot, either with the stock software, or the custom software.
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Whatever you choose to do, I hope it works out for you, the reboots were personally driving me crazy, and I'm glad my second tablet doesn't reboot like its got a mind of its own.

thisguysayswht said:
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Click to expand...
Click to collapse
I also bought mine at a Best Buy but am a few weeks out of the return period. I'll give it a try and see if they'll take it back. I was really trying to avoid sending it to Asus. Thanks for your input.

I never had any random reboot issues however, it might have been due to having it running on CleanRom 2.6 and ElementalX Kernel since almost day 1. These two make the device so snappy I don't even care.

[Q] Help troubleshooting soft resets. Possible firmware problem.

These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.

Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.

So is there no fix/ solution for random reboots?

I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?

mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.

Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."

I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.

I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/

Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.

So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.

Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."