Database Users

malfunction?

Hello
I have a nexus 4 of 9 days, and something happens rarely.
Block the night. Remain locked at night. It may be a malfunction? or a rom problem?
Not root
Thanks

liviugreuu said:
Hello
I have a nexus 4 of 9 days, and something happens rarely.
Block the night. Remain locked at night. It may be a malfunction? or a rom problem?
Not root
Thanks
Click to expand...
Click to collapse
If u want some help from anyone here you might want to be a little clear about what you are trying to explain

mdaamir1989 said:
If u want some help from anyone here you might want to be a little clear about what you are trying to explain
Click to expand...
Click to collapse
At night when the phone sits idle, the screen remains black and no longer listening.
Morning he must do a reset to start.
What could it be?

Are you rooted if not RMA that sucker sounds like you got a refurb.
Sent from my Nexus 7 using xda premium

monte666 said:
Are you rooted if not RMA that sucker sounds like you got a refurb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I not root.
Be more specific please

liviugreuu said:
I not root.
Be more specific please
Click to expand...
Click to collapse
maybe a intrusive app or something.

liviugreuu said:
I not root.
Be more specific please
Click to expand...
Click to collapse
may be a conflict with Smart ram booster?

Try doing factory reset and flashing the stock ROM again to see if the malfunction still happens.
If the malfunction still happens, return it to Google (RMA) for a replacement.
Sent from my Nexus 4 running the latest PA ROM 3+ and Franco's M1 kernel

Accidentally flashed Nexus 4 with GS2 rom

So I was helping my friend root and install PA on his phone. I got everything going good and asked him to find me the rom he wanted to use while I was doing everything else on it. Only problem is that he gave me the file for a Galaxy S II Paranoid Android rom. Found out after flashing it, and GAPPS and the phone wouldn't turn on. I have already tried a few things. I cannot get the phone to boot into fastboot, all it does is show the red light for a second and disconnect from my PC after a few seconds. It does the little device connected sound really quick, then nothing.
Holding power shows no LED, but my PC does detect a device.
Holding power+volume down shows the red LED error and that's it.
Edit:
For anyone wondering we already tried all power up options and it still just gives a red LED.

It gets connected so you can use adb?
Skickat från min Nexus 4 med Tapatalk 4 Beta

norpan111 said:
It gets connected so you can use adb?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
It only connects for a second. Like, basically it turns on for a split second and immediately turns back off.

It's dead. Sorry. Only way to revive it is with JTAG.
Sent from my Nexus 4 using Tapatalk 4 Beta

El Daddy said:
It's dead. Sorry. Only way to revive it is with JTAG.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well that sucks. I'm still fairly new to android but it was pretty straight forward with the toolbox to get the basic stuff done. Oh well, warranty time now I guess.
Sent from my HTC One

Warranty time!? So someone else should pay for your mistake? Unreal...
Sent from my Nexus 4 using Tapatalk 4 Beta

El Daddy said:
Warranty time!? So someone else should pay for your mistake? Unreal...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yea.
Sent from my HTC One

So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta

cadcamaro said:
Yea.
Sent from my HTC One
Click to expand...
Click to collapse
Well thats what happens if you don`t know what you`re doing and on top op that use a toolbox. Sorry for your loss but you have yourself to blame.

norpan111 said:
So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
It was loaded to the internal memory and flashed on the device itself from the recovery menu. So no, no safety as far as I know.
gee2012 said:
Well thats what happens if you don`t know what you`re doing and on top op that use a toolbox. Sorry for your loss but you have yourself to blame.
Click to expand...
Click to collapse
Everything went fine on my end. I told him to research and find which Rom he wanted so he had downloaded it. Toolbox worked amazingly and everything else went fine, and I've never done a nexus 4 so I didn't know what the file name is even supposed to look like so I just assumed he got the right one. Either way thanks guys, I know there's nothin else we can do now but I figured it wouldn't hurt to ask.
Sent from my HTC One

