Showing posts with label mobile phones. Show all posts
Showing posts with label mobile phones. Show all posts

Wednesday, 29 January 2014

Google sells Motorola unit to Lenovo for $2.9B

Google sells Motorola unit to Lenovo for $2.9B

Source: Cnet

The Droid Ultra is one of Motorola's key franchises in the US.
(Credit: CNET)
Google is unloading Motorola Mobility onto Chinese PC maker Lenovo.
Google confirmed on its site that it has sold Motorola for $2.91 billion, consisting of $660 million in cash and $750 million in Lenovo shares, with the remaining $1.5 billion paid in the form of a three-year promissory note. Reuters earlier reported on the deal.
Lenovo gets the Motorola brand, as well as its portfolio of devices, including the Moto X and Moto G. In addition, it will also receive more than 2,000 patent assets, while Google will retain control of a majority of the patents it originally obtained when it acquired Motorola several years ago.
A deal instantly gives Lenovo, which has a thriving smartphone business in China but few other places, an established global brand. Google, meanwhile, will shed a business that has continually dragged down its profits.

The deal marks one of the worst investments in Google's history. In 2012, Google completed its acquisition of Motorola Mobility for $12.5 billion. At the time, it was thought that the primary reason for the acquisition was the treasure trove of Motorola patents that would help Google defend it and its partners against Apple.
The patents, however, have proven to be less than effective in warding off lawsuits, and much of the legal fighting as gone on between Apple and Samsung, with Google only tangentially related. Google and Samsungrecently signed their own cross-licensing pact.
Troubled handset business 
The handset side of Motorola, however, has always been a stress point between Google and its partners. While Google said it maintained a division between its Android group and the Motorola unit, other vendors have privately expressed irritation that a partner was also a competitor.
Google did legitimately try to revive the once vaunted Motorola brand with unique products, including the Moto X, which was built in the US and could be tweaked with different colors and covers, as well as the ultra-low-cost Moto G, geared toward emerging markets and lower-income consumers looking for a competitive smartphone.
The custom back of the Moto X.
(Credit: Motorola)
Throughout the last year or so, Motorola has continually posted losses. In the most recent quarter, Motorola posted an operating loss of $248 million, wider than the year-earlier period. Google reports its latest results Thursday.
Still, the move is a surprising one, given that Google has been moving toward becoming more of a hardware company. Beyond smartphones, the company is pushing its Google Glass headset and its Chromecast media dongle. It just purchased Nest for $3.2 billion to get into the smart thermostats and smoke detectors.
"This would be at odds with its recent push to hardware," said NPD analyst Stephen Baker. "Everybody was thinking they would get more hardware-oriented. This may signal a reversal."
Gaining a global brand 
Lenovo, meanwhile, could conceivably jump-start its smartphone ambitions with the purchase of Motorola. As the inventor of the cell phone, Motorola has a rich legacy and a still well-known brand that Lenovo could exploit.
"The acquisition of such an iconic brand, innovative product portfolio and incredibly talented global team will immediately make Lenovo a strong global competitor in smartphones," Lenovo CEO Yang Yuanqing said in a statement.
Indeed, Lenovo actually has a strong smartphone business itself, but one that is largely limited to China. Still, the market is big enough that it ranked No. 5 among global smartphone vendors in the fourth quarter, seeing its share rise to 4.7 percent from 4.2 percent a year ago, according to Strategy Analytics.
Lenovo's CEO said in May 2013 that it would bring its smartphones to the US within a year, but it hasn't updated its timing since then.
By buying Motorola from Google, Lenovo is repeating the same play is successfully pulled off in 2005, when it entered the global PC business by acquiring IBM's PC business. The deal instantly made Lenovo a major player with PCs, building on the business-centric ThinkPad with the consumer-facing IdeaPad.
"Lenovo intends to keep Motorola's distinct brand identity--just as they did when they acquired ThinkPad from IBM in 2005," Google CEO Larry Page said in a statement.
Lenovo reportedly attempted to purchase BlackBerry, but a deal was supposedly squashed by regulators sensitive to a Chinese company owning phones widely used by government agencies.
The Chinese computer giant is the world's biggest PC vendor, with about 17 percent share of the market, according to IDC.
Lenovo said earlier this month that it will buy IBM's server business for $2.3 billion.
With Motorola, Lenovo could use the company's established track record and contacts in the wireless industry to push its phones around the phone. And it doesn't have to build its own brand from scratch.
"We tend to think of the Chinese companies as rigid, but Lenovo has been adaptable in a lot of brands and geographies," Baker said.
Update 2:14 p.m. PT: Added confirmation from Google that it has sold its Motorola unit to Lenovo.

