Database Develop

phone randomly died....no life after running a simple app

OK so last night I was running aokp and flashed fauxs new test kernel everything was running great I oced the phone to 1.8 and fired up CPU master free made sure everything was good then went into antutu then out of nowhere there was a quick flash and my phone was lifeless. Now this freaked me out because I have never seen nothing like this phone usually just will reboot if oced to high or whatever ....and I have been doing this phone thing for awhile so battery was charged also ....now phone would not turn back on and the only life I could get out of it was a red blinking light when connecting charger or comp. And I managed to get into download mode but this download mode I have never seen before....maybe lg version? Idk . the red light reminded me of xboxs red eye of death. I had nothing but a red blinking light would not power on with any key combo at all. I even let it sit on charger and nothing . I just wanted to make u guys aware of this maybe it was a weird hardware failure but it sucks to know that this could possibly happen. Here are a few pics I grabbed
Red light
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The download mode I've never seen before weird thing is when I connected to comp it did nothing I even checked Odin

can you get to fastboot? Hold both volumes and power on. If so, flash stock rom again
Another way to try to get to fastboot is to plug in and then hold both volumes

Odin is a Samsung application.
Sent from my Galaxy Nexus using xda app-developers app

Why the f you need to OC it to 1.8? Nonsense to me. If the phone bricks, you deserve a new paperweight.

So you overclocked the CPU with a test Kernel and now you are wondering why you maybe fried it?
Btw. for what exactly do you need those 1.8Ghz x 4 on a phone that is more than fast for everything?

Testraindrop said:
So you overclocked the CPU with a test Kernel and now you are wondering why you maybe fried it?
Btw. for what exactly do you need those 1.8Ghz x 4 on a phone that is more than fast for everything?
Click to expand...
Click to collapse
This kills me... Ruin your phone by doing something stupid and you do not deserve a replacement.
sent via xda premium with nexus 7

this.
Odin is used only for samsung phones

lazinase said:
Why the f you need to OC it to 1.8? Nonsense to me. If the phone bricks, you deserve a new paperweight.
Click to expand...
Click to collapse
Dude why are u trolling u geek gtfo why do u care what I do with my phone people do that everyday with their phones u dork now leave and yes people ive tried all of that believe me I am pretty tech savvy crazy thing is that another guy and another thread is having the same issue that is freaky and I know that odin is a Samsung applications that is why that particular download mode looked weird

The title of your post is somewhat misleading.
The death of your phone was not "random", nor was it caused by "running a simple app".

Richieboy67 said:
This kills me... Ruin your phone by doing something stupid and you do not deserve a replacement.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Don't be jealous bud what are u so butthurt for dude! I already have one went out and grabbed one want pics? Jealousy is a moths!

Testraindrop said:
So you overclocked the CPU with a test Kernel and now you are wondering why you maybe fried it?
Btw. for what exactly do you need those 1.8Ghz x 4 on a phone that is more than fast for everything?
Click to expand...
Click to collapse
tell me why would a developer put that on a website then why would there be a over clocking kernel? Are u guys kidding me people oc everyday and because this happened now it is bad gtfo!

Robert_W said:
can you get to fastboot? Hold both volumes and power on. If so, flash stock rom again
Another way to try to get to fastboot is to plug in and then hold both volumes
Click to expand...
Click to collapse
Thank u for trying to help man

Devs aren't omniscient. Presumably he'll pull it if it's causing bricks. Sucks to be the first one to try it..

It is so remarkably stupid first of all to be messing with overclocking a phone less than a month after you bought it, but fine, I understand people wanting to tinker. It is so remarkably stupid second of all to be overclocking a phone less than a month old that ALREADY HAS THERMAL THROTTLING ISSUES. Seriously, so ridiculously stupid. And no, your title is nonsense. Its not the "simple app" that bricked your phone, its that you are running an experimental kernel for some stupid reason and chose to overclock to some stupid high frequency for some stupid reason and then OF COURSE tried to run a benchmark that ALREADY causes the CPU to thermally throttle on stock, for some stupid reason.
Please no one emulate this stupid behavior.

