Database Users

[Q] Updating to 1.1 on touchnooter rooted touch

I have a Touch rooted with Touchnooter. My touch doesn't seem to want to update to 1.1 (I know doing so will kill GAPPS, but I'm okay with that). I've waited for the update to be pushed and I've also put the update file in my Nook directory. Is there something about Touchnooter that prevents the Touch from updating?

I haven't tried to update after using touchnooter, dont really know if it blocks nothing, OTA or prevents from updates, OTA or manullay, but you should restore a copy of your nook if you have it, or use nookrestore and then force a reset to also delete /data.
Or use adb to force restore
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
and then reset normally and if it dosnt let you, force reset, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
That will erase /system (restore) and /data (reset), and you should be able to update.

I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?

kunchers said:
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
Click to expand...
Click to collapse
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.

The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?

TJay99 said:
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
There's nothing in TN 1.6.24 that will block updates.
If you want to make sure, here's the cleanest way of doing so:
Block BN OTA Updates the EASY way
Yes, it's a Nook Color thread but it would work for Nook ST aswell.

TJay99 said:
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
Blocking updates is also covered here http://forum.xda-developers.com/showthread.php?t=1346748 but with adb and sqlite.
Search for Blocking OTA updates: on the thread.

Yeah, I hear you. I gotta just do it. Strange though, why my Nook won't update.
ros87 said:
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
Click to expand...
Click to collapse

Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!

I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.

Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?

TJay99 said:
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
Click to expand...
Click to collapse
Touchnooter has adb enabled over wifi (If i'm not wrong), so you wouldnt have to enable it again, go directly into the OTA.

TJay99 said:
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
Click to expand...
Click to collapse
You should be good to go if you install jdk + android sdk.
With TouchNooter 1.6.24 you should allready have adb access enabled via wifi.
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Interesting, I need to take a closer look at the update process some day

Yep, same behavior with mine.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse

TJay99 said:
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
Click to expand...
Click to collapse
That is my guess. Without knowing for sure you're left with two unpleasant options:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
2) Your nook actually updates and destroys everything!
So you might take the time to "block" OTA updates as other have mentioned. But then there's option...
3) You go through the rigors and just get the 1.1.0 firmware upgrade over and done with, rerooting afterwards.
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?

This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Kralik said:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
Click to expand...
Click to collapse

kunchers said:
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Click to expand...
Click to collapse
This is the best time to do that, finally got Gapps to work on 1.1 manully, at last!
If you wish to try it, here is my post:
http://forum.xda-developers.com/showthread.php?t=1346748

Kralik said:
That is my guess
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
Click to expand...
Click to collapse
A good and interesting guess.
There are intervals defined for the update checks, but maybe if it finds an update but are unable to apply it, it end up in a loop..

GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?

Kralik said:
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Click to expand...
Click to collapse
At this moment, fun, learning, and stability (for the moment it allways works, but I need more feedback from people that tried it) eventually, when I delete all the blob that Gapps dosn't need for them to work, and is installed on the default package of Touchnooter (Don't get me wrong I really think its a great method) you will get a cleaner install.
Anyway, If you don't want to go through all the steps you can use the new 1.1 Touchnooter to get root, and then use my GApps method.

[Q] internal memory i cant open....

OK the problem is whenever I try to access the internal memory on Acer a 500 my windows explorer stops working.and as I am new to this OS(Android) I can't find any sort of file manager on the device......the version of my software is 3.1 so in order to get working do I need to update my device...?.....

I would suggest updating. My A500 works much better with my PC once I put 3.2.1 on it. You'll also want to get a filebrowser from the market.
Sent from my HTC Incredible 2 using Tapatalk

michael kikon said:
OK the problem is whenever I try to access the internal memory on Acer a 500 my windows explorer stops working.and as I am new to this OS(Android) I can't find any sort of file manager on the device......the version of my software is 3.1 so in order to get working do I need to update my device...?.....
Click to expand...
Click to collapse
You also may want to root your device, and get full access to the internal.
Astro, ES File Explorer, File Manager HD are some good file managers for android.