Hack iPhone 5 to improve Network Connectivity

How-to: Hack Your iPhone 5 to Improve Network Connectivity

iPhone 5_white_black
AT&T iPhone users can hack their device if they want to improve their network’s performance. It does this because carriers normally use a specific, preferred band for your signal. This hack, however, will make your phone  use the band giving off the strongest signal, which can improve connectivity.
Here’s how you can accomplish it on your iPhone 5:
1) Plug your iPhone 5 to perform a backup. If anything should go wrong, you’ll be glad you did.
2) You will also need the hacked carrier update, which is here.
3) You will want to enable iTunes to accept custom carrier bundles, which is explained here for both Windows and Mac:
64 bit:cd C:\Program Files (x86)\iTunes then type: iTunes.exe/setPrefInt carrier-testing 1
32 bit: cd C:\Program Files\iTunes then type: iTunes.exe/setPrefInt carrier-testing 1
Mac users you will need to open terminal and type the following and enter it in:
Mac: defaults write com.apple.iTunes carrier-testing -bool true
4) Go to your iPhone tab in iTunes and click “Update” or “Check for Update” while holding down Option (Mac) or Shift (Windows). Navigate to the hacked carrier file you saved earlier and select it.

How to install Super User and SU Binaries with just one click



Here an one-click application to install Superuser and su binary on phone. Look at the compatibility lists below to see if this application can be useful for you.
Feedbacks on compatibility devices will be greatly appreciated in order to update the compatibility list.
Superuser and su binary include in application work from android 2 to 4.

!! Important !!
Success with this application void warranty on your device.
Read the FAQ before posting your question.

If you like my work, you can buy Framaroot donation app
Many many thanks to all donors

Version 1.8.1: Another attempt to fix crashes.
Version 1.8.0: Add Faramir exploit, little brother of Boromir (potentially affect Mediatek based devices).
Version 1.7.1: Link to Framaroot donation added (it does nothing as this kind of application are forbidden on play store ... but it could do something someday)
Version 1.7.0: Due to a mistake, Pippin exploit didn't appear in exploit list, its fixed now (Huawei device owners welcome). Add Gollum exploit for AMLogic based devices.
Version 1.6.1: Remove Superuser as it fail to install. Add execution support from adb command line.
Version 1.6.0: Add Pippin exploit (potentially affect Huawei K3V2 based devices)
Version 1.5.3: An attempt to fix Gandalf error#10
Version 1.5.2: Revert to exploitation fix included in 1.4.1. Add Slovakian and Italian languages. Error # added in toast message when exploit failed (report the error number in this thread so I could give you the reason of failure). Previously fix for Framaroot crash was a dirty hack, with this version you shouldn't encounter crash.
Version 1.5.1: Should fix Framaroot crashes.
Version 1.5.0: Add Boromir exploit (potentially affect many Mediatek based devices).
Version 1.4.3: Update SuperSU to 1.34. Rewrote the fix include in 1.4.1 for better but slower exploitation.
Version 1.4.2: Add Russian and French languages. Add scrollbar for exploit list. Update SuperSU to 1.30
Version 1.4.1: Fix a bug in exploitation due to the different kernel data alignement between version and devices, so if exploits didn't work before it "may" work with this version if your device is vulnerable
Version 1.4: Add Gandalf exploit (potentially affect Qualcomm based devices, tested on Nexus 4, as always feedbacks are welcome)
Version 1.3: Add Aragorn and Legolas exploits (could affect wide range of samsung devices including non exynos devices, please give feedbacks for your devices. Thanks)
Version 1.2.1: Fix unroot bug. Improvements for exploitation. Embed SuperSU 1.25
Version 1.2: Add possibility to Install Superuser, Install SuperSU and Unroot
Version 1.1: Frodo exploit added
Version 1.0: Initial release

