Database Develop

Known Issue? Froyo clocktime issue with MobileNavigator (2.5.1,2.6.1) / Widgets

Hey guys,
i have a strange issue with Mobile Navigator and froyo:
Mobile Navigator gets the clock wrong. Its always one hour backward. I noticed that cause it calculated the arrival time for many routes exactly one hour different than for example google maps. Also i drove and the time in the noticationbar was past than the arrival time when there were like 60miles to go.
For exmaple Sygic Mobile Maps 10 works fine and calculates a right arrival time (so it must get the clocktime right) ... i experienced something similar with BeautifulWidgets and ToogleWidgets - they dont get the time at all and just freeze the clock. FancyWidgets then worked for me.
One may think of sommer/wintertime as a cause for the "one hour delay of MobilNav" ... but why is then the Clocktime in the Notificationbar right and why does it work with SygicMaps ... there is no setting for clock in MobilNav ... addionatly its strange that some widgets dont get the clocktime at all from froyo.
Is there some issue with apps dont get the clock time right from froyo?
I flashed nearly every froyo rom from Stock RC1, RC2 to the other mods. I wiped in fastboot erase system -w. Cleared cache, Dalvik .... I use the mtd paritions. Cleared battery, rotate settings. You see my radio and SPL in the sig.
Thanks for telling me it you got similar experiences
Is this a known issue? I never read of that in the rom thead, pls help if i skipped reading something.
greets

Random groups of apps failing suddenly at the same time.

Anyone heard of an issue where apps in internal storage just start fc'ing then are essentially deleted? I am running cm6 rc2 which I flashed about 6 weeks ago. I haven't had too many issues outside of the bugginess of the ads launcher which I replaced with launcher pro. This afternoon, I try to start up dogcatcher and it immediately force closes, I tried to access the podcast I was looking for through music mod and that fails as well. I thought I might need to reboot, but when I get back into the system two more apps fail as well as the original failed apps not working. Curious, I look in my application list and the apps are mostly gone except for a few apps that show the generic market app icon, which I take to mean corrupted apps. I was able to go into titanium and restore some of the apps to work again, but I have had a pop up stating mytracks has stopped working, but I haven't even started mytracks since the reboot. I guess what I am worried about is If my phone's internal storage is failing? Is it even possible? Any suggestions?
Sent from my Nexus One using XDA App

I had the same thing happen, everytime I rebooted more apps would become corrupt, I was worried that my internal storage was failing, so I wiped everything and started again from scratch, and haven't had a problem since.

When you say start from scratch are you talking about reflashing cm6? I had been holding out since I have been reading about a lot of issues with the 6 stable version.

I formatted the phone, deleting cache and dalvic cache, and then reinstalled. I was using CM6 at the time so reflashed it, did everything by the book to be sure and it has been smooth sailing since.

Only time I have ever had this issue, on the N1 or G1 was after flashing a ROM and not wiping. Sometimes I could get away with it, sometimes not. Wipe and reflash is what I would do.

Hey Thanks guys.
I went ahead and wiped everything and started fresh with cm6 stable.
I am not sure what was going on . I had done a complete wipe and install from stock to rc2 and it worked great for 4-5 weeks. The only thing I could think of was possibly an issue with K-9 mail. One of things I saw happen fairly regularly (3-4 times a week) after rc2 was installed was that K-9 would suddenly just fc. That in and of itself wasn't too weird, but every time it would fc I would get a low space notification right after, where I kew I had 40-50 mbs of space free. Memory leak or something? Dunno.
All weirdness aside, so far CM6 stable is running great...

I've seen this happen when my the /cache filesystem was full. ('App not installed' , FCs etc). Run a 'df' command in a shell to check.
Clearing the cache would be a temporary solution. Moving the /cache to the sd card using DarkTremor Apps2SD is a permanent solution.
I currently have 178 apps.

New Nook Locking Up

