Develop Bugs

Splash top 2 brick?

Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?

Its bricked?
So you put it in the trash or sent it back to ASUS?

I'm going to go out on a limb here and say this is not related to splashtop.

I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.

Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium

tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium

Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium

Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.

Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...

sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.

PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.

my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:

Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.

xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:

Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?

Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers

I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.

qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.

Kernels for cymod10.1

Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium

cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Look in the CM 10.1 thread I pointed out which are updated and compatible with the latest.

I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.

Aerowinder said:
I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.
Click to expand...
Click to collapse
Might be the case, but the flicker is resolved for me flashing a 3rd party kernel. I was getting it really bad, like screen would go black and come back 10 times with in 2 seconds so it was nasty. Not sure why it was happening on stock and not custom...

I'm not having any battery problem. Just screen flickering and random reboots. Any fix?
Sent from my SGH-T999 using xda premium

Did you not read what I posted? http://forum.xda-developers.com/showpost.php?p=40525936&postcount=11050

Sorry. I didn't refresh the page so I didn't see what you said. But I would try to flash a new kernel now. Thx for the help.
Sent from my SGH-T999 using xda premium

cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:

CodyRst said:
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:
Click to expand...
Click to collapse
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.

mt3g said:
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.
Click to expand...
Click to collapse
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.

CodyRst said:
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.
Click to expand...
Click to collapse
Almost all 4.2.2 roms that have the latest merges have reports of it happening. Not alarmed at all, it may end up happening to you soon enough lol.

Would lowering the maximum CPU frequency to 1459 MHz save battery?
Sent from my SGH-T999 using xda premium

You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.

Aerowinder said:
You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.
Click to expand...
Click to collapse
I'm not having problem with battery. I just want to save more so it can last long.
And it seem like battery life on cymod10.1 with katoon kernel for me is draining pretty fast compare to stock cymod 10.1 and stock kernal
Sent from my SGH-T999 using xda premium

careful of 10.1 nightlies from 24/25

for alot of people getting blue screen during first boot and have to battery pull and roll back to 22nd, just warning

my phone still getting blue screen on 26th nightly too

KronicSkillz said:
my phone still getting blue screen on 26th nightly too
Click to expand...
Click to collapse
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.

rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
You didn't try it yourself did you? Well it doesn't even work with the built-in CM Kernel. Even tried a full wipe - to no avail. We'll have to wait for more stable ones. :fingers-crossed:

rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
what is with the assumptions, all i did was update run the updater with 26th update and it blue screened after lg logo, so YES IT DOES HAVE BLUE SCREENS... take the idiotic attitude somewhere else when ur the one whos wrong
this is a widespread problem if u knew everything like you act like you do you would have already known that

Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2

rani9990 said:
Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You people..? What do you mean, You people..?
Sent from my LG-P930 using Tapatalk 2

has anyone tried the daily from today yet?
edit -
since no one else is talking i tried flashing 27th nightly and still BSOD upon first boot, confirmed the CM mods are finally aware of the issue, itll probably be fixed for tomorow.

Same problem for 27/05
Sent from my LG-P930 using xda app-developers app

ultimate_neet said:
Same problem for 27/05
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
yes I Still get the same problem

the 28th nightly is currently downloading it should be fixed today but ill post after i have it installed to verify.

the nightlies from today have fixed the BSOD on firstboot. confirmed.

YUP, it's fixed. But i have some problem installing the WIND Kernel, does someone knows something about it?

same here i reflashed to nightly from today to go back to stock kernel until its fixed

4th time I had to factory restore. This is unbelievable.

Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium

If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.

Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.

I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app

Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app

player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.

Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app

Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app

Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.

You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app

Delayed notifications on watch

Hey Everyone, this watch has been driving me crazy. When someone calls the watch doesn't notify until after I pick up or after the caller has gone to voicemail.
Tried factory resetting the watch
Tried uninstalling Android Wear
Tried a different watch face
Tried Facer
So far no luck and this has been since day one. Called Huawei and they want me to send it in, thought I would try here and see if there is another solution before doing so. Thanks

I have never had a problem with mine but I read where someone factory reset the phone and it fixed it. I can't post a reference as it was something I read but don't remember where.
Sent from my Nexus 6 using Tapatalk

crawrj said:
I have never had a problem with mine but I read where someone factory reset the phone and it fixed it. I can't post a reference as it was something I read but don't remember where.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Tried that at least 5x and also removed Android wear from my phone. Not a great first impression of Huawei, I have had almost every other Android watch and never had this issue.

Ok you didn't mention it in the OP so I thought it would be worth a shot. If you have factory reset both devices and tried it while the phone was vanilla, then you would want to return it.
Sent from my Nexus 6 using Tapatalk

I fixed that issue with a older AW version.
www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-1-1-2113877-android-apk-download/
Tested since a week and so far so good.
Give it a try
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

duchkata said:
I fixed that issue with a older AW version.
www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-1-1-2113877-android-apk-download/
Tested since a week and so far so good.
Give it a try
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
The old firmware was no better but I'm willing to give it a try. Are there instructions on how to roll it back?

I desinstalled the latest version, and installed the version provided in the link.
I know the older version is not better but at least, I don't miss a call phone anymore.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

duchkata said:
I desinstalled the latest version, and installed the version provided in the link.
I know the older version is not better but at least, I don't miss a call phone anymore.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, for some reason I thought the link was for the firmware on the watch.

I agree that new Aw provided some issues. Mine HW disconnect from smartphone all the time now after upgrade. It started just after installing updated AW.