I have this serious problem. The alarm doesn't sound in the morning( more than 6 hours) However if I set it for 2 hours it triggers! I currently have tony's latest cm10.1 with kelnel 126. You must know that I have tried all most recent cm10 with various kernels. Then I switched to official cm10.1( old boot). Then I tried cm10.1 tony old boot then new boot with no results. Between changes I formatted system, cache etc. Do you have this issue? It's the settings to blame? I'll be reading this post all day.
Yeah, its normal, a lot of O2X users have come late to work/school because of our phone's alarm hehe.
Anyway, charger must be plugged for alarm to be triggered.
If charger isn't plugged, the phone won't wake from deep sleep.
Even on stock ICS alarm won't hit unless you have stock LG kernel installed. That's all I know I'm afraid.
Custom40 said:
Yeah, its normal, a lot of O2X users have come late to work/school because of our phone's alarm hehe.
Anyway, charger must be plugged for alarm to be triggered.
If charger isn't plugged, the phone won't wake from deep sleep.
Even on stock ICS alarm won't hit unless you have stock LG kernel installed. That's all I know I'm afraid.
Click to expand...
Click to collapse
Every rom?! I remember cm10 roms in january or february had no such problems. (Why did I upgrade...) Can you all tell me what rom kernel combo ( cm10 or 10.1) has a working alarm? It's frustrating to have an expensive phone without the second most importatnt feature disabled.
when u need alarm disable second core plug
danut21 said:
expensive
Click to expand...
Click to collapse
expensive? maybe 2 years ago... now it's a bargain...
g3ar said:
when u need alarm disable second core plug
Click to expand...
Click to collapse
It' s off. So is the dinamic fsync and single core mode. What rom do you use? If it works for you
i use v30b germany baseband, and tonyp exp opt build ( lastone ) ,when i want to charge phone ( without bsod) i enable second core plug, when i want alarm to work i disable second core plug ( it will be fixed in next release of pegasus kernel
I flashed latest stable kernel m1 and still no alarm This morning when I unlocked, the alarm just disappeared from the notification bar. Previously it rang at least... What works for you? Please tell me. I don't wanna keep the phone charged all night. Is it related to baseband?
danut21 said:
I flashed latest stable kernel m1 and still no alarm This morning when I unlocked, the alarm just disappeared from the notification bar. Previously it rang at least... What works for you? Please tell me. I don't wanna keep the phone charged all night. Is it related to baseband?
Click to expand...
Click to collapse
Some users have solved this problem installing timely alarm clock from playstore, it's free. Try with it
sev3n1985 said:
Some users have solved this problem installing timely alarm clock from playstore, it's free. Try with it
Click to expand...
Click to collapse
I did. Still no alarm this morning. It rang when I unlocked it. I think goes into a deeper sleep than usual. I will try to format card and install a new rom.
should we freeze (or even uninstall) the clock & clock alarms apps if we use Timely? anyone tried that?
i'm not sure if those 2 apps are connected with anything else in the system besides stock clock/alarms...
Are there no alarm issues using timely?
I had moved from official ICS to Tony's CM 10.2 without re-partition, and alarm worked. Then I bricked my device and reformatted everything using AIOT. Now no alarm. I wonder if there is any connection.
Also, how about one of the experts here comparing logs from devices with working alarm and non working alarm.
so far, no issue with Timely here...
i have disabled the stock clock-alarms app with Titanium... (don't disable clock.apk because it will mess up the lockscreen clock )
Related
Ok firstly I'd like to say I just rooted my phone last week, this was my first time doing it. I decided to do it to get rid of various problems (I was led to believe rooting fixes everything). Some of them went away, some of them stayed, and new ones came up with the rooting.
I was coming a stock LG Optimus 2X P990 with Android 2.3.4 (had been updated because the phone was originally older 2.2.2 I think.. I'm not sure), and rooted to Nova HD Rom (ICS 4.0.4) using this thread : http://forum.xda-developers.com/show....php?t=1508492. Oh also, I'm using SPB Shell launcher.
Problem #1 : Signal interuption. This one is probably the worst problem I have. I rely on my phone a lot as I don't have a ground line I need it to catch all my calls. About 2-3times a day I'll check my phone and I'll have no network. Sometimes the signal bars are frozen, they don't flutuate as I move to different areas. Sometimes there's an X on the signal logo. Either way, where I go inside/outside.. my phone can't get network. At first I tried to activate/de-activate 2G, turning on/off airplane mode to somehow reset the damn thing, but it just won't pickup. Then I tried a reboot, after the reboot.. still stuck at no signal. Then I finnally found how to fix it.. a full power OFF, and back ON. That's right each time I peak at my phone and it seems to be doing this, I need to make a complete shut down to wake his ass off.
Problem #2 : Battery drain. Well after days of reading on the subject apparently rooting my G2X was gonna improve it's battery life. Result is : no difference. I've bought a bunch of apps to try and keep track on what's wrong (BetterBatteryStats, Battery Monitor Pro). Just this morning I unplug my fully charged phone at 7:00:AM, and by 1PM (6hours later) it was done. There was about 1½hours of awake time, and about 50mins of screen on (perhaps half of this was using my 3G internet with various apps), no SMS or Calls. Usually if the phone is kept sleeping it can last about 24hours, do you guys think this is normal battery drain?
Problem #3 : Phone Clock off? Last week I was woken up by my alarm in the morning to find out I was about 40minutes late. Only happened once so far. I checked to see if I had set my alarm incorrectly.. nope, then I saw my phone time.. It was was OFF by 40mins... WTF? I went in the options and everything was fine... "Automatic date & Time" checked. I unchecked/checked it, and it didn't fix it, I had to reboot the phone for the time to come back to normal. Now hopefully that was only a one time problem, only now I have to live with the stress every morning my phones time might be wrong and I'll be late for work.
Problem #4 : Seriously where the hell is my FM radio. I use to listen a lot of FM radio before I rooted my phone , this is a feature I enjoyed. After rooting the FM radio application was gone, I said what the hell I'll just get another app from google play. NOPE, not a single FM radio app (that works). I tried a bunch of stuff, read on the forums and searched google for like 3hours and couldn't believe how much work I had put into such a simple thing.. this is so infuriating. The next day I kept looking but was never able to get anything working.. Oh and every where I look people say "lol why use FM radio when you can stream 1gazillion radio with given apps or whatnot". DAMMMMMMNN CAUSE MAYBE I DON'T HAVE INFINITE DATA PLAN? (In fact I have only 500megs/month). Seriously I'm so mad about this.
Problem #5 : Can't copy MKV files?! . I swear to got now that I rooted my phone each time I try to do something, something ****S UP. I just wanted to plug in my phone and copy some episodes of a serie I watch. Each time I tried copying the files : BAM "Windows Explorer has stopped working". So after another 2hours or so of trials and errors I figured the damn thing out . If I try to copy anything, it works. If I try to copy a *.MKV file, explorer crash. A solution I found is renaming my files to *.****YOU and then copy it and rename it back to MKV after it's done copying. Then I wondered, what if I rename a txt file to mkv, will it crash when being copied? Nope won't crash. So it's not just the extension? But why does it work if I remove the mkv extension.. oh good god how the hell am I supposed to understand anything.
Problem #6 : Can't play that MKV file?. Hey I finnally copied my file, the next day at work during my break I open my phone to watch it and.... well I realised there wasn't any video player included in my ROM, so luckly this time I found apps on the market that could play it. I used MX Player. Oh alright time to watch it? NOPE The video is all laggy and skipping frames like hell. Also audio is off and about each 10sec it mutes as if it was re-syncing the sound. Later the next evening I wasted another couple hours figuring this one out. What comes out often : they say use Dice Player instend! LOL Funny! The damn app won't even open my file!.
Playing with my phone I opened an APP I've pushased : System tuner pro. Looking at the CPU stats I noticed the first CPU was at 1.01Ghz, and the second one was at 216mhz? What the hell? I thought isn't that suposed to be 2x1ghz dual core?. So I cranked up the thing up to 1.01Ghz just like the other CPU, opened MX Player and already my video was almost watchable (a definitive improvement). I went back in System tuner pro, and overclocked the damn thing (even tough I had no idea if it was safe to do so) to 1.4ghz on both cores. Another significant improvement, this time when set this way I could watch my video! And the app onlyl reports a 5Celcius increase so I guess it's fine.
My only problem/question about that is why does each time I reboot my phone does the damn thing turns back to 216mhz? In fact why was it set to 216mhz in the first place? Considering all the problems I have and that I reboot my phone about 10times a day, I can't just go in system tuner the re-set my CPU settings each time?
Hopefully you guys can help me.. I'm exhausted I''ve been searching this forum and the web for the last couple days, I have like 1000tabs open in chrome. Btw this forum is a goldmine for information but damn it's a lot of reading.
Thanks in advance for your help
First, I'd like to say that I admire your keenness to detail in writing all of your issues down. Thing is, most of the problems you have are mainly because you flashed a modified ICS ROM. ICS roms by themselves are in beta stage, meaning there are some things that people compromise in flashing them (such as the missing FM radio), and you flashed a modified one, which might be the reason for certain power saving features such as your 2nd core down stepping to 216MHz.
Thing is, most of those were discussed in the NOVA ICS thread.
I would recommend flashing the more stable ROMs. Temasek's CM7, DjangoManouche by Carburano, Nostalgia by Topogigi (Froyo ROM) are the ones that pop-up in mind.
For a panic button, you can do a smartflash and it will restore all partitions to stock LG (wiping all user data of course).
Anyway, read the threads carefully. The opening posts and the last 5 pages at least. In order to get a feel of user experiences with the ROM.
Goodluck and happy flashing!
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
I also noticed that you mentioned you have a G2X? But you also mention having a P990. If you're on a G2X, you have a different forum section my friend. This forum section is specifically for the O2X.
Flashing an O2X ROM on a G2X may result in softbricks.
(Please disregard my advise about ROM choices if you're have an LG P999 G2X, those are all intended for the LG P990 O2X.)
yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)
The ROM itself might not. But I highly recommend you wipe your device since you're moving from 1 version of android (ICS) to another (Froyo or GB).
I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA
Patbach said:
yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)
Click to expand...
Click to collapse
Yes it will wipe them.. for baseband changes too.. so if you have apps that you'd like to preserve, back them up before flashing anything.. Titanium backup will do the trick, but some instability issues might appear if you choose to just backup and then restore everything up.. so choose all your important apps and leave the rest.. this way if something is wrong with the rom after restore, you can at least pinpoint which app is causing it
Sent from my Optimus 2X using XDA
amateru said:
I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
CM7 has a working FM radio since late last year.
Just an FYI.
----------
Sent from my Optimus 2X
salisbury_steak said:
CM7 has a working FM radio since late last year.
Just an FYI.
Oh great.. that means you wouldn't mind using CM7.. i just don't bother checking for working FM radio app since long ago
why not try Temasek's kang build? I believe it is still the best stability wise..
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...
Patbach said:
is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...
Click to expand...
Click to collapse
CM 7 is Gingerbread
CM 9 is ICS
The numbers indicate Android's different iterations, so no, you can't
Sent from my Optimus 2X using XDA
CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2
markop90 said:
CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2
Click to expand...
Click to collapse
Which both are solved to about 95% by using etana kernel.
In short CM7 is the most feature complete ROM without sacrificing performance on our phones.
Skickat från min Optimus 2X via Tapatalk 2
Just to give an update I have changed my ROM to a CM7 based rom like u guys said. Temasek's kang build
Problem 1. Signal interuption : problem is definitly solved.
Problem 2. Battery drain : definite improvement, battery now last at least twice longer
Problem #3 : Phone Clock off? : Didn't get the problem again, so solved.
Problem #4 : Seriously where the hell is my FM radio. : Well I got an FM radio app, but I can't make it work. It doesn't pick up the stations..
Problem #5 : Can't copy MKV files?! : Well this is solved yes and no. If I manage to make my computer detect the damn phone, I can copy whatever I want to. Thing is for some reason I can't seem to be able to plug my phone into Mass Storage mode anymore. It worked a couple of times and all of sudden even tough I didn't change any drivers, my computer just doesn't see the phone anymore. I get a "USB Composite Device" with a yellow "!" mark in my device manager.
I tried a bunch of stuff in the options, rebooting the phone and/or computer, nothing worked. I decided to try reinstalling the rom, and boom right after I pluged it in, the USB Mass storage mode worked. Once again after a couple of times it started doing the same thing (yellow "!" mark in my device manager), and no new drive being detected. This time I'm completly clueless on what's going on, and I have no idea what I can do about it.
I'm currently copying files using Samba Filesharing over Wi-Fi, but sometimes I'd prefer using my USB cable, and I just can't...
New problem!!! : I had my phone at work yesterday and pluged in my headphones to listen to music, start my music and the sound was playing in both my heatphone and phone speakers. I tried unplugging/replugging the headphone, now the sound only worked on the phone speaker. Looked up every phone option possible regarding sound or headphones.. couldn't find nothing. I did a reboot on the device, and bam fixed everything. Couple hours later I re-open my phone for music, same problem occured. Had to reboot the device for the sound to be back in the headphones.
Most problems are fixed, I Guess I'm satisfied, but damn can't everything just work...
JuiceDefender Premium will make it that your device loses 1% every 10 hours if screen is off.
Stock 20Q from LG is free of bugs and full of functions.
Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).
Zorkman said:
Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).
Click to expand...
Click to collapse
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.
Patbach said:
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.
Click to expand...
Click to collapse
That FM radio thing is a bug that I haven't heard of actually. When you have the opportunity (or maybe on the next build #94, I'd suggest a full wipe then reflash).
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
HazzaGalaxy said:
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
Click to expand...
Click to collapse
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Hi,
Is you IMEI ok ? I had this problem with CM10 too but now my IMEI is ok I have no pb at all
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
SKArabaeus said:
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
Click to expand...
Click to collapse
Hey
Where is deep idle?
I have no idea where it is and ive looked everywhere in settings.
Do you have photos?
That would help.
Cheers
ThrashJan said:
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Click to expand...
Click to collapse
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Cheers
HazzaGalaxy said:
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Click to expand...
Click to collapse
Okay, let's start from the beginning :silly:
Whats the exact name of the rom you flashed?
How do you flashed it? (Wipe, etc.)
Have you flashed any other stuff? (Inverted Gapps, Battery mod, Kernel, etc.)
Have you many apps installed?
If i where you, i would flash the newest build with a full wipe, so you got a new, bugfree and stable system
same issue
I have been having the same issue ever since switching to CM10, I have been installing nightlies hoping it will end, but appears to be isolated. Would it help to manually flash boot for each ROM? It cuts off randomly and won't turn on unless charged by a wall charger, or other high-power input (doesn't turn on or charge from car outlet). It doesn't appear to be caused by an app.
Did you wipe when installing nightlies?
If you try to go stock with Odin, and the issue is exactly the same, I think you should consider it could be battery malfunction.
Sent from horseback.
I´m having quite a frustrating problem. Tried to search the net for hours, only finding a handful of people with the same issue but no solution. So, I wondered if anyone can help me out here? The problem is that my clock is not updating while screen is off. Naturally, this affects all alarms and notifications as well.
20:15 -> I adjust alarm to 20:30 and put the screen off. I press power right after the screen has gone off, and see the lockscreen.
Lockscreen informs it´s 20:15 and the alarm is set at 20:30.
20:30 -> Nothing happens.
20:45 -> I press power. Clock says 20:15 for a second. After one second, it shows 20:45, and the alarm starts ringing.
So the problem is quite easy to identify- the clock doesn´t get updated when screen is off. The moment I switch it on -seeing the lockscreen- it gets updated and acts accordingly if any alarms or notifications were to ring at the period it was not updating. However, it´s much less easy to find out what´s behind it. Could anyone spare me a hint here?
I´m running a rooted P7300 with CM10, 30/10 build. Using Tasker to underclock while the screen is off in order to preserve battery life. I thought that caused the problem, but while leaving the CPU untouched....
01:00 -> Switching tablet off, putting alarm at 9:00
09:10 -> Wife wakes me up instead of the alarm. I press power.
Clock says 8:48 for a second. After that second, it gets updated, shows 9:10, and the alarm starts ringing.
I´m getting a little clueless here, so any help would be appreciated.
Running rooted P7300 with CM10 (30/10 build).
Cheers, Henu.
EDIT: Ok, I´ve come to the conclusion that this freezing happens when entering Deep Sleep. If that could give anyone any clues?
Works on CM10 version 11-11
Hi,
I can confirm that it works correctly in CM10 from 11-11.
I only have one weird problem left: the device drains more power when turned of than in standby.
I have been running the 11_11 build since it was released and had not had clock issues until today. I am not overly technical and have no clue why it is happening again. But for as smooth as this rom is I will live with it.
When mine gets confused on time it will not reset itself once i wake the tablet up, it stays messed up until I manually fix it.
Sent from my GT-P7310 using Tapatalk 2
Launcher ?
Do you use the stock launcer? Mine did strange things when using the apex launcher. No problems with stock launcher from cm10.
I am using the stock launcher but have installed nova and thinking about giving it a try
Sent from my GT-P7310 using Tapatalk 2
You could try the clock sync app from the play store. It worked on my phone when it had clock sync issues with a rom. Unfortunately, i'm new to xda, so I can't post the link, but just go to the play store and search for clock sync. It's by Sergey Barinov.
Thanks, but unfortunately none of this methods helped- I´m still having the same issue even with the 11/11- build, running Clock Sync as well. Anyone could shed any light here? I wish I wouldn´t have to go back to some (yuck) stock version.
I don't know if this will help but I just resolved this issue for myself. I did a factory reset. And also wiped all caches and system before flash. Then immediately after flash before rebooting system I wiped everything again except system. And then I started up and there was no issue with the clock. I'm running cm 10. I hope this helps.
Sent from my HTC One X using xda app-developers app
Sounds like voodoo but I´m all in for trying even that. I will post the results tomorrow.
To confirm:
1) Basic superwipe procedure (factory reset/ system, cache, dalvik)
2) flash OS -> don´t boot yet up to OS like normally
3) wipe cache & dalvik
4) THEN reboot -> to OS?
Voodoo, baby.
It worked. Seriously, what the hell. My wild guess is that some file(s) might be corrupted in the actual package- and when the system notices they are missing at the first boot, it will replace them with working ones. Then again, I´m no Android/ Linux expert.
With a clean install, I ran alarm after 8 hours. Worked. Then I added Apex Launcher, waited 2 hours. Alarm went on. Installed everything again with Titanium Backup, put alarm after an hour. Still worked. So I can confirm that it´s not app- dependant but OS- dependant. However, it worked, so thanks a goddamn zillion!!!
Congratulations. Just happy to help.
Sent from my HTC One X using xda app-developers app
I´m going to snap this piece of junk into half soon.
The problems came back, no reason why. I´m now trying one more thing, which is completely disabling Tasker, as it´s basically the only thing running while the screen is off. If that doesn´t help, i´m clueless.
EDIT: What a surprise, it didn´t help. So, it´s either non- functioning CM10 or stock ICS. I could had settled with CM9 easily, but that gave me the battery bug after two weeks. Seriously, this whole me- buying- a- tablet- and- getting- it- to- work has been a living joke. I just would love to have a stripped down OS with a Kernel supporting "all sorts of stuff" like processor speed, running app restriction, tweakable backlight etc.
Ok, so I wiped cache and dalvik and it worked for a couple of hours. Then last night the clock froze again. And this was quite interesting..
Alarm set at 10:30
I wake up 11:15 (hey, it was New Year´s Eve )
I press power and the clock says 11:15 and next alarm is set "tuesday 10:30".
Two seconds later the alarm hops into "wednesday 10:30".
Two hours later I press power, and the clock is 11:15 for a second and jumps to real time. So it´s definitely broken again.
I was just wondering- maybe I could try replacing the clock with another kernel´s version, would that be possible? Any help would be much appreciated.
EDIT: I also tried -once again- without automatic time& date (as my connectivity is set to cut off while the screen is off) and it still didn´t alarm me until I manually pressed the screen on.
EDIT2: Ran A1 kernel, no effect, still bugged.
EDIT3: Ran Tracid´s official ICS. Worked for a day, then bugged. Same thing with A1 kernel. I also had some serious issues with MTP connection and bootloader, so I restored stock and brought it back to the store where I got it for warranty repair. They think it´s a faulty MoBo.
I´m shamelessly bumping this. I ran the stock firmware with Odin and took it to the repair, as I wrote earlier.
Got the tab from warranty repair, seems that the only thing they had performed was "software update" . Very useful for someone who is constantly switching ROMs etc... like I hadn´t tried that before.
After returning to stock and all, I installed CM10 again. And "surprisingly", the problems started again. With or without apps, launchers, cachewipes, younameit. I´m now giving this a test with the stock ROM for a couple of days. I actually hope it doesn´t work, because that would be the only reasonable thing now. If it works with the stock ROM, I´m getting clueless. Does that mean I have some sort of issue which happens only in flashed ROMs instead of the stock one? That would be just....awkward.
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues!
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?
bettuccio said:
hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?
Click to expand...
Click to collapse
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.
dev>null said:
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.
Click to expand...
Click to collapse
dear friend I have already tried everything, I changed 4 different ROMs Aosp (clean installation) but I understood now that the problem is not the overheating of the processor but it is the touch screen that is blocked. As for the programmed switch-on I discovered that in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds. A great solution for me. I did not understand if it is a bug of Aosp as the phone does not charge the battery if it is on but if it is off or I have to plug in the power cord and then restart then charge. I have a feeling it's time to switch phones. Thanks anyway ; }
All cool !
bettuccio said:
... in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds....
Click to expand...
Click to collapse
which Aosp roms? I'm curious to test
dev>null said:
All cool !
which Aosp roms? I'm curious to test
Click to expand...
Click to collapse
I remember 2 of the latest updates. One is "CrDroid" and the other is "Syberia" the one I have right now.