N80: Feeds Client bug and possible solution

Hi everyone,
I've found what appears to be a bug in Feeds Client V. 3.0(0529) in my Nokia N80 Internet Edition.
I've added a couple of feeds when connecting to a WLAN, but when I tried to read those feeds again, this time away from that WLAN range, it didn't even gave me the choice of network connection: it just tried to go back to the same connection without asking.
I deleted that network's entry in Tools->Network->Access points. Because I only had two feed address saved, I've also deleted them.
But this time the phone didn't even allow me to go into the Feeds folder!
What appeared to solve the bug was something like this.
1) Create a new bookmark with the feed address (e.g. Google News). You can delete it later.
2) Start browsing the feed. Your browser should ask what is the network to use, if you've configured that way.
3) You get the feed list, hopefully. If you choose Back, the mobile will show the feed list you've saved (in my case, only the feed I'm reading because I've previously deleted all of them).
This seemed to do it. If you want to be sure, save the new feed in the Feeds folder again, and delete the previous feed.
Hopefully this will allow you to go around the bug and let the Feeds Client think it should access the network connection you want. The problem is, it still only lets you read the feeds through the network connection you've selected!
Regards,
J.B.

A better test would be to move one at a time (Desktop folder) until you find the codec causing the trouble.
Two of my guesses:
Out of date DivX
VLC plug-in

