Hi there,
Running Android Revolution with faux123's latest kernel and recommended radio etc.
Everything is running swimmingly except that HTC Sense occasionally closes while I'm running a program.
It doesn't ruin the phone but it's a huge inconvenience for a custom rom.
It'll also reboot sometimes but that's for another time
zeecfc said:
Hi there,
Running Android Revolution with faux123's latest kernel and recommended radio etc.
Everything is running swimmingly except that HTC Sense occasionally closes while I'm running a program.
It doesn't ruin the phone but it's a huge inconvenience for a custom rom.
It'll also reboot sometimes but that's for another time
Click to expand...
Click to collapse
Clear data for sense apk in applications/ manage applications/ all apps. Reboot and see what happens. Should fix your issue
Hi.. Do you make full wipe?.. Before flash new rom..
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
thanks rddocke, that should work, didn't occur to me :S
@mrboy I did a superwipe and dalvik/cache wipe.
And uhh, mental note for those doing the same, remember your home settings or jot them down somewhere
No problem buddy and you should only superwipe if your flashing a Rom with a different build. Like 3.0 to 3.5 or leedroid to arhd. Not necessary for updates on current Rom. I never superwipe. Don't like the hassle. But there is a program developed by..... I forget sorry!.... But it allows you to restore apps on masses rather than one by one. Which makes restoring from full wipe a lot more convenient
Oh I've got titanium backup which i think created the issue when I restored sense with the data.
My advice to anyone else is. wipe dalvik/cache when changing from same rom type and pick and choose which apps you want to restore WITH data
Related
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Ssunyoto said:
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Does it happen specifically with the market? Or does it also happen with other apps too? Also, are there any other common factors among your random reboots (the colloquial term for what you are referring to)? My best advice would be to wipe your dalvik cache, cache, and data and then reflash the rom and kernel. Restore your apps the long way and see if that solves your problem.
(the reason I'd recommend this is that it sounds like there is an issue with your flash and a clean flash might clear that up)
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Ssunyoto said:
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Its no problem man, everyone has "silly" questions when they start. =)
Basically, the Dalvik cache (found in advanced in Clockwork Recovery mod, aka CWM) is a list of things to boot. It speeds up the booting process but it also can cause issues during boot if there are conflicts between an old rom and a new one so wiping this is always good.
When you flash a new rom, you don't need to wipe everything, just wipe the Dalvik Cache (again found in the advanced section of CWM), Cache (found in mounts and storage and the actual action you'll be selecting will be "format cache"), and Data (found in mounts and storage and the actual action you'll be selecting will be "format data"). Once you do this flash your rom. Now if you're going to flash a kernel that you have never used before, I generally suggest allowing the phone to boot to make sure everything is fine, get myself all setup, to do a NANDroid backup before adding the kernel. That is my preference and is by no means necessary. Once you flash the kernel you can reboot and re-add your apps.
Now, I mentioned Titanium Backup and I'm still not sure you 100% know what that is so let me explain (as it is a very useful tool). It is a program that backs up your applications all with their data (IE preferences and the like). It does a great job (with the one exception that due to the way Android is built it cannot restore widgets) but it does require some work so it gets tedious when you have to use it a lot. I generally only use it the first time I'm flashing a new ROM. If you want to have a variety of roms you can easily access and switch between here is something I posted in another thread that can make it very, very easy to do:
kenvan19 said:
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).
Click to expand...
Click to collapse
I apologize for the huge wall of text but I hope it helps! Always remember that we're here to help you (as long as you search before you post a question, not applicable to this but it makes everyone's lives easier hehe)
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Ssunyoto said:
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm. Try this: turn off your phone and then once its off hold the volume up button and then press the power. This should boot you into the bootloader. Now using the volume rocker to scroll and the power button to select, select recovery. Let it boot into that then tell me what color the text is in recovery.
Sent from my Nexus S
Fixed
Hey Kenvan,
Thanks for the help, I decided to revert back in to stock Android with no root and I have stopped having problems with anything! I also do not experience the rebooting during calls bug.
Thanks!
Hi all,
I can't post in the Desire S Development forum yet, so I might as well ask the question here.
I've been trying in vain to use CM on my Desire S (one of the major reasons why I wanted to root my phone). I'm able to use it for a while, but after a time, such as installing all my apps, it would hang on me and the only way to fix it is to remove the battery. At first, I thought it would be due to the Go Launcher EX, but it hanged when using ADW too. Then I thought that perhaps restoring the system data were the culprit, but I still got the same dilemma when I didn't. I then started restoring the apps one by one (using Titanium Backup) but it seems that it hangs at random.
I really want to use CM but I can't Has anyone encountered this problem? Anyone knows how to correct it?
Thanks in advance guys
Complete wipe all partition then reflash. Double check your phone's current HBOOT, RADIO, KERNEL if it is supported.
I have had CM7.1 working perfectly on my Desire S for weeks and I used Titanium Backup to restore previous apps and data.
The questions I would ask are which version of CM? 'Stable' or one of the nightlies? Have you formatted all your partitions to EXT4 first? What recovery are you using - shouldn't matter, but might be relevant if it's failing to write something properly. Did you verify the checksum after you downloaded CM7.1? Have you installed anything else from recovery mode afterwards, such as GAPPS? What happens if you install CM and just try running your Desire as a phone for a few days, using only the built-in apps - does it still hang?
Also, when it does hang, you are much better off trying to 'soft' kill it rather than pulling the battery if you possibly can - hold 'Vol -', 'Vol +' and 'Power' for maybe as long as 30 seconds to see if that works; pulling the battery can cause serious hardware failure.
Stable!
Nightlies are for experimentals only
Sent from my HTC Desire S using xda premium
well i have no issue at all.
No issues here either, also used TB to restore apps.
Don't restore any sense system apps or data, I imagine that could cause problems.
Sent from my HTC Desire S using xda premium
Thanks for the replies guys I'm using the ROM Manager app to dl and install CM. I always use the stable build. The recovery I use is 4ext. Kernel is stock, I think. The one that comes with the LBC mod, which is the one I'm currently using. How do I check for the radio? Oh and what radio and kernel are you guys using?
doesn't have hang issue....but my desire s did shut down by itself. It can be on again by pressing the power button but still it annoys me twice this week.
p/s : using cm7.1 stable release
BTW, here's my radio: 20.28b.30.0805U_38.03.02.15_M
How do I check compatibilities?
the radio perform same as in sense rom, i use radio as at my sig and its perform well.
Just an update:
I think I found the app that's making all the bollocks. I was using File Organizer to create labels and custom folders.
At first, I spend the whole time yesterday rebooting/restoring the ROM and found that problems arise when I started placing Folder Organizer widgets. Today, I restored the ROM again and instead used Go Launcher EX to create custom folders for the Home Screen. So far so good, it's just as snappy as the time I just installed CM. It's crappy that I'm no longer able to use one of the apps I paid for, but it's worth it because of all the ROMs (stock and custom) that I encountered, CM is the snappiest and the best
I'll still monitor the progress, but so far, it hasn't hang on me. Before uninstalling Folder Organizer, it would usually take around a minute before it hangs completely, and the soft reset (Power + Volume Down) doesn't work when that happens
Hi i have a problem with the ice cream samwich rom i install all rom all perfect but i have one problem the wifi no work please i need a help for fix this problem and take a signal wifi this rom work perfect only i need this help - I intall wifi fix APK but no work anything other solution for fix this bug? please i wait a goo respond thanks!!
billaboy said:
Hi i have a problem with the ice cream samwich rom i install all rom all perfect but i have one problem the wifi no work please i need a help for fix this problem and take a signal wifi this rom work perfect only i need this help - I intall wifi fix APK but no work anything other solution for fix this bug? please i wait a goo respond thanks!!
Click to expand...
Click to collapse
More info please. What ics ROM are u using?
If you can read this, I's been a drinkin
I had a similar problem with a used Desire HD -- I eventually found that doing a factory data reset solved the problem.
Seach the thread of the Rom your currently using first to see if anyone else if having that issue. Be sure to FULLY wipe before flashing the Rom. After fully wiping and re flashing, test your WiFi before restoring anything from tibu. If it works start restoring you user apps one by one to see if maybe one of those is giving you the fits. DO NOT restore any system apps.
Sent from my Desire HD using Tapatalk 2
Also, don't forget to flush the caches when installing the ROM. I know that failure to do this can cause issues with a fresh ROM.
cwhitney24 said:
Seach the thread of the Rom your currently using first to see if anyone else if having that issue. Be sure to FULLY wipe before flashing the Rom. After fully wiping and re flashing, test your WiFi before restoring anything from tibu. If it works start restoring you user apps one by one to see if maybe one of those is giving you the fits. DO NOT restore any system apps.
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
i was a nub and restored wifi passwords/config with tibu and killed my wifi entirely until i wiped. dont make this mistake
superwipe
I recommend you get super wipe from the Android rom revolution HD thread. Boot recovery and run super wipe whenever you install a new rom or during some updates. After super wipe than install your ROM and.then install inspire mod.zip and then reboot. If your wifi then does not work then you should install wifi fix. Most ROMs I've used I don't need the wifi fix actually never needed it. I highly recommend asopx ICS ROM. Latest version 31 has most everything except video can working.
1shukla said:
I recommend you get super wipe from the Android rom revolution HD thread. Boot recovery and run super wipe whenever you install a new rom or during some updates. After super wipe than install your ROM and.then install inspire mod.zip and then reboot. If your wifi then does not work then you should install wifi fix. Most ROMs I've used I don't need the wifi fix actually never needed it. I highly recommend asopx ICS ROM. Latest version 31 has most everything except video can working.
Click to expand...
Click to collapse
I was using AOSPx all day today and then around 7pm randomly lost signal and it never came back. Had to do factory reset and its working again but now I'm back to reinstalling a ton of apps.
asopx
Mehal88 strange about your wifi problem on asopx. Did you try a.simple reboot instead of factory wipe? I'm assuming you are talking wifi signal and not att? I'n my area radio, ril, and apn settings make a HUGE difference.
I've treid to flash both CM9 & CM10 and it worked, exept that ΒΌ of my apps won't start. They start for one second, and then, the show either an FC message or just close without any message. I've tried to wipe the data for some apps, but that don't change anything. The apps are restored with TitaniumBackup. I've always returned back to ViperS because of that problem, so does anybody now how to get rid of that problem and make the apps run again?
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Did u flash gapps?
Sent from my HTC Sensation using Tapatalk 2
Some apps dont work with backup programs because they tether themselves to the device ID. That way they can't be passed around to multiple phones and have to be downloaded fresh for all users.
When you flash a new rom the device id changes, so the app thinks its on a new phone.
Titanium has an option to revert to a previous device id in the paid version.
Still, a quarter of your apps seems like alot. If you are trying to restore system apps that's a whole different issue. System apps dont transfer well.
And any sensed based apps from Viper will simply never work in CM. Ever. That is probably the bulk of your problem apps im guessing.
Sent from my HTC Sensation using xda app-developers app
Yes! Gapps is flashed. I do only restore user apps .. I'll try to find the device id option and try again
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Recently I have been getting the white reset screen whenever I close an app. I know this means I have too little ram, but I keep checking and I am never below 100 free ram. Could something in the background be shutting sense down?
Do you use custom or stock rom? Do you have Gingerbread or ICS installed on your device? if you are very desperate, you may try doing a factory reset. If you are using stock ics, not rooted phone, go to DEVELOPER options in SETTINGS and set BACKGROUND PROCESS LIMIT to MAX 4. It helped me as well before I rooted my phone.
I am using arhd 1.2 for tmobile with faux and sense 3.6.
Did you disable MDP? In kernel I mean. It once caused me some problem but I'm not sure of cause too.
And try wiping dalvik and cache. Works too
It has been a while since I installed arhd so I am not sure. I'll check later.
If you haven't, you may want to reflash the rom and say yes to the supercharger option. Or checkout the supercharger thread on XDA.
I have found flashing a supercharged services.jar stops the Sense reloading screen when I'm on a sense 3.6 rom.
Sent from my HTC Sensation Z710e using Tapatalk 2