I recently upgraded my OnePlus One to Android 6.0.1 and while I can make phone calls I don’t have any network connectivity unless I’m on WiFi. The symptoms are;
Can’t send email,
No access any websites
Phone is not on a LTE network
This awkward fix, posted byrohitvermamech on the OnePlus Forums get’s LTE and networking working again:
Go into Settings > Mobile Networks > Access Point Names > Restore Defaults
The list should now have many many more choices of APNs. Choose the correct APN. Then go into Settings > Mobile Networks > Network Operators (make sure you are connected to WiFi) click “Choose Automatically”. Then turn Aeroplane Mode on and back off. Step 2:
VERY IMPORTANT! Restart your phone. Step 3:
Go into phone and dial *#*#4636#*#* and choose Phone Information. In Phone Information set the Preferred Network Type to LTE/GSM auto (PRL) [even if it says it already, do it again]. Turn off the radio. When the radio is turned off, turn the radio back on. Go down to the SMSC and hit “Refresh” and then “Update”.
Next, Liz’s first Android phone — a Virgin Mobile LG Optimus V. Keeping this as we can quickly reuse it for any visitors from Ireland and it’s a simple phone to use.
Next is my second Android phone a Samsung S2, I got this phone as the screen on my first Android a HTC Sensation cracked. I still have the HTC as I had plans to replace the screen but it’s hardly worth it at this point. The S2 was quite a step-up, lovely screen but it was missing a little something (this phone is being gifted to a friend for reuse), I hope he finds it better than today’s cheap Android phones.
Next up is my 3rd Android a Google Nexus 4, this was the first Android phone that really, really impressed me and is still a great device — fantastic camera too. I use this as my Irish Phone and it has my Irish SIM card in it and I’ll be walking around Ireland later this week with two phones as my US T-Mobile plan gives me free texts and data while in Ireland, and I can make free phone calls to any Irish phone after topping this up with 20 Euros.
The big yoke is my current phone a OnePlus One, fabulous device almost too big but at least I can read the text on the screen! 😉
Do you remember when a phone like the Nokia 6230 was the phone to have? I remember trying to get one of these for use in the US after seeing a friend’s phone in Ireland. At the time you could only get this model on the Cingular network and the things cost hundred. This phone was a classic for it’s time and it was durable and just worked and it’s form-factor is a classic from the period.
And these days you can an Android phone on Amazon for as low as $30 that’s more powerful that a 2005 era laptop. And you know, I still want this phone, the only problem is I can’t read the screen as it’s too small!
A user at work reported that ChemDraw suddenly started segfault-ing (crashing) on startup on his Mac. He’d opened a support ticket with CambridgeSoft and tried their suggestions, basically deleting every file associated with ChemDraw and reinstalling, which didn’t correct the problem.
I suspected that this was an issue with ChemDraw 12.0.2 (I’m using 12.0.1 and so are other CMLD members for the research lab I support). I suggested that he create a new user on his Mac and see if ChemDraw works correctly. I reasoned that ChemDraw was upgraded sometime in the past, and that there may have been some user preferences causing issues after upgrading, or some preferences settings were corrupted.
If a new user was able to use ChemDraw, then this would indicate that the installation is valid and working, and the issue is with the user’s preferences. If ChemDraw didn’t work, then the issue is probably with the installation, and we would need to install the application, and hunt down any remnants of the installation that may be in /Library or /System and then reinstall 12.0.1 to see if that would resolve the problem.
In this case, ChemDraw worked for the new user, thus indicating that the issue was not with the installation, but with the user’s setting. Deleting any files whose name started with com.cambridgesoft files in
Friday before I left work I kicked off the upgrade to Mac OS 10.6.3 on the MacBook Pro (MBP) I use at work. I’d already upgrade my personal MacBook at home (that I got a deal on at MicroCenter) and I didn’t have any observeable problems or issues and I was confident that I could upgrade and not bork my work environment.
When I arrived back into work on Monday it looked like the upgrade had completed. I logged into the MBP and my Bluetooth MagicMouse wasn’t working, and all bluetooth settings were unavailable and grayed out (both on the status bar, and in System Preferences).
I figured something had gotten out of sync during the upgrade and I thought a reboot would fix the problem. Rebooting didn’t fix the problem, but manually reinstalling the upgrade did solve the problem and Bluetooth is active and settings are accessible.
If you want to install Oracle’s SQL Developer on Ubuntu (or another DEB based system such as Debian) you can do one of the following:
Download the RPM package and install using rpm (not advisable).
Download the RPM package and convert to a DEB package using alien
Download the ZIP file titled “Oracle SQL Developer for other platforms” and manually install
Use the make-sqldeveloper-package to convert the ZIP file into a DEB package
I used the make-sqldeveloper-package, which is available for Debian and Ubuntu and it’s derivatives. However, the man page and the instructions are little unclear on how to use it. You need to download the zip file available at Oracle’s (and not the RPM file nor any of the other packages) and then use the make-sqldeveloper-package to convert it to a DEB which you can then install using the dpkg command.
This is preferable to using rpm or alien as you can more easily manage the package using Debian’s and Ubuntu package management tools, plus it will integrate SQL Developer into Gnome’s Menu System . Plus, when Oracle updates their version you can use make-sqldeveloper-package to create an updated DEB package and easily update the version you have installed. The procedure outlined below works on Ubuntu Karmic and should also work on any Debian version that has the make-sqldeveloper-package.
For me what happened is that X wouldn’t start properly and cause my Lenovo T400 to freeze and lock up. The laptop would boot but when X would start (when the login screen appears) I’d get a black screen with red lines at the top. To solve this I booted to runlevel 1, also known as failsafe mode. If your using a laptop with wireless, I suggest you connect directly to your router using a network cable, otherwise you may have to configure wireless manually (it’s not that hard).
When your system starts, select failsafe mode, on the next screen to appear choose the option to go to a “root shell with networking”.
Next remove the install ATI drivers and install from scratch the ones you need:
I started Firefox in safe-mode and now my WordPress editor is working fine. Methinks, maybe Google Gears was fecking up the editor somehow. Uninstalling Google Gears, exiting FF, restart in normal mode and see if my hypthosis is valid.
Yup, that might have been it. Some weird caching issues (even after clearing out the regular cache) or Google Gears was out of sync, and woudn’t sync properly, with the upgraded version WordPress. I’ll reinstall Google Gears at some point in the future and see what happens
I recently upgraded this WordPress installation from 2.7 to 2.7.1 using Dreamhost’s upgrade tools. However, the friggin’ feckin’ post editor is busted, at least in Firefox 3.0.6 on Ubuntu Intrepid. I can still use the QuickPress editor, which is only good for basic posts. If I want to add images or files, I’d have to manually upload them and link to them … anyways what a pain. If your planning on upgrading to WordPress 2.7.1 I’d suggest you wait a wee bit.
The problem I’m having is that on the “New Post” page, where the categories sections should be is instead an embedded (maybe an iFrame) of the WordPress Dashboard. When I try and type in the editor the pages changes to a near blank page with only the editor buttons showing. Grrrr …
I’ve tried the following steps (recommended on various sites and forums) to no avail:
Disabled all plugins
Disabled Google Gears
Cleared the browser cache
However, it works fine in KDE’s Konqueror browser. When I get the time, I may compare the generated HTML, and see if I can determine what’s causing the problem. Here’s a screenshot … sheesh now I can’t even insert a screenshot using Konqueror gotta do it manually. Look at the “Categories” section on the right-hand side: