Search
Hot Topics

Posts Tagged ‘psi’

Phoenix Auto Glass, Phoenix Windshield Replacement, And What You Should Know About Your Broken Windshield

Imagine driving in your car without it. Your windshield that is. The wind at your face, blowing through your hair while you fly down the road at high speeds. Sounds pretty neat huh. Fortunately the piece of Glass in front of you while you drive is one of the most important safety features of all cars today. Without it, stones, debris, weather, and other road hazards would do some serious damage to you and other passengers.What is a windshield you may ask. Well it is 2 pieces of float glass with a plastic laminate sheet sandwiched between the glass. The reason for this is safety. Windshields which hold an asa-1 rating can and must withstand impact ratings. That means that if a stone the size of a pebble hits your window, it will not penetrate the glass, even if you are going at high speeds. The main reason for windshield breakage is due to the stone getting between the treads of tires and are flung in the air bouncing off the road and into the glass. The glass depending on the angle of the hit and how fast you are going can get damaged. These stone bruises are pretty ugly, and many people fear that because the glass is broken, the windshield will cave in on then. This is not exactly true except for another safety factor discussed later on. Remember a Windshield is 2 pieces of glass. The Plastic Lamination between them has protected the inner piece of glass. So all you are left with is an unsightly crack in the outside glass. Now you can live with the bruise or get it repaired or replaced.

The glass in the rest of the car is different. Around the 1950′s the door glass and the backglass change to a tempered plate. It is just one piece of glass that is sent into an atmospheric oven that heats and quenches the glass which hardens it. PSI (pounds per square inch) can be in the 100′s. Have you ever seen a door glass break. I’m sure if you take a hammer to it you would be surprise. You either must hit it many times or break it on the first shot. But when it does break it falls apart into hundreds of small glass beads. A good tempered door glass will not cut you. A poorly tempered glass will break in shards and can cut badly. One of the reasons for choosing and OEM glass product.

The reason for different types of glass in vehicles today is safety. We could not have tempered glass for Windshields on the roads in the United States. Although harder to break than a Windshield, tempered glass is can be very unstable. If the skin is broken, it could explode in your face while driving. The real reason for this product is incase of rollover. It is very difficult to cut through laminated glass. So if you are ever trapped in your car, its easier to get through tempered than laminate.

Many people are amazed that one cold winter day or hot summer day, they came out to the car and all of a sudden they noticed a long crack running through the windshield, or the back glass is broken in a million pieces on your back seat. It is not a happy experience. They wonder how this happened, and they are now concerned for their safety. Many people ask their Glass expert how it happened when they go to get it replaced. The answer is simple. The windshield at some point had a small crack or bruise. The tempered backglass might of had a defect. Glass is very susceptible to quick changes in temperature. For example, on one cold winter morning you get into your car to warm it up. When you turned on your vehicle, you hit the defrost button on to take the ice, snow or frost off the windshield. Due to the fast expansion of the glass, the defect in the window started to run into a crack. The other situation is the heat of the summer. You drove to the supermarket with the A/C on. You get out of the car and shop for an hour. The range of temperature went from say 70 degrees to almost 200 degrees. Yes, you literally can fry an egg on the dashboard in this situation. The quick change of temperatures with cars that have a stone bruise, or an improperly installed or defective windshield or tempered part can fail, an break.

A cracked windshield compromises your safety. Even though the windshield will not cave in on you, it is not exactly safe and can pose as a dangerous situation. As vehicle manufactures started to streamline cars using Uni-Body design’s, which now the car has no main frame, windshields now perform a very important safety factor for the structural integrity of the car. All cars now must pass certain roll over tests, and as the car manufacture lighted the weight of the vehicle, they made the windshield an important factor in roll over safety. With a cracked, or stone bruised windshield you are now compromising the structure of that rollover safety. Let me give you an example that a science teacher might have taught us in grammar school. Take an egg. Place 2 fingers on the top and the bottom of the egg. Now squeeze with all your might. What happened. Nothing right. Yes, mother nature created the perfect non breakable structure, so that when mother hen sat on it the wrong way, it would not break. However now take a needle and poke it through the egg. Just like the stone in the windshield. You have now compromised its integrity. Now take your fingers to the egg, and squeeze again. Opss…you now have egg all over your hands. The same theory is now being used in windshield glass, and god forbid you get into an accident and roll. Your windshield better be free of bruises or cracks.