i understand that rooting means some sort of unlocking thing how dose one do that n if I do so shall I do it after updating my system to ice cream sandwich or 4.0 something.I am so sorry for my ignorance in this matter as I have said I am relatively new to this OS Android..ty

michael kikon said:
i understand that rooting means some sort of unlocking thing how dose one do that n if I do so shall I do it after updating my system to ice cream sandwich or 4.0 something.I am so sorry for my ignorance in this matter as I have said I am relatively new to this OS Android..ty
Click to expand...
Click to collapse
Well, ICS will be the same way, in stock mode.
If you want to see the full internal of your Tab, well, you just have to root.
Granted, installing the correct drivers will allow you to see a portion of your internal memory, but to see all of it, you have to root.
Also, try installing a file manager on your tab. You should be able to see your Downloads folder at the very least.
But I will say, install some drivers. This is why your windows is flubbing the dub.

tnk u... I did download the drivers but it did not work that is why i posted it here..and also I will try to root it after the update..thank u fr ur help....one thing which one will be better the ics or any one of the custom rom's avail here....

I'm rooted, I run my own custom Rom (picture signature).
Also, I have the android Dev Kit installed on my windows 7 pc. Not to mention Java SDK. So I think I have all the drivers covered, one way or another.
I think the problem is with your drivers, and the fact you are not rooted.
Note that my rom is for an a501 and not an a500.
I can't tell you to root it, that is your choice. But, you will still need android drivers for it. Right now, your pc knows it's there, it just cant understand or see it.
---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------
ICS, will not be out for some time. Maybe 6 months. Who knows...

i want to root it so that I will get maximum out of my device.one last thing can u recommend any good rom for my device.I can provide all my device info...if that is needed ty

YOU need to read up on each rom, its YOUR choice and what I like may not be suitable for you... Look in dev section, the A500 has the lions share of cooked roms....

Moscow Desire said:
Well, ICS will be the same way, in stock mode.
If you want to see the full internal of your Tab, well, you just have to root.
Granted, installing the correct drivers will allow you to see a portion of your internal memory, but to see all of it, you have to root.
Also, try installing a file manager on your tab. You should be able to see your Downloads folder at the very least.
But I will say, install some drivers. This is why your windows is flubbing the dub.
Click to expand...
Click to collapse
You can view everything with es file explorer without root, but you do need it to write to or modify system files.

After goin tru lot of rom;s i finally decided to install one from (kjy2010) Honeylicious 3.2.1 Flash Glass....hope it will be better then the one iam using (3.0)....i wanted to thank him but i was not allowed to post in that page so thank you kjy2010 i hope to donate to your awesome work one fine day...and thank you all for replying and helping me with my problem.

Hit the thanks button on the bottom of his post, it will show him your thanks....

[Q] I require different Nook Color boot image & CM7

I have gone through this forum (and google search) for a few days now, and I run into a wall I haven't been able to solve.
I bought mine December 2011, came with OS 1.4.2.
1) It seems my nook requires different boot files than the regular ClockWork 3.x files have. I found 1 image with clockwork 5.5 that seems to have the right boot files! Question: Is there a 'new' generic image?
2) With that one, the assert .... = 'encore' fails, in other words the 'newer' nook is not an ENCORE device. - some folks suggested zip file is bad, but has nothing to do with it at all - I'm not afraid, so took out the assert after which CM7 installs, as does Gapps...zip (Unfortunately it doesn't boot android, but rather tries to factory reset itself, guess BN doesn't like us making these into ANDROID devices)
3) So I wiped factory reset which fails at some point. Keep getting the ADOBE loader on boot-up. There must be a file somewhere I cannot reach that prevents me from deleting the files that bootstrap itself into factory reset. (But since I wiped everything else, it won't factory reset anymore LOL)
4) Came across the option of making a bootable SD Drive with CM7 on it. However, cannot find a bootable image that I can use, plus am very afraid the CM7 mod won't work on mine.... Not sure, will try anyway.
However, would like to try this, I can sacrifice 500MB and keep the 15GB that is left.
5) I started this.... not because I have no android tablet ( we have two) but after 6 months of my daughter complaining that her favorite games are not available on her nook.... I tried to 'side-load' Google-Market on the machine, which didn't work... (probably because of the same 'newer version OS') after which I decided to go all the way...
Anyway, I will muddle on, but need a bootable image for my newer nook, and probably a hint as to what my assert value (and with that my CM7 version) should be. Only reference I found so far was assert ..... = 'blaze' but that didn't work either.
I would have posted this in a thread for an SD bootable CM7 but it wouldn't allow me for being too new... Hey I'm a noob and proud of it
Thanks for anyone who can help.
James

