I flashed over to CM6.1 yesterday and applied the persist.sys.timezone=America/Los_Angeles edit to the build.prop. That is working just fine because everytime I start my tablet it sets the time to 4:00 PM 12-31-1969 which is 8 hours before 1-1-1970 (The beginning of time for UNIX).
My question is, is anyone else having this issue or am I the only lucky one?
If I'm not the only one, does anyone know how I can fix this??
I have tried to change the date and time, but after every reboot it changes back. Pretty frustrating, I do not want to be 3 years old again!
This is a known issue, due to the boot.img being used. You can use an apk like "clocksync" as a workaround, for now.
There's no fix yet. Easiest way to fix it is to install NTPc. It'll check the time servers on the internet and update your time/date appropriately.
Thank you, I was not aware that this was a known issue. I can live with it until the final fix is in place.
I will run those work arounds and continue to love the CM6.1 ROM.
Date goes back to 1970 on reboot
Three years have passed and this issue still remains even with CM10...
When the heck they are going to fix this?
Related
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
Hi there!
First time I need to make a topic, as I don't find the answer anywhere..
Had my Touchpad since about two weeks.
However the accelerometer has not functioned at all since I got it.
First thing to check is the auto rotation lock -> it's turned off
Second thing I did was download a sensor visualizer app -> Seismograph.. This shows very weird results for the x-axis (see attached file), fyi, the Y and Z-axis functioned as expected..
Then the third thing I tried, Need For Speed Hot Persuit... A game that uses the X-axis accelerometer (right!?)
This works brilliant!
Other things I have done to troubleshoot this:
Restart the device.
Full reset the device.
Run HP doctor.
All have failed in resolving my problem.
As I've bought the touchpad from a french webstore (fnac.com), HP Netherlands (where I'm from) tells me I need to get back to them for a solution, as they don't offer worldwide repair (unlike ASUS for example).
Fnac.com has not answered to my request to exchange the product (2 days after I got it). And actually I just want to solve it myself if possible, bought it for fun anyways (and reading of course xD)
Any ideas how I can make the OS recognize the accelerometer?
Last thing, the auto rotation functions in the following way: Tablet is stuck in landscape, I turn to portrait, screen turns as well, but within the second the tablet is back in landscape. This behavior can be read from the seismograph screenshot.
Thanks!
Hello
I just started a new thread for a different accelerometer problem (it is just dead)
http://forum.xda-developers.com/showthread.php?t=1284760
Was wondering how you ended up fixing your problem.
thanks
Just wanted to ask you the same question...
I still have the same problem. Need to contact Fnac.fr, but my french sucks and my time is scarce. So have been postponing this. My unit actually came DOA.. however Fnac didn't respond to my request, and has now asked me to call them.. sucky service
You have no solution I guess?
Well this is odd..
Out of nothing the auto rotate function is working since today.. I noticed it while reading a PDF in Android. Booting back to WebOS didn't make a difference, the sensor is working again
I've got no clue what did the trick.. I have not updated the kernel or something like that lately.
I wonder if the sensor was kicked back into action by brute force (for instance my cat jumping on the tablet..)
Anyway, problem soved for now =D
Hi all,
Firstly can I say thankyou to all of you at these forums, I've been a lurker for a while, waiting for my Prime to arrive, and I'm very grateful for all your insights!
I have now recieved it and seem to avoided most of the well-documented problems on here, but seem to have managed a new one (at least i couldn't find a similar one through searching).
So I updated the Prime with the new firmware and it all seemed to go well. After a while the notification popped up to do the camera firmware (as I had been expecting from these threads). I set it going, and after a short while it said it was complete. The next time I powered on however, the notification to update the camera firmware was back, so I did it again (thinking it must be additional one). But it keeps doing the same thing - saying it's successful, only to re-appear after a re-start.
My current versions are
Build - 8.8.3.33 (which i know is what it should be)
Camera - 0xFFFFFFFF (which I know is wrong!)
Anyone else had a similar problem? Or any ideas?
I have no idea if it's possible, but I am also wondering whether this is what's causing my auto-rotate not to work. Just to confirm, I have the auto-rotate set on, and the gyroscope doesn't seem to be working for anything else (tried it on riptide demo)
Any ideas would be greatly appreciated!
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
tdrussell said:
you should try reflashing .33 from the ASUS hosted file...i think there are a few threads about where to get it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1429067
Mine is completely borked. After installing ICS I got a notification for a camera firmware update. The update failed several times, and now when I launch the camera app it says it won't work without updated firmware...
EDIT: I rebooted and as soon as it started up it bugged me to install the camera update again. I made sure the screen stayed on while it updated this time and things seem to have worked out. Camera is working just fine!
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.