Hi.
I bought a Galaxy S2 phone in July and installed CM9 nightly (and now CM9 stable) on it.
Sometimes (5 times in August), when I take the phone from the table or from my pocket and try to switch the screen on, I find that the phone does not respond to the "power" button to bring the screen back on (just black screen). The phone is somewhat hot at this moment and I have to remove the battery to switch it on again.
When I switch it on again, the battery has reduced a lot (too much for the time passed since I left the phone over the table) just like if the phone was stuck in a battery-consuming process, not just "crashed".
This happens even if I'm connected to the charger (the battery goes down).
I'm using CM9 stable and thoravukk kernel ... any idea of what's wrong? Should I check a different kernel? Is a known CM9 problem and is not kernel related? Anyone else suffering the same problem?
Have you tried installing after full wipe?
NoP_Compiler said:
Hi.
I bought a Galaxy S2 phone in July and installed CM9 nightly (and now CM9 stable) on it.
Sometimes (5 times in August), when I take the phone from the table or from my pocket and try to switch the screen on, I find that the phone does not respond to the "power" button to bring the screen back on (just black screen). The phone is somewhat hot at this moment and I have to remove the battery to switch it on again.
When I switch it on again, the battery has reduced a lot (too much for the time passed since I left the phone over the table) just like if the phone was stuck in a battery-consuming process, not just "crashed".
This happens even if I'm connected to the charger (the battery goes down).
I'm using CM9 stable and thoravukk kernel ... any idea of what's wrong? Should I check a different kernel? Is a known CM9 problem and is not kernel related? Anyone else suffering the same problem?
Click to expand...
Click to collapse
u r experiencing SOD(sleep of death) thats ur phone is not coming back after deep sleep. reason might be due to kernel, try changing the kernel to stock cm9 or siyah kernel and see
oddlyshapedstickman said:
Have you tried installing after full wipe?
Click to expand...
Click to collapse
Hi.
I installed cm9-nightly-2012-07-28 after a full wipe (previously to this, I was using samsungs' stock 4.0.4), and I had this problem after the full-wipe install...
I passed from the nightly to the stable without the data wipe, and it's still happening...
I'm starting to think on make small tests. First of all, I was planning to replace thoravukk with siyah, to see if it's a kernel problem, or discard the kernel... but wanted to know if anybody is suffering the same problem.
(A friend of mine also suffers it with CM9 and the Galaxy S1...)
Thanks for answering.
Sun90 said:
u r experiencing SOD(sleep of death) thats ur phone is not coming back after deep sleep. reason might be due to kernel, try changing the kernel to stock cm9 or siyah kernel and see
Click to expand...
Click to collapse
Just a question ... if the phone is "deep sleep" ... why is so hot and why battery drains so much ? :-?
I'll test siyah...
Thanks
NoP_Compiler said:
Just a question ... if the phone is "deep sleep" ... why is so hot and why battery drains so much ? :-?
I'll test siyah...
Thanks
Click to expand...
Click to collapse
try siyah v4.1rc1 after installing the same go to recovery wipe cache/dalvik and do fix permissions and then allow a cpl o recharge cycle for the kernel to settle dwn and then see
NoP_Compiler said:
Hi.
I installed cm9-nightly-2012-07-28 after a full wipe (previously to this, I was using samsungs' stock 4.0.4), and I had this problem after the full-wipe install...
I passed from the nightly to the stable without the data wipe, and it's still happening...
I'm starting to think on make small tests. First of all, I was planning to replace thoravukk with siyah, to see if it's a kernel problem, or discard the kernel... but wanted to know if anybody is suffering the same problem.
(A friend of mine also suffers it with CM9 and the Galaxy S1...)
Thanks for answering.
Click to expand...
Click to collapse
Try a full wipe, wipe cache and delvik and reinstall stable, keep stock CM kernel.
Although you can flash from nightly to stable, its good to do data wipe beforehand since you aren't going to flash anything above stable.
oddlyshapedstickman said:
Try a full wipe, wipe cache and delvik and reinstall stable, keep stock CM kernel.
Although you can flash from nightly to stable, its good to do data wipe beforehand since you aren't going to flash anything above stable.
Click to expand...
Click to collapse
Hi.
I didn't wipe the data because it was just a couple of weeks between the nightly and the stable, very minor changes and seemt that wiping was not needed (and remember that I was having those "crashes" with the nightly, and I did a complete wipe to install it).
I installed thoravukk because the stock kernel does not have BLN support and I need it because SGS2 does not have a notification led and I miss text and whatsapp messages if I can't heard the audible notification ...
NoP_Compiler said:
Hi.
I didn't wipe the data because it was just a couple of weeks between the nightly and the stable, very minor changes and seemt that wiping was not needed (and remember that I was having those "crashes" with the nightly, and I did a complete wipe to install it).
I installed thoravukk because the stock kernel does not have BLN support and I need it because SGS2 does not have a notification led and I miss text and whatsapp messages if I can't heard the audible notification ...
Click to expand...
Click to collapse
Ahh OK, well you could Siyah as that has BLN.
So... You are not alone! I've got a I9100 with cm9 too. I've the described error too. Also over the nightlys over the past months it changed a bit to do it while in active use. Loss of 30% or something like at once!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I put the charger in while reboot. But this is no matter.
Also a friend of mine has the same problem with a stock SGS2 with the original 2.3.
Greetings
midnightflash said:
So... You are not alone! I've got a I9100 with cm9 too. I've the described error too. Also over the nightlys over the past months it changed a bit to do it while in active use. Loss of 30% or something like at once!
I put the charger in while reboot. But this is no matter.
Also a friend of mine has the same problem with a stock SGS2 with the original 2.3.
Greetings
Click to expand...
Click to collapse
The "suddently battery drop" problem is not only related to the Sleep of Death problem described by the OP. It appears in a lot of situations and in mostly all occations (probably including this one), it's just that the battery isn't callibrated anymore and you'd do a battery callibration to prevent those "suddent losses".
Calibrate your battery ! 3 charge et tout rentre dans l'ordre.
Envoyé depuis mon GT-I9100 avec Tapatalk
It's been more than a week since I intalled Siyah kernel 4.1rc1 and the problem has not appeared yet.
Let's cross the fingers and wait for a couple of weeks more and I'll confirm that the problem is with CM9-stock-kernel and thoravukk kernel.
Thanks!
I've tried with different versions of Siyah kernel (v4.1.5, v4.0.1) and still got SODs.. Reverted back to stock CM9 kernel and same..
I'm leaving wifi on with "Keep Wi-Fi on during sleep": Only when plugged in.
Strangely, I have found my phone SODed even when plugged in charger (that was only with siyah kernel if i remember right)..
Never suffered it again since I installed Siyah kernel...
--
Sent from my Samsung Galaxy S2 using Tapatalk 2.
black screen
I have the same problem with 7 different stock roms and kernels. can you help me ?
Related
I initially rooted and flashed my S2 using Litening, but moved over to VillianROM once it started looking like Litening was not going to get any further updates.
However, I kept getting odd force close issues using VillianROM, and Titanium Backup refused to work properly due to the ROM missing Busybox support.
I'm now using the Batista70 ROM, but 3G reception and battery usage have gotten worse compared to the other two ROMs. Even with full 3G reception available, the phone takes a ridiculous long time to load online content. That did not happen with Litening or VillainROM.
What other proven and popular ROMs would you all recommend I try?
jwai said:
I initially rooted and flashed my S2 using Litening, but moved over to VillianROM once it started looking like Litening was not going to get any further updates.
However, I kept getting odd force close issues using VillianROM, and Titanium Backup refused to work properly due to the ROM missing Busybox support.
I'm now using the Batista70 ROM, but 3G reception and battery usage have gotten worse compared to the other two ROMs. Even with full 3G reception available, the phone takes a ridiculous long time to load online content. That did not happen with Litening or VillainROM.
What other proven and popular ROMs would you all recommend I try?
Click to expand...
Click to collapse
Your problems sound user created, when installing any rom with different bases, always wipe everything and when restoring backups from Titanium, never restore system data, only apps and their data, Villain Rom is one of the most stable custom roms out here.
achillies400 said:
Your problems sound user created, when installing any rom with different bases, always wipe everything and when restoring backups from Titanium, never restore system data, only apps and their data, Villain Rom is one of the most stable custom roms out here.
Click to expand...
Click to collapse
I always wiped the phone before installing ROMs. I didn't use Titanium Backup with Litening, and never actually got the chance to use Titanium Backup on VillainROM, because it wouldn't work.
Have you thought about trying different kernels rather than different Roms?
Ospreylian said:
Have you thought about trying different kernels rather than different Roms?
Click to expand...
Click to collapse
+1 to this. Try some other kernels before switching ROMs.
I'm on Batista and it's quite solid.
try miui 1.10.28.
i was in the exact same situation that you are in.
i was on stock kg5 and when i wanted to try custom roms i waited for the first 2.3.5 custom rom. and villain rom came out first so i flashed it. but i found out that deodexed stock roms are not as smooth or as bug free as odexed ones (titanium backup didnt always work).
so i went back to stock odexed ki8 then moved to stock odexed ki4 with jkays mod.
all was good but i felt that there still are better roms out there. so i did a nandroid backup (you do itin cwm, and what it does is take a snapshot of your phones software so that when u restore it you go back to exactly how your phone was at the time u did it) then i tried cyanogennmod 7 and it was FAST! but i wanted to also try miui because i heard it was more user friendly but gives the same speed improvments that cm7 has. and i personally recommended that u try both cm7 and miui after doing a nandroid backup and a full titanium backup.
ps: sorry for the long post but i think you would find it useful.
pps; when u flash miui or cm7, dont restore app data in titanium backup or contacts or calendar data or any of that only restore non-system apps then restore the app data of each app individualy (only if you need the data)
ppps; to move your appointments and contacts sync them whith your google account. and then restore them after you flash
Before installing CM7 or MIUI install a ROM with old bootloader, KH3 for instance, or you will have problems...
Checkrom version 1 is awesome super smooth and great battery life you can choose what you want through the kitchen. Version 2 is a bit buggy but you won't have problems with the v1
Sent from my GT-I9100 using xda premium
Yeah, try the different kernel first.
Then, if you want another ROM to try, try CriskeloROM, click it in my sig, its an amazing ROM with a lot of customizations
MrPhilo said:
Guys you should try Siyahkernel 2.0 first before going to 2.1 (Final).
Simple & Clean v1.2 (Awesome battery tweak) - Siyahkernel 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have charged it abit like overall 5minutes but took it off straight away. But the result is great for long day users. I mean 15 hour and 30 minutes and I still have 75% left, you can see I left Wifi connected all day (while I was sleeping or I would have more battery). Also you can see I have abit of screen on time like 30 - 1 hour max along with 'Awake', that is music streaming along with youtube streaming (screen off but listening to youtube music) which is about 4 - 5 or 5 - 6 hour max.
Simple & Clean v1.2 battery is going to be more amazing for all heavy,average to light users!
Click to expand...
Click to collapse
I quoted this from my own ROM I customised, although Simple & Clean v1.2 isn't out yet (with the battery tweak), people are still getting amazing battery life out of it.
Battery + Perfomance, trust me !
jwai said:
However, I kept getting odd force close issues using VillianROM, and Titanium Backup refused to work properly due to the ROM missing Busybox support.
Click to expand...
Click to collapse
had the same issue
flash stock ROM root again then install custom ROM worked for me
Have you tried stock? Still the best IMO
jwai said:
I always wiped the phone before installing ROMs. I didn't use Titanium Backup with Litening, and never actually got the chance to use Titanium Backup on VillainROM, because it wouldn't work.
Click to expand...
Click to collapse
In this case, did you try installing Busybox from the market or try downloading busybox from within the Titanium Backup app, if you continue flashing ROMS willy nilly without first having a better grasp of what you are doing, you would either get lucky or continue having ROM issues, but I assure you, the problems thus far doesn't seem to be the ROMS.
And where did the information that deodexed ROMS are not as stable come from, I would like to read this info myself as I have used VR for months without any issue and many others can testify about using other deodexed custom ROMS
ODEX versus DEODEX
I'm the kind of person who flashes a new rom / update every three or so days.
So I can say I've tried close to every combination of ROM and Kernel abailable on the forums.
My favourite combination which I'm running at the moment is;
Androidmeda_Awesome_Arae_v1.3.2
combined with
SpeedMod K2-12
My battery never runs dry and never/close to recieve and FCs
Try Rom kitchen ki8 coupled with speedmod k2-13 kernel.
Best Rom I've tried, including the newer xwkj1 and cm7.
Sent from my GT-I9100 using xda premium
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Same here, even 3.2 ROMs flickering for me . The only one that doesn't flick is Task ROM
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Hey man, just got this sorted out
Try to follow this http://forum.xda-developers.com/showthread.php?t=1555984
Key part is that we need to unroot our tabs with North America stock. I think our "Non-NA" stock ROMs weren't really "unlocked" that's why custom kernel won't work well on them.
Super happy now with CM9 + latest pershoot kernel + latest CWM, smooth no flickering
Happy unrooting !
Make nand backup (if recovery flickers use rommanager)
Save it to PC
Wipe everything
Flash P7510UEKMP_P7510XABKMP_XAB.tar.md5 with odin
Reboot
Wipe everything again
Flash recovery.tar.md5 with odin
Reboot
Put this http://www.shabbypenguin.com/users/s0ckm0nk3y/android/acs/galaxytab10.1/Samsung_Galaxy_Tab_10.1_root.zip to storage
Put nand backup to storage
flash the zip
Reboot
Restore nand
Finisch! You can now flash another recovery and any other rom without flicker
In fact there is no way to get the flickering back^^
Files you can get here http://forum.xda-developers.com/showthread.php?t=1555984
ive had the same rolling screen during boot, but recovered with those instructions.
now i have another kind of problem:
roms flash ok, cwm is ok, boot is ok. but when i get to the desktop, if the device goes into standby, ot if i put it in standby withthe power button, when i wake it up, again a rolling screen, but much faster this time!
anyone had this problem before?
only happens on 3.2 custom roms. on the official one its ok, on cm9 from droidbasement its ok
any ideeas?
thanks
here it is a pic of what it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any ideeas?
thank you
nobody knows?
Hello all.
I have the exact same problem as tristan202 which is
Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all.
I am sorry but i think that solutions bringed by "hylde" is not related to this problem but to another problem, through very similar, in clockwork recovery tool : same flickering screen.
I used the link, 2 weeks ago to solve this problem, using 5.5.0.4 version.
But the original thread problem is still unsolved. I tried other ICS roms but with same problem. I'd also like to keep root access.
Thanks to all
cobrax2 said:
here it is a pic of what it looks like
any ideeas?
thank you
Click to expand...
Click to collapse
Well, I have almost the same problem. I am on overcome's rom, and I have a screen similar to yours. It is static, not rolling and it happens only once after reboot for two-three seconds before the lockscreen. After that it is ok, even when I lock the screen. Flashed again but nothing. I haven't found anything about that. Oh well. It may be weird but I can live with it. Has anyone encountered something like that before?
Sent from my amazing 10.1 galaxy tab
I posted this in Task 14 Thread!
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
bugs9477 said:
I had the same problem I fixed it like this!
Click to expand...
Click to collapse
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Galanthein said:
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Click to expand...
Click to collapse
So sorry it was ment to be in response to cobrax2's waking up from screen off!
bugs9477 said:
So sorry it was ment to be in response to cobrax2's waking up from screen off!
Click to expand...
Click to collapse
Ok that's what i thought. Too bad for us, we still have our problem
Thanks anyway !
bugs9477 said:
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
Click to expand...
Click to collapse
thanks for the reply, ill try this as soon as i find a bit of free time
Regarding tristan202 and mine problem (flickering boot screen which stops when we press two times the power button), i tried the nightly builds 19/05 and 22/05 of Cyanogen Mod without solution.
Tristan i'll try 2905 nightly build and keep you in touch
Trying to diagnose a problem with my Brother's phone. He got his Amaze about 8 months back, no issues whatsoever on the Stock ROM other than a backlighting issue on the bottom buttons that HTC is aware of.
Since installing ARHD Gingerbread, he gets random, and frequent phone shut downs when trying to wake it from lock/sleep statuts. The phone just shuts off and restarts by itself.
We were hoping that migrating to ARHD ICS this week would solve that issue, but it has not. It still shuts down randomly at wake.
Something on your phone is probably causing this, do a full wipe and reinstall.
I was actually experiencing this last night. Happened about 7 times while I was at work. After I cleared cache and dalvik-cache I fixed permissions. So far it hasn't happened again but waiting to see if it does. But maybe our issues maybe totally unrelated. I didn't pull a logcat to see if there was anything that maybe causing it. Next time it does I will.
Running ICS .3 Stock debloated, no scripts but with a theme. But its been on there since I flashed the newest ICS RUU so it can't be that.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Dark Nightmare said:
Something on your phone is probably causing this, do a full wipe and reinstall.
Click to expand...
Click to collapse
Except it has done this multiple times after using superwipe, with both ARHD Gingerbread and ARHD ICS.
Double0EK said:
I was actually experiencing this last night. Happened about 7 times while I was at work. After I cleared cache and dalvik-cache I fixed permissions. So far it hasn't happened again but waiting to see if it does. But maybe our issues maybe totally unrelated. I didn't pull a logcat to see if there was anything that maybe causing it. Next time it does I will.
Running ICS .3 Stock debloated, no scripts but with a theme. But its been on there since I flashed the newest ICS RUU so it can't be that.
Click to expand...
Click to collapse
I'll try this. For whatever reason the RUU on the ARHD page continually fails to update via ADB/Fastboot, I'll try again to see if it works now that ARHD ICS went on it successfully. Will try the Cache Clear and Permission Fix - definitely didn't do that after flashing this.
Weird update. In his bootloader it always said unlocked. I did the S-Off method advertised by JopountBear (sp), but now it seems it is locked? Odd.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Radio still won't install - says remote: not allowed.
Doing one more superwipe -> ROM -> Cache/Dalvik/Permissions Clear. Battery life very bad at the moment (But perhaps Battery Calibration is off?)
gotpriest said:
Except it has done this multiple times after using superwipe, with both ARHD Gingerbread and ARHD ICS.
I'll try this. For whatever reason the RUU on the ARHD page continually fails to update via ADB/Fastboot, I'll try again to see if it works now that ARHD ICS went on it successfully. Will try the Cache Clear and Permission Fix - definitely didn't do that after flashing this.
Click to expand...
Click to collapse
You didn't point this out in the beginning, if the bootloader is locked it won't allow flashing, re-unlock to flash whatever radio you're trying to flash.
Out of curiosity, why would a phone re-lock itself without me telling it to do so?
Dark Nightmare said:
You didn't point this out in the beginning, if the bootloader is locked it won't allow flashing, re-unlock to flash whatever radio you're trying to flash.
Click to expand...
Click to collapse
the bootloader needs to be locked for s-on, for s-off, it doesnt matter
gotpriest said:
Out of curiosity, why would a phone re-lock itself without me telling it to do so?
Click to expand...
Click to collapse
after you s-off'd, it went back to locked
On another note I use 4EXT Recovery. It has been the only recovery, for me, that actually wipes caches correctly and runs the Fix Permissions Correctly. You know that it does because it leaves a log on your sdcard. While any of the CWM that I've used doesn't.
And since you're s-off then don't worry about re-unlocking.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
after the shut down, when the phone comes back on, does your battery % drop significantly?
gotpriest said:
Trying to diagnose a problem with my Brother's phone. He got his Amaze about 8 months back, no issues whatsoever on the Stock ROM other than a backlighting issue on the bottom buttons that HTC is aware of.
Since installing ARHD Gingerbread, he gets random, and frequent phone shut downs when trying to wake it from lock/sleep statuts. The phone just shuts off and restarts by itself.
We were hoping that migrating to ARHD ICS this week would solve that issue, but it has not. It still shuts down randomly at wake.
Click to expand...
Click to collapse
i had same problem when i was on ginger bread and updating the sim to wifi calling enabled sim fixed this problem for me. but i am having this random reboot problem again since i updated to ics. i just do a battery pull if it shuts down by itself else it get stuck in a reboot loop.
Just out of curiosity...do you have fast boot checked on or off in Settings> Power ? Turn the check off and see if issue still happens. Just something to try.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Hello
I have investigated the problem for one week and found a solution for me
The Problem is the short distance of the Bluetooth audio transmission!
There are two settings file for the BCM4334 WIFI BLUETOOTH IC and it seems that it depends on the phone which is better.
For me it sadly was not the common used for CM10 nightly!
So i build two CWM files for you to test the differences.
Maybe we can find out on what it depend
I bought my S3 in Austria (the carrieris H3G) and for me bcm4334_semcosh works fine!
greetings
Patrick
Hi Patrick
So. I had i fine working BT audio streaming with cm 10. Then Changed to cm10.1. BT-connection was crap.
Flashed both of your files.
Aaaaaand: tataaa. the second one seems to work for me.
Thanx a lot!
so you are able to establish a audio-stream-connection longer than 1m?
This works for me! Used the second zip file listed (bcm4334_semcosh.zip) and it did the trick. Tried streaming some music from about 5m from the receiver, no problems at all! Thanks OP!
On CM10 I had excellend bluetooth audio streaming up to +/- 6 metre, on CM10.1 audio is (just) ok with max distance +/- 1 metre.
For who want to know, the Samsung bluetooth firmware files (bcm4334*) wrapped in the two packages in the first post are also in the CM 10.1 rom, see screenshot or browse to /system/bin/
Seems like the murata version is installed by default by CM 10.1.
I did a manual copy, rename and a reboot to try both files (e.g. to try the murata version, copy bcm4334_murata.hcd to bcm4334.hcd).
Both files give me the same performance I had already, sound is ok and max distance still +/- 1 metre.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you so much for your help. Finally I am able to use cm10.1 on my SGS3. Also for me the bcm4334_semcosh fixed the problem. I can leave my Phone in my pocket while driving.
New problem:
But now I have the problem that when i have had a call in the car I have no sound coming out the speaker when I get called or receive mail for example. The phone needs a reboot to get sound back. Cm10.1 b.t.w. Am I the only one?
pknoe3lh said:
Hello
I have investigated the problem for one week and found a solution for me
...
Patrick
Click to expand...
Click to collapse
Worked for me (semcosh), thanks so much!
Not working for me...
CM10.1 with Siyah kernel: I can't pair device. It actually asks for PIN, but no answer...
Any help, please?
gpvecchi said:
Not working for me...
CM10.1 with Siyah kernel: I can't pair device. It actually asks for PIN, but no answer...
Any help, please?
Click to expand...
Click to collapse
Try the stock CM10.1 kernel. I had the same problem, and not installing Siyah kernel fixed it for me.
Beardy
semcosh solve it for me audio Bluetooth works like a charm with Cyanogenmod 10.1. Thanks!
Hi there!
I'm on CM 10 on my SGS 3 too and have the problem of not being able to pair with my car's radio.
The two files didn't help, still can't pair.. it simply gets stuck at "Pairing.." in the Settings app.
I'm also using an austrian SGS3 (unlocked) with Siyah kernel and CM 10..
Any suggestions?
Greetings from another Patrik
fold93 said:
Hi there!
I'm on CM 10 on my SGS 3 too and have the problem of not being able to pair with my car's radio.
The two files didn't help, still can't pair.. it simply gets stuck at "Pairing.." in the Settings app.
I'm also using an austrian SGS3 (unlocked) with Siyah kernel and CM 10..
Any suggestions?
Greetings from another Patrik
Click to expand...
Click to collapse
Try stock cm kernel.
Click thanks if I've helped. Sent from my GT-I9300 using xda premium.
Thanks for reply!
Is there a way of getting it after flashing cm 10 or do i just have to reflash it?
Greetings
fold93 said:
Thanks for reply!
Is there a way of getting it after flashing cm 10 or do i just have to reflash it?
Greetings
Click to expand...
Click to collapse
Re-flash it without wiping worked for me.
Click thanks if I've helped. Sent from my GT-I9300 using xda premium.
No Cell Data
I'm using Galaxy S3 Verizon with cm-10.1-20130121-EXPERIMENTAL-d2vzw-M1
I flashed both of these files using ClockWork Mod. Neither helped my performance. I still have very poor Bluetooth A2DP audio and it will cut out after about a minute of playing.
The bigger issue I'm having is that I now get zero cell phone reception. I can't make calls, send texts, or use cell data. Wifi, GPS, and bluetooth all work. I had the phone in airplane mode when I flashed the first file, but I'm thinking that wouldn't have affected it.
Any ideas on how to get back to the original bcm4334 file?
Thanks
alongcor said:
I'm using Galaxy S3 Verizon with cm-10.1-20130121-EXPERIMENTAL-d2vzw-M1
I flashed both of these files using ClockWork Mod. Neither helped my performance. I still have very poor Bluetooth A2DP audio and it will cut out after about a minute of playing.
The bigger issue I'm having is that I now get zero cell phone reception. I can't make calls, send texts, or use cell data. Wifi, GPS, and bluetooth all work. I had the phone in airplane mode when I flashed the first file, but I'm thinking that wouldn't have affected it.
Any ideas on how to get back to the original bcm4334 file?
Thanks
Click to expand...
Click to collapse
just flash the custom rom again and the file will be overridden
pknoe3lh said:
just flash the custom rom again and the file will be overridden
Click to expand...
Click to collapse
Thanks for the reply. I actually did that and after the reboot I still don't have cell service. I even backed up all my apps and settings with Titanium. Wiped all user data and wiped cache, then flashed again. After doing the initial setup after the reboot, I still don't have cell service. I'm going to try to flash a different version of CM10.1, one of the nightly's and see if that helps any. I wish I would have done a full backup with CWM before flashing that bluetooth file
alongcor said:
Thanks for the reply. I actually did that and after the reboot I still don't have cell service. I even backed up all my apps and settings with Titanium. Wiped all user data and wiped cache, then flashed again. After doing the initial setup after the reboot, I still don't have cell service. I'm going to try to flash a different version of CM10.1, one of the nightly's and see if that helps any. I wish I would have done a full backup with CWM before flashing that bluetooth file
Click to expand...
Click to collapse
hm
yes a full wipe dont help
but if you flash CM again it is for sure overridden!
So your problem have another source.
I would guess you had flashed an other radio rom (CM dont come with Radio so new flashing has no effect on radio rom)
Also call problems are independent of the bluetooth hardware ...
I would recommend you to flash the orginal rom again and then rood again and then again flash CM but be careful as flashing is risky
greetings Patrick
Yeah I'm starting to think it was a just a coincidence that it stopped working when it did. From other threads I've found the best bet will be to indeed flash back to stock ROM and then back to CM. I'm downloading the stock ROM now found here:
http://forum.xda-developers.com/showthread.php?t=1762204
The only thing I did was flashed that semcosh.zip file using CWM though, so I'm not sure how that would have affected my radio.
Good thing it's a slow day in the office! Also, I think I'm just going to use wired headphones from now on!
---------- Post added at 03:31 PM ---------- Previous post was at 02:37 PM ----------
Just an update. I downloaded that root66.tar and flashed it with Odin. Did a full data wipe after (because it was stuck on the Verizon 4g splash screen). Still didn't have cell connection. Then did the step 2 on this page:
http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
Open the dialer and enter *2767*3855#
After it did some other sort of factory reset, I finally have cell connection again. And all before I leave work for the day.
Same issue here
Planet X said:
Thank you so much for youthe latest version available todayr help. Finally I am able to use cm10.1 on my SGS3. Also for me the bcm4334_semcosh fixed the problem. I can leave my Phone in my pocket while driving.
New problem:
But now I have the problem that when i have had a call in the car I have no sound coming out the speaker when I get called or receive mail for example. The phone needs a reboot to get sound back. Cm10.1 b.t.w. Am I the only one?
Click to expand...
Click to collapse
I have the same problem as you. When I disconnect from the car, all notification sounds are lost, BUT I've realized that you don't need to reboot. If you recieve a call to your phone (no email, sms or whatsapp, only a call will do the trick), it will actually ring and from then on, notifications go back to normal. It's not actually a fix, but until one comes out, it makes this issue a little less a pain in the ass.
Hope this helps. If anyone knows how to fix this for real then help is largely appreciated.
PS. My first custom ROM in S3 was CM10.1 nightly (the latest version available today) so I can't tell what happened before, but except for the mentioned issue and maybe a subtle loss in streaming quality, BT pairs and streams quite alright. Oh, and the media system in my car (Citröen C4) used to show artist and song name while streaming and doesn't anymore.
Hi, i've been experimenting this problem for 2 months. I've got CyanogenMod 9, but before I flashed Cyanogen Resurrection 4.0.3 and I formated everything as possible (Wipe Data, Cache, Dalvik and format /system). The battery doesn't lose charge when I restart it.
Thanks!
So, what is your question..?
Sent from the Matrix
If any of you have the same problem and know the solution. I've read other messages like mine, but I'm not in the same circumstances. I haven't got any apps except social (whatsapp, twitter...) none of my apps it's draining the battery I simply don't know why my phone shuts down by itself
You're running stock kernel right? Have you changed anything at the Performance-menu at Settings? And when do this reboots occur?
Have you tried flashing for example CM10.1 to see if the same problems come up? You could make a Nandroid backup to try this.
Sent from the Matrix
Thanks for the answers. I have the stock cm9 kernel. I don't touch anything at the performance settings. Actually, this problem comes from a couple of roms more. AOKP, ParanoidAndroid, and another one 4.2.1 which I don't remember the name. I've tried a stock ROM before but the performance was not good at all, freezes and slow work at general. Thanks.
Make a full wipe (4) and go as stock as you can. Try it for a day or two and then go back to custom.
You wanna see if it keeps going off on its own, don't worry about performance just yet.
If it does it on all roms you've tried its obviously a hardware issue.
Try a different battery, if that doesnt help then send it for repair.
SGS2 power off issue
Hiya,
I have been running and updating Resurrection Remix and Siyah/Dorimanx kernels for awhile now and this worked fine up until last week. After an update to Dorimanx 7.50 my phone started dropping its network connectivity and powering off randomly, i then updated the Kernel to a new verison hoping the issue had been address (8.3 to be specific) after which my phone wouldnt even go through the boot sequence properly.
After a bit of fiddling i have managed to install an Official JB ROM, (details in the image attached) and network connectivity now seems to be ok, but the phone still powers off...ALOT. Anyone else experience similar issues and find a solution?
Note: I have ordered a new battery in case that is the issue as suggested above, but just checking incase theres something im missing while I wait. Also, the phone is about 16 months old.
Sv: [Q] SGS2 turns itself off
Check your fuel gauge chip. Reset it with siyah or dorimanx kernel.
Skickat från min GT-I9100 via Tapatalk 2