I remember when I was using s3,couldnt flash a mod for a different firmware even because mismatch
Skickat från min Nexus 4 med Tapatalk 4 Beta

norpan111 said:
I remember when I was using s3,couldnt flash a mod for a different firmware even because mismatch
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
Consider yourself lucky then haha. The Nexus just let it flash without a problem and just didn't turn back on.

cadcamaro said:
Consider yourself lucky then haha. The Nexus just let it flash without a problem and just didn't turn back on.
Click to expand...
Click to collapse
That really sucks.. Luckily if someone would be able to brick their device it was almost always a way to get it back somehow. Is it able to boot in boot menu? Or it's just black? Really sad for your friend either way
Skickat från min Nexus 4 med Tapatalk 4 Beta
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
http://forum.xda-developers.com/showthread.php?t=2208289
[WIP] Unbricking the Nexus 4 using QPST
Skickat från min Nexus 4 med Tapatalk 4 Beta

norpan111 said:
That really sucks.. Luckily if someone would be able to brick their device it was almost always a way to get it back somehow. Is it able to boot in boot menu? Or it's just black? Really sad for your friend either way
Skickat från min Nexus 4 med Tapatalk 4 Beta
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
http://forum.xda-developers.com/showthread.php?t=2208289
[WIP] Unbricking the Nexus 4 using QPST
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
Won't boot at all and the screen stays black. I've only rooted a few phones and my N7 so that link is pretty advanced for me. Still a good read so I'll look into it but for now if insurance will replace it then well just do that.
Sent from my HTC One

cadcamaro said:
Won't boot at all and the screen stays black. I've only rooted a few phones and my N7 so that link is pretty advanced for me. Still a good read so I'll look into it but for now if insurance will replace it then well just do that.
Sent from my HTC One
Click to expand...
Click to collapse
People are asking if the N4 is able to get to the bootloader/fastboot...since you used a "toolbox", it is safe to assume that you rely on ADB and the auto-scripts provided by said GUI tool only after a full boot. Since you cannot get a full boot, you feel stuck...Are you aware of Vol Up + Vol Down + Power taking you to fastboot from an off state? The OP doesn't mention you trying this key sequence at all. Make sure your battery is charged first because you, likely, have a dead battery if your device has only shown a "black" screen...plug it in, let it charge (if it shows the battery charging, you are probably going to be ok).
Since no one has bluntly suggested trying the basics and told you the button sequences, you probably haven't even tried them. I am just trying to assist you so your flippant "warranty time" approach doesn't cause MY deductible (used only for physically damaged or lost/stolen devices) to rise, yet again, anytime soon.
Please reply on here so you can get that thing fixed. It is likely that you just had a bad install of an actually compatible ROM or failed install of that GS2 ROM versus a rogue full install from another device. Asserts are in scripts for a reason.
Sent from my GT-N5100 using Tapatalk 4 Beta

VicFreeze said:
People are asking if the N4 is able to get to the bootloader/fastboot...since you used a "toolbox", it is safe to assume that you rely on ADB and the auto-scripts provided by said GUI tool only after a full boot. Since you cannot get a full boot, you feel stuck...Are you aware of Vol Up + Vol Down + Power taking you to fastboot from an off state? The OP doesn't mention you trying this key sequence at all. Make sure your battery is charged first because you, likely, have a dead battery if your device has only shown a "black" screen...plug it in, let it charge (if it shows the battery charging, you are probably going to be ok).
Since no one has bluntly suggested trying the basics and told you the button sequences, you probably haven't even tried them. I am just trying to assist you so your flippant "warranty time" approach doesn't cause MY deductible (used only for physically damaged or lost/stolen devices) to rise, yet again, anytime soon.
Please reply on here so you can get that thing fixed. It is likely that you just had a bad install of an actually compatible ROM or failed install of that GS2 ROM versus a rogue full install from another device. Asserts are in scripts for a reason.
Sent from my GT-N5100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322593
That is the exact rom he chose. I asked someone else about it and he replied with this "The OP has cooked the kernel inside the rom. Your mates phone doesn't have a dead bootloader, it's trying to boot the S2 kernel but can't due to the diffirent chipsets".
I also tried powering it on every way possible without any luck, guess I should have mentioned that. Yeah though, already tried with
Just holding power
Holding power +vol down
hold power + vol up
holding all three down
No luck with any.

