Root Need help... Alarm reset popup

[jeremy.glenn87]

So i recently decided to flash a theme, and proceeded to do so.

I downloaded, moved it to my sd card, flashed into recovery, flashed the zip file, installed and the theme looked great....

Until i had this small rectangle box popping up in the middle of my screen that reads "alarm reset". I couldn't fathom what this could have been, so i immediately went and flashed back to the nandroid backup that i had made right before installing the theme. I figured this would fix my issue... but no. its still there.
It will pop up, then after a few seconds go away... then come back, and so forth....

I have since noticed that my phone will not go to sleep. If i want the screen to turn off, i have to lock it manually with the power button.

Dont know if it matters or not... but this is the theme i tired to install
http://forum.xda-developers.com/showthread.php?t=768848



If anyone could help me try and get this fixed, i would really appreciate the help...

Here is a screen shot with the alarm reset box

 

[akazabam]

I searched around for a bit and only found people asking about this, but couldn't not find any real answers. So, let's try this:

1) Install alogcat from the market
2) Open it, and go to menu->more->preferences->Format->Time.
3) Go back to the main screen, and wait for the message to pop up. Let it do that maybe five or so times.
4) After it has popped up a few times, select menu->save.
5) Using any file browser, you can find the log at /sdcard/alogcat/alogcat."date/time", were date/time is whatever the date and time when the file was created.

Copy that file to your computer and either post it here if it's short enough, or just send it to me. I'll see if I can find anything interesting.

 

[bubbleboy]

I was running into the same thing. It seems to have been caused when I updated programs earlier today. The same day as your original post.

I checked for updates again a few moments ago and there were 2. Google goggles and another.

After these two updates, the 10 second spaced "alarm reset" message no longer appeared.

Causal relationship? Seems like it.

M

 

[jeremy.glenn87]

guys... I want to thank you for responding so quickly...

For some reason my problem has been fixed....

akazabam, I did everything you told me to, and i even got as far as about to post the results on here, and i realized that it has stopped what it was doing...

For whatever reason it was... this was the code that it was giving when the alarm reset box was popping up

01-18 07:19:58.018 D/cg ( 888): BootReceiver.java:34 app/alarm/rotatelogs/rotate

Anyways.. like i said thanks guys for helping... I may go ahead and try installing that theme again...

 

[jeremy.glenn87]

Ok... so i went ahead and put the theme back on and everything is fine...except for when I try to pull up the phone screen to dial a number the only response I get is a small grey box at the bottom of the screen that says "phone"


I like this theme but I kinda need the phone option...lol.

Any ideas?

 

[akazabam]

It must have been related to an app update. A theme wouldn't have done that. Unfortunately, that one log entry isn't enough information. I guess it's a good thing it stopped.

What exactly do you mean a small grey box? Can you open the phone from the app drawer?

 

[jeremy.glenn87]

Yeah im positive it was because of an app update. Just a coincidence that it happened when i flashed the theme.


I went ahead and went back (again) with my nandroid backup, because I could not access the phone option, and to answer your question about the app drawer, no I could not. The Icon wasn't even there. Here is a picture of the "grey box"

 

[akazabam]

Interesting. What ROM are you running, and which version of the theme did you flash?

 

[jeremy.glenn87]

Below is what my system is running, which is pretty much normal stock? with the battery mod i think...

and i flashed the

3.70:
Standard Edition
v1.5: Download

from here
[THEME] MattedBlues - CM 6.1.2 / Sense 3.70 / MikFroyo Versions *UPDATED 1/12/2010* - xda-developers

 

[akazabam]

That looks like stock (aside from the kernel). Did you flash a deodexed ROM at any point. You need to do that before trying to flash a theme like that. If you didn't, I'd be surprised the system booted up at all after flashing a theme. Pretty much any custom ROM will do.

 

[jeremy.glenn87]

At one point when i first started messing with the whole root process.. i flashed cyanogen, but i didn't like the fact that i lost everything, and had not realized what titanium would do, so i went back to my original nandroid backup.

So, i guess this obviously would be the root of my problem... Im backing up all my data now, and im going to flash a custom rom....

Any suggestions on which rom I should flash? whats your personal favorite?

 

[akazabam]

I use mikfroyo, as it has some optimizations that make it load and run a little faster. If you use that one one, though, take note that while the mattedblues theme does support that ROM, it's still on 4.3. Mikfroyo is up to 4.4, now. Presumably, it will get an update, but you can still with 4.3 for assured compatibility. Also, make sure you use the Mikfroyo specific version of Mattedblues if you want that theme, still. Myn's Warm is also a good ROM. You can use the standard version of the theme if you like. Either way, see how you like the default theme for whatever ROM you flash. Make a nandroid backup of the ROM the way it is after flashing before flashing the theme, no matter what you decide.

 

[Matlock]

I am starting to wonder if a Theme section would do well.. But eh... Way too many ROMs/Versions/and Themes... So.. I might just wait on that one.

 

[akazabam]

Lol, yeah that would be a huge pain to maintain. The wiki method used for ROMs at xda works great as long as developers update it. The same should probably be done for themes. It would be hard for just you to do in a guide, though.

 