Compatibility for Qualcomm devices (Gandalf exploit only) :
  • ASUS Memopad FHD 10 LTE
  • Asus Padfone 1/2
  • Asus Padfone Infinity
  • Asus Transformer Pad Infinity TF700KL
  • BLU Studio 5.3 S
  • BW T18+ (Fortis Evo)
  • Cloudfone Thrill 430x
  • Disgo 8400g
  • DNS S4504/S4503/S4502
  • FAEA F1
  • Gigabyte GSmart G1315 Skate
  • Gigabyte GSmart Rio R1
  • Google Nexus 4
  • Highscreen Spark/OMEGA Q/Blast/Strike/Boost
  • Hisense AD683G
  • HTC One S
  • Huawei Honor Pro (U8950-1)
  • Huawei Premia 4g
  • Huawei U8815/U8816 Ascend G300/G301
  • Huawei U8825D Ascend G330D
  • Huawei Y215
  • K-TOUCH TITAN S100
  • Karbonn Titanium S5
  • kyocera Hydro Edge
  • Kyocera Torque
  • Lenovo A600e
  • Lenovo A706
  • Lenovo S870E
  • LF-LTE3 (F260S)
  • LG Nitro HD
  • LG L1 II
  • LG L7 II P710/P714/P715
  • LG Optimus F5 (P875)
  • LG Optimus G E970/E975
  • LG Optimus L3 II E425
  • LG Optimus L5 E610/612/615
  • LG Optimus L7 II P710/P713/ P714/P715
  • LG Optimus L7 P700/Р705
  • LG Optimus LTE 2
  • MEDION LIFE P4013
  • Micromax A111 Canvas Doodle
  • Motorola Defy Mini XT321
  • Oppo Find 5
  • Orange Nivo
  • Orange Zali
  • Pantech Discover
  • Pantech Flex
  • Pantech IM-A840S Vega S5
  • Pentagram Combo
  • Phicomm i600
  • Samsung Galaxy Core i8260
  • Samsung Galaxy Express GT-I8730
  • Samsung Galaxy Win I8552
  • Sharp Aquos Phone SH930W
  • Smartfren Andromax U
  • Smartfren Andromax i2
  • Sony Xperia E C1505/Dual C1605
  • Sony Xperia L C210X
  • teXet TM-3204R
  • teXet TM-4677
  • Xiaomi Mi-2S
  • ZTE V880G/ZTE V955
  • ZTE V9815 Grand Memo N5
  • ZTE Warp Sequent
  • Waiting feedbacks ...

Compatibility for MTK devices (Boromir and Faramir exploits only) :
  • Acer A1-810
  • Acer A1-811
  • Acer Liquid E2
  • Acer Liquid Z3
  • Alcatel OT 4030D S'POP
  • Alcatel OT 8008D Scribe HD
  • Alcatel OT 997D
  • Alcatel OT Idol 6012X / Le Mobile Sosh / Orange Hiro
  • Alcatel OT Idol 6030X/6030D/6030H
  • Alcatel OT Scribe Easy 8000a
  • Alcatel OT Star 6010X
  • Alcatel OT X'Pop 5035D
  • Amoi N828
  • Archos 40 Titanium
  • ASUS Memo Pad HD 7
  • AVUS A24
  • Blu Life Play
  • BLU Studio 5.0 / 5.5
  • Bq Aquaris 5
  • Cat B15
  • Changhong z9
  • Cherry Mobile Burst 2
  • Cherry Mobile Cosmos S
  • Cherry Mobile Cosmos X
  • Chinese Star S7589
  • Coolbox Quore v57
  • Cube U39GT 3G (CubeTalk 9)
  • Cube U55GT (CubeTalk 79)
  • Cubot A890
  • CUBOT GT90
  • CUBOT ONE
  • DAXIAN XY100S
  • Doogee DG200 Hotwind
  • Explay HD Quad
  • Explay infinity II
  • Explay Polo
  • Explay Surfer 7.32 3G
  • Explay Surfer 8.31 3G
  • Explay X-Tremer
  • Fly IQ440 Energie
  • Fly IQ441 Radiance
  • Fly IQ442 Miracle
  • Fly IQ443 Trend
  • Fly IQ446 Magic
  • Fly IQ450 Quattro Horizon 2
  • Fly IQ451
  • Gionee 868H
  • Gionee GN 708
  • Gionee Pioneer P2
  • GoClever Fone 570Q
  • GoClever Quantum 4
  • GoClever Tab M713G
  • GSmart Aku A1
  • GSmart Sierra S1
  • Haier W718
  • Haipai I9389
  • HDC I9500/N9006
  • Highscreen Alpha GTX
  • Hisense U970
  • HKC Q79 3G
  • Hosin v70
  • Huawei U8836D G500 Pro
  • Huawei G700-U10 / G700-U20
  • HTM A6
  • IconBIT NetTAB Space 3G Duo
  • IconBIT NetTAB Mercury Q7
  • I-mobile series I-style 7.2
  • iOcean X7
  • Jiayu G2
  • Jiayu G3S
  • Jiayu G4
  • Karbonn A30
  • KENEKSI Beta
  • Lava iris 405
  • Lenovo 10.1" Tablet S6000
  • Lenovo IdeaPhone P700i
  • Lenovo IdeaPhone S720
  • Lenovo IdeaTab A3000-H
  • Lenovo IdeaTab S6000-H
  • Lenovo P770/P780
  • Lenovo S720, S820, S920, A390, A850, A516
  • Mi354 "Spice Smart Flo Space"
  • Micromax A58
  • Micromax A90S
  • Micromax Canvas 2 Plus
  • Micromax Canvas 4 A210
  • Micromax Canvas EGO A113
  • Micromax Canvas HD
  • Mlais MX70
  • MoreFine S6 Pro
  • Motorola RAZR D1
  • Motorola RAZR D3
  • MSI primo 76
  • MyPhone Agua Iceberg
  • N800 Mini Note
  • Neken N6
  • NEO N003 Advance
  • Newman N1
  • Omate TrueSmart
  • OPPO Find Clover
  • Oppo findway U7015
  • OUMEI X5
  • Overmax Vertis-02
  • Pantech Vega LTE Ex (IM-820L)
  • Pearl Smartwatch AW-414
  • Philips W536
  • Philips W736
  • Prestigio MultiPhone 4055
  • Prestigio MultiPhone PAP 3400/4505/5044 DUO
  • Runbo x5
  • S09 W63 IP68
  • Sharp AQUOS SH837W
  • Shengda S4
  • Smartfren Andromax V
  • Star HD9000+
  • Star S5 Butterfly
  • Starmobile Diamond V3
  • Starmobile Knight
  • Symphony Xplorer ZII
  • TeXet NaviPad TM-7055HD
  • Texet TM-5277
  • THL V12
  • THL W8 Beyond
  • THL W8S
  • THL W11
  • THL W100 (130711)
  • THL W200
  • Vonino Ego QS
  • Vonino Sirius QS
  • Xiaomi Hongmi
  • Xolo A600/Q700/Q800
  • Zen Ultrafone 701HD
  • ZOPO 980/990
  • ZOPO C2 Platinum
  • ZOPO C3
  • ZOPO ZP910
  • ZOPO ZP300+ / ZP500+
  • ZOPO ZP900 Leader
  • ZOPO ZP950H
  • ZTE Kis
  • ZTE N986
  • ZTE Open
  • ZTE Roamer 2
  • ZTE V795
  • ZTE V880G/H
  • ZTE V967S
  • ZTE V987 Grand X Quad
  • Walton Primo F3i
  • Walton Primo G1
  • Walton Primo H2
  • Wiko Cink Peax 2
  • Wiko Darkfull
  • Wiko Darknight
  • Wiko Ozzy
  • Wiko Stairway
  • Waiting feedbacks ...