Similar Messages

  • Captivate 7 - The Exit Bug and a Solution

    Hey Everyone,
    I wanted to take a second and share some good information I found in regards to SCORM and the Exit functionality in Captivate 7. Below is the blog post that shows how to make the Adobe Exit functionality "SCORM Compliant" and solved my issues when uploading my project and getting them to exit. Hope this helps
    Captivate 7, Exit Bug and a Solution
    Several of our Inquisiq R3 users have alerted us to the fact that courses developed with Captivate 7 published to HTML5 and SWF do not close properly when using the “Exit” button, forcing the user instead to manually close the browser window by clicking the “X” in the upper-right corner of the browser window.
    Through our investigation into this issue, it appears that the process that Adobe has implemented when clicking the “Exit” button is to simply attempt to close the content window and rely on the LMS to capture and commit the session data. Nowhere did we see that the content was actually calling the “LMSFinish()” [SCORM 1.2] or “Terminate()” [SCORM 2004] methods in the LMS’s SCORM API to commit the lesson data to the LMS as required by the SCORM specification.
    Adobe uses their own defined function, “DoCPExit,” to close a lesson window.  This method contains a “window.close()” call and additional logic to “bubble up” the command through the frame parents (if they exist and also contain the “DoCPExit” method - presumably because they would also be Adobe-published content files within your package).
    There are several flaws to this approach.
    By not calling “LMSFinish()” or “Terminate(),” the content is, by definition, not SCORM conformant.  Part of the minimum requirements for conformance are that the content calls the initialization method “LMSInitialize()” in SCORM 1.2 or “Initialize()” in SCORM 2004 and the  termination method “LMSFinish()” in SCORM 1.2 or “Terminate()” in SCORM 2004. The LMS is not required to clean up the data left behind when the content fails to make this call. So if your LMS doesn’t take this additional step (of setting ‘LMSFinish’ or ‘Terminate’ if the lesson does not), your data will be completely lost…i.e. no record of you taking the lesson will be recorded.
    The call to close the browser window will fail if the LMS is running the content within a frame or iframe. Since the SCORM specification allows content to be launched in frames or iframes (in addition to new browser windows), lessons need to be able to accommodate this scenario. Even with the “bubble up” logic, once the call reaches the top most content window, and the next parent window in line is the LMS container page, the call will no longer be passed and a “window.close()” call will be fired within the framed page.  When this call is made, nothing will happen as a framed page cannot close the browser window using this command. Through our investigation, we’ve learned that at least 4 other well-known LMSs have experienced this particular issue.
    Ironically, the solution that we’ve discovered is not only SCORM conformant, but also very simple and follows what we would consider to be SCORM “best practices”.  The foundation and logic for the solution is already contained within the published Captivate files (and it is the same solution whether you publish to SCORM 1.2 or SCORM 2004).
    We simply modify the “DoCPExit” method that is contained within the “Utilities.js” file to call the “Finish()” method.  Just replace all the code appearing between the “{“and the “}” as you see here:
    function DoCPExit(){     Finish();
    The “Finish()” method that we have inserted is, as mentioned, already contained within the published Captivate files and contains the logic to properly set the exit parameters and correctly identify whether the content is SCORM 1.2 or SCORM 2004; it will therefore make a call to the correct close method (“LMSFinish()” or “Terminate()”) accordingly.  Once the LMS has received this command, it should take care of removing the content properly, leaving no need for any “bubble-up” logic or window close calls within the content code.
    Overall, if the lessons you develop with Captivate 7 work as expected and required in your LMS, there is no need to implement this change. However, if your lesson’s Exit button is not working as it should, and/or you are losing progress and status data when closing the lesson, the fix described here should resolve all those issues.
    The biggest issue here is that since we’re changing published code, the next time you update and publish that same Captivate project, you have to remember to change that published function code AGAIN, as Captivate will simply publish the default code.
    We have been in touch with the Captivate team to discuss this problem and they are investigating. We would hope a patch to address this flaw would be released in the near future
    All credit of this fix goes to http://blog.icslearninggroup.com/2013/10/captivate-7-exit-bug-and-solution.html

    Try clearing out your project cache (Preferences > General > Clear Cache) then republish using the option to Force Republish All Slides.
    If that doesn't resolve the issue, you may be seeing the early stages of project file corruption.  Check the suggestions in this post about troubleshooting issues where you may need to copy all slides to a new blank project shell to try and strip out corruption:
    http://www.infosemantics.com.au/adobe-captivate-troubleshooting/basic-troubleshooting-tech niques

  • Why does Apple not give a list of error messages and possible solutions? I have the (-54) error continually that has suddenly appeared and cannot find a solution, even though other users seem to have the same problem.

    Why does Apple not give a list of error messages and possible solutions? I have the (-54) error continually that has suddenly appeared and cannot find a solution, even though other users seem to have the same problem.

    This is a user to user forum.  Apple isn't here and won't answer you.  You need to contact Apple directly.  You can use the Contact button at the bottom of the screen.

  • Hi everybody, adobe muse does not start at the first attempt after installation. know the reason and possible solution? (on iMac 27 retina - latest edition)

    Hi everybody, adobe muse does not start at the first attempt after installation. know the reason and possible solution? (on iMac 27 retina - latest edition)

    Hi
    Are you still experiencing the issue or is it fixed now?

  • Aperture 3 Hanging after upgrade and possible solution

    In advance, sorry for the long post:
    As many have reported already, I was also a user of Aperture staring at the beachball and finding my computer hanging completely up to the point I was ready to give it flight lessons for free. I might have done this to my MacBook Pro if I was not leaving for an overland trip to Capetown from the Netherlands in a Toyota Land Cruiser in 2 days. If you want to read about the trip: www.africaminded.com.
    How did I solve the issue in my case? I hope it helps some of you.
    *My aperture setup*
    Before you go through all the steps below let me explain how my Aperture workflow was set up:
    1. Projects in Aperture correspond to folders on my harddrives. The project folders in Aperture contain reference files to the fils on my harddrives. The folders on my harddrives have the same name as the projects in Aperture. Using the same name does not really matter much, except I find it easier to find images from aperture back on my harddrive without having to use aperture to find the images.
    2. I do not have the images imported into an Aperture library because this alllows me to access the images with other applications than Aperture (Photoshop etc).
    Preparations:
    *Actions I took before I started with a clean Aperture:*
    1. Launch Aperture with holding the shift key. This defers Aperture from processing images in the library. Tip from Apple website: http://support.apple.com/kb/HT3805
    2. Show Keywords HUD and export the keyword list in a separate file onto the desktop
    3. Create folder on desktop called "Exported Projects"
    4. Drag project by project to the just created folder. Yes this is a painstaking long process and one I would have liked avoided but I did not find any other solution and needed one. Luckily I only had 44 projects to go through.
    5. Close Aperture
    6. Delete the user preferences
    1. Quit Aperture if still running.
    2. In the Finder go to ~/Library/Preferences. (The tilde "~" represents your Home folder).
    3. Remove the "com.apple.Aperture.plist" file from the Preferences folder.
    7. Move the user created presets, keyword lists, and so on...
    1. Quit Aperture.
    2. In the Finder, go to ~/Library/Application Support/Aperture.
    3. Move the contents of this folder to your Desktop
    8. Delete your old Aperture Library or move it to another harddrive. If possible do not empty the bin of your computer (just in case you need the library again - I did not after following all steps below).
    9. Reinstall Aperture; Note: Make sure that you have your installation discs nearby before starting this.
    1. Open the Applications folder.
    2. Drag the Aperture application to the Trash.
    3. Insert your Aperture installation disc and install Aperture.
    4. When finished, choose Software Update from the Apple () menu to update your software to the latest version.
    *Now your computer has a clean install of Aperture*
    1. Launch Aperture
    2. Show Keywords HUD and import the keyword list that you saved in a separate file on the desktop
    3. Move the following files back into ~/Library/Application Support/Aperture:
    1. Adjustment Chain Presets.plist
    2. FileNamingPresets.plist
    3. Metadata Presets.plist
    4. MetadataSets.plist
    4. Close Aperture and go to
    Following the steps below allows you to keep all you metadata and rating as well. It is possible in Aperture 3 to read and import sidecar files containing metadata but this will not include the rating! So if you want to keep your metadata and your ratings, follow the steps below:
    (*A) Importing Project*s
    1. Launch aperture
    2. File > Import >Library / Project
    3. After selecting the exported project you want to import, confirm you want to merge the project
    4. Which library should be used when a conflict is detected? Choose current library (and not the library/project you are importing).
    5. Let Aperture take its time to merge the projects (depending on the size of the project you import this can take longer and you might see the famous beach ball for a few seconds). In the beginning it will look like Aperture does nothing or hangs again.
    6. After merging the libraries are completed Close Aperture.
    7. Launch Aperture and immediately select Window > Show Activity from the menu. Let Aperture process new previews (this should start automatically after opening Aperture). Show activity will give you an idea how far Aperture is when processing the images so you don't have to stress and stare at the spinning wheel in the bottom left corner.
    8. After the processing has finished Close Aperture again to save the new previews and share them with iLife and iWork.
    9. Repeat the above until you have imported all your projects. Remember to keep repeating step 6 to 9. This allows you to find out which project contains corrupted images or is corrupt and to deal with it separately. Importing all projects at the same time and then processing all pictures at the same time does not give you the opportunity to figure out how to get rid of the beachball!
    *(B) What to do when images are corrupted in a project?*
    In case you imported a project that was corrupted or contains corrupted images that causes Aperture to hang completely and slow down your computer to a complete halt:
    1. Force quit aperture
    2. Reopen aperture and immediately press the shift key after launching the program. Pressing the shift key stops Aperture from rendering/processing the images you imported from the "corrupted project".
    3. Select the last imported projected (the one that contains 1 or several corrupted images and gave you the beachball again).
    4. Delete the project and empty the trash in Aperture as well. Do not delete the master files associated with you referenced images.
    5. Move the corrupted project into a folder called "Corrupted projects". Do not throw the corrupted project away - we will deal with this one later. Just make sure they are not part of the main library you are building.
    6. Quit and launch aperture. Aperture should not be processing any images anymore as you already completed that with step 8 above.
    7. Complete the importing of your projects following the exact steps above, skipping the corrupted project.
    Ps. In my case I found 1 project with corrupted images.
    *(C) What do you do with the corrupted projects?*
    1. Make sure that Aperture is not yet running.
    2. Double click the corrupted project and press the shift key to defer the processing of images. This will launch aperture and treat the project as an individual library.
    3. Select all thumbnails and export masters to a new folder and select "Create IPTC4XMP Sidecar File" in the pulldown list where it says "Metadata" in the export window. You should now have all master images of this corrupted project and the sidecar files containing the metadata of these images in the same folder.
    4. Quit Aperture
    5. Press the Alt-Key/Option-Key and Launch Aperture. Aperture should now ask you which library you want to open. Select your Main Library that contains all the projects you imported following step 1-9 above.
    6. Create a new project for the images you are going to import from step 3 of section C.
    7. Import the images and move them to where you want them to have. Aperture should import the non-corrupted images including their metadata (as the sidecar file of these images is in the same folder as the images). All you have lost in this case is the rating and possibly the adjustment of these images. The IPTC data will be imported by Aperture in step 9 Section C. You could survive having to redo the rating manually. Redoing the adjustments is a bit of more work, sorry.
    8. Quit Aperture.
    9. Launch Aperture with pressing the alt-key or option-key and select your main library as in step 5 and select "Show Activity" from the menu. You are now back into step 7 of section A. Complete step7, step 8 and 9 of section A.
    *D. Congrats*
    1. When all projects have imported correctly delete the projects from your harddrive to gain space.
    2. Delete the temporary Aperture library created in section C step 2.
    3. Re-install plug ins that you might have moved in the preparation phase (if possible 64-bit versions if available)
    Congrats. You now have a completely new and well functioning new Aperture 3 library that offers you all the new features and is very fast I should say. My machine: MacBook Pro 2.93GHz with 4GB Ram.
    After you think you can trust Aperture again empty your bin to gain space on your computer.
    How long did this take me? All in all about 3 days but not full time luckily. How many real corrupted images? None - something else in the project data was messing everything up.

    WOW!
    I'm REALLY impressed by your exhaustive and detailled description!
    How long did it take to write? Sure longer than the import itself...
    Thank you so much. I got a working import of Ap2 lib before but your description have me various hints for handling problematic or faulty projects.
    Matt

  • IChat A/V, error -8 and possible solutions

    Ok as Ralph, RJ know I've had tons of issues for 18+mos with Tiger and iChat. In the past few weeks I've had some successes.
    I was using my Linksys WRT54GS 1.1 with Sveasoft and it never really worked. So I tried a new beta with better UPNP and still no go. So then on a lark I tried the D-Link 624 that verizon gave me with FIOS, no luck. Then I saw on apple's support pages that I needed to turn off uPNP. So I did and it worked!
    Tried other cases, all worked.
    Skip ahead some time, things stopped working. Turned out to be ChatFX, for some reason, causing issues. I was also able to talk to my friend in Geneva for the first time.
    Now I find a HyperWRT firmware for the Linksys at http://thibor.co.uk/ so I install that, and give it a shot. Doesn't work. Then I turned off UPNP and it worked with RJ!
    So I tried with Janet, worked! Then tried with tim, no go. he has a d-link DSL modem/router/wifi in Canada. Turned off his port fowarding, turned off UPNP, still didn't work. Then I had him uninstall ChatFX and it worked!
    Then we tried adding the two apple test users, and that didn't work. No connections, or really slow, or crash ichat. Then I switched from WiFi to Ethernet and it worked!
    So here is my summary:
    * FIOS D-Link 624, no port forwards, no port triggers, no UPNP - Works!
    * Linksys WRT54GS 1.1 with HyperWRT - Fresh install, no port forwards, no port triggers, no UPNP, works!
    * Ethernet is better than WiFi for 3+ people
    * ChatFX seems to cause connection issues. I can't disparage it, but I had two occasions in two days where disabling it stopped -8 issues. Also removed Chax. Its possible these great extensions are just confusing iChat for some of us.
    * Always, always power cycle your router after changing port forwardig or uPNP settings. Routers are notorious for keeping old routes until you power cycle them.
    * Also used my Vonage phone during these tests, works ok. I had Vonage move the SIP port of my Linksys Router box to a port other than 5060 or 5061.
    I need a couple of weeks to verify all of these settings, but its a step in the right direction. I'm especially surprised it all works wiht no port fwding, both outgoing and incoming calls.

    HI Steven,
    I was looking for a list of improvements when I said that.
    Many devleopers post this sort of info so you can see how the progress was made.
    However found this http://www.scriptsoftware.com/press/index.php?action=show_product
    Press release.
    1:14 AM Saturday; August 12, 2006

  • MacOS X + NX Client, bugs and keyboard

    I have some problem with MacOS X Client to freenx terminal server.
    1) Keyboard layout switching.
    Client: MacOS X 10.5.5 (mac mini + system upgrade), NX Client 3.2.0-13, X11 from MacOS X distribution.
    Server: Ubuntu 8.04.1, freenx 0.7.2, RU(winkeys) + EN, i trying to set layout and model macintosh and apple, but there is no result. Keyboard switching not working. With windows client with NX Client 3.2.0 all ok, but with mac, witch same options - only EN.
    2) In froat window mode (NX Client -> Desktop -> Custom), when a clicking buttons and menu options, X11 windows jumping down for 10-20 pixels. Windows runs down under the panel and viewport.
    Please help with this problems.

    We've recently run into an issue related to this. We found that it was related somehow to Firefox. If one looks inside of
    /Applications/Cisco/Cisco AnyConnect Secure Mobility Client.app/Contents/MacOS/ there are symlinks to Firefox libraries:
    $ ls -lntotal 1800-rwxrwxr-x  1 0     80  891232 Aug  3  2012 Cisco AnyConnect Secure Mobility Clientlrwxr-xr-x  1 1001  80      60 Jun 13 15:57 libmozsqlite3.dylib -> /Applications/Firefox.app/Contents/MacOS/libmozsqlite3.dyliblrwxr-xr-x  1 1001  80      55 Jun 13 15:57 libnspr4.dylib -> /Applications/Firefox.app/Contents/MacOS/libnspr4.dyliblrwxr-xr-x  1 1001  80      54 Jun 13 15:57 libnss3.dylib -> /Applications/Firefox.app/Contents/MacOS/libnss3.dyliblrwxr-xr-x  1 1001  80      58 Jun 13 15:57 libnssutil3.dylib -> /Applications/Firefox.app/Contents/MacOS/libnssutil3.dyliblrwxr-xr-x  1 1001  80      54 Jun 13 15:57 libplc4.dylib -> /Applications/Firefox.app/Contents/MacOS/libplc4.dyliblrwxr-xr-x  1 1001  80      55 Jun 13 15:57 libplds4.dylib -> /Applications/Firefox.app/Contents/MacOS/libplds4.dyliblrwxr-xr-x  1 1001  80      58 Jun 13 15:57 libsoftokn3.dylib -> /Applications/Firefox.app/Contents/MacOS/libsoftokn3.dylib
    So as a simple confirmation we were able to remove Firefox and have AnyConnect connect fine. As a more permanent workaround we replaced the above symlinks with 0 byte files and we were able to have our cake (AnyConnect connecting) and eat it too (Firefox installed as well).

  • MMC Password Problem for E71 and Possible Solution

    Hi,
    I wanted to share with you the following (took me some time to figure it out...).
    On E71 there is a possibiity to remotely lock the phone via an SMS with a specific code you can define. Now if you didn't protect the MMC with an own password before, after the remote lock, the MMC will become protected and the password for it is the SMS code you used for the remote lock. Note that the SMS code doesn't have to be the same as the code with which you unlock the phone itself after the remote lock (except of course if you define them both to be the same).
    I hope it helps, at least for some cases. Funny that this is not described in any manual or whatsoever (at least I couldn't find it)....
    This was tested on the E71-1 (33), RM-346, product code 0558786), FW Version 100.07.76, with an original Nokia 8GB microSD-HC MMC memory card.
    Cheers,
    dubi
    Solved!
    Go to Solution.

    I had this same problem. My memory card suddenly getting corrupted, but I managed to solve it. I believe the source of the problem is the Remote Lock and the Device Lock of the unit. I have an E63 unit (same as E71).
    The problem started after I enabled the Device Lock and Remote Lock of my E63 unit. After a couple of hours, I tried to manage my apps in the memory card. To my surprise, it's corrupted! I didn't panic because I believe I could retrieve the files with my PC. But when I inserted my memory card to a memory reader into my PC, the card is unreadable. I had a feeling that the card is really corrupted. But how? I just got this unit almost a day ago. I didn't do anything odd. I'm an OOP-Design Patterns oriented programmer so I'm not newbie when it comes to best practices.
    As I searched the web, I found that there are cases too that had this same exact problem. And their guess is also the Device Lock.
    So what I did is I disable the Remote Lock and the Device Lock. I checked my memory card and it's still corrupted!
    So, I turn off my unit and turn it on again, it's still corrupted!
    I removed the memory card while the unit is on (Make sure you use the remove memory card feature of your unit!!!) and then reinserted the card, and it worked.
    In summary, to solve this memory corrupted problem. Try disabling the Remote Lock and Device Lock. To disable the Device Lock, revert the password to "12345" (Do not type the quotes). Remove the memory card (Use the remove memory card feature of your unit!!!). Re-insert card and problem fixed.

  • Workaround and possible solution to CONSTANT STATIC

    The workaround is disabling your driver then re-enabling it.
    Go to control panel->sound
    Click speakers, properties
    Click properties next to X-fi logo
    If windows security is on, click change settings, continue
    Click driver tab
    Click disable, wait while windows disables your sound card
    Click enable
    I can not confirm the solution, but turning off the windows startup sound seems to have worked for me.
    Go to control panel->sound
    Click sounds tab
    uncheck "Play Windows Startup sound"
    Someone please test this to confirm if this works or not.

    Well, after a couple days of playing games on the computer, another problem showed itself. Occasionally, when I would boot, the sound wouldn't work at all and I would get strange intermittent static sounds from my speakers.
    My new fix that has worked every time for me is to make sure my speakers are ON when I turn on the computer. If I forget, I get intermittent static and I have to reboot.

  • Erratic shutdown, AHT diagnosis and possible solution

    I just wanted to post this as I have seen others who have had similar experiences during G5 shutdown.
    It seems that during shutdown, I wait for the screen to blank and do its usual thing, and eventually power off. Occasionally, it either takes unusually long to do so, or does not shot down at all. Then, I have to manuallly power it off with the I/O button. Doing an AHT Extended test, I received the message:
    Mass storage error, 2STF/8/3:B (lower)
    This is the OEM Maxtor which I moved to the lower bay, while running a 74GB Raptor in the upper.
    Note, performing the quicker AHT "passed" the mass storage, so I was intrigued what the situation was.
    I reset the PRAM, rebooted, and initialized another AHT Extended test. This time, the lower bay storage in question was labeled as "passed". Just the same, I backed everything up on an external drive.
    I will also follow up with inspection of the drive cable, as I have a spare, but I wanted to relay this find to anyone who may be experiencing similar events with their G5.
    Last, at startup, there are two barely audible "pops", usually close to one second apart. Now, they are further between (1.5-2 sec.) Does this indicate anything I shoudl be aware of?
    Thanks.

    Thanks for your thorough post. I too need to use BTMM on almost a daily basis for my job, and it has fallen short countlness times. I too have taken great pains to check all of the typical trouble shooting steps within iCloud and in the Apple keychain on each Mac etc, but after the latest rounds of system updates from Apple a few weeks ago to Mountain Lion, BTMM on one of my Macs is completely broken and unusable. I would concur that if you need remote access for "real" mission critical use, just bite the bullet and pay for a service like LogMeIn. You won't regret it and you will get real software support.

  • Need to find all Bugs and QF created for 8.0.0.13

    Hi all,
    I kneed to know how to find all bugs and possibly patches/QF created on top of 8.0.0.13 for bugs found in 8.0.0.13 after its release on Jan 2012. This is for my Customer that needs to know if they have to plan some QF in proactive way.
    I can access to Internal Support Portal, so if there is any place where Support people can go I can access.
    Thank you in advance
    Chiara Scarafiotti
    ACS TAM

    Hi radhika,,
    This the the way to go..just modify the col according to your table col names...
    You can do a CONNECT BY query without a START WITH clause to link every node with each of its ancestors.
    Getting the total is just a matter of GROUP BY.
    SELECT emp_id, employee_name, manager_id
    , CASE
              WHEN COUNT (*) = 1
              THEN 0
              ELSE COUNT (*)
         END               AS cnt0
    ,     COUNT (*)      AS cnt1
    FROM employee
    CONNECT BY emp_id     = PRIOR          manager_id
    GROUP BY emp_id, employee_name, manager_id
    ORDER BY emp_id;
    output:
    Output:
    . EMP_ID EMPLOYEE_N MANAGER_ID CNT0 CNT1
    1 Mark 0 5 5
    2 John 1 3 3
    3 Stella 1 0 1
    4 Karen 2 0 1
    5 Andrea 2 0 1
    I made this a bottom-up query (going from each node to its ancestors) rather that a top_down query (node to descendants) because you can't GROUP BY CONNECT_BY_ROOT.
    In your description you implied that each node would be counted among its own descendants, but in the sample output you had 0, not 1, as the count for all the leaves, that is, managers counted as their own descendants, but non-managers did not. The column called count0 in the query above does that; the column count1 counts each node as its own descendant, leaves included.
    Regards
    Onenessboy

  • Adding reminders to my calendar items is no longer an option after the software upgrade.  I also can't get to day and week view, only month view.  What's a possible solution?

    Adding reminders to my calendar items is no longer an option after the software upgrade.  I also can't get to day and week view, only month view.  What's a possible solution?  I'm using Andriod version 4.4.2 with kernal 3.4.0.

        @MaloneTP
    Thanks for keeping me updated!  Do you see the screen options displayed in the following link: http://bit.ly/T2koBL for changing the calendar view options in Kies Air?  Also, let me know if you're able to add a Reminder by following these steps: http://bit.ly/T2l9dY.  Keep me posted.  Thanks!
    AnthonyTa_VZW
    Follow us on Twitter @VZWSupport

  • Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions?

    Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions? SecSigner is not responding.

    Well, I contacted SecCommerce about the issue, the response was, that I should sign the file later (afterwards). This is a solution, but not the best in my opinion.
    When I sign the document the SecSigner window/Java window appears and freezes. Adobe is not responding. I have to terminate Adobe because the program is not responding.
    I only found this support website, so I have realized that this is a User 2 User site, but it was a try to get some help.

  • I have just updated to the new iOS 6, and all my contacts have disappeared? Is there a possible solution to get them back?

    I've just updated to the new iOS 6 and all my contacts have dissappeared, is there a possible solution to bring them back, I really need them back. Thanks in advance.

    You tried clicking on "phone" then "groups" and "Show All Contacts"

  • I am having trouble connecting MacBook Pro (10.6.7) to Novell server. I get incorrect username and password message. I can connect worksations running 10.5 without any problem. Any possible solution? Thanks, Ned

    I am having trouble connecting MacBook Pro (10.6.7) to Novell server. I get incorrect username and password message. I can connect worksations running 10.5 without any problem. Any possible solution? Thanks, Ned

    Having the exact same problem with connecting ML and Snow Leopard machines to a Windows 8.1 machine. Oddly enough, connecting and copying to/from works perfectly from a Mavericks machine, despite the problems reported about Mavericks regarding the exact opposite. An old thread, but did you find a solution?

Maybe you are looking for