updated my kernell for my mt4g
but everything is gone off my sd
i think thats why its bootlooping
can anyone help me out
not running any custom roms
i can boot into recovery and bootloader
big_d093 said:
updated my kernell for my mt4g
but everything is gone off my sd
i think thats why its bootlooping
can anyone help me out
not running any custom roms
i can boot into recovery and bootloader
Click to expand...
Click to collapse
You are attempting to run a custom kernel with the Stock ROM. The two most likely causes of your loop are 1) you installed the wrong kernel, or, 2) you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Just flashed a nightly mod then icerglacier over it problem fixed no need to be a **** though thanks
Sent from my HTC Glacier using XDA App
big_d093 said:
Just flashed a nightly mod then icerglacier over it problem fixed no need to be a **** though thanks
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Are you serious? All he did was try and help you figure out what YOU did wrong. I would imagine that you would have rather him put a bunch of smiley faces and thank you for not researching some other threads to get this figured out.
WTF is wrong with people these days? And BTW, as much as you think your problem is fixed...and that one probably is. You are going to run into other things and people such as myself arent going to be as willing to help you when you treat the people that are trying to help like that.
Dont forget that you are the one asking for the help not us.
Oh, I can see where he saw me as "being a ****." My comment about not having a backup available can be seen as snide. (Of course, with the wrong version of CWMR installed, a restore isn't going to do anything more than produce a boot loop anyway.)
My apologies for being a large penis.
jggimi said:
Oh, I can see where he saw me as "being a ****." My comment about not having a backup available can be seen as snide. (Of course, with the wrong version of CWMR installed, a restore isn't going to do anything more than produce a boot loop anyway.)
My apologies for being a large penis.
Click to expand...
Click to collapse
LOL wow wow wow thats to much information there lets keep it G rated LOL.
Now keep in mind this has NOTHING to do with CWM as it has to do with the chip itself what you have to understand is not all chip is created equal as some can utilize normal stock voltage and other can be using lower voltage thus not allocate in first place and it will be stuck on bootloop. Faux address this as most of his kernel has LV/SV but sometimes it may not work as you have to replace it with another kernel like granklin's and then flash it over. This is not CWM issue its kernel issue.
BlackSHELF said:
LOL wow wow wow thats to much information there lets keep it G rated LOL.
Now keep in mind this has NOTHING to do with CWM as it has to do with the chip itself what you have to understand is not all chip is created equal as some can utilize normal stock voltage and other can be using lower voltage thus not allocate in first place and it will be stuck on bootloop. Faux address this as most of his kernel has LV/SV but sometimes it may not work as you have to replace it with another kernel like granklin's and then flash it over. This is not CWM issue its kernel issue.
Click to expand...
Click to collapse
The kernels available all boot at close to stock clocks, so you would have to set it higher before the boot loop problem.
Flashing a rom with the wrong version of cwm would cause the loops instantaneously.
option94 said:
The kernels available all boot at close to stock clocks, so you would have to set it higher before the boot loop problem.
Flashing a rom with the wrong version of cwm would cause the loops instantaneously.
Click to expand...
Click to collapse
Thats normally true but in his case its VOID. If you check his post you will see he didn't flash new rom.
"not running any custom roms"
As I know this is problem with voltage which is kernel related.
"updated my kernell for my mt4g"
Now I am not sure what your talking about in this line.
"so you would have to set it higher before the boot loop problem"
You are confusing clock frequency with voltage the power supplied to the chip to function. Now he can't access that if he knew how and where it was allocated in kernel then we wouldn't have be in this thread. BTW not all kernel use stock voltage or even close. This is not CWM related as it has NOTHING to do with it.
They don't run stock voltages, correct.
Generally, problems only arise when over clocking, not with voltage changes, since the changes in the kernel are fairly minimal. I have yet to hear about anyone having issues with any of our kernels voltages. Only about not being able to clock past a certain point without freezing.
As always, I could be wrong. Just my observations and experience.
option94 said:
They don't run stock voltages, correct.
Generally, problems only arise when over clocking, not with voltage changes, since the changes in the kernel are fairly minimal. I have yet to hear about anyone having issues with any of our kernels voltages. Only about not being able to clock past a certain point without freezing.
As always, I could be wrong. Just my observations and experience.
Click to expand...
Click to collapse
Look let me put it this way once the kernel is flashed and when you reboot it has to be allocated right? now if its under voltage it won't even get passed the bootscreen. This is voltage problem which has to be supplied to the chip for it to function normally which varies chips to chips as they are not all created equal which depends on the defect rate of the wafer. But yes you are correct in your post above as that is aftermath of clock frequency which can only be initiated once the kernel is fully allocated, which also depends on the threshold of the chip itself as they are not all equal. If you get passed the bootscreen then obviously its working but it can still freeze as you stated. Only time voltage come in play again is when you scale from very low frequency to high frequency in short time because normally gradually the power has to be supplied but since it can't due to the power swing it will freeze. Don't confuse clock frequency with voltage. I been OCing for past 15+ years lol long before it was made easy back when you had to manually change the controller's die.
BlackSHELF said:
Look let me put it this way once the kernel is flashed and when you reboot it has to be allocated right? now if its under voltage it won't even get passed the bootscreen. This is voltage problem which has to be supplied to the chip for it to function normally which varies chips to chips as they are not all created equal which depends on the defect rate of the wafer. But yes you are correct in your post above as that is aftermath of clock frequency which can only be initiated once the kernel is fully allocated, which also depends on the threshold of the chip itself as they are not all equal. If you get passed the bootscreen then obviously its working but it can still freeze as you stated. Only time voltage come in play again is when you scale from very low frequency to high frequency in short time because normally gradually the power has to be supplied but since it can't due to the power swing it will freeze. Don't confuse clock frequency with voltage. I been OCing for past 15+ years lol long before it was made easy back when you had to manually change the controller's die.
Click to expand...
Click to collapse
I understand your point quite well actually, all I was saying is that if the voltages were truly causing his issue, It would be the first time that its been reported to my knowledge. Generally, the only issues we have on this phone are clock speed based.
option94 said:
I understand your point quite well actually, all I was saying is that if the voltages were truly causing his issue, It would be the first time that its been reported to my knowledge. Generally, the only issues we have on this phone are clock speed based.
Click to expand...
Click to collapse
Well you are right that if you go beyond curtain threshold then it will freeze but that falls under clock frequency. Which means the kernel was allocated and successfully booted thus user were able to amend changes to the clock frequency which in any extreme case would freeze and need battery pull. But once rebooted it will go back as it won't get stuck in bootloop even with the max OC thus voiding the whole point of the thread as it would not be stuck on the bootloop and isolating CWM and clock frequency as the cause.
However voltage fits the bill and it is not new issue in kernel world as its very common issue matter of fact this has been reported by many users for MT4G and its not new issue. I use to make kernels for device and system as I been using *nix for close to 12+ years and virtually mastered SC.
Related
hi my wildpuzzle version is 8.0, but i'm waiting a bit before upgrading to one of the latest.
I'm waiting also because i'd like to know a bit more about overclocking the cpu.
On one hand, i'm sure the phone will be smoother and faster, but on the other hand? Are there any problems, or effect i should be aware of?
One more thing, there is a list with 6 different kernels with oc enabled. How do i choose which one to flash? Which is the best?
thanks in advance
pro:
your phone will be faster
battery usage during idle is potentially decreased
cons:
your phone might become unstable as the hardware will be running outside of tested specs
battery usage during active usage is increased
The different kernels all have different levels of overclocking. If you try one and your phone becomes unstable (random Force Closes or restart) try and flash it with a slower kernel (lower maximum frequency).
There is no danger of directly harming the hardware in the phone from overclocking. However if the phone is pushed so far it is becoming unstable data corruption might occur.
ok that's what i was afraid of.
is this (damaging the hardware) a real possibility? Or is it just in theory?
Than is the phone really faster? I mean, is it worth to overclock the cpu (considering the possible damage of the processor and the various improvement)?
Sorry about that...
I missed a "no" in there. I meant to say that your phone will not explode into a ball of fire or otherwise become unusable from overclocking.
If it is pushed to far it will simply hang or crash and need to be rebooted.
I can notice a rather big difference. I mean going from 528Mhz -> 768Mhz. That's almost a 50% speed increase.
If you require a rock solid telephone and do not want to mess with stability then don't over clock. If you on the other hand like experimenting just go ahead and try it.
just remember to make a nandroid backup that you can go back to in case your phone doesn't work properly after installing the new kernel.
if we overlocking the wildfire , can i play divs with rockplayer or auther?
If I have WPR 8.06 installed and the 0050kernel, is it ok to try installing new kernels to test? And if its unstable, just test a new one? (have a previous nanbackup that I done directly after rooting the phon).
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Akerhage said:
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!
Click to expand...
Click to collapse
You can flash kernels back and forth. You don't have to reflash the entire ROM for that. Just make sure you have a working nandroid backup first in case your phone doesn't want to boot.
Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
Yes, in Theory. In practice computer CPUs have temperature monitors that will limit CPU speed to prevent it from rising to high.
In the context of a phone it will be to hot to handle before the temperature becomes high enough to do any critical damage.
Yes, the life time of the electrical circuits will be shortened but a mobile phone will become outdated. Besides the phone is only active for very short periods of time compared to computer.
Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
with a 768mhz speed?.. i dont think it will result to an intense heat that makes the device unusable.. it will make more heat than usual but its tolerable enough..
@OP
Please post in the appropriate sections. This thread belongs in the General Section not Android Development.
After reading, reading and more reading on these forums (thanks to everyone posting) I've finally broken into the true capabilities of these phones. I come to a question every time i'm surfing around tho...
Voodoo or not?
If so, what do the sv, lv, ov remarks mean when choosing a kernel? I havent and dont want to mess things up on my phone...
any insight is always appreciated
I guess you run what the phone can handle. From a logical point of view, if you increase the performance of something it will need more fuel to operate. Some folks seem to be able to get away with low voltage or ultra low voltage kernels at the higher processing speeds without ill affects but it was the opposite for me. When I tried the OTB ul1300, lv1300, or sv1300, it would constantly have issues running most any app, and the lower the voltage the more it would boot loop. With the over voltage 1300 I was able to almost function normally but it still wasn't steady enough for daily use. Any 1200 I tried worked with no problems.
You go with stability and performance that suits you. If I were you I would start at the top but have all of the kernels you want to try at the ready so you can go into recovery and flash another and try again until you settle on what works best. The 1300's are almost guaranteed to give you problems but it's a simple fix if you have them all on standby.
Whether to go with voodoo or not; it works very well and with the new recovery(red lagfix version), it is a piece of cake to disable. Just go to voodoo menu and disable for next boot and enable the partition conversion. As long as you are testing voodoo kernels, you don't have to mess with that setting. Just flash the next one.
I came from a g1,mytouch,and droid 1 to the fascinate. Rooted from day 1. I also questioned the voodoo method. I chose not to because of the hassle of removing it to install certain roms then reinstalling it. It fixes lag in the file system but i truely haven't noticed any without it. And to answer your kernel questions....oc=overclocked sv=standard voltage and lv=low voltage (doesn't always work with all phones)
Sent from my SCH-I500 using XDA App
xlinth said:
I chose not to because of the hassle of removing it to install certain roms then reinstalling it.
Click to expand...
Click to collapse
Yeah, you don't have to do that any more. Voodoo5 plays well with Clockwork (or, actually, comes with its own custom Clockwork), so you only have to remove it to switch to a non-Voodoo kernel. Nandroid backups, restores, etc. can all be done with Voodoo active.
Plus removing it doesn't hang up much (if at all) these days.
What I'm battling is battery life, I'm running DJ05/SuperDark v.9/StupidFast 1.54. I use my phone for almost everything, all the time(even now via wifi tether for internet). I'm expierencing moderate batt life. Although I have ample oppurtunities to be on a charger, I'm worrying about those times I cant. Obviously I want great life w/ great performance. Maybe I'm watching the battery too much and expecting more than I should. I guess I'm still trying to find the best combination for my needs. Can't wait for cyanogen.
props to all the devs
Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!
a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?
It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.
Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.
You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.
I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??
xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.
First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App
Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.
I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..
Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA
xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.
Apologies if this is covered elsewhere, but I have been struggling to trawl through all 1000 pages on the relevant thread as I can't get the search terms to get the info!
Basically, when I leave the phone overnight charging, in the morning I cannot turn it on unless I press and hold the power button and volume down to reset the device.
Other than this it is great in terms of being able to adjust the colours and the battery life seems better.
I have tried both the nightly and stable versions..
What ROM are you using?
Sent from my Nexus 4 using xda premium
murtezahu said:
What ROM are you using?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am currently using the stock ROM but could change to a custom... (I am learning as I go at the moment...)
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
LOL
Sent from my Nexus 4 using xda premium
sounds like a classical case of sod. do you undervolt?
and rolmply
simms22 said:
sounds like a classical case of sod. do you undervolt?
Click to expand...
Click to collapse
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
vindikleuk said:
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
goldeneye243 said:
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
Click to expand...
Click to collapse
do you use the pgm slide to wake app?
simms22 said:
do you use the pgm slide to wake app?
Click to expand...
Click to collapse
No, I don't - Should I, or is it possibly what is could have caused the problem?
goldeneye243 said:
No, I don't - Should I, or is it possibly what is could have caused the problem?
Click to expand...
Click to collapse
its a possible cause of sod if you had it installed.
goldeneye243 said:
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
Click to expand...
Click to collapse
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:. From my experience, you wouldn't need any battery management apps when you're on franco's M1 anyway - using common sense to save your battery should suffice.
vindikleuk said:
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:.
Click to expand...
Click to collapse
I will do that if I have not already got it fixed with the reboot. Battery guru is still in learning mode so possibly isn't messing with the kernel yet but is the next thing to try...
Alrighty, let's hope it'll get figured out.
vindikleuk said:
Alrighty, let's hope it'll get figured out.
Click to expand...
Click to collapse
Well, it turned on OK this morning, so hopefully fixed...
I guess I will only know in a few days time when I have got more confidence...
I had another SOD so I have reset all settings (installed nightly version 110) and started again -
The only changes I have made are to the gamma settings and changing the governer to conservative to see if that gives me a longer battery life.
Will see how it goes....
I had some more SODs with 110/111 so I changed to 121 and the battery life did not seem as good.
Takes a while to work out what is going on when it only happens once a day...
I still get occasional SODs with battery guru disabled so i guess it is either the kernel or possibly the ROM... I will try on the support thread....
I have a very odd problem that I can't solve nor diagnose, my device (N9005) keeps rebooting at no expected pattern if I changed CPU governor to anything but interactive or under-voltage.
The problem started about a year or so ago and since then I have tried lots of roms, kernels and batteries if they had something to do with it but I can't understand why the reboot happen.
I can record a cat log if it would show the problem and if someone can help identify the cause of it or if someone already familiar with this problem and solve it would be much better.
I would appreciate any suggestions in order to try and solve the issue.
What happens with stock rom ??
JJEgan said:
What happens with stock rom ??
Click to expand...
Click to collapse
You mean AOSP or TW? since both can be considered stock in different ways xD
Anyway, the behavior is the same on either but the problem started while on Temasek's ROM last year which was and still my main rom.
Samsung stock TW .
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Samsung stock TW .
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Aha, and same thing happen as mentioned earlier.
tharwat96 said:
Aha, and same thing happen as mentioned earlier.
Click to expand...
Click to collapse
Check your CPU binning (pvs) and read about it. You might find answers.
zlazaar said:
Check your CPU binning (pvs) and read about it. You might find answers.
Click to expand...
Click to collapse
Thank you very much for the suggestion. However, after reading about it which is a very new concept for me so thank you again for that, I understood it affects overclocking speeds and tolerance but I still don't understand what could it mean to my case.
One thing I forgot to mention or implicitly mentioned is that, I used to use conservative or powersave governors and used to undervolt by 25mv till the problem occured.
Also, I think checking device's CPU binning method differs from a device to another (not sure if I'm right) but I tried a command found on OPO's site and it didn't show an actual output but it showed a 1 before the usual command line and I don't know if it means anything but thought of mentioning it anyway.
tharwat96 said:
Thank you very much for the suggestion. However, after reading about it which is a very new concept for me so thank you again for that, I understood it affects overclocking speeds and tolerance but I still don't understand what could it mean to my case.
One thing I forgot to mention or implicitly mentioned is that, I used to use conservative or powersave governors and used to undervolt by 25mv till the problem occured.
Also, I think checking device's CPU binning method differs from a device to another (not sure if I'm right) but I tried a command found on OPO's site and it didn't show an actual output but it showed a 1 before the usual command line and I don't know if it means anything but thought of mentioning it anyway.
Click to expand...
Click to collapse
You can find your soc's pvs by navigating to /sys/devices/system/soc/soc0 then open the file "soc_pvs" with a text viewer.
There will be an integer (from 1 to 6).
1 means best support for undervolt/overclock. And 6 the worst one.
Your phone reboots when you just set different governor (no undervoltage applied) ? And which governor you set ?
zlazaar said:
You can find your soc's pvs by navigating to /sys/devices/system/soc/soc0 then open the file "soc_pvs" with a text viewer.
There will be an integer (from 1 to 6).
1 means best support for undervolt/overclock. And 6 the worst one.
Your phone reboots when you just set different governor (no undervoltage applied) ? And which governor you set ?
Click to expand...
Click to collapse
Thank you very much for your reply.
I just checked and it is actually 1 .
The governor I was trying to set was Yankactive/ondemand.
There's a chance that the problem is actually fixed but I'm still not sure. However, if it's solved the reason would be ridiculous actually but compounded into 2 parts and I'm not sure if one of them it the main cause or both but they are the most recent changes which led to the current stability with no reboots since 2 hours now.
The first part is the SELinux status which was enforcing and had to change it to permissive for any heavy change otherwise it won't work and it kept changing after every reboot so what I did is forcing it to change to permissive on each boot. and it helped a lot but I'm not sure how it affected my situation.
The second part is that I was using PowerNap xposed module and there's a chance that it force stops the android system. I also have no idea how this contribute to solving my problem since the problem existed before even installing xposed.
Anyway, I'm still testing the device to see if it's actually solved.
tharwat96 said:
Thank you very much for your reply.
I just checked and it is actually 1 .
The governor I was trying to set was Yankactive/ondemand.
There's a chance that the problem is actually fixed but I'm still not sure. However, if it's solved the reason would be ridiculous actually but compounded into 2 parts and I'm not sure if one of them it the main cause or both but they are the most recent changes which led to the current stability with no reboots since 2 hours now.
The first part is the SELinux status which was enforcing and had to change it to permissive for any heavy change otherwise it won't work and it kept changing after every reboot so what I did is forcing it to change to permissive on each boot. and it helped a lot but I'm not sure how it affected my situation.
The second part is that I was using PowerNap xposed module and there's a chance that it force stops the android system. I also have no idea how this contribute to solving my problem since the problem existed before even installing xposed.
Anyway, I'm still testing the device to see if it's actually solved.
Click to expand...
Click to collapse
Sorry i did a mistake.
The higher the PVS bin value the better. This means 1 is not good.
I have the value of 1 on my Note 3 and undervolt by 30 with zero problems. Also i change between interactive and performace govs a dozen times a day.
zlazaar said:
Sorry i did a mistake.
The higher the PVS bin value the better. This means 1 is not good.
Click to expand...
Click to collapse
Undervolting aside, shouldn't I be able to change governors no matter the PVS bin value? since it matters the most while overclocking and I'm trying to do the opposite
RaduNastase said:
I have the value of 1 on my Note 3 and undervolt by 30 with zero problems. Also i change between interactive and performace govs a dozen times a day.
Click to expand...
Click to collapse
I used to do too but no clue what happened on newer Android versions. BTW, which ROM and Kernel you are on?
Kernel: CivZ-KK_Xplorer-Rev1.9
Rom: Omega 4.4.2 v24
I am using both Synapse and Kernel Toolkit for CPU/GPU tweaking, as they wok well together (on the other hand Kernel Adiutor conflicts with Synapse).
In case you want to know, the battery goes down 1% every hour or so in idle and about 1% every 3 minutes of using the phone with screen on (browsing, gaming, etc).
RaduNastase said:
Kernel: CivZ-KK_Xplorer-Rev1.9
Rom: Omega 4.4.2 v24
I am using both Synapse and Kernel Toolkit for CPU/GPU tweaking, as they wok well together (on the other hand Kernel Adiutor conflicts with Synapse).
In case you want to know, the battery goes down 1% every hour or so in idle and about 1% every 3 minutes of using the phone with screen on (browsing, gaming, etc).
Click to expand...
Click to collapse
I believe your battery is dead?
tharwat96 said:
I believe your battery is dead?
Click to expand...
Click to collapse
Why do you say that? It's brand new (bought it original from Samsung, a month ago). One of the few new original batteries left in stock. manufactured at the end of 2014.
Only yesterday (@3%) i got 4 hours of gaming in Retroarch emulator (pretty intensive on the CPU), with a total of 4 h and 40 min SOT, with the Note charged to full 21 hours before that. Pretty decent performance imo.
RaduNastase said:
Why do you say that? It's brand new (bought it original from Samsung, a month ago). One of the few new original batteries left in stock. manufactured at the end of 2014.
Only yesterday (@3%) i got 4 hours of gaming in Retroarch emulator (pretty intensive on the CPU), with a total of 4 h and 40 min SOT, with the Note charged to full 21 hours before that. Pretty decent performance imo.
Click to expand...
Click to collapse
O.O I'm terribly sorry I somehow misread your post.
I was confused when I read it since I was actually sticked to SlimKat before switching to nougat because of the battery.
BTW, what is your usual SOT without heavy usage?
tharwat96 said:
O.O I'm terribly sorry I somehow misread your post.
I was confused when I read it since I was actually sticked to SlimKat before switching to nougat because of the battery.
BTW, what is your usual SOT without heavy usage?
Click to expand...
Click to collapse
Well, it depends on how bright the image is. That is if you watch some darker images or pages, it consumes less than white ones.
If i unplug it in the morning (i usually unplug it in the evening), the SOT is a sure 5 hours, with some 5 % left in the evening.
RaduNastase said:
Well, it depends on how bright the image is. That is if you watch some darker images or pages, it consumes less than white ones.
If i unplug it in the morning (i usually unplug it in the evening), the SOT is a sure 5 hours, with some 5 % left in the evening.
Click to expand...
Click to collapse
Aha, now with RR nougat and synergy the consumption is very close to yours.
tharwat96 said:
Aha, now with RR nougat and synergy the consumption is very close to yours.
Click to expand...
Click to collapse
Great Should be even better overall with that deep sleep option that nougat has.
RaduNastase said:
Great Should be even better overall with that deep sleep option that nougat has.
Click to expand...
Click to collapse
When the device doze the battery percentage gets stuck for how long you may leave the device idle, it's pretty impressive