If the boot loader is fine you should try to get into fastboot mode. Power off. Now press Power and volume down together until you get something on the screen. I would be surprised the phone is bricked just because you flash the wrong kernel.
Sent from my Nexus 4 using xda app-developers app

rasengan82 said:
If the boot loader is fine you should try to get into fastboot mode. Power off. Now press Power and volume down together until you get something on the screen. I would be surprised the phone is bricked just because you flash the wrong kernel.
Click to expand...
Click to collapse
This.
The ROM, Kernel, and Bootloader are totally different parts to the Nexus 4. You can commonly flash a wrong ROM, and even Kernel, but the Bootloader should be the last thing touched.
So, as long as you have a bootloader, you can access fastboot, and restore Google's factory image (or flash TWRP and have another go at a custom ROM/Kernel).

norpan111 said:
So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
you probably had signature checking turned off in your recovery

I have never heard of a phone being bricked from only a ROM flash. It doesn't make too much sense. How could the wrong rom influence the bootloader?
Your phone should boot. Either you're doing something wrong while trying to boot, or the rom flash wasn't the only thing you have done to that phone.

Ghost fingers on touch screen...??

Hi guys,
I recently bought a Google Nexus 4. Great device! But now I have a problem with the touch screen I guess.
I have some ghost touches on the screen. They are always on the same places.
To be more specific, on the same X-as of the screen. 3 to 5 touches in horizontal direction, swiping and touching the screen.
It's not always there, that's what's bothering me.. what is gods name could it be...
I'll add a screenshot of the touches when I get a chance to...
I have this problem for about a week now. And I was wondering if someone knows the solution to this.
ROM: Cyanogenmod 10.1.2
Cheers,
Alexander

When did this happen?
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
When did this happen?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.

Alexandersch said:
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.
Click to expand...
Click to collapse
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have installed the custom rom the moment I got this device. It didn't happen before.. So I doubt it is a software problem. I'd rather think of it as a hardware problem, don't you think?

No-one?

If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium

mariosraptor said:
If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I flashed another ROM CM10.2 UNOFFICIAL. Did a clean install.
Untill now it is reacting normal.. Let's wait and see.
I am thinking, could it be of some backup settings it is recovering from my google account?
Because it has no Gapps installed yet. Downloading at the moment.
Thanks in advance

As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4

naenee said:
As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Ok, The CM10.2 did not work. I disabled auto backup and recovery of Google settings and stuff and flashed the Stock ROM 4.2.2.
Also there was an official update to 4.3. And surprisingly enough, the device is responding normal again. Still though, i think it was very strange that the problem was also in the recovery...

Simpsons Tapped Out

I'm running stock rooted and since day one with this phone, the Simpsons game has been choppy and crashes often. I've sent quiet a bit of reports once it crashes, but I was wondering if anyone else had this problem?
Sent from my Nexus 5 using Tapatalk

bigdog_nick said:
I'm running stock rooted and since day one with this phone, the Simpsons game has been choppy and crashes often. I've sent quiet a bit of reports once it crashes, but I was wondering if anyone else had this problem?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Mine is choppy (low frame rate) occasionally - it was more noticeable during the recent halloween event. Seems ok now since the thanksgiving update.
It does crash quite frequently though - maybe one out of every three or four sessions.