Compatibility for Huawei K3V2 devices (Pippin exploit only) :
  • Huawei Ascend G615
  • Huawei Ascend Mate
  • Huawei Honor 2
  • Waiting feedbacks ...

Compatibility for AMLogic devices (Gollum exploit only) :
  • Waiting feedbacks ...

Compatibility for Samsung devices (Legolas and Aragorn exploits only) :
  • Samsung Galaxy Core GT-I8262
  • Samsung Galaxy S Aviator
  • Samsung Galaxy Proclaim S720C
  • Samsung Galaxy Young GT-S6312/GT-S6310
  • Samsung Illusion SCH-I110
  • Samsung Lightray SCH-R940
  • Waiting feedbacks ...

Compatibility for Exynos devices (Sam, Frodo, Legolas and Aragorn exploits only) :
  • AT&T Galaxy Note 2 SGH-I317
  • Highscreen Explosion
  • Hyundai T10
  • Hyundai T7s
  • Impression 9702 (Exynos 4412)
  • Lenovo K860/К860i
  • Newman N2
  • Meizu MX2
  • Samsung Galaxy Camera EK-GC100
  • Samsung Galaxy Note 10.1 GT-N8000, GT-N8010, GT-N8013, GT-N8020
  • Samsung Galaxy Note 2 GT-N7100
  • Samsung Galaxy Note 2 LTE GT-N7105
  • Samsung Galaxy Note 8.0
  • Samsung Galaxy Note GT-N7000
  • Samsung Galaxy S GT-i9000
  • Samsung Galaxy S2 AT&T SGH-I777
  • Samsung Galaxy S2 Epic 4G Touch - SPH-D710
  • Samsung Galaxy S2 GT-I9100
  • Samsung Galaxy S3 GT-I9300
  • Samsung Galaxy S3 LTE GT-I9305
  • Samsung Galaxy Tab Plus GT-P6200/GT-P6210
  • Samsung Galaxy Tab 7.7 GT-P6800/GT-P6810
  • Samsung SGH-i997 Infuse 4G
  • T-Mobile Galaxy Note 2 T-889
  • Verizon Galaxy Note 2 SCH-I605
  • iBerry Auxus CoreX2 3G and CoreX4 3G

