Related
Foremost, I apologize if this has been asked and answered before. I've been searching for weeks...maybe I'm a bad searcher.
My issue is that I have been experiencing random force closings on random apps, including random partial reboots when unlocking the Unlock screen (screen freeze then goes to Rom intialization screen). Sometimes Dolphin HD closes when loading pages, same with stock browser and Opera Mini, though sometimes the same page will load fine (both with JS on and off and with Flash turned off in Froyo ROMs). Swype (v.2.15) will sometimes close when typing in the search widget or an SMS message in both ChompSMS and stock messaging app. Titanium Backup and Astro sometimes close when scrolling down the app list. The only consistant factor that I can think of is available RAM or the processor overheating.
I have installed multiple ROMs thinking its ROM-specific, but the same behavior manifests in each one. I've tried Assonance 5.2, Cognition 3.04, Phoenix 4.5 and Serendipity 5-1.4.
With each new flashing I first use Odin to get back to stock, then use Odin to Master Clear, then root the phone, then install Clockwork, flash it's recovery app and then use Clockwork to flash the new ROM.
I did fresh installs of any apps I installed from the Market as I know user data from 2.1 will cause issues with 2.2.
Because I thought it was a RAM issue I installed Autokiller Memory and used the 'Optimum' preset.
After all this I still have the same issues with random apps closing and the phone doing ROM reboots when at random times I unlock the phone. Can anyone give me some guidance?
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
diablo009 said:
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
Click to expand...
Click to collapse
I'll give your ROM a shot.
Stupid question - Do all ROMs have kernels and modems cooked into them? I was just thinking that I've been flashing tons of ROMs lately and I'm not sure of the most stable kernels to have.
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
avgjoegeek said:
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
Click to expand...
Click to collapse
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
DRoc740 said:
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
Click to expand...
Click to collapse
When u restore to stock, format the internal SD from within windows. (Ok, I won't contest anyone's arguments on this, but I personally find it easier than doing a master clear and to wipe off even the basic folders android os format creates.)
And, I would recommend u download a fresh copy of 5.5, with a kernel that does not have any OC in it, to play safe. 5.5 is available in two versions - one with OC kernel, and one with non-OC kernel.
It could be a case of kernel too. Try swapping kernel and see if that helps. Not all kernels go well with all hardware. That's the reason I swapped to xcalibur kernel as soon as I loaded 5.5.
I think, personal opinion here, u could do away with clockwork recovery too. U cud download the cwm console update.zip and put it on ur sdcard root. And apply the update.zip with in console in stock to load up CWM console. This is the most non-intrusive way of going to CWM console as far as I know.
I've been running stock since yesterday with zero issues. My force closing issue usually appears within an hour of flashing a new ROM so this is a very good sign that its a flashing and not a hardware issue.
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Maybe its a kernel issue as I think i've exhausted all other options. I'll try xcaliburinhand's v2.3.2 01.31.2011 and see if it works.
Any other suggestions?
DRoc740 said:
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Click to expand...
Click to collapse
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
diablo009 said:
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
Click to expand...
Click to collapse
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
DRoc740 said:
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
Click to expand...
Click to collapse
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not now be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
diablo009 said:
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
Click to expand...
Click to collapse
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
DRoc740 said:
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
Click to expand...
Click to collapse
welcome to the world of flashing. let me (us) know if u need any more help
diablo009 said:
welcome to the world of flashing. let me (us) know if u need any more help
Click to expand...
Click to collapse
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
DRoc740 said:
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
Click to expand...
Click to collapse
did you restore anything with titanium backup?
Pirateghost said:
did you restore anything with titanium backup?
Click to expand...
Click to collapse
No, didn't restore anything.
I flashed the update and had the force closings within a few minutes while I was typing an SMS using Swype.
Bumping
I have the same problem
i have used darky9.2 and lagfix for a period of time
and some days ago
i reset my i9000 in the setting-----applications
will there be any problem?
coz my frd tell me i cant reset my phone as there will be some important data deleted
so what should i do?
if i want to use darky 9.5 or other rom
do i need to unlagfix and how to do it?
marco199311 said:
i have used darky9.2 and lagfix for a period of time
and some days ago
i reset my i9000 in the setting-----applications
will there be any problem?
coz my frd tell me i cant reset my phone as there will be some important data deleted
so what should i do?
if i want to use darky 9.5 or other rom
do i need to unlagfix and how to do it?
Click to expand...
Click to collapse
Doing a factory reset wont cause any problems, too be honest it fixes problems, all it will do is delete your apps and settings.
if you are flashing to another ROM you SHOULD ALWAYS DISABLE LAGFIX, the only times you dont need to undo the lagfix is when upgrading, say... from darkys 9.5 - 10.0 BUT, only if you are on the same kernel.
to be safe i always disable lagfix, the times i dont, i make a nandroid backup.
its better to be safe than try and fix a bricked phone, it takes a few minutes to disable / make nandroid so its always worth it.
azzledazzle said:
Doing a factory reset wont cause any problems, too be honest it fixes problems, all it will do is delete your apps and settings.
if you are flashing to another ROM you SHOULD ALWAYS DISABLE LAGFIX, the only times you dont need to undo the lagfix is when upgrading, say... from darkys 9.5 - 10.0 BUT, only if you are on the same kernel.
to be safe i always disable lagfix, the times i dont, i make a nandroid backup.
its better to be safe than try and fix a bricked phone, it takes a few minutes to disable / make nandroid so its always worth it.
Click to expand...
Click to collapse
how to disable lagfix?
marco199311 said:
how to disable lagfix?
Click to expand...
Click to collapse
Instructions are with the lagfix or posts you used .
jje
So im wondering, what is the standard practise, or based on your own experiences. What is the best way to flash over an existing rom using CWM? What do you do to prepare the fone for new rom, wipe user data, dalvik cache, before or after flashing. Just trying to get a good idea of how to do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Pirateghost said:
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
Click to expand...
Click to collapse
+1
Except I do clear the caches manually, but that's just because I have OCD.
CremeFraiche said:
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Click to expand...
Click to collapse
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Thx for info guys, I have flashed a few times and it seemed like now and then my fone must became bogged down and needed to be fully wiped, sound didnt work or lagfix folders bunch of text docs, just seemed cluttered. So if wanted to really clear out junk what would be a good way without having to flash back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just flash. If you have a problem then back to stock Ans a MC. I have flashed hundreds of time back to stock once.
Sent from my SGH-I897 using XDA Premium App
Pirateghost said:
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Click to expand...
Click to collapse
I would definitely agree. I have also seen people say to disable lagfix before flashing. I have not done that either and never had any problem.
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
modest_mandroid said:
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
Click to expand...
Click to collapse
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Glad to hear the advice about not flashing back to stock, that's been one of the major reasons I haven't flashed quite as many rom's as I want, too time consuming.........not to say that i'm not flashing a couple rom's a week, but there's just so many options to try
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Making "search" a standard practice would be very helpful.
Restoring system is known to mess up ROMs in all cases. Though may not be mandatory, but make it a standard practice to flash stock. Takes hardly 10 mins, and helps save big headaches later.
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Incompatibilities across rom versions, mostly. As the guy above me said, restoring system files tends to mess up a rom because you are overwriting part of it with files from a different rom.
There is one caveat, however. If you're flashing back to a rom you originally performed the backup on, you can safely restore system files. For example, if you were running Cog 4.3 and did a full TB backup, then decided to flash Serendipity 6.3, you would want to restore only your user apps and user data. However, if you decided to flash back to Cog 4.3 at some point, you could do a full TB restore without worrying about incompatibilities.
I agree with everyone else. Flashing over another rom seldom causes issues. I make s nandroid backup of my favorite rom with everything setup the way i like it. then flash away trying different roms. When i am done, i just restore my backup and all is good!
I have done a search, couldn't find the specific answer I needed, hence my asking. Could be I wasn't phrasing the search correctly......but here I am.....
To clarify, what do you dpo to get your system settings back after flashing a new rom? I flashed to serendipty 6.4 last night, as per the advice, I didn't restore system files, just apps and data, but that didn't work so well for me. I lost my data connection, could only use my wifi, and had no contacts, or any sms msgs. I don't know what else was missing, but I then went and restored system files, everything came back as needed, and there seems to be no issue......
How do I get my info setting back, or do I just need to manually re-set everything after flashing? Apart from wireless info, msgs and contacts, what else do you lose by not restoring?
Appreciate your help
havent flashed a new rom in a while and forgot if anything extra was needed when flashing a rom over a rom
thx!
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
2) If its not fixable, what ROM you advice me to reinstall? I have s5830XWKS2, some people say the DDxxx8(or something like that) is better don't know why I'm no programmer...
2.1) If I really have to have to reinstall it in order to fix it, how can I do it? Can you point out the thread for it?
3) I run a small business, and I use Tasker for all my stuff. together with other 60+ apps I need to keep, i'm using SD card with ext partition with Link2SD. And the thing i'm most afraid of, is loosing all the data. I came from a Nokia 5800XM, and I flashed it some times, backups are easy to do. Now here on Android becomes a bit complicated. Maybe never someone cleared me enough about it. So what can I do to sucessfully restore all data on the new ROM? I got Titanium backups, and CWM..Will that backup even my dictionary saved words?
4) Thanks, and please, again, make notice that I can't loose anything due to my business, but I can't work with phone needing to reboot at random times cause of wifi or bluetooh beeing bricked.
First of all. There is no such things as urgent situation here. You should remember that.
Second thing. You should post questions in Q&A sub-section. General is for sharing and discussions.
Third thing. There is a adb logcat thingie, which allows to understand a root of your problem more than 'Help me. Something doesn't work'
I remain this thread open but move to correct section.
NunoPitbull said:
Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
2) If its not fixable, what ROM you advice me to reinstall? I have s5830XWKS2, some people say the DDxxx8(or something like that) is better don't know why I'm no programmer...
2.1) If I really have to have to reinstall it in order to fix it, how can I do it? Can you point out the thread for it?
3) I run a small business, and I use Tasker for all my stuff. together with other 60+ apps I need to keep, i'm using SD card with ext partition with Link2SD. And the thing i'm most afraid of, is loosing all the data. I came from a Nokia 5800XM, and I flashed it some times, backups are easy to do. Now here on Android becomes a bit complicated. Maybe never someone cleared me enough about it. So what can I do to sucessfully restore all data on the new ROM? I got Titanium backups, and CWM..Will that backup even my dictionary saved words?
4) Thanks, and please, again, make notice that I can't loose anything due to my business, but I can't work with phone needing to reboot at random times cause of wifi or bluetooh beeing bricked.
Click to expand...
Click to collapse
Yes I experienced the same problem,could be software bugs problem so I think you can reinstall your software for the better.
I prefer cm mod7/8 for ace as it is much faster so you can try Google cyanogenmod for ace. They have all the tutorial you need.
As for your Apps, titanium backup will do fine. Its the best backup so far. Your dictionary words is the default system one? I recommend you smart keyboard pro as it has the function to backup all your words
So in short, backup your EVERYTHING with titanium backup, rmb your contacts too, and install cyannogen mod 7 or 8 whichever you prefer! Hope this helps!
Sent from my LG-P705 using xda premium
spaz1201 said:
Yes I experienced the same problem,could be software bugs problem so I think you can reinstall your software for the better.
I prefer cm mod7/8 for ace as it is much faster so you can try Google cyanogenmod for ace. They have all the tutorial you need.
As for your Apps, titanium backup will do fine. Its the best backup so far. Your dictionary words is the default system one? I recommend you smart keyboard pro as it has the function to backup all your words
So in short, backup your EVERYTHING with titanium backup, rmb your contacts too, and install cyannogen mod 7 or 8 whichever you prefer! Hope this helps!
Sent from my LG-P705 using xda premium
Click to expand...
Click to collapse
There's no such thing as cyanogen mod 8...only unofficial cm 7.1 kang and official cm 7.2...
Nunopitbull, wifi & bluetooth problems that you experience are caused by the kernel, not the firmware or rom...so my suggestion is to use a kernel that is not based on cf root or use a stock kernel (the one that came with your phone)...just root your phone with the update zip method will do, and for cwm flash the zip for it...the newest version for sga is 5.0.2.6...there's no need to flash a custom kernel...
About cwm backups, it backups your whole system and data partition and also your boot.img (kernel related)...so yes, it is quite safe to say that your whole phone is backup-ed...but keep in mind that stock roms use .rfs format for the partitions...new custom roms use .ext4 format...so to flash a backup of a stock rom, first flash a fresh stock firmware with ODIN and the cooper.pit file...then re-root and re-flash cwm to restore your phone...
And fyi, link2sd uses a second partition right? The apps inside the second partition can be relinked if you reset the phone...as long as you don't format the second partition...but personally I suggest you to use DTa2sd or amarulzz script as it saves more internal space...check it out...
Hope that all the above helps...
So you're saying my problem of wi-fi/bluetooth is because of kernel? Can you help me by PM how to get it working again? I wanted a custom kernel don't remember already why, but I think was for the custom speeds of CPU, so I could have low ones..
Just want this bug to disapear of bluetooth and wifi!
Ryuinferno said:
There's no such thing as cyanogen mod 8...only unofficial cm 7.1 kang and official cm 7.2...
Nunopitbull, wifi & bluetooth problems that you experience are caused by the kernel, not the firmware or rom...so my suggestion is to use a kernel that is not based on cf root or use a stock kernel (the one that came with your phone)...just root your phone with the update zip method will do, and for cwm flash the zip for it...the newest version for sga is 5.0.2.6...there's no need to flash a custom kernel...
About cwm backups, it backups your whole system and data partition and also your boot.img (kernel related)...so yes, it is quite safe to say that your whole phone is backup-ed...but keep in mind that stock roms use .rfs format for the partitions...new custom roms use .ext4 format...so to flash a backup of a stock rom, first flash a fresh stock firmware with ODIN and the cooper.pit file...then re-root and re-flash cwm to restore your phone...
And fyi, link2sd uses a second partition right? The apps inside the second partition can be relinked if you reset the phone...as long as you don't format the second partition...but personally I suggest you to use DTa2sd or amarulzz script as it saves more internal space...check it out...
Hope that all the above helps...
Click to expand...
Click to collapse
So far I haven't seen a custom kernel for sga that works flawlessly...especially the ones with oc function...only stock kernels work with the least problems...since you want to underclock, just use the stock kernel and set it to the lowest value with an app like set cpu...it shall do you fine...
Ryuinferno said:
So far I haven't seen a custom kernel for sga that works flawlessly...especially the ones with oc function...only stock kernels work with the least problems...since you want to underclock, just use the stock kernel and set it to the lowest value with an app like set cpu...it shall do you fine...
Click to expand...
Click to collapse
What are the other advntages with the CF Root kernel? I can't remmeber why I puted it, but I think they were another reason behind it...
Where I can get teh stock kernel? Or which one you advise?
Chill please...don't shoot questions in here...if you want quick answers, please search about it (e.g. go to the cf-root thread and read about the features, I don't memorise them, but I believe you want the overclock and a2sd features)...If you want direct answers, you will have to wait...
I understand that you need your phone for your business, it's very important to you...I'm trying my best to help out here ok? To get a stock kernel, just flash a stock firmware via ODIN...but you will have to re-root and re-flash cwm...any stock kernel will do, as long as it is with the firmware you flashed...
Ryuinferno said:
Chill please...don't shoot questions in here...if you want quick answers, please search about it (e.g. go to the cf-root thread and read about the features, I don't memorise them, but I believe you want the overclock and a2sd features)...If you want direct answers, you will have to wait...
I understand that you need your phone for your business, it's very important to you...I'm trying my best to help out here ok? To get a stock kernel, just flash a stock firmware via ODIN...but you will have to re-root and re-flash cwm...any stock kernel will do, as long as it is with the firmware you flashed...
Click to expand...
Click to collapse
Chill what? I'm not in a hurry for answers You answer when you can. I jsut reply when I can, if it was fast, I didn't noticed
I remember to put this kernel i did something from CWM reboot, your saying i need to reinstall a full ROM to get the stock kernel?:S And what's ODIN
Reply when u can, im in no hurry ;D
NunoPitbull said:
Chill what? I'm not in a hurry for answers You answer when you can. I jsut reply when I can, if it was fast, I didn't noticed
I remember to put this kernel i did something from CWM reboot, your saying i need to reinstall a full ROM to get the stock kernel?:S And what's ODIN
Reply when u can, im in no hurry ;D
Click to expand...
Click to collapse
Yea...a full stock samsung rom..you might wanna look at this
http://forum.xda-developers.com/showthread.php?p=12874680
Is your Samsung Galaxy Ace a GT-S5830 or a GT-S5830i ??
Sent from my GT-S5830i using xda app-developers app
If you want only professionals to answer your questions, take your phone to the Samsung Engineers....
Sent from my GT-S5830 using Tapatalk 2
NunoPitbull said:
Before you start reading, please make sure, you are 100% sure of ur answers, and that you have TIME to answer them ALL with clarification
Really thanks for ur time and help!
So i got a samsung galaxy ace, it's rooted and with b84 CF-Root kernel.
1) The thing is sometimes, I press Wi-Fi button or Bluetooth, and in the Wifi it says Error and on bluetooth just won't conect. I don't know what the problem is, and the only solution is to reboot the phone. Is this a problem? Can it be fixed? If It can, how? If not, please read point number 2.
Click to expand...
Click to collapse
Try flashing a new kernel, this is NOT a rom issue, just a kernel issue.