Related
Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
This obviously seems to be the wrong board I am posting that supposedly simple question in -- could somebody please point me in the right direction and I will ask again in a more appropriate board.
I'd say the board is the right one ... but at least I can't help you here, as I don't know the answer .
My only advice would be to flash a newer ROM, isn't inParis kinda "outdated"? I think android.media has something to do with connecting USB devices to the tab, since it's the thing that crashes on ICS KANGs when you plug out your USB stick ... but that's all I can help you with (if it's any help)
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
Freeze the app with Titanium Backup or use this specific purpose app from the market
https://market.android.com/details?id=com.addz.mediascannerroot
Worked for me
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
search pershoot's thread... Or check his website... it's there...
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
Honestly, I was going to say that you'll spend less time doing the ICS update than looking for this; especially on that ROM (great ROM.... 6 months ago...). I'd suggest go with the last milestone from Romann.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
I would check your media files... delete them or put .nomedia file in all those places.
Next thing to try is to clean dalvik cache.
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
mrmagmrmag said:
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
Click to expand...
Click to collapse
I can understand if you'd just rather wait because of having to bother with reinstalling every thing, but it looks like you can change ROMs quickly. So why not goto Task14 while you wait for ICS?
There might be device issue I'm not aware of also, so just wondering.
If you can read this, thank the person that taught you how.
I have a problem with occasional hot reboots of my device.
Description of the device: international galaxy s3, omega Rom (from the day of purchase, now it's 33.3), siyah kernel (also from the very beginning, now it's 1.8), extsd2intsd mod. No OC or UV is required to replicate the problem.
Typical situation when it happens: I read news in flipboard, use touch translator to translate selected word, goldendic opens.I try to edit the word in the search bar of the dictionary (by pressing backspace), and at this moment device hot-reboots itself. Hot reboot also happened in other programs (one time I was also editing search bar when it happened, another time I tried to copy a text fragment).
I thought that Swype keyboard might be the cause. So I froze it in Titanium backup. However, reboot happened with Samsung keyboard.
It's important to mention that sometimes I can replicate the reboot (playing with flipboard and dictionary), but often device works perfectly despite my attempts to cause hot reboot.
Finally, the most important part: hot reboots do not happen when I have either V6 Supercharger or Bestmultitaskingfix working. That's why I think that it's a software problem. However, supercharger causes TW redrawals plus bad multitasking (at least the version which comes with omega Rom), and Bestmultitaskingfix causes lags on my device, so I don't find them to be a decent solution.
I tried to overload ram with opened apps, but nothing happened, old apps simply closed.
So, I think that the solution could be a bootable tweak which is used in both V6 Supercharger and BestMultitaskingFix. However, I'm not aware of the structure and tweaks used in these scripts. May be someone with experience in this area could suggest something?
I would like to hear your suggestions about the problem. Any ideas will be greatly appreciated!
Update: vibration is not the cause. Device rebooted even with tactile feedback turned off.
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
xSpeced said:
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
Click to expand...
Click to collapse
Flashed the stock firmware (ICS - I had nandroid backup), did full wipe. So far, no reboots were observed (intentionally played with flipboard and golden dictionary). Seems that it's a software problem. Still, I need to fix my omega rom somehow...
A clean flash for Omega might be a good idea.
Frequent random boots can be the beginning of "sudden death"... look for this thread in General section....
Just a noob sharing some thoughts, hope it can help some other noobs like me.
A no wipe in my book:
Here is how i do a no wipe.
In recovery, mount and storage and choose format system.
Go back and wipe Cache and Dalvik
Install / flash the rom.
A full wipe in my book:
Into recovery, mount and storage and format system, data and cache.
Go back, wipe/ reset data, cache and dalvik.
Install/flash rom
Format of the internal SD:
Here is what i do:
Make a app backup with TB to my external sd
Make a nandroid to my external sd
Make sure i also have a efs backup on my external sd
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Then i reboot to recovery.
Mount and storage and format internal sd.
And to be save and have it nice a clean, also format system, data and cache and because i am not only a flashohalic but also a cleanohalic, i then wipe/reset factory reset, cache and dalvik.
Probably a big overkill, but he, done it several times it works for my and it only cause a few seconds.
Then i reboot, skip the setup/registration, move my download map back to my internal sd (don't like flashing from external sd).
Back in cwm, again a full wipe which includes the formats data, system and cache.
Then flash the rom and setting it up.
This way, you have a nice clean fresh S3, but and this is a big BUT.
Backup, backup backup and don't forget a efs backup to your external sd and pc.
Don't think lightly about those backups, when imei is broken and you don't have a backup, your a done, only thing left is a visit to Samsung.
Good luck when you are going for it.
And i know, Aroma installer is also doing some automatic wiping, but i am just a bit old fashion and like to do some stuff manually.
Bootloader.
As you all know, the new bootloader can be a pain in the ass.
But, i am still not sure that Samsung only released the new bootloader just to discourages us to flash custom stuff.
So, if you like flashing stuff and you are on the new bootloader like me, just remember when you entered recovery and you are done flashing stuff, use Triangle Away from Chainfire,
But, for some, like on my wifes phone, the latest version works without problem, but on my S3, i need to use the older version, 2.37, why, don't have a glue.
Not all S3 are the same, although have the same name and using the same chipsets.
But you can also use the old bootloaders, with does, you just have to run Triangle Away just once, when entering recovery, it will not count.
Your own choose.
About Sudden Death.
A lot of threads are open for this.
My 5 cents:
I have the "sudden Death" chips VTU00M chip with 0xf1 on both our phones.
Mine is running since 27 may 2012 without problems, still fast and smooth.
The other is up and running since 31 Augustus 2012 and also still fast and smooth.
Both have been rooted from day one, the only thing i do, is turning the devices off completely for a few minutes 4 to 5 times a week.
Old habit to clear memory, anyway, gives me time to do a good cleaning of my screen.
Here is the code to check your revision and to see from which day you are running your S3 *#12580*369#
Further more, AndreiLux found i string in the ELLA kernels released by Samsung that looks like that it solves the sudden death issue.
So, if indeed if fixes this issue, then off course the latest kernels releases from Sammy has also the fix and not just the custom kernels.
As far as i know, all the custom kernels has the fixes integrated this string by now, but i myself like the stock kernels, Indie puts in the Omega Roms.
Phil3759 has also made a repack of recovery based on CWM touch 6.0.2.7 to get it all safe.
More to come in the future, because i am learning everyday here on XDA and like to share and help others.
Edit, here is quote from AndreiLux about the new bootloader:
http://forum.xda-developers.com/showpost.php?p=37163086&postcount=1298
Do I need any particular Bootloader? No - There is no evidence to suggest this fixes anything
Apparently that's wrong, download mode on the device uses a microkernel from inside the bootloader instead of the full blown Linux kernel. When flashing something via Odin in download mode you'd be using the bootloader's MMC driver and thus be at risk.
All-day users are still safe via recovery and live kernel, but are not advised to flash things in download mode with an older bootloader. This also explains why they updated the bootloader in LLA. The security checks are a mere update to bring it up with what the 9305 and Note 2 users already have in terms of not able to get rid of the exclamation mark.
Personal note:
Maybe i am seeing this wrong, to much thinking in terms of home computers, but here is some thoughts regarding above.
From cold, turned off device,.
Turning the device on, micro kernel inside the bootloader kicks in to send information how to start the device correctly.
If it works this way and you are on the old bootloader, then every time you start the device with the old bootloader, you are at risk?
Some useful links:
My struggle with TA
Omega roms S3
Chris_84 Faq
Triangle Away
http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/
Old bootloader
Philz recovery
https://www.google.nl/search?q=andr...s=org.mozilla:en-US:official&client=firefox-a
https://play.google.com/store/apps/details?id=com.electricsheep.asi&hl=nl
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Here i will post stuff that comes along the road like question about batterystats at recovery.
We used to have a option to wipe the battery stats at recovery, also there are some tools at Play store that claims to give a better battery life by just wiping those stats.
But after reading this excellent article, it comes clear that wiping those stats are bull.
So i am glad that option isn't available anymore and perhaps in time, the questions about those stats will faint away in oblivion
And another one i like to share.
Fast Dormancy.
Here is a great article about it, made by Erica.
For me, my provider is saying it's not supporting FD, but when use the method to check, it is supported.
So i tested it for a few days on and off and found that when it's off, i do get some better battery life, but it's just minor.
Instead of losing 5% battery at 8 hours standby, i lost 6%.
Also, i didn't see any benefits in speeds, so i turn it off every time after a flash of a new rom using gokhanmoral tool.
Another thing i like to add.
Wifi.
I have seen many posts about wifi problems.
Here what always works for me.
Sometimes just a reboot of the router will help.
Also, i find changing from dynamic (default) to static that my connection is faster connecting to my router (always use the never setting at wifi advanced to save battery).
Here is how to do it the easy way.
First set it up using it with the default dynamic settings, this way all will be filled in for you.
To change it to static.
Long press your connection and choose modify network config and check show advanced options.
Scroll down a bit and tap on IP settings and choose Static.
And that is all, now you have changed it to static and there is no more need for ip adress to negotiation any more.
https://www.google.nl/search?q=wifi...s=org.mozilla:en-US:official&client=firefox-a
Also if still having problems, adding some more permissions can solve it.
I use root explorer for this
ETC > Long press wifi folder and choose permissions (remember to change Mount R/W to Mount R/O) and check all nine boxes.
Hit back and go to Data > Misc and again long press wifi folder and again, check all nine boxes.
Space
I know, i am a control freak and i hate it when i see space just vanish.
So did some search and found a thumbnail map with more then 1gb size.
Looked at some submaps and i only saw some old stuff.
So, selected all the submaps and just deleted it without problems and gain more then a gb free space.
Here is where you can find it using root explorer:
storage > sdcard0 > .thumbnails.
Edit:
As bigmo7 pointed out, the thumbnails will be rebuild, but off course not off stuff that isn't present on the S3 anymore.
So, if you are someone that is just making pictures or making / creating movies and never delete then from your S3, there is no point off deleting the thumbnails.
But if you like me, moving, creating copying and deleting this kind off stuff, then you can gain space.
Battery life
Always a hot item.
First all, the S3 is a mini computer and computers need juice, just remember this.
Here are some stuff i always do after flashing a new rom.
If the rom comes with a aroma installer which let you select stuff to install or not install, look careful to the list.
Stuff you don't use, can just eat resources and i myself, just find it a waste.
Next, after flashing and setting up the new rom, you will be presented with the option to use wifi.
I always go to advanced when making a wifi connection to choose Never when phone is in standby.
For me, but this can be different for you, wifi is a bit off a drainer so do some testing, let it run overnight with Always selected and another night with Never and see the difference.
Next you will be present if you want to restore and let google backup your phone.
I always deselect backup my phone, first reason, i am a control freak and i decide when and what i want to backup.
And second it can give you wakelocks and this will cost you battery life.
Next step i do is going into settings and to sounds, i don't like the clicking sounds and i deselect all the system sounds.
Next, location services and deselect GPS and Location and Google search.
I want GPS active only when i need it, some apps like Facebook will activate GPS when running and i don't like this.
And i don't want Google to know where i am all the time.
Some weather apps needs Location and Google search to determine your location, but i use Weather pro and it don't need it.
Next step is going into accounts and look what you have selected for syncing.
I always deselect Google photos, Internet and Picasa web albums.
Stuff i don't need .
Location settings at accounts is also off.
Next step is using the Fast Dormancy toggle to disable Fast Dormancy, although my provider is supporting it, enabled costs me a little more juice. Although it's minor, but a lot off minors things makes it bigger .
Then starting Playstore and at settings, deselect Notifications.
And finally freeze stuff i don't use with Titanium Backup pro.
http://forum.xda-developers.com/showpost.php?p=31576747&postcount=105
All this, is giving me a great battery life, with screen on time between 4 1/2 to 6 1/2 hours, depends what i am doing.
And with the latest JB roms, 1 to 2% battery los in 7 hours standby.
No need for me to toggle Airplane mode, mobiledata or some other powersaving setting or app.
I am also always running the stock insecure kernel that comes with the rom, for me no need for a custom one.
Reserved
KeesStolk said:
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Click to expand...
Click to collapse
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
thorcyar said:
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
Click to expand...
Click to collapse
I never save mods because most of the time when flashing a new rom, it's based on a new build and not every time mods are compatible, just like some themes by the way.
I just safe the mod files and thems, when i am sure they are compatible, i just flash them again.
Indie's Omega roms has already a lot of mods in it by default by the way, but i don't think he was for a 9305.
Good work Kees! Now I'm learning from you.
Chris_84 said:
Good work Kees! Now I'm learning from you.
Click to expand...
Click to collapse
Thank you for your kind words, but it is l who is learning from you every day .
Sent from my GT-I9300 using Tapatalk 2
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
vegeta1 said:
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
Click to expand...
Click to collapse
Thank you very much, but from you, Chris, Indie and the rest of the omega team are the ones I learn all this great stuff every day.
Sent from my GT-I9300 using Tapatalk 2
i always feel like a noob when ever i read here
big big thanks my friend for pointing out all this so nicely
Very nice posts KeesStolk. Maybe you should write a manual for us?
I'm about to post this in Q&A (searching for an answer brought me here )
I just (3 days ago) upgraded my Omega ROM to v40. All seemed fine - I did as normal but in v35, my last Omega there wasn't a Full Wipe option. I chose not to wipe and everything went as per usual with Omega. I reinstalled my extras (6 x 5 icons, Loud phone hack, Increasing ring phone, Note2 Keybd) and was back to normal.
Except, now my apps will not update.
I found out the hard way. I had a problem with Play Store - open it and it would flash briefly then close. Tried all I knew of but nothing worked so, logic said, Omega v40 is different enough I need a wipe and that why they put it in there as a choice this time. (I checked the Omega thread and couldn't see anything relevant but I was in the pub at the time and may not have been as thorough as I should have been)
I had a TB backup and Nandroid on my ExtSD from 2 days back and an EFS so I ran the install again and chose Full Wipe - again everything went well... until I tried to download TB so I could restore all my apps and data. Play Store opened and stayed Open (yaaaay!) and TB acts like it is downloading but nothing comes through - it just sits until it times out on an error.
I tried several apps and none would DL but then AuWeather DL'd just fine. I went back to TB - no go.
After much frustration I Restored my Nandroid and got back to where I was (Omega v35) but still I can't DL and update for TB. At least Play Store stays open though. I tried running the v40 update again, installing the Default, just in case, (& I have just finished DL'ing v41) but the DL/Update problem persists.
I'm now on:
AP – I9300XXEMA2
CP – I9300BUELK1
CSC – I9300LBEMA1
RF cal – 2012.6.28
HW Rev – MP 1.100
Any ideas? If I can't DL TB once I have flashed, I can't get my data back so a wipe isn't really an option until I fix the DL issues.
As I said, this will also be in Q&A but you seem to have a good grasp on the basics so I thought maybe...? :fingers-crossed:
So... I tried restoring back to v35 and got the same problem. And yet that version has been running since v35 came out, at least a couple of months. So I did it again but this time used the Android Revolution Wipe zip, then a straight install of v35. I could then load TB from Play Store and restore my apps and data. Phone seems back to normal now although I have lost some logs data from the couple of days between my backup and now - no biggie... I also now can update my apps.
So it seems it is something to do with Omega v40.
I've just DL'd v41 so will give that a try. Any help with what might have gone wrong would be much appreciated.
Thank you for your kind words, just sharing what i know and hoping this info can help others.
And how is it with v41?
Did you tried it with wifi and 3g, any difference?
Also tried removing your google account, reboot and setting it up again?
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
xanthrax said:
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
KeesStolk said:
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
Click to expand...
Click to collapse
absolutely !!!
everyone`s choice ! but people must follow proper threads , i`ve got nothing against a certain rom but against disarray when users post or open endless threads about same thing .
some users hates me for this , i know it well , in my thread i always pointed out but somehow is unfair to maintain same topic on more threads .
that`s a bad habit for new users and not only for the rule`s sake but this is the way should be in a human community .
-=-=-
i was thinking as well to open a thread as yours but due to lack of time i didn`t. as soon as i`ll find interesting things i`ll let you know .
i myself am a NOOB !
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
... and i must agree with you this time ...
Thanks guys.
@xanthrax, i know the feeling, kind off busy family
But i like your comments, just straight forward, the way i like it.
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
I think it should stay here as it "Helps" other users. General is more for discussions IMO.
But how about these?
http://forum.xda-developers.com/showthread.php?t=1749214
http://forum.xda-developers.com/showthread.php?t=1827635
http://forum.xda-developers.com/showthread.php?t=1732722
http://forum.xda-developers.com/showthread.php?t=1895737
http://forum.xda-developers.com/showthread.php?t=1946481
http://forum.xda-developers.com/showthread.php?t=2041679
and that's just the first page. all of the above are for "help"
Hey,
Ive had an S2 for a little while now. I have rooted and flashed several different roms and tried everything from changing settings to flashing stock firmware and wiping the handset to try and get rid of this problem..
Currently on:
4.1.2 JZO54K.I9100XWLSD
siyah-s2-v6.0b4+
BetterBatteryStats shows:
0% Deep Sleep
~40% suspend_backoff
~20% l2_hsic
~20% sec-battery-monitor
(and some other tiny, irrelevant wakelocks)
I have been trying to go through dmesg but I have no idea how to read it properly and I havn't been able to find much info on the subject.
I would be grateful if someone could have a quick look to see if they can identify a problem.
DMESG: attached
..from what I can tell, my cpu1 is constantly turning off and on.
Any ideas anyone? :crying:
1st way, pull out the battery and wait for 1 min, Then put it back. If it does not work, try the second method.
Wipe everything, data, cache, format system and flash a stock-like rom like Omega v23. I suggest you to backup everything on your phone and format your external and internal sd's with recovery. Your faulty musics can even cause media server to work all the time.
jsw666 said:
Any ideas anyone? :crying:
Click to expand...
Click to collapse
Have you tried changing your kernel? I'm running Rootbox and Dorimanx and dont have those issues. Have you tried that setup?
Dampierre said:
1st way, pull out the battery and wait for 1 min, Then put it back. If it does not work, try the second method.
Wipe everything, data, cache, format system and flash a stock-like rom like Omega v23. I suggest you to backup everything on your phone and format your external and internal sd's with recovery. Your faulty musics can even cause media server to work all the time.
Click to expand...
Click to collapse
Just recently I have tried wiping everything and flashed the official stock rom for my network from samfirmware, would Omega v23 make any difference?
I removed the external sd card..
I have tried formatting internal sd card in recovery, getting mounting errors followed by "skipping format", also tried formatting in plain old settings->storage, which doesn't seem to remove any data.
* I have manually deleted everything from internal sdcard.
kilometers4 said:
Have you tried changing your kernel? I'm running Rootbox and Dorimanx and dont have those issues. Have you tried that setup?
Click to expand...
Click to collapse
I have tried various roms/kernels, stock and custom, so I don't believe thats the problem.
I think your problem is about hardware, but how can you explain this to the warratry.
--Hi, my phone does not go to deep sleep.
--Sammy-- What??
I hope, if you have warranty, you will be able to explain your problem.
Dampierre said:
I think your problem is about hardware, but how can you explain this to the warratry.
--Hi, my phone does not go to deep sleep.
--Sammy-- What??
I hope, if you have warranty, you will be able to explain your problem.
Click to expand...
Click to collapse
Haha.. They would give me sleeping pills.
I'm beginning to think this is a hardware problem, but the handset functions perfectly except the no sleep (resulting in poor battery life).
I do not have a warranty on this one so i'm hoping that if it is a hardware problem I can achieve some kind of work-around.
jsw666 said:
Haha.. They would give me sleeping pills.
I'm beginning to think this is a hardware problem, but the handset functions perfectly except the no sleep (resulting in poor battery life).
I do not have a warranty on this one so i'm hoping that if it is a hardware problem I can achieve some kind of work-around.
Click to expand...
Click to collapse
Have you tried a full wipe and not install anything but cpu spy to see if the device sleeps without any apps installed?
kilometers4 said:
Have you tried a full wipe and not install anything but cpu spy to see if the device sleeps without any apps installed?
Click to expand...
Click to collapse
I have, but with BetterBatteryStats, not CPU Spy.
Any fresh ideas?
Does anyone notice anything in the dmesg?
Someone HEEEELP
jsw666 said:
Someone HEEEELP
Click to expand...
Click to collapse
Please attach the full text log of BBS, it could help .
Can't be hardware, it must be a kernel thing.
I guess you tried em all already, so, as it is weird, you can easily contact samsung and ask them if it could blow off at any time soon
With the s4 coming out they won't like S2 blowing up in people's pockets all of a sudden.
Sent from the little guy
fxrb said:
Please attach the full text log of BBS, it could help .
Click to expand...
Click to collapse
Attached bbs log.
jsw666 said:
Attached bbs log.
Click to expand...
Click to collapse
Kernel wakelock suspend_backoff: could be from apps and/or services running in the background, like FB etc. Try using TB to freeze apps (and services!) and see if things are getting better.
Kernel wakelock sec-battery-monitor: do you use a battery monitoring app? I sometimes use Battery Monitor Widget to monitor the battery. This app can run as service in the background when closed, hence I have to disable background logging before I close the app. If I miss to disable it I will have those sec-battery-monitor wakelocks too.