[Matlock]

Lol, yeah that would be a huge pain to maintain. The wiki method used for ROMs at xda works great as long as developers update it. The same should probably be done for themes. It would be hard for just you to do in a guide, though.

Hell, all I was thinking about was a How-To on the basics.. and even that would have been a burden. Let-alone everything else. haha

 

[moespeeds]

I also had this problem today, and it went away on it's own after a few hours. I rebooted my phone, and now it's back. WTF.

 

[akazabam]

If you'd like to do what I suggested earlier with logcat, feel free to post it here or send it to me.

 

[moespeeds]

Last night I sbf'd back to .320, then back to .340, wiped cache, etc. I downloaded most of my programs back from martket rather then just reloading them via Ti. I got everything back up and running, rooted the phone again with Z4, then installed Apex via Rom Manager. Everything was good all day. Came home from work, sat on the couch a played Sims3 for about 15 min, and battery went from about 90% to zero and phone died. When I plugged it back in and charged it enough to start up, the damn "alarm reset" popup was back! When I get some time I'll run alogcat and post here.

FYI I'm on a Droid X Verizon

 

[moespeeds]

Here's what I got. It seems that as I charged my battery back up, it went away.

I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
D/cg ( 1908): BootReceiver.java:34 app/alarm/rotatelogs/rotate
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
D/dalvikvm( 1841): GC_EXPLICIT freed 2996 objects / 213784 bytes in 48ms
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
D/cg ( 1908): BootReceiver.java:34 app/alarm/rotatelogs/rotate
D/NetworkRequestUtil/ConstructEventRequestPath( 2065): /__utm.gif?utmwv=4.5ma&utmn=935016719&utmt=event&utme=5(market_install*search*appbrain)(0)8(5!phone)9(5!verizon%20cdma_shadow)11(5!1)&utmcs=UTF-8&utmsr=480x854&utmul=en-US&utmac=UA-7184590-8&utmcc=__utma%3D999.1434977313.1295483404.1295483404.1295483404.1%2B__utmz%3D999.1295483404.1.1.utmcsr%3Dandroidmarket%7Cutmccn%3Dsearch%7Cutmcmd%3Ddevice%7Cutmctr%3Dappbrain
W/googleanalytics( 2065): Problem with socket or streams.
W/googleanalytics( 2065): java.net.ConnectException: www.google-analytics.com/127.0.0.1:80 - Connection refused
W/googleanalytics( 2065): at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:254)
W/googleanalytics( 2065): at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:533)
W/googleanalytics( 2065): at java.net.Socket.connect(Socket.java:1055)
W/googleanalytics( 2065): at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
W/googleanalytics( 2065): at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
W/googleanalytics( 2065): at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
W/googleanalytics( 2065): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
W/googleanalytics( 2065): at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
W/googleanalytics( 2065): at android.os.Handler.handleCallback(Handler.java:587)
W/googleanalytics( 2065): at android.os.Handler.dispatchMessage(Handler.java:92)
W/googleanalytics( 2065): at android.os.Looper.loop(Looper.java:143)
W/googleanalytics( 2065): at android.os.HandlerThread.run(HandlerThread.java:60)
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
D/dalvikvm( 1961): GC_EXPLICIT freed 2616 objects / 169976 bytes in 76ms
D/cg ( 1908): BootReceiver.java:34 app/alarm/rotatelogs/rotate
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 353, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
D/dalvikvm( 2417): GC_FOR_MALLOC freed 5742 objects / 710776 bytes in 87ms
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 353, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 353, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 353, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 354, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 355, 55, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 356, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 357, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]
I/WindowOrientationListener( 1266): 358, 56, 0
I/WindowOrientationListener( 1266): setTiltFlatStatus[false]

 

[akazabam]

Well we at least have it narrowed down to this:

D/cg ( 1908): BootReceiver.java:34 app/alarm/rotatelogs/rotate

I've done a little research, and all I can find out is that the problem just seems to go aways for most people after app updates. I'll tell you what. So that we can try and figure this out once and for all, can you tell me what app updates you have available? Don't update anything yet. We might be able to narrow it down a little.

 

[moespeeds]

No app updates. It started again last night just randomly, I had put the phone down to charge for a few hours and when I picked it up again it had started. This morning I did a battery pull, and it was still going. I did a fully app and system setting backup with Titanium, with the intention of doing a wipe. By the time Ti was done backing up, the problem was gone and it's been good all day. I was thinking about it last night, the problem started when my battery went completely dead while playing sims3 a few days ago, and started again yesterday when I did the same thing. I've since removed sims3 with no change.

 

[jeremy.glenn87]

akazabam, the app update that did it for me, i believe, was craigslist mobile.

it seems that different apps are doing this for different people.


I havent had a problem with mine since two days ago.

 

[akazabam]

Yeah, I heard somebody say updating craigslist fixed it, but like you said, it could be other apps. I think this might be some issue with the system, and apps trying to do something incorrectly - hence different apps causing the problem. Unfortunately, the log, didn't have much information in it other than the alarm popup itself. I'll keep looking into it.