The adhessive which holds your windshield in place is another very important factor. The adhesive must be auto glass urethane which meets or exceeds government safety standards. That is it must be strong enough to keep the vehicles occupants in the car during an accident. Automotive urethanes are rated on a PSI(pounds per square inch) scale of 500 or more. So when you have your windshield replaced the technician must use automotive urethane.

The biggest concern people have about replacing their windshield is breaking the original seal at the factory. It is true that the glass installer must cut the old windshield out of the car, if properly installed the new seal is just as good as the one done at the factory. Again the auto glass installer must use auto adhessive Urethane, and primers that have met or surpassed governement safety standards.

Another concern of all Glass Dealers and Customers are cure times (how long does it take for the Urethane (glue) to dry and become safe for the customer to drive). At Rock Star Auto Glass we only use a true “quick cure urethane.” This quick dry will allow you to be on the roida angain within the hour!

Of course, with any auto glass need, please call ROCK STAR AUTO GLASS! We are more than happy to cmoe to your home or office to replace or repair that broken piece of glass!

Sincerely,

Brian Burt President Rock*Star Auto Glass www.rockstarautoglass.com 480.232.5554

by

Brian Burt is a well recognized figure in the auto glass industry. His expertise has led Rock Star Auto Glass to become Arizona’s number 1 auto glass company.

Mobile applications, RIP

Summary: The business of making native apps for mobile devices is dying, crushed by a fragmented market and restrictive business practices. The problems are so bad that the mobile web, despite its many technical drawbacks, is now a better way to deliver new functionality to mobiles. I think this will drive a rapid rise in mobile web development, largely replacing the mobile app business. This has huge implications for mobile operators, handset companies, developers, and users.

The decline of the mobile software industry

Mobile computing is different from PC computing.

For the last decade, that has been the fundamental rule of the mobile data industry. It was the central insight of Palm Computing’s “Zen of Palm” philosophy. Psion came up with similar ideas, and you can hear echoes of them from every other successful mobile computing firm: Mobile computers are used differently from PCs, and therefore must be designed differently.

We all assumed this also meant mobile devices needed a whole mobile-specific software stack, including an operating system and APIs designed specifically for mobility, and native third-party applications created from the ground up for mobile usage.

That’s what we all believe, but I’m starting to think we got it wrong.

Back in 1999 when I joined Palm, it seemed we had the whole mobile ecosystem nailed. The market was literally exploding, with the installed base of devices doubling every year, and an incredible range of creative and useful software popping up all over. In a 22-month period, the number of registered Palm developers increased from 3,000 to over 130,000. The PalmSource conference was swamped, with people spilling out into the halls, and David Pogue took center stage at the close of the conference to tell us how brilliant we all were.

It felt like we were at the leading edge of a revolution, but in hindsight it was more like the high water mark of a flash flood. In the years that followed, the energy and momentum gradually drained out of the mobile applications market.

The problem wasn’t just limited to Palm; the level of developer activity and creativity that we saw in the glory days of Palm OS hasn’t reappeared on any mobile platform since. In fact, as the market shifted from handhelds to smartphones, the situation for mobile app developers has become substantially worse.

That came home to me very forcefully a few days ago, when I got a call from Elia Freedman. Elia is CEO of Infinity Softworks, which makes vertical market software for mobile devices (tasks like real estate valuation and financial services). He was one of the leaders of the Palm software market, with a ten year history in mobile applications.

I eventually moved on from Palm, and Elia branched out into other platforms such as Blackberry. But we’ve kept in touch, and so he called recently to tell me that he had given up on his mobile applications business.

Elia gave me a long explanation of why. I can’t reproduce it word for word (I couldn’t write that fast), but I’ve summarized it with his permission here:

Two problems have caused a decline the mobile apps business over the last few years. First, the business has become tougher technologically. Second, marketing and sales have also become harder.