TonyHoyle said:
Devs aren't omniscient. Presumably he'll pull it if it's causing bricks. Sucks to be the first one to try it..
Click to expand...
Click to collapse
exactly! I knew the chance I was taking and obviously something bad happened not a big deal I just wanted to make other people aware I have been doing this for a long time and to see this was freaky

I don't think he's jealous, he's probably upset that people will still overclock and do VERY unsafe modifications to a beast of a phone that just came out. Even developers haven't fully grasped the Nexus 4. Quad core clocked at 1.5 GHz is more than enough, I'm a PC Builder and I can tell you the extra 300 MHz is hardly noticeable. Now a 600 MHz to a 1 GHz increase would be noticeable. However, you would fry that processor like bacon. GOOD LUCK, I really hope you do get it working again, I love my Nexus 4 so I can imagine how you feel dude.

sarni84 said:
Dude why are u trolling u geek gtfo why do u care what I do with my phone people do that everyday with their phones u dork now leave and yes people ive tried all of that believe me I am pretty tech savvy crazy thing is that another guy and another thread is having the same issue that is freaky and I know that odin is a Samsung applications that is why that particular download mode looked weird
Click to expand...
Click to collapse
My eyes hurt.
I started my Android life since G1 then Nexus One. Did I ever OC my phones? Yes. Did I ever brick my phones? No. See that's the difference.

shadymouse said:
I don't think he's jealous, he's probably upset that people will still overclock and do VERY unsafe modifications to a beast of a phone that just came out. Even developers haven't fully grasped the Nexus 4. Quad core clocked at 1.5 GHz is more than enough, I'm a PC Builder and I can tell you the extra 300 MHz is hardly noticeable. Now a 600 MHz to a 1 GHz increase would be noticeable. However, you would fry that processor like bacon. GOOD LUCK, I really hope you do get it working again, I love my Nexus 4 so I can imagine how you feel dude.
Click to expand...
Click to collapse
your absolutely right and I am NOT going to argue that but this is why we are at XDA right? So for this to happen is kind of freaky but I did not know what happened see I have done this with many other phones you know it doesn't matter if it first came out 3 weeks ago or whatever if you shouldn't have happened who knows what caused it maybe it wasn't the kernel maybe it was something totally different maybe it was a combo of the things

lazinase said:
My eyes hurt.
I started my Android life since G1 then Nexus One. Did I ever OC my phones? Yes. Did I ever brick my phones? No. See that's the difference.
Click to expand...
Click to collapse
Lol OK buddy OK .....

lazinase said:
My eyes hurt.
I started my Android life since G1 then Nexus One. Did I ever OC my phones? Yes. Did I ever brick my phones? No. See that's the difference.
Click to expand...
Click to collapse
Your a troll you obviously do not help people and I really do not think you know your stuff look at your thanks count........Cmon bro! Get real your just a laptop gangster

New Google Wallet

Here's the apk
http://goo.gl/Qal2tm
Download the zip from the link. Extract the apk and install like normal.
Credit to androidpolice for getting it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk 4

It looks exactly like PayPal's new app.
Sent from my HTC One using xda app-developers app

Mine just updated to the new version. But then again im stock and unrooted.

Has anyone been able to get it to work on non-Sense based ROMs? I've seen a few out there that say it will work, but they involve using cracked apks and I just don't feel safe putting my financial information into one of those.
(Edit) I know its still early on with it, just popping the question out there to see if anyone has had success tinkering with it yet.(/edit)

Looks like the same version that is in the PlayStore currently.

im0rtalz said:
Looks like the same version that is in the PlayStore currently.
Click to expand...
Click to collapse
Yes, it is. Keep in mind, however, that this is a staged rollout and as a result not everyone can see it in the Play Store.

I am guessing that the rollout is based on device so I would honestly imagine all Sprint Ones can see it but that is just a complete guess.
Sent from my HTCONE using Tapatalk 4

