So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?
Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.
So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?
Click to expand...
Click to collapse
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium
absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
false works fine with the camera fix
beankid said:
Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.
Click to expand...
Click to collapse
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.
crazylilazn said:
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.
Click to expand...
Click to collapse
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots
CheesyNutz said:
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots
Click to expand...
Click to collapse
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?
crazylilazn said:
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?
Click to expand...
Click to collapse
I use app + data but only for market installed apps, I don't backup system apps or any of the apps installed with the rom. I personally have not had any problems doing it this way. I have not had any reboots or major lags on Viper XL btw.
I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2
thejosh86 said:
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
CheesyNutz said:
false works fine with the camera fix
Click to expand...
Click to collapse
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
Checkout post #3 of the BeastMode kernel thread.
zounduser said:
I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I actually flashed the 1.8Ghz version, and I have been running it at 1.7Ghz only.
However, I have all the voltage-step frequencies set to the default. Global voltage is also set at "0 mV". Does anybody have any suggestions for the Voltage Frequency Steps?
Also, although I have the "Use Separate Voltages" unchecked. I noticed two separate settings for Frequency steps that seems kind of odd.
On one, the frequency says 0MHz, with a corresponding voltage of 852mV.
However, right underneath, the frequency says 0MHz again, but with a voltage of 0 mV. Is that something I should change?
absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
At least two weeks ago, I only found it because I was flicking through the viper thread.
Like redpoint said check post #3 of the thread.
Sent from my HTC One XL using xda premium
Related
Sense 4.0 keeps crashing, and I can't do anything
I am S-off and hboot 1.27.000
//Ignore quoted text, it was the OP
Hi,
I have just installed the ViperS rom v1.1.0.. well when I say just, I mean about 2 hours ago.
Its still busy booting... at the screen where it says HTC Sense and then animates to HTC Sensation with the snake that moves out, and also has the beatsaudio logo.
is it supposed to take this long?
I used most of the default settings when installing, apart from removing a few apps, ie twiiter, flckr, etc.
Also changed the GPS fix to South Africa, as that is where I'm from.
Thanx
Click to expand...
Click to collapse
hmm ok, so eventually got the rom working...
however sense 4.0 keeps crashing... so I cant do anything.
Any suggestions?
I was using viper and my device kept freezing. I kept having to pull battery to get it to un freeze. The older version never done that. Perhaps it's the Rom It's self? Many people use viper without issue, but for me it continued to freeze. I did fresh install, wiped, on newest firmware, just can't figure out what's causing it? Last version ran wonderfully! This version had to pull battery around 5 times a day to un freeze .....
Sent from my Sensation 4G using xda premium
realsis said:
I was using viper and my device kept freezing. I kept having to pull battery to get it to un freeze. The older version never done that. Perhaps it's the Rom It's self? Many people use viper without issue, but for me it continued to freeze. I did fresh install, wiped, on newest firmware, just can't figure out what's causing it? Last version ran wonderfully! This version had to pull battery around 5 times a day to un freeze .....
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
I am going to flash the older version now v1.0.1, to see if my problems are sorted.
Do you know if I need to change my kernel or anything for mine to work?
is it just me or is the aroma installer buggy?
No it should work fine with default kernel. It's bricked. Never had a problem with older version. Ran like a dream! Just new updated version brings issues...
Sent from my Sensation 4G using xda premium
realsis said:
No it should work fine with default kernel. It's bricked. Never had a problem with older version. Ran like a dream! Just new updated version brings issues...
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
hmmm flashed older version now and still does the same... sense 4.0 perma crash
the sens4 crash might be a firmware issue. Or it may happen if you did not do a full wipe.
Strange because older version was solid .but the new version I can't use. Too many issues with freezing. Have you tried the new ROM lightning? It's also sense4 and seems fast and smooth and has tweaks and aroma installer.? I'm trying it out now. Seems good and solid.
Sent from my Sensation 4G using xda premium
You should try cm10 if you fancy jellybean...
Sent from my HTC Sensation using xda app-developers app
i ever used viper rom older version
but when i tried to connect to my office's wifi, when the wifi ask identity and password, the place for input the identity and password is keep disappear.
i don't know where is the problem, and i never post it in the developer section, because my post is not enough yet hehehe
After flashing 1.2.1 (and .0) as well, I can record 1080p videos only in default app.
Dailyroads and blackbox (recording video in case of car accident) are not working - recording just crashes. Performed full wipe. Anybody has similar problem?
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Did you try fixing permissions?
Zalithian said:
Did you try fixing permissions?
Click to expand...
Click to collapse
Do that and also format cache and dalvik.
shinjielric said:
Do that and also format cache and dalvik.
Click to expand...
Click to collapse
Did all of those and still no change in outcome.
MistarJones said:
Did all of those and still no change in outcome.
Click to expand...
Click to collapse
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
shinjielric said:
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
x714x said:
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I tried with several camera alternatives and all said couldn't connect to camera as well. :/
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
DertyDOH said:
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
Click to expand...
Click to collapse
I tried that and any backup still having camera FC issues.
Originally Posted by shinjielric
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
Click to expand...
Click to collapse
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
I've had the same issue and reflashed multiple times and tried all the above.
My Galaxy III SCH-I535 operates on Android 4.1.2 aokp_d2vzw_jb_milestone_1
Kernel is 3.0.48-cynagenmod-faux123-vzw...
I love this ROM. I'm not sure how it randomly a day or two into operation just quit the camera operation completely. This would be a real miracle solved
MistarJones said:
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Click to expand...
Click to collapse
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
re fix
bandit2443 said:
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
Click to expand...
Click to collapse
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
MistarJones said:
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
Click to expand...
Click to collapse
Oh wow... that's an idea i hadn't thought of. Samsung replaced it under warranty? What did you tell them was wrong with it?
Camera Can't Connect & Firmware
shinjielric said:
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I am having the "cannot connect" issue on CM10. I posted about it here: http://forum.xda-developers.com/showthread.php?t=2152348
The camera works fine in stock, but on CM10 no-go. According to this post its a firmware issue: http://forum.xda-developers.com/showthread.php?t=2006128
only problem is to fix I need to figure out what camera firmware I have so I can flash a new one - but I cannot determine what firmware i535 has? Anyone?
Based on another thread, seems like I might be able to copy the bins from the cameradata folder on stock where the camera works. No need to flash or anything.
http://forum.cyanogenmod.org/index.php?/topic/66022-Can't-Connect-To-Camera
Sent from my SCH-I535 using xda app-developers app
I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
EDIT: I was just able to flash over the ElementalX kernel just fine. I'm still confused on why Beastmode isn't flashing. When I go to install from TWRP, the .zip install time is no less than 2-3 seconds long and then it says finished.
Sent from my HTC One XL using xda app-developers app
Really... 151 views and not one person has a suggestion?
Sent from my HTC One XL using xda app-developers app
The kernel didn't stick or the CPU settings?
I went into setcpu and it said min 384 max 384 after flashing the kernel.. so I sent min to 384 and max to 1809 and applied set on boot. That worked for.me, but I notice a few bugs. Like the lockscreen won't unlock so I have to hard reboot
Sent from my HTC One XL using xda app-developers app
The kernel...
Sent from my HTC One XL using xda app-developers app
Myrder said:
I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Don't post threads unless you've tried full wipe. No one knows what's wrong if you're doing a dirty flash.
Myrder said:
The kernel...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Works for me and I use SetCPU..
Might just do a factory reset and see if that won't solve my problem.
Sent from my HTC One XL using xda app-developers app
work yet? I have the same problem and i am on stock .....wiped dalvik,cache, before i flashed it....it just says sucessfully installed...it flashes very quickly for some reason when I know it should not...did a recovery before i flashed, recovered....still nothing..
Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.
Myrder said:
Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.
Click to expand...
Click to collapse
Don't do it! IceColdJelly isn't worth it!
absolutelygrim said:
Don't do it! IceColdJelly isn't worth it!
Click to expand...
Click to collapse
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.
Myrder said:
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.
Click to expand...
Click to collapse
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy
absolutelygrim said:
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy
Click to expand...
Click to collapse
This I know, I saw that when I found ViperX 2.6 in the international thread... Going to try the stabilizer from the v4 thread and see if that will work. read a post about page 14 +/- a page said to try the stabilzer and see if that would work.
Edit: Speaking of no fix for bricked 2.20, how's that coming? Jtag looking like the only method so far? Haven't read your WIP thread in awhile.
Edit2: Stabilizer didn't do a thing. I really want to be able to flash this kernel... :crying: Seems like it does a really nice job for everyone that has it working... Might end up with going back to RUU again, when I feel I am competent in flashing everything correctly, in the next day or so.
So I've tried another option..
Trying to pull the boot.img from the kernel using "adb pull /tmp/abootimg". Since that looks like where it makes the boot.img in Aroma. Didn't work.
Just flashed ElementalX v1.14 and that works just fine.
Ok, so this is probably a weird one. I'm using an HTC One X with ViperX 2.1.2 Rom on stock kernel. I started noticing that when I use Google Search (the widget or the app), I'll search for something and when the results come up, I couldn't click on some of the results. I click on the blue text and it just highlights it once then does nothing. It won't launch the browser. So then I was noticing that it was only happening sometimes, so I continued to experiment and found that it only does it when the title of the result extends onto two lines. If the resulting webpage title is only one line long, the link opens the browser perfectly every time. This being one of the most used features on my phone, it gets extremely irritating. I've tried everything I know to try. Please help!
Bump
Can anyone help me?
Wipe caches and reflash gapps would he my suggestion. May even want to redownload your zip to make sure its not corrupt.
Sent from my One X using xda premium
subarudroid said:
Wipe caches and reflash gapps would he my suggestion. May even want to redownload your zip to make sure its not corrupt.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Tried that and only made more problems. I just found that when I rotate my phone to landscape while viewing the results in.google now, I am able to open any result. (Because the webpage titles don't extend onto two lines). Such a weird issue! It's like when you tap a result, the programming only knows to try to open the immediate next line.
I just tried to duplicate your issue. All works well. I'm on CM10 with full 4.2 gapps. ???? Maybe try a different ROM?
Sent from my One X using xda premium
subarudroid said:
I just tried to duplicate your issue. All works well. I'm on CM10 with full 4.2 gapps. ???? Maybe try a different ROM?
Sent from my One X using xda premium
Click to expand...
Click to collapse
I would, but I love the viper rom so much. It's just this small issue that I can't figure out. I've tried finding a reinstall for google now itself that is compatible with ViperX 2.2.0, but haven't been able to find it. Does anyone know where i can get that?
Thanks
Must have been a super rare problem, no one else has had it like me. I since installed a newer version of viper and it works fine. I think a potential for some of the weirder random problems with these roms might be a virus scanner on your computer (if you downloaded the Rom on your computer). Seems that it might break the Rom in small ways.
Sent from my HTC One XL using Tapatalk 2
I have this exact problem, it persists even though I totally wiped and reinstalled the entire Rom (negalite blurom in htc evo 3d) two separate times months apart
Sent from my HTCEVOV4G using XDA Premium 4 mobile app
xnaterion said:
I have this exact problem, it persists even though I totally wiped and reinstalled the entire Rom (negalite blurom in htc evo 3d) two separate times months apart
Sent from my HTCEVOV4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you have the latest version of Google Search installed? Have you tried clearing the app data and cache? Or uninstalling and reinstalling the app?
Sent from my Evita
timmaaa said:
Do you have the latest version of Google Search installed? Have you tried clearing the app data and cache? Or uninstalling and reinstalling the app?
Sent from my Evita
Click to expand...
Click to collapse
Just the version that came with the rom ...can't update I because it's not compatible on the play store. I did some research and since it is an ICS rom it must be some special modded version of the JB or whatever version of Google search. All the projects trying to mod the newer Google search versions to ICS appear dead, so I figured it was hopeless and just used "Google now remover". Now I'm back to the old Google search. Funny though, as this rom is still in somewhat active development and it's specifically designed for my phone but nobody on the development thread has ever mentioned this problem. Oh well, not really a problem for me now.
If you have root you can use Titanium Backup to uninstall system apps, you could do that and then install Google Search from the Play Store which should update it to the latest version.
Sent from my Evita
Hey everyone, I have the HTC One X and it has restarted at least 3 times today and around 3 times yesterday also.
I realize there are other threads on here but none of them have my ROM or have no solutions.
The bootloader is unlocked (via HTC Dev), it's rooted, and I have the CleanROM 6 R2 ROM installed. It's incredibly annoying considering every time it restarts I have to restore my widgets, set up Swiftkey again, etc. ANNOYING. Please help
What can I do to fix this?
Thanks a ton XDA
Custom kernel or the one that comes with cleanrom? Overclock or undervolt at all?
Sent from my One X using xda app-developers app
exad said:
Custom kernel or the one that comes with cleanrom? Overclock or undervolt at all?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No custom kernel at all, just flashed CleanROM 6 and got a new boot splash screen from a trusted guy here, so the only kernel I have is the one that is w/ CR.
Didn't overclock or undervolt.
Did you check the md5 before flashing to make sure the download wasnt corrupted?
Sent from my One X using xda app-developers app
exad said:
Did you check the md5 before flashing to make sure the download wasnt corrupted?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No, but I'm pretty sure the download wasn't corrupt as nothing else seems to be wrong with my phone.
toughtrasher said:
No, but I'm pretty sure the download wasn't corrupt as nothing else seems to be wrong with my phone.
Click to expand...
Click to collapse
That is not logical reasoning. A corrupted ROM flash can cause a wide range of issues, multiple or just one.
Also what version of twrp are you using? Did you wipe cache dalvik system and factory reset prior to flashing?
Sent from my One X using xda app-developers app
exad said:
That is not logical reasoning. A corrupted ROM flash can cause a wide range of issues, multiple or just one.
Also what version of twrp are you using? Did you wipe cache dalvik system and factory reset prior to flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I am using the latest version of TWRP. I followed all the instructions from ScottsRoms.com when I flashed CustomROM 6.
Flash 2.3.3.1 or under, all versions above have issues wiping.
Fastboot erase cache after then wipe everything and flash the ROM again.
Sent from my One X using xda app-developers app
So I flash a older version of TWRP, clear cache, erase everything, then flash the same rom?
what can I use to backup my apps? because I really don't want to start over again.
Sent from my HTC One X using Tapatalk 2
toughtrasher said:
So I flash a older version of TWRP, clear cache, erase everything, then flash the same rom?
what can I use to backup my apps? because I really don't want to start over again.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
it's a bug with 4.1 jellybean. Use titanium backup to backup swiftkey, and other widgets that resets on boot. Then uninstall them in settings and go back to titanium and restore the apps and data.
s1l3nt said:
it's a bug with 4.1 jellybean. Use titanium backup to backup swiftkey, and other widgets that resets on boot. Then uninstall them in settings and go back to titanium and restore the apps and data.
Click to expand...
Click to collapse
I think this guy is confused but he's right about titanium backup backing up your apps.
Sent from my HTC One X using xda app-developers app
exad said:
I think this guy is confused but he's right about titanium backup backing up your apps.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
h8rift said:
FAQs
Q: My paid application (ex Swype, Swiftkey, Beautiful Widgets) is not there/set by default after a reboot.
A: This is a known Jellybean problem. See here for more details.
Click to expand...
Click to collapse
i'm not confused at all
backing up the applications and restoring them with titanium "fixes" the issue
Fixes random reboots?
Sent from my HTC One X using xda app-developers app
exad said:
Fixes random reboots?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
You are right, i was confused
Sent from my Nexus 7 using Tapatalk 2
toughtrasher said:
Hey everyone, I have the HTC One X and it has restarted at least 3 times today and around 3 times yesterday also.
I realize there are other threads on here but none of them have my ROM or have no solutions.
The bootloader is unlocked (via HTC Dev), it's rooted, and I have the CleanROM 6 R2 ROM installed. It's incredibly annoying considering every time it restarts I have to restore my widgets, set up Swiftkey again, etc. ANNOYING. Please help
What can I do to fix this?
Thanks a ton XDA
Click to expand...
Click to collapse
My girlfriend's has started doing this as well. Stock rooted, clean Rom, and viper. Stock reboots the least, about 3 times a day. Clean Rom reboots up to 10 times a day. Maybe the device is slowly dying?
Sent from my Nexus 4 using Tapatalk 4 Beta
uToTMeH8 said:
My girlfriend's has started doing this as well. Stock rooted, clean Rom, and viper. Stock reboots the least, about 3 times a day. Clean Rom reboots up to 10 times a day. Maybe the device is slowly dying?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
S-OFF if you aren't already, and RUU. Keep it like that for a few days and see if it's still happening. If so, then yes it's hardware related.
htc one xl rebooting itself
i installed venom rom ics,but from last few days it keeps on restarting ,when i try to go to recovery by using bootloader,it again restarts but it doesnt come to recovery mode...what should i do
saikrishnagatika said:
i installed venom rom ics,but from last few days it keeps on restarting ,when i try to go to recovery by using bootloader,it again restarts but it doesnt come to recovery mode...what should i do
Click to expand...
Click to collapse
Bootloader details and exact ROM version please.
Transmitted via Bacon
I'm also having constant reboots and crashes, 3-4 times a day and if I go to sleep I always wake up to find the phone off, which is extremely annoying and somewhat concerning as I need to be reachable by some people. I'm using the TeamEOS ROMs. I haven't found a custom ROM yet that doesn't crash constantly after a while. They all seem stable at first but as time goes on the crashes get more and more frequent, I wipe and reset as recommended (cache and dalvik) with every flash.
S-ON
HBOOT 2.14.0000
Radio 0.24p.32.09.06
OpenDSP v34.1.0.45.1219
TWRP v2.7.1.0
Any recommendations for a truly stable ROM? Or a Fix? RUU? (haven't done that before, don't even know where to find it)
yarch said:
I'm also having constant reboots and crashes, 3-4 times a day and if I go to sleep I always wake up to find the phone off, which is extremely annoying and somewhat concerning as I need to be reachable by some people. I'm using the TeamEOS ROMs. I haven't found a custom ROM yet that doesn't crash constantly after a while. They all seem stable at first but as time goes on the crashes get more and more frequent, I wipe and reset as recommended (cache and dalvik) with every flash.
S-ON
HBOOT 2.14.0000
Radio 0.24p.32.09.06
OpenDSP v34.1.0.45.1219
TWRP v2.7.1.0
Any recommendations for a truly stable ROM? Or a Fix? RUU? (haven't done that before, don't even know where to find it)
Click to expand...
Click to collapse
Updating your firmware might help. Download and instructions in my guide thread (link in my signature).
Transmitted via Bacon