I play daily and it crashes at least once every time I play it. Used to have sgs4 I337 running gpe Roms and it wouldn't work at all. Warrantied a bad headset speaker and here I am. The new sgs4 AT&T sent me had a locked boot loader and no root android 4.3. I didn't want a galaxy phone so sold it for 400 bought the nexus 5.
Level 37 now. Same as zulugod stated was laggy with Halloween update, better now.
Sent from my Nexus 5 using Tapatalk

In 37, it does have fps lag and crashes like six times before I can assign everyone to tasks
Sent from my Nexus 5 using xda app-developers app

Ok glad it's not just me. I'm hoping in the next play store update, They'll fix it or something.
Sent from my Nexus 5 using Tapatalk

Every time it crashes I send the report. So I'm sure someone will eventually take a look and issue a small patch.
Sent from my Nexus 5 using Tapatalk

Same
Jnewell05 said:
Every time it crashes I send the report. So I'm sure someone will eventually take a look and issue a small patch.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Here is the new christmas update and nothing changes same **** with crashes(((

SOPUN said:
Here is the new christmas update and nothing changes same **** with crashes(((
Click to expand...
Click to collapse
I installed a different kernel and haven't had an issue yet. I'm using Francos Kernel its in the original android Dev thread. I understand that some people don't want root and modify googles pretty work but this is a fix for me.
Sent from my Nexus 5 using Tapatalk

Thx
Jnewell05 said:
I installed a different kernel and haven't had an issue yet. I'm using Francos Kernel its in the original android Dev thread. I understand that some people don't want root and modify googles pretty work but this is a fix for me.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi i'm totally newbie in such tipe of thing. i used to have only iPhones since 2007) and that is my first android phone))) (i also used to have Blackberrys) So it's totally stock, i am actually in love with it as it is. Maybe someday i will try to root or mod it or kernel( i even donno what does it mean)))))

Encrypt or Decrypt?

Hi mates,
I've 3 days with my 6P and i'm wondering if is there a better performance with a decrypted phone, or it does not matter really.
Iam encrypted at the moment, just wondering if i should decrypt it, and what would be the benefits if i decrypt the phone?
Thanks in advance.

I doubt if you'd notice any difference in day to day use, so unless you put an encrypted unit next to a decrypted one and run benchmarks I don't see the benefit.
Verstuurd vanaf mijn Nexus 6P met Tapatalk

Be a rebel and decrypt. Be part of the decrypt crew, I am. ?✌haha. In TWRP if your not encrypted your flashes are faster. That's about all I've noticed really but I stay unencrypted.
Sent from my Nexus 6P using Tapatalk

Nomoi said:
I doubt if you'd notice any difference in day to day use, so unless you put an encrypted unit next to a decrypted one and run benchmarks I don't see the benefit.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
Click to expand...
Click to collapse
Thanks Nomoi
SM210 said:
Be a rebel and decrypt. Be part of the decrypt crew, I am. ?haha. In TWRP if your not encrypted your flashes are faster. That's about all I've noticed really but I stay unencrypted.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
hahaha thanks bro

SM210 said:
Be a rebel and decrypt. Be part of the decrypt crew, I am. ?haha. In TWRP if your not encrypted your flashes are faster. That's about all I've noticed really but I stay unencrypted.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you notice any difference in regards to battery life?

TheySaidWhat?! said:
Did you notice any difference in regards to battery life?
Click to expand...
Click to collapse
No there's no difference in battery. Some say decrypted is faster but I don't know.. I never could really tell s difference myself.
Sent from my Nexus 6P using Tapatalk

SM210 said:
No there's no difference in battery. Some say decrypted is faster but I don't know.. I never could really tell s difference myself.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok thanks. And one last question, does the nexus 6p usuable storage get reduced to 23gb instead of 25gb when decrypting /formatting internal storage???
I've 'heard' someone claim their usuable storage was 2gb's less. Got no clue what else they did tho...
But I do like the sound of faster flashes in twrp If decrypting /formatting has no negative effect... I'll do it just for faster flashing! Wipe it down clean lol