Are you sure you don't have a nook tablet? They have an assert value of acclaim. It looks just like a nook color, but silver. It also runs 1.4.2.
Sent from my Nook Color running ICS and Tapatalk

may need to change mt user name
No I'm not certain at all, but this will give me a new angle.
Thanks for your reply I have read many of your posts with much interest and learned much.
I'll find a way to give you a thank you point...
Have a great rest of the wweekend.
James

OK Definitely need a name change
leapinlar said:
Are you sure you don't have a nook tablet? They have an assert value of acclaim. It looks just like a nook color, but silver. It also runs 1.4.2.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
OK Pressed thank you yesterday.
You were absolutely right, got the tablet completely transformed into Gingerbread 2.3.7 CM7 Mod! Woohoo.
Everything went smooth. I will (try to) post my procedure and all files I used, so anyone can do this easily.
Thanks again,
James

jjc_NookColor said:
OK Pressed thank you yesterday.
You were absolutely right, got the tablet completely transformed into Gingerbread 2.3.7 CM7 Mod! Woohoo.
Everything went smooth. I will (try to) post my procedure and all files I used, so anyone can do this easily.
Thanks again,
James
Click to expand...
Click to collapse
If you do post your procedure, do it on the Nook Tablet forum. It will be more useful there.
Sent from my NookColor using Tapatalk

[Q] Galaxy Tab 10.1, CM10 4.1.2 Jelly Bean Rom, A1 Kernel

I think the CM10 Jellybean rom 4.1.2. is stable enough for daily use. Packed with A1 Kernel 1.7.4b build pushes the tab's performance more, due to the GPU overclocking . The issue i found so far is that the MTP does not work, even when the MTP setting is clicked, updating the drivers, uninstalling the device from device manager, and installing again. When re-flahsed using the default CM10 4.1.2 Beta4, MTP is working fine again.
Anyone has any fix for this ?

voltairejohn said:
I think the CM10 Jellybean rom 4.1.2. is stable enough for daily use. Packed with A1 Kernel 1.7.4b build pushes the tab's performance more, due to the GPU overclocking . The issue i found so far is that the MTP does not work, even when the MTP setting is clicked, updating the drivers, uninstalling the device from device manager, and installing again. When re-flahsed using the default CM10 4.1.2 Beta4, MTP is working fine again.
Anyone has any fix for this ?
Click to expand...
Click to collapse
hi dude
I've had your problem but I do it.
do this:
1 put your tab on MTP mode in storage in setting
2 attach ure tab on computer
3 go Control Panel\Hardware and Sound\Devices and Printers you can find your device.
be lucky dude
if have Q ask Im at your service
sorry because of my bad english

