Related
This is a custom kernel for the Continuum. It's based off of the DL17 source provided from Samsung, but should work on DJ20 as well. There are a lot of changes to the stock kernel though, and I'll try to list them all.
Features
init.d support, from Adrynalyne, also requires busybox with run-parts support
Voodoo Sound (v9), from supercurio, use Voodoo Control App to adjust settings
Voodoo Lagfix, from supercurio and the Project Voodoo team, applies only to files labeled with voodoo5
Undervolted
Updated CPU scaling to reduce lag
Battery fix, from SirGatez, allows for the use of non-oem batteries
USB Mount fix, from SirGatez, prevents phone from mounting as a cd-rom drive
ThumbEE Support
Removed almost all debugging
Optimized compiler flags
Updated in 0423
Simple IO Scheduler
SDCard Read Fix
Tweaked TCP settings
Tweaked CFS
Updated in 0510
Voodoo Sound V8
Disabled custom boot animations (for real this time)
Switched to Linaro Toolchain for cross compiling
Removed shutdown animation from zip
Made flash script CWM 3.x compatible
Disable CD-ROM Mount (maybe?)
Voodoo Lagfix <-- FLASH WITH CAUTION
Updated in 0529
Voodoo Sound V9
Voodoo Lagfix should no longer convert /cache which caused market download problems
Known Issues
Video issues on boot, works fine after the system boots up though. Will work on fixing it, if I can find out the root cause.
Naming convention
novoodoo - kernel does not have Voodoo Lagfix
voodoo - kernel has Voodoo Lagfix, create /sdcard/vodooo/disable-lagfix to prevent filesystem conversion
Thanks goes to DroidXcon, TrailBlazer102, Logan302, dfgged, and crazyknight
.zip files can be flashed with CWM Recovery, see here
If you like my work, feel free to donate to me. Alternatively, sign up for Dropbox via my referral link Also, remember that none of this would really be possible without the generosity of DroidXcon, so you could donate to him as well.
If you would like to develop your own kernels, visit my Github
If you have any questions about how to flash the files, ask before flashing, not after. I have only attached the novoodoo version of the kernel to this post due to issues in the past with Voodoo on the Continuum. If you would like to test out the Voodoo version, PM me and I'll send you the kernel with voodoo. Be warned though that in the past, there were issues with people using voodoo lagifx.
Just flashed the one with standard voltage with voodoo lagfix., Works good.
Edit: Never mind i see you uploaded that lol.
Ok for some reason i cant download anything from the market. It says your item is downloading and then just stops and says nothing.
CrazyKnight122 said:
Ok for some reason i cant download anything from the market. It says your item is downloading and then just stops and says nothing.
Click to expand...
Click to collapse
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.
adrynalyne said:
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.
Click to expand...
Click to collapse
SOunds good ill give it a try.
adrynalyne said:
This happens sometimes. If its a large item, disable voodoo from voodoo recovery, and then let it convert back. Then install the large item (over 20mb seems to be an issue). Then convert back.
Click to expand...
Click to collapse
It's a problem with the cache being converted to ext4. When apps are being installed from the market they are downloaded to the /cache partition and then installed to /data after fully downloaded, however if there isn't enough space in /cache, due, here, to the fact the ext4 journal takes up quite some space, then it can't download the app or game to the cache to install it, and it errors out. I've talked to supercurio about it and he states he's working on it.
Yeah i tried disabaling it and downloading something and it still doesnt work.
Try clearing cache from within recovery and see if that helps.
Tried it and didnt work.
No big deal really i can wait for a fix lol.
I got it to work.
I flashed the 50 undervolt kernal and set up voodoo lagfix and worked perfect first time.
I was using the 100 undervolt kernal before. Also the 50 had the dancing bananna bootani and the 100 did not.
CrazyKnight122 said:
I got it to work.
I flashed the 50 undervolt kernal and set up voodoo lagfix and worked perfect first time.
I was using the 100 undervolt kernal before. Also the 50 had the dancing bananna bootani and the 100 did not.
Click to expand...
Click to collapse
They should both be the same minus the undervolt level
The 100 undervolt didnt have the dancing banana boot ani just the stock.
Can anyone test to see if there are video issues on boot with these?
imnuts said:
Can anyone test to see if there are video issues on boot with these?
Novoodoo
Voodoo
Click to expand...
Click to collapse
Ill give it a try.
just sat at the samsung screen for me.
CrazyKnight122 said:
just sat at the samsung screen for me.
Click to expand...
Click to collapse
I can confirm that they just freeze :|
Well, the novoodoo one does the video problems.. Then just like shuts off..
trailblazer101 said:
I can confirm that they just freeze :|
Well, the novoodoo one does the video problems.. Then just like shuts off..
Click to expand...
Click to collapse
hmm, something must be messed up in my source tree Will need to figure that out, but I'm guessing it happened when i was trying to get it all on Github.
hmm.. okay... Hopefully its not anything big
I posted a picture of what the video problems look like on the IRC for when you are done working
trailblazer101 said:
hmm.. okay... Hopefully its not anything big
I posted a picture of what the video problems look like on the IRC for when you are done working
Click to expand...
Click to collapse
Thanks I'm pretty sure I know how to fix the no-boot issue, shouldn't be to difficult, though it will prevent anyone from building off of my Github until I get it fixed.
ah, okay.. sweet
So, i would like to confirm that i have my own boot animations working on my phone now im so happy its working!
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
ajay131 said:
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
Click to expand...
Click to collapse
which kernel are u using???
which stock rom u used when u flashed hyperion??
what steps did u take to flash hyperion detail??
ajay131 said:
I have created this thread as the "Hyperion 7.x | Pre GM" is temporarily closed.
I have successfully flashed the "Hyperion 7.x | Pre GM".. It works 10-15 min & then goes back to boot logo... Same problem happened with me on flashing previous version of this ROM... I doesn't face any problem while flashing other ROMs. Followed the instructions carefully.. Please help me to solve this problem...
Click to expand...
Click to collapse
This is because of undervolting
You can try one of these
1. If you don't need undervolting, then
1. Using root explorer go to /etc /init.d
2. There will be either one of the two files:
--> 00undervolt or
--> bacem_tweak
Just delete it if any of these is present..
Click to expand...
Click to collapse
I think hyperion has 00undervolt script..
bacem_tweak was in jelly blaat but I am not sure about it
2. If you want to use undervolting then
1. Using root explorer go to etc/init.d
2. Search for the mentioned files
3. Open with text viewer
4. Change undervolt vaue.. eg if it is -120mv, change it to -100mv or lower
Click to expand...
Click to collapse
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority and can be locked in the memory. Previous builds of Hyperion has kernel panic tweak adapted from zeps scripts but it works desirable only in stabke kernels. Sadly, the tweak causes some minor problems so it was removed in 7.x.
Here's what you can do, investigate on your device/apps and see how much memory each app takes and how much background services you have (using devtools).
Also, reducing startup applications (using autostarts) will help in decreasing unnecessary system load.
Some quick and handy troubleshooting that you may try:
1. Reflash the rom
2. Reformat the 2nd partition of your SD Card
NOTE:
I/We/DevTeam cannot guarrantee that your phone will perfom as expected (based on our test) if you are using other tweaks and/or kernel.
CarlDeanCatabay said:
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority
*taking a break* will come back after a while
Click to expand...
Click to collapse
hey carl
i need some help !!i ve flashed hyperion 7 GM final and fixed my wifi ,data connection problem from your dev section OP !!my wifi is connected but can't browse any thing !!data connection is fine but wifi is connected but no browsing !!!i am using white kernel 1.3.3 with wifi drivers!any suggestions to solve it???
percy215 said:
hey carl
i need some help !!i ve flashed hyperion 7 GM final and fixed my wifi ,data connection problem from your dev section OP !!my wifi is connected but can't browse any thing !!data connection is fine but wifi is connected but no browsing !!!i am using white kernel 1.3.3 with wifi drivers!any suggestions to solve it???
Click to expand...
Click to collapse
It is either the wifi driver from WhiteXP's Kernel or the mother of all host file in Hyperion 7 GM that's causing the problem.
NOTE:
Drivers are the bridge between your Wireless NIC and the system itself, it there is something wrong with the driver, we cannot expect the device (your phone) to behave as we would expect.
You can:
Re-download (to make sure files are intact) and re-install (to make sure drivers are properly installed) the wifi driver
Modify your hosts file and/or remove NetForks tweak. Instructions are posted in Hyperion's Thread in Wireless and Network Troubleshooting.
CarlDeanCatabay said:
It is either the wifi driver from WhiteXP's Kernel or the mother of all host file in Hyperion 7 GM that's causing the problem.
NOTE:
Drivers are the bridge between your Wireless NIC and the system itself, it there is something wrong with the driver, we cannot expect the device (your phone) to behave as we would expect.
You can:
Re-download (to make sure files are intact) and re-install (to make sure drivers are properly installed) the wifi driver
Modify your hosts file and/or remove NetForks tweak. Instructions are posted in Hyperion's Thread in Wireless and Network Troubleshooting.
Click to expand...
Click to collapse
Thnx for info I will try reflashing it and use another kernel!
Sent from my GT-S5360 using xda premium
@percy bro: i flashed this on my rooted stock rom. No any other kernel or tweak..
@khazir amin sir: as per ur instruction, change undervolt value to 100.. No problem till last half N hour... If any, will update the comment..
@carlDeanCatabay sir: thanx for the valuable info... Since long time wanted to try this rom... But same problem occured with each version...
Thanx to all you guys... To help me..
Sent from my Brain...
CarlDeanCatabay said:
Hi,
Please try to re-flash Hyperion and do not restore any backup be it titanium backup or cwm backup as it may restore corrupted files. The description of the problem may have one or more cause which as of now isn't clear yet.
Make sure your sd card's 2nd partition is clean as by experience, an un-cleaned 2nd partition may cause problems or boot loop.
I can't say that there's no problem with Hyperion but we tested it several times before release without getting the problem you are reporting.
If you are getting system reboot, this *maybe* caused by kernel panic, it is a situation where the system gets loaded and the only way to avoid lockups is to force the system to reboot.
In most cases, background services/applications may remain in the memory (specially root apps) as they are given high priority and can be locked in the memory. Previous builds of Hyperion has kernel panic tweak adapted from zeps scripts but it works desirable only in stabke kernels. Sadly, the tweak causes some minor problems so it was removed in 7.x.
Here's what you can do, investigate on your device/apps and see how much memory each app takes and how much background services you have (using devtools).
Also, reducing startup applications (using autostarts) will help in decreasing unnecessary system load.
Some quick and handy troubleshooting that you may try:
1. Reflash the rom
2. Reformat the 2nd partition of your SD Card
NOTE:
I/We/DevTeam cannot guarrantee that your phone will perfom as expected (based on our test) if you are using other tweaks and/or kernel.
Click to expand...
Click to collapse
well the reboot problem in my case was due to -120mV undervolting which is pre included in the rom..
and probably this is the same case here..
so please reduce the undervolt value to -100 etc
Changed the value to 100.. Worked well. But when i connect charger. It again restarted... So i deleted the 000undeevolt or whatever that file is.. N working good now.. No restart even on charging...
Thanx again Amin sir for the help...
Sent from my Brain
I'm glad I never had those problems coming from stock rom! Been using Hyperion 7 for quite sometime now and I can say that it's stable and responsively fast. I just hope that the development of Hyperion will be back. :waves at Carl
Sent from my GT-S5360 using Xparent Cyan Tapatalk 2
HYPERION 8 and HYPERION 7.. auto restard PROBLEM!!!
Sir Catabay can you help me fix auto restart problem on SAMSUNG GALAXY Y. At first i thought that it was battery problem cuz my battery got overcharge. then i buy a new one. it was ok until it happen again.. From Hyperion 8 i change ROM cuz i thnk that the rom wasnt compatible so i tried the Hyperion 7.. yet still it happens again..T_T i dont know what to do now.. i ended up erasing apps and formatting my sd card.:crying:
same problem
I had the same problem but now I'm using creeds rom 3.5 and it's stable
This is a banned rom..
Threads related to banned rom are not allowed on xda..
@Lady Android
Sent from my GT-S5360 using Tapatalk 2
sanny5 said:
This is a banned rom..
Threads related to banned rom are not allowed on xda..
@Lady Android
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
hi sanny,
i appreciate your report but i mods have warned before not to use the quote function since the report button is there
anyways,
banned roms and their discussions are not allowed on xda
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
logs?
poodleDoo said:
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
Click to expand...
Click to collapse
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
I would use ODIN or KYES to flash it back to OEM stock firmware. Also remove the micro SD card if you have one in there, sometimes corrupt cards can cause boot loop.
true
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
sharing
poodleDoo said:
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
Click to expand...
Click to collapse
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
dsilx said:
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
Click to expand...
Click to collapse
The tablet did the same without the sdcard, and I tried a couple times to do a factory reset with no luck.
The fact that it does the same with a different ROM and kernel is what makes me think it's hardware related
moonbutt74 said:
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
Click to expand...
Click to collapse
Cool, i'll get syslog installed and see if I can find anything.
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
awesome
poodleDoo said:
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
Click to expand...
Click to collapse
Awesome to hear sounds like @moonbutt74 was right
Hope it keeps working have fun
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
cool
poodleDoo said:
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
Click to expand...
Click to collapse
Well that sucks u have to have battery saver on all the time but at least its working now
hmmm
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
moonbutt74 said:
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
Click to expand...
Click to collapse
I'm running rooted deodexed stock ROM with Blackhawk 2.1 kernel.
But as I mentioned in the OP, the problem was there with the full stock device, the new ROM and kernel were installed after the problem started.
ouch
i think you pegged it right with internal storage being damaged.
only thing i can think of besides getting your money back is do a full data partition wipe and format
and a full system wipe and format
either way that has to suck. sorry i couldn't help.
m
I had my htc one replaced under warranty for battery issues and purple camera issue.
My new one is running latest nusense rom but i had the same issue on stock debloated/deodexed rom.
Sometimes the screen just won't turn on. It appears that issue is only present when charging. Last time it happened i was tethering and internet connection was fine even though the phone was unresponsive.
The only solution is reset by holding the power button.
Any ideas?
thatsonlyme said:
I had my htc one replaced under warranty for battery issues and purple camera issue.
My new one is running latest nusense rom but i had the same issue on stock debloated/deodexed rom.
Sometimes the screen just won't turn on. It appears that issue is only present when charging. Last time it happened i was tethering and internet connection was fine even though the phone was unresponsive.
The only solution is reset by holding the power button.
Any ideas?
Click to expand...
Click to collapse
Is the USB OEM, ive had cheap cables from china do this to me in the past.
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
thatsonlyme said:
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
Click to expand...
Click to collapse
sorry to hear that, are you getting replacement from VZW or HTC?
Verizon. I replaced my original phone through them, it was easy and free. It sucks that i will have to pay for the sunshine root again.
I might try flashing new firmware first just to see if that makes any difference but i'm afraid it's hardware issue
synisterwolf said:
Is the USB OEM, ive had cheap cables from china do this to me in the past.
Click to expand...
Click to collapse
thatsonlyme said:
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
Click to expand...
Click to collapse
I remember there was an issue like this with other older HTC models, like the Rezound... Try, if you can, upping the min frequency up one notch. Synisterwolf remembers this old issue.
That can be a temp fix until you get your replacement.
Sent from my HTC6500LVWBLU using XDA Free mobile app
thatsonlyme said:
Verizon. I replaced my original phone through them, it was easy and free. It sucks that i will have to pay for the sunshine root again.
I might try flashing new firmware first just to see if that makes any difference but i'm afraid it's hardware issue
Click to expand...
Click to collapse
i would take your Paypal statement and pm jcase and tell him whats going on. maybe he can work something out with you.
Ive had my share of lemons from VZW. i hope you have better luck with the next one.
So far daydream mode seems to be preventing screen from freezing. i will try upping the frequency.
is it possible that this is software issue if it works?
thanks for all your help, it's much appreciated!
Also does anyone know what stock default frequency is? I'm pretty sure that i selected default upon installation but i'm wondering if i might have accidentally underclocked. My default was 384, i upped it to 486.
I'm just hoping that this is just a kernel issue i guess lol
Even though i had it happen on stock deodexed rom too. I'm not sure about full stock because i rooted and flashed immediatelly lol
thatsonlyme said:
Also does anyone know what stock default frequency is? I'm pretty sure that i selected default upon installation but i'm wondering if i might have accidentally underclocked. My default was 384, i upped it to 486.
I'm just hoping that this is just a kernel issue i guess lol
Even though i had it happen on stock deodexed rom too. I'm not sure about full stock because i rooted and flashed immediatelly lol
Click to expand...
Click to collapse
When it does it freezing thing and you reboot into android pull a last kernel message like this ...
Code:
adb pull /proc/last_kmsg
Upload it as a .txt file to xda so we can take a look...
Thx Josh
Looks like frequency change did the trick. It's been working fine since i change it.
When I get a chance, I'll try to set it back to 384 and pull the kernel message. Thanks Josh.
lj50036 said:
When it does it freezing thing and you reboot into android pull a last kernel message like this ...
Code:
adb pull /proc/last_kmsg
Upload it as a .txt file to xda so we can take a look...
Thx Josh
Click to expand...
Click to collapse
is there any way i can pull last_kmsg without adb and save it on my phone, download it later? this damn thing just won't freeze now when I'm home and I won't have access to my computer with adb later so I wonder if I could just pull it through root explorer. I located the file but can't figure out how to open it from my phone.
thatsonlyme said:
is there any way i can pull last_kmsg without adb and save it on my phone, download it later? this damn thing just won't freeze now when I'm home and I won't have access to my computer with adb later so I wonder if I could just pull it through root explorer. I located the file but can't figure out how to open it from my phone.
Click to expand...
Click to collapse
Last_kmsg is the kernel log from last boot. Just go into any file explorer that has root permissions and go to /proc folder. Copy the last_kmsg file to your SD card
Sent from my HTC6500LVWBLU using XDA Free mobile app
I had the same issue with my lg g. I think its a kernel issue. Not sure about yours.
Uzephi said:
Last_kmsg is the kernel log from last boot. Just go into any file explorer that has root permissions and go to /proc folder. Copy the last_kmsg file to your SD card
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I tried that yesterday but for some reason it wouldn't copy. I guess I'll just have to wait until it happens when I'm home.
mudassirrashid said:
I had the same issue with my lg g. I think its a kernel issue. Not sure about yours.
Click to expand...
Click to collapse
I kinda hope you're right because the phone works great when I upped the minimum frequency and I don't feel like dealing with another warranty replacement, returning this one to stock and rooting my new phone.
What worries me is that it first happened on santods stock deodexed rom with stock kernel, now it's happening with santods nusense six with kernel that came with that rom.
I'm thinking about returning it to full stock but I really need tethering to work. maybe I'll just try stock rooted with wifi tether.
thanks for all your help guys!
thatsonlyme said:
I tried that yesterday but for some reason it wouldn't copy. I guess I'll just have to wait until it happens when I'm home.
I kinda hope you're right because the phone works great when I upped the minimum frequency and I don't feel like dealing with another warranty replacement, returning this one to stock and rooting my new phone.
What worries me is that it first happened on santods stock deodexed rom with stock kernel, now it's happening with santods nusense six with kernel that came with that rom.
I'm thinking about returning it to full stock but I really need tethering to work. maybe I'll just try stock rooted with wifi tether.
thanks for all your help guys!
Click to expand...
Click to collapse
Welcome dear
So i tried new lunar kernel on default settings, it froze again 10 minutes after i left home. Once again i couldn't pull last_kmsg. At this point i'm pretty sure it's a hardware defect. I guess another trip to Verizon store is in order
Yesterday i returned the phone to stock, leaving it rooted and s-off. No freezing at all so far. So i guess it's not a hardware issue. I'll try installing older version of TWRP recovery and try to do fresh flash of nusense.
flashed back nusense with an older recovery with all stock settings last night, this morning the phone wouldn't wake up.
finally managed to pull last_kmsg. (i had to upload it as zip file, it wouldn't allow me to upload the file with no extension)
thatsonlyme said:
flashed back nusense with an older recovery with all stock settings last night, this morning the phone wouldn't wake up.
finally managed to pull last_kmsg. (i had to upload it as zip file, it wouldn't allow me to upload the file with no extension)
Click to expand...
Click to collapse
Cant unzip that zip file..... :fingers-crossed:
Thx Josh