Compatibility for Omap36XX devices (Gimli exploit only) :
  • Archos Gen8
  • Cliq 2 MB611
  • Coolpad Quattro 4G
  • Droid 2 (a955)
  • Droid 2 Global (a956)
  • Droid X (MB810)
  • LG Marquee LS855
  • LG P970 Optimus Black
  • Motorola DEFY+ (MB525 / MB526)
  • Motorola Droid PRO
  • Motorola Droid X
  • Motorola Milestone 2
  • Motorola XPRT
  • Parrot ASTEROID Smart
  • R2D2 (a957)

Possible case once application is launched
  • A popup saying "Your device seems not vulnerable to exploit included in Framaroot", in this case you can uninstall app
  • You seeing one or more exploit name, also click on one after you have selected an action and you will see one of the above messages

Possible case once exploit is launched
  • "Success  ... Superuser and su binary installed. You have to reboot your device"
  • "Failed  ... Exploit work but installation of Superuser and su binary have failed"
  • "Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root", happen when the filesystem in use on system partition is a read only filesystem (ex: squashfs)
  • "Failed  ... Try another exploit if available"

FAQ
Is framaroot work on my device ?
If your device is in the compatibility list above, the short answer is : yes but it depends of your firmware version, latest firmware have less chance to be rooted.
If your device is not in the compatibility list and it embed one of the processor mentionned above, the answer is : try it and see.

Why framaroot doesn't root anymore after I update my device ?
Because framaroot exploit security holes present in several devices which has been patched with update you have done, so exploits can't root your device anymore. Framaroot's exploits have a very short life to keep your device "less exposed" to others malicious application. Keep in mind that framaroot is not a permanent rooting application.

I loose root after update, what I can do to root my device now ?
An advice : if you want to have a chance to keep root after update, don't update with Kies or ODIN for samsung devices or don't flash system partition, prefer OTA update and use OTA survival feature in Superuser or SuperSU.
And if you have no choice, you can use the traditional method : flash tools specific to your device

Will framaroot include more exploits ?
Yes, but don't ask when since I don't know myself, it depend of the vendors fix response.

Framaroot crash when I select Gandalf exploit ?
Often the first time you launch Framaroot by selecting Gandalf as exploit, it crash Framaroot. Don't worry, in this case you have to re-launch Framaroot and select Gandalf again, the second time it should work.

What means error# on result ?
All errors less or equal to 9 mean your device is not vulnerable.
If you get error#10, give a try with Framaroot 1.5.3.
All other errors need some investigation about your kernel image.
ATTACHED FILES
File Type: apkFramaroot-1.4.1.apk - [Click for QR Code] (2.14 MB)
File Type: apkFramaroot-1.4.apk - [Click for QR Code] (2.14 MB)
File Type: apkFramaroot-1.3.apk - [Click for QR Code] (2.14 MB)
File Type: apkFramaroot-1.4.2.apk - [Click for QR Code] (2.16 MB)
File Type: apkFramaroot-1.4.3.apk - [Click for QR Code] (2.02 MB)
File Type: apkFramaroot-1.5.0.apk - [Click for QR Code] (2.02 MB)
File Type: apkFramaroot-1.5.1.apk - [Click for QR Code] (2.02 MB)
File Type: apkFramaroot-1.5.2.apk - [Click for QR Code] (2.03 MB)
File Type: apkFramaroot-1.5.3.apk - [Click for QR Code] (2.03 MB)
File Type: apkFramaroot-1.6.0.apk - [Click for QR Code] (2.03 MB)
File Type: apkFramaroot-1.6.1.apk - [Click for QR Code] (908.2 KB)
File Type: apkFramaroot-1.7.0.apk - [Click for QR Code] (1.03 MB)
File Type: apkFramaroot-1.7.1.apk - [Click for QR Code] (1.03 MB)
File Type: apkFramaroot-1.8.0.apk - [Click for QR Code] (1.03 MB)
File Type: apkFramaroot-1.8.1.apk - [Click for QR Code] (1.03 MB)

How to ROOT Acer Liquid S2 / S520 via Superboot Method

How to ROOT Acer Liquid S2 / S520 via Superboot Method



Requirement
  • USB drivers for S520 installed on your PC
  • The device must have debug mode activated

Package

Root SuperBoot for S520


Install
  • Unzip the package on your computer
  • Start the root_S520.cmd script
  • Plug your device (with USB debug activated)
  • Follow the instructions
  • At the end, don't forget to install SuperSU from Play Store
  • Reboot your device, root is done

How to publish an App to Android App Market


Publish the app created with App Inventor in the Android Market