From the technical perspective, there are a couple of big issues. One is the proliferation of operating systems. Back in the late 1990s there were two platforms we had to worry about, Pocket PC and Palm OS. Symbian was there too, but it was in Europe and few people here were paying attention. Now there are at least ten platforms. Microsoft alone has several — two versions of Windows Mobile, Tablet PC, and so on. [Elia didn't mention it, but the fragmentation of Java makes this situation even worse.]

I call it three million platforms with a hundred users each (link).

The second technical issue is certification. The walls are being formed around devices in ways they never were before. Now I have to certify with both the OS and with each carrier, and it costs me thousands of dollars. So my costs are through the roof. On top of that, the adoption rate of mobile applications has gone down. So I have to pay more to sell less.

Then there’s marketing. Here too there are two issues. The first is vertical marketing. Few mobile devices align with verticals, which makes it hard for a vertical application developer like us to partner with any particular device. For example, Palm even at its height had no more than 20% of real estate agents. To cover our development costs on 20% of target customer base, I had to charge more than the customers could pay. So I was forced to make my application work on more platforms, which pushed me back into the million platforms problem.

The other marketing problem is the disappearance of horizontal distribution. You used to have some resellers and free software sites on the web that promoted mobile shareware and commercial products at low or no charge. You could also work through the hardware vendors to get to customers. We were masters of this; at one point we were bundled on 85% of mobile computing devices. We had retail distribution too.

None of those avenues are available any more. Retail has gone away. The online resellers have gone from taking 20% of our revenue to taking 50-70%. The other day I went looking for the freeware sites where we used to promote, and they have disappeared. Hardware bundling has ended because carriers took that over and made it impossible for us to get on the device. Palm used to have a bonus CD and a flyer that they put in the box, where we could get promoted. The carriers shut down both of those. They do not care about vertical apps. It feels like they don’t want any apps at all.

You can read more of Elia’s commentary on his weblog (link).

Add it all up, and Elia can’t make money in mobile applications any more. As he told me, “Mike, it’s time for you to write the obituary for mobile apps.” More on that later.

Although it’s a very sad situation, if Elia’s experience were an isolated story I’d probably just chalk it up to bad luck on the part of a single developer. But it mirrors what I’ve been hearing from a lot of mobile app developers on a lot of different operating systems for some time now. The combination of splintering platforms, shrinking distribution channels, and rising costs is making it harder and harder for a mobile application developer to succeed. Rather than getting better, the situation is getting worse.

I’ve always had faith that eventually we would solve these problems. We’d get the right OS vendor paired with a handset maker who understood the situation and an operator who was willing to give up some control, and a mobile platform would take off again. Maybe not Palm OS, but on somebody’s platform we’d get it all right.

I don’t believe that any more. I think it’s too late.

The mistake we made

We told ourselves that the fundamental rule of our business was: Mobile is different. But we lost sight of an even more fundamental law that applies to any computing platform:

A platform that is technically flawed but has a good business model will always beat a platform that is elegant but has a poor business model.

Windows is the best example of inelegant tech paired with the right business model, but it has happened over and over again in the history of the tech world.

In the mobile world, what have we done? We created a series of elegant technology platforms optimized just for mobile computing. We figured out how to extend battery life, start up the system instantly, conserve precious wireless bandwidth, synchronize to computers all over the planet, and optimize the display of data on a tiny screen.

But we never figured out how to help developers make money. In fact, we paired our elegant platforms with a developer business model so deeply broken that it would take many years, and enormous political battles throughout the industry, to fix it — if it can ever be fixed at all.

Meanwhile, there is now an alternative platform for mobile developers. It’s horribly flawed technically, not at all optimized for mobile usage, and in fact was designed for a completely different form of computing. It would be hard to create a computing architecture more inappropriate for use over a cellular data network. But it has a business model that sweeps away all of the barriers in the mobile market. Mobile developers are starting to switch to it, a trickle that is soon going to grow. And this time I think the flash flood will last.

If you haven’t figured it out yet, I’m talking about the Web. I think Web applications are going to destroy most native app development for mobiles. Not because the Web is a better technology for mobile, but because it has a better business model.

Think about it: If you’re creating a website, you don’t have to get permission from a carrier. You don’t have to get anything certified by anyone. You don’t have to beg for placement on the deck, and you don’t have to pay half your revenue to a reseller. In fact, the operator, handset vendor, and OS vendor probably won’t even be aware that you exist. It’ll just be you and the user, communicating directly.

Until recently, a couple of barriers prevented this from working. The first was the absence of flat-rate data plans. They have been around for a while in the US, but in Europe they are only now appearing. Before flat-rate, users were very fearful of exploring the mobile web because they risked ending up with a thousand-Euro mobile bill. That fear is now receding. The second barrier was the extremely bad quality of mobile browsers. Many of them still stink, but the high quality of Apple’s iPhone browser, coupled with Nokia’s licensing of WebKit, points to a future in which most mobile browsers will be reasonably feature-complete. The market will force this — mobile companies how have to ship a full browser in order to keep up with Apple, and operators have to give full access to it.

There are still huge problems with web apps on mobile, of course. Mobile web apps don’t work when you’re out of coverage, they’re slow due to network latency, and they do not make efficient use of the wireless network. But I believe it will be easier to resolve or live with these technical drawbacks in the next few years than it will be to fix the fundamental structural and business problems in the native mobile app market.

In other words, app development on the mobile web sucks less than the alternative.

Here’s a chart to help explain the situation. Imagine that we’re giving a numerical score to a platform, rating its attractiveness to developers. Attractiveness is defined as the technical elegance of the platform multiplied by how easy it is for developers to make money from it. The attractiveness score for native mobile app development looks like this over time:

This is why mobile app developers are in trouble. Even though the base of smartphones has been growing, and the platforms themselves have become more powerful, the market barriers have been growing even faster. So attractiveness has been dropping.

Now add in mobile web development:

Based on what I’m hearing from mobile developers, the lines just crossed. The business advantages of mobile web development outweigh its technical limitations. More importantly, if you look at where the lines are going, the advantage of mobile web is going to grow rapidly in the future.

I’m not saying all native mobile development is dead. In fact, we’re about to see the release of Apple’s native development tools for the iPhone, and as Chris Dunphy just pointed out to me, they are sure to result in a surge of native development for that platform. But I think even a rapidly-growing base of iPhones can’t compare to the weight of the whole mobile phone market getting onto a consistent base of browsers.

What it all means

If you’re a mobile developer, you should consider stopping native app development and shifting to a mobile-optimized website. That’s what Elia did, and he said it’s amazing how much easier it is to get things done. Even mobile game developers, who you’d think would be the last to abandon native development, are looking at web distribution (link; thanks to Mike Rowehl for pointing it out).

See if you can create a dumbed-down version of your application that will run over the mobile web. If the answer is yes, do it. If the answer is no, try to figure out what technology changes would let you move to the web, and watch for those changes to happen.

There are exceptions to any rule, and I think it makes sense to keep doing native development if your app can’t work effectively over the web, and it’s a vertical application so popular that you can get about $50 or more in revenue per copy. In that situation, you probably have enough resources to stay native for the time being. But even you should be monitoring the situation to see when you can switch to the web, because it will cut your expenses.

If you’re a mobile customer, make sure your next smartphone has a fully functional browser that can display standard web pages. And get the best deal you can on a flat-rate data plan; you’ll need it.

If you’re an operator or a handset vendor, get used to life as a dumb pipe. By trying to control your customers and make sure you extract most of the revenue from mobile data, all you’ve done is drive developers to the Web, which is even harder to control. You could have had a middle ground in which you and mobile developers worked together to share the profits, but instead you’ve handed the game to the Google crowd.

Congratulations.

Oh, about that obituary…

In loving memory of the mobile applications business. Adoring child of Java, Psion, Palm OS and Windows Mobile; doting parent of Symbian, Access Linux Platform, and S60; constant companion of Handango and Motricity. Scared the crap out of Microsoft in 2000. Passed away from strangulation at the hands of the mobile industry in 2008. Awaiting resurrection as a web service in 2009. In lieu of flowers, the family asks that you make a donation to the Yahoo takeover defense fund.
Copyright 2008 Michael Mace.

Symbian Tricks And Tips

Tip 1 : Do u know how to use the edit button (abc or pencil button)?
Heres how… in the inbox for example; u wanna delete multiple sms, simply hold the edit button, scroll down, and then, press c to delete the marked sms. The edit button can also b used to copy and past text in sms, simply hold it and scroll across, choose copy. pretty good for placing song names in ngages

Tip 2 : Shit happens, on a smartphone, its inevitable u do something wrong, and tis calls for a format of fone. to format the fone, press *#7370#, then enter the lock code, which is the sec code of the fone. NOTE: batt must b full, else if format is disrupted by low batt, consequences will b disatrous
I heard the code *#7780# works too, pretty much the same i tink.

for 6600 users, to format the fone, theres an alternative way. Press and hold <3>, < *>, and the buttons, then power on fone, keep holding on the 3 buttons, till u come to a format screen. tis method ONLY works on 6600, and need not enter the sec code. BUT sec code wun be reset to default 12345.

Tip 3 : TO NGAGE USERS; Did u know u can install .sis files simply using the cable given? Juz plug it in, place the .sis file anywhere on e: (the mmc), not in any folders, root of e:, disconnect, then look for it in manager.

Tip 4: Save on battery and system memory being used by regulary checking the task manager which can be accessed by holding down the menu button!!

Tip 5: Type *#06# to display your IMEI serial number, very valuable for the unlocking your phone to other sim cards

Tip 6: Type *#0000# to view which firmware version you are running

Tip 4a: Set the screen saver to a short time out period to prolong battery life.
Tip 4b: Avoid restarting the phone, or repeatedly turning it on and off. This helps increase battery life.

Tip 7: If you would like to avoid being “blue jacked”, keep bluetooth turned off, or set your phone’s visibility to hidden.

Tip 8: Don’t want to carry a watch and a phone? Set the screen saver to show date and time, then you can ditch the watch.

Tip 9: Save memory when installing apps, by installing over bluetooth. This can be done using the nokia phone suite and a bluetooth serial connection. Only works with .SIS files, so java still has to be sent to the phone, but will save space when using .SIS files.

Tip 10: Operator logos
Use a filemanager like FExplorer or SeleQ to add the folders: “c:/system/Apps/phone/oplogo”. Add a .bmp picture to folder “oplogo” and restart your phone! The .bmp picture size needs to be: 97 x 25 pixels

Tip 11: Check if the recepients phone is on
Delivery reports

or

Type *0# your message in the message composer window space then write your message, the recipient will not see the star zero hash bit – just the message When they read it it will relay a message back to your fone showing the time they recieved it. (haven’t yet tried it myself though)

Tip 12: BlueJacking

First up, you need to know what Bluetooth is. There are lots of types of modern devices that incorporate Bluetooth as one of their many features. PDAs, mobile phones and laptops are a few of these modern devices. Bluetooth means that Bluetooth enabled devices can send things like phonebook/address book contacts, pictures & notes to other Bluetooth enabled devices wirelessly over a range of about 10 metres. So, we’ve got past the boring part. Now, using a phone with Bluetooth, you can create a phonebook contact and write a message, eg. ‘Hello, you’ve been bluejacked’, in the ‘Name’ field. Then you can search for other phones with Bluetooth and send that phonebook contact to them. On their phone, a message will popup saying “‘Hello, you’ve been bluejacked’ has just been received by Bluetooth” or something along those lines. For most ‘victims’ they will have no idea as to how the message appeared on their phone.

Tip 13: While you are viewing a picture in your phone’s gallery, press one of these shortcut keys (definitely works on 6600, not sure about other symbians)
1 – turn image anticlockwise
3 – turn image clockwise
* – toggle on/off of full screen
5 – zoom in
0 – zoom out

#15 u can select all files in a folder by selecting THE folder and copy it then paste it somewhere. however u need to make a new directory. fexplorer wun let u copy that folder together. well seleQ can mark files to copy but it really takes time!

#16: A soft and Hard reset
A Soft-reset – the process of resetting all the settings of the phone to the factory default! No applications are deleted! A Hard-reset is like formatting a drive! It does format the memory. Everything that has been installed after the first use of the phone is deleted! It will recover the memory of the phone to the state you purchased it! It is done by inputing the following code: *#7370# NOTE: The battery must be full or the charger has to be connected to the phone so that it does not run out of power and make the phone unusable.

#17: Formats of images

supported ones: JPG UPF GIF87a/89a WBMB MBM TIFF/F PNG EXIF

How to copy & paste text in your Nokia 3650:
Press and hold the pencil key and select your text using the scroll key.
Left function key will change to ‘Copy’. Press it to copy the selected text to clipboard.
You can paste the clipboard contents the same way:
press and hold the pencil key and press ‘Paste’. Or, press pencil key once and select ‘Paste’.

Press and hold the Menu key to open the application switching window, where you can *duh* switch between applications.
If a program hangs and you can’t shut it down, select the application in the
application switching window and press ‘C’ to kill it. It’s also a faster way to exit programs.

Turn on/off the “click” sound made by the camera by selecting the ‘Silent’ profile or by turning warning tones on/off:
Menu > Profiles > “select your activated profile” > Personalise > Warning tones > On/Off.
(This also effects the sound of Java games and apps).

To change background image go to:
Menu > Tools > Settings > Phone > Standby mode > Background image > Yes > “choose an image”.
The best size for background images is 174×132 pixels.

Only got blue, green and purple in your 3650 colour palette?
This free app adds 3 more colours: Palette Extender.

Display an image when someone’s calling:
Menu > Contacts > “select a contact card” > Options > Edit > Options > Add thumbnail > “choose an image”.

Add a personal ringing tone to a contact:
Menu > Contacts > “select a contact card” > Options > Open > Options > Ringing tone > “choose a ringing tone”.

Delete all messages from your Inbox at once:
Menu > Messaging > Inbox > Options > Mark/Unmark > Mark all > Options > Delete.

Send or hide your caller ID: Go to: Menu > Tools > Settings > Call > Send My
Caller ID > ‘Yes’, ‘No’ or ‘Set By Network’ to follow the default settings of your home network.

If you often copy large files to your MultiMedia Card, I recommend a card reader.
E.g. With a card reader it takes only 12 seconds to copy a 10 MB file!

Record the sound of a phone call using the (sound) Recorder.
Menu > Extra’s > Recorder > Options > Record sound clip.
Note: short beeps are audible during call registration.
But there is a 60 second limitation so if you want unlimited sound recording get this app: Extended Recorder.

While writing text, press “#” to switch between upper and lower case and Dictonary on/off (predictive text input).
Press and hold “#” to switch between Alpha mode and Number mode.

Keyboard shortcuts for zooming and rotating images in Images:
1 = zoom in, 0 = zoom out, press and hold to return to the normal view.
2 = rotate anticlockwise, 9 = rotate clockwise, * = full screen.

In standby mode, press and hold the right soft key to activate voice dialling.
To add a voice tag to a phone number, open a contact card and scroll to the phone number and select:
Options > Add voice tag.

You can customize both soft keys located below the screen (in standby mode):
Menu > Tools > Settings > Phone > Standby mode > Left/Right selection key > “select an application”.

In standby mode. press scroll key center (joystick) to go directly to Contacts.

In standby mode, press and hold 0 to launch your wap home page.

In Menu or any subfolder, press numbers 1 – 9 to start the application at that location.
123
456
789

In standby mode,
45# + dials the number on your sim in memory slot 45.
50# + dials slot 50 and so on.

If you have your keylock activated just press the on/off button to turn on your backlight
to look at the time when it’s dark without having to unlock the keypad.

Never, ever, in your whole life, install WildSkinz on your Nokia 3650!!! WildSkinz screws up
the whole 3650 system. It was never intended to work on the 3650, only on the 7650.

Why assigning Video Recorder in the right or left soft key does not work?

(Sound Recorder is launched instead of Video Recorder)
It’s a bug with firmware version 2.50.

How to check your firmware version:

A “Firmware” is the phone’s operating system stored in internal Flash memory of the device (disk Z.
Manufacturers release new firmware versions containing bug fixes, improvements and – sometimes – offering new functions.
Firmware upgrade can only be made in authorized Nokia service centre (point).
To check your current firmware version simply type *#0000# on main Phone screen.

?

How to check your IMEI (International Mobile Equipment Identity)?

Type *#06# on main Phone screen.

Start up in Safe Mode so no ‘auto start’ apps will be running:

To make sure that no memory-resident programs start when you reboot your phone,
hold down the pencil key when you turn on the phone and hold it on untill you have to enter your PIN code.
(When you have trouble booting up the phone with the MMC in it because it got corrupted for some reason, this trick will
almost always let you boot up the phone so you can remove the latest installed app which might have caused the
problem or if your phone is “unrepairable” you can still back up your important data before you do a format.)

Q: How to totally format your Nokia 3650 and remove all installed applications, user files and restore all
settings to default like it’s new out of the box? (OEM apps won’t be deleted like Camera and RealOne Player).

A: First Format your MMC: Menu > Extras > Memory > Options > Format mem. card > Yes.
Note: It is very important to format your MMC before you format your phone!
Then format your phone by typing *#7370# on main Phone screen.
Phone will ask: “Restore all original phone settings? Phone will restart.” Press ‘Yes’ and enter your Lock code (default is 12345).
Tip: Formatting takes several minutes so you’d better connect your Nokia 3650
to a charger to ensure that your battery doesn’t get empty in the middle of formatting.
Note: All your created acces points and mailboxes will be lost so take a note of them. And all application settings will be reset.
E.g. In Camera, image quality is set back to normal and memory in use is set back to phone memory. And also in Messages,
memory in use is set back to phone memory, etc. Also backup your contacts with PC Suite or a program like Contacts Manager.

To reset your wallet, should you forget your code,

Type in:
*#7370925538#

this will reset the wallet code, the wallet contents will be deleted.

– —————————————————————————————–

How to free more RAM on your phone >>>

>>> Method 1: Flight mode:

Put your phone in “Flight mode” with Psiloc System Tools. Install System Tools, open it and select “Flight mode”. This way you can restart the phone without your SIM card so there will be no running phone tasks in the background. Now you can have up to 3,5 MB of free RAM!

Note: ironically enough, Flight mode doesn’t work when Smart Launcher is installed, at least in my case.
But i’ve also heard several reports of people who have both apps running without any problems.

>>> Method 2: Smart Launcher trick:

Install Smart Launcher and open it. Go to Options, Settings and put Launcher ON.
Now plug in your charger and switch off your phone. Wait untill the battery meter appears and short press the Menu button (don’t hold).
The menu should appear and now you can have 3,5 to 4,5 MB free RAM! (Hold Menu button to check RAM).

The trick is that with the charger plugged in, the phone must get a minimum software support for charging, even when
the phone is switched off. And somehow Smart Launcher has still got it’s shortcut running and that’s the Menu button. So when
you press the Menu button, you go directly to the Menu without any other phone tasks running in the background so
you trick the phone and you have more free RAM!
Note: when you unplug the charger, the phone will switch off.

>>> Method 3: Menu :

This method I found it by myself, it frees a little about 100~200 KB but I guess it’s useful sometime

Close your menu not by selecting the right selection key “exit”, or pressing the menu key another time, they only hide the menu app but do not close it, to close it select the left selection key “option” and scroll down and select “exit”

So when you open an app needs more ram reopen menu and close it, it’s useful when play low bit rate video in realplayer paradis.

Your Ad Here

The end of the dream

No matter how it works out in the long run, the purchase of Symbian by Nokia marks the end of a dream — the creation of a new independent OS company to be the mobile equivalent of Microsoft. Put a few beers into former Symbian employees and they’ll get a little wistful about it, but the company they talk about most often is Psion, the PDA company that spawned Symbian.

Psion never got much attention in the US, but it was a pioneer in the PDA market in the UK, and even to this day I think the Psion Revo is one of the two coolest-looking PDAs ever made (the Palm V is the other one).


The Revo

Psion explored many ideas that eventually turned into major new consumer electronics categories, but it failed to follow up on them. The company was effectively dismembered when Symbian was formed, and many of its best people drifted off to other companies. Now Symbian itself is transitioning to something very different, with most of its people absorbed into Nokia. What the Psion veterans talk about wistfully is how many smart people worked at Psion, how many great ideas the company fumbled, and how successful many of the people have been in the tech industry post-Psion. In this sense, Psion is similar to many other tech pioneer companies that assembled staffs of very bright people, taught them how to work together, and then blew apart like exploding stars, scattering the elements of new companies across the industry. This process dates back at least to Fairchild Semiconductor, which trained the founders of many of the most prominent semiconductor companies (link). You can find similar networks of former employees from places like Apple, Netscape, and Palm. I think Yahoo is in the process of forming a network now, and some day there’s going to be a dandy one made of former Googlers.

What makes the Psion story different is that many of the Psion veterans had to leave the UK, or join non-UK companies, in order to become successful. Some are in other parts of Europe, some are in the US, and some are in London but working for foreign companies. This is a source of intense frustration to the Psion folks I’ve talked with. They feel like not only their company failed, but their country failed to take advantage of the expertise they had built.

There’s a big body of academic research on why Silicon Valley has been successful in sustaining itself, and part of the reason is that the Valley recycles companies very efficiently. Failing companies do not last long, but in the process the brightest people and ideas are rarely lost, they are just shuffled around into new configurations.

About a year ago, Andrew Orlowski of the Register wrote an amazing article on the history of Psion, and how company culture and government philosophy failed to take advantage of it to grow a new industry. It’s the longest piece I’ve ever seen in the Register, almost the nucleus of a book, and it’s well worth reading. It didn’t get enough attention when it was published, and I’m embarrassed to say that I never posted a link to it. So I’m glad to remedy that now. If you want to understand the context what happened to Symbian, and learn a bit about how the tech industry works, go read it here.

If you want to hear more about what Symbian is morphing into, two of its executives have just started personal weblogs in which they are commenting on the migration to Symbian Foundation (among other things). It’s an interesting move, and it seems symbolic of the transition they’re trying to make into the open source world. Previously Symbian had a company blog that several execs contributed to; now the execs have personal blogs where they talk directly to the industry.

David Wood (Symbian’s EVP of Research) link.
John Forsyth (Symbian’s Strategy VP) link.
Copyright 2008 Michael Mace.

Customizing the Sliding Panel Homescreen

Hi, my name is Jorge Peraza; I am a Developer on the Windows Mobile team that was responsible for the new ?Sliding Panel? home screen in Windows Mobile 6.1.

< ?xml:namespace prefix = o /> 

When we were working on the visual style and functionality of the home screen we tried to make something that looked both professional and appealing while still showcasing all the information the user is going to need to know what?s important and requires attention.  While I think the default design looks really cool, we added some customization features to enable users to make it their own.

 

Customizing the layout:

 

The home screen layout can be modified using the same home.xml file from previous versions of WM, the schema of the file was extended to allow the customization of many of its elements, this includes the art assets that are used for most of the plug-ins.

 

When you open the SlidingPanel.home.xml file (inside \ApplicationData\Home) you will find the plug-in element that corresponds to the sliding panel home screen (its CLSID is {E9267CAB-02EE-4f37-8216-6BF6A8FF5A71}).  All the child elements inside it are designed to tweak and customize the way the home  screen will look.

 

The top level element is the plugins tag, this has one attribute called ?Order? and it?s used to list the plug-ins that will be shown and the order they are going to be laid out on the screen.

 

The built in plug-in names are:

1)      CClock ? The big clock

2)      CAppointments  - The calendar plugin

