Hy guys I have seen on a noob guide that I can see my phone cpu "stats".
This tells me is my phone a powerfull machine or a bad brick.
So I have installed the faux kernel and with root explorer I came to this t3_variant
/sys/kernel/debug/t3_variant
If your cpu_process_id=
"0"- Sorry, but your in for a world of hurt. I'd recommend only trying out his mainline edition, nothing else.
"1"- Well, you''ll do just fine, but it still sorta shaky. Don't think about overclocking though, unless you're on a beta or VF version
"2"- Knock yourself Out! ;p
"3"- Lock that phone in Fort Knox and, if you see faux lurking around your house, then just run . Jokes aside, your phone can do ANYTHING.
Click to expand...
Click to collapse
This is a quote from a Noob Guide - here.
Mine cpu_process_id=0. Does this mean I bought 4500kn (597.32€ - Yes that's the price of HOX in Croatia) brick?
I have problems with battery he shuts down sometimes more like often, is he really that bad and I am angry right now cause I think I bought bad and expensive phone?!
If you need more info I will be glad to post just someone help me please.
LOL, those cpu variants are to be ignored. They are for hard core overclockers.
It has nothing to do with battery life and you do not own a phone shaped brick. I paid the same amount for my HOX.
Well can you tell me why does he act strange all the time. He just shuts down but he doesn't do that when he is on charger. I think I have some serious power issue. I'will give you all logs you ask and all screenshots just help please.
You might want to try another kernel and do a clean reflash of rom.
Give me the kernel reboot log from /proc/last_kmsg.
No need I think I solved the problem. I have now just moved the governor to interactive witch was default "ondemand". He didn't went off for like 6 hours witch is a record and battery is still 50% can't believe. I know I am noob sry for that
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
faiz02 said:
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
Click to expand...
Click to collapse
All those random reboots were on stock jb xD
Oh OK,
Case closed.
Related
Ok, not sure where to post this but it has to be rom related or maybe kernel
this has been going on for a little while now and i cant figure out whats causing it..
it may be temp related but it has been doing it when the temp is normal too...
basically, it reboots and doesnt stop, i have to take the batt out and then it will reboot normal.
i tried different kernels and roms, they all have been doing it...
not sure if something is damaged like the batt or phone but im getting sick of it..
any ideas?
i got this evo when it came out, it was rooted from day one and i have been able to OC heavy at times..
im not over doing the OC since i know how much to push it there... the undervolt is fine.
Mayonesa said:
Ok, not sure where to post this but it has to be rom related or maybe kernel
this has been going on for a little while now and i cant figure out whats causing it..
it may be temp related but it has been doing it when the temp is normal too...
basically, it reboots and doesnt stop, i have to take the batt out and then it will reboot normal.
i tried different kernels and roms, they all have been doing it...
not sure if something is damaged like the batt or phone but im getting sick of it..
any ideas?
i got this evo when it came out, it was rooted from day one and i have been able to OC heavy at times..
im not over doing the OC since i know how much to push it there... the undervolt is fine.
Click to expand...
Click to collapse
Uh oh...spaghettios
Mayonesa said:
Ok, not sure where to post this but it has to be rom related or maybe kernel
this has been going on for a little while now and i cant figure out whats causing it..
it may be temp related but it has been doing it when the temp is normal too...
basically, it reboots and doesnt stop, i have to take the batt out and then it will reboot normal.
i tried different kernels and roms, they all have been doing it...
not sure if something is damaged like the batt or phone but im getting sick of it..
any ideas?
i got this evo when it came out, it was rooted from day one and i have been able to OC heavy at times..
im not over doing the OC since i know how much to push it there... the undervolt is fine.
Click to expand...
Click to collapse
boot into recovery
wipe 3x
flash a stock ruu
post this in Q&A next time
How are you wiping in between roms? My wifes phone does that every once in a while. Usually a good wipe with Virusroms Superwipe does the trick.
Mayonesa said:
i got this evo when it came out, it was rooted from day one and i have been able to OC heavy at times..
im not over doing the OC since i know how much to push it there... the undervolt is fine.
Click to expand...
Click to collapse
This question belongs here http://forum.xda-developers.com/forumdisplay.php?f=652
Also before you go to sleep tonight, please read the first rule in the rule thread below
http://forum.xda-developers.com/announcement.php?a=81
mazdarider23 said:
This question belongs here http://forum.xda-developers.com/forumdisplay.php?f=652
Also before you go to sleep tonight, please read the first rule in the rule thread below
http://forum.xda-developers.com/announcement.php?a=81
Click to expand...
Click to collapse
lmao nothing better to do?
take it any way you want but i find these types of post funny as hell and a bigger waste that posting in the wrong section...
thanks for the laugh
and thanks for those that did offer help, i wipe the old fashion way plus i use the calk format all.
mazdarider23 said:
This question belongs here http://forum.xda-developers.com/forumdisplay.php?f=652
Also before you go to sleep tonight, please read the first rule in the rule thread below
http://forum.xda-developers.com/announcement.php?a=81
Click to expand...
Click to collapse
Sometimes people bored, sometimes they feel important, being forum police
Sent from my PC36100 using XDA App
Amanchik said:
Sometimes people bored, sometimes they feel important, being forum police
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Some people also get their jollies trying to be white knights, protecting the ignorant.
Sent from my PC36100 using XDA App
Mayonesa said:
Ok, not sure where to post this but it has to be rom related or maybe kernel
this has been going on for a little while now and i cant figure out whats causing it..
it may be temp related but it has been doing it when the temp is normal too...
basically, it reboots and doesnt stop, i have to take the batt out and then it will reboot normal.
i tried different kernels and roms, they all have been doing it...
not sure if something is damaged like the batt or phone but im getting sick of it..
any ideas?
i got this evo when it came out, it was rooted from day one and i have been able to OC heavy at times..
im not over doing the OC since i know how much to push it there... the undervolt is fine.
Click to expand...
Click to collapse
Yea bro im having the same problem too. Pisses me off!!!!
Ninja25 said:
Yea bro im having the same problem too. Pisses me off!!!!
Click to expand...
Click to collapse
HTC phones are very picky meaning that after flashing so many ROM's it can cause bad mtd blocks. Thus the phone does not let the it boot proper. I'm not saying that this is the problem but it could be one. If I were you I would try to flash a RUU and wait a couple days to see if the phone acts normal. If it does try to flash a ROM and see if it starts again, if it does then it may be a bad mtd block. You should do a log cat so we can see where and why the phone will randomly reboot.
Try virusrom's superwipe, and yes, try going back to stock for a while. But also, don't laugh off the people that tell you to post in the right section. This forum is way too cluttered already. Development forums in particular. Mistakes happen, but please read the rules at least once. Anyway, now you know--have fun here at XDA.
carnegie0107 said:
Try virusrom's superwipe, and yes, try going back to stock for a while. But also, don't laugh off the people that tell you to post in the right section. This forum is way too cluttered already. Development forums in particular. Mistakes happen, but please read the rules at least once. Anyway, now you know--have fun here at XDA.
Click to expand...
Click to collapse
ill give that a try, thanks.
every forums i have ever gone too gets cluttered, no way around that. yes i do agree in searching but( at least for me) searching doesnt help too much at times, so much comes up in the search.
but anyways, i do laugh, no offense to anyone but i find it funny some people take the time to correct you like if it was a huge deal... let the mods take care of if, that simple.
anyways, thanks again
now if i could only find the superwipe lol ...... found it
Mayonesa said:
ill give that a try, thanks.
every forums i have ever gone too gets cluttered, no way around that. yes i do agree in searching but( at least for me) searching doesnt help too much at times, so much comes up in the search.
but anyways, i do laugh, no offense to anyone but i find it funny some people take the time to correct you like if it was a huge deal... let the mods take care of if, that simple.
anyways, thanks again
now if i could only find the superwipe lol ...... found it
Click to expand...
Click to collapse
Can you post the superwipe?
Of course..... Cant attach files but here is the link
http://infectedrom.com/showthread.php/238-Vr_superwipe?highlight=Superwipe
Sent from my PC36100 using Tapatalk
ok, well i flashed and used superwipe but i still had problems a little while ago.
do you guys think it would help if i flash a stock rooted rom?
Like was stated above, try flashing back to STOCK and UNROOTED. If it still does it, take it to Sprint for a replacement since it'll be a hardware issue then.
snowboarda42 said:
Like was stated above, try flashing back to STOCK and UNROOTED. If it still does it, take it to Sprint for a replacement since it'll be a hardware issue then.
Click to expand...
Click to collapse
i may have to do that then, i wanted to stay away from that cause i didnt want to have to root it again but i may have too
i do remember from my windows mobile days when i flashed a stock rom then flashed back to custom to clear things up...
thanks
this is driving me nuts!!!
hand up the phone and it reboots none stop
it feels hot, but damn... it didnt do this before
man, im almost at my limit!!!
i have been messing with the phone a lot today... partition my SD card and flashed
but man, this reboot problem is driving me nuts!
this hasnt happened to anyone else?
i do flash a lot from time to time but i dont think i have over done it...
AHHHHHHHHHHH lol
Karma for posting in the wrong section and blowing off the guy who tried to tell you.
So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!
Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.
It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%
It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)
HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj
Hi everyone.
My friend recently got a galaxy nexus, and he has been complaining about a weird problem he has been having. Randomly, maybe once a day, he would press the power button to wake the phone up but the display won't come on. If he holds down the power button, there is a short vibrate indicating the power off prompt, but the display is completely off. Have to pull the battery for the phone to come back again.
The current setup is Xenon HD vXVII with Franco kernel r295. I have the exact same setup on my gnexus and mine is flawless.
Can anyone please suggest something? The phone is brand new, only two weeks old.
Hasan10 said:
The current setup is Xenon HD vXVII with Franco kernel r295. I have the exact same setup on my gnexus and mine is flawless.
Click to expand...
Click to collapse
Your device isn't the same as your friend's, every chip is different.
Return his device to stock through fastboot. Do SOD's still occur on stock? No? There's your awnser.
Still doing it?
Get us logcat/dmesg/last_kmsg or "it didn't happen".
bk201doesntexist said:
Your device isn't the same as your friend's, every chip is different.
Return his device to stock through fastboot. Do SOD's still occur on stock? No? There's your awnser.
Still doing it?
Get us logcat/dmesg/last_kmsg or "it didn't happen".
Click to expand...
Click to collapse
What's with the hostile attitude? If I am being polite in my question, I perhaps expect the same from a civilized society. This is not Apple forums, its xda.
The problem did also occur on stock firmware, and thus I flashed xenon and Franco.kernel on it thinking the problem could be fixed. It did improve it some what, but still the problem is there just not as frequent.
And how/where do I get the logcat/dmesg/last_kmsg?
Hasan10 said:
What's with the hostile attitude? If I am being polite in my question, I perhaps expect the same from a civilized society. This is not Apple forums, its xda.
The problem did also occur on stock firmware, and thus I flashed xenon and Franco.kernel on it thinking the problem could be fixed. It did improve it some what, but still the problem is there just not as frequent.
And how/where do I get the logcat/dmesg/last_kmsg?
Click to expand...
Click to collapse
no one is being hostile, and you could just have used search to find out what adb/logcat/dmesg/last_kmsg is.
http://forum.xda-developers.com/showthread.php?t=1812959
bk201doesntexist said:
no one is being hostile, and you could just have used search to find out what adb/logcat/dmesg/last_kmsg is.
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
I will flash complete stock image on his phone without BL unlock or custom recovery and see if that still gives the problem. If it still does then I will just make a new thread with the log cat file.
I have been using my Nexus 7 2013 for few months and the battery is really strange.
The battery graph is often zigzag-like as attached and I really don't know where the issue is.
I have been using purity rom, franco kernel with smart cover.
I am also charging my Nexus 7 2013 with my Nexus 4 charger and external powerbank.
Is this a battery problem and should I get it back to ASUS for warranty?
Thanks everyone
If it hasent been doing this long i would give it a week or two and if its still doing it, then i would be concerned. But i also think that some custom kernels may also have this side effect, i dont know why, maybe someone more with more knowledge of kernels could clear this up. Atleast. I hope... Mine does this aswell, but i dont stay on the same rom for more than a week or two ?
Andromendous said:
If it hasent been doing this long i would give it a week or two and if its still doing it, then i would be concerned. But i also think that some custom kernels may also have this side effect, i dont know why, maybe someone more with more knowledge of kernels could clear this up. Atleast. I hope... Mine does this aswell, but i dont stay on the same rom for more than a week or two ?
Click to expand...
Click to collapse
I am not sure why this happen and my first thought is battery issue.
I am lazy to try out different roms and kernels unless this issue persists.
Id go through a few full cycles, it does this to me on glitch kernel, but i tryed stock rooted rom the other day and noticed it wasnt happening anymore.
Edit: just looked at the graph again. Looks like you werent even using the tablet at all. If thats the case then im afraid this might be bad. Sorry friend.
But i wouldnt get too worried just yet, give it a few days, if it doesnt settle down or stock does the same then id think about a warranty.
Andromendous said:
Id go through a few full cycles, it does this to me on glitch kernel, but i tryed stock rooted rom the other day and noticed it wasnt happening anymore.
Edit: just looked at the graph again. Looks like you werent even using the tablet at all. If thats the case then im afraid this might be bad. Sorry friend.
But i wouldnt get too worried just yet, give it a few days, if it doesnt settle down or stock does the same then id think about a warranty.
Click to expand...
Click to collapse
Thanks very much and I may observe it for another week.
I have the exact same issue with my Nexus7. Rooted stockrom and it is zigzaging also. But batterylife is still very good, now its been up 2days and 12 hours with screen time over 5 hours. So im not going to send my own into warranty just yet, because every other common known problem is not on my device
I have stock rom , not rooted and I get the zig zag battery also. No problem tho, I am very happy with the battery life .
Hi Guys,
My galaxy S3 , SGH-I747M (d2can) is crashing regularly with no warning. I'll give you the symptoms as best I can.
My phone dies only when I'm using it, not when it's in sleep mode. it doesn't have to be a very power-hungry task, though the frequency of the crashes increases when I multitask. There is no lag on the task I'm performing when it crashes, it just looks like the screen has timed out. When I go to restart it right away, I usually only get to the samsung logo, about 6-10 seconds after it boots up. The likelihood that it will stay on after a crash increases the longer I wait with it off after the crash, 30 minutes is usually enough, though pulling the battery seems to help it boot up as well. The battery is not hot when I feel it, it's not even warmer than room temperature which I thought was unusual.
This tends to happen once every two days now
I tried eMMC check and it came back clear.
My phone was rooted shortly after I got it, though the crashes happened even before I rooted it. Just not as frequently, but I also had no apps installed at the time. limiting the background processes does nothing.
Any thoughts? I'm kind of stumped.
This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.
audit13 said:
This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.
Click to expand...
Click to collapse
It's the S3 SGH-I747M, which I believe is d2can.
Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?
audit13 said:
Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?
Click to expand...
Click to collapse
it's all stock. I just did cf autoroot and twrp. This problem started even before I rooted it.
Sounds like a hardware problem since the issue has always been present.
Definitely seems like a hardware issue. If you still have a warranty, you'll want to get it replaced ASAP (usually the warranty is a year or longer, and some carriers don't care if you've flashed your phone or not). No amount of tweaking will be able to get that thing running properly, most likely.
Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.
jdezwaan91 said:
Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.
Click to expand...
Click to collapse
Not unless it was definitely a RAM issue and you had some sort of memory dump that shows exactly when it crashes, and even then, you'd have to manually add things to the kernel to stop it from ever accessing that sector.
It's incredibly hard to do on Linux even, never mind on Android.
You could try undervolting + running different I/O Schedulers and Governors, but I don't know how far that'll get you, honestly.