Publish the app created with App Inventor in the Android Market

We succeded and the guide should be final.

What I'm about to describe is created to overcome the impossibility of publishing apps created with App Inventor in the Android Market

What you need:

  • 1.6 Java Development Kit and Runtime Environment 1.6 already installed on your PC
  • Android SDK already installed and running
  • Appinventor Extras
  • APKTool
  • Auto-Sign 6.5
  • .... A lot of Patience


1) Creating the key

This procedure is a one-off and we don't need to do those steps every time.

So, thanks to the JAVA SDK we will create a private key, which will be used for publishing our applications

From the Bin folder of the Java SDK we'll execute in a terminal:

codice:
keytool.exe -genkey -v -keystore my-release-key.keystore -alias aliasname -keyalg RSA -keysize 2048 -validity 10000
The Market requires that applications need to publish the private key has a duration subsequent to October 22, 2033, so we'll use a validity of 10000 days (over 27 years!).

2) Customize the Icon of the application

Download the APK file on a local folder on your computer.

We'll use AutoSigner for those steps: (thanks to Marcor Online info@marcoronline.tk for this part).
Open the apk file with 7zip.
Delete META-INF folder (which is the folder where the application contains the certificates, no longer valid after the change).
The images are generally stored in the folder res\drawable, and in particular the icon of the program is called ya.png. Extract all the images you want with your favorite software (we use 7zip).
Be careful not to change the size in pixels and not to change the name and extension.
Once you have completed the changes you go to put the files again into the apk (using 7zip) by simply dragging and overwriting the original.
Close 7zip and rename your program Launcher.apk.
Extract the contents of the Auto-Sign v0.65.exe and copy the Launcher.apk file inside the folderAuto-Sign\update\app.
Run the tool by the Auto-Sign v0.65.exe executable and iselect from the drop down menùLauncher.apk. (The name should been green. If not, you've made something wrong.)
Now click on Autosign and in a few seconds you'll get a confirmation message.
Inside the folder Auto-Sign\update\app will be a Launcher_signed.apk. You can delete the old file and keep only the signed one.

3) Edit the APK to be compatible with the Market

Decompile our apk

codice:
apktool -s pre-nomeapk.apk
in the just created folder called pre-nomeapk, go editing the AndroidManifest.xml file.

First we add the version of the application by adding the keyword "android: versionCode" and "android: versionName" in the keyword "package", just like this example:

codice:
<? xml version = "1.0" encoding = "UTF-8"?>
<manifest xmlns: android = "http://schemas.android.com/apk/res/android"
package = "appinventor.xyz.xyz"
android:versionCode = "1"
android:versionName = "1.0">
Specify the minimum version of Android is needed to run the application. Beware that the Market has a bug at the moment, and does not support applications compiled for Froyo android 2.2. Consider the following table:

codice:
API Level -> Android Platform Version
1 -> 1.0
2 -> 1.1
3 -> 1.5
4 -> 1.6
5 -> 2.0
6 -> 2.0.1
7 -> 2.1
8 -> 2.2
If your application needs Eclair we enter the following keyword:
codice:
<uses-sdk android:minSdkVersion="7" />
Finally fix the last things needed to make compatible the apk to the Market

Remove the android:icon keyworld on this line:

codice:
<activity android:label="123" android:icon="@drawable/ya" android:name=".Screen1">
and add it in this line:

codice:
<application android:label="XXXXX" android:debuggable="true">
Also on the line relative to the "application", remove the key "android_: debuggable"

In the end the AndroidManifest.xml will result like this:

codice:
<? xml version = "1.0" encoding = "UTF-8"?>
<manifest xmlns: android = "http://schemas.android.com/apk/res/android"
package = "appinventor.xyz.xyz"
android:versionCode = "1"
android:versionName = "1.0">
<uses-sdk android:minSdkVersion="3" />
......
<application android:label="XXXX" android:icon="@drawable/ya">
<activity android:label="123" android:name=".Screen1">
....
</activity>
</application>
</manifest>
Now compile the apk again:
codice:
apktool b pre-nomeapk
With 7zip open the apk and remove the file in the META-INF folder like:
codice:
ANDROIDK.SF
ANDROIDK.RSA
File allegati File allegati

Everything you wanted to know about Li-Ion batteries but were afraid to ask!

Everything you wanted to know about Li-Ion batteries but were afraid to ask!

So after noticing how much of a difference people get in their battery lives, I've decided to do some research and make a guide-line that will give us all we need to know about properly using our batteries. First part is a general information and usage techniques for LIBs, second part is taken from Google materials on Android-powered devices (G1, Magic, Droid, Nexus One, etc).