3)      CHome ? The notifications plugin

4)      CMyPhotos ? The photos plugin

5)      CMessage ? The message center (this is off by default on all sliding panel built in layouts.

6)      CMusic ? The music plugin

7)      Settings ? The settings plug-in

8)       Custom Plugins ? Users can  specify custom plug-ins with static content that can be displayed on the home screen.

 

For example, the XML snippet bellow moves the photos plug-in to the first position and enables the message center (which is turned off by default on both “Sliding Panel” and “Sliding Panel Media”)

 

<plugin clsid=”{E9267CAB-02EE-4f37-8216-6BF6A8FF5A71} name=”Bronze height=”266“>

  <Plugins Order=”CMyPhotos;CClock;CMessage” />

</plugin>

 

 

There are many other ways of customizing the home screen using the plug-in settings like overriding the default images or even adding your own custom plug-ins that display static content, I’ll post and updated entry latter on on how to do this in detail but for now, you can use the provided home.xml files to start experimenting with this.

 

The notifications plug-in and message center

 

In the sliding panel home screen, the notifications plug-in by default serves as a dual-purpose notifications/gateway to all you phone/message accounts where every page represents one account (so, if you have multiple notifications in one category they will be shown as one summary page).

 

There is however an alternative behavior where individual notifications are added as independent pages (Similar to what the T-Mobile shadow home screen does) and the plug-in only shows accounts that have new notifications in them.  One cool feature of this alternate behavior is that each individual notification can be dismissed without having to leave the home screen.

 

 