Just bought a NC. Installed CM7 and everything seemed to be fine. Now the NC is locking up after less than a minute of use. I rebooted into CWM and wiped cache and dalvik but its still locking up. I checked to make sure it wasn't overclocked... nope... still locking up.
Any ideas?
I'm running the latest nightly....
Not my first time around CM7. I've got a Droid INC that's been running CM since 6.0 and I'm on the latest nightly with it.

Locking up as in it just quits responding? Of you have to fc?
Are you installing to emmc or sd? If the latter, what card do you have?

Completely locks up and I have to hold the power button. Its installed to emmc. I've got a sandisk 2gb in there which I've swapped.
I reloaded the nightly with a cache and dalvik wipe. When that didn't help I did a reload with a full data/factory reset. I'm still getting lockups though not quite as frequent.
Is bad hardware an option?

Always a possibility.
Was it new or refurbished?
Did you use out as stock before you flashed it with cm7?
Can you reinstall 1.2 stock, if it reinstalls ok, does it lock up also?

Brand new. Ran it for 5 minutes before slapping cm7 on it. I was thinking about putting 1.2 back on it and see what I get.

Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......

menos08642 said:
Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......
Click to expand...
Click to collapse
Yeah it's a common problem. It's Badly coded app.
Sent from my LG Optimus V using Tapatalk

think i am using fancy widgets, if you want something similar, that to date, i havent had a problem with - other than it uses clock cycles for something that you would think wouldnt take anything (showing the clock!?)

Yeah.. I installed fancy widgets. So far no problems. Don't know what the problem with BW is.

I am using BW on my nook as I type this at work..no problems at all.
Sent from my NookColor using Tapatalk

What build are you running? Are you on a nightly or the RC?

[Q] Random Bluescreen (lines) Issue

Hi all,
I have a 32GB TP that has been doing fine (save for some battery issues) up until recently.
Now, at random, it flashes a full screen of blue lines. This lasts for about 1 - 2 seconds. Anything running appears to freeze while it happens, and if audio is playing, the TP will just BOOOOOOOOP while the blue lines appear.
Some times it will go an hour. Other times it does it every 20 seconds or so. Even just scrolling through the apps list. Does it both while plugged in and not.
I was running CM9 and thought that maybe it was a corrupt ROM or something. So, I did a full wipe (system, caches, etc) and installed CM10.x/4.2.2. Still doing it.
Anybody have ANY idea what might be causing this? Im guessing its a hardware issue now. Ive seen similar issue mentioned but never with any resolution.
Except for this issue and the occasional not wanting to turn on, the TP has been great. So...Im hoping its something fixable.
I'm not OC'd. Running pjsports CM build with non-system apps restored with TBU. Nothing funky (performance enhancing, monitoring, tweaking, av apps) installed.
Thanks.

Ahhk said:
Hi all,
I have a 32GB TP that has been doing fine (save for some battery issues) up until recently.
Now, at random, it flashes a full screen of blue lines. This lasts for about 1 - 2 seconds. Anything running appears to freeze while it happens, and if audio is playing, the TP will just BOOOOOOOOP while the blue lines appear.
Some times it will go an hour. Other times it does it every 20 seconds or so. Even just scrolling through the apps list. Does it both while plugged in and not.
I was running CM9 and thought that maybe it was a corrupt ROM or something. So, I did a full wipe (system, caches, etc) and installed CM10.x/4.2.2. Still doing it.
Anybody have ANY idea what might be causing this? Im guessing its a hardware issue now. Ive seen similar issue mentioned but never with any resolution.
Except for this issue and the occasional not wanting to turn on, the TP has been great. So...Im hoping its something fixable.
I'm not OC'd. Running pjsports CM build with non-system apps restored with TBU. Nothing funky (performance enhancing, monitoring, tweaking, av apps) installed.
Thanks.
Click to expand...
Click to collapse
I got this whenever I tried to change to a rom that was not supported with the current partition layout or needing an SE version or a data/media on a non data/media version....
I held home and power at same time till it re-booted and went into CWM recovery and re-flashed the original rom. (I bet you could use your NANDroid as well)