omid.bibak said:
hi dude
I've had your problem but I do it.
do this:
1 put your tab on MTP mode in storage in setting
2 attach ure tab on computer
3 go Control Panel\Hardware and Sound\Devices and Printers you can find your device.
be lucky dude
if have Q ask Im at your service
sorry because of my bad english
Click to expand...
Click to collapse
Hi There, thank you for your time in replying. Appreciate that. I did check the control panel , printers sounds setting, but all i can see is the Samsung Android Device (modem) nothing else. There are no undefined hardware in my control panel.
I do transfer right now file to and from my 10.1 through Wifi Explorer Pro. A bit slow, but it works.
Probably, i will flash a CM10 kernel, or revert back to the CM10 Beta 4 and wait for A1 Kernel probably to notice this issue.

voltairejohn said:
Hi There, thank you for your time in replying. Appreciate that. I did check the control panel , printers sounds setting, but all i can see is the Samsung Android Device (modem) nothing else. There are no undefined hardware in my control panel.
I do transfer right now file to and from my 10.1 through Wifi Explorer Pro. A bit slow, but it works.
Probably, i will flash a CM10 kernel, or revert back to the CM10 Beta 4 and wait for A1 Kernel probably to notice this issue.
Click to expand...
Click to collapse
By the way, anyone who can post to XDA on A1 kernel p7500 regarding this issue? My account is so weak it's only limited to Q/A Forum and general facts.

Issue with Play Store - Jelly Bean ROM
Hi
First off, I flashed my GTP7500 Galaxy Tab 10.1 with the new JB ROM after having had issues with getting applications to update/download from Play Store. I tried everything before flashing, from deleting and re-adding my back-up account, to flushing the app cache and downgrading the Play Store app to an earlier version. Nothing worked. Then when I flashed the new JB ROM, I accidently used the WiFi-only version. Everything worked fine, I just didn't have 3G. So I went back to the drawing board and flashed the correct version, using TWRP's version. Now, I am back to square one with Play Store not downloading/updating any apps. The progress bar just scrolls, and then eventually times out. My only question is, why would it work without any hassles in the Wifi-ONLY version, but not in both the official release of ICS and un-official JB? Could someone please help me with this, as I have absolutely no more answers left
Thanx