You can enable this alternative behavior by setting the following registry key to a value other than 2 (The actual value indicates how many pages of each notification type will be added to the home screen before collapsing them into a summary page. We have tested 2 and 5 but feel free to experiment with other values)

 

[HKLM\Software\Microsoft\Chome\Chome]

PageCollapseThreshold: DWORD

 

Note that this prevents you from being able to access the email/phone account data if there are no notifications for it. If you still want to be able to do that you can always re-enable the message center as described in the previous section as a separate plug-in.

 

There is one more behavioral change you can make that allows you to ?dock? the condensed view of the first plug-in to the top of the screen when it is not active, we added this for people like me that want to have the clock always visible. To enable just set the following registry key to ?1?

 

[HKLM\Software\Microsoft\Chome]

DockOperatorBar: DWORD

 

Advanced layout modification:

There are even more advanced things you can do to further tweak the look of the home screen but it is unsupported by Microsoft at this moment so you?ll have to experiment on your own J (Hint, look at the following files \windows\CHome_240x320.cpr and \windows\CHome_320x240.cpr).

Important update, please read:< ?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Although we’re excited to see developers interested in taking advantage of the new home screen, any code samples in this blog post apply only to Windows Mobile 6.1 Standard devices. We do not expect this code to work on previous or future versions of Windows Mobile. Please keep this in mind if you decide to develop plugins for Sliding Panel today.