SteveoSupremo said:
I got this whenever I tried to change to a rom that was not supported with the current partition layout or needing an SE version or a data/media on a non data/media version....
I held home and power at same time till it re-booted and went into CWM recovery and re-flashed the original rom. (I bet you could use your NANDroid as well)
Click to expand...
Click to collapse
Thanks, but as I said, this was originally happening with the lastest stable build of CM9 (Sept '12?) - which was fine for about a year. So, since I had to reinstall to try and eliminate the issue, I went with the latest build 4.2.2 ROM that DIDNT require the new partition layout.

[Solved] [I9305] crash reboot, dalvik cache and battery problem

Hey Guys,
First the relevant data
Galaxy S3 LTE I9305
ROM: Carbon Rom KK 4.4 (CARBON-KK-NIGHTLY-20140701-1234-i9305.zip)
Kernel: Standard Carbon Kernel
Problem Description:
The phone reboots itself sporadic and then gets stuck at bootlogo. It is completly sporadic so sometimes it is when i am using it heavyly sometimes just when i end a call or want to do something else not intensive.
The only solution then is to go to recovery, wipe cache and dalvik cache and the reboot. The phone the rebuilds the dalvik cache and crashes a few times while the process.
But there are some more strange things going on:
- Battery
The battery is almost fully charged, when the phone crashes and reboots a few times while rebuilding dalvik cache the battery show up empty suddenly! Phones turns off and only turns on when plugged to charger and then shows battery level 0% when running again. The charging process begins normally from there.
Sometimes the battery shows empty as described above but when i restart the phone again and rebuild dalvik cache it's on its old state (almost full).
- Kamera
When i take pictures, sometimes the camera shows some red stripes all over the stored picture or even in focus mode. Then the screen starts flickering and phone crashes as describes above.
- PIN
When crashed and running again after some tries to build dalvik cache, sometimes i enter PIN to unlock sim card and nothing happens. Then the screen starts flickering again and it crashes. Procedure start again then.
- Charger
When the phone crashes and i plug it to the charger before rebuilding dalvik cache, it runs through without any errors like it should.
What i tried so far:
- Other ROM (AOKP, CM, other Carbon Rom builds)
- wiped everything (really everything on internal storage) and clean install
- reflash after crash (dirty)
- reflash after crash (wipe)
- leave phone with just a few apps after clean install (thought it could be one of my apps)
- recording a logcat (aLocRec and logcat reader) but the problem here is as the logcat is stored in memory it's not accessible after crash (reboot).
What i want to try next:
- try getting a logcat via adb and hope it crashes while logging
- other kernel (don't want to try this, would be last option).
Does anyone have an idea?
Thanks!
Dark Smile

One idea may be a bad battery which may cause inconsistent power supply and all kind of strange errors. Especially because, as you write, with charger = stable voltage source things look good.
Cheers,
Axel

Thanks for the tip s3axel, i'll buy a new one when i get off work and try it.

I just ordered a original battery from here:
http://www.trade-shop-online.de/ori...galaxy_i9305_galaxy_i9305-p-29153.html?ref=20
I'll give feedback when arrived and tested.

Good luck

Unbelievable, it was the battery! No problems with the new battery. Thanks for your advice s3axel
Sent from my GT-I9305 using XDA Free mobile app

I was experiencing exactly EVERY one of those issues besides the battery jumping to zero. It would even crash when opening messaging, chrome, contacts, literally everything crashed it.
I tried everything that you tried, and was about to logcat from my computer too lol.
And without looking it up I had the idea, maybe its the battery and it just cant support the changes in power needs, maybe I should buy a new battery!
Thought, nahh... ill try some more things first. Then boom! Reading this post I felt like I wrote it!
This thread just blew my mind!!!