Gallery issue
I have an issue, the gallery cant detect pics that were moved using root explorer.
So this is what happened:
1. downloaded some images via browser (all downloaded images are in download folder in root)
2. grouped all of them in a folder via root explorer (all downloaded images are in download/foldername
3. opened the gallery, it cannot find that folder, and shows a album called "download" with the pictures except they are all blank(black icons).
Can anyone verify this and if anyone has a fix for this pls tell me thx.
I wanted to use multilive wallpaper so i need downloaded pics grouped for separate homescreens... not using gallery will cause slow downs...

polaris office does not work
y doesnt polaris office work on this rom?

[Q] Problem Upgrading to 1.2.1

Hi there
New to all things Nook - Just bought my NST yesterday for the bargain price of £29 and am well chuffed. I have had Android phones for 3 years though and always rooted bejaysus out of them so I understand rooting, CWM, etc fairly well.
The NST is currently on 1.2.0 firmware, so having read up in this forum I DLd the 1.2.1 firmware update, NookManager and NGTAppsAttack to install in that order.
However, I have followed the instructions on B&Ns website to the letter but I can't get the 1.2.1 update to install. To be clear, I Dl'd the firmware on my Win7 PC, didn't open it at all but connected the NST by its USB cable and copied the zip file straight in to the root directory (as shown in Windows Explorer), did a safe eject and then set the nook to sleep mode. Two hours later - Still on 1.2.0.
I then tried to let it auto-update by leaving it sleeping overnight conneted to my home wifi network. - Still on 1.2.0
Any other way to force the update? I may be being stupid here and the update isn't crucial (?or isn't available for UK devices?) but I have learned to follow instructions carefully over the years and I wanted to get the latest firmware in so that I only needed to root it once!
I can boot NookManager from my SDcard (and I've already done a full backup). I was wondering if I rename the firmware file to factory.zip and use NM to do a factory restore would that work? Or is the update file a different beast that would brick the reader if forced on in this way?
All advice welcome. If I can ignore 1.2.1 and just proceed with rooting then - happy days - I'll just fire ahead and do that.
But have I been stupid and missed a basic step or what? Enlighten me please, someone!: silly:

I've also got the same issue. The update doesn't happen and if you reconnect to usb the update file is gone.
---------- Post added at 12:35 PM ---------- Previous post was at 11:43 AM ----------
I've copied the file to the root and then ejected the nook and plugged it back in straight away and the file is gone already!

i have the same problem

BelfastLad said:
Hi there
New to all things Nook - Just bought my NST yesterday for the bargain price of £29 and am well chuffed. I have had Android phones for 3 years though and always rooted bejaysus out of them so I understand rooting, CWM, etc fairly well.
The NST is currently on 1.2.0 firmware, so having read up in this forum I DLd the 1.2.1 firmware update, NookManager and NGTAppsAttack to install in that order.
However, I have followed the instructions on B&Ns website to the letter but I can't get the 1.2.1 update to install. To be clear, I Dl'd the firmware on my Win7 PC, didn't open it at all but connected the NST by its USB cable and copied the zip file straight in to the root directory (as shown in Windows Explorer), did a safe eject and then set the nook to sleep mode. Two hours later - Still on 1.2.0.
I then tried to let it auto-update by leaving it sleeping overnight conneted to my home wifi network. - Still on 1.2.0
Any other way to force the update? I may be being stupid here and the update isn't crucial (?or isn't available for UK devices?) but I have learned to follow instructions carefully over the years and I wanted to get the latest firmware in so that I only needed to root it once!
I can boot NookManager from my SDcard (and I've already done a full backup). I was wondering if I rename the firmware file to factory.zip and use NM to do a factory restore would that work? Or is the update file a different beast that would brick the reader if forced on in this way?
All advice welcome. If I can ignore 1.2.1 and just proceed with rooting then - happy days - I'll just fire ahead and do that.
But have I been stupid and missed a basic step or what? Enlighten me please, someone!: silly:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40993706&postcount=385
- Downgrade to FW 1.1
- Update to 1.2.1
- Root
In that order.
Rooting process block all future updates.

Thanks. This has worked for me.

Are there any significant differences between 1.2.0 and 1.2.1? Does 1.2.1 only work with the US ebook shop?
Sent from my GT-I9100 using xda app-developers app

cowbutt said:
Are there any significant differences between 1.2.0 and 1.2.1? Does 1.2.1 only work with the US ebook shop?
Don't know about differences - None visible to me but update as per osowiecki's instructions has worked perfectly and I'm just rooting now.
Many thanks to all.
Click to expand...
Click to collapse

cowbutt said:
Are there any significant differences between 1.2.0 and 1.2.1? Does 1.2.1 only work with the US ebook shop?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
The biggest change I've heard of is adding european wifi channels 1-13. There's a (very) little bit of discussion about other changes here.

Just realised that the downgrade to 1.1.0 -> upgrade to 1.2.1 linked above has converted my Nook to the US 1.2.1 firmware. Apparently B&N UK website now has a 1.2.1 FW update which will work with the £29 UK NSTs if you want less hassle!
Not sure of any other FW issues - poss wifi channels as another post states. More importantly, I must compare UK and US prices on books and see if I want to change back or not.....
Seriously, I presume my change might give grief if I need to do a warranty return to Curry's - but then again - what are the odds of the average sales assistant in Curry's knowing the difference??

Was also having this problem but looks like I was trying the US version of the update.
For those looking for the UK update you can find it here:
http://uk.nook.com/support/nook-simple-touch-software-updates
Thanks BelfastLad for pointing me in the right direction.

For those still having issues when using the correct firmware, try leaving your NST/G plugged in until it reboots after you've dragged the 1.2.1 firmware .zip over to it. Make sure you eject the NST/G from your computer, just leave it plugged in.

I finally managed to install the 1.2.1 update after downloading the uk version and making sure the zip file didn't have (1) or (2) next to it as I had downloaded the file a few times.