The update broke the app for me... Went from making nfc payments on the regular to not being able to open the app without it stopping immediately.
{update} uninstalling and re-installing the app fixed the "unexpected stop" issue for me, in case anyone else had the same issue. {/update}
(and shouldn't this be in the apps section?)
Sent from my beige box using xda premium

Am amazed people would trust a random apk on xda-dev for Wallet. Then again, a malicious ROM dev could have back door access to all your accounts, so I guess it's not much different.

Still doesn't seem to allow NFC payments for stock cyanogenmod though. Not a huge deal as I don't need at all though would have been nice if they would enable the NFC payments for all phones too. The app just adds the ability to send money from friend to friend.

gobaers said:
Am amazed people would trust a random apk on xda-dev for Wallet. Then again, a malicious ROM dev could have back door access to all your accounts, so I guess it's not much different.
Click to expand...
Click to collapse
This random apk from a dev on xda is cryptographically signed by Google. It is identical to the one put up in the market.

epyon22 said:
Still doesn't seem to allow NFC payments for stock cyanogenmod though. Not a huge deal as I don't need at all though would have been nice if they would enable the NFC payments for all phones too. The app just adds the ability to send money from friend to friend.
Click to expand...
Click to collapse
Google's explanation for this is that, with a rooted and/or romed phone, they (Google) do not have the same confidence in the security of your banking data. I think it's an ass covering situation so that if something does happen, people can't blame the app (and Google)
Sent from my beige box using xda premium

This is actually a problem not with cyanogenmod but with the HTC one's implementation on cyanogenmod(maybe others). My nexus s running cyanogenmod works with google wallet's nfc perfectly. Usually they just give a warning saying that your phone is rooted that that it might not be secure.

epyon22 said:
This is actually a problem not with cyanogenmod but with the HTC one's implementation on cyanogenmod(maybe others). My nexus s running cyanogenmod works with google wallet's nfc perfectly. Usually they just give a warning saying that your phone is rooted that that it might not be secure.
Click to expand...
Click to collapse
So what you're essentially saying is that it isn't a problem with Cyanogenmod but rather that it is a problem with Cyanogenmod's official builds for the HTC One? It's like saying it's not Steve's fault but that it's actually Steve's fault.

rougegoat said:
So what you're essentially saying is that it isn't a problem with Cyanogenmod but rather that it is a problem with Cyanogenmod's official builds for the HTC One? It's like saying it's not Steve's fault but that it's actually Steve's fault.
Click to expand...
Click to collapse
I'm trying to say its not global to cyanogenmod builds across phones and I don't belive google is actively blocking it for the sole reason it is a aftermarket ROM. From my understanding to get it working the build.prop just needs to be modified to match the original phone, which changing these values in cyanogenmod's code is a design decision/organizational decision causing google wallet to think that its a phone that might not have nfc. I'm sure there is a way for them to detect NFC but they are taking the safe secure road and using some sort of lookup for each phone.

epyon22 said:
I'm trying to say its not global to cyanogenmod builds across phones and I don't belive google is actively blocking it for the sole reason it is a aftermarket ROM. From my understanding to get it working the build.prop just needs to be modified to match the original phone, which changing these values in cyanogenmod's code is a design decision/organizational decision causing google wallet to think that its a phone that might not have nfc. I'm sure there is a way for them to detect NFC but they are taking the safe secure road and using some sort of lookup for each phone.
Click to expand...
Click to collapse
I've gone through pretty much every line where the CM team did something that would break compatibility(such as using m7spr instead of m7wls) and it has never worked for me. They may have removed something from the build.prop that caused it, but I don't really see that as likely. I mean if all that was needed was a slight change to that it would already have been done and merged into the nightlies.

rougegoat said:
I've gone through pretty much every line where the CM team did something that would break compatibility(such as using m7spr instead of m7wls) and it has never worked for me. They may have removed something from the build.prop that caused it, but I don't really see that as likely. I mean if all that was needed was a slight change to that it would already have been done and merged into the nightlies.
Click to expand...
Click to collapse
I tried the same and got nothing. I don't what they're using to verify now.

This post discuses what was done to crack the apk and make Tap-to-Pay work. I don't trust cracked financial apps though, regardless of how open they are about it. Maybe it could lead to a fix for CM10.2?

rougegoat said:
This post discuses what was done to crack the apk and make Tap-to-Pay work. I don't trust cracked financial apps though, regardless of how open they are about it. Maybe it could lead to a fix for CM10.2?
Click to expand...
Click to collapse
Yea that apk worked. The apk was modded to get galaxy nexus as os from whatever phone its installed to. So NFC tap and pay will work but it also need wallets cert keys which cm 10.2 does have so nfc stuff can work. I'm not sure what we can do in rom that's similar. It seems it's not getting info from the build.prop
Sent from my HTCOne using Tapatalk 4

I wonder if a fix for this type of issue is something we can expect as a result of Cyanogenmod going commercial. It may be easier for them to get general approval as a company than it was for them to get it as a bunch of random developers working for the greater good.

I am loosing my mind! Note eating battery and superslow

Hi!
My Note has for a quite long time now been slow, laggy and eating battery.
Didn't mind, had a car charger, suspected old battery and clogged storage.
About a week ago it came to a complete stop, taking 30 sec to open facebook.
And typing in Swiftkey an impossibillity, having keystrokes on a 5-10sec lag.
So finally i got a new battery, whiped the phone clean.
Flashed the phone with a fresh rom (Team Union JB XXLT4 V7)
Installed my apps manually, making shure no crap cache was brought.
Formatted internal storage and got a new 32Gb SanDisk Ultra card.
Fresh start, fast phone right? no.
Apps still unusably slow, typing on swiftkey impossible without lagging.
Battery from a full charge last about 6h with light usage.
Would like to stay on TW only for the MHL capability, but now i am open to anything.
Can't really afford a new phone, so if this can't get resolved ill switch to my old 3GS.
What do i do now?
What can i try?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The screenshots are from different days and scenarios, but changing governor or other settings gives me about the same result.
Just listened to som music, and some light surfing, thats about all. Battery blames is all on the screen and os about 33% & 33%.

YOu should try AOSP/AOKP Roms!!!

I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.

have you try to replace new battery ?!

NoteboyTech said:
YOu should try AOSP/AOKP Roms!!!
Click to expand...
Click to collapse
Thanks for the reply, but i am afraid ill have the same issues.
Azeazezar said:
I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.
Click to expand...
Click to collapse
Good suggestion, i'll run top once in a while, see i find anything.
nokia2002 said:
have you try to replace new battery ?!
Click to expand...
Click to collapse
Well, yeah couldn't find any original though, and don't want to wait weeks for a shipment, so got a copy brand "ENERGY" spacy logo and made here in Thailand. Only 2350mAh compared to the original 2500mAh.
Found that the new battery didn't really make any difference, about the same.
So worried i got new but crappy battery I'm now back on original, without any noticable change.
Considering getting a external charger and carrying the spare battery, that is not really a solution either.
Got get this phone working reliably soon, or i need to find a replacement.
Appreciate the tips, and ill try and make a study with "top" and get back to you guys.
Maybe i have a energy hog after all...

It's a pain in the butt, but it looks like the only way to resolve it is to do a clean wipe, then install each
app one by one, giving yourself a day or two of usage. Sucks, but it sure sounds like one app is
screwing up another one. Any chance you can (shudder) use a "memory cleaner/program closer"
after you use each app, to make sure it's closed as a test? Sounds like something sure is
interacting with something else.

USe Greenify and hibernate all apps!!!

Check your Google account settings. If you have sync Internet ticked disable it.
Sent from my GT-N7000 using XDA Premium 4 mobile app

You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app

JellybeanSandwich said:
You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
That is with wifi and bluetooth (with music playing) on and connected.
GPU overclocked and lowest step 200mhz(from 133 and max 400) and cpu up to 1550 Mhz.(okay, i did reduce the voltages, sue me)
and google location service on.
On original battery (dec 2011), that is about to die (screen starts glitching around 30%)
Somehow you are doing it wrong.

You would be surprised at what a speed deference you will get and battery life with aosp roms I have used tw and aosp and always go back to aosp based when tw starts to get laggy. But as most have said most likely a app causing your problem you should try install new Rom with all wipes inclueding preload I think thats what its called and make sure that media scan is not always running
Sent from my GT-N7000 using XDA Premium 4 mobile app

I'm pretty dependant on my camera for my kids. From my readings of AOSP threads, the camera app has never really worked well? Or am I misinformed?
Sent from my GT-N7000 using xda app-developers app

I do not use the camera that much, but i have not had problems with it.
Focal does crash for me and makes me reboob my phone.

Azeazezar said:
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
Click to expand...
Click to collapse
With a new battery original OEM just purchased yesterday, I am at 4h10m with 55 minutes screen time at 64%
This is much better.
Sent from my GT-N7000 using xda app-developers app

Just an update everyone:
I'm currently at 7h15m with 2 hours screentime.
The battery is at 38%
I will have to chalk this up to a worn battery being replaced by a real Samsung battery and not a knockoff 3rd party battery.
Sent from my GT-N7000 using xda app-developers app

Batteries make a big difference and as for cm roms and the camera they work great
Sent from my GT-N7000 using XDA Premium 4 mobile app

How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?

This didn't start out as a battery discussion
Sent from my GT-N7000 using xda app-developers app

AndroidSlave said:
How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?
Click to expand...
Click to collapse
JellybeanSandwich said:
This didn't start out as a battery discussion
Click to expand...
Click to collapse
How about reading the first post AndroidSlave?
What's this snarkyness that's infected xda?
Shure wasn't around back in the WM days.
This is and or was a very "General" issue with my phone, as i am still not entierely shure is a plain software issue.
However i've made the switch to a or the PA-rom out of desperation.
Still too early too tell, as it is first day after flash, but feels smoother.
What is driving me mad on PA is the lack of lockscreen-homebutton-torch.
Also a bit dissapointed in "Screen Mode" dynamic mode missing.
Missning SPen->screenshot->notetaking is bugging me aswell, but i'm shure ill find some replacement thing for that.
EDIT:
You, know what.
I apoligise if i posted this in the wrong place.
And no bad intentions towards you AndroidSlave.
I just feel that it's the place of a MOD and not of a user to make these claims.
Please just use the report button in if you feel like this, instead of posting a retorical question.

I know, right? What's up with the uninformed snark?
Sent from my GT-N7000 using xda app-developers app

[Conspiracy Theory] - VZN "so called leak"

I'm a firm believer that VZN and LG both couldn't get figure out a method to properly secure KK. I think the final OTA will have some method to ruin someone's day. My opinion, VZN is having fits over the old bootstack booting the ROM. I also figure they wanted the root method from ioroot to try to close it as well. Talk amongst yourselves ?
I just can't buy that there was an accidental slip up by both companies. Seems they setup a situation and decompile everything the devs post.
Sent from my VS980 4G using XDA Premium 4 mobile app

Maybe we actually do have a friend inside vzw. Since somehow every phone leaks or finds some miraculous method
Sent from my VS980 4G using Tapatalk

Dri94 said:
Maybe we actually do have a friend inside vzw. Since somehow every phone leaks or finds some miraculous method
Click to expand...
Click to collapse
Definitely a possible... Tho our devs have skills that border on the magical, and the power of collective knowledge is a wonderful thing haha.
But as far as VZW's predicament, I have no doubt that someone watches these forums, and curses over the extra dollars they'll have to spend on keeping their big red fingers locked tightly around our phones. As to whether it actually delays their official OTA, I'm sure they have deadlines to meet (esp. where the bloatware vendors are concerned), but it would be anyone's guess.
I'm just thrilled we have these leaks period. Even if the official OTA seals up security holes, this leak means a big boost to VS980 custom development!

The new KK leak seems odd, especially when some of its not even working correctly. I'm kinda stuck now. Device can get into Download mode but it just locks there.

Jivetime said:
Definitely a possible... Tho our devs have skills that border on the magical, and the power of collective knowledge is a wonderful thing haha.
But as far as VZW's predicament, I have no doubt that someone watches these forums, and curses over the extra dollars they'll have to spend on keeping their big red fingers locked tightly around our phones. As to whether it actually delays their official OTA, I'm sure they have deadlines to meet (esp. where the bloatware vendors are concerned), but it would be anyone's guess.
I'm just thrilled we have these leaks period. Even if the official OTA seals up security holes, this leak means a big boost to VS980 custom development!
Click to expand...
Click to collapse
Yea and how big red and lg both accidently leaked the rom and kernel.
Sent from my VS980 4G using Tapatalk

You ever think maybe they release it so devices get bricked and they gotta pay for new ones?

Well, if we're tossing out ideas...what if it got leaked so vzw could track who has 4.4 installed? Then they can red flag the rooters.
Today, I called to get a replacement. Speaker stoped working... she asked me if it was the original one I bought. I said Ya, then asked if I traded it or rooted it. I was Like, root? Lol...anyways, something on her end was flagging the phone. Of course, at the time of calling my phone was 100% stock. But I DID have 4.4 installed..replacement is in its way but still..more complicated then I expected
Sent from my VS980 4G using Tapatalk

zathus said:
Well, if we're tossing out ideas...what if it got leaked so vzw could track who has 4.4 installed? Then they can red flag the rooters.
Today, I called to get a replacement. Speaker stoped working... she asked me if it was the original one I bought. I said Ya, then asked if I traded it or rooted it. I was Like, root? Lol...anyways, something on her end was flagging the phone. Of course, at the time of calling my phone was 100% stock. But I DID have 4.4 installed..replacement is in its way but still..more complicated then I expected
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I don't really believe it, but I've seen some say VZW knows what apps you've installed. I saw a user once say they told him exactly what root apps he currently had. If that's true, some root app you've installed at some point may have flagged it. Or she was a liar. Lol. To be honest...once it was confirmed that you could downgrade and keep Loki on the other variants, I'm surprised LG didn't pull the Sprint rollout.

When the KK kernel source was "accidentally" leaked early after the devs were having problems with trying to create a zip rom from the KK leak and needed that info, that's is when my eyebrows were raised....lol. I was like, that's too much of a coincident. Somebody" was reading and listening to our cries....lmao. Nevertheless, thank you to whoever it was.

Tinfoil hat, anyone?
Sent from my VS980 4G using Tapatalk

JRJ442 said:
I don't really believe it, but I've seen some say VZW knows what apps you've installed. I saw a user once say they told him exactly what root apps he currently had. If that's true, some root app you've installed at some point may have flagged it. Or she was a liar. Lol. To be honest...once it was confirmed that you could downgrade and keep Loki on the other variants, I'm surprised LG didn't pull the Sprint rollout.
Click to expand...
Click to collapse
Lol, well she was definitely not lying. I didn't want to pry to much on what the issue was. Playing ignorant is sometimes the best rout but my guess is the Mac ids or sns from the day I bought the phone to now changed. She just kept saying "something is preventing me from sending you a replacement, are you sure you didn't trade phones with a friend or something?"
Sent from my VS980 4G using Tapatalk

Serial number is hardware level. Not possible unless you actually were swapped. They don't check it until old one is sent back, which is why you are given a purchase clause on returns. I'll assume your account was a bit jacked up if she wasn't lying, otherwise, liar.

Maybe Verizon wanted to wait for the knock code update to release KK instead of releasing it and then putting out another update right away for knock code.
Sent from my VS980 4G using Tapatalk

imhowie said:
Maybe Verizon wanted to wait for the knock code update to release KK instead of releasing it and then putting out another update right away for knock code.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
This is what I was thinking verizon isn't going to push 2 updates back to back, there going to make us wait for lg to add in knock code the release it
Sent from my VS980 4G using xda app-developers app

R0gersism said:
The new KK leak seems odd, especially when some of its not even working correctly. I'm kinda stuck now. Device can get into Download mode but it just locks there.
Click to expand...
Click to collapse
You said in the other thread that you wiped your Rom in recovery,not really conspiracy related just an accidental goof on your part.happens to the best of us.
Sent from my VS980 4G using Tapatalk

I don't know if it was necessarily a leak; I pulled it off their servers and published the link here one xda like a week back. It took us a few days but @xdabbeb found a way to trick our devices into taking that OTA. One thing I find suspicious is that it hasn't been taken down yet, which means it *might* be our official, it just hasn't had the green light yet. Also, the kernel source is still alive (direct link download) it just has the link removed.

Agreed. At the very least I think it was intended to be the official release. Whether they're holding off on pushing it to everyone because of a last minute issue they found or internal delays is anyone's guess. I tend to believe it's the latter.

Steamer86 said:
Serial number is hardware level. Not possible unless you actually were swapped. They don't check it until old one is sent back, which is why you are given a purchase clause on returns. I'll assume your account was a bit jacked up if she wasn't lying, otherwise, liar.
Click to expand...
Click to collapse
Liar? About what lol what is there to lie about. It was just an interesting conversation that kind of applied to this thread. And by the way, when I said serial number I was referring to the IMEI which, like the mac address is supposed to be unchangeable and yet there have been cases where they changed. But like I said, I don't know what the issue was. And obviously wasn't that big of a deal because my new phone is on its way
Sent from my VS980 4G using Tapatalk

JackpotClavin said:
I don't know if it was necessarily a leak; I pulled it off their servers and published the link here one xda like a week back. It took us a few days but xdabbeb found a way to trick our devices into taking that OTA. One thing I find suspicious is that it hasn't been taken down yet, which means it *might* be our official, it just hasn't had the green light yet.
Click to expand...
Click to collapse
I told ya, you devs are magic! I have been following the progress from day 1, and wondered how xdabbeb got it done.
zathus said:
Lol, well she was definitely not lying. I didn't want to pry to much on what the issue was. Playing ignorant is sometimes the best rout but my guess is the Mac ids or sns from the day I bought the phone to now changed. She just kept saying "something is preventing me from sending you a replacement, are you sure you didn't trade phones with a friend or something?"
Click to expand...
Click to collapse
When I quit working for VZW a couple years ago, the systems we used listed all the software/update/PRL version info of the software you had installed on your phone. It seemed that a lot of that info was based on the updates your phone pulled from the servers, and I never saw anything that actually indicated root status. However, they are constantly updating their capabilities so I wouldn't put it past em. I am of the opinion that most manufacturers don't check all that closely for root, at least if the phone is on a stock rom. I have never actually heard or read online of a VZW customer whose phone got rejected purely because it was rooted.

Jivetime said:
I told ya, you devs are magic! I have been following the progress from day 1, and wondered how xdabbeb got it done.
When I quit working for VZW a couple years ago, the systems we used listed all the software/update/PRL version info of the software you had installed on your phone. It seemed that a lot of that info was based on the updates your phone pulled from the servers, and I never saw anything that actually indicated root status. However, they are constantly updating their capabilities so I wouldn't put it past em. I am of the opinion that most manufacturers don't check all that closely for root, at least if the phone is on a stock rom. I have never actually heard or read online of a VZW customer whose phone got rejected purely because it was rooted.
Click to expand...
Click to collapse
I don't think it was rooting but maybe my update status. Example, my warranty date on the phone 2/4/2014. This is located in hardware information, hardware not software. I'll assume the warranty date is assigned the day you buy your phone. Now, it's changed. Point is, if that's changed what else could have changed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS980 4G using Tapatalk

App crashes and reboots

Anyone had apps crash / close not responding or phone reboots ?
Installed stability patch that was released but still getting reboots of os and app crashes.
Sent from my TA-1012 using Tapatalk

Nokia 8 bud
Sent from my TA-1012 using Tapatalk

Nope no problems here, everything runs clean and smooth. Maybe you should hard reset?

No issues here

No issues...

Lorditler. I'm no troll buddy. Sadly my Nokia 8 is going back. Crashes, reboots, smart lock doesn't work period.
I'm pretty gutted about it not being 100% from the get go.
Sent from my XT1572 using Tapatalk

I've had the odd app crash and reboot, I've got one more week to decide if I'm keeping it. Only thing is, I'm not sure there's anything else around that's going to be pure android with these specs for the same price. Pixel 2 is interesting, but likely to be £700+...

Smudger40 said:
I've had the odd app crash and reboot, I've got one more week to decide if I'm keeping it. Only thing is, I'm not sure there's anything else around that's going to be pure android with these specs for the same price. Pixel 2 is interesting, but likely to be £700+...
Click to expand...
Click to collapse
You sound like your exactly where I'm at smudger40. My phone arrived last wed so under DSR I've got a fortnight. After a fortnight I'm stuck with it for the next 2 years.
I'm after a near stock / totally stock android phone which leaves the pixel.
But like you I'm watching what price it is released at and with the fruity firm releasing a £1150 handset, what's not to say the pixel 2 hasn't suddenly gone up even more.
Like yourself I suspect it's going to be around £750 ish.
Which makes the Nokia a real bargain. My Nokia is going back so I'm covered under DSR and im just going to sit on the fence and see what pixel 2 looks like come oct.
And at that point i maybe re-order the nokia and hope I get a better one than the one I'm returning.
As for the X phone... I think this will open the flood gates to 3 year phone contracts to make the phone contract affordable or people are going to have to put 300-400 towards the handset cost.
Sent from my XT1572 using Tapatalk

I've had random reboots. Also issues with phone app and alarm. Phone app is being silent and unresponsive, alarm is just silent.

No issues here at all. Maybe try a factory reset and run with bare minimum a day or 2.
If it still happens it could very well be issues specific to your phone and you should be able to return it and get it either replaced or repaired.
My phone version is... Read below ?
Sent from my TA-1004 using Tapatalk

swejuggalo said:
No issues here at all. Maybe try a factory reset and run with bare minimum a day or 2.
If it still happens it could very well be issues specific to your phone and you should be able to return it and get it either replaced or repaired.
My phone version is... Read below
Sent from my TA-1004 using Tapatalk
Click to expand...
Click to collapse
Running a flagship phone with bare minimum? That makes no sense.
I have random reboots, phone app crashes on incoming calls, apps lag heavily, phone gets stuck in landscape mode.
Even the original ZTE Blade had better software than this. This is my first Nokia phone in 17 years and I will probably never get another one.

nuggeo said:
Running a flagship phone with bare minimum? That makes no sense.
I have random reboots, phone app crashes on incoming calls, apps lag heavily, phone gets stuck in landscape mode.
Even the original ZTE Blade had better software than this. This is my first Nokia phone in 17 years and I will probably never get another one.
Click to expand...
Click to collapse
The very least you can do is to factory reset and some basic trial and error... If the service workshop factory reset it and can't find issues they basically end up claiming you caused the problems. Gathering some proof makes them look like the idiot instead.
It could very well be hardware related since mine works perfectly. **** happens. No brand has 100% flawless phones.
Avoid Nokia if you must... But then avoid Samsung due to Note 7 aka Firestarter, Sony due to random reboots on my Z5 premium (that they fixed later), Apple due to critically flawed updates... The list can go rather large if you really put some time on finding reasons to avoid something.
Sent from my TA-1004 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 11:48 AM ----------
A interesting question... All with issues is that TA-1012? Mine is TA-1004. Only issue I've seen is that I had Data Saver function enabled a few times automatically.
Sent from my TA-1004 using Tapatalk

No, I'm on TA1012 with no problems.

swejuggalo said:
The very least you can do is to factory reset and some basic trial and error... If the service workshop factory reset it and can't find issues they basically end up claiming you caused the problems. Gathering some proof makes them look like the idiot instead.
It could very well be hardware related since mine works perfectly. **** happens. No brand has 100% flawless phones.
Avoid Nokia if you must... But then avoid Samsung due to Note 7 aka Firestarter, Sony due to random reboots on my Z5 premium (that they fixed later), Apple due to critically flawed updates... The list can go rather large if you really put some time on finding reasons to avoid something.
Sent from my TA-1004 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 11:48 AM ----------
A interesting question... All with issues is that TA-1012? Mine is TA-1004. Only issue I've seen is that I had Data Saver function enabled a few times automatically.
Sent from my TA-1004 using Tapatalk
Click to expand...
Click to collapse
Already am avoiding all brands you mentioned.

I really like the Nokia 8. Just what I really wanted but, mines not been right from the first day. However, having seen pics that were leaked last night of the pixel 2, I think that looks a proper minger. Then there's leaks of the Nokia 9 appearing every where.
Sitting this one out till Nov when either I go Nokia 8/9 or minger phone (pixel 2 XL) depending on how stupidly it is priced
Sent from my XT1572 using Tapatalk

Janzerfaust said:
I've had random reboots. Also issues with phone app and alarm. Phone app is being silent and unresponsive, alarm is just silent.
Click to expand...
Click to collapse
I have exactly the same issues, with the phone app crashing and alarm is silent sometimes, have you found a solution to your problem?

As others have not had this issue I've returned my handset to carrier. Awaiting a replacement bud
Sent from my XT1572 using Tapatalk

cpu-z crashes for me all the time.....ayone can give that app a try and report back please?

Thorgoth said:
cpu-z crashes for me all the time.....ayone can give that app a try and report back please?
Click to expand...
Click to collapse
Works fine @.my end
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}