Sources:

Wikipedia http://en.wikipedia.org/wiki/Lithium-ion_battery
BatteryUniversity http://www.batteryuniversity.com/parttwo-34.htm
Google IO Conference 2009 - http://www.youtube.com/watch?v=OUemfrKe65c
Electropaedia - http://www.mpoweruk.com/life.htm
xda-Developers - http://forum.xda-developers.com/

General Lithium-Ion Battery (LIB) Usage:
  1. • Discharging your LIB fully (or less than 2.4 Volt per cell) is bad for the battery. Every time you do that, it can be said that small part of your battery (some cells) dies (they forever lose their charge). Do not store your batteries depleted, there's a high chance they will die completely or will become very "weak".
  2. • You cannot restore bad LIBs by overloading/heating/praying. You gotta go buy a new one. They DO degrade overtime, some cells naturally lose the ability to gain/give electricity.
  3. • Although it is said that LIBs do not have memory, it's not entirely true. LIBs have gauges that monitor performance of cells, and if you do a lot of small charges, it won't let those gauges to monitor a full battery potential, causing an invalid indication of charge level. A complete charge/discharge should be made when battery capacity seems reduced, that will calibrate gauges and they will provide your phone with correct charge level status. A full charge/discharge cycle should be done every 30 (or so) partial charges.
  4. • LIBs have a shelf-life. Do not buy them to store them. Use them early, use them often, they will die whether you use them or not. Do not buy LIBs to use them in 6 months/year/etc, buy them right before actually using them.
  5. • LIBs have short lives (in comparison to NiCa batteries, etc). You should expect to buy a new battery in 2-3 years after being manufactured. It is caused by internal oxidation and there's nothing you can do to stop or prevent that.
  6. • Worst LIB treatment is to keep it at 100% charge level at high temperature (think laptop/phone under direct sunlight, like car dashboard).
  7. • Best LIB treatment, or LIBs "favorite" charge level - 40%. That's also the usual charge level you buy them with.
  8. • LIBs don't like heat. For example, while always at 100%, typical LIB in a laptop, at temperatures of 25C (77F) will lose 20% (twenty percent!) of full capacity per year. That capacity loss is reduced to 6% (six percent) at 0C (32F), and increased to 35% loss at 40C (104F). So, keep them cool (LIBs like fridges), don't let your devices sit in the sun or overheat at charge. Also, keep in mind that while in use, battery will be significantly hotter than phone/outside environment
  9. • LIBs like frequent partial charges/discharges more than they like full charges/discharges.

General Android power usage advice from google:
  1. • Although this part is somewhat controversial, they do recommend having a complete, full FIRST charge to be made. If time allows, a preferred time for the first charge is 12 hours. This may have more to do with the OS than the battery.
  2. • Battery on a Android device, in average, will last about a full day with normal use (some videos, mail, calls). That's what you should kind-of expect.
  3. • Speaking in averages, "idling" 3G/EDGE connection (when phone is sleeping and no data is transferred through 3G), drains almost no energy. Just a little more than having 3G/EDGE radio off completely. So when no apps are using 3G, you don't need to keep it off.
  4. • Same goes to WiFi connection - although it's on, if there is no data flowing through it, it uses almost no energy.
  5. • At full throughput (100% data flow), EDGE is using more energy than 3G. In average, 3G is more energy-efficient than EDGE.
  6. • WiFi is using more energy than 3G (when both are at 100% use), but since it transfers files much faster and then goes to "sleep", it's actually recommended to use WiFi whenever possible. Since it'll "sleep" more often than 3G, overall it will use much less battery than using 3G.
  7. • Some bad apps or widgets can use android's "WakeLock", keeping CPU at 100%, screen always-on, or both. I myself have encountered such widget (I won't mention the name, it's in the market) that used a WakeLock to keep CPU spun-up at 100% all the time. That makes a huge impact on battery life. My advice - use a CPU profiling app to monitor the CPU - make sure that CPU slows down by itself when it's not used. So, beware of such widgets/apps. To check for CPU cycles, many recommend OSMonitor (free from market, install it, go to options, sort by "Load" in descending order. It'll give you "busiest" processes at the top). At rest you should be getting about 10-20% for OSMonitor itself, and 1-10% Android System. At rest, everything else should be 0-1%.
  8. • Android slows down CPU when not in use by itself, as a built-in feature. Apps that throttle/change CPU frequency, are not necessarily needed.


All this info comes from those reputable resources I mentioned above, I didn't make any of it up.

Installing Stock ROM Samsung Galaxy s2 SGH-T989





Install Stock T989UVMC6 Android 4.1.2 JB Firmware on Samsung Galaxy S 2 SGH-T989

This method is called manual flashing by using Odin downloader and the original stock firmware, for we can’t upgrade on kies or OTA anymore after installing unofficial firmware on our devices previously.

Disclaimer: We shall not be held responsible if anything happens to your device by following this guide. Proceed at your own risk.This procedure is for advance users only, typical users may only upgrade only thru Kies or via OTA and may not use this method.

Important!

- Back up all important files before proceeding. Although the Internal memory and microSD card are both left alone during after the flash process for this firmware is a non wipe version. But all your settings and configuration will all be reset. So, be sure to have a back up all of it for safety.
- If your device currently runs with any custom ROM, you may ask any assistance first from your ROM developer on how to safely return back to official stock to get rid of any issues.
- Fully recharge your phone’s battery.
- Use Windows-based OSX PC/laptop, Odin will not work on MAC OSX
ODIN http://hotfile.com/dl/161620048/6c6d...v3.07.rar.html
USB DRIVER https://hotfile.com/dl/169667640/bd9...river.zip.html

Grab the original T989UVMC6 stock ROM:
http://www.hotfile.com/dl/202091699/...6_TMB.zip.html

1) “Extract” or “unzip” the downloaded stock ROM to get the .tar.md5 file.
2) Run Odin3_v3.07.exe on PC desktop

