I'm running dastin's latest 10.1 (16th), I'm on the virgin version, and after the March 6th update I noticed instead of my dates reading Monday, March 17th, it now reads 1 3 17...like just the numbers. I know that it's day of week, month, day, but it's annoying that it changed. I didn't notice anyone in the forum thread with this issue, so I wonder if it's something I did in settings.
This is in the notification menu, gcal app, and everywhere that the android system date is used. All of the settings I believe weren't changed, I haven't tried a clean flash but I hope there is something easy I'm missing to correct this issue. Did some searchs on google and this forum and couldn't find anyone else with this problem!
Thank you for the help!
Linksbro said:
I'm running dastin's latest 10.1 (16th), I'm on the virgin version, and after the March 6th update I noticed instead of my dates reading Monday, March 17th, it now reads 1 3 17...like just the numbers. I know that it's day of week, month, day, but it's annoying that it changed. I didn't notice anyone in the forum thread with this issue, so I wonder if it's something I did in settings.
This is in the notification menu, gcal app, and everywhere that the android system date is used. All of the settings I believe weren't changed, I haven't tried a clean flash but I hope there is something easy I'm missing to correct this issue. Did some searchs on google and this forum and couldn't find anyone else with this problem!
Thank you for the help!
Click to expand...
Click to collapse
When you go to settings in the SYSTEM section there is a DATE & TIME option. At the bottom there should be date format which you can select whatever. See if that fixes you up.
Related
since installing the new market i've noticed that after reboots sometimes i have to reupdate apps that i updated maybe even days before.
anyone else?
Are you sure the apps are rolling back are you "have" to "re-update" them or is there just a new update available for these apps? It isn't uncommon for a developer to have an update pushed out then realize (after it's running on a large sampling of phones) that it broke something else or a new bug has popped up and, therefore, release a new update.
Check the version number (bottom of the market description) and see if you are in fact needing to reinstall the update.
positive.
today after a reboot i had 10 "new" updates and they had all been updated either earlier this morning or in the past 2 days.
and some of those had already been updated twice.
and when looking at the recent changes nothing was newer than the last update.
I've noticed the same thing as well. Thought it was just groundhog day or something! Tried clearing the Market's cache and it didn't make a difference.
Sent from my PG86100 using XDA App
the phone seems to have issues holding things after reboots. just like hte home screen icons.
another problem.
it seems to also lose saved contacts that are new if you haven't had them backup over google yet.
some real issues with internal storage somehow?
I have downloaded the firmware update from ASUS, but I have absolutely no idea how to install it. Anyone know?
place it on the root of the /sdcard or on the microsd card if you have one, it should automatically pick it up and ask you to update.
the method is in the manual (iirc) and also on the support section of asus' website.
Now that I'm looking at more threads- is this update worth doing? Seems some people are having serious problems with it. Anyone find it to be very useful?
Before I upgraded, I was experiencing times where I'd have to double tap letters on the keyboard for them to properly register. After the update it hasn't happened since.
I also had some weird hangs and crashes when scrolling through my apps and homescreens, that also hasn't happened since.
Hey if you can't auto-update, check to see if you have a serial number. settings/about/status I believe. I don't have mine in front of me. If you do not have a serial search serial number in the general section and read that thread. Ultimately it just says that the TFP is missing a couple scripts in the kernel and other portions of the system. It's best to return it for a new one. Mine had no serial # and a few other issues, so I returned mine and will be getting a new one tomorrow night.
I have searched on phone issues and even messagebank... There was a post that seemed similar but not the same.
Unfortunately I can't say just where this issue came in; I only noticed it yesterday and, as mentioned in another thread, I have been trying out ROM flashing. My GUESS would be it has to do with flashing 'modem_CWM_I9300XXDLH7' but that is purely a guess because it is call related.
I have flashed a stock ROM, GT-I9300_XSA_1_20120710170916_9xjds9h0pm to install an Aussie ROM (phone from Kogan and was German model) and more recently flashed 'Kernel_CM10_20120820_Official_CWM' in preparation for trying a JB ROM. (I am planning on using 'I9300XXBLH4_Jelly_Bean_4.1.1_Clean_Stock_Rom_Nandroid_Backup' for a first try)
SO, phone seems to be working well; I managed to crash it (stuck on Samsung screen) but have backups that brought me back up to where I was without too many issues.
But, I noticed yesterday I got a Telstra Messagebank notification for a missed call/voice message. It says it came from +101 but when I click the notification it takes me to a Telstra recording saying the number is not connected. This used to work. Dialling 101 works just fine and I have looked to try to locate where the phone has decided MB is now +101 but can't find it.
It's not a biggie, and I figure maybe I need to call Telstra to get their info resent or something, but it is a little annoying to have to dial each time instead of just press the notification.
Any ideas of what to try? I'm about to flash the JB ROM so if that fixes it I will be back (hopefully without dramas ) soon. Thanks in advance for any suggestions.
XXBLH4 is a really old JB leak, flash XXDLH8 instead (DLH9 is newer but has a keyboard bug)
As for your problem, I don't know what to tell you but your carrier won't be able to help you as you have unofficial firmware on your phone and that may be the reason and they will only be able to assist you in regards to the official Telstra fw.
Is it really that big of a deal to dial 101?
Sent from my GT-I9300 using xda premium
Journyman16 said:
It says it came from +101 but when I click the notification it takes me to a Telstra recording saying the number is not connected. This used to work. Dialling 101 works just fine and I have looked to try to locate where the phone has decided MB is now +101 but can't find it.
Click to expand...
Click to collapse
that is a strange one. It seems as though it's trying to dial 101 as an international call (with that plus in front of it making it a call to USA number 01), when it should have picked it up as +61 101.
Out of curiosity, what does it come up with when you tap and hold on the SMS and go to "View Message Details"?
@nodstuff - The reason for I9300XXBLH4_Jelly_Bean was because, a. I found it and the file date was something like 25/8/12, and because the description said it has been cleaned up and all bloatware removed. I don't recall seeing XXDLH8 for download but I am new here... I was thinking along the lines of getting something known and stable for my first JB flash.
@Dinty - I don't get a 'View Message' option on a long tap, I get a menu with, Call +101, Send Msg, Edit numbr, Add to Contacts, Send Nmbr, Add to Reject list, Delete.
Further info just noticed - older call from MB (30/8 - prior to new Modem flash) came in as Int'l M'Bank with #101# so somewhere the MB number has altered.
I doubt Telstra will have an issue with the FW etc. It isn't their phone. I bought outright and would be speaking to a rep - IIRC when I got my Moto Defy from the dealer a couple of years back they had to send me a txt which I saved and it set up the Telstra info on the phone. Might be mistaken in memory of that though...
@nodstuff - do you have a recommendation for a XXDLH8 ROM to flash? I'm looking for stable with some optimisation and as clean of standard apps as possible. I've got an Apps backup in Titanium Pro that I figure I can use to put my new apps back.
Also, is the Keybd issue with LH9 itself or just with some ROM's?
thanks for the help...
Journyman16 said:
@nodstuff - The reason for I9300XXBLH4_Jelly_Bean was because, a. I found it and the file date was something like 25/8/12, and because the description said it has been cleaned up and all bloatware removed. I don't recall seeing XXDLH8 for download but I am new here... I was thinking along the lines of getting something known and stable for my first JB flash...
Click to expand...
Click to collapse
Well don't flash XXBLH4 so, its very buggy and not stable.
XXDLH8 is very stable and pretty bug free.
There are a few downloads for it (cwm flashable, Odin or an ota package. I suggest cwm or Odin method as the ota method is quite tricky.)
Sent from my GT-I9300 using xda premium
Journyman16 said:
IIRC when I got my Moto Defy from the dealer a couple of years back they had to send me a txt which I saved and it set up the Telstra info on the phone. Might be mistaken in memory of that though...
Click to expand...
Click to collapse
I believe you're talking about the automatic set-up service. I think this is what you mean:
http://www.configure.telstra.com.au/telstra/index.jsp
Not sure it will have any effect on that messagebank issue, but I suppose it doesn't hurt to try!
Dinty said:
I believe you're talking about the automatic set-up service. I think this is what you mean:
http://www.configure.telstra.com.au/telstra/index.jsp
Not sure it will have any effect on that messagebank issue, but I suppose it doesn't hurt to try!
Click to expand...
Click to collapse
Thanks for the link - that looks what I originally had to do over the phone, but then I didn't have a Telstra account set up at that point.Didn't work unfortunately. le sigh!
So, I am now the owner of a JellyBean phone, all working nicely and with my apps installed again. All went smoothly and I just chose my purchased and download apps from my titanium backup and Voila!!!
I took the advice and installed GT-I9300_WanamLite.XXDLH8.V3.0.RC4.NO-WIPE - I thought about the DLH9 version of it but saw a note in the thread about keybd issues, so, taking the advice above I DL'd the DLH8 version.
Only thing I have noticed so far is it seems a bit slow on the USB charging. Once it's at 100% I will disconnect and see if maybe power is draining too fast, then look at ways to improve battery.
Just did some trials of the MB issue and noticed something odd - if I try to create a Contact I am unable to enter numbers in the name field. I also tried to set up my mobile banking and using the app provided by the bank I cannot use numbers for my ID, even though it is an 8 number ID. The Keybd simply will not change to numbers until I go to the PW line - is this the keybd error you mentioned as being present in DLH9, nodstuff??
Hm... so I took a chance and flashed Wanamlite's keybd fix; the thread says it is for DLH9 but I figured what the heck, if it fails the phone I can easily reflash the ROM.
Seems to have worked. Gonna leave a comment over there about it because I seem to have noticed something not mentioned by others.
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
ill give $5 to the person that fixes this.
tatzelworm said:
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
Click to expand...
Click to collapse
I have the same problem.
Fixed?
James Musacchio said:
I have the same problem.
Click to expand...
Click to collapse
Well as I stated in my edit, the 12/24 nightly appears to have fixed this issue so far as i can tell. Also updated to the 12/25 nightly and the camera still works. One bad thing about this is that I have experienced more than a few reboots, but my phone starts up so fast afterwards that its a small price to pay for having my camera back.
As always, make a backup before you flash the newest nightly but I haven't seen too many problems other than the occasional crash of a couple apps and the unfortunate reoccurring crash of Apollo which is annoying.
Let me know if this fixes your issue, if it does then I'm glad I could help.
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
12/25 is a bit sketchy
gregsarg said:
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
Click to expand...
Click to collapse
Yeah I decided to try the 12/25 build and didn't notice any improvements from the 12/24. Ironically about an hour after my last post my phone then went into a reboot loop that I couldn't stop until I removed my battery. I had to boot into cwm recovery and then reflash the 12/24 build. So far this is the most stable nightly that allows for the camera to work without causing too many issues besides one incident I had the first day I flashed it.
I recommend people stay away from 12/25 as it was extremely unstable in my experience. I may try the 12/26 build simply because I can, but I'll definitely keep the 12/24 on hand if that fails as well.
I have the notification to update [Test] M1D65H to M1D65N this morning and don't see mention here. I am holding off installing it for the moment. Anyone know anything about it?
I've tried to take a screenshot to show it but that's been coming up black...
I have the same update, but the [Test] part seems a bit scary since it's out of warranty.
Have you already updated it?
FireFly3k said:
I have the same update, but the [Test] part seems a bit scary since it's out of warranty.
Have you already updated it?
Click to expand...
Click to collapse
I have also received this notification on my watch. I'm a little wary of the '[Test]' part too - don't recall seeing this on previous updates.
I think I'll probably delay the update until we get some more information.
I had the same this morning. Just did the update. After Wear rebuilt the cache I went to Settings and now this is the version:
Wear 1.5.0.3853039
Android OS 6.0.1
Security level April 1, 2017
So it just looked like a monthly security update I think
I had exactly the same message this morning and it is still sitting on my watch for actioning....the [TEST] made me aphrensive
Thanks farris for being the guinea pig. based on this I shall go ahead and update from 1st Feb security level release to this 1st April release.
farris said:
I had the same this morning. Just did the update. After Wear rebuilt the cache I went to Settings and now this is the version:
Wear 1.5.0.3853039
Android OS 6.0.1
Security level April 1, 2017
So it just looked like a monthly security update I think
Click to expand...
Click to collapse
Thanks! I'll install it as well. Lets see what will happen
edit:
It's still working!
Wish it was Android 2.0...
I had the same Test labeled Update today popping Up, just Hit Install. Worked.
Good to See updates, had hoped for android2 too
Thanks for the feedback everyone. After posting that, I had a busy day and never got to revisit the matter. I may wait a little longer.
Any improvements? My watch can get unusably sluggish at times. Removing unnecessary apps and factory resetting did nothing.
Is the option " change watchface" under settings new? I don't remember this one
I haven't updated and have change watch face, second setting option below adjust brightness.
april security update
I have just updated my G Watch and everything seems to work fine (just like it did before).
A question for those on the latest (end of March) Android Wear app: did you experience occasional notifications sync problems (especially when replying from the watch) and (above all) frequent force closes of the Android Wear app (on the phone)? If yes, has this update fixed those problems?
I am asking because due to those annoying problems I went back to the Android Wear app version from February so I would like to avoid updating and going back to the latest Android Wear app (the most recent one is still the troublesome one from the end of March) only to see again the same problems and having to go again through the downgrade process (uninstall Android Wear, install the version from February, re-set everything up).
a mirror please
hanschke said:
a mirror please
Click to expand...
Click to collapse
Here: https://mega.nz/#F!H9AV3Yra!55CKVg6yE9-YDs87W3NIJw
I will also upload the boot.img predone with magisk if anyone wants it or they can just follow my guide (look at signature)
Bait-Fish said:
I have the notification to update [Test] M1D65H to M1D65N this morning and don't see mention here. I am holding off installing it for the moment. Anyone know anything about it?
I've tried to take a screenshot to show it but that's been coming up black...
Click to expand...
Click to collapse
FireFly3k said:
I have the same update, but the [Test] part seems a bit scary since it's out of warranty.
Have you already updated it?
Click to expand...
Click to collapse
farris said:
I had the same this morning. Just did the update. After Wear rebuilt the cache I went to Settings and now this is the version:
Wear 1.5.0.3853039
Android OS 6.0.1
Security level April 1, 2017
So it just looked like a monthly security update I think
Click to expand...
Click to collapse
After a few months, I finally noticed what the [TEST] tag were for. It was released on April fools day(april 1st), carry the code M1D65N, "N" as in nougat, or android wear 2.0. Read it as, [TEST] Nougat build. Someone tried to make an april fools prank and it didn't work.. ROFL.
The first letter signifies the Android version, not the last...
Sent from my Pixel XL using Tapatalk