3) In Odin - DO NOT CHECK the RE-PARTITION check box, only both ‘Auto Reboot’ and ‘F-Reset’ left checked.

4) Click on the PDA button then browse to the folder where you extracted the stock ROM “tar file”


‘T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5′

5. Reboot the phone in download mode

5) Once the phone in download mode screen, connect the PC USB cable To Phone. In Odin, the ID:COM box will change its color and its an indication that the device is connected properly to PC. If you still do not get any results, try another USB port on your computer.

6) Click the Start button to begin flashing.

7) Wait until it finishes or watch out for the word “PASS”.

Once the phone completely reboots, perform wipe/factory reset to get a fresher firmware installation.
1. Hold Power and Volume Up together, this will switch the device into recovery mode.
2. Release Power after holding it for a second but continue to hold the Volume Up button until recovery menu appears.

Select wipe cache
Select wipe data/factory reset.
Select reboot

That’s all! your Samsung Galaxy S II SGH-T989 now fully installed or restored to the original Android 4.1.2 Jelly bean

Samsung opens 60 dedicated stores in Europe with Carphone warehouse

Samsung opens 60 dedicated stores in Europe with Carphone warehouse


Samsung Electronics is joining forces with retailer Carphone Warehouse to create 60 dedicated Samsung stores in Europe, hoping that will help keep the growing competition in the Android smartphone market at bay.
The stores will be opened in the next three months across the U.K., Ireland, Germany, Spain, Portugal, Sweden and the Netherlands. The 60 stores will be a mixture of new locations and of existing Carphone Warehouse locations that will be converted to sell Samsung products, according to a Carphone Warehouse spokeswoman. About a third of the stores will be in the U.K. making it the largest market, she said.
The stores will sell smartphones, tablets, laptops and wearables, according to Samsung. With the European economy improving, the company sees an opportunity to increase sales with this push. Also, while consumers knows its smartphones and tablets, the dedicated stores will draw more attention to its laptops and the Galaxy Gear smartwatch, Samsung said.
Dedicated stores have been a mixed bag for manufacturers of consumer electronics. While Apple's chain of stores has flourished, other manufacturers, such as Nokia, are closing down their retail operations.
Samsung's retail push follows the opening of three stand-alone stores in Spain last year, also operated by Carphone Warehouse, so Samsung is convinced it has found a winning concept.
"The deal will benefit both sides. Samsung is desperate to replicate Apple's famous retail store experience, while Carphone Warehouse badly needs to develop fresh revenue streams in the saturated European mobile market. I expect Samsung to use its flagship stores as showrooms to generate a feel-good factor around the brand," said Neil Mawston , executive director at Strategy Analytics.
As all markets mature and become more crowded, retail becomes more critical. However, whether the stores can remain profitable long-term, as more sales of consumer electronics shift online, remains to be seen, according to Mawston.
Last year Samsung extended its worldwide lead over Apple to 160.5 million smartphones, but the company isn't impervious to increased competition in the smartphone sector. Its market share dropped from 29.1 percent to 28.8 percent year on year during fourth quarter, while Huawei Technologies, Lenovo and LG Electronics all increased their share, according to IDC.
"Samsung is a bit like Nokia a few years ago; very dominant, biggest product portfolio and biggest distribution, but everyone is gunning for them," said Mawston

UA-55000532-1